DRAFT DBRS SOW v3.3.docx

CUI

DEPARTMENT OF THE AIR FORCE

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA

STATEMENT OF WORK

C-17 Databus Recording System

FA8526 / FA8577

XX XX 2025

Distribution D. Distribution authorized to Department of Defense and U.S. DoD contractors only, CTI [21 March 2025]. Other requests for this document must be referred to the C-17 System Program Office, AFLCMC/WLM, 660 Eleventh Street, Robins AFB, GA 31098-2428.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

Controlled by: AFLCMC Controlled by: WLM CUI Category: PROCURE Distribution/Dissemination Control: D POC: Capt D’Morea Wicks, 225-532-7796

1. SCOPE

1.1 The Databus Recording System (DBRS) shall provide the ability to record all pertinent system/subsystem parameters, components, and flight profile data from all installed 1553/429 buses and fuel quantity computers on the C-17. A lack of detailed data capture leads to reactionary flight schedules that are a victim to unscheduled maintenance. The ability to capture/package clean & complete C-17 flight information, system parameters and component data (up to 4 TB) is necessary for the enterprise to forecast root-cause analysis. Fulfilling this requirement will lead to never-before-achieved levels of MWSAA, improved parts supportability, and a proactive understanding of fleet health.

1.2 This Statement of Work (SOW) specifies and sets forth the general requirements for the procurement of DBRS system. The general requirements can be found in section 4 of the SOW and the system requirements can be found in addendum xx. The DBRS LRU must be a commercial item and any NRE costs to meet system requirements shall be covered by the awarded vendor. The procured LRU’s will be utilized to support SIL testing, government flight tests, and fleetwide fielding. After contract award, the applicable units must be shipped to the C-17 integration team for lab testing and flight testing. At the conclusion of the verification test period, the fielding assets must be shipped to the installation location. Vendors will be evaluated on their compliance with criteria identified in section M of the RFP.

1.3 The acquisition of DBRS will be an IDIQ. The IDIQ will consist of a base and four (4) options. The base will consist of 12 PRU’s and the follow-on options will be executed as required based on the quantities needed. The total number of LRU’s procured in the IDIQ will be 253. Additionally, the base and each option executed will include the applicable number of SSD cards needed to support. The total number of SSD’s procured in the IDIQ will be 693.

2. APPLICABLE DOCUMENTS

3. ACRONYMS and DEFINITIONS

4. REQUIREMENTS

4.1. Program Management

4.1.1. The Contractor shall manage, control, and report activities applicable to the deliverance of the DBRS LRU. The Contractor shall report any anomalies that disrupt scheduled delivery of the DBRS LRU within 3 business days of an identified delay to the C-17 SPO. The contractor shall provide commercial DBRS LRU’s and SSD cards compliant with the system requirements data listed in addendum xx. The contractor shall perform preliminary testing to demonstrate the DBRS system capability to meet the SRD requirements and is airworthy before entering government DT/OT phase.

CDRL A234, DI-MGMT-81178, Report, Production or Delivery Problem(s)

4.1.2. Government Furnished Information. The contractor shall provide required source data to integrate the DBRS LRU onto the C-17 aircraft. The GFI will be provided to the C-17 primary integrator upon contract award.

4.2. General Requirements

4.2.1. General Requirements. The Contractor shall provide the services required to manufacture, support integration, qualify, and certify an integrated, open architecture databus recorder solution that captures all databus traffic on the C-17A. The Contractor shall provide source data necessary to update technical publications impacted by the DBRS modification. These services include PM, manufacturing, system integration support, T&E support, PS, LRIP,

4.2.2. Period of Performance.

Performance shall occur from FY26-30 as determined by exercised options of the IDIQ contract.

4.2.3. Contract Data Requirements List (CDRL).

DATA

ITEM

PARAGRAPH

NUMBER

Deliverables A&A Project Plan, ATO Package and IATT Package 4.7.2

Technical Report, Engineering Verification Report 4.7.1

