Draft RFP Package - TO 4 MMIII Integration Support PWS.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

1. MMIII Integration ORGANIZATION ICBM Integration Organization Description The ICBM Integration organization provides specialty engineering and technical support to MMIII acquisition and sustainment programs/projects as well as select functional areas of support to GBSD Enterprise. It falls under the MMIII SPO and consists of three sections: Data Management, Specialty Engineering, and Test and Assessment.

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 personnel participate in IPT(s) per the IPTs’ need for High-Demand/Low-Density (HD/LD) and other specialty services provided by the Integration organization (e.g. Test, Nuclear Surety, Hardness, etc.). Integration personnel are commonly assigned to multiple IPTs. When assigned to multiple IPTs, their time is aligned with priorities set by Leadership.

Although the Integration organization falls under the MMIII SPO, it 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, the Technical Order Management Agency (TOMA) and Diminishing Manufacturing Sources and Material Shortages (DMSMS).

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 organization’s responsibilities is the Alternate Lead Developmental Test Organization (Alt-LDTO).

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 Government Program Manager (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 FAR 7.3

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

2.7. Meeting Support - Appropriate functional contractor personnel shall participate in, contribute to, and provide technical and programmatic expertise for meetings, reviews, and boards involving the program, IAW the Basic PWS paragraph 3.9.

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 Office (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. (31000B)

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. (31000B)

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) (81875)

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

· Engineering Change Proposals (ECPs) (80750)

· Engineering Orders (EOs) (81018)

· Specification Change Notices (SCNs) (81401C)

· Product Engineering design data and associated lists (80776B)

· Interface Control Documents (ICDs) (81248B)

· Request for Variance (RFV) (80640)

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

3.2.1.3. The contractor shall provide support to the Government Technical Evaluation 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 (80750)

· 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. (31000B)

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 (81248B)

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 all stakeholders are kept appropriately informed 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: (82009A)

· 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.). (81785A, 81808)

3.3.1.3. The contractor shall provide inputs and administrative support to the Operational Baseline Document (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 WS 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. (81808, 967)

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). (81808)

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 contractor shall analyze prime and subcontractor risk management processes

3.3.3. Model Based Systems Engineering (MBSE) Support (81938) 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 WS technical baseline.

The MMIII Integration organization is responsible for SySML system modeling of MMIII at the system level down to the Configured Item (CI). This is characterized as a “top-down” approach to support cross-subsystem integration. The Integration organization will also integrate SySML modeling accomplished by the MMIII Acquisition and Sustainment organizations, ISC 2.0, and/or Subsystem Support Contractors as required (“bottom-up”, i.e. within a current MMIII CI) into the base-lined MMIII system model.

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

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. (31000B)

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

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.

3.4. Diminishing Manufacturing Sources and Material Shortages (DMSMS) - SPO All DMSMS activities for the MMIII Weapon System are directed, controlled and managed by the PM in the MMIII SPO and supported by the 414 SCMS, the ISC Contractor, and the Subsystem Support Contractors. Specific support for Budget Code 8 items are directed by the 414 SCMS. CDRL items developed for the 414 SCMS will be included in the report provided to the MMIII SPO DMSMS PM.

3.4.1. The contractor shall use the AF DMSMS predictive tool (currently the Advanced Component Obsolescence Management (AVCOM) tool), and other government-selected obsolescence databases when deemed necessary by the government.

3.4.1.1. The contractor shall perform health analysis on the obsolescence flagged item(s) as harvested from AVCOM, plus other items, as directed and prioritized by the SPO DMSMS PM, in the DMSMS database.

3.4.2. The contractor shall provide monthly reports to the DMSMS PM identifying those potential DMSMS parts that may pose a risk to ICBM WS maintainability.

3.4.3. The contractor shall provide a monthly report of recommended solutions. (CDRL)

3.4.4. The contractor shall perform up-front data mining efforts of the drawings located in JEDMICS for the selected National Stock Numbers (NSNs)/Part Numbers (PNs) and/or Technical Orders (TOs), as directed by the SPO DMSMS PM.

