MMIII INTEG DRAFT v1.16.pdf

FA8207-XX-X-XXX

MMIII INTEGRATION TASK ORDER PWS- ISC 2.0

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

INTEGRATION SUPPORT CONTRACT (ISC) 2.0

MMIII SUSTAINMENT TASK ORDER

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

dd MMM 2019

1.0 MMIII Integration

1.1 Scope ........................................................................... Error! Bookmark not defined.

1.2 Purpose ........................................................................ Error! Bookmark not defined.

1.3 Background .................................................................. Error! Bookmark not defined.

2.0 Requirements Summary

2.1 Required Labor Categories .......................................... Error! Bookmark not defined.

2.2 Deliverables ................................................................. Error! Bookmark not defined.

2.3 Property Management .................................................. Error! Bookmark not defined.

2.4 Quality ......................................................................... Error! Bookmark not defined.

2.4.1 Summary Matrix [Example] .................................... Error! Bookmark not defined.

2.5 Security ........................................................................ Error! Bookmark not defined.

2.6 Cyber Security Requirements ...................................... Error! Bookmark not defined.

3.0 Award Fee Plan .................................................................. Error! Bookmark not defined.

2.0 Appendices

APPENDIX A: ACRONYMS AND ABBREVIATIONS

APPENDIX B: WORK BREAKDOWN STRUCTURE

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT

(GFP/GFS/GFE)

APPENDIX E: CONTRACT DATA REQUIREMENTS LIST (CDRL)

1. MMIII INTEGRATION BRANCH

ICBM Integration Branch Description

The ICBM Integration Branch provides specialty engineering and technical support to MMIII acquisition and sustainment programs/projects as well as select functional areas of support to

GBSD.

Branch Structure (as of Jan 2020)

The Integration Branch falls under the MMIII SPO and consists of three sections.

SPO and Directorate Support

Leadership from the three branches in the MMIII SPO are responsible for establishing system-level priorities and articulating branch perspectives while working together to balance system-level requirements. They review, deconflict and prioritize the IPTs’ recommendations.

Integration Branch personnel participate in IPT(s) per the IPTs’ need for High-

Demand/Low-Density (HD/LD) and other specialty services provided by the Integration

Branch (e.g. Test, Nuclear Surety, Hardness, etc.).

Integration Branch personnel are commonly assigned to multiple IPTs. When assigned to multiple IPTs, their time is aligned with priorities set by Division Leadership.

Although the Integration Branch falls under the MMIII SPO, the branch also provides select functional areas of support to the GBSD SPO as needed.

Integration Sections

The Data Management Section includes Data Management, Configuration Management, Interface Control, Systems Engineering, and the Technical Order Management Agency

(TOMA).

The Specialty Engineering Section includes Nuclear Surety, Nuclear Hardness and

Survivability, System Safety, Corrosion, Environmental Engineering, and Systems Security

The Test and Assessment Section includes Operational Test Launch, Weapon System

Assessment, Modeling and Simulation, the Strategic Missile Integration Complex (SMIC), and Test Management.

Also included in the Integration Branch’s responsibilities are the Alternate Lead

Developmental Test Organization (Alt-LDTO) and Diminishing Manufacturing Sources and Material Shortages (DMSMS) process.

2. GENERAL REQUIREMENTS

2.1. All requirements in the Basic PWS of this contract apply to this Task Order

2.2. All work shall be performed in coordination and cooperation with pertinent overseeing government personnel. (The Gov Program Manager and Engineer are responsible for meeting the program’s cost, schedule, technical and performance objectives. As the system integrator, the Government is the decision authority.)

2.3. All work shall be performed in coordination with other contracted personnel as applicable.

2.4. The contractor shall collaborate with appropriate internal and external stakeholders as needed to accomplish requirements and tasks.

2.5. All work shall be performed IAW applicable laws and regulations. The contractor shall

NOT perform any Inherently Government Functions as defined in XXX

2.6. The contractor shall recommend and incorporate process and resource efficiencies, including application of streamlined program management techniques and other industry best practices.

3. DATA MANAGEMENT SECTION

Data Management Section Description

The Data Management Section is responsible for managing and maintaining the technical baseline of the MMIII weapon system. Specifically, the Data Management Office (DMO), Configuration Management Office (CMO), Systems Engineering (Risk, MBSE, System

Requirements Analysis (SRA)), and the Technical Order Management Agency (TOMA) all reside in the Data Management Section.

3.1. Data Management Organization (DMO)

DMO Description

The DMO includes the following, with the goal of effectively supporting the Warfighter with the best capability at the time it is needed:

Identifying, planning, resourcing, and implementing management actions to develop and acquire data to operate, install, maintain, and train on equipment to maximize effectiveness and availability

Effectively cataloging the acquisition of spare/repair parts, support equipment, and all classes of supply

Defining the configuration baseline of the system (hardware and software)

3.1.1. DMO Requirements

3.1.1.1. The contractor shall support the DMO in integrating program/technical data captured in current and future data systems throughout the MMIII division.

3.1.1.2. The contractor shall assist the DMO in managing MMIII data, including managing data deliveries, systems, processes, schedules and tools for efficiently maintaining, archiving, and retrieving MMIII data.

3.1.2. DMO Tools

The current official Data Management System of Record (DMSOR) is CDRLVue. The

DMSOR will be the central repository for all MMIII- and contractor-developed data, draft, final versions, CRMs, and official approving/rejecting documents.

3.1.2.1. The contractor shall utilize the current DMSOR for managing data.

3.1.2.2. The contractor shall assist in managing data deliverables received by the

DMO. (The government will manage ISC data requirements and deliverables.)

