CPES - SOW.pdf

CUI

CUI

STATEMENT OF WORK

SECTION C – DESCRIPTION/SPECIFICATION/WORK STATEMENT

C.1 BACKGROUND

This acquisition will provide the Naval Surface Warfare Center, Dahlgren Division (NSWCDD) with Computer Program Engineering Services (CPES) needed to support naval weapons and combat system development, test, evaluation, certification, In-Service support (including software maintenance and sustainment), training, and development of simulation systems. This effort includes support for Weapon System Element and Combat System Domain Engineering;

Fleet and Land Based Test Site Support; System Safety Engineering (SSE) analysis and risk characterization; Combat Systems Readiness; and Configuration Management Verification and

Validation (CMVV).

The supported systems include, but are not limited to: Aegis, Aegis Ballistic Missile Defense

(BMD), Guided Missile Frigate (FFG)[R(2.1], Integrated Combat System (ICS), Littoral Combat

System (LCS), Next Generation Guided Missile Destroyer (DDG(X)), Ship Self Defense System

(SSDS), Unmanned Surface Vessel (USV), the United States Coast Guard (USCG), Zumwalt, United States Marine Corps (USMC), Foreign Military Sales (FMS), and North Atlantic Treaty

Organization (NATO) program support. Additionally, this effort provides simulation, virtualization, and communication support for emerging technologies and future defense concepts.

C.2 SCOPE

The Contractor will provide CPES development and lifecycle support for new construction ships and in-service surface combatants to successfully transition new capabilities to the Fleet. To accomplish this, the Contractor will execute the following tasks:

• Software Engineering & Maintenance: Design, develop, and modify computer program code, including defect corrections and capability enhancements.

• Systems Analysis & Architecture: Conduct engineering studies, data and tradeoff analyses, System Safety Engineering (SSE) risk characterizations, and define future high-performance architectures.

• Simulation, Test, & Training Systems: Perform requirements analysis, design, prototyping, assembly, integration, Verification and Validation (V&V) testing, functional accreditation, documentation, and final delivery for combat system interface simulations, test systems, analysis systems, and simulation-supported training systems.

• Process Improvement: Assist in the development and implementation of computer program development processes.

Combat System Functional Areas include:

CUI

1. Navy Combat Systems, such as: Aegis, Aegis BMD, FFG, ICS, LCS, DDG(X), SSDS, USV, USCG, and Zumwalt, including the system's associated sensors, command and control systems, weapons, navigation, and communications interfaces

2. Joint Combat System Programs and associated sensor, command and control, weapon, navigation and communication interfaces

3. Link 11, Link 16, STJ (Satellite Tactical Data Information Link J), Joint Range Extension

(JRE), Link 22 and variants thereof

4. Network centric and non-real-time information exchange systems.

5. Cooperative Engagement Capability (CEC)

6. Distributed Interactive Simulations (DIS), High Level Architecture (HLA), Test and

Training Enabling Architecture (TENA), Global Reusable Interface Domain (GRID), Standard

Interface for Multiple Platform Link Evaluation (SIMPLE) distribution standards

7. Subsystems to include Radar, Navigation, and Audio signal generation

8. Combined Integrated Air and Missile Defense (IAMD) and Anti-Submarine Warfare

(ASW) Trainer (CIAT)

9. Multi Warfare Planning and Training System (MWPTS)

10. Combat System and Simulation System virtualization

11. Foreign Military Sales (FMS) and North Atlantic Treaty Organization (NATO) program support

12. Joint Simulation Environment (JSE) blue surface force representation

13. Marine Air Defense Integrated System (MADIS) program support

14. Simulation supported training systems and analysis systems include systems developed under this Task Order and the following:

a. Combat System Simulator/Stimulator (CS3)

b. Next Generation Simulation (NGS)

c. Common Connectivity Device (CCD)

d. Universal Message Generator (UMG)

e. Tactical Data Link Integration Exerciser (TIGER)

f. Clock Distribution System (CDS)

g. Combat System Behavior Model (CSBM)

h. BMD Computer Program (BCP) Rehost

i. BMD Signal Processor (BSP) Rehost

C.2.1 Applicable Documents

The following documents are applicable to this SOW. The most current versions of these documents are accessible through the internet or will be provided to the Contractor upon request.

Other Department of Defense Specifications/Standards/Other Applicable Documents may become applicable throughout the life of the Task Order and may be added to the Task Order via modification.

The Contractor shall ensure compliance with the most current versions of these documents throughout the life of the Task Order:

Number Document Name

DODM 8140.03 Cyberspace Workforce Qualification and Management Program

SAE AS5553 (series) SAE Aerospace Standard 5553

NISPOM – 32 Code of

Federal Regulation Part

National Industrial Security Program Operating Manual (NISPOM)

NSWCDDINST 5510.4

(series)

NSWCDD Command Security Manual

SEAD-3 Security Executive Agent Directive 3 – Reporting Requirements for

Personnel with Access to Classified Information or Who Hold a

Sensitive Position

SEAD-3

Implementation Memo

Implementation of Security Executive Agent Directive 3, Reporting

Requirements for Personnel with Access to Classified Information or Who Hold a Sensitive Position

SEAD-4

Implementation Memo

Implementation of Security Executive Agent Directive 4: National

Security Adjudicative Guidelines

DODI 5200.48 Controlled Unclassified Information (CUI)

DoDM 5400.07 DoD Freedom of Information Act (FOIA) Program

SECNAVINST 5210.8

(series)

Department of Navy Records Management Program

NSWCDDINST 5100.1

(series)

Occupational Safety and Health Program

NAVADMIN 216/15 Cyber Hygiene Authorization to use Personal Wearable Fitness

Devices

NAVSEA S0420-AA-

RAD-010 (series)

Radiological Affairs Support Program (RASP) Manual

CUI

Number Document Name

DODI 8510.01 Risk Management Framework for DOD Systems

CJCSI 6211.02 (series) Defense Information Systems Network (DISN) Responsibilities

DODM 1000.13 Department of Defense Identification (ID) Cards

NAVSEAINST 4200.19

(series)

Planning, Use and Control of Services Contracting

COMUSFLTFORCOM/

COMPACFLT 6320.3

(series)

Medical Screening for U.S. Government Civilian Employees, Contractor Employees, Guests and Visitors Prior to Embarking

Fleet Units

C.3 REQUIREMENTS

C.3.1 General Engineering and System Analysis

C.3.1.1 System Analysis and Evaluation: The Contractor shall study and analyze existing or proposed systems and their documentation to develop use cases. These use cases will determine which parts of the system require simulation and the necessary degree of fidelity and performance. The analysis will cover relevant hardware, software, networking, interfaces, and associated documentation.

C.3.1.2 Documentation and Planning: The Contractor shall develop presentations, documentation, and a notional schedule to outline the proposed computer program or simulation system configuration. The Contractor must identify any items that need to be purchased or developed and prepare a Rough Order of Magnitude (ROM) for cost. The Contractor shall provide status updates of software development activities and record meeting minutes.

C.3.1.3 Technical Evaluations: The Contractor shall provide technical evaluations, options, and recommendations to support program and product planning and sustainment for weapon system elements, combat system domains, and subsystems to improve Navy engineering and computer program products.

C.3.2 System and Software Development and Lifecycle Support

C.4.2.1 Requirements Analysis: The Contractor shall perform system and functional level requirements analysis, create requirements, and enter them into the Government Furnished

Equipment (GFE) Requirement Management tool (e.g., DOORS).

1. The Contractor shall generate, deliver, and update requirements documents, participate in reviews, and notify the Government of any discrepancies.

2. The Contractor shall provide technical reports and position papers to substantiate functional computer program requirement change recommendations.

3..The Contractor shall analyze specifications and recommend cybersecurity requirements and controls;

CUI

C.3.2.2 System Engineering and Design: The Contractor shall perform system engineering for combat systems, test systems, and training systems. This includes gathering Interface Design

Specifications (IDS) and other documentation to develop a high-level system architecture, including Computing Infrastructure (CI) equipment architectures.

1. The Contractor shall develop preliminary and detailed design documentation for the system, subsystems, networks, and interfaces, ensuring the design meets all required use cases.

2. The Contractor shall document and track configuration of computer program design, development, test, and production materials and artifacts.

3. The Contractor shall track the configuration and versioning of computer program problem reports and assist in maintaining the Government-owned trouble report database by providing updates and status information for the weapon system elements and combat and training system domains.

4. The Contractor shall develop and test CI equipment architectures and equipment refresh options for current and future Navy ship platforms.

C.3.2.3 Technology and Market Investigations: The Contractor shall investigate various technologies, including Commercial Off-The-Shelf (COTS) products, to meet system requirements. This includes analyzing the life expectancy of hardware and software and submitting investigation results, trade studies, and recommended solutions.

1. The Contractor shall investigate and conduct engineering studies and experiments pertaining to the migration of legacy computer program into various COTS equipment and

COTS/Government-Off-The-Shelf (GOTS) applications.

2. The Contractor shall provide recommendations and evaluation of legacy component replacement with reliable, COTS-based solutions. The Contractor shall define notional computing architectures for the COTS based solutions.

C.3.2.4 Design Reviews: The Contractor shall conduct Preliminary Design Reviews (PDR) and

Critical Design Reviews (CDR) with the Government, demonstrating how the design maps to requirements and meets all use cases.

1. The PDR documentation shall address how the requirements will map to the various components and be met by the design. The Contractor shall address how the design will meet the required use cases. The Contractor shall present design alternatives investigated and the rationale for the various design decisions.

2. The CDR shall communicate the system design, its major components, and internal and external interfaces. The review shall address how the requirements will map to the various components and be met by the design. The Contractor shall address how the design will meet the required use cases.

CUI

C.3.2.5 Software Development: The Contractor shall provide computer program engineering expertise in support system safety analysis, risk characterization, infrastructure, display, sensor, track management, combat control, weapon management, vehicle control, external communication management, position, navigation, time services, and training related to software development of naval weapons systems elements, combat system domain and sub-systems, and simulation systems.

1. The Contractor shall develop code and implement code changes for assigned corrections or modifications, Engineering Change Proposals (ECPs), Specification Changes (SCs), and

Interface Change Requests (ICRs).

2. The Contractor shall generate Simulation System software code in compliance with the

Software Development Plan (SDP) and Government-provided coding standards.

a. The software developed will consist of both executable and non-executable code.

b. The Contractor shall ensure simulation system computer program design and implementation is compliant with Risk Management Framework (RMF) for DoD Information

Technology Standards specified in DODI 8510.01

c. The Contractor shall develop simulation scenarios to test functionality and ensure repeatability for Government identified use cases.

3. The Contractor shall develop and update computer program artifacts required to reproduce, build, install and execute the computer program.

4. The Contractor shall document and resolve computer program requirement deficiencies and provide change recommendations.

5. The Contractor shall identify the selected operating systems, middleware products, Original Equipment Manufacturer (OEM) software and will identify what software will be developed and what software languages and scripting tools will be used. The Contractor shall identify and provide for Government approval of the software tools and build environments that will be used.

6. The Contractor shall generate and update cybersecurity documentation; and perform information assurance vulnerability management.

C.3.2.6 Virtualization: The Contractor shall design, develop, test, and modernize virtualization environments and Computing Infrastructure (CI) equipment architectures for tactical applications, including hypervisor underway testing and container implementations.

1. The Contractor shall provide expertise in the provisioning and deployment of combat system variants within the virtualization environment as requested by the Government.

CUI

2. The Contractor shall provide expertise in the integration of additional interfaces and capabilities within the virtualized combat systems

3. The Contractor shall identify and correct any weaknesses and vulnerabilities of the virtualized environments and CI.

C.3.2.7 Prototyping and Installation: The Contractor shall support the prototyping, assembly, test, packaging, delivery, installation, and documentation of combat system interface simulation systems, utilizing Government Furnished Materials (GFM) where applicable.

1. The Contractor shall provide technical expertise for baseline deployment and ship underway engineering activities.

2. The Contractor shall evaluate, diagnose, resolve and make recommendations to resolve equipment issues including prototype integration and document functionally equivalent equipment.

3. The Contractor shall provide weapon system element and combat system domain expertise to support computer program delivery and installation efforts of Contractor developed computer programs.

4. The Contractor shall provide technical specifications to enable the Government to procure materials for prototype systems.

5. The Contractor shall provide design information to the Government to support the preparation of Information Assurance Package Approval for Simulation Systems.

6. The Contractor shall perform detailed Simulation System design and deliver detailed design documentation.

7. The Contractor shall complete and provide the final hardware detailed design documentation to communicate the design details of the system, subsystem, networks, interfaces, and operator control interfaces.

C.3.3 Testing and Verification

C.3.3.1 Developmental and Integration Testing:

1. The Contractor shall create, maintain, and review test plans for software development and integration.

2. The Contractor shall conduct software developmental testing to demonstrate the correctness and completeness of the software design.

3. The Contractor shall develop integration test plans, conduct integration testing of new capabilities, and submit test results.

CUI

4. The Contractor shall conduct unit, element, domain, integration, regression, and Fleet

Synthetic Testing (FST) level testing of computer programs.

5. The Contractor shall conduct code inspection and peer reviews throughout development.

6. The Contractor shall produce computer program executable files and perform unit tests for the purpose of verifying changes to computer programs.

7. The Contractor shall investigate and support developmental testing of automated methods of deploying virtualized infrastructure, combat systems, and simulation artifacts.

8. The Contractor shall investigate and recommend enhancements and upgrades in support of test facility improvements to increase the effectiveness of the weapons system and combat system domain and sub-system level computer program testing.

a. The contractor shall provide architectures for test facilities that is electronically compatible with the shipboard military (MIL) qualified equipment. The Contractor shall create functional equivalents for tactical equipment.

C.3.3.2 Verification, Validation, and Operational Testing:

1. The Contractor shall assist the Government with the build, test and validation of computer programs.

2. The Contractor shall develop test plans and procedures and perform dry run testing in support of functional performance assessment, verification, validation, and operational testing of weapon system elements, combat system domain and subsystems and simulation systems. The

Contractor will manage test data, perform data analysis, and deliver V&V test plans, procedures, artifacts, and reports to support accreditation activities.

3. The Contractor shall perform verification, validation, and operational testing of simulation systems with a team independent of the system designers and developers.

4. The Contractor shall isolate computer program execution deficiencies, provide root cause analysis and recommend potential resolutions such as recommended corrections, prototyping, or recommending specification changes or alternatives.

5. The Contractor shall verify that computer programs execute per requirements via detailed data analysis.

6. The Contractor shall capture and provide recorded tactical system extraction data.

7. The Contractor shall verify the accuracy of data generated by Weapon System alignment adaptation data programs following program updates.

8. The Contractor shall collect and manage simulation systems test data for analysis.

CUI

9. The Contractor shall provide on-site expertise in support of data reduction computer programs, utilities, Data Analyzer and Translator (DAT) template, and other data reduction tool development.

10. The Contractor shall provide on-site weapon system element and combat system domain expertise to include data analysis in support of Deployment Group Systems Integration Testing

(DGSIT) events, Combat System Ship qualification Tests (CSSQTs), and other test and training events.

11. The Contractor shall provide computer program design, development, configuration management, documentation, training, and Cloud computing transition for computer program analysis tools and requirement verification and validation test tools.

12. The Contractor shall conduct analysis on weapon system element and combat system domain specific memory and timing studies (i.e., conduct memory availability and optimization studies and timing performance studies).

13. The Contractor shall provide mission, system, and computer program requirements and operational impact analysis, and define mission test objectives.

14. The Contractor shall participate in, and present technical data, evaluations, and recommendations to selected working groups and Integrated Product Teams (IPTs).

15. The Contractor shall analyze software for cybersecurity risk assessment; and assess and recommend cybersecurity improvements to the development pipeline.

16. The Contractor shall support and recommend/perform correction and enhancements to shipboard capability improvements based on Fleet events and data reconstruction.

C.3.3.3 Fleet and Test Site Support: The Contractor shall provide on-site and remote-site domain expertise, configuration, integration, and testing support at various locations, including the

Integrated Warfare Systems Laboratory (IWSL) at NSWCDD, other land-based test sites, and onboard Navy ships.

1. The Contractor shall provide pre-event analysis (mission, system, and computer program requirements and operational impact analysis, define mission test objectives, and dry run testing), conduct mission and data collection as determined in the pre-event analysis, provide onsite Waterfront Integration and Testing (WIT), and post event analysis and reporting.

2. The Contractor shall provide weapon system element and combat system domain expertise in assisting Fleet Support, waterfront ship new construction and land-based test site activities.

3. The Contractor shall identify, investigate, analyze, document and resolve reported shipboard and land based test site computer program and equipment deficiencies and defects.

CUI

4. The Contractor shall identify, investigate, analyze and document fleet operational impacts of weapon systems and combat systems computer program deficiencies and defects.

5. The Contractor shall conduct Pulse Current Injection (PCI) testing during the new construction phase of the shipbuilding process and provide support as requested for other PCI events as requested by the customer.

6. The Contractor shall provide on-site engineering expertise and recommendations for the

Combat System Alignment Verification (CSAV) alignment process as part of the new-construction programs. Detailed tasks include the following:

a. The Contractor shall witness the execution of the shipbuilder-conducted test procedures which obtain the raw combat system survey values and provide verification of the raw combat system survey values.

b. The Contractor shall conduct an engineering review of the shipbuilder-provided

Mechanical Battery Alignment Report (MBAR) and deliver findings both prior to and post-delivery of the MBAR.

c. The Contractor shall verify the combat system adaptation data prior to installation on the combat system and by analysis of the date resulting from the execution of all the Combat

System Alignment Verification test procedure events.

7. The Contractor shall conduct Electro-Magnetic Interference (EMI) testing during the new construction phase of the shipbuilding process and provide support as requested for other EMI events as requested by the customer.

8. The Contractor shall be responsible for scheduling and coordinating the Radiation Hazard

(RadHaz) survey on new-construction ships and installing appropriate RadHaz placards as required onboard the ship structure.

C.3.3.4 System Safety Engineering & Cybersecurity Testing:

1. The Contractor shall support System Safety Engineering testing for verification and analysis of requirements.

2. The Contractor shall identify, evaluate, develop, integrate, and test combat system cybersecurity capabilities.

3. The Contractor shall provide support or conduct software assurance assessments using a variety of tool types, including Static Code Analysis, Dynamic Code Analysis, and Origin

Analysis.

4. The Contractor shall analyze software assurance tool findings for true positives, false positives, Common Weakness Enumeration (CWEs), Common Vulnerabilities and Exposures

(CVEs), and other weaknesses and vulnerabilities.

CUI

5. The Contractor shall assist the government with Certifications and Authority to Operate

(ATO) processes.

C.3.4 Maintenance and Program Management Support

C.3.4.1 Computer Program Maintenance: The Contractor shall perform computer program maintenance, analyze defects (Test Observation Reports - TORs), and implement authorized corrections (Software Change Requests - SCRs). The Contractor shall also provide troubleshooting support for critical situations at Government Land Based Training and Test

Sites.

1. The Contractor shall generate and deliver tactical databases and scripts (e.g. airways, threat data, geospatial information, and master ship list).

2. The Contractor shall provide, maintain, and verify computer program scripts and procedures to enable processed tactical database to be uploaded to Navy combat systems onboard ships, land-based test sites, and training facilities.

3. The Contractor shall upload the processed databases to a Navy specified data repository.

4. The Contractor shall perform product replacement evaluation for existing hardware and software components.

5. The Contractor shall generate and maintain computer program data dictionaries.

6. The Contractor shall review and update Computer Room and Data Recording User’s

Manual.

7. The Contractor shall evaluate and recommend improvements in procedures and tools for data dictionaries and data recording capabilities.

C.3.4.4 Strategic Planning: The Contractor shall support Government strategic planning by monitoring and reporting on advancements in simulation technology, industry trends, and best practices.

1. The Contractor shall develop combat system domains and weapon system element technology roadmaps to support future baseline and technology insertion decisions.

2. The Contractor shall recommend improvements in engineering and development processes to the weapon system elements and combat system domains.

3. The Contractor shall summarized technology roadmaps and continuously improve the computing infrastructure processes.

4. The Contractor shall conduct engineering studies to refresh technologies and insert new technologies compatible with weapon system computing, storage and network needs.

CUI

5. The Contractor shall provide computing infrastructure architecture concepts and options for next generation capabilities. The Contractor shall refine options selected by the Government.

6. The Contractor shall support integration and utilization of large language learning models

(ie. GenAI) and conduct verification of the output of the model.

C.4 TASK ORDER MANAGEMENT

The Contractor shall provide sufficient supervision to ensure all personnel work instructions and schedules originate with the Contractor rather than with the Government technical office. This supervision shall ensure that the Contractor’s personnel are not assigned work instructions and schedules outside this SOW. Any perceived conflicts with the SOW shall be directed to the

Contracting Officer and Contracting Officer’s Representative (COR).

C.4.1 Progress Report

The Contractor shall submit a Contracting Officer’s Management Report. (CDRL A00X) The

Contractor shall maintain and provide a list of all personnel assigned to the Task Order. The

Contractor shall provide copies of invoices received from Sub-contractors and consultants as well as evidence of its review to ensure that all invoiced costs represent services that have been performed and deliverable items. In accordance with G-232-H005, Supplemental Instructions

Regarding Invoicing, and FAR 52.216-7(DEVIATION 2026-O0045), Allowable Cost and

Payment, the Contractor shall provide the COR supporting documentation, including receipts, for all travel and material purchases with each invoice submission.

C.4.2 In Progress Reviews (IPRs)

The Contractor shall participate in both formal and informal In Progress Reviews (IPRs) of work being performed. IPRs may be conducted at the overall Task Order level or for specific projects/work areas. Reviews will be scheduled by the Government. An initial formal IPR is planned within 90 days of the Task Order award date and will follow the agenda agreed to by the

COR. Subsequent formal IPRs shall be held approximately every six (6) months thereafter unless waived by the Government. The IPRs shall be conducted at a location mutually agreed upon by the Contractor and the Government. At the time the review is scheduled, the

Government will communicate the specific purpose of the review and advise the Contractor as to the desired content of the presentation. (CDRL A00X)

C.4.3 Task Prioritization Meetings

The Contractor shall participate in periodic Task Prioritization Meetings with the COR and

Subject Matter Experts (SMEs). The purpose of these meetings is to convey the Government’s technical program schedules and priorities and to identify corresponding task priorities for this

Task Order. The Contractor shall document meeting minutes of the meetings. (CDRL A00X)

C.4.4 Cyber Incident Reporting

CUI

If a cyber incident (as defined in FAR 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting) occurs, the Contractor shall rapidly report the cyber incident in accordance with the instructions outlined in FAR 252.204-7012(c). The Contractor shall also immediately notify both the COR and Contracting Officer.

C.4.5 Telework

In accordance with H-216-H002 Level of Effort -- Alternate I (NAVSEA) teleworking at an alternative worksite is permitted. Telework is also dependent upon the type of work being performed.

C.5 SKILLS AND TRAINING

C.5.1 The Contractor shall provide capable personnel with qualifications, experience levels, security clearances, and necessary licenses, certifications, and training required by Federal, State, and Local laws and regulations. Information assurance functions require certifications specified in DOD Manual (DoDM) 8140.03 Cyberspace Workforce Qualification and Management

Program.

C.5.2 Per the requirements set forth in DODM 8140.03 as a condition of meeting requirements, personnel performing Information Assurance (IA) functions outlined in the manual will be tracked for compliance, designated in writing from the Local Command Authority as Cyberspace

Workforce (CWF), shall already be in possession of an approved commercial certification for their environment at time of performance start, and shall satisfy both preparatory and sustaining

DOD IA training and certification requirements as outlined in DODM 8140.03. Additionally, personnel with Privileged Access must sign acknowledging duties on a "Privileged Access

Agreement", be able to maintain the appropriate investigation type, sign a System Authorization

Access Request-Navy (SAAR-N) with “privileged” indicated, complete applicable Operating

System/Computer Environment (OS/CE) training to Navy’s standards, and maintain a valid commercial certification that meets outlined designations. Failure to maintain all requirements at the appropriate level may result in the removal of elevated access and removal from tasks being performed. Non-privileged Information Assurance Workforce (IAWF) members may be removed from tasks being performed. In both situations, access will be returned once the failure(s) are corrected.

The following is deemed as part of the Cyber Security Workforce (CSWF):

Labor Category # of Persons IAT Level IT Level

Principal Systems Engineer All IAT-II IT-2

Senior Systems Engineer All IAT-II IT-2

Senior Systems Engineer - Combat

Systems

All IAT-II IT-2

Systems Engineer All IAT-I IT-2

Junior Systems Engineer All IAT-I IT-2

Principal Software Engineer All IAT-II IT-2

C.5.3 Training necessary to ensure that personnel performing under this Task Order maintain the knowledge and skills to successfully perform the required functions is the responsibility of the

Contractor. Training necessary to maintain professional certification is the responsibility of the

Contractor. The Contractor shall provide training opportunities to maintain Contractor capabilities and/skills to coincide with changing technology environments. All costs for DODM

8140.03 certification shall be borne by the Contractor for new employees on this Task Order.

C.5.4 Training on non-commercial and department-specific tools and procedures will be provided by the Government.

C.5.5 Notwithstanding the above, it is understood that the Government may require services requiring knowledge and skills of a newly emergent technology. The Contracting Officer may, on a case-by-case basis, authorize the expenditure of Government funds for the training of

Contractor personnel. Advance approval is required. The Contractor is encouraged to suggest a cost-sharing arrangement that addresses registration, tuition, travel, and labor costs.

C.5.6 The Contractor shall complete all mandatory training as prescribed by the Government.

These training requirements are accessed through Government web-based training (WBT), classroom training, or combination of both.

C.5.7 Mandatory Training Completion Log - The Contractor shall submit a CWF report (CDRL

A00X). The CWF report shall address required CWF training including annual continuous learning training requirements. The Contractor shall also submit Mandatory Training

Completion Log (CDRL AXXX). The Mandatory Training Completion Log shall address all mandatory training completed as directed by the COR.

C.6 OTHER DIRECT COSTS

During the performance of this Task Order the Contractor will have to travel and procure material and consumables to perform the tasking of the SOW.

C.6.1 Travel

The Contractor shall be required to travel in performance of this Task Order. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements and shall be requested of and authorized in advance by the COR by email.

All requests shall show the appropriate Task Order number, the number of people traveling, the number of days for the trip, the reason for the travel, an estimated cost (with G&A separate), and any high cost or unusual costs expected. The Contractor is not authorized to perform any travel

Senior Software Engineer All IAT-II IT-2

Software Engineer All IAT-I IT-2

Junior Software Engineer All IAT-I IT-2

Programmer All IAT-I IT-2

Computer Technician All IAT-II IT-1

CUI

that is not in conjunction with this effort. All travel shall be conducted in accordance with Class

Deviation 2026-O0032 Revolutionary FAR Overhaul (RFO) 31.205-46 Travel Costs. Locations will be determined by the Government and are subject to change.

Representative travel locations may include: [Specify destinations]

The Contractor shall submit trip reports following any travel under this effort. (CDRL A00X)

C.6.2 Direct Charge of Materials

1. No Materials will be purchased under this Task Order.

C.7 GOVERNMENT FURNISHED SPACE/GOVERNMENT FURNISHED

PROPERTY/GOVERNMENT FURNISHED INFORMATION

C.7.1 Government Furnished Space

1. Government Furnished Office Space, will be not be provided.

2. Access to Government Lab Space will be provided. Lab space does not constitute office space. Government Furnished Lab Space will be provided for the following labor categories and number of personnel. No separate office space will be provided.

Labor Category # of Persons

Principal Systems Engineer 1

Senior Systems Engineer 4

Senior Systems Engineer - Combat

Systems

Systems Engineer 5

Junior Systems Engineer 5

Principal Software Engineer 1

Senior Software Engineer 3

Software Engineer 5

Junior Software Engineer 5

Programmer 1

Computer Technician 2

3. Government Furnished Property (GFP) (hardware, software, firmware) will be provided to support access to NMCI/Nautilus or other Government computer resources as required during performance of this Task Order.

C.7.1.2 Identify Other Locations of Performance

1. Bath, ME: 2 FTEs

2. Pascagoula, MS: 1 FTE

C.7.2 Government Furnished Property (GFP)

1. GFP may be issued under this Task Order. The Government will make available the

Government Property identified in the attachment J.X, Government Furnished Property on a rent-free basis in performance of the Task Order. The Contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation, or rehabilitation costs.

2. The Contractor shall maintain and report the inventory of GFP (CDRL A00X) issued under this Task Order. This requirement is in addition to anything required by regulation, statute, or the assigned Government Property Administrator.

C.7.3 Government Furnished Information (GFI)

1. The Government will provide access to information and documentation required for Task

Order performance (Attachment J.X, Government Furnished Information).

2. All information and documentation shall be retained at the Government work site.

C.8 SECURITY

C.8.1 Personnel and Facility Clearance Requirements

1. Facility Clearance Level (FCL) Requirement: The Prime Contractor supporting this Task

Order is required to have an FCL of TOP SECRET and safeguarding clearance level of SECRET at the primary facility supporting this Task Order.

2. Personnel Clearance Level (PCL) Requirement: All personnel directly supporting this

Task Order, except Management and Support personnel, are required to have, as a minimum, a current SECRET security clearance in the Defense Industrial Security System (DISS). Interim clearances are acceptable. Personnel performing in the following labor categories shall have a final TOP SECRET security clearance with Sensitive Compartmented Information (SCI) eligibility in DISS: Principal Systems Engineer (2), Senior Systems Engineer (2), Principal

Software Engineer (2), and Senior Software Engineer (2)

C.8.2 The Contractor will have access to information and compartments with a TOP SECRET /

SCI classification. All deliverables associated with this Task Order are unclassified unless otherwise specified. Access to classified spaces and material and generation of classified material shall be in accordance with the attached DD Form 254 (Attachment J.X).

C.8.3 The Department of Defense Contract Security Classification Specification (DD Form 254) provides the security classification requirements for this effort. The Contractor shall obtain facility and personnel security clearances as required by the National Industrial Security Program prior to starting to work on tasks requiring clearances. Access to classified spaces and material

CUI

and generation of classified material shall be in accordance with the National Industrial Security

Program Operating Manual (NISPOM) 32 Code of Federal Regulation (CFR) Part 117 and the

NSWCDD Command Security Manual.

C.8.4 Some work accomplished under this Task Order will be classified up to the level of TOP

SECRET. The Contractor shall maintain the capability to store information up to and including

SECRET. All data generated under this Task Order shall be classified in accordance with the guidance in the NISPOM 32 CFR Part 117 and the NSWCDD Command Security Manual.

C.8.5 The Contractor must comply with guidelines specified on the DD Form 254. Contractors

SCI indoctrinated in support of this Task Order shall comply with the reporting requirements as outlined in DOD policies Security Executive Agent Directive (SEAD)-3 dtd 12 June 2017

Implementation memo dtd 02 Nov 2020 and SEAD-4 Implementation memo dtd 12 Jan 2018.

C.8.6 The Contractor shall require access to Communications Security (COMSEC) information and materials. A COMSEC account is also required in order to maintain and use COMSEC material, which includes accountable/non-accountable COMSEC Material and Controlled

Cryptographic Items (CCI). The Contractor shall utilize CRYPTO and have access to Secure

Terminal Equipment (STE) and associated encryption device(s) at the Contractor site(s). SCI requirements are hereby authorized. Questions regarding Block 10e (1) and requests for retention or release of intelligence shall be through the NSWCDD SSO, (540) 284-0419. All SCI work on this Task Order will be performed at cleared government/contractor installations listed in block

8a (Cleared Contractor facilities require current Physical and TEMPEST Accreditations along with copies of FFC and TEMPEST Addendum.). The Contractor requires access to Non-SCI intelligence is needed in order to utilize intelligence documents related to foreign government weapons systems. The Contractor will be required to take NATO training to obtain a SIPRnet

(or cRDTE) account/s and to utilize the DTIC system to obtain documents on intelligence.

Access to classified NATO information is required by the Contractor. All personnel who have access to classified NATO information will be a U.S. citizen, have a need-to -know and a final government security clearance. Access to Foreign Government Information is required to obtain documents from Japan, Korea, Australia, Norway, Canada, and Germany for specific weapon information. In performing under this Task Order, the Contractor shall have access to U.S.

classified information outside the U.S., Puerto Rico, U.S. Possessions, and Trust Territories

(Korea, Australia, Norway, Poland, Italy, Japan, Bahamas, Guam, Romania, Spain, Germany, Bahrain, Qatar, Sweden, and Canada). Controlled Unclassified Information (CUI), formerly For

Official Use Only (FOUO) and Personally Identifiable Information (PII), generated and/or provided under this Task Order shall be safeguarded and marked as specified in DoDI 5200.48 and DoDM 5400.07. All above accesses are needed to support and provide the system engineering, software development, testing, and maintenance of Navy tactical to support

NSWCDD.

C.8.7 Facility Clearance: The Contractor shall possess and maintain TOP SECRET facility clearance as verified within the National Industrial Security System (NISS).

C.8.8 Physical Security: The Contractor shall be responsible for safeguarding all Government information or property provided for Contractor use. At the end of each work period, CUI

Government information, facilities, equipment and materials shall be secured as specified by the

32 CFR Part 117 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 Task Order.

C.8.9 Contractors working in Open Storage Secret (OSS) spaces with Open/Close privileges shall be aware of their responsibility and be trained in procedures for end-of-day security checks to include closing OSS spaces.

C.8.10 Electronic Spillage

C.8.10.1 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.

If a Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation could be charged to the Contractor.

C.8.10.2 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 that involve the Contractor. 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 annually, 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.

C.8.11 Portable Electronic Devices (PEDs)

C.8.11.1 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 General Office Spaces (GOS). All personnel need to be aware of the

PEDs policy and what is permitted in a building by asking authorized personnel or reviewing the entrance area signs and instructions. The Contractor/personnel visiting 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. PED’s 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

CUI

drives, ZIP disks, CD-RWs, DVD-RWs, MP3 players, iPADs, digital picture frames, electronic book readers, kindle, nook, cameras, external hard dish drives, and floppy diskettes.

C.8.11.2 Personal Wearable Fitness Devices (PWFDs) marketed primarily as fitness or sleep devices are allowed in all Navy spaces, if they are compliant with NAVADIN 216/15, where collateral non-Sensitive Compartmented Information (SCI), classified information is processed, stored, or discussed up to and including SECRET. The user must ensure the PWFD is compliant with all requirements in NAVADMIN 216/15, Cyber Hygiene Authorization to use Personal

Wearable Fitness Devices (e.g., FitBit, Jawbone UP, etc.) in Navy Spaces, dated 14 September

2015 and register PWFD in the NSWCDD Fitness Device Tracker.

C.8.11.3 Personnel requiring the use of Medical Portable Electronic Devices (MPEDS) must submit Form NSWCDD 5239/4 for SCIF authorization to the Special Security Officer (SSO).

For Special Access Program Facility (SAPF) authorizations, follow the guidance provided by the

Government Special Access Program Security Officer (GSSO). Authorizations for use in SAPFs that are co-utilized within NSWCDD SCIFs require coordination between both the GSSO and

SSO. For authorizations to use MPED in Collateral Classified spaces, submit form to the Special

Programs Branch, Code 1053.

C.8.11.4 PED’s 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 Temporary Approval Request for Information System (TARIS) form and action tracker process.

C.8.11.5 Personally owned hardware or software shall not be connected or introduced to any

NSWCDD hardware, network or information system infrastructure.

C.8.11.6 Navy-issued peripheral:

C.8.11.6.1 Government procured headsets with or without microphones must be wired, use either a 3.5 millimeter (mm) audio jack or universal serial bus (USB) port, cannot contain active-noise cancelling functionality and may be used on systems of classification up to and including collateral Top Secret. The headsets are considered unclassified when unplugged and must be unplugged when not in use within classified spaces.

C.8.11.6.2 Government procured Bluetooth earbuds and headsets that do not require a USB dongle or any other physical connection to enable wireless connectivity are allowed for use on

Government issued tablets, phones, and personal devices in telework environments or unclassified general office space where no classified discussion are occurring.

C.8.11.6.3 Web cameras may only be used on systems at the classification level of the space.

For example, in a collateral SECRET open storage area an external web camera may be connected to the SECRET workstation only. No camera pass is required for these devices.

C.8.11.6.4 Government provided printers and/or scanners are authorized in a telework environment. Users must ensure that any paper or media containing Controlled Unclassified

Information (CUI) or unclassified information not authorized for public release is safeguarded by

CUI

locking in a drawer, cabinet or room. CUI and unclassified information not approved for public release must be returned to the worksite for destruction.

C.8.11.6.5 Government issued peripherals may be used on personal devices.

C.8.11.6.6 While connected to any Navy network, whether on site or while in a telework environment, the use of headsets with microphones and web cameras are restricted to official

Government duties.

C.8.12 Operations Security (OPSEC)

Contractor personnel shall follow OPSEC concepts and principles in the conduct of this requirement to protect critical information, personnel, facilities, equipment, and operations from compromise. All Contractors (including Sub-contractors) shall supplement their current security practices by requiring any personnel involved in executing this Task Order to complete

Government-sponsored and administered Operations Security (OPSEC) training. In addition, all

Contractors shall be aware of the Critical Information and Indicators List (CIIL) for the organization they are supporting as well as the OPSEC Manual for NSWCDD. These OPSEC requirements will be in effect throughout the life of the procurement from award through the conclusion of services at the end of the period of performance (PoP) or other procurement termination. The Contractor must immediately notify the Government upon the discovery of any nonconformance with the OPSEC Manual.

C.8.13 Privacy Program Training

Privacy training is mandatory for all NSWCDD personnel (military, civilian, and Contractor) and must be completed annually. Total Workforce Management Services (TWMS) is the official database for Contractor workforce training and is the tool for taking and recording Privacy Act training. The Contractor is responsible for ensuring individual annual privacy training requirements are met.

C.8.14 IT-I Designation Requirements

C.8.14.1 In accordance with (IAW) DON Chief Information Officer (CIO), NSWC

Headquarters, and NSWCDD guidance, IT Level-I positions are defined as users with privileged access. Contractor employees assigned to an IT Level-I designated position with SECRET access will be required to have a favorably adjudicated T5/T5R completed every 5 years.

Contractor employees that require a SECRET Clearance as part of their job duties, with IT

Level-I designation, will be initiated by the Government, and will be at the Government's expense. Contractor employees that require a Top Secret Clearance as part of their job duties, with IT Level-I designation, shall be initiated by the Contracting Company.