WCMDPWS.pdf

Performance Work Statement

Engineering Services

For

Wind Corrected Munitions Dispenser (WCMD)

Prepared By: Program Manager

AFLCMC/EBHCA

21 May 2020

Table of Contents Section Title Page Number

1.0 Scope 2

2.0 Flight Testing 2

3.0 Engineering Services & Technical Support 3

4.0 Travel Requirements 6

5.0 General Information 6

6.0 GFE Aircraft Integration 6

7.0 Service Summary 6

8.0 Security Requirements 8

9.0 Quality Control 10

10.0 Government Observations and Participation 11

11.0 Contract Data Requirements List (CDRLs) 11

1.0 Scope: The purpose of this Performance Work Statement (PWS) is to describe the engineering services necessary for the support of the WCMD System. The WCMD System support consist of Weapon System Evaluation Program (WSEP), Aircraft Integration Testing, Surveillance Flight Testing, and engineering/technical support services for WCMD System Support Simulators (SSS) within Aircraft System Integration Labs (SIL). The level of engineering experience is defined as at least three years of the last five years specific engineering accomplishing WSEP, Aircraft Integration, Flight Testing, and engineering/technical support on the WCMD System. *Please note that the contractor will need to coordinate with OEM in regards to a no fee, terms and conditions Special License for IP/TDP Software specific to WCMD Program. Additionally, should support events be less than expected, support effort for comparable events identified in this PWS shall be supported as determined by the Air Force WCMD Program Office.

2.0 Flight Testing

2.1 WSEP Testing, Surveillance and Aircraft Integration Flight Testing

2.1.1 The contractor shall support four WCMD flight tests per year using engineers with specific WCMD experience as defined in section 1.0. Two tests at Hill AFB Utah Test and Training Range (UTTR), two tests at Eglin AFB, FL Test and Training Range with WCMD telemetry install and support at Tyndall AFB, FL.

2.1.2 The contractor shall be required to install the telemetry kits and validate functionality with Government Lumistar and CMBRE equipment for the flight tests.

Telemetry installations are accomplished the week prior to flights. Telemetry installations and functional validation may be accomplished at an alternative aircraft location other than Hill AFB, Eglin AFB, or Tyndall AFB for each flight test based on airframe departure location.

2.1.3 The contractor shall provide on-site technical support to include installation and checkout of telemetry instrumentation kits and WCMD tail kits, Mission Control Center (MCC) support utilizing engineers with specific experience as defined in section 1.0 supporting WCMD and WCMD telemetry, Lumistar data collection in support of captive integration, and free flight missions.

2.1.4 The contractor shall provide engineering analysis of flight test data and anomalies utilizing engineers with specific experience as defined in section 1.0 analyzing WCMD tail performance and WCMD telemetry data and Lumistar equipment. The Contractor shall provide a flight test report. (CDRL A001: DI-MISC-80508B, Technical Report Services)

2.1.5 The contractor shall support Failure Review Board (FRB) activities to include providing reports and data relevant to anomaly or incident for WCMD on the following F- 15, F-16, A-10, B1-B, B-52, and F-35 Joint Strike Fighter (JSF) aircraft within 20 days of failure occurrence. (CDRL A001: DI-MISC-80508B, Technical Report Services)

2.1.6 The contractor may be required to support a WCMD aging and surveillance or WCMD aircraft integration support flight test required by the program office. Government conducted ground and flight testing will include captive carry and launch. Flight testing should be planned for Eglin AFB; Edwards AFB, Hill AFB; or Nellis AFB.

2.1.7 The contractor shall provide on-site technical support to include telemetry installation and validate telemetry functionality with Government Lumistar and CAMBRE equipment for the flight tests at Hill AFB; Nellis AFB; Eglin AFB; Tyndall AFB or otherwise specified from the Program Office. Telemetry installations are accomplished the week prior to flights.

3.0 Engineering Services & Technical Support

3.1 The contractor shall provide support related to aircraft integration, mission planning, weapon engineering support and flight test support efforts on all WCMD capable aircraft as directed. Additionally, support will include software certification for Weapons Simulator Unit (WSU), Simulator System Support (SSS), Dual Simulator System Support (DSSS) issues or repairs, failure analysis, maintenance of non-warranted WCMD tail kits, WCMD system training, analysis of operational field issues and technical order updates. (CDRL A002: DI-IPSC-81442A, Software Version Description (SVD))

3.2 Aircraft Integration: The contractor shall provide technical support for the integration efforts on the following aircraft: A-10, B-1, B-2, B-52, F-15E, F-16 BLK30, F-16 BLK 40/50 and F-35 Joint Strike Fighter (JSF). The support shall include the following activities:

3.2.1 The contractor shall provide support for aircraft integration activities using engineers having at least three years of experience within the past five years supporting WCMD aircraft integration: efforts shall include software interface updates between aircraft and weapon system that occur due to aircraft upgrades, weapon system improvements, Common Munitions Built in Test Reprogramming Equipment (CMBRE), Munitions Application Program (MAP), Mission Planning updates or deficiencies, or additional compatibility requirements. Four each, five day events (160 hours) are expected to be supported by the contractor as directed by Government.

3.2.1.1 CMBRE SLEP MAP Project: The WCMD Program Office will require a CMBRE SLEP MAP integration project within 60 days from contract award date as outlined in attached Addendum. The Contractor shall coordinate with WCMD Program Office and CMBRE Program Office and provide a detailed scope identifying the level of effort to include: expertise required; hours broken down by tasks;

schedule outlining how each phase will be completed; and deliverable closeout of the overall project.

3.2.1.2 Initial Meeting: A meeting shall take place with Contractor, WCMD Program Office and CMBRE Program Office within 15 days of Project award date to discuss the details of what equipment will be shipped to the contractor's facility, review user documentation, review DCSA system, review development environment, CMBRE SLEP Programmer’s Manual For Munition Application Program (MAP) Developers Guide, and provide readiness, feedback, and suggestions. (CDRL A003: DI-MGMT-80227, Contractor’s Progress, Status and Management Report)

3.2.1.3 Prototype MAP: CMBRE Program Office and Contractor shall coordinate to identify the scope of migration of existing ADA CMBRE functionality to new C++ framework hardware. Implement basic display functionality (legacy menu to new window framework), translate ADA TAU interface, translate ADA 1553 communication functionality, (ACE4 to AcExtreme), perform weapon BIT, and basic data logging to a CD. (CDRL A002: DI-IPSC-81442A, Software Version Description (SVD)) (CDRL A004: DI-SESS-81248B, Interface Control Document (ICD))

3.2.1.4 Close Out: Contractor shall provide a prototype demo to the WCMD & CMBRE Program Offices at the Contractor facility location. The contractor shall identity the lessons learned in this demo and review issues encountered during the migration and development phase. A demonstration of the new MAP functionality utilizing CMBRE and the WCMD Tail Kit will be required to display success. (CDRL A005: DI-ADMN-81373, Presentation Material)

3.2.1.5 Produce a Fieldable MAP for DT and OT: The task of creating a fieldable MAP shall be placed on the contractor to produce finalized displays and data entry functionality (User MAP and Contractor MAP), 1553 communication functionality, TAU API self-test, weapon BIT (fully translated ADA BIT routine), data logging (translate ADA log file capabilities), and regression testing. Lastly, the contractor is required to update documentation as stated in following: W Requirements Spec - 75845412, Test Procedure - CP3_200000604-001, Test Report, Version Description Document, Media Drawing, User's Manual- CP3_MAU3000000-001, and Tech Order

- USAF Task. (CDRL A006: DI-MCCR-80700A, Computer Software Product End items)

3.2.2 The contractor shall provide maintenance for WCMD SSS and WCMD tail simulators using engineers having at least three years of experience within the past five years supporting WCMD SSS and tail simulators in aircraft SIL's: Maintenance and repair of simulators include circuit card repair, software upgrades and anomaly resolution, troubleshooting, cable repair, and alterations necessary from aircraft hardware or software upgrades or technical changes. Three each, five day events (120 Hours) are expected to be supported by the contractor as directed by Government.

3.2.3 Host Program Management Reviews (PMR) on an Annual basis and Technical Interchange Meeting (TIM) Bi-annually. (CDRL A007: DI-MGMT- 80368A, Status Report)

3.2.4 Host Test Readiness Reviews (TRR). Two TRR Meeting to be hosted at the contractor facility. (CDRL A007: DI-MGMT-80368A, Status Report)

3.3 Interface Management & Additional Aircraft Integration Support:

The contractor shall support the continual WCMD interface control process: to include updating the Interface Control Document (ICD), accept and evaluate interface change notices, distribute change pages and support Interface Control Working Group (ICWG) meetings as required using engineers having at least three years of experience within the past five years.

