Brand_Name_or_Equal__Salient_Characteristics.docx
DOCX document 36 KB Posted
- Attached to
- Smartlogic Semaphore Tool Federal contract opportunity
- Solicitation number
- SECHQ115Q0119
- Issued by
- Securities and Exchange Commission
About this file
Attachment A - Brand Name or Equal Form
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 1449.pdf | ||
| SEC_CLAUSES.rtf | RTF text file |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment A - Brand Name or Equal Salient Characteristics SmartLogic – Semaphore: Taxonomy Tool
1. Identification of the item by generic descriptions.
· The SEC requires the purchase of a taxonomy tool to meet the taxonomy needs of OCIE. The tool must automate the classification of existing documents and new documents uploaded to SharePoint, TRENDS/Oracle UCM, and potentially other repositories. This will remove the need for manual tagging and greatly enhance SEC’s search capabilities by ensuring all documents are tagged and by providing more accurate results. The tool must integrate with the Oracle Fusion Middleware (OFMW) platform at SEC (using Oracle Text Search) “out of the box” and the new TRENDS OFMW pilot.
2. Brand name information.
· Make - SmartLogic Semaphore
· Oracle WebCenter Content connector for Semaphore
3. Name of manufacturer, producer, or distributor of the item and complete address.
· SmartLogic Semaphore:
· Manufacturer: SmartLogic
· Producer: SmartLogic
· Complete Address: 560 S. WINCHESTER BLVD, SUITE 500 SAN JOSE, CALIFORNIA, 95128
· Oracle WebCenter Content connector for Semaphore:
· Manufacturer: Team Informatics
· Producer: Team Informatics
· Complete Address: 1453 Helmo Ave North, Oakdale, MN 55128
4. Benchmark for performance (hardware or software).
· N/A
5. The key functional requirements.
· The tool must integrate with SharePoint 2010/2013 and Oracle WebCenter Content/Oracle Text Search out of the box
· The tool must integrate with TRENDS OFMW
· The tool must meet the following additional business requirements:
| Req ID |
| Requirement |
| 1 |
| The tool needs to support the Oracle 11g platform |
| 2 |
| The tool should automatically identify and tag documents when they are uploaded from TRENDS. This will help build the right tags against existing NEP taxonomy. Users can still optionally add tags manually as well |
| 3 |
| The tool should enable searching on metadata/tags and aliases (e.g. facet navigation) |
| 4 |
| An Admin should be able maintain and edit the taxonomy/metadata fields for selection |
| 5 |
| The tool needs to be able to represent/utilize the current NEP taxonomy |
| 6 |
| The tool should support integration with Oracle Web Center/UCM and optionally support SharePoint 2010 FAST Search |
| 7 |
| The tool shall allow documents to be tagged with a pre-existing taxonomy; All current documents in UCM repository must be tagged |
| 8 |
| When changes to the taxonomy are made, changes must be propagated to all existing documents |
| 9 |
| The tool should integrate with TRENDS; search and tagging of uploaded content should occur through the TRENDS application. End users should not “see” the taxonomy tool; integration should be seamless with TRENDS |
| 10 |
| The tool shall enable nested tagging. E.g. a document may be tagged as “Correspondence->Email” as its Doc Type since “Email’ is nested within “Correspondence”. Alternatively, the document can be tagged as “Correspondence” without further specificity. |
| 11 |
| The tool shall enable multiple sub-taxonomy tagging (tagging with various sub-taxonomies). E.g. a document may be tagged with “AML” as its Subject Category, as well as “Accountant” as its Entity Type. |
| 12 |
| The tool shall enable tag “aliases” (e.g. an alias for Anti Money Laundering is “AML”). |
| 13 |
| The tool shall support associative relationships between tags. E.g. Subject Category “Books and Records” is associated with the 40IA Act (Rule 204-2, and Sections 204 and 203(b)(3), the 40IC Act (Section 31, and Rules 31a-1, 31a-2, and 31a-3), and the 34 Act (Rules 17a-1, 17a-2, 17a-3, 17a-4, etc.). |
| 14 |
| The tool shall return documents that are associated with searched tags. I.e., using the example above, if searching for “Books and Records”, the result set will include documents tagged with, for example, the 40IA Act Rule 204-2. |
| 15 |
| Admin and end users shall be able to tag data objects other than documents or files with NEP Taxonomy terms. CLOBs are one example of the “non-documents” upon which we need to apply meta-data, but presumably, meta-data should be applicable to any data type. Practically speaking, it would pertain mostly to CLOB or varchar/text fields. Another example: on our SharePoint sites we apply meta-data to documents and non-documents (list items, or what we are referring to as “data objects” for lack of a better word) |
6. Timeframe for being operational or for delivery.
· As soon as possible so as to be implemented with the TRENDS OFMW pilot delivery.
Offerors proposing to furnish an equal product, in accordance with the “Brand Name or Equal”' provision of this solicitation, shall insert the following description for the product.
· Bidding on:
· Manufacturer's Name:
· Address:
· Product Name (if any):
· Product make, model, or catalog description:
Offerors shall also be responsible for submitting all additional information on the above product necessary for the Government to determine whether the product offered meets the salient characteristics of the brand name as listed in the solicitation.
File details come from the government source that posted it. Updated .