RSRV_SSC_PWS_-_8_Feb_2018.pdf

MINUTEMAN III (MMIII)

REENTRY SYSTEMS/REENTRY VEHICLES (RS/RV) SUBSYSTEM CONTRACT

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

Flight Systems Division (AFNWC/NIA) ICBM Reentry Systems/Reentry Vehicle (RS/RV) Branch (AFNWC/NIAE)

8 February 2018

FA8214-19-D-XXXX

Page | ii

TABLE OF CONTENTS

SECTION I - DESCRIPTION OF SERVICES

1.0 SCOPE

1.1. PURPOSE

1.2. BACKGROUND

1.3. ICBM SUSTAINMENT AND ACQUISITION CONSTRUCT DESCRIPTION:

1.4. RS/RV SUBSYSTEM DESCRIPTION

1.4.1. Reentry System (RS)

1.4.1.3. Reentry Vehicles (RV)

1.4.1.4. Penetration Aids

1.4.2. RS/RV Support Equipment

1.5. APPLICABLE DOCUMENTS

1.6. REQUIREMENTS

1.6.1. Sustaining Engineering

1.6.2. Systems Engineering (SE)

1.6.3. Program Management Support

1.6.4. Operations, Maintenance, and Logistics Support

1.6.5. Test and Assessment

1.6.6. Development, Procurement, and Repair Programs

SECTION II - SERVICE SUMMARY

2.0 SUMMARY MATRIX

SECTION III - PROPERTY MANAGEMENT

3.0 PROPERTY MANAGEMENT

3.1. GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES

Page | iii

3.2. NUCLEAR WEAPONS-RELATED MATERIEL (NWRM)

SECTION IV - GENERAL INFORMATION

4.0 GENERAL INFORMATION

4.1. SECURITY REQUIREMENTS

4.2. CYBERSECURITY REQUIREMENTS

4.3. QUALITY CONTROL

4.4. QUALITY ASSURANCE

4.5. PHYSICAL SECURITY

4.6. HOURS OF OPERATION

4.7. CONSERVATION OF UTILITIES

4.8. RECORDS

4.9. ENVIRONMENTAL CONTROLS

4.10. GOVERNMENT OBSERVATIONS

4.11. SAFETY REQUIREMENTS

4.12. QUALIFICATIONS

4.13. PARTNERING AGREEMENT (PA)

4.14. ANTITERRORISM CONSIDERATIONS

4.15. CONTINUATION OF ESSENTIAL DOD CONTRACTOR SERVICES DURING

CRISIS IAW DEPARTMENT OF DEFENSE INSTRUCTION (DODI) 1100.22

4.16. PHASE OUT/FOLLOW-ON

4.17. PUBLICATIONS

4.18. ASSOCIATE CONTRACTOR AGREEMENT (ACA)

SECTION V – APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B: WORK BREAKDOWN STRUCTURE

Page | iv

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

APPENDIX D: NWRM/CLASSIFIED SHIPPING ADDRESSES

APPENDIX E: APPLICABLE DOCUMENTS

APPENDIX F: CONTRACT DATA REQUIREMENTS LIST (CDRL)

APPENDIX G: DEPOT SUPPORT EQUIPMENT LISTING

APPENDIX I: EXAMPLES OF FUTURE EFFORTS OR PROGRAMS

Page | 1

SECTION I - DESCRIPTION OF SERVICES

1.0 SCOPE

This contract is required to support the MMIII ICBM Reentry RS/RV subsystem for an estimated 10-year period in the areas of sustaining engineering, maintenance engineering, test and assessment, modification of systems and equipment, software maintenance, developmental engineering, production engineering, repair, and procurement.

1.1. PURPOSE

This document outlines what is required for the contractor to execute in order to support the MMIII ICBM RS/RV subsystem.

1.2. BACKGROUND

The MMIII is a mature, fielded, weapon system that is in the operation and support phase of its life cycle. The primary activity is the sustainment of the MMIII force in a state of readiness such that national defense strategies involving these systems can be successfully executed, if required.

General system performance parameters that reflect the adequacy of readiness for the MMIII force are availability, reliability, accuracy, and hardness. Weapon system sustainment includes incorporating changes to ICBM systems in response to requirements for performance improvements, to take advantage of advances in technology, correction of system deficiencies, life extension programs, policies mandated by Congress or directed by other higher authorities, threat- or safety-driven changes, or other changes in the operational environment such as changes in support and maintenance policies.

Requirements for changes or modifications to fielded systems are usually applicable at the subsystem or lower level and may be performed by the subsystem contractors. Satisfying these requirements involves acquisition activities that can potentially impact system-level performance parameters. Reference documents include but are not limited to:

• Specification S-133-128 - System Specification for MMIII

• Silo-Based ICBM Standard (SBICBM-STD)-01 - Systems Requirements Analysis for

SBICBM Systems

• ICBM-Handbook (HDBK)-02 - ICBM Systems Directorate (ICBMSD) Interface Control

Management Handbook

• ICBM Interface Control Drawings listed in Report 62-46-1

• Overarching Performance Requirements- Threshold-Values for Accuracy, Availability, and Reliability

• ICBM System Directorate (ICBMSD) Environmental Requirements Summary

• Air Force Acquisition and Sustainment Life Cycle Management (Air Force Instruction

(AFI) 63-101/20-101) and Air Force Life Cycle Systems Engineering (AFI 63-1201)

• AFI 23-101, United States Air Force (USAF) Materiel Management

• AFI 63-103, Joint AF-NNSA Nuclear Weapons Life Cycle Management

• AFI 99-103, Capabilities-Based Test and Evaluation, 6 Apr 17