Utilization Matrix (HSFUM) 4.6.7

Document – Operator (HEDAD-O) 4.4.3

Verification Procedures (E3VP) 4.7.3

Effects (E3) Verification Report (E3VR) 4.7.3

Test Procedures (EMITP) 4.7.3

Activity, Validation and Verification Report 4.6.7

Management Plan 4.6.2

Special Test Equipment (STE) 4.3.3

Technical Report/Environmental Gap Analysis 4.7.5

4.2.4. Deliverables. The Contractor shall ensure contract data are generated and delivered through Air Force-Product Lifecycle Management Teamcenter or like PLM tool (TBD) to meet the requirements of the Contract Data Requirements List (CDRL) Data Item Description (DID) and SOW. The Contractor shall provide all items shown on the CDRL(s) attached to each individual task.

4.2.5. CDRL Receipt. 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.2.6. Post-Award Conference. The Contractor shall host a post-award conference IAW FAR 42.5, Post-Award Orientation for the Government and Contractor to achieve a clear, mutual understanding of contract requirements and resolve potential problems. The Contractor shall present, at a minimum, its approach to meeting the contract’s cost, schedule and performance requirements. The Contractor shall hold the post-award conference at a time mutually agreed between the parties, but no later than 60 calendar days after contract award.

4.2.7. Reviews and Technical Interchange Meetings (TIMs). The Contractor shall support weekly programmatic and technical reviews and TIMs (i.e. working groups) to provide status, demonstrate compliance and resolve open issues. The Contractor shall support each meeting via Microsoft Teams or other Government-approved method (e.g. phone, in-person). Prior to each review, the Contractor shall deliver the agenda and the material to be briefed. Following each review, the Contractor shall deliver final briefing material, meeting minutes and action items, to include action item status, points of contact 9POC), and recommended closure date. The Contractor may hold reviews in conjunction with other meetings. The Contractor shall hold the reviews at a site and date agreed upon by the Government PCO and the Contractor.

4.3. System Requirements

4.3.1. Interface Design. The Contractor shall capture each physical, functional, and logical interface of co-functioning components (both internal and external). The Contractor shall use industry standard interfaces IAW the DBRS SRD and Government Information Support Plan. The Contractor shall not use proprietary interfaces in the DBRS design. The Contractor shall manage each interface at the CI level. The Contractor shall provide DBRS interface requirements to its suppliers.

4.3.2. Reserve Capacity Requirements. The Contractor shall define, manage, track, and verify computer resources (hardware and software) growth and reserve capacity requirements as defined in the system and subsystem specifications. This includes reserve capacity for memory, throughput, Input/Output (I/O), and network.

4.3.3. Support Equipment (SE). The Contractor shall identify, design, or procure any SE (Test Measurement Diagnostic Equipment (TMDE), Automated Test Sets, etc.) required to operate the DBRS system. All SE/TMDE and tools requiring calibration shall be delivered with calibration certificates, calibration procedures, and calibration reports as required by T.O. 00-20-14 as a minimum. The Contractor shall minimize or eliminate peculiar support equipment. The Contractor shall generate a SE Recommendation Data (SERD) form for each new SE item IAW the following priority:

A. Common GFP already in inventory or being developed under Government contract B. Modified, common GFP C. Commercially available items that meet technical and logistical requirements D. Modified commercially available equipment E. New/developmental PSE – note: any required PSE must be approved by AFLCMC/WLME SE quantity will be defined by estimating the quantity and location of aircraft retrofit by this project.

CDRL A188, DI-SESS-82366, Peculiar Support Equipment (PSE) and Special Test Equipment (STE) CDRL A174, DI-QCIC-80798C/T, Calibration Certificate / Report

4.3.4. Support Equipment Data. The Contractor shall identify and document organizational and intermediate SE requirements, including Peculiar and Common Support Equipment, and follow and manage the Support Equipment Recommendation Data (SERD) process. The Contractor shall develop or modify depot and intermediate level Test Requirements Documents (TRD) for both hardware and software revisions.

