Introduction .................................................................................................................................................. 3
1. SCOPE OF WORK: .................................................................................................................................. 3
1.1 Conduct assessment of what needs to be done to integrate I-Harvest into the existing INSCOM architecture. .............................................................................................................................................. 3
1.2 Install and configure the I-Harvest software on the existing IDC architecture ............................ 3
1.3 Conduct an I-Harvest software dry run test event ....................................................................... 4
1.4 Evaluate the I-Harvest software and how it meets required objectives ...................................... 4
1.5 Provide an information paper with options to integrate and enhance the I-Harvest tool to better support the existing enterprise ..................................................................................................... 4
2. STAFFING: .............................................................................................................................................. 4
3. DELIVERABLES: ...................................................................................................................................... 4
4. ACCEPTANCE CRITERIA: Acceptance criteria will be based on the sub-contractor’s ability to successfully meet the deliverables stated. Acceptance will be mutually agreed upon by the subcontractor and prime contractor. ................................................................................................................. 5
5. PAYMENT: ............................................................................................................................................. 5
6. PERIOD OF PERFORMANCE: .................................................................................................................. 5
7. PLACE OF PERFORMANC: ...................................................................................................................... 5
8. CONTRACT TYPE: ................................................................................................................................... 5
9. APPLICABLE DOCUMENTS ..................................................................................................................... 5
11. TECHNICAL POINTS OF CONTACT: John Clark (703)-942-9415 (Integration Lead) A.J. Clark
(786)897-5015 (Project Lead) ....................................................................................................................... 6
12. QUALITY REQUIREMENTS: N/A ......................................................................................................... 6
13. WARRANTY REQUIREMENTS: N/A .................................................................................................... 6
14. SECURITY REQUIREMENTS: N/A........................................................................................................ 6
15. SPECIAL REQUIREMENTS: N/A .......................................................................................................... 6
16. ATTACHMENTS / EXHIBITS: N/A........................................................................................................ 6

Introduction
This Statement of Work (SOW) addresses but is not limited to support to integrating the I-Harvest software on the INSCOM IDC network and connecting it with various components on that network
(Database, User interfaces, Alerts, etc) for purposes of evaluation. This effort includes software development engineering, project management, database development, and systems engineering as it relates to the objectives listed above. Additional ad-hoc support to the Information Assurance,
Documentation, and Testing portions of the overall task may be required.
1.
SCOPE OF WORK:
1.1
Conduct assessment of what needs to be done to integrate I-Harvest into the existing INSCOM architecture.
1.1.1
Establish necessary building access cards, clearances, workspace, network accounts etc
1.1.2
Review INSCOM database schemas and design sketch of connection mechanism
1.1.3
Review INSCOM databasing process for new information and design a connector to review new messages entering the enterprise
1.1.4
Analyze operating systems, environment and detail how applications will handle evolving security requirements. Ensure necessary client proxy and scripting engine is present in browser
1.1.5
Conduct network assessment to ensure choke-points do not exist and alerting can ensue. Identify what systems may be required to support the integration phase and develop a schedule to get them on-line
1.1.6
Establish test bed for unclassified development to expedite integration time
1.2
Install and configure the I-Harvest software on the existing IDC architecture
1.2.1
Connect I-Harvest software client modules with IDC web based query tools a.
Configure frame based applications b.
Proxy query tool to enable cross window queries / account for browser security
1.2.2
Integrate I-Harvest concept Knowledgebase / User Profiles on IDC network
1.2.3
Connect Concept Analysis & Recommendation (CAR) Server with IDC Network data repositories
1.2.4
Couple real time notification services with I-Harvest CAR Server and Analyst review tools (Jabber and others after review)

