SOW_Redacted.pdf

(1) Much like the TACSIM training efforts, the TACSIM I&T efforts require that the Contractor provide continuous development, extension, and updates to ensure that solutions remain tactically interoperable with the subsystems, capabilities, and tools deployed in the Fleet.

(2) During performance of this effort, the Contractor shall provide continuous development and upgrades of the AN/SLQ-32(V)X l&T assets and the extension of the AN/SLQ-32(V)X l&T asset tools and capabilities to meet additional simulation and l&T needs of the Fleet and related l&T communities of interest.

(d) During performance of this effort, the Contractor shall develop combined hardware/software simulator(s), engineering artifacts, and documentation (Programmatic, Systems Engineering, and Software Engineering) applicable to each.

(1) Additionally, the Contractor shall leverage these services and products to extend to the additional tactical simulation needs and objectives of the Navy.

C.1.4 Applicable Documentation

(a) The following documents with the exact date and issue specified form a part of this Statement of Work to the extent specified herein. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

Military/Federal Standards and Specification (Guidance Only)

Standard Title Date

DI-IPSC-81488 Computer Software Product July 31, 1995 DI-ADMN-81505 Report, Record of Meeting/Minutes November 20, 1995 DI-MISC-81943 Trip/Travel Report August 27, 2013 DI-MGMT-81605 Briefmg Material February 15, 2001

DI-IPSC-81756 Software Documentation May 28, 2008 DI-IPSC-81443A Software User Manual (SUM) January 11, 2000 DI-MGMT-80368A Status report October 30, 2006

Handbooks (Guidance Only)

Handbook Title MIL-HDBK-61A (SE) Configuration Management Guidance

C.2 Item Descriptions

Date February 7, 2001

(a) The following item descriptions address the tasking and activities required to fulfill the requirements of this SOW. The line items apply to TACSIM development related to training, testing, and the extension of these tools and capabilities into additional TACSIM communities of interest. The Contractor shall execute the below line items, as required by the Government, for each TACSIM asset developed, delivered, and installed.

Item 0001 - Requirements Elicitation & Development

(a) The Contractor shall prototype, test, and deliver TACSIM tools and capabilities meeting the physical, functional, resource, and performance requirements for the specific TAC SIM unit as required by the Government.

(b) Requirements Engineering

(1) The Contractor shall conduct requirements working groups and Technical Interchange Meetings (TIMS) and deliver documentation of the meeting minutes (CORL A00l).

(2) The Contractor shall conduct engineering analyses to establish TACSIM requirements and the technical engineering approach involved in each TACSIM installation.

(3) The Contractor shall develop and deliver system/subsystem specification documentation as required by the Government (CDRL A002).

(4) The Contractor shall develop system and software requirements documentation utilizing appropriate tools and technology to capture, manage, track, map, and store all requirements.

(5) The Contractor shall develop and deliver a Software Requirements Specification documentation as required by the Government (CORL A002).

(6) The Contractor shall, as necessary, identify, document, and deliver Cybersecurity Requirements specific to the TACSIM installation (CDRL A002).

(7) The Contractor shall align all requirements elicitation efforts, system development, and prelim/final installation and testing with TACSIM installation site availability and schedule.

(8) The Contractor shall provide inputs to a Training System Installation Plan (TSIP), as necessary, for all applicable TACSIM installations (CORL A002).

(9) The Contractor shall conduct site visits to approved TACSIM installation sites to support requirements elicitation, installation, and testing and provide trip reports and after-action-reports detailing the results of the site visit (CORL A003).

(10) The Contactor shall review requirements and requirements-related documentation with TACSIM installation site stakeholders.

( c) Hardware Acquisition

(1) The Contractor shall procure commercial and non-commercial hardware for TACSIM unit prototypes and T ACSIM site installations.

Item 0002 - System Architecture and Software Design

(a) The Contractor shall prototype, test, and deliver TACSIM tools and capabilities that are designed to align to the requirements as required by the Government.

(b) Design Documentation

(1) The Contractor shall conduct software design activities to address specific TACSIM installation requirements and capture detailed design information (CORL A008).

(2) The Contractor shall develop and deliver System/Subsystem Design Description documentation for TACSIM installations (CORL A002).

The Contractor shall conduct all technical activities required to redesign current systems, as necessary, to ensure interoperability with new TACSIM tools and capabilities and to align with tactically-representative system/subsystem behavior and delivery System/Software Requirements Verification Matrix (SRVM) documentation (CORL A002).

( c) Build Environment

(1) The Contractor shall establish/update the software build environment specific to the TACSIM asset to be developed and delivered.

(2) The Contractor shall build the TACSIM software to run on the identified and applicable hardware configurations.

(4) The Contractor shall develop and deliver System User Manuals and/or Facilitator's Guides for each TACSIM installation (CORL A006) as required by the Government.

(c) Verification Testing

(1) The Contractor shall conduct and document all pre-installation and final testing to verify all requirements applicable to the TACSIM installation (CORL A002).

(2) The Contractor shall develop and deliver site-specific test plans and procedure documentation for each T ACSIM installation verification event (CORL A002).

(3) The Contractor shall develop and deliver a final test report for each TACSIM installation verification event

