DRAFT_Strike_Group_Defender_SOW.pdf

SECTION C

STATEMENT OF WORK

C.1. GENERAL INFORMATION

C.1.1 Introduction

(a) The contractor shall provide all personnel, equipment, tools, materials, supervision, and other items and non-personal services necessary to provide modeling and simulation, integration support, software design and development, software tools and data management support, and configuration management as defined in this Statement of Work (SOW) except for Government furnished information specified in C.2 as Government furnished property and services.

C.1.2 Background:

(a) The Naval Surface Warfare Center Dahlgren Division (NSWCDD), Electro-magnetic and Sensor Systems Department (B Department), supports multiple Navy and Marine Corps systems. B Department provides systems expertise across the entire acquisition lifecycle from concept exploration through sustainment of Navy and Marine Corps systems.

(b) B Department desires to augment its sustainment mission with new R&D initiatives to ensure that lifecycle planning incorporates a path for future integration of emerging technology. A central tenant of this plan it to be able to rapidly prototype new concepts, integrate data collection and analytics, capitalize on the data using new Artificial Intelligence tradecraft in the market and lastly, have a live, distributed, virtual multi-player war-gaming and simulation environment to test new features with the fleet.

C.1.3 Objective:

(a) B Department desires to augment its sustainment mission with new Research and Development (R&D) initiatives to ensure that lifecycle planning incorporates a path for future integration of emerging technology.

(b) A central tenant of this plan it to be able to rapidly prototype new concepts, integrate data collection and analytics, capitalize on the data using new Artificial Intelligence tradecraft in the market and lastly, have a live, distributed, virtual multi-player wargaming and simulation environment to test new features with the fleet.

C.1.4 Mandatory Documents:

(a) Mandatory publications applicable to this SOW are listed below:

(1) Department of Defense 8500 series

(2) Department of Defense Manual 5220.22, National Industrial Security Program Operating Manual (NISPOM), 28 Feb 06 (as amended and revised)

(3) Future Airborne Capability Environment (FACE), Edition 2.1, May 2014 (or later editions)

C.1.5 Mandatory Requirements:

(a) The following mandatory requirements shall be maintained from the date of award through the life of this contract.

(b) The mandatory requirements are as follows:

(1) Requirement 1, Facility Security Clearance - The primary facility for supporting this contact shall have a facility security clearance of SECRET; and shall be cleared at the SECRET level for both information processing and storage.

(2) Requirement 2, Personnel Security Clearances – All individuals performing under this contract shall possess personnel security clearances at the collateral SECRET level. Interim personnel security clearances are acceptable for all labor categories.

C.1.7 Travel:

(a) During the performance of this effort, contractor employees and consultants may be required to travel to other sites to support program activities. Travel to these destinations shall be specified in each Task Order.

(b) All travel shall be conducted in accordance with Clause HQ B-2-0020, and shall be pre-approved by the COR.

All travel requests shall be submitted to the COR in writing or by electronic mail, and must show the appropriate task order number, the number of people traveling, the number of days for the trip, the reason for the travel, and any high-cost or unusual costs expected. For local travel, also known as day travel, the travel itinerary will include “reasonable cost” wherever possible based on the start time of the scheduled event being supported. The contractor is not authorized to perform any travel that is not in conjunction with this Contract; and approved by the COR prior to occurring. the contractor shall document in a Trip Report (CDRL A001) actions performed during travel along with reconciling the travel for each task order.

(c) The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements.

(d) It is anticipated that travel will be required to the following places during the performance of this contract:

• Washington, DC

• NSWCDD Dahlgren

C.2 GOVERNMENT FURNISHED PROPERTY AND INFORMATION

C.2.1 Government Furnished Facilities:

(a) No Government Furnished facilities or space will be provided under this contract.

C.2.2 Government Furnished Information (GFI):

(a) The U.S. Government will make available as GFI, upon request, references to all necessary technical publications to be utilized in the performance of this contract. The contractor shall ensure the GFI being used or referenced in the performance of this contract is the latest version in effect.

(b) The U.S. Government will make available technical manuals, technical reports and technical data, in its possession, to be utilized as GFI in the performance of this contract through the incorporation of GFI as a NAVSEA Schedule C to this contract.

C.3. REQUIREMENTS

C.3.1 General

