Atch_01_SOW RSNF MH60 TOFT Upgrade R1 26Feb25.pdf

CUI

SOW 240042

26 Feb 2025

STATEMENT OF WORK

FOR

ROYAL SAUDI NAVAL FORCES (RSNF)

MH-60R TRAINING SYSTEM FOLLOW ON SUPPORT (TSFOS)

TACTICAL OPERATIONAL FLIGHT TRAINER (TOFT) UPGRADE

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

12211 SCIENCE DRIVE

ORLANDO, FL 32826-3275

APPROVED BY: DATE: 26 Feb 2025

Daniel P. Loth Program Manager International Programs Saudi MH-60R

NAWCTSD

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors CTI, Export Controlled, determined on 27 March 2024. Other requests must be referred to the Commanding Officer, Naval Air Systems Command (PMA299), 47123 Buse Road, Patuxent River, MD 20670

CONDITIONS FOR FOREIGN USE: This information is furnished upon the condition that it or knowledge of its possession will not be disclosed to another nation, and that it will not be used for other than the military purpose for which it is being provided without specific authority from the U.S. Department of the Navy; that individual or corporate proprietary rights contained within, whether patented or not, will be respected; that the information will be provided the same degree of security afforded it by the U.S. Department of Defense. Regardless of any declassification markings, this information may not be downgraded or declassified by a foreign recipient without the written approval of the originating U.S. agency.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801- 4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

DESTRUCTION NOTICE - CUI must be reviewed in accordance with DoD Instruction 5230.09 and DoD Instruction

5200.48 (March 6, 2020) prior to destruction. Destroy UNCLASSIFIED, CUI, and Classified Documents in accordance to DoD Manual 5200.01, Volume 3 (Change 3 July 28, 2020), Enclosure 3, Paragraph 17-19.

I

CUI

Revision History Revision

Date Description Affected

Pages Approval

06-Feb-25 Original 26-Feb-25 Rev 1 Administrative Created

Revision page Grammatical correction Address contractors Questions

5, 26, 35 Daniel P. Loth

II

CUI

Table of Contents Section Title Page

1 INTRODUCTION

1.1 Scope

1.2 Definitions

2 APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Non-Government Documents

3 REQUIREMENTS

3.1 General

3.1.1 Project Support

Project Planning Project Assessment and Control Integrated Program Management Report Risk Management Configuration Management Change Management Quality Assurance (QA) USG use of Contractor’s Test Tools & Equipment Management & Logistics IPT Engineering IPT Meetings Provisioning Items Selection Conference (PISC) Integrated Logistics Support Verification (ILSV) Conference

3.1.2 System Safety

3.1.3 Security

Operations Security (OPSEC) Cybersecurity Cybersecurity Assess Only Support Initial Cybersecurity RMF Meeting Cybersecurity Compliance Personnel Security International Traffic in Arms Regulation Unclassified Contractor-Operated Network Security – Safeguarding of CUI Transmission of CUI Cyber Incident and Compromise Reporting Protection of Critical Program Information (CPI) RSNF MH-60R Training Site Access

3.2 RSNF MH-60R TOFT Upgrade Detailed Tasks

3.2.1 System Configuration Upgrade

3.2.2 Technology Refresh

3.2.3 System Engineering Tasks and Assessments

Planning and Technical Assessments Technical Assessments Exit Criteria

III

Technical Assessment Agenda, Minutes, and Presentation Materials

Contractor Planning Assessment (CPA) CPA Entry Criteria CPA Exit Criteria

Requirements Analysis Traceability Functional Baseline Technical Assessment (FBTA)

FBTA Entry Criteria System Architectural Design / Allocated Baseline

Software Architectural Design Product Drawings, Models, and Associated Lists

System Detailed Design / Initial Product Baseline Software Product Detailed Design

Product Baseline Technical Assessment (PBTA) PBTA Entry Criteria

System Implementation Software Development

System Integration Test Procedures (TP) Software Integration

Software Version Description (SVD) Cold Start Process

Software System and Subsystem Assessment (SSSA) Media and Storage Devices Software License(s) Software Media Identification

Source Code Management System Verification Testing

Regression Testing Pre-Modification Inspection Contractor Verification Baselines

Contractor Software Product Baseline Installation DT-C1 – Contractor System Verification Verification Readiness Technical Assessment (VRTA)

VRTA Entry Criteria USG Verification Baselines

Physical Configuration Audit (PCA) USG Software Product Baseline Installation (SPBI)

IT-C1 (USG System Verification) IT-C1 exit criteria

Training System Installation Buy Through the Prime (BTTP) Parts Management

IV

Obsolescence Management Trainer Device Excess Trainer Equipment Disposal Packing, Handling, Shipping and Transportation (PHST) Terms and conditions for PHST can be found on Section D

(DTXT.247-9510) of the contract. Reliability and Maintainability (R&M) Engineering

Failure Reporting, Analysis, and Corrective Action System

(FRACAS)

R&M Predictions Inventory Management Training System Sparing Product Data (TSSPD) Bill of Materials (BOM) for Logistics and Supply Chain Risk

Management Technical Data Package

Commercial Technical Documentation (TD) TD Validation/Verification and In-Process Reviews

TD Validation TD Verification

Instructor/Operator Training Course Maintenance Training Course

3.2.4 Outside the Continental United States (OCONUS) Travel

STATEMENT OF WORK

FOR

