ATTACHMENT_3-PERFORMANCE_WORK_STATEMENT.pdf

P a g e 1 | 19

PERFORMANCE WORK STATEMENT (PWS)

For

F-16 Data Acquisition System (DAS) Redesign Effort Phase One

PREPARATION DATE: 29 Jul 2021

FD2030-22-00024

Drafted by:

Joe Terry

422 SCMS/GUEA

3001 Staff Dr 1AC494B Tinker AFB, OK 73071

Joe.terry@us.af.mil 405-582-5354 mailto:Joe

P a g e 2 | 19

Table of Contents

1 INTRODUCTION

1.1 Purpose

1.2 Background

1.3 Scope

2 REFERENCE DOCUMENTS

3 CONTRACTOR TASKING / REQUIREMENTS

3.1 Program Management

3.1.1 Project Kick-Off Meeting

3.1.2 Program Management Plan

3.1.3 Program Management Review

3.2 Testing

3.2.1 Qualification Testing

3.2.2 Initially left Blank reserved for Back shop testing if required by the F-16 SPO

3.2.3 On Aircraft Testing

3.3 Technical Data

3.4 Final Report

3.5 Service Contract Report

3.6 Cyber-Security

3.6.1 Program Protection

4 DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE

4.1 Period of Performance

4.2 Delivery Schedule for PR FD20302100241-00

4.3 Government Inspection and Acceptance of Deliverables

5 Services Summary 6 Data Marking

6.1 Asserted Rights in Technical Data

6.2 Removal of Unjustified and Nonconforming Markings

6.3 Distribution Statements

6.3.1 Distribution Statement A

6.3.2 Distribution Statements D and E

6.4 Export Control Warning Label

6.5 Destruction Notice for Unclassified Documents

6.6 Classification

6.7 General Marking Guidance

7 Safety and Health

7.1 VPP Overview

7.2 VPP BENEFITS Who benefits from VPP?

P a g e 3 | 19

ACRONYM LIST

ARO After Receipt of Order ASIP Aircraft Structural Integrity Program AT Anti-Tamper BIT Built-In Test CAPRE Common Aircraft Portable Reprogramming Equipment CDRL Contract Data Requirements List CPI Critical Program Information CSFDR Crash Survivable Flight Data Recorder DAU Data Acquisition Unit DAS Data Acquisition System DFLCS Digital Flight Control System DI Data Item ECSMU Enhanced Crash Survivable Memory Unit GFE Government Furnished Equipment GPM Government Program Manager IPB Illustrated Parts Breakdown LRU Line Replaceable Unit MLV Memory Loader Verifier NSN National Stock Number OC-ALC Oklahoma City Air Logistics Complex OSHA Operational Safety and Health Administration OSS&E Operational Safety, Suitability & Effectiveness P/N Part Number PWS Performance Work Statement SAU Signal Acquisition Unit SBIR Small Business Innovative Research SPO System Program Office SRA Shop Replaceable Assembly SRU Shop Replaceable Unit TAFB Tinker Air Force Base TFFI Total Fuel Flow Indicator USAF United States Air Force UUT Unit Under Test VPP Voluntary Protection Program

P a g e 4 | 19

1 INTRODUCTION

1.1 Purpose

The objective of this document is to describe the requirements for the F-16 Data Acquisition System (DAS) redesign effort. This effort shall be a two phased approach contracted with GE Aviation Systems LCC (GE Aviation), Grand Rapids, MI, to develop and qualify a replacement system for the current Data Acquisition System consisting of a Data Acquisition Unit and an Enhanced Crash Survivable Memory Unit. This new system shall be integrated into USAF Block 30/32/40/42/50/52 F- 16 Fighter Aircraft, as well as similarly configured foreign military partners. Phase one will consist of completing a Preliminary Design and get design approval by the System Program Office and the COR approval to move to phase two. Phase two will complete at a final product that is completely tested and qualified according to this PWS and ready for production.

1.2 Background

The Crash Survivable Flight Data Recorder (CSFDR) system is a reliable, compact, solid-state airborne recording system used for collecting, processing, and storing a variety of flight data for F-16 aircraft . The CSFDR is mission essential and currently consists of a Data Acquisition Unit (DAU) and an Enhanced Crash Survivable Memory Unit (ECSMU) as separate components. Its purpose on the aircraft is to acquire, process, and store raw parameter data from the aircraft; analog and discrete sensors, MIL-STD-1553B Avionics Multiplexed (A-MUX) Data Bus parameters, two serial channels from the Digital Flight Control System (DFLCS) and from a dedicated RS-422 serial communication channel from the aircraft engine. Attached to the armored housing of the ECSMU is an underwater locator beacon, which automatically activates upon immersion in water to aid in ECSMU recovery, in case of a catastrophic event. The CSFDR also includes built-in ground support provisions that allows a Viper or CAPRE MLV to connect to the aircraft for uploading flight software and documentary data, downloading of recorded data for Aircraft Structural Integrity Program (ASIP) evaluations, initiating and examining BIT results, and performing various other CSFDR maintenance related functions.