Page | 2

• AFI 91-208, Hazards of Electromagnetic Radiation to Ordnance (HERO Certification and Management, 1 Feb 17

• MIL-STD-1766C, Nuclear Hardness and Survivability Program Requirements for ICBM Weapon Systems, 17 Jan 17

1.3. ICBM SUSTAINMENT AND ACQUISITION CONSTRUCT DESCRIPTION:

The ICBMSD must prepare a sustainment concept to ensure a safe, secure and reliable MMIII weapon system until 2030.

1.3.1. Working Relationships

Figure 1. ICBM Sustainment and Acquisition Construct

1.3.1.1. RS/RV/ICBMSD Relationship

The RS/RV Subsystem Contractor will assist the Government in fulfilling its role as the RS/RV Subsystem manager by performing at the Governments request, sustaining engineering, maintenance engineering, aging surveillance, modification of systems and equipment, software maintenance, developmental engineering, production engineering and procurement. The RS/RV

ICBM Systems Directorate Function: Weapon System Integrator

Page | 3

Subsystem Contractor will transfer industrial ICBM technical expertise and knowledge to the ICBM organic workforce through briefings, training sessions, hand-on training, etc. as requested.

The contractor will provide breadth and depth of capabilities for the functional disciplines listed in the Work Breakdown Structure (WBS), listed in Appendix B, across the RS/RV Subsystem.

1.3.1.2. Integration Support Contract (ISC)/ICBMSD/RS/RV Subsystem Contractor Relationship

While the RS/RV Subsystem Contractor will provide preponderance of sustaining engineering support to the subsystems, the ISC contractor will also provide subsystem expertise to validate subsystem contractor analyses and produce requirements and other documentation for subsystem acquisitions that would create an Organizational Conflict of Interest (OCI) if produced by the subsystem contractor. As RS/RV Subsystem programs that require ISC contractor support are initiated, new contract line item numbers (CLINs) will be added to the ISC for those tasks. This is required to ensure the proper appropriations are used and each program pays for the additional support associated with their program.

In order to competently and conscientiously support the MMIII, the United States AF requires its contractors and their major subcontractors to effectively share information concerning the status of programs and technical issues with the weapon system. This communication shall occur with the Government and among other system support contractors to the maximum extent consistent with proper protection of classified and/or other sensitive information. To achieve this, the ISC contractor will have appropriate Non-Disclosure Agreements (NDAs) with the RS/RV Subsystem Contractor and other subcontractors, and demonstrate the ability and willingness to communicate openly. The ISC contractor will only provide contractual direction to its subcontractors. Likewise, the RS/RV Sub-System Contractor (SSC) shall only provide direction to its subcontractors.

1.3.2. Technical Council

The RS/RV Subsystem Contractor is a key participant on the ICBM Technical Council and is expected to send a representative to every meeting. The ICBMSD will establish and chair this council which will meet at a minimum semi-annually and maximum quarterly, as determined by the Director, ICBMSD, and be comprised of contractor and ICBMSD representatives from each of the subsystems. The Technical Council will provide a forum where the ICBMSD and key suppliers at various levels can directly, and on an equal level, engage on issues important to ICBM systems.

1.3.2.1. Government Members

Director, ICBMSD (Chair), Director of Engineering (Alt Chair), Chief Engineer, ICBM MMIII, ICBM Systems Engineering, Senior Engineer, ICBM Future Systems. Representatives from the following organizations will also be included: 748th Supply Chain Management Group (SCMG), Air Force Global Strike Command (AFGSC) (HQ/OL-J), Air Force Nuclear Weapons Center (AFNWC)/Engineering and Technical Management Directorate (AFNWC/EN), AFNWC Logistics Directorate (AFNWC/LG), AFNWC/Intelligence and Capabilities Integration

Page | 4

Directorate (AFNWC/XR), AF Program Executive Officer, Strategic Systems (AFLCMC/SS), 309th Maintenance Wing, and others as determined appropriate by the ICBMSD.

1.3.2.2. Associate Government Members

Associate Government members are designated by the relevant Integrated Product Team (IPT) Chief or Director of Engineering.

1.3.2.3. Contractor Primary Members

SE Contractors, Guidance System Contractors, Propulsion System Contractors, Reentry System (RS) Contractors, Ground System Contractors and Integration and Test Contractors.

1.3.2.4. Associate Contractor Members

Associate contractor members are designated by the relevant Government IPT Chief or ICBMSD Director of Engineering (DirEng) from among the contractors or subcontractors currently on contract to perform ICBM support. Examples of expected members are inertial instrument designers and producers, solid propulsion provider, liquid propulsion provider, flight control provider and Rapid Execution and Combat Targeting (REACT) console provider. If an associate contractor is also a subsystem contractor and primary Technical Council member, then additional membership is not required.

1.3.2.5. Ground Rules

Technical Council meetings shall be a process for candid discussion of ICBM issues. This body makes no decisions, nor provides contractual direction. Technical council members shall not coerce or censor discussion through existing contractual relationships.

1.3.2.6. Administration

The ICBMSD Director of Engineering (DirEng) is the process owner of the ICBM Technical Council. The ISC contractor will provide an administrative assistant to record minutes, schedule meetings and file presentations given at the ICBM Technical Council. The ISC contractor will assist the Director, ICBMSD and ICBMSD DirEng in updating the charter as required and coordinating it with the other Technical Council members. Meetings will initially be held quarterly. The frequency and duration of meetings will be adjusted by the ICBMSD DirEng in consultation with the Director, ICBMSD and the ICBM Technical Council members as the forum matures.

1.3.3. RS/RV Subsystem Contractor and Other Subsystem Contractors

Each subsystem support contract is designed to include the Sustaining Engineering efforts for that subsystem and any relevant tasks required to sustain the subsystem that are not accomplished on a different contract or by an organic entity. Test equipment programs and modifications may also be performed on the subsystem contract as long as the dollar threshold for the contract is not exceeded. Major modifications will be separately competed as these programs will be Acquisition Category (ACAT) 1D and ACAT II programs and are likely to

Page | 5 provide an opportunity for innovation from the larger industrial base to improve weapon system performance. However, ACAT III and non-ACAT programs may be executed by a subsystem contractor. Nuclear Safety Cross Check Analysis (NSCCA), Performance Analysis Technical Evaluation (PATE) and Independent Verification and Validation (IV&V) for software will be managed by the AF and performed by an independent contractor.

1.3.4. Special Considerations

The RS/RV Subsystem Contractor shall be responsible for supporting integration of all RS/RV efforts and shall collaborate with the ISC and all other subsystem contractors in the process of ensuring full compatibility with the RS/RV subsystem and the weapon system. The criticality of ensuring complete integration of any modification cannot be overstressed. All modifications accomplished by the RS/RV Subsystem Contractor or their subcontractors will be analyzed for any potential integration impact whether it is only the RS/RV subsystems or the weapon system as a whole. The RS/RV Subsystem Contractor will ensure assessment and analysis of modifications are accomplished using ICBMSD integration processes. The contractor will fully support and adequately staff all RS/RV integration related efforts to ensure backwards compatibility between legacy systems and modifications do not have a negative impact on RS/RV subsystems, as well as the weapon system as a whole. Additionally, the RS/RV Subsystem Contractor will proactively engage as directed by the government with the ISC contractor and the other subsystem contractors to ensure any modifications other subsystems contractors have performed will have no negative impact on the RS/RV subsystem. The RS/RV Subsystem contractor will also proactively engage with those awarded future modification efforts through open competition and ensure the non-RS/RV contractor’s modification efforts have no adverse impact to the RS/RV subsystem or the weapon system as a whole.

The responsibility to direct other contractors and ultimately approve or disapprove reports and other products remains with the ICBMSD. The ISC contractor will negotiate appropriate NDAs with all subsystem contractors so that information needed in support of ICBM weapon system can be freely shared between the subsystem contractors and the ISC contractor. In addition, the RS/RV Subsystem Contractor will be required to negotiate appropriate NDAs with the aforementioned contractors to ensure successful integration. While the ISC contractor maintains a close relationship with the ICBMSD, the ISC contractor is not allowed to perform inherently governmental functions.

1.4. RS/RV SUBSYSTEM DESCRIPTION

The MMIII RS/RV Subsystem consists of the RS and RS/RV support equipment. For the remainder of this document the term RS will include all components with the exception of the reentry vehicles.

1.4.1. Reentry System (RS)

The RS consists of four major components, the deployment module, shroud assembly, reentry vehicle, and penetration aids. For the remainder of this document the term RS will include all components with the exception of the reentry vehicles. The major components are briefly described below.

Page | 6

1.4.1.1. Deployment Module

The deployment module consists of the payload bulkhead which provides the structural support for mounting the reentry vehicles, chaff dispensers, electrical signal and power distribution equipment, as well as the RS Installation Kit and the Interface Cable Set.

1.4.1.2. Shroud Assembly

The shroud provides the aerodynamic cover for the entire RS that would otherwise be subjected to any and all environments during the missile’s powered flight. The shroud contains a rocket motor assembly and a separation clamp (or V-Band clamp).

1.4.1.3. Reentry Vehicles (RV)

The MMIII ICBM payload currently consists of either the Mark (Mk)12A or the Mk21 RV.

1.4.1.4. Penetration Aids

Penetration Aids provide credible false targets to enemy defenses to increase the probability of successful RV penetration. The penetration aids subsystem consists of the chaff subsystem, including a chaff dispenser and chaff dispenser attachment kit.

1.4.2. RS/RV Support Equipment

The MMIII RS/RV Subsystem is heavily dependent on handling and test equipment for field operations and deployment, as well as depot level maintenance and testing activities. The highest sustainment efforts involve, the Test Control System (TCS), the Low Frequency Instrumentation Console, Radio Frequency (RF) Instrumentation Console, and associated Interface Adapter Units (IAUs). This equipment is critical to sustainment of the MMIII RS/RV but difficult to maintain because most of it is 30+ years old which contributes to component aging, obsolescence, and inadequate documentation.

1.4.2.1. Low Frequency Instrumentation Console (LFIC)

The LFIC is used to test the Mk12A and Mk21 arming and fuzing assemblies and their components. It serves as an interface between the Test Control Station and the appropriate IAU.

The LFIC provides universal stimulus to the unit under test (UUT) and measurement and switching hardware for the required testing. LFIC is used for both depot level maintenance activities, mainly acceptance testing and troubleshooting, and test and assessment activities. The Government owns six LFICs; two are used for Mk21 activities, two for Mk12A activities, and one for Service Select, Test, Assess, and Report (STAR).

1.4.2.2. Radio Frequency Instrumentation Console (RFIC)

The RFIC is used to test the complete radar functionality of the Mk12A and Mk21 arming and fuzing assemblies and their radar subcomponents. It serves as an interface between the Test Control Station and the appropriate IAU. The RFIC provides universal stimulus to the UUT and measurement and switching hardware for the required testing. RFIC is used for depot level

Page | 7 maintenance activities, mainly acceptance testing and troubleshooting for the fuze radar subcomponents. The Government owns one RFIC that is currently non-operational.

1.5. APPLICABLE DOCUMENTS

See Appendix E

1.6. REQUIREMENTS

1.6.1. Sustaining Engineering

The Air Force Materiel Command (AFMC) Instruction (AFMCI) 63-510 definition of sustaining engineering is: “engineering effort on systems, products, or materials required resolving technical or supportability deficiencies revealed in operational service.” For ICBMs, major portions of sustaining engineering efforts are dedicated to assessment of ICBM weapon system status relating to key performance requirements. The AFMC definition specifically includes the following list of activities but does not limit activities to this list: assessing deficiency indicators;

defining the characteristics and cause of such deficiencies; determining the impact on the affected product; identifying and evaluating alternative solutions; determining the preferred solution; and designing, integrating, and validating the preferred solution. The definition continues with the inclusion of all associated contractual efforts (i.e., development of engineering and technical data, modeling and simulation, testing, etc.) which are integral to the completion of the overall engineering. The scope of this effort includes activities as they relate to the Mk12A and Mk21 reentry vehicles, including all subcomponents and fuzes, the MMIII RS and all related RS/RV support and test equipment. The contractor shall support the following on an as needed basis: the review of ICBM TO change recommendations produced by field units, ICBMSD, 748 SCMG and ICBM Depot organizations; TO data produced by ICBM modification programs; field or ICBMSD generated Engineering Technical Assistance Request (ETAR); field generated AFMC 107 request per TO 00-25-107; depot generated AFMC 202 request; test directives, test plans, and engineering procedures developed in support of depot and operational test and maintenance projects and assess changes to RS/RV items contained in the Master Nuclear Certification Listing (MNCL). (CDRL A011, A055-1, A056, A057, A058)

1.6.1.1. Closed Loop Failure Analysis (CLFA)

The contractor shall recommend components and prioritization for planning, conducting, and report findings from CLFA. The contractor shall write CLFA plans and reports that will be deliverable to the Government. CLFA plans will require Government approval. CLFAs will be conducted on a variety of Aerospace Vehicle Equipment (AVE) hardware to include Mk12A and Mk21 arming and fuzing assemblies (AFAs), any AFA subcomponents, as well as any RS hardware to include payload bulkheads, shrouds, and V-Bands. Required CLFAs may not be limited to the previous list. The contractor shall perform a CLFA on any piece of RS/RV related hardware at the request of the Government. (CDRL A007-1, A055-2)

1.6.1.1.1. The contractor shall properly deliver and archive CLFA test data into the Integrated Missile Database (IMDB) and other data repositories as required. (CDRL A058)

Page | 8

1.6.1.1.2. The contractor will provide input to the Government regarding the selection and prioritization of CLFA candidates. (CDRL A055-2, A057, A058)

1.6.1.2. Software Sustainment

Software sustainment is sustaining engineering applied specifically to software. The Government owns the RS/RV software baseline and any SSC developed modifications. The RS/RV Subsystem Contractor shall identify field and depot software-related problem root cause, create solution options, make recommendations, change software code, perform integration activities, create test plans, test software fixes, perform necessary configuration and functional audits and provide the Government with items needed to place software under formal configuration control.

The contractor shall help resolve issues during 516 SMXS/MXDEG software verification testing.

The contractor shall support the Government efforts to address key software focus areas throughout the life cycle, as identified in the Systems Engineering Plan (SEP) and Attachment 8 of AFI 63-1201 for development and maintenance programs. The contractor shall support the application of Modular Open Systems Approach (MOSA) and Open Technology Development (OTD) principles. Software being sustained is associated with a mature, fielded weapon system where useful life has been extended well past their originally planned service life. Software activities may be required in the following areas: (CDRL A042, A043, A044, A055-3, A056)

1.6.1.2.1. Operational Software Change Requests (OSCRs)

The RS/RV Subsystem Contractor shall assess OSCRs for RS/RV compatibility to include defining impacts and further coordination when directed by the Government. (CDRL A055-4)

1.6.1.2.2. Minuteman Operational Targeting Program

Any software changes shall comply with the established software configuration management plan outlined in section 1.6.2.4.

1.6.1.2.3. Depot Software Sustainment

1.6.1.2.3.1. Provides software sustainment encompasses all engineering efforts to identify depot software-related problems, root causes, create solution options, make recommendations, change software code, create test plans, perform integration activities, test software fixes, and provide the Government with items needed to place software under formal configuration control.

(CDRL A042, A043, A044, A046, A050)

1.6.1.2.3.2. The contractor shall provide trained manpower for software maintenance.

1.6.1.2.3.3. The contractor shall use Government Furnished Equipment (GFE) and use additional test equipment and facilities required for software maintenance. (CDRL A104)

Page | 9

1.6.1.2.3.4. The contractor shall complete software maintenance and deliver documentation as required through the ICBM Task Tracking Software (ITTS) tasking’s i.e. Technical Evaluation Review Board (TERB) Briefings, test plans, reports, etc. (CDRL A056, A057, A058)

1.6.1.2.3.5. The contractor shall analyze requirements, design software, develop software code, integrate software components, test software, and software deployment. (CDRL A036, A037, A040, A042, A043, A044)

1.6.1.2.3.6. The contractor shall develop test plans and reports In Accordance With (IAW) most current revision of ICBMSDOI 99-103. (CDRL A056, A057, A058)

1.6.1.2.3.7. The contractor shall provide documentation required for software validation, TO Changes, and record Time Compliance Technical Orders (TCTO)s. (CDRL A106)

1.6.1.3. RS/RV Subsystem Safety

The contractor shall support the ICBMSD in the System Safety Program to identify and control ICBM hazards, to prevent mishaps and track mishaps. This task is in support of the ICBMSD to comply with requirements tailored from applicable policy. (CDRL A066)

1.6.1.3.1. The contractor shall support the Safety Risk Management program established by the Government. Tasks may include but is not limited: to support for risk assessment studies, Preliminary Hazards Assessments, Safety Hazard Analysis, Safety Compliance Assessment Reports, risk acceptance recommendations, briefings, point papers, white papers, technical memoranda and source data for ICBM Technical Orders (TO)s. (CDRL A003, A062, A066, A069)

1.6.1.3.2. The contractor shall provide system safety support to working groups as needed for RS/RV related issues. These include but are not limited to: Program IPTs, AFNWC/NIEV Safety IPTs, ICBM Project Officers Group (POG), ICBM Codes Conference and ICBM System Security Working Group (SSWG) as required.

1.6.1.3.3. The RS/RV Subsystem contractor shall support the ICBMSD in maintaining and updating as required the RS/RV Vandenberg AF Base (VAFB) Range Safety System Safety Program. This will include providing RS/RV safety documentation that meets the criteria specified in AF Space Command Manual (AFSPCMAN) 91-710 and performing the tasks needed to demonstrate compliance of RS/RV hardware and software with the applicable Range Safety requirements. This also will include system safety review of TOs related to RS/RV operations performed at VAFB to confirm compliance with AFSPCMAN 91-710 requirements.

The contractor shall provide updates to the existing Mishap Risk Assessment Report (MRAR) for MMIII Force Development Evaluation and Mass Properties Testing Safety Assessment Report (SAR) as required to reflect updates to existing hardware/software design and operations.

(CDRL A063, A066, A106)

1.6.1.4. Nuclear Surety

The RS/RV Subsystem Contractor shall support the ICBMSD and ISC in the nuclear weapon system surety program to comply with Department of Defense (DOD) requirements detailed in

Page | 10

DOD 3150.2-M and DOD Directive (DODD) 3150.2. 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-106, AFI 91-107, AFI 91-114, AFI 91-117, Air Force Manual (AFMAN) 91-118 and AFMAN 91-119, AFMC and AFNWC supplements. The above policies are tailored for applicability to new or modified MMIII ICBM 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 AF policies may include: Nuclear Certification Impact Statements (NCISs), Nuclear Surety Evaluation Reports (NSER), Fault Tree Analyses, Probabilistic Risk Assessments, Briefings, point papers, white papers, technical memoranda and source data to ICBM TOs and Operational Certification/Decertification (OPCERT/DECERT) TO procedures for ICBM Nuclear Critical Components. (CDRL A003, A055-5, A055-6, A073, A076, A077)

1.6.1.4.1. The contractor shall provide nuclear surety support to the ICBMSD to preserve nuclear certification of the current RS/RV programs, as well as support the nuclear certification of new or modified RS/RV hardware and software components, subsystems and systems, SE, facilities, special test and maintenance programs. The contractor shall provide support to the ICBMSD IAW the nuclear certification program requirements specified in AFI 63-125.

1.6.1.4.2. The contractor shall provide nuclear surety support to the ICBMSD and as they relate to RS/RV. Support shall include tracking, providing detailed recommendations to close all assigned action items from Dull Sword deficiency reports (DR), High Accident Potential (HAP) reports, Safety Investigation Board (SIB) reports, Operational Review Board (ORB) reports and DR. The actions will be used to develop ICBM trend data to identify and correct problems before they occur/reoccur. (CDRL A031, A055-7)

1.6.1.4.3. The contractor shall provide nuclear surety support to special ICBM test and maintenance Hardness Surveillance Electromagnetic Pulse (EMP) Program (HSEP). Support will include development of assessments, reports and briefings to verify compliance with applicable AFI-91 series AFIs. The contractor shall assess changes to RS/RV items contained in the MNCL.

(CDRL A055-8)

1.6.1.4.4. The contractor shall provide nuclear surety support to working groups as needed for RS/RV related issues. These include: ICBMSD System Engineering, Environment, Safety & Technical Data (NIEV) Safety IPTs, ICBM Nuclear Surety Working Group (NSWG), AF Nuclear Weapon System Safety Groups (NWSSG), ICBM Project Officers Working Group (POG), Nuclear Security Working Groups, ICBM Codes Conference. Support shall include developing working group meeting agendas, preparing and consolidating briefing materials, status reports on engineering assessments or answers to assigned action items, and providing meeting minutes to participants. Support shall include engineering assessments or answers to assigned ICBMSD action items. (CDRL A002, A003, A004, A022)

1.6.1.5. Department of Energy Interface Control Support

Contractor shall provide support for the creation, review, update and configuration control of Interface Control Documents between the AF and other nuclear agencies such as Department of Energy (DOE), NNSA etc. (CDRL A028)

Page | 11

1.6.1.6. Specialty Engineering

The contractor shall support the Government with specialty engineering for the entire RS/RV subsystem. The special disciplines to be addressed are safety, security, corrosion, electromagnetic compatibility, and reliability.

1.6.1.6.1. Safety Engineering

The contractor shall integrate environmental, safety, and occupational health (ESOH) considerations to support Government safety activities as documented in MIL-STD-882E, Department of Defense Standard Practice for System Safety. The Government will comply with ESOH requirements in Attachment 4 of AFI 63-1201. The contractor shall eliminate ESOH hazards where possible and shall manage risks of hazards that cannot be avoided. The contractor shall report acceptance decisions and ESOH risks status. (CDRL A055-9, A062)

The contractor shall support system-related Class A and B mishap (http://static.e-publishing.af.mil/production/1/af_se/publication/afi91-204/afi91-204.pdf ) investigations by providing analyses of hazards that contributed to the mishap and recommendations for materiel risk mitigation measures, especially those that minimize human errors. Reference Appendix C.

1.6.1.6.2. Security Engineering

The contractor shall integrate security into the overall SE process. The contractor shall eliminate, reduce, or control through engineering and design any characteristics that could result in operational security deficiencies. The contractor shall identify, evaluate, and eliminate or contain system vulnerabilities to new or postulated security threats in the operational environment. The contractor shall support the Program Protection Plan. (CDRL A055-10, A071)

1.6.1.6.3. Corrosion Engineering

The contractor shall support the long-term RS/RV subsystem corrosion prevention and control strategy as identified in the Corrosion Prevention and Control Plan. The contractor shall objectively evaluate corrosion prevention and control measures for effectiveness and suitability throughout the life cycle. (CDRL A012, A118)

1.6.1.6.4. Electromagnetic Compatibility Engineering

The contractor shall support Government responsibilities for Electromagnetic Compatibility (EMC) per requirements in S-133-128D and RF spectrum management.

1.6.1.6.4.1. The contractor shall support efforts to avoid unacceptable performance degradation of operational, test, and support equipment from Electromagnetic Environmental Effects, to avoid causing unintentional performance degradation to equipment due to EME from other equipment, and to avoid causing inadvertent activation of RS/RV ordnance due to EME or ESD. With regard to the efforts stated above, the contractor shall address all electromagnetic disciplines, including EMC and electromagnetic interference (EMI); electromagnetic vulnerability; EMP; electro-static discharge; hazards of electromagnetic radiation to personnel, http://static.e-publishing.af.mil/production/1/af_se/publication/afi91-204/afi91-204.pdf http://static.e-publishing.af.mil/production/1/af_se/publication/afi91-204/afi91-204.pdf

Page | 12 ordnance, and volatile materials; and natural phenomena effects of lightning and precipitation static.

1.6.1.6.4.2. For development, procurement and repair programs concerning only RS/RV operational equipment, the contractor shall maximize built-in design compatibility vice after-the-fact remedial measures. RS/RV operational equipment and flight hardware shall meet emissions and susceptibility requirements without needing to implement external solutions such as special facilities or external equipment. (CDRL A081, A082, A083)

1.6.1.6.4.3. The contractor shall provide the expertise, measurement techniques, instrumentation and field engineering test facilities with the sensitivity, accuracy, range, and stability necessary to provide valid EME test data.

1.6.1.6.4.4. The contractor shall support Government efforts to mitigate radio spectrum interference and to maximize the benefit of the usable RF spectrum as identified in AFI 33-118.

1.6.1.6.5. Reliability Engineering

The contractor shall provide reliability engineering to support Government efforts to address Reliability, Availability, and Maintainability (RAM). The contractor shall find and present deficiencies to the Government with recommended corrections. The contractor shall treat RAM as an integral part of the SE process. The contractor shall balance program requirements, such as system performance, total ownership cost, schedule, supportability, risk, etc. The contractor shall coordinate and integrate reliability testing and evaluation plans and provides them to the Government for approval. (CDRL A031, A056, A057, A058)

1.6.1.6.6. Nuclear Hardness and Survivability

This support includes, but is not limited to, hardness impact assessments driven by changes in parts, coatings, etc. and changes in, hardware design; hardness assessment of test results, new drawings/TOs, and EOs/TO Changes; derivation of hardness requirements and verification criteria from S-133-128D to appropriate level (e.g. subsystem, component, piece-part, etc.) and other tasks/efforts in MIL-STD-1766C as required by the Government. The contractor shall support the ICBM Survivability Program Review as required.

The contractor shall support Hardness Data Manual and Nuclear Hardness & Survivability Design Analysis Report updates.

1.6.1.7. Modeling and Simulation

The contractor shall execute and maintain existing models as well as develop new models and simulation tools in order to analyze RS/RV related issues. All models must be validated and verified with Government approval. A list of RS/RV applicable models includes but is not limited to: Mass Properties, Radar Signature, Plasma, Fratricide, Damage Expectancy, Weather Impacts, RF Analysis, Finite Element Analysis, Circuit Analysis, Boundary Layer Transition Analysis and Flight Dynamics. The contractor shall maximize the use of modern commercial engineering tools for circuit simulation and 3D geometric modeling. (CDRL A023)

Page | 13

1.6.1.8. Task Log

The RS/RV Task Log is used to track all tasks identified in the RS/RV Subsystem. The identification and status of these tasks are tracked in a software tool called ITTS, which is managed by the ISC. The contractor shall coordinate directly with Government IPT leads to identify, define, and provide evaluation input for assigned ITTS tasks that documents the current and ongoing sustainment activities. The contractor shall assist the Government in prioritizing sustainment activities and manage and report how the operations and maintenance dollars are being expended on each task. ITTS tasks must be flexible to allow new, higher priority tasks to be quickly worked while lower priority tasks are temporarily postponed at the Government’s direction. The contractor shall engage in a Government-led ITTS task log review on a cyclic basis (defined by the AF) for RS/RV program management and engineering leadership.

As directed in the ITTS task, the contractor shall provide, in the AF’s Interim Data Repository (IDR) copies of request documentation. Providing these documents shall be considered a requirement of successful task completion. Examples of the types of documents that may be required by a ITTS task are Conference Agendas, Briefing Materials, and Meeting Minutes.

(CDRL A002, A003, A004, A055-11)

1.6.1.9. Data Management

The contractor shall populate and maintain IMDB and other automated information systems as appropriate with all applicable data and documentation regarding the RS/RV subsystem. This will include CLFA results, test and production data, test plan and reports, engineering change orders, and engineering change requests. (CDRL A027, A055-2, A056, A057, A058)

1.6.1.10. Department of Energy (DOE) and Project Officers Group (POG) Support

The contractor shall provide support to the AF representative on the POG and various subgroups as directed by ICBMSD. This support entails assistance in briefing charts, briefings, agendas, minutes, action item resolution, meeting attendance, and working with National Nuclear Security Administration (NNSA) and their contractors. POGs meet at various locations on a quarterly basis. The ICBMSD will be the lead on interactions with all government agencies. (CDRL A002, A003, A004)

1.6.1.11. Weapon System Effectiveness Report (WSER) and Data book

The contractor shall provide RS/RV input to the WSER. This input requires qualified personnel that understand the Reliability model and the Service STAR, Flight Test, and applicable aging surveillance (AS) test results that must be incorporated in the WSER. Tasks include but are not limited to:

• Identifying data needs

• Understanding system-level WSER report and what is needed from RS/RV to report at the system level

Page | 14

• Identifying how RS/RV will meet data needs. Examples of data sources: destructive physical analysis, CLFA results in addition to the traditional Force Development Evaluation (FDE), Service STAR and Aging Surveillance.

• Planning needed to capture required data

• Execution of activities needed to capture data

• Analysis of data

• Production of standalone RS/RV WSER data book

• Integration of RS/RV assessment into WSER as required

• Communication of RS/RV assessment to stakeholders

(CDRL A055-12)

1.6.1.12. Technical Order Management Agency (TOMA) Support

The contractor shall provide support to the ICBM TOMA for RS/RV related activities as needed.

Activities shall include creation of source data for new procedures related to sustainment of RS/RV hardware and software. The contractor shall also provide TO support for TCTOs and AF Technical Order (AFTO) Form-22 as required. Support for TO and TCTO validation and verification activities will also be required as necessary. (CDRL A106)

1.6.1.13. Trainers

The contractor shall support assessments and maintenance activities for RS/RV trainers and all associated support equipment that interfaces with RS/RV trainers. These activities will be coordinated with the applicable Integrated Program Team (IPT) Lead.

1.6.1.14. Security

The contractor shall comply with the Department of Defense Contract Security Classification Specification as applicable for the duration of this contract. The contractor shall also comply with the ICBM Security Classification Guide (SCG).

1.6.2. Systems Engineering (SE)

The SE process consists of evolving functional and design requirements. The goal is to achieve a proper balance between operational, economic and logistics factors. It employs a sequential and iterative methodology to reach cost effective sustainment solutions. Information developed from this process is used to plan and integrate the engineering effort for the system as a whole. The RS/RV Subsystem Contractor shall perform technical services related to SE and integration to include:

• Transforming operational needs into a description of system performance parameters and a preferred system configuration through the use of an iterative process of functional analysis, synthesis, optimization, definition, design, test, and evaluation.

• Integrating related technical parameters and assuring compatibility of all physical, functional, and program interfaces in a manner that optimizes the total system definition and design.

Page | 15

• Integrating reliability, maintainability, logistics support, safety, ability to produce, security, survivability, structural integrity, human factors and other related specialties into the total engineering effort.

(CDRL A030)

1.6.2.1. Risk Management

1.6.2.1.1. The RS/RV Subsystem Contractor shall participate with members of IPT Risk Management Boards to identify and evaluate weapon system risks. Reference ICBMSD Operating Instruction (OI) 62-10. If the Government risks management system changes, the RS/RV Subsystem Contractor shall comply with this change as well. The Contractor shall provide the Government the contractor’s Risk Management Plan and update as required to maintain consistency with the Government process. (CDRL A009)

1.6.2.2. Integration

The contractor shall support the Government with its role to provide vertical and horizontal integration within the RS/RV subsystem and with RS/RV related issues across the weapon system. The common objective is to maintain readiness and operational capability of the weapon system, subsystems, end-items, components, elements, and related support and test equipment throughout their combined life cycle. The Government will define the necessary System-of- Systems (SoS) engineering, technical management and control and engineering product support integration in the SEP. The RS/RV Subsystem Contractor shall analyze weapon system modifications for potential integration impact.

1.6.2.2.1. System-of-Systems (SoS) Engineering

The contractor shall support the Government’s SoS engineering tasks as defined in the Systems Engineering Planning (SEP).

1.6.2.2.2. Technical Management and Control

The contractor shall support the Government role to integrate stakeholder efforts. The Government will simultaneously ensure that contractors, and other personnel supporting programs and technical efforts, adequately employ SEP identified processes. The contractor shall balance supportability, life cycle costs, performance, and schedule considerations in making program recommendations for Government decisions.

1.6.2.2.3. Engineering Product Support Integration

The Government will integrate the activities of the product support providers, using the Acquisition Sustainment Tool Kit. The contractor shall provide intra-system and inter-system integration with supporting systems, subsystems, end-items, components and facilities. The contractor shall integrate efforts to assess the ongoing integrity of critical weapon system aspects, and support fleet viability assessments. The contractor shall ensure hardware and software modifications, process changes, and specification changes do not adversely affect subsystem and weapon system performance.

Page | 16

1.6.2.2.4. Systems Engineering Planning (SEP)

The Government will provide a SEP that integrates the many technical interests into a life cycle SE approach. The common objective is to provide a solid technical foundation to effectively unify, integrate, and focus the efforts of all stakeholders – researchers, acquirers, developers, users, operators, testers, trainers, maintainers, and sustainers – throughout the life cycle of the weapon system. The contractor shall provide a supporting relevant technical knowledge base that is matured, maintained, and transferred in a disciplined manner for the entire life cycle of the weapon system. The contractor shall provide adequate insight into technical planning and respond to Government technical direction.

1.6.2.3. Hardware Configuration Management

The RS/RV Subsystem Contractor shall perform the following tasks for RS/RV related issues, changes, modifications, and updates for both AVE and test equipment hardware. Drawings and updates will be compatible with, be submitted to, and go into the Joint Engineering Data Management Information and Control System (JEDMICS) IAW ICBMSD standards. (CDRL A023)

1.6.2.3.1. Provide support to the TERB and the Government Configuration Control Board

(CCB)

1.6.2.3.2. Prepare Engineering Change Proposals (ECPs) (CDRL A027)

1.6.2.3.3. Incorporate ECPs into the technical data systems

1.6.2.3.4. Support Government activities required to maintain the engineering baseline including drawing, hardware/process/material specifications updates, Hardness Data Manual updates, Nuclear Hardness & Survivability Design Analysis Report updates, and IMDB or equivalent updates. (CDRL A026)

1.6.2.3.5. Maintain drawing currency-end item drawing and ICD updates. (CDRL A023, A028)

This effort also includes supporting government efforts to transition into a 3D-model based environment and supporting the weapon system baseline in that environment and efforts to improve efficiency of this process.

1.6.2.4. Software Configuration Management

The contractor shall use software capable of meeting the Government configuration management requirements such as: Routing of engineering drawings, TERB/CCB support, ECPs, Software Change Requests (SCRs), Specification Change Notifications (SCNs), top level parts data, Indentured Parts Lists (IPLs), ICDs, specifications, and configuration items.

The RS/RV subsystem contract shall monitor and ensure configuration control of subsystem software, software analysis, and integration into the subsystem, maintaining configuration and Computer Program Identification Number (CPIN) support. Subsystem software includes

Page | 17

Operational Software, Trainer Software, Test Facility Software, Automatic Test Equipment software, Mission Application Software and Data System Software. The RS/RV Subsystem Contractor shall ensure CPINs are maintain currency and software used is authorized versions.

The contractor shall maintain software configuration congruency between depot support equipment and similar equipment (capital or Government owned) used at the contractor facility.

The contractor shall assist the Government to ensure that requirements allocated to software are satisfactorily met through the application of disciplined, well-defined processes. (CDRL A050)

1.6.2.4.1. Performing subsystems engineering and integration of software programs.

1.6.2.4.2. Performing software development activities, which include analyzing requirements, designing software, developing software code, integrating software components, testing software, and deploying software. (CDRL A036, A037, A038, A042, A043, A044, A045)

1.6.2.4.3. Sustaining software throughout its life cycle.

1.6.2.4.4. Maintaining software oversight.

1.6.2.4.5. Software changes are being made in accordance with approved policy and guidance.

1.6.2.4.6. Test planning and procedures to adequately address the changes made to accommodate the identified requirements. (CDRL A042, A043, A044)

1.6.2.4.7. Software release for operational testing is substantiated by test results.

1.6.2.4.8. Support government in establishing CPINs for all newly developed or modified software and its supporting documentation. This includes aiding the government in reviewing and/or creating test plans, procedures, and other documentation for CPIN efforts. Additional support is required in identifying ways to improve the CPIN process and implementing improvements when requested by the government.

1.6.2.5. Future Planning Studies

RS/RV Subsystem Contractor will support government directed planning activities. The studies may be focused on many different areas including future requirements, force capability, force structure, or critical shortfall areas for example.

1.6.3. Program Management Support

1.6.3.1. Commercial Small Business Involvement

1.6.3.1.1. RS/RV Subsystem Contractor will be required to meet small business subcontracting goals to include HubZone, Service Disabled Veteran Owned, 8(a) and Woman Owned small business. The Small Business Subcontracting Requirements and Incentives clause will require the contractor to meet an overall minimum small business subcontracting

Page | 18 requirement. The contractor will also be encouraged to meet and/or exceed goals for each socioeconomic category stated in the clause. A Small Business Subcontracting Plan will be required IAW with FAR 19.704. The Small Business Subcontracting Plan will be coordinated through and approved by Hill AF (HAFB) Base Small Business Office before contract award.

(CDRL A007-2)

1.6.3.2. Modification/Replacement/New Requirement Oversight

1.6.3.2.1. The RS/RV Subsystem Contractor shall support the Government Program Manager (GPM) in design changes and modifications to the RS/RV Subsystem as a result of correcting deficiencies, replacing obsolete parts, responding to operational requirement changes, incorporating technological advances, and changes driven by service-life extensions.

1.6.3.2.2. The RS/RV Subsystem Contractor shall provide oversight of all their modification/replacement subcontracts and ensure the Government is presented with options to receive the best value.

1.6.3.3. Program Management Information

1.6.3.3.1. The RS/RV Subsystem Contractor shall establish and maintain the capability to assist the GPM to report program cost, schedule, technical issues, and status for sustainment tasks and future efforts or programs.

The RS/RV Subsystem Contractor shall organize IPT and program information in a comprehensive and sufficiently detailed manner to provide insight into program and subcontractor approach and status. (CDRL A018, A019, A022)

1.6.3.3.2. The RS/RV Subsystem Contractor shall define and disclose work-around recovery plans for all issues and delays. (CDRL A007-3)

1.6.3.3.3. The RS/RV Subsystem Contractor shall…