SOURCES SOUGHT
70 -- Search Broker Capability
- Notice Date
- 5/28/2002
- Notice Type
- Sources Sought
- Contracting Office
- Defense Information Systems Agency, Acquisition Directorate, DITCO-NCR, 5111 Leesburg Pike Skyline 5, Suite 900A, Falls Church, VA, 22041-3206
- ZIP Code
- 22041-3206
- Solicitation Number
- NAICS511210
- Response Due
- 6/28/2002
- Archive Date
- 7/13/2002
- Point of Contact
- Charlotte Hunter, Contract Specialist, Phone (703)681-0923, Fax (703)681-1211,
- E-Mail Address
-
hunterc@ncr.disa.mil
- Description
- The Defense Information Systems Agency (DISA), Information Dissemination Management (IDM) Division is seeking sources that are capable of providing a product, preferably a commercial "off-the-shelf", with metadata search engine capability for the Secret Internet Protocol Router Network (SIPRNet). Please refer to the table for a listing of specific requirements the product must target. The Defense Information Systems Agency (DISA), IDM Division is issuing this Request for Information (RFI) to industry. THIS IS A REQUEST FOR INFORMATION ONLY!! It is neither a Request for Proposal (RFP)/solicitation, nor an indication that DISA will contract for the items and services described in this RFI. There is no obligation on the part of the Government to acquire any products or services. The Government does not intend to award a contract solely on the basis of the RFI. The Government will NOT pay for information received in response to this RFI. Submitted documents will NOT be returned to those firms who provide responses to this RFI. The objective of this RFI is to obtain market research in order to assist in the development of preliminary acquisition planning. All interested parties must respond via e-mail with information on their product and services with sufficient technical and cost information to allow for a detailed evaluation to the Technical Point of Contact, (POC) Ginny Parsons, PH: (703) 681-2474, email: parson1g@ncr.disa.mil or Acquisition Liaison POC Patsy Lake, PH: (703) 882-1008, email: lakep@ncr.disa.mil no later than 20 June 2002. The subject line of the e-mail should be "Search Broker Capability". The NAICS code is 511210. Proprietary information will be safeguarded in accordance with the applicable Government regulations. The vendor will incur, if applicable, all costs associated with modifying the product in order to meet the requirements listed. Firms who wish to respond to this RFI should include: a brief summary of the products offered in response to this RFI, a statement indicating an interest and capability to produce the product as described, an estimate of the time required to develop, test, and deliver the product and supporting documentation, and a cost/rough order of magnitude (ROM) for the licensing and maintenance options for the product is needed for budgetary planning purposes. IDM is the subset of information management that addresses the awareness, access, delivery, and dissemination support of information for the warfighter. IDM enterprise services will provide a common suite of distributed, network capabilities across domains to facilitate the "push" and "pull" of information. IDM will enable network-centric information operations to support command and control requirements. The following is a summary of the four IDM core services and their associated functions: Awareness: Search Services, Advertising, and Cataloging; Access: Information Profiling and Policy Management; Delivery: Retrieval Services, Resource Monitoring, and Delivery Planning; and Support : Security, Directory, and Catalog Services The IDM architecture will be implemented in accordance with the Department of Defense (DoD) Global Information Grid (GIG) and Joint Technical Architecture (JTA) specifications. An open architecture will be essential to enable the horizontal and vertical integration of existing DoD information systems. IDM enterprise services will utilize "cross-platform" commercial standards to provide legacy system integration as well as to promote future expansion capabilities for technology insertion. A scalable architecture will be required to support the secure data integration of "forward-deployed" repositories for metadata search and retrieval between operational and support infrastructures. The IDM enterprise services architecture must be developed within the DoD Network Operations (NETOPS) framework. It must complement existing as well as planned DoD information assurance (IA) countermeasures (i.e. intrusion detection, firewalls, Public Key Infrastructure (PKI), and Common Access Cards (CAC), etc) as well as on-going DoD network management initiatives (i.e. the Joint Network Management System (JNMS)). The following capabilities have been identified for the IDM Metadata Search Engine in accordance with DoD enterprise service requirements: a) Metadata Search and Retrieval, b) Database Publishing / Information Source Cataloging and "Smart" Updates, c) Information Profiling (Profile Management for Information Producers, Users, and Commanders; Dynamic Profiling; and Profile-Driven Information Delivery for "Planning" and "Survival"), d) Information Prioritization, e) Policy Management, f) Knowledge Management / Content Management, g) Secure Access (Identification, Authentication, Data Integrity, Non-Repudiation), h) Network Management Integration (i.e. JNMS) (Information Flow Awareness / "Smart Routing" to monitor and change the data communications path for "Intelligent" Information Dissemination), h) Scalability [Multiple Format Searching (e.g. Word documents, Adobe Acrobat "pdf" files, images, briefings, audio, video, etc), Organizational Domain Integration / Cross-Platform Protocol Usage (e.g. Extensible Markup Language (XML)), Terrestrial-to-Satellite Integration (Global Broadcast Service (GBS) and future evolution to two-way data/image/video transmissions), Support remote locations or users with limited bandwidth, e.g., tactical environment, Wireless Integration, Data, Voice, Imagery, and Video Streaming, and Storage / Archive Capabilities]. The IDM Capstone Requirements Document (CRD) should be used as a reference for a more in-depth discussion of threshold and objective IDM requirements. In addition, the GIG CRD, as well as Joint Vision 2020, provides a high-level perspective for IDM deployment capabilities and functionality. Items of Consideration DESCRIPTION/DIRECTIVE 1 (General) Preference will be given to COTS based solutions. 2 (General) The product shall be server based and web enabled. 3 (Searching) The product shall have a capability to search multiple metadata catalogs using brokered requests. 4 (Tracking) The product shall provide facilities that limit the time spent waiting for a search node to respond to a search query. 5 (Tracking) The product shall have a tracking feature for a system administrator to track/monitor the health of the product. 6 (Tracking) The product shall provide a capability to capture and report searches, search results, and users. 7 (Searching) The product shall combine search results from a variety of information sources into a single list and provide that list including a cross server relevance ranking to the user 8 (Searching) The product shall combine duplicate entries from the search nodes into a single entry before presenting the results to the user. 9 (Searching) The product shall provide source attribution for each returned result. 10 (Integration) The product shall serve as an information source to other search products. 11 (Integration) The product shall operate in the DII COE operational environment secured for use in the classified environment. 12 (Communication) The product shall communicate with the information sources using standard HTML or XML page transmission. 13 (Integration) The product shall be used with MS Internet Explorer as well as Netscape browser. 14 (Security) The product shall provide the ability to use external directory services for authentication. 15 (Support) The product shall include written documentation regarding its installation, use, management, and operation. 16 (Integration) The product shall allow the import and modification of the schema used to characterize information products. 17 (Support) The product shall allow policy based operations constrained by user, resource, and access. 18 (Configuration) The product shall dynamically configurable style sheets to allow conformance with DISA style guidelines. (www.disa.mil) 19 (Support) The product shall provide Section 508 compliance interface. 20 (Support) The product shall include an on-line help capability. The following criteria will be used to evaluate Metadata Search Engine products for implementation of IDM enterprise services: a) Search Accuracy / Relevance, b) Search Time, c) Advanced Search Capabilities, d) Profile Development / Query Profile Support, e) Publishing / Cataloging Capabilities, f) Display Format (e.g. Summaries, "Drill-Down" Capability for Sub-Category Results), g) Data Filtering, h) Change Notification, i) Advertisement Support, j) Integration Broker Methodology, k) Structured / Unstructured Content Management, l) Natural Language Support (e.g. phonetics, spelling errors, etc), m) Distributed Architecture Methodology (Scalability, Redundancy, Disaster Recovery), n) Security (Confidentiality, Integrity, Availability), and o) Joint Technical Architecture (JTA) / US Imagery and Geospatial Information Service Technical Architecture (UTA) / Commercial Standards Compliance.
- Record
- SN00083797-W 20020530/020528213107 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |