Attachment 1 - ATD ASW Engineering Services IDIQ_SOW.pdf

Section C - Descriptions and Specifications

C-1 STATEMENT OF WORK

1.0 Introduction

1.1 Background

This Statement of Work (SOW) defines the scope of services required to support the organization's mission, management, policy, programs, project management and administration within the Advanced Technology Development Department (AD2) Airborne Anti-submarine Warfare (ASW) Systems Engineering Division (AD21000) and the Airborne ASW mission area specific efforts provided by the Mission Systems Group Departments and Divisions. This collaborative organizational team is responsible for the research, design, development, test, integration, delivery, operations, training, and support of legacy and new mission avionics, sensors, subsystems, and systems for naval air platforms, manned or unmanned. The mission of this organization is to provide affordable, reliable, effective, and flexible avionics and mission systems critical to the implementation of Naval Air Systems Command’s (NAVAIRSYSCOM’s) strategies for naval aviation. The work and efforts defined in this document address the full spectrum of activities performed on a recurring basis. These efforts are in support of Navy, US Marine Corps, Joint DoD, Other Government Agency and Multinational including Foreign Military Sales programs.

The overarching areas of support address the technology areas for any of the life cycle phases, i.e., Requirements Analysis phase, Concept Development phase, Planning phase, Acquisition phase, Research and Development phase, Test and Evaluation phase, Implementation phase, and Operation and Maintenance phase. Core areas addressed in this SOW are:

• Airborne ASW Systems – Acoustic and Non-Acoustic

• Airborne Information Processing Systems

• Communication Systems

• Flight Information Systems

• Navigation Systems

• Identification Systems

• Recording Systems

• Airborne Mine Counter Measure Systems

• Avionics and Sensor Systems Engineering

• Radar and Antenna Systems

• Electro Optic (EO) and Infrared Systems

• Electronic Warfare (EW) Systems

• Special Mission Sensors

• Imagery and Video Systems Software Enhancements

• Integration and Interoperability/Integrated Warfare Capability

• Technologies in support of Fixed-Wing Aircrafts

• Technologies in support of Rotary Wing Aircrafts

• Disruptive Technologies

1.2 Scope

This contract is a single award indefinite delivery / indefinite quantity (IDIQ) contract. This work augments the Government team across all functional areas, e.g., administrative, business, engineering, information technology, logistics, operations, and program management, and all life cycle phases necessary to ensure continuity of services in support of legacy and new sensors, subsystems, systems, and mission avionics for naval air platforms and to improve existing mission systems. The scope will include engineering, management, and technical labor, materials for technology assessment and development, fabrication, laboratory and field experiments, ship and air exercises, test, installation, system integration, maintenance, aircrew training, fleet assistance/training, procurement activities, and environmental compliance documentation. The scope will also include the capability to arrange for aircraft support and function as Project Specialists for the purpose of hosting legacy and new sensors for inflight testing in accordance with (IAW) DFARS 252.228-7001 Ground and Flight Risk clause.

Specific requirements will be derived from the scope of this SOW and documented through individual non-performance based level of effort Task Orders (TOs).

The contract deliverables (including reports, software, and hardware) will not be classified at the Sensitive Compartmented Information (SCI) level. SCI will be utilized and accessed as part of routine work only. Tasking shall require access to SCI-level information and facilities.

2.0 Applicable Documents

The following documents are applicable to the SOW as specified herein. This list is not all-inclusive. This list is for reference only and defines the most common documents, policies, and specifications that may be applicable in the performance of the duties defined within this SOW.

New instruction, supplements, amendments, or revisions to documents may be issued during the term of the contract and shall be in full force and effective immediately upon receipt by the Contractor. In the case of an inconsistency between the industry standards referenced herein and the Government documents referenced below, the Government standard will always take precedence. Additional documents may be identified at the individual TO level.

2.1 Referenced Documents

2.1.1 Department of Defense (DoD) Documents

• DoD National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule

• DoD Risk, Issue, and Opportunity (RIO) Management Guide for Defense Acquisition Programs

• DoD 2875 SAAR – System Authorization Access Request (SAAR)

• DoDM 5205.02-M CH-2, DoD Operations Security (OPSEC) Program Manual 29 October 2020

• DoD 5220.22-M, National Industrial Security Program Operating Manual

(NISPOM)

• DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program, 5 Apr 2019

• DoDD 8140.01, Cyberspace Workforce Management

• DoDI 3204.01 CHG-2, DoD Policy for Oversight of Independent Research and

Development (IR&D)

• DoDI 5000.02, Operation of the Defense Acquisition System