Due to parts obsolescence issues and to increase long-term sustainability for fleet management, a redesign of the Data Acquisition System Line Replaceable Units (LRUs) into a single configuration is desired, combining both the functionalities of the current DAU and ECSMU into a single unit. A modified, redesigned, and tested version of the DAS must meet the aircraft current form, fit, and function.

1.3 Scope

The primary purpose of this effort is to provide a new LRU that is a combination of the current Data Acquisition Unit and the Enhanced Crash Survivable Memory Unit. This effort is to be accomplished utilizing the current mounting provisions and wiring configuration of the F-16 Aircraft.

The technical efforts and methods of design shall be focused on the identification, generation, evaluation, test, and documentation of a form, fit, function solution to address recording, processing and storage of raw data, and system engineering requirements for aircraft, avionics, sensors, and support systems. Task objectives shall address system engineering, integration, test and evaluation efforts necessary to analyze, prototype, install, integrate, document, and field identified solution.

Other engineering report efforts shall be provided by the contractor as required to meet Airworthiness

P a g e 5 | 19 and Operational Safety, Suitability & Effectiveness (OSS&E) requirements for supporting government qualification and installation of test articles on the above aircraft to include: electrical, environmental, mechanical, safety, and software.

Phase one will include: engineering design of a prototype that will meet the requirements of Section 3 of this PWS. This will include an engineering test plan and prototype drawings per PWS 3.3.

Phase two will include: production and delivery of six prototype flight data recorder systems to the Government. Two units for environmental testing per section 3.2, four units for ground testing in a System Integration Laboratory (SIL) and on F-16 aircraft testing. In addition, environmental test reports, Electro-Magnetic Interference (EMI) reports, integration instructions and accompanying technical user documentation as described in section 3.2 shall be delivered for inclusion to aircraft technical data updates.

2 REFERENCE DOCUMENTS

• 16ZF062B Prime Item Performance Specification

• PA2064 OEM Acceptance Test Procedure, Data Acquisition Unit

• PD3084 OEM Qualification Test Procedure, Data Acquisition Unit

• PM4043 OEM Electrostatic Discharge Damage Prevention Requirements

• MIL-STD-462D Electromagnetic Interference Characteristics, Measurement of

• MIL-STD-810H Latest Environmental Engineering Considerations and Laboratory Tests

• AFPAM 63-129 Air System Development and Sustainment Engineering Processes and

Procedures

3 CONTRACTOR TASKING / REQUIREMENTS

The Contractor shall design, qualify and fully document the new system to meet the following tasks:

• Design a single-box solution that incorporates full DAS functionality, compatible with all USAF F-

16 variants. Design shall utilize current wiring configurations and mounting provisions for form, fit, and function.

o Current form factor measurements (in inches) are: W6.23 x H7.03 x L7.28. The Beacon, which measures (in inches) approximately: W1.86 x H2.02 x L4.18 must be incorporated into the Single-Box Design along with the Crash Survivable Memory. If mounted internally, there exists no issues with current form factor. However, if mounted externally, there is approximately four (4) inches of space inboard of the current LRU for all C-Model variants of the F-16. Consideration must be made for D-Model aircraft, however; there is no additional room for a larger unit with the current mounting provisions.

• Design using GE’s next-generation flight recorder technology based on Xilinx UltraScale+ multiprocessor system-on-chip (MPSoC) or newer technology.

• Rework the schematics and layout for the newly designed DAS.

P a g e 6 | 19

• Update mechanical design due to changed thermal characteristics.

• Implement the DAS communication protocol in the new system.

• Update Flight Program to accommodate additional recording parameters.

• Update test equipment software, Environmental Stress Screening, and qualification testing to accommodate one box solution and communication interfaces.

• The contractor shall provide the ability to do JTAG memory dumps on the test assets. JTAG shall be removed on the production assets.

• Verify Viper/CAPRE communication with new system.

• Perform SIL and flight-testing support

• Integrate Technical Order documentation.

• Meet all Cybersecurity requirements

The contractor shall design, build and deliver six engineering pre-production units; four for testing in a US Air Force SIL and on USAF F-16 aircraft and two available for qualification and environmental testing.

3.1 Program Management