ROYAL SAUDI NAVAL FORCES (RSNF)

MH-60R TRAINING SYSTEM FOLLOW ON SUPPORT (TSFOS)

TACTICAL OPERATIONAL FLIGHT TRAINER (TOFT) UPGRADE

1 INTRODUCTION

The Naval Air Warfare Center Training Systems Division (NAWCTSD), Orlando, FL will conduct a technology refresh, correction of deficiencies, and Systems Configuration 20 (SC20) and 24 (SC24) upgrade to the RSNF MH-60R Tactical Operational Flight Trainer (TOFT), located in the Kingdom of Saudi Arabia (KSA). The initial effort will upgrade the trainer to SC24, perform a technology refresh of identified obsolete subsystems and establish a functional baseline by conducting a Pre-Modification Inspection (PMI). The PMI will identify and develop a Test Inspection Report (TIR). The TIR will be used to develop an Engineering Change Proposal (ECP) for updating previously unidentified obsolete Hardware/Software (HW/SW) components. This effort will include updates to all existing or creation of missing technical manuals, support equipment, tools, testing devices, and spares as required.

1.1 Scope

This Statement of Work (SOW) establishes the contractor’s tasks for the design, fabrication, delivery, logistic support, installation, verification and testing, of the MH60R TOFT upgrade from system configuration (SC) 18 to SC 24.04 and training system technical refresh for the RSNF. The RSNF MH-60R TOFT upgrade is being procured under Foreign Military Sales (FMS) case SR-P-GBX. The RSNF MH-60R TOFT is located at Al Jubail Naval Air Base, in

KSA.

1.2 Definitions

The following definitions apply to this SOW:

a. Access means the USG is provided the ability to inspect, read, and analyze the contractor’s artifacts created under and for the duration of this contract.

b. Action Item is a tasking assigned to a responsible party with a suspense date, made in the form of a Request for Actions (RFA), Request for Information (RFI), and Action to Minutes (ATM).

c. Action to Minutes (ATM) is an action item that is not required to close the conference and technical review and is often programmatic in nature.

d. Allocated Baseline describes the functional and interface characteristics for the training system elements (allocated and derived from the higher-level product structure hierarchy) and the verification required, demonstrating achievement of those specified characteristics. The allocated baseline for each lower-level system element (hardware and software) is established and put under configuration control.

This process is repeated for each system element and culminates in the complete allocated baseline.

e. Artifacts are the data and information items generated and captured by the contractor as part of performing their internal work processes. Artifacts can exist in whatever form and/or format that is dictated by the contractor’s internal work processes.

f. Baseline is defined in IEEE 828-2012 section 2.1.

g. Bill of Materials (BOM) for Logistics and Supply Chain Risk Management should apply to a singular device and will provide Diminishing Manufacturing Sources and Material Shortages (DMSMS) management essential information that enables the identification, forecasting, mitigation, and management of Hardware and Software obsolescence as a part of the Department of Defense (DoD) Program Manager’s Total System Life Cycle Management responsibilities.

h. Buy through the Prime, when required and requested, is the Provisioning Item Order (PIO) to procure a supply support package, after the design baseline is finalized (to the maximum extent practical).

i. Commercially Available Off-The-Shelf (COTS) is defined in Federal Acquisition Regulations (FAR) 2.101

j. Computational Subsystem, also referred to as Computer Subsystem is a programmable electronic device that can store, retrieve, and perform prescribed mathematical and logical operations.

k. Computational System, is one or more computational subsystems, their peripheral devices, and network equipment working synergistically to satisfy a set of requirements.

l. Computer Software is defined as computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae, and related material that would enable the software to be reproduced, recreated, or recompiled

m. Database is defined in IEEE 24765-2010 section 3.743.

n. Derived Requirement is defined in IEEE 24765-2010 section 3.796.

o. Existing Software is defined in IEEE 24765-2010 section 3.1081.

p. Final Product Baseline is the realization of the Initial Product Baseline, and includes the Government verified, and configuration-controlled hardware and software. The final product baseline forms the basis for delivery, operation, and sustainment.

q. Foreign Person means any natural person who is not lawful admitted for permanent residence as defined by 8 U.S.C. 1101(a)(20) or who is not a protected individual as defined by 8 U.S.C. 1324b(a)(3). It also means any foreign corporation, business association, partnership, trust, society or any other entity or group that is not incorporated or organized to do business in the United States, as well as international organizations, foreign governments and any agency or subdivision of foreign governments (e.g., diplomatic missions).

r. Functional Baseline defines the training system’s performance (in terms of functionality, interfaces, safety, stability, interoperability, operations, behaviors, limitations, quality, reliability, man-machine interfaces, regulatory requirements, and other characteristics); and the verification methods used to determine that the specified characteristics are achieved. The Functional Baseline is backward traceable to the Requirements Traceability Matrix (RTM) requirements, and forward traceable to the Allocated Baseline through use of the Requirement Traceability and Verification Matrix (RTVM)

s. Functional Baseline Technical Assessment (FBTA) is a formal; USG chaired Engineering review that determines the contractor has completed the system requirements definition activities and tasks, and documented the Functional

Baseline to a degree that the project has an acceptable level of schedule and performance risk to proceed to the next phase of the development life cycle.

