Draft_ SOW_B52_Crypto_Mod_Group_A_Kit_Production_7-15-26.docx

DRAFT Statement of Work (SOW) For B-52H Crypto Modernization Group A Kit Production

15 July 2026

CONTRACT NUMBER: FA8628-2X-X-XXXX

Developed By:

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

BOMBERS DIRECTORATE (AFLCMC/WB)

B-52 DIVISION (AFLCMC/WBD)

2690 LOOP ROAD WEST, BUILDING 556

WRIGHT PATTERSON AFB, OHIO 45433

Table of Contents

Scope/Background Scope This Statement of Work (SOW) identifies the tasks to be accomplished and sets forth the general requirements for B-52H Crypto Modernization/Mobile User Objective System (CM/MUOS) Group A production kits, spares, and technical support to facilitate installation on the B-52H aircraft.

As part of this effort the Contractor shall:

· Build and deliver Group A hardware kits required to install CM/MUOS on the aircraft in accordance with (IAW) this SOW.

· Deliver 76 Group A kits, plus one System Integration Laboratory (SIL) kit, and spares as specified in the contract; quantities broken out between 1 base year, plus four option years.

· One (1) Group A Kit will consist of: 54 wire harnesses, one Common Control Box, one Crypto Fill Panel, and provide associated parts/hardware per the Technical Data Package drawings. The Contractor is responsible to build the wire harnesses, control box, and fill panel according to the Tech Data Package.

· SIL Retrofit Kit will consist of: One Common Control Box and one Crypto Fill Panel for System Integration Laboratory (SIL) Retrofit. The Contractor is responsible to build these components per the Tech Data Package.

· Receive Parts, assemble/package the Group A Production kits, store kits until shipping, and fill complete forms specified in paragraph 2.3.

Background The B-52H CM/MUOS Program retains and improves upon current communication capabilities as provided by the ARC-210 Legacy and ARC-210 Warrior radio systems. The ARC-210 systems provide messaging through variable message format (VMF), Joint Range Extension Protocol-A (JREAP-A), Internet Protocol (IP) Data, and Radio Frequency (RF) voice communications capability for the aircraft in conventional combat missions, training, and test uses.

This Statement of Work (SOW) is for the production follow-on to Engineering and Manufacturing Development (EMD) contract FA8628-10-D-1000, D.O. FA8107-19-F-0003, which developed, verified, validated and documented the hardware and software configuration for the CM/MUOS Program. The objective of this SOW is to produce and deliver B-52H Crypto Modernization Group A production kits and spares.

Applicable Documents The documents listed form a part of this SOW to the extent specified herein. Unless otherwise specified, the latest released version of the referenced document is applicable. Where a revision by supplement, amendment, or notice is called out, the entire document up to and including that revision is being referenced. In the event of a conflict between this SOW and the references cited herein, this SOW takes precedence. The Contractor shall bring any such discovered conflicts to the attention of the B-52 System Program Office Contracting Officer. Sub-tier documents referenced within the cited documents shall not be applicable to this SOW unless the sub-tier documents are specifically referenced within this SOW or otherwise noted. Sub-tier documents may be used for guidance only. Only the basic documents, without specific revision, are referenced in the SOW text.

Government Documents

Non-Government Specifications & Documents

Forms

Requirements Program Management The Contractor shall identify and provide a Program Manager (PM) to act as the single point of contact responsible for managing and directing the Contractor’s activities with respect to this contract who is available for interfacing with the Government on standard Federal Government workdays.

The Contractor shall plan, schedule, execute, and manage the authorized contract work scope to ensure timely delivery of required products to the quality and performance standards/specifications cited herein. The Work Breakdown Structure (WBS) submitted under this contract shall follow MIL-STD-881-F. The Contractor shall coordinate and host a Contract Kick-Off Meeting within sixty (60) calendar days of contract award at contractor’s site. The Contractor shall submit an agenda and minutes.