3.1.2.3. The contractor shall collect data sets from current and future MMIII data and data systems, as requested by the government.

3.1.2.4. The contractor shall link or integrate deliverable schedules from MMIII programs into the DMSOR to provide a complete CDRL requirements system.

3.1.2.5. The contractor shall recommend changes and efficiencies to the DMSOR where warranted.

3.1.2.6. The contractor shall assist the DMO with gathering requirements and system migration of MMIII data from all current and future data sources.

(Data and processes are expected to transition to an enterprise Product

Lifecycle Management (PLM) system early in the PoP of this contract.)

3.2. Configuration Management (CM)

CM Description

CM is the planning and management of functional, allocated, and product baseline configurations for hardware and software. It generally includes:

Configuration identification

Configuration control

Configuration Status Accounting (CSA) o CSA is the ability to provide accurate, timely information concerning a product and its configuration information throughout the product lifecycle.

o CSA provides status of proposed changes, implementation of approved changes, and changes occurring due to operation and maintenance.

Configuration verification and auditing, IAW military and industrial guidance (i.e. MIL-

HDBK-61A, EIA-649, EIA 649-1, etc.)

Other configuration related processes and tasks

3.2.1. CM Requirements

3.2.1.1. The contractor shall provide CM support for all programs/projects/tasks within the MMIII Division.

3.2.1.2. This support shall include development and/or reviewing of the following documents: (CDRL)

Engineering Change Proposals (ECPs)

Engineering Orders (EOs)

Specification Change Notices (SCNs)

Product Engineering design data and associated lists

Interface Control Documents (ICDs)

Request for Variance (RFV)

Functional and Physical Configuration Audit (FCA/PCA) certification packages

3.2.1.3. The contractor shall provide support to the Government Technical

Engineering Review Board (TERB) and Configuration Control Board

(CCB) by acting as the Integrator. This includes tasks such as:

Scheduling TERB and CCB meetings

Reviewing briefings for completeness

Coordinating comments/non-concurrence with the briefer prior to the meeting

Tracking action items

Other tasks as needed to facilitate successful TERBs and CCBs

3.2.1.4. The contractor shall review ECPs for classification of change (Class I/

Class II) and impacts to the technical engineering baseline.

3.2.1.4.1. The contractor shall perform evaluations and develop recommended technical positions for all Class I ECPs

3.2.1.4.2. The contractor shall validate incorporation of ECPs into the technical data and configuration management status accounting systems.

3.2.1.5. The contractor shall maintain the technical engineering baseline

(configuration item specifications, process/material specifications, drawings/models, ICDs, hardness data manuals, etc) IAW AF and ICBM policy and applicable standards.

3.2.1.6. The contractor shall develop and maintain AF drawings and models IAW

AF policy and ASME Y14 series standards. (CDRL)

3.2.1.7. The contractor shall make recommendations for process improvements that could make ICBM documentation more usable/accessible in management and support of the weapon system, and execute those improvements approved and directed by the government.

3.2.2. Software Configuration Management

Weapon system software includes Operational Software, Trainer Software, Test Facility

Software, Automatic Test Equipment software, Mission Application Software and Data

System Software, etc.

3.2.2.1. The contractor shall monitor and ensure configuration control of weapon system software, software analysis, and integration into the weapon system, maintaining configuration and Computer Program Identification

Number (CPIN) support IAW ICBM Configuration Management Plan

(62-CMP).

3.2.2.2. The contractor shall ensure CPINs are maintained, current IAW Enhanced

Technical Information Management System (ETIMS), and that software is the authorized version IAW Software Version Description (SVD).

3.2.2.3. Contractor shall review and provide feedback on the following software requirements as applicable:

Computer Program End Item Documentation

Software Requirements Specification (SRS)

Software Design Description (SDD)

Software Test Plan (STP)

Software Test Description (STD)

Software Test Report (STR)

Software Product Specification (SPS)

3.2.3. Interface Control

Interface requirements consist of the functional, performance, environmental, human and physical requirements and constraints that exist at a common boundary between two or more functions, system elements, configuration items, or systems.

3.2.3.1. Interface Control Requirements

3.2.3.1.1. The contractor, in coordination with the appropriate subsystem contractor(s), shall assist the government in validating and controlling interface requirements.

3.2.3.1.2. The contractor shall maintain established controls for interface requirements and drawings, which include contractor, vendor, and subcontractor items, government furnished equipment, computer programs, facilities, data, etc.

3.2.3.2. The contractor shall ensure changes are properly coordinated IAW applicable regulations/processes.

3.2.3.3. The contractor shall adhere to the guidelines contained in ICBM-HDBK-

02 (which provides guidance and examples of all interface control procedures and policies used since inception of the ICBM Interface

Control Program), in order to enable any new interface documentation to be integrated into the existing ICBM Interface Control Documentation system.

3.2.3.4. The contractor shall participate as a member of the Interface Control

Working Group (ICWG).

3.2.3.4.1. The contractor shall provide engineering support to the ICWG chairperson (Government Chief Engineer)

3.2.3.4.2. The contractor shall assume collateral responsibilities with the

Government to accomplish interface management.

3.2.3.4.3. The contractor shall ensure coordination between and among

Government and subsystem contractors/subcontractors when:

Preparing Scope Sheets (SS), Interface Control Documents/

Drawings and Interface Revisions

Evaluating Interface Control problems and recommending the Government request corrective actions

Recommending required controls including gauges

Identifying and evaluating all Class I and II changes involving new technology parts, ECPs, or variances, for interface impacts and to ensure proper categorization.

3.3. Systems Engineering (SE)

3.3.1. General