t. Initial Product Baseline, also referred to as detailed design, is the Government accepted, and configuration-controlled build-to design documentation for the hardware (product, process, material specifications, engineering drawings, and other related data) and software unit design documentation. The Initial Product Baseline is backward traceable to the Allocated Baseline, and forward traceable to the Final Product Baseline through use of the RTVM.

u. Initial Support Kit (ISK) includes: the initial spares (repairable items) and repair parts that are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility; spares that support vendor hardware, utilized by the device, which can be procured on the open market or from established sources and for which the prime contractor is not the design activity;

items that are not an integral part of the end item, but are required to inspect, test, calibrate, service, repair, or overhaul the end item, which are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility; and items required for support of the trainer system (excluding common hand tools), which can be procured on the open market or from established sources and for which the prime contractor is not the design activity.

v. Integrated Logistics Support Verification (ILSV) is a series of USG led events to be conducted at the device site near the end of a contract period of performance.

These events will ensure that all logistics products will adequately support the delivered training system into the sustainment phase and meet the requirements of the contract. The ILSV will include a detailed, on-site audit of engineering drawings, a verification of all technical manuals, an inventory of all hardware, software and spared items, and a final facility inspection.

w. Integrated Product Team (IPT) meetings are collaborative and interactive working group environments where contractor and government personnel discuss the relevant technical, programmatic, and logistics subjects by sharing information and data; track and resolve issues and actions; and other items as defined within each IPT's charter. The contractor and USG collaborative IPT is independent of the contractor’s internal teaming and project organizational structure.

x. Integrated Test – Milestone C (IT-C1) is the identified Naval Standard title for the first test event.

y. Interface Requirement is defined in IEEE 24765-2010 section 3.1484.

z. Job Control Language is defined in IEEE 24765 section 3.1543.

aa. Life Cycle is defined in IEEE 24765-2010 section 3.1587.

bb. Major Functional Modification, in the context of software units, is where the scope of the unit’s functionality and the underlying logic, algorithms, and data elements are altered to the extent beyond that of a Minor Functional Modification.

cc. Minor Functional Modification, in the context of software units, is where the scope of the unit’s functionality and the underlying logic, algorithms, and data elements are relatively unchanged (not greater than 20 percent of the unit’s lines of code and data elements are added, deleted, or modified).

dd. Modified Software is a Reused software unit, which with minor functional modification, can be used to satisfy a set of TOFT requirements.

ee. NMCI (Navy/Marine Corps Intranet) Connected Computers are composed of both laptops and desktops using Microsoft Windows 10 as the operating system, with Internet Explorer 11 as the default browser. Most NMCI computers also have Mozilla Firefox and Google Chrome browsers available. The full Microsoft Office 2016 suite and Adobe Acrobat Reader are also installed. The NCMI provides access to the internet for FTP (port 20), HTTP (port 80), and HTTPS (port 443).

ff. Noncommercial Software also referred to as “other than commercial computer software” is defined IAW DFARS 252.227-7014.

gg. Nondevelopmental Item (NDI) is defined in FAR 2.101.

hh. Part I* Specification Discrepancy Report (SDR) jeopardizes safety and/or results in safety hazard(s) to personnel and/or equipment. Testing is halted until the safety hazard is resolved, as determined by the government.

ii. Part I SDR prevents the accomplishment of system verification, or jeopardizes security, life cycle support, or other critical requirements, as determined by the government. The Part I SDR results in significant degradation in technical performance, or supportability. Acceptable workarounds to this SDR may not be available or may have negative consequences, as determined by the government.

jj. Part II SDR affects the accomplishment of system verification, life cycle support, or other critical requirements, as determined by the Government. The Part II SDR results in significant degradation in technical performance, or reliability and maintainability; but a work-around solution is available and potentially acceptable, as determined by the Government.

kk. Part III SDR reduces technical performance or supportability but can be tolerated with little or no impact on system verification or performance.

ll. Physical Configuration Audit (PCA) is a non-functional, formal examination performed IAW the Government-accepted TP to demonstrate that the trainer as-built design satisfies the Specification requirements and that the deliverable hardware and software documentation accurately reflects the configuration items.

mm. Product Baseline Technical Assessment (PBTA) is a formal; USG chaired Engineering review that determines the contractor has completed the preliminary and detailed design activities and tasks and documented the Allocated and Initial Product Baselines to a degree that the project has an acceptable level of schedule and performance risk to precede into the next phase of the development life cycle.

nn. Qualified Personnel are contractor supplied personnel who will operate the TOFT during testing events defined here-in. These personnel will have practical experience operating the MH-60R aircraft and its systems. Additionally, they will have a level of proficiency whereby they can operate the RSNF TOFT and its systems efficiently, accurately, and without the use of manuals, instructions, or other supplemental information.

oo. Regression Testing is defined in IEEE 24765 section 3.2455.

pp. Request for Action (RFA) is a critical action item must be closed in order to close the associated conference or technical review (see NAVAIR Instruction 4355.19E).

qq. Request for Information (RFI) is an action item to only provide information and data in support of the conference and technical review. Closure of a RFI is not required to close the conference and technical review (see NAVAIR Instruction 4355.19E).

rr. Ready for Training (RFT) is when the training system is unconditionally accepted, operations and maintenance training has been completed, and all discrepancies have been addressed by the contractor, and approved by the Government.

ss. Reused Software is an existing software unit, component or item, whose functions and underlying code and data elements are used as-is, to satisfy a set of TOFT requirements.