(CDRL A056, DI-ADMN-81249C, Meeting Agenda) (CDRL A057, DI-ADMN-81250C, Meeting Minutes) The Contractor shall provide the Government insight into the CM/MUOS Group A Production Kit effort as requested during the period of performance. The delivery report shall include, but is not limited to, the status of ordered parts, status of kit builds and status of kit deliveries to the Government, actual or projected. The Contractor shall identify accomplishments to date, difficulties encountered, and compare the status achieved to planned goals and the resources expended.

(CDRL A022, DI-MGMT-80368A, Status Report, Kit Production Status Delivery) The Contractor shall hold a weekly status meeting with the Government covering weekly tasks, progress updates, risks and issues.

Program Management Plan The Contractor shall generate and maintain a Program Management Plan (PMP) that governs its management of all work authorized by this delivery order. This PMP shall specifically describe the Contractor’s production methodology for the B-52H Crypto Mod Group A kits. The PMP shall include the Contractor’s approach for contract startup, knowledge acquisition on the program, program risk management, supply chain risk management, engineering support, kit development management, kit delivery management, quality assurance, and spare management. The PMP shall be consistent with the Integrated Master Schedule (IMS).

(CDRL A094, DI-MGMT-80004A, Management Plan, Program Management Plan (PMP)) Integrated Master Schedule The Contractor shall develop, maintain, and use a CM/MUOS Group A Production Schedule to plan, execute, and manage the contractually authorized work scope to ensure timely delivery of required products to the quality and performance standards/specifications cited herein.

The IMS shall include CLIN level detail and define (at a minimum) program critical milestones, work timelines, any Government Furnished Equipment (GFE) required for Group A production need dates, Group A kit delivery dates, and program reviews. 2345 The Contractor shall notify the Contracting Officer (CO) immediately upon identification of a schedule delay that impacts the CM/MUOS Group A Kit delivery critical path by more than five (5) working days.

(CDRL A141A, DI-MGMT 81861C, Integrated Program Management Data Analysis Report (IPMDAR), Integrated Master Schedule) Program Risk Management The Contractor shall implement a risk management process to identify, analyze, document, track, handle, and communicate risks in accordance with an established Risk Management Plan. The Contractor shall provide continuous and comprehensive risk analysis to assist program management in identifying and mitigating program risks. The Contractor shall document risks and mitigation strategies in the Contractor’s risk tracking tool and incorporate risk handling strategies into program plans. The Government shall be notified as soon as practical and in advance of a CDRL submission regarding all identified risks that will impact scheduled deliveries or key milestones. Risk status shall be provided during scheduled Program Management Reviews (PMRs) and as new risks become known.

(CDRL A124A, DI-MGMT-81809, Risk Management Status Report, Program Risk Management Status Report) Supply Chain Risk Management (SCRM) Plan The Contractor shall ensure there is an approved Supply Chain Risk Management Plan in place for Group A hardware. This includes maintaining a list of suppliers back to the original source and managing the risk of single-source suppliers. The Contractor shall provide an SCRM Plan and execute an SCRM program that integrates with the program's overall risk management framework for the CM/MUOS system. The Contractor shall identify, assess, plan for, and mitigate actual or potential threats, vulnerabilities, and disruptions to the AF's supply chain throughout the lifecycle to ensure mission effectiveness. The SCRM Plan shall address the broad spectrum of supply chain risks that have the potential to jeopardize the integrity of products, services, people, and technologies; compromise intellectual property; disrupt the flow of product, materiel, information, and finances needed for continued AF operations; and drive material cost increases to the program. The Contractor shall have an SCRM Plan IAW R-DFARS.252.204-701.

