ISC2.0 PWS_ATTACH 4_MMIII INTEG v1.15 for DRFP.docx

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

DISCLAIMER: The requirements and structure of the ISC as expressed in this document are subject to change based on market research, feedback, and further refinement of requirements.

Contents

1.0 MMIII Integration Branch support (NIAI)

1.1. ICBM Integration Branch Description

To be added

1.2. Branch Structure

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

1.2.1. Leadership

To be added

1.2.2. IPT Participation

To be added

1.3. Objectives and Key Results (OKRs)

To be added

2.0 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 Government PM 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

3.0 Data Management Section (NIAID)

3.1. Data Management Section Description

The Data Management Section is responsible for managing and maintaining the technical baseline of the MMIII weapon system. Specifically, the Technical Order Management Agency (TOMA), Data Management Office (DMO), Configuration Management Office (CMO), and Systems Engineering (Risk, MBSE, System Requirements Analysis (SRA) all reside in NIAID.

3.2. Data Management Organization (DMO)

3.2.1. 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.2.2. DMO Requirements

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

3.2.2.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.2.3. 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.2.3.1. The contractor shall utilize the current DMSOR for managing data.

3.2.3.2. The contractor shall assist in managing data deliverables received by the DMO. (The government will manage ISC data requirements and deliverables.)

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

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

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

3.2.3.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.3. Configuration Management (CM)

3.3.1. 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)

· CSA is the ability to provide accurate, timely information concerning a product and its configuration information throughout the product lifecycle.

· 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.3.2. CM Requirements

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

This support shall include development and/or reviewing of the following documents:

· 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.3.2.2. 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.3.2.3. The contractor shall review ECPs for classification of change (Class I/Class II) and impacts to the technical engineering baseline.

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

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

3.3.2.4. 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.3.2.5. The contractor shall develop and maintain AF drawings and models IAW AF policy and ASME Y14 series standards.

3.3.2.6. 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.3.3. 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.3.3.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.3.3.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.3.3.3. Contractor shall review 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.4. Interface Control

3.4.1. Interface Control Description

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.4.2. Interface Control Requirements

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

3.4.2.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.4.2.2.1. The contractor shall ensure changes are properly coordinated IAW applicable regulations/processes.

3.4.2.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.4.2.4. The contractor shall participate as a member of the Interface Control Working Group (ICWG).

3.4.2.4.1. The contractor shall provide Contract Engineering support to the ICWG chairperson (Government Chief Engineer)

3.4.2.4.2. The contractor shall assume collateral responsibilities with the Government to accomplish interface management.

3.4.2.5. 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.5. Systems Engineering (SE)

3.5.1. The contractor shall perform appropriate SE technical and technical management processes (e.g. 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.) in support of acquisition and sustainment processes (e.g. Materiel Solution Analysis, Technology Maturation & Risk Reduction, Engineering & Manufacturing Development, Production & Deployment, Operation & Support, etc.)

3.5.2. The contractor shall plan and execute technical reviews and assessments (e.g. System Requirements Review, Technology Readiness Assessment, etc.) and develop documentation (e.g., Systems Engineering Plan, Risk Management Plan) inherent to the activities and processes listed above

3.5.3. The contractor shall provide inputs and administrative support to the OBD, SEP, RMP

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

3.6. Risk Management

3.6.1. Risk Management Description

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.6.2. Risk Management Requirements

3.6.2.1. The contractor shall perform and support execution of the MMIII Risk Management process

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

3.6.2.3. The contractor shall maintain the government-designated Risk Management Tool (database)

3.6.2.3.1. The contractor shall assist in data entry

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

3.6.2.4. The contractor shall publish a Risk Management Book

3.6.2.5. The contractor shall provide administrative support for Risk Management Boards, IPT Detailed Risk Reviews, and other Risk Management-related meetings

3.6.2.6. The contractor shall support IPT risk integrators

3.6.2.7. The contractor shall develop, maintain, and update program Risk Management Plans (RMPs)

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

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

3.6.2.10. The contractor shall analyze prime and subcontractor risk management processes

3.7. Model Based Systems Engineering (MBSE) Support

3.7.1. MBSE Support Description

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 MMIII system architecture model will be under Government configuration management oversight as part of the weapon system technical baseline.