The contractor shall establish a single management focal point to accomplish the requirements of this PWS and to coordinate with the government task leader (GTL) or the GTL’s technical representative. The contractor shall perform administrative, technical, and financial management functions during the course of the program and shall maintain a status of these. Contractor employees shall identify themselves as Contractor personnel and display distinguishing badges or other visible identification at all times. Contractor personnel shall appropriately identify themselves as Contractor employees in conversations, formal and informal written correspondence, teleconferences, video teleconferences, faxes, and/or other electronic communication whether with Government personnel, other contractor personnel, or with the public when supporting this contract where their status as contractor employees might not otherwise be apparent or where they might be mistaken for civil service employees or military personnel.

3.1.1 Project Kick-Off Meeting

The contractor shall host/conduct a kick‐off meeting with Government participation. The purpose of the meeting will be to establish/define communication points of contact (POCs), a review of the current design and overview of proposed changes, and determine a schedule of contract work to be completed. A Conference Agenda shall be delivered IAW CDRL A004 and Conference Minutes IAW CDRL A001, per the delivery schedule in Table 4.2. (DI‐ADMN‐81249B A004, Meeting Agenda), (DI‐

ADMN‐81250B, CDRL: A001)

3.1.2 Program Management Plan

The schedule of contract work to be completed shall be provided to the Government IAW CDRL A007.

(DI-MGMT-81861B, A007, Integrated Schedule/Management Plan and Analysis Report)

3.1.3 Program Management Review

P a g e 7 | 19

The Contractor shall schedule and conduct quarterly (or as determined necessary by the GTL) program status reviews in coordination with the Government Program Manager. The purpose of these meetings shall brief the progress of the project. The Contractor shall generate presentation materials as required to aid in the discussion of technical issues. The Contractor shall provide meeting agendas and meeting minutes, and shall track Action Items associated with these meetings.

(DI‐ADMN‐81249B A004, Meeting Agenda) (DI‐ADMN‐ 81250B, A005, Meeting Minutes)

3.2 Testing

3.2.1 Qualification Testing

The Contractor shall Perform Electrical, Electromagnetic Interference and Environmental Stress Screening and Testing IAW Para 2.0. The contractor will provide the test procedures and report results per. (DI-NDTI-80603A, Test Procedure, CDRL A009), (DI-ENVR-81663, ESS Report, CDRL:

A002), (DI-EMCS-80200C, EMI Testing Report, CDRL A008), (Test and Inspection Report, DI-NDTI- 80809B, A010)

Qualification testing shall include:

1. Electrical Power Test:

a. Qualify IAW MIL-STD-704A, 9 Aug 1966

• Prohibited from using later versions

• Use MIL-HDBK-704-3, 12 Sep 2018 as a guide

b. Required Data:

• Test Plan

• Test Procedures

• Test Report

2. Environmental Testing to include:

a. Qualify IAW MIL-STD-810H, 31 Jan 2019

• Method 501.7: High Temperature

• Method 502.7: Low Temperature

• Method 503.7: Thermal Shock

• Method 507.6: Humidity

• Method 509.7: Salt Fog

• Method 510.7: Sand and Dust

• Method 511.7: Explosive Atmosphere

• Method 513.8: Acceleration

• Method 514.8: Vibration Endurance

• Method 516.8: Shock

• Method 519.8: Gunfire Shock

• Method 523.4: Temperature with Vibration

• Additional Parameter testing deemed necessary

b. Crash Survivability IAW AFPAM 63-129

3. Electromagnetic Interface Test:

a. Qualified to MIL-STD-461G. 11 Dec 2015

b. Required Data:

• Test Plan

P a g e 8 | 19

• Test Procedures

• Test Report

c. Required Tests:

• Conducted Emissions (CE102)

• Conducted Susceptibility (CS101)

• Conducted Susceptibility (CS114)

• Conducted Susceptibility (CS115)

• Conducted Susceptibility (CS116)

• Radiated Susceptibility (RE102)

i. Radiated Susceptibility (RE103)

4. Cybersecurity and Resilience … see section 3.6.2

3.2.2 Initially left Blank reserved for Back shop testing if required by the F-16 SPO

3.2.3 On Aircraft Testing

The Contractor shall provide Engineering Services for On-Aircraft testing IAW 1F-16C-2-31JG-00-1 and 1F-16C-2-31FI-00-1 which fully checks the flight data recorder system. Participation with On- Aircraft testing for up to three days on site at a US Air Force Base to be determined later.

Contractors will also need to get access to an F-16 Base for flight testing TBD when phase two kicks off.

3.3 Technical Data

The Contractor shall provide Design Engineering Services for updates to Technical Manual. Services for updates to the Tech Order documentation is for the for any aircraft level interface Tech Order documentation. Technical Drawings for the DAS. (DI-MISC-80750, A003, Technical Data Report)

3.4 Final Report

The contractor shall provide a final report of findings. The purpose is to address all testing issues that could not be resolved during the testing phases of this contract.