(CDRL A160, DI-MGMT-82256, Supply Chain Risk Management (SCRM) Plan) Supply Chain Risk Management (SCRM) Tracking Report The Contractor shall develop and execute processes for: identifying supply chain risks as early as possible; the persistent and comprehensive tracking, monitoring, and re-evaluation of supply chain risks and their corresponding mitigation actions; and communicating supply chain risks to affected stakeholders and the Government. The Contractor shall provide a Supply Chain Risk Tracking Report for identified actual and potential supply chain risks. The Contractor's SCRM program and processes shall apply to the prime contractor and their suppliers, subcontractors, associated integrators, and vendors, spanning the entirety of the supply chain, from raw material stage to delivery of a finished product and/or service. The Contractor shall document and track risks and opportunities, including assessments and risk handling plans in a risk management tool. The Contractor shall submit the SCRM Tracking Report to the Government and support annual Government's Integrated Risk Assessments (IRA).

(CDRL A124B, DI-MGMT-81809, Risk Management Status Report, SCRM Report) Program Management Review The Contractor shall support two (2) PMR meetings per year to provide production updates to the Government. The PMR will be held at the contractor’s site. The first shall be conducted within one hundred and eighty (180) days after contract award. Subsequent PMRs shall be to update production status and risk mitigation efforts for completion of contract deliveries to the Government. The Contractor shall identify accomplishments to date, difficulties encountered, and compare the status achieved to planned goals and the resources expended. The Contractor shall submit an agenda and minutes.

(CDRL A056, DI-ADMN-81249C, Meeting Agenda) (CDRL A057, DI-ADMN-81250C, Meeting Minutes)

Quality Assurance Management The Contractor shall use a Quality Management System that adheres to the current versions of ISO 9001 and AS 9100 standards and the Contractor’s Best Practices. The Contractor shall ensure appropriate quality assurance requirements flow down to all subcontractors and vendors to ensure end items conform to specified requirements. The Contractor shall ensure compliance with the build-to drawings and specifications IAW AFMC Form 807 which will be provided at contract award.

Crypto Mod Group A Production Kits The Contractor shall build and deliver 76 complete Crypto Mod aircraft Production Group A Kits, which is itself a collection of kits/parts/components (e.g. each wire harness is itself a kit), to the Government comprised of the components listed in the Tech Data Package and sufficient to support the modification of 76 B-52 aircraft; quantity of 17 Group A kits initially, with four option years. Each Group A Production kit shall contain all components necessary to modify an aircraft (e.g. one Crypto Fill Panel per Group A Kit and not one box of 76 Crypto Fill Panels packaged separately). Any deficiencies (manufacturing defects that can be shown to result in a degradation of kit reliability or availability) identified in the contractor delivered kit after acceptance against the draft tech data package during CM/MUOS install shall be the Contractor’s responsibility to make the kit defect correct. The Contractor, or their sub-supplier, shall perform acceptance testing of Kit components IAW the Tech Data Package, and provide a Certificate of Compliance performed as part of delivery of the kit. Kit configuration information, to include technical guidance necessary for building are provided in section 3.3.6.

The contract’s CLIN structure identifies kit quantities to be procured with the base award and those to be procured via option CLINs, as well as spare kit requirements per base/option, and SIL requirements.

Item Unique Identification (IUID) The Contractor shall implement and maintain, as needed, an IUID Marking Plan for the CM/MUOS Group A Production Kit IAW MIL-STD-130N w/Change 1. The Contractor shall generate and deliver IUID Marking Activity, Validation and Verification Reports. The Contractor shall enter the IUID data for all marked components into the Wide Area Workflow (WAWF) database.

(CDRL A205, DI-MGMT-81804A, Item Unique Identification (IUID) Marking Activity, Validation and Verification Reports) Bill of Material (BOM) The Contractor shall create, maintain, and deliver a copy of the Bill of Material (BOM), at the Group A Production Kit level, to the Government at the lowest component indenture level for each deliverable end item. The Contractor shall prepare the deliverable IAW CDRL instructions.