• DoDI 5200.48, Controlled Unclassified Information

• DoDI 5220.31 National Industrial Security Program (NISP)

• DoDI 5230.24, Distribution Statements on DoD Technical Information

• DoDI 8500.01 CHG-1, Cybersecurity

• DoDI 8510.01, Risk Management Framework (RMF) for DoD Systems

• DoDI 8520.02, Public Key Infrastructure and Public Key Enabling

• DODI 8582.01 - Security of Non-DoD Information Systems Processing Unclassified

Nonpublic DoD Information

• DoDM 5105.21, Volumes I-III - Sensitive Compartmented Information (SCI)

Administrative Security Manual

• DoDM 5200.01 Vol 1 CHG-2, DoD Information Security Program: Overview, Classification, and Declassification

• DoDM 5220.32, Vol 1 CHG-2, National Industrial Security Program: Industrial

Security Procedures for Government Activities

• DoDM 5220.32, Vol 2 CHG-2, National Industrial Security Program: Procedures for

Government Activities Relating to Foreign Ownership, Control, or Influence (FOCI)

• DoDM 5400.07, Freedom of Information Act (FOIA) Program

• Joint Service Specification Guide (JSSG) 2005 NOT 3, Avionic Subsystem

• Joint Travel Regulation, The Per Diem, Travel and Transportation Allowance

Committee, Dept. of Defense, Dec 2024

2.1.2 Department of the Navy Documents

• SECNAVINST 5000.2G, Implementation & Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System

• SECNAVINST 5100.13F – Navy Tobacco Policy, 2 December 2020

• SECNAVINST 5239.25 – Department of the Navy Cyberspace Workforce

Qualification and Management Program

• SECNAVINST 5239.3C Department of the Navy Cyber Security Policy

• SECNAVINST 5510.30C, Department of the Navy, Personnel Security Program

• SECNAVINST 5510.36B, Department of the Navy Information Security Program

• OPNAVINST 3432.1A, Operations Security

• OPNAVINST 3440.17A, Navy Installation Emergency Management Program

• OPNAVINST 3710.7V, Naval Air Training and Operating Procedures (NATOPS)

Standardization Program

• OPNAVINST 5090.1E, Environmental Readiness Program

• OPNAVINST 5239.1D – US Navy Cybersecurity Program

• OPNAVINST C5510.93F

• OPNAVINST 5530.14E CH-3, Navy Physical Security and Law Enforcement

Program

• NAVAIRINST 13050.7, Change Management Policy, Procedures, and

Responsibilities for Aircraft Assigned to Naval Air Systems Command Aircraft Controlling Custodian

• NAVAIRINST 3710.1H, Contractor’s Flight and Ground Operations

• NAVAIRINST 3710.8F CH-1, Authority for Personnel to Pilot or Fly in Aircraft

Under the Controlling Custody of Naval Air Systems Command

• NAVAIRINST 4355.19E, Systems Engineering Technical Review Process

• NAVAIRINST 5000.21B, Naval Systems Command Risk Management Policy

• NAVAIRINST 5211.5A, Naval Air Systems Command Privacy Act Program

• NAVAIRINST 13034.1G, Airworthiness Policy

• NASPAXRIVINST 5510.15R –Regulations Governing Admission to the Naval Air

Station, Patuxent River, Navy Outlying Field Webster, and Naval Recreation Center, Solomon’s Maryland

• NASPAXRIVINST 12610.7H – Employee Reporting Procedures during Emergencies

• NAVSEAINST 9310.1C, Naval Lithium Battery Safety Program

• NAVSEA S9310-AQ-SAF-010, Rev 3, Navy Lithium Battery Safety Program

Responsibilities and Procedures

• NAVADMIN 259/23 System Access Authorization Request (SAAR)

2.1.3 Other Government Documents

• Executive Order 12829, as amended, National Industrial Security Program

• Executive Order 13526, Classified National Security Information

• CMS-1 Department of the Navy (DON) COMSEC Policy and Procedures Manual

• Committee on National Security Systems Instruction 1253, Security Categorization and Control Selection for National Security Systems

• Communications Security Materials System (CMS-1) Policy and Procedures Manual

• DFARS Clause 252.204–7012 Safeguarding covered defense information and cyber incident reporting

• DFARS 252.228-7001, Ground and Flight Risk

• Directive-Type Memorandum (DTM) 09-019 - “Policy Guidance for Foreign

Ownership, Control, or Influence (FOCI)

• MIL-HDBK-61B, Configuration Management Guidance

