PWSWCMDEngineeringSupportrev1.pdf

WCMD ENGINEERING SUPPORT

Performance Work Statement For

Wind Corrected Munition Dispenser (WCMD) Engineering Support

13 July 2021

Prepared By: Dewey Hayes Area Attack Program Manager AFLCMC/EBHCA

Table of Contents

1.0 DESCRIPTION OF SERVICES

2.0 WCMD FLIGHT TESTING SUPPORT

3.0 SOFTWARE & ENGINEERING SERVICES SUPPORT

4.0 AGING AND SURVEILLANCE SUPPORT

5.0 SERVICE SUMMARY

6.0 REPORTS

7.0 GOVERNMENT-FURNISHED PROPERTY (GFP)

8.0 GENERAL INFORMATION

9.0 SECURITY REQUIREMENTS

10.0 QUALITY CONTROL

11.0 GOVERNMENT OBSERVATIONS AND PARTICIPATION

12.0 CONTRACT DATA REQUIREMENTS LIST – (CDRL’s)

1.0 DESCRIPTION OF SERVICES

1.1 Scope: The purpose of this contract is for engineering services support on Wind Correction Munitions Dispenser (WCMD) systems and associated munition systems components necessary to support Weapon System Evaluation Program (WSEP), Aging & Surveillance flight testing, and munition component testing/analysis that are key to determine inventory health and warfighter readiness. The software and engineering services supports WCMD systems test and overall aircraft WCMD interface, including mission planning, Operational Flight Program (OFP) requirements, and System Support Simulator (SSS). The contractor shall provide technical and engineering support for aircraft integration, maintain WCMD ICD's, support ground/flight testing, system component testing, cybersecurity monitoring and software/hardware support for platforms that fly WCMD systems. As applicable, the proposal shall be based on typical and upcoming support requirements.

2.0 WCMD FLIGHT TESTING SUPPORT

2.1 The contractor shall support five WCMD flight tests at different test locations to include but not limited to Hill AFB Utah Test and Training Range (UTTR), Eglin AFB, FL Test and Training Range, and Tyndall AFB, FL.

2.2 The contractor shall install the telemetry kits and validate functionality with Government owned Lumistar and CMBRE equipment for the flight tests. Telemetry installations are accomplished the week prior to flights. Telemetry installations and functional validation may be required at an alternative aircraft location other than Hill AFB, Eglin AFB, or Tyndall AFB for each flight test based on airframe departure location. The Government will provide and ship the Telemetry Kits to the location needed for installation prior to need date.

2.3 The contractor shall provide on-site technical support in the Mission Control Center (MCC) for telemetry data collection in support of captive integration, and free flight missions.

2.4 The contractor shall provide engineering analysis of flight test data and anomalies by analyzing WCMD telemetry/Lumistar equipment data. The Contractor shall provide a flight test report. (CDRL A001: DI-MISC- 80508B, Technical Report Services)

3.0 SOFTWARE & ENGINEERING SERVICES SUPPORT

3.1 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-15, F-16 and F-

35. The support shall include the following activities:

3.1.1 The contractor shall provide support for aircraft integration activities.

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

3.1.2 The contractor shall provide maintenance for WCMD SSS and WCMD tail simulators. 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.

3.1.3 The contractor shall update 6DOF/3DOF support equipment for software/hardware obsolescence and cyber security requirements.

3.2 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. ICWG’s shall not exceed 150 hours. The contractor shall provide technical support for aircraft listed in paragraph 3.1 of this PWS and other Air Force aircraft as directed. (CDRL A002: DI-SESS-81248B, Interface Control Document (ICD))

3.3 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), and Windows OS (Operating System) future upgrades.

3.4 Software Integration Lab (SIL) Support: 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. 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.

(CDRL A003: DI-AVCS-80700A, Computer Software Product End items)

3.5 Weapon Simulator Support: 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.6 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 and hardware or provide flight path reconstructions for detailed analysis of test flights (i.e. WSEP analysis).

4.0 AGING AND SURVEILLANCE SUPPORT