(CORL A002).

( d) System Training

(1) The Contractor shall develop and deliver training material documentation for TACSIM training, testing, installation, and check-out, as required by the Government, for the TACSIM system (CORL A002).

Item 0006 - System Maintenance and Troubleshooting

(a) The Contractor shall be responsible for system maintenance and troubleshooting as required by the Government, for the TACSIM system.

C.3 Program Management

(a) Program Management and Reporting

(1) The Contractor shall establish and maintain program management practices throughout the entirety of the contract. The Contractor's program management practices shall include organizational techniques and practices used to manage the program, Sub-contractors, and data.

(2) The Contractor shall develop and deliver a detailed project plan for each TACSIM system developed (CORL A002).

(3) The Contractor shall develop and deliver a monthly status report for each DO (CORL A007).

(b) Data Management

(1) The Contractor shall establish and maintain a central system for managing all data associated with this effort.

(2) The Contractor data management practices shall include control of schedule for deliverables, maintenance and approval of deliverables, and the process of deliverable data products/deliverables throughout the course of the PoP.

(3) The Contractor shall also ensure that the data is maintained in a manner conducive to Government review. The Government reserves the right to review all data associated with, and developed as a part of, this project.

(c) Schedule Planning

(1) The Contractor shall develop and deliver a detailed Integrated Master Schedule (IMS) for each TACSIM system developed (CDRL A002).

(d) In-Plant Visits obtain a SIPRnet account and to utilize the DTIC system to obtain documents on intelligence. All above accesses are needed to support and provide the training systems necessary to support the SEWIP BLK 2 program

d) For Official Use Only (FOUO) and Personally Identifiable Information (PII) generated and/or provided under this contract shall be safeguarded and marked as specified in DoD 5400.7-R Chapters 3 and 4.

( e) The Contractor shall possess and maintain a SECRET facility clearance as verified within the Industrial Security Facility Database.

(t) The Contractor shall be responsible for safeguarding all Government information or property provided for Contractor use. At the end of each work period, Government information, facilities, equipment and materials shall be secured as specified by the NISPOM and the NSWCDD Command Security Manual. SECRET storage is required at the Contractor's facility in order to meet requirements of receiving and generating classified material in accordance with this contract.

(g) Electronic Spillages (ES) are unacceptable and pose a risk to national security. An electronic spillage is defined as classified data placed on an information system (IS), media or hardcopy document possessing insufficient security controls to protect the data at the required classification level, thus posing a risk to national security (e.g., sensitive compartmented information (SCI) onto collateral, Secret onto Unclassified, etc). The Contractor's performance as it relates to ES will be evaluated by the Government. ES reflects on the overall security posture of NSWCDD and a lack of attention to detail with regard to the handling of classified information of IS security discipline and will be reflected in the Contractor's performance rating. In the event that a Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation will be charged to the Contractor.

(h) NSWCDD Security will continue to be responsible for the corrective action plan in accordance with the security guidance reflected on the DOD Contract Security Classification Specification - DD Form 254. NSWCDD Security will identify the Contractor facility and contract number associated with all electronic spillages during the investigation that involve Contractor support. NSWCDD Security will notify the Contracts Division with the Contractor facility name and contract number, incident specifics and associated costs for clean-up. The Contracting Officer will be responsible to work with the Contractor Facility to capture the costs incurred during the spillage clean up. The Contractor is also responsible for taking Information Security Awareness training within 30 days of award and annually thereafter, via their Facility Security Officer (FSO), as part of the mandatory training requirements. If a spillage occurs additional training will be required to prevent recurrence.

(i) Operations Security (OPSEC):

All Contractors (including Sub-contractors) shall supplement their current security practices by requiring any personnel involved in executing this contract to complete Government-sponsored and administered Operations Security (OPSEC) training. In addition, all Contractors should be aware of the Critical Information List (CIL) for the organization they are supporting as well as the OPSEC plan for NSWCDD. Upon contract award, all identified Contractors (including Sub-contractors) shall sign a Contractor's conformance statement and submit it to the NSWCDD COR named in block 13 of the attached DD-254 thereby acknowledging that they will meet the requirements of this contract. The COR shall contact their Department Training Coordinator to schedule key employees to attend the Government-sponsored OPSEC training. The Contractor must immediately notify the Government upon the discovery of any nonconformance with the OPSEC Plans.

C.8.1 Portable Electronic Devices (PEDS)

(a) Non-Government and/or personally owned portable electronic devices (PEDs) are prohibited in all NSWCDD buildings with the exception of personally owned cell phones which are authorized for use in spaces up to, and including, Controlled Access Areas. The Contractor shall ensure the onsite personnel remain compliant with this PED policy. NSWCDD instruction defines PEDs as the following: any electronic device designed to be easily transported, with the capability to store, record, receive or transmit text, images, video, or audio data in any format via any transmission medium. PEDs include, but are not limited to, pagers, laptops, radios, compact discs and cassette players/recorders. In addition, this includes removable storage media such as flash memory, memory sticks, multimedia cards and secure digital cards, micro-drive modules, ZIP drives, ZIP disks, recordable CDs, DVDs, MP3