3.4.5. The contractor shall support and provide data for Applications, Programs and Indentures (API) file maintenance, and establishing and maintaining a process to validate the API export file against any existing API full range listing from the D200F database to ensure proper updating of the D200F database. (CDRL)

3.4.6. The contractor shall deliver errata documents to the SPO DMSMS PM as required. (CDRL)

3.4.7. The contractor shall provide Cost Avoidance and Return on Investment (ROI) information. (82161)

3.4.8. The contractor shall attend required conferences to support the DMSMS Program as directed by the Government.

3.4.9. The contractor shall prepare and deliver a monthly DMSMS Program Status Report identifying the progress of the ICBM DMSMS effort. This report shall include status of the following areas: (80368A)

· Analysis and Resolution Progress

· Parts Obsolescence Flagged Solutions Delivered

· Special A&R research tasking line items delivered, as required

· AFMC Form 252s generated, as available

· Number of 252 line item changes (including those developed for the 414 SCMS)

· List of Technical Orders linked to the 252 line item changes

· Program Cost Avoidance Computations

· Program ROI Computations

· API Information, as available, for parts loaded in AVCOM

· Errata Delivered

· Obsolete Errata Delivered and Removed (a.k.a. “burndown”), as required

· Data Mining Program Status, as available

· Data Mining Line Items Delivered

· List of Technical Orders linked to the Data Mining line items

· Mining and Loading Page Production Status (including backlog for previous years)

3.4.10. The contractor shall prepare and deliver an annual DMSMS Program Status Report summarizing the annual deliverables as outlined in the monthly status reports IAW para 3.4.9. above, due at the end of each period of performance. (80368A)

3.4.11. The contractor shall prepare and deliver a Contract Summary Report for DMSMS Program Status at the end of each period of performance, identifying the progress of the ICBM DMSMS effort, to the SPO DMSMS PM. (80368A)

3.4.12. The contractor shall assemble a list of agreed upon Illustrated Parts Breakdown Technical Orders from the MM III ICBM WS as a roadmap, and deliver the roadmap to the SPO DMSMS PM. (82297)

3.4.12.1. The contactor shall mine data IAW the roadmap and deliver data packages to the contractor managing the parts obsolescence database for SCM, via the Strategic Alternate Sourcing Program Office (SASPO), Tinker AFB, OK for loading into the AVCOM tool, at the direction of the SPO DMSMS PM. (82297)

3.4.12.2. The contractor shall ensure all data is the most current data available before beginning the mining effort.

3.4.12.3. The contractor shall ensure all previously mined data is the most current before sending to the SASPO for loading.

3.4.12.4. The contractor shall make any revisions, if necessary, before sending the mined data for loading into the AF DMSMS predictive tool (currently AVCOM).

3.5. DMSMS - 414th Supply Chain Management Squadron (414 SCMS) DMSMS Description This PWS section defines the effort required to support the 414 SCMS Manager for DMSMS. This DMSMS effort will involve technical support to extract and interpret data from technical data sources (Technical Order Libraries & Joint Engineering Data Management Information & Control System (JEDMICS)) in order to research and collect DMSMS related data to be furnished to the government.

Funding for the 414th DMSMS Program currently utilizes CSAG-S dollars, which by law limits efforts to budget code 8 items only. However, any indentured parts/subcomponents under a Budget Code 8 assembly can and will be supported by the 414th’s DMSMS program, regardless of their budget code (including non-stock listed items which have no budget code). Any “stand-alone” or non-indentured Budget Code 9 items will continue to be supported by the ICBMSD DMSMS program.

The roles required to satisfy the requirements identified in this SOW will range from Logistic Support Specialists to Engineers.

3.5.1. The contractor shall provide monthly reports to 414 SCMS DMSMS PM identifying potential DMSMS parts that may pose a risk to ICBM WS maintainability. (81995)

3.5.2. The contractor shall use the AF DMSMS predictive tool (currently AVCOM), and other government-selected obsolescence databases when deemed necessary by the government.

