Attachment 21 - ISC2.0 PWS ATO4 MMIII INTEG.pdf

FA8207-20-R-0003 - ISC 2.0

Task Order 4: MMIII Integration PWS

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

INTEGRATION SUPPORT CONTRACT (ISC) 2.0

TASK ORDER 4: MINUTEMAN III (MMIII) INTEGRATION

PERFORMANCE WORK STATEMENT (PWS)

FOR

ICBM ORGANIZATION AT HILL AIR FORCE BASE (AFB)

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

14 OCTOBER 2020

CONTENTS

1.0. MMIII INTEGRATION ORGANIZATION

2.0. GENERAL REQUIREMENTS

3.0. DATA MANAGEMENT SECTION

4.0. SPECIALTY ENGINEERING SECTION…………………………………………….…18

5.0. TEST AND ASSESSMENT SUPPORT SECTION

6.0. ALTERNATE LEAD DEVELOPMENTAL TEST ORGANIZATION (Alt-LDTO)...48

ACRONYM LIST………………………………………………………………………………49

1.0. 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 the Ground Based Strategic Deterrent (GBSD) Enterprise as needed. It falls under MMIII System Program Office (SPO) management and consists of three areas: Data Management, Specialty Engineering, and Test and Assessment.

SPO and Directorate Support Leadership from 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 recommendations from the MMIII Integrated Product Teams (IPTs).

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.

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

Data Deliverables (Contract Data Requirements Lists [CDRLs]) A master list of potential DoD Form 1423s (DD 1423s), Contract Data Requirements Lists, is provided as Section J Attachment 6, Contract Data Requirements Lists (CDRLs).

Due to the quantity and diversity of the programs in the ICBM Organization, the type and magnitude of required support is different for each program. Each program will employ the tasks in this PWS to the extent needed by that program. This also means that data deliverable needs will vary based on the program. To this end, CDRLs are not referenced in this PWS after every paragraph in which they may be required.

CDRLs specifically referenced in this PWS are to be delivered every time the task required by the referenced paragraph is performed (e.g. monthly status reports, training materials, specialty engineering documentation, etc.).

If a program determines that a formal data deliverable is needed for a paragraph without a CDRL reference (e.g. advice, recommendations, analysis reports, etc.), the Government representative will select the appropriate CDRL from the master list and specify the delivery date/address and any other necessary instructions on the DD 1423. Any additional tailoring will also be documented on the DD 1423 at that time. The CDRL number will be incorporated into the associated task assignment (see paragraph 4.9 of the Basic PWS).

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 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 in accordance with (IAW) applicable laws and regulations.

Publications listed within this Task Order PWS are current as of the date of the PWS, but are subject to change at any time. The Contractor shall acquire and follow current versions of laws, regulations, directives, policies, Operating Instructions (OIs), and other applicable publications, unless specifically directed otherwise.

2.6. The Contractor shall NOT perform any Inherently Government Functions as defined in Federal Acquisition Regulation (FAR) 7.503.

2.7. The Contractor shall recommend and incorporate process and resource efficiencies, including application of streamlined Program Management techniques and other industry best practices.

2.8. 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 Basic PWS paragraph 3.9. (CDRLs A002, A003, A004, A059-73)

2.9. Risk Management Framework (RMF) Support

2.9.1. The Contractor shall act as Information System Security Managers (ISSMs) as required (see Air Force (AF) Instruction (AFI) 17-101, Risk Management Framework (RMF) for Air Force Information Technology (IT)).

2.9.1.1. ISSMs shall provide independent assessments as primary cybersecurity technical advisors to the Authorizing Official (AO) for AF Information Technology (IT).

2.9.2. The Contractor shall act as Information System Security Officers (ISSOs) as required (see AFI 17-101).

2.9.2.1. ISSOs shall ensure the appropriate operational security posture is maintained for AF IT under their purview, including activities related to maintaining situational awareness and initiating actions to improve or restore cybersecurity posture.

3.0. 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 (WS). Specifically, the Data Management Office (DMO), Configuration Management Office (CMO), Systems Engineering (Risk, Model Based Systems Engineering (MBSE), System Requirements Analysis (SRA)), and the 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

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 is the central repository for all MMIII- and Contractor-developed data, draft and final versions, Comment Resolution Matrices (CRMs), and official approving/rejecting documents.

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

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

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

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

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

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

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

(Data and processes are expected to transition to an Enterprise Product Lifecycle Management (PLM) system early in the Period of Performance (PoP) of this contract.)

3.1.3. TOMA Support

3.1.3.1. The Contractor shall assist the TOMA in identifying all existing Technical

Order (TO) data from MMIII as well as other Government departments/ agencies.

3.1.3.2. Any TO development for the Government shall be developed to current AF Technical Manual Specifications and Standards (TMSS) or Government-approved Non-Government Specifications (NGS) IAW TO 00-5-3, paragraph 3.3.5.

3.1.3.3. The Contractor shall deliver all other page-based TOs (such as Commercial, Off-the-Shelf (COTS) manuals) required to support all operations IAW Technical Manual Contract Requirement (TMCR) (TM-

86-01). (CDRL A110)

3.1.3.4. The Contractor shall identify, develop, update/maintain, and deliver necessary data, drawings, documentation when required, before and after coding when required, and to perform In-Process Reviews (IPRs) as well as Contractor certification and Government verification. This includes:

• Conference/meeting agendas

• Report/record of meeting minutes

• Technical data assessments as requested

• Preliminary TOs (IAW TO 00-5-3, TO-00-5-1, AF TO System, and

TMCR)

• Manuals (IAW MIL-PRF-32216, MIL-DTL-87929E (USAF), MIL-

DTL-38804D, MIL-DTL-38807)

• Standards (MIL-STD-38784)

• Time Compliance TOs (TCTOs) (TO 00-5-15)

• Any other applicable data, including source data in TO Page

Supplements (TOPS) format

3.1.3.5. The Contractor shall ensure technical publications and TCTO changes resulting from certification and verification efforts for the system and support equipment are updated and finalized prior to formal delivery per the TMCR.

3.1.3.6. The Contractor shall participate in at least two (2) IPRs for draft TO and TCTO deliverables at least 90 days before the start of validation/ verification.

3.1.3.7. The Contractor shall participate in Pre-Publication Reviews (PPRs) and TCTO Pre-Publication Review Groups (PPRGs) after verification to ensure all comments and corrections are incorporated and meet contractual requirements.

3.1.3.8. Data rights shall be in compliance with the Government Rights in Data and Software (GRIDS), where the Government asserts Unlimited Rights, unless otherwise noted as an exception.

3.1.4. Specific Qualifications

3.1.4.1. Contractor personnel assigned to the DMO shall have knowledge and experience in:

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

• Effectively cataloging and acquiring spare/repair parts, support equip, and all classes of supply

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

3.2. Configuration Management (CM)

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

• Configuration identification

• Configuration control

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

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

• Configuration verification and auditing, IAW military and industrial guidance (e.g. MIL- HDBK-61A, EIA-649, EIA 649-1, etc.)

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

• 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 SPO.

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

• Engineering Change Proposals (ECPs) (CDRL A031)

• Engineering Orders (EOs)

• Specification Change Notices (SCNs) (CDRL A030)

• Product Engineering design data and associated lists (CDRL A027)

• Interface Control Documents (ICDs) (CDRL A032)

• Request for Variance (RFV) (CDRL A037)

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

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 (CDRL A059-73)

• 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 technical data and CM status accounting systems.