• MIL-HDBK-29612/1A NOT 4, Guidance for Acquisition of Training Data Products and Services

• MIL-PRF-29612B NOT 4, Training Data Products

• MIL-STD-464D, Electromagnetic Environmental Effects Requirements for Systems

• MIL-STD-882E, Change 1, System Safety

• MIL-STD-1472H, Human Engineering

• NASPAXRIVINST 12610.7H – Employee Reporting Procedures During Emergency

Conditions

• National Security Agency (NSA) Central Security Service (CSS) Policy Manual 3-

• NIST SP 800-171 Rev 2, Special Publication: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations

2.1.4 Other Documents

• IEEE/EIA 12207 Systems and Software Engineering —Software Life Cycle Processes

3.0 Requirements

3.1 General Requirements (RDT&E, PROC, NWCF, O&M, FMS, FCP, OTHER)

3.1.1 Compatibility

The Contractor shall maintain the capability to prepare documents and software packages compatible and interoperable with the Government Information Technology (IT) environment.

The current operating environment required for this contract includes:

• Microsoft Windows (current version the Government is utilizing)

• Microsoft Project 2016

• Microsoft Office Professional Plus 2016

• Microsoft Office M365 Products

• Microsoft SharePoint 2016

• Microsoft Teams

• Adobe Acrobat Pro

• Internet access

Additional capability requirements will be included in individual TOs and may include, but not be limited to the following:

• MATLAB 2019a

• LabView 2024 Q3

• AutoCad 2016

• SolidWorks 2016

• Visio 2010

• Linux Ubuntu Red

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. For contract administrative or indirect functions performed at the Contractor site, the Contractor shall ensure that all media delivered to the Government are virus free when delivered. The Contractor shall maintain real-time communications, both voice and data capabilities, with the Government during working hours whether at Contractor work site or on travel.

3.1.2 Work Location, Facilities, and Work Schedules

3.1.2.1 Primary Work Locations

Approximately 90 percent of the work will be performed at the Government site (Naval Air Warfare Center Aircraft Division (NAWCAD), Patuxent River MD and NAWCAD Detachment Crane Indiana) and 10 percent of the work will be performed at the Contractor site. Government onsite support does not include temporary and ad-hoc support performed away from NAVAIR facilities. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, network access including web servers, tooling, and applications necessary to carry out assigned tasks.

3.1.2.2 Secondary Work Locations

As defined at the TO level, the Contractor shall provide short and/or long-term technical support services at remote sites on land and at sea, both in Contiguous United States (CONUS) and Outside Continental United States (OCONUS). This may include both Government sites and other Contractor facilities.

3.1.2.3 Meeting Support

In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at classification levels up to Top Secret. The Contractor shall provide meeting space capacity of up to 80 individuals for Unclassified through Top Secret level meetings. Meetings that include SCI must be held at accredited government facilities only. The Contractor shall furnish sufficient equipment to conduct in-person or virtual meetings with presentations including compatible software as required in SOW paragraph 3.1.1. The Contractor shall provide the meeting support within 15 driving miles of Naval Air Station (NAS) Patuxent River, MD.

The Contractor shall conduct program meetings and reviews in support of contracted work. The Contractor shall establish agenda and content for each meeting and review. The Contractor shall participate in Government-led technical, programmatic, engineering Technical Interchange Meetings (TIMs). Whenever possible, meetings shall be combined and/or virtual to minimize Government and Contractor travel and documentation requirements.

3.1.2.3.1 Post-Award Conference

The Contractor shall conduct a Post-Award Conference (PAC). The purpose of the PAC is to ensure both Government and Contractor personnel have a clear understating of all contract requirements. The Contractor shall work collaboratively with the Government to establish the agenda for the PAC and shall deliver conference minutes following the PAC.

The Contractor shall prepare and deliver presentation material IAW CDRL A001. The Contractor shall prepare and deliver conference minutes IAW CDRL A002.

3.1.3 Facilities

When Federal facilities are closed by the Government or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility-related problem that prevents Federal personnel from working at the Government facility, Contractor personnel assigned to work at that facility in support of such Federal employees shall follow their parent company’s policies.

Contractor personnel may not perform work on-site at a Government facility without oversight from Federal personnel. In extremely limited circumstances, the Government may authorize the

Contractor to continue working at the Government’s facility, although closed, if the work is mission essential. The circumstances permitting mission-essential work performed by contractor personnel are extremely limited and generally only apply to the performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer (CO) must concur with any determination that work performed by contractor personnel is mission essential.

