Attachment 1 - AARDTE Sources Sought Statement of Work (SOW) - DRAFT.pdf

N0042124R0TBD

Section C - Descriptions and Specifications

1 Introduction

1.1 BACKGROUND

The Digital Analytics, Infrastructure and Technology Advancement (DAiTA) Group is the Naval

Air Warfare Center- Aircraft Division (NAWC-AD) center of excellence and point–of–entry for

Research, Development, Test and Evaluation (RDT&E) of the synthetic battlespace environment, modeling and simulation, aircraft prototyping, instrumentation and experimentation, electronic warfare and cyberwarfare and provides the associated laboratories, facilities and infrastructure to support research, development, testing, training, systems evaluation and experimentation. The DAiTA Group performs and supports full spectrum

RDT&E of highly integrated and adaptive aircraft, weapon, ground and distributed systems through the application of secure and controlled engineering processes and by the use of a suite of fully integrated stimulation and simulation laboratories. This environment is developed, integrated, validated, and maintained by a collection of highly integrated divisions. In performance of this mission, the DAiTA Group operates, maintains and manages a number of

Navy Installed System Test Facilities to support test and evaluation events for a variety of aircraft avionics and weapon systems. These facilities provide both physical and simulated environments and are designed to place test articles in a realistic, yet simulated combat environment. From launch to recovery, every phase and aspect of a mission is simulated to enable engineers to capture data necessary to assess the efficiency and capabilities of the avionics or weapons systems under test. Real– world threat signals are produced to evaluate avionics and sensor system performance while studying and identifying the Electromagnetic

Environmental Effects nE3) these and other signals have on the avionics and other co–located systems. A multitude of communications simulation and stimulation T&E systems provide assessments of aircraft and aircrew communications and interoperability capabilities. Additional testing provides an overall assessment of the entire kill–chain, from target identification, to target engagement, including damage assessment and indication. For large–scale simulations used across an acquisition lifecycle, the department is also the lead for model management, scenario development, interface support, distributed simulation expertise, and Verification, Validation, and Accreditation (VV&A).

The DAiTA Group contains Advanced Aircraft Research, Development, Test, and Evaluation

(AARDT&E) laboratories capable of operating either independently or collaboratively to provide complete test and evaluation of aircraft weapons systems across multiple Departments and

Divisions. DAiTA Group has the unique ability to reduce program risk by creating complex battlespace environments where concepts, hardware and war fighters can be immersed into the missions of today and of the future. The DAiTA Group laboratories and facilities are identified as

Major Range Test Facility Base (MRTFB) assets and as such are required to support all

Department of Defense (DoD) RDT&E. The integrated assets, distributed capability and the synthetic battlespace are powerful tools that support RDT&E across all phases of systems acquisition. The Integrated Battlespace Simulation and Test (IBST) Department is the responsible agent for the research, development, management, design, documentation, fabrication, installation, integration, test, evaluation, operation and maintenance for the Air Combat Environment Test

Facility (ACETEF) and other DAiTA AARDT&E capabilities, laboratories and facilities. These laboratories and facilities include, but are not limited to the following:

• Threat Air Defense Laboratory

• Electronic Warfare Integrated Systems Test Laboratory

• Communication Navigation and Identification (CNI) Laboratory

• Electro-Optical/Infrared Laboratory

• Kathy S. Johnson Radar Laboratory

• Advanced Systems Integration Laboratory

• Aircraft Anechoic Test Facility

• Electromagnetic Interference Chambers

• Shielded Hangar

• TEMPEST*

• Electromagnetic Immunity/Interference Laboratory

• Simulated Engagement Analysis Laboratory

• Multi Jammer Characterization Laboratory

• Modern Communications Laboratory

• Joint Simulation Environment

• DAiTA Managed Research, Development and Platform Laboratories

* TEMPEST is not an Acronym.

1.2 SCOPE

This contract is a single award indefinite delivery / indefinite quantity contract to perform research, development, management, design, documentation, fabrication, installation, integration, test, evaluation, operation and maintenance for the IBST and associated AARDT&E capabilities, laboratories and facilities. Specific requirements will be derived from the scope of this statement of work and documented through individual Delivery Orders (DO) or Task Orders