3.5.2.1. The contractor shall perform health analysis on the obsolescence flagged item(s) as harvested from AVCOM, plus other items, as directed and prioritized by the 414 SCMS PM and coordinated with the MMIII SPO system engineering PM, in the DMSMS database.

3.5.2.2. The contractor shall provide a monthly report of recommended solutions. (CDRL)

3.5.2.3. The contractor shall limit their efforts to budget code “8” items and any/all of their subcomponents only. (CDRL)

3.5.3. The contractor shall perform up-front data mining efforts of the drawings as located in JEDMICS for the selected NSNs/PNs and/or Technical Orders, as determined by the 414 SCMS DMSMS PM and coordinated through the MMIII SPO system engineering PM.

3.5.3.1. The contractor shall limit their efforts to budget code “8” items and any/all of their subcomponents only.

3.5.4. The contractor shall support and provide data for API file maintenance, and establishing and maintaining a process to validate the API export file against any existing API full range listing from the D200F database to ensure proper updating of the D200F database. (CDRL)

3.5.5. The contractor shall deliver errata documents to the 414 SCMS DMSMS PM as required. (CDRL)

3.5.6. The contractor shall provide Cost Avoidance and ROI information. (82161)

3.5.7. The contractor shall attend required conferences to support the DMSMS Program.

3.5.7.1. The Contractor shall provide no more than the noted number of attendees, unless otherwise directed, for the annual conferences listed:

· DoD DMSMS Conference (one attendee)

· AVCOM Obsolescence Working Group Meeting (two attendees)

3.5.7.2. Approval from the 414 SCMS DMSMS PM shall be required prior to travel to each conference.

3.5.8. The contractor shall prepare and deliver a monthly DMSMS Program Status Report identifying the progress of the ICBM DMSMS effort. This report shall include status of the following areas: (80368A)

· Analysis and Resolution Progress

· Parts Obsolescence Flagged Solutions Delivered

· Special A&R research tasking line items delivered, as required

· AFMC Form 252s generated, as available

· Number of 252 line item changes (414 SCMS only)

· List of Technical Orders linked to the 252 line item changes

· Program Cost Avoidance Computations

· Program ROI Computations

· API Information, as available, for parts loaded in AVCOM

· Errata Delivered

· Obsolete Errata Delivered and Removed (a.k.a. “burndown”), as required

· Data Mining Program Status, as available

· Data Mining Line Items Delivered

· List of Technical Orders linked to the Data Mining line items

· Mining and Loading Page Production Status (including backlog for previous years)

3.5.9. The contractor shall prepare and deliver an annual DMSMS Program Status Report summarizing the annual deliverables as outlined in the monthly status reports IAW paragraph 3.5.8. above, due at the end of each period of performance. (80368A)

3.5.10. The contractor shall prepare and deliver a Contract Summary Report for DMSMS Program Status at the end of each period of performance, identifying the progress of the ICBM DMSMS effort, to the 414 SCMS PM. (80368A)

3.5.11. The contractor shall assemble a list of agreed upon Illustrated Parts Breakdown Technical Orders from the MM III ICBM WS as a roadmap, and deliver the roadmap to the 414 SCMS DMSMS PM. (82297)

3.5.11.1. The Contactor shall mine data IAW the roadmap and deliver data packages to the contractor managing the parts obsolescence database for SCM via the SASPO at Tinker AFB, OK for loading into the AVCOM tool, at the direction of the 414 SCMS DMSMS PM and in coordination with the MMIII SPO System Engineering PM. (82297)

3.5.11.2. The contractor shall ensure all data is the most current data available before beginning the mining effort.

3.5.11.3. The contractor shall ensure all previously mined data is the most current before sending to the SASPO for loading.

3.5.11.4. The contractor shall make any revisions, if necessary, before sending the mined data for loading into the AF DMSMS predictive tool (currently AVCOM).

4. SPECIALTY ENGINEERING SECTION

Specialty Engineering Section Description The Specialty Engineering Section includes Nuclear Surety, Nuclear Hardness and Survivability, System Safety, Corrosion, Environmental Engineering, and Systems Security.

