DVES_PWS_10_May_18.pdf

DRAFT

AIR FORCE LIFE CYCLE MANAGEMENT CENTER ROBINS AIR FORCE BASE, GEORGIA

31098-1670

PERFORMANCE-BASED WORK STATEMENT

(PWS) FOR

Degraded Visual Environment System (DVES)

FD2060-19-30143

PR Number

10 May 2018

Prepared by:

AFLCMC/WIUBB

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government Agencies and their Contractors (administrative or Operational Use; 1 May 2018). Other requests for this document shall be referred to AFLCMC/WIUBB, Robins AFB, GA 31098.

PR: FD2060-19-30143 PWS Revision: 0 2

Table of Contents

Section Title Page Number

SECTION 1 Description of Services

SECTION 2 Services Summary

SECTION 3 Technical Requirements

SECTION 4 General Information SECTION 5 CDRLs

SECTION 6 Appendices .......................................................... Error! Bookmark not defined.

PR: FD2060-19-30143 PWS Revision: 0 3

1.0 Description of Services

The purpose of this effort is to perform the activities and tasks required to complete the system design, development, integration and test of the Degraded Visual Environment System (DVES) on the HH-60G aircraft. The objectives for the prime Contractor, as part of the Contractor’s overall responsibilities, shall be captured in a detailed Integrated Master Plan addressing program elements and an Integrated Master Schedule (IMS) addressing all requirements and deliverables in this PWS.

1.1 Objective(s)

This Performance-based Work Statement (PWS) describes the service required to modify the HH- 60G, managed by the Special Operations Forces/Personnel Recovery and Rotary Division AFLCMC/WIUBB, with a system to address the operational limitations posed by loss of visual situational awareness in aircraft-induced degraded visual environments (brownout/whiteout). This PWS describes the requirement to design, develop, qualify, certify, test, install, and logistically support the HH-60G DVES in accordance with (IAW) the HH-60G DVES Systems Requirements Document (SRD) (located in Appendix B). In the event of a conflict between the HH-60G DVES SRD and this PWS, this PWS shall take precedence. The Contractor shall ensure system performance, cybersecurity, and airworthiness requirements are met and verified for the DVES modification. The Contractor shall develop, adhere, and maintain an Integrated Master Schedule (IMS) and provide Monthly Status Reports (MSRs) promptly. The Contractor shall develop and maintain a Technical Data Package (TDP) that accurately depicts the DVES system. The Contractor shall generate and deliver DVES Technical Orders (TOs) IAW the Contract Data Requirements Lists (CDRLs). The Contractor shall conduct Systems Integration Lab (SIL) test prior to ground and flight testing. The Contractor shall design the DVES for permanent installation on all configurations of the HH-60G aircraft, including Block 152 and Block 162 aircraft. The Contractor shall install and integrate the DVES on a minimum of two aircraft and demonstrate acceptable system integration.

1.2 Benefit to the United States Air Force (USAF)

This acquisition will benefit the USAF by providing additional safety-of-flight features to the HH- 60G. This effort will reduce the number of non-combat losses, both material and personnel. This acquisition will provide the USAF with more capability in order to facilitate optimal mission effectiveness for combat search and rescue (CSAR).

1.3 Background

The HH-60G is a highly modified version of the Sikorsky UH-60 Black Hawk that is used for personnel recovery. The primary mission of the HH-60G is to recover downed aircrew members and other isolated personnel in austere and unfriendly territory. The USAF has a mission-critical need to modify the HH-60G with a new DVE capability. This capability will increase the level of situational awareness of the pilots, while simultaneously decreasing their workload and the risk of mishap during Degraded Visual Environment (DVE) operations. The DVES mitigates the aircraft-induced DVE, which will increase the margin of safety for the aircrew.

2.0 Services Summary

PR: FD2060-19-30143 PWS Revision: 0 4

Performance Objective PWS Ref. Performance Threshold

Develop, adhere, and maintain an

Integrated Master Schedule (IMS)

3.12.1, 3.12.4, 3.12.5

- The Contractor shall stay within ten (10) business days of the schedule critical path set forth in the IMS unless re-baselined.

- The IMS shall have no more than three minor discrepancies.

Provide MSRs promptly

3.12.1, 3.12.4, 3.12.5

- A draft MSR shall be submitted on the 15th of every month.

If the 15th falls on a holiday/weekend, the report is due the next business day. The initial report is due the 15th of the second month after contract award.

Develop and provide Agenda, Presentation Materials, and

Minutes

3.13, 3.13.1, 3.13.2, 3.13.3, 3.13.4, 3.13.5, 3.13.6, 3.13.7, 3.13.8, 3.13.9, 3.13.10, 3.13.11, 3.13.12, 3.13.13

- The Contractor shall provide draft presentation materials and agenda ten (10) working days prior to scheduled presentations.

- The Contractor shall provide minutes of the reviews, TIMs, and meetings five (5) working days after the event.

Data Deliverables Ref DD Form 1423s and PWS paragraphs

- The Contractor shall deliver all data complete and on time.

- The Contractor shall deliver the required data deliverables IAW schedule requirements.

Enterprise-wide Contractor Manpower Reporting

Application (eCMRA)

4.15 - The Contractor shall annually report manpower performed for this contract IAW paragraph 4.15.

3.0 Technical Requirements

3.1 Place and Period of Performance (PoP)

The PoP for the basic contract will be twenty-four (24) months. The contract will also include three (3), one-year options for DVES kit production. These services will be performed primarily at the Contractor’s facility with periodic trips to the HH-60G Extended Integration Support Environment (EISE) lab at Robins AFB, and HH-60G Combined Test Force (CTF) at Nellis AFB.

Additional testing may be required at locations advantageous to the Government and with appropriate testing conditions. The Contractor shall also be required to travel to various locations in support of program activities during the PoP.

PR: FD2060-19-30143 PWS Revision: 0 5

3.2 Systems Engineering

The Contractor shall perform all design, development, qualification, testing, maintenance, operations, training, and logistics tasks to meet the requirements of the DVES as detailed in this PWS and in the System Requirements Document (SRD) (located in Appendix B). In addition, the Contractor shall manage all sub-Contractors and supplier tasks to ensure the requirements of the SRD are met. The DVES shall meet the requirements of the DVES SRD including, but not limited to: environmental, EMI/EMC, maintainability, human factors, functional, logistics, training, documentation, installation/integration, and commonality

3.2.1 System Performance Requirements

An Off-the-Shelf (OTS) solution is required for this effort; however, non-recurring engineering effort is required to ensure compatibility with the electrical, mechanical, and software systems of the aircraft. The system shall meet the technical requirements as detailed in the SRD attached in (Appendix B).

3.2.2 Configuration Management

The Contractor shall maintain a Configuration Management process using best practices considering guidance provided in MIL-HDBK-61A Configuration Management Guidance, EIA- 649 National Consensus Standard for Configuration Management, and ISO 12207 Standard for Information Technology - Software Life Cycle Processes, to include subsets. The Contractor shall be responsible for documenting and maintaining configuration control for any hardware or software affected by the modification. Configuration Control is defined as any change to Form, Fit, Function, or Interface of hardware or software. The Contractor shall support the government Military Flight Release (MFR) and safety review board processes with requested data and participation if requested.

(DI-ADMN-81249B, CDRL A001; DI-ADMN-81250B, CDRL A002)

3.2.3 Diminishing Manufacturing Sources and Material Shortages (DMSMS) The Contractor shall implement a proactive DMSMS management program. The Contractor shall prepare and submit to the Government support data for forecasting DMSMS at all program reviews. The Contractor shall submit a separate DMSMS report for each Contractor developed Line Replaceable Unit (LRU) in the Group “B” kit. The Contractor shall submit a cumulative DMSMS report for all Group “A” kits.

(DI-PSSS-81656B/, CDRL A003)

3.3 Maintenance Support

The Contractor shall be responsible for all repair/maintenance of the HH-60G DVES system and Contractor Furnished Equipment (CFE) support equipment, beginning with DVES modification effort, up to the PoP completion, as appropriate. The Contractor shall create/initiate Air Force Technical Order (AFTO) Forms 95 for all newly installed time-tracked components on the aircraft.

The Contractor shall update/complete the aircraft forms (AFTO 781A through AFTO 781K) during/following completion of the modification. In support of Government Developmental Test and Evaluation (DT&E) the Contractor shall provide DVE maintenance support for laboratory, ground, and flight operations.

PR: FD2060-19-30143 PWS Revision: 0 6

(DI-MISC-80711A, CDRL A004)

3.4 Support Equipment (SE)

The Contractor shall procure sufficient support equipment to support DVES ground and flight testing as required. The Contractor shall perform an analysis sufficient to determine both new and modified SE requirements and formulate Support Equipment Recommendation Data (SERD) for specific items of peculiar SE, including modified hand tools. Contractor shall maximize the use of existing SE. Contractor shall notify the Government of the requirement for support or test equipment as soon as such determination is made and shall get United States Government (USG) approval prior to purchase of common/peculiar tools, support or test equipment. The SE selection criteria shall follow the precedence stated below in descending order of importance:

1) Existing government inventory

2) Off-the-shelf Commercial equipment

3) Modification of existing government inventory

4) Modification of commercial equipment

5) New development

(DI-MISC-80711A, CDRL A004)

3.5 Familiarization Source Data

The Contractor shall generate and deliver HH-60G DVES integrator unique items source data for use in developing/updating Aircrew/Maintenance differences Training. The Contractor shall develop HH-60G DVES integrator unique items source data, including processes specified on drawings, to meet Operations, Maintenance, Installations, and Training (OMIT) requirements.

The source data shall include unlimited data rights.

(DI-TMSS-81354, CDRL A005)

3.6 Orientation and Familiarization

The Contractor shall provide training material to familiarize aircrews and maintainers with the modification’s functionality and maintenance. The Contractor shall conduct training sessions for aircrews and maintainers at the HH-60G Prototype and Verification Installation location(s). The training material and instruction shall instruct the aircrews and maintainers on DVES usage and functionality. The training shall enable maintainers to be self-sufficient in properly troubleshooting the DVES system as installed on the HH-60G. Overall, the training shall enable aircrews and maintainers for the HH-60G to properly operate and maintain the installed system.

The training shall be conducted at a location advantageous to the Government.

(DI-ILSS-80872, CDRL A006)

3.7 Software

The Contractor shall develop Operational Flight Program (OFP) for the DVES to meet performance and mission requirements specified in the SRD located in Appendix B. The Contractor shall deliver both source and executable code of the finalized OFP after Government Developmental Test and Evaluation along with updated documentation for the purpose of Government organic sustainment of the OFP. The OFP shall be capable of being loaded to the

PR: FD2060-19-30143 PWS Revision: 0 7

DVES in methods specified in Appendix B. All software developed under this contract shall include unlimited data rights and shall not be marked proprietary.

3.7.1 Software Transition and Use

The Government defines acceptance criteria for software releases built by the Contractor.

Software baseline release procedures including provisions for Government ownership of the source code and object listings must be available for delivery at the request of the Government.

Any product developed under this order will be the property of the Government and must not be exported to outside entities without written Government approval.

3.7.2 Software Development Plan (SDP)

The Contractor shall develop, maintain, and deliver a SDP that describes the Contractor’s plan for modifying the DVES software.

(DI-IPSC-81427B, CDRL A007)

3.7.3 Computer Programming Manual (CPM)

The Contractor shall develop, maintain, and deliver to the Government a CPM to provide the information needed by the Government to understand how to program the DVES.

(DI-IPSC-81447A, CDRL A009)

3.7.4 Software Requirements Specification (SRS)

The Contractor shall develop, maintain, and deliver to the Government an SRS that specifies the requirements for the DVES software and the methods to be used to ensure that each requirement is met.

(DI-IPSC-81433A, CDRL A00A)

3.7.5 Software Transition Plan (STrP)

The Contractor shall develop, maintain, and deliver to the Government a STrP. The STrP identifies the hardware, software, and other resources needed for the life cycle support of deliverable software. The Contractor shall tailor the Data Item Description (DID) to take into consideration the existing Government facilities and resources in the development of the STrP.

(DI-IPSC-81429A, CDRL A00B)

3.7.6 Software Design Description (SDD)

The Contractor shall develop, maintain, and deliver to the Government a SDD that describes the design of the DVES software to include design decisions, architectural design, and the detailed design needed to implement the software. The Interface Design Description (IDD) may supplement the SDD for external interfaces.

(DI-IPSC-81435A, CDRL A00F)

3.7.7 Software Product Specification (SPS)

The Contractor shall develop, maintain, and deliver to the Government a SPS to include all source code, executables, and build procedures for the DVES software.

(DI-IPSC-81441A, CDRL A00G)

PR: FD2060-19-30143 PWS Revision: 0 8

3.7.8 Software Version Description (SVD)

The Contractor shall develop, maintain, and deliver to the Government a SVD that identifies and describes the software version consisting of all DVES Computer Software Configuration Items (CSCIs). The SVD will be used to release, track, and control software versions.

(DI-IPSC-81442A, CDRL A00H)

3.7.9 Firmware Support Manual (FSM)

The Contractor shall develop, maintain, and deliver to the Government a FSM that provides the information needed to program and reprogram firmware devices within the DVES.

(DI-IPSC-81448B, CDRL A00J)

3.7.10 Software Test Plan (STP)

The Contractor shall develop, maintain, and deliver to Government an STP that outlines the plans for qualification testing CSCIs. The plan shall describe the software test environment to be used for testing, the tests to be performed, and proposed schedules for test activities.

(DI-IPSC-81438A, CDRL A00K)

3.7.11 Software Test Description (STD)

The Contractor shall develop, maintain, and deliver to the Government test procedures used for qualification testing of the DVES OFP.

(DI-IPSC-81439A, CDRL A00L)

3.7.12 Software Test Report (STR)

The Contractor shall develop, maintain, and deliver to the Government a STR for all software testing events. The STR shall provide a record of the testing performed on a CSCI or subsystem.

(DI-IPSC-81440A, CDRL A00M)

3.7.13 Software User Manual (SUM)

If applicable, the Contractor shall develop, maintain, and deliver to the Government a SUM that provides the information needed to operate the DVES software.

(DI-IPSC-81443A, CDRL A00N)

3.7.14 Software Architecture Document (SAD)

The Contractor shall develop, maintain, and deliver to the Government a SAD that outlines the software architecture, viewpoints and design decisions as they relate to the DVES software and its subsystems.

(DI-SESS-82043, CDRL A00P)

3.7.15 Integrated Development Environment (IDE)

The Contractor shall design, manufacture, and deliver to the Government a desktop IDE capable of providing organic software sustainment of the DVES OFP for the HH-60G. The IDE shall include the ability to edit OFP source code and to generate a binary file capable of native execution on the DVES. This shall include, but not be limited to, licensed copies of the source code editor(s), compiler(s), linker(s), assembler(s), and any other software tools required to generate the binary file. Any external hardware, outside a Microsoft Windows desktop, shall be kept to a minimum.

PR: FD2060-19-30143 PWS Revision: 0 9

3.7.15.1 IDE Acceptance Test Plan (ATP)

The Contractor shall deliver an IDE draft ATP.

(DI-QCIC-80553A, CDRL A00S)

3.7.15.2 IDE Data Deliverables

The Contractor shall develop, maintain, and deliver sufficient documentation to the Government to allow organic sustainment of the IDE. At a minimum, these deliverable documents are to include an SPS and SUM.

(DI-IPSC-81441A, CDRL A00G; DI-IPSC-81443A, CDRL A00N)

3.7.16 IDE Data Rights and Licensing

All hardware and software developed for the IDE shall include unlimited data rights and shall not be marked proprietary. All software and hardware specifically developed for this task shall be delivered to the Government at the IDE acceptance test. All source code, executables, software licenses, configuration files, make files, and build scripts developed or purchased for this task shall be delivered to the Government at the IDE acceptance test. The Contractor shall provide ten (10) properly licensed sets of OFP maintenance software and hardware.

3.8 Engineering Analysis

3.8.1 System Engineering Master Plan (SEMP)

The Contractor shall generate, maintain, implement, and deliver a SEMP. The Contractor shall use the System Engineering Plan (SEP) to document the overarching systems engineering approach to management of the user’s requirements and the risk evaluation and decision-making process used by the Contractor when resolving technical questions. The SEMP will also document the Contractor’s systems engineering methodology including configuration management, requirements verification and validation methodology, architecture and design processes, software and hardware development methodology (including configuration control), the build management process used, and the testing processes to be used. The SEMP will describe interface development and management processes, and how data conversion management will be performed and managed. Finally, the SEMP will describe how the Contractor will support production and fielding through coordination and acceptance.

(DI-SESS-81785A, CDRL A00T)

3.8.2 Materials and Processes

The Contractor shall use materials and processes in the design of suitable quality and type so as to ensure the other requirements in the specification are not jeopardized. Materials shall be selected and specified in accordance with Metallic Materials Properties Development and Standardization (MMPDS). Materials not referenced in MMPDS may be used with Government concurrence only.

3.8.3 Crash Load Factors

The minimum ultimate crash load factors shall be in accordance with JSSG-2010-7 and SES- 700700.

PR: FD2060-19-30143 PWS Revision: 0 10

3.8.4 Factor of Safety

Unless otherwise provided, a factor of safety of 1.5 must be used. Margin of safety shall always be positive.

3.8.5 Strength and Deformation

The system structure must be able to support limit loads without detrimental permanent deformation.

3.8.6 Human Factors

The Contractor shall apply the principles, criteria and procedures of human factors engineering to the design of the system IAW the guidelines established in MIL-STD-1472G, Human Engineering.

The system shall not affect crew egress or survivor insertion/extraction operations.

3.8.6.1 Pilot Vehicle Interface (PVI) and Maintainer Vehicle Interface (MVI) Analyses The Contractor shall (using the SRD and CONOPS documentation as resources) perform PVI and MVI analyses in concert with and in support of the SSDD, SDD, and SUM, with the equivalent deliverable schedules.

3.8.6.2 Human Engineering Systems Analysis Report (HESAR)

The Contractor shall deliver a HESAR documenting human factors task analyses, the appropriateness and feasibility of system functions and roles allocated to operators and maintainers, descriptions and documentation of software user interface designs, and design descriptions of automation features, including design rationale and intended effect on operator workload and performance.

(DI-HFAC-80745C, CDRL A00R)

3.8.6.3 Human Engineering Design Approach Document– Maintainer (HEDAD-M) The Contractor shall document all maintenance tasks and equipment interfaces with maintainers through a HEDAD-M to be submitted in draft format 30 days prior to CDR.

(DI-HFAC-80747C, A014).

3.8.7 Weight and Balance

The Contractor shall evaluate any changes to the baseline HH-60G configuration(s) for effects to weight and balance and provide a report documenting this data in accordance with Technical Order (TO) 1H-60(H)G-5. Final aircraft weight and balance shall be within the constraints defined in TO 1H-60(H)G-5, Basic Weight Checklist and Loading Data, USAF Series HH-60G Helicopters given at task level. The Government will provide baseline data as required.

(DI-MGMT-81501A, CDRL A00U)

3.8.8 Electrical Power Distribution

The Contractor shall conduct an Electrical Load Analysis (ELA) and provide a report. The load analysis shall meet the requirements of MIL-E-7016F. The Government will provide baseline data as required. The initial ELA shall be delivered 30 days prior to Preliminary Design Review (PDR).

The final ELA shall be delivered 30 days prior to Critical Design Review (CDR).

(DI-MISC-80711A, CDRL A004)

PR: FD2060-19-30143 PWS Revision: 0 11

3.8.9 Technical Report-Studies/Services

The Contractor shall provide requested technical reports, studies, and services as required in support of the DVES.

(DI-MISC-80711A, CDRL A004)

3.8.10 Airworthiness

The Contractor shall develop a design and perform an analysis and test of the affected area, addressing at a minimum: the aircraft structure, wiring, and installation changes. The Contractor shall utilize an approach to airworthiness certification of the final aircraft configuration that complies with the intent of AFPD 62-6. The Contractor shall develop a Modified/Tailored Airworthiness Certification Criteria (MACC/TACC) in accordance with MIL-HDBK-516C to identify the specific certification criteria that applies to the modified aircraft and MACC/TACC compliance report to describe verification data and activities. The Contractor shall deliver the draft Airworthiness Verification Plans and Airworthiness Substantiation Report that documents the certification process. The Contractor shall provide any supporting data required for flight clearance authority to the Government.