4.4. Design Considerations

4.4.1. Airworthiness Certification Support. The Contractor shall provide documentation to support airworthiness activities for the USAF fleet to obtain a (AW) certification per AFPD 62-6, USAF Airworthiness; AFI 62-601, USAF Airworthiness; MIL-HDBK-516C, Airworthiness Certification Criteria; and all applicable Airworthiness Bulletins (AWB). This support shall include provision of documentation that includes, but is not limited to, structural and electrical analysis and test reports, environmental test reports, drawings, material certifications, and manufacturer’s technical data. This supports creation of Airworthiness Risk Assessment and Acceptance and Military Flight Release. Documentation shall support determination of the severity and probability of each identified hazard, identification of mitigations to minimize the risk, and identification of work remaining to achieve compliance.

4.4.2. Human Systems Integration (HSI). The Contractor shall conduct user evaluations to determine if the design is acceptable and intuitive for users trained on the install, use, and removal of the system.

4.4.3. Human Engineering Design Approach Document – Operator (HEDAD-O). The Contractor shall develop, maintain, and deliver the HEDAD-O that describes new or altered operator interfaces, specifically describing equipment that interfaces with the operator IAW MIL-STD-1472G, Human Engineering.

CDRL A137, DI-HFAC-80746C/T, Human Engineering Design Approach Document – Operator (HEDAD-O)

4.4.4. RM&A Allocations and Predictions. The Contractor shall develop and deliver RM&A allocations and predictions for the installed unit. The Contractor shall base RM&A predictions on operational data whenever such data is available.

CDRL A145, DI-SESS-81497B, Reliability and Maintainability Predictions Report

4.4.5. RM&A Test Planning and Reporting. The Contractor shall develop a RM&A test plan to show compliance with all relevant RM&A requirements within the SOW, SRD, or other Military standard documents referenced. The Contractor shall document the results of all testing in an RM&A test report for review and verification that requirements have been met.

4.5. Metrics

4.5.1. Technical Performance Measures (TPM). The Contractor shall establish a process to identify, track, report, and manage TPMs. TPMs shall be technical parameters that require close inspection and/or analysis to include risks, Key Performance Parameters (KPPs), and other system performance requirements requiring engineering management. TPMs shall include planning schedules to reach expected TPM values. The Contractor shall conduct an in-depth technical review of TPM data on a quarterly basis to include: TPMs and associated technical parameter data, trend charts, changes, root cause analyses, risks, action plans, and all other associated supporting data. The Contractor shall discuss TPMs during design reviews, TIMs, IPT, Working Groups, PMRs, Risk Review Boards (RRBs), IAW the C-17 SEP. The Contractor shall incorporate TPMs into the Contractor’s internal program and technical decision-making processes. The Contractor shall pass down all TPM requirements to lower-tier subcontractors and suppliers. TPMs that are used to mitigate risks shall be included, tracked, and reported with the applicable risk. The Contractor shall report TPM data during PMR or technical reviews.

4.5.2. Quality and Manufacturing Metrics. The Contractor shall submit quality and manufacturing metrics that report the Contractor’s performance and progress. The metrics shall include production operations, cost, schedule, and quality metrics to monitor and show the effectiveness of the Contractor’s manufacturing, quality, and supplier management programs. Metrics shall be presented at design, technical and PMRs.

4.6. Manufacturing and Quality

4.6.1. Value Engineering. The Contractor shall implement value engineering to reduce cost and improve quality and performance of the system. The contractor shall follow SD-24, Value Engineering: A Guidebook of Best Practices and Tools, in determining best practices for value engineering.