(TO). The Government anticipates that orders will include a combination of non-performance based level of effort task order and performance based completion efforts. This tasking shall include Sensitive Compartmented Information (SCI) requirements, but none of the deliverables shall contain SCI. Tasking shall require access to SCI level information and facilities.

2 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 DO/TO level.

2.1 Referenced Documents

2.1.1 Federal / DOD / Military Documents

Joint Travel Regulation (JTR)

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

Security Manual

DODI 5200.48 – DoD Information Security Program: Controlled Unclassified Information (CUI)

National Industrial Security Program Operating Manual (NISPOM)

DODD 5230.24 – Distribution Statements on Technical Documents

DODI 8582.01 - Security of NON-DOD Information Systems Processing Unclassified Non-

Public DOD Information

NIST SP 800-171 – Special Publication: Protecting Controlled Unclassified Information in

Nonfederal Systems and Organizations

DODI 6055.11 – Protecting Personnel from Electromagnetic Fields

NAVY Documents

EKMS-1b - Electronic Key Management System (EKMS) Policy and Procedures For Navy

EKMS Tiers 2 & 3

NASPAXRIVINST 5100.35D – Safety and Occupational Health Manual

NASPAXRIVINST 12610.7H – Employee Reporting Procedures During Emergencies

NASPAXRIVINST 11240.20 Licensing of Motor Vehicle and Equipment Operators and the

NASPAXRIVINST 11240.20 Licensing of Motor Vehicle and Equipment Operators

NASPAXRIVINST 5100.12C Traffic Safety Program.

OPNAVINST 3440.17A – Navy Installation Emergency Management Program

NAVADMIN 259/23 SAAR – System Authorization Access Request (SAAR), November 2023

OPNAVINST 5239.1D- US Navy Cybersecurity Program

NASPAXRIV 5510.15Q- Base Access Regulation

SECNAVINST 5100.13E – Navy Tobacco Policy

SECNAV M-5510.30 – Personnel Security Program

SECNAV M-5510.36 – Information Security Program

SECNAVINST 5510.36- DoN Information Security Program (ISP) Regulation

OPNAVINST 5530.14E Navy Physical Security and Law Enforcement Program

NASPAXRIVINST 3440.17A- Installation Emergency Management Program

NASINST 5100.35C Occupational Safety and Health Manual

NASINST 11320.1N Fire Bill

NAVAIR Technical Manual 01-1A-505, Installation Practices, Aircraft Electric and Electronic

Wiring

INDUSTRY/ Other Documents

IPC-J-STD-001F – Requirements for Soldered Electrical and Electronic Assemblies

IPC-A-610F – Acceptability of Electronic Assemblies

IPC/WHMA-A-620C – Requirements and Acceptance for Cable and Wire Harness Assemblies

IPC-7111/7721C – Rework, Modification, and Repair of Electronic Assemblies

SAE-AS-50881D Wiring, Aerospace Vehicles

3 Requirements

3.1 General Requirements

3.1.1 Compatibility

The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government 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 XI

• Internet access

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 be capable of Internet and

LAN communications with the Government. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the

Government during working hours whether at Contractor work site or on travel.

3.1.2 Work Location and Facilities

3.1.2.1 Approximately 90 percent of the non-performance based level of effort work will be performed at the Government site inclusive of situational telework (NAWCAD, Patuxent River MD) and 10% of non-performance based level of work will be performed at the Contractor site inclusive of full time telework in accordance with

Contractor policy. Government onsite support does not include temporary and ad-hoc support performed away from DAiTA 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. The Government anticipates that approximately 25% of the labor for completion based delivery orders will be performed at the Government site and 75% of the labor for completion based delivery orders will be performed at the Contractor site.

3.1.2.2 As defined at the DO/TO level, the Contractor shall be required to 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 As defined at the order level, the Government may provide computers and associated network connectivity hardware required at the Contractor facility for access to the

Research, Development, Test and Evaluation (RDT&E), or other Government operated networks.