NASPAXRIVINST 12610.7H – Employee Reporting Procedures During Emergencies identifies procedures Government employees, military personnel and contractors are to follow when an emergency condition is identified. The Contractors shall follow the procedures as defined except for being granted administrative leave. Contractors that are at work when a delay or restricted access is announced shall cease work and exit the base as soon as it is safe to do so.

3.1.4 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays and installation closure

3.1.4.1 Work Schedule

The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0730 to 1600 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.2). If different hours are needed by a government team or the Contractor (e.g. individual groups or locations may allow or require different hours) on a long-term basis, they will be coordinated through the Technical Point of Contact (TPOC) associated with that work and approved by the Contracting Officer Representative (COR). Specific test events may require hours be shifted on a short-term basis and do not require COR approval. Specific test events may require changes in normal work schedules and may include the requirement for staffing of multiple shifts. Test events will be identified at the individual task order level and do not require COR approval for schedule changes.:

3.1.4.1.1 CWS

The CWS is an alternative work schedule to the traditional five 8.5-hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one Friday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one Friday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

The Contractor may allow its employees to work a CWS schedule. The CWS schedule shall not prevent Contractor from providing necessary staffing and services coverage as required by the contract and individual TOs. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government.

3.1.4.1.2 Holidays

The Government observes the Federal holidays identified on the Office of Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview. With the exception of the events in section 3.2.6, the Contractor will follow its corporate policy on observing Federal holidays.

https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview

3.1.4.1.3 Overtime (OT)

Overtime premiums cannot be charged directly to the contract unless first approved in writing by the Chief of the Contracting Office IAW NMCARS 5222.103. For critical/time-sensitive tasking, with prior approval of the COR/ACOR, additional hours may be authorized at the Contractor's regular fully burdened hourly rate to the extent consistent with the Contractor's accounting practices and the Fair Labor Standards.

3.1.4.1.4 Travel/Temporary Duty (TDY)

When personnel are temporarily deployed offsite, the Contractor shall modify the traveler’s working hours to best support the assigned tasking and minimize overtime.

3.1.4.1.5 Telework

The Contractor may allow employees to telework with approval from the COR in writing, that a positions tasking is eligible for telework. The Contractor may utilize alternate worksites / locations and telework to support continued performance of SOW tasks in accordance with company policy. When using telework, the Contractor remains responsible for contract performance and compliance with any applicable cost accounting standards and contract cost principles / procedures.

3.1.5 Travel, Travel Locations

3.1.5.1 Travel

The Contractor shall be required to travel in support TOs issued under this contract. Travel will be allowable only when it is essential to the performance of the tasks detailed in the TO.

The Contractor shall provide the COR travel authorization validation documentation for all personnel participating on any travel requirements from the TO requiring office. The Contractor shall submit any travel authorization validation documentation no less than 10 business days prior to travel.

All travel shall be approved and reimbursed in accordance with CTXT.232-9509 TRAVEL

APPROVAL AND REIMBURSEMENT PROCEDURES (NAVAIR) (OCT 2013).

3.1.5.2 Travel locations

Travel locations may include, but are not limited to, various commercial facilities, contractor facilities, Navy facilities and ships, DoD facilities/installations, other Government agency offices (e.g. test ranges, operational activities, project/program offices, and support activities), including travel OCONUS to any Component Commander’s Area of Responsibility. CONUS travel locations may include:

• Florida: Kew West, Homestead, West Palm Beach, Panama City, Tampa, DeLeon Springs, Orlando, Pensacola, and Jacksonville.

• Georgia: Kings Bay

• North Carolina: Marine Corps Air Station New River, Marine Corps Air Station Cherry

Point.

• Maryland: Patuxent River, Lexington Park, and California.

• New Jersey: Lakehurst.

• Pennsylvania: Warminster, and Horsham.

• Indiana: Crane, Ft. Wayne, and Lapel.

• Washington: Seattle, Whidbey Island

• California: Huntington Beach, North Island, China Lake, San Diego, Point Mugu, and St

Clemente Island.

This list is not all-inclusive as locations may change over the life of the contract.

3.1.5.3 Travel Efficiency

The number of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. Contractor Personnel traveling for a common mission shall utilize common facilities and transportation (e.g., hotels and rental cars) as much as is practical. The Government will not reimburse travel costs incurred in replacing personnel at a TDY site when such replacement is at the Contractor’s or employee’s convenience. Exceptions may be made with COR approval when considering the circumstances of the stated travel.

3.1.5.4 Government and Military Transport

Contractor personnel may be authorized to be a passenger on Government or military aircraft, ships, and barges during non-test periods in the performance of their duties under this contract.