3.3.1.1. The contractor shall perform appropriate SE technical and technical management processes in support of acquisition and sustainment processes. SE processes include:

Requirements definition and analysis

Architecture design

Implementation

Integration

Verification and validation

Transition

Decision analysis

Technical planning

Technical assessment

Requirements management

Risk management

Configuration management

Technical data management

Interface management

Use of requirements management tools

Etc.

3.3.1.2. The contractor shall plan and execute technical reviews and assessments

(e.g. System Requirements Review, Technology Readiness Assessment, etc.) and develop associated documentation (e.g., Systems Engineering

Plan (SEP), Risk Management Plan (RMP), etc.).

3.3.1.3. The contractor shall provide inputs and administrative support to the

OBD, SEP, RMP

3.3.1.4. The contractor shall make recommendations for and support process improvement activities.

3.3.1.5. The contractor shall use applicable requirements management tools as appropriate

3.3.2. Risk Management

MMIII Risk Management is the process used by decision makers at all levels to identify and analyze risks and then accept/mitigate those risks. The MMIII Risk Management process includes developing, maintaining, and updating program Risk Management Plans

(RMPs) IAW the Risk Management Guide for DoD Acquisition, AFPAM 63-128, and the

Air Force Risk Identification Integration and Ilities (RI3) Guidebook; facilitating program risk identification, risk analysis, risk handling and risk monitoring; executing program Risk

Management Boards (RMBs), risk management working groups (or equivalent), and documenting results. The effort also includes analyzing prime and subcontractor risk management processes.

3.3.2.1. The contractor shall perform and support execution of the MMIII Risk

Management process

3.3.2.2. The contractor shall identify, analyze, and track MMIII weapon system risks

3.3.2.3. The contractor shall maintain the government-designated Risk

Management Tool (database)

3.3.2.3.1. The contractor shall assist in data entry

3.3.2.3.2. The contractor shall retrieve and analyze risk data as needed

3.3.2.4. The contractor shall publish a Risk Management Book (CDRL)

3.3.2.5. The contractor shall provide administrative support for Risk Management

Boards, IPT Detailed Risk Reviews, and other Risk Management-related meetings

3.3.2.6. The contractor shall support IPT risk integrators

3.3.2.7. The contractor shall develop, maintain, and update program Risk

Management Plans (RMPs) (CDRL)

3.3.2.8. The contractor shall facilitate program risk identification, risk analysis, risk handling, and risk monitoring;

3.3.2.9. The contractor shall execute program Risk Management Boards (RMBs) and working groups (or equivalent) and document results.

3.3.2.10. The contrtactor shall analyze prime and subcontractor risk management processes

3.3.3. Model Based Systems Engineering (MBSE) Support

ICBMSD requires MBSE to enable preservation of MMIII technical integrity by making it easier to determine if changes to one MMIII sub-system impact other sub-systems. The

Government is responsible for configuration management oversight of the MMIII system architecture model as part of the weapon system technical baseline.

3.3.3.1. The Contractor shall develop and deliver MBSE system architecture models for the MMIII system (CDRL)

3.3.3.2. The Contractor shall deliver system architecture models in System

Modeling Language (SySML) development tool-native file format, Extensible Markup Language (XML) format, and Hypertext Markup

Language (HTML) format, as appropriate. (CDRL)

3.3.3.3. The Contractor shall provide MBSE system architecture model elements to other Government-designated contractors (CDRL)

3.3.3.4. The contractor shall integrate externally-provided, government-approved updates to the system architecture model.

3.3.3.5. The Contractor shall ensure the MMIII system architecture model supports design review entrance/exit criteria development, requirements development and analysis, interface definition, system verification and validation, implementation of technical baseline changes, and other tasks necessary for the continued operational safety, suitability, and effectiveness of the MMII weapon system in all configurations.

3.3.3.6. The contractor shall support development and inclusion of SCSI, CSC, and lower level models into the MMIII system architecture model.

4. SPECIALTY ENGINEERING SECTION

Specialy Engineering Section Description

4.1. General

4.1.1. The contractor shall participate in ICBMSD data calls as subject matter experts to verify future programs have correct level of specialty requirements and deliverables.

4.1.2. The contractor shall participate in ICBMSD Technical Evaluation Review Boards and Configuration Control Boards by providing specialty engineering input and impacts for their area of expertise.

4.2. System Integrity Verification (SIV) Team

SIV review of proposed system and procedure changes informs the Engineering Approval Authority

(EAA) of their impact to Environment, Safety, and Occupational Health (ESOH), Explosive Safety, Nuclear Surety, Nuclear Hardness and Survivability (NH&S), Corrosion, and System Security for

ICBM systems. The SIV process assists with technical risk identification and mitigation throughout relevant milestones. The SIV process also reviews compliance with applicable requirements and regulations related to the specialty engineering areas.

4.2.1. The contractor shall support the ICBM SIV process by providing specialty engineering expertise in reviewing weapons system documentation.

4.2.2. SIV reviewers from specialty engineering shall review documents such as the following for impacts to their area of expertise:

ICBM Tech Order change recommendations produced by field units, SPO, AFGLSC, ICBM Depot organizations, and/or subsystem contractors

Tech Order data produced by ICBM modification programs

Field or SPO generated -107 ETAR requests per Tech Order 00-25-107

Depot generated AFMC IMT/Form 202 requests

Field generated -107 MAR requests per Tech Order 00-25-107

Time Compliant Technical Orders

Depot generated AFMC IMT/Form 202 requests

Test directives, test plans, test reports and engineering procedures developed in support of depot and operational test and maintenance projects

System engineering acquisition documentation and program/management plans

Implementation Management Plans

Drawings and Engineering Orders

Weapon system risks

System safety risk assessments

Engineering Change Proposals, Technical Evaluation Review Board packages, and Configuration Control Board packages

Programmatic Environmental Safety and Occupational Health Evaluation

(PESHE)

Specification or Specification Change Notice

Electromagnetic Compatibility (EMC) Analysis

4.2.3. The contractor shall provide SIV metrics IAW current ICBM policy

4.3. Nuclear Surety Support

Nuclear Surety Description

The Air Force uses the DoD definition for Nuclear Weapons Surety: Materiel, personnel, and procedures which contribute to the security, safety, and reliability of nuclear weapons and to the assurance that there will be no nuclear weapon accidents, incidents, unauthorized weapon detonations, or degradation in performance at the target. AF implementation of DoD requirements are described in AFPD 91-1 and further detailed in: AFI 91-101, AFI 91-102, AFI

91-103, AFI 91-104, AFI 91-105, AFI 91-106, AFI 91-107, AFI 91-114, AFI 91-117, AFMAN

91-118, AFMAN 91-119, AFMC and AFNWC supplements.

The above policies are tailored for applicability to new or modified ICBM and Air Launch

Control System (ALCS) (installed in Navy E-6B aircraft) hardware and software components, subsystems and systems, support equipment, ICBM facilities, special test and maintenance programs.

Engineering data delivered in support of the DoD and Air Force policies may include:

Nuclear Certification Impact Statements (NCIS)

Certification Requirements Plan (CRP)

Nuclear Certification Plan (NCP)

Nuclear Surety Evaluation (NSE) Report

Fault Tree Analysis

Probabilistic Risk Assessment

Unauthorized Launch Studies

Launch Action Studies

Briefing Materials (Nuclear Surety Briefings, Point Papers and White Papers)

Safety & Nuclear Surety Technical Memorandum

Assessments of Subsystem Contractor Deliverables and source data to ICBM Tech Orders and OPCERT/DECERT Tech Orders procedures for ICBM Nuclear Critical Components according to Technical Manual Contract Requirements (TMCR 86-01)

4.3.1. General Requirements

4.3.1.1. The contractor shall integrate nuclear surety requirements into the ICBM

System Engineering process under direction of the government.

4.3.1.2. The contractor shall support the ICBM System Directorate (ICBMSD) in maintaining its nuclear weapon system surety program IAW DoD requirements detailed in DoD 3150.2-M and DoDD 3150.2.

4.3.1.3. The contractor shall support ICBMSD in maintaining the nuclear certification program IAW AFI 63-125

4.3.1.4. The contractor shall support ICBMSD in achieving and maintaining nuclear certification for ICBM weapon systems.

4.3.1.5. The contractor shall assist AF acquisition PMs in tailoring requirments from AFMAN 91-118, AFMAN 91-119, and other applicable AFI 91 series to ensure nuclear certification requirements are completed in concert with assigned acquisition milestones.

4.3.1.6. The contractor shall derive applicable certification criteria for new or modified ICBM hardware and software components, subsystems and systems, support equipment, facilities, special test and maintenance programs.

4.3.2. Deliverables Support

4.3.2.1. The contractor shall review, provide assessment, and develop deliverables when directed, including deliverable such as:

Nuclear Certification Impact Statement (NCIS)

Certification Requirements Plan (CRP)

Ground Launched Missile Nuclear Safety Analysis Report (NSAR)

Nuclear Surety Evaluation (NSE) Report

Briefing Materials (Nuclear Surety-Briefings, Point Papers and White

Papers)

Safety & Nuclear Surety Technical Memoranda source data for ICBM Technical Orders IAW TMCR 86-01

Changes to ICBM Items in the Master Nuclear Certification List

(MNCL)

Nuclear Certification Plan (NCP)

Engineering Evaluation Report (EER) (Nuclear Surety)

Aircraft Nuclear Safety Analysis Report (NSAR) for Flight Safety

Analysis & NSAR

Software Certification Plan (SCP)

Others as needed

4.3.3. Nuclear Certification Actions

4.3.3.1. The contractor shall assess/analyze for:

Adverse effects on primary safety devices and ICBM weapon system features which control the following nuclear critical functions:

Authorization, Pre-arming, Launching, Releasing, Arming, and

Targeting as detailed in AFI 91-107.

Compliance with AFI 91-107 Table 1, which gives the Air Force established numerical probability requirements for obtaining an unintentional significant nuclear yield because of faults and failures in the ICBM system.

Compliance with AFI 91-107 Table 2, which gives the Air Force established numerical probability requirements for preventing inadvertent critical function activation because of system faults and failures.

Other assessment/analysis as determined by the government

4.3.4. Nuclear Surety Support Requirements

4.3.4.1. The contractor shall complete assigned ICBMSD action items from mishaps, generally including: (CDRL)

Providing detailed recommendations to close all assigned action items from DULL SWORD Deficiency Reports

High Accident Potential (HAP) Report

Safety Investigation Board (SIB) Reports

Operational Review Board (ORB) Reports

Discrepancy Reports (DR)

Potential Code Compromise (PCC) Reports

Code Related Event (CRE) Reports

Etc.

4.3.4.2. The contractor shall work with the IPTs to determine which nuclear certified items show failure trends that may yield a nuclear surety incident.

4.3.4.3. IAW the 91-series AFIs, the contractor shall support special ICBM test and maintenance programs including:

Program Depot Maintenance (PDM)

Hardness Surveillance Electromagnetic Pulse (EMP) Program (HSEP)

Simulated Electronic Launch Minuteman (SELM) test

Other special test or maintenance action required in the operational

