Attach_1_Performance_Work_Statement.pdf

FA8204-19-R-0001

BASIC PWS- GSSC 2.0

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

BASIC - PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

February 2019

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

1.0 Ground Subsystem Support Contract General Requirements

1.1 Scope

1.2 Purpose

1.3 Background

1.4 ICBM Sustainment and Acquisitions Construct

1.4.1 Working Relationships

1.4.2 Technical Council

1.4.3 Co-Location

1.4.4 Ground Subsystem Contractor and Other Subsystem Contractors

1.4.5 Special Considerations

1.5 Ground Subsystem Description

1.5.1 Launch Control Center (LCC)

1.5.2 Launch Facility (LF)

1.5.3 Ground Support Equipment (GSE)

1.5.4 ICBM Infrastructure & Equipment (IIE)

1.5.5 Joint Mission Division

1.6 Applicable Documents

1.6.1 Compliance Documents

1.6.2 Reference Documents

2.0 General Information

2.1 Security Requirements

2.1.1 Intelligence Information

2.1.2 Base Access

2.1.3 Unescorted Entry

2.1.4 Security Management

2.1.5 Communications Security

2.1.6 Joint Personnel Adjudication System

2.1.7 Security Clearance

2.1.8 Security Training

2.1.9 Handling of Classified Material

2.1.10 Personnel Reliability Program

2.1.11 Removable Media

2.1.12 Physical Security

2.1.13 Key Control

2.1.13.1 Loss of Keys

2.1.13.2 Prohibition of Keys by Persons Other than Contractor Employees

2.1.13.3 Lock Combinations

2.1.14. Operations Security (OPSEC)

2.1.14.1. OPSEC Plan

2.2 Quality Control

2.2.1 Quality Control Program

2.3 Quality Assurance

2.3.1 Metrics

2.3.2 Qualification Reviews

2.3.3 Software Quality Assurance

2.4 Contracting Officer Representative (COR)

2.5 Hours of Operation

2.5.1 Normal Hours of Operation

2.5.2 Recognized Holidays

2.6 Emergency Services

2.7 Conservation of Utilities

2.8 Records

2.9 Environmental controls

2.9.1 Compliance with Laws and Regulations

2.9.2 Notification of Environmental Spills

2.9.3 Materiel Storage and Usage

2.10 Government Observations

2.13 Antiterrorism Considerations

2.14 Cont. of Essential DOD Contractor Services During Crisis

2.15 Associate Contractor Agreement

2.16 Small Business Participation

2.17 Data Rights

2.18 Development, Procurement, and Repair Programs

3.0 Appendices

APPENDIX A: ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B: WORK BREAKDOWN STRUCTURE

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

APPENDIX D: CONTRACT DATA REQUIREMENTS LIST (CDRL)

APPENDIX E: ATTACHMENT LIST

GROUND SUBSYSTEM SUPPORT CONTRACT

1.0 GROUND SUBSYSTEM SUPPORT CONTRACT GENERAL REQUIREMENTS

1.1 SCOPE

This contract is required to support the Minuteman III (MMIII) ICBM Ground subsystem for an estimated 18-year period of performance in the areas including, but not limited to; sustaining engineering, maintenance engineering, test and assessment, modification of systems and equipment, software maintenance, developmental engineering, production engineering, repair, and procurement.

This Performance Work Statement (PWS) describes the services the GSSC Contractor must provide to ensure all Ground Subsystems remain operational to meet warfighter requirements.

Unless otherwise specified, “Government” refers specifically to the Intercontinental Ballistic Missile Systems Directorate (ICBMSD).

This effort also includes scope for compatibility with existing or future systems or programs.

This may include, but is not limited to, studies and efforts related to MMIII to Ground Based Strategic Deterrent (GBSD) transition.

1.2 PURPOSE

This document outlines what is required for the contractor to execute in order to support the MMIII ICBM Ground subsystem. The use of “contractor” hereafter refers to the GSSC2 contractor.

1.3 BACKGROUND

The MMIII is a mature, fielded, weapon system (WS) 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. WS 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. Class I changes to the MMIII WS will typically be added as future Task Orders. 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

• 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 OSS&E and LCSE (AFMCI 63-1201)

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

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

• AFMAN 63-143, Centralized Asset Management Procedures

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

• 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.4 ICBM SUSTAINMENT AND ACQUISITIONS CONSTRUCT

The ICBMSD must prepare a sustainment concept to ensure a safe, secure and reliable MMIII WS until 2036.

1.4.1 Working Relationships

Figure 1. ICBM Sustainment and Acquisition Construct

1.4.1.1 Ground/ICBMSD Relationship

The Contractor will assist the Government in fulfilling its role as the Ground Subsystem manager by performing system engineering to include, sustaining engineering, maintenance engineering, aging surveillance, modification of systems and equipment, software maintenance, developmental engineering, production engineering, anomaly resolution, test and evaluation (T&E), configuration management (CM), software updates, baseline compliance, Interface Control Working Group (ICWG) participation, nuclear surety, Nuclear Hardness & Survivability (NH&S), Electromagnetic Compatibility (EMC), corrosion, environmental and system safety, and assessment and risk management.

1.4.1.2 Integration Support Contract (ISC)/ICBMSD/Ground Subsystem Contractor Relationship

While the Contractor will provide a preponderance of sustaining engineering support to the subsystems, the ISC contractor will also provide subsystem expertise to validate subsystem contractor analyses and testing, and produce deliverables and other documentation for subsystem acquisitions that would create an Organizational Conflict of Interest (OCI) if produced by the subsystem contractor.

In order to competently and conscientiously support the MMIII WS, 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 WS. 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 Ground 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 GSSC contractor shall only provide contractual direction to its subcontractors.

1.4.2 Technical Council

The Contractor is a key participant on the ICBM Technical Council and shall 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.4.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

Directorate (AFNWC/XR), AF Program Executive Officer, Strategic Systems (AFPEO/SS), Ogden Air Logistics Center (OO-ALC), and others as determined appropriate by the ICBMSD.

1.4.2.2 Associate Government Members

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

1.4.2.3 Contractor Primary Members

Members include: Systems Engineering Contractors, Guidance System Contractors, Propulsion System Contractors, Reentry System (RS) Contractors, Ground System Contractors and Integration and Test Contractors.

1.4.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. If an associate contractor is also a subsystem contractor and primary Technical Council member, then additional membership is not required.

1.4.2.5 Ground Rules

Meetings of the ICBM Technical Council are expected to be a process for candid discussion of ICBM issues. Classified discussion may occur, requiring proper visitor clearances be on file with the ICBMSD security office. This body makes no decisions, nor provides contractual direction. Technical council members shall not coerce or censor discussion through existing contractual relationships. The technical council shall be conducted in a non-attribution environment with clear attention paid to protection of proprietary rights. Prior to each meeting a call for topics and agenda will go out to all participating members.

1.4.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.4.3 Co-Location

ICBMSD sees potential benefits associated with the opportunity to have co-located contractor support near Hill AFB, with a satellite office at FE Warren AFB to support the ICBM Infrastructure and Equipment Office, AFNWC/NIH. Having the contractor, ICBMSD, and ISC teams work in close proximity can lead to a tighter working relationship that fosters better collaboration and more efficient WS management. ICBMSD requires its contractors and their major subcontractors to effectively share information concerning the status of programs and technical issues with the WS. This communication shall occur with the Government, ISC personnel, and subsystem support contractors to the maximum extent consistent with proper protection of classified and/or other sensitive information. To maximize benefits of a synergistic workplace and ensure that communication is protected, the contractor shall co-locate with ICBMSD the majority of personnel on or within 20 miles of Hill AFB and F.E. Warren AFB.

The Government shall not provide facilities and workspace. The contractor shall negotiate the appropriate work space to fulfill their particular needs in accordance with their technical approach.

1.4.4 Ground Subsystem Contractor and Other Subsystem Contractors

Each subsystem sustainment contract will include the system and sustainment engineering efforts for that subsystem and any relevant support tasks required to sustain the subsystem that are not accomplished on a different contract or by an organic entity. ACAT II, and ACAT III programs, and non ACAT efforts may be executed by the contractor, or openly competed. It is not the intent of the Government to include ACAT I Programs on this contract; however, it is not prohibited. 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 (see Note below). The contractor will be responsible for integration of all Ground Subsystems efforts and will collaborate with other Government contractors as required.

Note: The NSCCA/PATE/IV&V contractor is required to maintain technical, managerial, and financial independence from ICBM Program software developer contractors. In order to maintain technical independence, the ICBM Program software developer contractors shall not have access to the NSCCA/PATE/IV&V contractor’s test plans, test procedures, and Final Design Certification Reports (FDCR). Similarly, the NSCCA/PATE/IV&V contractor will not have access to the developer’s test documentation.

1.4.5 Special Considerations

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

The responsibility to direct other contractors and ultimately approve or disapprove reports and other products remains with the ICBMSD. The GSSC contractor shall negotiate appropriate NDAs with the ISC contractor so that information needed in support of ICBM WS can be freely shared between GSSC and the ISC contractor. In addition, the Contractor shall 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.5 GROUND SUBSYSTEM DESCRIPTION

All Ground Subsystems-related sustainment will be within the scope of the GSSC 2.0. The nature of Ground Subsystems-related sustainment will necessitate new requirement generation for future efforts; the Government will retain the option of assigning them to the GSSC 2.0 contractor, or openly competing them if it is determined to be in the best interest of the Government. Any future efforts against GSSC 2.0 will be added as a task order to the basic contract.