Contractor personnel will never be authorized to be a passenger if the aircraft, ship or barge is an Engineering and Manufacturing Development (EMD) item. Contractor personnel may also be authorized to be a passenger in Government-operated shuttles. Contractor transport on Government or military vehicles will be authorized only when such transport is essential to the performance of the contract and is determined to be cost-effective for the Government. The Contractor's travel request to the COR shall specifically request the use of Government transportation when applicable. Note: This paragraph applies for travel only and does not apply for activities conducted as a Project Specialist for the purpose of performing inflight testing in accordance with (IAW) DFARS 252.228-7001 Ground and Flight Risk clause

3.1.5.5 OCONUS Travel

The Contractor shall comply with all OCONUS travel requirements dictated by the DoD, Department of State (DoS), Host Nation, and respective Combatant Command (COCOM).

3.1.6 Material

The Contractor shall obtain written approval by the COR/Procuring Contracting Officer (PCO) prior to the purchase of any material as directed in NAVAIR Clause CTXT.242-9520. If the Contractor’s TO proposal includes a list of materials with associated prices, then the PCO acceptance of the Contractor’s proposal shall constitute written approval of those purchases. Any material provided by the Contractor is subject to the requirements of the FAR, the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy regulations and instructions including NAVAIR Clause CTXT.242-9520 Procedures and Approvals Required Prior to Incurring Direct Material Costs. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The Contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administrative expenses but shall not include profit/fee

3.1.7 Program / Project Performance Management

Note: For this SOW, “Program” is defined as the entire contract effort, managed, administered, and managed by the Contractor. A “Project” is defined as an effort performed within the Program to meet specific technical and operational requirements for specific customers executed by Integrated Product Teams (IPTs) consisting of contractors, Government, military, and other personnel.

3.1.7.1 Performance Management

The Contractor shall maintain an effective performance management program to ensure services are performed and supplies are delivered IAW the basic SOW, individual TOs, and the Surveillance Activity Checklist (SAC). The Contractor shall implement procedures to identify, prevent, and ensure non-recurrence of defective services.

The Contractor’s program manager shall participate in weekly and ad-hoc management meetings with the COR to assess the contract status, accomplishments, issues and opportunities.

The Government will evaluate the Contractor’s performance under this contract IAW the SAC, which is included as an attachment to the contract in Section J.

3.1.7.1.1 Program Management Reviews (PMRs)

The Contractor shall conduct quarterly Program Management Reviews (PMRs) to provide the Government with visibility into the various efforts by the Contractor and its subcontractors. The Contractor shall work collaboratively with the Government to establish the agenda for the PMRs.

The Contractor shall present and review the status of the technical, financial, quality, test, and schedule performance of the program during the PMR. The Contractor shall highlight problem areas in the program and provide recommendations for corrective actions during the PMR.

The Contractor shall prepare and deliver presentation material IAW CDRL A001. The Contractor shall prepare and deliver conference minutes IAW CDRL A002.

3.1.7.1.2 Management of Contractor Personnel

The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for, individual contractor employees. All direction and clarification on work contained in this SOW shall come from the COR and/or the NAWCAD Contracts Office.

Contractor personnel shall remain employees of the Contractor and will not be considered employees of the Government. The contract PM shall ensure the Contractor workforce understands this employer difference when issues come up that affect the Government but does not include the Contractors.

3.1.7.1.3 Sub-Contractors

The Contractor shall communicate all provisions stated herein to all subcontractors providing support under this contract. The Contractor shall flow all provisions of this SOW down to the subcontractors providing support under this contract.

3.1.7.1.3.1 Working with the Government

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks.

3.1.7.2 Earned Value Management (EVM)

IF required at the TO level, the Contractor shall implement an EVM System (EVMS) that has been determined to be in compliance with the guidelines in EIA-748. The Contractor shall provide access to all pertinent records and data requested by the Contracting Officer or duly authorized representative as necessary to permit initial and ongoing Government compliance reviews to ensure that the EVMS complies, and continues to comply, with the guidelines in EIA-748. The Contractor shall prepare and deliver the EVM Report IAW CDRL A003.

3.1.7.3 Training

3.1.7.3.1 New Hire Orientation

The Contractor is responsible for providing an orientation to new hires to enable them to adequately perform their tasking. Orientation shall include, but is not limited to:

• Physical knowledge of the base and Government facilities

• Contract information (Contractor/COR interaction and basic contract requirements)

• Labor category requirements

• Specific process requirements (Government and Contractor)

• Org chart/hierarchy for both Contractor and Government