(DI-NDTI-80809B, A006 Test/Inspection Final Report)

3.5 Service Contract Report

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields in the Service Contract Report (SCR) at www.SAM.gov

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year Contractors may direct questions to the SAM.gov service desk (https://www.fsd.gov/fsd-gov/home.do)."

http://www.sam.gov/ https://www.fsd.gov/fsd-gov/home.do)

P a g e 9 | 19

*Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Guide: Data for Air Force service requirements must be input at www.sam.gov. A quick start user guide is available at on the SAM.gov website at https://sam.gov/SAM/transcript/SCR_QSG.pdf. In addition, a full user guides for contractors and government personnel are available at https://www.sam.gov/SAM/pages/public/help/samUserGuides.jsf.

3.6 Cyber-Security

3.6.1 Program Protection

A. The contractor shall deliver a Program Protection Implementation Plan (PPIP). The contractor shall integrate the PPIP activities in the Integrated Master Schedule. The contractor shall derive requirements from the PPIP and put into specifications, trace (reference 3.6.2.B),and verify through the Systems Engineering Processes. Program Protection includes the following areas: Cybersecurity to include Trusted Systems and Networks (TSN), Cyber Resiliency, Anti-Tamper, and Information Protection.

B. The contractor will notify the Government Contracting Activity and the Government Security Manager within 48 hours of any incident involving the actual or suspected compromise/loss of classified information to enable the Government to conduct immediate assessment of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Information will be reported IAW DFARS Clause 252.204-7012.

C. The contractor shall report Cyber incidents to the government IAW DFAR Clause 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting) to the Defense Cyber Crime Center (DC3) via the DIBNet. In addition, provide a root-cause, corrective-action report. The contractor shall establish and maintain an incident response infrastructure with identified membership and operating procedures to facilitate rapid response to cybersecurity incidents.

3.6.2. Cybersecurity and Trusted Systems and Networks

A. SCTM: The contractor shall allocate system security and resiliency requirements to architectural entities and system elements. The contractor shall trace system architecture design to the requirements derived from the agreed to Security Controls Traceability Matrix (SCTM) NIST 800-53 http://www.sam.gov/ https://sam.gov/SAM/transcript/SCR_QSG.pdf https://www.sam.gov/SAM/pages/public/help/samUserGuides.jsf

P a g e 10 | 19 controls IAW DoDI 8500.01 and DoDI 8510.01 and TSN per DoDI 5200.44, AT per DoDI 5200.44 and 5200.39, and Resiliency requirements. The contractor shall allocate requirements to the Safety Critical Functions (SCFs), Mission Critical Functions (MCFs), and CPI commensurate with operational risk categorization. The contractor shall ensure integration and verification that SCFs, MCFs, and CPI have the appropriate segregation and diverse redundancy in the architecture to complete the mission (resiliency).

B. When applicable the contractor shall provide information to obtain Defense Intelligence Agency – Threat Analysis Center (DIA-TAC) Report when Critical Components (CC) are known based on the Safety Critical Function, Mission Critical Function, and CPI thread analysis and traced to the Bill of Materials to the lowest critical components throughout the EMD phase. The contractor shall update design via system engineering processes to ensure above-medium risk components are not in the system.

C. SCRM: The contractor shall ensure all hardware, with special emphasis on lowest CCs and components containing CPI, are from trusted sources and are manufactured by approved personnel.

The contractor shall develop and implement a Counterfeit Parts Prevention program in compliance DFARS 252.246–7007 Contractor Counterfeit Electronic Part Detection and Avoidance System using with SAE AS5553, SAE AS6171, SAE AS6081, and IDEA-STD-1010B or similar practices to prevent the inclusion of counterfeit parts or parts with malicious logic. The contractor shall ensure that no critical components procured are on the section 806 List in the Supplier Performance Risk System (SPRS). The contractor shall develop a Supply Chain Risk Management (SCRM) plan IAW the current version of CNSSD No. 505 and NIST 800-160 to mitigate supply chain risk.

D. HAMAAR & Deep Dive Testing: The contractor shall perform a Program Protection / System Security Vulnerability Assessment. The contractor shall conduct its own weapon system penetration testing, with emphasis on lowest CCs and components containing CPI, and provide the test report.

The government shall be able to participate in all testing. In addition, the contractor shall complete a Hardware and Memory Architecture Analysis Report (HAMAAR) and allow the Government time in the laboratories and with the component to conduct testing and verification.