ICBM fleet

4.3.4.4. The contractor shall provide nuclear surety support to working groups, including:

Safety IPTs

ICBM Nuclear Surety Working Group (NSWG)

AF Nuclear Weapon System Safety Groups (NWSSGs)

ICBM Project Officers Working Group (POG)

ALCS Nuclear Surety Working Group (AINSWG) with US Navy

Nuclear Command and Control (NC2)/Nuclear Command, Control, and

Communications (NC3) study groups

Lead Project Office (LPO) meeting and working groups

ICBM Codes Conference

Other working groups focused on nuclear surety specialty areas such as

Targeting, Physical Security, etc.

4.3.4.4.1. Support shall include

Developing working group Meeting Agendas

Preparing and consolidating Briefing Materials from other

ICBM SPO IPTs

Status Reports on Engineering Assessments

Answers to Assigned Action Items that have been assigned to other ICBM SPO IPTs

Providing Meeting Minutes to participants

4.3.4.5. The contractor shall provide nuclear surety support to a Special Access

Program (SAP) in a government cleared facility. Level of support will be established post contract award.

4.3.4.6. The contractor shall provide nuclear surety support for assessing new acquisitions as well as existing systems/subsystems

4.3.4.6.1. Assessments shall focus on evaluation and testing of vulnerabilities related to adversary threats and may include:

Blue Team type assessments

Red Team type assessments

Securing multi-layered network architectures

Defense in depth architecture controls and strategies

Etc.

4.3.4.6.2. The contractor shall identify applicable DoD and AFI 91-series tailored requirements for incorporation into the new acquisition

4.3.4.6.3. The contractor shall review and assess acquisition delivered artifacts used for nuclear certification

4.3.4.6.4. The contractor shall support the acquisition in assessment of vulnerabilities affecting the weapon systems.

4.3.4.6.5. The contractor shall coordinate and work with nuclear surety and cybersecurity experts and program stakeholders to ensure that weapon systems meet nuclear surety requirements and standards published in DoD and AF regulations.

4.4. Nuclear Hardness and Survivability (NH&S) Support

NH&S Description

Definitions:

Hardness, as used in this document, refers to nuclear hardness. Nuclear hardness is the ability of a system or any of its elements to withstand exposure to one or more effects of a hostile nuclear environment.

Survivability is the probability of withstanding an enemy attack and is a function of enemy reliability, accuracy, and weapon yield; coupled with the hardness of our ground facilities and missiles.

The Government is responsible for ensuring modifications, maintenance actions, and aging do not degrade existing hardness unless coordinated decisions are made to allow such degradation after system impact (including survivability), cost, and program schedule considerations have been made. Hardness surveillance and assessment activities are necessary to monitor the status of weapon system survivability, track hardness performance trends, and to detect degradation.

The objective of the Nuclear Hardness and Survivability (NH&S) process is to sustain the capability of the weapon system to operate and carry out its mission in a nuclear environment in accordance with the list of governing documents and specifications listed in Table 1 below. This capability is expressed in terms of the hardness levels and distributions of various components and subsystems. This process is carried out at all levels throughout the force, from parts procurements, through Configuration Items (CI) and major subsystems, up to and including the total weapon system.

The NH&S assessment process for all IPTs is summarized in the figure below:

This process contains the essential steps to identify IPT NH&S impacts and risks to the weapon system. The process interfaces with Drawings, Engineering Orders (EOs), Technical Orders

(TOs), Time Change Technical Orders (TCTOs), Parts and Materials Support, and

Government/contractor conducted simulated environment tests. The NH&S process consists of problem confirmation, metric estimation, consequence analysis, and reporting. Problem resolution is worked through applicable sustainment, parts and materials support, and program processes.

4.4.1. General Requirements

4.4.1.1. The contractor shall support the Government and subsystem contractors in the performance of hardness assessments at the system and subsystem-level, evaluate proposals and recommend changes to the weapon system for hardness.

4.4.2. Hardness surveillance assessment

4.4.2.1. The contractor shall assess the adequacy of test planning, surveillance testing, hardness evaluation (including the effects of configuration changes), and FDE at the system and subsystem-levels.

4.4.2.2. In addition, the contractor shall consolidate subsystem inputs into required deliverable reports such as the WSER. (CDRL)

4.4.3. Hardness assurance assessment

4.4.3.1. The contractor shall, in coordination with subsystem contractors, perform studies and validate subsystem inspections and tests to provide assurance that the survivability values for configured modification/substitution items

(including developmental test and evaluation of responses to nuclear and conventional environments) are sufficiently high to prevent degradation of hardness.

4.4.4. Hardness maintenance

4.4.4.1. The contractor shall support the Government in verifying and validating actions recommended by subsystem contractors as required to prevent degradation of hardness.

4.4.4.2. The contractor shall, in coordination with subsystem contractors, recommend actions to maintain nuclear hardness and estimate or project the Key Performance Parameters (KPPs) for subsystem modifications.

(CDRL)

4.4.4.3. The contractor shall recommend actions to maintain current weapon system capabilities.

4.4.5. Deliverables

4.4.5.1. The contractor shall coordinate with and consolidate input from subsystem contractors, as required by the individual items, to deliver these essential products: (CDRL)

Trade-Off Studies and Analysis

NH&S Weapon System Assessment

Survivability Management Status Report Input to WSER

Input to Data Book(s)

Integrated Nuclear Effects Assessment

Subsystem/End Item Specifications (SSS)

System/Subsystem Hardness Requirements & System Requirements

Determination

Hardness Data Manual (HDMs) & Design Analysis Report (DAR)

Updates to include:

o Updates to bring out-of-date HDM or DAR data into agreement with current configuration o Updates necessitated by configuration changes made by any modification or replacement program o Updates necessitated by configuration changes made via drawing changes o Input to ICBM Long Range Planning (ILRP), OPLAN 8044 o Hardness maintenance cost/benefit analysis

4.5. System Safety Support

System Safety Description

The system safety discipline applies engineering and management principles, criteria, and techniques to life cycle activities. The process applies these principles within the constraints of Operational

Safety, Suitability, and Effectiveness (OSS&E). It is used to identify, evaluate, mitigate, and control potential hazards and safety deficiencies during design, development, production, deployment, modification, testing, and sustainment of ICBMSD managed specific equipment items, subsystems, systems, and support facilities. System safety risks are tracked and accepted IAW AFI 91-202, US

Air Force Mishap Prevention Program.

System safety employs MIL-STD-882, System Safety, and methodology and includes Environmental, Safety and Occupational Health (ESOH). Per MIL-STD-882, “ESOH. An acronym that refers to the combination of disciplines that encompass the processes and approaches for addressing laws, regulations, Executive Orders (EO), DoD policies, environmental compliance, and hazards associated with environmental impacts, system safety (e.g., platforms, systems, system-of-systems, weapons, explosives, software, ordnance, combat systems), occupational safety and health, hazardous materials management, and pollution prevention.”

4.5.1. General Requirements

4.5.1.1. The contractor shall support the Government to maintain its Safety Risk

Management Program IAW the most current version of MIL-STD-882, AFI 91-202 and the Safety Risk Management Plan.

4.5.1.2. The contractor shall support the System Safety Program to identify and control ICBM hazards and risks and to prevent and/or track mishaps IAW the requirements tailored from MIL-STD-882, Joint Software Systems

Safety Engineering Handbook, AFPD 91-2, AFI 91-202, AFMAN 91-203, AFI 91-204, AFI 91-208, AFSPCMAN 91-710, AFI 63-101/20-101 and

AFMAN 91-221 Air Force policies.

4.5.2. Deliverables Support

4.5.2.1. The contractor shall review and provide an assessment of subsystem contractor deliverables and other weapon system documents, including

Risk Assessment Studies

System Safety Hazard Analysis Report (SSHAR)

Safety Assessment Reports (SARs)

Risk Acceptance Recommendations

Threat Hazard Assessment

Briefing Materials (Briefings, Point Papers and White Papers)

Safety & Nuclear Technical Memoranda

Source data for ICBM Technical Orders IAW TMCR 86-01

Changes to ICBM Items in the MNCL when risks are addressed at the subsystem-level (CDRL)

Program data entry and maintenance and current risk acceptance status of weapon systems Hazard Tracking Systems (HTS)

System Safety Program Plans

Hazard Tracking System data

Programmatic, Environmental, Safety, and Health Evaluation (PESHE)

Hazardous Materials Management Plan

4.5.2.2. The contractor shall produce any of the listed deliverables when the risk requires system-level resolution.

4.5.2.3. The contractor shall maintain the AF Safety Risk Management official files of all risk assessment/acceptance.

4.5.2.3.1. The contractor shall prepare risk assessments and risk acceptance recommendations and staffing packages

4.5.2.3.2. The contractor shall enter hazard data into the Hazard Tracking

System

4.5.2.3.3. The contractor shall enter risk acceptance dates into the Hazard

Tracking System

4.5.2.3.4. The contractor shall track need for reacceptance of system safety risk per AFI 91-202

4.5.3. Safety Support

4.5.3.1. The contractor shall, in coordination and cooperation with subsystem contractors as required, provide safety support to complete assigned ICBM

SPO action items from ICBM mishaps.

4.5.3.2. Support shall include

Tracking

Providing detailed recommendations to close all assigned action items from DULL SWORD Deficiency Reports

High Accident Potential (HAP) Report

Safety Investigation Board (SIB) Reports

Operational Review Board (ORB) Reports

Potential Code Compromise (PCC) Reports

Code Related Event (CRE) Reports

Contractor’s Corrective Action Plan

4.5.3.3. The contractor shall, in coordination and cooperation with subsystem contractors as required, provide safety support to Special ICBM test and maintenance programs such as Programmed Depot Maintenance (PDM), HSEP, and SELM tests or other special test or maintenance action required in the operational ICBM fleet.

4.5.3.4. Support shall include development of assessments, reports and briefings to verify compliance with applicable AFI 91 series requirements. (CDRL)

4.5.3.5. The contractor shall support test safety activities through review of test planning documentation for system safety requirements IAW AFI 91-202

AFMCSUP Chapter 13.

4.5.3.5.1. The Contractor shall provide System safety test witnessing on government behalf as needed.

4.5.3.5.2. The Contractor shall provide input into the test safety review board for test hazards based off review of delivered test planning documentation.

4.5.3.5.3. The Contractor shall provide review of test reports for safety impacts following testing activities.

4.5.3.5.4. The contractor shall provide system safety metrics based on current ICBM policy.

4.5.3.6. The contractor shall, in coordination and cooperation with subsystem contractors as required, provide safety input and participation support to working groups including

Program IPTs

System Safety Groups

Nuclear Surety Working Groups

ICBM POG (Project Officers Working Group)

ICBM Codes Conference

Other conferences and working groups as needed

4.5.3.6.1. Support shall include: (CDRL)

Developing working group Meeting Agendas, Preparing and consolidating Briefing Materials from other

ICBM SPO IPTs, Engineering assessments or answers to assigned ICBM SPO action items

Reporting to the Government via Engineering Assessments for Working Groups

Providing Meeting Minutes to participants