tt. Software Release is the distribution of the latest version of a software application to be installed in the training device(s).

uu. Source Code, also referred to as Source, is defined in IEEE 24765 section 3.2817

vv. Specification Discrepancy Report (SDR) is used to identify, classify, and track a TOFT technical issue that does not meet the TOFT requirements.

ww. Technical Assistance Agreement (TAA) is an agreement (e.g., contract) for the performance of a defense service(s) or the disclosure of technical data, as opposed to an agreement granting a right or license to manufacture defense articles.

Assembly of defense articles is included under this section, provided production rights or manufacturing know-how are not conveyed. Should such rights be transferred, ITAR part §120.21 is applicable.

xx. Technical Documentation (TD) Terminology regarding required submissions are as follows:

1) Draft Submissions – Refers to the documentation prior to the contractor’s preliminary submission. The draft submissions will be delivered for the in-process reviews and will be used to evaluate the contractor’s progress, review for technical accuracy and adequacy, and to assess compliance with contractually-cited specifications.

2) Preliminary Submission – Refers to the Preliminary Submission by the contractor of the documentation in its entirety. The Preliminary Submission Electronic Technical Manual (ETM) is intended for use during Technical Documentation Verification and for training purposes at the device site(s) pending receipt and distribution of the Final ETM. Preliminary ETMs are to be complete and validated prior to delivery.

3) Final Submission – Refers to the final submission of the documentation by the contractor. The Final ETM is the final document acceptable for reproduction and publication as an authenticated ETM. All necessary changes resulting from hardware testing and Technical Documentation Verification are incorporated in the Final ETM.

yy. Validation - Validation is the process by which the contractor tests Technical Data for technical accuracy and adequacy, comprehensibility, and usability prior to the delivery to the Government. The validation process and procedures are provided by the contractor in accordance with a contractor developed validation plan.

Validation is normally conducted at the contractor’s site.

zz. Verification - Verification is the final QA iteration by the Government for acceptance of the Technical Data (TD) during which TD is tested to determine its adequacy and operational suitability for operation and maintenance of equipment or systems using target audience personnel. Verification is planned and scheduled by the Government and contractor involvement is at the discretion of the Government.

aaa. Verification Readiness Technical Assessment (VRTA) is a formal, USG chaired Engineering review that determines the contractor has completed and documented the results of their system verification activities and tasks, and that the project has an acceptable level of schedule and performance risk to proceed into the next phase of the development life cycle.

2 APPLICABLE DOCUMENTS

The following documents form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW take precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

2.1 Government Documents

The following specifications, standards, and handbooks of the exact revision listed below form a part of this SOW to the extent specified herein. Copies of the listed documents from the

RSNF MH-60R TACTICAL OPERATIONAL FLIGHT TRAINER (TOFT), DEVICE 2F245-

01 training system will be provided as GFI.

SPECIFICATIONS:

Naval Air Systems Command (NAVAIR), MH-60 Multi-Mission Helicopters Program Office, PMA-299

SPEC NUMBER 240041 - Requirements Traceability Matrix for RSNF MH-

60R Tactical Operational Flight Trainer (TOFT) dated 25 Sep 2024

OTHER PUBLICATIONS:

Code of Federal Regulations (CFR) (Information available at https://www.osha.gov)

29 CFR 1910.147

- The Control of Hazardous Energy (Lockout/Tagout)

Department of Defense (DoD) Handbooks (Information available at http://assistdocs.com)

MIL-HDBK-217F, Notice 2 - Reliability Prediction of Electronic Equipment MIL-HDBK-472, Notice 1 - Maintainability Prediction

DoD Instructions (Information available at http://www.dtic.mil) https://www.osha.gov/ http://assistdocs.com/ http://www.dtic.mil/

DoDI 5200.39 - Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E), dated 25 May 2015

DoD and Department of the Navy (DoN) Security and Cybersecurity Instructions, Manuals, Policy Memos, and Guidance Documents

DoDI 8510.01 - Risk Management Framework (RMF) for DoD

Information Technology, dated 27 September 2018 DoDI 5200.48 - Controlled Unclassified Information (CUI), dated 06

March 2020 NIST SP 800-53 - National Institute of Standards and Technology

(NIST) Special Publication (SP) 800-53, Revision 5 “Security and Privacy Controls for Federal Information Systems and Organizations,” current edition, dated 20 September 2022

CNSSI 1253 - Committee on National Security Systems Instruction (CNSSI) 1253, “Security Categorization and Control Selection for National Security Systems,” dated 27 March 2014

2.2 Non-Government Documents

GEIA-HB-0007-B - Logistics Product Data Handbook

GEIA-STD-0007-B - Logistics Product Data

INDUSTRY STANDARDS:

ANSI/Institute of Electrical and Electronics Engineers (IEEE) (Information available at (www.ieee.org)

IEEE 12207-2008,

2nd Edition

- Systems and Software Engineering – Software Life Cycle Processes

IEEE 15288-2015 - Systems and Software Engineering – System Life Cycle Processes

IEEE 29148-2018 - Systems and Software Engineering – Life Cycle Processes - Requirements Engineering http://www.ieee.org/

3 REQUIREMENTS

The contractor shall make available and accessible to the United States Government (USG); to view, inspect, analyze, and read (on a not to interfere basis); while physically present within the contractor’s facility, and as specified in SOW paragraph 3.1.1.4 (b), and 3.1.1.5 (b); the artifacts generated by the contractor while performing their work processes and the activity and task requirements specified in this SOW, through successful completion of the TOFT upgrade.

a. The USG will coordinate with the contractor, the facility visits to assess artifacts.

b. The contractor shall permit the USG to capture, document, and keep; notes, results, summaries, and findings pertaining to the viewing, inspection, analyzing, and reading of the artifacts.

3.1 General

The contractor shall perform the engineering, technical, logistics and management tasks to plan, document, modify, build, integrate, test, validate, install, and deliver the MH-60 TOFT trainer that meets the performance requirements specified by NAWCTSD Specifications 240041.

3.1.1 Project Support

Project Planning The contractor shall perform the project planning activities and tasks specified in IEEE 15288- 2015 section 6.3.1.3, and IEEE 12207-2008 section 7.1.1.3.1.

Project Assessment and Control The contractor shall perform the project assessment and control activities and tasks as specified in IEEE 15288-2015-2015 section 6.3.2.3.

Integrated Program Management Report The contractor shall prepare the Integrated Program Management Report (IPMR) (Integrated Master Schedule (IMS)) IAW CDRL (B004).

Risk Management

The contractor shall establish and maintain a risk management program to identify risks related to the project. The contractor shall identify and track all risks and corrective actions required to mitigate the risks. The contractor shall define and implement a risk assessment methodology that includes not only an understanding of cost, schedule, and performance impacts on risk areas, but also provides a periodic reassessment of these impacts on risk areas. The contractor shall update, maintain, and execute program metrics to monitor issues and to determine the likelihood of risks occurring. The contractor shall ensure that the risk management process is utilized to manage risks across all facets of the contract, including subcontractor activities.

a. The contractor shall perform the risk management activities and tasks as specified in IEEE 15288-2015 section 6.3.4.3.

b. The contractor shall answer questions; and provide information and data related to project cost, schedule, and performance risks discussed during the Technical Interchange Meetings (TIM) meetings.

Configuration Management The contractor shall:

a. Perform the configuration management (CM) activities and tasks as specified in IEEE 15288-2015 section 6.3.5.3.

b. Make their CM artifacts accessible to the USG for review.

c. Only make changes to USG approved baselines (Functional, Allocated, Initial

Product, Testing, and Final Product) after receiving USG authorization.

d. Maintain configuration control of the USG approved TOFT baseline through successful completion of the upgrade.

e. Use Engineering Change Proposals (ECPs) and Request for Variances (RFVs) to request changes to a Government approved baseline.

Change Management

The contractor shall:

a. Use an Engineering Change Proposal (ECP) to obtain Government approval on changes to the accepted product baseline and the associated configuration documentation.

b. Use a Request for Variance (RFV) to obtain Government approval on products that do not conform to contract requirements.

c. Prepare an ECP IAW the CDRL (A00A).

d. Prepare an RFV IAW the CDRL (A00B).

Quality Assurance (QA)

The contractor shall:

a. Perform the QA activities and tasks as specified in IEEE 15288-2015 section

6.3.8.3.

b. Make their QA activity and task artifacts accessible to the USG from a NAWCTSD

NMCI connected computer.

USG use of Contractor’s Test Tools & Equipment

During USG testing events (IT-C1) and the Physical Configuration Audit (PCA), the contractor shall make available for USG use, the test tools, equipment and any special tools required to execute the Acceptance Test Procedures and perform the PCA.

The contractor shall perform the calibrations and verify the accuracy and condition of the test tools & equipment.

During USG testing events and the ILSV, the contractor shall provide the personnel needed to operate the testing tools and training equipment.

Management & Logistics IPT

The purpose of the combined Management and Logistics IPT is to review and discuss the status of the management and logistics program under development by the contractor and its subcontractors and any technical and administrative issues. The combined

Management and Logistics IPT shall identify and resolve potential problem areas that could affect the timely planning, implementation, and verification of the support program. All ILS elements shall be presented to the IPT. Specialists from Management and the various ILS disciplines, including facilities engineering, shall attend the IPT meetings as necessary to discuss specific aspects of the management and logistic programs.

a. The contractor shall provide the resources and personnel; participate in, and manage the Management and Logistics IPT.

b. The contractor shall resource the IPT to occur no less than monthly, commencing 14 calendar days after Contractor Planning Assessment (CPA) through final acceptance of the RSNF MH60R TOFT training device.

c. As part of Program Management, the contractor shall be ready to present the information and discuss no less than the following project related topics:

1) Up-to-date Organizational Chart

2) Current Point of Contact (POC) List

3) Current Integrated Master Schedule (IMS)

4) Action Items (including RFAs, RFIs, and ATMs)

5) Risks (Potential, Identified, Status, Assessed, Mitigations)

6) Issues (realized risks)

a. Project Status

i. Accomplishments

ii. Working on

iii. Challenges

iv. Efficiencies

v. Potential ECPs

d. Subcontractor Activities and Status

1) Discrepancy List and Status

e. Travel Planning and Scheduling

i. Upcoming events and task with 30, 60 and 90 day look ahead

i. Logistics

ii. CDRL Status

f. The contractor shall resource IPT participation to account for variable activity levels throughout the project lifecycle; during high levels of activity, IPTs may require more frequent meetings, and less frequently during lower levels of activity.

g. The contractor shall assign contractor leads to each functional area for the purpose of coordinating with their USG counterparts.