(CDRL A156, DI-PSSS-81656B, Bill of Materials (BOM) for Logistics and Supply Chain Risk Management) Crypto Mod Group A Kit Delivery Kit Packaging, Handling, Storages and Transportation (PHS&T) The Contractor shall deliver only fully compliant Group A Production Kits, plus one SIL Kit, to the Government; partial compliant kits (i.e. missing one or more items specified in the Tech Data Package or within this SOW) will not be accepted. The Contractor shall adhere to the AFMC Form 158, Packing Requirements, specified Department of Defense (DoD) military standards American Society for Testing Materials (ASTM) International, American National Standard Institute (ANSI) ESD S20.20, Data Item Description(s), DoD specifications, FAR/DAR Clauses, documentation, and marking for the development of military packaging as prescribed in the contract.

The Government will notify the Contractor of any classified parts or data which the Contractor shall manage. Packaging of any classified items/data shall meet 32 CFR Part 117, National Industrial Security Program Operating Manual.

Kit Management The Contractor shall implement a kit management program to ensure that modification kits are delivered per contract requirements. The kit management program shall also ensure any part/tool changes identified during DMSMS resolution are incorporated in the configuration management/engineering system(s), procurement orders, and applicable technical data. The Contractor shall complete and deliver an AF Form 874, with full list of all kit components, work unit codes, NSN, and part numbers. The Contractor shall maintain a manufacturing management program for all aspects of the manufacturing process. The Contractor shall provide status on all kit items and deliveries.

(CDRL A022, DI-MGMT-80368A, Status Report, Kit Production Status Delivery) Reusable Containers The Contractor shall safeguard all received reusable shipping containers. The Contractor shall contact the Product Support Manager and Administering Contracting Office (ACO) during normal business hours (M-F, 8-5pm EDT) for disposition instructions and replacement when Long Life Reusable Container(s) are received in an unserviceable condition.

Reach Back Support The Contractor shall be available for reach back support for all kits delivered until the kits are successfully installed on the aircraft. The reach back support will cover quality or performance deficiencies identified during Group A Kit installation (e.g., missing components, defective components).

Kit Shipping Location The Contractor shall notify the program managers two weeks in advance at the location listed below the kit/items and quantities being shipped and then the program manager will provide the Contractor with the shipping address based on the item and the quantities. Contact information and method of notification will be provided at the start of the contract.

SW3232: POC: Mr. Michael Jansing (B-52 Kit Manager) DDOO TCTO Kitting 7330 Sentry Blvd Bldg. 469, Door 12 Tinker AFB, OK, 73145-8000 Kit Configuration Tech Data Package drawings contain the instructions and the parts lists for building and kitting the Crypto Mod MUOS Group A kits; Wire Harnesses, Common Control Box, Crypto Fill Panel, and associated hardware. Installation instructions within the Tech Data Package are included as reference only, the Contractor will not install the kits on aircraft. Specifically, regarding the Wire Harness requirements, there are 54 Detailed drawings the Contractor is required to build and package for each Group A Production kit. Note, all wiring harnesses shall be built with a connector installed on one end per drawing (Example: Drawing 827-18402, Sheet1).

All parts for a given Drawing (example: 827-18XXX) shall be packaged together in a single kit (unless otherwise specified). The kit shall then be labeled with the associated Drawing number (example: 827-18XXX). This enables the easy identification of component level kits within the overarching Group A Production Kit deliverable.

The Contractor is not responsible for the following components. Information in the Tech Data Package is provided as reference only.

822-1276-006 REMOTE CONTROL UNIT

822-2852-001 HIGH POWER AMPLIFIER - AM-7642

822-2857-001 TRIPLEXER

822-3347-001 RADIO RECEIVER/TRANSMITTER ARC-210 RT-2036

MAR-5915-21 DURAMAR 5915 ROUTER WITH ESS 2020 SWITCH

3.3.6.1 Kit Configuration Deliverable