(a) The contractor shall integrate single platform and force level modeling and simulation (M&S) capabilities into the Joint Cognitive Operations Research Environment (jCore) to enable multiple Government customers solve warfighter scenario and battle management requirements; support R&D into future technology integration into lifecycle support; and provide a live, virtual simulation environment to support various B Division initiatives.

(b) All work shall be performed in a secure environment. (c) The contractor shall maintain one customer SGDNet-S User Node located at the Naval Surface Warfare Center Dahlgren Division throughout the performance of this contract. Additional SGDNet-S User Nodes may be required during the performance of each task order. The number and locations of additional SGDNet-S User Nodes will be provided in each task order.

(d) The contractor shall prepare “Lessons Learned” from each development effort. The contractor shall incorporate all Lessons Learned into jCore’s Capability Maturity Model Integration (CMMI) infrastructure on a non-attribution basis.

C.3.2 Physical Environment

(a) The contractor shall provide the physical environment suitable to perform collateral SECRET work in support of this contract.

(b) The contractor shall comply with all National Industrial Security Program (NISP) requirements necessary to manage and administer the physical environment. NISP requirements are specified in the DD Form 254 provided as Attachment # to the contract.

C.3.2 Open Architecture

(a) The contractor shall develop and maintain an open architecture (OA) that incorporates appropriate considerations for security, re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability. The contractor shall use the U.S. Navy's Open Group Technical Standard for the Future Airborne Capability Environment (FACE), Edition 2.1, May 2014.

The contractor may use other Modular Open Systems Architectures (as needed) to converge the OA resulting from this contract within the Defense Standardization Council guidelines as specified by the Deputy Assistant Secretary of Defense for Systems Engineering (DASD(SE)), including but not limited to: the U.S. Air Force's Open Mission Systems (OMS) Project; and the U.S. Army's Integration in Ground Platforms (IGP).

C.3.3 Software Design and Development

(a) The contractor shall design, develop and integrate modeling and simulation capabilities into jCore to help this customer solve its multiple warfighter scenario and battle management requirements as required by the Government.

(b) The contractor shall integrate current and future Government and privately developed algorithms into the jCore immersive computer environment as required by the Government.

(c) The contractor shall develop realistic, cost-conscious, and operationally-relevant warfighter scenarios for further analyses as required by the Government.

(d) The contractor shall provide NSWCDD near-real time predictive modeling to aid in decision making.

(e) The contractor shall leverage real-world information and shall integrate real-time Artificial Intelligence in a low computational environment as required by the Government.

(f) The contractor shall deliver all source code (CDRL A002).

C.3.4 Software Tools and Data Management Support

(a) The contractor shall design, develop, and maintain any software support tools and models necessary to perform the requirements of this Statement of Work (CDRL A003).

(b) The contractor shall perform analysis of tools to aid in software development (e.g. memory checking tool, test automation tools, code coverage tools, etc.) as required by the Government (CDRL A003).

(c) The contractor shall perform testing of COTS hardware replacements for systems and software impacts as required by the Government (CDRL A003).

C.3.5 Configuration Management:

(a) The contractor shall use an Industry Standard code management tool (such as PerForce) to assure that change control functions are properly implemented on software for personal computer-based systems.

(b) The contractor shall perform Computer Software Configuration Item (CSCI) compiles and system installations for all software developed under this contract (CDRLS A005, A006) .

(d) The contractor deliver System Installation Documentation Procedures (CDRL 005) for all software releases developed under this contract.

(e) The contractor shall be responsible for configuration and version control of all tactical and support hardware and software developed under this contract including generating or duplicating official release media and supporting material (CDRLS A005, A006).

(f) The contractor shall generate test media for software verification test events for integration agent test events and to trouble shoot /duplicate reported fleet issues (CDRL A003).

(g) The contractor shall implement industry standard quality assurance procedures for software releases to ensure that the all files are written correctly to the distribution media and that the proper version of the software is released to appropriate activities. The contractor shall provide documentation of the quality assurance procedures followed for each software release delivered to the Government (CDRL A003).

(h) The contractor shall be responsible for the identification and implementation of all software improvements including the development of shell scripts (CDRL A003).

(h)The contractor shall provide schedule and status information for development and release efforts as required by the Government (CDRL A004).

(i) The contractor shall track and resolve any action items resulting from these Government/Contractor interchange meetings (CDRL A004).

(j) The contractor shall generate status accounting reports and special reports as required by the Government

(CDRL CDRL A004).

C.3.6 SECURITY