4.6.2. Parts Management. The Contractor shall establish and maintain a parts management program IAW MIL-STD-11991B, General Standard for Parts, Materials, and Processes. The Contractor shall optimize part reliability and standardization to minimize logistics footprint and total lifecycle cost. The Contractor shall source parts from the Federal Logistics Information System (FLIS), Qualified Products List (QPL), or Qualified Manufacturers List (QML). The Contractor shall deliver a request for deviation/waiver to use non-standard parts (i.e. parts not listed in FLIS, QPL, or QML). The Contractor shall document its approach in a Parts Management Plan (PMP). The Contractor may use SD-19, Parts Management Guide, as a Guide.

CDRL A187, DI-STDZ-81993, Parts, Materials, and Processed (PM&P) Management Plan

4.6.3. Diminishing Manufacturing Sources and Material Shortages (DMSMS). The Contractor shall establish and maintain a DMSMS program to manage the impending loss of manufacturers and parts/material suppliers. The Contractor shall use SD-22, A Guidebook of Best Practices for Implementing a Robust DMSMS Management Program and MIL-HDBK-896, Manufacturing and Quality Program, as guides. The Contractor shall identify DMSMS solutions that consider lowest lifecycle cost and impacts to data rights, licenses, certification, training, TOs, Operational Manuals, and sustainment. The Contractor shall report identified DMSMS issues and proposed solutions for Government approval within sixty (60) calendar days of its discovery. The Contractor-supplied data shall be used in Government-approved DMSMS forecasting tool using an agreed-to data standard. The Contractor shall link its DMSMS tool to its IDE.

CDRL A012, DI-MGMT-81941/T, Obsolescence Alert Notice

4.6.4. Government-Industry Data Exchange Program (GIDEP). The Contractor shall participate in GIDEP in accordance with GIDEP Operations Manual S0300- BT-PRO-010 and SD-25, GIDEP Operating Policies and Procedures. The Contractor shall deliver GIDEP alerts and advisories as required. The Contractor shall:

A. Receive alerts and advisories from GIDEP and other agencies, or internal sources.

B. Determine any impact to its product design and already manufactured hardware.

C. Implement corrective actions when design and/or produced hardware are affected.

4.6.5. Counterfeit Electronic Parts. The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory. The system shall incorporate processes/procedures to address the requirements listed in DFARS 246.870 Contractors’ Counterfeit Electronic Part Detection and Avoidance Systems; DFARS 252.244-7001 Contractor Purchasing System Administration; DFARS 252.246-7007 Contractor Counterfeit Electronic Part Detection and Avoidance System; DFARS 252.246-7008 Sources of Electronic Parts; and Aerospace Standard (AS) 5553D Fraudulent/Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition.

CDRL A178, DI-MISC-81832, Counterfeit Prevention Plan

4.6.6. Quality Management System (QMS). The Contractor shall establish a Quality Management System IAW AS9100D, Quality Management Systems-Requirements for Aviation, Space, and Defense Organizations to ensure the DBRS meets the technical requirements. The Contractor shall document its approach to meeting the AS9100D requirements in a Quality Assurance Program Plan (QAPP). 100% compliance with the QMS is required.

CDRL A076, DI-MGMT-82184, Quality Management System (QMS) CDRL A153, DI-QCIC-81794A, Quality Assurance Program Plan (QAPP)

4.6.7. Qualification Kits. The Contractor shall deliver 11 complete DBRS LRUs IAW the approved TDP for SIL and aircraft integration testing. The Contractor shall procure 22 spare kits, for a total of 253 kits. The Contractor shall maintain configuration control of each kit IAW its CMP. The Contractor shall deliver each kit to the installation location. The Contractor shall mark each kit and repairable sub-assembly with a permanent machine-readable IUID. The Contractor shall provide kit status updates to the Government.

CDRL A135, DI-IPSC-82367/T, Hardware, Software and Firmware Utilization Matrix (HSFUM) CDRL A170, DI-MGMT-81803/T, Item Unique Identification (IUID) IUID Marking Plan CDRL A171, DI-MGMT-81804A, Item Unique Identification (IUID) IUID Marking Activity, Validation and Verification Report