The contractor role is to provide support for MMIII Ground Subsystems equipment in system and sustainment engineering, and relevant operations and maintenance (O&M) tasks as directed.

The contractor will be responsible for providing support to the Government as needed to repair and/or maintain Ground Subsystems components. The contractor will also provide support during Missile Potential Hazard Network (MPHN) events. A MPHN is initiated in response to abnormal situations outside of technical data that create potential personnel or system safety hazards.

The following represents Ground Subsystems Integrated Program Team (IPT) structure of current programs and is provided for informational purposes only. This is to serve as a guide to enable the contractor to scope the total effort, provide the optimal skill level, and labor category mix required to effectively accomplish the required support. For additional information on ICBM Ground Subsystems reference the following documents: Ground Subsystems Division Work Unit Code Manuals, Work Breakdown Structure, Minuteman Ground Subsystems Reference Book, and the Product WBS in APPENDIX B: WORK BREAKDOWN STRUCTURE (WBS).

MMIII Ground Subsystem consists of Launch Control Center (LCC), Launch Facility (LF), Ground Support Equipment, and ICBM Infrastructure & Equipment (IIE). As applies to this document, the term Ground Subsystem will include all components.

1.5.1 Launch Control Center (LCC)

LCC is an underground structure of reinforced concrete and steel with sufficient strength to withstand weapon effects. It houses equipment and personnel capable of monitoring and controlling a squadron of Minuteman missiles.

The LCC Branch consists of Acquisition Programs and two Sections in support of the MMIII

WS.

The acquisition programs consist of the Pressure Monitor Receiver Transmitter (PMRT) Min Mod program and the Launch Control Center Block Upgrade (LCCBU). The sections consist of Communications Sustainment and Codes & Software Sustainment. The Sections are made up of several different sustainment Integrated Product Teams (IPT). The Communications Sustainment section consists of the WS Control Console (WSCC), Command and Control Equipment, and Communication Infrastructure IPTs. The Codes & Software Sustainment section consists of the Code System, Higher Authority Command/Rapid Message Processing Element (HAC/RMPE) Sustainment, and ICBM Operational Software Sustainment IPTs.

1.5.2 Launch Facility (LF)

The Launch Facility (LF) Branch consist of Acquisition Programs and three Sections in support of the MMIII WS. The acquisition programs consist of ICBM Cryptography Upgrade (ICU II), Automatic Switching Unit (ASU), Replacement Program, and Launch Control Center Break-In Kit (LCCBiK). The sections consist of Hardness & Survivability, Heating and Air Conditioning (HVAC), Power, Security, & Access Control.

The Sections are made up of several different sustainment Integrated Product Teams (IPT). The Hardness & Survivability Section consist of Blast Doors, Shock Isolators, Blast Valves, Launcher Support Systems, and Missile Suspension Systems IPTs. The HVAC Sections consist of the HVAC IPT. The Power, Security, and Access Control Sections consist of Power Systems, Surge Protection Program (SPP), Security Systems, Primary Security Door (A-Vault) and Secondary Security Door (B-Plug) IPTs.

1.5.3 Ground Support Equipment (GSE)

GSE is the equipment used to move, test, and maintain missile components. The GSE includes but is not limited to Payload Transporter III (PTIII), Transporter Erector (TE), MT, PMT, PSRE Trailer, Bunker Winch, GMMP, GMATS, Pipe Pusher, GMLEC, Simulated Electronic Launch – MMIII (SELM), etc. GSE also included all of the WS trainers.

1.5.4 ICBM Infrastructure & Equipment (IIE)

The ICBM Infrastructure & Equipment Office consists of two branches in support of the MMIII Weapon System. The Electrical Branch and Mechanical Branch have sustainment IPTs assigned to various systems and sub-systems. The Infrastructure & Equipment Office supports the ICBM Real Property/Real Property Installed Equipment (RP/RPIE) along with the ICBM Infrastructure & Equipment.

The Electrical Branch supports the MAF and LF Power Generation and Distribution systems including but not limited to Diesel Electric Units, Power Distribution Panels, Automatic Transfer Switches, Transformers, Power Filter Assemblies and Protection devices along with conduits, raceways and enclosures.

The Mechanical Branch has six IPTs supporting the MMIII weapon system. The Water Distribution and Waste Systems IPT consists of various waste Sump Pump systems, Dewatering Wells, Water Diverters, Emergency Shutoff Valves systems along with the LCC water distribution. The HVAC IPT consists of LSB Electric Unit Heaters and brine lines between the LSB and LER. The LF/MAF Structural IPT consists of the Launcher Closure Door and Bearing Surfaces, Abutment Areas, Steel Liners, Access Shafts, Floor Structures, Structural Penetrations along with the Air Entrainment System. The Support Systems IPT consists of Elevators, Fire Alarms, Security Systems, and Fuel Leak Detection Systems. The Crew Comfort IPT consists of LCC Carpet, Headliner, File Cabinets, Modular Bed Storage Units, and Kitchen Services Groups. The Vandenberg Launch Support Systems IPT consists of the Launcher Closure Arrestor System and Launch Warning System.