4.1 The contractor shall provide surveillance teardown support and component testing support for Area Attack Munitions. This effort shall be performed on Government selected munitions systems with system teardowns at McAlester AAP and China Lake Naval Air Weapons Station. The government requires 20 teardowns within a 12-month period of performance (PoP).

4.2 The contractor shall conduct work efforts consisting of supporting teardown and component testing of 10 each CBU-87 CEM, and 10 each CBU-89 Gator munition systems and system components. Test assets will be selected by the government for teardown/test to be accomplished at designated government facilities. The contractor shall track test results with historical test information. The contractor shall assist the government with selection of system lot numbers for component and flight test based on historical test data.

4.3 The contractor shall perform wind tunnel testing on sub munition decelerators for

Ram Air Decelerators (RADs) and/or Air Inflatable Device (AIDs).

4.4 The contractor shall assist the government with tasks associated with teardown test equipment located at McAlester Army Ammunition Plant (CEM) and China Lake Naval Air Weapons Station (Gator). Two efforts will not exceed 3 days of onsite support.

4.5 The contractor shall provide an overall technical assessment report following completion of all testing activities. (CDRL A001: DI-MISC- 80508B, Technical Report Services)

5.0 SERVICE SUMMARY

Required Services (Tasks)

Performance Standards

Acceptable Quality Levels

Methods of

Surveillance

PWS: 2.0

WCMD Flight Testing Support

PWS: 3.0

Software & Engineering Support

PWS: 4.0

Aging & Surveillance Support

100 % Performance IAW schedule jointly developed between the Government and the Contractor jointly developed between the jointly developed between the

98%

Documentation reviews, periodic inspections, test participation and observations.

File reviews, periodic inspections, and observations.

Documentation reviews, periodic inspections, test participation and observations.

6.0 REPORTS

All reports must meet industry standards and the requirements of the contract data requirements list.

7.0 GOVERNMENT-FURNISHED PROPERTY (GFP)

7.1 GFP Provided: All required GFP/GFE for this contract will be provided by the

USAF.

7.2 Inventory and Reporting: All GFP/GFE for this contract will be managed and inventoried by the contractor. (CDRL A004: DI-MGMT-80441D, Government Property Inventory Report)

8.0 GENERAL INFORMATION

8.1 Delivery Schedule: Products and services shall be delivered on a schedule jointly defined by the AFLCMC/EBHCA Program representative and the contractor.

8.2 Period of Performance: This contract will have a 12 month period of performance beginning in September 2021.

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

8.4 The contractor shall host Program Management Reviews (PMR) on an Annual basis and Technical Interchange Meetings (TIM) Bi-annually. The contractor shall participate in an annual CMBRE PMR. (CDRL A005: DI-MGMT- 80368A, Status Report)

8.5 Travel Requirements: Travel conducted by the contractor shall be included in the contract effort. The contractor shall request travel approval from the Contracting Officer.

9.0 SECURITY REQUIREMENTS

9.1 Security Management: The Contractor shall comply with the security requirements specified in the DD Form 254, Contract Security Classification Specification. The Contractor shall flow down the security requirements to subcontractors as applicable. For further information on how to obtain a facility security classification please refer to this link to DCSA:

https://www.dcsa.mil/mc/ctp/fc/

9.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 http://www.dcsa.mil/mc/ctp/fc/

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.

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

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

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

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

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

10.0 QUALITY CONTROL

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

10.2 Quality Assurance: The government’s Contracting Officer’s 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.

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

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

10.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).

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

11.0 GOVERNMENT OBSERVATIONS AND PARTICIPATION

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

11.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 A006: DI-GMT-80555A, Program Progress Report)

12.0 CONTRACT DATA REQUIREMENTS LIST – (CDRL’s)

A001 DI-MISC-80508B, Technical Report Services 2.4, 4.5, 11.0 A002 DI-SESS-81248B, Interface Control Document (ICD) 3.2, 11.0 A003 DI-AVCS-80700A, Computer Software Product End items 3.4, 11.0 A004 DI-MGMT-80441D, Government Property Inventory Report 7.2, 11.0 A005 DI-MGMT-80368A, Status Report 8.4, 11.0 A006 DI-MGMT-80555A, Program Progress Report 11.2, 11.0