3.7.2. MBSE Support Requirements

3.7.2.1. The Contractor shall develop and deliver MBSE system architecture models for the MMIII system

3.7.2.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.

3.7.2.3. The Contractor shall provide MBSE system architecture model elements to other Government-designated contractors

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

3.7.2.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.7.2.6. The contractor shall support development and inclusion of SCSI, CSC, and lower level models into the MMIII system architecture model.

4.0 Specialty Engineering Section (NIAIS)

4.1 Specialty Engineering Section Description

To be added

4.2. Section-Level Requirements

4.2.1. System Integrity Verification (SIV) team - The contractor shall support the ICBM SIV team by providing nuclear surety support and monitoring for compliance with applicable AFI 91 series policies.

4.2.2. The contractor shall review for surety impacts:

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

· TO data produced by ICBM modification programs

· Field or SPO generated -107 ETAR requests per TO 00-25-107

· Depot generated AFMC IMT/Form 202 requests

· Field generated -107 Maintenance Assistance Requests (MAR) requests per TO 00-25-107

· Depot generated AFMC IMT/Form 202 requests

· Test Directives, Test Plans and engineering procedures developed in support of depot and operational test and maintenance projects

4.2.3. The contractor shall participate in ICBMSD data calls as SMEs to verify programs have correct level of specialty requirements

4.3. Nuclear Surety Support

4.3.1. 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 Technical Orders and OPCERT/DECERT Technical Orders procedures for ICBM Nuclear Critical Components according to Technical Manual Contract Requirements (TMCR 86-01).

4.3.2. Nuclear Surety General Requirements

4.3.2.1. The contractor shall integrate nuclear surety requirements into the ICBM System Engineering process under direction of the government.

4.3.2.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.2.3. The contractor shall support ICBMSD in maintaining the nuclear certification program IAW AFI 63-125

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

4.3.2.5. The contractor shall assist AF acquisition PMs in tailoring requirements 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.2.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.7. The contractor shall review, provide assessment, and develop deliverables when directed, 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 the 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:

· 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.3. 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

· Other working groups focused on nuclear surety specialty areas such as Targeting, Physical Security, etc.

· Lead Project Office (LPO) meeting and working groups

· ICBM Codes Conference

4.3.4.3.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.4. 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.5. The contractor shall provide nuclear surety support for assessing new acquisitions as well as existing systems/subsystems

4.3.4.5.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.5.2. The contractor shall identify applicable DoD and AFI 91-series tailored requirements for incorporation into the new acquisition

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

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

4.3.4.5.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

4.4.1. 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.2. NH&S Requirements

4.4.2.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.2. The contractor shall coordinate with and consolidate input from subsystem contractors, as required by the individual items, to deliver these essential products:

· 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:

· Updates to bring out-of-date HDM or DAR data into agreement with current configuration

· Updates necessitated by configuration changes made by any modification or replacement program

· Updates necessitated by configuration changes made via drawing changes

· Input to ICBM Long Range Planning (ILRP), OPLAN 8044

· Hardness maintenance cost/benefit analysis

4.4.3. Hardness Surveillance Assessment

4.4.3.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.3.2. In addition, the contractor shall consolidate subsystem inputs into required deliverable reports such as the WSER.

4.4.4. Hardness Assurance Assessment

4.4.4.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.5. Hardness Maintenance

4.4.5.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.5.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.

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

4.5. System Safety Support

4.5.1. System Safety Description

To be added

4.5.2. System Safety General Requirements

4.5.2.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.2.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-882D, AFPD 91-2, AFI 91-202, AFI 91-204 and AFMAN 91-221 Air Force policies.

4.5.2.3. The contractor shall support the ICBM System Integrity Verification (SIV) team by providing system safety, ground safety, and weapons safety support and monitoring for compliance of applicable AFI 91 series policies.

4.5.3. Deliverables Support

4.5.3.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

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

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

4.5.3.4. The contractor shall support the review of:

· ICBM TOs, drawing and specification changes produced by field units, IPTs, AFGLSC, ICBM Depot organizations, and/or subsystem contractors

· TO data produced by ICBM modification programs

· Field or SPO generated -107 ETAR requests per TO 00-25-107