Specifically the vendor shall develop a test procedure based on the Memory verification section of the HAMAAR as Pass/Fail tests, run the associated tests in their facilities and allow Government representatives to witness, review, and accept all testing activities and results. Typical Deep Dive reviews can be completed in 3-5 business days, and involve time in the vendor’s lab/test stands, as well as meeting spaces. The vendor shall also make available the appropriate system experts to run the tests and answer questions about the results. The end goal of these efforts is to validate and verify how data in the system is handled, with specific interest in what resides in the system’s non-volatile memory.

E. The contractor shall perform an Attack Path Analysis. The contractor shall identify and analyze the cyber-attack surface by listing any hardware, software, connection, data exchange, service, removable media, or any other system attribute that may expose it to exploitation to determine likely avenues of cyber-attack. The contractor shall perform a covert channel analysis to identify those aspects of communications within the component that are potential avenues for covert storage and/or timing channels.

P a g e 11 | 19

F. As applicable the contractor shall conduct software assurance assessments to identify and correct weaknesses identified in the following enumerations: Common Vulnerability Enumeration ®; Common Attach Path Enumeration and Classification™; and Common Weakness Enumeration™. In addition, software will be tested for invalid or malformed data, also known as “out of bounds” testing or “negative” testing. Details of the assessment tools and methodology shall be included in the Software Test Report, as well as any residual weaknesses that were not fixed. These results will be included in the System Security Vulnerability Assessment (reference 2.2.E). If there are interconnects/interfaces, the Software Development Plan shall ensure software assurance is maintained for the SCF, MCF, and CPI/AT

G. In general the contractor shall support the program office with data and information to obtain Interim Authority To Test (IATT) and Authority To Operate (ATO).

3.6.3. Critical Program Information (CPI) / Anti-Tamper (AT)

A. If CPI is identified the contractor shall develop and implement Anti-Tamper (AT) hardware and software protection measures to protect (by deterring, preventing, detecting, and/or reacting to anti-tamper attacks) the Government approved resident Critical Program Information (CPI) per the DoD AT Desk Reference and Anti-Tamper Technical Implementation Guide (TIG), and document in an AT Plan formatted IAW DoD ATEA Annex: Anti-Tamper Plan Template. The contractor shall trace the test plan requirement to the specification and verify through the systems engineering processes.

3.6.4. Security Management

A. The contractor shall establish and maintain a security program to comply with requirements of the Government-provided Contract Security Classification Specification, DD Form 254, and other security-related contractual requirements as indicated in all RFP/SOO/SOW documents.

B. The contractor shall apply Operations Security (OPSEC) in their management of the Program IAW AFI 10-701 Operations Security and the OPSEC Plan and program’s Critical Information List provided by the Government program office. (CDRL X)

C. The contractor shall provide Operations Security (OPSEC), Communications Security (COMSEC) and Cybersecurity Training as part of its overall training requirements. OPSEC, COMSEC, and Cybersecurity Training outline specific actions to protect classified and sensitive unclassified information, activities and operations during the course of the contract.

D. The contractor shall be compliant to National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 in accordance with DFARS, Clause 252.204-7008.

E. The contractor shall develop and store in a secure facility all DoD technical data (e.g., source code), and computer software in the possession or control of non-DoD entities on non-DoD information systems in protected means through segregation control (e.g. firewall, isolated network) to prevent connections to the GIG and document meeting this requirement in the Security Plan.

P a g e 12 | 19

F. When applicable the contractor shall implement and maintain administrative, technical, and physical safeguards and controls with the security level and services required IAW the DoD Cloud Computing Security Requirements Guide (SRG) unless notified by the Contracting Officer that this requirement has been waived by the DoD Chief Information Officer (DoD CIO).

4 DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE

4.1 Period of Performance

The period of performance for this task shall be for 36 months from contract award. Early completion and delivery is acceptable and encouraged, but without additional monetary compensation/reward.

4.2 Delivery Schedule for PR FD20302100241-00

The following table summarizes the deliverables and their respective due dates. The Contractor shall develop a finalized Integrated Schedule IAW CDRLA007. All schedules are specified in terms of calendar days

Table 4.2 CDRL Deliverable Schedule

Paragraph Description/CDRL CDRL

Data Item

Due Date

3.1.1 Kick Off Meeting Minutes

DI‐ADMN‐81250B

A001 10 Days after meeting

3.2.1 Environmental Stress Screening Report

DI-ENVR-81663

A002 10 Days After Testing Complete

3.3 Tech Data Package Report

DI-MISC-80750

A003 60 Days Before Contract Competition

3.1.1 3.1.3

Meeting Agenda

DI‐ADMN‐81249B

A004 5 Days Before Scheduled meeting

3.1.3 Meeting Minutes

DI‐ADMN‐ 81250B

A005 5 Days After Scheduled meeting

3.4 Test/Inspection Final Report

DI-NDTI-80809B

A006 30 days prior to Contract Completion

P a g e 13 | 19