Upon completion of the first Group A Production kit, the Contractor shall verify with the Government that kit configuration conforms to the Tech Data Package requirements and submit a Configuration Audit Summary Report and Certification. Such verification is not required for subsequent Production kits. Additionally, the Contractor shall support a Configuration Audit Meeting upon Government request.

(CDRL A058, DI-SESS-81022E, Configuration Audit Summary Report and Certification) (CDRL A056, DI-ADMN-81249C, Meeting Agenda) Spares The Contractor shall provide spares in accordance with Appendix 1.

Engineering Support Configuration & Technical Change Management The Contractor shall perform configuration management and data management for the program that assures systematic tracking, controlling, and reporting activities for change control, to include evaluation, review, coordination, approval, documentation, implementation, and verification of changes to approved baselines for configuration control.

Technical engineering changes or variances must be approved by the B-52 System Program Office. The Contractor shall follow the established B-52 Configuration Management Plan provided by the Government to ensure approved changes are reflected in the product baseline documentation. Changes or deviations from the approved specifications shall be prepared and submitted to the Government via the following processes, with documentation handled IAW associated CDRL instructions.

For requests to deviate or depart from any portion of the approved product specifications, the Contractor shall follow the Request for Variance (RFV) process. RFV requests shall comply with CDRL instructions and include the specific part/component impacted, the number of units impacted, and/ or a defined period of time for which the variance is sought. Note, a deviation will not result in the revision of the part/component/product’s current approved configuration baseline.

The Contractor shall submit and obtain Government approval via an Engineering Change Proposal (ECP) for Class 1 changes to Government-baselined specifications, documentation, and/or products. Following approval of an ECP, the Contractor shall submit and obtain Government approval for a Specification Change Notice (SCNs) to update the approved configuration baseline documentation. Additionally, if needed, the Contractor shall submit Contractor Change Proposals (CCPs) upon written request from the Contracting Officer and shall include applicable SOW language to support the proposed modification(s).

(CDRL A111, DI-SESS-80640E, Request for Variance (RFV)) (CDRL A018, DI-SESS-80643E, Specification Change Notice (SCN)) (CDRL A073, DI-SESS-80639E Engineering Change Proposal (ECP)) (CDRL A061, DI-ADMN-81401C, Contract Change Proposal (CCP))

Data Management The Contractor shall maintain data management procedures for the preparation, quality control, administration, and delivery of data required by the CDRL Package as specified in the delivery order. The Contractor shall prepare, maintain, and track the contract data status, and schedule and ensure timely data deliveries.

The Contractor is required to submit data right assertions as part of their proposal IAW R-DFARS provision 252.227-7992 (Identification and Assertion of Use, Release, or Disclosure Restrictions). This Data Rights Assertions List (DRAL) shall identify known technical data and computer software deliverables identified at time of proposal for which the Contractor intends to assert restrictions, consistent with R-DFARS.252.227-7992. The Government shall obtain Unlimited Rights to Form, Fit, and Function data and OMIT data as defined in R-DFARS.252.227-7989, limited to the minimum information necessary to meet those definitions. The Government may challenge asserted restrictions in accordance with R-DFARS.252.227-7997, Validation of Restrictive Markings on Technical data. The Contractor and all subcontractor(s) have an obligation to maintain records showing funding sources for development of the technology, component, or process in question to the extent the Government initiates a formal validation under R-DFARS.252.227-7997. Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software, the DRAL, required under R-DFARS.252.227-7989, shall be updated as required by R-DFARS when new technical data or software deliverables with asserted restrictions are proposed. Assertions must be completed with specificity regarding each item, component, or process listed and IAW the format required in the R-DFARS. The Contractor shall provide sufficient information to enable the Contracting Officer to evaluate the Contractor's assertions. The Contracting Officer reserves the right to add the Contractor's assertions to the DRAL and validate any listed assertion, at a later date, IAW the procedures in the R-DFARS.252.227-7997, Validation of Restrictive Markings on Technical Data, clause of this contract. The negotiated DRAL will be an attachment to the contract. Nonconforming DRALs will be rejected.