1.2.5
Develop I-Harvest user authentication capability to exploit current enterprise architecture access capabilities
1.3
Conduct an I-Harvest software dry run test event
1.3.1
Create test plan and scenario
1.3.2
Conduct test
1.3.3
Document test, lessons learned, and recommendations for future action
1.3.4
Conduct test follow-up to implement recommendations and lessons learned prior to evaluation
1.3.5
Configure necessary software components to support evaluation phase
1.3.6
Conduct user training
1.4
Evaluate the I-Harvest software and how it meets required objectives
1.4.1
Create evaluation plan and scenario
1.4.2
Conduct software evaluation
1.4.3
Document evaluation, lessons learned, and recommendations for future action
1.5
Provide an information paper with options to integrate and enhance the
I-Harvest tool to better support the existing enterprise
2.
STAFFING:
The Contractor shall provide One Project Manager, One Database Development Engineer, and One
Software Development Engineer. Contractor support is estimated to be required in the following allocations:

Project Manager --------------------------------------------------------- *100 Hours

Database Development Engineer --------------------------------- 560 Hours

Software Development Engineer ---------------------------------- 1,120 Hours
*Support from Project Manager is to be coordinated in conjunction with TST project lead prior to task execution
3.
DELIVERABLES:

The Contractor shall provide a cost report to accompany a monthly invoice for labor, travel, and other direct costs.


The Contractor shall provide periodic updates on the status of the project to include milestone information

The Contractor will submit a travel request in an agreed upon format to request all travel.

At the conclusion of each trip, the Contractor will submit a trip report to SAIC in an agreed upon

 format.
All travel costs over $75 require the Contractor to submit all receipts to SAIC with the expense report.
Test Plan – Contractor shall create test plan and scenario to ensure that I-Harvest software is sufficiently in place for a an evaluation by intelligence analysts
4.
ACCEPTANCE CRITERIA:
Acceptance criteria will be based on the sub-contractor’s ability to successfully meet the deliverables stated. Acceptance will be mutually agreed upon by the sub-contractor and prime contractor.
5.
PAYMENT:
Payment terms will be specified in follow-on contract documents.
6.
PERIOD OF PERFORMANCE:
The period of performance for this effort is December 17, 2007 through May 9, 2008.
7.
PLACE OF PERFORMANC:
The work performed in support of this SOW should occur at the end Customer’s facility on Ft. Belvoir in
Alexandria, VA; SAIC facilities in Alexandria, VA and Contractors facilities in Cambridge, MA
8.
CONTRACT TYPE:
The worked defined in this SOW will be provided under a Time and Material Subcontract.
9.
APPLICABLE DOCUMENTS
10.
In the event of a conflict between the SOW and any of the reference documents, the SOW shall take precedence. The sub-contractor shall use the following documents as guidelines. The subcontractor is expected to understand and implement, where practical, the contents of these documents.
MIL-STD-490A Specification Practices June 85
MIL-STD-498 Software Development & Documentation Dec 94

MIL-STD-1521B
MIL-DTL-31000A
MIL-STD-100G
MIL-STD-882C
DS-2610-142-01
Technical Reviews and Audits for Systems, Equipment, and Computer
Software June 85
Technical Data Packages, General Specification for Sep 91
Engineering Drawing Practices Sep 91
System Safety Program Requirements
DoDIIS Security Certification and Accreditation Guide, DS-2610-142-
01, April 2001
AR-25-2 Information Management: Management of Subsystems Information
Assurance. 14 November 2003
ISO 10007 Quality Management, Guidelines for CM 1995
DoD Information Technology Security Certification and Accreditation Process (DITSCAP)
DCID 6/3, Director of Central Intelligence (DCI) Directive (DCID) 6/3, Protecting Sensitive
Compartmented Information within Information Systems, 6 June 1999, Administratively updated 3 May
2002 (policy), and 12 April 2002 (manual)
11.
TECHNICAL POINTS OF CONTACT: John Clark (703)-942-9415 (Integration Lead)
A.J. Clark (786)897-5015 (Project Lead)
12.
QUALITY REQUIREMENTS: N/A
13.
WARRANTY REQUIREMENTS: N/A
14.
SECURITY REQUIREMENTS: N/A
15.
SPECIAL REQUIREMENTS: N/A
16.
ATTACHMENTS / EXHIBITS: N/A