The IIE ground systems are an integral part of the ICBM weapon system and are a subset of the overall RP/RPIE portion of the MMIII weapon system supported by the ICBM Infrastructure & Equipment Office.

1.5.5 Joint Mission Division

The Ground System Support Contractor is required to support the Joint Mission Division (JMD) as requested by the Government. It is planned that any specific support will be called out in individual task orders. At this time Strategic Automated Command and Control System (SACCS) and Airborne Launch Control System (ALCS) efforts will be supported under JMD.

All applicable standards and supporting documents apply to JMD effort(s).

1.5.6 414th Supply Chain Management Squadron (SCMS)

The Ground System Support Contractor shall be able to support the 414th SCMS with CSAG projects related to ICBMSD managed Ground Subsystem Equipment as requested by the Government. Specific support requested will be called out in individual task orders. All applicable standards and supporting documents apply to SCMS efforts.

1.6 APPLICABLE DOCUMENTS

1.6.1 Compliance Documents

The following table contains the documents that require ICBM Program Office compliance for all MMIII WS sustainment activities. The contractor shall use the most current version of these documents. As a result, the Grounds Subsystem Contractor shall ensure that all sustainment efforts conducted under the PWS will allow the AF to demonstrate compliance. The contractor will create/modify their internal policies and procedures in order to demonstrate compliance.

When compliance is not possible, the Grounds Subsystem Contractor shall notify the Government.

In some cases, ICBM Systems Directorate Operational Instructions (OI) exist at the local level.

These documents can be located on the ICBM SharePoint or by contacting the Contracting Officer (CO) and/or the appropriate Grounds program manager or engineer.

Document Number Document Title DOD 3150.2-M DOD Nuclear Weapon System Safety

Manual DOD 4140.1-R Supply Chain Materiel Management

Regulation DOD 5210.42 Nuclear Weapons Personnel Reliability

Program” DOD 5220.22-M and Supplement 1 National Industrial Security Program

Operating Manual DODD 3150.02 DoD Nuclear Weapons Surety Program DODD 8100.02 Use of Commercial Wireless Devices, Services, and Technologies in the DOD Global Information Grid (GIG) Nuclear Weapons-Related Materiel Management

DODD 8500.01 Cybersecurity DODI 1100.22 Policy and Procedures for Determining

Workforce Mix DODI 4140.01 DOD Supply Chain Materiel Management

Policy DODI 5000.02 Operation of the Defense Acquisition

System DODI 8320.04 Item Unique Identification (IUID)

Standards for Tangible Personal Property DODI 8500.01 Cybersecurity DODI 8510.01 Risk Management Framework (RMF) for

DoD Information Technology (IT) DODM 5200.01 DoD Information Security Program:

Overview, Classification, And Declassification

S-133-128 System Specification for MMIII (WS- 133A-M Wings I, III, V)

1.6.2 Reference Documents

Document Number Document Title Hardness Data Manuals ICBM Security Classification Guide MILSTAR/Advanced Extremely High

Frequency (AEHF) Security Classification/ Declassification Guide

40 CFR 302 Designation, Reportable Quantities, and Notification

526 ICBMSW OI 20-04 Parts, Materials, and Processes Engineering 526 ICBMSW OI 91-01 Nuclear Surety and Nuclear Certification AFGSCI 36-283 ICBM Training System Management

AFGSCI 99-102 AFGSC Instruction, ICBM Operational

Test and Evaluation AFI 10-245 Antiterrorism AFI 10-601 Operational Capability Requirements

Development AFI 16-1404 AF Information Security Program AFI 20-110 Nuclear Weapons-Related Materiel

Management AFI 23-106 Standard Reporting Designators AFI 24-203 Preparation and Movement of Air Force

Cargo AFI 31-401 Information Security Program Management AFI 32-Series Civil Engineering Programming and Real

Property management AFI 32-7086 Hazardous Materials Management AFI 36-2251 Management of Air Force Training

Programs AFI 48-109 Electromagnetic Field Radiation

Occupational and Environmental Health Program

AFI 63-101 Integrated Life Cycle Management AFI 63-125 Nuclear Certification Program AFI 63-131 Modification Program Management 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-103 Air Force Nuclear Safety Design Certification Program

AFI 91-104 Nuclear Surety Tamper Control and Detection Programs

AFI 91-105 Critical Components AFI 91-106 Unauthorized Launch, Threat Mitigation, and Launch Action Studies AFI 91-107 Design, Evaluation, Troubleshooting, and

Maintenance Criteria for Nuclear Weapon Systems

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

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