• Introductions (COR/Alternate Contacting Officer Representative (ACOR), Government task lead, Contractor task lead, etc.)

• Security

• Safety

• Government Standard Operating Procedures

3.1.7.3.2 Labor Category Training Requirements

The Contractor is responsible for providing individuals who are trained, certified, and qualified to perform the tasks outlined in the SOW. Training to meet labor category requirements is the sole responsibility of the Contractor – both initial training and required re-certifications. The Contractor is responsible for the cost of the training (class, travel, supplies) and the labor associated with the training. These training requirements shall be met before the contractor personnel reports for duty except as identified in the specific labor category description. Due to the availability and location of some training classes, exceptions may be made to allow personnel to begin working while waiting for the training to become available with prior approval by the COR. In the case of re-certifications, the Contractor shall plan ahead of time to not impact workload due to missed days for training or expiring certifications.

3.1.7.3.3 Technical Training

Due to the technical nature of the work, there may be special, unique, and emergent training required during the execution of this contract. This training may include but is not limited to, specific software, hardware, and procedures as required for the specific system, or requirements being supported. All requests for cost-reimbursable training shall include a written justification by a Government TPOC and course information including, but not limited to, the source of the training, the dates of the training, a training course description, and training cost including quotes from the vendor. General educational courses or programs for the enhancement of basic qualifications or academic standing of employees shall not be accomplished at the Government’s expense. No cost-reimbursable training shall be scheduled or executed without written approval from the COR IAW CTXT.242.9520 PROCEDURES AND APPROVALS REQUIRED PRIOR

TO INCURRING DIRECT MATERIAL COSTS (APR 2022).

3.1.7.3.4 Mandated Training

For the performance at Government facilities, this contract requires contractor personnel to complete training such as Anti-Terrorism and Active Shooter, and any required Operational Security (OPSEC) topics. In addition, during the contract, the Government may mandate training for all personnel. This training may be computer or instructor based. Contractor personnel shall participate in these training requirements. Participation may be at live training, events, computer-based training, or via review of a provided set of documents. This training shall be provided and/or reimbursable by the Government. Contractor personnel supporting functions where Personally Identifiable Information (PII) or classified data may be handled, shall complete the Navy-provided “Security Awareness training” and “Privacy Act Training” within forty-five (45) days of assignment to such functions and annually thereafter. The Contractor Program Manager shall ensure all contractors on the contract are trained and shall report compliance to the COR within five (5) working days after the announced deadline of the training.

3.1.8 Aircraft Facility Related Activities

In the performance of the contract, the Contractor will have access to aircraft hangars, flight lines, maintenance areas, mobile and fixed ground control stations, or other facilities or spaces. All Contractor personnel shall follow the local instructions, policies, and procedures regarding physical access, foreign object damage, tool control, and reporting requirements.

3.1.9 Shipboard Related Activities

In the performance of the contract, the Contractor may have access to ships, support vessels, harbors, dock, piers, and other associated facilities. All Contractor personnel shall follow the local instructions, policies, and procedures regarding physical access, foreign object damage, tool control, and reporting requirements.

3.1.10 Reports and Data Management

To enable electronic data harvesting and cross-checking, the Contractor shall use personnel names and labor categories EXACTLY the same across all CDRLs consistent with SOW Section 3.5.

3.1.10.1 Integrated Data Environment

The Contractor shall implement and maintain an Integrated Digital Environment (IDE) for the exchange of programmatic and technical data with the Government. The Contractor shall provide access to the IDE for up to 20 Government personnel and support contractors with appropriate NDAs.

The Contractor shall ensure that the IDE contains all program development information, including intermediate and final artifacts, both in-work and completed, developed and used as a part of the development activity, to include, at a minimum, all design data items, review materials (briefings and reports), technical reports and briefings, all measures and metric reports, peer review reports, program schedules, architectural System Models, and all Software Development Folders (SDF) (including all requirements, design documents, code, test cases, and test results).

The Contractor shall implement cybersecurity measures to protect contract data stored on the IDE. The Contractor shall implement security safeguards to protect confidentiality, integrity, and availability of contract data products on the IDE.

The Contractor shall implement receive and maintain IDE authority to operate from Defense Security Services (DSS). The Contractor shall prepare and deliver a Data Accession List (DAL), IAW CDRL A004.

3.1.10.2 Monthly Progress and Status Reporting

