Attachment 1 WC-130J SFMR DPU Refresh_PWS.pdf

PR: FD2060-21-31347 PWS REVISION: 0 1

Distribution Statement: C

Performance Work Statement for

WC-130J Stepped Frequency Microwave Radiometer (SFMR)

Data Processor Unit (DPU) Refresh

Purchase Request: FD2060-21-31347

Distribution Statement C: Distribution authorized to U.S. Government agencies and their Contractors (Administrative or Operational Use; 01-11-27.) Other requests for this document shall be referenced to AFLCMC/WLNCC Robins AFB, GA 31098.

PR: FD2060-21-31347 PWS REVISION: 0 2

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to upgrade current Stepped Frequency Microwave Radiometer (SFMR) Data Processor Unit (DPU) hardware, software and transition from Operating System (OS) Debian GNU/Linux 4.0 (“etch”) to CentOS (LINUX) Revision 8.1. These services include hardware upgrades and software application updates that support National Hurricane Operations Plan (NHOP) requirements. The Contractor shall minimize aircraft structural and electrical system modifications required to achieve program requirements. The Contractor will update all affected engineering drawings, documentation and technical publications. The Contractor will perform all required software testing to ensure compliance with existing, modified, and new functional requirements, to include hardware and software compatibility. The Contractor shall comply with cybersecurity requirements for software and hardware used in the SFMR DPU. The Contractor will perform environmental and electromagnetic interference and compatibility testing for the SFMR DPU and the results reported. The Contractor will not modify or redesign any commercial-off-the-shelf (COTS) hardware procured for this project for meeting WC-130J environmental or electromagnetic interference and compatibility requirements under this PWS. The Contractor will assist in the performance of aircraft-level electromagnetic interference (EMI) tests for the SFMR DPU and will provide an EMI test plan and report.

The Contractor will provide ten SFMR DPUs, software and associated material for installation in the ARWO console. In addition, the Contractor shall provide to the customer seven spare SFMR DPUs and any required OS licenses.

1.2 Benefit to United States Air Force (USAF): The SFMR DPU resides in the Aerial Reconnaissance Weather Officer (ARWO) console in the WC-130J cargo bay. The upgrade SFMR hardware and software will allow the WC-130J aircraft to continue to meet mission requirements, enhance the data system software, and provide the capability to meet new data system requirements.

1.3 Background:

The current SFMR DPU data system computer (part number 3361486-5) has been in use for over 10 years and needs to have both the hardware and software upgraded. Critical hardware components are now no longer available, such as the single board computer and the front LED panel (DMS issues). Crucial need to upgrade the hardware as the new software by Pro Sensing will not be compatible with the existing Processor CPU board. Cannot capture any of the mission critical data. Also, the current displays are no longer available for replacement if defective.

PR: FD2060-21-31347 PWS REVISION: 0 3

2.0 Services Summary

Performance Objective PWS Reference

Performance Threshold

Delivery of upgraded SFMR DPU’s

4.12 Upgraded assets shall be delivered in accordance

with the schedule defined by the contract/order.

There shall be no more than one late delivery.

The Contractor shall notify the Government if the delivery of any asset will not meet the scheduled delivery date and negotiate a revised delivery date. The late asset shall be delivered by the revised delivery date acceptable to the Government.

Quality of CDRL deliverable

4.5.1 There shall be no more than one (1) rejection of

any deliverable. There shall be no more than two (2) total rejection(s) of deliverables per contract period. The Government will reject a deliverable if one or more technical errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection.

Receipt of CDRL deliverable

4.5.2 There shall be no more than one (1) late

submission(s) of deliverables per contract period The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Provide On-Time responses to suspenses

4.4 & 4.5 No more than one (1) delinquent suspense per six (6) month period starting from award date.

Software Releases 4.3.2 Contractor shall deliver SFMR DPU software without errors that cannot be deferred to the next software cycle.

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in their possession in accordance with (IAW) the Federal Acquisition Regulation (FAR) and applicable supplements including, but not limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property. The FAR and applicable supplements can be accessed at the site: http://farsite.hill.af.mil.

http://farsite.hill.af.mil/

PR: FD2060-21-31347 PWS REVISION: 0 4

3.1.2 Government Property to be Provided

During development of SFMR DPU hardware and associated software, the USG will provide the usage of up to two DPUs as required by the contractor. Upon direction from the USG, the Contractor shall ship Government Furnished Property (GFP) to a given location within 48 hours.

3.1.3 Base Support

Integration & Testing (I&T) activities for the WC-130J SFMR DPU shall be performed in the field at USG facilities using ARWO platforms operational at those facilities. The Contractor will perform I&T activities in the field as needed with the replacement SFMR DPU systems and software integrated/connected into existing systems at those USG facilities.

For SFMR DPU system software, Contractor will run any automated tests it has developed at Contractor facilities as part of the development process prior to QT and FQT activities. If the contractor requires access to an aircraft at Keesler AFB, requests need to be submitted to the 53rd Weather Reconnaissance Squadron at least two weeks prior to need date.