AFI 91-208 Hazards of Electromagnetic Radiation to

Ordnance (HERO) Certification and Management

AFI 99-103 Capabilities-Based Test and Evaluation AFMAN 23-110 United States Air Force Supply Manual

AFMAN 63-143 AMR/CAM

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 AFMAN 91-201 Explosive Safety Standards AFMC Supplement 1 to AFI 20-110 Nuclear Weapons-Related Materiel

Management AFMCI 21-103 Reliability-Centered Maintenance (RCM)

Programs AFMCI 63-1201 Implementing Operational Safety, Suitability and Effectiveness (OSS&E) and Life Cycle Systems Engineering (LCSE)

AFMCI 99-103 Test Management AFGSCI 32-1005 ICBM Real Property/Real Property

Installed Equipment Responsibilities AFMCMAN 21-1 Air Force Materiel Command Technical

Order System Procedures AFNWCI 99-101 Nuclear Enterprise Test and Evaluation

Management AFPAM 63-128 Guide to Acquisition and Sustainment Life

Cycle Management AFPAM 63-113 Program Protection Planning for Lifecycle

Management AFPD 63-1/AFPD 20-1 Integrated Life Cycle Management AFPD 91-1 Nuclear Weapons and Systems Surety AFSPCMAN 91-710 Range Safety User Requirements AFSPCMAN 91-711 Launch Safety Requirements for Air Force

Space Command Organizations ANSI/ASQ Q9001:2000 Quality Management Systems:

Requirements ANSI/ASQ Q9001:2008 Quality Management Systems:

Requirements ANSI/ASQ Z 1.13-1999 Quality Systems Guide for Research ANSI/EIA-748 Earned Value Management System ASME NQA-1-2004 Quality Assurance Requirements for

Nuclear Facility Applications CJCSM 6510.01 Enclosures B and C Information Assurance (IA) and Support to

Computer Network Defense (CND)

Defense Transportation Regulation (DTR), Part II

Cargo Movement

DNA-H-93-140 Military Handbook for Hardness Assurance, Maintenance, and Surveillance (HAMS)

DOD 5210.41-M Nuclear Weapon Security Manual DODD 3150.01 Joint DoD-Department of Energy/National

Nuclear Security Administration (DoD- DOE/NNSA) Nuclear Weapon Life-Cycle Activities

DODI 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks

(TSN)

DODI 5200.39 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E)

DODI S-5200-16 Objectives and Minimum Standards for Communications Security (COMSEC) Measures Used in Nuclear Command and Control (NC2) Communications (U)

DOE M 470.4-6 Nuclear Material Control and Accountability

EO 13526 Classified National Security Information GEIA-STD-0007A Logistics Product Data ICBM Interface Control Drawings listed in Report 62-46-1

Latest Revision can be obtained by

AFNWC/NIE

ICBM-HDBK-01 Systems Requirement Analysis for ICBM Systems

ICBM-HDBK-02 Intercontinental Ballistic Missile Interface Control Management Handbook

ICBMSD 62-CMP ICBM Configuration Management Plan ICBMSD OI 10-245 The Air Force Antiterrorism Program ICBMSD OI 10-2501 Emergency Management ICBMSD OI 31-01 Information Security Program Management ICBMSD OI 31-04 Survivability and Vulnerability Integration

Center Entry Criteria at Little Mountain ICBMSD OI 62-01 Configuration Control Board (CCB) ICBMSD OI 62-02 Interface Control Management ICBMSD OI 62-03 Configuration Management Policies and

Procedures ICBMSD OI 62-04 Configuration Audits ICBMSD OI 62-06 Engineering Orders Policies/Procedures ICBMSD OI 62-08 Requirements Validation Board ICBMSD OI 62-10 Risk Management

ICBMSD OI 62-13 Software Configuration Management ICBMSD OI 62-16 Intercontinental Ballistic Missile (ICBM)

Assessment ICBMSD OI 62-18 Weapon System Effectiveness Report

(WSER)

ICBMSD OI 62-23 Supply Chain Risk Management ICBMSD OI 62-24 New and Replacement Electrical Power

Compatibility Requirements for MAF or LF Equipment

ICBMSD OI 99-02 Test and Evaluation Nuclear Hardness Critical Item (HCI) Parts Procurement

ICBMSD OI 99-103 Test and Evaluation MIL-DTL-38769 Manuals, Technical - Work Unit Code MIL-HDBK-454 General Guidelines for Electrical

Equipment MIL-HDBK-470 DOD Handbook – Designing and

Developing Maintainable Products and Systems

MIL-HDBK-515 Weapon System Integrity Guide (WSIG) MIL-HDBK-61A(SE) Configuration Management Guidance MIL-PRF-49506 Performance Specification Logistics

Management Information MIL-STD 3018 SD-19 and SD-22 DOD Standard Practice for Parts