In the event that the Government determines there are non-compliances against the approved certification criteria pertaining to the Contractor’s system integration effort, the Contractor shall support the associated System Safety Risk Assessment (SSRA) to enable the Government to mitigate the risk associated with each non-compliance. Draft airworthiness documents shall be delivered 30 days prior to PDR, and final airworthiness documents shall be delivered 30 days after

CDR.

(DI-MISC-80711A, CDRL A004)

Note: MACC will be in revision until final approval/signature is obtained from the Operational, Safety, Suitability & Effectiveness (OSS&E) authority.

3.8.11 Cybersecurity/Information Assurance (IA)

The Contractor shall identify, design, manage, implement, and verify cybersecurity requirements.

The Contractor shall perform analyses and verifications and deliver necessary artifacts, source data, and verification results to the Government in order to obtain Authorization for the system to operate IAW DoDI 8500.01 and 8510.01.

The Contractor shall ensure security requirements are traced to specifications and architectures that comprise the functional and allocated baselines. The Contractor shall integrate cybersecurity considerations into program systems engineering processes, especially risk management. The Contractor shall integrate cybersecurity into all SIL testing. The Contractor shall consider Cyber resiliency (Anticipate, Withstand, Recover, Evolve) into the system design, development, and integration of system components as to deny adversaries the ability to degrade, modify, or destroy DVES functionality and capability.

The Contractor shall develop and deliver draft documentation to support the following: Penetration Test Report, IA Design Review Information Package, IA Test Plan, IA Test Report, RMF Comprehensive Package with Artifacts, Software Assurance Evaluation Report, Software

PR: FD2060-19-30143 PWS Revision: 0 12

Assurance Case, Vulnerability Assessment Report, Security Test Plan, and Security Test Report.

These deliverables shall meet the requirements of the DVES SRD. Draft documents shall be submitted 30 days prior to PDR, and final documents shall be delivered 30 days after CDR.

(DI-MISC-80711A, CDRL A004; DI-MGMT-81845, CDRL A00S; DI-MGMT-81844, CDRL

A00W; DI-MGMT-81843, CDRL A00X; DI-NDTI-81351, CDRL A00Y)

3.8.11.1 Cybersecurity In Technical Data

The contractor shall ensure that training materials, technical manuals, and other technical data developed for the program address any cybersecurity controls (e.g., administrative, procedural, inherited) or requirements that affect system operation, maintenance, repair, or other support activities.

3.8.11.2 Cybersecurity Requirements

The Contractor shall identify, manage, and verify cybersecurity requirements in the same manner as all other system requirements. The Contractor shall refine the system specifications by translating and deriving cybersecurity specifications from the system cybersecurity requirements, both explicitly specified and implicitly derived. The Contractor shall map and allocate cybersecurity requirements to the hardware and software design for the system. See Committee on National Security Systems Instruction (CNSSI) No. 1253. Refined specifications, with mapped requirements, due as a draft 30 days prior to PDR and final at CDR.

(DI-MISC-80711A, CDRL A004)

3.8.11.3 System Architecture Analysis Report

The Contractor shall prepare a system-level architecture analysis detailing system architecture, data types, hardware, software, interfaces, peripherals, networks, access, and incident handling capabilities. Analysis shall include interconnection diagrams, data type descriptions, data flow diagrams, hardware and software lists. Analysis shall include identification of internal configuration management, quality assurance, security, and systems engineering processes applied during system design, build, test, and manufacture. Analysis shall be in a format complementary to the Architecture Analysis Report (AAR). A draft shall be submitted 30 days prior to PDR, and the final document shall be delivered 30 days after CDR.

(DI-MISC-80711A, CDRL A004)

3.8.11.4 Security Assessment Plan (SAP)

The contractor shall provide a Risk Management Framework (RMF) package including Committee on National Security Systems Instruction (CNSSI) No. 1253 requirements in support of an Interim Authority to Test (IATT). The SAP shall identify means to assess the system against the cybersecurity requirements, determining the extent to which the controls are effecting, operating as intended, and producing the desired outcome. In addition, SAP shall specify test platforms, equipment, and interfaces. To the extent possible, the contractor shall integrate test and evaluation (T&E) of cybersecurity requirements into the overall T&E process, to include component level testing performed by suppliers. AAR Architecture Analysis: The contractor shall prepare a system-level architecture analysis detailing system architecture, data types, hardware, software, interfaces, peripherals, networks, access, and incident handling capabilities. Analysis shall include

PR: FD2060-19-30143 PWS Revision: 0 13 interconnection diagrams, data type descriptions, data flow diagrams, hardware and software lists.

SAP due as a draft 30 days prior to TRR and final at TRR.

(DI-MISC-80711A, CDRL A004)

3.8.11.5 Security Assessment Report (SAR)

The contractor shall verify the implementation of cybersecurity controls and submit the verification results in a Security Assessment Report (SAR). SAR shall map to procedures outlined in SAP. Report due as a draft at TRR and final 30 days after completion of final assessment. A draft shall be submitted 30 days prior to PDR, and the final document shall be delivered 30 days after CDR. This document may contain sensitive or classified information and must be delivered using proper procedures.

(DI-MISC-80711A, CDRL A004)

3.8.11.6 System Authorization Boundary