4.6.8. Spares and Peculiar Support Equipment (PSE). The Contractor shall identify and deliver DBRS spares, and support equipment needed to operate and maintain the DBRS system during integrated DT/OT and OT&E. The Contractor shall provide transportation and storage as required.

4.6.9. Packaging, Handling, Storage, Shipping, and Transportation The Contractor shall be responsible for the packaging, handling, storage, shipping and transportation IAW the following paragraphs and applicable AFMC Form 158.

The Contractor shall combine all components into a single package for install kits. The Contractor shall package the kits per the guidelines in MIL-STD-2073-1E, Standard Practice for Military Packaging. Shipping containers received, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reutilization. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of AFMC Form 158. Kits will be marked per the guidelines in MIL-STD-129R. To facilitate the installation of trial install, kit proof and production kits, the kits shall be packaged by individual installation drawing with the appropriate parts/hardware, and a packing list of comprised material in each installation sub-kit.

4.6.10. Failure Mode Analysis

The Contractor shall provide a Failure Mode, Effects & Criticality Analysis (FMECA) to identify, analyze and resolve single item failures resulting in impacts to potential mission success, performance, personnel safety and maintainability. The FMECA shall address all the following:

a) Test failure descriptions reported within five business days of an occurrence

b) Identification of the failure mode(s), historical trends, and statistical failure distribution update with root cause identification and corrective action for each failed test within 10 business days of an occurrence as an objective or 15 business days of an occurrence as a threshold requirement.

c) The status of design and process corrective actions and risk-mitigation decisions

d) Completion of all corrective actions and risk-mitigation tasks within 30 business days after Government acceptance of corrective action

e) The effectiveness of all implemented corrective actions

f) Lessons learned CDRL A223, DI-SESS-81495C, Failure Modes, Effects, and Critical Analysis (FMECA)

4.6.11. Provisioning

The Contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability IAW the Air Force Initial Provisioning Performance Specification (IPPS). MIL-PRF-49506 should be used as a guide. Format must be consistent with existing government Provisioning data system (D220).

Provisioning Guidance Conference The Contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the Contractor. The Contractor shall provide draft agenda and draft presentation materials ten (10) working days prior to the scheduled presentation. The Contractor shall provide conference minutes five (5) working days after the conference.

CDRL A001, DI-ADMN-81249C, Meeting Agenda CDRL A002. DI-ADMN-81250C, Meeting Minutes CDRL A021, DI-ADMN-81373, Presentation Material CDRL A235, DI-SESS-81874, Engineering Data for Provisioning (EDFP) CDRL A236, DI-SESS-81758A, Logistics Product Data

4.6.12. Integrated Logistics Support Plan (ILSP)

The Contractor shall develop, maintain, and deliver an ILSP.

CDRL A182, DI-ILSS-80095, Integrated Logistics Support Plan

4.6.13. Storage

The Contractor shall provide secure storage for all system components until production kits are assembled and packaged. During storage, the assets shall be preserved and capable of withstanding exposure to ambient temperature extremes.

4.6.14. Shipping/Transportation

The Contractor shall ship the units by any traceable means to locations specified by the Government.

4.7. Test, Evaluation, and Analysis

4.7.1. Systems Integration Lab (SIL) Testing. The Contractor shall develop an LRU to support system level qualification of the DBRS. The LRU shall be capable of integration into the existing SIL to support all flying configurations. The LRU hardware and software shall be configuration managed in accordance with the Configuration Management Plan. The Contractor shall support SIL testing to integrate software avionics suite prior to installation on aircraft. The Contractor shall use the SIL as a verification point prior to release for aircraft testing and acceptance. The Contractor shall track all software deficiencies found during SIL testing. The Contractor shall notify the government prior to each verification tests for the Government to witness scheduled testing. The Contractor shall conduct at least one final prototyping event in the SIL prior to CDR to verify critical system requirements are met. The Contractor’s LRU shall:

a. Record all aircrew and operator inputs, bus signals, and switching positions