Management, SD-19, Parts Management Guide/SD-22, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Guidebook

MIL-STD-130 Identification Marking of U.S. Military Property

MIL-STD-1472 Human Engineering, Design Criteria for Military Systems, Equipment, and Facilities

MIL-STD-1540 Test Requirements for Space Vehicles MIL-STD-1766 Nuclear Hardness and Survivability

Program Requirements, ICBM Weapon Systems

MIL-HDBK-1785 System Security Engineering Program Management Requirements

MIL-STD-461 Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

MIL-STD-464 Electromagnetic Environmental Effects Requirements for Systems

MIL-STD-882 Department of Defense Standard Practice:

System Safety

MNCL Master Nuclear Certification List NDIA Version 1.0 Engineering for System Assurance NIST IR 7622 Notional Supply Chain Risk Management

Practices for Federal Information Systems Other Documents Overarching Performance Requirements-

Classified Briefing Chart, Threshold-Values for Accuracy, Availability, and Reliability, (Revision 3) dated Oct 01/ (Rev 3) dated Oct 01

Other Documents ICBMSD Environmental Requirements Summary, 30 May 1997

Other Documents Current ICBMSD OIs Public Law 112-81 Section 818, Counterfeit Prevention Plan RCC 324-01 Global Positioning and Inertial

Measurements for Range Safety Tracking Systems’ Commonality Standard

SAE AS5553 Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition

SMC-S-012 Software Development Standard for Space Systems

SMC-S-021 Technical Reviews and Audits for Systems, Equipment, and Computer Software

TO 00-25-107 Maintenance Assistance TO 00-25-260 Asset Marking and Tracking Item Unique

Identification Marking Procedures TO 21M-LGM30G-12 Safety and Electromagnetic Interference

Provisions WINGS I, III, V, AND VAFB

USAF SERIES LGM-30G

TO 21M-LGM30G-2-31 Weapon System Hardness Preservation and Installation Hardware

62-SEP Minuteman III Weapon System Sustainment Systems Engineering Plan

2.0 GENERAL INFORMATION

2.1 SECURITY REQUIREMENTS

2.1.1 Intelligence Information

This project and the work being proposed may be classified and Need-To-Know (NTK). The following clearances may be required, up to and including:

• Top Secret (TS)

• Sensitive Compartmented Information (SCI)

• Restricted Data (RD)

• Special Access Program (SAP)

• Formerly Restricted Data (FRD)

The following Security Classification Guides (SCGs) will be followed:

• ICBM SCG, 23 Oct 2008

• Applicable joint DoD/DOE classification guides

• Applicable DoD weapon delivery SCGs

• Applicable DOE weapon SCGs

2.1.2 Base Access

The contractor shall complete an AFMC Form 496, Application for AFMC Identification Card for each employee of the contractor requiring access to Hill Air Force Base (AFB) and F.E.

Warren AFB. The requests shall be submitted to the ICBMSD Security Office to provide to the 75th Security Forces Squadron (SFS) or 90th Security Forces Squadron Pass and Registration (South or West Gate Visitor Center).

2.1.3 Unescorted Entry

The contractor shall complete an AF Form 2586, Unescorted Entry Authorization Certificate for each employee requiring entry into controlled areas. The request shall be submitted to the ICBMSD security office for processing.

2.1.4 Security Management

The contractor shall comply with security requirements contained in DOD 5220.22-M, National Industrial Security Program Operating Manual; DD Form 254, Contract Security Classification Specification, Department of Defense; ICBMSD OI 31-01, Information Security Program Management; and Nuclear Regulatory Commission (NRC) EA-05-090, Nuclear Regulatory Commission Holders of Material Licenses Authorized to Possess Radioactive Material.

2.1.5 Communications Security

The contractor shall possess a Communications Security (COMSEC) account and make available a COMSEC custodian able to accept, store, and ship commercial CRYPTO interface (CCI) items to worldwide units, reference DOD 5220.22-M.

2.1.6 Joint Personnel Adjudication System

The contractor shall possess a Joint Personnel Adjudication System account.

2.1.7 Security Clearance

The contractor shall ensure all employees have proper security clearances as required. Contractor employees with final Top Secret security clearances shall be trained and capable of performing the appropriate escort duties for personnel without the required security clearance IAW DOD 5220.22-M, National Industrial Security Program Operating Manual.

2.1.8 Security Training

The contractor shall be responsible for providing employees security training and briefings as required.

2.1.9 Handling of Classified Material

The contractor duties involve the regular handling/use of classified material and creation/copying of the material onto new media for use by the AF. The contractor shall be responsible for maintaining, operating, and controlling classified information IAW DOD 5220.22-M, National Industrial Security Operating Manual; AFI 16-1404, Information Security Program Management;

DODM 5200.01 vol 1 to vol 4, DOD Information Security; Executive Order (EO) 13526, Classified National Security Information; and DODD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the DOD Global Information Grid (GIG).

2.1.9.1 The contractor shall be responsible for safeguarding classified information, equipment, and materiel up to and including Top Secret level IAW DOD 5220.22-M, AFI 16-1404, Information Security Program; DODM 5200.01 vol 1- vol 4, DOD Information Security Program, EO 13526, Classified National Security Information, and DODD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the DOD Global Information Grid

(GIG).

2.1.9.2 The contractor shall be responsible for complying with International Traffic in Arms Regulations (ITAR) which implements the U.S. Arms Export Control Act by controlling the export of defense articles specified in the U.S. Munitions List and the technical data directly related to them. This Act has jurisdiction over information (including classified) relating to defense articles and services; information covered by an invention secrecy order; and information directly related to designing, engineering, developing, operating, overhauling, maintaining, modifying, etc., weapon systems.

2.1.9.3 The contractor may be responsible for transportation of classified materials (physical and electronic) to operational locations IAW DOD 5220.22-M, as directed by the Government

2.1.10 Personnel Reliability Program

The contractor shall comply with the nuclear weapon personnel reliability program contained in DOD 5210.42, Nuclear Weapons Personnel Reliability Program (PRP) Regulation, as required.

2.1.11 Removable Media

The contractor shall comply with the restrictions on use of Removable Media on Government Computers: Use of removable media on Government computers shall be prohibited. The following removable flash media are unauthorized on all Non-Secure Internet Protocol Router (NIPR), Secure Internet Protocol Router (SIPR), and Joint Worldwide Intelligence Communications System (JWICS) connected computers using Windows Operating Systems:

• Memory Sticks

• Thumb Drives

• Camera Flash Memory Cards

2.1.11.1 All other removable storage media not listed above (e.g., portable hard drives, portable electronic devices, Compact Disc – Rewritable (CD-RW), rewritable Digital Versatile Disc (DVD), floppy disk, etc.) must meet the requirements of applicable directives before they can be utilized. Personal flash media devices, such as iPods or MP3 (MPEG-1 Audio Layer-3) players, are also prohibited for use on AF networks.

2.1.12 Physical Security

The contractor shall be responsible for safeguarding all Government property provided for contractor use. Government facilities, property, and materials shall be secured at the close of each work period.

2.1.13 Key Control

The contractor shall establish and implement methods of ensuring that no keys/key cards issued to the contractor by the Government are lost or misplaced and are not used by unauthorized persons.

Note: All references to keys also include key cards. No keys issued to the contractor by the Government shall be duplicated. The contractor shall develop procedures covering key control that shall be included in the quality control plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas.

2.1.13.1 Loss of Keys

The contractor shall immediately report the loss of a duplicate key to the CO. In the event keys, other than master keys, are lost or duplicated, the contractor shall, upon written direction of the CO, rekey or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform rekeying. The total cost of rekeying or the replacement of the lock or locks shall be deducted from the monthly payment due the contractor when the Government performs the replacement of locks or rekeying. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the contractor.

2.1.13.2 Prohibition of Keys by Persons Other than Contractor Employees

The contractor shall prohibit the use of keys issued by the Government by any persons other than the contractor’s employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the CO.

2.1.13.3 Lock Combinations

The contractor shall establish and implement methods of ensuring lock combinations are only revealed to authorized persons. The contractor shall ensure lock combinations are changed when personnel granted access to the combinations no longer have a need to know such combinations.

These procedures shall be included in the contractor’s Quality Control Assurance Program Plan.

2.1.14. Operations Security (OPSEC)

OPSEC requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. The Critical Information List will be provided by the government IAW AFI 10-701, Operations Security.

2.1.14.1. OPSEC Plan

The contractor shall develop and implement an OPSEC Plan in its management of the system.

2.2 QUALITY CONTROL

2.2.1 Quality Control Program

In compliance with the clause entitled “Inspection of Services”, FAR 52.246-4 or FAR 52.246-5, the Contractor shall establish a complete Quality Control Program to ensure the requirements of this contract are provided as specified.

2.3 QUALITY ASSURANCE

The Government will periodically evaluate the Contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The Government representative will evaluate the contractor’s performance through intermittent on-site inspections of the Contractor’s quality control program and receipt of complaints from Government personnel. The Government may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints. Likewise, the Government may decrease the number of quality control inspections if merited by performance.

The Government will also investigate complaints received from various customers. The Contractor shall be responsible for initially validating customer complaints. However, the Government representative shall make final determination of the validity of customer complaint(s) in cases of disagreement with customer(s).

2.3.1 Metrics

The Government and the contractor shall share program performance databases to the greatest extent possible. The contractor and the Government shall develop mutually agreed upon program performance metrics that will provide the Government with insight into program performance.

2.3.2 Qualification Reviews

The Government reserves the option to audit the qualifications of any contractor personnel providing services to the Government under this contract who fit into one of the designations categorized in Labor Categories Descriptions.

2.3.3 Software Quality Assurance

2.3.3.1 The contractor shall establish and implement a Software Quality Assurance Plan (SQAP) as an appendix to the Software Development Plan. The SQAP shall define the techniques, procedures, and methodologies that will be used to assure timely delivery of the software that meets specified requirements within project resources. The contractor shall implement a software quality assurance program that assures:

• Quality is built into the software products.

• The creation of complete, correct, workable, consistent, and verifiable software.

• Implementation of plans, procedures, requirements, designs, and verification methods.

• Adherence to those software requirements, plans, procedures, and standards to successive products.

Note: The software quality assurance discipline consists of product and process assurance activities that are performed by the functions of software quality assurance, software quality engineering, and software quality control.

2.3.3.2 The contractor shall perform product assurance to verify that:

• All required plans (e.g., configuration management, risk management, software development plan) are documented, adhere to applicable standards and procedures, are mutually consistent, and are being executed.

• All software requirements are defined, traceable from one life cycle phase to another, and analyzed in a manner that is measurable or otherwise verifiable.

• Software products and related documentation have been evaluated, according to the software assurance plan.

• Project documentation, including plans, procedures, requirements, design, verification documentation, reports, schedules, and records and any changes to them are reviewed for impact to the quality of the product.

• Formal and acceptance software testing are witnessed by software assurance personnel to verify satisfactory completion and outcome.

• Lower level testing results and software development folders are updated, audited, and/or reviewed for completeness.

• Software quality metrics are in place and are used to ensure the quality and safety of the software products being delivered. Trends in software quality metrics are reported to assist in risk mitigation.

• The software development plans specify the standards and procedures for management, acquisition, engineering, and assurance activities.

• The software is verified (e.g., tested, analyzed, measured) for compliance with functional and performance requirements.

2.3.3.3 The contractor shall perform process assurance to verify:

• Those software life cycle processes employed for the project adhere to the applicable plans.

• Problems found with implementation of the software life cycle processes, including management, engineering, and assurance are documented, tracked, and resolved through the problem reporting and corrective action process and through discussions with the project manager.

• The software engineering practices, development environment, test environment, and libraries employed for the project adhere to applicable standards and procedures.

• Formal reviews and inspections are monitored and address software quality issues.

• All management, engineering, and assurance processes are audited for compliance with applicable plans.

• The software quality metrics process is assessed for compliance to appropriate documentation or requirements. Trending is accomplished following the defined software quality metrics process.

2.3.4 Quality Management

2.3.4.1 The Contractor quality management system shall be certified to AS 9100.

2.3.4.2 Plan Quality Management: The contractor shall identify quality requirements and/or standards for the project and its deliverables and document how the project will demonstrate compliance with quality requirements.

2.3.4.3 Perform Quality Assurance: The contractor shall audit the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used.

2.3.4.4 Control Quality: The contractor shall monitor and record results of executing the quality activities to assess performance and recommend necessary changes.

2.3.4.5 Reports: The contractor shall provide a quarterly quality report detailing subcontract audit reports, internal audit reports, external audit reports non-compliance findings and corrective action status.

2.4 CONTRACTING OFFICER REPRESENTATIVE (COR)

The COR(s) are the authorized Government representatives who will perform assessments of the contractor’s performance. Subsequent to contract award, the identity of the COR, with a letter defining their duties and authority will be promptly furnished to the successful bidder/offeror.

The COR(s) will inform the contract manager in person when discrepancies occur and will request corrective action. The COR(s) will make a notation of the discrepancy on their surveillance checklist with the date and time the discrepancy was noted and will request the contract manager, or authorized representative, to initial the entry on the checklist.

Any matter concerning a change to the scope, prices, terms, or conditions of this contract shall be referred to the CO and not to the COR. The contractor’s services shall be subject to review by the CO or authorized representative during the period of this contract and at all times and places.

2.5 HOURS OF OPERATION

2.5.1 Normal Hours of Operation

The contractor shall perform the services required under this contract during the following hours:

M-F, except federal holidays. However, contractor shall provide support as needed 24 hours a day, seven days a week to meet requirements created by emergencies and other contingencies.

The contractor may work, with prior approval of the CO, with extended hours to ensure timely completion of work.

2.5.2 Recognized Holidays

The contractor is not required to provide service on the following days: New Year’s Day, Martin Luther King Day, Presidents Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Days, Thanksgiving Day and Christmas Day. If the holiday falls on Saturday, it is observed on Friday. If the holiday falls on a Sunday, it is observed on Monday.

2.6 EMERGENCY SERVICES

On occasion, services may be required to support an activation or exercise of contingency plans outside the normal duty hours described within individual task orders.

2.7 CONSERVATION OF UTILITIES

The contractor shall instruct employees in…