Qualification Test (QT) and Formal Qualification Test (FQT) activities for the SFMR DPU system software shall be performed on a WC-130J aircraft at Keesler AFB post the TKI modification. Flight testing will be conducted at Keesler AFB. If required and mutually agreed upon, Contractor personnel will be present on flight test to assess FQT.

3.2 Reporting of Government Property

The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property (GFP) and IAW the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property

“Loss of Government property” means unintended loss of or damage to Government property Loss of Government property” means unintended, unforeseen, or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property. Loss of Government property does not include purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of Government property includes, but is not limited to:

(1) Items that cannot be found after a reasonable search

(2) Theft

(3) Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition

(4) Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair. “Unit acquisition cost” means:

a. For Government Furnished Property (GFP), the dollar value assigned by the

Government and identified in the contract

b. Reporting Loss of Government Property, the Contractor shall use the Defense

PR: FD2060-21-31347 PWS REVISION: 0 5

Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order. http://www.dcma.mil/aboutetools.cfm

(1) Unless otherwise provided for in this contract, the requirements of this clause do not apply to normal and reasonable inventory adjustments, i.e., losses of low risk consumable material such as common hardware, as agreed to by the Contractor and the Government Property Administrator. Such losses are typically a product of normal process variation. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

(2) The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to:

a. Theft

b. Inadequate storage

c. Lack of physical security or

d. “Acts of God”

(3) This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

3.3.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access To eTools.

3.4 Return/Retention of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

3.5 Government System(s)

Access to Government system(s) will not be required to perform tasks under the contract/order.

4.0 Technical Requirements

See Paragraph 4.3 for requirements.

4.1 Period and Place of Performance

http://www.dcma.mil/aboutetools.cfm

PR: FD2060-21-31347 PWS REVISION: 0 6

4.2 Place of Performance

These services will be performed a contractor’s facility ProSensing, 107 Sunderland Road, Amherst, MA 01002 CAGE Code: 0K2E3 and at Keesler AFB, Mississippi.

4.3 Specific Services

4.3.1 Hardware Upgrades

The Contractor will upgrade the SFMR DPU hardware to meet the requirements defined in paragraph 4.4. Modifications internal to the SFMR DPU will be included to accommodate changes in component sizes and interface connection changes between components as required.

4.3.2 Software Upgrades

The Contractor will update the SFMR DPU software to run on the CentOS (LINUX) OS. This software upgrade, including, but not limited to, any third party software, simulation software, test software and scripts, and application installation software associated with or contained therein, shall be in a modern computer language and to the latest version available that will still be compatible with all other upgrades and the new OS. In the event that a third party software package cannot be upgraded, a suitable substitute shall be identified to, and approved by, the contracting officer. If a suitable substitute is not available, or the Contractor finds it more cost effective, the Contractor may develop and integrate the capability covered by the third party package, upon approval by the contracting officer. The software shall not contain errors so significant that they cannot be deferred to the next software delivery.

4.4 Contract Data Requirements List (CDRL) Documentation

CDRL TITLE DOCUMENT ID PWS REF

A001 System/Software Test Plan DI-IPSC-81438A 4.7.2.1 A002 System/Software Test Procedures DI-IPSC-81439A 4.7.2.1 A003 Software Version Description

(SVD)

DI-IPSC-81442A

A004 System/Software Test Report DI-IPSC-81440A 4.7.2.1.1 A005 Weight and Balance Report for

Aircraft

DI-MGMTT-81501A 4.7.2.2

A006 Conference Agendas DI-ADMN-81249B 4.5.1 A007 Conference Minutes DI-ADMN-81250B 4.5.2 A008 Status Reports DI-MGMT-80368A 4.7 A009 Scientific and Technical reports –

Architecture Analysis Report

DI-MISC-80711A 4.4.5.1

A010 Scientific and Technical Reports – Software Code Assessment Report

DI-MISC-80711A 4.4.5.2

A011 Scientific and Technical Reports – DISA STIG Checklist

DI-MISC-80711A 4.4.5.3

A012 Scientific and Technical Reports – Operating System Vulnerability Assessment

DI-MISC-80711A 4.4.5.3

PR: FD2060-21-31347 PWS REVISION: 0 7

A013 Risk Management Status Report DI-MGMT-81809 4.4.5.4 A014 Counterfeit Prevention Plan DI-MISC-81832 4.4.5.5 A015 Data Accession List (DAL) DI-MGMT-81453B 4.4.5.6 A016 Program Protection

Implementation Plan (PPIP)

DI-ADMN-81306 4.4.5.7

A017 Cyber Incidents DI-MISC-80508 4.4.5.8

SFMR DPU software documents to be updated and delivered under the SFMR DPU upgrade effort are as follows:

A. SFMR DPU System/Software Test Plan shall be changed for any type of testing change performed on the SFMR DPU software.

