Attachment_30_-_Integrated_Data_Environment.docx

Attachment 30 Integrated Data Environment

PM AAA

Amphibious Combat Vehicle

ACV-ATT-02002

Version 1.0

DISTRIBUTION A: Approved for public release: distribution unlimited.

Attachment 30, Section J

ACV-ATT-02002, v1.0 Page 4 of 10

Table of Contents

Requirements Pursuant to the Statement of Work (SOW) and in accordance with 48 C.F.R. § 227.7108, the Contractor shall provide, maintain, and use an Integrated Data Environment (IDE) to support the exchange, collaboration, archival, and use of UNCLASSIFIED, contract related data, including contract related technical data, computer software, computer software documentation, administrative data, financial data, and management data, in accordance with this IDE document. The Contractor shall store, maintain, and archive such data for the ACV Program in the IDE to reduce cycle time, cost, and administrative waste while at the same time establishing a collaborative environment for its continued exchange, management, archival, and use by all stakeholders designated by the Contractor and the Government.

Except where noted specifically on the DD-1423, the Contractor shall provide this service for items on the Data Accession List (DAL), management data, and technical data generated/maintained in digital format.

Contractor IDE The Contractor shall provide and manage the IDE throughout the life of the contract. The Contractor shall provide access to the IDE for 50 Government personnel. At the end of the contract, the Contractor shall deliver to the Government the full IDE equipment, support software/utilities, all databases developed on or in support of the ACV Program, and all ancillary documentation in commercial and/or Contractor format.

Minimum Capabilities The IDE shall be internet accessible. The IDE shall use a standard web browser application without the need to install or download additional client software. If necessary, the Contractor shall provide any software required for the Government to exercise the read-only capability at locations designated by the Program Contracting Officer (PCO) throughout the period of contract performance and shall provide digital media at the request of the PCO. Any software required for installation/download shall comply with Government information security requirements.

Navigation The IDE shall be logically ordered to permit ease of navigation, and shall include a search or query function within each application in order to more easily identify and locate data or information of interest.

Data Exchange The IDE shall allow for the exchange of contract documents and other data, including technical data, computer software, and computer software documentation, between the Contractor and the Government.

All data shall be of sufficient quality that the Government is able to read the data both online and in printed form. Data shall be virus-free and in a manipulative/editable format, including Microsoft Word, Excel, PowerPoint, Project and/or Access.

User Access The IDE shall be accessible by authorized users, including authorized Government users, 24 hours a day, and seven (7) days a week. Occasional periods of unavailability for maintenance purposes are allowed provided that all authorized users are provided at least 10 days advance notice, 48 hour warning notice and 24 hour final notice. The Contractor shall provide the Government (and/or Government support Contractors) electronic access to its IDE and the ability to download artifacts throughout the term of the contract.

Metadata The Contractor shall use Metadata to improve the search and query functions of the IDE. The Contractor shall propose the Metadata fields that shall be utilized and shall transfer with the document from the IDE to the Government portal. The Government will approve the Metadata fields that will transfer.

Data Management Contract Data Requirements List Management The Contractor shall plan for, generate, collect, prepare, publish, and distribute contractual data with content, format, and in quantities specified by the Contract Data Requirements List (CDRL) to the IDE. The Contractor shall be responsible for the management of changes, additions, and deletions of data items. The Contractor shall recommend items to be added, revised or deleted, as appropriate, and shall maintain the status of all data deliverables. The Contractor shall generate and maintain Contract Data Status information to monitor all CDRL activity (i.e., delivery, documentation, approvals due but not delivered, and status of delinquent data). This data shall be available via the IDE in the form of a dashboard that visualizes the Contract Data Status.

Data Accession List The Contractor shall provide the Government access to internal documents produced to design, develop, test, and manage the program. The Contractor shall make available, for review by the Government on an electronic data management system, all internal data generated in compliance with contractual tasks and documented in the DAL (ref CDRL A054).

Data Interaction Approved users shall have the ability to view, print, and download information residing on the IDE including the ability to access and interact with all modified or archived versions of such information. Configuration controlled items will permit read only access but will allow users to download them for external review and printing.

Error Checking The IDE shall provide error-checking protocols to ensure the correct and complete transmission of data when data is transmitted via electronic means.

Archival The IDE shall include an archive library of all submittals exchanged via the data exchange process.

Security/Control The security/protection of all data (Unclassified, Classified, Proprietary and privacy related) shall be the responsibility of the Contractor. For further guidance refer to Section 3.1.2 Security of the SOW.

IDE Security The Contractor shall implement security safeguards to detect and prevent data aggregation and unauthorized access, modification, release, or destruction of all data contained in the IDE. The Contractor shall secure the web-server using the Defense Information Systems Agency (DISA) Web server Security Technical Implementation Guide (STIG) Version 7 release 1 or the newest version and release of the STIG as of the date of establishment of the IDE as guidance. The Contractor shall report immediately all instances of possible cyber intrusion to the ACV PCO who in concert with the Contractor will make appropriate decisions based upon the incident and ongoing response.

Security Operation The Contractor IDE shall only host unclassified data. The IDE shall not host classified data. All classified data shall be controlled and delivered to the Government in accordance with DoD 5200.1-R, Chapter 7 and Attachment 4. Questions concerning the classification or submittal of classified data shall be referred to the ACV PCO. The Contractor shall report immediately all instances of possible data spillage to the ACV PCO. Spillage of classified information shall be reported in accordance with DoD 5200.01, vol. 3.

Markings All technical data, computer software, and computer software documentation, including in-process, shall contain appropriate markings.

Data Rights All technical data, computer software, and computer software documentation residing in the IDE shall be marked in accordance with the Rights in the Technical Data and Computer Software and Computer Software Documentation clauses of the contract.