(a) The Contractor shall comply with guidelines specified on the DD Form 254. All Contractor personnel shall possess, at a minimum, at the time of contract award a current SECRET (S) clearance based on a National Agency Check (NACLC) completed within the last 10 years. Interim clearances are acceptable at time of award so long as a current clearance, respectively, is obtained within 180 calendar days subsequent to award unless further extended by prior written authorization by the Contracting Officer. The Contractor shall submit completed clearance packages within 10 calendar days or identification of any increased security requirements. Access to classified spaces and material and generation of classified material shall be in accordance with the DD Form 254, NISPOM and the NSWCDD Command Security Manual.

(b) The Contractor shall have access to information up to SECRET classification to complete tasking previously described in this SOW.

(c) All deliverables associated with this Contract are unclassified unless otherwise specified in the technical instruction. Access to classified spaces and material and generation of classified material shall be in accordance with the attached DD Form 254.

(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.

(f) 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 Subcontractors) 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 Subcontractors) shall sign a Contractor's conformance statement and submit it to the NSWCDD COR named in block 16 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.3.7 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 players, iPADs, digital picture frames, electronic book readers, kindle, nook, cameras, external hard dish drives, and floppy diskettes.

(b) PEDs belonging to an external organization shall not be connected to NSWCDD networks or infrastructure without prior approval from the NSWCDD Information Assurance and compliance Branch. This approval will be granted using the TARIS form and action tracker process.

(c) Personally owned hardware or software shall not be connected or introduced to any NSWCDD hardware, network or information system infrastructure.

C.3.8 INFORMATION SECURITY AND COMPUTER SYSTEM USAGE

(a) In accordance with U.S. Navy policy, and personnel, including the Contractor, who utilizes DOD-owned systems, shall assume responsibility for adherence to restrictions regarding internet and e-mail usage. Navy policy prohibits racist, sexist, threatening, pornographic, personal business, subversive or politically partisan communications. All personnel, including the Contractor, are accountable and must act accordingly. DOD computer systems are monitored to ensure that the use is authorized, to facilitate protection against unauthorized access, and to verify security procedures, survivability and operational security. During monitoring, information may be examined, recorded, copied, and used for authorized purposes. All information, including personal information, placed on or sent over a DOD system may be monitored. Use of a DOD system constitutes consent to monitoring. Unauthorized use may result in criminal prosecution. Evidence of unauthorized use collected during monitoring may be used as a basis for recommended administrative, criminal or adverse action.

C.3.9 USE OF INFORMATION SYSTEM RESOURCES

(a) Contractor Provision of Information System (IS) Resources except in special circumstances explicitly detailed elsewhere in this document, the Contractor shall provide all IS resources needed in the performance of this contract This includes, but is not limited to computers, software, networks, certificates, and network addresses.

(b) Contractor Use of NSWCDD IS Resources.

(i) In the event that the Contractor is required to have access to NSWCDD IS resources, the login name used for access shall conform to the NMCI login naming convention. If the Contractor requires access to applications/systems that utilize client certificates for authentication, the Contractor is responsible for obtaining requisite certificates from a DoD or External Certificate Authority. If this contract requires that the Contractor be granted access and use of NSWCDD IS resources (at any site), the IS shall be accredited for Contractor use in accordance with procedures specified by the Information Assurance Office.

(c) Connections between NSWCDD and Contractor Facilities.

(i) If there is a requirement (specifically delineated elsewhere in this contract) for interconnection (e.g., link level or Virtual Private Network (VPN)) between any facilities and/or ISs owned or operated by the Contractor and ISs owned or operated by NSWCDD, such interconnection shall take place only after approval from the NSWCDD Information Assurance Office. All such connections as well as the ISs connected thereto will be accredited in accordance with DoD policy (DoDI 5200.40) by the cognizant Designated Approving authority (DAA) and comply with the requirements of CJCSI 6211.02B regarding Memorandums of Agreement. All such connections will be made outside the appropriate NSWCDD firewall.

C.3.10 SENSITIVE PROPRIETARY, AND PERSONAL INFORMATION

Work under this contract may require that personnel have access to Privacy Information. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code Section 552a and applicable agency rules and regulations.

Access to and preparation of sensitive information subject to Privacy Act and Business Sensitive safeguarding and destruction may be required in the execution of tasking associated with this contract. Administratively sensitive information/data must not be shared outside of the specific work areas. All personnel with access to privacy act data in support of this contract must sign a privacy act certification.