3.1.3 Contract Status Reporting

3.1.3.1 Program Financial Summary Report

The Contractor shall provide a monthly contract financial status report in accordance with the Contract

Data Requirement List (CDRL) A001.

3.1.3.2 Monthly Progress Report

The Contractor shall provide a monthly progress report in accordance with CDRL A0002.

3.1.3.3 Contractor Personnel Locator Report

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

A003.

3.1.3.4 Government Property Report

The Contractor shall provide a monthly Government Property Report in accordance with CDRL A004.

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 below). Some supported Government offices have flexibility to start as early as 0600 and end as late as 1800, Monday–Friday. 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 extended shifts or performance outside of normal work schedules, this also may include the requirement for staffing of multiple shifts. The following areas of performance are exceptions to the normal or CWS schedule:

a. Shipping and Receiving shall be supported Monday through Thursday 0700 to 1600 and

Fridays 0700 to 1500.

b. Visitor Control shall be provided Monday through Thursday 0630 – 1630 and Fridays

0630 – 1530.

The compressed work schedule (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 of time: 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.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.1.4.5 below, the

Contractor is permitted to observe Federal holidays IAW its corporate policy.

3.1.4.3 Overtime (OT)

Overtime as defined in this contract refers to hours worked by a Contractor employee in excess of the employee’s normal workweek. When support requirements outside of normal working hours occur, the Contractor shall ensure qualified personnel are available to support the requirements through the use of overtime. Overtime is authorized under this contract to the extent specified in individual task orders, provided COR approval is obtained in advance. The

COR may provide concurrence for overtime on a task, event, program, project, or general function basis. The total cost for overtime over the life of the contract cannot exceed the amount specified in clause 52.222-2 Payment for Overtime Premiums unless first approved in writing by the Chief of the Contracting Office (CCO).

3.1.4.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.5 General Facility Access

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.

While generally, Contractor personnel may not perform work on-site at a Government facility without oversight from Federal personnel, in very limited circumstances, work being performed by Contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by

Contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer (KO) must concur with any determination that work being performed by Contractor personnel is mission essential.

NASPAXRIVINST 12610.7H – Employee Reporting Procedures During Emergencies identifies procedures Government employees are to follow when an emergency condition is identified.

The Contractors shall follow the procedures as defined with the exception of 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.6 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 PWS 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 Other Direct Costs:

3.1.5.1 Travel: The Contractor shall be required to travel in support task orders issued under this contract. Travel will be allowable only when it is essential to the performance of the tasks detailed in the task order. All travel shall be approved and reimbursed in accordance with CTXT.232-9509

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

3.1.5.1.1 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. Expected travel locations include: NAS China Lake, CA;

NAS Pt. Mugu, CA; Edwards Air Force Base (AFB), CA; Eglin AFB, FL; Nellis AFB, NV;

Elmendorf AFB, AK; and Wright-Patterson AFB, OH. This list is not all-inclusive as locations may change over the life of the contract.

3.1.5.1.2 The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. 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.1.3 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. This authorization may only be granted if the aircraft, ship, or barge is a test asset.

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.

3.1.5.1.4 For OCONUS activities, the Contractor shall coordinate with the Government to ensure all documentation, approvals, access and other requirements authorizing personnel to enter the OCONUS operating location are met, including required personnel trainings, briefs, theater and country clearances, IAW Foreign Clearance Guide, Travel Orders, SPOT/Letter of

Authorization, CAC, Contractor Verification System approval, etc.

3.1.5.2 Material:

The Contractor shall obtain prior written approval by the COR /PCO. If the Contractor’s DO/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 (APR 2022). 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.6 Sub-Contractors

Provisions stated herein shall be clearly and effectively communicated to all Sub-Contractors providing support under this contract. All provisions of this PWS shall flow down to Sub-

Contractors providing support under this contract.

3.1.7 Management of Contractor Personnel

The Contractor shall supervise its workforce and control the methods by which required tasks are performed. The Contractor shall assign tasks to and prepare work schedules for individual

Contractor employees. 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. All direction and clarification on work contained in this SOW shall come from the COR and/or the NAWCAD

Contracts Office.

3.1.7.1: Personnel

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.2: Organization

The Contractor shall possess a flexible organization to provide a quick-reaction capability to meet urgent operational requirements, aircraft availability schedule changes and emergent requirements.

Personnel must be versatile and readily adaptive to support a broad range of aircraft test and evaluation support services and associated test and evaluation capability and technology development requirements.

3.1.7.3: Working with the Government

All Sub-Contractors and Sub-Contractor personnel working on this contract are viewed by the

Government as part of the Prime’s workforce. As such, there shall be no processes, requests, approvals, or other documents or procedures that are presented to the Government from the Sub-

Contractor. All Sub-Contractors shall conform to the same processes and documentation as the

Prime when interfacing with the Government.

3.1.8 Training

3.1.8.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/ACOR, Government task lead, Contractor task lead, etc.)