CDRL A116, DI-SESS-82361/T, Acquisition and Sustainment Data Package (ASDP) Technical Report, Engineering Verification Report

4.7.2. Cybersecurity. The Contractor shall identify, allocate, evaluate, and implement the applicable cybersecurity controls, corresponding to the cybersecurity requirements documented in the System Requirements Document (SRD), for the DBRS system IAW Committee on National Security Systems Instruction (CNSSI) No. 1253 and National Institute of Standards and Technology Special Publication (NIST SP) 800-53 Rev 5, tailored with the Aircraft security control overlay. Recommendations shall be provided for resolving cybersecurity issues. Additionally, the Contractor shall provide a risk analysis for acceptance of the shortfalls of cybersecurity controls in the as implemented systems. The Contractor shall provide support, source data and analysis required to support the Government in obtaining assessment and authorization for the system IAW DoDI 8510.01, Risk Management Framework for DoD Systems. The Contractor shall integrate Cybersecurity and Cybersecurity risk management into its overall systems engineering, acquisition, test and evaluation, and risk management processes IAW DoDI 8500.01, Cybersecurity; DoDI 8510.01, Risk Management Framework for DoD Information Technology; and Air Force Instructions (AFI) 17-101_DAFGM2022-01, Risk Management Framework for Department of the Air Force Information Technology. The Contractor shall support successful issuance of Interim Authority to Test (IATT) and Authority to Operate (ATO) as needed. The Contractor shall link all cybersecurity data/artifacts to the lowest relevant level. The Contractor shall update the cybersecurity baseline documented in the System Security Plan to reflect the implemented modifications. The Contractor shall identify and implement the applicable controls IAW with Security Controls Traceability Matrix. The Contractor shall develop a DBRS System Security Plan that identifies how each implemented security control will be evaluated. The results of the security control evaluation shall be documented in the Security Assessment Report and Risk Assessment Report. The Contractor shall update the Plan of Actions and Milestones with all non-compliant controls as applicable. Cybersecurity for product integration shall include the incorporation of technical and non- technical requirements to protect C-17A systems and data from unauthorized access and exploitation. The Contractor shall participate in the Government-led System Security Engineering Working Group (SSEWG). The Contractor shall ensure the design does not inhibit future implementation of sanitization and/or declassification through software. The Contractor shall deliver a DBRS Cybersecurity Test Plan and DBRS Cybersecurity Test Report that shall support the Government accreditation efforts for the C-17A system to comply with Cybersecurity policies and criteria and identified per the Government approved IMS. The Contractor shall deliver Cybersecurity data for Government review at all design reviews and applicable TIMs.

CDRL A079, DI-MGMT-82001A/T, DOD Risk Management Framework (RMF) Package Deliverables CDRL A163, DI-MGMT-82377, Cyber Test Plan CDRL A164, DI-MGMT-82142A, Cyber Test Report

4.7.3. Environmental Qualification & Reliability Testing. The Contractor shall provide specifications attesting to completed qualification testing (e.g., accelerated life testing and environmental stress screening) to verify the DBRS meets the environmental and reliability requirements specified in the SRD. The Contractor shall support environmental MIL-STD-461G, Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, and MIL-STD-464D, Electromagnetic Environmental Effects, Requirements for Systems.

CDRL A160, DI-EMCS-80201C, Electromagnetic Interference Test Procedures (EMITP) CDRL A161, DI-EMCS-80200C, Electromagnetic Interference Test Report (EMITR) CDRL A158, DI-EMCS-81541B, Electromagnetic Environmental Effects (E3) Verification Procedures (E3VP) CDRL A159, DI-EMCS-81542B, Electromagnetic Environmental Effects (E3) Verification Report (E3VR)