Distribution Statements Distribution statements shall be included on the title screen(s)/cover page of each technical document indicating the extent of permissible distribution without further authorization or approval of the controlling DoD office. Appropriate distribution statements are provided in DoD Directive 5230.24, Distribution Statements on Technical Documents.

Export Control Warnings All technical documents containing export-controlled technical data shall be marked on the title screen(s)/cover page with an Export-Control Warning Notice as provided in DoD Directive 5230.25, Withholding of Unclassified Technical Data from Public Disclosure.

Access Control Access to the IDE shall be restricted to authorized users through an appropriate web-enabled application. The IDE shall provide various levels of access privileges at the user level. The IDE shall be capable of limiting access to file-level granularity, allowing access to specific files to selected user only. The PCO will provide the Contractor with the information of authorized users, which will include contracted support personnel, and the levels of access authorized to each user. The Contractor shall manage authorized user access and provide a list of valid users throughout the performance period.

Access Controls shall account for limitations in the Government’s rights to use such data by Government and contract support personnel. Controls shall include the administration of appropriate non-disclosure agreements pursuant to 48 C.F.R. § 227.7103-7 (2011) when necessary. Data from other Contractors, including sub-Contractors, shall be protected in accordance with applicable Contractor agreements and Rights in Technical Data and Computer Software and Computer Software Documentation clauses of the contract.

Accountability/Audit The Contractor shall implement safeguards to monitor user activities within the IDE and provide an audit trail of IDE use and performance. The IDE shall include a security audit capability that documents the identity of the user accessing the system, date and time of each access, all login attempts (failed or successful), and activities that might modify, bypass, or negate safeguards controlled by the IDE. The IDE shall archive this information and be capable of generating audit reports. The IDE shall protect audit trails from unauthorized access, modification, or deletion.

Data Delivery, Approval, and Revision Letter of Transmittal For electronic data deliverables, notification shall be provided to those offices and/or persons listed in Block 14 of the relevant DD Form 1423s via authorized e-mail addresses provided by the Government to the Contractor. The e-mail notification letter of transmittal shall contain a reference to the contract number, CDRL sequence number, DID number, title/subtitle of the DID/data, WBS number (to the lowest possible level), document number, document revision, document date and classification, as well as summary of revisions. Notification shall include instructions for accessing the file.

Final Submittals For final submittals of a data item, the Contractor shall clearly state in the final letter of transmittal that it is the last submittal being made and that such last transmittal is in accordance with the contract.

Alternate Delivery For data files too large to transfer via the IDE to the Government, the Contractor shall, upon verbal approval by the PCO, deliver the data utilizing an alternate method.

Alternative delivery methods, including the use of paper, magnetic media, or optical disk, shall be an alternative to electronic access/submittal of contract related data when such access does not meet the Government’s needs and is requested by the PCO. Examples where electronic access/submittal of contract related data via the IDE may not meet agency needs include, but are not limited to, the following:

· Instances where the Government has identified a requirement for bulk delivery of data to recipients listed in Block 14 of the relevant DD Form 1423s not having access to the IDE.

· Instances where data is more easily viewed when printed on paper as compared to when provided on an electronic display.

In instances of alternate delivery, the letter of transmittal shall contain a reference to the contract number, CDRL sequence number, DID number, title/subtitle of the DID/data, WBS number (to the lowest possible level), document number, document date, and classification. At the end of the letter of transmittal, a complete list of distribution addresses shall also be provided.

Approval When approval of data is required as indicated in Block 8 of the relevant DD Form 1423, the PCO will notify the Contractor of such approval/disapproval as specified or scheduled in Blocks 10, 12, and 13 of the relevant CDRL Exhibit and DD Form 1423. If the Government requires revision or clarification of the data prior to approval, the Contractor shall revise and resubmit the data or provide return comments as specified or scheduled in Blocks 10, 12, and 13 of the relevant CDRL Exhibit and DD Form 1423.

Revision Each revised submittal of a data item shall be a complete revision and shall include at the front of the volume sufficient additional information (i.e., volume numbers and revision levels) for positive identification of the data item. A summary of changes since the last submittal shall be included in the front matter. If paper is used for delivery of data, revised material shall be indicated by a vertical line down the right margin. Revisions to electronically accessed data may use the vertical line method or by another mutually agreeable format between the Contractor and the Government.

Data Quality All data transmitted to the Government shall be of sufficient quality that the Government is able to read the data both online and in printed form. If the Government receives a document that has quality/readability issues, the Government will reject the data and the Contractor shall correct the deficiencies.

Data Maintenance and Support Data Maintenance Once contract related data, including technical data, computer software, and computer software documentation is submitted or approved, the Contractor shall take reasonable care to ensure the integrity and security of said data is maintained.

User Support The Contractor shall develop and provide a cost effective mix of support for a Government user population estimated at approximately 50 users at any given time. User support shall promote rapid acquisition of the skills needed to use the IDE and quick access to assistance when encountering problems during use, and will, at the discretion of the Government, consist of classroom instruction, help desk support, printed desk guides, online help, Frequently Asked Questions (FAQs), and other similar methods.

Back-up Support and Delivery of the IDE Industry standard back up capability shall be provided and all back up media shall be kept in accordance with FAR 4.7 or until satisfactorily delivered to the Government. The IDE and associated back up media shall be indexed to provide straightforward access in case of information requests. In the event of an IDE failure (including compromise due to hacker or virus attacks), lost information shall be limited to activities that have occurred within the preceding 24 hour period.

The Contractor shall verify that all data is present and uncorrupted in the backup media, archives, and within the full IDE equipment upon delivery to the Government at the end of the contract period or on the date determined to be most advantageous to the Government.