The Contractor shall prepare a system-level authorization boundary report describing the PIT boundary, interconnections, data types, and data transfers in a format complementary to the aircraft Architecture Analysis Report (AAR). A draft shall be submitted 30 days prior to PDR, and the final document shall be delivered 30 days after CDR.

(DI-MISC-80711A, CDRL A0004)

3.8.11.7 Cybersecurity Schedule

The Contractor shall include cybersecurity Rick Management Framework (RMF) activities and events on the Integrated Master Schedule (IMS).

(DI-MGMT-81861A, CDRL A01D)

3.8.11.8 Cybersecurity Workforce

The Contractor shall implement DoD Directive 8140.1 and DoD 8570.1-M for requirements and processes necessary for information management and cybersecurity controls (e.g., administrative, procedural, inherited) or requirements that affect system operation, maintenance, repair, or other support activities.

3.8.12 Safety

The safety criteria and considerations set forth in MIL-STD-882E, System Safety shall be used in establishing system safety design features. Warning notices shall be provided where applicable for high voltage electrical sources, noise, explosive devices, and electromagnetic radiation.

3.8.12.1 Laser Safety

The Contractor shall ensure the laser design meets the requirements of MIL-STD-1425A. The provisions of AFI 48-139 apply, to include identification of the Nominal Ocular Hazard Distance (NOHD), Nominal Skin Hazard Distance (NHSD), coordination with the 711HPW/RHDO on a Laser Hazard Evaluation (LHE), and USAF Laser System Safety Review Board (LSSRB) approval of the laser prior to fielding. The Contractor shall develop and deliver a Hazard Management Plan (HMP) detailing the procedures for safe operation of DVES with respect to emitted laser radiation.

Analysis of the Nominal Ocular Hazard Distance (NOHD) must be included within this plan. The

PR: FD2060-19-30143 PWS Revision: 0 14 contractor must obtain either an accession number from the Food and Drug Administration (FDA) or DoD exemption for the laser, consistent with AFI48-139 and DoDI 6055.15. Draft documents shall be delivered 30 days prior to CDR, and final/approved documents shall be delivered 30 days prior to the start of Developmental Testing (DT).

(DI-MISC-80711A, CDRL A004)

3.8.13 System Safety and Hazard Analysis (SSHA)

A SSHA shall be performed in accordance with MIL-STD-882E, System Safety. The analysis shall cover all electrical, mechanical, and human interfaces affected by this modification. The SSHA shall be in the format outlined in AFI 91-202, Mishap Prevention Program, Attachment 15, Preparation of Risk Assessments.

(DI-SAFT-80101C, CDRL A00Z)

3.8.14 Program Environmental Safety and Health Evaluation (PESHE) The Contractor shall develop and deliver a PESHE for DVES for integration into the HH-60G platform PEHSE.

(DI-ENVR-81840, CDRL A010)

3.8.15 Aircraft Structural Integrity

The Contractor shall use MIL-STD-1530D to perform the following tasks:

1) Loads Analysis for any Group A structural modifications deviating from the baseline HH- 60G configuration.

2) Durability and Damage Tolerance Assessment (DADTA) for the HH-60G.

3) Vibration Analysis for Group A structural modifications.

4) Stress Analysis for any Group A structural modifications.

Draft documents shall be submitted 30 days prior to PDR, and the final documents shall be delivered 30 days after CDR.

(DI-MISC-80711A, CDRL A004)

3.8.16 Reliability and Maintainability (R&M)

The Contractor shall develop and deliver an R&M Predictions Report to document quantitative predictions of reliability, maintainability, and Built-In-Test (BIT). Reliability activity updates shall be presented by the Contractor at TIMs and program design reviews to achieve HH-60G DVES SRD compliance.

(DI-SESS-81497A, CDRL A011)

3.8.17 Electromagnetic Interference/Compliance (EMI/EMC)

All electrical and electronic components shall conform to DO-160E, F, or G Section 20, Environmental Conditions and Test Procedures for Airborne Equipment. Aircraft-level system integration shall be designed IAW MIL-STD-464C and MIL-STD-461G, Electromagnetic Environmental Effects Requirements for Systems, and shall be tested by a government-appointed test agency. The Contractor should strive to select proven equipment in the commercial marketplace or in other military applications and shall ensure the equipment will be used in the same environment and under the same conditions for which it was designed.

PR: FD2060-19-30143 PWS Revision: 0 15

3.8.18 Failure Mode Analysis

The Contractor shall provide a Failure Mode, Effects & Criticality Analysis (FMECA) to identify, analyze and resolve single item failures resulting in impacts to potential mission success, performance, personnel safety and maintainability. The FMECA should address all of the following:

1) Test failure descriptions reported within five business days of an occurrence

2) Identification of the failure mode(s), historical trends, and statistical failure distribution update with root cause identification and corrective action for each failed test within 10 business days of an occurrence as an objective or 15 business days of an occurrence as a threshold requirement.

3) The status of design and process corrective actions and risk-mitigation decisions

4) Completion of all corrective actions and risk-mitigation tasks within 30 business days after Government acceptance of corrective action

5) The effectiveness of all implemented corrective actions

6) Lessons learned

(DI-SESS-81495A, CDRL A012)

3.8.19 System/Subsystem Specification (SSS)

The Contractor shall develop and maintain a SSS that specifies the requirements for the system and associated subsystems. The SSS shall document the methods used to ensure that each requirement has been met in a Requirements Traceability Verification Matrix (RTVM).