B. SFMR DPU Software Version Description (SVD) shall be updated and released when an official release occurs to the field. This SVD identifies the set of changes contained within the release along with installation instructions. This will be released for Formal Qualification Test (FQT) releases.

C. SFMR DPU Software User’s Manual shall be updated for Functionality Changes or Functionality Additions. Update is based upon scope and type of change/addition performed to SFMR DPU Software.

D. SFMR DPU Software Test Report shall be updated and released when Qualification Tests (QT) and Formal Qualification Tests (FQT) on the new software version are completed. This STR identifies the set of tests run and results of the test for the software being released.

4.5 Contract Data Requirements List(s) (CDRL)

4.5.1 Quality of CDRL Deliverable:

There shall be no more than one rejection of any deliverable. There shall be no more than one total rejection(s) of deliverables per performance. The Government will reject a deliverable if one or more technical errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection.

4.5.2 Receipt of CDRL Deliverable

CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than one late submission(s) of deliverables per contract period. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.5.3 Technical Support (T&M)

This task is for technical services required to support the WC-130J end user community (e.g.

Keesler AFB, National Hurricane Center, and WR-ALC) to investigate and respond to WC- 130J fleet-originated inquiries relative to the SFMR DPU hardware/software update contained

PR: FD2060-21-31347 PWS REVISION: 0 8

herein. The Contractor's response shall be considered the Design Authority's recommendation for resolution and implementation. Technical assessments shall support – but not include – potential follow-on Change Definition and Change Development Engineering Change Proposal (ECP) activities.

This task shall consist of participating in short-term, bounded investigations, and is not intended to support larger, long-term studies. These Technical Support hours shall be utilized by the Contractor to perform Change Development activities as necessary.

The intent of the technical support task is to provide a method for rapid engineering support to WC-130J Customer inquiries/questions concerning the SFMR DPU hardware/software to include telephone support. This task shall be used to support the WC-130J as approved by the Contracting Officer. Except for telephone support, each task request will include the following information:

• Task description

• Desired time for completion of effort

• Type of response required

• Task closure action

4.5.4 Field Support

This task shall support requests for the Contractor to travel to a Government facility to investigate problems with the SFMR DPU hardware/software in support of this effort.

4.6 Requirements

4.6.1 SFMR DPU Hardware Requirements

The SFMR DPU hardware requirements are as follows: Replace with general hardware provided in ProSensing RFI response.

4.6.2 SFMR DPU Software Requirements

4.6.2.1 Operating System: CentOS (LINUX) Revision 8.1

4.6.3 Electromagnetic Interference/Compatibility Requirements The SFMR DPU electromagnetic interface requirements per MIL-STD-461G for the C- 130J Aircraft:

A. CS101 Conducted Susceptibility, Power Leads B. CS114 Conducted Susceptibility, Bulk Cable Injection C. CS115 Conducted Susceptibility, Bulk Cable Injection, Impulse Excitation D. CS116 Conducted Susceptibility, Damped Sinusoidal Transients, Cables and Power

Leads E. CE102 Conducted Emissions Power Leads F. RE102 Radiated Emissions, Electric Field G. RS103 Radiated Susceptibility Electric Field H. Electrostatic Discharge (ESD) per RTCA/DO-160, Section 25, Category A (not

PR: FD2060-21-31347 PWS REVISION: 0 9

applicable to pins) I. Indirect Lightning Effects per RTCA/DO-160, Section 22, Category XXG2L2 for unshielded and XXJ2L2 for shielded cable bundles in accordance with installation location and cable routing.

4.6.4 Environmental Requirements

The SFMR DPU environment requirements are as follows:

A. Operational Shock per MIL-STD-810E, Method 516.4, Figure 516.4-4, Procedure I B. Performance Vibration per MIL-STD-810E, Method 514.4, Procedure I, Category 4 C. Temperature and Altitude per RTCA/DO-160 Category A4 D. Humidity per RTCA/DO-160 Section 6 Humidity Category A E. Explosive Atmosphere per RTCA/DO-160 Section 9 Explosive Atmosphere Category

4.6.5 Cybersecurity Requirements

4.6.5.1 Architecture Analysis Report

The Contractor shall develop and submit a WC-130J SFMR Architecture Analysis Report (AAR) including boundary and data flow diagram(s). The Contractor shall produce Architecture Analysis Data per AFI 17-101 and DOD Instructions 8500.01 and 8510.01 to support the Authority to Operate (ATO) certification process. The Contractor shall produce Architecture diagrams including boundaries and description of data flow across the boundaries. Data flow descriptions shall include direction of flow, type of information, and bandwidth. (CDRL A009, DI-MISC-80711A, SCIENTIFIC AND TECHNICAL REPORTS – ARCHITECTURE

ANALYSIS REPORT)

4.6.5.2 Software Assurance