The Contractor shall provide a monthly progress and status report IAW CDRL A003. This report provides the progress of ongoing and accomplished work, performance to plan, status of the contract and TOs, financial status, projections against financial budget, and informs the Government of any existing or potential problem areas. The Contractor shall provide an overall contract summary of the awarded ceiling, funded ceiling, unfunded committed ceiling from unexercised priced options, obligations not expensed, and expenditures. The Contractor shall include an itemized breakout of all work accomplished since the submittal of the last report. The Contractor shall itemize both monthly and cumulative man-hour labor costs and labor fee expended by Contract Line Item Number (CLIN) and labor category. The Contractor shall itemize material, and travel costs including general and administrative. All information shall be organized by TO/DO.

The report shall include a summary table of the current average hourly fully burdened rate in execution by labor category, level, and performance period compared to the proposed average rates. The report shall also provide an order financial health projection based on average labor burn rates for each TO/DO and at the basic level of the contract.

3.1.10.3 Government Furnished Property/Information (GFP/I)

The Contractor shall have an approved system for storage and tracking of all GFP/I provided by the Government. The Contractor shall ensure that GFP/I is traceable to the TO level.

The Contractor shall prepare and deliver an annual Government Furnished Property Report IAW CDRL A005. This report enables the Contractor to provide the requiring office with an inventory listing of Government property (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) in the contractor’s possession (to include subcontractors) by TO. The Contractor shall document all non-consumable GFP, Government Furnished Equipment (GFE), and CAP that is or has been in the possession of the Contractor at any time. The Contractor shall report each item, quantity, replacement value, location, purchase order number (CAP only), date of receipt, and date of transfer of custody to the Government, and the Government and Contractor technical point of contact. The Contractor shall return all GFP/GFE/CAP to the Government upon completion of the associated TO/DO and termination or expiration of the contract.

3.1.10.4 Contractor Personnel Locator Report

The Contractor shall provide a monthly Contractor Personnel Locator Report in accordance with

CDRL A006.

3.1.10.5 Accident Incident Reporting

While performing this work accidents or incidents occasionally occur to equipment and personnel. The Contractor shall protect its personnel from hazards and create a healthy work environment. The Contractor shall report any incidents observed (whether they are involved or not) to ensure proper procedures are followed to minimize the risk of any further injury or property damage. The Contractor shall establish a log of recordable incidents, injuries, and illness and present this information to the COR after each incident IAW CDRL A007.

3.1.11 Transition Strategy

3.1.11.1 Phase-In Activities

Due to the IDIQ structure of this contract, transition activities may occur throughout the lifecycle of the contract. This includes basic contract award and individual orders. The Contractor shall support the Government with Phase-in activities to include, but not limited to, the following actions:

• Provide a written narrative delineating a phase-in plan that ensures a smooth workplace change over from an incumbent, with no loss of service and minimal loss of corporate knowledge

• Customer requirements analysis and order level contract structure (i.e. new vs modification of existing order, CLINs, cost type, options, TDLs, etc.) recommendations

• A transition communication plan between all agents

• Customer resourcing recommendations

• Generation of rough orders of magnitude of cost and schedule

• Identification of required Government Furnished Property and Information

• Risk and mitigation strategies

• Performance Location requirements assessment and recommendations

• Identification and requirements definition of additional order level CDRLs

• Employee On-Boarding

The Contractor shall submit a Phase-In Transition Plan, to include the minimum elements listed above IAW CDRL A008.

3.1.11.2 Phase-Out Strategy

The Contractor shall develop a Phase-out strategy that provides continuity of operations of the work. The Phase-out strategy will include timeliness of performance and ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation.

The Contractor shall submit a Phase-Out Transition Plan, to include the minimum elements listed below IAW CDRL A009.

• Work Turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming contractor or Government personnel for the period of transition via weekly status meetings.

• Quality Assurance. The Contractor shall provide a plan of action to ensure the continuation of quality review processes during the transition period to the successor company.

• Risk Mitigation Strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

• Data/Information/Materials Transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of data and materials/Government Property to the successor company.

3.2 Security (RDT&E, PROC, NWCF, O&M, FMS, FCP, OTHER)

3.2.1 Citizenship Requirements

Only United States (U.S.) citizens may perform under this contract. The Contractor shall submit a citizenship waiver justification to the Government Security Office, via the TPOC, if unable to find a qualified U.S. citizen to perform the work, the waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific Government contract (TBD at time of award).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

Note that submittal of a waiver does not guarantee Government approval.

3.2.2 Investigative Requirements

All contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract's DD-254, Contract Security Classification Specification Form.

Contractor personnel shall require access to classified information in the performance of this contract up to and including TS/SCI with a safeguarding level of TOP SECRET. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