h. The contractor shall generate IPT informational artifacts IAW CDRLs listed below, no later than 24 hours before the meeting via email to the IPT members to support collaboration.

1) B002 - DI-ADMN-81505 Report, Record of Meeting/Minutes

2) B004 - DI-MGMT-81861B Integrated Program Management

Report (IPMR) IMS

3) B006 - DI-MGMT-81928 Contractors Progress and Status

Management Report

i. The contractor shall generate informational artifacts such as meeting minutes within

48 hours after the meeting via email to the IPT members to support collaboration.

Engineering IPT Meetings The contractor shall resource the Engineering IPT to occur no less than bi-weekly, commencing 7 days after Contractor Planning Assessment (CPA) through final acceptance of the RSNF MH60R TOFT training device.

a. The contractor shall include within the Engineering IPT, the engineering, visual, cyber and testing specialties personnel associated with the TOFT development efforts.

b. The contractor shall present the information and discuss no less than the following project related topics during the Engineering IPT:

1) Review, status, and discussion of contractor activities and task artifacts

2) System engineering process and life-cycle management activities and tasks

3) System Engineering issues and actions

4) Verification testing activities, planning, issues, discrepancies, corrective actions

5) Technical assessments collaboration planning and actions

c. The contractor shall conduct not less than five Visual IPT meetings to review the TOFT Visual Database elements, features, and capabilities.

1) The contractor shall prepare the Visual Database Design Document IAW CDRL (A008).

d. The contractor shall capture requirements derived during the Visual IPTs and incorporate them into the Functional Baseline.

Provisioning Items Selection Conference (PISC)

The contractor shall conduct and participate in the PISC within 30 calendar days of the completion of PBTA.

a. The contractor shall provide the TSSPD during the PISC in order to facilitate discussion on the range and depth for the recommended spares.

b. During the PISC, the contractor shall demonstrate the approach to developing and populating the data elements of the TSSPD.

c. The contractor shall include a representation of the top-down breakdown structure of all training system components reduced to the line replaceable unit (LRU).

d. The contractor shall deliver prior to the PISC, the Training System Sparing Product Data (TSSPD) and Bill of Materials (BOM) for Logistics and Supply Chain Risk Management for Government review and acceptance. The TSSPD and BOM shall contain sufficient data to assist the Government in selecting an Initial Support Kit (ISK). The TSSPD and BOM shall be delivered IAW CDRLs (C001, C002).

e. The contractor shall submit prior to the PISC, the PISC presentation briefing materials and agenda for Government review and acceptance. The PISC presentation briefing materials and agenda shall be delivered IAW CDRLs (B003 and B001).

f. The contractor shall capture PISC action items and assign suspense dates for closure of each action item.

g. The contractor shall submit after the PISC, the PISC final presentation briefing materials and minutes for Government review and acceptance. The PISC presentation briefing materials and minutes shall be delivered IAW CDRLs (B003 and B002).

Integrated Logistics Support Verification (ILSV) Conference The conference shall commence in conjunction with the final PCA. The Contractor shall participate in support of the ILSV conference, and the Government will lead and conduct the ILSV. The ILSV shall include a physical inventory of all deliverable Logistics’ products, including verification of technical manuals and training documentation, training equipment hardware, drawings, tools, test and support equipment, and spare parts procured (See 1.2, v). The contractor shall support by assisting during the USG verification process by demonstrating adequacy of Logistics’ products, and by providing all necessary printed documents in support of the ILSV conference to include:

Inventory records (TDICL/R) Technical Product Data, including technical Manuals (BOM, PEDDAL, O&M, PMS, TSSD, COTS supplemental data)

Spares list (TSSPD) The USG will verify during the ILSV conference, the readiness and completeness of the device support system including the logistics support package, technical data, engineering data, storage of support resources and the inventory control system. The contractor shall record all findings and initiate corrective actions to resolve all deficiencies. The Training Device Inventory Checklist/Record (TDICL/R) CDRL D001 shall be used as a master control document for all inventoried items.

a. The contractor shall conduct the Instructor/Operator Training Course at the training facility in KSA after completion of ILSV and prior to RFT.

b. The contractor shall conduct the Maintenance Training Course at the training facility in KSA after completion of ILSV and prior to RFT.

3.1.2 System Safety

The contractor shall perform system safety activities and tasks to identify, capture, analyze, and resolve (eliminate or reduce the associated risk to a level acceptable to the USG) safety hazards to personnel, facilities, and equipment. The contractor shall notify the USG of identified operational safety concerns, risk, or issues.

3.1.3 Security

Operations Security (OPSEC) The contractor shall perform Operations Security (OPSEC) to protect controlled unclassified information (CUI), activities, equipment, and material used and developed by the contractor on this program IAW DoDI 5200.48.

a. The contractor shall safeguard unclassified DoD information from loss, misuse, and unauthorized access to, and modification of the information.

b. The contractor shall designate and identify to the USG the person responsible for OPSEC management and implementation on this program.

c. The contractor shall have documented OPSEC procedures and plans applied to this program to identify vulnerabilities and apply applicable countermeasures.

d. The contractor shall make program related OPSEC artifacts available to the USG.

e. The contractor shall provide OPSEC education and awareness training to project personnel.

f. The contractor shall perform management annual review, and evaluation of the OPSEC program.

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

h. Contractor personnel shall require access to classified information in performance of this contract up to and including Secret, with a safeguarding level of Secret. 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, 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.

