SPECIAL NOTICE
99 -- Pilot for Retrospective Metadata Tagging
- Notice Date
- 2/6/2003
- Notice Type
- Special Notice
- Contracting Office
- Other Defense Agencies, Defense Intelligence Agency, Virginia Contracting Activity (ZD50), 200 MacDill Boulevard Post Office Box 46563, Washington, DC, 20035-6563
- ZIP Code
- 20035-6563
- Solicitation Number
- Reference-Number-RPI5990
- Archive Date
- 5/15/2003
- Point of Contact
- DeBorah Lane, Contract , Phone 202-231-8460, Fax 202-231-2831, - James Dashiell, Branch Chief - CO, Phone (202) 231-2947, Fax (202) 231-2831,
- E-Mail Address
-
DeBorah.Lane@dia.mil, jim.dashiell@dia.mil
- Description
- STATEMENT OF WORK Pilot for Retrospective Metadata Tagging 1. Purpose: The purpose of this SOW is twofold: the Government desires to understand what the commercial-off the-shelf (COTS) landscape looks like for the problem domain described below and to conduct several proof of concept explorations identified from that landscape. The Government seeks to identify potential pilot approaches and techniques available from commercial industry to perform markup and/or indexing of heterogeneous stores using metadata to improve accessibility, relevance (precision + recall) to the community?s legacy data. The proposed solutions shall be based on the Extensible Markup Language (XML) and include the identification of data elements and objects with the goal of improving access through improved content marking or advanced indexing techniques. The information gathered from this pilot will be applied to various heterogeneous data stores located throughout a wide community. The proposed approach shall be based on XML and it must be based on a commercially available capability. The end state of this pilot is to identify a scalable methodology that ultimately demonstrates relevancy, the value of using the Intelligence Community defined metadata when data is searched and/or accessed in an integrated manner. This pilot study is a three (3) month level-of-effort. 2. Scope And Objectives The scope of the task includes the following key objectives:  Provide a proven and cost effective methodology for retrospectively applying XML metadata tagging and/or indexing a suite of heterogeneous, legacy data stores to include, but not limited to, unstructured and semi-structured data in multiple formats (.doc, html, etc.) and textual fields in structured databases.  More specifically the Intelligence Community?s Markup Language (ICML) should be applied to tag unstructured and semi-structured data found in legacy text reports.  Where applicable, elements of ICML should be used to facilitate searches and/or access across text fields in databases. A searchable index would point to relevant occurrences within the existing legacy databases, for example.  Provide a pilot demonstration of the proposed technology approach and demonstrate how the proposed approach satisfies the above requirements. The demonstration should illustrate how the specific tools used either achieve the tagging of legacy data and/or return (via an indexed full search) all instances of that information in the legacy data. As an example, a search against a specific Basic Encyclopedia number/facility/person should return pointers to the full content in unstructured, semi structured and structured data sources published within a certain time period (metadata) that discusses that BE number/facility. 3. Background: Currently, many of the needed data sources are held in ?stove-pipe? systems that do not allow easy fusion of information across multiple sources. Inability to seamlessly access the ?right? data from multiple sources makes many user tasks either impossible or difficult to accomplish in the time required. Metadata is ?data about the data?. The Intelligence Community would like to leverage metadata to facilitate the retrieval of information from automated systems in order to increase the relevance (precision + recall) of the data returned. For the purposes of this pilot, metadata includes standardized information about security classification, the producer and subject content among many other elements of interest. Metadata has the potential to describe an entire document, a field in a database, or a single word as needed. By applying standardized metadata to multiple systems, the task of automating access to those systems is greatly simplified. Metadata tagging using the Extensible Markup Language (XML) is presently the leading technology currently available to address this situation and has been selected by the community to address. The Intelligence Community has developed several documents on its markup language that will be made available. The sharing of data and information is a mission and business essential capability within the Intelligence Community (IC). The IC System for Information Sharing (ICSIS) architecture defines the underlying framework that facilitates data and information sharing. To fully realize ICSIS precepts, the use of metadata is critical to enabling an agile environment where data and information is accessed and exchanged efficiently across the IC. It is the intent of the IC to use IC standardized metadata tagging and metadata markup (Intelligence Community Markup Language?ICML) when exchanging or sharing data within the IC. To enhance data sharing and to facilitate metadata queries, the IC metadata repository is used to register all metadata and metadata markup standards created or used by the IC and will serve as the baseline for the IC Metadata Standard for Products (ICMSP). 4. References a. ICSIS Phase One, Concept of Operations, 28 January 2002 b. W3C Recommendation REC-xml-20001006, Extensible Markup Language (XML) 1.0 (Second Edition) c. W3C Recommendation REC-xslt-19991116, XSL Transformations (XSLT) Version 1.0 d. Intelligence Community Markup Language (ICML) v1.0, Summer 2002 e. IC Core Metadata V 1.0, 15 July 2002 f. IC Information Security Marking V1.0, 15 July 2002 g. Data Element Dictionary for the Information Security Marking version 1.0, 15 July 2002 h. ICML v1.0a Data Element Dictionary September 16, 2002 5. Requirements. 5.1 Technical Requirements: Provide a formal methodology and demonstration of the ability to conduct automated metadata tagging of information across heterogeneous data sources applying the ICML. The data to be processed includes, but is not limited to, softcopy and hard copy text based, formatted messages, desktop publications (including those produced by MS Word, Acrobat, PowerPoint, Excel, as well as other current and past desktop application formats). Use of existing metadata should be exploited where feasible. ICML defines a minimal set of mandatory data elements that must be used. The proof of concept should attempt to discover and or tag the minimal mandatory set defined in the standard. Many finished intelligence products and other materials have previously been processed using various forms of metadata to include abstracts, indices, thesauri terms, and product identification codes. 5.2. Period of Performance. From Date of Award for a period of Ninety (90) Days. 5.2.1 Task 1. Data analysis. The Government will provide a mix of unstructured, semi structured and structured data to be used in the proof of concept. The data will be Sensitive Compartmented Information (SCI). A representative mix might include finished intelligence reports, message traffic, and a copy of a database. 5.2.2 Task 2. Conduct a pilot demonstration to show how data is metadata tagged using various examples of the intelligence legacy data stores based on analysis completed in Task 1. Show how a search accurately returns all relevant data across the data stores. Explain the capabilities and limitations of the technology and the accuracy associated with the results. Provide the government with an in-depth, detailed technical understanding in an annotated briefing (PowerPoint brief with detailed notes) explaining the technical components used in the pilot to achieve the results. 5.2.3 Task 3. Based on the results gained from Task 2, validate the expected costing model for a larger, follow-on effort, identify the best overall strategy for tagging the actual data, test the solution with existing search tools (Intelink is enhancing their search tools to leverage ICML). 6. Deliverables: 6.1 Deliverables Project Management Plan ? Due 15 days after contract award. Annotated Briefing -- The contractor shall thoroughly document the methodology and identify the technical solutions applied, how they were applied to meet the requirements of this level of effort, lessons learned. (60) days after contract start) --The Contractor shall be required to deliver various white papers, technical assessments and/or other briefings throughout the period of the contract. Frequency and subject will be determined by both the COR and the Contractor. Monthly Status Reports ? The Contractor shall provide the Government a status report, due 5 days after the end of each month. Demonstrations, Briefings and Conference Support ? The contractor shall provide various briefings and demonstration in support to the program manager. Some local travel may be required. Support for briefings at one technical conference may be required. 6.2 Quality Assurance The Contractor shall work independently, but will coordinate with the PMO Office as may be necessary to ensure quality application of staffing resources for tasked work. 6.3 Documentation All documentation that falls within the work scope of this SOW shall adhere to the guidance provided by DIA. All documentation shall be free of spelling and grammar errors. Microsoft Word 2002 is the standard format for all documentation. The Contractor shall deliver both hard- and soft-copy documentation, where required. 7.4 Personnel Standards of Conduct Contractor management is responsible for quickly resolving al issues with regards to Contractor employees, especially as relates to programmatic performance. The Contractor shall maintain continuity in expertise to ensure tasks are delivered on time. The Contractor shall establish or maintain the necessary relationships with all Government Contractors associated with the project. The Contractor shall ensure all employees conduct themselves professionally as well as show proper tact and diplomacy while in liaison over project review. 7.5 Management Structure The Government Program Manager (PM) will exercise day-to-day program management. The PM shall be the focal point for all activities associated with the SOW. Minutes from all scheduled meetings shall be the responsibility for the meeting lead, and the responsibility of the Contractor. The format will be a bulleted summary, action items, and items for PMO review. The Contractor shall identify a Project Manager who will work with the Government's Project Manager on all matters related to the activities of this SOW. The Contractor Project Manager will collaborate with the Government Project Manager to develop and maintain a detailed work plan to include specific tasks, assignments, milestones and schedules. This Project Management Plan shall include planned labor hour and funding expenditure charts to facilitate Government and Contractor Project Managers? monitoring activities. The Contractor will develop such a Plan within 15 calendar days of award of the order resulting from this SOW. The Plan will be certified by the Government and Contractor Project Managers, and updated as required. Both the Government and Contractor Project Managers will document their concurrence on the initial PMP by signing/dating it. For each subsequent update, both will initial/date the revisions, documenting concurrence. The Contractor and Government Project Managers are responsible for providing appropriate labor skills to accomplish the work. 7.6 Management Subtasks The Contractor shall provide monthly progress reports to the PMO during the period of performance to assess progress. The Contractor shall regularly determine the status of effort and report monthly on progress toward accomplishment of contract requirements. The end of the month report shall present the status of contract funding. These reports shall document all concerns and requirements related to the project. 8. Special Provisions 8.1 Security Requirements. SI/TK access will be required for this contract. 8.2 Place of Performance. Between Contractors site and the Defense Intelligence Analysis Center (DIAC) at Bolling Air Force Base, Washington D.C. 8.3 Travel Requirements. Local travel may be necessary. 9. Government Project Manager. The Government Project Manager for this Order is TBD. The Government Project Manager delegated authority is as follows:  Provide technical direction and establish priorities within the scope of this SOW and the existing JIVA SI contract vehicle  Approve Contractor requests for Government-furnished materials (GFM)  Receive and inspect deliverables  Certify payment invoices 10. Inspection and Acceptance 10.1 Receiving Reports. Unless otherwise directed by the Contracting Officer, all receiving reports shall be submitted in accordance standard DFARs guidance. The Government's Project Manager will inspect and accept all deliverables, except Program Manager Reports submitted to the COR, and provide written evidence of such acceptances to the Contractor (file copy to Contracting Officer) for certifications to the Defense Finance and Accounting Service (DFAS). 10.2 Invoice and Payments. The Project Manager will certify payment invoices to DFAS in accordance with Agency guidelines unless directed otherwise by the Contracting Officer on the BPA order resulting from this SOW.
- Place of Performance
- Address: VIRGINIA CONTRACTING ACTIVITY, 200 MACDILL BLVD., BLDG 6000, BOLLING AIR FORCE BASE, WASHINGTON, D.C. 20340-5100
- Zip Code: 20340-5100
- Zip Code: 20340-5100
- Record
- SN00254946-W 20030208/030206213822 (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 |