· Depot generated AFMC IMT/Form 202 requests

· Field generated -107 Maintenance Assistance Requests (MAR) requests per TO 00-25-107

· Test Directives, Test Plans and Engineering Procedures developed in support of depot and operational test and maintenance projects

4.5.4. Safety Support

4.5.4.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.4.1.1. 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 (The actions will be used to develop ICBM trend data to identify and correct problems before they occur/reoccur.)

4.5.4.2. The contractor shall, in coordination and cooperation with subsystem contractors as required, provide safety support to Special ICBM test and maintenance programs such as Rivet MILE, HSEP, and SELM tests or other special test or maintenance action required in the operational ICBM fleet.

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

4.5.4.3. The contractor shall, in coordination and cooperation with subsystem contractors as required, provide safety support to working groups, including Program IPTs, System Safety Groups, ICBM POG (Project Officers Working Group), ICBM Codes Conference, and other conferences and working groups as needed.

4.5.4.3.1. Support shall include:

· 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.

4.5.5. Ground Safety Program

4.5.5.1. The contractor shall support the ICBM Program Office Ground Safety program.

4.5.5.2. This support shall include:

· 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

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.

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

4.6. Corrosion Prevention

4.6.1. Corrosion Support 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.

4.6.1.2. 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.

4.6.2. Corrosion Support Requirements

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

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

4.6.2.3. The contractor shall support management of the ICBM Corrosion Prevention Advisory Board (CPAB).