Cybersecurity The trainer shall meet the Cybersecurity criteria specified in DoDI 8510.01 Risk Management Framework (RMF) security control set as defined in NIST SP 800-53 for a CNSSI 1253 Security Categorization of an NSS as (Confidentiality= Moderate), (Integrity=Low), (Availability=Low) with a Classified Overlay.

Cybersecurity Assess Only Support The contractor shall support the DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), Change 1 dated September 27, 2018, as outlined in the Naval Air Systems Command (NAWC) Training Systems Domain Guide, Version 1.0 dated September 2016.

Initial Cybersecurity RMF Meeting

The contractor shall conduct an initial Cybersecurity RMF meeting with the NAWCTSD FMS Information System Security Officer (ISSO) prior to SRR. The contractor shall complete the actions below in support of this meeting:

a. Present changes in the security architecture to the ISSO for approval.

b. Present the following as meeting objectives:

1) High level program description, including the following:

a) Scope

b) Team members

2) Identification of each non-cyber enabled subsystems with supporting rationale

3) Preliminary network diagram and boundary to include:

a) Network devices

b) External connections

c) Non-cyber enabled and Cybersecurity-enabled delineations

4) Present and establish the RMF security controls and sub controls

5) Propose and establish the RMF security control implementation plan

Cybersecurity Compliance

Contractor personnel shall:

Implement DCBP-1 (Best Security Practices) control on the RSNF tech refresh components.

Implement ECVP-1 (Virus Protection) control on the RSNF tech refresh components.

Implement the Security Technical Implementation Guides (STIG) on the RSNF tech refresh components.

Prepare the RMF Package IAW the CDRL A00Q.

Personnel Security

Contractor personnel shall:

a. Undergo the company internal vetting process prior to gaining access to CUI.

b. The contractor shall use the Employment Eligibility Verification Program (E-

Verify) IAW FAR 52.222-54.

c. The contractor shall report to the NAWCTSD Security Office, any information pertaining to program personnel that would affect their security clearances and ability to work on the program.

d. When an employee no longer supports this program, the contractor shall terminate the employee’s access to and possession of program related CUI.

e. The contractor shall ensure that terminated employees having worked this program receive a debriefing on the need to maintain confidentiality of program related CUI.

International Traffic in Arms Regulation Contractor personnel shall:

a. Ensure that commercial exports of defense articles and defense services are consistent with U.S. national security and foreign policy objectives per 22 U.S.C.

2778 of the Arms Export Control Act (AECA) and the International Traffic in Arms Regulations (ITAR, 22 CFR 120-130) ITAR requirements.

b. Restrict foreign persons from access to CUI, sensitive information, defense articles, defense services, and technical data, as defined in the ITAR, Part 120, without proper issuance of an export license from the USG authority.

c. Ensure the transfer of program related technical data and equipment outside of the United States is in compliance, and within the scope of the approved US State Department, Defense Technology Security Assistance (DTSA), Technical Assistance Agreements (TAA).

Unclassified Contractor-Operated Network Security – Safeguarding of CUI The contractor shall manage and maintain contractor-operated unclassified IT network assets used to process USG CUI for this program.

Transmission of CUI

The contractor personnel shall:

a. Use approved encryption to safeguard the electronic transmission of all CUI;

b. Ensure that when transmitting CUI over non- secure e-mail (e.g. not connected to the Navy Marine Corps Intranet through Broadband Unclassified Remote Access System / Virtual Private network), those transmissions are encrypted using Department of Defense Public Key Infrastructure (PKI), or an approved DoD External Certificate Authority, in accordance with Public Key Infrastructure & Public Key Enabling, DoDI 8520.02; and