Data Accession List (DAL) The Contractor shall update and maintain the DAL which includes contract-referenced data, existing data and internally generated data used by the Contractor to develop, test, and manage the program, and not otherwise delivered IAW a CDRL. The Contractor shall flow this requirement down to the subcontractors and suppliers and shall include their data on the DAL. Upon request, the Contractor shall deliver data items from the DAL.

(CDRL A068, DI-MGMT-81453B, Data Accession List (DAL)) Diminishing Manufacturing Sources and Materiel Shortages (DMSMS) The Contractor shall establish, implement, and maintain a proactive DMSMS management program encompassing the CM/MUOS system Group A Kit, and document standard operating procedures in a DMSMS Management Plan (DMP). This DMP shall address the CM/MUOS components from all levels of suppliers to forecast and address any parts supportability issues. As part of the DMSMS program the Contractor shall, to the maximum extent possible, maintain adequate competition among the sources. The Contractor shall identify solutions to resolve DMSMS issues to prevent delays to CM/MUOS production deliveries. The Contractor’s DMSMS solutions shall minimize impact to CM/MUOS life cycle cost and assess impacts to data rights, licenses, certification, training, Technical Orders, Operation Manuals, and sustainment (for example: supply chain and repair procedures). The Contractor shall address any DMSMS issues by the submittal of an Engineering Change Proposal (ECP). The Contractor shall use the SD-22 DoD DMSMS Guidebook, in establishing this program.

The Contractor shall identify and notify the Government of all issues related to the loss or impending loss of manufacturers and suppliers, and the obsolescence of all electronic and non-electronic parts, non-developmental items (NDI), and material required for performance of this contract. The Contractor shall deliver an Obsolescence Alert Notice, and DMSMS Health Assessment Report, to notify the Government of the status of obsolete components and obsolescence status reports and detail the status of obsolescence and mitigation steps.

(CDRL A121, DI-MGMT-81948, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan) (CDRL A157, DI-MGMT-81941, Obsolescence Alert Notice)

Deficiency Reporting The Contractor shall investigate, and report, any Group A Kit deficiencies IAW TO 00-35D-54. The Contractor shall provide a Deficiency Report (DR) including corrective action recommendations that identify, as applicable, any risks to the delivery schedule, as well as cost and duration estimates for development, test, manufacturing, and documentation management.

(CDRL A095, DI-MGMT-80258C, Acquisition and Sustainment Data Package (ASDP) Material Improvement Project (MIP) Report, Deficiency Report) System Integration Laboratory (SIL) Retrofit The Contractor shall manufacture/procure and deliver material to upgrade one (1) SIL located at Boeing Defense in Oklahoma City with the CM/MUOS configuration. The material is defined as Common Control Box (Part Number 827-18480, built from drawings 827-18480 thru 827-18485) and Crypto Fill Panel (Part Number 827-18490, built from drawings 827-18490 thru 827-18494).

The Contractor shall be available for reach back support for the material until it has been successfully installed into the SIL.

Security The Contractor shall provide basic program and information security. The Contractor shall continue to support program protection planning efforts required by the National Industrial Security Program Operating Manual including:

· Identification of critical program information

· System security engineering

· Anti-tamper

· Security classification guides

· Program protection cost estimates

· Other materials in support of program protection The Contractor shall comply with:

· FAR 40.302-3 Security Requirements,

· FAR 40.303 Basic Safeguarding of Covered Contractor Information,

· DFAR 252.204-7008 Compliance with Safeguarding Covered Defense Information Controls

· DFAR 252.204-7000 Disclosure of Information

· DFAR 252.204-7009 Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information

· DFAR 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting

The Contractor shall also conduct a security program in compliance with the requirements of the contract security classification specification (DD Form 254).

