Attachment_1_Performance_Work_Statement.pdf

CUI

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIRCREW FLIGHT EQUIPMENT TEST EQUIPMENT (AFETE)

PRODUCTION AND REPAIR

REPAIR PR Number: FD2060-23-32892 PRODUCTION PR Number: FD2060-23-32891

Date: June 9, 2023

Distribution Statement D – Distribution authorized to the Department of Defense (DOD) and U.S. Contractors only for administrative or operational use; 09 March 22. Other requests must be referred to AFLCMC/WNU, Sustainment.

Department of Air Force

Warner Robins Air Logistics Complex Human Systems Division

AFLCMC/WNU, Sustainment 235 Byron Street, Suite 19A

Robins AFB GA 31098

1.0 Description of Services

1.1 Objective: The purpose of this Performance Work Statement (PWS) is for the Contractor to provide support, expertise, capabilities, engineering, and technical services to support the production and repair of Aircrew Flight Equipment Test Equipment (AFETE). This document incorporates the Contractor and Government requirements for the AFETE contract production and repair services program. Task shall include program planning, laboratory testing, support equipment, and life cycle planning. The scope of this acquisition is to provide a contract vehicle for production and repair of AFETE to support user requirements for the assets in Table 1.

1.2 Benefit to the United States Air Force (USAF): The benefit to the USAF is that serviceable AFETE will be returned the Air Force supply system and the warfighter through production and repair, while enabling maintenance and inspection of Aircrew Flight Equipment

(AFE).

1.3 Equipment Background: The AFETE system includes those assets listed in Table 1.

Table 1. AFETE

1.3.1 Joint Combined Aircrew Systems Tester (JCAST): The JCAST system interfaces with four main A-10, F-15, F-16, and F-22 Aircrew Flight Equipment (AFE) components: the oxygen mask (MBU-5/P, MBU-10/P, MBU-12/P, MBU-19/P, MBU-20A/P, MBU-20/P, and KMU- 511/P), goggles (EEU-2/P, EEU-2A/P), G-suit (CSU-13B/P, CSU-15/P, CSU-17/P, and CSU- 22/P CSU-23/P), Man-Mounted Regulator-MMR (CRU-43/P, CRU-80/P, CRU-103/P, CRU- 60/P, CRU-94/P, CRU-120/P, and CRU-122/P), and communications (microphone and earphones in mask and helmet). It provides air at pressure levels consistent with aircraft supply levels to test the Man Mounted Regulators (MMR). It is also capable of performing pre-flight checks of pilot-mounted equipment, fit testing of pilot oxygen masks, leak testing on the G-suit and related hoses and fittings, listen and talk checks with headsets and microphones used with the communications system, and continuity tests of this equipment as a means of fault isolation.

Noun NSN Part

Number Joint Combined Aircrew Systems Tester (JCAST) IUID Noun: Aircrew Test Set

4920-01-619-9654 6177100-20

Altitude Combined Aircrew Systems Tester-High Altitude

(ACAST-HA)

IUID Noun: Fixture Assembly, Test, Interface Device

4920-01-665-4645 6213100

Upgraded System Communication and Oxygen Tester (SCOT) IUID Noun: Test Stand, Aircraft

4920-01-691-9686MH 6112300-1

1.3.2 Altitude Combined Aircrew Systems Tester-High Altitude (ACAST-HA): The ACAST- HA is an accessory unit that interfaces to the JCAST to provide expanded and complementary capability including altitude chamber testing with minimal size and maximum flexibility. The ACAST-HA interfaces with Regulators: CRU-120/P, CRU-122/P.

1.3.3 System Communication and Oxygen Tester (SCOT): The SCOT is a self-contained, portable testing system designed to integrate the testing of multiple life support equipment into a single unit capable of testing Life Support equipment for USAF. In addition, the test unit is used to test the oxygen mask, similar oxygen masks, and P series helmets to discover evidence of leakage and other malfunctions. It is used to perform pressure drop leak tests on all related hoses and fittings and G suit. It performs "talk-out" checks on all Air Force headsets and microphones used with the aircraft communications systems. It is used to test continuity of the above equipment and related harnesses. The SCOT interfaces with Regulators: CRU-43/P, CRU-60/P, CRU-80/P. Masks: MBU-5/P, MBU-10/P, MBU-12/P, MBU-19/P, MBU-20A/P, 358. G-Suits:

CSU-13B/P, CSU-15/P, CSU-22/P, CSU-23/P. Mics: Dynamic, Electret, 10V amplified, 28V amplified. Headset: Mono Low Impendence, Mono High Impendence.

2.0 Service Delivery Summary

Table 2. Service Delivery Summary

Performance Objective

PWS

Reference

Performance Threshold

Compliance with the quality levels of repair necessary to return assets in serviceable condition

5.10

Assets shall be repaired in accordance with technical standard Contractor’s approved specifications.

There shall be no more than one validated Product Quality Deficiency Report (PQDR) per contract year.