4.6.2.4. The contractor shall provide technical corrosion support to IPTs and subsystem contractors by providing oversight review and reporting on various types of technical data (e.g. 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.2.5. The contractor shall support technical reviews and report as required on new corrosion prevention and control materials, processes, and technologies.

4.6.2.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

4.7.1. 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.2. Environmental Engineering Requirements

4.7.2.1. The contractor shall provide technical support for environmental compliance by reviewing and reporting on various types of technical data (e.g. TOs, drawings, specifications, etc.). Reviews may be by special report or as part of the SIV Process.

4.7.2.2. The contractor shall assist the Government in developing and managing National Environmental Policy Act (NEPA) compliance for the weapon system.

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

4.7.3. Weapon System Pollution Prevention Program

4.7.3.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.3.2. The contractor shall provide pollution prevention support and technical reviews of new materials, processes, and technologies.

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

4.7.4. Environmental Compliance Program

4.7.4.1. The contractor shall assist the Government in execution of an Environmental Compliance Program to assess environmental compliance of assigned activities.

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

· 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.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:

· 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.8. Systems Security Support

4.8.1. 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.2. Systems Security Requirements

4.8.2.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.2.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.2.3. The contractor shall identify and analyze programs’ CPI and critical components (Criticality Analysis)

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

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

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

4.8.2.7. The contractor shall design and integrate system security protection and countermeasures

4.8.2.8. The contractor shall develop, review, and manage Security Classification Guides

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

4.8.2.10. The contractor shall manage and distribute assigned SCGs, including rewriting, editing, etc.

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

4.8.2.12. The contractor shall perform damage assessments

4.8.2.13. The contractor shall recommend and review security related documentation, such as:

· 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.3. Program Protection Planning

4.8.3.1. The contractor shall support programs in management of assigned Program Protection Planning IAW AFPAM 63-113.

4.8.3.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.3.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.3.4. The contractor shall develop intuitive database(s) for tracking and management of identified security engineering activities and mitigations as required.

5.0. TEST AND ASSESSMENT SUPPORT SECTION (NIAIT)

5.1. Test and Assessment Description

To be added

5.2. Section-Level Requirements

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

5.2.2. The contractor shall provide programmatic support to PMs in the Test and Assessment section as needed to include 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. Additional systems and reporting may be added as changes are made to the methods of reporting.

5.3. Operational Test Launch Support

5.3.1. Operational Test Launch Description

The Operational Test Launch (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.3.2. OTL Requirements

5.3.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.3.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.3.2.2.1. The contractor shall provide predictions of flight performance and support launch planning, integration, and logistic activities.

5.3.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.3.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.3.2.5. The contractor shall provide pre-flight engineering support including data analysis, logistics, presentation creation, meeting support, etc. Meetings and associated presentations include:

· T-30 Day Preflight Review

· T-7 Day Preflight Review

· Test Readiness Review Board

· Confidence and Range Checks

· Other pre-flight meetings as required

5.3.2.6. The contractor shall maintain expertise in areas of ICBM operations necessary to, but not limited to evaluate flight performance, perform detailed analyses, assess flight anomalies (including their impact on weapon system reliability), and identify/recommend corrective actions.

5.3.2.7. The contractor shall obtain binary telemetry data from MMIII test flights

5.3.2.7.1. The contractor shall process data to determine performance and identify trends and anomalies

5.3.2.7.2. The contractor shall incorporate data into an overall ICBM database.

5.3.2.7.3. The contractor shall maintain existing capabilities to display flight data and video at/near Hill AFB live during launches.

5.3.2.8. The contractor shall reduce flight data and evaluate system-level performance using models such as: Earth Coordinates, Aerodynamics, Missile Separation, Gravity, Post Boost Reentry Drag, Structural Dynamics, Atmosphere, Chaff Deployment, Propellant Residual, Climatology, RV Reentry, Boost Steering, Propulsion, IM-Flight, Coordinate Systems, Mass Properties, Control Systems, Guidance Computer, etc.

5.3.2.8.1. If model results differ from actual performance and mass properties, the contractor shall evaluate the flight to determine whether differences lie with flight performance anomalies or inaccuracies in models.

5.3.2.8.2. After the flight, the contractor shall publish a performance report and update models if necessary.

5.3.2.9. The contractor shall provide post-flight engineering support including data analysis, logistics, presentation creation, meeting support, etc. Meetings and associated presentations include:

· Post Flight “Hot Wash” discussions

· Assessment Integration Meetings

· Performance Analysis Reviews

· Reliability Scoring Panels

· Data Reviews

· Accuracy Working Groups

· Other post-flight meetings as required

5.3.2.10. Using government-directed data sources, the contractor shall provide flight-related documentation such as:

· Pool of Fielded Assets (with evaluation of all missiles which make up the wing or group from which the sortie/flight asset will be selected)

· Pre-Flight Configuration Certifications

· Pre-Launch Processing Report

· White Papers on Component Replacement Requests (CRR), Requests for Guidance (RFG), Waiver Requests (WR), Special Request (SR), and other issues

· Quick-Look Flight Performance Reports

· Post Flight Performance Reports

· Etc.

5.4. Weapon System Assessment Support

5.4.1. Weapon System Assessment Description

The Weapon System Assessment (WSA) Team is directly responsible for two of the KPPs: Reliability and Availability. Under this function, the WSA Team receives input for management decisions concerning actions required to maintain system operational readiness. Subsystem contractors will provide assessment of subsystem areas in coordination with Government counterparts and provide assessment products to the WSA Team on a schedule coordinated to meet system reporting requirements.

5.4.2. Weapon System Assessment Requirements

5.4.2.1. The contractor shall support the Weapon System Assessment Team.

5.4.2.2. The contractor shall develop, maintain, update, and coordinate the MMIII Weapon System Effectiveness Report (WSER).

5.4.2.3. The contractor shall, in coordination with the subsystem contractors, consolidate the various assessment reports and perform weapon system-level assessment to produce the WSER and other system assessment products as required.

5.4.2.4. The contractor shall provide reliability, availability, and maintainability estimates.

5.4.2.4.1. The contractor shall validate suspected performance trends and determine force impacts by conducting statistical and engineering analysis at the system-level and/or verifying any IPT/subsystem-level analysis.

5.4.2.5. The contractor shall maintain/update the MMIII Reliability Database.

5.4.2.6. The contractor shall maintain/update (e.g. ensure functionality, ensure parameters are applicable, make necessary changes, etc.) the government-designated database and evaluation system which records all parameters that are out of specification, out of family, or unusual when compared with expected or modeled performance at the system or component level.

5.4.2.7. The contractor shall evaluate the adequacy of subsystem aging surveillance plans in cooperation and coordination with the WSA Team Government Lead.

5.4.2.7.1. The contractor shall perform analysis on subsystems/components to determine life expectancy and support proactive repair and procurement decisions.

5.4.2.8. The contractor shall…