Additional investigative requirements apply for all personnel supporting TS/SCI tasking;

reference Section 3.2.11.

3.2.3 Common Access Card (CAC)/ Public Key Infrastructure (PKI), SAAR, and Other

Badging

3.2.3.1 CAC/PKI

Contractor CACs and facility-specific identification badges will be issued by the Government to on-site personnel and shall be always visible above the waist while personnel are at the

Government site. The Contractor shall furnish all requested information required to facilitate the issuance of identification badges. The Contractor shall return CAC identification.

All CACs and identification badges issued to contractor employees shall be returned to the Trusted Agent (TA) following completion of the contract, relocation, or termination of an employee, or upon request from the Contracting Officer’s Representative/PCO. The Government will provide the Contractor access to Government facilities, as required, for the performance of tasks under this contract.

3.2.3.2 SAAR

All Contractor personnel requiring access to Government IT systems shall access and operate IT systems and networks IAW NAVADMIN 259/23 and CTXT.204-9505 SYSTEM

AUTHORIZATION ACCESS REQUEST NAVY (SAAR) REQUIREMENTS FOR

INFORMATION TECHNOLOGY (IT) (NAVAIR) have an approved SAAR – System Authorization Access Request form on file, and complete required Annual Information Awareness/Cyber Security Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. The form may be completed electronically online at:

https://nhdsm.navair.navy.mil/ or manually by downloading the SAAR form is available at:

https://www.esd.whs.mil/Portals/54/Documents/DD/forms/dd/dd2875.pdf The Contractor shall submit SAAR forms to the COR, Government TPOC, or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.3 Other Badging

Badges to special, classified, limited access, and/or commercial facility (e.g. Prime Contractor for a project or platform) areas may be required by the Contractor based on location and tasking.

The Contractor shall adhere to the rules governing the issuance of those badges.

3.2.4 DD-254

The Contractor shall comply with security requirements as specified in the DD-254 of this contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “Controlled Unclassified Information (CUI).” Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the COR of this contract for approval.

CU information generated and/or provided under this contract shall be marked and safeguarded as specified in DODM 5200.01 – DoD Information Security Program: Controlled Unclassified Information (CUI) Vol. 4 (enclosure 3 pages 11-18) available at https://www.dodig.mil/Portals/48/Documents/Policy/520001_vol4.pdf.

3.2.5 Information Security

If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI IAW National https://nhdsm.navair.navy.mil/ https://www.esd.whs.mil/Portals/54/Documents/DD/forms/dd/dd2875.pdf https://www.dodig.mil/Portals/48/Documents/Policy/520001_vol4.pdf

Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAV M-5510.36B, Department of the Navy, Information Security Program. If the work is performed at the Government’s facility, the Contractor shall comply with instructions/guidance required by that facility.

3.2.5.1 Marking

All information generated by the Contractor shall be properly marked. CUI including Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF.

3.2.5.2 Public Release

No information about this contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by the appropriate U.S. Government authority. Proposed public releases shall be submitted for approval before release through the NAWCAD Public Affairs Office (PAO) via the COR listed in GTXT.201-9501 Designation Of Contracting Officer's Representative (COR)

(NAVAIR) (APR 2022).

3.2.5.3 Loss, Compromise, and/or Electronic Spillage of Classified or Controlled Unclassified Information

All instances of loss, compromise, and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC, and Government Security Office within 24 hours of the incident occurring.

3.2.5.4 Compliance with NIST 800-171

a. The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev.

1) (NIST SP 800-171) or establish a System Security Plan (SSP) and Plan of Action and Milestones (POA&M) that varies from NIST 800-171 only IAW DFARS clause 252.204- 7012(b)(2), for all covered contractor information systems affecting this contract.

b. Notwithstanding the allowance for such variation, the Contractor shall name in any SSP and POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to use acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as Computer Numerical Control (CNC) equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted.

(2) Implement Control 3.1.5 (least privilege) and associated Controls and name practices that the Contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles.

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis.

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e., FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in an SSP and POA&M).

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POA&M for implementation, which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

3.2.5.5 Operational Security (OPSEC)

The Contractor shall develop, implement, and support an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during the performance of the contract IAW CDRL A00A.

The Contractor shall develop, implement, and support a Program Protection Implementation Plan (PPIP) IAW CDRL A00B to protect classified and sensitive information to be used at a contractor's and subcontractor's facilities during the performance of this contract. The Contractor shall require the subcontractors to implement the PPIP and OPSEC requirements. This program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be IAW National Security Decision Directive (NSDD) 298, and at a minimum shall include:

a.…