At a minimum, 90% of repaired assets shall pass initial acceptance inspection per quarter. Remaining 10% (or less) of failed assets shall pass on the second attempt. This metric will be calculated utilizing the Joint Deficiency Reporting System (JDRS) validated process for all National Stock Numbers (NSNs) mentioned within this PWS.

Delivery of repair

4.7

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

There shall be no more than one late delivery per month. 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 Contract Data Requirements List (CDRL) deliverable

4.6

There shall be no more than one rejection of any single deliverable. There shall be no more than a total of one rejection of deliverables per month. The Government will reject a deliverable if any technical errors or six or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

Receipt of CDRL deliverable

4.6

There shall be no more than one late receipt of deliverables per quarter. 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.

Request for assistance 5.0

The Contractor shall initially respond to a request for assistance within two business days. Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government.

CAV-AF reporting

4.7.4

The Contractor shall report production in CAV-AF.

The Contractor shall provide data on the actions conducted for each unit. The Contractor shall report as transactions occur. No more than two late or incorrect entries shall be allowed per delivery order.

Any delayed entries shall not exceed three business days.

The following metrics will be monitored: GFM In- Transit, Repairable GFM Accountability, and Assets Not on Contract.

Contractor Manpower Reporting

5.8

Within 30 calendar days of contract/order award, the Contractor shall establish a record for the contract/order in the System for Award Management (https://www.sam.gov).

The Contractor shall provide a count of contractor/subcontractor personnel performing services for each fiscal year and report all contractor/subcontractor labor hours required for performance of services for each fiscal year.

Adherence to Contractor Quality Management System (QMS)

5.10

100% compliance with the QMS is required.

3.0 Government Property

3.1 Repairing Government Property: Government property, as defined under this contract, will be the AFETE sent to Chemring Energetic Devices, Inc (CED) for repair. GFP that is received and returned shall be reported appropriately. [CDRL A018, Government Property (GP) Inventory Report, DI-MGMT-80441D]

3.2 Contractor Property: The Contractor shall furnish all material and parts necessary for the repair of the end item.

4.0 Technical Requirements

4.1 Contractor Responsibilities: The Contractor is responsible for engineering support of the AFETE listed in Table 1. The Contractor shall support the AFETE Program Office. The Contractor shall accomplish repair of designated NSNs and Part Numbers (P/Ns) listed in Table 1, observing accepted quality standards and relevant technical standards. Findings and recommendations will be presented to Program Office. The repaired items shall be defect-free and Contractor shall meet all Government established suspense dates. The Contractor shall successfully resolve customer complaints within 10 business days of receipt, 100% of the time, or other such time periods and numbers of complaints as specified in the task order.

AFETE is a production and repair program. The major objective of the program is to return unserviceable, reparable units of the system to a serviceable condition and to return such items to Air Force supply. The USAF Depot manages a serviceable pool of Testers. Therefore, the Contractor will not be required to manage a pool. Work performed under this PWS includes all actions necessary to return the end item to a serviceable condition.

4.2 Surge Item Reporting: Contractor shall conduct reporting as to the status of Surge Items and provide revised delivery status within 2 business days upon request for status or change in status of Surge Items delivery.

4.3 Improved Production Delivery Turn-Around Time (TAT): The turn-around time required is 60 calendar days ARO (After Receipt of Order)/Reps, whichever is later. However, Surge and MICAP requirements will be within 14 calendar days ARO/Reps and will be shipped by fastest traceable means. Contractor shall make every effort to expedite delivery of repaired units to meet fastest turn-around times possible. The Contractor shall provide written notice of inability to meet the required TAT with a detailed explanation for the delay, the latest estimated completion date, and plan for repair completion within 10 business days. Factors that could lead to longer lead times other than those set forth in this schedule shall be identified and reported to the Program Office (AFLCMC/WNU, Sustainment). Contractor agrees to take appropriate action to correct these problems to comply with the TAT specified by the Program Office before production begins, at no additional cost to the Government as part of this agreement.

If a reparable item is required by the Government on an emergency basis, the Procurement Contracting Officer (PCO) will notify the Contractor in writing (e-mail or facsimile preferred) as soon as the need is identified. In these situations, the Contractor will use every means possible to process the item on a priority basis. The Contractor shall forward any production problems to the contracting officer, and any items received which are not manufactured by CED will be returned at the Government’s expense.

4.4 Inspection and Functional Test: Incoming inspection shall be performed in accordance with ISO 10012-2003 which requires that a unit is tested as it is upon receipt. After incoming inspection, CED will perform initial evaluation testing in accordance with the CED internal check sheet for each device. After initial evaluation, the unit(s) will proceed through CED’s internal Calibration and Repair process until completion. The Contractor performing repairs shall be ISO 9001:2015 certified.

Neither design nor functional capabilities shall be changed, modified, or altered without the written approval from the procuring agency. After repair is completed, the Contractor shall inspect each item to ensure that all tools/foreign objects have been removed.

4.4.1 Calibration: The USAF PMELs and Air Force Metrology and Calibration (AFMETCAL) shall assume calibration responsibilities for the Digital SCOT, JCAST-20, and ACAST-HA. The Contractor shall prepare a calibration procedure manual for the Digital SCOT (in accordance with CDRL B001 and CDRL A022) and deliver said manual to the Government within the basic contract year. The Contractor shall prepare a Calibration and Measurements Requirements Summary (CRMS), which shall be developed using DI-QCIC-80278C and MIL-STD-1839D as guidance. The CRMS shall identify the System’s calibration and measurement requirements and procedures, the measuring and test equipment, and the calibration equipment or standards required to maintain a proper calibration system. The Operational/System Equipment shall be reflected under Category I of the CRMS; the Test, Measurement, and Diagnostic Equipment under Category II; the Calibration Equipment/Standards under Category III by each system (tester) as applicable. Standards shall be traceable to National Institute of Standards and Technology (NIST) or other DoD-approved measurements sources. Reference DAFI 61-201 for guidance and procedures to manage Scientific and Technical Information (STINFO) throughout the lifecycle of the information. The Contractor shall still calibrate all AFETE (JCAST-20, ACAST-HA, and Digital SCOT) after performing all repairs. If/when there are instances where the USAF cannot calibrate the AFETE, the Contractor shall calibrate the AFETE when a calibration contract order is placed. [CDRL B001, Calibration and Measurements Requirements Summary (CRMS), DI-QCIC-80278; CDRL A022 Technical Manual Contract Requirements (TMCR)]

4.5 Period and Place of Performance

4.5.1 Contract/Order Period of Performance: The period of performance for the contract/order will be a basic year with four (4) option years and will extend one year beyond the date of the final order or will end on the last day of the contract.

4.5.2 Place of Performance: These services will be performed at the Contractor’s (CED) facility as required on an order-by-order basis as specified in the PWS and/or Task Order.

Contractor location:

Chemring Energetic Devices

2525 Curtiss Street

Downers Grove, IL 60515

4.6 Contract Data Requirements List (CDRL)

4.6.1 Quality of CDRL Deliverable: The Contractor shall deliver all data/reports associated with CDRL, with no more than one rejection of any single deliverable. There shall be no more than total of one rejection of deliverables per month. The Government will reject a deliverable if there are any technical errors, or if six or more minor errors are found within the deliverable. A technical error is defined as a format incompatible with the CDRL or inaccurate/incomplete content as defined by the CDRL, PWS, or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection, in accordance with the associated DD Form 1423 instructions/requirements.

4.6.2 Submission of CDRL Deliverable: The Contractor shall electronically deliver all contractual data using the Government-controlled method of delivery, Multi-user ECP Automated Review System (MEARS), https://mears1.redstone.army.mil/mears/Default.aspx.

The Contractor shall work with the Government to ensure that an adequate number of Contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. The Contractor shall be receptive to the training offered by the Government on the MEARS system. The Contractor shall prepare, maintain, and track the contract data status and schedule to ensure timely data deliveries. An alternate method of delivery when MEARS is down for maintenance will be the DISA application, known as DoD SAFE, https://safe.apps.mil/.

It will be available to all DoD Common Access Card (CAC) holders or Contractor personnel who possess Public Key Infrastructure (PKI) certification from an accepted Government source.

Separately priced data must also be submitted/accepted in Wide Area Workflow (WAWF) for the Contractor to receive payment.

4.6.3 Receipt of CDRL Deliverable(s): There shall be no more than one late receipt of deliverables per quarter. 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.6.4 Data Management/MEARS: The Contractor shall electronically deliver all contractual data using the Government-controlled method of delivery, Multi-user ECP Automated Review

System (MEARS), https://mears1.redstone.army.mil/mears/Default.aspx. The Contractor shall work with the Government to ensure that an adequate number of Contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. The Contractor shall be receptive to the training offered by the Government on the MEARS system.

The Contractor shall prepare, maintain, and track the contract data status and schedule to ensure timely data deliveries. An alternate method of delivery when MEARS is down for maintenance will be the DISA application, known as DoD SAFE, https://safe.apps.mil/. It will be available to all DoD Common Access Card (CAC) holders or Contractor personnel who possess Public Key Infrastructure (PKI) certification from an accepted Government source.

4.7 Maintenance and Repair: The Contractor shall accept unserviceable units from Air Force Program Office (AFLCMC/WNU, Sustainment (SRAN FD2060)) supply and return the same items to a serviceable condition. The Contractor shall cooperate with the Program Office to ensure the best value for the United States Air Force. The Contractor shall offer feasible, cost-effective, and reasonable support by means of parts attrition regarding obsolescence of the JCAST (P/N 6177100-10) and the Legacy SCOT (P/N 6112300). When items are no longer available, the Government supports the Contractor’s decision for assets to be no longer supportable/reparable. The Contractor shall permanently and legibly mark each repaired item with the Contractor’s identification. This identification shall be affixed by decal or similar means and shall include the Contractor’s name, date of repair, and contract number. Painted portions of the end item shall be inspected to determine if repair is required. Loose and scaled paint shall be removed. All bare metal surfaces shall receive corrosion treatment prior to application of primer and paint. The Contractor shall replace damaged, illegible, or missing instruction or data plates in accordance with MIL-STD-130N. Each repair should fall into one of the below categories for appropriate pricing:

Levels of repair are determined by this process:

1. Troubleshooting at the unit level should be written as procedures in the Technical Orders for each tester. Until the procedures are developed in the Technical Orders (in accordance with the TMCR CDRL A022), Chemring can perform troubleshooting with the unit directly.

2. If unit-level troubleshooting is unsuccessful, the owning unit will issue a contract repair order through the Government program office and Chemring will assign an RMA to the

Level Description Detailed Repair Description 1 No Fault Found Actions taken to identify level of repair (Test, Teardown, & Evaluation). Inspection resulted in no findings. Unit Functional.

2 Minor repair One or two small components need replacement/repair.

3 Medium repair Three or four components or requiring extensive labor.

4 Major repair Larger subassembly repair/replacement with extensive labor.

5 Overhaul Multiple major system(s) repair/replacement.

6 BER (Beyond Economical Repair) Unit unrepairable. Will be dispositioned according to owning unit’s instructions.

order. The unit will then send the tester to Chemring for Test, Teardown, & Evaluation

(TT&E).

3. Order of evaluation and repair at Chemring is determined by priority of contract order (can be communicated from WNUS to Chemring). If priority isn’t established, then Chemring can perform TT&E based on order of receipt.

4. Upon completion of TT&E, the customer is contacted and updated with the results. The repair level is determined and the fixed price fee is billed, or the customer can request termination of repairs.

5. Completed repairs are documented in CRM with information including: the technician, date, the specific work completed, parts replaced, labor hours, etc.

6. Chemring’s contracting department notifies the owner and prepares the paperwork for shipping the tester back to the owning unit (return shipping cost is included in the repair fee).

7. Chemring’s shipping department ships the tester back to the owning unit and forwards tracking information to Chemring’s contracting department. The contracting department will then share the tracking information with the owning unit.

4.7.1 Item Unique Identification

4.7.1.1 IUID Marking Requirement: The Contractor’s IUID Marking Plan shall fully detail and document the strategy and scope to be used to meet MIL-STD-130N, DoD Standard Practice Identification Marking of US Military Property. The plan must be approved by the Government Engineering organization prior to implementation. One hundred percent (100%) of units shall be marked, inspected, evaluated, and added to the Activity and Verification Report. The Government will accept the receiving report through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. The Government will indicate approval or disapproval through WAWF within 60 days of submittal. [CDRL A001, DI- MGMT-81803A Item Unique Identification (IUID) Marking Plan; CDRL A002, DI- MGMT-81804A Item Unique Identification (IUID) Marking Activity and Verification Report]

4.7.1.2 Reporting in IUID Registry

4.7.1.3 Transmission of Government property must be recorded in the IUID Registry. The Government is required to record the transfer of GFP to the Contractor. The Contractor is required to record the receipt of GFP from the Government. The Contractor is required to record the return of GFP to the Government.

4.7.1.4 The Government or contractor/subcontractor personnel responsible for causing a “life cycle event” (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 – non-Government, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry.

4.7.2 Test and Final Inspections

4.7.2.1 Post Repair Inspection: Inspect, service, test, and check the completed item in accordance with Contractor procedures to ensure item meets operational standards called out on item drawing, prior to presentation to the Government for acceptance.

4.7.2.2 Acceptance Testing: Acceptance testing shall be performed on 100% of deliverable items in accordance with the Government-approved Contractor’s established Acceptance Test Procedure (ATP) or the Government approved test specification. Acceptance Test Data Reports shall be provided when required. At a minimum, 90% of repaired assets shall pass initial acceptance inspection per quarter. Remaining 10% (or less) of failed assets shall pass on the second attempt. This metric will be calculated utilizing the JDRS validated process. Electronic format using Microsoft Office 2016 applications is acceptable for requirement to be type-written on 8 ½” x 11” paper. Submit final report with DD250 through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. [CDRL A006, Test/Inspection Report, DI-NDTI-80809B; CDRL A007, Acceptance Test Plan, DI-QCIC- 80553A]

4.7.2.3 Test Procedure Qualification: Contractor shall use approved Acceptance Test Procedures (ATPs) already in Contractor’s possession in the normal course for repair and manufacture. If ordered, the Contractor shall be required to generate or modify the ATP qualification. If applicable, the qualification shall consist of specific requirements which will be stipulated in the applicable Delivery Order. The negotiated schedule for the ATP generation or modification shall be included in the Delivery Order. Production delivery of affected items shall not occur prior to the Government approval of the ATP qualification activity. Electronic format using Microsoft Office 2016 applications is acceptable for requirement to be type-written on 8 ½” x 11” paper.

Submit final with DD 250 through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. [CDRL A008, Test Procedure, DI-NDTI- 80603A; CDRL A006, Test/Inspection Report, DI-NDTI-80809B]

4.7.2.4 Test Procedures: When included at time of Delivery Order issuance (and included in Contractor’s price as a separate CLIN), if required by CDRL, the Contractor shall prepare and submit for Government approval, an ATP in accordance with the requirements of this PWS, the Contract Data Requirements List (CDRL), and the specification, drawing, and/or Purchase Department Specification (PDS) for each part number listed as an output item in this PWS.

Otherwise, the Contractor shall complete testing of the item using Contractor’s established ATP.

If required by CDRL and if no provisions for acceptance testing are contained in the referenced documents, the Contractor shall propose an ATP based upon his current engineering evaluation of the item, including all components, sub-components, and assemblies. The ATP shall include procedures that verify the item performance, functionality, quality, and reliability as specified in the item drawing, and include Environmental Stress Screening (ESS) for each part number referenced in this document as requiring ESS.

4.7.2.5 Nonstandard Parts: Nonstandard parts defined as non-Mil-Standard or commercial equivalent that are used in this repair must be approved via submittal of a Parts Approval Request. Electronic format using Microsoft Office 2016 applications is acceptable for requirement to be type-written on 8 ½” x 11” paper. Submit final with DD 250 through WAWF.

The Contractor shall submit the receiving report upon final submission to DODAAC FB2065.

[CDRL A009, Parts Management Plan, DI-SDMP-81748]

4.7.2.6 Delivery Schedule: TAT and delivery schedules shall be negotiated prior to contract award or at the delivery order level. The Government reserves the right to adjust the delivery schedule at the start of each ordering period based on changes in Monthly Demand Rate or other factors. Routine delivery schedule shall be maintained with not more than one item late per month. Contractor is authorized to exceed the delivery rate or to complete performance of this contract prior to the time set forth in the Schedule; provided, however, that nothing contained herein shall obligate the Government to perform any of its obligations to the Contractor at an earlier date than set forth in the contract in order to assist the Contractor to make deliveries on an accelerated basis.

4.7.3 Preservation, Packaging and Transportation

4.7.3.1 The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked, and delivered in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

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

4.7.3.3 Repaired assets will be shipped by traceable mode of transportation. Surge and MICAP requirements will be packaged/shipped by traceable overnight transportation.

4.7.3.4 Contractor will ship/return all assets back to their respective units after work has been completed. Contractor will put “Mark For” before the unit’s return address in BOLD on ALL shipping documents. The Contractor should insert this statement in the DD250, Block 14, “Mark

For” or similar area on other shipping documents. Owning USAF units and their return addresses will be identified when the orders are placed.

4.7.3.5 The Contractor shall provide all CONUS transportation services for loading and off-loading of equipment. Shipment of repaired items will be via Fast Transportation. The Contractor shall be responsible for shipment of repaired items. Serviceable assets can be shipped when Federal Stock Class (FSC) and Military Management Aggregate Code (MMAC) changes, providing the National Item Identification Number (NIIN) and part number are the same.

4.7.3.6 When shipping containers are received that meet the requirements of the AFMC form 158 and are suitable for return shipment of serviceable assets, they shall be reclaimed, stored, and protected for reuse. Unserviceable containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

4.7.3.7 The Contractor shall adhere to MIL-STD-2073-1E for packaging and packing of excess Government property. When shipping containers are received that meet the requirements above and are suitable for return shipment of serviceable assets, they shall be reclaimed, stored, and protected for reuse. Unserviceable containers shall be disposed of and replaced with new containers that meet the above requirements.

4.7.4 Commercial Asset Visibility-Air Force (CAV-AF)

4.7.4.1 Contractor is required to comply with all CAVAF requirements identified in the CDRLs and attachments to the contract. Additionally, upon completion of the repair, the Contractor is required to print the DD1348-1 (in triplicate) from CAVAF. One copy is to be placed inside the box with the returnable repair asset, one copy will be affixed outside the box, and one copy will be electronically uploaded to WAWF as part of the Receiving Report (DD250). NOTE: The assigned Air Force personnel responsible for managing the item are required to track the item through the CAVAF system and notify the contracting officer if the Contractor is not complying with CAVAF requirements.

4.7.4.2 Data will be provided IAW attached DD Form 1423 Contractor Communication Network (CCN) (CAV-AF). The Contractor shall conduct production reporting as transactions occur and report problems. No more than two late or incorrect entries shall be allowed per delivery order.

Any delayed entries shall not exceed three calendar days. All reporting shall be submitted in the English Language. The Contractor’s CAV AF Reporting shall reflect their inventory property control management system data records which shall represent timely and accurate accountability of AF inventory assets at the physical location(s) of the Contractor’s repair facility (including Subcontractor facilities), shop floor, bond room, and/or receiving/shipping docks, etc.

for each repair. The Contractor shall report by contract delivery order on all applicable categories, totals, and on-hand balances providing TABLE I (DI-PSSS-81995) for EACH repair location, including Subcontractor facilities, for the contract’s maintenance occurrence actions during the reporting period. The Contractor shall report on production, providing TABLE I (DI- PSSS-81995) for EACH repair location, including subcontractor facilities, for which the Contractor produced assets during the reporting period. WAWF/Government acceptor will be the Contracting Officer Representative (COR). The Contractor shall report End Item transactional data through electronic submission in CAV AF using the CAV AF website or CICA XML. The Contractor shall submit a DD Form 250 (Material Inspection and Receiving Report) electronically via the Internet to iRAPT (WAWF) website address: https://wawf.eb.mil, using DODAAC FB2065. A Letter of Transmittal shall be submitted in the month the delivery order is completed, covering all reports transmitted for that order. [CDRL A003, Commercial Asset Visibility Air Force (CAVAF) / Government Furnished Material Report, DI-MGMT- 81634C; CDRL A004, Commercial Asset Visibility (CAV) Reporting, DI-MGMT-81838;

CDRL A019, Contract Depot Maintenance (CDM) Monthly Production Report, DI-PSSS- 81995A; CDRL A020, Contract Government Furnished Material (GFM) Monthly Requisition and Inventory Report, DI-MGMT-82128A].

4.7.4.3 The Contractor shall report using the Commercial Asset Visibility (CAVAF). The Contractor shall provide data related to the tasks and efforts conducted for each repairable unit.

The Contractor shall conduct production reporting as transactions occur. The Contractor shall obtain a valid DoD PKI certificate to log into CAVAF. Each user shall be required to have an Identity Certificate only; an encryption certificate is not required. [CDRL A003, Commercial Asset Visibility Air Force (CAVAF) / Government Furnished Material Report, DI-MGMT- 81634C]

4.7.5 Counterfeit Prevention Plan

4.7.5.1 The Contractor shall establish and maintain policy and procedures to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory in accordance with Aerospace Standard (AS) 5553, Counterfeit Electronics Parts;

Avoidance, Detection, Mitigation, and Disposition. Certification under Counterfeit Avoidance Accreditation Program (CAAP) meets this requirement. Otherwise, the Contractor shall provide a Counterfeit Prevention Plan. The Government will accept the receiving report through WAWF.

The Contractor shall submit the receiving report upon final submission to DODAAC FB2065.

The Government will indicate approval or disapproval through WAWF within 60 days of submittal. [CDRL A005, Counterfeit Prevention Plan, DI-MISC-81832]

4.7.5.2 The system shall incorporate processes/procedures to address the requirements listed in accordance with the FAR and applicable supplements and shall comply with all applicable guidance and clauses listed in the contract. The Government's review of the Contractor’s system will be accomplished as part of the evaluation of the Contractor’s purchasing system in accordance with the FAR and applicable supplements and shall comply with all applicable guidance and clauses listed in the contract.

4.8 Software Management

4.8.1 The Contractor shall include the Government-assigned CPIN along with the Contractor assigned operational software part number and Load I.D. number in a “Read Me” text file on the deliverable media containing the operational program executable code. The Contractor shall manage all AFETE software programs as Computer Software Configuration Items (CSCIs) and deliver all revisions using the applicable Air Force-assigned Automated Computer Program Identification Number (ACPIN). Releases shall be made as block updates and submitted semi-annually or as requested by the PM through the PCO. Requirements for new CSCIs shall be identified through the ECP process. All software releases shall meet requirements for quality, configuration control, and systems engineering. Approval by AFLCMC/WNUS through the PCO is required prior to delivery of any software. The Contractor shall generate a Software Version Description (SVD) describing each version of the CSCI in accordance with this PWS, including the changes incorporated, manuals affected, and known or potential issues. The Contractor shall also provide a report to the USG regarding the delivery, status of software and description, ACPIN data, and control record. The Contractor shall provide the USG PM office a report for the initial delivery of ACPIN 60 calendar days prior to any due date for each CSCI. Information regarding ACPIN can be found in T.O. 00-5-16.

4.8.2 Contractor will establish an ESTS CPIN Country Standard Compendium that will include: CPIN I.D. and Revision Number; Contractor Load I.D. Number and Revision; Software Date; and Description. The Contractor shall provide an initial Country Standard Compendium within 90 calendar days after contract award and will release updated Compendium annually to the AFLCMC/WNUS Program Office. Delivery of AFETE CPIN shall be through the AFLCMC Program Office Software Center to be delivered to Technical Order Publication Distribution Office. Electronic format using Microsoft Office 2016 applications is acceptable for requirement to be type-written on 8 ½” x 11” paper. Reference Technical Order (TO) 00-5-16 for further clarification of managing CPIN. Submit final with DD 250 through WAWF. The Contractor shall submit the receiving repot upon final submission to DODAAC FB2065. [CDRL A014, Software Version Description (SVD), DI-IPSC-81442A; CDRL A015, Computer Program Identification Number (CPIN) Catalog Information, DI-MISC-81454D; CDRL A016, Computer Program End Item Documentation, DI-IPSC-80590B]

4.9 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as directed by the Contractor. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.10 Travel: Contractor/Sub-Contractor travel is not required because production and repairs will be accomplished at the Contractor’s facility.

4.11 Condemnation: The Contractor shall not condemn any asset without the approval of the Government. Condemnation must be approved by the ACO/PCO. Condemned items shall be disposed of IAW DCMA-approved local plant procedures. Items condemned under provisions of this contract shall be replaced by reparable assets, if available. Any work expended on any item prior to condemnation shall be at no cost to the Government.

4.12 Sustaining Engineering Specific Requirements: The Contractor shall provide engineering support for the relevant NSNs on an as-needed basis to the Government to include technical analysis, engineering proposals, redesigns, tests, meetings, and working groups. The Contractor shall initially respond to a request for assistance within two business days. Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government.

In support of this tasking, the Contractor shall respond with a cost estimate within the Government-requested timeline (normally 45 calendar days or less). Engineering projects will be specific to the NSNs on contract (which have been determined to be sole source for buy/repair to the Contractor). Additionally, all engineering services task orders will be separately reviewed to determine/verify that the engineering service is truly sole source to the Contractor in accordance with FAR 6.302-1. Engineering Services required in support of the NSNs listed herein, per the requirements described in individual task orders, shall be accompanied by a performance specification or performance-based statement of work to address requirements not contained within this PWS. Electronic format using Microsoft Office 2016 applications is acceptable for requirement to be type-written on 8 ½” x 11” paper. Submit final with DD 250 through WAWF.

The Contractor shall submit the receiving report upon final submission to DODAAC FB2065.

Reference DAFI 61-201 for guidance and procedures to manage Scientific and Technical Information (STINFO) throughout the lifecycle of the information. [CDRL A010, Scientific and Technical Reports, DI-MISC-80711A]

4.12.1 Configuration Management (CM): The Government has the responsibility to ensure operating forces are provided with correctly configured hardware, software, and the information necessary to operate and maintain them effectively. The Government will maintain configuration management and oversight of all end items. All changes/modifications shall be authorized by the Government Configuration Control board (CCB). Work performed shall be IAW the Contractor's engineering directives, internal drawings, and procedures or Government-approved Contractor verification test procedures. The Contractor shall make engineering directives, internal drawings, and procedures or Government-approved verification test procedures available for Government on-site review when requested by the Government. The Contractor shall track and inform the cognizant System Engineer/Program Manager of configuration changes.

4.12.1.1 Configuration Change: Changes to the configuration shall be made only when the approved by the Government. Examples of such changes are ECPs generated as a result of diminishing sources, reliability and maintainability, safety, and preferred spares. Records shall be maintained which readily and systematically account for configuration changes from baseline configuration.

4.12.1.2 Engineering Change Proposal (ECP): When development of a Formal ECP is recommended by the Contractor, the Contractor shall submit the ECP to the Ordering PCO/Program Office for review. Upon submission to the PCO, the PCO shall inform the appropriate Government entity of any change notice, design change notice, engineering order, engineering change order, engineering change notice, or specification change that would affect the configuration of an item. ECPs submitted shall be technically accurate, complete, clearly written, and systematically account for the proposed configuration changes. The ECP shall contain a technical solution write up, program plan, and detailed pricing. It shall be in sufficient detail to provide information needed for proper evaluation and determination of requirements for actual modification. Any changes made without written approval from the Contracting Officer may require removal at the Contractor’s expense. Once a change has been implemented, including any substitute parts changes, the Contractor shall notify the Government through Notice of Revision (NOR). Format shall be in either of the following formats: DD Form 1692 ECP or a format that is mutually agreed to by the Government and Contractor. Any format other than DD form 1695 shall be compatible with PC-based versions of Microsoft Office 2016 or higher. Submit final with DD 250 through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. [CDRL A011, Engineering Change Proposal (ECP), DI-SESS-80639E; CDRL A012, Notice of Revision (NOR), DI-SESS- 80642E]

4.12.1.2.1 Class I Engineering Changes: Class I Engineering Changes are major changes that impact the Form, Fit, Function, Interface of the item. The Contractor shall be required to propose Class I Engineering Changes as required (such as for the proposed resolution of a Diminishing Manufacturing Sources and Material Shortages (DMSMS) issue). Format shall be in either of the following formats: DD Form 1692 ECP or a format that is mutually agreed to by the Government and Contractor. Submit final with DD 250 through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. [CDRL A011, Engineering Change Proposal (ECP), DI-SESS-80639E]

4.12.1.2.2 Class II Engineering Changes: Class II Engineering Changes are changes to correct documentation or changes not otherwise defined as a Class I Change. The Contractor shall obtain Government concurrence on the classification of the change, concurrent with the release of the change for Class II engineering changes. Class II changes will be forwarded to the PCO. Once the Government concurs with the change classification, hardware deliveries may proceed prior to release of the updated TOs once red-line changes are in place. TO changes required as a result of Class II ECPs shall be documented via red-lined changes and submitted in Contractor format to the Government Multi-Functional Team (MFT). Format shall be in either of the following formats: DD Form 1692 ECP or a format that is mutually agreed to by the Government and Contractor. Submit final with DD 250 through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. [CDRL A011, Engineering Change Proposal (ECP), DI-SESS-80639E]

4.12.1.3 Service Bulletins (SB)

4.12.1.3.1 All modifications to fielded equipment shall be made only by Government approved Service Bulletins (SBs) in accordance with PWS paragraph 4.13.1.3.2. SBs may be proposed by an ECP or other method as directed by the PM. Any kits required to implement a SB shall be built prior to final approval of the SB. Historical record forms shall be used to record compliance with SBs Design.

4.12.1.3.2 Service Bulletins Procedures: An SB approved by the Government CCB and released by AFLCMC/WNUS is the final implementing authority for changes to end item configuration baselines associated with operational systems, hardware/software, and supporting equipment. SBs are the official documents, providing service instructions concerning changes affecting Government owned equipment. Instructions may pertain to testing, installation, modification, servicing, overhaul, repair, inspection, and identification of equipment. It is very important that Contractors of systems, sub-systems and support equipment work closely with AFLCMC/WNUS and the PM on any proposed changes. A coordination copy for all proposed SBs will be forwarded to AFLCMC/WNUS for review and approval. Electronic format using Mircosoft Office 2016 applications is acceptable for requirement to be type-written on 8 ½” x 11” paper. Submit final with DD 250 through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. [CDRL A017, Service Bulletins, DI-

MISC-81618]

4.12.2 Obsolete Parts and DMSMS: The Contractor shall notify the Government of obsolete part conditions within five business days of identification and make recommendations including last-time buy opportunities and any redesign that may ensue. The Contractor shall identify any obsolescence and DMSMS issues that arise for the duration of this contract. The Contractor shall be responsible for conducting a comprehensive DMSMS and Obsolescence program for Class II form, fit, function replacement items needed to complete repair of the asset. This program shall include identification, analysis, and resolution for Class II DMSMS and Obsolescence. If the aforementioned analysis determines that there is no feasible Class II change that will resolve the issue(s), the Contractor shall recommend a course of action. Replacement parts shall be recommended to minimize impact. Requests for funding and all related issues will be directed through the Contracting Officer. Electronic format using Microsoft Office 2016 applications is acceptable for requirement to be type-written on 8 ½” x 11” paper. Submit final with DD 250 through WAWF. The Contractor shall submit the receiving report upon final submission to DODAAC FB2065. [CDRL A013, Bill of Materials (BOM) for Logistics and Supply Chain Risk, DI-PSSS-81656B]

4.13 Spares Specific Requirements: The Contractor shall perform all actions necessary to produce the end items/spares in accordance with the timeframes established in individual orders.

Routine delivery schedule shall be maintained with not more than one late delivery per delivery order. First Article and prototype requirements will require elements of the Engineering Services Specific Requirements as required by the delivery order.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis

5.1.1 Designation of Services as Mission-Essential: The Functional Commander (FC) or civilian equivalent has determined certain services under this contract/order are mission-essential and will continue in the event of a crisis.

5.1.2 Mission-Essential Contractor Services Plan

5.1.2.1 The Contractor shall submit a plan describing procedures for continuing performance of mission-essential services during a crisis. The Contractor shall identify provisions for ensuring required personnel and resources are available to support continuity of operations for up to 30 calendar days or until normal operations can be resumed. The Contractor shall submit any revision to the plan for approval prior to implementation. The Contractor shall activate the plan only if authorized by the PCO acting under the direction of the FC or civilian equivalent.

5.1.2.2 If the Contractor anticipates an inability to perform the mission-essential services, they shall notify the PCO as soon as possible and fully cooperate with the Government’s efforts to maintain continuity of operations.

5.2 Security Requirements

5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility, and, if applicable, international security requirements are met. The Contractor shall comply with all applicable Government regulations including, but not limited to, Department of Defense Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; Department of Defense (DoD) Manual 5205.02, DoD Operations Security (OPSEC) Program Manual; and DoD 5220.22-M, National Industrial Security Program Operating Manual

(NISPOM).

5.2.2 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 comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.)

Government interests. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply or military installation with the OPSEC procedures of the facility or installation.

5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or…