• Security

• Safety

• Ground Operating Procedures

3.1.8.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 PWS. 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 prior to the Contractor personnel reporting for duty except as identified in the specific labor category. Due to 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 so as to not impact workload due to missed days for training or expiring certifications.

3.1.8.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 Technical Point of Contact (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 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 in accordance with CTXT.242-9520 PROCEDURES

AND APPROVALS REQUIRED PRIOR TO INCURRING DIRECT MATERIAL COSTS (APR

2022).

3.1.8.4 Mandated Training

For performance at Government facilities, this contract requires Contractor personnel to complete training such as Anti-Terrorism and Active Shooter (as referenced in paragraph 3.2.6), and any required Operational Security (OPSEC) topics (as referenced in paragraph 3.2.5). In addition, during the course of 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.9 Non-Disclosure Agreements (NDAs)

In the performance of the contract, the Contractor may have access to non-public proprietary information. The Contractor shall require that any employee performing services under the contract execute a NDA satisfactory to the Contracting Officer or their designated representative.

The NDA shall acknowledge the Contractor and employees’ duties with respect to non-public information and promise to comply with those obligations. A copy of the executed NDAs shall be provided to the COR upon request.

3.1.10 Aircraft Facility Related Activities

3.1.10.1 Attachment C-1 GOP Guidance identifies the minimum GOPs that shall be completed prior to working on aircraft. GOPs shall be written as specific procedures as defined in NAVAIR

3710.1G – Contractor’s Flight and Ground Operations, that Contractor personnel shall follow. All site locations the GOPs apply shall be identified. If different procedures are needed at specific locations, these differences shall be addressed within the applicable GOPs or as separate GOPs.

(CDRL A005)

3.1.10.2 The Contractor is responsible for the GOPs training required for applicable Contractor personnel. Training and Certifications identified in approved GOPs that are not required otherwise by the contract (within the SOW and/or the Labor Category Qualifications) is the responsibility of the Contractor with respect to compliance (initial and recurring). Training in support of the

Contractor’s GOPs is reimbursable training. Non-labor associated costs of training are reimbursable as ODCs and shall require prior approval by the COR.

3.1.10.3 In the performance of the contract, the Contractor may have access to non-DAiTA Group controlled aircraft hangars, flight lines, maintenance areas, mobile and fixed ground control stations, or other facilities or spaces that operate under local Ground Operating Procedures. All

Contractor personnel shall follow the local instructions, policies, and procedures in regard to physical access, foreign object damage, tool control, and reporting requirements.

3.1.11 Transition Strategy

3.1.11.1 Transition 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 in transition activities to include, but not limited to, the following actions:

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

• Customer resourcing recommendations

• Generation of rough orders of magnitude of cost and schedule

• Identification of required Government Furnished Property and Information

• Performance Location requirements assessment and recommendations

• Identification and requirements definition of additional order level CDRLs

• Employee On-Boarding

3.1.11.2 Transition Out Strategy

The overall End of Contract strategy shall be built around maintaining the mission of the DAiTA

Group and IBST with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination, expiration of the contract or discontinuance of the placement of new orders, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with

CDRL A006.

• 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 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 Transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.1.11.3 Order Specific Close Out / Transition Out

Due to the IDIQ structure of this contract, order level close out or transition activities may occur throughout the lifecycle of the contract. The Contractor shall support the Government in close out / transition activities to include, but not limited to, the following actions:

• Personnel Resource Planning

• Deliverables Audit

• Audit and disposition/return of Government Furnished Property and Government

Furnished Information

• Performance Review and Lessons Learned

• Financial reconciliation

3.1.12 Safety and Health

The Contractor is directly responsible for complying with federal, state, and local occupational safety and health (OSHA) standards for its employees.

3.1.12.1 Safe Working Environment

The Contractor shall ensure OSHA regulations, as well as, specific site requirements are followed. The Contractor shall be responsible for all costs related to Personal Protective

Equipment (PPE), health testing (hearing, blood, etc), and Industrial Hygiene surveys for

Contractor work areas. The Contractor shall provide PPE for their personnel including safety shoes, safety glasses, goggles, cranials, hearing protection and other PPE as required based on individual tasking.

3.1.12.2 Hazardous Material (HAZMAT)

No HAZMAT shall be brought onto Government property that does not directly relate to the performance of this contract. The Government is not responsible for disposal of Contractor material brought onto the job site that is not required in the performance of this contract. The

Contractor shall obtain and maintain HAZMAT Coordinator Certification for employees designated to perform these tasks. The Contractor shall be responsible for meeting training requirements and costs associated with obtaining and maintaining HAZMAT Coordinator certifications throughout the PoP of this contract.

3.1.12.3 Incident Reporting

In the course of performing this work mishaps or incidents occasionally occur to equipment and personnel. The Contractor shall ensure its personnel is on the lookout for potential and realized incidents. Each person shall report any incidents they observe (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 in accordance with Accident/Incident

Report (CDRL A007).

3.1.13 Vehicles

The Contractor shall be required to operate Government owned or leased vehicles in performance of tasking in the SOW. Government-owned or leased vehicles that the Contractor may use include general purpose passenger carrying vehicles, special-purpose vehicles, tractor trailer, and range authorized vehicles. All vehicles shall be operated in accordance with

NASPAXRIVINST 11240.20 Licensing of Motor Vehicle and Equipment Operators and

NASPAXRIVINST 5100.12C Traffic Safety Program.

3.1.13.1 Vehicle Status

The DAiTA Group operates a fleet of Government owned and leased trucks. The Contractor shall monitor the state (e.g. status, scheduled maintenance, mileage, etc.) and readiness of the SD vehicles.

3.1.13.2 Vehicle Maintenance

When operating the vehicles, the Contractor shall monitor the requirements for normal operator maintenance such as checking and maintaining air pressure in tires and fluids such as engine oil, radiator coolant, power steering, and transmission prior to use. The Contractor shall report any damage observed on the vehicle/equipment and shall notify the Government TPOC/COR of any need for service or repair of the Government owned or leased vehicles.

3.1.13.3 Vehicle Damage

The Contractor shall report any known accidents involving the Government owned or leased vehicles to the Government TPOC/COR. If the Contractor is involved in an accident while operating a Government owned or leased vehicle, they shall notify the Government TPOC, the

Contracting Officer, and the COR within twenty-four (24) hours and shall provide an accident report within forty-eight (48) hours in accordance with Accident/Incident Report (CDRL A007).

3.1.13.4 Vehicle Operation

When operating the vehicle/equipment, the Contractor shall utilize the Government Fleet Card, the WEX Card, or the Fuel Farm Smart Key, depending upon the particular vehicle/equipment and whether the use is on base or off base, for fueling and maintenance services. Contractor use of the Fleet Card will be in accordance with the requirements and regulations contained in

NAVSUPINST 4200.98A. When operating the vehicle, the Contractor shall be liable for any moving or non-moving violations (e.g., speeding tickets, parking tickets, reckless driving). The

Contractor shall also be liable for any damage caused to the vehicle as a result of such violations, and any costs associated therewith. The Contractor shall be responsible for reimbursing the

Government for any unauthorized charges made by the Contractor, its employees, and sub-

Contractors on the Fleet Card.

3.1.14 Environmental Compliance

The Contractor shall operate in accordance with all Federal and local environmental regulations.

3.1.15 Government Property (GP)

Government property means all property owned or leased by the Government. GP includes

Contractor Acquired Property (CAP). The Contractor shall use GP, either furnished or acquired under this contract, only for performing on this contract, unless otherwise provided for in this contract or approved by the Contracting Officer.

3.2 Security

3.2.1 Citizenship Requirements

Only United States (U.S.) citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. 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 (specify contract number).

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

3.2.2 Investigative Requirements

A minimum of a SECRET security clearance is required for all positions on this contract. A complete ‘Day One’ staffing requirement will be provided by the Government NLT two (2) weeks after contract award. Positions required to possess TOP SECRET clearances with a current investigation or other special security requirements at the start of contract performance will be identified at the DO/TO level.

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 performance of this contract up to and including TOP SECRET/Sensitive Compartmented Information with a safeguarding level of None. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with National Industrial

Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part

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

The Contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information; Covered Defense Information). 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 TPOC/COR of this contract for approval.

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

reference Section 3.2.13.

3.2.3 Common Access Card (CAC)/PKI, SAAR-N

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

3.2.3.2 CAC/Local Badges

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

Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site following completion of the contract, relocation or termination of an employee, or upon request from the COR. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract.

3.2.3.3 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.3.4 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 Information Security

The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and CUI and to control distribution of CUI

IAW the National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NIPSOM Rule, and SECNAV M-5510.36B – Information

Security Program. If the work is performed at the Government’s facility, the Contractor shall comply with instructions/guidance required by that facility.

Information at the TS/SCI level will be protected in accordance with DoDI 5200.01 DoD

Information Security Program and Protection of Sensitive Compartmented Information (SCI).

3.2.4.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. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW the National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, SECNAV M-5510.35B – Information

Security Program, and program Security Classification Guidance. Any product containing

Covered Defense Information shall be assigned and marked accordingly a distribution statement

(distribution statements B through F) using the criteria set forth in DODI 5230.24 (Distribution

Statements on Technical Documents); and have this statement displayed per DODI 5230.24, Enclosure 3.

3.2.4.2 Public Release

No information pertaining to 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 to the COR for initial approval and awareness. Upon initial approval, the Contractor shall submit proposed public releases for approval prior to release through the NAWCAD

Procuring Contracting Officer, and through;

Public Affairs Office

NAVAIR

navairpao@us.navy.mil

301-757-1487

3.2.4.3 Loss, Compromise, or Spillage

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 twenty-four (24) hours of the incident occurring.

3.2.4.4 Compliance to 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 SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with 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 identify 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 utilize acceptable multi-factor authentication.

For legacy systems and systems that cannot support this requirement, such as

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 identify practices that the Contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its Sub-Contractors, suppliers, or vendors based on need-to-know principles;

(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 a SSP and

POAM); and,

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 POAM 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 Operational Security (OPSEC)

For work performed at the Contractor facility, the Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any Sub-

Contractor during performance of the contract. The Contractor shall be responsible for the Sub-https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program

Contractor implementation of the OPSEC requirements. This program may include Information

Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

a) Assignment of responsibility for OPSEC direction and implementation.

b) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

c) Establishment of OPSEC education and awareness training.

d) Provisions for management, annual review, and evaluation of OPSEC programs.

e) Flow down of OPSEC requirements to Sub-Contractors when applicable.

While performing aboard NAVAIR or NAVAIR sites, the Contractor shall comply with facility

OPSEC program instructions and contribute to organization-level OPSEC efforts. Include

OPSEC as part of its ongoing security awareness program and take all required Agency training.

Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and

Contractor in support of the mission.

The Contractor shall develop, implement, and maintain an OPSEC plan (CDRL A007) 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 is responsible for ensuring

SubContractor implementation of the OPSEC program requirements for this contract.

3.2.6 Anti-Terrorism Force Protection and Emergency Management

The work performed on this contract is not Emergency Essential IAW OPNAVINST 3440.17A –

Navy Installation Emergency Management Program and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all

Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives.