CSMULSSOW3Dec.pdf

Solicitation #: FA8110-19-R-0001

UNCLASSIFIED

Statement of Work (SOW)

For

B-2 Flight Data Recorder (FDR) / Crash Survivable Memory Unit (CSMU) Subsystem Modernization Program

AIR FORCE MATERIEL COMMAND

Air Force Life Cycle Management Center B-2 Sustainment Branch

Tinker AFB, OK 73145-3019

L3 Aviation Products

03 December 18

Table of Contents

1.0 INTRODUCTION

1.1 Background

1.2 Scope

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Other Documents

3.0 REQUIREMENTS

3.1 Air Vehicle

3.1.1 Developmental Units

3.1.2 Production Deliverables (contract option)

3.2 System Engineering

3.2.1 Program Security

3.2.2 Sanitization

3.2.3 Airworthiness Certification

3.2.4 Obsolescence

3.2.5 System Security Engineering / Cyber Resiliency / Cybersecurity

3.2.6 Reliability Availability and Maintainability

3.2.7 Programmatic Environmental Safety and Occupational Health

3.2.8 Engineering Support

3.3 Program Management

3.3.1 Program Management

3.3.1.1 Interaction with Integration Contractor

3.3.1.2 Meetings and Design Reviews

3.3.1.3 Plans, Reports, and Presentations

3.3.2 Risk Management Program

3.3.3 Program Control

3.3.3.1 Contractor Work Breakdown Structure

3.3.3.2 Project Schedule

3.3.3.3 Status and Cost Tracking

3.3.4 Product Support

3.4 System Test and Evaluation

3.4.1 Developmental Test and Evaluation

3.4.2 Operational Test and Evaluation

3.5 Training

3.6 Data

3.6.1 Technical Data

3.6.2 Technical Orders (Field Level)

3.6.3 Software Documentation

3.6.4 Configuration and Data Management

3.6.4.1 Configuration Management

3.6.4.2 Data Management

3.6.4.3 Engineering Changes

3.6.5 Procurement Specification

3.6.6 Other Data

3.7 Peculiar Support Equipment (see partial in 3.1.2d)

3.8 Common Support Equipment

3.9 Operational/Site Activation – Not Applicable

3.10 Industrial Facilities – Not Applicable

3.11 Initial Spares and Repair Parts – See paragraph 3.1.2

1.0 INTRODUCTION

The purpose of this Statement of Work (SOW) is to define the requirements to be accomplished by the contractor to efficiently and effectively meet the Air Force requirement to alleviate Flight Data Recorder (FDR) Crash Survivable Memory Unit (CSMU) obsolescence/sustainability issues and meet the performance requirement from AFH 63-1402 to increase recording capability/duration of the CSMU in the B-2 Spirit FDR subsystem. There are six general tasks the contractor shall be required to accomplish. The tasks are:

a. Nonrecurring engineering (NRE) design including adapting the L3 commercial off-the-shelf (COTS) Cockpit Voice/Flight Data Recorder SRVIVRTM for use as the replacement CSMU, designing and engineering a modification to the government-furnished property (GFP) Flight Data Recorder Processor (FDRP) to provide 28 volt direct current (VDC) current versus 9 VDC, modifying the FDRP Operational Flight Program (OFP) to record additional flight information data (FID), verifying system operation as modified, and updating technical documentation (technical orders and specifications).

b. To support NRE, the government will provide L3 three (3) FDRP line replaceable units (LRU) to be modified and integrated with the SRVIVR CSMU. Those units will be used for testing in the B-2 Weapon System Support Center (WSSC) and ground/flight test. Once NRE is completed and the technical solution has been integrated into the B-2 and successfully tested and approved, the contractor shall manufacture and deliver replacement CSMUs, modify GFP FDRPs, and provide an updated FDRP OFP. The FDRPs will be modified in accordance with (IAW) an asset rotation plan (to be briefed at contract kickoff) to allow ongoing operations of B-2 aircraft until all FDRPs have been modified.

c. Delivery of a production-level technical data package for the FDR subsystem (CSMU, FDRP, FDRP OFP) and miscellaneous hardware.

d. Providing Post-Production Support (PPS) for FDR subsystem components starting at delivery of production units and continuing to the end of the performance period established under this delivery order. Anticipated PPS activities include: (1) engineering support to address any product quality issues, (2) repair for delivered repairable items, and

(3) repair of delivered download laptops.

e. Providing spare CSMU adaptor hardware for initial provisioning.

f. L3 is also expected to work with and support the integration contractor for this effort.

1.1 Background