The software shall include: specific identification of all code with open source origins as well as a description of the code; its specific origin; how it is controlled; how it is tested or analyzed for vulnerabilities; what vulnerabilities have been identified and overcome; and if open source code is used, why open source code is not a risk to the program. The Contractor shall ensure software assurance in accordance with (IAW) DoD Software Assurance Countermeasures in Program Protection Planning (March 2014). The contractor shall also develop, and submit software product Cybersecurity assessments that enable the Government to obtain Cybersecurity authorization of the software modification that is occurring within the accreditation boundary of the aircraft. Assessment techniques shall be performed IAW the guidance defined in DoD Software Assurance Countermeasures in Program Protection Planning. A draft report on the processes and procedures utilized to verify both the expected functional and security performance shall be submitted upon completion of software validation/verification followed by a final delivery in 15 days after USG review of the draft report. Software assessments shall be performed, documented, maintained, and delivered in supporting scientific and technical reports that identify the software modification’s overview, posture, and impacts. The Contractor shall submit cybersecurity data for Government review. (CDRL A010, DI-MISC-80711A, Scientific and Technical Reports – Software Code Assessment Report)

PR: FD2060-21-31347 PWS REVISION: 0 10

4.6.5.3 Operating System Hardening and Vulnerability Assessment The Contractor shall configure the SFMR Operating System (OS) in accordance with guidance from the latest DISA Operating System SRG, or STIG. All STIG, or SRG settings applied to the SFMR OS along with detailed comments shall be documented in a DISA STIG Viewer Checklist, and provided as an artifact to the USG to support the Authority to Operate (ATO) certification process. The Contractor shall utilize a vulnerability assessment tool such as Assured Compliance Assessment Solution (ACAS), or Nessus to perform a vulnerability analysis against the SFMR OS. The report generated by the vulnerability assessment tool shall be provided as an artifact to the USG to support the Authority to Operate (ATO) certification process.

(CDRL A011, DI-MISC-80711A, SCIENTIFIC AND TECHNICAL REPORTS-DISA

STIG CHECKLIST) and (CDRL A012, DI-MISC-80711A, SCIENTIFIC AND

TECHNICAL REPORTS-OPERATING SYSTEM VULNERABILITY ASSESMENT)

4.6.5.4 Supply Chain Risk Management (SCRM)

The Contractor shall establish and implement a SCRM process and integrate it into the program’s risk management process to ensure that the SFMR does not incorporate counterfeit parts, malicious code, or any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations. The Contractor shall support the Government-led supply chain risk assessment to prioritize the Critical Components (CC), assess for supply chain risk as defined in DoDI 5200.44, and develop and document mitigations or countermeasures to minimize the risks. If additional CCs are identified as a result of updates to the Criticality Analysis or changes to suppliers of previously identified CCs, the Contractor shall support the Government-led supply chain risk assessment to prioritize these CCs, assess for supply chain risk, and develop and document mitigations or countermeasures to minimize the risks. The Contractor shall require its suppliers and subcontractors to participate in the supply chain risk mitigation activities. The Contractor shall require its subcontractors and suppliers to notify them of changes that affect supply chain risk, such as changes in their suppliers, locations, processes, or technology. The Contractor shall notify the Government within thirty (30) days of these changes. The Contractor shall include supply chain risks in the Risk Management Status Report. (CDRL A013, DI-MGMT-81809, RISK MANAGEMENT STATUS REPORT)

4.6.5.5 Counterfeit Prevention

The Contractor shall develop, implement, and maintain a Counterfeit Prevention Plan that describes how it will prevent the procurement of counterfeit materials and parts using Society of Automotive Engineers (SAE) AS5553B as a guide. The Counterfeit Prevention Plan shall include a description of the processes for reviewing suppliers and subcontractors and approving ones that meet appropriate counterfeit avoidance criteria. The Contractor shall require its suppliers and subcontractors to participate in counterfeit prevention activities.

(CDRL A014, DI-MISC-81832, COUNTERFEIT PREVENTION PLAN)

4.6.5.6 Counterfeit Prevention Activities

If the Contractor uses custom application-specific integrated circuits that are custom-designed, custom-manufactured, or tailored for a specific DoD military end use, then the Contractor shall acquire them using a trusted flow from supplier(s) accredited by the Defense Microelectronics Activity. The Contractor shall buy parts directly from OEMs, OCMs, and authorized distributors.

PR: FD2060-21-31347 PWS REVISION: 0 11

The Contractor shall provide rationale for any exceptions to this and conduct a supply chain risk assessment to determine the potential risk of obtaining counterfeit parts from such sources. The Contractor shall establish testing and verification requirements for items not received from an OEM, OCM, or authorized distributor. The Contractor shall base the level of testing and verification on each item's identified risk for counterfeit potential. The Contractor's Certificate of Conformance indicating that the parts are not counterfeit will be acceptable for verification of testing. The Contractor shall make the Certificate of Conformance available on the Data Accession List. CDRL A015, DI-MGMT-81453B, Data Accession List (DAL)