Other tasks as needed

4.5.4. Occupational Safety Program

4.5.4.1. The contractor shall support the ICBM Program Office Ground Safety program. Support includes: (CDRL)

Mishap investigation support IAW Mishap Risk Assessment Report

(MRAR)

Operational safety inspections at government facilities

Operational hazard identification, mitigation and closure IAW System

Safety

Hazard Analysis Report (SSHAR)

Trend Analysis and reporting

Other tasks as needed

4.5.5. Explosive Safety Program

4.5.5.1. The contractor shall support the ICBM Program Office Explosive Safety program. Support includes:

Mishap investigation support IAW Mishap Risk Assessment Report

(MRAR)

Operational safety inspections at government facilities

Operational hazard identification, mitigation and closure IAW System

Safety

Hazard Analysis Report (SSHAR)

Trend Analysis and reporting

HERO Certification process IAW AFI 91-208

Weapons systems electromagnetic compatibility

Manage and collect Explosive Hazard Classification (EHC) and

Explosive Ordnance Disposal (EOD) data

Identification of weapon system changes that affect Class 1 ordnance devices

Other tasks as needed

4.5.6. Accident/Incident Report

4.5.6.1. The contractor shall, with Government oversight, develop and manage a program to prepare and maintain Programmatic Environmental Safety and

Health Evaluation (PESHE) documentation for acquisition programs.

(CDRL)

4.5.6.2. The contractor shall, with Government oversight, develop and manage a program to prepare and maintain an Environmental Health & Safety Plan.

(CDRL)

4.6. Corrosion Support

Corrosion Description

This effort includes Corrosion Prevention and Materials Engineering to support acquisition and sustainment of the fielded weapon system. This entails identifying corrosion affects and potential corrosion, and assisting IPTs to implement corrosion mitigations.

Activities include providing materials engineering review of solicitation documents, program management, and systems engineering processes and documents, developing and maintaining corrosion prevention design considerations, conducting site surveys, and assessing weapon system corrosion trends. (CDRL)

4.6.1. The contractor shall assist the Government in development and management of weapon system Corrosion Prevention and Control Plans.

4.6.2. The contractor shall perform inspections and studies to assess corrosion, corrosion prevention, and material compatibility.

4.6.3. The contractor shall support management of the ICBM Corrosion Prevention

Advisory Board (CPAB).

4.6.4. The contractor shall provide technical corrosion support to IPTs and subsystem contractors by providing oversight of review and reporting on various types of technical data (ie. Technical Orders, drawings, specifications, 202, etc). These reviews generally will be done by subsystem support contractors. These may be by special report or as part of the Systems Integrity Verification (SIV) Process

4.6.5. The contractor shall support technical reviews and report as required on new corrosion prevention and control materials, processes, and technologies.

4.6.6. The contractor shall provide field support for corrosion issues at missile wings as required by IPTs in support of subsystem support contractors.

4.7. Environmental Engineering Support

Environmental Engineering Description

The AF must ensure compliance with applicable AF environmental programs IAW AFPD32-70

Environmental Quality. These environmental programs are identified in applicable regulations including:

AFI 32-7040 Air Quality Compliance

AFI 32-7041 Water Quality Compliance

AFI 32-7042 Solid And Hazardous Waste Compliance

AFI 32-7047 Environmental Compliance Tracking and Reporting

AFI 32-7061 The Environmental Impact Analysis Process

AFI 32-7063 Air Installation Compatible Use Zone Program, AFI 32-7064 Integrated Natural Resources Management

AFI 32-7065 Cultural Resources Management Program

AFI 32-7080 Pollution Prevention Program

AFI 32-7086 Hazardous Materials Management and applicable supplements

Activities include:

Environmental engineering review of solicitation documents

Program management

Systems engineering processes and documents

Developing and maintaining ESOH design considerations, and National Environmental

Policy Act (NEPA) and Executive Order (EO) 12114 compliance schedules

Hazardous materials management tracking

Pollution Prevention requirements

Assessing Environmental regulatory impacts to the full lifecycle of the system including system’s supportability and disposal

Additionally includes support of Little Mountain and SMIC environmental oversight inspections.

4.7.1. General Requirements

4.7.1.1. The contractor shall provide technical support for environmental compliance by reviewing and reporting on various types of technical data,

ie. Technical Orders, drawings, specifications, etc.

4.7.2. Weapon System Pollution Prevention Program

4.7.2.1. The contractor shall assist the Government in oversight and management of a weapon system Pollution Prevention Program IAW AFI 32-7080, supporting both acquisition and sustainment programs.

4.7.2.2. The contractor shall provide pollution prevention support and technical reviews of new materials, processes, and technologies. (CDRL)

4.7.2.3. The contractor shall submit Pollution Incident Report when applicable.

(CDRL)

4.7.3. Environmental Compliance Program

4.7.3.1. The contractor shall assist the Government in execution of an

Environmental Compliance Program to assess environmental compliance of assigned activities.

4.7.3.2. The contractor shall perform tasks including conducting periodic inspections of processes, documenting findings, and managing corrective actions IAW with the following: (CDRL)

Environmental Compliance Assessment and Management Program

(ECAMP) Action Plan Report

Environmental Project Planning Schedule (PPS)

Environmental Permits and Contractor’s Corrective Action Plans at

Little Mountain, SMIC and other government locations

4.7.4. National Environmental Policy Act (NEPA)

4.7.4.1. The contractor shall assist the Government in developing and managing

NEPA compliance for the weapon system.

4.7.5. Hazardous Materials Management Program (HMMP)

4.7.5.1. The contractor shall assist the Government in developing and managing a weapon system HMMP Plan IAW AFI 32-7086 for both acquisition and sustainment programs.

4.7.5.2. The contractor shall provide hazardous materials support and technical reviews of new materials, processes, and technologies IAW: (CDRL)

Operating Procedures for Hazardous Materials

Hazard Assessment Test Report

Polychlorinated Biphenyl Risk Assessment

Chemical Safety Program Plan

Chemical Accident or Incident Report

Threat Hazard Assessment

4.7.6. Demilitarization and Disposal Plan

4.7.6.1. The contractor shall assist the Government in development, oversight, and management of Demilitarization and Disposal Plan documentation for acquisition and sustainment programs. (CDRL)

4.8. Systems Security Support

Systems Security Description

Security Engineering applies scientific and engineering principles to identify programs’ security vulnerabilities and threats, and minimize or contain associated risks (MIL HDBK-1785; System

Security Engineering Program Management Requirements). System Security Engineering analysis results are documented and captured in the Program Protection Plans which is submitted at each technical review and audit, and incorporated into the technical review assessment criteria as part of functional, allocated, and product baselines

4.8.1. Systems Security Requirements

4.8.1.1. The contractor shall assist the government in establishing and maintaining a comprehensive security program for all acquisition and sustainment programs throughout the system lifecycle.

4.8.1.2. TSN and Criticality Analysis (Testing, evaluation and analysis of vulnerability assessments for CPI and Critical components (e.g. Software, Hardware, Firmware, supply chain, etc) using different methods and techniques as required.)

4.8.1.3. The contractor shall identify and analyze programs’ CPI and critical components (Criticality Analysis).

4.8.1.4. The contractor shall request, review, and analyze programs’ vulnerability assessments.

4.8.1.5. The contractor shall request, review, and analyze programs’ threat assessments.

4.8.1.6. The contractor shall conduct Risk, trade-off, and cost-benefit analyses.

4.8.1.7. The contractor shall design and integrate system security protection and countermeasures. (CDRL)

4.8.1.8. The contractor shall develop, review, and manage Security Classification

Guides. (CDRL)

4.8.1.9. The contractor shall integrate, consolidate, incorporate, and streamline strategies.

4.8.1.10. The contractor shall manage and distribute assigned SCGs, including rewriting, editing, etc. (CDRL)

4.8.1.11. The contractor shall ensure Systems Security Requirements are accounted for in the Supply Chain Risk Management (SCRM) process.

4.8.1.12. The contractor shall perform damage assessments.

4.8.1.13. The contractor shall recommend and review security related documentation, such as: (CDRL)

PPP

Anti-Tamper Plan

Memorandum of Agreement

Trusted System Network Plan

Counterfeit Prevention Plan

Cybersecurity Strategy

Product Assurance and Material Control Process (Authenticity verification techniques, Storage, Marking, Handling, Shipping etc.)

Security Classification Guide

Program Protection Implementation Plan (PPIP)

Solicitations

Contract Data Requirement Lists (CDRLs)

RFP

SOW/PWS

Program Protection Surveys (PPSs)

TEMPEST

Test and Evaluation documents (TEMP, DT&E, OT&E, modeling & simulations testing, LFT&E, family of testing interoperability, integration test, etc.)

Protection requirements contained in System Security Concepts (SSC), Initial Capabilities Documents (ICDs), Capabilities Development

Documents (CDDs), Capabilities Production Documents (CPDs), Modification Proposals, and other requirements documentation

Etc.

4.8.2. Program Protection Planning

4.8.2.1. The contractor shall support programs in management of assigned

Program Protection Planning IAW AFPAM 63-113.

4.8.2.2. The contractor shall support government in the development and implementation of System Security/Program Protection related processes and tools to address and identify CPI, Mission critical functions, and critical components.

4.8.2.3. The contractor shall identify and analyze CPI and CC Security threat and vulnerability assessment risks, risk mitigation and protection measures, and assist in their implementation as required.

4.8.2.4. The contractor shall develop intuitive database(s) for tracking and management of identified security engineering activites and mitigations as required.

5. TEST AND ASSESSMENT SUPPORT SECTION

5.1. Section-Level Requirements

5.1.1. All requirements shall be performed in cooperation and coordination with the cognizant government personnel.

5.1.2. The contractor shall provide programmatic support to PMs in the Test and

Assessment section as needed, including organic workload support through 206 processing in G04L, CCaR PR and Form 9 tracking and processing, and ABSS access to ensure full utilization of CCaR is available.

5.1.2.1. The contractor shall adapt to new systems and processes as changes are made to methods of reporting.

5.2. Operational Test Launch (OTL) Support

OTL Description

The OTL team is responsible for coordinating with subsystem contractors to perform in-depth review of all available missile and component processing, build, and test data. The team provides predictions of flight performance and support launch planning, integration, and logistic activities.

The OTL team is also responsible for flight night and post-flight analysis and logistics support.

5.2.1. The contractor shall provide engineering support to range support planning and analysis activities. Contractor will provide support and documentation for flight

“Associated Operations.”

5.2.2. Prior to flights, the contractor shall coordinate with subsystem contractors to perform an in-depth review of all available missile and component processing, build, and test data.

5.2.2.1. The contractor shall provide predictions of flight performance and support launch planning, integration, and logistic activities.

5.2.3. The contractor shall interface with other contractors providing support to Air Force

Nuclear Weapon Center, ICBM Systems Directorate, and Air Force Global Strike

Command (AFGSC) for operational flight test.

5.2.4. The contractor shall interface with other contractors to provide current information on all missiles to enable selection of missiles for developmental and operational testing.

5.2.5. The contractor shall provide pre-flight engineering support including data…