(DI-IPSC-81431A, CDRL A008)

3.8.20 System/Subsystem Design Description (SSDD)

The Contractor shall develop and deliver to the Government a SSDD. The SSDD describes the system or subsystem-wide design and architectural design of the system or subsystem.

(DI-IPSC-81432A, CDRL A00C)

3.8.21 Interface Design Description (IDD)

The Contractor shall develop, maintain, and deliver to the Government an IDD.

(DI-IPSC-81436A, CDRL A00D)

3.8.22 Interface Control Document (ICD)

The Contractor shall develop an ICD for the system as installed detailing interfaces with all connected systems.

(DI-SESS-81248B, CDRL A00E)

3.8.23 Interface Requirements Specification (IRS)

The Contractor shall modify, maintain, and deliver to the Government an IRS that addresses and documents the interfaces of the DVES and associated or resulting platform changes. The IRS shall specifically document the CSCI interfaces and external interfaces.

(DI-IPSC-81434A, CDRL A00Q)

3.8.24 Acceptance Test Plan (ATP)

PR: FD2060-19-30143 PWS Revision: 0 16

Testing shall be defined in an Acceptance Test Plan (ATP). The ATP shall include procedures to verify the DVES modification meets the requirements documented in the HH-60G DVES SRD while ensuring the DVES hardware integration does not degrade existing aircraft systems.

(DI-QCIC-80553A, CDRL A00S)

3.8.25 Aerodynamics

The Contractor shall develop and deliver an analysis of the impact of adding the DVES sensor to the exterior of the aircraft. This analysis shall include an equivalent addition to the flat-plate drag of the aircraft and related updates to all affected charts in TO 1H-60(H)G-1. A draft shall be submitted 30 days prior to PDR, and the final document shall be delivered 30 days after CDR.

(DI-MISC-80711A, CDRL A004)

3.9 System Testing and Evaluation

3.9.1 Test and Evaluation Master Plan (TEMP)

The TEMP documents the overall structure and objectives of the test and evaluation program including integrated simulation, test and evaluation plans, schedules, and resource requirements.

It will be prepared as a Government supplied document in accordance with Department of Defense Instruction (DoDI) 5000.2. The TEMP will address:

• Test matrices detailing methodologies, objectives and measures of effectiveness,

• Data collection methods (including use of vendor data) plans & schedules,

• Test scenario definition,

• Resource requirements,

• Test venue definition (ranges, labs, simulators, etc.),

• Stakeholders, roles and responsibilities,

• Submission, screening, prioritization, and tracking of deficiencies

The TEMP will also describe how and when the certification process is implemented.

The DVES test and evaluation program intends to save time and money by avoiding repeating tests; thus DVES will integrate Developmental and Operational Test and Evaluation (DT/OT), integration flight test, lab integration and test, and modeling and simulation (M&S). Time and cost savings are realized by combining test and verification data at the simplest/lowest level possible without compromising either developmental or operational test objectives.

3.9.2 Site Survey

For the purpose of an aircraft survey, the Government will provide two fully mission-configured, one in a Block 152 configuration and one in a Block 162 configuration, aircrafts at a location to be determined. This should assure accuracy and configuration compatibility during the design effort. The Contractor shall prepare a site survey report after completion of the survey, including pictures in JPEG.

(DI-MGMT-80368A, CDRL A013)

3.9.3 Government Test Support

PR: FD2060-19-30143 PWS Revision: 0 17

The Contractor shall support Government test activities including flight test. The Contractor shall correct any system design deficiencies attributable to the Contractor’s design that are identified during Government test. The Contractor shall also support Government deficiency investigations and corrective action activities for those deficiencies not attributable to the Contractor-developed design. The Contractor shall support any retesting activities to verify all corrections.

3.9.4 Environmental Testing

The Contractor shall develop a comprehensive Environmental Test Plan (ETP) for each Contractor developed or provided LRU. When possible, engineering analysis shall be documented in a technical report in lieu of actual testing to support environmental compliance. The Contractor shall develop comprehensive Environmental Test Procedure (ETPr) to document test procedures for each environmental factor. The Contractor shall conduct the ETPr on the first production hardware of each Contractor developed LRU design. If the LRU hardware is an unmodified COTS item, then the Contractor shall ensure the COTS item is capable of passing the ETPr (through presenting COTS technical documentation or actual testing). The Contractor shall document the ETPr test results in a test report.

(DI-NDTI-80809B, CDRL A016)

3.9.5 Bench Testing

The Contractor shall travel and provide technical support for the bench test accomplished on the Extendable Integration Support Environment (EISE) Node and EWAISF (EW-suite) integration testing at Robins Air Force Base (AFB), GA in addition to the Government Lead Designated Test Organization (LDTO) for the Qualification Test & Evaluation (QT&E) ground and flight tests to verify system operation. This includes on-aircraft participation in flight testing as necessary. The Contractor shall document and submit test results no later than 30 days after completion of test event.

(DI-MISC-80711A, CDRL A004)

3.9.6 Aircraft Testing