4.6.5.7 Program Protection Implementation Plan

The Contractor shall obtain a draft PPP and supporting annexes as Government Furnished Information (GFI) from the Government at CA. The Contractor shall provide support from all appropriate areas of expertise to assist the Government in the development and approval of an updated, Contractor design-specific PPP, including, but not limited to, CPI identification, Anti- Tamper (AT), Criticality Analysis, vulnerability identification, risk assessment, countermeasure development, Supply Chain Risk Management (SCRM), counterfeit prevention, software assurance, and cybersecurity. The Contractor shall develop, implement, maintain, and submit a Program Protection Implementation Plan (PPIP) that is compliant with the security requirements IAW DD Form 254, DoD Contract Security Classification Specification, the NISPOM, the PPP and applicable DoD/AF Cybersecurity policies. The Contractor shall execute a supply chain risk analysis to identify the probability and consequence of unmitigated mission criticality analysis risks. (CDRL A016, DI-ADMN-81306, PROGRAM PROTECTION IMPLEMENTATION

PLAN (PPIP))

4.6.5.8 Safeguarding Covered Defense Information and Cyber Incident Reporting The contractor shall report Cyber incidents (for all sections in the PWS) to the government IAW DFAR Clause 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting) via CDRL/DID and 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 as documented in the Security Plan/Security Assessment Plan. (CDRL A017, DI-MISC-80508, CYBER INCIDENTS) NOTE: DIBNet is a web portal for sharing threat information between DoD and Defense Industrial Base (DIB) companies.

4.7 Program Management

Contractor shall combine meetings whenever possible. There shall be no more than one delinquent suspense per six month period starting from award date.

4.7.1 Conference Agenda

The Contractor shall send agendas announcing all meetings at least 10 working days prior to all meetings.

(CDRL A006, DI-ADMN-81249B, CONFERENCE AGENDAS)

4.7.2 Conference Minutes

Minutes shall be distributed within 10 working days after the meeting/conference.

PR: FD2060-21-31347 PWS REVISION: 0 12

(CDRL A007, DI-ADMN-81250B, CONFERENCE MINUTES)

4.7.3 Kickoff Meeting

The Contractor shall host a post-contract award meeting with the government to review the requirement of the PWS and approve and finalize the IMP/IMS. The Contractor shall prepare and distribute an agenda and minutes of all meetings and conferences (See par.

4.7.1 & 4.7.2).

4.7.4 Technical Interchange Meeting (TIM)

The Contractor shall conduct TIMs at the Contractor’s facility or where the USG deems viable due to budget constraints. The TIM shall provide program (Contractor and Customer) agreement on the tasks and requirements for the development of the upgraded SFMR DPU hardware and associated software. The Contractor shall prepare and distribute an agenda and minutes of all TIMs (See par. 4.5.1 & 4.5.2).

4.7.5 System Requirements Review (SRR)

The Contractor shall conduct an SRR at the Contractor’s facility. This review shall provide program (Contractor/Customer) agreement on the system-level requirements for this ECP.

These requirements shall be documented in the Systems Performance Specification addendums (SPS). The Contractor shall prepare and distribute an agenda and minutes for the SRR (See par. 4.5.1 & 4.5.2).

4.7.6 Software Specification Review (SSR)

The Contractor shall conduct an SSR at the Contractor’s facility. This review shall provide program (Contractor/Customer) agreement on the software requirements for this ECP. These requirements shall be documented in the Software Specification addendums. The Contractor shall prepare and distribute an agenda and minutes for the SSR (See par. 4.5.1 & 4.5.2).

4.7.7 Aircraft Functional Configuration Audit (FCA)

The Contractor with the USG Program Manager shall conduct a formal audit to verify that the modification under review has been completed satisfactorily and that the modification has achieved the performance and functional characteristics. The Contractor shall prepare and distribute minutes for the FCA (See par. 4.5.2).

4.7.8 Physical Configuration Audit (PCA)

The Contractor with the USG Program Manager shall conduct an audit to formally examine the “as-built” (as modified) configuration of the modification against its technical documentation to validate the product specification, thereby establishing and verifying the product baseline is under configuration control. The Contractor shall prepare and distribute minutes for the PCA (See par. 4.5.2).

4.8 Program Schedule Information

The Contractor shall develop an Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) based on contract deliverables and submitted at the Tier 1 level to accomplish said deliverables. All dates other than contract deliverables are considered non-contractual and provided as information only, unless otherwise specified. Status and reporting visibility for

PR: FD2060-21-31347 PWS REVISION: 0 13

tasks below the Tier 1 level that are defined in the IMS can be included in reviews as required to support program visibility on progress.

4.8.1 Integrated Master Plan (IMP)

The Contractor shall update the IMP as required.

4.8.2 Integrated Master Schedule (IMS)

The Contractor is responsible for the development and delivery to the government of a detail IMS within 15 calendar days after award of contract. The IMS shall be updated at least once per calendar quarter and within 15 calendar days of a significant shift in the program schedule.