Program Protection The contractor shall deliver a Program Protection Implementation Plan (PPIP). The contractor shall integrate the PPIP activities in the Integrated Master Schedule (IMS). The contractor shall use the B-52 Crypto Modernization (CM)/Mobile User Objective System (MUOS) Program Protection Plan (PPP) to derive the requirements. Program Protection includes specific areas, detailed in the B-52 Crypto Modernization (CM)/Mobile User Objective System (MUOS) Program Protection Plan (PPP) (ANNEX D to the B-52 Platform PPP).

(CDRL A216, DI-MGMT-82144A, Program Protection Implementation Plan (PPIP)) Counterfeit Prevention Plan The Contractor shall develop, implement, and maintain a Counterfeit Prevention Plan in compliance with R-DFARS.252.246-7007 using the Society of Automotive Engineers (SAE) AS5553B, SAE AS6081, IDEA-STD-1010C or similar practices to prevent the inclusion of counterfeit parts or parts with malicious logic. The Counterfeit Prevention Plan shall include a description of the processes for reviewing suppliers and subcontractors and approving ones that meet appropriate counterfeit-avoidance criteria. The Contractor shall require its suppliers and subcontractors to participate in counterfeit prevention activities. The Contractor shall acquire parts using a trusted flow from supplier(s) accredited by the Defense Microelectronics Activity. The Contractor shall buy parts directly from Original Equipment Manufacturers (OEMs), Original Component Manufacturers (OCMs), and authorized distributors. The Contractor shall provide rationale for any exceptions to this and conduct a supply chain risk assessment to determine the potential risk of obtaining counterfeit parts from such sources. The Contractor shall have processes to detect the occurrence, reduce the likelihood of occurrence, and mitigate the consequences of products potentially containing counterfeit components or malicious functions. The Contractor shall establish testing and verification requirements for items not received from an OEM, OCM, or authorized distributor. The Contractor shall perform acceptance testing on the lowest Critical Components and components containing Critical Program Information. The Contractor shall describe the process of how suspected counterfeit, malicious, or confirmed counterfeit parts will be reported to the Government-Industry Data Exchange Program (GIDEP). The Contractor shall base the level of testing and verification on each item’s identified risk for counterfeit potential. The Contractor shall provide Certificates of Conformance indicating the parts were tested and are not counterfeit.

(CDRL A146, DI-MISC-81832, Counterfeit Prevention Plan)

Acronyms ACO- Administering Contract Office ANSI-American National Standard Institute ARC-210 - AN/ARC-210 – Radio ASTM-American Society for Testing Materials BOM- Bill of Materials CCP- Contractor Change Proposal CM/MUOS – Crypto Modernization / Mobile User Objective System CO- Contracting Officer DAL - Data Accession List DR - Deficiency Report DMSMS - Diminishing Manufacturing Sources and Material Shortages ECP- Engineering Change Proposal FRACAS - Failure Recording, Analysis and Corrective Action System GFE- Government Furnish Equipment GIDEP - Government-Industry Data Exchange Program IAW- In Accordance With IMS - Integrated Master Schedule IP-Internet Protocol IRA - Integrated Risk Assessment IUID - Item Unique Identification JREAP-A- Joint Range Extension Protocol –A NDI - Non-Developmental Items OCM - Original Component Manufacturers OEM – Original Equipment Manufacturer PHS&T - Packaging, Handling, Storage & Transportation PM-Program Manager PMP - Program Management Plan PMR - Program Management Reviews PPIP – Program Protection Implementation Plan PPP – Program Protection Plan RF- Radio Frequency RFP- Request for Variance R&M - Reliability & Maintainability SOW - Statement of Work SCRM - Supply Chain Risk Management SCN- Specification Change Notice SIL - System Integration Laboratory TCTO – Time Compliance Technical Order VMF- Variable message Format WBS - Work Breakdown Structure image1.jpeg