The B-2 FDR is deficient because it does not record 25 hours of FID, is not equipped with an Underwater Locater Beacon (ULB), and it does not record all the required FID parameters that are currently available on the various 1553 data buses on the B-2. Additionally, the legacy CSMU is obsolete and key components can no longer be procured making it unsupportable over the projected life of the weapon system. The technical deficiencies of the legacy CSMU were highlighted during investigation of the Air Vehicle 89-0127 mishap on Guam. Multiple Engineering Investigations and white papers were completed following the mishap identifying the deficiencies and providing the path forward for this modernization program.

1.2 Scope

The purpose of this project is to complete NRE required to replace the legacy B-2 CSMU (NSN 6610-01 368-0232) with a COTS CSMU. The NRE effort includes (1) adapting the L3 COTS SRVIVR for use with the B-2 legacy FDRP, (2) modifying the FDRP to provide SRVIVR with 28 VDC power, (3) adding an ULB, and (4) modifying the FDRP OFP to allow recording of additional FID currently available on the 1553 data buses monitored by the FDRP.

Additionally, this effort will support B-2 integration and test and evaluation that will be conducted on behalf of the government by Northrop Grumman, the B-2 platform integrator and configuration management lead. To support WSSC testing, the contractor shall meet with the government program manager (PM) and WSSC lead to identify the resources required and the schedule of integration and testing activities, which require development contractor participation. The contractor shall deliver the software documentation identified in paragraph

3.6.3 for use by the integration contractor to develop the WSSC Software Integration Lab (SIL) test procedures. The contractor shall make available appropriate subject matter experts (SME) to support the lab testing planning and execution.

This effort includes modifying the FDRP OFP to add and/or delete FID in accordance with the recommendations in the Final Report for B-2 Engineering Investigation R10026 ''Improved FDR Parameters 2" dated 25 January 2011. The replacement CSMU shall be fully integrated and interoperable with the legacy FDRP (NSN 6610-01-368-8344). The replacement CSMU shall be equipped with an ULB. Additionally, this effort includes any development testing and installation for modifications within the FDRP that are required to allow required electrical power to be provided to the replacement CSMU. The legacy CSMU requires 9 VDC power and all known COTS CSMUs currently on the market require 28 VDC power. The replacement CSMU and ULB must fit within the space constraints available and must be compatible with legacy mechanical and electronic interfaces.

2.0 APPLICABLE DOCUMENTS

The following is a list of applicable technical documents and original equipment manufacturer (OEM) documents/drawings. The list is for reference only; it is not intended to be all-inclusive and does not relieve the contractor from showing due diligence in regard to referencing documents applicable to the subject SOW.

2.1 Government Documents

The tables below identify applicable technical documents and non-proprietary OEM documents:

Document Number Document Date Description

EAF1212-002 01 December 2013 B-2 Reliability, Availability, and Maintainability (RAM) Plan

MIL-STD-31000A 26 February 2013 Technical Data Packages DoDI 5230.24 23 August 2012 Distribution Statements on Technical Documents

ISO/IEC/IEEE12027 November 2017 Systems and Software Engineering-Software Life Cycle Processes

Document Number Document Date Description DAA3322P001C 16 October 1992 Flight Data Recorder Procurement Specification

B-2 CSMU SRD 28 June 2018 B-2 CSMU Addendum to Procurement Specification for Flight Data Recorder, Additional System Requirements Document (SRD)

2.2 Other Documents

Document Number Document Date Description NGC Engineering Investigation R08068 05 November 2009 Final Report Improved FDR Parameters

NGC Engineering Investigation R10026 25 January 2011 Final Report Improved FDR Parameters

3.0 REQUIREMENTS

The work required by this delivery order shall be performed IAW the B-2 CSMU Additional SRD (Addendum to Procurement Specification for FDR) and this SOW. The contractor shall perform required administrative, technical, material, schedule, and financial management functions and shall track and report the status of the directed effort to achieve the SOW objectives to the government PM during the program period of performance (POP). The contractor shall deliver the documentation and execute the contract in accordance with the integrated master schedule (IMS). Unless otherwise specified, all time spans given are in calendar days. When the required delivery date falls on a weekend or holiday, the contractor shall deliver the subject deliverable on the next business day.

3.1 Air Vehicle

The contractor shall perform NRE necessary to develop, test, and deliver a qualified and certified COTS CSMU and modified FDR through completion of work specifications updates, qualification, ground/flight test, and certification. The contractor shall perform system engineering to include requirements analysis, decomposition, and management; integration; and verification planning. The contractor shall identify, coordinate, and schedule all resources required to complete this effort excluding WSSC support. The contractor shall ensure the modified FDR components comply with current regulatory requirements. The contractor is not responsible for B-2 system limitations that preclude compliance with AFH 63-1402-specified FID requirements due to lack of digitized data for specified systems/components/parameters.