4.7.4. Operational Utility Evaluation (OUE). The Contractor shall support the Government’s testing of the DBRS. The Contractor shall deliver the engineering design data and installation procedures (e.g., preliminary TOs, verified TCTOs) to support the modification and de-modification of the test aircraft. The Contractor shall deliver Contractor-specific instrumentation requirements to be installed on the test aircraft. The Contractor shall support Government safety reviews in conjunction with internal Contractor safety planning. The Contractor shall participate in pre-test and post-test mission briefings and support analysis of test results. If requested, the Contractor shall provide on-site support during testing. The Contractor shall support the Government ITT to demonstrate OT&E readiness certification IAW DAFMAN 63-119, Mission-Oriented Test Readiness Certification. As requested, the Contractor shall assist test personnel and maintenance personnel on anomalies encountered and participate in T&E DRRBs.

CDRL A233, DI-SESS-81003F, Commercial Engineering Design Data and Associated Lists

4.7.5. Environmental Gap Analysis. The Contractor shall deliver an environmental gap analysis. The gap analysis shall document whether each LRU is compliant with all the environmental requirements specified in the SRD. Although the SRD specifies military test standards, equivalent commercial standards may be used to meet the test limits of the SRD with a test equivalency analysis/justification. Non-compliances shall be identified and assigned a risk, IAW MIL-STD-882E, to determine if further analysis and/or testing is required. Environmental Test reports used to qualify airworthiness of all LRUs/components shall be included as an attachment to the gap analysis.

CDRL A237, DI-SESS-82361, Acquisition and Sustainment Data Package (ASDP) Technical Report, Environmental Gap Analysis

4.7.6. Thermal Analysis. The Contractor shall accomplish, document, and deliver a thermal/cooling analysis to ensure the installed system operates and endures the aircraft cooling requirements as described in the SRD.

CDRL A123, DI-SESS-82361/T, Acquisition and Sustainment Data Package (ASDP) Technical Report, Thermal Analysis

4.8. Program Security

4.8.1. In performance of the contract, the Contractor shall comply with all applicable security requirements listed in the DD Form 254 for the C-17 Globemaster III Sustainment Contract (G3).

4.8.2. Operations Security (OPSEC). The contractor shall ensure all information, classified and unclassified, must be limited in distribution on a “need to know” basis. All methods of communication must be safeguarded. Everyone must take the responsibility to assure the security of all information. The protection of information transmitted between the program directorate, contractors and other agencies must be in accordance, at minimum, with governing directives.

4.8.3. Cyber Test

4.8.3.1. Program Protection. The Government shall provide a draft Program Protection Plan (PPP) as Government Furnished Information (GFI) at contract award. The Contractor shall support the Government to develop and approve an updated, Contractor design-specific PPP annex, including, but not limited to, Computer Program Information (CPI) identification, Anti-Tamper (AT), Criticality Analysis, vulnerability identification, risk assessment, countermeasure development, Supply Chain Risk Management (SCRM), counterfeit prevention, software assurance, and cybersecurity. The Contractor developed PPP annex shall be compliant with the security requirements imparted by the DD Form 254, DoD Contract Security Classification Specification, the NISPOM, the PPP and applicable DoD/AF Information Assurance (IA) policies.

CDRL A028, DI-MGMT-82144A/T, Program Protection Implementation Plan

4.8.3.2. Supply Chain Risk Management (SCRM). The Contractor shall identify, assess, plan for, and mitigate actual or potential threats, vulnerabilities, and disruptions to the FDR supply chain throughout the duration of the contract to ensure mission effectiveness. The Contractor shall inform and include the Government in any mitigations or alterations to the program. 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 Air Force operations; and drive materiel cost increases to the program. 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 notify in writing the identified actual and potential supply chain risks. The Contractor's SCRM program and processes shall apply to the prime 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. As part of the overall SCRM approach, the Contractor shall establish, document and maintain documentation about subcontractors/vendors for all parts that will be used for Government contracts. The Contractor shall continuously monitor their sources of supply for unknown, unauthorized, non-certified, or unqualified sources providing parts or services from any sub-tier supplier within the contractor's supply chain. The Contractor shall investigate and submit findings to include root causes, impacts and a corrective action.