3.1.2 Integrated Schedule/Management Plan

and Analysis Report

DI-MGMT-81861B

A007 3 days before Kick-off meeting

3.2.1 EMI Testing Report

DI-EMCS-80200C

A008 10 Days after testing is complete

3.2.1 Test Procedure

DI-NDTI-80603A

A009 10 days before testing starts

3.2.1 Test and Inspection Report

DI-NDTI-80809B

A010 10 Days after testing is complete

4.3 Government Inspection and Acceptance of Deliverables

The Government Program Manager will have the right to reject or require correction of any deficiencies found in deliverables. Specifications will be identified by each CDRL. If no comments are provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the Government.

5 SERVICES SUMMARY

The Contractor shall ensure the performance objectives, performance thresholds, and support for surveillance methods are achieved as follows:

Table 5.1: Services Summary

Description PWS Para Performance Objective Remedy

Delivery of Meeting Minutes - CDRL A001

3.1.1 The contractor shall provide CDRL

A001 Meeting Minutes, DI‐ADMN‐ 81250B deliverable in accordance with the PWS with 2 or fewer defects.

COR will provide feedback on the CDRL. Revised CDRL shall be resubmitted within 5 working days.

Final CDRL will be defect free at time of delivery.

Delivery of Environmental Stress Screening Report

–CDRL A002

3.2.1 The contractor shall provide CDRL

A002, Environmental Stress Screening Report, DI-ENVR-81663 deliverable in accordance with the PWS; subject CDRL shall be delivered to the COR with 2 or fewer defects. A defect is defined as a mistake that adversely impacts technical content and/or clarity.

COR will provide feedback on the CDRL. Revised CDRL shall be resubmitted within 5 working days.

Final CDRL will be defect free at time of delivery.

P a g e 14 | 19

Delivery of Tech Data Package Report -CDRL A003

3.3 Contractor shall deliver the CDRL

A003, Technical Data Package, DI- MISC-80750,deliverable in accordance with the PWS; subject CDRL shall be delivered to the COR with 2 or fewer defects. A defect is defined as a mistake that adversely impacts technical content and/or clarity

COR will provide feedback on the CDRL. Revised CDRL shall be resubmitted within 5 working days.

Final CDRL will be defect free at time of delivery.

Delivery of Meeting Agenda - CDRL A004

3.1.1 3.1.3

The contractor shall provide CDRL A004 Meeting Agenda, DI-ADMN- 81249B deliverable in accordance with the PWS with 1 or fewer defect.

COR will provide feedback on the CDRL. Revised CDRL shall be resubmitted within 5 working days.

Final CDRL will be defect free at time of delivery.

Delivery of Meeting Minutes- CDRL A005

3.1.3 The contractor shall provide CDRL

A005 Meeting Minutes, DI-ADMIN- 81250 deliverable in accordance with the PWS with 1 or fewer defect.

COR will provide feedback on the CDRL. Revised CDRL shall be resubmitted within 5 working days with no additional cost/fee. The final CDRL will be defect free at time of delivery.

Delivery of Test/Inspection Final Report - CDRL A006

3.4 The contractor shall provide CDRL

A006, Test/Inspection Final Report, DI-NDTI-80809B deliverable in accordance with the PWS; subject CDRL shall be delivered to the COR with 2 or fewer defects. A defect is defined as a mistake that adversely impacts technical content and/or clarity.

COR will provide feedback on the CDRL. Revised CDRL shall be resubmitted within 5 working days.

The final CDRL will be defect free at time of delivery.

Delivery of Integrated Schedule/Management Plan and Analysis Report- CDRL A007

3.1.2 The contractor shall provide CDRL

A007 Integrated Schedule/Management Plan and Analysis Report, DI-MGMT-81861B deliverable in accordance with the PWS with 1 or fewer defect.

COR will provide feedback on the CDRL. Revised CDRL shall be resubmitted within 5 working days.

The finalized CDRL will be defect free at time of delivery.

Delivery of EMI Testing Report- CDRL A008

3.2.1 The contractor shall provide CDRL

A008, EMI Testing Report, DI- EMCS-80200C deliverable in accordance with the PWS; subject CDRL shall be delivered to the COR with 2 or fewer defects. A defect is defined as a mistake that adversely impacts technical content and/or clarity.

COR will provide feedback on the Final CDRL. Revised Final CDRL shall be resubmitted within 5 working days with no additional cost/fee. The final CDRL will be defect free at time of delivery.

P a g e 15 | 19

Delivery of Test Procedure- CDRL A009

3.2.1 The contractor shall provide CDRL

A009, Test Procedure DI-NDTI- 80603A deliverable in accordance with the PWS; subject CDRL shall be delivered to the COR with 2 or fewer defects. A defect is defined as a mistake that adversely impacts technical content and/or clarity.