Based on the capabilities and operational system differences, the performance specification shall be updated to reflect results of this contract. Deviations from the specification may be required as a part of this effort. Any changes to the original specifications shall be submitted to the government in writing and approved in writing by the government. The contractor performance shall include the following:

a. Modify FDRP hardware

b. Modify FDRP OFP software

c. Modify processor card/assemblies

d. Replace CSMU (adapt COTS L3 SRVIVR for B-2)

e. Add Underwater Locater Beacon

f. Add pigtail and pigtail bracket

g. Add mounting adaptor plate (adapts bolt pattern)

h. Manufacture replacement CSMU design

i. Design and manufacture wiring pigtail and pigtail bracket

j. Provide Data Extraction Software Program (in Windows 10 operating system)

k. Provide ruggedized laptops for FID extraction

3.1.1 Developmental Units

a. The contractor shall produce and deliver three CSMU and three modified FDRP

(hardware and OFP) and associated mounting brackets and pigtail/pigtail brackets to support WSSC integration and flight test.

[Note: One of the developmental units shall be upgraded to production unit status for installation after testing is completed.]

3.1.2 Production Deliverables (contract option)

The contractor shall produce and deliver the following products:

a. CSMU

(1) 1 (one) adapted COTS SRVIVR developmental unit upgraded to production unit status with mounting adaptor (plus all attaching hardware), wiring pigtail/pigtail bracket, and ULB for installation on B-2 aircraft

(2) 19 adapted COTS SRVIVR units with mounting adaptor, wiring pigtail/bracket, and ULB for installation on B-2 aircraft

(3) 7 adapted COTS SRVIVRs with mounting adaptor (plus all attaching hardware), wiring pigtail/bracket, and ULB for supply (spares)

(4) 3 SRVIVR pigtails for supply (spares)

(5) 3 SRVIVR pigtail brackets for supply (spares)

(6) 3 SRVIVR mounting adapter plates for supply (spares)

(7) 2 adapted COTS SRVIVR units with wiring pigtail/bracket and adapter plate for the WSSC

(8) 4 spare ULB assemblies

(9) Spare ULB batteries (IAW contractor stockage proposal)

(10) 5 ULB portable test sets

b. FDRP

(1) 19 modified FDRPs for installation

(2) 7 modified FDRPs for supply (spares)

(3) 3 modified FDRPs for the WSSC

(4) Updated FDRP OFP with software development document deliverables

c. CSMU Download Software. The contractor shall deliver software necessary to extract FID and purge (sanitize) SRVIVR.

d. Download Laptops. The contractor shall deliver five ruggedized laptops (Whiteman AFB [2], WSSC [2], Edwards AFB [1]) configured to download FID from the CSMU.

The contractor shall deliver equipment to power (5 sets) and interface (5 sets) with

SRVIVR.

3.2 System Engineering

3.2.1 Program Security

The contractor shall provide program security IAW B-2 Security Classification Guide and Joint Special Access Program (SAP) Implementation Guide (JSIG) requirements.

The contractor shall complete all documentation required for B-2 security clearances for their personnel and their subcontractors/vendors and forward that documentation to the government PM. The contractor will provide a Certificate of Volatility to support development of the WSSC Classification Memorandum of Record.

3.2.2 Sanitization

The contractor shall provide procedures for on-aircraft SRVIVR memory erase (cockpit-managed zeroization) initiated from the cockpit that takes approximately 20 seconds to complete. The contractor shall also provide as an option procedures for on-aircraft sanitization initiated from the cockpit (overwriting three times). The contractor shall provide procedures for CSMU download and sanitization using a delivered laptop and L3 download software. DI-MISC-80711A (A006)

3.2.3 Airworthiness Certification

Note: The Modified Airworthiness Certification Criteria (MACC) will be created by the Integration Contractor.

The contractor will support development of the MACC document by providing CSMU technical information, as requested.

3.2.4 Obsolescence

The contractor shall provide a preliminary Obsolescence Assessment Reports at Preliminary Design Review and Critical Design Review, with a final Obsolescence Assessment Report at completion of qualification testing. DI-MISC-80711A (A006)

3.2.5 System Security Engineering / Cyber Resiliency / Cybersecurity The contractor shall:

a. Address vulnerabilities and defects throughout the development and operational lifecycles through a cyclical combination of automated and manual vulnerability assessments and reviews. In addition, identify and correct/mitigate vulnerabilities, to include attack surface analysis during the initial system concept definition, architecture selection, and design phase.