4.9 Data Management

The Contractor shall identify, schedule, coordinate, manage, track, and status the development, procurement, and delivery of contractual data items related to this program. The Contractor shall utilize its existing automated exchange, scheduling and tracking tools to provide the data in contract compliant media and formats. (CDRL A008, STATUS REPORT, DI-MGMT- 80368A)

4.9.1 Engineering and Design Data

The Contractors design shall not degrade the structural integrity characteristics of the ARWO console or the aircraft. The physical and electrical interfaces will be maintained.

4.9.2 Reports and Data Deliverables

All reports will be licensed to the U.S. Government at no additional cost. As the documents may contain vendor or Lockheed proprietary data, documents shall be so marked and will be provided with a Government-only Use license. All other data developed specifically for this effort will be provided with an unlimited license. The Contractor is responsible for tracking any system deficiencies and providing the government a report containing all deficiencies (See section 4.3).

4.9.2.1 Test Planning: The Contractor shall host and co-chair Test Plan Working Groups (TPWG) with the government program office and Lead Developmental Test Organization (LDTO). The Contractor test planning shall comply with AFI-99-103, Test and Evaluation- CAPABILITIES-BASED TEST AND EVALUATION. The TPWG shall develop, document and conduct the ground and flight testing and the processes and procedures that shall be required to certify the SFMR DPU updates. Contractor shall be responsible for consolidating a detailed test plan in accordance with requirements and producing the final versions for submission to the government. Test Planning should include provisions for form, fit and function, ground and flight testing, and Contractor certification of G-loading requirements. LDTO and AFLCMC/WLNCC Program Manager shall approve of the SFMR DPU ground and flight test plans required prior to testing. (CDRL A001, SYSTEM/SOFTWARE TEST PLAN; CDRL

A002, SYSTEM/SOFTWARE TEST PROCEDURES)

4.9.2.1.1 Flight Test Support: The Contractor shall provide on-aircraft engineering support during the Government’s flight test. The Government’s flight test will verify EMI

PR: FD2060-21-31347 PWS REVISION: 0 14

compatibility, communication, and applicable requirements specified in paragraph 4.3 thru

4.3.6. Contractor support shall include resolution of any deficiencies related to the installation of the SFMR DPU that occur during the flight test. It is expected that the flight test will take place at Keesler AFB, MS, with a total duration of 5 days (2 days travel, 3 days test). (CDRL

A004, SYSTEM/SOFTWARE TEST REPORT)

4.9.2.1.2 Test/Inspection Report: The Contractor shall submit an Engineering Verification Report (EVR) after completion of all contract testing as identified in the approved ECP.

(CDRL A004, SYSTEM/SOFTWARE TEST REPORT)

4.9.2.1.3 Electromagnetic Test Report: The Contractor shall conduct electromagnetic interference/electromagnetic compatibility (EMI/EMC) EMI/EMC analysis/testing to identify potential WC-130J peculiar Safety of Flight and operational interference. The Contractor shall submit an EMI Test Report.

4.9.2.2 Weight and Balance: The Contractor will develop and provide updated weight and balance data as applicable. (CDRL A005, WEIGHT AND BALANCE REPORT FOR

AIRCRAFT)

4.9.2.3 System Safety Hazard Analysis Report (SSHA): The Contractor will provide an Engineering Change Proposal System Safety Report/Safety Impact Assessment (ECPSSR/SIA) The Contractor will include this ECP during the next update of the SSA.

4.9.4 Commercial Drawings

Pertinent commercial drawings associated with updated SFMR DPU or system components from suppliers will be provided to USG.

4.9.5 Technical Manuals

The government will be updating all the technical manuals and the contractor shall provide all necessary data.

4.9.6 Technical Reports

The Contractor shall provide an update/revision as required to the following Reports

A. Configuration Verification Report (CVR) B. Certificate of Design (CoD)

4.10 Item Unique Identification

4.10.1 Item Identification and Valuation, Unique item identification is a method of marking items with unique item identifiers which have machine-readable data elements. Unique item identification is required for all items to be delivered to the DoD that meet the criteria established in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

4.10.2 In accordance with the Department of Defense Guide to Uniquely Identifying Items Assuring Valuation, Accountability and Control of Government Property, the Government

PR: FD2060-21-31347 PWS REVISION: 0 15

agent or Contractor representative responsible for causing “life cycle events” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update applicable item record(s) in the IUID Registry.

4.11 Packaging

The Contractor shall package and mark material in accordance with the contract (basic and/or order, as applicable) in accordance with the attached Air Force Materiel Command (AFMC) Form 158, Packaging Requirements. The Contractor shall package and mark material in accordance with other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns.