ICWG’s shall not exceed 80 hours per year. The contractor shall provide technical support for aircraft listed in paragraph 2.1.5 of this PWS and other Air Force aircraft as directed. (CDRL A004: DI-SESS-81248B, Interface Control Document (ICD))

3.4 WCMD Aircraft Integration Integrated Product Team (IPT):

This effort will be supported with continuous aircraft integration oversight, task management and task execution determined by the contractor and coordinated with Government Program Office IPT using engineers with specific WCMD experience as defined in section 1.0. Four each, three day IPT events are expected.

3.4.1 Authorization for the IPT lead and for supporting IPT members shall be required to coordinate and perform general aircraft integration, mission planning and flight test support activities.

3.4.2 Efforts performed by the IPT lead or any supporting IPT members for a specific platform or specific tasking will be charged to the specific authorization associated with that platform or tasking IAW Section H of the contract.

3.4.3 All general oversight, process management and general integration efforts by the IPT lead will be charged to the associated authorization clause of the contract.

3.4.4 The contractor shall provide maintenance, storage, tracking, the repair and disposition recommendations for WCMD program GFE hardware and associated software, including sub-tier supplier GFE as identified in the GFE list of this contract.

(CDRL A008: DI-MGMT-82173, Government Furnished Equipment (GFE) Inventory Report) (CDRL A009: DI-MGMT-80441C, Government Property Inventory Report)

3.5 Mission Planning: The contractor shall provide mission planning to include the support required to maintain existing WCMD PC weapon planning module (WPM), integrated with the Portable Flight Planning System (PFPS), WCMD Fly-Out- Models (FOM’s), Windows OS (Operating System) future upgrades and any sustaining engineering tasks utilizing engineers having with specific experience as defined in section 1.0. Two each, five day Mission Planning events are expected to be supported.

3.6 Software Integration Lab (SIL) Support, Maintenance and Upgrades:

The contractor shall provide support and maintenance of existing WSU’s, SSS’s, DSSS’s and tail kit simulators using engineers having with specific experience as defined in section

1.0 working with a WCMD SIL. Contractor support will include updates of software and hardware for platforms as identified under section 3.2 and shall include but not limited to the following activities. Six each, five day SIL support events are expected to be supported.

(CDRL A006: DI-MCCR-80700A, Computer Software Product End items)

3.6.1 The contractor shall maintain and repair existing WSU’s, SSS’s, DSSS’s and WCMD tail kit simulators at government locations. Note: WCMD software is utilized on Joint Air-To-Surface Standoff Missile (JASSM) SSS hardware. The contractor shall provide aircraft support for upgrading or new manufacture of SSS’s with the current SSS supplier in support of aircraft SIL’s. The contractor shall have the capability to obtain support from the JASSM contractor as required for WCMD Icon and WCMD software interface utilized on JASSM SSS’s for aircraft SIL support.

3.6.2 The contractor shall update existing WSU, SSS and DSSS operating systems, host PC, Avionics Components, Monitor, Keyboard or Case as required and update simulator unit at government locations.

3.6.3 The contractor shall provide technical, engineering and production support to update, redesign or upgrade WCMD weapon simulators to include producing simulators of current or upgraded designs. Support shall include maintenance or refurbishment of existing simulators, modification, redesign or improvements to the simulator and address parts obsolescence, diminishing manufacturing sources, simulator requirement changes and other problems preventing effective maintenance or procurement of weapon simulators.

3.7 WCMD Tail Fin Release Lanyard Repair: The contractor shall repair WCMD tails that have had the Lanyards pulled by accident during downloads. The contractor shall have specific tools for this process that will allow the government to recover WCMD tails that would otherwise have to be discarded. A detailed status report shall be required from contractor for all required lanyard repairs. One, three-day repair event is expected by the contractor. (CDRL A007: DI-MGMT-80368A, Status Report)

3.8 Hardware In The Loop (HWIL) Support and Update: The contractor shall support the HWIL and ensure that it maintains the ability to update WCMD software (including FMS Country ID for SFW production) and hardware or provide flight path reconstructions for detailed analysis of test flights (i.e. WSEP analysis) utilizing engineers that having specific WCMD experience as defined in section 1.0 supporting WCMD HWIL requirements. Three each, four day HWIL events are expected by the contractor. *Please note that the contractor will need to coordinate with OEM in regards to a no fee, terms and conditions Special License for HWIL equipment/training specific to WCMD Program.

4.0 Travel Requirements: Travel conducted by the contractor shall be included in the contract effort. The contractor shall request from the program government office and contracting office approval for travel.

5.0 General Information

5.1 Delivery Schedule: Products and services covered under this contract shall be delivered on a schedule jointly defined by the AFLCMC/EBHCA program representative and the contractor.

5.2 Period of Performance: FY 2020 - FY 2021

5.3 Government Inspection and Acceptance of Deliverables: The government program representative will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the contractor will be notified in writing by the government of the specific reasons why the deliverable was rejected. The contractor shall have 30 calendar days to correct the rejected deliverable and resubmit to the government for re-inspection. If no comments are provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the government. (CDRL A001: DI-MISC-80508B, Technical Report Services)

6.0 GFE/GFP: All required GFE/GFP for this contract will be provided.

7.0 Service Summary (SDS)

ATTACHMENT 1: PERFORMANCE REQUIREMENTS SUMMARY

Required Services

(Tasks)

Performance

Standards

Acceptable Quality Levels

Methods of

Surveillance

PWS: 3.2

Aircraft integration 100 % Performance 98% Documentation IAW schedule reviews, periodic jointly developed inspections, and test between the participation and Government and the observations.

Contractor

PWS: 3.2.2

System Integration 100 % Performance 98% File reviews, Lab (SIL) IAW schedule periodic inspections, jointly developed and observations.

between the Government and the Contractor

PWS: 3.6

WSU, SSS and 100 % Performance 98% Documentation DSSS Support, IAW schedule reviews, periodic Maintenance and jointly developed inspections, and Upgrades between the observations

Government and the

PWS: 3.7

100 % Performance 98% Periodic inspections, IAW schedule and test participation

WCMD Tail Fin jointly developed Release Lanyard between the Repair Government and the

100 % Performance

98%

Documentation

PWS: 3.8 IAW schedule reviews, periodic WCMD HWIL jointly developed inspections, and test Support and between the participation and Update Government and the observations.

8.0 Security Requirements

8.1 Security Management: The Contractor shall comply with the security requirements specified in the Contractor’s DD Form 254, Contract Security Classification Specification. The Contractor shall flow down the security requirements to subcontractors as applicable. The Contractor shall ensure they get their cage code registered with Defense Counterintelligence Security Agency (DCSA) to be able to store/process classified material.

8.2 Operations Security (OPSEC): The contractor shall ensure OPSEC is incorporated into the performance of the contract IAW DoD Directive 5205.02E, DoD Operations Security (OPSEC) Program and AFI 10-701 Air Force OPSEC Program. The Contractor shall flow down all OPSEC requirements to subcontractors that handle Critical Information (CI). CI is defined as specific facts about friendly intentions, capabilities, or activities needed by adversaries to plan and act effectively against friendly mission accomplishment.

8.3 Controlled Unclassified Information (CUI): The Contractor shall comply with DoDM 5200.01, Volume 4, DoD Information Security Program: CUI, Enclosures 3 & 4, for identification, protection and training requirements of CUI. The contractor shall be responsible for training their personnel and accomplishment of the out-processing procedures identified in DoDM 5200.01, Volume 4, Enclosure 4. The contractor shall comply with DoDM 5400.07/Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program 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. The Contractor shall distribute controlled unclassified information IAW DoD Instruction 3200.14, Principles and Operational Parameters of the DoD Scientific and Technical Information Program, and DoD Instruction 2040.02, International Transfer of Technology, Articles, and Services. The Contractor shall properly mark all such documents IAW DoD Instruction 5230.24, Distribution Statements on Technical Documents.

Technical documents not subject to distribution are defined in DoD Instruction 5230.24, DoD Directive 5230.25, and DoD Manual 5010.12-M, Procedures for the Acquisition and Management of Technical Data.

8.4 Program Protection Plan (PPP): Program Protection Planning and Implementation: The contractor shall support the government by developing/updating the Program Protection Plan (PPP) to address the required elements in accordance with the guidance provided in AFPAM 63-113. After final government approval of the PPP, the contractor shall produce a Program Protection Implementation Plan (PPIP). Additionally, the contractor shall support annual Inspections consisting of a review of contractor/subcontractor implementation of the government furnished program protection plan, is required at the government’s discretion. (CDRL A001: DI- MISC-80508B, Technical Report Services)

8.5 Critical Program Information (CPI) Identification/Protection: The contractor shall identify CPI and Resident CPI (formerly called Critical Technology) which need to be protected.

The CPI identified shall be approved by the USG Program Manager. The CPI identification shall include a review of the system, unique integration, support equipment and the Non-Resident design/process/material aspects of the program. All identified CPI shall be protected with appropriate countermeasures. In the case of Resident CPI the use of Anti-Tamper shall be considered and documented in an Anti-Tamper Recommendation Report in accordance with the DAG Chapter 13 and DoDI 5200.39. The contractor shall identify system security engineering requirements in the contractor’s Requirements Management Specification, write Test Plans and accomplish Verification Testing to mitigate protection risks to an appropriate level. (CDRL A001: DI-MISC-80508B, Technical Report Services)

8.6 Criticality Analysis: The contractor shall accomplish a critical design analysis in accordance with the DAG Chapter 13 and DoDI 5200.44. The criticality analysis shall show traceability from the mission threads to the supporting subsystems, critical functions/processes and ultimately identify Critical Components (CC). The CC shall subsequently be identified as level I through level IV critical. The contractor shall identify current risk and recommend supply chain countermeasures for all level I and II CC, to include alternate components as needed. (CDRL A001: DI-MISC-80508B, Technical Report Services)

8.7 Security Classification Guide (SCG): The contractor shall follow the CBU-WCMD Security Classification Guide (SCG) and all security classification guides of systems/information associated with the program for derivative classification, identification of the level and duration of classification for specific information elements, and public release requirements.

8.8 Communications Security (COMSEC): The Contractor and Sub-contractors shall establish a COMSEC account and appoint a COMSEC custodian. The Contractor shall request, maintain, and store all COMSEC material needed to support development and testing.

8.9 Personnel Security: The Contractor shall ensure applicable Contractor personnel have security clearances at the appropriate level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items.

8.10 Security Incidents and Violations: The Contractor shall 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 assessments of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Information will be reported IAW DFARS Clause 252.204-7012

8.11 Common Access Card (CAC): The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)] The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

9.0 Quality Control

9.1 Quality Control Program: The contractor shall establish a Quality Control Program to ensure the requirements of this contract are provided as specified.

9.2 Quality Assurance: The government’s Contracting Officer Representative (COR) and technical representative for this contract will be identified with the contract award. The government will periodically evaluate the contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The government representative will evaluate the contractor’s performance. The government may evaluate each test task as it is completed.

9.2.1 The COR is a representative of the contracting officer and will participate in the administration of this contract. Subsequent to contract award, the identity of the COR will be furnished to the contractor.

9.2.2 The COR or alternate(s) will inform the contract manager in person when discrepancies occur and will request corrective action. The COR or alternate(s) will make a notation of the discrepancy with the date and time the discrepancy was noted and will request the contract manager (or authorized representative) initial the entry.

9.2.3 Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contracting Officer and not to the COR(s)

9.2.4 The services performed by the contractor shall be subject to review by the Contracting Officer or authorized representative(s) during the period of this contract at all times and places.

10.0 Government Observations and Participation

10.1 Government Observations: Government personnel, other than contracting officers CO(s) and COR(s), may from time to time, with CO coordination, observe contractor operations.

10.2 Government Participation: The government shall be allowed to participate in all aspects of testing at contractor or government facilities. The contractor shall provide a test schedule no later than 30 days prior to testing and coordinate its activities with the government.

(CDRL A010: DI-GMT-80555A, Program Progress Report)

11.0 Contract Data Requirements List (CDRLS)

CRDL Data Requirement listing PWS Section A001 DI-MISC-80508B, Technical Report Services 2.1.4, 2.1.5, 5.4, 8.4, 8.5, 8.6

A002 DI-IPSC-81442A, Software Version Description (SVD) 3.1, 3.2.1.3

A003 DI-MGMT-80227, Contractor’s Progress, Status and Management Report 3.2.1.2

A004 DI-SESS-81248B, Interface Control Document (ICD) 3.2.1.3, 3.3

A005 DI-ADMN-81373, Presentation Material 3.2.1.4

A006 DI-MCCR-80700A, Computer Software Product End items 3.2.1.5, 3.6

A007 DI-MGMT-80368A, Status Report 3.2.3, 3.2.4, 3.7

A008 DI-MGMT-82173, Government Furnished Equipment (GFE) Inventory Report

3.4.4

A009 DI-MGMT-80441C, Government Property Inventory Report 3.4.4

A010 DI-MGMT-80555A, Program Progress Report 10.2