b. Ensure that all new and modified software code (excluding lab support software) written for this program is scanned by a static code cybersecurity analysis tool.

Ensure all findings are repaired or adjudicated.

c. Deliver code scan reports to B-2 Division Information System Security Manager (ISSM) and obtain B-2 Division ISSM approval.

d. The contractor shall support the government development/update of the Program Protection Plan, which will include addressing any Critical Program Information and implementing appropriate countermeasures, if needed.

3.2.6 Reliability Availability and Maintainability

The contractor shall develop and deliver a reliability, availability, and maintainability (RAM) plan that is consistent with the B-2 Enterprise RAM Plan. The contractor shall develop reliability allocations and predictions; failure modes, effects, and criticality analysis (FMECA); Failure Reporting and Corrective Action System (FRACAS) inputs utilizing MIL-HDBK-2155, reliability growth model analysis; software reliability analysis;

operational and environmental loads analysis; and a final RAM assessment report to ensure the LRUs and systems comply with reliability requirements of the work specification. The contractor shall develop process failure modes and effects analysis (PFMEA) to minimize manufacturing defects. The contractor shall perform 2,000 hours of reliability development growth testing (RDGT), along with associated analysis and reports, in accordance with the latest version of the B-2 Enterprise Systems Engineering Plan. This RDGT requirement may be satisfied through analysis and/or qualification by similarity with prior justification and approval from the B-2 Systems Program Office Engineering.

The Reliability & Maintainability (R&M) Program Plan shall be in the contractor’s format.

The plan shall identify and describe the planned contractor activities for implementation of the R&M plan. The program plan shall also include:

a. Monitoring and control of subcontractors; suppliers

b. Maintainability design criteria

c. Software design documentation

d. Environmental stress screening

e. Reliability Development Growth Testing

f. RM&A design review information (PDR, CDR, ITT)

The contractor shall report status of the RAM program at design reviews and technical interchange meetings. DI-SESS-81315B (A023), DI-SESS-81613 (A024)

3.2.7 Programmatic Environmental Safety and Occupational Health Programmatic Environmental Safety and Occupational Health (PESHE) is an overall evaluation of program Environmental, Safety and Occupational Health (ESOH) risks and is required for all programs. The PESHE is part of a program risk management/reduction efforts with the goal to eliminate ESOH hazards, where possible, and manage the associated risks where hazards cannot be eliminated. The contractor shall provide the Contracting Officer (CO) previous safety assessment and hazard analyses that demonstrate compliance with MIL-STD-882E, DoD Standard Practice: System Safety.

3.2.8 Engineering Support

The contractor will provide Engineering Support (ES) starting at the beginning of production kit delivery and continuing to the end of the contract POP. Anticipated ES activities include the following: (1) engineering support to address any product quality issues and (2) repair (if required) for delivered modernized FDRs. During the 3-year post-delivery ES period, the contractor shall collect and provide RAM data for the modernized

FDR.

3.3 Program Management

The contractor shall ensure all cost, schedule, and performance requirements are met. The contractor shall use an integrated master plan (IMP) to organize and complete major contract events. The contractor shall report the status of the directed effort to achieve the SOW objectives to the government PM during the contract POP. The contractor shall designate a single point of contact for all work required for this effort. The contractor shall participate in monthly telecoms and Joint Integrated Product Team (JIPT) meetings. The contractor shall prepare, distribute, and update all action items, meeting agendas, and minutes for meetings identified in Section 3.3.1.2 in Microsoft Office format. The contractor shall generate presentation material to aid in the discussion of program or technical issues. The contractor shall provide a detailed get-well plan when applicable and/or requested by the government PM through the CO. Presentation material described in this paragraph shall be jointly defined and agreed upon by both government and contractor PMs. The contractor may be required to travel to fulfill this SOW.

3.3.1 Program Management

3.3.1.1 Interaction with Integration Contractor

Throughout the contract POP, the development contractor shall participate with the integration contractor in joint systems engineering reviews/meetings, as scheduled by the government, to ensure the integration contractor understands the development contractor's time line and to provide the development contractor a system configuration management perspective. The development contractor shall provide the integration contractor (thru the government CO) the proposed hardware and software changes to allow assessment of all technical impacts including, but not limited to, system power and cooling differences, weight and balance changes, and required software modifications.

Shortly after contract award to the integration contractor, the government will host a joint kickoff meeting with both the development contractor and the integration contractor.

Thereafter, similar meetings will be scheduled as needed. During integration and testing in the WSSC and testing at Whiteman AFB, the development contractor shall provide technical information and SMEs to support these activities.