COR will provide feedback on the CDRL. Revised Draft CDRL shall be resubmitted within 5 working days with no additional cost/fee. The final CDRL will be defect free at time of delivery.

Delivery of Test Inspection Report– CDRL A010

3.2.1 The contractor shall provide CDRL

A010, Test and Inspection Report DI-NDTI 80809B deliverable in accordance with the PWS; subject CDRL shall be delivered to the COR with 2 or fewer defects. A defect is defined as a mistake that adversely impacts technical content and/or clarity.

COR will provide feedback on the CDRL. Revised Draft CDRL shall be resubmitted within 5 working days with no additional cost/fee. The final CDRL will be defect free at time of delivery.

6 DATA MARKING

The following references govern how artifacts containing technical data shall be marked

• DODI 5230.24, Distribution Statements on Technical Documents

• AFI 61-201, Scientific, Research And Development Management of Scientific and

Technical Information (STINFO)

• DFARS 252.227-7013, Rights in Technical Data--Noncommercial Items

6.1 Asserted Rights in Technical Data

Mark all technical data to be delivered to the Government IAW DFARS 252.227.7013(f) Technical data delivered or otherwise provided under a contract without restrictive markings shall be presumed to have been delivered with unlimited rights and may be released or disclosed without restriction.

6.2 Removal of Unjustified and Nonconforming Markings

IAW DFARS 252.227.7013(h), Proprietary markings shall be considered non-conforming and not authorized. The words "unlimited rights" shall be considered non-conforming and not authorized.

All nonconforming markings will require removal and redelivery of the artifacts within 60 days.

6.3 Distribution Statements

Mark STINFO to be delivered to the Government IAW DODI 5230.24 and AFI 61-201.

Descriptions and examples of each applicable Distribution Statement are listed below.

6.3.1 Distribution Statement A

Distribution Statement A shall be used for technical data with asserted license rights of Unlimited where Export Control is not required. A Destruction Notice is not required.

DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.

6.3.2 Distribution Statements D and E

Distribution Statements D and E shall be used for the following instances:

P a g e 16 | 19

• Distribution Statement D shall be used for technical data with asserted license rights of Unlimited where Export Control is required.

• Distribution Statement E shall be used for technical data with asserted license rights of Limited.

• Distribution Statement E shall be used for technical data with asserted license rights of Government Purpose.

• Distribution Statement E shall be used for technical data that contains proprietary information.

Distribution Statements D and E are expressed in a standard format comprising four components presented in the following order and as applicable to this Contractual Engineering Task (CET):

1. Authorized Audience – Department of Defense and DOD contractors or DoD Components only.

2. Reason for Control - More than one reason or justification for non-release of controlled technical information may apply. Therefore, more than one reason may be used in a Distribution Statement. Applicable reasons are: a. Administrative or Operational Use.

b. Critical Technology.

c. Export Controlled – All artifacts found to contain export controlled technical data, must specify “Export Controlled” as a reason for limitation in addition to all other reasons that apply.

d. Proprietary Information – For technical data, note the Government’s license rights i.e. “Proprietary Information (DFARS Limited Rights)”. For non-technical data, such as financial information, state “Proprietary Information” without the Government’s license rights.

3. Date of Determination – Date contract was awarded.

4. Controlling Office - 422 SCMS/GUEAA, 3001 Staff Drive, Tinker AFB, OK 73145.

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S.

DoD contractors only; Critical Technology and Export Controlled; 23 August 2018. Other requests shall be referred to 422 SCMS/GUEAA, 3001 Staff Drive, Tinker AFB, OK 73145.

DISTRIBUTION STATEMENT E. Distribution authorized to DoD Components only; Proprietary Information (DFARS Limited Rights) and Export Controlled; 23 August 2018. Other requests shall be referred to 422 SCMS/GUEAA, 3001 Staff Drive, Tinker AFB, OK 73145.

6.4 Export Control Warning Label

Mark all STINFO determined to contain export controlled data to be delivered to the Government IAW DODI 5230.24. The Export Control Warning shall be placed directly below the Distribution Statement. All documents assigned a Distribution Statement other than A shall be marked on every page with the following statement:

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, P a g e 17 | 19

U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

6.5 Destruction Notice for Unclassified Documents

Mark all limited-released (marked with a Distribution other than A) STINFO to be delivered to the Government IAW DODI 5230.24 and AFI 61-201. The Destruction Notice illustrated below, shall be placed directly underneath the Export Control Warning.

DESTRUCTION NOTICE - Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

6.6 Classification

Mark all data to be delivered to the Government with classification markings representing the highest classification of the document.