4.1. General

4.1.1. The contractor shall participate in ICBM 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 ICBM 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, System Security, and other specialty engineering areas 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

· Technical Order data produced by ICBM modification programs

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

· Depot generated AFMC IMT/Form 202 requests

· Field generated -107 MAR requests per Technical 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

· Etc.

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, and AFMAN 91-119.

The above policies are tailored for applicability to new or modified ICBM and Airborne 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) (81888B)

· Certification Requirements Plan (CRP) (81409B)

· Nuclear Certification Plan (NCP) (81409B)

· Nuclear Surety Evaluation (NSE) Report (81411A)

· Fault Tree Analysis

· Probabilistic Risk Assessment (81808)

· Unauthorized Launch Studies (81313A)

· Launch Action Studies (81313A)

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

· Safety & Nuclear Surety Technical Memorandum (81065)

· 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 organization 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 the ICBM organization in maintaining the nuclear certification program IAW AFI 63-125

4.3.1.4. The contractor shall support the ICBM organization in achieving and maintaining nuclear certification for ICBM WSs.

4.3.1.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.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) (81888B)

· Certification Requirements Plan (CRP) (81409B)

· Ground Launched Missile Nuclear Safety Analysis Report (NSAR) (81065)

· Nuclear Surety Evaluation (NSE) Report (81411A)

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

· Safety & Nuclear Surety Technical Memorandum (81065)

· 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) (81409B)

· Engineering Evaluation Report (EER) (Nuclear Surety) (81411A)

· Aircraft Nuclear Safety Analysis Report (NSAR) for Flight Safety Analysis & NSAR (272A)

· Software Certification Plan (SCP) (81888B)

· 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 AF 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 AF 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: (81300B)

· 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. The contractor shall provide support IAW the 91-series AFIs for 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 NH&S process is to sustain the capability of the weapon system to operate and carry out its mission in a nuclear environment IAW applicable governing documents and specifications, including:

· DoDI 3150.09, Chemical, Biological, Radiological, and Nuclear (CBRN) Survivability Policy

· AFI 10-2607, Chemical, Biological, Radiological, and Nuclear (CBRN) Survivability

· S-133-128E, System Specification for MMIII

· MIL-STD-1766C, NH&S Program Requirements for ICBM Weapon Systems

· MIL-STD-2169B, High-Altitude Electromagnetic Pulse (HEMP) Environment

· All other applicable Instructions, Standards, Specification, Regulations, Directives, etc.

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, 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. (1766C, 461G)

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. (461G)

4.4.4.3. The contractor shall recommend actions to maintain current WS 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:

· Trade-Off Studies and Analysis (81021)

· NH&S Weapon System Assessment (80266A)

· Survivability Management Status Report Input to WSER (80156B)

· Input to Data Book(s)

· Integrated Nuclear Effects Assessment (80298)

· Subsystem/End Item Specifications (SSS) (81431A)

· System/Subsystem Hardness Requirements & System Requirements Determination (81431A)

· Hardness Data Manual (HDMs) & Design Analysis Report (DAR) Updates to include: (82096)

· 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.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 specific equipment items, subsystems, systems, and support facilities managed by the ICBM organization. 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 (81808)

· System Safety Hazard Analysis Report (SSHAR) (80101C)

· Safety Assessment Reports (SARs) (81065)

· Risk Acceptance Recommendations (81543A)

· Threat Hazard Assessment (81124)

· Briefing Materials (Briefings, Point Papers and White Papers) (81605)

· Safety & Nuclear Technical Memoranda (81411)

· 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) (38804E)

· System Safety Program Plans (81066)

· Hazard Tracking System data (82085)

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

· Hazardous Materials Management Plan (80106C)

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: (81300B)

· 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. (81605)

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 the government’s 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: (81605, 81505)

· 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 Occupational Safety program. Support includes: (81300B, 81841)

· 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: (81300B, 81841, 80931B, 272A, 81066)

· 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. The contractor shall, with Government oversight, develop and manage a program to prepare and maintain PESHE documentation for acquisition programs. (81840)

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