The development contractor will cooperate with the integration contractor to execute an Associate Contractor Agreement (ACA) to cover the portion of the contract requiring joint participation in accomplishment of the USAF’s requirement. Duration of the ACA will be defined by mutual agreement between the government and the contractors. The ACA shall, at a minimum:

a. Identify the associate contractors and their relationships.

b. Identify the program involved and the relevant Government contracts of the associate contractors.

c. Describe the associate contractor interfaces by general subject matter.

d. Specify the categories of information to be exchanged or support to be provided.

e. Include the expiration date (or event) of the ACA.

f. Identify potential conflicts between relevant government contracts and the

ACA; include agreements on protection of proprietary data and restrictions on employees.

A copy of the ACA shall be provided to the government CO for review prior to execution by cooperating contractors. The development contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor. Liability for the improper disclosure of any proprietary data contained in or reference by any ACA shall rest with the parties to the agreement, and not the government.

3.3.1.2 Meetings and Design Reviews

The contractor shall plan and execute systems engineering meetings/reviews for which the contractor is designated as lead in the IMP. This includes making facility arrangements, providing a government-approved agenda, and presentation materials, making presentations, and documenting meeting results in minutes (including action items).

The contractor shall support a contract kick-off meeting at the contractor’s facility no later than (NLT) 30 days after contract award. The contractor shall ensure IMP entry and exit criteria are completed for the major contract events included in the list below.

a. Integrated Baseline Review (IBR) (six months after contract award)

b. Data Management Review (conducted in conjunction with the IBR)

c. System Requirements Review (SRR)/System Functional Review (SFR)/

Preliminary Design Review (PDR)

d. Critical Design Review (CDR)

e. System Verification Review (SVR)/Functional Configuration Audit (FCA)

f. Joint Program Management Reviews (JPMR)

g. Technical Interchange Meetings (TIM)

h. Contract Closeout Conference (CCC)

3.3.1.3 Plans, Reports, and Presentations

Documents to be submitted for approval are normally due to the government PM 30 days before the event to which they apply. If a document is not directly tied to an event, it is due IAW with the IMS. The government will complete review and return "approved" or "disapproved" NLT 15 days after receipt. Contractor format for these deliverables is acceptable.

Minutes of completed meetings are due to the government PM NLT 15 days after the meeting. Documents submitted for approval are only considered approved when a written approval is received from the government CO. Risk-related documents are due quarterly IAW the IMS. Documents (e.g., technical data) to be submitted for review are due IAW with the IMS. Some Documents may be identified by the government to be reviewed by the integration contractor; if so, that review will be completed within 10 workdays. At the Contract Closeout Conference, the contractor shall summarize all work performed under this SOW.

a. Documents to be submitted for approval, DI-MISC-80711A (A006):

(1) IBR Minutes

(2) SRR/SFR/PDR Minutes

(3) CDR Minutes

(4) TRR Minutes

(5) FRR Minutes

(6) SVR/FCA Minutes

(7) Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Assessment Plan

(8) Provisioning Documentation

(9) Technical Data Package

b. Documents to be submitted for review, contractor format acceptable:

(1) Kickoff Meeting Minutes

(2) TIM Minutes

(3) Qualification Test Procedures and Qualification Test Report

(4) Bill of Materials

(5) JPMR Presentations

(6) JIPT Presentations

(7) DMSMS Assessment Report (quarterly beginning after PDR)

(8) Failure Review Board results and presentations

(9) Data Accession List

3.3.2 Risk Management Program

The contractor shall implement effective risk management and tracking to include the identification of all known risks, key assumptions, probability of occurrence, consequences of occurrence (in terms of cost, schedule, and performance) if not mitigated, analysis of mitigation options, decisions about actions to mitigate risk, and execution of those actions.

Effective risk management is not just risk identification and tracking. Risk management is proactive and should be focused on the actions that will be taken and resources that will be allocated to reduce both the likelihood and consequences of risks being realized.

The contractor shall develop and deliver a Risk Management Plan that describes their approach to implement effective risk management for the B-2 Flight Data Recorder/CSMU Modernization program. Initial presentation of the risk management approach shall be made at the contract kickoff meeting with delivery of the Risk Management Plan 30 days later and subsequent risk register updates provided in accordance with the Risk Management Plan. DI-

MISC-80711A (A006)

3.3.3 Program Control

3.3.3.1 Contractor Work Breakdown Structure

The contractor shall develop and update a Contractor Work Breakdown Structure (CWBS) throughout the contract and use a CWBS structure for contract reporting in conjunction with the Integrated Master Schedule. Prior approval of the government is required for any changes to the CWBS structure at the reporting level. First submission shall be made NLT 60 calendar days after award. Subsequent dates of submission shall be upon major revision.