The Contractor may mark all unclassified technical data to be delivered to the Government with “UNCLASSIFIED” typed on the footer and header of each page.

6.7 General Marking Guidance

• All markings shall be conspicuously electronically fixed as to not interfere with other markings contained within the document.

• All markings shall be legible when viewed at normal 100 percent viewing resolutions.

• All markings shall be electronically fixed to the footer of every page of the electronic document.

• Coversheets shall not be used unless coversheet page numbering is sequentially consistent with the document.

• Portions or pages of a document may have different distribution statements that would govern their distribution if separated from the main document. The most restrictive distribution on its parts applies to the document as a whole.

7 SAFETY AND HEALTH

While performing work under this contract the contractor shall comply with all applicable federal, state and local regulations regarding occupational safety and health. The contractor shall notify the Contracting Officer (CO), within eight (8) hours of any damage to government property where the dollar value exceeds $500,000.00 and within two workdays, for any damage to government property less than $500,000.00 during the execution of the contract.

Mishap notifications shall contain, as a minimum, the following information:

a. Contract, Contract Number, Name and Title of Person(s) Reporting

b. Date, Time and exact location of accident/incident

c. Brief Narrative of accident/incident (Events leading to accident/incident)

d. Cause of accident/incident, if known

e. Estimated cost of accident/incident (material and labor to repair/replace)

f. Nomenclature of equipment and personnel involved in accident/incident

g. Corrective actions (taken or proposed)

h. Other pertinent information

P a g e 18 | 19

If requested by the designated CO, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by the Procuring Safety Office.

Emergency Procedures: The Contractor’s personnel shall follow the direction of the Government’s personnel with regard to emergency procedures, such as fire, tornado, active shooter, bomb threats, or other emergency. It is the responsibility of the Contractor to provide guidance and to establish procedures for its employees on how to respond to an emergency. It is the Contractor’s responsibility to account for their employees following an emergency evacuation. The Contractor’s personnel shall participate with the Government’s personnel in all fire and tornado drills at no additional cost to the Government.

Privately Owned Motor Vehicles (POV): Contractor personnel shall comply with the directives pertaining to operation of POVs on Tinker AFB per AFMAN 31-116, in its entirety, “Motor Vehicle Traffic Supervision”. The Contractor shall comply with Tinker AFBI 24-302, in its entirety for the operation of POVs within Tinker AFB.

7.1 VPP Overview

What is VPP?

Working with industry and labor, OSHA created the Voluntary Protection Programs (VPP) in 1982 to recognize and partner with worksites that implement exemplary systems to manage worker safety and health. The managers, employees, and any authorized employee representatives at these sites voluntarily implement comprehensive safety and health programs — hereinafter referred to as safety and health management systems — that go beyond basic compliance with OSHA standards.

Sites qualifying for VPP attain Star, Merit, or Demonstration status. Star participants meet all VPP requirements. Merit participants have demonstrated the potential and willingness to achieve Star status, but some aspects of their programs need improvement.

Statistical evidence for VPP’s success is impressive. Consistently since the Programs began, the average VPP worksite has had a recordable incidence rate for days away from work, restricted work activity, and/or job transfer (DART rate) about 50 percent below the average for its industry!

In VPP, Management commits to operating an effective occupational safety and health management system characterized by four basic elements: Management Leadership and Employee Involvement, Worksite Analysis, Hazard Prevention and Control, and Safety and Health Training.

Employees agree to participate in the program and work with management to ensure a safe and healthful workplace.

The site submits an application to OSHA that describes its system of worker protection.

P a g e 19 | 19

OSHA evaluates the application. If OSHA accepts it, the agency then conducts an onsite review to verify that the safety and health management system meets VPP requirements. With approval comes OSHA’s public recognition of the applicant’s exemplary safety and health management system.

OSHA also periodically reevaluates the participant to confirm its continuing qualification for VPP. Onsite evaluations are every 2 1/2 to 5 years for Star, 12 to 18 months for Demonstration, and 18 to 24 months for Merit.

OSHA removes VPP participants from its programmed inspection lists.

OSHA enforcement personnel will investigate workplace complaints, any fatality or catastrophe, and other significant events. After such events, VPP personnel may also review a participant’s continuing eligibility for VPP.

7.2 VPP BENEFITS

Who benefits from VPP?

The foremost beneficiaries of OSHA’s VPP are the workers who, at day’s end, arrive home safe and healthy to families who needn’t fear the tragedy of worker death, injury, and illness.

Employers Benefit – Fewer injuries and illnesses mean greater profits as workers’ compensation premiums and other costs plummet.

Unions Benefit – Labor-management cooperation on safety and health sets the tone for improved cooperation in other areas.

Industries Benefit – VPP sites are models of excellence that can influence best practices industry-wide