CDRL A194, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan CDRL A195, DI-MGMT-82255A, Supply Chain Risk Register

4.8.3.3 Packaging Handling, Storage, Shipping, and Transportation

5. Configuration Management

5.1. Configuration Management. The Contractor shall perform configuration and data management to support the Databus Recording System (DBRS) configuration IAW SAE EIA-649-1A, Configuration Management Requirements for Defense Contracts, and the latest Government Configuration Management Plan. The Contractor shall plan to manage the FDR configuration throughout the life cycle, identify configuration items to be controlled, manage configuration changes, account for configuration status, and conduct configuration verification and audits. The Contractor may use MIL-HDBK-61B, Configuration Management Guidance, and SAE EIA-649C, Configuration Management Standard, and GEIA-HB-649, Configuration Management Standard Implementation Guide, as guides.

5.2. Configuration Management Planning. The contractor shall provide a Supplier’s Configuration Management Plan (SCMP) for the DBRS. The contractor shall specify parts numbers for each DBRS and sub-components in the Supplier’s CMP. The Contractor shall maintain traceability and currency among all product documentation and system software and equipment. The Contractor shall document its configuration management process in a Configuration Management Plan (CMP), to include configuration management of its system.

CDRL A067, DI-SESS-80858D/T, Supplier’s Configuration Management Plan (CMP)

5.3. Configuration Change Management. After the DBRS is completed, the contractor shall provide Engineering Change Proposals (ECP), if requested by the USG to modify the DBRS. The contractor shall submit Requests for Variance (RFV) from the approved SSS to the USG when required. The contractor shall provide Contract Change Proposals (CCP) when requested by the USG. Class I and Class II changes affecting form, fit, function and/or interface to the C-17 system and are subject to Government System Program Manager or delegate approval at a Configuration Control Board (CCB).

CDRL A064, DI-SESS-80639E/T, Engineering Change Proposal (ECP) CDRL A077, DI-SESS-80640E, Request for Variance (RFV) CDRL A127, DI-ADMN-81401C, Contract Change Proposal (CCP)

5.4. Audits If requested by the USG, the contractor shall conduct and support Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) with the USG for each new or modified part. FCAs/PCAs shall be addressed in the contractor’s CMP. The contractor shall notify the USG of upcoming suppliers/vendors FCAs/PCAs.

6. Data Management

6.1. Data Management. The Contractor shall establish and maintain data management procedures for the preparation, quality control, administration, and delivery of data required by the CDRL. The Contractor shall prepare, maintain, and track the contract data status, schedule, and ensure data deliveries. The data shall be available through electronic access or as directed by the Government. The Contractor shall mark all deliverable technical documents, data, and information appropriately before primary distribution is accomplished IAW DoD Directive 5230.24, Distribution Statements on DoD Technical Information. The Contractor shall maintain the current implemented data management program for generating, acquiring, identifying, verifying Government data rights, statusing, planning, and controlling technical and management data and related information; provide continued Government access to a Contractor data system that supports an integrated digital environment for delivery, storage, and archiving of informal documents and formal CDRL documents; and continue to plan, schedule, and control data so that the data essential for program milestones (e.g., design reviews and audits) is available consistent with the IMS. All data rights markings shall be appropriate and justified per the DFARS for all data generated under the program.

6.2. Data Accession List (DAL). The Government shall be provided rights in accordance with the contract for all technical data, models, computer software, and computer software documentation. The Contractor shall provide a Data Accession List (DAL) listing all data, models, and software developed by the Contractor and maintained for accomplishment of the contract which is not provided under a Contract Data Requirements List (CDRL). The Contractor shall maintain and make available data listed in the DAL as requested by the Government. The Government’s access to the Contractor’s data shall be as required by the provisions of the contract.

CDRL A003, DI-MGMT-81453C, Data Accession List (DAL)

CUI

image1.jpg