The CWBS shall be submitted in electronic format agreed upon by both parties. DI-

MGMT-81334D (A018)

3.3.3.2 Project Schedule

The contractor shall develop, maintain, update, and deliver a monthly IMS incorporating the CWBS data with major contract events outlined within the IMP for government PM review. The contractor shall notify government PM in writing (email) when project schedule Level 1 and 2 tasks or forecast dates are projected to change by 14 calendar days or more. Contractor shall identify the critical path and notify the government of critical path schedule conflicts and slips within five business days of schedule conflict identification. If the contractor has any subcontractors, the contractor shall ensure subcontractor schedule dates align with contractor's project schedule. DI-MGMT-81861 (Format 6) (A021)

3.3.3.3 Status and Cost Tracking

The contractor shall perform cost reporting and shall report in accordance with the CWBS.

The data must be available to identify problems and resolution to the appropriate cost center. The required reports are:

a. Contract Funds Status Report, DI-MGMT-81468 (A014)

b. Cost Data Summary Report, DI-FNCL-81565C (A0l5)

c. Functional Cost-Hour Report, DI-FNCL-81566C (A016)

d. Contract WBS, DI-MGMT-81334D (A018)

e. Contractor Business Data Report, DI-FNCL-81765B (A048)

3.3.4 Product Support

The contractor shall:

a. Acquire and manage all material required for adapting the COTS SRVIVR to the B-2.

The government shall provide FDRPs as GFP for use in developing the 9 VDC to 28 VDC modification, testing the FDRP OFP modifications, and, if required, modifying FDRP firmware. There will be no destructive testing of the GFP FDRP or FDRP modifications due to the limited numbers of FDRP assets. If the contractor believes destructive testing is needed, the contractor will notify the government PM in order to agree on an alternate means of testing. The contractor shall provide documentation of the qualification testing of the modified FDR.

b. Comply with the requirements of MIL-STD-130, DoD Standard Practice:

Identification Marking of U.S. Military Property, as applicable to the SRVIVR

CSMU.

c. Perform analysis of existing support equipment to determine if changes in the modernized FDR design creates a requirement to update or develop peculiar support equipment.

d. Perform life cycle logistics support and product support efforts required to support the B-2 CSMU program. This includes activities associated with life cycle logistics and product support for acquisition programs IAW AFI 63-101/20-101, Integrated Life Cycle Management, and applicable AF and DoD level policy; product support elements (PSE) IAW AF Pamphlet 63-128, Integrated Life Cycle Management; support equipment analysis; and DMSMS.

e. Provide Level of Repair Analysis, to include comparative data for other platforms using SRVIVR CSMU.

f. Identify and recommend spare/repair parts sufficient to meet system/equipment operation and support objectives IAW the initial provisioning performance specification. Provisioning shall be submitted and processed through the official AF Provisioning System, as directed by the CO. The contractor shall continue provisioning documentation of spare and repair parts for the air vehicle fleet, organizational and intermediate level support equipment, and any funded (P-3) modifications to an air vehicle IAW the provisioning requirements statement. The contractor shall continue prescreening for all items as required by DoD Manual 4100.39, Federal Logistics Information System Procedures. DI-SESS-81759A (A008), DI-SESS-81874 (A009), DI- SESS-81758A/T (A010)

g. Be responsible for preservation, packaging, packing, and marking of parts, subassemblies, and assemblies in accordance with Section D of the contract and the AFMC Form 158, Packaging Requirements. When military packaging and marking are specified, the contractor shall comply with MIL-STD-2073-1E, DoD Standard Practice for Military Packaging, and MIL-STD-129P, DoD Handbook: Military Marking. When commercial packaging is specified, the contractor shall comply with ASTM D3951-98, Standard Practice for Commercial Packaging, and MIL-STD-129P for marking. The contractor shall provide packaging data for new equipment entering the DoD inventory or for modified equipment when the packaging data has changed. The packaging data shall identify the electrostatic discharge sensitive items and assemblies as defined in MIL- STD-1686C, Military Standard: Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices), and hazardous materials per Code of Federal Regulations Title 49.

h. Address DMSMS issues affecting the implementation and sustainment of the B-2 SRVIVR CSMU modification by proactively identifying, investigating, and reporting potential DMSMS problems IAW best commercial processes. DMSMS reports should include, as a minimum, identification of problem component(s), indication if the problem is an actual or potential problem, estimate of impacts to the weapon system, recommended plan of action to mitigate impacts, and the estimated cost (i.e., rough order of magnitude) for implementing the recommendation. DI-MISC-80711A (A006)