The aircraft system shall undergo system operational ground testing prior to Government flight test by the LDTO. The Contractor shall attend Government Test Planning Working Group (TPWG) meetings to assist with Government test planning. Unless otherwise directed by the Government, the Contractor shall not proceed to the next phase until any design deficiencies are corrected and any necessary retesting is completed. The Contractor shall provide assistance with EMI/EMC testing. The Contractor shall document and submit test results no later than 30 days after completion of test event.

(DI-MISC-80711A, CDRL A004)

3.10 Technical Documentation

3.10.1 Engineering Data

The Contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, PR: FD2060-19-30143 PWS Revision: 0 18 testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). This shall include software and all test requirement documentation data required to test systems, subsystems and/or components. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be created IAW the following American Society of Mechanical Engineers (ASME) standards: ASME Y14.100-2013, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41 and as defined in the corresponding CDRL for this task to create and deliver Product Drawings Models and Associated Lists (Engineering Data) under this contract.

Data set classification code marking IAW Appendix F of ASME Y14.100-2013 is required. CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification IAW MIL-STD-130N, other applicable documents referenced therein, and as specified in this contract. Test Criteria for Electrical and Avionics Items shall be IAW document 9579777 Revision B (CAGE 98752) The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision N (CAGE 98752), reference attached DD Form 1423 Block 16.

(DI-SESS-81000E/T, CDRL A017)

3.10.1.1 Engineering Data Updates and Revisions

The Contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a) All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b) All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c) All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

d) Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

PR: FD2060-19-30143 PWS Revision: 0 19

3.10.1.2 Relationship of Contractor with Subcontractors/Vendors The Contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

3.10.2 Technical Orders (TOs)

The Contractor, for the purpose of the proposal, based on their design concept, shall identify all Air Force TOs and an approximate count of affected pages. The Contractor shall develop the TO change pages necessary for the operation, maintenance, and support of the modification in accordance with the requirements of the Technical Manuals Contract Requirements (TMCR) TM- 86-01. The Government will retain the right of approval of the final TOs/Interactive Electronic Technical Manual (IETM) through the certification and verification process and the pre-pub review. Additionally, the Contractor is responsible for technical accuracy through verification.

Refer to the TO Management Plan (TOMP) and TO Verification Plan (TOVP) attached to the

TMCR.

(TM-86-01, CDRL A018)

3.10.2.1 Time Compliance Technical Order (TCTO)

The Contractor shall develop a routine TCTO IAW T.O. 00-5-15 for installation of the DVES onto the HH-60G. The TCTO shall be developed and delivered IAW the Technical Manual Contract Requirements (TMCR) TM-86-01.

(TM-86-01N, CDRL A018)

3.10.2.2 In Process Review (IPR) of TOs

The Contractor shall host, support, and co-chair an IPR of the TOs and other supporting documentation. The IPR shall be conducted only after the Contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 40% and 80% completion points and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). The TOs shall be submitted to the Government no later than 30 working days prior to the scheduled review. The TOs shall be delivered in the format identified in the TMCR.

(DI-ADMN-81249B, CDRL A001; DI-ADMN-81250B, CDRL A002; DI-ADMN-81373,

CDRL A01F; TM-86-01N, CDRL A018)

3.10.3 Provisioning

The Contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). MIL-PRF-49506 should be used as a guide.

Format must be consistent with existing government Provisioning data system (D220).

(DI-SESS-81758A/T, CDRL A019; DI-SESS-81874, CDRL A01A)

3.10.4 Program Protection Plan (PPP)

The Contractor shall develop and provide a Program Protection Plan for DVES.

PR: FD2060-19-30143 PWS Revision: 0 20

(DI-ADMN-81306, CDRL A01B)

3.11 Prototype and Verification Installations

For the purpose of this modification, the terms Prototype Installation and Verification Installation are equivalent to Trial Kit Installation and Kit Proof Installation, respectively. The guidance provided in regulations AFI 63-101 and T.O. 00-5-15 apply to these events and this modification.

3.11.1 Prototype Installation (PI)

The Contractor shall manufacture and assemble necessary components and all attaching hardware for the PI. This kit will be used to install the DVES onto the HH-60G aircraft IAW the design approved at the CDR. The installation kit shall be packaged per the requirements in paragraph 3.14.2, and the applicable AFMC Form 158. The Contractor shall provide technical support of the initial kit installation on a selected aircraft. The installation shall be at a location determined to be most advantageous to the Government. The Contractor shall provide technical non-recurring engineering support for the initial kit installation. The Contractor shall note and ‘redline’ any affected drawings, kit lists, and Technical Orders (TOs) that require changes as result of information learned from the installation. The Contractor shall correct all applicable kit deficiencies discovered during the initial installation and test activities. The Contractor shall install the kit, document the installation, and provide pictures in a MS Office®-compatible format.

The Contractor shall perform operational checkout of the system following the installation using their Acceptance Test Procedures (ATPs). If the installation is deemed successful by the procuring agency, the installation kit may remain installed for the purposes of supporting government ground and flight testing. The successful kit installation should be considered to be the first production kit installation. The Contractor shall document and submit test results no later than 30 days after completion of event.

(DI-MISC-80711A, CDRL A004)

3.11.2 Prototype Installation Test

The Contractor shall develop and execute a Government-approved Prototype Installation Test Plan for the HH-60G to include all testing requirements for the purpose of accepting the PI prior to Government testing.