c. Use SAFE (https://safe.apps.mil) as an alternative way to send encrypted files.

Cyber Incident and Compromise Reporting The contractor shall report to the USG, cyber incidents related to CUI stored on or transiting contractor IT IAW FAR 252.204-7012.

Protection of Critical Program Information (CPI) The contractor shall identify candidate CPI and Resident CPI which requires protection IAW DoDI 5200.39.

a. The Contractor shall ensure that Program Protection Awareness (PPA) training is provided to the personnel working this program who have access to CPI; and prior to performing any work involving CPI.

b. The contractor shall provide annual PPA refresher training to the applicable personnel through successful completion of IT-C1 and DD-250 signing.

RSNF MH-60R Training Site Access Contractor personnel shall:

a. Coordinate with, and obtain from the installation site, the necessary personnel security clearances, access passes, and equipment property passes.

b. Immediately report to the installation site POC, and USG, any accidents, damages, or incidents with security or safety implications.

c. Conduct all tasks associated with the system upgrade and technology refresh at the training site from 0700-1900 daily, 7 days a week, with no holiday restrictions. If additional working hours are required the contractor shall coordinate with the USG on a case by case basis. The regular Jubail Naval Airport work-week is Sunday to Thursday.

3.2 RSNF MH-60R TOFT Upgrade Detailed Tasks

The contractor shall complete on-site modifications to the RSNF MH-60R TOFT that meets the performance requirements specified in the Requirements Traceability Matrix (RTM) Specification 240041, without degrading the current performance of the training system and minimizing the trainer down-time.

3.2.1 System Configuration Upgrade

The contractor shall upgrade the RSNF MH-60R TOFT to SC 24.04 in accordance with the Requirements Traceability Matrix (RTM) Specification 240041. The contractor shall include all updates to the related requirements documents, specifications, technical data, training materials, user/maintenance and configuration documentation and deliver all spare parts associated with the modification which meets the performance requirements specified in the RTM Specification 240041.

3.2.2 Technology Refresh

a. The contractor shall design, document, develop, inspect, procure, fabricate, integrate, test, verify, validate, deliver, and install the hardware and software that meets the performance requirements specified in the Requirements Traceability Matrix (RTM) Specification 240041.

b. The contractor shall upgrade the following subsystems for the RSNF MH-60R

TOFT:

SUBSYSTEM

Requirements Traceability Matrix Reference

Architecture Design Document Reference

Video distribution 2.1.2.22 & 2.1.9 3.7.18

Aural cueing and communication 2.1.3.113, 2.1.2.13, 2.1.2.14 & 2.1.17 3.6.7 & 3.7.10

Domain controller 2.1.24 & 2.1.17 3.7.3

Intelligent Input Output 2.1.17 3.7.14 & 3.6.15.1.10

Image generators 2.1.21.37 & 2.1.17 3.6.9 & 3.7.16

Visual display system and projectors 2.1.21 & 2.1.17 3.6.13 & 3.7.17

Visual Database 2.1.21 3.6.9

SIM Host 2.1.17 3.6.3 & 3.7.3

Instructor Operation 2.1.2, 2.1.9 & 2.1.17 3.6.2 & 3.7.3 Semi-automated forces

(SAF) 2.1.21.3 & 2.1.17 3.6.12

Acoustic Simulator 2.1.8.10 & 2.1.17 3.6.6 & 3.7.8 High level architecture

(HLA) 2.1.17 3.6.3 & 3.7.3

Radar 2.1.6.20, 2.1.8.8 & 2.1.17 3.7.6 Multispectral Targeting System (MTS)/Forward Looking Infrared (FLIR)

2.1.6.18 & 2.1.17 3.6.11 & 3.7.7

Control loading 2.1.17 3.6.8 & 3.7.5

Debrief 2.1.9.3, 2.1.9.4, 2.1.9.5 & 2.1.17 1.5.4, 3.6.2 & 3.7.11

Software Engineering Environment (SEE) 2.1.17.34 & 2.1.17 3.3

c. The contractor shall replace the current Semi-Automated Forces and integrate with the Next Generation Threat System (NGTS).

d. The contractor shall replace the current acoustic simulator and integrate the Common Acoustics Synthetic Environment (CASE) C2PO (Coherent 2D Propagation Ocean).

e. The contractor shall reuse the collimating mirrors and Back Projection Screen

(BPS).

f. The contractor shall conduct an analysis during PMI and submit a Test inspection report (TIR) of concurrency requirements and identified obsolete equipment.

g. The contractor shall submit a proposal for additional repairs/upgrades in the form of an ECP.

3.2.3 System Engineering Tasks and Assessments

Planning and Technical Assessments The contractor shall host the Planning and Technical Assessments (PTAs) at their facilities.

a. The contractor shall organize, conduct, attend, and participate in the PTAs as specified in this SOW.

b. The USG will chair the PTAs.

c. The contractor shall use the NAVAIR 4355/4 RFA form to capture RFAs, RFIs, and ATMs.

d. The contractor shall present and explain at the PTAs, the rationales, and methodologies used in determining the project’s assumptions, decisions, conclusions, recommendations, and alternatives in the performance of the activities and tasks required by the contract.

e. The contractor shall have key project personnel available to attend and participate at the PTAs.

f. The contractor shall have key subcontractor’s personnel available to participate in the PTAs.

g. The contractor shall make facilities available during PTAs for USG only meetings and discussions.

h. The contractor shall capture RFAs, RFIs, and ATMs.

Technical Assessments Exit Criteria The contractor shall consider the technical assessments closed when the following items are completed:

a. The associated PTA Briefing Materials IAW CDRL (B003) has been presented to, and discussed with the USG;

b. The associated PTA Minutes CDRL IAW (B002) has been accepted by the USG;

c. The contractor assigned RFIs and ATMs have been assigned to a responsible person with a response date; and

d. The contractor assigned RFAs have been closed by the USG.

Technical Assessment Agenda, Minutes, and Presentation Materials The contractor shall:

a. Conduct and participate in conferences, reviews and audits;

b. Prepare the Planning and Technical Assessment Agenda IAW CDRL (B001);

c. Prepare the Planning and Technical Assessment Minutes IAW CDRL (B002); and

d. Prepare the Planning and Technical Assessment Briefing Materials IAW CDRL

(B003).

Contractor Planning Assessment (CPA) The purpose of this conference shall be to establish the framework of the contractor and Government interaction during performance of the contract. At the CPA, the contractor shall present an Integrated Master Schedule (IMS) showing the critical milestones and supporting events, including logistics, leading to these milestones. The contractor shall make available to the Government, the completed program specific planning documents presented and discussed during the CPA, such as the Quality Assurance task. The CPA shall include a presentation and discussion of information and data relating to the following:

a. Introduction and contract overview;

b. Discussion and clarification of specification and SOW requirements;

c. Presentation of a complete, accurate, and realistic IMS and schedule with status;

d. Identification of the critical paths and next nearest driving paths within the IMS and schedule;

e. CDRL delivery schedule and status;

f. Program…