i. Develop the approach for the maintenance concept and source of repair analysis for the CSMU, to be included in the Product Support Plan. The maintenance concept shall be based on reliability-centered maintenance. The approach shall include, but is not limited to: delineating accessibility, real-time health monitoring and diagnostics, repair, sparing requirements, identifying requirements for manpower factors that impact system design utilization rates, identifying lifecycle supportability design, installation, maintenance, and operating constraints and guidelines, skills/training requirements, providing economic and non-economic repair analyses. Programmed and scheduled maintenance requirements shall be consolidated as much as feasible to reduce the number and frequency of maintenance activities. DI-SESS-81759A (A012)

j. Provide a counterfeit prevention plan for the B-2 CSMU Modernization program.

DI-MISC-81832 (A025)

3.4 System Test and Evaluation

3.4.1 Developmental Test and Evaluation

a. The contractor shall complete design and FDR subsystem testing IAW its own best practices for the replacement CSMU (SRVIVR) to confirm (and document via traceability matrix) that it meets all SRD requirements, and to verify operational compatibility with both (1) the legacy OFP currently on the B-2 and (2) the modified OFP being delivered with SRVIVR CSMU. The contractor shall deliver a report of test results at completion of testing. DI-MISC-80711A (A006)

b. The contractor shall plan for support of integration and testing activities IAW the dates/times identified in the CSMU IMS to be provided by the government. [Note:

integration and testing will be performed in the WSSC SIL, building 1083, Tinker AFB, OK by the B-2 System Integrator, Northrop Grumman Corporation (NGC).] The delivered software documentation identified in section 3.6.3 will be used by the integration contractor to develop the WSSC SIL test procedures. The contractor shall make available appropriate SME to support the lab testing planning and execution. The contractor shall provide sanitization procedures/tools to completely wipe the CSMU memory.

3.4.2 Operational Test and Evaluation

The contractor shall support on-aircraft ground testing and, if required, flight testing activities at the 412th Flight Test Wing (FTW), Edwards AFB, CA (or 72d Test and Evaluation Squadron (TES), Whiteman AFB, MO) IAW the dates/times to be provided by the government. Those dates shall be included in the IMS. Support includes making SMEs available during test planning and execution, and other support to be identified during the Test Readiness Review. The contractor shall work with the Combined Test Team to ensure all requested functions are completed in order to ensure success of test events. The contractor shall support the Combined Test Team in developing detailed test requirements and, if required, supporting test results analysis and reporting.

3.5 Training

The contractor shall support NGC development of the maintenance and operator difference briefing for the product developed by this contract to the initial cadre of personnel supporting testing at Edwards AFB and the Force Development Evaluation flight test at Whiteman AFB.

The contractor shall support NGC in the development of a training plan, a syllabus, and updates as required for review 3 months prior to scheduled training for first kit installation.

The contractor shall provide on‐site support during delivery of the briefings.

3.6 Data

3.6.1 Technical Data

a. The contractor shall deliver a full production-level Technical Data Package (TDP) representing the configuration of the CSMU/Flight Data Recorder IAW MIL- STD-31000A. The contractor shall ensure document markings conform to Defense Acquisition Regulation Supplement (DFARS) Part 227 as prescribed by DFARS

252.227 and DoDI 5230.24, Distribution Statements on Technical Documents. The contractor shall mark all technical data to be delivered to the government with restriction on use, reproduction, and disclosure IAW DFARS 227.71 and 252.227.

b. The contractor shall review all data for engineering competency and completeness, and correct any errors prior to delivery to the government. The contractor shall deliver the TDP 30 calendar days prior to CDR. If any CDR TDP data is found by the government to be in error, those data shall be corrected and re-delivered within 30 calendar days of notice. At SVR, the contractor shall deliver any data not approved at CDR. The final TDP must represent the final “as is” design. DI-

SESS-81000E (A026)

3.6.2 Technical Orders (Field Level)

The contractor shall prepare and deliver engineering source data required for the development of technical orders by NGC. Delivery of the source data shall be 30 days prior to SVR. The contractor shall support the initial Technical Order Guidance Conference and a 70% In Process Review. The contractor shall support the combined Validation and Verification.

3.6.3 Software Documentation

The contractor shall deliver complete software documentation representing the configuration of the FDRP OFP in accordance with ISO/IEC/IEEE 12207:2017, Systems and Software Engineering – Software Life Cycle Processes, and shall deliver software documents IAW Contract Data Requirements List A007 and the Data Item Descriptions listed below. The delivered items shall be documentation and tools sufficient for organic software sustainment.