The Contractor shall reuse the packaging in which the items were received, if undamaged, and package and mark material for movement, shipment, receipt and storage in a manner that ensures the protection and preservation of the material for shipment to and storage at the destination. In the event packaging in which the items were received is damaged and unusable, the Contractor shall package and mark material for movement, shipment, receipt and storage in a manner that ensures the protection and preservation of the material for shipment to and storage at the destination. The Contractor shall package electronic parts susceptible to electrostatic discharge damage in accordance with MIL-STD-1686C, Department of Defense Standard Practice / Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices), and MIL- HDBK-263B, Military Handbook / Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices). In accordance with MIL-STD-2073-1E, Standard Practice for Military Packaging, shipping containers received, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reutilization. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

4.12 Delivery of upgraded SFMR DPU’s

Upgraded assets shall be delivered in accordance with the schedule defined by the contract/order.

There shall be no more than one late delivery. The Contractor shall notify the Government if the delivery of any asset will not meet the scheduled delivery date and negotiate a revised delivery date. The late asset shall be delivered by the revised delivery date acceptable to the Government.

The Contractor shall deliver assets to:

800 PHANTOM RD.

BUILDING 4266

KEESLER, AFB 39534

4.12 Travel

Travel requests for Contractor personnel shall be submitted for approval to the PCO prior to costs being incurred and a minimum of five business days in advance of departure. Travel by

PR: FD2060-21-31347 PWS REVISION: 0 16

Contractor personnel shall be conducted in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.0 General Information

5.1 Continuation of Mission-Essential Services during a Crisis The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with all security regulations and clauses listed in the contract.

5.2.1 Operations Security (OPSEC)

The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-M to protect U.S. Government interests.

5.2.2 Security Regulations

The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.) Government interests.

5.2.3 Security Clearance/Controlled Unclassified Information (CUI) Actual knowledge and/or generation of classified information and/or CUI are not expected to be necessary for performance of the contract/order. However, Contractor personnel are required to comply with security requirements to preclude potential security incidents or violations IAW DoDM 5200.01, Volume 4, DoD Information Security Program: CUI, Enclosures 3 & 4, for identification, protection and Contractor personnel training requirements of CUI. It is not expected Contractor personnel will require security clearances for proper accomplishment of contract/order requirements. Contractor personnel shall not be authorized access to classified information and/or CUI and classified items or be permitted to work on classified projects and/or programs without a valid security clearance and a need-to- know. If security clearances become necessary after contract/order award, the Contractor shall ensure applicable Contractor personnel obtain valid security clearances appropriate to the access required for proper accomplishment of contract/order requirements and shall train personnel and accomplish out-processing procedures identified in DoDM 5200.01, Volume 4, Enclosure

4. The Contractor shall comply with DoD 5400.07, Freedom of Information Act (FOIA), and AFI 16-1404, AF Information Security Program, for requirements. Protection of unclassified DoD information not approved for public release on non-DoD Information Systems will be protected IAW DoDI 8582.01, Security of Unclassified DoD Information on non-DoD Information Systems, Enclosure 3.

PR: FD2060-21-31347 PWS REVISION: 0 17

5.2.4 Security Incident or Violation

The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.5 Security of Contractor System(s)

The Contractor shall ensure the security of Automated Information System(s) (AIS) at the Contractor’s facility to preclude potential security incidents or violations.

5.2.6 Access to Government System(s)

Access to Government system(s) will not be required to perform tasks under the contract/order.

5.2.7 Access to Government Facility or Military Installation

The Contractor shall ensure Contractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation. The Contractor shall ensure Contractor personnel who require access to a USAF installation comply with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.3 Safety Requirements

5.3.1 Contractor Compliance

The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, as amended by Public Law 101-552 [Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).

5.3.2 Mishap Notification/Investigation

In accordance with AFI 91-204, Safety Investigations and Reports, the Contractor shall report mishaps involving damage or injury to USAF interests. The Contractor shall ensure the USAF is notified of mishaps. The Contractor shall contact the Contracting Officer’s Representative (COR), if available, or another MFT member by telephone within 8 business hours and the Contractor shall cooperate with USAF safety investigations.

5.3.3 Inspection of Services

Definition. “Services,” as used in this clause, includes services performed, workmanship, and material furnished or utilized in the performance of services (FAR 52.246-4). Inspection of Services will be accomplished in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The Government reserves the right to inspect Contractor performance.

5.3.4 Trafficking in Persons

The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the

PR: FD2060-21-31347 PWS REVISION: 0 18

site for the Department of State’s Office to Monitor and Combat Trafficking in Persons.

http://www.state.gov/j/tip

5.4 Contractor Manpower Reporting

5.4.1 In accordance with 10 United States Code 2330a, the Contractor shall provide an annual count of contractor/subcontractor personnel performing work for each fiscal year if the DoD is the requiring activity and if the acquisition is in excess of $3,000,000.00. The Contractor shall report all Contractor direct labor hours, including subcontractor direct labor hours, required for performance of the services provided under the contract in the Enterprise-wide Contractor Manpower Reporting Application (eCMRA). Reporting shall be conducted for each fiscal year, which extends October 1 through September 30. While inputs may be made any time during the fiscal year, all data shall be reported no later than October 31 of the following fiscal year.

