Section_C_PDGU_SOO_19_NOV.pdf

For Official Use Only 19 November 2015

Statement of Objectives

(SOO)

Programmable Display Generator Upgrade (PDGU)

November 19, 2015

FOR OFFICIAL USE ONLY (FOUO): This electronic message and its attachment(s) contain restricted, sensitive, non-public information. The information is not intended to disclosure outside official government channels and is exempt from release under the Freedom of Information Act, 5 U.S.C. 552.* If you have received this message in error, please notify the sender and delete all copies of this message.

Table of Contents 1 Introduction

1.1 Purpose

1.2 Scope

1.3 Program Objectives

2 Applicable Reference Documents

2.1 Government Documents

2.2 Industry Documents

3 Contractor Tasking/Requirements

3.1 Period of Performance

3.1.1 PDGU System Capability Requirements

3.2 WBS 1.0 Engineering and Manufacturing Development

3.2.1 WBS 1.1 Program Management

3.2.2 WBS 1.2 Systems Engineering

3.2.3 WBS 1.3 Software

3.2.4 WBS 1.4 System Integration, Test & Qualification

3.2.5 WBS 1.5 Security Management

3.2.6 WBS 1.6 Data

3.2.7 WBS 1.7 Contractor Support

3.2.8 WBS 1.8 Training

3.2.9 WBS 1.9 Manufacturing and Quality Assurance

4 WBS 2.0 Production and Deployment

4.1 WBS 2.1 Non-Recurring Production

4.2 WBS 2.2 Recurring Production

4.2.1 WBS 2.2.1.Production Acceptance Testing

4.2.2 WBS 2.2.2.Production & Deployment Item Unique Identification

4.2.3 WBS 2.2.3.Defense Report Information Logistics Reporting System

4.3 WBS 2.3 Depot Stand-Up

4.4 WBS 2.4 Test Program Sets/Interface Test Adapters

4.5 WBS 2.5 Interim Contractor Support

4.6 WBS 2.6 Spares

4.6.1 WBS 2.6.1 Initial Spares

4.7 WBS 3.0 Government Furnished Equipment

5 WBS 4.0 Block 30 Integration Option

6 Acronyms

Appendix A:

Appendix B:

Appendix C:

1 Introduction

1.1 Purpose

The United States Air Force (USAF) requests a proposal for the F-16 Programmable Display Generator Upgrade (PDGU) Program to design, develop, test, manufacture, deliver, and support a PDGU and re-host of an existing Operational Flight Program (OFP), and support the re-host of a future OFP on-site at Hill AFB for USAF F-16 Blocks 40/42/50/52, C&D Model aircraft with a separately priced option for the Block 30/32 aircraft. This contract will cover development, qualification, integration support, production, and support equipment acquisition.

This Statement of Objectives (SOO) defines threshold tasks required for the development, production, and support of the PDGU. The AFLCMC/WWM F-16 System Program Office (SPO) will be the overall USAF Management Agency for all tasks defined in this SOO and primary integrator for the equipment. Any changes, modifications, or amendments to the efforts defined herein shall be approved by the AFLCMC/WWMK Procuring Contracting Officer (PCO).

The PDGU is to address the current display/video processing limitations, and support high definition video and moving map by enhancing throughput and memory to provide properly functioning displays in a dynamic fighter environment. Also, the PDGU shall provide a platform for video enhancements, Ethernet connectivity, sustainability, and OFP growth through the remaining service life of the F-16. The display generation is critical to pilot situational awareness and weapon system effectiveness through a variety of key mission displays. The contract will cover development, integration support, production, and support equipment acquisition.

1.2 Scope

The scope of this effort is to design/develop/integrate/qualify/manufacture an upgraded PDG hardware platform; re-host an existing United States Government (USG) furnished OFP, support system and sub-system integration testing, along with re-hosting and integrating a second future OFP at Hill AFB facility. The performance improvements in the PDGU will allow modern components, such as high definition targeting pods, center pedestal displays, and high speed data networks, to be incorporated into the avionics suite. The Contractor shall be responsible for design and development of the PDGU hardware and associated software as defined within the contractual requirements. Appendix A contains the Contract Data Requirements List (CDRL), Appendix B identifies the Data Accession List (DAL) documents to be provided or made available as part of this contract, and Appendix C contains the Security Requirements Traceability Matrix

(SRTM).

1.3 Program Objectives

The Contractor shall be responsible for the design and development of the PDGU hardware and associated software as defined within this SOO and in the Government’s PDGU System Requirements Document (SRD) and Subsystem Requirements Document (SSRD) required to re-host a Government supplied OFP.

2 Applicable Reference Documents

The following documents of the exact issue shown form a part of this SOO to the extent specified herein.

2.1 Government Documents

United States Government

• DFARS 252.211-7003 Item Unique Identification and Valuation

United States Air Force Manuals

• AFI 10-701 Air Force Instruction 10-701 - Operations Security (OPSEC), dated 8 Jun 2011

• AFPAM 63-113 Air Force Pamphlet 63-113 - Program Protection Planning for Life

Cycle Management, dated 17 Oct 2013

• AFI 63-125 Nuclear Certification Program

• AFI 91-103 Air Force Nuclear Safety Design Criteria Certification Program

• AFI 91-205 Non-Nuclear Munitions Safety Board

Department of Defense

• DoDI 5200.39 Critical Program Information (CPI) Protection Within the

Department of Defense, dated 28 Dec 2010, Change 1

• DoDI 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks(TSN), dated 5 Nov 2012

• DoDI 8500.1 Cybersecurity, dated 14 Mar 2014

• DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology(IT), dated 12 Mar 2014

DoD Forms

• DD Form 254 Contract Security Classification Specification, dated 01 Dec1999

Military Handbooks

• MIL-HDBK-61A Military Handbook - Configuration Management Handbook, dated

07 Feb 2001

• MIL-HDBK-217F Reliability Prediction of Electronic Equipment, dated 28 Feb 1995

• MIL-HDBK-2164A Environmental Stress Screening Process of Electronic Equipment

• MIL-HDBK-470A Designing and Developing Maintainable Products and Systems, dated, 04Dec 1997

• MIL-HDBK-516C Airworthiness Certification Criteria, dated 12 Dec 2014

Military Standards

• MIL-STD-130N Identification Marking of U.S. Military Property, dated 16 Nov

• MIL-STD-196F Joint Electronics Type Designation System, dated 01 Sept 2013

• MIL-STD-881C Work Breakdown Structures For Defense Material Items, dated 03

Oct 2011

• MIL-STD-882E System Safety, dated 11 May 2012

• MIL-STD-961E Defense and Program - Unique Specifications Format and Content, dated 9 Jan 2014

Government Electronics and Information Technology Association

• GEIA-STD-0005-1 Performance Standard for Aerospace and High Performance

Electronic Systems Containing Lead-free Solder

• GEIA-STD-0005-2A Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High Performance Electronic Systems

• GEIA-STD-0006 Requirements for Using Solder Dip to Replace the Finish on

Electronic Components, dated 05 Jan2011

National Aerospace Standards

• NAS 411 Hazardous Materials Management Program, dated 19 Jan 1995

Technical Orders/Manuals

• T.O. 00-5-16 Software Managers and User’s Manual for the USAF Automated

Computer Program Identification Number System (ACPINS), dated 15 April 2015

• T.O. 00-35D-54 USAF Deficiency Reporting, Investigation, and Resolution, dated 01 Aug 2015

2.2 Industry Documents

Committee On National Security Systems

• CNSSI 1253 Security Categorization and Control Selection for National

Security Systems, dated 15 March 2012, Version 2

National Institute of Standards and Technology

• NIST SP 800-47 Security Guide for Interconnecting Information Technology

Systems, dated Aug 2002

• NIST SP 800-137 Information Security Continuous Monitoring (ISCM) for Federal

Information Systems and Organizations, dated Sept 2011

• NIST SP 800-161 Supply Chain Risk Management Practices for Federal Information

Systems and Organizations, dated Jun 2014, second draft

• NIST IR 7622 Notional Supply Chain Risk Management Practices for Federal

Information Systems, dated 01 Oct 2012

Society of Automotive Engineers

• SAE AS5553A Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition, dated 21 Jan 2013

• SAE AS6500 Manufacturing Management Program, dated 13 Nov.2014

• AS9100C Quality Management Systems – Requirements for Aviation, Space and Defense Organizations, dated 15 Jan 2009

American National Standards Institute/Electronic Industries Alliance

• ANSI/EIA-748-C Earned Value Management Systems - Intent Guide, dated 29

April2014

Solid State Technology Association

• IPC-J-STD-609 Marking and Labeling of Components, PCBs and PCBAs to Identify

Lead (Pb), Lead-Free (Pb-Free) and Other Attributes, dated 1- May-07

3 Contractor Tasking/Requirements

3.1 Period of Performance

A ten year contract will be awarded, estimated to begin in Fiscal Year (FY) 2016.

3.1.1 PDGU System Capability Requirements

The Contractor shall provide a subsystem compliant to the requirements identified in the PDGU SSRD and this SOO. The Contractor shall ensure the technical requirements identified in the SSRD are achieved through the development progress.

3.2 WBS 1.0 Engineering and Manufacturing Development

3.2.1 WBS 1.1 Program Management

The Contractor shall provide and establish a PDGU Program Management Plan (PMP), that establishes a process and an organization that shall be responsible for the tracking of the PDGU program technical development, schedule, and cost performance. The Contractor shall ensure their program management organization has the necessary contractual responsibility and authority to effectively execute and adhere to all contractual obligations.

The program management organization shall be responsible for conducting reviews with the Government to ensure the programs execution is meeting the Government’s objectives.

The Contractor’s Program Management shall conduct the program management and design reviews, and other meetings outlined within the SOO.

The Contractor’s PMP structure shall provide a systematic approach and a multi-disciplined team given the authority to focus technical resources on the PDGU supplier management, technical development, integration, qualification, and manufacturing, DI-MGMT-81797 and a Software Development Status Report per DI-MISC-80508B.

3.2.1.1 Program Support

The Contractor shall plan, schedule, and manage the development and production efforts to ensure internal control and completion of the tasks specified in this SOO. Additionally, the Contractor shall work with the USG in an Integrated Product Team (IPT) approach.

The Contractor shall provide program oversight and management of sub-Contractor functional organizations supporting this program. The Contractor shall assure conformance to schedule, cost, and quality requirements of the contract. The Contractor shall provide quarterly status of the sub-Contractor management.

The Contractor shall generate monthly contract cost performance reporting as defined in the Integrated Program Management Report (IPMR), DI-MGMT-81861A. The Contractor shall also provide a quarterly Contract Funds Status Report (CFSR), DI-MGMT-81468.

3.2.1.2 Integrated Master Plan/Integrated Master Schedule

The Contractor shall develop an Integrated Master Plan (IMP) and Integrated Master Schedule (IMS). The IMP shall be an event driven plan which documents the significant accomplishments the Contractor shall perform to complete the PDGU design and development through production. The IMP shall tie each Contractor accomplishment to a key program event. In the IMS, the Contractor shall provide an integrated and networked multi-layered logical critical path schedule of program tasks outlining the step-by-step work effort required to complete the PDGU design and development through production as outlined by the IMP and traceable to the Work Breakdown Structure (WBS). The Contractor shall develop the IMP and IMS as per DI-

MGMT-81861A.

3.2.1.3 Contractor Work Breakdown Structure

The Contractor shall provide a Contractor Work Breakdown Structure (CWBS) which decomposes the tasks identified in the IMP/IMS into lower level organizational elements, tasks, work packages and deliverables, DI-MGMT-841334D.

3.2.1.4 Technical Performance Management

The Contractor shall establish monthly reporting of key Technical Performance Parameters (TPP) to track the technical progress of the PDGU program and to provide early notification of potential technical risks. The key TPPs are weight, power, mechanical envelope, software re-host, resource utilization, and thermal performance, DI-MGMT-80227.

3.2.1.5 Risk Management

The Contractor shall develop and maintain a Program Risk Management Plan (PRMP) which details how program management will manage technical and programmatic risks, assess impacts and identify potential mitigations or opportunities. As part of the PRMP the Contractor shall provide an appendix containing the known and anticipated program risks and the anticipated impacts (cost, schedule, etc.) of each risk along with a list of tasks the Contractor will use to manage or mitigate the impact of each risk DI-MGMT-81808.

The Contractor shall prepare and submit a monthly Risk Management Report (RMR) which details the programmatic and technical risks applicable to the program, DI-MGMT-81809.

3.2.1.6 Configuration Management

3.2.1.6.1 Configuration Management Plan

The Contractor shall develop and accomplish Configuration Management (CM) tasks in accordance with (IAW) the Configuration Management Plan (CMP) jointly developed by the Contractor and the USG, using MIL-STD-973 and MIL-HDBK-61A as guides. CM shall include procedures, responsibilities for configuration identification, change control, audits, status accounting, interface management, and sub-Contractor management. The Contractor shall establish a process to assure that configuration control is maintained on the system, and in functional, allocated, and product baseline configuration identification documentation, DI-SESS- 81875.

3.2.1.6.1.1 Configuration Control

The USG will exercise formal configuration control of the Functional Baseline (and all external interfaces) from the time it is established at System Requirements Review (SRR) until the system is accepted by the USG. The Contractor shall maintain formal configuration control of the allocated baseline (and internal interfaces) from the time it is established at the successful completion of a Preliminary Design Review (PDR) until the system is accepted by the USG. The Contractor shall maintain formal configuration control of the initial product baseline (and all internal interfaces) from the time it is established at the successful completion of Critical Design Review (CDR) until the final product baseline is established at Physical Configuration Audit (PCA). The Contractor shall also maintain formal configuration and quality control of the

“development baseline” as the product is integrated and tested to assure integrity of the test results.

3.2.1.6.1.2 Configuration Item Identification

The Contractor shall identify system hardware and software recommendations for designation as Configuration Items (CI) and Computer Software Configuration Items (CSCI) and provide recommendations to the USG for review and approval. The Contractor shall develop, document, and process Requests for Nomenclature IAW MIL-STD-196F (Joint Electronics Type Designation System) for all newly developed CIs. The Contractor shall develop, document, and process Automatic Computer Program Identification Numbers (CPIN) IAW TO 00-5-16 (Technical Manual Software Manager’s Manual) for all CSCIs. The Contractor shall develop, implement, and maintain Subsystem Specifications for designated subsystems and Program Unique Specification Documents IAW MIL-STD-961E for all CIs, DI-SDMP-81493A. The Contractor's format is acceptable for commercial specifications for Commercial-Off-The-Shelf (COTS) items and modifications to those specifications for modified COTS.

3.2.1.6.1.3 Configuration Status Accounting

The Contractor shall develop, maintain, and document Configuration Status Accounting (CSA) information, capturing all current change status and change history and the as-designed, as-built, as-delivered, and as-modified configuration of any serial numbered component and any component with USG participation. For software CSCIs and Computer Software Components, the CSA shall include the as-delivered, as-modified, and as-tested configuration as-of dates, DI-

SESS-81253B.

3.2.1.6.1.4 Item Unique Identification

The Contractor shall implement an Item Unique Identification (IUID) program on the PDGU during Engineering Manufacturing and Development (EMD). IUIDs are required for the PDGU (Aircraft, Spares, Alternate Mission Equipment (AME), Support Equipment, Modification, and Modification Kit) and shall be applied during EMD and finalized in Production. IUID implementation methodology for F-16 USAF contracts is applied to end item Contract Line Item Numbers (CLIN) (Aircraft, Alternate Mission equipment (AME) and Support Equipment, spare or kit) when the unit deliverable price is $5,000 or higher. This program compliance requirement shall be established meeting the intent of Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7003 and MIL-STD-130 (latest revision).

3.2.1.6.1.5 Item Unique Identification Part Numbers

The Contractor shall ensure that once an IUID has been used to uniquely identify an item, that that same number will not be used to identify any other item (the Contractor and suppliers must guarantee uniqueness of IUID marks). The Contractor shall retain shipping and receiving documentation for a period of time consistent with the requirements of Federal Acquisition Regulation (FAR) Subpart 4.7 for retention of IUID information. The Contractor shall provide a list of applicable EMD IUID part numbers as an attachment to the contract DI-MGMT-81803 and

DI-MGMT-81804A.

3.2.1.7 Data Management

The Contractor shall implement a data management process and provide a plan which addresses the preparation, quality control, administration, and delivery of data required by DI-MISC- 80168, IAW the CMP and Appendix A. The Contractor shall maintain data status and delivery schedules for all CDRL items. The Contractor shall also plan for, develop, manage, and maintain documentation for engineering data products. The Contractor shall deliver all program data IAW the CDRL and the DAL. The Contractor shall develop and maintain a DAL that is accessible to the USG, which shall include data referenced within the SOO and all existing data, internally generated data, and computer software used by the Contractor to develop, test, and manage the program. The Contractor shall, upon request, provide the USG access to all electronically available DAL items.

The Contractor shall maintain data status and delivery schedules for CDRL items. The Contractor shall also plan, develop, manage, and maintain documentation for engineering data products.

The CDRL provided in Appendix A.

3.2.1.7.1 Engineering Change Proposal Management

As part of the Contractor’s CMP, the Contractor shall describe how the Contractor will manage and prepare Engineering Change Proposals (ECP). ECPs shall be required whenever a change affects the PDGU SSRD performance or requirements, or the PDGU’s form, fit and function and associated Technical Data Package (TDP) changes. The Contractor shall submit ECPs per DI-SESS- 80639D and DI-CMAN-80643C.

3.2.1.7.2 Variance Management

As part of the Contractor’s CMP, the Contractor shall describe the process the Contractor will implement to request variances from the Government. The Contractor shall prepare and submit a Variance Request per the applicable DI-CMAN-80640C.

3.2.1.8 Reviews and Meetings

The Contractor shall engage jointly with the USG’s Program Manager for the Initial Program Review (IPR) no later than six (6) months after contract award to evaluate cost, schedule, and technical risks inherent in the contract’s Performance Measurement Baseline (PMB).

The Contractor shall propose a technical review process appropriate for all phases of the product development. The Contractor’s planning for major technical reviews shall include telecoms and Technical Interchange Meetings (TIM), Design Reviews, Interface Control Working Group (ICWG) meetings, and Depot Infrastructure meetings with the USG.

Major technical reviews shall be identified, and included as milestones in the IMS.

The Contractor shall provide the appropriate technical and management personnel to support design reviews and technical meetings. It is anticipated ICWGs, TIMs, Depot Infrastructure (DI), and Program Management Reviews (PMRs) will be held on a quarterly basis and major design reviews will be scheduled to ensure proper oversight of the product as its design matures.

The Contractor shall be responsible for the preparation of agendas, presentations and meeting minutes for all Design Reviews, PMRs and technical meetings DI-ADMN-81249A and DI-ADMN- 81250A.

Technology Readiness Levels (TRL) and Manufacturing Readiness Levels (MRL) shall be assessed and presented, along with supporting data and analyses, at each major technical review.

Major technical reviews shall have as a minimum the following attributes for the phase and scope of the development activity:

• Technical reviews planned in accordance with the activities to be reviewed as identified in the IMP.

• Clearly identified entry and exit criteria that are agreed to by the USG.

• A review panel comprised of the appropriate engineering and program disciplines to ensure a thorough detailed review.

• Detailed technical content appropriate for the phase and scope of the development activity at the time of the review (e.g., requirements, system architecture, analyses and trades, detailed designs, test results, design margin and design characterization status).

• An assessment of relevant technical performance measures, risk watch items, and all identified risks along with risk mitigation plans and status.

• A closed-loop process for addressing issues and actions from the review.

• A presentation of design margin analyses and testing, along with results of system characterization.

As a minimum the following major technical reviews shall be conducted:

• System Requirements Review (SRR): The SRR shall be a multi-disciplined technical review convened by the USG and the Contractor’s team for the formal review of the System Requirements and the Contractor’s system solution. The data presented in the review shall provide evidence that the Contractor’s system solution (including both hardware and software, as applicable) is consistent with the system requirements. The USG will co-chair the SRR.

• Preliminary Design Review (PDR): The PDR shall be a multi-disciplined technical review convened by the USG and the Contractor’s team, subsequent to the SRR and the decomposition of the system’s functional definition, to determine whether the hardware and software preliminary designs are complete, and the program is ready to start detailed design. The USG will co-chair the PDR.

• Critical Design Review (CDR): The CDR shall be a multi-disciplined technical review convened by the USG and the Contractor’s team for the formal review of the product’s detailed design. Completion of the CDR confirms that the design is ready for the commencement of formal system integration and weapon-level testing. The USG will co-chair the CDR.

• Test Readiness Review (TRR): The TRR shall be a multi-disciplined technical review convened by the USG and the Contractor’s team to assess the readiness of the system and/or its subsystems to proceed into formal testing (e.g., qualification testing, EMI/EMC, and other subsystem test events). The USG will co-chair the TRR.

• Functional Configuration Audit (FCA): The FCA shall be conducted by the USG and the Contractor’s team at the system and configuration item level to validate to the USG that testing and other required methods of verification have been accomplished and that the system’s performance meets all specification requirements. The Verification Cross Reference Matrix (VCRM) shall be a key tool of the FCA process and forms the basis for requirements verification. If the audits are performed incrementally, then the Contractor shall review and address all open configuration item discrepancies from the previous FCAs. The Contractor shall host all FCAs at their facility unless otherwise agreed to by the USG. The USG shall co-chair, witness, and participate in the audits.

• Physical Configuration Audits (PCA): The Contractor shall perform PCAs at the Configuration Item level during Production. The PCAs shall assure that the successfully tested system configuration items are adequately documented for replication or production (i.e., product configuration documentation is a clear, complete, and accurate depiction of the item). The PCA shall formally examine the actual (as-built) configuration items compared to the associated design documentation including product specification, source code listing, and engineering drawings. The PCA shall establish the final product baseline. The Contractor shall host all PCAs at the Contractor’s facility. The USG will co-chair, witness, and participate in the audits.

• Hill SIL TRR: The Contractor shall provide on-site technical support of Hill AFB SIL TRR.

Meeting support may consist of Contractor related slide presentations and support of technical discussions and side meeting. The meeting will take place at Hill AFB, specific location to be provided by the PM. The duration of the meeting will be two (2) days maximum.

• Flight Test TRR: The Contractor shall provide on-site technical support of Hill AFB M6.5 and M8.0 Flight Test TRRs. Meeting support may consist of slide preparation and presentation of material related to the Contractor’s M6.5 and M8 efforts. Support technical discussions and side meetings. The meetings will take place at Hill AFB, specific location to be provided by the PM. The duration of the each meeting will be two (2) days maximum.

• TIMs: The Contractor shall conduct TIMs and document meeting minutes and action items. The Contractor shall follow-up on action items with a resolution plan. TIMs will be held on a quarterly basis throughout the develop phase of the contract.

• ICWG: The Contractor shall conduct and host ICWG meeting to coordinate the definition and development of Interface Control Documentation (ICD) (hardware and software) of the PDGU, as needed, but no less than on a quarterly basis. The Contractor shall follow-up on working group action items with a resolution plan. ICWGs will be held on a quarterly basis throughout the develop phase of the contract.

• PMRs: The Contractor shall conduct PMRs and document meeting minutes and action items. The Contractor shall follow-up on action items with a resolution plan. PMRs will be held on a quarterly basis.

• Depot Infrastructure: The Contractor shall conduct and support, as necessary, depot infrastructure meetings to address Tech Orders, Depot repair facilities, repair manuals and repair test procedures, and product supply chain management activities required support the effective fielding of the PDGU. Depot Infrastructure meetings will be held on quarterly basis starting after CDR through depot set-up.

• Program Protection Working Group: The Contractor shall support the USG-led Program Protection Working Group. These meetings are intended to discuss program protection and system security engineering activities, relay threats and risk information to industry, and provide program protection training/expectations. These meetings can and should be held as VTCs or telecoms or as part of existing face-to-face meetings including TIMs and Design Reviews.

• Provisioning Guidance Conference and Technical Review Conferences: The Contractor shall support and participate in USG led Provisioning Guidance Conferences between USG, USAF, and major vendors to ensure a mutual understanding of the contractual provision requirements. The goal of the conference will be to clearly define requirements and establish deadlines for the provisioning cycle. The Provisioning Guidance Conference will be held at Ogden Air Logistics Complex (OO-ALC) 60 days after the initial production option has been exercised, or as directed by the Program Manager.

• Spare Provisioning Conference: The Contractor shall support and participate in a USG led Spare Provisioning Conference to define item selection, appoint technical, and management codes to include validation of source, maintenance, and recoverability (SMR) codes. Spare Provisioning Conference meetings will be held on annual basis starting after CDR through depot set-up.

• F-16 Test Integrated Product Team: The Contractor shall support Test Integrated Product Team (TIPT) and Integrated DT&E/OT&E meetings. The Contractor shall follow-up on action items with a resolution plan. TIPT meetings will be held on quarterly basis starting after PDR through DT&E/OT&E.

• Airworthiness Certification board: The Contractor shall support and participate in the Airworthiness Certification boards. The board is anticipated to be held on a quarterly basis through-out the EMD phase of the program.

3.2.1.9 Utilization of Small Business

The contractor shall make a best effort to meet small business subcontracting goals to include Small Businesses (SB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran-Owned Small Business (SDVOSB), HUB Zone Small Business (HUB Zone), Small Disadvantaged Business (SDB), and with Women Owned Small Business (WOSB).

3.2.1.9.1 Small Business Participation Requirements

a) The Government has set a minimum small business subcontracting goal for this effort of 10% of the total subcontracted amount the allocations are:

• Small Disadvantaged Business (SDB): 5% of total subcontracted amount in para. “a” above

• Woman-Owned Small Business: 5% of total subcontracted amount in para. “a” above

• Hub-zone: 3% of total subcontracted amount in para. “a” above

• Service-Disabled Veteran-Owned Small Business: 3% of total subcontracted amount in para. “a” above.

b) The Contractor shall provide a Small Business Subcontracting Plan in accordance with (IAW)

Federal Acquisition Regulation (FAR) 52-219-9, Small Business Subcontracting Plan.

3.2.2 WBS 1.2 Systems Engineering

The Contractor shall provide a Systems Engineering Management Plan (SEMP) which describes how the Contractor’s Systems Engineering (SE) processes and organizational structure will support the development and production of the PDGU, integration with the Governments Integrated Product Team (IPT) organizational structure, and the activities outlined in section 3.4.

The SEMP shall also address the overall life cycle approach to the integrated Contractor/USG technical management of the program, to include logistics, and sustainment and maintenance.

The SEMP shall comply with DI-SESS-81785.

3.2.2.1 System/Subsystem Design

The Contractor shall develop and provide the following PDGU design documentation: Subsystem Specification (SSS), DI-IPSC-81431A. The SSDD shall describes the system or subsystem-wide design and the architectural design of a system or subsystem and the performance requirements for hardware, software, and data management/processing requirements for aircrew and maintenance training devices.

In addition, the Contactor shall develop and provide the following software deliverables that address each CSCI proposed for development: Software Requirements Specifications (SRS) DI- IPSC-81433A, Software Design Description (SDD), DI-IPSC-81435A, Software Test Plans, DI-IPSC- 81438A, Software Test Descriptions, DI-IPSC-81439A, Software Test Reports, DI IPSC-81440A, Interface Design Descriptions, DI-IPSC-81436B, and Software Version Descriptions, DI-IPSC- 81442A.

For reused, off-the-shelf, or non-developmental software that did not have the deliverable developed, the Contractor shall provide an equivalent level of development documentation, verification data and/or certification package data showing suitability for use within the PDGU.

3.2.2.2 Requirements Management

The SEMP shall address how the Contractor will manage requirements throughout the PDGU subsystem development and qualification. The SEMP shall address the Contractors requirement management tools and process and how the Contractor plans to baseline and manage requirement development, changes along with bi-directional traceability. The Contractor shall grant the USG access to the Contractor’s requirements database and bi-directional traceability tool. 30 days after FCA/PCA the Contractor shall deliver the final version of the requirements database a bi-directional traceability. The Contractor shall provide this file in an electronic format compatible with the DOORS software requirement management toolset.

The Contractor shall generate requirements specifications, using a comprehensive and rigorous requirements analysis and management process, for the system, subsystem(s), and configuration item(s) levels including the functional and performance baseline, the allocated baseline (i.e., design-to), and product baseline(s) per, DI-IPSC-81432A , DI-SDMP-81464A and DI-

SDMP-81493A.

The Contractor shall trace all requirements bi-directionally and ensure the requirements are documented and traced (1) to the SSRD, (2) between levels (e.g., SSRD to system specification, system specification to subsystem specification, subsystem specification to hardware/software specifications), and (3) to verification plans/procedures/products.

The Contractor shall ensure the requirements traceability identifies Safety Critical Functions (SCF) and identifies any requirement that supports a given SCF.

The Contractor shall develop and deliver a PDGU’s Subsystem Specification (SSS). The SSS shall contain the performance requirements for hardware and software, and data management/processing requirements for aircrew and maintenance training devices DI-IPSC- 81431A.

3.2.2.3 Interface Management

The Contractor shall manage all interfaces (hardware and software) of the PDGU. The Contractor shall establish an interface management process which shall be addressed in the

SEMP.

The Contractor shall develop and deliver internal and external PDGU ICDs (hardware and software). The deliverable ICDs shall be in a native electronic form, preferably a form fillable (fields tied to data) or Excel (table) format clearly delineating the data field used as a guideline

DI-CMAN-81248A.

3.2.2.3.1 Electrical Interface Management

The Contractor shall manage and document all non-software and software controlled electrical (internal and external) interfaces of the PDGU subsystem. The deliverable shall be an electronic format explicitly indicating interfaces and traceability to requirements, DI-CMAN-81248A.

3.2.2.3.2 Mechanical Interface Management

The Contractor shall manage and document all mechanical interfaces (internal and external) of the PDGU subsystem. The deliverable shall be an electronic format explicitly indicating interfaces and traceability to requirements, DI-SESS-81000E. In addition the Contractor shall provide a Structural Engineering Analysis Technical Report per DI-SESS-80567B.

3.2.2.3.3 Software Interface Management

The Contractor shall manage and document all software (internal and external) Computer Software Component (CSC) and CSCI interfaces of the PDGU subsystem, DI-IPSC-81436B.

3.2.2.4 Weight Management

The Contractor shall implement a weight management program and process to ensure the PDGU weight remains within the PDGU SSRD weight allocation. The weight management program and process shall ensure the following:

• Provide a Mass Properties Management Plan that describes the methodology to track, manage and report each PDGU CI weight allocation (budget) to the actual CI weight, DI-MISC-80508B,

• Provide a Weight and Balance Report which tracks the mass properties for each PDGU CI (3 axis center of gravity and moment of inertia, and weight), DI-MISC- 80508B

• Ensure each CI comprising the PDGU mass properties is clearly documented and identified on a Source Control Drawing (SCD).

3.2.2.5 Life Cycle Cost Management

The Contractor shall perform Life Cycle Cost Management which includes such technical tasks as engineering and logistical investigations and analyses, intended to ensure continued operation and maintenance. Specifically the Contractor shall perform: collecting and triage of all service use and maintenance data; analysis of safety hazards, failure causes and effects, reliability and maintainability trends, and operational usage profiles changes; root cause analysis of in-service problems (i.e. deficiency reports, parts obsolescence, corrosion effects, and reliability degradation); development of required design changes to resolve operational issues; and other activities necessary to ensure cost-effective support to achieve readiness and performance requirements over the PDGU system’s life-cycle. The Contractor shall address these activities during the Material Improvement Project Review Boards (MIPRB) to address technology insertion, engineering dispositions, technical manual and technical order updates, repair and upgrade versus disposal or retirement analyses, and maintenance evaluations analyses DAL.

3.2.2.6 Parts Management

The Contractor shall develop and deliver a Parts Management Plan, DI-SDMP-81748 and DI- MISC-80072D, which is intended to implement a process that ensures long-term availability of configured parts that are intended to mitigate expected and unexpected changes required to satisfy redesign as part of future Diminishing Manufacturing Sources (DMS) DI-MISC-80508B.

The Contractor shall implement a DMS program and process which will track and identify potential PDGU components at risk of becoming unavailable. In addition, the DMS program shall identify alternative components which may be used as replacement for components at risk of becoming unavailable without impacting the PDGU subsystems performance, form, fit, function, and interface. Any changes in components which affect the PDGU performance, form, fit, or function shall be coordinated with the USG for approval. The Contractor shall provide notification to the USG of any changes not affecting PDGU performance, form, fit, or function.

The Contractor shall provide a PDGU DMS support plan to include managing parts via DMS component obsolescence database, which will continuously assess component availability for customer systems, providing detailed engineering evaluations and support for DMS component issues, alerting the customer of DMS issues specifically affecting their systems, and providing recommendations to the customer for resolving DMS issues based on cost, risk, or other critical management factors DI-MISC-80508B.

The Contractor shall resolve DMS issues pertaining to change in form, fit, function, or interface within the scope of this contract period. The Contractor shall provide a notice of major changes (Class I and II) to the USG following the establishment of an updated configuration.

The Contractor shall requalify the PDGU when DMS part replacement is within the form, fit, function, or system interface.

The Contractor shall provide all Class I changes to the USG for review and approval per DI-SESS- 80639D. The Contractor shall provide all Class II changes to the USG for review per DI-MISC- 81562. The USG reserves the right to reclassify Class II changes to Class I.

3.2.2.7 Lead Free Solder

The Contractor shall comply with and meet the performance, compatibility, reliability, and safety and verifiability requirements for lead free products in GEIA-STD-0005-1, GEIA-STD-0005- 2A, GEIA-STD-0006, and IPC-J-STD-609.

The Contractor shall develop and implement, or provide evidence of, an existing Lead-Free Control Program (LFCP) which reduces the harmful effects of metal whiskers. The LFCP shall encompass all the requirements of GEIA-STD-0005-1 and GEIA-STD-005-2. The Contractor shall ensure that the risks associated with lead-free solder and finishes are considered, mitigated, and managed in the Contractor’s Systems Engineering Risk management process DI-MGMT- 81772.

3.2.2.8 Reliability and Maintainability Management

The Contractor shall develop and implement a Reliability and Maintainability Plan (R&MP) and program, DI-SESS-80567B. The R&MP shall address how the Contractor will comply with the Reliability and Maintainability (R&M) requirements stated in the PDGU SSRD. MIL-HDBK-470A may be used as a guide for the development of the R&MP. The Contractor shall identify and provide details on any proprietary or commercial reliability software or toolkits planned for use to aid in the development of the R&MP.

The Contractor shall ensure all hardware CIs provided are designed, developed, tested, and produced IAW the R&MP and R&M requirements stated in the PDGU SSRD. The Contractor shall ensure the first production article complies with the R&MP and R&M requirements stated in the

SSRD.

The R&MP shall address in detail the Contractor’s approach to performing a Reliability Prediction Analysis (RPA) on each hardware CI. The Contractor may use MIL-HDBK-217F, Reliability Prediction Procedure of Electronic Equipment and DI-SESS-80567B as a guide for the development of the RPA.

The Contractor shall identify and provide details in the R&MP on any proprietary or commercial reliability prediction software or tools planned for use to aid in the generation of the PDGU prediction analysis. The RPA shall take into account the full spectrum of exposure to the environmental conditions defined in the PDGU SSRD.

The R&MP shall address in detail the Contractor‘s approach to performing a System/Subsystem Hazard Analysis (SSHA) and Failure Mode, Effects and Criticality Analysis (FMECA) and Fault Tree Analysis, DI-SAFT-80101C, DI-SESS-81495A and DI-MISC-80508B on each configuration item.

The R&MP shall address the areas the Contractor will cover in the FMECA including failure mode, probability of failure of components, and failure detection methods. The FMECA shall classify each failure mode according to its impact on the PDGU’s operational performance, and safety.

The R&MP shall address in detail the Contractor’s approach to performing a Reliability and Maintainability Prediction Analysis, DI-SESS-81497A, on each CI. The Contractor may use MIL- HDBK-470A as a guide for the development of the MPA; however the Contractor is encouraged to use actual maintenance data, if available, for the MPA.

The R&MP shall address in detail how the Contractor shall manage, plan, and execute a Reliability Test Program (RTP). The Contractor shall use the following DID as a guide to develop the applicable documents, DI-NDTI-80566 for the Reliability Test Plan, DI-NDTI-80603A for the Reliability Test Procedure and DI-QCIC-81890 for the Reliability Test Report. The RTP is intended to present how the PDGU design reliability increases through the identification of design deficiencies (hardware and software) and the effectiveness of corrective actions with the intent to reduce the occurrence of operational failures. The R&MP shall discuss the test method(s), environments, and test profiles the Contractor will use during the performance of the RTP.

The R&MP shall address in detail the Contractor’s approach to detect early life and latent failures in each PDGU CI prior to delivery.

In the event the Contractor uses sub-Contractors to develop portions of the PDGU, the Contractor shall ensure all R&M requirements stated in the PDGU SSRD are allocated to each sub-Contractor.

3.2.2.8.1 Failure and Deficiency Reporting Management

The R&MP shall address in detail the Contractor’s implementation of a Failure Reporting (FR) process as part of the PDGU formal developmental test activities during EMD. The objective of the failure reporting process is to identify failure trends, failures that appear to indicate reliability issues with the PDGU, and corrective actions. Corrective actions shall focus on preventing a reoccurrence of the failure. The failure reporting process shall document failures or anomalies that occur during formal development testing activities and include failure analysis, root-cause failure analysis, and repair and corrective actions. As part of the FR process, the Contactor shall provide data to and coordinate with the USG on how failed equipment will be repaired.

The R&MP shall address in detail the Contractor’s establishment of a Failure Review Board (FRB) which will be comprised of key Contractor and USG technical and management personnel. The FRB will direct and control all test failure reporting, analysis, and corrective and repair actions.

The FRB meeting schedule will be coordinated with the USG program office personnel to ensure the FRB meeting schedule supports the PDGU program development FR process. The Contractor has the responsibility to record all FRB meeting minutes and action items, and shall provide all meeting minutes to the Government according to DI-ADMN-81249A and DI-ADMN- 81250A.

The Contractor shall identify and generate Deficiency Reports (DR), use DI-SESS-80567B as a guide, for any PDGU deficiency that impacts performance compliance, Operational Safety, Suitability, and Effectiveness (OSS&E) and the Program Protection Plan (PPP) of systems and their sub and/or support systems to include trainers, test, and support equipment.

The Contractor shall notify the USG within 24 hours of failures which occur during development (acceptance, environmental stress screening, performance, and environmental and electromagnetic qualification testing). Notification shall be via email and/or phone call to the assigned USG point of contact. Deficiency Reports shall be provided within 48 hours of the failure notification. Production failures shall be submitted to the USG on a monthly basis.

3.2.2.9 Logistics, Packaging, Handling, Storage and Transportation

The Contractor shall develop an Integrated Logistics Support Plan (ILSP) describing the maintenance concept, supply support concept and provisioning tasks, configuration control procedures, training requirements, and other applicable items DI-ILSS-80095.

The Contractor shall implement a comprehensive design approach for system supportability, testability, and self-diagnostic capabilities which addresses cost benefits, effectiveness, risk, and future support system requirements. The Contractor shall integrate engineering and logistics analyses and modeling efforts to quantify support resources (i.e. support equipment, spares, personnel, and facilities) to minimize PDGU logistics footprint while meeting operational requirements at each operational location, the Contractor shall use MIL-HDBK-502 as a guide.

The Contractor shall recommend an Initial Spare Parts List. The Contractor shall support provisioning at a top-down Line Replaceable Unit (LRU)/ Shop Replaceable Unit (SRU) level and at the component parts level, the Contractor shall provide the above information in the Logistics Management Information Data Products (LMI).

The Contractor shall meet Packaging, Handling, Storage, & Transportation (PHS&T) requirements IAW MIL-STD-2073-1D and the most current revision of Special Packaging Instruction (SPI) F01-222-3829.

3.2.2.9.1 Provisioning

In cooperation with the USG, the Contractor shall participate in the provisioning process to determine and acquire the range and quantity of support items necessary to operate and maintain the PDGU for an initial period of service and for long-term sustainment.

The Contractor shall provide the provisioning data per and the Initial Provisioning Performance Specification (IPPS) provided with this contract.

The Contractor shall submit a Logistics Product Data (LPD), DI-SESS-81758 and Logistics Product Data Summaries DI-SESS-81759A. The LPD shall be submitted in a format compatible with the Air Force Material Command (AFMC) Automated Provisioning System (D220) as requires by the IPPS including attachments. The schedule for submitting the LPD shall be in accordance with the Provisioning Performance Schedule (AFMC Form 718) which will be completed at the Provisioning Guidance Conference.

Engineering Data for Provisioning (EDFP) schedule and requirements for submitting shall be per

DI-SESS-81874.

3.2.2.10 Materiel Improvement Project and Joint Deficiency Reporting System

The Contractor shall perform Material Improvement Project (MIP), DI-MGMT-80258A, and investigations as directed by the USG. The Contractor shall provide a MIP coordinator and the necessary staff for the receipt, status control, conduct, preparation, and transmittal of engineering/investigative analysis and recommended solutions to deficiency reports as described in TO 00-35D-54, USAF Deficiency Reporting and Investigating System.

The Contractor shall participate and provide investigation, analysis, testing, and reporting in support of the USG’s Joint Deficiency Reporting System (JDRS) (USAF TO 00-35D-54) and the USG MIP review board.

3.2.2.11 System Safety Management

The Contractor shall conduct a System Safety Program IAW MIL-STD-882E. Section 4 of MIL- STD-882E identifies the overall system safety requirements and Section 4.4 identifies the specific requirements related to software’s contribution to overall system risk. The Contractor shall ensure all the requirements of section 4 of MIL-STD-882E are met. The Contractor may use Appendix B of MIL-STD-882E as a guide to ensure the software safety requirements stated in Section 4.4 are met.

The Contractor shall develop and provide a System Safety Program Plan (SSPP), DI-SAFT-81626.

As a minimum the SSPP shall document, track and discuss the resolution of hazards related to the PDGU hardware and software and Contractor developed support equipment. As part of the

SSPP the Contactor shall address, in detail, the verification methodology to be implemented to verify safety features incorporated in the PDGU. Verification of safety features shall be documented in a Safety Assessment Report (SAR).

The…