The contractor shall mark all software and software documentation delivered to the government with restriction on use, reproduction, and disclosure IAW DFARS 227.71 and 252.227. In addition, the contractor shall review all data for accuracy and completeness and correct any errors prior to delivery to the government. The contractor shall deliver the software documentation 30 calendar days prior to CDR. If any data is found by the government to be in error, those data shall be corrected and re• delivered within 30 calendar days of notice. At SVR, the contractor shall deliver any data not approved at CDR. The final documentation must represent the final “as is” design.

a. Software Version Description Document, DI-IPSC-81442 (A007)

b. Software Requirements Specification, DIIPSC-81433 (A050)

c. Software Test Plan, DI-IPSC-81438 (A051)

d. Software Test Report, DI-IPSC-81440 (A052)

e. Interface Control Data, DI-IPSC-81436 (A053)

3.6.4 Configuration and Data Management

3.6.4.1 Configuration Management

The contractor shall employ an approved Configuration Management and Data Management Plan (CMDMP). The CMDMP shall be in accordance with MIL- STD-3046, DoD Interim Standard Practice: Configuration Management, or IEEE 828 Standard for Configuration Management in Systems and Software Engineering. The CMDMP shall maintain consistency of the product’s performance, functionality, and physical attributes with respect to its requirements. The CMDMP shall maintain a control process defining how engineering changes are incorporated into the delivered product (e.g., architectures, requirements, specifications, designs, drawings, interfaces, software, hardware, firmware, operational information, and documentation). The CMDMP shall provide a process addressing configuration identification, configuration control, configuration status accounting, and performing configuration audits. DI-

MISC-80711A (A006)

3.6.4.2 Data Management

The contractor shall provide data management (DM) enabling timely, accurate, and auditable data exchange between and among the JIPT, consisting of the contractor, the government, and NGC. The DM activities shall use approved access control and in accordance with applicable information assurance requirements of this contract. The contractor shall support and supply the JIPT with appropriate and sufficient information system access and processing/storage capacity to accomplish timely, accurate, and auditable data exchange throughout the contract period. The contractor shall ensure appropriate and required agreements are in place with complete data exchanges among the JIPT (e.g., non-disclosure agreements, etc.). The contractor shall maintain all data and ensure information assurance compliance for that data at the UNCLASSIFIED//FOR OFFICIAL USE ONLY level.

3.6.4.3 Engineering Changes

Prior to the submittal of any Class I Engineering Change Proposal (ECP), the contractor shall submit an advance notice to the CO. The advance notice shall summarize the nature of the potential change, the affected specification paragraphs, the reason for the change, and a rough order of magnitude of the cost and schedule impacts. The contractor shall not proceed with preparation or submittal of a Class I ECP until directed by the CO.

After directed by the CO, the contractor shall prepare Class I ECPs for any changes that affect contract compliance and/or the form, fit, function, or interface requirements of the system. The contractor shall submit Class I ECPs for consideration of any changes to the initial, functional, or allocated baselines once they are established. Requests for equitable adjustments related to ECPs will only be considered if they are associated with changes to the initial or functional baselines. DI-SESS-80639D (A002)

3.6.5 Procurement Specification

The contractor shall update the Procurement Specification (P-Spec) (DAA3322P001C, 16 Oct 92) provided as government-furnished information to reflect the hardware/software changes made to the FDRP, FDRP OFP, and CSMU under this contract.

3.6.6 Other Data

The contractor shall provide the government PM a list of all other data and documents created during contract execution. The list shall be delivered during contract closeout.

DI-MGMT-81453A (A005)

3.7 Peculiar Support Equipment (see partial in 3.1.2d)

The contractor shall develop and maintain Support Equipment Requirement Documents (SERD) for all support equipment requirements identified. The contractor shall perform analysis of existing support equipment to determine if changes in the modernized FDR design creates a requirement to update or develop Peculiar Support Equipment. The contractor shall ensure support equipment calibration requirements are current, correct, and applied to the system. If the CSMU requires special test equipment, the contractor shall deliver a set to the

WSSC and provide training on its use. Recommendations for test or support equipment shall be identified to the government prior to Critical Design Review. DI‐ALSS‐81530

3.8 Common Support Equipment

The contractor shall minimize the requirement for new or modified test and measurement equipment. The contractor shall identify common test and measurement equipment if/as required. The contractor shall identify common support and handling equipment if/as required.

The contractor shall develop and maintain SERDs for all support equipment requirements identified. DI‐ALSS‐81530

3.9 Operational/Site Activation – Not Applicable

3.10 Industrial Facilities – Not Applicable

3.11 Initial Spares and Repair Parts – See paragraph 3.1.2