The Contractor shall establish a record for the contract/order in eCMRA no later than 30 calendar days after contract/order award. The Contractor shall enter Order Data, Contact Data and Location Data. Data for Air Force service requirements must be input at the Air Force CMRA link. Additional information and user manuals for government personnel and contractors are available at the CMRA link at http://www.ecmra.mil.

5.5 Invoicing/Payment and Receipt/Acceptance

The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area WorkFlow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) IAW all applicable clauses located in the basic contract.

5.6 Quality Control Plan/Quality Management System (QMS)

The Contractor shall ensure the quality of services through an internal quality and/or inspection system. The Contractor shall submit a copy of their internal quality and/or inspection system.

6.0 Appendices

6.1 Appendix A: References

Publication Title of

Publication Date of Publication Section(s) that Apply

AFI 10-403 Deployment Planning and Execution

20 September 2012 Change 1 – 29 April 2013 http://www.e-publishing.af.mil/

Paragraph 1.9.1.33

AFI 17.101 Risk Management Framework for AF IT

2 February 2017 Entire

AFI 91-204 Safety 9 August 2012 Paragraphs Investigations and reissued 8 April 2013 1.3.1.1, http://www.state.gov/j/tip http://www.ecmra.mil/ http://www.e-publishing.af.mil/

PR: FD2060-21-31347 PWS REVISION: 0 19

Reports 2.4.6.1.1-http://www.e-publishing.af.mil/ 2.4.6.1.2

AFI 99-103 Test and Evaluation

16 October 2013 Entire

AFMC/CV

Policy Letter

Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force Installations

1 Aug 07 Entire

AFPAM 91-210 Contract Safety 14 February 1994 certified current 6 January 2012 http://www.e-publishing.af.mil/

Pages 7-9

Assistant Secretary of the Air Force Policy Letter

Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force

11 Dec 06 Entire

None Defense Contingency COR Handbook

Version 2 September 2012 http://www.acq.osd.mil/dpap/ccap/cc/corhb/ Fi les/DCCOR_Handbook_2012.pdf

Section on Combating Trafficking in Persons in Chapter 8, Monitoring the Contractor

DoD 5200.02-R Personnel Security Program

21 March 2014 Change 1 - 9/9/2014 http://www.dtic.mil/whs/directives/corres/pu b 1.html

Entire

DoDD 4715.1E Environmental, Safety, and Occupational Health (ESOH)

March 19, 2005 http://www.dtic.mil/whs/directives/corres/pu b 1.html

Entire http://www.e-publishing.af.mil/ http://www.e-publishing.af.mil/ http://www.acq.osd.mil/dpap/ccap/cc/corhb/Fi http://www.acq.osd.mil/dpap/ccap/cc/corhb/Fi http://www.dtic.mil/whs/directives/corres/pub http://www.dtic.mil/whs/directives/corres/pub http://www.dtic.mil/whs/directives/corres/pub

PR: FD2060-21-31347 PWS REVISION: 0 20

DoDD 5205.02E

DoD Operations Security

(OPSEC)

Program

June 20, 2012 http://www.dtic.mil/whs/directives/corres/pu b 1.html

Entire

DoD Manual 5205.02-M

DoD Operations Security

(OPSEC)

Program Manual

November 3, 2008 http://www.dtic.mil/whs/directives/corres/pu b 1.html

Entire

E.O. 13423 Strengthening Federal Environmental, Energy, and Transportation Management

January 24, 2007 http://www.gpo.gov/fdsys/pkg/FR-2007-01- 26/pdf/07-374.pdf

Entire

E.O. 13514 Federal Leadership in Environment, Energy, and Economic

5 October 2009 http://www.whitehouse.gov/assets/documents/ 2009fedleader_eo_rel.pdf

Entire

FAR and supplements

Federal Acquisition Regulation http://farsite.hill.af.mil

Sections applicable to contract and

PWS

OSD

Memorandum

Enterprise-wide Contractor Manpower Reporting Application

Nov 28 2012 http://www.acq.osd.mil/dpap/policy/policyv ault/Enterprise-wide_Contractor_Manpower_Reporting_Ap

Entire

Public Law 91-

Occupational Safety and Health Act of 1970

December 29, 1970 as amended through January 1, 2004 http://www.osha.gov/pls/oshaweb/owadisp.s how_ d ? id 2743& bl OSHACT

Entire

SAF/AQ

Memorandum

Implementation of FY11 NDAA Section 8108, Contractor Inventory

Nov 13 2012 https://cs.eis.af.mil/airforcecontracting/kno wledge _center/Documents/AFFARS_Library/5337/ f df

Entire

USD

Memorandum

Establishment of the DoD Green Procurement Program

August 27 2004 http://www.wbdg.org/pdfs/dod_gpp_082704 .pdf

Entire

Publication Title of Publication

Date…