3.2.1.5. The Contractor shall maintain the technical engineering baseline (CI 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 American Society of Mechanical Engineers (ASME) Y14 series standards.

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 WS, and execute those improvements approved and directed by the Government.

3.2.2. Software CM

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 WS software, software analysis, and integration into the WS, maintaining configuration and Computer Program Identification Number (CPIN) support IAW the ICBM Configuration Management Plan (62-CMP).

3.2.2.2. The Contractor shall ensure CPINs are maintained and current IAW Enhanced Technical Information Management System (ETIMS), and that software is the authorized version IAW Software Version Description

(SVD).

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

• Computer Program End Item Documentation

• Software Requirements Specification (SRS)

• Software Design Description (SDD)

• Software Test Plan (STP)

• Software Test Description (STD)

• Software Test Report (STR)

• Software Product Specification (SPS)

3.2.3. Interface Control

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

3.2.3.1. Interface Control Requirements

3.2.3.1.1. The Contractor, in coordination with the appropriate

Subsystem Contractor(s), shall assist the Government in validating and controlling interface requirements.

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

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

3.2.3.3. The Contractor shall adhere to the guidelines contained in ICBM-HDBK- 02 (which provides guidance and examples of all interface control procedures and policies used since the 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, ICDs, 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.2.4. Specific Qualifications

3.2.4.1. Contractor personnel assigned to CM shall have knowledge and experience in the planning and management of functional, allocated, and product baseline configurations for hardware and software IAW military and industrial guidance (e.g. MIL-HDBK-61A, EIA-649, EIA 649-1), including configuration identification, configuration control, configuration status accounting, and configuration verification and auditing.

3.3. Systems Engineering (SE)

3.3.1. General

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

• Requirements definition and analysis

• Architecture design

• Implementation

• Integration

• Verification and validation

• Transition

• Decision analysis

• Technical planning

• Technical assessment

• Requirements management

• Risk management

• Configuration management

• Technical data management

• Interface management

• Use of requirements management tools

• Etc.

3.3.1.2. The Contractor shall plan and execute technical reviews and assessments (e.g. System Requirements Reviews (SRRs), Technology Readiness Assessments (TRAs), etc.) and develop associated documentation (e.g., Systems Engineering Plans (SEPs), Risk Management Plans (RMPs), etc.).

3.3.1.3. The Contractor shall provide inputs and administrative support to the Operational Baseline Documents (OBDs), SEPs, RMPs, etc.

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 RMPs IAW the “Risk Management

Guide for DoD Acquisition”, AF Pamphlet (AFPAM) 63-128, Integrated Life Cycle Management, 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) and Risk Management working groups (or equivalent), and documenting results

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

3.3.2.5. The Contractor shall provide administrative support for RMBs, IPT

Detailed Risk Reviews, and other Risk Management-related meetings.

(CDRLs A002, A003, A004, A059-73)

3.3.2.6. The Contractor shall support IPT risk integrators.

3.3.2.7. The Contractor shall develop, maintain, and update program RMPs.

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

The MMIII SPO requires MBSE to enable preservation of MMIII technical integrity by making it easier to determine if changes to one MMIII subsystem impact other subsystems.

The Government is responsible for CM oversight of the MMIII system architecture model as part of the WS technical baseline.

The MMIII Integration organization is responsible for System Modeling Language (SySML) system modeling of the 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. (CDRL A059-119)

3.3.3.2. The Contractor shall deliver system architecture models in SySML development tool-native file format, Extensible Markup Language (XML) format, and Hypertext Markup Language (HTML) format, as appropriate.

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 WS in all configurations.

3.3.3.6. The Contractor shall support development and inclusion of Small Computer Standard Interface (SCSI), Computer Software Configuration (CSC), and lower level models into the MMIII system architecture model.

3.3.4. Specific Qualifications

3.3.4.1. Contractor personnel assigned to SE:

• Shall have knowledge and experience in efficiently and effectively delivering SE capability in support of acquisition and sustainment processes

• Shall have knowledge and experience in SE technical and technical management processes in paragraph 3.3.1.1. above

• Shall have knowledge and experience in planning and executing technical reviews and assessments (e.g. SRR, TRA) and documentation development (e.g. SEP, RMP) that are an inherent part of the activities and processes listed above

• A minimum of one (1) Contractor individual shall be an Object Management Group (OMG) Certified Systems Modeling Professional (OCSMP) Model Builder – Advanced certified o One-half of the remaining team-members shall be OCSMP Model

Builder - Intermediate certified o Other team members shall obtain OCSMP Model Builder - Fundamental certification within one (1) year of contract award or employment

• A minimum of one (1) Contractor individual shall be International Council on Systems Engineering (INCOSE) Expert System Engineering Professional (ESEP) certified o One-half of the remaining team-members shall be INCOSE

Certified System Engineering Professional (CSEP) certified o Other team members shall obtain INCOSE Associate System

Engineering Professional (ASEP) certification within one (1) year of contract award or employment

3.3.4.2. Contractor personnel assigned to Risk Management shall have knowledge and experience in:

• Developing, maintaining, and updating program RMPs IAW “Risk

Management Guide for DoD Acquisition”, AFPAM 63-128, and “Air Force Risk Identification, Integration, and Ilities (RI3) Guidebook”

• Facilitating program risk identification, risk analysis, risk handling, and risk monitoring

• Executing program RMBs and risk management working groups (or equivalent), and documenting results.

3.4. Diminishing Manufacturing Sources and Material Shortages (DMSMS) - SPO All DMSMS activities for the MMIII WS are directed, controlled and managed by the PM in the MMIII SPO and supported by the 414 Supply Chain Management Squadron (SCMS), the ISC Contractor, and the Subsystem Support Contractors. Specific support for Budget Code 8 items are directed by the 414 SCMS.

3.4.1. The Contractor shall use the AF DMSMS predictive tool (currently the Avionics 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 potential DMSMS parts that may pose a risk to ICBM WS maintainability. (CDRL A026-2)

3.4.3. The Contractor shall provide a monthly report of recommended solutions. (CDRL A026-2)

3.4.4. The Contractor shall perform up-front data mining efforts of the drawings located in the Joint Engineering Data Management Information and Control System (JEDMICS) for the selected National Stock Numbers (NSNs)/Part Numbers (PNs) and/or 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 A151)

3.4.6. The Contractor shall deliver errata documents to the SPO DMSMS PM as required.

3.4.7. The Contractor shall provide cost avoidance and Return on Investment (ROI) information. (CDRL A152)

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. (CDRL A026-2) This report shall include status of the following areas:

• Analysis and Resolution (A&R) Progress o Parts Obsolescence Flagged Solutions Delivered o Special A&R research tasking line items delivered, as required

• Air Force Materiel Command (AFMC) Form 252s generated, as available o Number of 252 line item changes (including those developed for 414 SCMS) o List of TOs 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 o Data Mining Line Items Delivered o List of TOs linked to the Data Mining line items o 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 year of the contract. (CDRL A026-2)

3.4.11. The Contractor shall prepare and deliver a Contract Summary Report for DMSMS Program status at the end of each PoP, identifying the progress of the ICBM DMSMS effort, to the SPO DMSMS PM. (CDRL A019)

3.4.12. The Contractor shall assemble a list of agreed upon Illustrated Parts Breakdown TOs from the MMIII ICBM WS as a roadmap, and deliver the roadmap to the SPO

DMSMS PM. (CDRL A136)

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 Supply Chain Management (SCM), via the Strategic Alternate Sourcing Program Office (SASPO), Tinker AFB, OK for loading into the AF DMSMS predictive tool, at the direction of the SPO DMSMS PM.

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.

3.4.13. CDRL items developed for the 414 SCMS shall be included in the report provided to the MMIII SPO DMSMS PM.

3.5. DMSMS - 414th SCMS

DMSMS - 414th SCMS 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 (TO libraries and JEDMICS) in order to research and collect DMSMS related data to be furnished to the Government.

Funding for the 414th DMSMS Program currently utilizes Consolidated Sustainment Activity Group (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 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 MMIII SPO DMSMS program.

The roles required to satisfy the requirements identified in this section 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. (CDRL A026-2)

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 SE PM, in the DMSMS database.

3.5.2.2. The Contractor shall provide a monthly report of recommended solutions.

(CDRL A026-2)

3.5.2.3. The Contractor shall limit their efforts to Budget Code 8 items and any/all of their subcomponents only.

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 TOs, as determined by the 414 SCMS DMSMS PM and coordinated through the MMIII SPO SE 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 A151)

3.5.5. The Contractor shall deliver errata documents to the 414 SCMS DMSMS PM as required.

3.5.6. The Contractor shall provide cost avoidance and ROI information. (CDRL A152)

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:

• Department of Defense (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. (CDRL A059-71)

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: (CDRL A026-2)

• Analysis and Resolution Progress o Parts Obsolescence Flagged Solutions Delivered o Special A&R research tasking line items delivered, as required

• AFMC Form 252s generated, as available o Number of 252 line item changes (414 SCMS only) o List of TOs 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 o Data Mining Line Items Delivered o List of TOs linked to the Data Mining line items o 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 year of the contract. (CDRL A026-2)

3.5.10. The Contractor shall prepare and deliver a Contract Summary Report for DMSMS Program status at the end of each PoP, identifying the progress of the ICBM DMSMS effort, to the 414 SCMS PM. (CDRL A019)

3.5.11. The Contractor shall assemble a list of agreed upon Illustrated Parts Breakdown TOs from the MM III ICBM WS as a roadmap, and deliver the roadmap to the 414

SCMS DMSMS PM. (CDRL A136)

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 AF DMSMS predictive tool, at the direction of the 414 SCMS DMSMS PM and in coordination with the MMIII SPO System Engineering PM.

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.

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

(SMEs) to verify future programs have the correct level of Specialty requirements and deliverables.

4.1.2. The Contractor shall participate in ICBM TERBs and CCBs 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 WS documentation.

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

• ICBM TO change recommendations produced by field units, SPO, AF Global

Strike Command (AFGLSC), ICBM Depot organizations, and/or Subsystem Contractors

• TO data produced by ICBM modification programs

• Field or SPO generated -107 Engineering Technical Assistance Requests

(ETARs) per TO 00-25-107

• Depot-generated AFMC Information Management Tool (IMT)/Form 202 requests

• Field generated -107 Maintenance Assistance Requests (MARs) per TO 00-25-

• TCTOs

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

• SE acquisition documentation and program/management plans

• Implementation management plans

• Drawings and EOs

• WS risks

• System safety risk assessments

• ECPs, TERB packages, and CCB packages

• Programmatic Environmental Safety and Occupational Health Evaluations (PESHEs)

• 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 AF Policy Directive (AFPD) 91-1, Nuclear Weapons and Systems Surety, and further detailed in:

• AFI 91-101, Air Force Nuclear Weapons Surety Program

• AFI 91-102, Nuclear Weapon System Safety Studies, Operational Safety Reviews and Safety

Rules

• AFI 91-106, Unauthorized Launch, Threat Mitigation, and Launch Action Studies

• AFI 91-114, Safety Rules for the Intercontinental Ballistic Missile System

• AFI 91-117, Safety Rules for the Airborne Launch Control System

• AF Manual (AFMAN) 91-118, Safety Design and Evaluation Criteria for Nuclear Weapon

Systems

• AFMAN 91-119, Safety Design and Evaluation Criteria for Nuclear Weapon Systems

Software The above policies are tailored for applicability to new (such as GBSD Enterprise acquisitions) or modified ICBM and Airborne Launch Control System (ALCS) (installed in United States Navy (USN) E-6B aircraft) hardware and software components, subsystems and systems, support equipment, ICBM facilities, special test and maintenance programs.

4.3.1. General Requirements

4.3.1.1. The Contractor shall integrate Nuclear Surety requirements into the ICBM

SE 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 Directive (DoDD) 3150.02, DoD Nuclear Weapons Surety Program, and DoDD 3150.2M.

4.3.1.3. The Contractor shall support the ICBM organization in maintaining the nuclear certification program IAW AFI 63-125, Nuclear Certification Program, and associated elements including:

• Safety Design Certification

• Weapon System Safety Rules Development

• TO Certification

• Compatibility Certification

• Applicable activities supporting Operational Certification

4.3.1.4. The Contractor shall assess compliance with applicable certification criteria for ICBM Enterprise hardware and software components, subsystems and systems, support equipment, facilities, special test and maintenance programs.

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

4.3.1.6. The Contractor shall assist in defining interdependencies, assessing effects and integrating between Nuclear Surety, System Safety and cybersecurity requirements, IAW DoDD 3150.02.

4.3.1.7. The Contractor shall assist in assessing compliance with applicable Nuclear Command and Control (NC2) safety and security requirements detailed in DoDD S-5210.81, (U) U.S. Nuclear Weapons Command and Control, Safety, and Security.

4.3.1.8. The Contractor shall assist the SPOs in complying with the DOD nuclear physical security program IAW requirements detailed in DoDD 5210.41, Security Policy for Protecting Nuclear Weapons, and applicable AFIs and supplements.

4.3.1.9. The Contractor shall provide Nuclear Surety support for assessing new acquisitions as well as existing systems/subsystems.

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

• Unauthorized Launch (UL) assessments and studies

4.3.1.9.2. The Contractor shall coordinate and work with Nuclear Surety, System Safety and cybersecurity experts and program stakeholders to ensure that ICBM WSs comply with Nuclear Surety requirements and standards published in DoD and AF regulations.

4.3.1.10. The Contractor shall review and assess acquisition delivered artifacts used for nuclear certification to ensure accuracy and completeness.

4.3.1.11. When required by the SPOs, the Contractor shall conduct Nuclear Safety Analysis and Technical Evaluation (NSATE) assessments of nuclear certified software not assessed by the (Nuclear Surety Cross Check Analysis) NSCCA Contractor. The NSATE is an independent software verification process that can include any of the common forms of verification: test, demonstration, inspection, and analysis. Reference

AFMAN 91-119.

4.3.1.11.1. Deliverables required in support of an NSATE assessment include the following IAW AFMAN 91-119:

• Test Plan (CDRL A060)

• Test Procedure (CDRL A061)

• Test/Inspection Report (CDRL A062)

• Deficiency Report (DR) (CDRL A035)

• Nuclear Certification Plan (NCP) (CDRL A078)

4.3.2. Deliverables Support

4.3.2.1. The Contractor shall review, provide assessment, and develop deliverables when directed, including:

• Briefing Materials (Nuclear Surety briefings, Point/White Papers, etc.)

(CDRL A003)

• Certification Requirements Plan (CRP) (CDRL A078)

• Changes to ICBM Items in the Master Nuclear Certification List

(MNCL)

• Engineering Evaluation Report (EER) (Nuclear Surety) (CDRL A079)

• Nuclear Safety Analysis Report (NSAR) for Ground Launched Missiles

(CDRL A077)

• NCP (CDRL A078)

• Nuclear Certification Impact Statement (NCIS) (CDRL A080)

• Nuclear Surety Evaluation (NSE) Report (CDRL A081)

• Safety and Nuclear Surety Technical Memorandum

• Software Certification Plan (SCP) (CDRL A078)

• Source data for ICBM TOs IAW TMCR 86-01 (CDRL A110)

4.3.3. Nuclear Safety Support

4.3.3.1. The Contractor shall support the AF UL program IAW AFI 91-106.

4.3.3.2. The Contractor shall assess/analyze ICBM WSs for:

• Adverse effects on primary safety, security, and cyber features in ICBM WSs which control nuclear critical functions detailed in AFI 91- 101, AFMAN 91-118, and 91-119.

• Compliance with AFMAN 91-118, Table 3.21, which gives the AF established numerical probability requirements for preventing inadvertent critical function activation because of system faults and failures.

• Compliance with AFMAN 91-118, Table 3.1, 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.3.3. Nuclear Surety Mishap Requirements

4.3.3.3.1. The Contractor shall assist the SPOs in the emergency response to incidents involving a Nuclear Weapon or other nuclear critical components.

4.3.3.3.2. The Contractor shall assist the SPO to complete assigned ICBM corrective action items from mishaps, generally including:

• Assessing compliance with AFMAN 91-118 Table 3.1, which gives the AF established numerical probability requirements for preventing inadvertent critical function activation because of system faults and failures

• Assessing Compliance with AFMAN 91-118, Table 3.2, which gives the AF established numerical probability requirements for obtaining an unintentional significant nuclear yield because of faults and failures in the GBSD system

• Recommendations to close all assigned action items from DULL SWORD Deficiency Reports

• High Accident Potential (HAP) Reports

• Safety Investigation Board (SIB) Reports

• Operational Review Board (ORB) Reports

• Weapon System Discrepancy Reports

• Potential Code Compromise (PCC) Reports

• Code Related Event (CRE) Reports

4.3.3.4. 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.3.5. The Contractor shall provide support IAW the 91-series AFIs for special ICBM test and maintenance programs including:

• Programmed Depot Maintenance (PDM)

• Hardness Surveillance Electromagnetic Pulse (EMP) Program (HSEP)

• Simulated Electronic Launch (SEL) test

• Other special test or maintenance action required in the operational

ICBM fleet and new acquisitions

4.3.3.6. 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 and Survivable Launch Platform – Airborne (SLP-A) Nuclear

Surety Working Group (AINSWG) with the USN

• NC2/Nuclear Command, Control, and Communications (NC3) study groups

• Lead Project Office (LPO) meeting and working groups

• ICBM Codes Conference

• System Theoretic Process Analysis (STPA) for Security (STPA-Sec) and associated efforts

• Other working groups focused on Nuclear Surety Specialty areas such as Targeting, Physical Security, etc.

4.3.3.6.1. Support shall include:

• Developing working group meeting agendas (CDRL A002)

• Preparing and consolidating briefing materials from other

ICBM SPO IPTs (CDRL A003)

• Status reports on Engineering assessments

• Answers to assigned action items that have been assigned to other ICBM SPO IPTs

• Providing meeting minutes to participants (CDRL A004)

4.3.3.7. The Contractor shall provide Nuclear Surety support to Special Access Programs (SAPs) and Sensitive Compartmented Information (SCI) in Government-cleared facilities.

4.3.4. Specific Qualifications and Required Skills

4.3.4.1. UL Assessment: The Contractor shall provide Engineering expertise in

Nuclear Surety, nuclear certification, cybersecurity, physical security, risk assessment, and information assurance.

4.3.4.2. NSCCA/NSATE: The Contractor shall provide shall provide software expertise with independent software evaluation/verification methods, nuclear software certification, software safety, cybersecurity, information assurance, and SE.

4.3.4.3. Other subject matter expertise is required in:

• Assessing the Nuclear Surety consequences created from an ICBM WS safety or cyber incident involving a Nuclear Weapon or nuclear critical component and providing technical solutions to resolve the incident

• Assessing Supply Chain vulnerabilities and Nuclear Surety consequences if vulnerabilities are exploited, and providing technical solutions to mitigate Nuclear Surety impacts

• Assessing Nuclear Surety consequences of vulnerable electronic, software, and networked systems if vulnerabilities are exploited, and providing technical solutions to mitigate Nuclear Surety impacts

• Assessing operational vulnerabilities in technical processes and providing technical solutions to mitigate Nuclear Surety impacts

4.3.4.4. The Nuclear Surety Team Contractor Lead Engineer shall have:

• A minimum of seven (7) years of ICBM experience obtained either at a

SPO, ICBM operational wing, industry partner, or other nuclear enterprise assignment

• The necessary knowledge, skills and abilities to assist the AF in execution of the ICBM Nuclear Surety and certification program.

• Training or experience in conducting safety assessments to determine hazard/cause/effects in complex DoD WSs

• The ability to conduct threat assessments to determine if proposed developer solutions to ICBM mission requirements create Nuclear Surety risks.

• A degree from an Accreditation Board for Engineering and Technology, Inc. (ABET)-accredited Engineering school or a minimum of a four (4) year degree in physics, math, or computer science.

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

NH&S Description NH&S in the ICBM Organization at Hill AFB uses the definitions of NH&S from MIL-STD- 1766C, NH&S Program Requirements for ICBM Weapon Systems:

Hardness: (see 1766C A.3.54) Hardness is a measure of the ability of a system or any of its constituent elements to withstand exposure to one or more effects of man-made or natural hostile environments. In this document, hardness always refers to Nuclear Hardness.

Survivability: (see 1766C A.3.132) Survivability is the capability of a system to withstand a hostile attack without suffering an abortive impairment of its ability to accomplish its designated mission. In this standard, survivability always refers to nuclear survivability and is a probability between zero and one. It is dependent upon threat, scenario of threat employment, and the design and concept of operations of the system.

The Government is responsible for ensuring design decisions, modifications, maintenance actions, and aging do not degrade the existing hardness of an ICBM nor hinder an ICBM from meeting its hardness requirements 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 determine future WS survivability, monitor current WS survivability status, track hardness performance trends, and detect degradation.

The objective of the NH&S process is to ensure ICBMs achieve and maintain the level of hardness necessary to meet their respective…