FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 1 of 64

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)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 2 of 64

1.0 Ground Subsystem Support Contract General Requirements ............................................. 6

1.1 Scope ..................................................................................................................................... 6

1.2 Purpose .................................................................................................................................. 6

1.3 Background ........................................................................................................................... 6

1.4 ICBM Sustainment and Acquisitions Construct ................................................................... 7

1.4.1 Working Relationships ................................................................................................... 7

1.4.2 Technical Council .......................................................................................................... 8

1.4.3 Co-Location ................................................................................................................. 10

1.4.4 Ground Subsystem Contractor and Other Subsystem Contractors .............................. 10

1.4.5 Special Considerations ................................................................................................. 10

1.5 Ground Subsystem Description .......................................................................................... 11

1.5.1 Launch Control Center (LCC) ..................................................................................... 12

1.5.2 Launch Facility (LF) .................................................................................................... 12

1.5.3 Ground Support Equipment (GSE) .............................................................................. 12

1.5.4 Joint Mission Division ................................................................................................. 12

1.6 Applicable Documents ........................................................................................................ 13

1.6.1 Compliance Documents ............................................................................................... 13

1.6.2 Reference Documents .................................................................................................. 14

1.7 Services Summary .......................................................................................................... 18

1.8 Property Management .................................................................................................... 19

1.8.1 Government-Furnished Property (GFP) and Services ................................................. 19

1.8.2 Nuclear Weapons-Related Material (NWRM) ............................................................ 20

2.0 General Information ................................................................................................................ 24

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 3 of 64

2.1 Security Requirements ........................................................................................................ 24

2.1.1 Intelligence Information ............................................................................................... 24

2.1.2 Base Access ................................................................................................................. 25

2.1.3 Unescorted Entry ......................................................................................................... 25

2.1.4 Security Management .................................................................................................. 25

2.1.5 Communications Security ............................................................................................ 25

2.1.6 Joint Personnel Adjudication System .......................................................................... 25

2.1.7 Security Clearance ....................................................................................................... 25

2.1.8 Security Training ......................................................................................................... 26

2.1.9 Handling of Classified Material ................................................................................... 26

2.1.10 Personnel Reliability Program ................................................................................... 26

2.1.11 Removable Media ...................................................................................................... 26

2.1.12 Physical Security ........................................................................................................ 27

2.1.13 Key Control ................................................................................................................ 27

2.1.13.1 Loss of Keys ........................................................................................................... 27

2.1.13.2 Prohibition of Keys by Persons Other than Contractor’s Employees ..................... 27

2.1.13.3 Lock Combinations ................................................................................................. 28

2.2 CYBERSECURITY REQUIREMENTS ........................................................................ 28

2.2.6 Board Participation ...................................................................................................... 28

2.2.7 Change Proposals ......................................................................................................... 29

2.2.8 Cybersecurity Documentation ..................................................................................... 29

2.2.9 Cybersecurity Implementation and Controls ............................................................... 29

2.2.11 Information System Security Management ............................................................... 30

2.2.12 System Security Engineering ..................................................................................... 30

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 4 of 64

2.2.13 Critical Program Information Protection ................................................................... 30

2.2.14 Government Foreign Disclosure ................................................................................ 30

2.2.15 System Safety Working Group (SSWG) Support ...................................................... 30

2.2.16 Vulnerability Assessments ......................................................................................... 30

2.2.17 Vulnerability Inspections ........................................................................................... 31

2.2.18 Cyber-related Investigations ...................................................................................... 31

2.2.19 USCYBERCOM and Information Assurance Vulnerability Advisory Support ........ 31

2.3 Quality Control ................................................................................................................... 31

2.3.1 Quality Control Program.............................................................................................. 31

2.4 Quality Assurance ............................................................................................................... 31

2.4.1 Metrics ......................................................................................................................... 32

2.4.2 Qualification Reviews .................................................................................................. 32

2.4.3 Software Quality Assurance ........................................................................................ 32

2.5 Contracting Officer Representative (COR) ........................................................................ 33

2.6 Hours of Operation ............................................................................................................. 34

2.6.1 Normal Hours of Operation ......................................................................................... 34

2.6.2 Recognized Holidays ................................................................................................... 34

2.7 Emergency Services ............................................................................................................ 34

2.8 Conservation of Utilities ..................................................................................................... 34

2.9 Records ............................................................................................................................... 34

2.10 Environmental controls ..................................................................................................... 34

2.10.1 Compliance with Laws and Regulations .................................................................... 34

2.10.2 Notification of Environmental Spills ......................................................................... 35

2.10.3 Materiel Storage and Usage ....................................................................................... 35

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 5 of 64

2.11 Government Observations ................................................................................................ 35

2.13 Training ............................................................................................................................. 36

2.14 Partnering Agreement ....................................................................................................... 37

2.15 Antiterrorism Considerations ............................................................................................ 37

2.16 Cont. of Essential DOD Contractor Services During Crisis ............................................. 37

2.17.2 Site Visits ................................................................................................................... 38

2.18 Associate Contractor Agreement ...................................................................................... 38

3.0 Appendices .............................................................................................................................. 40

APPENDIX A: ACRONYMS AND ABBREVIATIONS LIST .............................................. 40

APPENDIX B: WORK BREAKDOWN STRUCTURE ......................................................... 51

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION ............ 52

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ....................................................................................................................... 62

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................. 63

APPENDIX F: ATTACHMENT LIST .................................................................................... 64

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 6 of 64

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 11-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 Ground Subsystems Support Contract (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).

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 GSSC contractor.

1.3 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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 7 of 64

• 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 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 weapon system until 2036.

1.4.1 Working Relationships

Figure 1. ICBM Sustainment and Acquisition Construct

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 8 of 64

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, hardness (NH&S), corrosion, environmental and system safety. The Contractor will transfer industrial ICBM technical expertise and knowledge to the ICBM organic workforce through briefings, training sessions, hands-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 E, across the Ground Subsystem.

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 produce requirements and other documentation for subsystem acquisitions that would create an Organizational Conflict of Interest (OCI) if produced by the subsystem contractor. As Ground 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 weapon system, 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 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, GSSC 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.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 9 of 64

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. Examples of expected members are Finite Element Analysis provider, C3 provider, ICBM crypto/codes 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.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 at the SECRET level 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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 10 of 64

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 possible satellite office (of limited staff) 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 weapon system management. ICBMSD 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, 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 near Hill 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 near Hill AFB.

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 weapon system. The criticality of ensuring

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 11 of 64

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 weapon system 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 modifications do not have a negative impact on Ground subsystems, as well as the weapon system 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 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 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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 12 of 64

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), and Ground Support Equipment. 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.

1.5.2 Launch Facility (LF)

The Launch Facility (LF) Branch consist of Acquisition Pprograms and three Sections in support of the MMIII Weapon System. 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 PTIII, TE, MT, PMT, PSRE Trailer, Bunker Winch, GMMP, GMATS, Pipe Pusher, GMLEC, SELM, etc. GSE also included all of the weapon system trainer. This also includes answering ETARs and 202s.

1.5.4 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 Launce Control System (ALCS) efforts will be supported under JMD. All applicable standards and supporting documents apply to JMD effort(s).

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 13 of 64

1.6 APPLICABLE DOCUMENTS

1.6.1 Compliance Documents

The following table contains the documents that require ICBM Program Office compliance for all MMIII weapon system sustainment activities. Contractor will use most current version of 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 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-R Nuclear Weapons Personnel Reliability

Program (PRP) Regulation DOD 5220.22-M and Supplement 1 National Industrial Security Program

Operating Manual DODD 3150.2 DOD Nuclear Weapon System Safety

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)

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 14 of 64

Document Number Document Title DODM 5200.1 DOD Information Security Program:

Overview, Classification, and Declassification

S-133-128 System Specification for MMIII, (WS-133A-M, Wings I, III, V) (WS-133B, Wing I) End Item Specifications

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 20-110 Nuclear Weapons-Related Materiel

Management AFI 24-203 Preparation and Movement of Air Force

Cargo AFI 31-401 Information Security Program Management AFI 32-7086 Hazardous Materials Management AFI 36-2251 Management of Air Force Training

Programs AFI 63-101 Integrated Life Cycle Management AFI 63-125 Nuclear Certification Program AFI 63-131 Modification Program Management AFI 63-143 AMR / CAM AFI 91-101 Air Force Nuclear Weapons Surety

Program AFI 91-102 Nuclear Weapon System Safety Studies,

Operational Safety Reviews, and Safety Rules

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 15 of 64

Document Number Document Title 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 99-103 Capabilities-Based Test and Evaluation AFMAN 23-110 United States Air Force Supply Manual AFMAN 91-118 Safety Design and Evaluation Criteria for

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

Nuclear Weapon Systems Software 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 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-1701 Program Protection Plan 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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 16 of 64

Document Number Document Title 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.1 Joint Nuclear Weapons Development

Studies and Engineering Projects DODI 5030.55 DOD Procedures DOD- Department of

Energy (DOE) Nuclear Weapons Life-Cycle Activities

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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 17 of 64

Document Number Document Title 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 99-02 Test and Evaluation Nuclear Hardness

Critical Item (HCI) Parts Procurement ICBMSD OI 99-103 Test and Evaluation 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 Defense Acquisition Guidebook (DAG) 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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 18 of 64

Document Number Document Title 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

SBICBM-STD-01 Systems Requirements Analysis for Silo-Based ICBM Systems

SBICBM-STD-01 Systems Requirements Analysis for Silo-Based ICBM Systems

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-2-31 Weapon System Hardness Preservation and

Installation Hardware Minuteman III Weapon System

Sustainment Systems Engineering Plan 62-SEP

1.7 SERVICES SUMMARY

Below are performance standards (metrics) the Government will use for monitoring contractor performance on critical tasks. These metrics are a meaningful measure of contractor performance and conform to commercial standards to the maximum extent practicable. This PWS is based upon the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. The Government Contracting Officer Representative (COR) will audit the contractor’s processes to ensure they are in place and will use the data from the contractor inspection reports to assess contractor performance. If the contractor does not have processes in place or meet the standards listed, then the contractor shall establish a corrective action plan to correct the deficiency.

Table 1. – SERVICES SUMMARY MATRIX

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 19 of 64

Performance Objective

PWS Para Performance Threshold Frequency

Quality: Quality of work and level of support met task requirements. Work required little or no rework and services met or exceeded expectations. Deliverables were complete and accurate to meet customer objectives.

No more than two (2) verified formal customer complaints/contract discrepancy reports per quarter.

The contractor must resolve or provide resolution plan for customer complaints within 10 working days of receipt.

If Government requires peer review, then ensure peer review has occurred before initial delivery to Government.

Customer Surveys

COR will conduct periodic interviews/surveys with Government personnel to ensure quality of work and services received are satisfactory

Schedule: Deliverables are completed in a timely manner.

98% of requests for products received on agreed upon date.

100% of requests for products/services received on agreed upon date + 5 working days.

100% of comments and edits are incorporated per CDRL requirements.

Customer Surveys

COR will conduct periodic interviews/ surveys with Government personnel to ensure items are being delivered in accordance with the CDRL requirements

Cost Control Contractor performs tasks within +/-10% of allocated hours and schedule.

Periodic inspections

COR will conduct periodic interviews/surveys

1.8 PROPERTY MANAGEMENT

1.8.1 Government-Furnished Property (GFP) and Services

Contractors shall be responsible for accurate and complete property management of all GFP/Materials and shall provide reports of all property in their possession upon request.

“Government-furnished property” means property in the possession of, or directly acquired by, the Government and subsequently furnished to the contractor for performance of a contract. GFP

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 20 of 64

includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. GFP also includes contractor-acquired property if the contractor acquired property is a deliverable under a cost contract when accepted by the Government for continued use under the contract.

“Equipment” means a tangible item that is functionally complete for its intended purpose, durable, nonexpendable, and needed for the performance of a contract. Equipment is not intended for sale, and does not ordinarily lose its identity or become a component part of another article when put into use. Equipment does not include material, real property, special test equipment or special tooling.

1.8.1.1 The Contractor shall assist the Government to assess and determine the GFP (equipment, material, and information) required. Note: Each time a piece of equipment is added or deleted, the Government will not update the listing with a contract modification.

1.8.1.2 The Contractor shall identify any items not listed, but necessary, for performance of Grounds Subsystem functions. The Contractor shall determine actions required to acquire those items not listed.

1.8.1.3 The Contractor is granted authority to dispose of miscellaneous non-stock listed items of Government Furnished Property (GFP) which will have no future use in the end product ultimately being delivered to the government. Examples include (but are not limited to) cut up flexes, screws, washers, gaskets, foam, etc. The items to be disposed of are of nominal value and will not exceed $100 per item.

1.8.2 Nuclear Weapons-Related Material (NWRM)

The contractor (to include all subcontractors) shall be compliant with all aspects of AFI 20-110, NWRM Management, and its AFMC supplement that are applicable to contracted activities, and as specifically stated below.

Note: This instruction and related AF policies are available at the following link: http://static.e-publishing.af.mil/production/1/af_a4/publication/afi20-110/afi20-110.pdf

1.8.2.1 Contractor Responsible Officer (RO)

1.8.2.1.1 The contractor shall assign an NWRM RO to perform the following duties relative to NWRM assets, under their control, within their facilities to include subcontract facilities:

1.8.2.1.2 Exercise custody, care, safekeeping/security over property entrusted to his or her possession or under his or her supervision, and place specific emphasis on proper recording of transactions affecting NWRM under their functional control and problems or discrepancies that may require corrective action or adjustment. Report these directly to the designated Government NWRM Accountable Officer (NWRMAO) and Item Manager (IM).

1.8.2.1.3 Ensure auditable and/or accountable records are maintained, controlled, secured, and signed by appointed representatives.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 21 of 64

1.8.2.1.4 Manage interactions, transactions, and validate management processes to control materiel and auditable/accountable documents affecting supplies/materiel within their functional processes or control.

1.8.2.1.5 Assist the NWRMAO in conducting and reconciling inventories of all NWRM assets under the contractor’s control.

1.8.2.1.6 Perform root cause analysis (RCA) and research for any NWRM discrepancies at the request of their NWRMAO.

1.8.2.1.7 The contractor shall provide to their NWRMAO a copy of the RO appointment letter upon completion and maintain a list of contractor personnel authorized to handle NWRM.

1.8.2.2 Mandatory NWRM Training

1.8.2.2.1 The contractor RO and all contractor employees handling NWRM assets shall complete NWRM Fundamentals Course training annually. See AFI 20-110, Nuclear Weapons-Related Materiel Management Chapter 9 for training requirements.

Note: Current requirements are NWRM training shall occur on an annual basis. However, a two-phase certification program is projected to establish near-term and AFI 20-110, Nuclear Weapons-Related Materiel Management will be updated to reflect the certification program. Training will be through the Advanced Distributed Learning Service (ADLS). If ADLS is not accessible except through a military network, the Government will provide either briefing material or a hardcopy of the required training.

1.8.2.2.2 The contractor shall track and maintain a report of all contractor employee annual training completions and provide report to the NWRMAO upon request.

1.8.2.3 Mandatory Contractor Reporting of All NWRM Shipments

1.8.2.3.1 The contractor shall report all NWRM shipments and receipts, repair actions, and demilitarization actions within the Commercial Asset Visibility (CAV) AF system by serial number (S/N). If the contractor will be performing CAV AF entries directly, the contractor shall identify two primary and two alternate personnel to be trained on CAV AF and be responsible for all CAV AF transactions and reporting accuracy.

1.8.2.3.2 The contractor shall track and report all transactions and shipments of all NWRM assets, by S/N at a minimum, and Unique Item Identifier (UII) if available. If the NWRM asset moves between the GSSC contractor and its subcontractors facilities to different sites, those movements shall be tracked and reported to the IM and NWRMAO at the time the movement is initiated.

1.8.2.4 NWRM Marking and Packaging

1.8.2.4.1 For all new NWRM items the contractor is marking, DFARS 252.211-7003I (4) shall apply. When the technical data package does not specify the marking location/method for the

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 22 of 64

UII, the contractor shall notify the AF through established contractual notification procedures or the Contracting Officer (CO) so AF personnel can provide proper instructions.

1.8.2.4.2 Packaging and Documentation Procedures:

1.8.2.4.2.1 The contractor shall follow all procedures defined in AFI 20-110, Nuclear Weapons-Related Materiel Management Chapter 4.

1.8.2.4.2.2 The contractor shall contact the packaging specialist for the specific stock number with any packing questions or problems and follow specific instructions within the AFMC Form 158, Packaging Requirements included in the contract.

1.8.2.5 IUID Nameplates and Product Marking

1.8.2.5.1. For applicable items provided to the Government under this contract, the contractor shall ensure compliance with MIL-STD 130, Identification Marking of U.S. Military Property; Technical Order (TO) 00-25-260, Asset Marking and Tracking Item Unique Identification Marking Procedures; and Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.211-7003.

1.8.2.5.2 The contractor shall provide an Item Unique Identification (IUID) Plan, which covers asset marking and tracking and IUID marking procedures.

1.8.2.5.3 The contractor shall register IUID data in the IUID Registry IAW DODI 8320.04, Item Unique Identification (IUID) Standards for Tangible Personal Property.

1.8.2.6 NWRM Storage Management

The contractor shall maintain security and access control of facilities housing NWRM and/or where NWRM work is performed IAW AFI 20-110, Nuclear Weapons-Related Materiel Management Chapter 5 in particular, provisions for indoor storage and asset segregation.

1.8.2.7 Movement, Shipment, and Receipt Processing

1.8.2.7.1 The contractor shall coordinate NWRM asset movements in advance with the NWRMAO and IM, and follow movement instructions issued by the IM, Production Management Specialist (PMS), or equivalent for NWRM movements, including between the GSSC contractor and its subcontractors facilities. The DD Form 1348-1A, Issue Release/Receipt Document, is required for all shipments between contractor and Government facilities, and between the GSSC contractor and its subcontractors facilities.

1.8.2.7.2 The contractor shall request that the IM provide specific instructions and authorize use of a manual DD Form 1348-1A for shipments where the DD Form 1348 1A cannot be AF system-generated. The contractor shall use the requisition document number, provided by the IM as the Transportation Control Number (TCN). The DD Form 1149, Requisition and Invoice/Shipping Document are not authorized for shipping NWRM.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 23 of 64

1.8.2.7.3 The contractor shall provide, in addition to standard entries on the DD Form 1348-1A, a printed S/N list along with the shipping document (separate S/N listing is not required when all S/Ns are printed on the DD Form 1348-1A) and stamp the form with the statement “Classified NWRM Item” in red ink.

1.8.2.7.4 When preparing NWRM assets for shipment the contractor shall ensure NWRM assets are properly packaged and marked IAW Chapter 4 of AFI 20-110, Nuclear Weapons-Related Materiel Management.

1.8.2.7.5 The contractor shall perform shipment planning and prepare and/or maintain movement/shipment documents IAW the Defense Transportation Regulation (DTR) Part II and AFI 24-203, Preparation and Movement of Air Force Cargo. For all Continental United States (CONUS) movements, use of Transportation Protective Services (TPS1), to include satellite monitoring is mandatory.

1.8.2.7.6 The contractor shall accomplish NWRM transportation in-check at the time of conveyance off-load IAW AFI 24-203, Preparation and Movement of Air Force Cargo Chapter 5. NWRM receiving shall be accomplished IAW AFMAN 23-110, United States Air Force Supply Manual, Volume I, Part I, Chapter 19 and AFI 24-203, Chapter 5. In the event of a discrepancy, the contractor shall complete a Supply Discrepancy Report (SDR) IAW AFMAN 23-110, United States Air Force Supply Manual Volume 2, Part 2, and Chapter 10.

1.8.2.7.7 If discrepancies are found, the contractor shall notify the shipping and receiving NWRMAO, transportation office, IM, and Defense Contract Management Agency (DCMA) via e-mail within 24 hours. Completion of notification will be based on when the email is sent from the contractor and not when interested parties do read it. The contractor shall follow NWRMAO or IM instructions for discrepancy reporting and documentation.

1.8.2.7.8 If a discrepancy is found between the IM/PMS or equivalent and contractor’s inventory balance records, and the error is due to contractors omission or error in CAV AF input, the contractor shall correct the CAV AF transactions within 24 hours of notification by the owning organization PMS or IM.

1.8.2.7.9 Within 24 hours of receipt of NWRM, the contractor shall record receipt in CAV AF, and notify the NWRMAO via e-mail, to include the shipment TCN, total quantity received, and individual S/Ns as listed on the shipping document and DD Form 1500-series condition tag(s).

1.8.2.7.10 For all new NWRM assets delivered to the AF under a DD Form 250 (or Wide Area Workflow, WAWF), Material Inspection and Receiving Report, the contractor shall provide the IM the DD Form 250 (or WAWF) within 24 hours of asset acceptance.

1.8.2.8 Contract Depot Maintenance/Repair

1.8.2.8.1 The contractor shall ensure S/N tracking and accountability are maintained for all NWRM through the entire repair process from the time it is received until it is either expended during use or returned to the AF supply/stock.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 24 of 64

1.8.2.8.2 The contractor shall report all repair activity for all NWRM assets through the CAV AF system to include shipments, receipts, inductions, demilitarization, and repair work.

1.8.2.9 Items No Longer Required

The contractor shall pick up supply accountable records within 24 hours of disassembly or removal for any NWRM item not subsequently reinstalled or reassembled in the same repair action or maintenance process (grouping of maintenance tasks). Such items shall be properly tagged to ensure, at a minimum, item identification, S/N tracking, part number, cage code, and condition code status. The contractor shall promptly mark unserviceable NWRM items with the correct condition and ensure the items are not co-mingled with serviceable items or other unserviceable items of another condition.

1.8.2.10 Inventories and Audits

All NWRM at contractor and subcontractor and subcontractors facilities shall be subject to inventory requirements as specified in AFI 20-110, Nuclear Weapons-Related Materiel Management Chapter 8. A complete physical inventory count of NWRM by S/N and/or UII shall be conducted semiannually IAW the procedures in AFMAN 23 110, United States Air Force Supply Manual Volume I, Part I, Chapter 6.

1.8.2.11 Demilitarization and Disposal of NWRM

1.8.2.11.1 All NWRM declared excess to AF requirements shall be demilitarized, destroyed, and disposed of by the contractor as directed by the AF. Demilitarization and disposal of NWRM is required within 2 years of excess/condemned determination.

1.8.2.11.2 The contractor shall coordinate with the Government for demilitarization/disposition instructions and scheduling of Government witnesses for final demilitarization/destruction. An AF, DCMA, or National Nuclear Security Administration (NNSA) representative shall witness NWRM assets demilitarized/destroyed by contractors. The contractor shall sign as the certifier and the AF, DCMA, or NNSA representative will verify asset demilitarization.

1.8.2.11.3 The contractor is responsible for providing the completed Defense Reutilization and Marketing Service (DRMS) Form 145, Demilitarization Certificate to the IM within 24 hours.

2.0 GENERAL INFORMATION

2.1 SECURITY REQUIREMENTS

2.1.1 Intelligence Information

A Top Secret/Sensitive Compartmented Information/Restricted Data/Special Access Program/Formerly Restricted Data (TS/SCI/RD/SAP/FRD) clearance is required to perform the work under this task. Depending on the data need, special access may be required for the specific programs.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 25 of 64

This project and the work being proposed may be classified and Need-To-Know (NTK). The following Security Classification Guides (SCGs) will be followed:

• Applicable joint DoD/DOE classification guides • Applicable DoD weapon delivery SCGs • Applicable DOE weapon SCGs

This task requires access to SCI by contractor personnel.

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). The requests shall be submitted to the ICBMSD Security Office to provide to the 75th Security Forces Squadron (SFS) 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.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 26 of 64

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 31-401, Information Security Program Management; DODM 5200.1, DOD Information Security Program: Overview, Classification, and Declassification; 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 31-401, Information Security Program Management DODM 5200.1, 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-R, Nuclear Weapons Personnel Reliability Program (PRP) Regulation.

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:

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 27 of 64

• 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’s 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’s employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the CO.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 28 of 64

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.2 CYBERSECURITY REQUIREMENTS

The contractor shall support the government, as directed, in cybersecurity activities related to Grounds Subsystems to ensure the appropriate level of confidentiality, integrity, and availability is maintained proportionally with the importance and sensitivity of the information and information assets. This support includes, but is not limited to, documenting and resolving threats and vulnerabilities; the trustworthiness of users and interconnecting systems; the impact of impairment or destruction to the DOD information system; and its cost effectiveness IAW Department of Defense Instruction (DODI) 8500.01, Cybersecurity.

2.2.1 The contractor shall perform all applicable system security tasks required for Assessment and Authorization as identified within DODI 8510.01, Risk Management Framework (RMF). These efforts will enable cybersecurity assessable systems to obtain and maintain authorization through a cognizant cybersecurity Authorization Official. Authorizations required may range from Interim Authority to Test (IATT) to an Authority to Operate (ATO). Assistance with other authorizations such as an Authorization to Connect (ATC), certificate of net worthiness, emergency action message (EAM) certification, Joint Interoperability Test Center (JITC) certification, and security test and evaluation (ST&E), may also be requested. 2.2.2 The contractor shall conduct system Assessment and Authorization activities under the direction of the cognizant AF Authorizing Official (AO) or with the Defense Security Service (DSS), whichever is applicable, IAW the DOD 5220.22-M and Supplement 1, National Industrial Security Program Operating Manual (NISPOM).

2.2.3 The contractor shall conduct Government-owned system security assessment and authorization support, documentation development, and testing based on DODI 8510.01, RMF for DoD Information Technology (IT) and DODI 8500.01, Cybersecurity.

2.2.4 The contractor shall assess changes to the authorized system, changed risks, or security-related impacts.

2.2.5 The contractor shall develop, maintain, and submit updated artifacts to support DODI 8510.01, RMF for DoD IT.

2.2.6 Board Participation

The contractor shall, with Cybersecurity certified personnel, support SSWG, Engineering Review Boards (ERB), Deficiency Review Boards (DRB), Risk Management Boards (RMB), and other meetings on an as needed basis and as determined by the Government.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 29 of 64

2.2.7 Change Proposals

The contractor shall evaluate change proposals, e.g., ECPs, task change proposals (TCP), configuration change proposals (CCP), waivers, and deviations. Evaluations shall address cost, schedule, performance, and Cybersecurity impacts/risks, and meet change board documentation requirements.

2.2.8 Cybersecurity Documentation

The contractor shall conduct and document security testing using Defense Information Systems Agency (DISA)-approved tools, guides, etc., IAW DODI 8500.01, Cybersecurity. Contractor personnel performing Cybersecurity functions as defined in Department of Defense (DOD) 8570.01-M, Information Assurance (IA) Workforce Improvement Program, Table AP3.T1, shall satisfy both preparatory and sustaining DOD Cyber training and certification requirements per DODD 8570.01-M. Personnel performing privileged functions shall be certified at least to Information Assurance Technical (IAT) Level II (DOD 8570.01-M Table Ap3.T1). New contractor hires performing privileged access Cybersecurity functions will be required to already be compliant with DODD 8570.01-M, IA Training, Certification, and Workforce Management and DOD 8570.01-M for IAT Level II (not acquired at Government expense).

2.2.9 Cybersecurity Implementation and Controls

The contractor shall identify, design for, and implement detailed Cybersecurity requirements, anti-tamper measures, red-black separation, and supply chain management. The contractor shall address the DODI 8500.01, Cybersecurity Implementation and Cybersecurity controls.

2.2.10 Program Protection Plan

The contractor shall support the Government’s program protection planning, implementation, and sustainment. Included is program protection for the resources and facilities associated with the design, development, production, integration, assembly, certification artifact developments, test operation, sustainment, and retirement. Establish the appropriate administrative technical and physical safeguards to protect any and all Government data, to ensure its confidentiality, integrity, and availability. Provide for personnel security, information systems security, and physical security as mandated in the DOD 5220.22-M and Supplement 1, National Industrial Security Program Operating Manual (NISPOM) and defined in the applicable Department of Defense (DD) Form 254, Contract Security Classification Specification.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 30 of 64

2.2.10.1 The contractor shall support internal setup and Government approval of classified computer processing, classified document control administration, personnel security clearance administration, processing incoming/outgoing classified and unclassified visits, and transmission security, including subcontractor facilities. The contractor shall provide for capital improvements related to security (safes, alarms, entry controls, etc.), security education training, temporary duty to support program protection, cost of transporting classified components, and security equipment (Secure Terminal Equipment (STE), computer hardware/software), as well as all security-related installation, operations, and maintenance.

2.2.11 Information System Security Management

The contractor shall perform all Information System Security Manager (ISSM) tasks IAW AFI 17-101, section 2.15 and 2.16.

2.2.12 System Security Engineering

The contractor shall perform all systems security engineering (SSE) tasks IAW AFI 17-101, section 2.17; MIL-HDBK-1785, Defense Acquisition Guidebook (DAG); and AFPAM 63-113, Program Protection Plan for Lifecycle Management.

2.2.13 Critical Program Information Protection

The contractor shall protect critical program information (CPI), technologies, systems, and resource assets, and assess protection threats and countermeasures to those CPI assets IAW the PPIP (PCO-approved version).

2.2.14 Government Foreign Disclosure

The contractor shall support Government Foreign Disclosure reviews and processes.

2.2.15 System Safety Working Group (SSWG) Support

The contractor shall participate in the Minuteman Systems SSWG in conjunction with technical working groups when an applicable subsystem program is under consideration. Each SSWG will be conducted IAW the SSWG charter. Program Protection Plan (PPP) will be revised based on contractor Program Protection Implementation Plan (PPIP) and joint working sessions.

2.2.16 Vulnerability Assessments

The contractor shall document and analyze all vulnerability attacks to ensure that the security controls in place provide the required protection and, where necessary, provide recommendations and direction to fortify Cyber controls. The contractor will also coordinate with all necessary parties to assist in the execution of penetration and any/all other necessary system testing. The contractor shall provide recommendations to the Government based on relevant guidance and policy.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 31 of 64

2.2.17 Vulnerability Inspections

The contractor shall continuously ensure that all inspections, resolution of violations and/or abnormal events, authorizations, certifications, documents, and requirements to keep all systems continuously operational from a Cyber perspective are current, fully valid, and/or settled.

2.2.18 Cyber-related Investigations

As needed, the contractor shall research and investigate all Cyber-related matters through relevant channels including, but not limited to: all facets of the DoD, Designated Approving Authority (DAA), National Security Agency (NSA), DISA, and all other relevant elements of the US Government at large.

2.2.19 USCYBERCOM and Information Assurance Vulnerability Advisory Support

In coordination with appropriate Government IT specialists, the contractor shall ensure that all USCYBERCOM and other Information Assurance Vulnerability Advisories (IAVAs) are reviewed and complied with in a timely manner.

2.3 QUALITY CONTROL

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

The Contractor shall supply the original copy of the quality control plan within the technical proposal.

The PCO will notify the Contractor of acceptance or required modifications to the plan before the contract start date. The Contractor shall make appropriate modifications (at no additional costs to the Government) and obtain acceptance of the plan by the PCO before the start of the first operational performance period.

2.4 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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 32 of 64

Government representative shall make final determination of the validity of customer complaint(s) in cases of disagreement with customer(s).

2.4.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.4.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.4.3 Software Quality Assurance

2.4.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.4.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.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 33 of 64

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

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 34 of 64

2.6 HOURS OF OPERATION

2.6.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.6.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.7 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.8 CONSERVATION OF UTILITIES

The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that prevent waste of utilities to include the following:

• Lights shall be used only in areas where and when work is actually being performed. • Mechanical equipment controls for heating, ventilation, and air conditioning systems shall

not be adjusted by the contractor or by contractor employees unless authorized. • Water faucets or valves shall be turned off after required use has been accomplished. • Government telephones shall be used only for official Government business.

2.9 RECORDS

The contractor shall be responsible for creating, maintaining, and disposing of only those Government-required records that are specifically cited in this PWS, applicable to the work accomplished under this PWS, or required by the provisions of applicable publications and forms. If requested by the Government, the contractor shall provide the original record or a reproducible copy of any such record within 5 working days of receipt of the request.

2.10 ENVIRONMENTAL CONTROLS

2.10.1 Compliance with Laws and Regulations

The contractor shall be knowledgeable of and comply with all applicable Federal, State, and Local laws, regulations, and requirements regarding environmental protection. In the event

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 35 of 64

environmental laws/regulations change during the term of this contract, the contractor is required to comply as such laws come into effect. If there is an increase or decrease in cost because of the change, the contractor shall inform the CO pursuant to notice requirements and negotiate a modification to the contract.

2.10.2 Notification of Environmental Spills

If the contractor spills or releases any substance listed in 40 Code of Federal Regulations (CFR) 302 into the environment, the contractor or its agent shall immediately report the incident to Hill AFB Command Post at (801) 777-3007. If the spill is located on or near Hill AFB, notify the Hill AFB Fire Department or the local Fire Department closest to the incident by calling 911. The liability for the spill or release of such substances rests solely with the contractor and its agent.

2.10.3 Materiel Storage and Usage

The contractor shall follow manufacturer’s guidelines and professional recommendations for control of humidity, temperature, cleanliness, and materials handling. This includes hazardous materials.

2.11 GOVERNMENT OBSERVATIONS

Government personnel, other than COs and CORs, may from time to time, with CO coordination, observe contractor operations. However, these personnel may not interfere with contractor performance or make any changes to the contract.

2.12 SAFETY REQUIREMENTS

2.12.1 In performing work under this contract, the contractor shall:

2.12.1.1 Conform to the safety requirements contained in the contract for all activities related to the accomplishment of the work

2.12.1.2 Take such additional immediate precautions as the CO may reasonably require for safety and mishap prevention purposes.

2.12.1.3 Develop and provide (at the start of the first operational performance period) a safety plan, IAW Appendix C, for the protection of Government facilities and property and to provide a safe work environment for contractor personnel.

2.12.1.4 Provide protection to Government property to prevent damage during the period of time the property is under the control or in possession of the contractor.

2.12.1.5 Include a clause in all subcontracts to require subcontractors to comply with the safety provisions of this contract as applicable.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 36 of 64

2.12.1.6 Record and report promptly (within one hour) to the CO or designated Government representative (GR), all available facts relating to each instance of damage to Government property or injury to either contractor or Government personnel.

2.12.1.7 In the event of an accident/mishap, take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence until released by the accident/mishap investigative authority through the CO.

2.12.1.8 If the Government elects to conduct an investigation of the accident/mishap, the contractor shall cooperate fully and assist Government personnel in the conduct of investigation until the investigation is completed.

2.12.1.9 Include a clause in each applicable subcontract requiring the subcontractor's cooperation and assistance in accident reporting and investigation.

2.12.1.10 If the Contractor provides more than 1000-hours of on-base support during any quarter, then the USAF Voluntary Protection Program (VPP) applies to all Contractor personnel performing services on HAFB. In this case, the Contractor shall:

• Be familiar with VPP requirements, which can be found at http://www.osha.gov/dcsp/vpp/index.html.

• Submit a safety and health plan to the PCO within 10 days after contract award. • The plan shall also be made available to the installation safety office for acceptance prior to

contract performance. • Submit their Total Case Incidence Rate (TCIR), Day Away, Restricted, and /or Transfer Case

Incident Rate (DART) rate and Occupational Safety and Health Act (OSHA) Form 300 A to the PCO by 15 JAN of each year within the contract period-of-performance

• Ensure its quality control plan identifies the processes and procedures the Contractor will use to track compliance with their Safety and Health Plan, along with the corresponding corrective processes and procedures.

• Ensure VPP requirements are included in subcontractor PWSs/Statements of Work/Statements of Objectives whenever that subcontractor meets the requirements in this paragraph.

• Ensure its employees and subcontractors promptly report pertinent facts regarding mishaps involving reportable damage or injury.

• Ensure any employees and subcontractors involved with an on-base mishap cooperate in any safety investigation, to include toxicology testing.

2.12.1.11 The contractor shall provide an accident/incident and/or mishap report in case of safety related incident.

2.13 TRAINING

The contractor shall ensure all employees have been properly trained to safely and effectively perform their assigned duties.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 37 of 64

2.14 PARTNERING AGREEMENT

The PCO may require a partnering agreement between the Government and the contractor to ensure cooperation and sound partnership of all parties involved in the execution of this contract. Partnering is the creation of a Government-Contractor relationship that promotes achievement of mutually beneficial goals. It involves an agreement in principle to share the risks involved in completing the project and to establish and promote a nurturing partnership environment.

Representatives from each organization are encouraged to participate in developing the partnering agreement. Suggested representation is the civil engineer manager, the Government inspector, the Government contract administrator, the contractor’s manager, and the contractor’s quality control person.

When the partnering agreement is required, all costs shall be shared equally between the Government and the contractor. This group is responsible for developing a formal partnering agreement that shall be signed by all parties involved. The agreement shall contain as a minimum: specific goals to be reached and a list of objectives to reach the goals, a set of metrics to evaluate the objectives, a frequency for meetings to review the metrics, and a statement of cooperation to execute the terms of the agreement.

2.15 ANTITERRORISM CONSIDERATIONS

For working locations on an AF installation, the contractor shall follow the Antiterrorism Considerations requirements according to AFI 10-245, Antiterrorism (AT).

2.16 CONT. OF ESSENTIAL DOD CONTRACTOR SERVICES DURING CRISIS

In accordance with DODI 1100.22, Policy and Procedures for Determining Workforce Mix, this requirement is not considered mission essential.

2.17 PHASE OUT/FOLLOW-ON

2.17.1 Phase-out Familiarization ActivitiesIf there is a change in the contractor or if the operation reverts to total organic support, the incumbent contractor shall provide familiarization to the Government and the follow-on contractor. During the phase-out familiarization period, the incumbent contractor shall:

• Be fully responsible for the continuation of all contracted services and maintain the existing staff on-site throughout the phase-out period. No additional staffing requirements are anticipated to complete the phase-out activities to the follow-on contractor. • Respond to the Government with a proposal and schedule for phase-out, detailing a clear, orderly workload and responsibility transition from the contractor to the follow-on contractor(s).

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 38 of 64

• Designate a phase-out project manager to work with the follow-on contractor throughout the phase-out.

• Meet with the Government (with ISC support) and the follow-on contractor to jointly plan the transition of responsibility of relevant workload to the follow-on contractor and Government.

• Cooperate to permit an orderly change over to the follow-on contractor.

• Stand up its phase-out team in order to facilitate the activities necessary for successful phase-out. It is assumed that the follow-on contractor will establish a similar team to coordinate the GSSC transition.

• If the Government awards a follow-on contract to a non-incumbent contractor, the contractor shall respond to the Government with a proposal and schedule for Phase-Out, detailing a clear, orderly workload and responsibility transition from the contractor to the follow-on contractor(s). The contractor will jointly plan for transition of the Ground Subsystems workload to the follow-on contractor(s) to include all GFP, data, software, documentation, tools, and models used in the execution of support to the Ground Subsystems. This effort will be priced separately and placed on a separate task order.

2.17.2 Site Visits

The Government reserves the right to conduct site visits with Government personnel in all contractor-operated facilities in conjunction with the solicitation of offers for a follow-on GSSC.

2.17.3 Phase-Out Plan

The contractor shall document the approach for transition in a GSSC Phase-Out Plan.

2.17.3.1 The Phase-Out Plan shall document the process for the transition of the duties, activities, and functions of tasks including

2.17.3.1.2 The entrance and exit criteria for each task to be transitioned, the responsible person for the respective contractors, and the milestone schedule for achieving transfer of responsibility for each.

2.17.3.1.3 An organizational chart showing all resources and their roles in the phase-out (i.e. Phase-Out Project Manager, etc.). Key team members should be from both the incumbent and new contractors as well as the customer.

2.18 ASSOCIATE CONTRACTOR AGREEMENT

The contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge,

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 39 of 64

expertise, and/or resources essential to the sustainment of the MMIII WS, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. ACAs shall include the following general information:

• Identify the associate contractors and their relationships. • Identify the program involved and the relevant Government contracts of the associate

contractors. • Describe the associate contractor interfaces by general subject matter. • Specify the categories of information to be exchanged or support to be provided. • Include the expiration date (or event) of the ACA. • Identify potential conflicts between relevant Government contracts and the ACA; include

agreements on protection of proprietary data and restrictions on employees. • The cooperating contractors shall provide a copy of such agreement to the CO for review

before execution of the document. • The contractor is not relieved of any contract requirements or entitled to any adjustments to

the contract terms because of a failure to resolve a disagreement with an associate contractor. • Liability for the improper disclosure of any proprietary data contained in or referenced by

any agreement shall rest with the parties to the agreement, and not the Government. • All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 40 of 64

3.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS LIST

Acronyms Definition

A ACA Associate Contractor Agreement ACAT Acquisition Category ACO Administrative Contracting Officer ADLS Advanced Distributed Learning Center AEHF Advanced Extremely High Frequency AETC Air Education and Training Command AF Air Force AFB Air Force Base AFGSC Air Force Global Strike Command AFGSCI Air Force Global Strike Command Instruction AFI Air Force Instruction AFMAN Air Force Manual AFMC Air Force Materiel Command AFMCI Air Force Materiel Command Instruction AFNWC Air Force Nuclear Weapons Center AFNWCI Air Force Nuclear Weapons Center Instruction AFOSH STD Air Force Occupational Safety and Health Standards AFPAM Air Force Pamphlet AFPD Air Force Policy Directive AFTO Air Force Technical Order Ai Inherent Availability ALCS Airborne Launch Control System ANSI American National Standards Institute APT ALCS (Airborne Launch Control System) Procedures Trainer AS Aging Surveillance AT Antiterrorism ATC Authorizations to Connect ATE Automatic Test Equipment ATO Authorization to Operate AVE Airborne Vehicle Equipment C C3 Command, Control and Communications

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 41 of 64

Acronyms Definition

CAV Commercial Asset Visibility CCB Configuration Control Board CCI Commercial CRYPTO Interface CCP Configuration Change Proposals CCS Computer Control Software CDRL Contract Data Requirements List CD-RW Compact Disc - Rewritable CERT Certification CFR Code of Federal Regulations CFSR Contract Funds Status Report CISM Certified Information Security Manager CISSC Communication Installation and Sustainment Support Contract CISSP Certified Information System Security Professional CJCSM Chairman of the Joint Chiefs of Staff Manual CJCSI Chairman of the Joint Chiefs of Staff Instruction CLFA Closed Loop Failure Analysis CLIN Contract Line Item Number CLS Contract Logistics Support CM Configuration Management CMMI Capability Maturity Model Integration CMPT Control Monitors Procedures Trainer CMRA Contractor Manpower Reporting Application CMS Contractor Maintenance Support CND Computer Network Defense CO Contracting Officer COMSEC Communications Security CONUS Continental United States COP Console Operations Program COR Contracting Officer Representative COTS Commercial Off-the-Shelf CPI Critical Program Information CRISC Certified Risk and Information System Control CRP Certification Requirements Plan CSAG-Supply Consolidated Support Activity Group-Supply CSCI Computer Software Configured Items CSRD Computer Systems Requirements Documents

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 42 of 64

Acronyms Definition

CSS Control and Support Software CSU Computer Software Unit C-TPAT Customs Trade Partnership Against Terrorism CWBS Contract Work Breakdown Structure D DAA Designated Approving Authority DAG Defense Acquisition Guidebook DAL Data Accession List DART Days Away, Restricted or Transferred DCMA Defense Contract Management Agency DD Department of Defense DFARS Defense Federal Acquisition Regulation Supplement DIACAP DOD Information Assurance Certification and Accreditation Process DID Data Item Description DISA Defense Information Systems Agency DIT-MCO Data Information Test Material Checkout DMSMS Diminishing Manufacturing Sources and Materiel Shortages DOD Department of Defense DODD Department of Defense Directive DODI Department of Defense Instruction DOE Department of Energy DPA Destructive Physical Analysis DR Deficiency Report DRB Deficiency Review Board DRMS Defense Reutilization and Marketing Service DSS Defense Security Service DTR Defense Transportation Regulation DVD Digital Versatile Disc E EAM Emergency Action Message ECP Engineering Change Proposal EDI Electronic Data Interchange EHF Extremely High Frequency EIA Electronic Industries Alliance EMC Electromagnetic Compatibility EMI Electromagnetic Interference

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 43 of 64

Acronyms Definition

EMITR Electromagnetic Interference Test Report EMP Electromagnetic Pulse EMSEC Electromagnetic Security EO Executive Order ER Emergency Response ERB Engineering Review Board ESOH Environmental, Safety, and Occupational Health ETAR Engineering Technical Assistance Request EVMS Earned Value Management System EWO Emergency War Order F FAR Federal Acquisition Regulation FCA Functional Configuration Audits FCA/PCA Functional Configuration Audit/Physical Configuration Audit FDCR Final Design Certification Report

FISAC Future ICBM (Intercontinental Ballistic Missile) Sustainment and Acquisition Construct

FISMA Federal Information Security Management Act FO Foreign Object FOD Foreign Object Damage FMECA Failure Modes and Effects and Criticality Analysis FOT&E Follow-On Operational Test and Evaluation FY Fiscal Year G GEIA Government Electronics Information Technology Association GFE Government-Furnished Equipment GFP Government-Furnished Property GFS Government-Furnished Software GIDEP Government Industry Data Exchange Program GIG Global Information Grid GMATS Ground Minuteman Automatic Test System GOTS Government Off-the-Shelf GR Government Representative GRID Government Rights in Data GSD Ground Systems Division GSSC Ground Subsystems Support Contract H

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 44 of 64

Acronyms Definition

HAC/RMPE Higher Authority Communications/Rapid Message Processing Element HACDC Higher Authority Communication Data Collector HACTS Higher Authority Communication Test Station HAMS Hardness Assurance, Maintenance, and Surveillance HDBK Handbook HICS Hardened Intersite Cable System HSEP Hardness Surveillance Electromagnetic Pulse HSP Health & Safety Plan HSSF HAC/RMPE Software Support Facility I IA Information Assurance IAM Information Assurance Manager IAO Information Assurance Officer IAT Information Assurance Technical IATT Interim Authorization to Test IAVA Information Assurance Vulnerability Alert IAW In Accordance With IBR Integrated Baseline Review ICBM Intercontinental Ballistic Missile ICBMSD Intercontinental Ballistic Missile Systems Directorate ICD Interface Control Documents ICWG Interface Control Working Group IDE Integrated Data Environment IEE ICBM Infrastructure and Equipment IM Item Manager IMDB Integrated Missile Data Base IMDS Integrated Maintenance Data System IMP Integrated Master Plan IMS Integrated Master Schedule

IOSSP ICBM (Intercontinental Ballistic Missile) Operational Software Sustainment Program

IPB Illustrated Parts Breakdown IPIC ICBM (Intercontinental Ballistic Missile) Prime Integration Contract IPL Indentured Parts List IPMR Integrated Program Management Report IPT Integrated Product Team IR Interagency Report

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 45 of 64

Acronyms Definition

ISC Integration Support Contract ITAR International Traffic in Arms Regulations ITT Integrated Test Team IUID Item Unique Identification IV&V Independent Verification and Validation IVV Integrity Verification and Validation J JCS Joint Chiefs of Staff JEDMICS Joint Engineering Data Management Information and Control System JWICS Joint Worldwide Intelligence Communications System

JITC Joint Operability Test Center

JROC Joint Requirements Oversight Council K KPP Key Performance Parameter L LCC Launch Control Center LCSE Life Cycle Systems Engineering LF Launch Facility LRU Line Replaceable Unit M MAF Missile Alert Facility MAR Maintenance Action Request MC Mission Capable MEDL Master Engineering Document List MEECN Minimum Essential Emergency Communications Network MEO Missile Engineering Office MEP Minuteman Enhanced Procedures MILE Minuteman Integrated Life Extension MILSTAR Military Strategic and Tactical Relay MIL-STD Military Standard MILSTRIP Military Standard Requisitioning and Issue Procedures MM Minuteman MMIII Minuteman III

MMP Minuteman Minimum Essential Emergency Communications Network (MEECN) Program

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 46 of 64

Acronyms Definition

MMT Missile Maintenance Trainer MNCL Master Nuclear Certification List MOTP Minuteman Operational Targeting Program MP3 MPEG-1 Audio Layer-3 MPE Mission Planning Element MPHN Missile Potential Hazard Network MPT Missile Procedures Trainer MRAR Mishap Risk Assessment Report MTBF Mean Time Between Failures MTTR Mean Time to Repair N NALDA Naval Aviation Logistics Data Analysis NC3 Nuclear Command, Control and Communications NCIS Nuclear Certification Impact Statements NDA Non-Disclosure Agreement NDIA National Defense Industrial Association NEPA National Environmental Policy Act NIPR Non-Secure Internet Protocol Router NISPOM National Industrial Security Program Operating Manual NIST National Institute of Standards and Technology NNSA National Nuclear Security Administration NRC Nuclear Regulatory Commission NRTS Not Reparable This Station NSA National Security Agency NSCCA Nuclear Safety Cross Check Analysis NSE Nuclear Surety Evaluation NWRM Nuclear Weapons-Related Materiel NWRMAO Nuclear Weapons-Related Materiel Accountable Officer O O&M Operations & Maintenance OCB Operations Control Board OCI Organizational Conflict of Interest OEM Original Equipment Manufacturer OFP Operational Flight Program OGE Operational Ground Equipment OGP Operational Ground Program

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 47 of 64

Acronyms Definition

OI Operating Instruction OPCERT/DECERT Operational Certification/Decertification OPLAN Operations Plan OSCR Operational Software Change Requests OSHA Occupational, Safety and Health Act OSS&E Operational Safety, Suitability and Effectiveness OT&E Operational Test and Evaluation P PADS Performance Analysis Data System PAS Personal Alarm System PATE Performance Analysis Technical Evaluation PBC Partial Bridge Contract PCA Physical Configuration Audits PCO Procuring Contracting Officer PCR Publication Change Request PDM Periodic Depot Maintenance PDU Power Distribution Unit

PESHE Programmatic Environmental, Safety, and Occupational Health Evaluations

PFAS Personal Fall Arrest System PIDS Prime Item Development Specification PMR Program Management Review PMS Production Management Specialist PPIP Program Protection Implementation Plan PPP Program Protection Plan PR Purchase Request PRP Personnel Reliability Program PTO Preliminary Technical Order PTOFCN Preliminary Technical Order Field Change Notice PWS Performance Work Statement R RAWG Risk Assessment Working Group RCA Root Cause Analysis RCM Reliability-Centered Maintenance REACT Rapid Execution and Combat Targeting REMIS Reliability and Maintainability Information System RFP Request for Proposal

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 48 of 64

Acronyms Definition

RMB Risk Management Board RM&S Reliability, Maintainability and Sustainability RO Responsible Officer ROM Rough Order of Magnitude RPIE Real Property Installed Equipment RVA Remote Visual Assessment RVB Requirements Validation Board S SACCS Strategic Automated Command and Control System SAE Society of Automotive Engineers SAR Safety Assessment Report SAV Staff Assistance Visit SAR Safety Assessment Reports SBICBM Silo-Based Intercontinental Ballistic Missile SCG Security Classification Guide SCMG Supply Chain Management Group SCN Specification Change Notification SDD Software Design Description SDP Software Development Plan SDR Supply Discrepancy Report SDS Squadron Data Simulator SE Support Equipment SELECT Systems Engineering Level Evaluation and Correction Team SELM Simulated Electronic Launch Minuteman SEMP Systems Engineering Management Plan SFS Security Forces Squadron SGML Standard Generalized Markup Language SIMCERT Simulator Certification SINAD Signal to Noise and Distortion SIPR Secure Internet Protocol Router SLEP Service Life Extension Program SMIC Strategic Missile Integration Complex SME Subject Matter Expert SMSR Survivability Management Status Report S/N Serial Number SOO Statement of Objectives

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 49 of 64

Acronyms Definition

SOW Statement of Work SPS Software Product Specification SQAP Software Quality Assurance Plan SRA System Requirements Analysis SRS Software Requirements Specification SRU Shop Replaceable Unit SSC Software Support Center SSE Systems Security Engineering SSHAR System Safety Hazard Analysis Report SSMP Systems Security Management Plan SSS System/Subsystem Specification SSWG System Security Working Group STD Standard STD Software Test Description STE Secure Terminal Equipment STMR SACCS Trouble Monitor Report STOS Strategic Operations Squadron STP Software Test Plan STRATCOM Strategic Command STrP Software Transition Plan STR Software Test Report SVD Software Version Description SW Systems Wing T T&E Test and Evaluation T&H Transportation & Handling TAT Turn-Around Times TCB Trusted Computing Base TCIR Total Case Incidence Rate TCN Transportation Control Number TCOSS Telecommunications Certification Office Support System TCP Task Change Proposals TCTO Time Compliance Technical Order TEMP Test & Evaluation Management Plan TIM Technical Interchange Meetings TM Technical Manual TMDE Test Measurement and Diagnostic Equipment

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 50 of 64

Acronyms Definition

TMMA Technical Manual Management Agency TO Technical Order TOR Technical Operating Report TOVR Technical Order Verification Recommendation TPS Test Program Sets TPS1 Transportation Protective Services TERB Technical Evaluation Review Board TRC Technology Repair Center U UII Unique Item Identifier USSTRATCOM United States Strategic Command V VAX Virtual Address Extension VLF Very Low Frequency VPP Voluntary Protection Program W WBS Work Breakdown Structure WCPS Wing Code Processing System WS Weapon System WSER Weapon System Effectiveness Report

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 51 of 64

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be defined at draft RFP release

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 52 of 64

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

INDUSTRIAL SAFETY REQUIREMENTS

For

MINUTEMAN III (MM III)

GROUND SUBSYSTEM SUPPOR CONTRACT

PREPARED BY AFNWC/NIEV

AFNWC.NIEV.SafetyManager@us.af.mil

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 53 of 64

SECTION I - GENERAL REQUIREMENTS

A. Safety Program Requirements.

The contractor will implement a safety program plan that ensures protection of Government personnel and property. The program will consist of, as a minimum:

1. Mishap reporting, as defined in paragraph B1 below.

2. A Safety Plan that addresses, as a minimum, the subjects listed in Section II –Specific Requirements, and will be used during the performance of the work described in the contract. The Safety Plan will be approved by ICBMSD System Safety Program Office, AFNWC/NIEV prior to commencement of any work described in this contract.

3. Routine and recurring surveillance to ensure safety requirements of contract are enforced.

4. Competent personnel to provide surveillance of the Safety Plan.

5. Identification of segregated work site locations for operations that cannot be co-mingled with general industrial operations and the process for ACO approval of operations and changes at these specific sites.

6. All contractor personnel shall be trained and qualified to perform their duties safely.

7. The contractor shall include a clause in all subcontracts requiring the subcontractors to comply with the safety provisions of this contract, as applicable.

B. Mishap Notification

1. The contractor shall notify the appropriate base safety office or commend post (after normal duty hours), and the designated Government Representative (GR), i.e., the ACO, PCO, or DCMA QAR (Quality Assurance Representative) within one (1) hour of all mishaps or incidents at or exceeding $2,000 (material + labor) in damage to DOD property entrusted by this contract, even if the government is wholly or partially reimbursed. This notification requirement shall also include physiological mishaps/incidents. A written or email copy of the mishap/incident notification shall be sent within three calendar days to the GR, who will forward it to the appropriate safety office. For information not available at the time of initial notification, the contractor shall provide the remaining information no later than 20 calendar days after the mishap, unless extended by the ACO. If work is being performed at other Government owned facility, mishaps must be reported to the local facility Command Post and/or Safety Office.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 54 of 64

Base Command Post DSN Base/Wing Safety DSN

341st Missile Wing 632-3801 731-6719

90th Missile Wing 481-3921 481-3684

91st Missile Wing 453-3101 453-2293

Vandenberg AFB 276-9961 605-7233 (605-SAFE)

Barksdale AFB 781-2152 781-5618

Hill AFB 777-3007 777-7233 (777-SAFE)

Mishap notifications shall contain, as a minimum, the following information:

(a) Contract, Contract Number, Name and Title of Person(s) Reporting

(b) Date, Time and exact location of accident/incident

(c) Brief Narrative of accident/incident (Events leading to accident/incident)

(d) Cause of accident/incident, if known

(e) Estimated cost of accident/incident (material and labor to repair/replace)

(f) Nomenclature of equipment and personnel involved in accident/incident

(g) Corrective actions (taken or proposed)

(h) Other pertinent information

2. The contractor shall cooperate with any and all government mishap investigations. Additionally, if requested by government personnel or designated government representative (GR), i.e., the ACO, PCO, or DCMA QAR (Quality Assurance Representative), the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by safety investigators.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 55 of 64

3. The contractor shall provide copies of contractor data related to mishaps, such as contractor analyses, test reports, summaries of investigations, etc. as necessary to support the government investigation.

4. The contractor shall support and comply with the safety investigation and reporting requirements of AFI 91-204, Chapters 1 – 5.

C. General Safety Requirements:

If the safety plan is modified, the contractor shall submit the proposed modification, in writing, to the Contract Administration Office safety representative.

The contractor is solely responsible for compliance with all federal, state and local laws, the Occupational, Safety and Health Act (OSHA) (Public Law 91-596) and the resulting standards, OSHA Standards 29 CFR 1910 and 1926, as applicable, and the protection of their employees. Additionally, the contractor is responsible for safety and health of all subcontractor employees.

The contractor shall ensure assigned personnel are adequately trained and qualified for the task being performed. Brief all personnel on the hazards involved with operations and applicable precautions to be taken. Should unidentified hazards arise, cease operations until actions are taken to eliminate or mitigate hazards to safe levels.

Compliance with OSHA and other applicable laws and regulations for the protection of contractor employees is exclusively the obligation of the contractor. Note: Air Force Occupational Safety and Health Standards (AFOSH STD) are annotated because many of the Air Force Standards exceed the OSHA standard criteria. If a conflict is noted, the most stringent requirement takes precedence. The government shall assume no liability or responsibility for the contractor's compliance or non-compliance with such requirements. The contractor shall furnish to each of his/her employees a place of employment, which is free from recognized hazards. The contractor shall brief his/her employees on the safety requirements of this contract and on hazards associated with prescribed tasks. The contractor is responsible for compliance with OSHA Public Law and the resultant standards identified within. In addition, the contractor is required to flow down the safety requirements/specification to all subcontractors. This applies to Federal Acquisition Regulation (FAR) 12 commercial acquisitions as well. This contract shall in no way require persons to work in surroundings or under working conditions which are unsafe or dangerous to their health. The contractor must coordinate and perform work so as not to impact the safety of government employees or cause damage to government property. This requires providing personnel with protective equipment and associated safety equipment as may be necessary. The contractor must also protect personnel from hazards generated by the work. If the contractor employs BILINGUAL speaking employees, they must post bilingual signs and have written procedures for specific tasks in applicable languages.

SECTION II – SPECIFIC REQUIREMENTS

The contractor’s prepared Safety Plan shall:

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 56 of 64

• Demonstrate a management commitment to employee safety and health • Identify applicable rules and regulations • Identify the roles and responsibilities of Management, Supervisors, Employees and Safety Coordinator • Identify work to be performed and location of expected operations • Provide a description of safety program, safety monitoring responsibilities, organizational structure, and contact information for on-site personnel • Include a work hazard analysis of the worksite and operations to be performed to include baseline hazard identification and required control measures • Identify employee safety and health training requirements and the documentation process • Include emergency response plans and procedures that relate to protection of government personnel and property • Include a workplace inspection frequency, to include the identity of the individual responsible for conducting the inspection • Include hazard reporting procedures and identify individual(s) responsible for the correcting identified hazards • Identify first aid and injury procedures • Identify procedures for accident reporting and investigation • Identify the process for tracking controlled hazards in contractor’s work area

The contractor shall ensure that each element identified below is adequately addressed in detail in the safety and health plan:

PEDESTRIAN CROSSWALKS: All contractor personnel are required to use the closest crosswalk, or traffic controlled intersection when crossing the road. Pedestrians must look both ways to ensure the coast is clear before stepping out into the crosswalk. Pedestrians DO NOT have the right of way unless they are already in the crosswalk. Contractor vehicle operators have the same responsibilities as pedestrians, to share the road and mutually observe and yield to pedestrians.

MOTOR VEHICLES: Contractor shall comply with the standards in: DoD Directive 5525.4, Enforcement of State Traffic Laws on DoD Installations", 2 Nov 81, Change 1 (31 Oct 86), Para 3-4; DODI 6055.4, DoD Traffic Safety Program, 20 April 09, Change 2 (23 Jan 13); AFI 91-207, USAF Traffic Safety Program, 12 Sep 13; and AFI 91-207 AFMC SUP1, The US Air Force Traffic Safety Program, 11 Feb 14. Each applies to all persons at any time on an Air Force Installation and includes all leased, owned, or privatized property including housing areas. In addition: AFI 13-213, Airfield Driving, 1 Jun 11, Ch. 3, applies to all contractors, sub-contractors, vendors, commercial delivery companies, and all other private business vehicles who operate anywhere on Hill Air Force Base, including the airfield (to include the industrial areas and any buildings or hangars located upon the airfield) in support of their mission.

WALKING – WORKING SURFACES: Contractor shall comply with the standards in 29 CFR 1910 Subpart D and National Fire Protection Association (NFPA) 101, Life Safety Code. All interior walking and working surfaces which are part of the means of egress shall remain clear at

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 57 of 64

all times and comply with the requirements of NFPA 101. Floors shall be kept in good condition and free of defects that can endanger workers or interfere with the handling of materials. Housekeeping – methods and controls are in place to minimize tripping hazards, the accumulation of flammable/combustible materials, etc. Portable metal ladders – methods and controls are in place to ensure inspection and safe use. Open-sided floors/platforms/runways must be protected and not left uncovered to prevent injury.

PERSONAL PROTECTIVE EQUIPMENT: Contractor shall comply with the standards in 29 CFR 1910 Subpart I and 29 CFR 1926, 28, 95, 100, 101, 102, & 951. Personnel protective equipment is required to be worn when employees are exposed to a potential hazard, working overhead, falling objects, etc.

Contractor’s Safety Plan shall also address: - Eye and face protection - Head protection - Foot Protection

HAZARDOUS COMMUNICATIONS: Contractor shall comply with the standards in 29 CFR 1910.1200.

Contractor’s Safety Plan shall also address: - Written Program

- List of hazardous chemicals, methods used to inform employees of the hazards, precautionary measures

- Identity of the hazardous chemical(s) and labeling system - Material safety data sheets and location - Employee information and training

HAZARDOUS MATERIALS: Contractor shall comply with the standards in 29 CFR 1910 Subpart H – The handling and Storing of Hazardous Materials (chemicals, compressed air, acetylene, etc.). When handling the hazardous material, the following must be accomplished: Compressed gases – training, handling, storage, use, and PPE; flammable and combustible liquids – training, handling, storage use, and PPE.

Contractor’s Safety Plan shall also address: - Training, handling, storage, use and PPE - Explosives and blasting agents - Dipping and coating operations

HAZARDOUS WASTE OPERATIONS: Contractor shall comply with the standards in 29 CFR 1910.120 and 29 CFR 1926.65.

Contractor’s Safety Plan shall also address: - Emergency Response Plan - Personal Protective Equipment - Medical Surveillance

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 58 of 64

- Health and Safety Plan (HASP– required elements have been incorporated) - Employee Training

TOXIC AND HAZARDOUS SUBSTANCES: Contractor shall comply with the standards in 29 CFR 1910 Subpart Z and 29 CFR 1926 Subpart Z.

Contractor’s Safety Plan shall also address: - A section related to working with toxic and hazardous substances, such as asbestos, benzene, lead, and styrene, where the following areas are addressed: - Threshold Limit Values (TLV)-Exposure monitoring - Medical surveillance - Work practices - Engineering controls - Respiratory protection - Protective clothing (PPE)

SYSTEM MODIFICATION-WHICH ALTERS FORM, FIT OR FUNCTION: Contractor shall comply with MIL-STD-882E, Standard Practice for System Safety, 11 May 2012 and AFI 91-202, The US Air Force Mishap Prevention Program, 5 Aug 2011, for system modifications, which alter form, fit, or function.

ELECTRICAL: Contractor shall comply with the standards in 29 CFR 1910 Subpart S, 29 CFR 1926 Subpart K, AFOSH STD 91-501, Air Force Consolidated Occupational Safety Standard, 7 Jul 04, Chap 8, and NFPA 70, National Electrical Code, 2014 Edition. All electrical wiring must be IAW National Electrical Code. Electrical wiring and equipment shall be a type listed by Underwriters Laboratories (UL) or another recognized listing agent.

Contractor’s Safety Plan shall also address: - Selection and use of work practices - Training (basic electrical safety knowledge) - Use of equipment (handling, visual inspection, rating of equipment) - GFCI Protection for outside contractor drops and wet/damp areas - Arc Flash

FIRE PROTECTION FOR FACILITIES: Contractor’s procedures shall comply with NFPA 10, Portable Fire Extinguishers, 2013 Edition; NFPA 13, Installation of Sprinkler Systems, 2013 Edition; NFPA 33, Spray Application Using Flammable or Combustible Materials, 2011 Edition; NFPA 70, National Electrical Code, 2014 Edition; NFPA 72, National Fire Alarm Code, 2013 Edition; NFPA 91, Exhaust Systems for Air Conveying of Vapors, Gases, Mists, and Noncombustible Particulate Solids, 2015 Edition.

HAZARDOUS ENERGY CONTROL PROGRAM ELEMENTS (LOCKOUT-TAGOUT): Contractor shall comply with the standards 29 CFR 1910 Subpart S, 29 CFR 1926 Subpart K, AFI 91-203, Air Force Consolidated Occupational Safety Instruction, 15 Jun 12, Chap 21, and Hill AFB Instruction 91-302, Control of Hazardous Energy (Lockout/Tagout).

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 59 of 64

Contractor’s Safety Plan should also address: - Purpose of hazardous energy control program - Employee training - Lockout/tagout procedures - Restoring equipment to normal operations - Removal of locks and tags - Periodic inspections - Portable Fire Extinguishers – proper type, inspection, maintenance, testing, and training

MATERIALS HANDLING AND STORAGE: Contractor shall comply with the standards in 29 CFR 1926.250, 953, 957; 29 CFR 1910.101, Subparts F, H & N; and 29 CFR 1910.178.

Contractor’s Safety Plan shall also address: - Storage and handling of materials - Disposal of trash from elevations - Personnel lifting techniques--proper storage to prevent shifting, for stability, etc. - Rigging (requirements, inspection, components, and qualifications) - Equipment (use in handling materials) - Industrial trucks (training, inspection, maintenance, and safe use) CONFINED SPACE PROGRAM ELEMENTS: Contractor shall comply with the standards in 29 CFR 1910.120, 146; 29 CFR 1926.21, 353; and AFI 91-203, Air Force Consolidated Occupational Safety Instruction, 15 Jun 12, Chap 23. A confined space must meet the following three criteria: (1) Is large enough and configured that an employee can bodily enter and perform assigned work (2) Has limited or restricted means for entry or exit (for example, tanks, vessels, silos, storage bins, hoppers, vaults, and pits are spaces that may have limited means of entry.) (3) Is not designed for continuous employee occupancy. Examples: underground vaults, tanks, storage bins, manholes, pits, silos, process vessels, and pipelines. Contractor’s Safety Plan shall address: - Hazards of confined space - Permit and Non-permit confined spaces - Responsibilities of management, entry supervisor, authorized entrant, and authorized attendants - Training requirements - Permit handling and approval - Emergency and rescue plans - Testing and monitoring requirements - Special hazards - Posting requirements (applicable to subcontractor operated facilities)

GENERAL ENVIRONMENTAL CONTROLS: Contractor shall comply with the standards in 29 CFR 1910 Subpart G, 29 CFR 1910 Subpart J and 29 CFR 1926 Subpart D.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 60 of 64

Contractor’s Safety Plan shall also address: - Sanitation-toilet and washing facilities - Accident prevention signs and tags

RESPIRATORY PROTECTION PROGRAM ELEMENTS: Contractor shall comply with the standards in 29 CFR 1910.134 and 29 CFR 1926.103. Respirators are required to be worn if employees are exposed to inhalation hazard.

Contractor’s Safety Plan shall also address: - Training - Medical evaluation - Fit tests - Selection of respiratory equipment - Storage of respiratory equipment - Pre-use checks

HEARING CONSERVATION PROGRAM ELEMENTS: Contractor shall comply with the standards in 29 CFR 1910.95 and 29 CFR 1926.52. NOTE: Noise exposures are based on ACGIH guidelines of 85 dB Time Weighed Average (TWA).

Contractor’s Safety Plan shall also address: - Monitoring (survey of noise producing equipment) - Audiometric testing - Hearing Protectors - Training - Recordkeeping/Access to information and training material

MEDICAL AND FIRST AID: Contractor shall comply with the standards in 29 CFR 1910 Subpart K and 29 CFR 1926 Subpart C.

Contractor’s Safety Plan shall also address: - Adequate first aid supplies - Trained employee to render first aid - Recordkeeping - Reporting and investigating accidents/incidents - Off-site physician(s) - Maintenance of and employee access to exposure monitoring data and medical records

EXPLOSIVE SAFETY REQUIREMENTS: Contractor shall comply with the standards in AFMAN(I) 24-204, Preparing Hazardous Materials for Military Air Shipments, 3 Dec 12; and dash 11 series TOs; DoDI 4145.26M, DoD Contractors' Safety Requirements for Ammunition and Explosives, 13 Mar 08; AFI 23-101, Air Force Material Management, 08 Aug 13; TO 11A-1-33, Handling and Maintenance of Explosives-Loaded Aircraft, 20 Nov 08), TO 11A-1-46, Fire Fighting Guidance, Transportation, and Storage, 15 Nov 04 Change 6 (12 Nov 08) for all handling of all explosive devices to be removed, installed, stored or transported, AFMAN 91-201, Explosive Safety Standards, 12 Jan 11.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 61 of 64

FOREIGN OBJECT DAMAGE (FOD) Awareness, Prevention and Responsibilities: Contractor shall comply with the standards in: AFI 21-101 AFMC SUP 1, Aircraft and Equipment Maintenance Management, 26 Apr 12, paragraphs 14.19 - 14.19.10.1.13; National Aerospace Standard (NAS) 412, Foreign Object Damage/Foreign Object Debris (FOD) Prevention Program, Sep 13; AFI 91-203, Air Force Consolidated Occupational Safety Instruction, 15 Jun 12, Chap 24.

The FOD program must be integrated into the day-to-day operations to reduce/eliminate FOD incidents. Programs will include covering waste dumpsters, waste hauling trucks, barriers in place to stop migrating FOD from dirt and gravel piles, and end of shift or daily clean-up. The contractor will brief their personnel at least weekly on any FOD requirements. All contractors, subcontractors performing maintenance in a FOD–potential area will receive and have documented initial FOD Awareness and Prevention training. All vehicle operators are responsible for performing a Foreign Object (FO) inspection on their vehicles including all towed equipment, vehicle tires and open cargo areas of vehicles prior to entering the marked runway, taxiway, flight line, and aircraft parking ramps and other areas as directed by the Installation FOD Awareness and Prevention Officer. All “open-air” delivery vehicles must be free of loose items/debris that could potentially fall from the vehicle and cause a FOD hazard. The cargo beds of pickups truck must be clean or covered prior to entering the airfield. Vehicles will be subject to inspection and denied entry if found unacceptable. Contractors and site/operations evaluators will ensure tools; equipment, rags, residue and hardware are properly stored and accounted for. “Clean as you go” methods are desired.

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 62 of 64

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 63 of 64

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be defined at Draft RFP release

FA8214-20-D-XXXX 14 MAY 2018

BASIC PWS- GSSC 2.0

Page 64 of 64

APPENDIX F: ATTACHMENT LIST

ATTACHMENT NO. TITLE

ATTACHMENT 1 General Sustainment

ATTACHMENT 2 ICBM Operational Software Sustainment Program (IOSSP)

ATTACHMENT 3 Higher Authority Communications / Rapid Message Processor Equipment (HAC/RMPE)

ATTACHMENT 4 Codes

ATTACHMENT 5 Trainers

ATTACHMENT 6 Ground Minuteman Automatic Test Station (GMATS)

ATTACHMENT 7 Strategic Automated Command Control System (SACCS)

ATTACHMENT 8 Airborbe Launch Control System (ALCS)

ATTACHMENT 9 Flight Test, Telemetry and Termination (FT3)

ATTACHMENT 10 Depot Field Team

ATTACHMENT 11 Software Lab Relocation

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 1 of 54

ATTACHMENT 1

GENERAL SUSTAINMENT

IN SUPPORT OF

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 2 of 54

1.0 GSSC General Sustainment ...................................................................................................... 3

1.1 Scope ..................................................................................................................................... 3

1.2 Purpose .................................................................................................................................. 3

1.3 Background ........................................................................................................................... 3

1.4 Requirements Summary ........................................................................................................ 3

1.4.1 Sustainment Engineering ............................................................................................... 3

1.4.2 Systems Engineering .................................................................................................... 21

1.4.3 Program Management Support .................................................................................... 31

1.4.4 Knowledge Transfer (KT) ............................................................................................ 40

1.4.5 Travel ........................................................................................................................... 40

1.4.6 Contractor Manpower Reporting ................................................................................. 40

1.4.7 Process Improvement Planning .................................................................................... 41

1.4.8 Response to Government Requests .............................................................................. 41

1.4.9 Emergency Response ................................................................................................... 42

1.4.10 Development, Procurement, and Repair Programs .................................................... 42

1.5 Services Summary .............................................................................................................. 42

2.0 Appendices .............................................................................................................................. 50

APPENDIX A: ACRONYMS AND ABBREVIATIONS ....................................................... 50

APPENDIX B: WORK BREAKDOWN STRUCTURE ......................................................... 51

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION ............ 52

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ....................................................................................................................... 53

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................. 54

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 3 of 54

Attachment 1 General Sustainment PWS

1.0 GSSC GENERAL SUSTAINMENT

1.1 SCOPE

Scope is listed in section 1.1 of the Basic PWS.

1.2 PURPOSE

Purpose is listed in section 1.2 of the Basic PWS.

1.3 BACKGROUND

Background is listed in section 1.3 of the Basic PWS.

1.4 REQUIREMENTS SUMMARY

The contractor shall provide a capability to perform the following activities, to include but not limited to, as directed in the performance of the GSSC. For program specific requirements refer to task order attachment.

1.4.1 Sustainment 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 LCC, LF and Grounds Support Equipment, including all subcomponents and support and test equipment. The contractor shall support the review, development and/or response to the following on an as needed basis: the review of ICBM TO change recommendations, ICBMSD, JMD, 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 items contained in the Master Nuclear Certification Listing (MNCL).

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 4 of 54

1.4.1.1 Software Sustainment

1.4.1.1.1 The contractor shall ensure continued operation and maintenance of Ground Subsystems software through software sustainment activities.

1.4.1.1.2 The contractor shall employ software sustainment practices to identify, review, assess, and resolve deficiencies for Ground Subsystems software.

1.4.1.1.3 The contractor shall maintain the software at its baseline configuration and capability.

1.4.1.1.4 The contractor shall perform all software sustainment work to the same software processes as required in software development section (e.g., according to the requirements defined in the Government-approved SDP).

1.4.1.1.5 Should updates to the SDP be required for sustainment, the contractor shall submit these changes to the Government for approval.

1.4.1.1.6 The contractor shall provide technical advisor support to Ground Subsystems operations during the sustainment to include:

• Software analysis • Software development (includes upgrade, enhancement, repair, and test) • Software problem/deficiency analysis • Anomaly resolution • Configuration management • Subsystem troubleshooting • WS integration • Trending analysis to optimize Ground Subsystems operations, sustainment,

and test procedures • Review delivered documentation for proposed hardware and software changes

to Ground Subsystems • Develop and recommend changes to Ground Subsystems operation procedures

and training documentation • Perform technical feasibility and analysis studies • Support software at the Depot, Missile Wings, or other facilities where GFE

(including GOTS) and software exist • Test set control, operation, diagnostic, data production, and data storage • Software T&E on existing test equipment designed to support Ground

Subsystems maintenance and/or assessment IAW AFI 99-103, Capabilities-Based Test and Evaluation

• Document and process software CPIN requests and updates

Perform requirements traceability for all proposed changes to the baseline(s)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 5 of 54

1.4.1.1.7 The contractor shall support any Government required certifications such as Software Certification for Nuclear Surety (as applied to the Ground Subsystems for the weapon system).

1.4.1.1.8 The contractor shall perform software maintenance activities to include software requirements analysis, software product requirements development and management, software design, software code change, software code module integration, software qualification testing, CPIN activities and support to System Integration Test.

1.4.1.1.9 The contractor shall implement a software metrics collection and tracking capability. Metrics shall include software memory usage and maintainability, such as code complexity, file or computer software unit (CSU) frequency of change.

1.4.1.1.10 Prior to testing, software plans (including test plans) shall be developed, completed, coordinated, and approved by the Government. The contractor shall provide software test reports, addressing testing results to include any anomalies discovered during testing and mitigation requirements.

1.4.1.1.11 To ensure proper CM, the contractor shall provide accurate software version descriptions (SVD), software product specifications (SPS), and software test plans on the introduction of new software and ensure they accurately describe all modified software provided.

1.4.1.1.12 The contractor shall manage the software baseline until completion of FCA/PCA. The Government owns the software baseline, and the contractor is required to provide updates through Government processes (ICBMSD OI 62-01, Configuration Control Board (CCB)) to the CCB, and other panels at the various milestones to ensure changes are not made without Government involvement.

1.4.1.1.13 The contractor shall ensure deficiency-tracking capabilities exist for contractor-developed software or COTS software recommendations.

1.4.1.2 Hardware Sustainment

1.4.1.2.1 The contractor shall perform all hardware sustainment work to the same system requirements IAW the respective hardware specifications for each configured item (e.g., according to the requirements defined in the Government-approved Prime Item Development Specification (PIDS)). Should updates to the PIDS be required for sustainment, the contractor shall submit changes to the Government for approval.

1.4.1.2.2 In addition to the task list within the PWS, the contractor shall support the Government in sustaining MMIII Ground Subsystems hardware (installed equipment, transportation and handling equipment, trainers and support equipment) by performing the following tasks:

• Perform and document technical analyses (circuits, structural, hydraulic, pneumatic, heat transfer, thermodynamics, closed loop failure analysis (CLFA), corrosion prevention, feasibility, failure modes and effects and

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 6 of 54

criticality analysis (FMECA) and failure trends, test launch silo thermal, air blast affects, suspension system (dynamic) launcher closure door performance, etc.)

• Perform troubleshooting at Depot/Missile Wings and recommend potential mitigations

• As prioritized and directed by the government, provide level of effort technical support to research, analyze, recommend and help implement solutions to hardware sustainment and repair issues documented in ETARs, MPHNs, TERB, CCB, ICWG, AutoTATS, AFMC Forms 202, 107 requests, PNSSRS, AFTO 252, 22, 229, 918 and MARs.

• Develop test plans/procedures and perform testing as defined in section 1.6.4.4.1 (form/fit/function, diagnostic, and field/SMIC troubleshooting)

• Perform nuclear hardness (electromagnetic interference (EMI), electromagnetic compatibility (EMC), Electrostatic Discharge (ESD), radiation, shock and vibration) test and evaluation.

• Provide support to test set control, operation, diagnostic, data production and storage

• Provide and maintain source data for specifications, TOs, EOs, drawings, and Implementation Management Plans (IMP).

• Provide system integration support on issues that cross subsystem boundaries • Select and qualify suitable substitute parts and support PNSSR technical

solutions and COTS unique issues for Government approval • Perform environmental assessments and regulation compliance • Perform long-term weapon supportability planning • Perform 3-D and other computer modeling/analysis to include Finite Element

Analysis (FEA). • Perform requirements traceability for all proposed changes to the baseline(s)

1.4.1.2.3 The contractor shall sustain Ground Subsystems hardware by performing the following tasks:

• Commercial item support issues • Corrosion prevention and problems • Kit support, to include development, procurement, stock listing, provisioning

and fielding

1.4.1.2.4 The contractor shall support hardware T&E on existing test equipment designed to support Ground Subsystems maintenance and/or assessment.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 7 of 54

1.4.1.3 Ground Subsystems Assessment

1.4.1.3.1 Ground Subsystems Health

1.4.1.3.1.1 The contractor shall assess Ground Subsystems in coordination with their Government counterparts and provide assessment reports to the Government. Assessment areas include aging surveillance (AS), reliability, availability, maintainability, supportability, and nuclear hardness and survivability.

1.4.1.3.1.2 The contractor shall provide and maintain a list of launch essential/mission critical Operational Ground Equipment (OGE), Support Equipment (SE) and Test Equipment (TE) to track and monitor.

1.4.1.3.1.3 The contractor shall provide explanation for including these items in the list and how each group of item affects critical KPPs (availability, reliability, hardness, safety, surety, etc.) and how failures will be detected.

1.4.1.3.1.4 The contractor shall report on Ground Subsystems items for equipment, spares, failures, unscheduled downtime, failure trends, and mean time between failures (MTBF), ensuring rigorous assessments are accomplished. Items with adverse conditions (e.g., insufficient spares, excessive downtime, decreasing MTBF, or increasing failure trend) shall be reported as marginal/critical in assessment reports to the Government and the Technical Council.

1.4.1.3.1.5 The contractor shall include a watch list, in rank order of criticality, in the assessment report, consisting of OGE, SE and TE items which are judged “critical” for such issues as field/test failures, MTBF degradation, failure trend, spares depletion, downtime, and system risk.

1.4.1.3.1.6 The contractor shall make recommendations for new risk items and mitigation options to the Government. This information shall be consolidated into a Data Book and submitted to the Government to be used as inputs to the Weapon System Effectiveness Report (WSER).

1.4.1.3.1.7 The contractor shall perform data mining of Government data sources (e.g., IMDS, Reliability and Maintainability Information System (REMIS), IMDB, Performance Assessment Data System (PADS), Naval Aviation Logistics Data Analysis (NALDA), Impresa, JDRS and supply system databases) to conduct trend analysis for assessing Ground Subsystems.

1.4.1.3.1.8 The contractor shall assess risks against current and future operations following deployment and while in the operations and support phase assessment. Sustainment risks warranting particular attention include obsolescence, aging trends, unintended usage profiles, surveillance, and maintenance activities.

1.4.1.3.1.9 The contractor shall conduct failure and anomaly analysis to determine what effect such failures or anomalies would have on the weapon system and Ground Subsystems.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 8 of 54

1.4.1.3.1.10 The contractor shall participate in Closed Loop Failure Analysis (CLFA) efforts, including writing a CLFA plan, failure determination, CLFA reports, and collection of metrics IAW ICBMSD OI 99-04, Closed Loop Failure Analysis.

1.4.1.3.1.11 The contractor shall conduct Failure Modes and Effects and Criticality Analysis (FMECA) IAW SAE ARP5580 on Ground Subsystems hardware and software as directed to determine what failures could occur and the effect such failures would have on the WS.

1.4.1.3.1.12 The contractor shall provide and report information on spares, failures, and not reparable this station (NRTS) items, and highlight depleted items or projected to be depleted within 2 calendar years.

1.4.1.3.1.13 The contractor shall provide recommendations for improving the ease and efficiency in which preventive and corrective maintenance can be conducted.

1.4.1.3.2 Technical Risk Assessment

1.4.1.3.2.1 The contractor shall test, monitor, analyze, evaluate, and report capabilities of operational Ground Subsystems IAW AFI 63-101, Integrated Life Cycle Management and referencing ICBMSD 62-10, Risk Management.

1.4.1.3.2.2 The contractor shall report potential new risks and risk changes on a monthly basis at the PMR and Risk Management Board (RMB) IAW ICBMSD 62-10, Risk Management.

1.4.1.3.2.3 The contractor shall compile and provide data from T&E activities, assess requirements, and provide specific recommendations for Government requirements determination decisions. System requirements are identified through continuous monitoring of the Ground Subsystems, using formal assessment and surveillance programs.

1.4.1.3.3 Aging Surveillance (AS)

1.4.1.3.3.1 The contractor shall perform service life assessments and detect/quantify and report aging trends as early as possible.

1.4.1.3.3.2 The contractor shall maintain an AS database.

1.4.1.3.3.3 The contractor shall monitor system performance degradation resulting from aging.

1.4.1.3.3.4 The contractor shall conduct age-sensitive items analysis to determine which materials or components change with the life of the Ground Subsystems and the likelihood of failures resulting from continued use of aged materials or components.

1.4.1.3.3.5 The contractor shall maintain a list of critical OGE that require service life assessment and/or aging surveillance testing along with a rationale for why the items are critical, what parameters will be monitored, and what failure modes will be detected. The results of

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 9 of 54

service life testing shall be provided to the Government to be included in the Assessment Report and WSER as appropriate.

1.4.1.3.3.6 The contractor shall prepare, review, and provide test plans and test reports for tests required as a result of trend analysis and assessments.

1.4.1.3.3.7 The contractor shall analyze component-level AS test data, trends, and possible impacts documented in nonconformance documents, e.g., AFMC Form 202, Nonconforming Technical Assistance Request and Reply, field-generated MARs per TO 00-25-107, Maintenance Assistance.

1.4.1.3.3.8 The contractor shall conduct and provide shelf-life analysis for specific components as requested by the Government.

1.4.1.3.3.9 The contractor shall review any required AS test types and make recommendations for increased or decreased subsystem-level testing based on current and emerging service life estimates, and aging trends.

1.4.1.3.4 Nuclear Hardness and Survivability

1.4.1.3.4.1 The contractor shall perform hardness assessments for new/modified/existing equipment occurring/sustained under this contract. The contractor will evaluate and document changes to the Ground Subsystems for hardness and provide updates to Hardness Data Manuals and Hardness Critical Items (HCI).

1.4.1.3.4.2 The contractor shall perform hardness and survivability assessments which may include the development of models and tools, modified ground systems sustained equipment and evaluate changes to the Ground Subsystems for hardness and survivability.

1.4.1.3.4.3 The contractor shall provide Survivability Management Status Reports (SMSR) on quarterly or an as needed basis for sustained hardware.

1.4.1.3.4.4 The contractor will provide Ground Systems support to the ICBM Survivability Program Review (ISPR) and support to the weekly NH&S IPT chaired by NIE. As directed by NIA, the contractor will provide support to conferences and events in support of the NH&S IPT.

1.4.1.3.5 Nuclear Surety

1.4.1.3.5.1 The Air Force uses the DOD definition for Nuclear Weapons Surety as: materiel, personnel, and procedures which contribute to the security, safety, and reliability of nuclear weapons and to the assurance there will be no nuclear weapon accidents, incidents, unauthorized weapon detonations, or degradation in performance at the target. The contractor shall integrate nuclear surety requirements into the ICBM Ground Subsystems engineering processes.

1.4.1.3.5.2 The contractor shall comply with DOD requirements detailed in the CDRL

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 10 of 54

• DOD 3150.2 M, DOD Nuclear Weapon System Safety Manual • DODD 3150.2, DOD Nuclear Weapon System Safety Program • AF implementation of DOD requirements are described in Air Force Policy Directive

(AFPD) 91-1 and further detailed in: • AFI 91-101, Air Force Nuclear Weapons Surety Program • AFI 91-102, Nuclear Weapon System Safety Studies, Operational Safety Reviews, and

Safety Rules • AFI 91 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 • 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 • AFMC and AFNWC supplements

1.4.1.3.5.3 The contractor shall support the Government in maintaining the nuclear certification program and preserving the nuclear certification of MMIII weapon system. The nuclear certification program shall be IAW AFI 63-125, Nuclear Certification Program.

1.4.1.3.5.4 The contractor shall support the development of applicable Ground Subsystems certification criteria new or modified ICBM hardware and software components, subsystems and systems, support equipment, facilities, special test and maintenance programs.

1.4.1.3.5.5 The contractor shall prepare nuclear certification actions that document:

• Adverse effects on primary safety devices and ICBM weapon system features which control the following nuclear critical functions: authorization, pre-arming, launching, releasing, arming, and targeting as detailed in AFI 91-107, Design, Evaluation, Troubleshooting , and Maintenance Criteria for Nuclear Weapon Systems.

• Compliance with AFI 91-107 Design, Evaluation, Troubleshooting, and Maintenance Criteria for Nuclear Weapon Systems Table 1 which gives the Air Force established numerical probability requirements for obtaining an unintentional significant nuclear yield because of faults and failures in the ICBM system.

• Compliance with AFI 91-107 Design, Evaluation, Troubleshooting, and Maintenance Criteria for Nuclear Weapon Systems Table 2 which gives the Air Force established numerical probability requirements for preventing inadvertent critical function activation because of system faults and failures.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 11 of 54

1.4.1.3.5.9 The contractor shall support the ICBM System Integrity Verification (SIV) team by providing nuclear surety support and monitoring for compliance of applicable AFI 91-series policies related to Ground systems.

1.4.1.3.5.10 The contractor shall provide nuclear surety support to Ground Subsystems-related ICBM test and maintenance programs. Support shall include development of assessments, reports, and briefings to verify compliance with applicable AFI 91-series and 526 ICBMSW OI 91 01, Nuclear Surety and Nuclear Certification.

1.4.1.3.5.11 The contractor shall provide and implement a Certification Requirements Plan (CRP) to support nuclear surety as part of the software development effort.

1.4.1.4 Test Support

1.4.1.4.1 Test and Evaluation (T&E)

1.4.1.4.1.1 The contractor shall identify and define test requirements where applicable for all Ground Subsystems programs and for future assigned sustainment, modification, or acquisition programs associated with the Ground Subsystems.

1.4.1.4.1.2 The contractor shall perform T&E on all Ground Subsystems replacement, modification, and sustainment activities requiring test IAW AFI 99-103, Capabilities-Based Test and Evaluation and subordinate documents: ICBMSD OI 99-103, Test and Evaluation references related to AFPD 99-1, Test and Evaluation Process; AFI 99-103, Capabilities-Based Test and Evaluation; AFMCPD 99-1, Test Management; Air Force Materiel Command Instruction (AFMCI) 99-103, Test Management; and Air Force Nuclear Weapons Center Instruction (AFNWCI) 99-101, Nuclear Enterprise Test and Evaluation Management.

1.4.1.4.1.3 The contractor shall support test integration and scheduling, and conduct associated testing with WS effectiveness programs performed to measure AS, reliability, availability, maintainability, accuracy, and nuclear hardness and survivability.

1.4.1.4.1.4 The contractor shall develop and implement a Test and Evaluation Master Plan (TEMP), test procedures and test plans, and analyze test plans for correlation to specification, design and implement the ITT and TRR, execute and coordinate test activities, provide assistance as technical consultant, and make statistically viable recommendations. The contractor shall support all testing, to include developmental test, operational test, follow-on test and evaluation, qualification test, acceptance test, and integration test.

1.4.1.4.2 Operational Test and Evaluation (OT&E) Support

1.4.1.4.2.1 The contractor shall provide support for Follow-On T&E (FOT&E) associated with MMIII Effectiveness Programs including reliability, availability, maintainability, supportability, and hardness. Ground Subsystems assessment will determine effectiveness of Ground

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 12 of 54

Subsystems equipment based on results of OT&E events/exercises such as Flight Test, Olympic Play, Hardness Surveillance Electromagnetic Pulse (HSEP), and SELM test.

1.4.1.4.2.2 The contractor shall support the determination of requirements for FOT&E on all modification or acquisition programs associated with the Ground Subsystems. Vandenberg AFB OT&E often results in a situation or anomaly which results from preflight preparations that is not fully defined in published TO data.

1.4.1.4.2.3 The contractor shall make technical recommendations to Ground Subsystems counterparts, which will aid in anomaly resolution and allow completion of preparations for a successful OT&E flight test.

1.4.1.4.2.4 The contractor shall prepare briefing materials for the T minus 7-day and T minus 30-day reviews, describing the recommended and accepted deviations or guidance.

1.4.1.4.3 Hardness Surveillance Electromagnetic Pulse (HSEP) and Simulated Electronic Launch Minuteman (SELM) Testing

The HSEP is a field test activity performed on-site under a separate contract to determine the electromagnetic pulse (EMP) hardness characteristics of the LFs and MAFs. The purpose for SELM is to provide launch reliability data and test that the weapon system will send the first stage ignition signal when commanded.

1.4.1.4.3.1 The contractor shall provide technical support as necessary to identify, troubleshoot, and correct anomalies that are identified under HSEP or SELM testing.

1.4.1.4.3.2 The contractor shall participate in determining whether a HSEP or anomaly has resulted from 1) a failure of the test setup, interface, and/or test execution, or 2) a failure or deficiency in a Ground Subsystems-managed equipment item.

1.4.1.4.3.3 The contractor shall perform CLFA and recommend changes necessary to bring the equipment item’s performance back into specified functional requirements if the failure resulted from a Ground Subsystems-managed equipment item.

1.4.1.4.3.4 The contractor shall analyze subsequent test results in order to discern any equipment failure trends, and recommend mitigation as necessary.

1.4.1.5 Parts, Materials, and Maintenance

1.4.1.7.1 The contractor shall proactively identify and analyze problems with parts, materials, and processes related to Ground Subsystems and formulate and document recommended corrective actions.

1.4.1.7.2 The contractor shall support tasks for identifying parts substitutes and replacements, developing standards, and controls for repair parts modifications and replacement actions, and

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 13 of 54

maintaining the data required to perform these tasks consistent with 526 ICBMSW OI 20-04, Parts, Materials, and Processes Engineering.

1.4.1.7.3 The contractor shall provide the Diminishing Manufacturing Sources and Materiel Shortages (DMSMS) plan as required by DOD 4140.1 R, Supply Chain Materiel Management Regulation.

1.4.1.7.4 The contractor shall provide technical guidance and expertise to the ICBM DMSMS Working Group through ongoing design and development program progress, status, and system performance monitoring.

1.4.1.7.5 The contractor shall author DMSMS reports that detail the past and planned activities of the working group, major items of interest, DOD initiatives or regulations, and related issues necessary to assure DMSMS requirements are adequately met and managed.

1.4.1.7.6 The Contractor shall support all Government activities associated with executing portions of a DMSMS program, which include but are not limited to:

• Studies of limited production capabilities of Grounds Subsystem components, tooling/fixtures and support equipment

• Performing market research, including site visits, to determine current Grounds and MMIII industrial base capabilities

• Interfacing with Government efforts to modernize ICBM Grounds Subsystem industrial base capabilities.

1.4.1.7.7 The contractor shall implement a risk-based Counterfeit Prevention Plan to comply with Public Law 112–81 – Section 818, and MIL-STD-3018, Parts Management to minimize the impact of counterfeit parts or suspect counterfeit parts on Ground Subsystems.

1.4.1.7.8 The contractor shall be responsible for detecting and avoiding the use or inclusion of counterfeit parts or suspect counterfeit parts in Ground Subsystems delivered to the Government under this PWS.

1.4.1.7.9 The contractor shall perform logistics support analysis as requested by the Government to support parts, materials, and processes activities and provide annual input change pages for the Logistics Support Plan to include assessment studies and reports.

1.4.1.7.10 The contractor shall take preventative steps, at all levels of the respective supply chain, to commit suppliers to providing authentic materiel. Preventative actions include:

• Establishing measures to mitigate counterfeiting risks, • Managing residual risk throughout the life cycle, • Maintaining traceability of parts origination and distribution.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 14 of 54

See MIL-STD-3018, DOD Standard Practice for Parts Management, Standardization Document (SD)-19, Parts Management Guide, and SD-22, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Guidebook. The Defense Contract Management Agency (DCMA) serves as the interface between the Government and the contractor for identifying, eliminating, and reporting counterfeit parts. See DODI 4140.01, DOD Supply Chain Materiel Management Policy for further guidance on counterfeit materiel management.

1.4.1.7.11 The contractor shall identify counterfeit control measures including:

• Authentic parts maximization processes • Distributor assessment processes • Product assurance processes (authenticity verification techniques, counterfeit

material detection methods) • Materiel control processes (storage, handling, and shipping) • Counterfeit materiel disposition processes • Unused/replace parts and material disposition • Reporting processes to provide instances of counterfeit or suspect counterfeit

parts to the MAJCOM Trusted Systems and Networks focal point and in the Government and Industry Data Exchange Program (GIDEP) database (http://www.gidep.org)

• Measures of effectiveness to execute within sustainment planning documents. Establish a feedback loop such as: monitor, report, investigate, and eliminate known and suspected breaches to in-service inventory assets.

• Correct the problem or eliminate the source of supply from AF business until satisfactorily corrected.

1.4.1.7.12 The contractor shall flow the counterfeit prevention provisions to each first-tier supplier and require and verify that the supplier flow the same provisions to all sub-tier suppliers. The contractor shall ensure suppliers use approved inspection test methods, including destructive physical analysis (DPA), to detect potential counterfeit parts and materials.

1.4.1.7.13 Criticality Analysis/Supply Chain Risk Management

1.4.1.7.13.1 The contractor shall implement mitigations with attention to vulnerabilities in the supply chains for COTS/GOTS hardware and software.

1.4.1.7.13.1.1 Supply chain threat mitigations include complying with Society of Automotive Engineers (SAE) Standard AS5553, Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition (except procurement from other than an authorized source requires prior Government approval); purchasing goods from original equipment manufacturers, original component manufacturers, or their authorized resellers, franchisees, or distributors; mandatory use of contractor-approved shipping companies; ensuring that any foreign products are compliant with Government’s Customs Trade Partnership Against Terrorism (C-TPAT) program;

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 15 of 54

participation in the GIDEP; and requesting that hardware vendors provide procedures for authenticating each unit received.

1.4.1.7.13.2 The contractor shall identify for each Level I and Level II mission critical function identified in the criticality analysis, the associated logic bearing system components that implement, or introduce vulnerability to these functions (hereafter referred to as “critical components”).

1.4.1.7.13.3 The contractor shall demonstrate visibility into its supply chain for critical components, understanding the risks to that supply chain and has implemented or plans to implement risk mitigations to counter those risks.

1.4.1.7.13.4 The contractor shall plan for and implement countermeasures which mitigate foreign intelligence, technology exploitation, supply chain, and system vulnerabilities that result in the catastrophic (Level I) and critical (Level II) protection failures, including:

1.4.1.7.13.4.1 The application of supply chain risk management best practices, applied as appropriate to the development of the system. Supply chain risk management key practices may be found in the National Institute of Standards and Technology (NIST) Interagency Report (IR) 7622, Notional Supply Chain Risk Management Practices for Federal Information Systems, National Defense Industrial Association (NDIA) Version 1.0, Engineering for System Assurance.

1.4.1.7.14 Software/Hardware Depot Maintenance

The contractor shall perform all sustainment efforts IAW Chairman of the Joint Chiefs of Staff Manual (CJCSM) 6510.01, Information Assurance (IA) and Support to Computer Network Defense (CND), Enclosures B and C and the DISA IAVA Handbook and as required by this PWS.

1.4.1.7.15 Software/Hardware Maintenance Level I

The contractor shall implement mitigations with attention to vulnerabilities in the supply chains for COTS/GOTS hardware and software.

1.4.1.8 Demilitarization and Disposal

1.4.1.8.1 The contractor shall assist the Government in decisions to recapitalize or dispose of Ground Subsystems components, test and maintenance equipment, tooling, specialized fixtures, or any other hardware associated with Ground Subsystems Life Cycle Management.

1.4.1.8.2 The contractor shall assist the Government in creating and maintaining a current Demilitarization (DMIL)/Disposal Plan for all Grounds components IAW DOD 4160.28 V1, AFI 23-101, and AFI 20-110 and current legal and regulatory requirements, particularly Environmental Safety and Occupational Health (ESOH) considerations and explosives safety. The contractor-provided disposal plans, at a minimum, shall address:

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 16 of 54

• Disassembly to the lowest level required to gain access to the item, component, or material requiring removal for demilitarization and disposal

• Removal of older/obsolete items from the inventory first • Maximizing the use of equipment and parts from deactivated systems for

items in the current inventory • Demilitarization of items, including components, to protect national security

and public health and welfare • Protection of the environment and personnel by minimizing ESOH impacts,

resulting from demilitarization and disposal activities • Minimizing demilitarization and disposal costs by maximizing the re-use of

generated waste materials • Transportation of the item to removal/demilitarization/recycling area and

advise Government on the best available transportation options • Efficient processes to defuel, de-energize, and remove hazardous materials • Handling procedures for classified materials, explosives, dangerous articles,

munitions, and hazardous materials • Preferred and alternative methods for demilitarization and/or disposal. • Ensuring critical components are properly disposed to prevent reintroduction

of counterfeit parts into the supply chain.

1.4.1.9 ICBM Infrastructure and Equipment (IIE)

1.4.1.9.1 ICBM Infrastructure and Equipment (IIE) encompasses a broad reaching system within the overarching ICBM “Ground Subsystem.” ICBM Infrastructure replacement value exceeds $4B and historically requires an annual sustainment line of more than $50M. In FY17, AFNWC, stood up a new ICBM Infrastructure and Equipment Office (AFNWC/NIH) to improve overall weapon system integration and sustainment. The office replaced the former AFGSC Missile Engineer Office (MEO) and the majority of the MEO assets were transferred to the Systems Directorate on 1 October 2016.

1.4.1.9.2 IIE remains critical to Weapon System readiness, directly affecting ICBM availability, reliability, endurability and hardness/survivability. The purpose of the IIE Office is to enable ICBM operations and readiness through the analysis, testing, maintenance, sustainment, repair, and modernization of ICBM Infrastructure and Equipment (IIE) at Air Force ICBM Launch Facilities (LF’s), Missile Alert Facilities (MAF’s), training and test facilities, and the IIE interface with Aerospace Ground Equipment (AGE) and Operational Ground Equipment (OGE)..

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 17 of 54

1.4.1.9.3 The Contractor should be prepared to support ICBM Infrastructure and Equipment subsystems to include (but not limited to) the following:

MAF/LCC/LF POWER GENERATION & DISTRIBUTION • MAF Support Building Power Generation & Distribution System • LCEB/LF Standby Power Generation System • LCEB/LCC/LF Power Distribution • MAF/LF Cathodic Protection System

HEATING, VENTILATION, & AIR CONDITIONING • MAF/LFSB Heating & Ventilating • Other Facility Heating & Ventilating • LCC Bathroom Ventilating

MECHANICAL SPECIALTY SYSTEMS • Launcher Closure Doors • ESA Rooms/EMP Shielding • Platform/Winch/Hinges

WATER SUPPLY, DISTRIBUTION, & WASTE • MAF Water Source Systems • MAF Storage Systems • MAF Treatment Systems • MAF Distribution Systems • LCC Distribution Systems • MAFSB Fire Suppression Systems • MAF Waste Disposal Systems

MISCELLANEOUS SYSTEMS • MAFSB Security Monitor Panel • SCC Door Lock System • MAF/LF/HICS Gate Systems • MAFSB Fuel Systems • LCEB & MAFSB Underground & Day Tanks • Above Ground Tanks • LCEB & MAFSB Fire Alarm Systems • MAF Elevator Systems

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 18 of 54

• Brine Lines • Concrete and Steel Structures • Conduits • Fences • MAF Transporter Erector & Helicopter Pad Service Areas • MAF Structure & Detached Garages • LMR Towers • MAF Air Entrainment Systems • Power & Lighting Poles • Lightning/Grounding Systems

1.4.1.9 Specialty Engineering

1.4.1.9.1 System Safety

1.4.1.9.1.1 The contractor shall support the Government System Safety Program by identifying and controlling ICBM hazards, preventing mishaps, and tracking mishaps IAW System Safety Program Plan, Safety Study Plan, and Safety Study Report. This task is in support of the Government efforts to comply with requirements tailored from Military Standard (MIL-STD)-882, DOD Standard Practice: System Safety; AFPD 91-2, Safety Programs; AFI 91-202, The US Air Force Mishap Prevention Program; AFI 91-204, Safety Investigations and Reports, and Air Force Manual (AFMAN) 91-221, Weapons Safety Investigations and Reports, and Air Force policies.

1.4.1.9.1.2 The contractor shall establish a System Safety Program Plan IAW PWS Appendix C, Section I, A. Safety Program Requirements and document it per CDRL

1.4.1.9.1.3 The contractor shall perform system safety assessments and hazard analyses as directed and incorporate system safety practices into all phases of the program per MIL-STD-882, DOD Standard Practice: System Safety.

1.4.1.9.1.4 The contractor shall recommend or propose design requirements and management controls to prevent mishaps by eliminating hazards or reducing risks.

1.4.1.9.1.5 The contractor shall execute the system safety responsibilities for the areas of Fault Tree Development and Analysis, Nuclear Safety Assessment, human factors, reliability analysis, probabilistic risk assessments, and the capabilities to perform system safety engineering in general.

1.4.1.9.1.6 The contractor shall support the Government in performing the following system safety tasks on Ground Subsystems programs:

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 19 of 54

• Ensure critical system safety design features are identified and highlighted in technical data documents.

• Report potential WS hazards recognized during performance of contractual requirements. • Assess system safety impacts associated with ICBM TO drawing and specification changes

produced by field units, ICBMSD, AFGLSC, ICBM depot organizations, and/or subsystem contractors; TO data produced by ICBM modification programs (AFTO 22/252); field- or ICBMSD-generated -107

• Engineering Technical Assistance Requests (ETAR) per TO 00-25-107; depot-generated • Air Force Materiel Command (AFMC) IMT/Form 202, • Nonconforming Technical Assistance Request and Reply requests; field-generated -107, • Maintenance Assistance Requests (MAR) per TO 00-25-107; test directives, test plans and

engineering procedures developed in support of depot and operational test and maintenance projects.

1.4.1.9.1.7 The contractor shall report potential impacts of changes affecting system safety and in general, be responsible for ensuring all regulations and standards pertaining to system safety are strictly followed.

1.4.1.9.1.8 The contractor shall provide analysis of suspected safety issues as part of the normal course of sustainment.

1.4.1.9.1.9 The contractor shall implement the Safety Risk Management program established by the Government. Tasks include: risk assessment studies, preliminary hazards assessments, safety hazard analysis, safety compliance assessment reports, risk acceptance recommendations, briefings, point papers, white papers, technical memoranda, source data for ICBM TOs, and changes to the ICBM items in the Master Nuclear Certification List (MNCL).

1.4.1.9.1.10 The contractor shall support Government Safety program described in Basic PWS.

1.4.1.9.2 Environmental Engineering

1.4.1.10.2.1 The contractor shall comply with environmental regulations in support of Ground Subsystems acquisition, modification, and sustainment activities to include: AFPD 32-70, Environmental Quality. These environmental programs are identified in applicable regulations including AFI 32-7040, Air Quality Compliance; AFI 32-7041, Water Quality Compliance; AFI 32-7042, Solid And Hazardous Waste Compliance; AFI 32-7086, Hazardous Materials Management; AFI 32-7047, Environmental Compliance Tracking and Reporting; AFI 32-7061, The Environmental Impact Analysis Process; AFI 32-7063, Air Installation Compatible Use Zone Program; AFI 32-7064, Integrated Natural Resources Management; AFI 32-7065, Cultural Resources Management Program; AFI 32-7080, Pollution Prevention Program; and applicable supplements.

1.4.1.9.2.2 The contractor shall provide plans and permits to ensure compliance with environmental regulations in all assigned activities under this contract. This requirement

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 20 of 54

includes, as a minimum, pollution prevention, air quality, water quality, hazardous material and hazardous waste management, and environmental assessments.

1.4.1.9.2.3 The contractor shall prepare and provide a Programmatic Environmental, Safety, and Occupational Health (ESOH) Evaluation (PESHE) Plan to support acquisition and life cycle management of assigned programs for new or modified equipment or hardware.

1.4.1.9.3 Corrosion Prevention and Control

1.4.1.9.3.1 The contractor shall prepare and provide a Corrosion Prevention and Control Plan to support acquisition and life cycle management of assigned programs for new or modified equipment or hardware.

1.4.1.9.3.2 The contractor shall participate in the ICBM Corrosion Prevention Advisory Board meetings.

1.4.1.9.4 Electromagnetic Radiation

The contractor shall ensure the electronic, electrical, and electromechanical subsystems and electrical interconnections provided to the Government under this contract, function IAW with the performance requirements without interference as required, in compliance with MIL STD-461, Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, MIL-STD-464, Electromagnetic Environmental Effects Requirements for Systems and hardness requirements.

1.4.1.10 Task Log

The Task Log is used to track all tasks identified in the Grounds 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 Grounds 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 include but are not limited to: Conference Agendas, Briefing Materials, Meeting Minutes, technical reports, white papers and trade studies.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 21 of 54

1.4.2 Systems Engineering

The contractor shall perform systems engineering for Ground Subsystems hardware and software. The contractor shall transform operational needs into system performance parameters and apply systems engineering processes to ensure updates or upgrades to Ground Subsystems do not degrade operational readiness. The contractor’s systems engineering processes shall be consistent with Air Force Instruction (AFI) 63-101, Integrated Life Cycle Management and DODI 5000.02, Operation of the Defense Acquisition System, Enclosure 12, Systems Engineering.

1.4.2.1 Systems Engineering Requirements

1.4.2.1.1 The contractor shall transform an operational need into a description of system performance parameters and a preferred system configuration, using the requirements in this PWS and an iterative process of functional analysis, optimization, definition, design, and test and evaluation.

1.4.2.1.2 The contractor shall integrate technical parameters and assure compatibility of all physical, functional, and program interfaces in a manner that supports weapon system optimization.

1.4.2.1.3 Upon Government approval of an Engineering Change Proposal (ECP), the contractor shall design changes, modifications, and integration 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.4.2.1.4 The contractor shall provide designs that meet weapon system requirements from the appropriate weapon systems specifications.

1.4.2.2 Systems Engineering Process Management

1.4.2.2.1 The contractor shall develop, maintain, and implement an integrated SEMP across their program team (including subcontractors).

1.4.2.2.2 The SEMP shall define the overarching processes used to perform and manage systems engineering development and sustainment tasks in this PWS and be consistent with the Minuteman III Weapon System Sustainment Systems Engineering Plan 62-SEP.

1.4.2.2.3 The SEMP shall be maintained consistent with other contractor plans (e.g., Program Protection Implementation Plan (PPIP), Software Development Plan (SDP), Test Plans, and Contractor’s Corrective Action Plans).

1.4.2.2.4 The SEMP shall integrate reliability, safety, producibility, security, human factors, program protection, information assurance, and other related specialties into the total engineering effort.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 22 of 54

1.4.2.2.5 The SEMP shall include the configuration management plan.

1.4.2.2.6 The SEMP shall include the risk management plan.

1.4.2.2.7 The SEMP shall include the plan for data management.

1.4.2.2.8 The contractor shall implement the approved SEMP’s defined and disciplined processes across their program team (including subcontractors) for ICBM product development, sustainment, and service processes that produce repeatable results.

1.4.2.2.9 The contractor shall implement the SEMP to perform systems engineering for Ground Subsystems hardware and software, using processes consistent with the Capability Maturity Model Integration for Development and Services Level 3 (CMMI-DEV, CMMI-SVC), Version 1.3. The defined and disciplined processes for the Ground Subsystems shall be planned, implemented, and include:

• Readiness (entrance) criteria • Inputs and outputs • Standards and procedures for performing the work • Verification methods used to ensure process performance and product quality (e.g., peer

reviews) • Process and product measures used to manage the program • Completion (exit) criteria • Identification of roles and responsibilities of the participants and stakeholders and their

involvement throughout defined period of performance • Skilled people having adequate resources • Evaluation for adherence to the defined process

1.4.2.2.10 The contractor shall integrate and use the system engineering processes described in the SEMP, 62- and 63-series AFIs and ICBMSD OIs, and this PWS. This includes process reviews such as Requirements Validation Board, Risk Management Board, Configuration Control Board (CCB), ICWG, Program Protection Plan (PPP), and the risk database with utilization of collaborative system engineering methodology between the contractor, the Government, the ISC contractor, and any subsystem contract support. The contractor shall prepare presentations for the review boards.

1.4.2.3 Systems Engineering Level Evaluation and Correction Team (SELECT)

The contractor shall support the SELECT as required by providing data and information.

Note: The SELECT will be staffed under the ISC. The SELECT will determine the type of data and information. The SELECT provides high-level expertise as necessary to troubleshoot and provide correction recommendations for anomalies that occur during WS testing, operations, and maintenance.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 23 of 54

1.4.2.4 Risk Management

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

1.4.2.5 Integration

1.4.2.5.1 The contractor shall assess, advise, coordinate, complete, test, verify, validate, and document systems integration for Ground Subsystems.

1.4.2.5.2 The contractor shall be responsible for the integration of the activities identified with the Government, all ICBM contractors, and other stakeholders to include, but not limited to:

• AFGSC • STRATCOM • 20 AF • Navy Airborne Launch Control System (ALCS) • 625th Strategic Operations Squadron ALCS • 414th Supply Chain Management Squadron (equipment specialists/item

managers) • Vandenberg Air Force Base (AFB) Missile Range • AF Safety Center • National Security Agency • 309th Missile Maintenance Group (Strategic Missile Integration Complex

(SMIC), LF/LCC PDM Depot Field Team, etc.) • Missile Wings • AFNWC • Little Mountain Test Facility • NIH

1.4.2.5.3 The contractor shall ensure assessment and analysis of modifications are accomplished using Government integration processes as defined in the following Government documents: ICBMSD Operating Instruction (OI) 62-02, Interface Control Management and ICBMSD OI 62 03, Configuration Management Policies and Procedures.

1.4.2.5.4 The contractor shall proactively engage with the Government, ISC contractor, other subsystem contractors, and those contractors awarded future modification, reverse engineering and baseline compliance efforts to ensure any proposed modifications will have no negative impact on the Ground Subsystems, other subsystems, or the weapon system as a whole.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 24 of 54

1.4.2.5.5 The contractor shall coordinate with the ISC contractor to assess and validate all modifications, reverse engineering and baseline compliance for any potential integration impact(s) on the subsystems or the weapon system as a whole.

1.4.2.6 Trade Studies

1.4.2.6.1 The contractor shall provide inputs and analyses to the Government when requested to support trade studies. At a minimum, all trade studies shall include: requirements traceability, lifecycle costs, a comprehensive schedule, maintain compliance with nuclear technical performance criteria (as applicable), meet all information assurance requirements, and include impacts to system performance, risks, logistics, infrastructure, system architecture, operations, manpower, training, data, intellectual property, documentation, drawings, laboratory assets, support equipment, GFI, GFE, and GFP. All other impacts, changes, and project elements must also be included.

1.4.2.6.2 The contractor shall perform and document trade studies on those contracts and programs awarded to them at the Ground Subsystems-level.

1.4.2.7 Configuration Management (CM)

1.4.2.7.1 For hardware, software, firmware, protocols, and interfaces, the contractor shall perform configuration identification, configuration control, configuration status accounting, and configuration audits to maintain the integrity of Ground Subsystems. Configuration management processes shall be IAW ANSI/EIA-649, National Consensus Standard for Configuration Management and shall be consistent with ICBMSD 62-CMP, ICBM Configuration Management Plan, OI 62-03, Configuration Management Policies and Procedures, and OI 62-13, Software Configuration Management (CM).

1.4.2.7.2 The contractor’s plan for configuration management shall include:

• Maintaining control of baselines and environments including those delivered by subcontractors and associate contractors

• Ensuring contractor’s CM processes and tools interoperate with the Government’s CM processes and tools

• Conducting Functional Configuration Audits (FCA) and Physical Configuration Audits (PCA) consistent with ICBMSD OI 62-04, Configuration Audits, to verify the functional and physical baselines of products and demonstrate compliance to the technical requirements of the developmental and product specifications.

• Maintaining product baseline after PCA • Providing Government-approved baselines to the NSCCA/PATE/IV&V

contractor, upon direction of the Government

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 25 of 54

1.4.2.7.3 The contractor shall provide the plan for hardware and software configuration management in the SEMP consistent with ICBMSD 62-CMP, ICBM Configuration Management Plan

1.4.2.7.4 The contractor shall provide CM support for the following types of tasks:

1.4.2.7.4.1 Provide support through the Government to the Government Configuration Control Board (CCB) consistent with ICBMSD OI 62-01, Configuration Control Board (CCB).

1.4.2.7.4.2 Provide engineering change proposals (ECP) and specification change notices (SCN), reference ICBMSD OI 62 06, Engineering Orders Policies/Procedures.

1.4.2.7.4.3 Maintain the engineering baseline by providing updates to process/material specifications, hardness data manuals, the IDE, and other required documentation.

1.4.2.7.4.4 Maintain drawing currency through end item drawing and interface control drawing (ICD) and interface requirement specification (IRS) updates.

1.4.2.7.4.5 Assist Government CM activities supported through TopVue or other equivalent software packages. This assistance shall include:

1.4.2.7.4.6 Route and receive approval of engineering drawings, CCB support, ECPs, SCNs, top-level parts data, indentured parts lists (IPL), ICDs, specifications, and configuration items.

1.4.2.7.4.7 Submit drawings, updates, and metadata that are compatible with the Joint Engineering Data Management Information and Control System (JEDMICS).

1.4.2.7.4.8 The contractor shall identify issues/concerns with interface requirements and drawings, including contractor, vendor, and subcontractor contract items, as well as Government-furnished equipment (GFE), Government-furnished software (GFS), and facilities relating to Ground Subsystems activities consistent with ICBMSD OI 62-02, Interface Control Management. The contractor shall provide Ground Subsystems interface control through:

• Participating as a member of the ICWG • Providing corrective action to interface control problems • Report potential and evaluate Class I (those affecting form, fit, or function of an item)/Class

II changes, ECPs, waivers, and deviations for interface impacts • Following interface control guidelines contained in the ICBM-HDBK-02, Intercontinental

Ballistic Missile Interface Control Management Handbook

1.4.2.8 Subsystem/End Item Specifications

1.4.2.8.1 The contractor shall prepare specifications to support future acquisition and life cycle management of the items IAW the Government-approved SEMP.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 26 of 54

1.4.2.8.1.1 The specifications prepared by the contractor shall define the functional/ performance requirements, interface requirements, and technical constraints for each system element along with the qualification provisions required to verify achievement of each specified requirement.

1.4.2.8.2 At the product level, the specification shall define the requirements for a design solution that meets the requirements and constraints of the higher-level specifications.

1.4.2.8.2.1 The design solution shall meet all requirements, other applicable specifications and ICDs, and be operationally effective, suitable, sustainable, and cost-effective; meet DOD security, protection, nuclear surety, and Cybersecurity requirements; facilitate interconnections with other classified systems; and meet DOD net-readiness standards for interoperability, supportability, and functional capability.

1.4.2.8.3 Product level specifications shall also incorporate requirements and verification methods needed for acceptance and first article inspections when required.

1.4.2.9 Software Development

The contractor shall develop and modify both nuclear and non-nuclear certified software IAW AFMAN 91-119, Safety Design and Evaluation Criteria for Nuclear Weapons Systems Software in support of Ground Subsystems operational needs. The contractor shall be capable of transforming an operational need into a description of system performance parameters and apply software engineering process to ensure software updates or upgrades to Ground Subsystems do not degrade operational readiness.

1.4.2.9.1 Software Engineering Process Management

1.4.2.9.1.1 The contractor shall implement software engineering processes for ICBM software product development and sustainment processes consistent with the Level 3 CMMI-DEV, Version 1.3 for software.

1.4.2.9.1.2 The defined and disciplined processes for the Ground Subsystems shall be planned, implemented, and include:

• Readiness (entrance) criteria • Inputs and outputs • Standards and procedures for performing the work • Verification methods used to ensure process performance and product quality

(e.g., peer reviews) • Process and product measures used to manage the program • Completion (exit) criteria • Identification of roles and responsibilities of the participants and stakeholders and

their involvement throughout defined period of performance • Skilled people having adequate resources • Evaluation for adherence to the defined process

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 27 of 54

1.4.2.9.1.3 The contractor shall develop, maintain, and implement an integrated Software Development Plan (SDP) across their program team (including subcontractors) for all Ground Subsystems software. The SDP shall be maintained consistent with other contractor plans (e.g., Systems Engineering Management Plan (SEMP), Test Plans, Contractor’s Corrective Action Plans, Management Plan, etc.).

1.4.2.9.1.3.1 The SDP shall integrate software reliability, maintainability, nuclear surety, system safety, producibility, security, survivability, human factors, program protection, information assurance, and other related specialties into the total software engineering effort.

1.4.2.9.1.3.2 The SDP shall address software items and non-developmental software (e.g., Commercial Off-the-Shelf (COTS) and Government Off-the-Shelf (GOTS)) for the following software categories (including the software portion of firmware):

1.4.2.9.1.3.2.1 Ground Subsystems (e.g., mission planning; tracking and commanding; data archive and storage; data processing; data analysis and dissemination; mission support; networking, information systems, infrastructure, and services; databases and tools support; and integration support)

1.4.2.9.1.3.2.2 Other software (e.g., applications, security, safety, training, modeling, simulation, analysis, database support, automatic test equipment, test facility and environment, and maintenance) used in:

• Satisfying, verifying, or validating requirements • Testing (e.g., test scripts) • Performing or supporting operations

1.4.2.9.1.3.3 The SDP shall include a software CM system that addresses management of both the software code and related technical documentation, utilizing automated configuration management tools that enforce controls for software development and maintenance; preventing unauthorized modifications to software to include software that has not yet been moved to the Government software control center; and limiting privilege of application programmers to change production code and documentation.

1.4.2.9.1.3.4 The SDP shall include the Software Quality Assurance Plan.

1.4.2.9.1.3.5 The SDP shall be coordinated with the appropriate Government stakeholders including the GSD, ICBMSD Engineering Division, and the ISC contractor.

1.4.2.9.1.4 The contractor shall define and implement a software configuration management system to:

1.4.2.9.1.4.1 Ensure all incremental software data and item deliveries remain in synchronization at all times and are documented accordingly.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 28 of 54

1.4.2.9.1.4.2 Ensure all commercial and noncommercial computer programs (inclusive of firmware) delivered to the Government for fielding are identical to PCA-approved versions.

1.4.2.9.1.4.3 Include all developmental software, COTS/GOTS, non-developmental items (NDI), or proprietary software required to install, check-out, and use the GSSC software.

1.4.2.9.1.4.4 Transfer GSSC delivered software to the Government with all files and manuals to ensure it can be recreated from provided source files (e.g., “make” files).

1.4.2.9.1.4.5 Ensure all software and associated products are correctly transferred from the contractor’s database to the Government’s database.

1.4.2.9.1.4.6 Limit the privilege of application programmers to change production code and documentation, and periodically review those privileges.

1.4.2.9.1.4.7 Deliver updates to the Government-owned software baseline through the Government processes (ICBMSD OI 62-01, Configuration Control Board (CCB)) to the CCB, and other panels at the various milestones to ensure changes are not made without Government involvement.

1.4.2.9.2 Software Engineering Requirements

1.4.2.9.2.1 The contractor shall develop, document, and maintain software requirements and software design. The contractor shall perform integration of requirements and design implementation between concurrent programs, impacting the same Computer Software Configuration Items (CSCI).

1.4.2.9.2.2 The contractor shall maintain consistency and traceability between software products developed and maintained (e.g., requirements, use cases, architecture documentation, design artifacts, code, and test cases).

1.4.2.9.2.3 The contractor shall identify interdependencies between software artifacts and maintain them in an automated system to support software design analysis and assessment of impacts due to changes.

1.4.2.9.2.4 The contractor shall perform integration of requirements across the various software end items to ensure that a requirement affecting multiple CSCIs is implemented and tested properly. Testing will include both CSCI qualification testing and weapon system testing to ensure correct interfaces and function within the weapon system.

1.4.2.9.2.5 The contractor shall develop, maintain, and implement a plan for analyzing and correcting all problems and anomalies found during all phases of the software life cycle into the Corrective Action Plan.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 29 of 54

1.4.2.9.2.6 The contractor shall evaluate software products and control the software development through proactive analysis and corrective action (e.g., cost, schedule, tasks, progress of peer reviews, product metrics, integration, verification).

1.4.2.9.2.7 The contractor shall plan, perform, and document the integration, regression testing, and qualification testing of software items for each build, including support of WS integration.

1.4.2.9.2.8 The contractor shall develop software test reports addressing testing results to include any anomalies discovered during testing and mitigation requirements.

1.4.2.9.2.9 The contactor shall develop a Software Version Description (SVD) document, describing the contents and versions of the software code being delivered and its related documentation being represented in the software delivery.

1.4.2.9.2.10 The contractor shall develop, maintain, and follow plans for transitioning each software end item to operations and sustainment.

1.4.2.9.2.11 The contractor shall manage the program baseline until completion of FCA/PCA.

1.4.2.10 Hardware Development

1.4.2.10.1 The contractor shall be capable of performing hardware development in support of Ground Subsystems operational needs.

1.4.2.10.2 The contractor shall be capable of transforming an operational need into a description of system performance parameters and apply systems engineering processes to ensure hardware updates or upgrades to Ground Subsystems do not degrade operational readiness.

1.4.2.11 Weapon System Effectiveness Report (WSER) and Data book

The contractor shall provide Grounds input to the WSER. This input requires qualified personnel that understand the Reliability model and have applicable knowledge of inputs into the WSER. Tasks include but are not limited to:

• Identifying data needs • Understanding system-level WSER report and what is needed from Grounds to

report at the system level • Identifying how Grounds will meet data needs. Examples of data sources:

destructive physical analysis, CLFA results in addition to the traditional Force Development Evaluation (FDE), and Aging Surveillance.

• Planning needed to capture required data • Execution of activities needed to capture data • Analysis of data • Production of standalone Grounds WSER data book • Integration of Grounds assessment into WSER as required

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 30 of 54

• Communication of Grounds assessment to stakeholders

1.4.2.12 Technical Order Support

1.4.2.12.1 The contractor shall provide support to the ICBM TOMA for Grounds related activities as needed. Activities shall include creation of source data for new procedures related to sustainment of Grounds hardware and software. The contractor shall also provide TO support for TCTOs and AF Technical Order (AFTO) 22 and AFTO 252’s as required. Support for TO and TCTO validation and verification activities will also be required as necessary.

1.4.2.12.1.1 In support of the Modification/Replacement Program, the contractor shall:

• Provide source data electronically which identifies the required changes to existing TO(s) IAW AFI 21-302, Technical Data Requirements for Logistic Support

• Provide new TO(s) to include COTS Manual • Provide TCTOs for modification implementation • Validate TO(s) and/or TO changes, using AFTO Form 27, Preliminary Technical Order

(PTO) Publication Change Request (PCR)/TO Verification Record/Approval IAW ICBMSD OI 23-01, Technical Order Management

• Participate in Ground Subsystems T.O. reviews (30%, 80%, PPRs, etc.) and development of new procedures, attending reviews either in the field or at depot

1.4.2.12.1.2 The contractor shall create, review, and evaluate source data in AFTO Form 252, Technical Order Publication Change Request format for recommended changes to TOs as required.

1.4.2.12.1.3 In support of sustainment programs, the contractor shall

• Format and provide TCTOs IAW T.O. 00-5-15, Technical Manual Air Force Time Compliance Technical Order Process and AFI 21-302, Technical Data Requirements for Logistic Support

• Provide support for AFTO 22 changes • Support conversion of commercial/contractor procedure documents to AFTO 252, Technical

Order Publication Change Request format • Develop/Acquire information to operate, maintain, and train on the equipment • Validate TO(s) and/or TO changes, AFTO Form 27, Preliminary Technical Order (PTO)

Publication Change Request (PCR)/TO Verification Record/Approval IAW ICBMSD OI 23-01, Technical Order Management

1.4.2.12.1.4 The contractor shall participate in the Technical Data Management Working Group (TDMWG) if requested.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 31 of 54

1.4.3 Program Management Support

1.4.3.1 Program Management Information

1.4.3.1.1 The Contractor shall establish and maintain the capability to assist the Government to report program cost, schedule, technical issues, and status for sustainment tasks and future efforts or programs.

The Contractor shall organize IPT and program information in a comprehensive and sufficiently detailed manner to provide insight into program and subcontractor approach and status.

1.4.3.1.2 The Contractor shall define and disclose work-around recovery plans for all issues and delays.

1.4.3.1.3 The Contractor shall support all cost risk assessments with appropriate cost analyses and estimating or logistics cost models.

1.4.3.1.4 The Contractor shall de-conflict at a minimum with previously defined deployment plans, Management Plan, and Technology Mission Area Plans when planning all work

1.4.3.1.5 The Contractor shall prioritize support efforts in accordance with (IAW) GPM direction, to include tasks described as “significant” and “critical,” and provide a prioritized list of efforts to the Government Program Manager (GPM) upon request.

1.4.3.2 General Programmatic Support

The Contractor will support the Ground’s IPTs as well as individual programs by assisting as needed in the following activities:

1.4.3.2.1 Provide technical writing capability to include writing test plans and complying with ICBMSD test OIs.

1.4.3.2.2 Requests for data, briefings, background papers, technical reports and other inquiries.

1.4.3.2.3 Support all Program Reviews and IPT meetings with relevant information to help resolve challenges and issues.

1.4.3.2.4 Record meeting minutes and distribute to all IPT members as required.

1.4.3.2.5 Support meetings as requested by ICBMSD IPT members including but not limited to:

• Support Technical Evaluation Review Boards (TERBs) • Safety Review Boards (SRBs) • Sustainment Management Reviews (SMRs) • Program Management Reviews (PMRs)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 32 of 54

1.4.3.2.6 Maintain and update subsystem and end item baselines.

1.4.3.3 Program Management Processes

1.4.3.3.1 Integration Management

1.4.3.3.1.1 Develop Program Management Plan: The contractor shall define, prepare, and coordinate all subsidiary project plans integrating them into a comprehensive program management plan. The contractor’s program planning shall incorporate cost effective program management concepts and use approaches that will provide affordable services and products meeting system requirements.

1.4.3.3.1.2 Direct and Manage Program Work: The contractor shall lead and perform the work defined in the Program Management Plan and implement approved changes to achieve the program objectives.

1.4.3.3.1.3 Perform Integrated Change Control: The contractor shall review all requests for changes or modifications to project documents, deliverables, baselines, or Project Management Plans, obtain Government approval, and manage and document those changes which are approved IAW the ICBMSD OI 62-01, Configuration Control Board.

1.4.3.3.1.4 Close Project or Phase: The contractor shall finalize all activities across all program management processes areas defined in the Program Management Processes section of this PWS to formally complete the project or phase.

1.4.3.3.2 Scope Management

1.4.3.3.2.1 Plan Scope Management: For each project, the contractor shall create a Scope Management Plan that documents how the project scope will be defined, validated, and controlled.

1.4.3.3.2.2 Collect Requirements: The contractor shall determine, document, and manage stakeholder needs and requirements to meet program objectives.

1.4.3.3.2.3 Define Scope: The contractor shall develop a detailed description of the project and product.

1.4.3.3.2.4 Create Work Breakdown Structure: The contractor shall subdivide project deliverables and project work into manageable components. The Contract Work Breakdown Structure (CWBS) shall be generated at level 4 or greater for all discrete projects, unless specifically relieved by the Government.

1.4.3.3.2.5 Validate Scope: The contractor shall obtain formalized acceptance of the completed project deliverables.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 33 of 54

1.4.3.3.2.6 Control Scope: The contractor shall monitor the status of the project and product scope and manage changes to the scope baseline.

1.4.3.3.3 Time Management

1.4.3.3.3.1 Plan Schedule Management: The contractor shall establish procedures and documentation for planning, developing, managing, executing, and controlling the project schedule.

1.4.3.3.3.2 Define Activities: The contractor shall identify and document the specific actions to be performed to produce the project deliverables.

1.4.3.3.3.3 Sequence Activities: The contractor shall identify and document relationships among the project activities.

1.4.3.3.3.4 Estimate Activity Resources: The contractor shall estimate the type and quantities of material, human resources, equipment, and supplies required to perform each activity.

1.4.3.3.3.5 Estimate Activity Durations: The contractor shall estimate the number of work periods needed to complete individual activities with estimated resources.

1.4.3.3.3.6 Develop Schedule: The contractor shall analyze activity sequences, durations, resource requirements, and schedule constraints to create a project schedule model.

1.4.3.3.3.7 Control Schedule: The contractor shall monitor the status of project activities to update project progress and manage changes to the schedule baseline to achieve the plan.

1.4.3.3.3.8 Corrective Action Plans: For issues or delays, the contractor shall define and provide corrective action plans consistent with previously defined deployment plans.

1.4.3.3.4 Cost Management

1.4.3.3.4.1 Plan Cost Management: The contractor shall establish procedures and documentation for planning, managing, expending, and controlling project costs.

1.4.3.3.4.2 Estimate Costs: The contractor shall develop an approximation of the monetary resources needed to complete project activities.

1.4.3.3.4.3 Determine Budget: The contractor shall aggregate the estimated costs of individual activities or work packages to establish an authorized cost baseline.

1.4.3.3.4.4 Control Costs: The contractor shall monitor the status of the project to update the project cost and manage changes to the cost baseline.

1.4.3.3.4.5 Individual Baseline Reviews: The contractor shall establish and maintain the capability to prepare and conduct Integrated Baseline Reviews (IBR) as directed.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 34 of 54

1.4.3.3.4.6 Cost Related Reports: The contractor shall report current and projected program cost, schedule, technical issues, and status. Reports shall be comprehensive and sufficiently detailed to provide insight into program approach, status, and prognosis including subcontractors’ activities.

1.4.3.3.5 Quality Management

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

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

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

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

1.4.3.3.6 Human Resource Management

1.4.3.3.6.1 Plan Human Resource Management: The contractor shall identify and document project roles, responsibilities, required skills, reporting relationships, and create a staffing management plan.

1.4.3.3.6.2 Build Team Structure and Partnership: The contractor shall confirm human resource availability and obtain the team necessary to complete project activities. The contractor shall establish and maintain an organizational team structure (including subcontractors) possessing the knowledge, skills, processes, and experience necessary to effectively support all GSSC requirements. See Section J Attachment 12, Labor Categories Description for personnel qualifications.

1.4.3.3.6.2.1 The contractor shall ensure skills, experience, training, and education are directly related to the specific service or specialty which the individual is designated to perform.

1.4.3.3.6.2.2 The contractor shall ensure at all times, personnel have sufficient expertise to perform the tasks identified in this PWS.

1.4.3.1.6.2.2.4 Depending on the scope of add-on efforts, the level(s) of expertise required on each add on will be evaluated separately outside of these requirements, if applicable.

1.4.3.3.6.2.3 The contractor shall provide an initial listing of all personnel, positions, etc.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 35 of 54

1.4.3.3.6.2.5 The contractor shall submit resumes of all key personnel. Key personnel specified for this GSSC effort are considered to be essential to work performance of the Ground Subsystems support in accordance with (IAW) the work breakdown structure. Key personnel shall comply with Section J, Attachment 12 labeled “Labor Categories Description” qualifications.

1.4.3.3.6.2.6 In the event an individual designated as key personnel retires, is reassigned, or otherwise terminates his or her employment, the contractor shall notify the Procuring Contracting Officer (PCO), in writing, of such action at least 30 days prior to the effective date of this action, or within 5 business days if action is immediate/unplanned. The notification shall include name of the individual leaving, the effective date of departure, and the name and resume of the replacement individual to be assigned to the key position. The contractor shall provide updated key personnel resumes to the PCO IAW Clause 9952.736-H736.

1.4.3.3.6.3 Develop Team: The contractor shall improve competencies, team member interaction, and overall team environment to enhance project performance.

1.4.3.3.6.4 Manage Team: The contractor shall track team member performance, providing feedback, resolving issues, and managing changes to optimize project performance.

1.4.3.3.7 Subcontractor Management

1.4.3.3.7.1 The Contractor shall manage all subcontracted activities required to meet requirements.

1.4.3.3.7.2 The 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 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.

1.4.3.3.7.3 Plan Subcontractor Procurement Management: The contractor shall document project subcontracting decisions, specifying the approach, and identifying potential subcontractors.

1.4.3.3.7.4 Conduct Subcontractor Procurements: The contractor shall obtain subcontractor responses, select subcontractors, award a contract and ensure proper flow-down of Government PWS requirements.

1.4.3.3.7.5 Control Subcontractor Procurements: The contractor shall manage subcontractor relationships, monitoring contract performance, and making changes and corrections as appropriate. The contractor shall be responsible for ensuring proper integration and test of products, and any changes to the products from a subcontractor.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 36 of 54

1.4.3.3.7.6 Close Subcontractor Procurements: The contractor shall complete and document each project subcontractor procurement.

1.4.3.4 Transition

1.4.3.4.1 The contractor shall cooperate with the incumbent contractor and the ISC contractor to ensure a smooth transition of support for the Ground Subsystems.

1.4.3.4.2 Following the Contract Post Award Conference, the contractor shall meet with the Government (with ISC support) and incumbent contractor to jointly plan transition of responsibility and workload.

1.4.3.4.3 The contractor shall submit a Transition Plan for approval by the Government.

1.4.3.4.3.1 The contractor shall identify, in the Transition Plan, the risks for transitioning Ground Subsystems tasks from the incumbent and provide level of the identified risks and the criteria used. The Transition Plan shall include recommended mitigation strategies to overcome the identified transition risks.

1.4.3.4.3.2 The contractor shall include, in the Transition Plan, a transition schedule, detailing identification, impacts, and mitigation(s) for on-going Ground Subsystems efforts. The contractor shall execute the Transition Plan and be responsible for performance of all tasks covered within this PWS not later than 6 months after the Contract Post Award Conference. It is the intention of the Government to transition as quickly and effectively away from the incumbent as possible. The transition schedule shall accommodate a phased approach to transition tasks quickly and efficiently with no impact to current operations.

1.4.3.4.3.3 The contractor shall address, in the Transition Plan, all necessary material used in the execution of sustainment and acquisition in support of the Ground Subsystems. At minimum, the contractor shall identify how Government-furnished property (GFP), software code (and associated compilers), data, documentation, tools, and models can be effectively used to ensure completion of all tasks covered within this PWS while avoiding, to the maximum extent possible, negative impacts to on-going Ground Subsystems efforts on other contracts.

1.4.3.4.3.3.1 The contractor shall have the capability to establish or have access to the facilities, equipment, and qualified personnel necessary to meet the requirements of the PWS. The contractor shall have the ability to obtain and effectively utilize these facilities, equipment, and qualified personnel not later than 6 months after the Contract Post Award Conference. The Government is not obligated to provide these facilities/equipment; however, the contractor may opt to make arrangements or partnerships to use Government or other facilities/equipment.

1.4.3.4.3.3.2 If the contractor proposes alternative tools, models, equipment, etc., in supporting Ground Subsystems sustainment and acquisition, the verification, validation, and accreditation of those items shall be included in the Transition Plan.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 37 of 54

1.4.3.4.4 The contractor shall describe, in the Transition Plan, how the entrance and exit criteria will be accomplished for each task, the responsible person for the respective contractors, and the milestone schedule for achieving transfer of responsibility.

1.4.3.4.5 The contractor shall present any issues regarding the transfer of data, tools, and models used in the execution of sustainment and acquisition support to the PCO for equitable resolution.

1.4.3.4.6 The contractor shall document responsibility transfer for each task with the incumbent contractor and submit a copy of the transfer documents to the Government Procuring Contracting Officer (PCO).

1.4.3.4.7 The contractor shall meet with the Government on an agreed upon schedule (at least once every 2 weeks) to review the transition schedule, report status, and track progress until all tasks have been transitioned.

1.4.3.5 Data Rights

All data developed, delivered and/or otherwise provided in performance of this contract shall be in accordance with:

• Attachment titled “Government Rights in Data (GRID)” • Attachment titled “Contract Data Requirement List (CDRL) Instructions &

Master Listing”

1.4.3.6 Data Management

The contractor shall populate and maintain IMDB and other automated information systems as appropriate with all applicable data and documentation regarding the Grounds subsystem. This will include CLFA results, test and production data, test plan and reports, engineering change orders, and engineering change requests.

1.4.3.6.1 The contractor shall develop a plan for managing program data in collaboration with the Government. The contractor’s plan for managing program data shall include:

• Maintaining a Data Accession List (DAL) on the EDI • Providing Government access and ability to download all items on the EDI • Transferring historical electronic data from the incumbent contractor and

Government-managed systems to the EDI with no data loss • Transferring historical hard copy data from the incumbent contractor to the

contractor facility which shall include storage and retrieval capability

1.4.3.6.2 The contractor shall provide the plan for managing program data in the Systems Engineering Management Plan (SEMP).

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 38 of 54

1.4.3.6.3 The contractor shall begin executing the plans for data management within 5 days of the PCO notifying the contractor of SEMP approval.

1.4.3.6.4 The contractor shall use a digital delivery system approved by the PCO (e.g., e mail, direct electronic access) to minimize program hard copy documentation.

1.4.3.6.5 The contractor shall use the digital delivery system to generate record, disclose, and deliver technical data over the life of the contract.

1.4.3.6.6 The contractor shall provide a DAL of all data items required to execute the program, including Contract Data Requirements List (CDRL), nondeliverable data (e.g., assembly instructions, development specifications and manufacturing instructions, unique tooling documents, and engineering notes and records), and subcontractor and associate contractor data.

1.4.3.6.7 The contractor shall provide Government access to all data items listed in the DAL.

1.4.3.6.8 Should the Government develop and deploy an integrated data environment (IDE), the contractor shall collect data from numerous tools, both contractor and Government-managed, with the goal of ensuring all Ground Subsystems data transitions with no data loss, compatibility issues, or data inaccuracies, to the new IDE.

1.4.3.6.9 The Contractor shall be able to gain and maintain access to a Government repository to submit Data Deliverables.The contractor shall ensure the integrity of the data pertaining to Ground Subsystems within the IDE, including delivered data is compatible and data modifications and versioning is controlled. The contractor shall be capable of storing Government hard copy data as required

1.4.3.6.10 The contractor shall ensure the integrity of the data pertaining to Ground Subsystems within the IDE, including delivered data is compatible and data modifications and versioning is controlled. The contractor shall be capable of storing Government hard copy data as required.

1.4.3.6.11 The contractor shall ensure hard copy data is compatible with the ISC created Technical Data Package Index tool that facilitates locating and viewing Government hard copy data. All new hardcopy data indexed and/or stored by the contractor shall be considered delivered to the Government for purposes of data rights.

1.4.3.7 Modification/Replacement/New Requirement Oversight

1.4.3.7.1 The Contractor shall support the Government in design changes and modifications to the Grounds 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.4.3.7.2 The Contractor shall provide oversight of all their modification/replacement subcontracts and ensure the Government is presented with options to receive the best value.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 39 of 54

1.4.3.8 Earned Value Reporting

1.4.3.8.1 The Contractor is not required to provide the GPM Earned Value Management (EVM) reporting for the Sustainment Engineering TO IAW DODI 5000.02 Table 8 (EVM Application Requirements) for “Level of Effort” work.

1.4.3.8.2 Subsequent Task Orders that meet the requirements for EVM reporting are to provide EVM reporting from EVM systems that adhere to the guidelines in the ANSI/EIA - 748 Standard and the Department of Defense Earned Value Implementation Guide (EVMIG). All efforts estimated over $20M will provide EVM reporting in accordance with the prevailing Department of Defense Data Item Description (DID). Efforts considered high interest or high risk estimated below $20M may be required to provide EVM reporting and will be determined when the effort is added to the contract. The WBS and level of reporting will be negotiated when additional efforts are added. All efforts that are not required to provide EVM reporting are required to provide monthly cost reports that contain at a minimum expended hours and costs in an agreed upon contractor format.

1.4.3.9 Integrated Master Plan (IMP)

1.4.3.9.1 The Contractor shall assist the Government in:

• Correcting deficiencies identified through sustainment activities • Correcting parts obsolescence issues • Responding to changing operational requirements • Incorporating technological advances • Extending Grounds Subsystem service life • Maintaining all Grounds Subsystem-related IMPs • Maintaining IMP-supporting data which is easily integrated into the ICBM IMP, Integrated

Master Schedule (IMS), and weapon system Roadmap • Producing program planning concepts which consider and incorporate cost effective program

management concepts, such as Integrated Product Development, Acquisition Streamlining, Electronic Data Transfer, Use of Commercial Practices, and approaches that will provide affordable services and products that meet system requirements

1.4.3.10 Integrated Program Management Report (IPMR)

1.4.3.10.1 The Contractor shall (if directed by the Government) provide information to, as well as define and maintain, IPMRs as required by the Governement for all development, procurement and repair programs as required.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 40 of 54

1.4.4 Knowledge Transfer (KT)

1.4.4.1 The Contractor shall assist the GPM in creating, executing, and maintaining a KT program which addresses:

• The ICBMSD Grounds Subsystem knowledge base • Critical ICBM Grounds technical skills • Critical ICBM Grounds technical capabilities

1.4.4.2 Additionally, the contractor shall:

• Identify KT topics and provide a plan to the ICBMSD Branch Chief(s) for approval. Upon said approval the training shall be prepared and delivered

• Maintain a log of all training and provide as part of the Award Fee meeting period end. • Archive all training materials in IDR

1.4.5 Travel

1.4.5.1 The Contractor shall perform travel in support of this effort, as required on a Cost Reimbursable No Fee (CRNF) CLIN basis. Travel performed in support of this effort will comply with FAR 31.205-46. Travel requests outside of preapproved travel occurrences in support of IPTs shall be initiated via taskers in the ITTS Task Log. Tasks must be approved by the appropriate Government IPT or Branch Chief personnel.

1.4.6 Contractor Manpower Reporting

1.4.6.1 The Contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Grounds Subsystem via a secure data collection site. The contractor is required to fill in all required data fields completely and accurately at http://www.ecmra.mil.

1.4.6.2 Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 Oct through 30 Sep. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

1.4.6.3 The Contractor shall report contractor labor hours via Contract Funds Status Report. Report shall report down to the fourth WBS element level to identify work loading trends. The rationale provided for reporting may replace EVM reporting for Sustainment Engineering if warranted by Missile Defense Agency (MDA).

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 41 of 54

1.4.7 Process Improvement Planning

Identify and recommend improvements to any activities/processes that will make the Government more efficient, cost effective, or timely. Efforts in this area will be coordinated and approved in advance with the applicable IPT lead. An implementation plan will be submitted to the Grounds Branch PM or Engineering Branch Chief for approval. Upon approval, the Contractor will support the execution as defined by the plan. Process improvements shall be summarized in an end of period report and improvement documentation filed in IDR.

1.4.8 Response to Government Requests

1.4.8.1 The contractor shall provide impact statement inputs and/or rough order of magnitude (ROM) estimates for program contract modification exercises. These exercises may include budget increases or decreases, schedule accelerations or stretch-outs, or program scope or content changes. The contractor shall provide firm proposals in response to Government Requests for Proposals.

1.4.8.2 The contractor shall prepare and provide responses to the Government for approval on the comments Government provides on delivered documents IAW the CDRL Instructions and Master Listing.

1.4.8.2.1 The contractor shall participate in associated technical reviews, technical interchange meetings (TIMs), program management reviews, meetings, working groups, and work all associated actions as assigned and prepare agendas, briefing materials, and minutes as requested by the Government. Support and participation for the reviews are projected to average once a month.

1.4.8.2.2 The contractor shall prepare reports based on contractor findings within the specified periods for each performance objective shown in 1.5 Services Summary.

1.4.8.2.3 The contractor shall compile, track, and provide the data for use in trend analysis using industry standards. Data must be compatible with Government software.

1.4.8.3 The contractor shall support the Government IPTs and individual programs as needed in the following activities:

• Provide support in the form of data, briefings, background papers, technical reports and other inquiries for Government integration meetings, program reviews, and IPT meetings with relevant information to help resolve Ground Subsystems production and sustainment problems

• Record meeting minutes and distribute to all IPT members • Provide support in the form of data, briefings, background papers, technical reports and other

inquiries for Technical Evaluation Review Boards (TERB), Program Management Reviews (PMR), Certifications (CERT), Technical Interchange Meetings (TIMs) and other programmatic related meetings

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 42 of 54

• Provide support in the form of data, briefings, background papers, and other inquiries for engineering meetings

1.4.9 Emergency Response

1.4.9.1 The contractor shall assist the Government in maintaining an emergency response program, and shall support the Government by providing travel support and Subject Matter Experts (SMEs) during the recovery effort. Additional support shall include critical review of site survey and recovery options proposed by the onsite team.

1.4.9.2 The contractor shall provide representatives for technical support for on-site at both Hill AFB and the incident scene for emergencies. The contractor will provide procedures, documentation, and personnel, as well as augmentation of technical documentation, occupational and system safety reviews during MPHN events. ICBMSD OI 10-2501 Emergency Management contains information regarding types of emergency response events.

1.4.10 Development, Procurement, and Repair Programs

The Contractor may be required to perform activities related to development, procurement, repair and refurbishment programs for Grounds hardware, support equipment, and related Grounds software as directed by the Government during the contract period of performance. Many of the programs will include acceptance and qualification testing of hardware and their associated support equipment. Specific activities that will be required at contract award will be added as a task or delivery order. Additional requirements that occur after contract award will be added via task or delivery order to the existing contract. Consequently, the contractor shall be able to provide any Grounds related capability for MMIII sustainment that may occur within the period of performance of this contract.

1.5 SERVICES SUMMARY

Below are performance standards (metrics) the Government will use for monitoring contractor performance on critical tasks. These metrics are a meaningful measure of contractor performance and conform to commercial standards to the maximum extent practicable. This PWS is based upon the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. The Government Contracting Officer Representative (COR) will audit the contractor’s processes to ensure processes are in place and will use the data from the contractor inspection reports to assess contractor performance. If the contractor does not have processes in place or meet the standards listed, then the contractor shall establish a corrective action plan to correct the deficiency.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 43 of 54

Table 1. – SERVICES SUMMARY MATRIX

Performance Objective

PWS Para Performance Threshold Frequency

Quality: Quality of work and level of support met task requirements. Work required little or no rework and services met or exceeded expectations. Deliverables were complete and accurate to meet customer objectives.

No more than two (2) verified formal customer complaints/contract discrepancy reports per quarter.

The contractor must resolve or provide resolution plan for customer complaints within 10 working days of receipt.

If Government requires peer review, then ensure peer review has occurred before initial delivery to Government.

Customer Surveys

COR will conduct periodic interviews/surveys with Government personnel to ensure quality of work and services received are satisfactory

Schedule: Deliverables are completed in a timely manner.

98% of requests for products received on agreed upon date.

100% of requests for products/services received on agreed upon date + 5 working days.

100% of comments and edits are incorporated per CDRL requirements.

Customer Surveys

COR will conduct periodic interviews/ surveys with Government personnel to ensure items are being delivered in accordance with the CDRL requirements

Cost Control Contractor performs tasks within +/-10% of allocated hours and schedule.

Periodic inspections

COR will conduct periodic interviews/surveys

Program Management Support

1.4.3 100% of requests for assistance acknowledged within 1 business day; 100% of requests for assistance

Monthly Status Report for new; Quarterly PMR/Task Log Review for on going

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 44 of 54

Performance Objective

PWS Para Performance Threshold Frequency

prioritized within 3 business days.

Coordinate assignment of 100% of tasks (to include contractor prioritizations) with Government within 5 business days.

Integration Management

Clearly present cost, schedule, performance, technical issues, and status for 100% of sustainment tasks and in-scope programs/activities as described in 1.6.3.1.1.

Provide 100% of the EVMS products on a monthly basis.

Monthly Status Report for new; Quarterly PMR for on-going

Cost Reporting Provide program and subcontractor approach and status information at the IPT-level in a clear, organized manner for 100% of applicable activities.

Provide recovery plans which clearly describe the necessary steps and estimated timelines associated with 100% of important issues/delays and of significant issues/delays.

Provide assessments for 100% of “medium and high” consequence cost risks with appropriate cost analyses and estimating or logistics costs models (threshold).

Monthly Status Report for new; Quarterly PMR for on-going

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 45 of 54

Performance Objective

PWS Para Performance Threshold Frequency

Subcontractor Small Business Utilization and Participation

Contractor is proactive in conducting market research and seeking qualified small business sources to meet goals established in subcontracting plan.

Review of Small Business report submissions

Review GSSC subcontractor awards to ensure goal is being met

Human Resource Management

(including recruitment, employment, and efficient application to Government needs)

Provided fully qualified staff for positions in all cases.

Contractor management cognizant of customer needs and provides the staffing required on assigned tasks when required by the task.

Customer satisfied with staffing efforts.

Provide replacement personnel within 30 working days of occurrence of vacancy.

Periodic inspections

COR will conduct periodic interviews/surveys with Government personnel to ensure reasonable efforts are made to retain and recruit personnel, as needed.

100% inspection upon vacancy identification

Transition Compliance with 100% of Transition Plan elements within 180 calendar days of Government approval of Transition Plan (threshold).

Compliance with 100% of Transition Plan elements within 90 calendar days of Government approval of Transition Plan (objective).

Monthly Status Report and Quarterly PMR until Government declares end to transition period

Data Rights 100% of Government-rights data provided IAW applicable CDRLs.

Semi-Annually in PMR

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 46 of 54

Performance Objective

PWS Para Performance Threshold Frequency

Systems Engineering

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Risk Management 100% of reported risks are managed IAW the current ICBMSD Risk Management Plan.

100% assessment of medium and high cost risks with appropriate cost analyses and estimating or logistics costs models.

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly RMB for on-going

Trade Studies 100% compliance with the applicable performance requirements.

Annually in PMR

Configuration Management

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

System Safety 100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Electromagnetic Radiation

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Nameplates & Product Markings

100% compliance with the applicable performance requirements

Physical inspection upon receipt

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 47 of 54

Performance Objective

PWS Para Performance Threshold Frequency

Environmental Engineering

100% compliance with the applicable performance requirements

IAW applicable CDRLs or Semi-Annually

Software Development

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Contractor Logistics Support (CLS)

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Hardware Development

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Cybersecurity 100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Sustainment Engineering

100% of requests for assistance acknowledged within 1 business day; 100% of requests for assistance prioritized within 3 business days.

Coordinate 100% of tasks (to include contractor prioritizations) with Government within 5 business days.

Monthly Status Report for new; Quarterly PMR for on-going

Sustainment Engineering Requirements

100% compliance with the applicable performance requirements

Monthly Status Report

Software Sustainment

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 48 of 54

Performance Objective

PWS Para Performance Threshold Frequency

Hardware Sustainment

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Contractor Logistics Support (CLS)/Contractor Maintenance Support (CMS)

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Parts, Materials, and Maintenance Support

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

DMSMS Provide Government a DMSMS Plan (contractor draft) within 365-days of contract Period of Performance start.

Review DMSMS Plan annually and provide Government updated DMSMS Plan (contractor draft) addressing any applicable improvement recommendations and all applicable new technologies and processes

Receipt of document; annually reviewed in PMR following document delivery

Technical Order Support

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Ground Subsystems Health

100% compliance with the applicable performance requirements

Quarterly Status Report

Technical Risk Assessment

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 49 of 54

Performance Objective

PWS Para Performance Threshold Frequency

Aging Surveillance

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Nuclear Hardness and Survivability

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Nuclear Surety 100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Test & Evaluation (T&E)

100% compliance with the applicable performance requirements

Monthly Status Report for new; Quarterly PMR for on-going

Emergency Response

100% compliance with the applicable performance requirements

Event-driven (evaluated at each exercise or event debrief)

Environmental Controls

100% compliance with the applicable performance requirements detailed in 4.9 and associated governing regulations and statutory laws on the tasks assigned and completed.

Annually in PMR

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 50 of 54

2.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 51 of 54

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 52 of 54

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Basic Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 53 of 54

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 1 GENERAL SUSTAINMENT – GSSC 2.0

Page 54 of 54

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 1 of 11

ATTACHMENT 2

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

OPERATIONAL SOFTWARE SUSTAINMENT PROGRAM (IOSSP)

TASK ORDER UNDER THE

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 2 of 11

1.0 IOSSP PWS .............................................................................................................................. 3

1.1 Scope ..................................................................................................................................... 3

1.2 Purpose .................................................................................................................................. 3

1.3 Background ........................................................................................................................... 3

1.4 Requirements Summary ........................................................................................................ 3

1.5 Services Summary ................................................................................................................ 6

2.0 Appendices ................................................................................................................................ 7

APPENDIX A: ACRONYMS AND ABBREVIATIONS ......................................................... 7

APPENDIX B: WORK BREAKDOWN STRUCTURE ........................................................... 8

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION .............. 9

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ....................................................................................................................... 10

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................. 11

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 3 of 11

Attachment 2 IOSSP PWS

1.0 IOSSP PWS

1.1 SCOPE

The Intercontinental Ballistic Missile (ICBM) Operational Software Support Program (IOSSP) software is critical to the Minuteman III ICBM) mission. The Ground Systems Support Contract (GSSC) performs annual changes to the software in support of United States Strategic Command (USSTRATCOM) operational requirements and overall sustainment needs. IOSSP software consists of the six domains identified in paragraph 1.4.3.

1.2 PURPOSE

The purpose of IOSSP is to enable the ICBM System Directorate (ICBMSD) the ability to provide agile and timely software domain upgrade products in response to the needs and concerns of AFGSC/A3OC, AFNWC/NWC, AFNWC/NI and the warfighter.

1.3 BACKGROUND

Prior to 2005 the ICBM system software was updated during major programs where a major modification was deemed necessary, such as Rapid Execution and Combat Targeting (REACT) Service Life Extension Program (SLEP). These programs would happen about every 10 to 15 years. There was concern that putting the development equipment in storage between programs, and the potential loss of the software expertise on these programs, would have a negative impact on the next major program. The fact that our enemy had changed since the Cold War era, meant that the Customer, then Air Force Space Command, now Air Force Global Strike Command needed the capability to have changes made to the weapon systems as the need arises. It was determined to have an on-going program for maintaining the Operational Software for the ICBM System; hence the creation of IOSSP.

1.4 REQUIREMENTS SUMMARY

1.4.1 Intercontinental Ballistic Missile (ICBM) Operational Software Sustainment Program (IOSSP)

1.4.2. The contractor shall develop, maintain, change, and update IOSSP operational software. Any updates to trainers software affected by IOSSP will be implemented by the Trainer task order.

1.4.3 The contractor shall also maintain the labs where IOSSP operational software is developed. The IOSSP operational software is grouped into the following categories:

• Airborne Vehicle Equipment (AVE) • Console Operations Program (COP)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 4 of 11

• Squadron Data Simulator (SDS) • Mission Planning Element (MPE) • Minuteman Operational Targeting Program (MOTP) • Wing Code Processing System (WCPS)

1.4.4 The contractor shall provide a capability to correct existing software deficiencies, implement new requirements in operational software domains, and maintain the ICBM operational software development capability.

1.4.5 The contractor shall provide the support for sustaining the IOSSP. The IOSSP requires support for the entire software system to include:

• Troubleshoot, repair, and revise software/firmware • Maintain support equipment • Store and inventory GFE/P • Provide technical services • On-site response and maintenance, source data for TOs, and modifications/Time

Compliance Technical Order (TCTO) kits (as required)

1.4.6 The contractor shall participate in meetings, reviews, and quality deficiency reporting programs and host meetings and reviews as required by the Government. All sustainment meetings will be supported and attended by NG. Examples of these meetings includes OCBs, Integrated Product Team (IPT), Reference Model Meeting (RMM), Risk Management Board (RMB), Nuclear Surety and Safety Working Group (NSSWG), Technical Interchange Meetings (TIM), and other future sustainment meetings. For developmental meetings, NG will support and attend the meetings under future Task Orders. Examples of developmental meetings include kick-off meeting, Software Specification Review (SSR), TERB, Preliminary Design Review, Critical Design Review, Test Readiness Review, Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA), validation and verification (Val/Ver), software study TIMS, and other future developmental meetings.

1.4.7 The contractor shall provide Strategic Operations Squadron (STOS) personnel with training on the use of the REACT Virtual Address Extension (VAX) operating system and system utilities, as well as the installed application software (ie. Strategic Targeting Support Software (STSS)).

1.4.8 The contractor shall provide ongoing ICBM operational software sustainment capability.

1.4.9 The contractor shall address and accomplish software updates and improvements as documented in 1067s and in the Operational Software Change Requests (OSCR) database as prioritized by AFGSC/A3IA through the Operations Control Board (OCB) process.

1.4.10 The contractor shall provide ongoing capability to respond to emerging operational software requirements.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 5 of 11

1.4.11 The contractor shall be flexible to the maximum extent in allocating assets to the highest priority AF requested changes and studies. Highest priority is established through the OCB.

1.4.12 The contractor shall ensure the OCB prioritized OSCR database items resolution and or studies for the COP, Operational Ground Program (OGP)/Operational Flight Program (OFP), MPE, MOTP, and WCPS are continually updated and maintained through IOSSP. The baseline process is an ongoing process and the baseline for every software domain will be coordinated between the Government, AFGSC/A3IA, and the contractor on a continuing basis.

1.4.13 The contractor shall ensure the following years after completion of the original tasks will be proposed to continue software development lab availability and the necessary resources to perform software studies to support subsequent software updates.

1.4.14 The contractor shall ensure that software end item change/study content is determined through OCBs, as directed by Government.

1.4.15 The contractor shall work cooperatively in sharing with the Government information throughout the period of performance. The contractor shall provide the Government with clear visibility into concepts, design solutions, research, cost, schedule, meetings, technical performance, engineering data, tests, analysis, and risks.

1.4.16 The contractor shall manage the program to minimize technical, cost, and schedule risk.

1.4.17 The contractor shall conduct quality audits and Technical Interchange Meetings (TIM).

1.4.18 The contractor shall establish efficient and timely internal and external communication processes to maximize integration/coordination with the Air Force and outside agencies.

1.4.19 The contractor shall ensure appropriate project integration to support all necessary technical requirements and documentation requirements.

1.4.20 The contractor shall conduct in-process milestone reviews (informal), audits and interchange meetings with the Government and comply with industry standard ANSI/EIA-649 for Configuration Management.

1.4.21 The contractor shall coordinate closely with the Air Force on code, requirements, testing, status, etc., via telephone conferences or informal meeting.

1.4.22 The contractor shall provide data via DAL and the CDRL to include data packages for all reviews and audits, program reports (test, trades, analysis, etc.), and system requirements analysis (SRA) and engineering data.

1.4.23 The contractor shall participate in regular status meetings with the Government, as requested by the Government, to plan and schedule assigned tasks. The contractor shall document these sessions, identifying dates, determine revised forecast dates, task duration,

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 6 of 11

identify predecessor and successor changes, map resources to tasks, document resource loading, and discuss other cost and schedule issues, as required.

1.5 SERVICES SUMMARY

Reference Basic GSSC 2.0 PWS section 1.7 Services Summary.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 7 of 11

2.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 8 of 11

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be included with Draft RFP Release

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 9 of 11

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 10 of 11

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 2 IOSSP – GSSC 2.0

Page 11 of 11

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be included with Draft RFP Release

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 1 of 11

ATTACHMENT 3

HIGHER AUTHORITY COMMUNICATIONS /

RAPID MESSAGE PROCESSOR EQUIPMENT (HAC/RMPE)

PERFORMANCE WORK STATEMENT (PWS)

TASK ORDER UNDER THE

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 2 of 11

1.0 HAC/RMPE PWS ..................................................................................................................... 3

1.1 Scope ..................................................................................................................................... 3

1.2 Purpose .................................................................................................................................. 3

1.3 Background ........................................................................................................................... 3

1.4 Requirements Summary ........................................................................................................ 4

1.4.1 Meetings and Briefings ...................................................................................................... 4

1.4.2 Security Clearances ............................................................................................................ 4

1.4.3 Operational Hardware, Peculiar Support Equipment (PSE), Test Support Equipment (TSE), and Support Equipment (SE) .......................................................................................... 4

1.4.4 Software Support ............................................................................................................... 5

1.4.5 Multiple Baselines ............................................................................................................. 6

1.4.6 Operational Support ........................................................................................................... 6

1.4.7 Facilities ............................................................................................................................. 6

1.4.8 Government Furnished Equipment (GFE) ......................................................................... 6

1.5 Services Summary ................................................................................................................ 6

2.0 Appendices ................................................................................................................................ 7

APPENDIX A: ACRONYMS AND ABBREVIATIONS ......................................................... 7

APPENDIX B: WORK BREAKDOWN STRUCTURE ........................................................... 8

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION .............. 9

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ....................................................................................................................... 10

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................. 11

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 3 of 11

1.0 HAC/RMPE PWS

1.1 SCOPE

The Higher Authority Communications Rapid Message Processor Equipment (HAC/RMPE) software is critical to the Minuteman III Intercontinental Ballistic Missile (ICBM) mission. The Ground Systems Support Contract (GSSC) performs annual changes to the software in support of United States Strategic Command (USSTRATCOM) operational requirements and overall sustainment needs. Operational HAC/RMPE software consists of three Computer Software Configured Items (CSCIs) the Message Processing (MP), the Communication Integrator/Backup (CI/B), and the Transmission Integrator (TI).

1.2 PURPOSE

The GSSC is responsible to conduct software changes to the CI/B and TI. The contractor coordinates with the HAC/RMPE Software Support Facility (HSSF), ICBM SPO, and 520th SMXS, Offutt AFB, NE on all changes. Deficiencies, enhancements, and changes in operational procedures drive changes to the executable code. Changes to the higher authority communications network drive changes to the MP, CI/B, and TI software. Northrop Grumman (NG) provides the following support for the operational HAC/RMPE software and support equipment. Technical expertise for maintenance of the HAC/RMPE software, which includes the MP, TI, CI/B software ‐ Investigation of software anomalies‐ Independent validation and verification of software modifications‐ Software modifications ‐ Documentation red line, changes and distribution Delivery of Master Programmable Read‐Only Memory (PROM) devices, production and distribution for CI/B and TI updates Engineering services to support trade studies.

1.3 BACKGROUND

Developed of the Rapid Execution and Combat Targeting (REACT) Program began in 1989 and deployed in 1995. The HAC/RMPE is a TS/NC3 System integrating all ICBM Strategic Communications Systems for ICBM Missile Alert Crews. HAC/RMPE provides rapid execution of Nuclear Command and Control via Interactive decoding & authentication of EAMs, Automated processing of retargeting data (FDMs), Duplicate message suppression, and provides backup-independent means for receiving and transmitting messages. Software updates ensure ICBM Weapon System compliance with OPLAN 8010 Directives and annual USSTRATCOM Emergency Action Procedure (EAP) Volume releases. This sustainment effort is needed to ensure that the HAC/RMPE software meets the Operational Plan (OPLAN) 8000 series. The updated software will deliver an essential capacity to the HAC/RMPE function within the Weapon System Control Console (WSCC) component of the Minuteman III Ground systems. This project is time-sensitive in that the updated software must be available on various dates determined by the Commander in Chief, Chairman of the Joint Chiefs of Staff, USSTRATCOM, and AFGSC. This sustainment workload originated in and was mandated by the Concept of Software Support for HAC/RMPE and MMP Software, sections 1.6.5 and 1.6.6, dated 14 -Jan -2014.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 4 of 11

1.4 REQUIREMENTS SUMMARY

Higher Authority Communications/Rapid Message Processing Element (HAC/RMPE) sustainment

1.4.1 MEETINGS AND BRIEFINGS

The contractor shall provide materials, agendas, and participate in regular status meetings with the Government, to plan and schedule assigned tasks to include identifying dates, determining revised forecast dates and task duration, identifying predecessor and successor changes, mapping resources to tasks, documenting resource loading, and discussing other cost and schedule issues, as required.

1.4.2 SECURITY CLEARANCES

Personnel working with the HAC/RMPE and associated activities must obtain and maintain security clearances at the following levels:

• HAC/RMPE program without access to Emergency Action Procedures (EAP), Reserve Force Target List (RFTL), or operational data is SECRET.

• HAC/RMPE program with training data is TOP SECRET • HAC/RMPE program with EAP, RFTL, and operational data is TOP SECRET, NC2-

Extremely Sensitive Information (ESI), Category C.

1.4.3 OPERATIONAL HARDWARE, PECULIAR SUPPORT EQUIPMENT (PSE), TEST SUPPORT EQUIPMENT (TSE), AND SUPPORT EQUIPMENT (SE)

The contractor shall provide support for the Operational HAC/RMPE, PSE, TSE, and SE related hardware, firmware. This support shall consist of:

• Review, analysis, and updates of the subsystem or end item specifications. • Review, analysis, and updates of the Operational HAC/RMPE, PSE, TSE, SE, and technical

baseline documentation. • Support resolution of queries concerning Operational HAC/RMPE, PSE, TSE, and SE

anomalies through either assessment, analysis, and/or test actions. • Conduct Operational HAC/RMPE, PSE, TSE, and SE Trend Analysis with

recommendations. [CDRL A027, DI MISC-80508B/T, Trend Analysis (subtitle)] • Monitor Operational HAC/RMPE, PSE, TSE, and SE parts obsolescence and availability

issues and notify the Government of any such issues that occur. The contractor shall use this data to update the associated sustainability reports

• When required to maintain support for software development activities the contractor shall perform technical refreshes of the HAC/RMPE PSE, TSE, and SE hardware and Computer Software Configuration Items (CSCI) which includes:

• Card Tester (CT) CSCI 01300

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 5 of 11

• Communications Integrator/Backup CSCI 00400 • Cross Connector Box • Data Reduction Tool (DRT) • Drawer Tester (DT) CSCI 01200 • HAC/RMPE firmware • HAC/RMPE Simulator • Higher Authority Communication Data Collector (HACDC) • Higher Authority Communication Test Station (HACTS) • Journal Memory Loader • Message Generator CSCI 00900 • Message Processor CSCI 00300 • Transmission Integrator CSCI 00500 • Weapon System Console Element (WCSE) Simulator • In Circuit Emulator (ICE) • PROM Burner • Protocol Analyzer (PA) • Software Development & Maintenance Equipment (SDME) • Rapid Message Processor (RMP) • RMP Backup (RMPB) • Disk Duplicator

1.4.4 SOFTWARE SUPPORT

The contractor shall perform and document software maintenance activities to include software requirements analysis, software product requirements development and management, software design, software code change, software code module integration, software qualification testing, and support to system integration test.

The contractor shall provide software support to the HAC/RMPE Software Support Facility (HSSF), as requested by the Government, to include requirements analysis, software design, software code integration, and testing. Provide hardware technical support, as requested by the Government, for fielded HAC/RMPE and HSSF HAC/RMPE equipment.

The contractor shall provide Independent Verification and Validation (IV&V) support to the HSSF for support of software development functions.

The contractor shall perform HAC/RMPE software block updates which may include:

• Incorporating AF Forms 1067, Modification Proposal approved by the AFGSC/A3 and A6 Operational Configuration Board (OCB)

• Making updates to correct post-delivery discovered software deficiencies • Making updates to correct existing latent defects identified in the software

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 6 of 11

• Making updates to improve software performance or maintainability in the operational environment

The contractor shall provide support to software anomaly identification and recommended solutions.

The contractor shall implement a software metrics collection and tracking capability. Metrics shall include HAC/RMPE software memory usage and maintainability, such as code complexity, file, or Computer Software Unit (CSU) frequency of change.

The contractor shall provide and maintain the secure electronic interface between HSSF and the contractor facility used to transfer HAC/RMPE classified data.

1.4.5 MULTIPLE BASELINES

When required the contractor shall support multiple software baselines to ensure that OCB driven requirements are maintained while new requirements are integrated into the operational baseline. Once completed the contractor shall return to a single baseline support.

1.4.6 OPERATIONAL SUPPORT

The contractor shall provide technical support to modifications of the HAC/RMPE Message Specification Matrix (Blue Book).

The contractor shall participate in the OCB to validate and prioritize software change requests.

1.4.7 FACILITIES

The contractor shall maintain the lab where HAC/RMPE operational software is developed.

The contractor shall ensure HAC/RMPE, HAC/RMPE Support Equipment, and developer certifications, including Risk Management Framework and TEMPEST, are obtained and maintained.

1.4.8 GOVERNMENT FURNISHED EQUIPMENT (GFE)

The contractor shall maintain and update a list of GFE used at all contractor facilities.

1.5 SERVICES SUMMARY

Reference GSSC 2.0 Basic PWS section 1.7 for details.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 7 of 11

2.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 8 of 11

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be included with Draft RFP Release

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 9 of 11

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 10 of 11

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 3 HAC/RMPE – GSSC 2.0

Page 11 of 11

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be included with Draft RFP Release

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 1 of 37

ATTACHMENT 4

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

CODES - PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 2 of 37

Attachment 3 ................................................................................................................................... 3

1.0 CODES PWS ............................................................................................................................ 3

1.1 Scope ..................................................................................................................................... 3

1.2 Purpose .................................................................................................................................. 3

1.3 Background ........................................................................................................................... 3

1.4 Requirements Summary ........................................................................................................ 3

1.5 Services Summary ................................................................................................................ 3

2.0 Appendices .............................................................................................................................. 33

APPENDIX A: ACRONYMS AND ABBREVIATIONS ....................................................... 33

APPENDIX B: WORK BREAKDOWN STRUCTURE ......................................................... 34

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION ............ 35

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ....................................................................................................................... 36

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................. 37

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 3 of 37

ATTACHMENT 3

1.0 CODES PWS

1.1 SCOPE

1.2 PURPOSE

1.3 BACKGROUND

1.4 REQUIREMENTS SUMMARY

1.4.1 Engineering Support Engineering support provided for the ICPS by The Contractor is performed in concert with established maintenance concepts. Maintenance procedures have been written that allow the Air Force to maintain most of the system. However, the Air Force has the option to contract the maintenance for their systems and equipment to civilian contractors. Operational level of repair (formerly Organizational repair and Intermediate repair) is performed by the Air Force and is accomplished within the shielded enclosure and the codes storage vault by authorized/qualified Air Force maintenance/repair technicians. Depot repair for the ICPS requires Depot personnel to oversee maintenance at the ICPS field sites. The Contractor support is considered to be a Technical Repair Center (or Depot) function. The Contractor provides Depot level maintenance and services for the ICPS hardware configuration items (Cis). The ICPS hardware Cis are: (1) Wing Code Processing System (WCPS) (CI 0042156, see Figure 2) (2) Shielded Enclosure (CI 0042157) 1.4.1.1 The Contractor does not maintain government fumished equipment (GFE) used in the WCPS. 1.4.1.2 The Contractor maintains the following ICPS computer software Cis:

(1) Common Certification/Operating System (CCOS) (CI 0045871) (2) SCPS Application Program (SAP) (CI 0045872) (3) WCPS Minuteman Application Program (WMAP) (CI 0045874)

1.4.1.3 The Contractor also provides training of government personnel for the operation and maintenance of the ICPS and The Contractor maintains the associated training materials. Training support levels are subject to prioritization as determined by the Codes IPT.

1.4.2 Technical Order Maintenance

Three Air Force TOs are used to support ICPS operations and maintenance. These manuals undergo

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 4 of 37

both the required validation and verification processes to assure technical content and accuracy. The ICPS TOs are:

(1) 31X8-2-2-1 Operation Instructions Console, WCPS (Part Number 10365-107-XX)

(2) 31X8-2-2-2 Maintenance Instructions with

Illustrated Parts Breakdown

Console, WCPS (Part Number 10365-107-XX)

(3) 31X8-2-3-1 Operation and Maintenance Instructions with

Illustrated Parts Breakdown

Console, HCVE (Part Number 11800-315-XX)

(Where XX in the part number represents the latest version of the equipment)

1.4.3 Spares Management

The original ICPS equipment sparing concept established a 20-years spares inventory of components (1986 through 2005). This decision was based upon nuclear certification requirements, equipment obsolescence considerations for commercial off-the-shelf (COTS) components, and economic reasons for contractor-produced components. However, in 1994 the Air Force extended the life requirement for the Minuteman weapon system, including the ICPS, to the year 2020. As a result, a spares obsolescence assessment was performed to verify the adequacy of the existing spares inventory to support maintenance to 2020 and to identify shortfall dates for running out of spare components. The primary tool of the assessment is a personal computer-based database program called the ICPS Spares Assessment Model that considers a variety of factors such as predicted and actual mean time between failures, equipment operating time, number of spares on hand, etc., in order to calculate shotifall dates. The assessment is updated and the model's input data is reviewed twice yearly for accuracy. In 2007, the Air Force indicated the MMIII system life would be extended through 2030T. he Spares Assessment Model identifies shortfalls for both 2020 and 2030. A critical assumption concerning the ICPS Spares Assessment Model is that all shelf spares are in serviceable condition, unless known to have failed previously. Starting in 2006, the Codes IPT initiated testing of serviceable shelf spare! to confirm their serviceable condition. Air Force Space Command (AFSPC) is responsible for maintaining physical control of spares and bench stock materials. Each ICPS activity maintains inventory records and documents spares usage and other inventory changes. Inventory updates are compiled by ICPS site personnel and are provided to The Contractor for overall program inventory management reporting. 1.4.4 Engineering Support

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 5 of 37

The Engineering Support task comprises the effort to resolve problems in the field (i.e., Engineering Field Support), including the attendant Engineering Analysis, as well as the analysis associated with determining system impacts resulting from potential changes, weapon system test (WST) support, and preventive maintenance inspections (PMI). 1.4.5 Enigneering Field Support Engineering Field Support consists of the technical support to resolve problems occun·ing at the ICPS field sites. Problems are analyzed first via telecommunications f e.g., telephone (1-800-596-4498), FAX (7141762-0418) or e-mail] at The Contractor and then, if required, by a trip to the field site. Engineering analysis is performed to resolve anomalies occurring in the field and may eliminate the need to travel to the fielded site. This effort may also be performed as needed in parallel with repair actions on-site when a trip to the field is required. Field problems are first characterized fully so that the problem is understood before proceeding with a recommended fix. In-plant analysis of the problem is done to the extent feasible prior to visiting the field site. If applicable, in-house systems, integration facilities and engineering laboratories are used to attempt to duplicate and/or validate the problem. Prior test data obtained during performance verification or qualification testing may be examined during the investigation. A central point of contact is assigned to collect, record, analyze, and report anomalies along with documenting corrective actions so that the following is ensured:

(1) Collecting and prioritizing the anomaly data (2) Recommending repair/corrective action (3) Field support team dispatch (if electric communication support is unsuccessful) (4) Documenting corrective action (5) Corrective action follow-up (on-going) (6) Failure prevention recommendation

The Deficiency Reporting process is one vehicle by which deficiencies and enhancements concerning the ICPS are submitted, investigated, validated, and documented. Deficiency Reports (DR) submitted by Air Force personnel regarding ICPS problems occurring in the field may be written against any condition that limits or could prevent the ICPS from fulfilling its mission. Reports may be against hardware or software failures, ICPS design and quality, human factors, safety, or logistics support. The Contractor uses DR data in accomplishing engineering support. 1.4.6 Preventative Maintenance Inspeciton Engineering support also includes PMI support. This support is provided as an annual on-site visit to each ICPS site. Verification that Air Force maintenance personnel have performed the required maintenance

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 6 of 37

on ICPS equipment takes place during PMI visits. Additional possible activities include testing and repair of failed/suspect spares. 1.4.7 Engineering Analysis Engineering Analysis for ICPS CLS is performed to ascertain how the system may be affected by potential changes resulting from identified anomalies, or suggested reliability, maintainability, and supportability improvements. The following paragraphs identify and define the sub-tasks requiring engineering analysis. 1.4.8 ICPS Modifications Seperately contracted programs are the vehicle for Class I Engineering Change Proposal (ECP) modifications to the ICPS. Class I ECP modifications to the ICP’s are not implemented under ICPS CLS. Implementations of a Class II ECP depends upon the extent of the change and available funding. 1.4.9 Nuclear Surety Support Nuclear Surety Support is the analysis of the impacts to nuclear surety and certification of potential modifications to ICPS hardware, software, procedures, or spares actions. 1.4.10 Weapon System Test Support Weapon system test support involves the production of CPS-generated test material and the analysis of ICBM data media. Test output, which includes fully verified media and corresponding documentation, will be generated upon request following Codes IPT approval. This output may be used for testing at Vandenberg AFB, Hill AFB, or contractor test facilities. 1.4.11 Technical Order Maintenance Maintenance of ICPS related technical orders involves the following: (1) providing an interface with the user, (2) source data generation and Air Force Technical Order (AFTO) Forms 252 review, if requested, and (3)TO Library maintenance at contractor site. The following paragraphs define these TO Maintenance sub-tasks. 1.4.12 Providing User Interface The Contractor provides the interface for responding to ICPS TO related field inquiries and problems. The The Contractor point-of-contact and phone number (1-800-596-4498) is available to all ICPS units and ICPS TO users. 1.4.13 Technical Order Support Upon determination of a TO anomaly, details of the anomaly are documented by The Contractor for

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 7 of 37

future generation of source data for a Technical Order Page Supplement (TOPS). How soon the source data is generated depends on the criticalness of anomaly. When generated, the source data is provided to NGAS and the Equipment Specialist identifying the discrepancy and a suggested fix for the anomaly. The The Contractor Codes IPT will review AFTO 252's from the ICPS Equipment Specialist, if requested. However, The Contractor review of AFTO 252's is not required by the 526 ICBM SG AFTO FORM 22/AFMC Forms 202 & 252 Routing Process Flow. 1.4.14 Technical Order Library Maintenance A library containing ICPS related Technical Publications is established and maintained at The Contractor Anaheim/Huntington Beach, CA. 1.4.15 Spares Management ICPS spares management consists of: (1) spares inventory control management (including all required reports involving supply support concerns); (2) !CPS spares procurement, scheduling and delivery support; and (3) spares assessment and consumption management. These sub-tasks are defined in the following paragraphs. 1.4.16 ICPS Spares Inventory Control Management As part of the ICPS spares inventory control management effort, The Contractor maintains the ICPS inventory control database based upon twice-yearly inventory updates received from the ICPS field sites. The database is comprised of part numbers, stock numbers, quantities-on-hand, and condition codes. The Contractor submits inventory reports to 20AF, 509th, NGAS, AFSPC, ICPS wings and USSTRATCOM. In addition, on –site visits will be made as determined by the Codes IPT to ensure that inventory records are accurate and that adequate suppy support is being maintained. The Contractor assists site personnel with ICPS inventory problems. The Air Force maintains and replenishes consumable items (bench stock materials). The Contractor assists in identifying alternative sources of supply if any ICPS consumable items become obsolete for procurement. 1.4.17 ICPS Spares Procurement, Scheduling, and Delivery Support ICPS spares procurement, scheduling, and delivery support consists of performing the spares management services to procure, schedule, and provide delivery support to the sites for new and replenished spares. This support is based on availability of funding. 1.4.18 ICPS Spares Assessment and Consumption Management Analysis of spares quantities and repair parts required to sustain CPS operations through the year 2030, based on consumption demand, is performed. Recommendations for replenishment quantities to support the ICPS through the support period are made, as required. The inability to set nuclear certify most Type I COTS spares precludes them from the normal replenishment process. Post-production support will be

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 8 of 37

performed to identify and evaluate potential problem items (e.g., obsolete). Assistance is provided to the Codes IPT to determine qualifiable new sources and to produce the documentation necessary for The Contractor to procure the components required to suppmt spares replenishment. The extent to which assessments will be performed and which spares are procured will depend upon the quantities required and available funding. 1.4.19 Laboratory Management/Support Lab management/support consists of providing the support and maintenance of the Code Processing Laboratory sites. The Code Processing Lab consists of the following equipment:

(1) WCPS Engineering Model (EM) (2) WCPS Operational Model (OM) (3) ICPS Development Site (IDS) (4) Hardware Certification Verification Equipment (HCVE) (is WCPS lose equipment) (5) Shielded Enclosure (SE)

Configuration of the WCPS EM and OM is controlled in accordance with approved The Contractor Quality Assurance procedures and certification processes. Only Codes IPT approved changes (temporary or permanent) are made to the OM. Specific support is provided for activities that include: hardware and software development and test; field problem investigations; coordination and installation of upgrades to the WCPS EM and OM; kit proofing; prototyping; modification and certification of the EM and OM sites to any fielded configuration maintenance and repair of ICPS equipment maintaining the inventory of lab supplies; administration and coordination of site usage; allocation of lab resources; maintenance of records for special test equipment, GFE, hardware equipment transfers, calibration and maintenance schedules, site log books and repairs; and performance of security inspections and security procedures for processing classified material in accordance with the requirements specified by the DD Form 254. Laboratory management/support also consists of the activities necessary to satisfy administrative, housekeeping, health and safety requirements plus the discipline necessary to ensure that development and test operations (including weapon system test support) are conducted in an organized and efficient manner. 1.4.20 Interface Management Interface management includes establishing interface controls to maintain ICPS interface requirements. This tasking is implemented for system changes that may impact the interfaces with the !CPS and addresses GFE, computer programs, hardware, facilities and data. Inte1face control document/drawings (lCD) are updated via the preparation, approval, and incorporation of interface revisions (IR). This task includes the coordination with contractors and the Government [Interface Management Staff (IFMS), and Interface Control Working Group (ICWG) chairmanl to obtain approval.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 9 of 37

1.4.21 Configuration Management Configuration Management applies technical and administrative direction and surveillance to control changes to the functional and physical characteristics of the ICPS configuration end items and, as required, record and report change processing and implementation status. Configuration Management includes the maintenance of complete information regarding the rationale for configuration changes, thus permitting analysis and correction of deficiencies when they arise. Configuration changes are controlled so that the impacts of proposed changes to the functional and physical characteristics are identified. A The Contractor Program Configuration Control Board (PCCB) will review proposed changes to the approved (i.e., fielded) ICPS configuration and advise the !CPS IPT. Proposed changes will be submitted to ICBM Prime Team for approval by the government configuration control board before review and approval. Support to the Government's configuration control board will be provided, as requested. Maintenance and update of the ICPS field item product baseline specifications will be funded by design changes. The proposed change process task encompasses the use of an Engineering Change Analysis (ECA), form 835-J-32. The ECA process includes determining the effects of a change intended to correct a field anomaly or determining the effects of suggested modifications to ICPS hardware or software that would enhance reliability, maintainability or supportability of the system, or improve field operation capability. The analysis includes justification for the change, description of the change, documentation affected, the performance of trade-offs, and identification of alternative solutions. This task also includes the preparation, review, and coordination of ECAs and, if required, an Engineering Change Proposal (ECP), DO form 1692 will be prepared and submitted through the Prime Process. Implementation of a Class I ECP modification to the ICPS will be accomplished on a separately funded contract. Implementation of a lass II ECP change to the ICPS depends upon the extent of the change and available funding. 1.4.22 Performance Measurement ICPS CLS performance measurement is based on metrics that are collected at an established frequency as tasks .are performed. Metrics are reviewed promptly and unfavorable variances and trends are identified for revised planning. Performance measurement serves to:

(1) Provide visibility of actual versus planned performance (2) Provide early detection or prediction of problems which require management attention (3) Support assessment of program impacts of proposed change altematives (4) Facilitate continuous process improvement

1.4.23 Resources and Facilities

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 10 of 37

Personnel and facilities, having the appropriate levels of security clearance, are in place to perform the required ICPS CLS tasks. The The Contractor facility at 5301 Bolsa A venue Huntington Beach, CA, 92647, has a Top Secret facility clearance from the Department of Defense issued 1996/12/ll. In addition, all key/core ICPS CLS technical and managerial personnel have, as a minimum, Secret clearances. A number of these personnel have Top Secret clearances with some holding Communications Security and Cryptographic access. 1.4.24 Personnel The The Contractor ICPS personnel are an expert team with extensive ICPS and overall ICBM weapon system experience. This team contains the expertise needed to perform the ICPS CLS tasks (e.g., Management, Systems Engineering, Hardware and Software Engineering, Lab support, Spares support, and TO Maintenance). 1.4.25 Facilities The facilities to develop ICPS modifications and troubleshoot field anomalies are located Building 45 at the The Contractor Huntington Beach, CA, campus. These facilities contain GFE and The Contractor developed tools that have been designed specifically for ICPS developments. These hardware and software laboratory sites shown in Figure 3 are capable of duplicating or emulating the operational configuration of the fielded ICPS systems and are used in supporting hardware engineering, software engineering, systems engineering, technical publications, and weapon system test. Field anomaly investigations will take precedence of ICPS Lab resources over all other activities.

Figure 3. ICPS Lab Sites The following describes how the !CPS facilities provide support: (1) Hardware Engineering Support

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 11 of 37

a. The HCVE is used for developing and testing hardware modifications, as well as for

troubleshooting defective Hewlett-Packard (HP) equipment. It contains an HP 2117F computer, an HP 7970 9-track tape drive, a printer, two magneto-optical disk drives (Pinnacle Micro Vertex or Sony) (system and data drives), a terminal, an input/output extender and a

b. The WCPS EM is primarily used for hardware/software integration and can be used to support

field anomaly investigations since it is functionally equivalent to the fielded WCPS and is configuration controlled.

c. The WCPS OM is primarily used to support field anomaly investigations and is also

configuration controlled.

(2) Software Engineering Support

a. The IDS is used for software driver development and testing, and to develop code and program design. The software subsystem contains an HP 2117F computer, a system terminal, approximately five support terminals, two magneto-optical disk drives (Pinnacle Micro Vertex or Sony) (system and data drives), an HP system clock, an HP 2608 printer, an HP 7970 9-track tape drive, a Raymond 6412 cartridge drive unit, a KS-60, two KI-45's (when needed), a permutation-plug/keying variable plug, a bulk storage/loader, and a floppy disk drive.

b. The WCPS EM is used primarily for checkout and integration. The WCPS OM may be used also if the development does not include hardware modifications. (Reference paragraph 3.3.)

(3) Systems Engineering Support

a. Two sites can be used for qualification testing of software modifications. If the software modifications are a result of hardware changes, the WCPS EM is required to accomplish qualification testing. The WCPS OM may be used if the development does not include hardware modifications. The OM may also be used to test software functions not impacted by the new hardware.

b. The WCPS EM is required for end-to-end testi ng. The WCPS OM may be used if there is

no new hardware. (Reference paragraph 3.3.)

c. The IDS is used to create error tapes, produce printouts of qualification test data for

analysis, and perform comparison of tape or disk data.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 12 of 37

(4) Weapon System Test Support The WCPS EM is used to provide WST support devices/media (e.g., encoding/loading hardware devices, and generating tapes and cartridges) and for WST data analysis (e.g., tapes, cartridges, or head disk assemblies). The WCPS OM may be used if the current development does not contain hardware modifications, or after any required new hardware is installed in support of kit proofing. (5) Technical Publications Support The WCPS EM or OM is used to develop, test, and validate TO and AFRO Forms 22 and AFMC Forms 252 Program Change Request procedures. Use of the OM is preferred for TO Validation and will be made available on an as-required basis for Verification. 1.4.26 WCPS EM and OM Configuration Control and Usage The WCPS EM and OM configurations are controlled. Both are certified and monitored by The Contractor Quality Assurance for configuration and compliance to configuration control procedures. The OM configuration is maintained to the production drawings. The EM configuration is maintained to engineering drawings controlled by Quality Assurance. The procedures for maintaining configuration control include:

(1) Maintaining Engineering Sign-Off Packets for the EM and OM. These sign-off packets document site activity such as maintenance, testing, equipment configuration, inspections performed, anomalies, and failures

(2) Temporary changes to the WCPS OM are coordinated within the Codes lPT and temporary

changes to the EM are coordinated with The Contractor Quality Assurance

(3) Generating a Plan of Action documenting special action required concerning the EM or any temporary change to the OM. This plan is reviewed and approved by The Contractor management and Quality Assurance, and the in-plant Defense Contract Management Agency (DCMA)

(4) Implementing permanent changes to the EM and OM only in accordance with approved

ECPs and engineering change orders Temporary changes include alterations to support field anomaly investigations or enhancement study investigations. The WCPS OM will be restored to the documented configuration following completion of the activity.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 13 of 37

The following OM activities are acceptable without Codes IPT approval:

(1) Maintenance and repair (2) Executing the The Contractor engineering copies of the deliverable software (i.e., CCOS, SAP,

andWMAP) (3) Executing test software in support of field anomaly investigations (4) Software development and testing, and qualification testing involving existing hardware (5) WST media generation and other media generation as requested (6) Analysis of media provided to Contractor (7) TO pre-validation, validation, including any associated disassembly, and software TCTO

trial-kit proofing (8) Disassembly to confirm configuration status

1.4.27 Implementation Approach Accomplishment of the identified ICPS CLS tasks is assured by implementation of an IPT. This approach yields better products, more quickly and more economically. IPT fosters continuous process improvement. The IPT approach for ICPS CLS is based upon the following: (1) Maintaining a customer focus (2) Executing the program via multidisciplinary teams, led by the Contractor, that includes various contractor functions (Engineering, Logistics, Program Management, Contract Management), and participation by the Ground Systems IPT, 20AF/A3NB, USSTRATCOM, and AFSPC (users) to facilitate early problem solving. (3) Physically collocating core teams whenever practical, and when impractical, virtual collocation will be achieved by electronic communications means. (4) Placing an appropriate emphasis on product and related process selection or development (5) Empowering the teams (6) Representative(s) of required viewpoints participating, via open communication and data sharing, in

all decisions impacting product quality The Codes IPT meets twice monthly to review Task Requests (TR), raise and resolve issues/concerns, and monitor and control the overall program. The multidisciplinary Codes IPT also meets twice monthly for similar reasons. 1.4.28 Engineering Support 1.4.29 Enigneering Field Support

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 14 of 37

Engineering Field Support (see Figure 4) is initiated upon notification of a problem. The Contractor will

respond to calls for assistance placed to the 1-800 number by 10:00 A.M. Pacific Coast Time the next Contractor working day.

Pertinent, available information (e.g., from site logs, "Dull Swords", deficiency reports, etc.) is requested in order to assess the problem. The deficiency reporting (DR) process (in accordance with TO 00-35D-54) is instrumental to providing engineering support. ADR is a vehicle to describe anomalies occurring in the field to the ICPS IPT for subsequent investigation. ICPS experts in the areas of hardware, software, systems, TOs, and spares management review DRs received by The Contractor for ICPS impacts. Site

personnel may be contacted to clarify the reported anomaly. Clarifications will be reflected in the investigation report.

The Government determines if the Material Improvement Project (MIP) process is warranted. The MIP process involves further investigation of the problem and coordination of recommendations with the MIP Review Board. Support to the MIP Board will be provided, as required. Key personnel, including hardware, software and systems engineers, evaluate the problem and suggest solutions. Solutions are coordinated with the Codes Vault and E-Lab personnel. The criticality of the problem (e.g., WCPS down, WCPS up, but with limited functionality) will be determined. The criticality of the problem influences the decision to travel to the field. If the problem is sufficiently critical and telephone support has not resolved the problem, the decision for the Contractor Codes Team to travel will be determined per the flowchart shown in Figure 4. If the Air Force authorizes the Contractor to travel, the Contractor coordinates the details of the travel with the Codes Vault. As Personnel Reliability Program (PRP) requirements stipulate that non-PRP contractors/subcontractors shall not perform hands-on maintenance on the ICPS equipment, The Contractor and its HP repair

subcontractor support Air Force ICPS Maintenance personnel in a consulting capacity. The Contractor coordinates with subcontractor(s) if COTS (HP equipment or Shielded Enclosure) is involved. The Contractor personnel will be on base within 72 hours of travel authorization with a goal of arrival on site within 48 hours of travel authorization, particularly when the problem is urgent.

Documentation of the support provided and problem resolution will take the form of a Trip Report, and/or a Weekly Status input. Previously, from February 1987 through March 2000, The Contractor maintained

an ICPS Anomaly Log (PRIME-15067) to document anomaly support. Now this support is documented solely via the Trip Reports and Weekly Status. If no solution is found and the problem is not critical, the item will be placed on the The Contractor Site To Do List for the next opportune trip. The Trip Report will be provided to NGAS and the government ICPS program manager within 15 working days upon returning from the site.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 15 of 37

1.4.30 Preventive Maintenance Inspection PMis are scheduled annually for each ICPS site subject to available funding. A PMI may be included during emergency field trips to troubleshoot down sites, if convenient for the Air Force. Specific schedule dates will be coordinated with each site and 20AF/A3NB. The schedule will also be coordinated with the COTS repair sub-contractor when necessary. The Contractor coordinates with each field site regarding necessary support and parts availability. The

Contractor also coordinates with the sub-contractor regarding necessary supplies to complete the PMI. PMI trips also include testing/assessing failed equipment (F condition), equipment in unknown condition (K condition) and/or accomplishing tasks on the Site To Do List, as time allows.

If required, because of performing Site To Do List activities, spares repackaging is identified for Air Force personnel to accomplish. A trip report is written to document the activities of the trip. Trip report distribution is made to NGAS and appropriate government agencies, including the site visited, 20AF/A3NB, and the government ICPS program manager.

Travel Decision Flowchart for On-Site

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 16 of 37

Problem Resolution Support by Codes Sustainment

Figure 4. Engineering Field Support Process

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 17 of 37

1.5 Engineering Analysis 1.5.1 Nuclear Surety Support When proposed modifications to any element (hardware or software) of the ICPS are being considered, The Contractor will petform analyses of the effects of the modification on the nuclear safety of the system. Three types of documentation are available for reporting the results of these analyses: (1) the ICPS Nuclear Safety Analysis Report (NSAR), (2) the ICPS Launch Action Study (LAS), and (3) a Nuclear Safety Impact Letter (NSIL). Typically, a NSIL is required for all modifications. The NSAR and/or LAS may also require updating, depending on the nature and extent of the modification. In all but the simplest of changes, the NSAR is updated. The LAS is updated for major modifications or if the modification introduces a new or modified nuclear safety threat or a change to the ways in which a threat may be carried out. The process flow for the three types of documentation is shown in Figure 5.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 18 of 37

Figure 5. Nuclear Surety Support Process

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 19 of 37

1.5.2 Weapon System Test Support The process by which ICPS-generated test material is produced and delivered, including fully verified output media and corresponding documentation is described in Figure 7. Upon receipt of a request for test material, The Contractor documents details of the request. Internal coordination sets priorities and ensures adequate lab support and appropriate funding are available.

Figure 6. WST Support Process

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 20 of 37

1.5.3 Technical Order Maintenance This section describes the approach for performing the TO maintenance tasks related to: (1) providing an interface with the user, (2) managing source data and AFrO Forms 22/252. 1.5.4 Providing User Interface To facilitate its interface with the user community, The Contractor has specified a point-of-contact for all ICPS TO related field inquiries and problems. The The Contractor point-of-contact can be reached at 1-800-596-4498. 1.5.5 Source Data and AFTO Forms 22/252 Management The TO maintenance process, encompassing AFTO Forms 22 that are field generated and source data TOPS that are The Contractor generated. 1.5.6 Field Generated AFTO Forms 22 Upon receipt of a field generated AFTO Form 22, the Equipment Specialist reviews the AFTO 22 and may submit the resulting AFTO 252 to the The Contractor ICPS IPT for review and comment. The Contractor comments will be collected by the The Contractor ICPS TO representative for forwarding to the Equipment Specialist. 1.5.7 The Contractor Generated Source Data TOPS Upon identification of an anomaly requiring a TO change, a source data TOPS package will be generated by the ICPS IPT TO representative for the respective technical publication. Copies will be provided to the ICPS IPT for review and comment. Comments will be collected by the TO representative and incorporated into the TOPS package. The ICPS IPT review process will be repeated until no additional comments are received. The final version of the source data TOPS will be forwarded to Equipment Specialist, where the established approval cycle begins. 1.5.8 Spares Management This section describes the processes by which the planned spares management tasks and activities are perfmmed. The processes encompass: (1) providing spares inventory control management, including all required reports involving supply support issues, (2) ICPS spares procurement, schedule management and delivery support of new and replenishment spares to support weapon system availability, and (3) conducting a spares assessment and consumption management.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 21 of 37

1.5.9 ICPS Spares Inventory Control Management The ICPS spares inventory control management process performed by The Contractor is depicted in Figure 8 and described below. Adjusted usage inventory reports received from ICPS site personnel are reviewed for spares consumption usage and compared against the site anomaly log, Deficiency Reports, and site trip reports. The ICPS sites are contacted if discrepancies are discovered. The ICPS Master Inventory Database is updated and reviewed based upon ICPS site inputs and the resolution of any site discrepancies. Spares reports are updated and submitted twice-yearly to 526 ICBMSW, 20AF/A3NB, AFSPC, the ICPS sites, and the Codes IPT. On-site visits will be conducted as determined by the Codes IPT, subject to available funding, to ensure that inventory records are accurate and that an adequate inventory is being maintained. The Contractor will assist site personnel in resolving inventory problems.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 22 of 37

Figure 7. ICPS Spares Inventory Control Management Process

1.5.10 ICPS Spares Procurement, Scheduling, and Delivery Support The spares procurement process shown in Figure 9 involves order review, order control and generation of the required documentation to procure new and replenishment spares identified by the spares assessment analysis. This procurement is performed within the constraints of available funding as determined by the Codes IPT. Schedule management is the decision-making process that ensures on-schedule delivery of procured spares. The approach involves conducting meetings and corresponding with vendors, customers, and among The Contractor functions to resolve any procurement problems. Delivery support includes: performance of delivery surveillance and delinquency reporting; issuance of basic shipping instructions; and close-out and reconciliation, as applicable, of all elements of effort pertaining to delivery of materials.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 23 of 37

Figure 8. ICPS Spares Procurement, Scheduling and Delivery Support

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 24 of 37

1.5.11 ICPS Spares Assessment and Consumption Management Spares assessment and consumption management relies upon the results attained from execution of the Spares Assessment Model, as depicted in Figure 10. Data from the site inventory reports received from the field are inputs to the model. The data output from the model is also compiled in an assessment report quarterly. This assessment report calculates the spares quantities required to sustain the system through the support period and identifies the spared ICPS components that fall short of this date. Spares shortages identified by the model are documented on a "Watch List". A Watch List Analysis report documents the analysis performed leading to decisions regarding new or replenishment spares. This analysis considers suitable COTS substitutes, if the parts are contractor built spares, nuclear certification issues, near future modifications that might remove parts from the ICPS, weapons system changes that are negating the requirement for equipment and next higher assembl y quantities. Procurement and delivery support will be initiated if spares replenishment is required as determined by the Codes IPT.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 25 of 37

Figure 9. ICPS Assessment and Consumption Management

1.5.12 Laboratory Management/Support Processes and procedures are in place to ensure the accuracy of tasks performed in the ICPS Lab, control Lab equipment, maintain accurate records of Lab activities, and properly safeguard all hardware. The Contractor Process Manual Procedures document the procedures that primarily direct the Lab activities. These procedures include those addressing the following:

(1) Government Furnished Equipment (2) Property Loss, Damage, or Destruction (3) Modification and Repair (4) Failure Reporting, Analysis, and Corrective Action (5) Certification of Test Processes (6) Electrostatic Discharge Control (7) Calibration Control System (8) Engineering Test and Evaluation (9) Certification of Test Equipment/fest Processes (10) Test/Inspection Operations

Sound security practices are ensured by adherence to the procedures specified in the Standard Practice Procedure documents for each site in the Lab. The Standard Practice Procedure includes the procedures for:

(1) Physical Security (2) General Safeguarding, Accountability, and Identification of Classified (3) Markings (4) Declassification, Verification, and Release of Equipment (5) Audit Trails, Records and Logs (6) Communications (7) Emergency Procedures

Failed GFE is returned to the appropriate government facility for repair or replacement.

1.5.13 Interface Management Interfaces between the ICPS and hardware and software used or processed by the ICPS are controlled by lCD (or Internal ICDs for interfaces confined to contractor-developed items). These interfaces may be mechanical, electrical, or functional. Since the ICPS is a mature fielded system, ICDs exist and require only periodic maintenance. The process by which

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 26 of 37

ICDs are maintained is depicted in Figure 12. Maintenance is performed in two ways: (1) generation of an IR,and (2) complete revision of the lCD. IR preparation is done on an a required basis. A complete revision will be performed when directed by the ICWG.

Figure 11. ICD Maintenance Process 1.5.14 Performance Measurement The Performance Measurement process consists of defining metrics, collecting the metrics data, processing the data, and storing the data in a database. The metrics required to provide insight into the ICPS CLS issues and aid in understanding and improving the technical and management processes are defined in section 5 of this plan. Metric collection consists of collection of raw data on a periodic basis. After collection of the data, it must be processed and analyzed to yield indicators that are objective and useful. The metric data will be stored in a database for use in assuring continuous process and product improvement. 1.5.15 Technical and Contract Performance Measurement The ICPS CLS effort involves performing the processes necessary to accomplish the required program tasks. Performance measurements are made to systematically target the

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 27 of 37

processes and implement process improvement. Performance measurements are used to assess and document ICPS CLS technical and managerial performance for ICPS support. The metrics used will be based upon program requiremen ts, key issues, objectives, and processes. The use of metrics data facilitate quality improvement by indicating how well goals are being met and showing trends A metric is a measurement made over time, which communicates vital information about the quality of a process, activity, or resource. The metrics defined in this plan are for the processes specifically related to ICPS CLS. These metrics are to be collected at critical or convenient nodes that, if measured and controlled, will provide maximum benefit to system support/management. These metrics will have the following characteristics:

(1) Accepted as meaningful to the customer (including the user) (2) Tell how goals are being met through processes and tasks (3) Simple, understandable, logical, and repeatable (4) Show a trend (5) Unambiguously defined (6) Economical to collect (7) Timely

This section identifies the performance metrics for the processes, tasks, and products that contribute to achieving the primary ICPS CLS objectives. These objectives pertain to maintaining ICPS availability and managing the ICPS CLS program. Figures 13 and 14 depict the CLS activities contributing to the achievement of the respective primary objectives. By measuring these contributory activities, the extent to which the ICPS CLS program objectives are being met can be evaluated. Performance metrics, measurable and subjective, are defined for the identified ICPS CLS tasks (i.e., engineering support, TO maintenance, spares inventory management, program management), and address response time, time to repair, and reliability and maintainability preservation/improvement. The metrics for the ICPS CLS related tasks/activities/products/ information and their respective measurement criteria have been chosen as key indicators of the quality of performance of ICPS CLS. Response time metrics are identified in Tables 1, 2, 3, and 4. Quality metrics are collected for continuing evaluation of the ICPS CLS processes.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 28 of 37

Figure 12. ICPS Availability Diagram

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 29 of 37

Figure 13. Manage CLS Program Diagram

1.5.16 Reponse Time A response time metric is defined as the elapsed time to complete an action (e.g., process, task, or produce a product) upon receipt of an input(s) that initiates the action. Response time metrics are identified for a number of ICPS CLS tasks and sub-tasks previously defined in this plan. Table 3 identifies and defines the response time metrics that best reflect overall ICPS CLS responsiveness. 1.5.17 Engineering Support Providing engineering support is a key element to achieving maximum ICPS availability. As shown in Figure13, engineering support related tasks include: collecting data regarding ICPS performance in the field, data analysis, investigating field problems, trips to field sites, and preventive maintenance.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 30 of 37

Measurement of some of the tasks listed above is included as part of the metrics for response times as shown in Table 1. Other metrics for engineering support are cited below. The quality of trips to a field site for investigating field problems is measured by utilizing data gathered on those trips. The measurement of the tasks identified will reflect on the ICPS CLS Program's ability to preserve/improve ICPS reliability and maintainability, and on the capability of performing repairs in a timely manner. Support of preventive maintenance inspection is provided. As part of these PMI actions at the field site, verif ication occurs that ensures E-Lab has performed required maintenance on ICPS equipment. E-Lab personnel are notified when required scheduled preventive maintenance has not taken place. Contact with ICPS user personnel in the field occurs monthly. This serves to assess trends with respect to equipment performance, and facilitate rapid response to the occurrence of field anomalies.

Table 1. Engineering Support Repsonse Time Metrics

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 31 of 37

1.5.18 Technical Order Maintenance TO maintenance also contributes to ensuring ICPS availability. The expedient and accurate updating and maintenance of TOs serves to preserve/improve ICPS reliability and maintainability. As shown in Figure13, TO maintenance tasks include collecting and analyzing data regarding ICPS performance that may impact the TOs. Measurement of some of the TO maintenance related tasks (i.e., those pettaining to expediency) are included as part of the metrics for response times as shown in Table 2. The tasks/activities identified in the table are among those that are performed as part of TO maintenance.

Table 2. Tachnical Order Maintenance Repsonse Time Metric

1.5.20 Spares Inventory Management ICPS availability is contingent upon successful spares inventory management. The responsiveness and cotTectness of this process upholds ICPS reliability and maintainability. As shown in Figure 14, spares inventory management tasks are concerned with collecting and analyzing data to determine consumption/trends and obsolescence, and providing support to the spares procurement process. Measurement of some of the spares inventory management tasks is included as part of the metrics for response times as shown in Table 3.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 32 of 37

1.5 SERVICES SUMMARY

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 33 of 37

2.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 34 of 37

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be provided at Draft RFP release

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 35 of 37

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 36 of 37

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 4 CODES – GSSC 2.0

Page 37 of 37

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be provided at draft RFP release

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 1 of 72

ATTACHMENT 5

TRAINERS PERFORMANCE WORK STATEMENT (PWS)

TASK ORDER UNDER THE

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 2 of 72

1.0 Trainers PWS ...................................................................................................................... 4

1.1 SCOPE .................................................................................................................................. 4

1.2 PURPOSE ............................................................................................................................. 5

1.3 BACKGROUND .................................................................................................................. 5

1.4 REQUIREMENT SUMMARY ............................................................................................ 5

1.4.1 APPLICABLE DOCUMENTS ......................................................................................... 5

1.4.2 SPECIAL CONSIDERATIONS ........................................................................................ 6

1.4.2.1 Associated contractors .................................................................................................... 6

1.4.3 Trainers CLS ...................................................................................................................... 6

1.4.4 Trainers Software ............................................................................................................. 14

1.4.4.1 General Requirements ............................................................................................... 14

1.4.4.2 Basic Services ........................................................................................................... 14

1.4.4.3 Disassembly, Cleaning, Inspection and Test ............................................................ 15

1.4.4.4 Condemnation ........................................................................................................... 16

1.4.4.5 Corrosion Prevention and Control ............................................................................ 16

1.4.4.6 Finishing ................................................................................................................... 16

1.4.4.7 Required Markings.................................................................................................... 16

1.4.4.8 Product Acceptance .................................................................................................. 17

1.4.4.9 Specific Services ....................................................................................................... 17

1.4.4.10 Current/Specific Tasks for SW Maintenance ......................................................... 20

1.4.4.11 SERVICE SUMMARY .......................................................................................... 32

1.4.4.12 GENERAL INFORMATION ................................................................................. 35

1.4.5 GOVERNMENT FURNISHED PROPERTY (GFP and services) ................................. 35

2.0 APPENDICES ........................................................................................................................ 36

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 3 of 72

APPENDIX A - ACRONYMS AND ABREVIATIONS LIST ............................................... 36

APPENDIX B - TECHNICAL ORDERS, MANUALS and OTHER CURRENT DOCUMENTATION and SPECIFICATIONS ........................................................................ 41

APPENDIX C - WORK BREAKDOWN STRUCTURE (WBS) ............................................ 49

APPENDIX D - CDRLs ........................................................................................................... 49

APPENDIX E: CLS/CMS TRAINERS TABLES ................................................................... 50

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 4 of 72

1.0 TRAINERS PWS

1.1 SCOPE

The Trainer Contractor Logistics Support (CLS) Contractor Maintenance Support (CMS) requirement is to provide continuous technical, logistic, and maintenance services to support the Minuteman Intercontinental Ballistic Missile (ICBM) Operations Trainers and Maintenance Trainer Operations & Equipment. Technical elements of CLS are composed of maintenance support, software sustainment, and technical engineering data support. Management of CLS consists of a properly structured organization of trained & qualified personnel working within specific security restraints while providing a quality product to the user. This workload is accomplished at the Operational Wings (Malmstrom, Minot, and FE Warren), Vandenberg Air Force Base, and Offutt Air Force Base. No associated WCNs. No discrete quantity, this effort is for engineering services in support of the Contractor Logistics Support for Intercontinental Ballistic Missile (ICBM) Trainers. Contractor Logistics Support for trainers consists of Software support for Operational Trainers and maintenance and sustainment support for all operational and maintenance trainers.

This workload is accomplished by a Contractor, The contractor will perform the work at each Operational Wing (Malmstrom, Minot, and FE Warren), Vandenberg Air Force Base, and Offutt Air Force Base. Air Force Global Strike Command (AFGSC) requires all personnel to be trained prior to performing any operational or maintenance duties on weapon system components. Therefore, operations trainers and maintenance trainers support at the Wings, Vandenberg Air Force Base, and Offutt Air Force Base through Contractor Logistics Support (CLS) is required.

The scope of this effort also includes Development, Test and Execution (DT&E)DT&E to fix software (SW) problems per type (emergency, urgent, non-scheduled, routine) with assumptions, deliveries, and timelines IAW AFGSC Concept of System Support (CSS), conduct problem and related requirements analysis, develop and recommend technical and related funding and budget solutions to problems, re-designing and modifying software (SW) and firmware (FW) (SW/FW) problems, develop post-test 1067 requests, fix problems uncovered in testing as negotiated between GOV and contractor, recommend the certification of SW/FW fixes after testing to program office and to AFGSC/A3I and A4M, maintain integration of current revisions, distribute SW/FW releases, perform Configuration Management (CM) for test and support SW/FW and documentation, recommend technology and SW/FW improvements, perform studies as directed/approved by program office, and maintain SW/FW resources with (CLS), (CMS), military or other hardware maintenance contractor..

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 5 of 72

1.2 PURPOSE

Purpose of this effort is to maintain CLS/CMS trainer support and Trainers operations and support simulation SW and systems as revised, to a correct and high-fidelity condition which is as close as possible to the functions IAW with operational counterpart.

1.3 BACKGROUND

This contract is required to support the Intercontinental Ballistic Missile (ICBM) Systems Directorate (ICBMSD) in its requirement to sustain the Maintenance and Operations trainers along with the software (SW) condition and capability of the ICBM Minuteman III (MMIII) Ground System Trainers under the Ground System Support Contract (GSSC). This activity is comprised of two parts maintenance and operations trainer support and software sustainment.

The Trainer Contractor Logistics Support (CLS) Contractor Maintenance Support (CMS) requirement is to provide continuous technical, logistic, and maintenance services to support the Minuteman Intercontinental Ballistic Missile (ICBM) Operations Trainers and Maintenance Trainer Operations & Equipment.

Thesoftware (SW) and firmware (FW) Development, Test and Execution (DT&E) to sustain actions directed by the Operations Control Board (OCB)(via approved and prioritized form 1067s) with AFGSC/A3I validation for:

1) Missile Enhanced Procedures (MEP) Trainer and Missile Procedures Trainer (MPT), or

2) Airborne Launch Control System Trainer (APT) with AFGSC/A4M validation for 1067s for the Minuteman Maintenance Trainers (MMT including the QDIT and QD Trainers), the

3) Control Monitor Procedures Trainer (CMPT – classroom and field variants with associated peripheral assemblies), and subsystem trainers including the Fast-Rising B-Plug Classroom Trainer (CT), Power and Environmental Control Trainer (P&ECST) which includes the Missile Power Processor (MPP), Automatic Switching Unit (ASU) and the Power Control Computer (PCC – contained in Cummins Diesel Electric Unit (DEU) and support systems laptops and applications SW commercial packages for PCC FW trouble-shooting and DEU operational settings).

The MMT, CMPT and subsystem Trainers are going through modifications at this time

1.4 REQUIREMENTS SUMMARY

1.4.1 APPLICABLE DOCUMENTS

Compliance and reference documents related to specifications, standards, handbooks, regulations, instructions and tables applicable to the work required in the performance of this

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 6 of 72

contract are listed in APPENDIX B. If vendors are knowledgeable of critical documents or requirements not listed in this task order, it is expected they inform the Government to ensure adequate coverage. The contractor will be responsible to use the latest version of compliance documents.

1.4.2 SPECIAL CONSIDERATIONS

1.4.2.1 ASSOCIATED CONTRACTORS

The TSSC contractor will need to act in cooperation with the ICBM support contractors, ICBM Ground Support Systems Contractor (GSSC), ICBM Integration Support Contractor (BAE), AFGSC/A3I and A4M, 625 STOS/ALCS, 20 AF/A3 and NIA (Ground Systems), and NIE (NI Engineering) and AF Supply Complex (AFSC/414 SCMS) for the overall success of the effort. The contractor will be required to negotiate appropriate non-disclosure agreements (NDA) or associate contractor agreements (ACA) with the cited Government and contractor entities who are participating in the Trainer SW requirements so that information needed in support the effort can be freely shared. While the Government maintains close relationships with support contractors, contractors are not allowed to perform inherently governmental functions. The responsibility to direct other contractors and ultimately approve or disapprove reports and other products remains with ICBMSD. The contractor shall accommodate support of independent contractor representatives whose primary duties require on-site access, a dedicated work space, and observation of repair activities. Support provided by these contractor representatives will provide independent insight to repair activities. The contractor shall engage with both the government and contractor representatives to avoid organizational conflict of interest (OCI) circumstances. The contractor shall support visits of ICBMSD representatives, including support contractor representatives, and will engage with the government to avoid organizational conflict of interest (OCI) circumstances.

1.4.3 TRAINERS CLS/CMS

1.4.3.1 The contractor shall provide continuous technical, logistic, and maintenance services to support the MM ICBM Operations Trainers and Maintenance Trainer Operations & Equipment. The contractor will also provide ICBM Trainer Software support IAW with the Software Support section contained in this Task Order.

1.4.3.2 The contractor shall provide continuous Engineering Services and Sustainment Engineering support (IAW GSSC PWS 1.4.1 and 1.4.2) of the MM ICBM Operations Trainers and Maintenance Trainer Operations & Equipment IAW APPENDIX E Tables 1 and 2.

1.4.3.3 The contractor shall provide CLS/CMS that maintains and sustains specified ICBM systems, devices, and equipment to the level of mission capable (MC) operational availability of 95% and technician support and response times listed in APPENDIX E, TABLE 3.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 7 of 72

1.4.3.4 The contractor shall provide the availability percentage calculations monthly for each training device. All hours on the weekly schedule, as modified by surges, are credited as scheduled time.

1.4.3.5 The formula for monthly trainer availability calculation is provided below. The monthly trainer utilization and availability status will be reported in the Monthly Field Service Report (FSR).

1.4.3.5.1 (CLS/CMS) – Training Time Lost

All periods of trainer non-availability that detract from unit trainer availability are categorized as either chargeable or non-chargeable lost time.

1.4.3.5.2 (CLS/CMS) – Chargeable Lost-time

All training time lost is calculated as chargeable lost time – except as identified in (Non-Chargeable Lost Time). Chargable Lost Time begins once the contractor physically responds on site. Chargeable lost time shall be determined by the local Project Officer (PO) (or representative).

1.4.3.5.3 (CLS/CMS) – Non-Chargeable Lost Time

Non-chargeable lost time is that portion of lost time for which the contractor is not held responsible. Non-chargeable lost time exists under the following conditions:

• Facility power outage, when not caused by contractor negligence. • Fire or other facility problems, when not caused by contractor negligence. • Negligence on the part of Government personnel. • Natural disaster (e.g., flood, windstorm) or inclement weather (determined by the PO or

representative). • Criminal acts by persons not employed by the contractor. • Failure of the Government to supply the required parts and/or responses for which it has

responsibility. Lost time designated non-chargeable under this condition shall commence upon receipt of such request by the Government, and shall terminate upon checkout (after installation) of the parts delivered to the contractor by the local base supply function. Time tracking shall be verified by the PO or OAR.

• Non-serviceability of hardware, software or firmware systems which are solely the responsibility of the Government, as identified in APPENDIX E Table 4.

• Time lost as a result of trainer damage incurred during a weather warning period after: o Receipt of a severe weather warning issued by the local base weather office or

Command Post, and o Notification of the trainer operator, and o Continued Government operation of the trainer after recommendation by the

contractor to discontinue trainer operations. • Maintenance response time (APPENDIX E Table 3).

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 8 of 72

• Time lost as a result of failures during non-contractor supported hours (APPENDIX E Table 3).

• Periodic Maintenance Inspections (PMI) • Trainer modifications or TCTOs.

1.4.3.5.4 (CLS/CMS) – Impaired Trainer Sessions

When a trainer is less than Mission Capable (MC) for reasons for which the contractor is responsible, lost-time will be assessed for the scheduled trainer time lost, The Government may elect to conduct an impaired-trainer session, rather than declaring a trainer unacceptable for training use (not MC) and turning the trainer over to the contractor for repair of the malfunction of the required trainer items. Impaired-trainer sessions will be conducted with no chargeable lost time credited. The Government may declare the trainer not MC at any time during an impaired-trainer session, and allow the contractor immediate access to repair the malfunction. If the trainer is declared not MC, the lost time will be chargeable.

1.4.3.5.5 (CLS/CMS) – Availability Disagreement

If disagreement exists between the contractor and the PO on the computation of availability, impaired mission hours, complete details of the malfunction(s), scheduled activities, facility conditions, and any other factors affecting the non-availability or aborted trainer session(s) shall be documented by the contractor and the PO, and forwarded to the Administrative Contracting Officer (ACO) as an attachment to the contractors next monthly billing. The ACO is the final decision authority in areas of availability disagreement.

1.4.3.5.6 (CLS/CMS) – Availability Calculation Formula:

(Hours available – Chargeable lost time) divided by (Hours available) x 100 = Trainer availability WHERE: Hours available = Hours the contractor is on site (CLS) – Utilization Calculation Formula: Hours utilized divided by (Hours available x Trainer availability rate) WHERE:

Hours Utilized = Total hours a trainer is used including: Training, software testing, script proofing and evaluations.

1.4.3.6 The contractor shall provide CLS/CMS capability that includes the performance of all trainer maintenance and corrosion control activities compliant with technical data (TOs/TMs,

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 9 of 72

specifications, and drawings), commercial manuals, and directives as necessary to maintain the training devices and equipment identified in APPENDIX E, TABLE 2 at mission capable (MC) status. Examples of maintenance activities include but are not limited to: minor to moderate corrosion control repairs, up to but does not include replacement of surface material, to return surfaces to required configuration; paint removal, painting; cork repair, nut plate replacement, servicing of air conditioning systems, inspections and periodic maintenance. All required replacements of stencils, markings, etc. will be done IAW Tech Data and Drawings.

1.4.3.7 The contractor shall establish, implement, and maintain a logistics support posture that maximizes trainers, and equipment availability (APPENDIX E, TABLES 1 & 2) for use by the AFGSC and Air Education and Training Command (AETC) and provide the updates monthly in a monthly Contract Field Service Report, Technical Operation Report)

1.4.3.8 CMS Maintenance Trainers and Equipment. The contractor shall provide qualified technicians to respond during scheduled support hours to troubleshoot and repair the trainers listed in APPENDIX E, TABLE 2. Trainer response times are defined in APPENDIX E, TABLE 3. For supported equipment not listed, the response time will be within (1) business day. The contractor will deliver a quarterly maintenance report, Maintenance Service Report. This report should include all maintenance actions (e.g. remove and replace, troubleshooting, repair of removed training device components (e.g. circuirt cards), etc.).

1.4.3.9 CLS Trainers and Equipment. The contractor shall provide basic trainer operations support to the user, if requested during normally scheduled support hours .

1.4.3.10 CLS Maintenance Trainers and Equipment. The contractor shall provide qualified technicians who possess sufficient knowledge and technical expertise for the trainers/equipment identified in Table 1 to perform the requirements specified in this Task Order. Trainer response times are defined in APPENDIX E, TABLE 3; for supported equipment not listed, the response time will be within (1) business day. After initial response, the maintenance activities shall address troubleshooting and repair within the normal work shift. The contractor will deliver a quarterly maintenance report, Maintenance Service Report. This report should include all maintenance actions (e.g. remove and replace, troubleshooting, repair of removed training device components (e.g. circuirt cards), etc.).

1.4.3.11 CLS Maintenance and Government Furnished Equipment (GFE). The contractor shall maintain the trainers in APPENDIX E, TABLES 1 and 2 IAW the applicable documentation listed in this Task Order. The contractor shall perform all scheduled and unscheduled maintenance, servicing and repair actions required to maintain the operability and usability of the trainers. The contractor shall repair and maintain all spares that are provided as GFE in a serviceable condition. The contractor will also provide an annual inventory IAW, DIALSS-81533C, Government Furnished Material (GFM) and End Item Transaction Report.

1.4.3.12 UPS TSSC Maintenance. The contractor will service and repair the Uninterruptable Power Supply (UPS) in building 7403B at Vandenberg AFB supportting the TSSC.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 10 of 72

1.4.3.13 Trainer Equipment and Training Aids Maintenance. The contractor shall service trainers, trainer equipment, and training aids, not managed by a Logistics Center by using the best commercial practices. APPENDIX E, TABLE 2

1.4.3.14 Media Maintenance. The contractor shall maintain all Government authorized software and firmware trainer media such as computer disks, tapes, and removable storage media IAW configuration management, security, information assurance and site policy and procedures.

1.4.3.15 Servicing. The contractor shall perform cleaning, adjusting, ordinary lubrications, tightening of nuts and bolts, troubleshooting, calibration, and preventive maintenance actions recommended by the manufacturers’ commercial manuals or specified in the equipment technical data or user manuals, including weapon system equipment items (see APPENDIX E, TABLE 4, Government Weapons System Controlled Items – Government Supply and Depot Responsibilities). This servicing is to be performed during normal CLS/CMS duty hours as trainer availability allows. The contractor will deliver a quarterly maintenance report, Maintenance Service Report (MSR). Maintenance activities requiring the use of a crane, maintenance on an equipment item that is the responsibility of and performed by the designated shop (resource flight – ELAB, Mechanical and pneudraulics sections (MAPS); Depot), and items listed in Table 5 are the responsibility of the local unit. The contractor is responsible to coordinate with local maintenance shops to gain access to a tool account and/or access to checking out specialized tools to perform maintaenance activities requiring these tools. Provide

1.4.3.16 Maintenance, Inspections, and Tests. The contractor shall perform all inspections, repairs, replacement of parts or assemblies, testing, calibrations, and operational checks to correct the malfunctions and verify adequate and proper serviceability of all components, or subsystems of those items listed in APPENDIX E, TABLES 1 and 2, except those items identified in APPENDIX E, TABLE 4, Government Weapons System Controlled Items – Government Supply and Depot Responsibilities. These actions are to be performed during normal CLS/CMS duty hours as trainer availability allows. Maintenance activities requiring the use of a crane, maintenance on an equipment item that is the responsibility of and performed by the designated shop (resource flight – ELAB, Mechanical and pneudraulics sections (MAPS); Depot), and items listed in Table 5 are the responsibility of the local unit. The contractor is responsible to coordinate with local maintenance shops to gain access to a tool account and/or access to checking out specialized tools to perform maintenance activities requiring these tools.

1.4.3.17 Support Equipment. The contractor shall use only properly calibrated test measurement and diagnostic equipment (TMDE) when performing calibration of the trainers’ support equipment and ATE. All GFE trainer support equipment and ATE shall be calibrated before being returned to the Government at the end of contract performance.

1.4.3.18 Trainer Setup. During normally scheduled support hours, the contractor, if requested by user, shall accomplish trainer setup for MPT, APT, and Minuteman Enhanced Procedures (MEP) activities prior to each trainer session. Setup shall include loading software and user-developed courseware, and performing equipment conversions. These activities are to be done during normally scheduled support hours.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 11 of 72

1.4.3.19 Non-configured Equipment. The contractor shall maintain and provide replacements as required for the following items.

• Instructor and student console Plexiglas • Battery-operated emergency lighting equipment • Handsets and headsets (including consumable ear pieces) • Unit installed simulated Emergency War Order (EWO) safes (lock boxes) • Rubber floor matting, carpet and/or linoleum floor covering installed in the trainers • Book storage cabinets/shelves installed in the trainers • Fire extinguishers installed in the trainers

1.4.3.20 Weapon System Controlled Items. The contractor shall perform maintenance of the equipment listed in APPENDIX E, TABLE 4 to the extent authorized by Government-approved technical order (T.O.) procedures and data, and Government-provided replacement spares/consumable items. Items that cannot be repaired using approved T.O. procedures shall be forwarded to the appropriate Air Force depot for repair through the local base supply. Replacement items shall be obtained from the unit supply function by coordinating the request with the local unit.

1.4.3.21 Technical Manual (TM) Core Requirements. The contractor shall have sustaining custodial responsibility for all TMs identified in CLS-90-01 and shall update, maintain, print, and distribute changes IAW CLS-90-01. The contractor shall identify additional commercial manuals that are required, but have not been provided, for the maintenance of the trainers. All commercial manuals that are approved for purchase shall become property of the Government. The contractor shall correct all TM deficiencies as directed by the Technical Manual Management Agency (TMMA). The contractor shall incorporate, publish, and distribute TM changes. Distribution of TMs will be made to all deliverable organizations in Attachment 3 of CLS-90-01.

1.4.3.21.1 Initial TM Issue. The contractor shall be responsible for providing a complete set of TMs and reproduction media to the Government at the conclusion of the contract. The set shall contain the latest revisions (incorporated) and be in usable condition. The contractor shall replace missing data and shall recommend deletion of all outdated documentation.

1.4.3.22.2 TM Verification. The contractor shall verify changes and revisions to CLS maintenance TMs and assist in the verification of changes and revisions to SIMCERT TMs, upon request from the TMMA.

1.4.3.22.3 TM Index. The contractor shall develop a TM index that includes a listing of current TMs, the latest changes, and the dates of CLS contractor-developed publications Technical Data Package Index.

1.4.3.22.4 TM Deficiencies. The contractor shall identify all TM deficiencies. The contractor shall validate all SIMCERT TM deficiencies, and then forward them to AFSPC Missile Operations Trainer Program Management Office (HQ AFSPC/A3TO) at Barksdale AFB LA.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 12 of 72

1.4.3.22.5 Technical Order (TO) Deficiencies and Changes (IAW TM-86-01). The contractor shall prepare Air Force Technical Order (AFTO) Forms 22, Technical Manual (TM) Change Recommendation and Reply for any deficiencies noted in Air Force managed Technical Orders (TO). All AFTO Forms 22 shall be reviewed by TSSC Management and submitted for processing IAW TO 00-5-1, AF Technical Order System as supplemented.

1.4.3.23 Drawing Changes. The contractor shall develop engineering drawing changes for all impacted trainers and drawings IAW contractor existing drawing practices. The contractor shall subcontract with the baseline custodian for each affected trainer for the integration of configuration changes.

1.4.3.24 Temporary – Fixes. The training devices shall be maintained to function and be configured as described in the approved TOs and TMs, engineering data, and approved commercial technical data. Temporary fixes shall comply with applicable Government guidance. The contractor’s Quality Representative/Site Manager will certify the temporary repair work and related documentation.

1.4.3.25 Temporary Fix approval. All temporary fixes will be coordinated through the System Program Office (SPO), 20AF/A3/A4 and AFGSC/A3/A4 and approved prior to implementation IAW AFI 63-101 paragraph 9.3.2. Temporary fixes are designed to correct an immediate issue and not meant as a permanent repair, correction or modification.

1.4.3.26 Modification Installation. The contractor shall install Government-approved modification kit after Air Force acceptance of the kit proof or trial installation, when directed by the applicable contracting authority. If the installation of a modification kit results in additional costs to the contractor, the contractor shall submit a cost proposal in writing to the applicable contracting authority for approval prior to installation. The contractor shall install all MCLs and TCTOs to applicable trainers within timelines identified in the change notice.

1.4.3.27 The contractor shall not install any modification kit unless the scheduled installation has been approved by the Government.

1.4.3.28 Responsibilities during Modifications by Other Contractors. The modification contractor accomplishing kit proof or trial installation is responsible for maintenance of the trainer for the areas affected by the modification. The contractor shall maintain all other areas of the trainer during the modification period. The condition of the training device shall be verified before and after a modification installation to assure the trainer is returned to the contractor in a functionally verified condition. This verification effort shall be jointly accomplished by the contractor and the modification contractor as part of the modification contract. During pre-modification inspection, the contractor shall correct the conditions which would degrade or preclude installation of the modification, if directed by the Government. The modification program is responsible for any required contractor personnel technical training resulting from trainer modifications.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 13 of 72

1.4.3.29 Responsibilities during annual/semi-annual trainers conferences. The contractor shall coordinate and facilitate both the annual Technical Interchange Meeting (TIM) and semi-annual Program Support Review Meeting (PSR).These meetings, hosted by AFGSC/A3T/A4B and AETC, allow the trainer community to discuss current and future trainer modifications, scheduling, and issues and to review all operations and maintenance trainers for currency and supportability. The contractor will schedule the TIM / PSR, and assemlbe the agenda and provide hard copies of agenda and charts to all participants in coordination with the SPO. The contractor shall deliver the approved meeting presentation package approximately 2 weeks prior to the meeting date. The contractor shall provide sufficient packages for each conference participant. The contractor shall record and track all meeting action items through completion and provide meeting minutes with updates to the briefing slides approximately 2 week following the meeting.

Contractor is responsible for annual review and updates to the Trainer Handbook. Printing of the handbook (size and format to be determined by Government) will be provided 2 times during the contract when request by the Government (minimum of 70 copies).

1.4.3.30 Facilities: Government will provide a minimum of 1 Computer, 1 Printer, and 1 DSN Government phone line for IMDS access at each of the five locations. Office space will be provided IAW the U.S. Air Force required/authorized 6’x6’ work space.

Sevice Summary Summary

The below table lists performance standards (metrics) the Government will use for monitoring contractor performance on critical tasks. These metrics are a meaningful measure of contractor performance and conform to commercial standards to the maximum extent practicable. The Government will audit the contractor’s processes to ensure they are in place and will use the data from the contractor inspection reports to assess contractor performance along with contractor information addressing the below measures of performance via a PowerPoint Presentation. In lieu of a PMR/TIM the Government may 1) require electronic submission of the PMR/TIM PowerPoint slides (described above) for Program Office review of contractor performance, or may 2) waive any or all PMRs/TIMs, at Government discretion. Contractor will be notified by the Program Office of PMR/TIM intentions and directions by the Government.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 14 of 72

Performance Objective

Task Order Paragraph

Performance

Method of Surveillance Performance Thresho

1 FSR 100% on-time delivery to users. 2 MSR 100% on-time delivery to users. 3 Annual Inventory 100% on-time delivery to users. 4

1.4.4 TRAINERS SOFTWARE 1.4.4.1 General Requirements

The TSSC contractor shall provide all personnel, supplies, tools, materials, and other items necessary to perform SW maintenance to Trainer systems and assemblies cited in 1.0 SCOPE, and shall use Government Furnished Equipment (GFE) contained in the Trainer Systems Support Center (TSSC) (MPT/MEP, APT/APTE and SDME). In the case of MPT/MEP and APT/APTE DT&E, USSTRATCOM and AFGSC will determine thru NIA the basic schedule for the changes (development/test/delivery).

The contractor shall also perform disposal actions as required under this contract.

The current Trainer SW maintenance workload (defined by 1067s) is centered on the MPT/MEP and the APT/APTE, which DT&E resources are currently available in the TSSC. However, the APT/APTE does not adequately cover full development and system test of the APT, and requires the APT at Offutt to complete. The TSSC contractor will develop new 1067s to cover test issues and other deficiencies uncovered outside the approved 1067 packages for trainer end items or components comprising the MPT/MEP and the APT/APTE. Currently, the MMT, auxiliary subsystems within the P&ECST and B-Plug CT contain HW/SW/FW for which no organic DT&E capability exists. At this time and into the future the MMT, P&ECST items and the B-Plug CT systems are undergoing various major modifications or replacements, and future maintenance HW/SW/FW projects. After these modifications, maintenance 1067 requirements (not currently existent) will arise and be integrated into the workload, as agreed between AFGSC/A3 and A4, NIAI and the contractor. This workload will, like the APTE, require definition/development of further TSSC DT&E capabilities before it can be successfully integrated as a workload.

1.4.4.2 Basic Services

1.4.4.2.1 The TSSC MPT/MEP DT&E system, also known as Software Development & Maintenance Environment (SDME) is contained in a closed compartment, which facilitates

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 15 of 72

classified development, operation, test and media/data storage. Formal testing of the MPT/MEP is conducted in the SDME. The APT/APTE DT&E lab area is part of the TSSC, but is contained in an open area as the SW does not process classified code, data, media or documentation.

The configuration of the SDME within the TSSC shall not be altered without AFNWC/NI CM process and NIA approval and participation. Electrostatic Discharge (ESD) procedures around electronic equipment and computer systems are cited in TOs in Appendix D as applicable, and MIL-STD-1686 and MIL-HDBK-773 will apply.

1.4.4.2.2 The contractor shall perform DT&E SW maintenance on Trainer systems as specified in 1.0 SCOPE. These services will be primarily focused on fixes as addressed in 1067s which are derived from various functional sources (including organic and contractor developers) and approved by AFGSC and AFNWC/NI. The functional program sources include Higher Authority Communications – Rapid Message Processing element (HAC-RMPE), Rapid Execution and Combat Execution (REACT) Console Operation Program (COP), ICBM Operations Software Sustainment Program (IOSSP) and their related trainer sources. Changes to the MPT/MEP and the APT will be routinely gathered and worked into revision packages/trainer SW baselines, as directed by USSTRATCOM OCB and further negotiated with AFNWC. The MPT/MEP changes typically occurs about 2x per year (6 mo cycle) and the APT/APTE changes occur about 1x per year (12 mo cycle). Additionally, every 18 months the IOSSP will integrate and test an update to the current baseline. Prior to the end of IOSSP, the ICU-2 and MMPU will provide program modifications for incorporation into the MPT and SDME (with additional workload) which will require maintenance contractor activities.

1.4.4.2.3 Until MMPU has been fully fielded, the MMPU trainer hardware and MMPU trainer SW will be regularly integrated into the MPT and form a dual-baseline SW and HW configuration (2 baselines) which will affect the DT&E workloads and MPT and SDME configurations. Additionally, there will be a need for the integration of the dual baseline into both the non-MMPU and MMPU configured MPT trainers. These dual-baseline activities will impact both MPT, MMPU, and HAC/RMPE software updates, and will continue until the MMPU modifications are fully fielded (operationally and trainers).

1.4.4.2.4 Emergency (144 hour) and urgent changes (60 – 90 days) may occur but are rare (Urgent 1 per 5 years, Emergency – no history of occurrence).

1.4.4.3 Disassembly, Cleaning, Inspection and Test

The contractor shall clean filters, inspect/test as necessary in order to maintain each system (and in-particular the complete TSSC suite) in operable order. Inspection, test, fault isolation, and repair IAW technical (Government & commercial) data listed in Appendix C and D, and shall be done in concert with the Contractor Logistics Support organization. Identified repairs involve test, adjustment and replacement. All defects shall be remedied and are chargeable to the contract. Defects shall be confirmed to the extent necessary to assure definite acceptance or

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 16 of 72

rejection of the suspected item. Rejected items will NOT be subject to Closed Loop Failure Analysis (CLFA) actions or Failure Review Board (FRB) actions.

1.4.4.4 Condemnation

Condemnation typically occurs when the repair costs exceed 75% of the cost to purchase a new item. Repair costs that exceed 75% of the cost to purchase a new item require approval from program office prior to beginning repair. The contractor shall research the cost to purchase new replacement and if a new replacement is not available and/or obsolete, the contractor shall not condemn items without prior approval of the Program Manager through the PCO. This situation will probably occur with cables, connectors, electronic assemblies, computers, etc…, but is not meant to apply to the entire TSSC, the MEPs and APT/APTE.

1.4.4.5 Corrosion Prevention and Control

The contractor shall accomplish corrosion prevention and control IAW TO 1-1-691F and MIL-223 HDBK-1568.

1.4.4.6 Finishing

1.4.4.6.1 Internal Finishing - The contractor shall repair or replace damaged internal protective finish to the extent necessary to ensure serviceability and provide protection during operation IAW the technical data listed in Appendix C and D.

1.4.4.6.2 External Finishing - The contractor shall accomplish external finishing only to the extent necessary to provide adequate protection and a reasonable/durable cosmetic appearance. Minor scratches shall be touched up or spot painted IAW the technical data listed in Appendix C and D.

1.4.4.6.3 Damaged Markings - The contractor shall replace damaged markings, identification and decals IAW the technical data listed in Appendix C.

1.4.4.7 Required Markings

The contractor shall fill out the necessary condition tags upon completion of refurbishment of the end items. The contractor shall append the condition tags to the end items prior to shipment and shall ensure that they are legible and correct IAW the technical data in Appendix C and D. The contractor shall permanently and legibly mark each completed end item with the contractor’s facility identification. This identification will display the name of the contractor facility, date of repair, and contract number. This identification may be by decal, rubber stamps, or stencil as appropriate IAW the technical data in Appendix C and D. When using rubber stamp or stencil, use permanent waterproof ink or paint of contrasting color.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 17 of 72

1.4.4.8 Product Acceptance

The contractor shall perform repair and validation of asset serviceability of TSSC equipment IAW established TOs, commercial manuals and approved processes.

1.4.4.9 Specific Services

1.4.4.9.1 MPT/MEP SW Maintenance

Software sustainment efforts in trainers are directed toward routine, urgent and emergency changes (via 1067 requirement) to the MPT and MEP (herein termed MPT/MEP) – about 90%, with the remaining 10% allocated to APT, TSSC system and other SW efforts (MMT, other auxiliary SW), with other program modifications and SDME usage “exceptions” noted in paragraph 1.4.4.10.1 and 1.4.4.10.2. MPT/MEP support will normally comprise 2 routine support packages per year on one SW baseline, and the APT estimating 1 package every 12 months on one baseline. During the MMPU dual-baseline period the contractor will maintain 2 baselines (of both hardware and SW) – one baseline of HAC/RMPE and one baseline of HAC/RMPE with MMPU. At the current time MPT/MEP activities consumes most trainer software resources, but it is envisioned that as the APT begins to draw greater 1067 attention, having been recently modified and gone through first sustainment activity, more 1067s will be generated. The SDME SW and HW configuration and support baseline will be developed by the contractor, and will be discussed below.

Trainer software change requirements (1067s) for the MPT/MEP and the APT/APTE are determined and prioritized (1 – 5) by AFGSCs Operations Control Board (OCB), and is derived from OPLAN 8010, REACT/COP, and trainer-unique changes requested by the end users (Wing instructors/evaluators). Currently, the directed changes come to Trainers program in a variety of ways: 1) OPLAN 8010 changes to HAC/RMPE are operationally conceived by a joint USSTRATCOM/J381 and AFGSC/A3I and requirements provided to a government-led/contractor supported HAC/RMPE Software Support Facility (HSSF) team. Requirements that are provided to Government software developers (HSSF and their contracted support) are developed into operational changes to the HAC/RMPE Message Processor (MP), classified Parameterized Data (P-Data) database, Communications Integrator (CI) and Transmission Integrator (TI) firmware and Reserve Forces Target List (RFTL) Database at the TOP SECRET/NC2-ESI level and a training version (at the TOP SECRET level). Since the operational SW/HW and trainer SW/HW are unique in classification (to allow the trainer version to be used with students who are in the process of obtaining final security clearance and NC2-ESI access) and performance in that the trainer software emulates the firmware that is not physically present in the MPT/MEP and adds instructor faulting capabilities. Operationally developed changes are provided by HSSF and their contractor support to the TSSC contractor (at the TOP SECRET level) for baseline trainer software integration, system integration testing, formal acceptance/regression testing, delivery of copies to training sites and subsequent fielding. The TSSC trainer team (contractor) shall maintain the MPT/MEP software as a configuration-managed baseline, in TOP SECRET repository and made available to the Government and/or other modification contractors, as directed. REACT/COP changes come directly from IOSSP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 18 of 72

contractor support for development into Console Operations Program (COP) software, a version which shall be integrated with the current trainer baseline – these activities are covered under the respective programs. The new COP software revision is unit & integration tested by IOSSP contractor support which performs a “demonstration” of the COP changes to the Trainers Government Program Office at existing MPT/MEP facilities. The approved COP changes are then provided to the TSSC contractor for integration, as part of the COP modification program, into the trainer software baseline with further Verification and Validation (V&V) testing and interaction with IOSSP contractor support. The TSSC contractor shall integrate and test trainer-unique software changes, and then perform a systems integration and acceptance/regression test for the AFNWC/NIA, 20 AF and AFGSC/A3I in the final trainer software baseline. This baseline version shall then be delivered to the training sites and fielded. A master copy of integrated baseline shall be maintained by TSSC contractor. This estimate of MPT/MEP software activities is directed toward IOSSP contractor support & TSSC contractor efforts. TSSC contractor shall perform changes to MPT/MEP databases to accurately emulate communication system and missile targeting parameters. These include significant coding of simulated crypto keys, channel data and configuration parameters for emulation of the Military Strategic and Tactical Relay (MILSTAR) UHF, MILSTAR EHF, VLF/LF and SACDIN systems, as derived from the classified 20th Air Force Communications And Reporting Directive (CARD)), Target/Execution Plan Case Input Library, Preparatory Launch Command – A (PLCA) and Preparatory Launch Command-B (PLCB) libraries, which are derived from the 20th Air Force Training Target and Timing Document (TTATD). These changes are normally accomplished annually in conjunction with but not limited to associated changes to OPLAN 8010.

End-user requested changes (from AF Form 1067) prioritized by OCB and assigned for work by AFNWC and ICBM SPO are included in software sustainment efforts. These 1067s typically cover simulation fidelity deficiencies between the MPT/MEP/APT software and the operational weapon system, user interface improvements to aid instructors, system/code maintenance and system performance enhancements. TSSC contractor shall perform these corrections, modifications, improvements and enhancements using funded contract Level of Effort (LOE) remaining after completing requirements described in comments above.

This change process (as shown in the AFGSC CSS document) is shown below:

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 19 of 72

Trainer software change requirements (AF Form 1067s) for the SDME are determined by AFGSC/A3I and software sustainment of current tools and documentation in that laboratory by the TSSC contractor.

1.4.4.9.2 APT SW Maintenance

Trainer software change requirements (AF Form 1067s) for the APT applications software are determined and prioritized (1 – 5) by AFGSC OCB as derived from E-6B crew station changes, ALCS procedure changes, instructor interface improvements and other trainer-unique/fidelity changes required to emulate the Battle Staff area and Airborne Launch Control System portions of the E-6B. Currently, directed changes are envisioned to come to trainers program and directed to the TSSC contractor for front-to-back development (in the APTE) and then system integration and field-tested at Offutt in the one-of-a-kind APT. Future software change requirements (1067s)

ICBM SD or

ICBM SD or SMC

ICBM SD or

ICBM SD or SMC

532 TRS

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 20 of 72

for the APTE will be determined by AFGSC/A3I and may represent a view toward upgrade of the obsolete equipment and documentation used to develop APT software.

APT software efforts have failed to achieve full fidelity in the past, resulting in multiple trips to the APT facility and extensions to testing schedules to ensure each APT station is correctly emulated in the software. These failures are solely attributable to the software development environment not being capable of full emulation of all APT operations. In order to reduce software development risk, better adhere to modification schedules, and assure greater fidelity in the trainer simulation, the contractor shall provide a detailed list of equipment to be added to the TSSC for incorporation and sustainment in order to provide an accurate emulation and development environment, to include integration of the APT Trainer Software into the new GFE hardware with expanded software emulation to accommodate a more effective test and evaluation environment. This list of equipment shall include government furnished items as well as items the contractor will need to purchase; with a total price estimate for all items.

1.4.4.9.3 MMT SW Maintenance

Trainer software requirements (AF Form 1067s) for the MMT may occur after completion of the current round of modification programs, and may be selected for incorporation into the MMT SW baseline. The TSSC shall be responsible for these updates and incorporation.

1.4.4.10 Current/Specific Tasks for SW Maintenance

The following tasks (including boards, reviews, developments, testing, delivery, training and other miscellaneous) are primarily associated with software sustainment changes to MPT/MEP and APT which have been approved and directed by the USSTRATCOM OCB and allocated to IOSSP contractor support and TSSC contractor and software provided to TSSC contractor by HSSF and their contractor support for integration. The goal is to establish 100% MPT/MEP simulation and training compatibility and operability with the corresponding operational REACT system (including critical Emergency War Order (EWO) and other procedures that cannot be trained in the operational system due to WSSR prohibition) by maintaining the integrity and fidelity of the MPT Control Program (MPTCP), Trainer databases and supporting software/firmware of the MPT/MEP REACT training simulation.

“Tasks” are applied to 1) software received for integration and demonstration (DEMO) or system integration testing (SIT), and 2) 1067 requirements received for development, integration and contractor system tests. Sustainment software activities allocated to the MMT, SDME and APTE would “follow” the same tasks but with an agreed required need date.

1.4.4.10.1 SW Maintenance Requirements – MPT/MEP and APT/APTE

The TSSC contractor shall perform the following tasks related to development of software changes:

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 21 of 72

a. Perform change planning including Engineering Change Proposal (ECP) and Specification Change Notice (SCN) development, specification and related design documentation updates, version control documentation, Technical Order update, QA planning and other contractor-determined activities necessary to process, integrate, and test the changed software or the AF Form 1067 changes provided in response to ROUTINE, URGENT and EMERGENCY USSTRATCOM directed requirements (reference AFGSC CSS);

b. Develop and maintain a program schedule and other program tools with cost accounting to support reporting requirements and other related activities prescribed by the main contract. Perform adjustments to the schedule as required by AFNWC/NIA – all responses;

c. Prepare and deliver draft Initial ECP briefs to NIA to support LEVEL II Briefings and the Technical Evaluation Review Board (TERB) briefing by NIA Program Manager (PM)/Engineer. Perform adjustments to the briefing as required by AFNWC/NIA, and when required by NIA perform requested presentation at Hill AFB or other locations per the AFGSC HAC/RMPE CSS – all responses (routine, urgent, and emergency);

d. Maintain the highest possible integrity and fidelity (touch/feel) of the MPT Control Program (MPTCP) with the operational REACT console form/fit/function and other instructor/evaluator supporting software and firmware with special attention to Touch Panel functionality, Audio Buffer performance, and reality simulation of the REACT consoles, etc… - all responses (routine, urgent, and emergency);

e. Prepare and present a design review-level technical briefing (at Hill AFB) to TERB, including test planning and subsequent deliveries. Submit a draft briefing to NIA to support LEVEL II briefings by AFNWC/NIA PM/Engineer 30 days prior to TERB. Perform corrections to the briefing as required by AFNWC/NIA – ROUTINE responses, with higher responses to be notified;

f. Prepare and submit a Test Plan per AFNWC/NI 99-103 and AFNWC 99-101 to NIA as soon as possible/practical, but about 60 days prior to test. Perform corrections to the test plan as required by AFNWC/NIA, AFNWC/NIE and AFNWC/ENT Center Test Authority – ROUTINE response, with higher responses to be notified;

g. Prepare and submit Test Procedures to Government to NIA 30 days prior to testing – ROUTINE responses, with higher responses to be notified;

h. Prepare and present a Test Readiness Review at the contractor facilities 5 days prior to testing, and prepare Minutes with attendees/phone conference – ROUTINE responses, with higher responses to be notified;

i. Conduct testing per Program Schedule. Provide notifications and make accommodation and briefings for Government and other contractors during testing – all responses (routine, urgent, emergency);

j. Prepare and disseminate to all test participants, Government and other contractors a “Quick-Look” report within 24 hours of test completion per AFGSC CSS – all responses (routine, urgent, emergency);

k. Should testing identify defects or test failures, the contractor test organization will conduct a “next-day” brief to the Test Manager (Trainers Program engineer or PM ITT Co-Chair), the ITT Operational User Representative (A3IA) and to all test participants, based on the disseminated “Quick-Look” Report. Government PM ITT Co-Chair will “direct or defer” any resolution to test failures. Should a resolution be presented by the TSSC contractor and

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 22 of 72

approved by the Government or a resolution determined during the briefing and approved by the Government, a draft POA&M will be established and approved by AFNWC/NIA, AFNWC/NIE and AFGSC/A3 at that time (preferable PATH). Otherwise, the resolution will be deferred and subsequently presented by “paper” by the test organization and approved by AFNWC/NIA, AFNWC/NIE and AFGSC/A3 at a subsequent time (alternate PATH).

l. Prepare and submit a Test Report per NI OI 99-103 and deliver 30 days after test to NIANIA. m. Conduct FCA – ROUTINE responses, with higher responses to be notified; n. Participate in PCA, performing corrections as required by NIE – ROUTINE responses, with

higher responses to be notified; o. Participate in TO V&V, performing corrections as required by NIE – ROUTINE responses,

with higher responses to be notified; p. Prepare and deliver configured software and related products (IOSSP contractor support to

TSSC contractor, and TSSC contractor to specified field and Control Center locations). Classified software and related products will be maintained in repository with adequate backup and disaster recovery plans/logistics by the contractor. Deliver classified source and executable code to the Government and to other development teams as directed by Program Manager (PM) – NIA (i.e. ICU-2, IOSSP, SACCS, etc.). AFNWC/NIE Waiver allows the immediate delivery of test products and media after successful test activities. Unclassified software and related products will be delivered to the Government to NIA for transfer to NIES (CM) and then to the Hill AFB 309 Software Control Center – all responses;

1) For ROUTINE responses provide software, database and documentation products 45 days prior to operational HAC/RMPE releases (OPLAN 8010 changes);

2) For URGENT and EMERGENCY responses meet delivery requirements for SW, database and documentation products per AFGSC CSS and as directed by AFNWC/NIA and USSTRATCOM;

3) For all MPT/MEP and APT responses software, database and documentation products will be couriered (delivered by the contractor to their respective deployment sites - 532 TRS - Vandenberg AFB; 341 MW – Malmstrom AFB; 90 MW – FEW AFB; 91 MW – Minot AFB; AFGSC/A3IN – Barksdale AFB);

4) For all responses prepare and provide up to 4 hours of Class 1 training to units at time of delivery as pertaining to changes in the software, databases and documentation.

q. Maintain the classified MPT/MEP source code baseline in repository at secure location capable of housing, accounting, and controlling software at the TS/FRD level. Source and executable code and related documentation shall be made available to the Government on request. Classified repository will ensure adequate backup and disaster recovery procedures/logistics for the source code such that software development/maintenance can resume with minimal delay should a natural or other disaster occur at the primary development location;

r. Prepare and submit a Test Report for approval per AFNWC/NI 99-103 and AFNWC 99-101 to Government (NIA) 30 days following the conclusion of testing. Perform corrections to the report as required by AFNWC/NIA, AFNWC/NIE and AFNWC/ENT Center Test Authority – ROUTINE and URGENT responses. Participate in Government-directed meetings, video teleconferences or phone conferences at: 1) Hill AFB, at 2) HSSF and their contractor

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 23 of 72

support (for IOSSP contractor support & TSSC contractor), IOSSP contractor support (for TSSC contractor) and TSSC contractor (for IOSSP contractor support ) sites as necessary/required, at 3) AFGSC activities at Barksdale AFB, at AFGSC OCB operational and trainer activities, and at 4) other program sites in order to maintain sufficient knowledge and interface regarding trainer contract activities (HAC/RMPE, COP, etc…);

s. Provide management representation and recurring updates to AFGSC OCBs to include cost, schedule, technical and requested presentational materials for MPT/MEP and APT software changes; t. Develop metrics data for system resources, memory allocation, processor utilization (et al) to support software system health assessments (up to 4 per year). Assist NIA in data interpretation; u. In addition to any related requirements above, TSSC contractor will:

1) support IOSSP contractor support testing at IOSSP contractor support facilities and in the FEW MPT or other site as determined by the Government.

2) perform Acceptance Test of any changed HW or SW at TSSC contractor facilities at VAFB or other location determined by Government.

3) perform a System Integration Test (SIT) of any software/firmware changes to the MEP/MPT in the SDME contractor facilities (for the MEP) and in the 532 MPTs (as arranged with AFGSC/A3IA, 532 TRS and Program Office);

4) support MMPU dual baseline integration activities outlined in paragraph 1.4.4.2.3 and 1.4.4.10.1 to include integration of MMPU dual baseline into MPTs IAW GOV determined schedules.

5) develop and maintain a SW and HW support baseline for the SDME and APT/APTE, with baseline products recommended by the contractor and approved by NIA. This baseline would potentially include all commercial and developed SW products used to support the current HW baseline(s), drawings, lab diagrams, TOs, commercial manuals, SW development products (as determined), electrical interfaces, and a lab user manual.

6) Develop a listing of all trainer HW, FW and SW resident in trainer systems. Develop an archive HW, FW and SW suite, with documentation to use, capable of reading, writing and copying all trainer SW and FW data currently being held in 309 SSC (including capability to read and write/burn firmware (FW) associated with trainer systems/assemblies containing unique trainer programming (i.e. as with the IMPSS trainer…)). As an option old media forms may be converted to newer TBD media forms (i.e. TK52 cartridge data to CD media for instance).

7) Further develop (and then maintain) Work Breakdown Structure (WBS) provided partially in Appendix C to the 4th level or deeper, as representative of the contractor work efforts.

1.4.4.10.2 Data Maintenance Requirements – MPT/MEP and APT/APTE

a. Maintain and periodically deliver classified MPT/MEP configuration databases that support simulation of VLF/LF, UHF MILSTAR, EHF MILSTAR, SACDIN (and Advanced EHF

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 24 of 72

Radio Networks after MMPU modification) in accordance with current 20th Air Force Communications and Reporting Directive (CARD);

b. All trainer software/firmware and hardware design and interface control. Assist Maintain and periodically deliver classified MPT/MEP configuration databases that support simulation of Emergency War Orders (EWO) scenario realism (Target Case Generation (TCG), Execution Plan Generation (EPG) in accordance with current Task Force 214 Training Reserve Forces Target List (RFTL).

c. Develop software change candidate lists for MPT/MEP and APT for each periodic software release for approval by AFGSC OCB;

d. Support NIA and NIAD in the role of Subject Matter Expert (SME) for NIA and NIAD in technical exchanges, modification activities with other Government and contractor organizations, boards (requirements Validation Board (RVB), Requirements Screening Panel (RSP) and Operations Control Board (OCB), Technical Interface Meetings and Program Status Meetings with CLS contractor, projects and programs and their related meetings, as directed;

e. Participate in development of operational concepts of employment to ensure MPT/MEP and APT software supports USAF operations training needs, and

f. Act as “Help-Desk” for MPT/MEP, APT, and MMT and other authorized users (on a 5 business-day basis, 8 hours per day, excluding federal holidays) regarding system operations, and software logistics (media maintenance, executable load procedures, copies, backups, problems, etc…), as requested. With each release provide on-site training in general system use (in addition to the software change release training cited above.

1.4.4.10.3 Personnel Requirements – MPT/MEP and APT/APTE

a. Provide TS-cleared and trained personnel in TS/FRD control methods to perform 1)software and hardware engineering, 2) Configuration Management, 3) Quality, 4) TO handling, 5) project management of MPT/MEP change and maintenance activities.

b. MEP and MPT DT&E developers and test conductors shall have depth of knowledge of current EAPs, processes, message formats, etc… to enable personnel to demonstrate that the SW/FW provides 100% fidelity with operational HAC/RMPE and APT performance.

1.4.4.10.4 SW Maintenance Requirements – MMT, P&ECST and B-Plug

The TSSC contractor shall perform the following tasks related to development of software changes: a. Perform change planning including ECP and SCN development, specification and related

design documentation updates, version control documentation, Technical Order update, QA planning and other contractor-determined activities necessary to process, integrate, and test the changed software or the AF Form 1067 changes provided by the NIA Program Manager (PM).

b. Develop and maintain a program schedule and other program tools with cost accounting to support reporting requirements and other related activities prescribed by the main contract. Perform adjustments to the schedule as required by AFNWC/NIA PM.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 25 of 72

c. Prepare and deliver draft Initial ECP briefs to NIA to support LEVEL II Briefings and the Technical Evaluation Review Board (TERB) briefing by NIA Program Manager (PM)/Engineer. Perform adjustments to the briefing as required by AFNWC/NIA, and when required by NIA perform requested presentation at Hill AFB or other locations.

d. Prepare and present a design review-level technical briefing (at Hill AFB) to TERB, including test planning and subsequent deliveries. Submit a draft briefing to NIAA to support LEVEL II briefings by AFNWC/NIA PM/Engineer 30 days prior to TERB. Perform corrections to the briefing as required by AFNWC/NIA PM.

e. Prepare and submit a Test Plan per AFNWC/NI 99-103 and AFNWC 99-101 to NIA as soon as possible/practical and about 60 days prior to testing. Perform corrections to the plan as required by AFNWC/NIA PM.

f. Prepare and submit Test Procedures to Government to NIA 30 days prior to testing. g. Prepare and present a Test Readiness Review at the contractor facilities 5 days prior to testing,

and prepare Minutes with attendees/phone conference. h. Conduct testing per Program Schedule. Provide notifications and make accommodation and

briefings for Government and other contractors during testing. i. Participate in TO V&V, performing corrections as required by NIE. j. Submit a Test Report per NI OI 99-103 30 days after completion of test. k. Conduct FCA – ROUTINE responses, with higher responses to be notified; l. Participate in PCA, performing corrections as required by NIE. m. Prepare and deliver configured software and related products will be delivered to the

Government to NIA for transfer to NIES (CM). n. Prepare and submit a Test Report for approval per AFNWC/NI 99-103 and AFNWC 99-101

to Government (NIA) 30 days following the conclusion of testing. Perform corrections to the report as required by AFNWC/NIA, AFNWC/NIE and AFNWC/ENT Center Test Authority (CTA). Participate in Government-directed meetings, video teleconferences or phone conferences at 1) Hill AFB, at 2) HSSF and their contractor support (for IOSSP contractor support & TSSC contractor), IOSSP contractor support (for TSSC contractor) and TSSC contractor (for IOSSP contractor support) sites as necessary/required, at 3) AFGSC activities at Barksdale AFB, at AFGSC OCB operational and trainer activities, and at 5) other program sites in order to maintain sufficient knowledge and interface regarding trainer contract activities (HAC/RMPE, COP, etc…); Provide management representation and recurring updates to AFGSC OCBs to include cost, schedule, technical and requested presentational materials;

o. Develop metrics data for system resources, memory allocation, processor utilization (et al) to support software system health assessments (up to 4 per year). Assist NIA in data interpretation;

p. TSSC contractor will: • Perform Acceptance Test of any changed hardware at TSSC contractor facilities. • Perform a System Integration Test (SIT) of any software/firmware changes developed at

TSSC contractor facilities in the MEP in the SDME, and in the VAFB MPTs as directed by AFGSC/A3IA in coordination with the 532 TRS and NIA.

r. The P&ECST and the B-Plug CT have embedded processors and related electronics that contain FW. In the case of the P&ECST, the Cummins Diesel Electric Unit (DEU) has a Power

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 26 of 72

Control Computer (PCC) that controls the engine. This PCC is programmable via a laptop computer system which has commercial applications (Insight/Inpower) programs used to “patch” and modify default values, and download FW from Cummins. The Motor Drive Controller (MDC) unit in the B-Plug CT has modified FW which is used to drive the B-Plug up/down action. These systems are currently not configured. The contractor shall capture the baseline firmware, software and documentation associated with the P&ECST (FW, documentation and support laptop systems associated with the DEU PCC) and the B-Plug CT (FW and documentation) associated with the MDC, and subsequently develop such documentation as to complete the baselined system and submit to NIE for initial baselining, as necessary.

1.4.4.10.5 Data Maintenance Requirements – MMT, P&ECST and B-Plug Classroom Trainers

a. Maintain and periodically deliver configuration databases that support the MMT, P&ECST and B-Plug CT.

b. Develop software change candidate lists for MMT, P&ECST and B-Plug CT, and assist the NIA PM in development of AF Form 1067s.

c. Support NIAA and NIAD in the role of Subject Matter Expert (SME) in technical exchanges, modification activities with other Government and contractor organizations, boards (requirements Validation Board (RVB), Requirements Screening Panel (RSP), Control Board, Technical Interface Meetings and Program Status Meetings with CLS contractor, projects and programs and their related meetings, as directed;

1.4.4.10.6 Personnel Requirements – MMT, P&ECST and B-Plug

There are no specific data maintenance requirements for these items at this time.

a. Provide SECRET-cleared and trained personnel to perform 1) software and hardware engineering, 2) Configuration Management, 3) Quality, 4) TO handling, 5) project management of MPT/MEP change and maintenance activities.

b. Developers and test conductors shall have depth of knowledge of requisite systems and processes to enable personnel to demonstrate that the SW/FW provides 100% fidelity with the requisite operational system performance.

1.4.4.10.7 Other Requirements – all maintained systems and assemblies

a. Assist NIAA in maintaining (monitoring, update of) the Information Assurance (IA) PIT certifications (on a yearly basis) for the MPT/MEP, APT/APTE, and MMT (yearly PIT updates and EITDR/eMASS revisions for each).

b. Develop plans, procedures and processes to ensure compliance with Capabilities Maturity Model Index (CMMI) Level 5 in support of TSSC (MPT/MEP, APT/APTE, and SDME systems), and MMT software sustainment activities.

1.4.4.10.8 Time Compliance Technical Orders

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 27 of 72

Assist Government with writing TCTO verbiage regarding CPINS software requiring changes

1.4.4.10.9 Trainer Supply Chain Management

The TSSC systems Trainer’s supply chain is managed through Contractor Logistics support, and is detailed in Trainers CLS task order under GSSC.

1.4.4.10.10 Government Industry Data Exchange Program (GIDEP)

The program office manages these alerts. The contractor shall report any defective and counterfeit (see 1.4.4.10.11) discoveries to the program office.

1.4.4.10.11 Counterfeit Control

The contractor shall employ Counterfeit Control measures to reduce the risk of Counterfeit parts. Measures include but are not limited to: a. Maximizing the use of authentic parts by obtaining them from Original Equipment

Manufacturers (OEM), Original Component Manufacturers (OCM), or authorized distributors.

b. Assessment of vendors/manufacturers. c. Maintain traceability of parts origination and distribution. d. Recommended material control processes (storage, handling, transport) e. Reporting, upon discovery, any suspect or counterfeit parts to the Government for reporting

to the Trusted Systems and Networks (TSN) focal point and to GIDEP. f. Flow of counterfeit prevention provisions to each first-tier supplier and require that supplier

flow the same provisions to all sub-tier suppliers. g. (No Critical Components) h. Levy counterfeit control measures requirements for all subcontractors.

1.4.4.10.12 Data Rights

The Government asserts rights as outlined in Section J of the solicitation, Government Rights in Data (GRID), the individual CDRLs and also in the accompanying contract H-clauses contained within the contract document. The contractor shall ensure subcontracts supporting SW DT&E activities (SW updates, documents, and drawings) contain the assertion of data rights to reflect Section J, GRID.

During the period of performance, the ICBMSD will transition all ICBM Government data into a single electronic repository, the Integrated Data Environment (IDE). Data delivered by the contractor shall be in a format compatible with the new IDE system.

1.4.4.10.13 Information Assurance

The contractor shall support the Government's Program Protection Planning, implementation, and sustainment, and the following:

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 28 of 72

a. provide program protection for the resources and facilities associated with SW maintenance and sustainment activities under this contract.

b. establish and use the appropriate administrative technical and physical safeguards to protect all Government data, to ensure its confidentiality, integrity, and availability.

c. provide for personnel security, information systems security, and physical security as mandated in the National Industrial Security Program Operating Manual (NISPOM) and defined in the applicable DD Form 254, Contract Security Classification Specification.

d. support internal setup and Government approval of classified computer processing, classified document control administration, personnel security clearance administration, processing incoming/outgoing classified and unclassified visits and transmission security, including at subcontractor facilities if required, provide for capital improvements related to security (safes, alarms, entry controls, etc.), security education training, temporary duty to support program protection, cost of transporting classified components and security terminal equipment (STE, computer hardware/software), as well as all security-related installation, operations, and maintenance.

e. assist NIA in the development of Information Assurance documentation for accreditation.

1.4.4.10.14 Risk Management

Risk Management Program and reporting may be required in this SW maintenance/sustainment action, and will be in compliance with AFNWC/NI frameworks.

1.4.4.10.15 Quality Control

In compliance with contract clause 52.246-5 and 52.246-4, “Inspection of Services,” the contractor shall utilize their internal company Quality Control Program considered equivalent or better than ISO 9001, subject to review by the Government, to ensure the requirements of this contract are complied. Quality Control reporting will be presented at the periodic program management reviews held by the contractor at the contractor facility.

1.4.4.10.16 Serialized Control and Reporting

The Trainer computer systems are GFE and are serialized, but are otherwise adequately tracked by the Trainer CLS contract under GSSC.

1.4.4.10.17 Configuration Tracking and Control

The contractor shall report system, subsystem, and component configuration information IAW the drawings and technical data listed in Appendix C. This type reporting shall be presented at the periodic program management reviews scheduled and conducted by the contractor.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 29 of 72

1.4.4.10.18 Configuration Management PlanThe contractor shall use contractor practices and management to handle, store and retrieve any drawings and technical data/drawings supplied by the Program Office through the PCO for configuration management (CM) required in the performance of the contract. Status and condition of this management area will be reported through the periodic PMRs. Deficiencies or conditions in the TSSC which are noted being outside the scope of the contract shall be reported to the Program Office at the periodic PMRs in slides and/or photos with associated simple markups to configured drawings and/or technical data from the contractor CM library. Engineering Change Proposals (ECPs) and SCNs or related management of the engineering baseline is required (i.e. the contractor shall recommend changes to the configuration baseline of the SDME, MEP-MPT and APT/APTE as required). All SW maintenance shall to be conducted by TOs and TSSC procedures when available, or by commercial manuals or contractors best practice as required. The Program Office, via the PCO, will assist the contractor maintaining drawings and TO and related technical data currency.

1.4.4.10.19 Packaging and Marking for Shipment and Storage

The contractor shall pack and mark the major end items IAW the applicable 441 technical order listed in Appendix D and MIL-STD-129, Military Marking for Shipment and 442 Storage, and MIL-STD-130, Identification Marking of U.S. Military Property and Technical 443 Manual 00-25-260, which covers Asset Marking and Tracking Item Unique Identification (IUID) 444 Marking Procedures.

1.4.4.10.20 Hardware Transfer.

If transfer of any hardware is required, un-packing and (on test completion) re-packing will need to occur. Insurance and commercial carrier transportation will need to be secured. Cost is reimbursable through the contract.

1.4.4.10.21 GFP Status Accounting.

The TSSC contractor shall provide an accounting of GFP at the government and TSSC contractor’s facilities in an annual inventory report to the Government as part of the annual inventory report required in the CLS Trainer contract under GSSC.

1.4.4.10.22 Computer Program Identification Number (CPIN)

TSSC operations shall manage a variety of classified and unclassified system and applications SW and test SW and related products. The TSSC shall maintain the classified baseline for the MPT/MEPs. The APT SW and documentation baseline, as well as the software and documentation for maintenance trainers (MMT) is unclassified and is maintained in the 309 Software Control Center (SCC). The contractor shall continue this activity for TSSC development and test systems. As the SW activity begins to include the maintenance trainers (MMT, others) that maintenance trainer SW will be included in these tasks.

1.4.4.10.23 Computer Systems Support

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 30 of 72

The TSSC contractor shall maintain the TSSC systems which are used to perform DT&E for the MPT/MEP and APT/APTE. The SDME, which is contained in a “closed” area, is generally focused on classified MPT/MEP and associated SW revisions (assembly into the new revision MPT/MEP baseline, with related documentation), and the development of test procedures to prove the Block Update revision (prior to formal tests in the MPT). Since activities involving the APT and APTE are unclassified, similar DT&E is conducted outside the closed area in adjacent “open” areas. The APT SW and documentation baseline is maintained in the 309 Software Control Center. Updates to non-MPT/MEP SW configured baselines (APT, MMT, P&ECST and B-Plug CT) shall be delivered to NIE. These baselines are maintained in the 309 SW Control Center (SCC).

1.4.4.10.24 Computer System Operation

The SDME contains operational MEPs, and a REACT simulator used to develop and assemble the MPTCP, and incorporate the MPTCOP into the trainer MPT/MEP SW revision, and then troubleshoot and fix problems. Other VAX 4000/NUVAX development stations are contained in the SDME. The SDME has user manuals, commercial manuals and TOs to conduct operations. The SDME is primarily configured by drawings, but is not detailed in a system specification.

The APT and APTE are VAX-based 4000 systems consisting of development stations and VAX console. The APT is a low-level simulation of the APT that is used for minimal development and display. The APTE is tailored to the newer communications update to the APT. However, complete troubleshooting of the APT SW can only be done in the APT at Offutt AFB. There are user and commercial manuals as well as TOs to conduct operations.

1.4.4.10.25 Data Systems Maintenance

All data and instructor scripts associated with testing of the MPT/MEP and APT/APTE is related to SW baseline/SW block update activities. This data, in some cases, is tailored for the testing (instructor scripts and certain related data), and in other cases is supplied by IOSSP contractor support and TSSC contractor. Test specific data is configured to the SW revision and related tests. At this point no data from the maintenance systems is available or maintained.

1.4.4.10.26 Depot Support Equipment (DSE) Support

No SDME or APT/APTE is maintained outside TSSC. The CLS contractor maintains all TSSC equipment in facilities at Vandenberg.

1.4.4.10.27 Response to Government Requests for Information (GOV-RFI)

The TSSC contractor shall ensure timely and effectively support of program priority realignments, reprioritizations, re-direction of efforts, schedule accelerations, and other shifts in areas of focus on the following priority and response-time at the time of request (with impact statement inputs provided as/if appropriate): 1) high priority – 5 working days, 2) medium priority – 14 working days, and 3) low priority – 30 calendar days. The contractor shall provide

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 31 of 72

the Government “impact statement inputs” in contractor format for proposed program adjustment exercises as appropriate and in contractor format. These drills may include, but are not limited to, budget increases or decreases, reprioritization, schedule accelerations or stretch-outs, priority realignments, redirection of efforts and/or areas of focus. GOV-RFIs will be supplied to the contractor by the government on a suitable RFI form, serialized and tracked by the contractor, and returned to the government Program Office, with the response signed/dated by respective contractor Program Manager. The date signed by the contractor will be the determining date for performance.

1.4.4.10.28 Contractor Routine Reporting.

The contractor shall report program cost in the monthly CSFR cited in para 1.4.4.11.1. Schedule, technical issues, and repair tasks status shall be presented in periodic TIMs/PMRs. Reports of the Minutes of TIMs and PSRs shall be submitted within 10 days of the event in an RROM cited in para 1.4.4.11.1. Reporting of certain technical issues (progress, issues, related schedules and action items/status) may require more-frequent reports which the contractor shall provide to Program Office personnel (PM, engineer, ect…) directly. These increased reports (if unclassified) shall be satisfied using e-mails and provided in contractor format to best effect.

1.4.4.10.29 Workaround Plans.

The contractor shall report workaround recovery plans in contractor format on a time and criticality basis, as agreed with the Program Office, as follows: 1) high criticality – every 5 working days, 2) medium criticality – 14 working days, and 3) low criticality – 30 calendar days.

1.4.4.10.30 Cost-Risk Reporting.

The contractor shall support a once-quarterly cost risk assessment with estimates in contractor format, at the request of the Government.

1.4.4.10.31 Conduct of PMRs/TIMs.

The contractor shall coordinate and facilitate both the annual Technical Interchange Meeting (TIM) and semi-annual Program Support Review Meeting (PSR).These meetings, hosted by AFGSC/A3T/A4B and AETC, allow the trainer community to discuss current and future trainer modifications, scheduling, and issues and to review all operations and maintenance trainers for currency and supportability. The contractor will schedule the TIM / PSR, and assemlbe the agenda and provide hard copies of agenda and charts to all participants in coordination with the SPO. The contractor shall deliver the approved meeting presentation package approximately 2 weeks prior to the meeting date. The contractor shall provide sufficient packages for each conference participant. The contractor shall record and track all meeting action items through completion and provide meeting minutes with updates to the briefing slides approximately 2 week following the meeting.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 32 of 72

1.4.4.10.32 TO Support.

Various Trainer-unique TOs are associated with Trainer SW and operation (for startup/shutdown/abnormal operation), and its use in the MPTs, MEPs and APT. The contractor shall be responsible for any/all these Trainer-unique TOs.

1.4.4.10.33 Corrosion Prevention and Control

The contractor shall prepare and provide a Corrosion Prevention and Control Plan to support acquisition and life cycle management of assigned programs for new or modified equipment or hardware. In general this paragraph refers to the SDME and APT DT&E areas and equipment, insuring that preservation of GFE equipment is maintained.

1.4.4.10.34 Trainer Field Support.

Field support to contractors and Government groups providing APT, MPT/MEP, MPTCOP and MPTCP (HAC/RMPE) SW deliveries related to trainer DT&E will be required on a regular basis, and will include support to TIMs, SW/HW problem resolutions, and other related. All field support activities are subject to approval by the Trainer PM or designated representative.

1.4.4.10.35 Travel

Travel will be required to the following: 1) TIMs (as determined by AFGSC/A3I and A4M – 2X per year for manager plus up to 2 persons for 5 days per instance), and to other bases (1 person up to 4X per year for 5 days per instance) and contractor sites (manager plus 1 person up to 4X per year for 5 days per instance) as necessary to observe delivery SW performance, anomaly resolution and any related demonstration, 2) support HAC/RMPE OCB at Offutt AFB (manager plus 1 person up to 2X per year for 5 days per instance), 3) COP support to Colorado Springs, CO and HAC/RMPE demos to Offutt AFB or Boston area ( manager plus 1 person up to 4X per year for 5 days per instance), 4) HSSF support to Offutt AFB (manager plus 1 person up to 4X per year for 5 days per instance), 5) ALCS support to various organizations at Offutt AFB (manager plus 2 persons up to 4X per year for 5 days per instance), and 6) Miscellaneous support to other base locations as required. All travel is subject to review/approval from PCO and COR.

1.4.4.11 SERVICE SUMMARY

1.4.4.11.1 SUMMARY

The below table are performance standards (metrics) the Government will use for monitoring contractor performance on critical tasks. These metrics are a meaningful measure of contractor performance and conform to commercial standards to the maximum extent practicable. The Government will audit the contractor’s processes to ensure they are in place and will use the data from the contractor inspection reports to assess contractor performance along with contractor information addressing the below measures of performance via a PowerPoint Presentation. In

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 33 of 72

lieu of a PMR/TIM the Government may 1) require electronic submission of the PMR/TIM PowerPoint slides (described above) for Program Office review of contractor performance, or may 2) waive any or all PMRs/TIMs, at Government discretion. Contractor will be notified by the Program Office of PMR/TIM intentions and directions by the Government.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 34 of 72

Performance Objective

Task Order Paragraph

Performance

Method of Surveillance Performance Threshold

1 Basic Services PMR/TIM 100% on-time delivery to users 2 Data Rights PMR/TIM 100% of Government-rights to data provided 3 Information Assurance PMR/TIM 100% compliance with performance paragraphs cited 4 Quality Control PMR/TIM 100% compliance with performance paragraphs cited 5 Configuration Tracking and Control PMR/TIM 100% compliance with performance paragraphs cited 6 Configuration Management (CM) PMR/TIM No more than 2-5 moderate SW and documentation deficiencies (total) no major

deficiencies in each MEP-MPT and APT baselines.

1) CM plan in-place to manage drawings and TOs (and related) as provided by government. 2) Drawing and TOs (and related) under CM and readily available to contractor staff. 3) Classified SW for MEP-MPT baseline up-to-date and available. 4) Unclassified baseline for APT baseline up-to-date and available.

7 CPINS PMR/TIM 100% compliance with performance paragraphs cited 8 Computer Systems Support PMR/TIM 100% compliance with performance paragraphs cited 9 Response to Government RFI PMR/TIM Performance Threshold:

1) 75% high priority RFIs answered in 5 working days or less 2) 90% medium priority RFIs answered in 14 working days or less 3) 90% low priority RFIs answered in 30 calendar days or less

10 Program Management Information PMR/TIM Performance Threshold: 1) All reports, assessments and workaround plans required by cited paragraphs provided as specified 2) All PMRs and TIMs conducted or supported as cited 3) WBS to 4 levels up-to-date

11 Technical Order Support PMR/TIM 100% compliance with performance paragraphs cited 12 Travel Management PMR/TIM 100% compliance with performance paragraphs cited

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 35 of 72

1.4.4.12 GENERAL INFORMATION

1.4.4.12.1 PUBLICATIONS

Publications Compliance. Compliance with all publications, regulations, and operating instructions applicable to the safe, effective and efficient operation is required as it pertains to the procedures for materials expediting, and when the contractor is authorized by the Task Order to accomplish the work specified in the publication, regulation, or operating instructions. The publications prescribe USAF policies, use of materials, procedures, and processes applicable to the work requirements.

The contractor is required to acquire and work to the latest version of the publication. 1.4.5 GOVERNMENT FURNISHED PROPERTY (GFP AND SERVICES)

Equipment in the SDME and APT/APTE, excluding parts and spares maintained under the CLS contract, is the only GFP on the contract, unless otherwise specified in the APT development environment equipment list referenced in this Task Order. Contractor is responsible for accurate and complete property management of GFP/Materiel and shall be required to provide reports of all property in their possession upon GOV request, and at a minimum, annual reporting.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 36 of 72

2.0 APPENDICES

APPENDIX A - ACRONYMS AND ABREVIATIONS LIST

Abbreviation Title

AFNWC Air Force Nuclear Weapons Center

AFGSC Air Force Global Strike Command

ALCS Airborne Launch Control System (E-6B)

APT ALCS Procedure Trainer

APTE APT Equipment

ASU Automatic Switching Unit

ACA Associate Contractor Agreements

B-Plug LF PAH Plug

CT Communications Translator or Classroom Trainer

CDRL Contract Data Requirements List

CPIN Computer Program Identification Number

CMPT Control Monitor Procedures Trainer

CM Configuration Management

CLS Contractor Logistics Support

CMS Contractor Maintenance Support

COP Console Operations Program

CLFA Closed Loop Failure Analysis

CI Communications Integrator

CSS AFGSC Concept of Systems Support

CARD Communications and Reporting Directive

CMMI Capability Maturity Model Index (for SW development)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 37 of 72

COP Console Operations Program

CTA Center Test Authority

DT&E Development, Test and Execution

DEU Diesel Electric Unit

EHF Extremely-High Frequency

ESD Electro-Static Discharge

E-6B Navy aircraft supporting ALCS mission

ECP Engineering Change Proposal

EWO Electronic War Order

EAL Entry Access List

EPG Execution Plan Generation

FRB Failure Review Board

FRD Formerly Restricted Data

FW Firmware

FCA Functional Configuration Audit

GIDEP Government Industry Exchange Program

GSSC Ground Systems Support Contractor

GFP Government Furnished Property

GFE Government Furnished Equipment

GOV Government

HW Computer Hardware

HAC/RMPE Higher Authority Communications/Rapid Message Processing Element

HSSF HAC/RMPE Software Support Facility

ICBM Intercontinental Ballistic Missile

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 38 of 72

ICBMSD ICBM Systems Directorate

IOSSP ICBM Operations Software Sustainment Program

ICU-2 ICBM Crypto Upgrade - 2

ITT Integration Test Team

LOE Level of Effort

LF Low Frequency (MILSTAR) or Launch Facility

MMIII Minuteman III

MEP Minuteman Enhanced Procedure (Trainer)

MPT Missile Procedure Trainer

MMT Minuteman Maintenance Trainer

MPP Missile Power Processor

MMPU Minuteman MEECN Processing Mode

MP Message Processor

MILSTAR Military Strategic and Tactical Relay

MPTCP MPT Control SW Program

MPTCOP Missile Procedures Trainer COP (SW) Program

NDA Non-Disclosure Agreements

NISPOM National Industrial Security Program Operating Manual

OCI Organizational Conflict of Interest

ODC Ozone Depleting Chemicals

OEM Original Equipment Manufacturer (assembly-level)

OCB Operations Control Board

OCM Original Component Manufacturer

PCA Physical Configuration Audit

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 39 of 72

PIT Platform IT

PMR Program Management Review

PAH Personnel Access

PCC Power Control Computer

P&ECST Power and Environmental Control Trainer

PWS Performance Work Statement

PCO Program Contract Officer

POA&M Plan of Action & Milestones

PLCA Pre-Launch Command - A

PLCB Pre-Launch Command - B

P-Data Parameterized Data

QA Quality Assurance

RFTL Reserve Forces Target List

REACT Rapid Execution and Combat Targeting

RSP Re-competition Support Package

RVB Requirements Verification Board

RFI Request for information

SW Computer Software

SACDIN Strategic Air Command Digital Information Network

SPO System (Directorate) Program Office - NIA

SME Subject Matter Expert

SIT System Integration Test

STE Security Telephone Equipment

SCN Software Change Notice

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 40 of 72

TSSC Test Systems Support Center - VAFB

TO Technical Order

TI Translations Integrator

TTATD Training Target and Timing Document

TERB Technical Evaluation Review Board

TS Top Secret

TIM Technical Interface Meeting

TCG Target Case Generation

USSTRATCOM US Strategic Command

UHF Ultra-High Frequency

V&V Validation and Verification

WBS Work Breakdown Structure

WSSR Weapons System Safety Rule

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 41 of 72

APPENDIX B - TECHNICAL ORDERS, MANUALS AND OTHER CURRENT DOCUMENTATION AND SPECIFICATIONS

Number Title

TO 43D2-3-100-1 Operation Instructions Missile Procedures Trainer Training Set, Guided Missile System (U)

TO 21M-LGM30F-1-23 Operation Instructions – Communications & Ancillary Equipment (U)

TO 21M-LGM30G-1-24 Minuteman Weapon System, Operation Instructions, WING I, III, V (U)

TM LGM30-MEP-02 Maintenance Guide Minuteman Enhanced Procedures Trainer (U)

TM LGM30-MPT-02 Maintenance Guide Missile Procedures Trainer (U) AN/GSQ-T87, -T88, -T89, -T90, -T91,-T92, -T93, -T99

TM LGM30-MPT-13 Simulator Certification (U)

TM LGM30-MPT-15 Computer System Operator’s Manual Software Development and Maintenance Environment for REACT Missile Procedures Trainer (U)

FDM 3.0 Force Direction Message (FDM) Catalogue for Version 3.0 (U)

TO 12R2-2A-1632 Intermediate Maintenance Instructions for Control Indicator, Telegraph Modem, Memory Unit, and Electrical Equipment Mounting Base (U)

TCTO 43D2-3-100-xxx Modification to incorporate MMPU modification into the MPT (current)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 42 of 72

AF Form 1067 Modification Proposal (U) AF e-Publishing

AFI 99-103 Capabilities-Based Test and Evaluation (U)

AF e-Publishing

AFMCI 99-103 Test Management (U) AF e-Publishing

AFNWCI 99-101 Nuclear Enterprise Test and Evaluation Management (U)

ICBMSD SharePoint

ICBMSD OI 99-103 Test and Evaluation (U) ICBMSD SharePoint

AFI 91-202 USAF Mishap Prevention Program (U)

AF e-Publishing

AFI 91-203 AF Consolidated Occupational Safety Instruction (U)

AF e-Publishing

AFI 91-204 Investigating and Reporting USAF Mishaps (U)

AF e-Publishing

AFI 91-203 AF Consolidated Occupational Safety Instructions

AF e-Publishing

MIL-STD-498 Software Development and Documentation (U)

AF e-Publishing

DI-NDTI-80566 Test Plan Data Item Description (DID) (U)

AF e-Publishing

AFGSC OCB CSS Air Force Global Strike Command (AFGSC) Operations Control Board (OCB) Concept of Software Support (CSS) for Higher Authority Communication/Rapid Message Processing Element (HAC/RMPE)

Missile Exchange Portal

EAP STRAT Vol 1 Emergency Action Procedures

(USSTRATCOM) Vol 1 (TS) Controlled document available only from originator.

Contact USSTRATCOM/J381

EAP STRAT Vol 2T Emergency Action Procedures (USSTRATCOM) Vol 2,Training (TS)

EAP CJCS Vol 7/7A Emergency Action Procedures, Chairman Joint Chiefs of Staff (CJCS) Vol 7 and 7A (S)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 43 of 72

AFGSC CARD AFGSC Communications and Reporting Directive (S)

90 MW Comm and Launch Reporting Guide (S)

91 MW Comm and Launch Reporting Guide (S)

341 MW Comm and Launch Reporting Guide (S)

Controlled document available only from originator.

Contact 20 AF/A3NK or HQ AFGSC/A3IN

TEAP TF-214 Training Emergency Action Procedures, Task Force 214 (TS)

Training RFTL Training Reserve Forces Target List, TF-214 (TS)

TTATD TF-214 Training Timing and Targeting Document, Task Force 214 (TS)

HIT TF-214 Handbook for ICBM Targeting, TF-214 (S)

AFGSCI 13-5301 Vol 4 Rapid Execution and Combat Targeting (REACT) Emergency War Order (EWO) Training and Evaluation Procedures (S)

MPT PLCA Document MS Excel file contains 20 AF/A3NK directed PLCA numbers effective 1 April 2013 (S/FRD)

Training PLCA Document OPLAN 8010 REV05 EPP/MA

(EMA05F) PLC-A Document (TS) Controlled document available only from originator, 625 STOS/OSK

AFSCI 13-5301 Vol 1 Rapid Execution and Combat Targeting (REACT) Crew Training (U)

AF e-Publishing

AFGSCI 13-5301 Vol 2 Rapid Execution and Combat Targeting (REACT) Crew Standardization/Evaluation (U)

AF e-Publishing

AFGSCI 13-5301 Vol 3 Rapid Execution and Combat Targeting (REACT) Crew Operations (U)

AF e-Publishing

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 44 of 72

“Blue Book” HAC/RMPE Message Specification Matrices for v3.1 (S/FRD)

Controlled document available only from originator. Contact: 520 SMXS/MXDEB

DI-MCCR-80025A Software Requirements Specification (as tailored by REACT SOW) (U)

Missile Exchange Portal

S-133-36002 REACT SRS for the MPTCP (U) Missile Exchange Portal

S-133-30001 Prime Item Development Specification (PIDS) for WSCE of REACT(U)

Missile Exchange Portal

S-133-35000 Prime Item Development Specification for MPT (U)

Missile Exchange Portal

S-133-36000 Software Requirements

Specification, Computer Program Development REACT Console Operations Program (COP) (U)

Missile Exchange Portal

S-133-19240 Operational Ground Program for Minuteman III AM System (Type V) (U)

Missile Exchange Portal

S-133-19291A Computer Program Development Specification for the REACT EPP (U)

Missile Exchange Portal

S-133-19215C Computer Program Development Specification for the REACT Minuteman Operational Targeting Program (MOTP) III (U)

Missile Exchange Portal

S-133-19571 Software Requirements Specification for the Safety Enhanced Reentry Vehicle Operational Ground Program of the Minuteman Guidance Replacement Program (U)

Missile Exchange Portal

S-133-19572 Software Requirements Specification for the Safety Enhanced Reentry Vehicle Operational Flight Program of the Minuteman Guidance Replacement Program (U)

Missile Exchange Portal

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 45 of 72

ESD-RMP-161-00300 Part I, Specification, Computer

Program Development for the REACT Higher Authority Communications/Rapid Message Processing Element (HAC/RMPE) (U)

Missile Exchange Portal

ESD-RMP-162-00300 Interface Requirements Specification for the Message Processing (MP) CSCI 00300 of Higher Authority Communications Integration and Control and Rapid Message Processing Element (HAC/RMPE) - GTE Government Systems Corporation (U)

Missile Exchange Portal

ESD-RMP-162-00400 Interface Requirements Specification for the Communications Integration/Backup (CIB) CSCI 00400 of Higher Authority Communications Integration and Control and Rapid Message Processing Element (HAC/RMPE) - GTE Government Systems Corporation (U)

Missile Exchange Portal

ESD-RMP-162-00500 Interface Requirements Specification for the Transmission Integrator (TI) CSCI 00500 of Higher Authority Communications Integration and Control and Rapid Message Processing Element (HAC/RMPE) - GTE Government Systems Corporation (U)

Missile Exchange Portal

ICD D25-65000 Interface Control - LF Operations Programming and Timing, Boeing/Autonetics (U)

Missile Exchange Portal

ICD C-2117 Interface Control - Launch Facility Operational Support Equipment to Launch Control System Controller to Missile - Programming, Sequencing and Timing, GTE/Boeing/Autonetics (U)

Missile Exchange Portal

RE-2.14 Form B HAC/RMPE (R1) 6 February 1990 (U)

Missile Exchange Portal

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 46 of 72

RE-PT.0 Form B Train Weapon System Personnel (R7) 17 July 1990 (U)

Missile Exchange Portal

28138 Critical Item Development Specification for Control-Indicator, Telegraph Modem, Memory Unit, Electrical Equipment Mounting Base (U)

Missile Excha

ICD 25-R030 Interface Control - Higher

Authority Communications Integration and Control and Rapid Message Processing Element (HAC/RMPE) of the REACT to WSCE Digital Interfaces Programming and Timing/Electrical, GTE/FAC (U)

Missile Exchange Portal

ICD 25-R036 Interface Control - Missile Combat Crew Member to REACT Segment - Human Machine Interface, Lockheed Martin Command & Control Systems (U)

Missile Exchange Portal

ICD 25-R050 Interface Control - REACT WSCE Programs and Databases to Wing Code Processing System, Programming, Sizing and Data Format, Ford Aerospace/AUC/SAC (U)

Missile Exchange Portal

ICD 25-R053 Interface Control - Higher Authority Communications Integration and Control and Rapid Message Processing Element (HAC/RMPE) to AFSATCOM, Programming and Timing/Electrical (REV A), GTE/WRALC/OO-ALC (U)

Missile Exchange Portal

ICD 25-R055 Interface Control - Higher Authority Communications Integration And Control And Rapid Message Processing Element (HAC/RMPE) Of The Rapid Execution And Combat Targeting (REACT) Program To Console, Weapons System Control, OJ-673(V)/GSW – Electrical

Missile Exchange Portal

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 47 of 72

Power/Mechanical/Envelope/Environmental Lockheed Martin/GD-CS (formerly GTE) (U)

ICD 25-R059 Interface Control - Weapon System Control Volume I and II Element Console Components Mechanical, Envelop, Electrical, Environmental, Programming and Timing, Ford Aerospace (U)

Missile Exchange Portal

ICD D25-92853 Interface Control - Higher

Authority Communications Integration and Control and Rapid Message Processing Element (HAC/RMPE) of the Rapid Execution and Combat Targeting (REACT) Program to the Minuteman Minimum Essential Emergency Communications Network (MEECN) Program (MMP) MMP- EHF Terminal (ET) Programming and Timing/Electrical (U)

Missile Exchange Portal

ICD D25-92854 Interface Control - Higher Authority Communications Integration and Control and Rapid Message Processing Element (HAC/RMPE) of the Rapid Execution And Combat Targeting (REACT) Program to the Minuteman Minimum Essential Emergency Communications Network (MEECN) Program (MMP) MMP-VT VLF/LF Terminal Programming and Timing/Electrical (U)

Missile Exchange Portal

ICD D25-92878 Interface Control KS-60 ICBM Cryptographic Equipment to Launch Facility, Wing Code Processing System, Data Management Device, and Simple Key Loader - Electrical, Mechanical, and Programming and Timing Boeing (KS-60 IPT) / Boeing (ICPS IPT) (U)

Missile Exchange Portal

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 48 of 72

EKMS 308 Electronic Key Management

System (EKMS) Data Tagging and Delivery Standard 0N481181 (U)

Missile Exchange Portal

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 49 of 72

APPENDIX C - WORK BREAKDOWN STRUCTURE (WBS)

APPENDIX D - CDRLS

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 50 of 72

APPENDIX E: CLS/CMS TRAINERS TABLES

TABLE 1 - CLS SUPPORTED TRAINERS AND EQUIPMENT

TRAINER SEQ LOCATION S/N SYSTEM

MPT RY FEW AFB WY 72160004 WS-133

MPT RY FEW AFB WY 72220013 WS-133

CMPT (T46) WU FEW AFB WY 74420004 WS-133

CMPT (T47) WU FEW AFB WY 74430004 WS-133

MEP N/A FEW AFB WY 0000101 WS-133

MEP N/A FEW AFBWY 0000104 WS-133

MEP N/A FEW AFB WY 0000111 WS-133

MEP N/A FEW AFB WY 0000115 WS-133

MPT RY MINOT AFB ND 72160001 WS-133

MPT RY MINOT AFB ND 72230009 WS-133

CMPT (T46) WU MINOT AFB ND 74420003 WS-133

CMPT (T47) WU MINOT AFB ND 74430002 WS-133

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 51 of 72

TABLE 1 - CLS SUPPORTED TRAINERS AND EQUIPMENT

TRAINER SEQ LOCATION S/N SYSTEM

MEP N/A MINOT AFB ND 0000102 WS-133

MEP N/A MINOT AFB ND 0000117 WS-133

MEP N/A MINOT AFB ND 0000118 WS-133

MPT RY VAFB CA 72160014 WS-133

MPT RY VAFB CA 72160005 WS-133

MPT RY VAFB CA 72160006 WS-133

MPT RY VAFB CA 73040003 WS-133

MPT RY VAFB CA 73040008 WS-133

*Missile

Maintenance

Trainer (MMT)

QD VAFB CA 72060001 WS-133

*MMT QDIT VAFB CA 0000101 WS-133

CMPT (T46) WU VAFB CA 72180007 WS-133

CMPT (T-46) WU VAFB CA 71020003 WS-133

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 52 of 72

TABLE 1 - CLS SUPPORTED TRAINERS AND EQUIPMENT

TRAINER SEQ LOCATION S/N SYSTEM

CMPT (T47) WU VAFB CA 74420003 WS-133

MEP N/A VAFB CA 0000106 WS-133

MEP N/A VAFB CA 0000107 WS-133

MEP N/A VAFB CA 0000116 WS-133

MEP N/A VAFB CA 0000112 WS-133

MEP N/A VAFB CA 0000113 WS-133

MEP N/A VAFB CA 0000114 WS-133

MM Alarm Set Maint TNR

N/A VAFB CA 74460001 WS-133

Auto Sw & Stby Pwr Ctrl

N/A VAFB CA 72620001 WS-133

MPT RY MAFB MT 72750007 WS-133

MPT RY MAFB MT 73040018 WS-133

CMPT (T46) WU MAFB MT 74420001 WS-133

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 53 of 72

TABLE 1 - CLS SUPPORTED TRAINERS AND EQUIPMENT

TRAINER SEQ LOCATION S/N SYSTEM

CMPT (T47) WU MAFB MT 74430001 WS-133

MEP N/A MAFB MT 0000103 WS-133

MEP N/A MAFB MT 0000110 WS-133

MEP N/A MAFB MT 0000119 WS-133

MEP N/A MAFB MT 0000120 WS-133

APT PH OAFB NE 71420002 WS-118

MEP N/A VAFB CA 0000116 WS-133

MEP N/A VAFB TSSC 0000109 WS-133

MEP N/A Barksdale AFB, LA

0000105 WS-133

*REACT – modified trainer unique equipment only

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 54 of 72

TABLE 2 - CMS SUPPORTED TRAINERS AND EQUIPMENT

TRAINER SEQ DESIGNATOR LOCATION S/N SYSTEM

Auto SW & S/B Control

TB A/3E7U-T11 VAFB 72620001 WS-133

Power & ECS TT A/F37U-T21 VAFB 73050002 WS-133

Power & ECS TT A/F37U-T22 MAFB 73060001 WS-133

Power & ECS TT A/F37U-T23 Minot AFB 73080001 WS-133

Power & ECS TT A/F37U-T24 FEW AFB 73090001 WS-133

LCC Maint

Battery

N/A A/F37V-T1 VAFB 0000001 WS-133

LF Maint Battery

N/A A/F37V-T2 VAFB 0000001 WS-133

Accelerated

Secondary

Door Classroom Trainer (ASDCT) (B-Plug)

N/A A/F37P-6 VAFB 0000001 WS-133

Accelerated N/A A/F37P-6 MAFB (T-9) 0000002 WS-133

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 55 of 72

TABLE 2 - CMS SUPPORTED TRAINERS AND EQUIPMENT

TRAINER SEQ DESIGNATOR LOCATION S/N SYSTEM

Secondary

Door Classroom Trainer (ASDCT) (B-Plug)

Alarm Set Maint

ST AN/FSM-T1 VAFB 74460001 WS-133

TLF T12 AN/GSQ-T12 VAFB 72660001 WS-133

TLF T13 AN/GSQ-T13 FEW AFB 72670001 WS-133

TLF T10 AN/GSQ-T10 MINOT AFB 72640001 WS-133

TLF T9 AN/GSQ-T9 MAFB 72550001 WS-133

TLF T41 AN/GSQ-T41 MAFB 72330001 WS-133

*MMT QD AN/GSQ-T4 VAFB 72060001 WS-133

*MMT QDIT A/F37A-T109 VAFB 0000101 WS-133

Code Change Verifier

GQ SM-876/G VAFB 72080001 WS-133A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 56 of 72

TABLE 2 - CMS SUPPORTED TRAINERS AND EQUIPMENT

TRAINER SEQ DESIGNATOR LOCATION S/N SYSTEM

Code Change Verifier

GQ SM-876/G MAFB 72080005 WS-133A

Code Change Verifier

GQ SM-876/G Minot, AFB 72080006 WS-133A

Code Change Verifier

GQ SM-876/G FEW AFB 72080007 WS-133A

*Weapon System hardware only

** The T-9 trainer will not be maintained until the modification is complete (estimated January 2021) and the B-Plug trainer removed from T-9 will be maintained as a stand-alone trainer until it is re-installed in T-9.

TBL 2 EQUIPMENT DESIGNATOR LOCATION QUANTITY

Telephone Test Set VAFB CA 2

Connector Adapter Set AN/GSM-85 VAFB CA 2

Liquid Cooler Test Set VAFB CA 2

Cable Set VAFB CA 2

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 57 of 72

TBL 2 EQUIPMENT DESIGNATOR LOCATION QUANTITY

Fault Locating Indicator ID-2288 VAFB CA 1

Magnetic Tape Transport CTU VAFB CA 3

Electrical Power Test Set AN/GSM-42 VAFB CA 2

Alarm Set, Test Set AN/GSM-319(V)2 VAFB CA 2

Gulton Micro-Printer 20 VAFB CA 1

Cable Set SE-213A VAFB CA 1

Electro-Mechanical Actuator VAFB CA 1

Secondary Door, Launcher, Personal

VAFB CA 2

Secondary Door, Launcher, Personal

MAFB 1

Secondary Door, Launcher, Personal

MINOT AFB 1

Secondary Door, Launcher, Personal

FEW AFB 1

Wing I MAF DEU MAFB 1

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 58 of 72

TBL 2 EQUIPMENT DESIGNATOR LOCATION QUANTITY

Work Station (NIDA) VAFB CA 14

Training Aid (NIDA) VAFB CA 14

Command Signals Decoder Training

VAFB CA 1

Reentry System Trainer UA VAFB CA 1

Reentry System Trainer UA MAFB 2

Reentry System Trainer UA MINOT AFB 1

Reentry System Trainer UA FEW AFB 1

Upper Umbilical Trainer VAFB CA 1

Security Pit Vault Door VAFB CA 3

Leak Test Fixture VAFB CA 1

Test Set Adapter 4935-01-2181917AH

VAFB CA 2

Safing Pin Wrench Assembly VAFB CA 3

Compressed Gas Cyl Valve VAFB CA 1

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 59 of 72

TBL 2 EQUIPMENT DESIGNATOR LOCATION QUANTITY

Cable Set (W-1-W-10) 615000-516-8445AH

VAFB CA 2

Chain Hoist VAFB CA 2

Safe and Arm Pin Container VAFB CA 2

AVE Protector Cover VAFB CA 1

Upper Cable Grip Assy VAFB CA 2

Umbilical Skirt VAFB CA 1

Missile Guidance System (MGS)

6920-00-483-0854 VAFB CA 1

Missile Guidance System (MGS)

6920-00-483-0854 MAFB 2

Missile Guidance System (MGS)

6920-00-483-0854 MINOT AFB 1

Missile Guidance System (MGS)

6920-00-483-0854 FEW AFB 1

Guided Missile PSRE 6920-00-236-4773 VAFB CA 1

Guided Missile PSRE 6920-00-236-4773 MAFB 2

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 60 of 72

TBL 2 EQUIPMENT DESIGNATOR LOCATION QUANTITY

Guided Missile PSRE 6920-00-236-4773 MINOT AFB 1

Guided Missile PSRE 6920-00-236-4773 FEW AFB 1

TBL 2 TRAINER AIDS

Basic Hydraulic Trainer VAFB CA 1

Relief Valve Trainer, 2/4 Port VAFB CA 1

4-Port Solenoid Selector Valve VAFB CA 1

Corrosion Identification VAFB CA 1

Minuteman Power Processor VAFB CA 5

Float Switch Trainer VAFB CA 1

Diesel Cut-a-Way VAFB CA 1

Minuteman Power Verification Box

VAFB CA 2

Power System Verification Box

VAFB CA 3

Multimeter Trainer VAFB CA 25

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 61 of 72

TBL 2 EQUIPMENT DESIGNATOR LOCATION QUANTITY

Refrigerant Trainer VAFB CA 3

ESD Trainer VAFB CA 1

Transporter/Erector Pylons VAFB CA 2

Mate/DeMate Trainer VAFB CA 1

Tool Applicator VAFB CA 19

Upper Umbilical Trainer VAFB CA 1

Safety Wire/Tool Application Trainers

VAFB CA 6

PAH Ladder Trainer VAFB CA 1

3rd Stage Mate/DeMate

Trainer

VAFB CA 1

Tub Trainers (Sump pump trainers)

Class 3 Trainers

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 62 of 72

TABLE 3 - CLS/CMS MAINTENANCE RESPONSE REQUIREMENTS

TRAINER TYPE HOURS X DAYS LOCATION RESPONSE

RY - MPT 18 hr min (Mon-Fri) * 8(Sat) VAFB CA 15 mins

QD - MMT 12 hr min (Mon-Fri) * 8(Sat) VAFB CA 2 hrs

QDIT – MMT 12 hr min (Mon-Fri) * 8(Sat) VAFB CA 2 hrs

WU - CMPT 12 hr min (Mon-Fri) * 8(Sat) VAFB CA 2 hrs

TT - PWR/ECS 12 hr min (Mon-Fri) * 8(Sat) VAFB CA 2 hrs

TT - PWR/ECS 12 hr min (Mon-Fri) MAFB MT 2 hrs

TT - PWR/ECS 12 hr min (Mon-Fri) MINOT AFB ND 2 hrs

TT - PWR/ECS 12 hr min (Mon-Fri) FEW AFB WY 2 hrs

ALARM SET Maint Trainer

12 hr min (Mon-Fri) * 8(Sat) VAFB CA 2 hrs

LCC BATTERY TNR

12 hr min (Mon-Fri) * 8(Sat) VAFB CA 2 hrs

LF BATTERY TNR

12 hr min (Mon-Fri) *8(Sat) VAFB CA 2 hrs

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 63 of 72

TABLE 3 - CLS/CMS MAINTENANCE RESPONSE REQUIREMENTS

TRAINER TYPE HOURS X DAYS LOCATION RESPONSE

TB - SW/SB 12 hr min (Mon-Fri) * 8(Sat) VAFB CA 2 hrs

T12 - TLF (LF-08) 12 hr min (Mon-Fri) * 8(Sat) VAFB CA 4 hrs

MEP 12 hr min (Mon-Fri) * 8(Sat) VAFB CA 24 hrs

T9 – TLF 12 hr min (Mon-Fri) MAFB MT 2 hrs

T10 - TLF 12 hr min (Mon-Fri) MINOT AFB ND 2 hrs

T13 – TLF 12 hr min (Mon-Fri) FEW AFB WY 2 hrs

T41 - TLF 12 hr min (Mon-Fri) MAFB MT 2 hrs

RY - MPT 18 hr min (Mon-Fri) 8 (Sat) FEW AFB WY 15 mins

WU - CMPT 12 hr min (Mon-Fri) FEW AFB WY 2 hrs

MEP 12 hr min (Mon-Fri) 8(Sat) FEW AFB WY 24 hrs

PH - APT 9 (Mon-Fri) OAFB NE 2 hrs

RY - MPT 18 hr min (Mon-Fri) 8 (Sat) MAFB MT 15 mins

WU - CMPT 12 hr min (Mon-Fri) MAFB MT 2 hrs

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 64 of 72

TABLE 3 - CLS/CMS MAINTENANCE RESPONSE REQUIREMENTS

TRAINER TYPE HOURS X DAYS LOCATION RESPONSE

MEP 12 hr min (Mon-Fri) 8 (Sat) MAFB MT 24 hrs

RY-MPT 18 hr min (Mon-Fri) 8 (Sat) MAFB ND 15 mins

WU-CMPT 12 hr min (Mon-Fri) MAFB ND 2 hrs

MEP 12 hr min (Mon-Fri) 8 (Sat) MAFB ND 24 hrs

MEP No scheduled support BAFB LA **

*Saturday at VAFB will be covered with overtime on an as needed basis with a maximum of 2 per month.

**Support to the MEP at AFGSC is on an “as staffing at FEW permits” basis. All other scheduled periodic maintenance for this trainer is waived.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 65 of 72

TABLE 4 – GOVERNMENT WEAPONS SYSTEM CONTROLLED ITEMS – GOVERNMENT DEPOT MAINTENANCE RESPONSIBILITIES

PART NUMBER DESCRIPTION

108620-101 ALCC Printer

8502426-901 Camp Visual Display Unit (VDU)

02-1345185 Keyboard Input Device

10-03110-03 Multi-Function Keypad

C007940 –(1) Keyboard, data entry KY-995/GSW (ARF013,ARF053)

C003311-01 Alarm Reset Switch Assembly (Master Alarm Reset(ARF011, ARF051))

C004153-01 Cooperative Launch Switch Simulator, COOP Launch (ARF007, ARF047, ARF054) (Switch Assembly, COOP Launch)

C004175-01 Headset (Headset, Operator)

C003921-01 Secure Storage Enclosure

C005980-01 Time of Day Clock (ARF023)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 66 of 72

TABLE 4 – GOVERNMENT WEAPONS SYSTEM CONTROLLED ITEMS – GOVERNMENT DEPOT MAINTENANCE RESPONSIBILITIES

PART NUMBER DESCRIPTION

25-79445-3

Operator Seat (Seat Assembly, Operator)

1B1520-1Z Carriage Assembly

25-79416-1 Track Assembly, Lateral

MAE85188-1 Oxygen Regeneration Unit (ORU)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 67 of 72

TABLE 5 – LOCAL UNIT MAINTENANCE RESPONSIBILITIES

PART NUMBER DESCRIPTION

Security Pit Vault Door Drill Out (A-Pit)

Hand driven linear actuator (repair)

Launcher Closure Door and subsystems (in place work)

Shock Isolation System

Umbilical Maintenance

LF Battery (R&R)

LF Motor Generator (R&R)

Multiplying Linkage (R&R)

Environmental Control System (R&R)

Ballistic Gas Generator (R&R)

Diesel Engine (R&R)

B-Plug/Support Equipment (R&R)

Electro-Mechanical Actuator (R&R)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 68 of 72

Lock Pin

Any task requiring a crane

Major corrosion control requiring more than resurfacing and painting

Launch Facility Trainer Bulb Seal replacement

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 69 of 72

TABLE 6 – LFT Maintenance Support Equipment Government Responsibilities

PART NUMBER DESCRIPTION (P) = Proof load

Blue Gear Maintenance

Personal Access Hatch (PAH) Hoist (P)

Explosive Set Circuitry Test Sets (New-Elab Checkout)

Guidance & Control (G&C) Chiller Test Sets (Periodics)

Jib Hoist (P)

Maintenance Van (M-Van) Hoist (P)

Misc. Chain Hoist (P)

Misc. Slings (P)

Multiple Leg Slings (P)

Portable Hoists (P)

Payload Transporter III (Hoists, ECS, Auxiliary Power Unit, Security System) (P/Periodics/PREL)

Purge Manifold

Re-entry System (R/S) Handling Fixture (P)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 70 of 72

R/S Maintenance (Limited Support Through Munitions)

Umbilical Cable Hoist Support (P)

Guided Missile Maintenance Platform (GMMP) Slings (P)

GMMP (P/periodics)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 71 of 72

TABLE 7 – LFT Depot Level Support Government Responsibilities

PART NUMBER DESCRIPTION (NDI = Non Destruct Inspection)

B-Plug (R&R)

EMA (R&R)

Launcher Closure and Subsystems (Major Repair)

PAH Door (R&R)

Emergency Drive Shaft (NDI)

Umbilical Cable Hoist Supports (NDI)

GMMP (NDI)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 5 TRAINERS – GSSC 2.0

Page 72 of 72

TABLE 8 – LFT Depot Real Property Site Maintenance Government Responsibilities (Base CES)

PART NUMBER DESCRIPTION (NDI = Non Destruct Inspection)

Commercial Power to Site

Launch Facility Trainer perimeter Fence

Pavement/Grounds

Portable Toilets

Topside Site Lights

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 1 of 14

ATTACHMENT 6

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

GROUND MINUTEMAN AUTOMATIC TEST STATION (GMATS)

TASK ORDER UNDER THE

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 2 of 14

Attachment 6 ................................................................................................................................... 3

1.0 GMATS PWS ........................................................................................................................... 3

1.1 Scope ..................................................................................................................................... 3

1.2 Purpose .................................................................................................................................. 3

1.3 Background ........................................................................................................................... 3

1.4 Requirements Summary ........................................................................................................ 3

1.4.1 Contractor Logistics Support (CLS) .................................................................................. 3

1.4.1.1 Ground Minuteman Automatic Test System (GMATS) ............................................. 3

1.5 Services Summary ................................................................................................................ 9

2.0 Appendices .............................................................................................................................. 10

APPENDIX A: ACRONYMS AND ABBREVIATIONS ....................................................... 10

APPENDIX B: WORK BREAKDOWN STRUCTURE ......................................................... 11

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION ............ 12

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ....................................................................................................................... 13

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................. 14

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 3 of 14

Attachment 6 GMATS PWS

ATTACHMENT 6

1.0 GMATS PWS

1.1 SCOPE

Reference Section 1.1 of Basic PWS.

1.2 PURPOSE

Reference Section 1.2 of Basic PWS.

1.3 BACKGROUND

Reference Section 1.3 of Basic PWS.

1.4 REQUIREMENTS SUMMARY

1.4.1 CONTRACTOR LOGISTICS SUPPORT (CLS)

1.4.1.1 Ground Minuteman Automatic Test System (GMATS)

1.4.1.1.1 The contractor shall perform logistic and maintenance support for the Minuteman (MM) ICBM GMATS. The GMATS includes automatic test equipment (ATE) hardware, the control and support software (CSS), and the Consolidated Support Activity Group-Supply (CSAG-Supply) Test Program Sets (TPS).

1.4.1.1.2 During normally scheduled support hours, the contractor shall be available to provide support for all GMATS equipment for the following locations:

• Hill AFB, UT • Malmstrom AFB MT • Minot AFB ND • FE Warren AFB WY • 576th Flight Test Squadron, Vandenberg AFB CA • 532d Training Squadron, Vandenberg AFB CA • Offutt AFB NE

1.4.1.1.3 Maintenance Response Time. The contractor shall adhere to the following maintenance response requirements:

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 4 of 14

Current CLS Maintenance Response Requirements

USER TYPE RESPONSE

1 Station NMC 2+ Stations NMC

Malmstrom AFB, Minot AFB, FE Warren AFB, Vandenberg AFB, and Offutt AFB

1 business day 2 Hours

Hill/Depot repair user 2 business days 1 business day

1.4.1.1.4 The contractor shall provide support for organizational and depot-level (D-Level) maintenance identified in TOs 33D7-50-2753-2, 33D7-50-2753-13, 33D7-50-2754-3, and 33D9-61-117-3.

1.4.1.1.5 The contractor shall provide all maintenance for the GMATS equipment located at the following locations:

• Malmstrom AFB, WY • Minot AFB, ND • FE Warren AFB, WY • Vandenberg AFB, CA • Offutt AFB, NE • Hill AFB, UT

1.4.1.1.6 The contractor shall provide supply support and report shortages which involves the activities necessary to have spares available at Intermediate-Level (I-Level) user’s location when needed to maintain and operate installed equipment. Supply support consists of the actions, procedures, and techniques necessary to acquire, receive, store, and transfer repair parts and consumable supplies.

1.4.1.1.7 The contractor shall maintain a spares kit at Wing, 576th Flight Test Squadron, and Offutt AFB user locations. When a spare is used from the spares kit, the contractor shall ship a replacement from the central spares location at Hill AFB. The user will sign a hand receipt for the spares kit and will notify the CLS contractor of any and all parts used by part number and serial number.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 5 of 14

1.4.1.1.8 The contractor shall provide access to spares equipment in the GMATS line replaceable unit (LRU) storage lockers to user technicians required to perform authorized maintenance.

1.4.1.1.9 The contractor shall provide training to all technicians and GMATS users at Wing, 576th Flight Test Squadron, and Offutt AFB user locations. This training is considered Type I training which is conducted five times per year (one time per base) with class size of 8 personnel.

1.4.1.1.10 The contractor shall provide D-level maintenance and logistics support of all GMATS LRU spares.

1.4.1.1.11 Intermediate Level (I-Level) Maintenance Support. The contractor shall provide a contact number to each unit. When contacting the contractor, the user will provide a detailed description of the system malfunction and the maintenance actions, including any LRUs removed and replaced by serial number. The contractor shall then take the actions necessary to return the system to fully operational status as quickly as possible.

1.4.1.1.12 Depot-Level (D-Level) Maintenance. The contractor shall provide special tools or test equipment necessary to support depot level activities per TO 33D7-50-2753-2, 33D7-50-2754-3, and 33D9-61-117-3, such as the Power Distribution Unit (PDU) lift. The contractor shall be able to utilize Military Standard Requisitioning and Issue Procedures (MILSTRIP) to acquire parts available only from the Government.

1.4.1.1.13 System Administration. The contractor shall be assigned system administrator access to Teradyne’s Test Studio at all sites to perform software preventative maintenance, disk backup/restoration and defragmentation, virus scan, and user account and file management as required. The Government will have primary system administration responsibility. Test Studio software updates shall be accomplished by the contractor.

1.4.1.1.14 Line Replaceable Unit (LRU) Repair. When a test station LRU has failed, the contractor shall perform the repair or shall ship the LRU to the appropriate original equipment manufacturer (OEM) or third party for repair, returning the item to the spares kit when repairs are complete. The contractor shall maintain reparable spares at 100% serviceable.

1.4.1.1.15 Line Replaceable Unit (LRU) Functionality. The contractor shall ensure any vendor-repaired LRUs received that deviate from established configuration (e.g., firmware) be checked “in-system” to ensure compatibility prior to use for operational testing.

1.4.1.1.16 The contractor shall perform and document maintenance activities (as described above) to include requirements analysis, product requirements development and management, qualification testing, and support to system integration test.

1.4.1.1.17 GMATS Configuration Management. The contractor shall maintain the configuration of the GMATS equipment per the base configuration drawing (Boeing drawing number 25-93588) and all data assembled there under. Configuration of each individual GMATS equipment

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 6 of 14

item shall be maintained to include the serial numbers where available, and where applicable, the firmware revisions installed within the equipment.

1.4.1.1.18 Metrics. For the AN/GSM-315A Electronic Equipment Test Station, the contractor shall collect and report metrics to include mean time to repair (MTTR), mean time between failures (MTBF), and inherent availability (Ai).

1.4.1.1.19 Mean Time to Repair (MTTR). The contractor shall calculate the D-level maintenance support MTTR. MTTR shall be defined as the mean time required to return a GMATS test station to operation from the time the contractor is on-site until it is returned to the customer as fully serviceable. The time necessary to acquire parts not on hand will be reported but will not be included in the MTTR calculations.

1.4.1.1.20 Inherent Availability (Ai). IA is the inherent test station reliability, excluding considerations for logistics support functions. The GMATS Test Station IA calculation formula to be used is as follows:

Ai =MTBF

MTBF + MTTR

1.4.1.1.21 Where: MTBF = Mean Time Between Failures. MTBF shall be defined as the mean elapsed time from the time the test station was returned to the user as serviceable following a repair action until the contractor is notified that the test station is down. MTTR = Mean Time To Repair. MTTR shall be defined as the mean time elapsed for the contractor to restore the test station back to full mission capable (FMC) status after being notified of a failure. Time shall be defined as all available hours during which GMATS users could possibly utilize the test stand at each respective operating location during normal duty hours.

If disagreement exists between the contractor and the Program Manager on the computation of availability, impaired mission hours, complete details of the malfunction(s), scheduled activities, facility conditions, and any other factors affecting non-availability it shall be documented by the contractor and the Program Manager, and forwarded to the ACO as an attachment to the contractors next monthly billing. The ACO is the final decision authority in areas of availability disagreement.

Non-chargeable lost time is that portion of lost time for which the contractor is not held responsible and should not be reflected in MTBF and/or MTTR calculations. Non-chargeable lost time exists under the following conditions:

a. Facility power outage, when not caused by contractor negligence.

b. Fire or other facility problems, when not caused by contractor negligence.

c. Negligence on the part of Government personnel.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 7 of 14

d. Natural disaster (e.g., flood, windstorm) or inclement weather (determined by the PO or representative).

e. Criminal acts by persons not employed by the contractor.

f. Time lost as a result of test station damage incurred during a weather warning period after:

(1) Receipt of a severe weather warning issued by the local base weather office or Command Post, and

(2) Notification of the test station operator, and

(3) Continued Government operation of the test station after recommendation by the contractor to discontinue trainer operations.

g. Time to conduct semi-annual calibrations.

h. Time to complete GMATS modifications or TCTOs.

1.4.1.1.22 The contractor shall maintain a 95% inherent availability rate and calculate the rate for each GMATS operating location. At Hill AFB, for example, the rate shall be calculated separately for each user operating location such as the SMIC, Bay L, 309th Software Sustainment, and 309th Tech Refresh workload. For bases/user locations with more than one test stand, a 97% inherent availability rate of at least one FMC test stand shall be maintained. The contractor shall provide a quarterly status report to the government detailing MTBF downtime, failure root causes, and corrective actions taken. If two test stands are NMC or PMC for the same issue for more than a week, the contractor shall notify the government and should make arrangements to send a more experienced technician from another base if warranted at no additional cost to the government.

1.4.1.1.23 Computer Control Software (CCS) Sustainment Support. The contractor shall maintain the capability to adapt, correct, perfect, update or replace the CSS as defects, anomalies, or enhancements are identified. The contractor shall also provide the necessary labor and expertise to implement mitigations of software/hardware/COTS obsolescence issues as determined by the government. The government shall only provide additional funding for the hardware necessary to execute tech refreshes and obsolescence mitigation efforts. The contractor shall also support software updates/migrations as required by government Information Assurance/Cyber agencies and guidance.

1.4.1.1.24 Consolidated Sustainment Activity Group (CSAG)-Supply Sustainment Support. The contractor shall be able to repair GMATS assets transitioned to and/or residing in the CSAG.

1.4.1.1.25 GMATS-Related Support Equipment. The contractor shall maintain and repair all test and support equipment used to maintain GMATS test equipment. This shall include contractor-owned equipment, GFP (e.g., special wiring repair tools, Drive in Theater Movie Company (DIT-MCO) Wiring Analyzer, etc.), or any contractor-owned equipment provided for long-term

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 8 of 14

CLS maintenance of GMATS. The contractor shall maintain a master inventory and conduct inventories annually, verify asset serviceability status quarterly, and provide a copy of the inventory to the government.

1.4.1.1.26 The contractor shall participate in regular status meetings with the Government, as requested by the Government, to plan and schedule assigned tasks. During these sessions, the contractor shall identify dates, determine revised forecast dates, task duration, identify predecessor and successor changes, map resources to tasks, document resource loading, and discuss other cost and schedule issues, as required.

1.4.1.1.27 The contractor shall provide all needed office supplies and electronic equipment necessary for CLS personnel to complete their daily duties. This includes commercial access phones and computers.

1.4.1.1.28 The contractor shall maintain an accurate spares listing and perform failure trend analysis for the life of the contract. The historical failure trend data shall be delivered to the government at the completion of the contract. The listing shall also keep an updated status on items sent to OEM for repair. The spares listing shall also include information on what extent the OEM or other repair vendor can repair each asset and how long it will be available. The contractor shall update the spares listing at least quarterly, actively send in components to the OEM for repair, and notify the government if assets can no longer be repaired. At least semi-annually, the contractor shall meet with the government and recommend components for obsolescence mitigation. The contractor should then use this information to plan and execute regular tech refresh phases for obsolete components to address failure trends ahead of time as required by paragraph 1.6.4.1.13.1.23. The contractor shall quote and provide funding forecasts for hardware two years in advance to keep in line with government funding cycles.

1.4.1.1.29 The contractor shall maintain proficiency in HUNTRON operations to facilitate card level-repairs, including troubleshooting circuit cards and providing troubleshooting reports. The contractor shall allow for utilizing the HUNTRON for other ICBM workloads that have circuit card reapair needs.

1.4.1.1.30 Modification Installation. The contractor shall install Government-approved modification kit after Air Force acceptance of the kit proof or trial installation, when directed by the applicable contracting authority. If the installation of a modification kit results in additional costs to the contractor, the contractor shall submit a cost proposal in writing to the applicable contracting authority for approval prior to installation.

1.4.1.1.31 The contractor shall provide transportation for all CLS personnel that require it to fulfill their daily duties. This includes providing gasoline and all maintenance (e.g. oil, tires, washes, etc.).

1.4.1.1.32 The contractor shall, on a yearly basis, review the log files for all GMATS test stands and verify that the latest CPINs are loaded and match the ACPIN system. If there are discrepancies, the contractor shall upload the most current CPINs.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 9 of 14

1.4.1.1.33 The contractor shall, on a quarterly basis, conduct pin depth checks on the Virginia Panel panel using the COTS manual from Virginia Panel and appropriate depth gauges. Pins found to be out-of-tolerance shall be corrected IAW the COTS manual as a preventative measure to prevent connectivity issues. The contractor shall also, on a semi-annual basis, verify the firmware version on all GMATS COTS components and maintain a configuration baseline. The contractor shall correct any firmware versions that deviate from the baseline.

1.4.1.1.34 The contractor shall organize and support technical interchange meetings (TIM) with all GMATS users as directed by the government. The contractor shall establish the agenda, send invites, secure travel for CLS personnel, reserve meeting locations, run the briefings, capture action items, and capture meeting minutes. The TIMs can be run in conjunction with Trainer’s regular TIMs if similar CLS personnel are

1.5 SERVICES SUMMARY

Reference GSSC 2.0 Basic PWS section 1.7 for details.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 10 of 14

2.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 11 of 14

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 12 of 14

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 13 of 14

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 6 GMATS – GSSC 2.0

Page 14 of 14

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

ATTACHMENT 7

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

STRATEGIC AUTOMATED COMMAND CONTROL SYSTEM (SACCS)

PERFORMANCE WORK STATEMENT (PWS)

TASK ORDER UNDER THE

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 2 of 24

TABLE OF CONTENTS

1.0 SACCS ............................................................................................................................. 3

1.1. SCOPE ............................................................................................................................. 3

1.2. PURPOSE ........................................................................................................................ 3

1.3. BACKGROUND ............................................................................................................. 3

1.4. APPLICABLE SYSTEM(S) ........................................................................................... 4

2.0 – STRATEGIC AUTOMATED COMMAND CONTROL SYSTEM (SACCS) ................ 5

3.0 – SERVICES SUMMARY ..................................................................................................... 11

3.1. SERVICES SUMMARY .............................................................................................. 11

Table 1: Services Summary Matrix............................................................................................. 11

4.0 – GENERAL INFORMATION ............................................................................................. 13

4.1. CONTRACTING OFFICER REPRESENTATIVE (COR) ..................................... 13

5.0 APPENDICES ......................................................................................................................... 14

APPENDIX A: ACRONYMS AND ABBREVIATIONS ........................................................................ 14

APPENDIX B: WORK BREAKDOWN STRUCTURE ......................................................................... 15

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION ........................ 16

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ..................................................................................................................................... 17

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) ................................................. 18

APPENDIX E: APPLICABLE DOCUMENTS ......................................................................... 19

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 3 of 24

1.0 SACCS

1.1. SCOPE This Performance Work Statement (PWS) describes the services the Ground Subsystems Support Contract (GSSC) contractor must provide to ensure Strategic Automated Command Control System (SACCS) remains operational to meet warfighter requirements. This PWS specifically addresses GSSC requirements to support all SACCS related sustainment efforts. All other requirements listed in the Intercontinental Ballistic Missile (ICBM) Ground Subsystems Support Contract (GSSC) Performance Work Statement (PWS) remain in full effect and must be adhered to. Unless otherwise specified, “Government” refers specifically to the Intercontinental Ballistic Missile Systems Directorate (ICBMSD). Some sustainment efforts will have separate Contract Line Item Numbers (CLIN) and separate Statements of Objectives (SOO) as part of the Request for Proposal (RFP). The nature of sustainment will necessitate new requirement generation for future efforts; the Government will retain the option of assigning them to the GSSC contractor, or openly competing them if it is determined to be in the best interest of the Government. Any future efforts against GSSC will be added as a contract modification, using a separate CLIN and SOO/Statement of Work (SOW).

1.2. PURPOSE The purpose of the GSSC is to provide SACCS sustainment support, engineering services, and emergency response that adheres to defined requirements specified in this PWS. This PWS identifies contract effort and products necessary to perform required support in operational and sustainment activities, encompassing areas such as analyses; system and subsystem evaluation; technical advice and assistance; risk management and mitigation; equipment reviews; Acquisition Category (ACAT) III, and non-ACAT acquisitions; and training in support of sustainment of the SACCS Weapon System (WS). The use of “contractor” hereafter refers to the GSSC contractor. All references to other contractors will be specifically stated (e.g., Integration Support Contract (ISC) contractor and other subsystem contractors, etc.).

1.3. BACKGROUND

SACCS is a mature weapon system currently in the Operations and Support Phase of its life cycle. General system performance parameters that reflect the suitability (degree of readiness to perform the mission) for the SACCS weapon system (WS) are availability, reliability, maintainability, compatibility, transportability, usage, human factors, manpower, logistics supportability, environmental effects and impacts, training, sources of supply and maintenance, and critical manufacturing processes. Effectiveness is defined as degree of mission accomplishment and is defined by the key performance parameters of availability, reliability, accuracy, and hardness as

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 4 of 24

identified in Weapon System Specification (WSS) S-133-128, System Specification for MMIII, (WS-133A-M, Wings I, III, V) End Item Specifications threats and vulnerabilities defined in Appendix III of the WSS, and operations doctrine developed and maintained by United States Strategic Command (USSTRATCOM). Further details are contained in the draft Operational Safety, Suitability and Effectiveness (OSS&E) Baseline Document (OBD). The primary activity is the sustainment of the operational force in a state of readiness such that national defense strategies involving these systems can be successfully executed. Many major components have exceeded their life cycles and others are projected to exceed them in the future. Critical emphasis must be focused on prudent logistical intervention through such methods as, Service Life Extension Programs (SLEP), modifications, and replacement programs to ensure the SACCS WS continues to reliably operate through the end date currently projected through 2021. Weapon system sustainment includes incorporating system modifications in response to requirements of the following:

• Performance improvements • Correction of system deficiencies • Life extensions • Advances in technology • Policies mandated by Congress or directed by other higher authorities • Threat or safety-driven changes • Changes in the operational environment such as support and maintenance policies

Requirements for changes or modifications to fielded subsystem(s) are usually driven at the subsystem or lower level. Satisfying these requirements for performance improvements or deficiency corrections generally involves subsystem modification activities that inherently include potential for impacting system-level performance parameters.

1.4. APPLICABLE SYSTEM(S)

The contractor role is to provide technical support for SACCS equipment in system and sustainment engineering, and relevant operations and maintenance (O&M) tasks as directed. The contractor will be responsible for providing technical support to the Government as needed for government repair and/or maintenance actions on SACCS components to include integration and set up of equipment and labs.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 5 of 24

2.0 – STRATEGIC AUTOMATED COMMAND CONTROL SYSTEM (SACCS)

2.1. SUPPORT TO SACCS OPERATIONS

The contractor shall provide on-site advisory support to areas of operations, troubleshooting, analysis, test, technical services, training, and maintenance. The contractor shall maintain a presence at Offutt Air Force Base (AFB), NE only for training purposes. All other personnel (e.g SACCS Engineering Support) will be provided at Hill AFB, UT (exceptions must be approved). The contractor shall provide findings and recommendations to the Government in accordance with (IAW) CDRL A020, Engineering Evaluation Report (EER), DI-NUOR-81411A.

SACCS-Unique Technical and/or Engineering Support. The contractor shall provide telephone- based technical and/or engineering support in the event that the Government cannot organically resolve technical and/or engineering issues.

2.1.1. In the event this telephonic support does not resolve the issue, the contractor shall

provide a quick reaction, on-site engineering and/or technical response to SACCS users across the globe via the 595th Strategic Communications Squadron (SCS) (Offutt AFB, NE) when specifically directed by Government. The purpose of this support is to aid the Government with maintaining the operational readiness of SACCS, aid the Government with tracing suspected engineering or technical deficiencies to a specific root cause, and/or aid the Government with expedited resolution of SACCS engineering or technical deficiencies IAW applicable DOD requirements. The contractor shall physically engage in maintenance action(s) only when directed and formally authorized by the Government. The contractor shall provide a report IAW CDRL A018, Technical Report – Study/Services, DI-MISC-80508B/T.

2.1.2. Operational Procedures, Guides, and Checklists. The contractor shall create and verify

technical and/or operational procedures, guides, and checklists to ensure this data reflects all written and visual information necessary for Government personnel to readily operate SACCS.

2.1.3. Feasibility Investigations. The contractor shall perform feasibility investigations for

modifications and/or SLEPs, impacting the SACCS network’s on-line and off-line (i.e., support equipment) baseline. These studies shall include impacts to: requirements traceability, technical documentation, logistics, operations, infrastructure, cost, schedule, manpower, system performance, compliance with nuclear technical performance criteria, and Cybersecurity. Studies will be delivered to the Government IAW CDRL A024, Technical Report – Study/Services, Trade-Off Studies & Analysis, DI-MISC-80508B/T.

2.1.4. Hardware, Software, Firmware, Interfaces, and Protocols. The contractor shall identify,

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 6 of 24

analyze, design, test, and recommend corrections, updates, and/or revisions to SACCS hardware, software, firmware, interfaces, protocols, and/or other elements of SACCS in conjunction with the 595th SCS. Solutions may involve: legacy SACCS equipment,

COTS/GOTS items, IBM CS-1 Macro assembler language, C and C++ programming languages, CS-1 and PC-based hardware and software architecture, characteristics, and functions.

2.1.5. The contractor shall provide support as required on SACCS interfaces, executive and

trusted computing base (TCB) software, applications software, database and controller software; Software that implements high-level interface protocols to other systems such as the Command and Control Enterprise Database and Nova; and Message processing applications which may process messages from multiple sources and workstations. The contractor shall provide a report IAW CDRL A018, Technical Report – Study/Services, DI-MISC-80508B/T.

2.1.6. The contractor shall support planning, scheduling, authoring, developing, drafting,

revising, correcting, finalizing, and submitting all technical documentation to include Technical Orders (T.O.), Time Compliance Technical Orders (TCTO), ICDs, specifications, technical and/or design drawings, special packaging instructions, technical data packages, family tree(s), trade studies, white papers, and design review materials. Deliver documentation IAW CDRL A060, Product Drawings/Models and Associated Lists, DOSESS-81000E/T.

2.1.7. Engineering Change Proposals (ECP). The contractor shall create, manage (in

coordination with the Government), submit, and archive all SACCS ECPs for SACCS modifications, upgrades, and all other baseline changes. Deliver final ECP IAW CDRL A061, Engineering Change Proposal (ECP), DI-CMAN-80639C.

2.1.8. Training. The contractor shall provide Government-approved maintenance and

operations training, or other SACCS-unique courses (as directed), to Government personnel at locations and times specified by the Government, and provide copies of one- page contractor-developed/contractor-administered student course feedback surveys. These training courses are scheduled by the 595th SCS and are typically conducted in the SACCS-unique training facility located in Building D, Offutt AFB, NE. As an exception, training may also be conducted at an alternate location such as a user location (i.e., at a base Command Post) and as directed by the Government.

2.1.9. Technical Support to Site Visits. The contractor shall go on site visits as approved by the

Government to include every Base Communication Processor (BCP) and Port Expansion Processor (PEP) at least every two years. The technical focus of the visit will include ensuring full and complete operability of all SACCS equipment, both on-line and off-

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 7 of 24

line, present at each location/unit by engaging each respective location’s/unit’s leadership to immediately submit necessary maintenance action requests; review each location’s/unit’s forward supply point, or equivalent function, to ensure that all spares are present, all inoperable or suspect equipment is submitted for repair, all spare equipment present is in “A” condition, and that the forward supply point, or equivalent function, is fully capable of ensuring the full mission capability of the SACCS equipment at that location/unit; provide impromptu or informal user-requested, on-site training or formal user training (must be scheduled) with the 595th SCS; and with the 595th SCS any user- requested procedures, guides, and/or checklists to be immediately provided to the user. During the site visit the contractor will note SACCS equipment configuration, assess the condition of the equipment, and provide technical guidance as needed. The contractor shall provide reports IAW CDRL A021, Site Survey Report, DI-MISC-81381.

2.1.10. Site Surveys. The contractor shall participate in and perform site surveys in support of

installation, removal, and/or renovation of SACCS user sites and/or SACCS equipment, as directed by the Government. Site surveys may be conducted at any location within any country on the globe, but (at current) are restricted to CONUS and Europe. At a minimum, site surveys for installation and renovation shall assess: physical security, Cybersecurity compliance (including Electromagnetic Security (EMSEC)/TEMPEST, and Protection Level), structural capacity, electrical capacity, HVAC capacity, floor plan/facility configuration, and all other elements applicable to meeting SACCS requirements. Coordination with base civil engineering is required to attain much of this data. The contractor shall provide reports IAW CDRL A021, Site Survey Report, DI- MISC-81381.

2.1.11. Circuit Analysis. The contractor shall interface with SACCS Operations and/or the 595th

SCS to assist with attaining optimum end-to-end system performance as requested by the Government and in coordination with the DISA, commercial circuit providers, and/or the respective base communications flight/squadron to include maintaining access to the Telecommunications Certification Office Support System (TCOSS) provided by DISA in the performance of these responsibilities and monitor outages/degradations and report status to the Government for corrective action, utilizing the SACCS Trouble Monitor Report (STMR) database and/or other Government-populated database(s). Report all trending, troubleshooting, monitoring, and related data IAW CDRL A008, Status Report, DI- MGMT-80368A.

2.1.12. SACCS Trouble Monitor Report (STMR) Analysis. The contractor shall analyze SACCS

Operations monthly STMRs, and additional metrics if STMRs are augmented, to provide network and equipment item metrics, availability rates, and trending data that both depict health of system and enable the determination of whether or not Nuclear Technical Performance Criteria (NTPC) are being met. SACCS engineering personnel require ready access to NIPRNet and SIPRNet to accomplish such analysis and reporting. For

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 8 of 24

the personnel at Offutt AFB, the 55th CS will provide them access to NIPRNet and SIPRNet (provided that the personnel meet the clearance requirements). A report of the analysis shall be provided.

2.1.13. The contractor shall detect and recommend actions to correct emerging and/or known

systemic problems. Contractor shall provide this data.

2.1.14. SACCS Logistics. The contractor shall collect, track, analyze, and determine root cause of any discrepancies for SACCS equipment, its condition, and location. This data shall be reported in a spreadsheet, or equivalent toolset as determined by the Government. This spreadsheet may be incorporated in a technical services report and shall be provided.

2.1.15. Cybersecurity. The contractor shall provide cybersecurity support, IAW Department of

Defense Instruction (DODI) 8500.01, Cybersecurity, to proactively support every operational and sustainment facet of SACCS including RMF and information assurance.

2.1.16. Nuclear Command, Control, and Communications (NC3) Support. The contractor shall

analyze, define, and document deficiencies with/across the Hybrid Solution that are relevant to the SACCS mission. The contractor shall provide written recommendations on corrective actions.

2.1.17. The contractor shall provide technical, performance, schedule, cost trade-off, and risk

assessments in order to ensure current and future operational and sustainment requirements conform to Hybrid Solution architectural, integrity, interoperability, and technical performance requirements.

2.1.18. The contractor shall provide organized, analytical assessments and evaluations in support

of policy development, decision making, management, and administration for SACCS. Included are studies in support of SLEPs, recommendations related to acquisition of sustainment equipment, methodologies, and related supporting studies, analyses, or evaluations. The contractor shall provide written recommendations on corrective actions.

2.1.19. The contractor shall identify and eliminate technical deficiencies within SACCS to assure

end-to-end integrity and compliance with nuclear technical performance criteria. 2.1.20. Notifications to AFNWC/NIBN. In an expeditious manner, the contractor shall notify the

SACCS Program Manager of real or potential SACCS technical, engineering, Cybersecurity, project management, test, sustainment, logistics, supply, schedule, cost, performance, and all other actual/potential issues and concerns within the contractor’s control or cognizance. If the SACCS Program Manager or Systems Engineer is unavailable, the Government Procurement Contracting Officer (PCO) shall immediately be notified.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 9 of 24

2.1.21. SACCS Testing. The contractor shall design, author, and modify tests, test procedures,

test plans, and test approaches; author, modify, adapt, and extend test and evaluation guides, precedents, criteria, methods, and techniques; and provide assistance as technical consultant, planner, evaluator-advisor, and coordinator of test and evaluation activities.

2.1.22. The contractor shall be proficient in the following test disciplines: qualification, acceptance, developmental, and integration.

2.1.23. The contractor shall be capable of designing and implementing the Integrated Test Team

(ITT) and Test Readiness Review (TRR), updating Government test master plans, analyzing test plans for thoroughness and correlation to the engineering specifications, and making statistically viable recommendations.

2.1.24. SACCS Material. The contractor shall proactively identify material required to perform

effort in support of SACCS. Once identified, the contractor shall seek and receive approval from the Government PCO prior to making any materials purchases. The contractor will monitor for and identify potential Diminishing Manufacturing Sources and Material Shortages (DMSMS) for SACCS equipment and supplies.

2.1.25. The contractor shall provide technical advice and assistance to the 309th SMXG in SEIL

management. The contractor will use the SEIL for engineering activities, development, testing and failure replication if lab is available. This includes pre-production testing of new hardware and software, 3rd party testing of 595th software updates, feasibility testing of solutions, and EAM testing.

2.1.26. Cost Related Reports. The contractor shall report current and projected program cost,

schedule, technical issues, and status. Reports shall be comprehensive and sufficiently detailed to provide insight into program approach, status, and prognosis including subcontractors.

2.1.27. Contractor Logistics Support (CLS). The contractor shall provide CLS with continuous

technical, logistic, and maintenance services that maintain and sustain Ground Subsystems, devices, and equipment at Offutt AFB (near CRA/CERF). The contractor- provided CLS shall be compliant with DOD policies and guidance, system/device technical orders/technical manuals (TO/TM), commercial manuals, specifications, drawings, and directives as applicable. The contractor shall provide storage and warehouse control for Commercial Off-The-Shelf (COTS) assets to include crypto devices and government furnished equipment items. They shall provide 100% inventory control and provide reports and analysis of the assets. Additionally GSSC shall ship items that do not need CRA/CERF prep actions. The CRA/CERF will ship items that require CRA/CERF prep actions before going to the field with the option for GSSC to ship if

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 10 of 24

funds are not available. All OCONUS shipping will be performed by the CRA/CERF. 2.1.27.1. Storage/Warehouse Control for SACCS Assets: The GSSC storage process will be as

follows: 1) Initial transfer of SACCS equipment will be done by Memo for Record

(MFR) to GSSC.

2) Sufficient storage space, shelving, and support equipment will be provided by GSSC to sustain the current system and support one technical refresh at a time

3) Transportation and handling of equipment will be provided between storage facility, CRA/CERF, and shipping service

2.1.27.2. Inventory Control of SACCS Assets: The GSSC inventory process will be as follows:

1) Keep a current 100% inventory listing of all assets under SACCS direct control.

2) Keep an inventory listing of items transferred to other agencies, i.e. items transferred by MFR to the CRA for their use in repair actions.

3) Continue to maintain the 100% serial number listings of SACCS equipment at using field locations.

2.1.27.3. Provide Status Reports and Analysis of SACCS Assets: The GSSC reporting process

will be as follows: 1) Create a monthly 100% inventory listing of all assets in SACCS direct

control. 2) Create a monthly report showing all assets delivered to and received from the

CRA for shipping during that month 3) As required, provide a report outlining analysis of system health based on

actions taken on only those items under SACCS direct control. 4) Report submitted IAW CDRL A008, Status Report, DI- MGMT-80368A.

2.1.27.4. GSSC Shipping (CONUS only): GSSC shall perform the following process for all

items not shipped through CRA/CERF. (crypto if applicable and consumables such as keyboard/monitor/mouse/printers, miscellaneous cables, and spare hard drives and/or carriers):

1) Pull the item from stock 2) Update the SN Database as required, include in monthly report (2.1.27.3) 3) Create FedEx shipping and return labels 4) Deliver to FedEx for shipment 5) Track shipment 6) Verify item is received 7) Provide disposition as required 8) Close Help Desk JN

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 11 of 24

3.0 – SERVICES SUMMARY 3.1. SERVICES SUMMARY

Below are performance standards (metrics) the Government will use for monitoring contractor performance on critical tasks. These metrics are a meaningful measure of contractor performance and conform to commercial standards to the maximum extent practicable. This PWS is based upon the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. The Government Contracting Officer Representative (COR) will audit the contractor’s processes to ensure they are in place and will use the data from the contractor inspection reports to assess contractor performance.

Table 1: Services Summary Matrix

Performance Objective

PWS Para Performance Threshold Frequency

Sustainment Engineering

2.1.1 2.1.9

Perform feasibility investigations for modification and/or SLEPs impacting the SACCS network

As directed by the government

Technical Support Site Visit

2.1.9 100% compliance with the applicable performance requirements

As generated following site visit

Configuration and Compliance Site Survey

2.1.10 100% compliance with the applicable performance requirements

As generated following site survey

Circuit Analysis 2.1.11 Analyze SACCS circuits, provide STMRs, analyze data and report

Monthly

STMR Analysis 2.1.12 Analyze SACCS operations provided STMRs, analyze data and report

Monthly

Logistics Analysis 2.1.14 Collect, track, analyze and determine root cause of any discrepancies for SACCS equipment, condition and location

Monthly

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 12 of 24

Performance Objective

PWS Para Performance Threshold Frequency

Cost Reporting 2.1.26 Provide program and subcontractor approach and status information at the IPT- level in a clear, organized manner for 100% of applicable activities.

Provide recovery plans which clearly describe the necessary steps and estimated timelines associated with 100% of important issues/delays and of significant issues/delays.

Provide assessments for 100% of “medium and high” consequence cost risks with appropriate cost analyses and estimating or logistics costs models (threshold).

Monthly Status Report for new; Quarterly PMR for on-going

Contractor Logistics Support (CLS)

2.1.27 Provide storage/warehouse control for SACCS assets

Provide 100% inventory control of COTS assets within SACCS possession in

Provide status reports and analysis of SACCS assets

Ship SACCS assets as required

As Required

As Required

Monthly Inventory Listing

As Required

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 13 of 24

4.0 – GENERAL INFORMATION

4.1. 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 Contracting Officer (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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 14 of 24

5.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 15 of 24

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 16 of 24

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 17 of 24

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 18 of 24

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

Table 2: Contract Data Requirements List (CDRL) To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 19 of 24

APPENDIX E: APPLICABLE DOCUMENTS

Table 3: Compliance Documents Applicability Notes Document Number Document Title ALL DOD 3150.2-M DOD Nuclear Weapon System

Safety Manual ALL DOD 4140.1-R Supply Chain Materiel

Management Regulation ALL DOD 5220.22-M and

Supplement 1 National Industrial Security Program Operating Manual

ALL DODD 3150.2 DOD Nuclear Weapon System Safety Program

ALL DODD 8100.02 Use of Commercial Wireless Devices, Services, and Technologies in the DOD Global Information Grid (GIG) Nuclear Weapons-Related Materiel Management

ALL DODI 4140.01 DOD Supply Chain Materiel Management Policy

ALL DODI 5000.02 Operation of the Defense Acquisition System

ALL DODI 8320.04 Item Unique Identification (IUID) Standards for Tangible Personal Property

ALL DODI 8500.01 Cybersecurity ALL DODI 8510.01

Risk Management Framework (RMF) for DoD Information Technology (IT)

ALL DODM 5200.1 DOD Information Security Program: Overview, Classification, and Declassification

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 20 of 24

Table 4: Reference Documents Applicability Notes Document Number Document Title ALL Hardness Data Manuals ALL SACCS Security Classification

Guide ALL 40 CFR 302 Designation, Reportable

Quantities, and Notification ALL 526 ICBMSW OI 20-04 Parts, Materials, and Processes

Engineering ALL AFGSCI 36-283 ICBM Training System

Management ALL AFGSCI 99-102 AFGSC Instruction, ICBM

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

Requirements Development ALL AFI 20-110 Nuclear Weapons-Related

Materiel Management ALL AFI 31-401 Information Security Program

Management ALL AFI 32-7086 Hazardous Materials

Management ALL AFI 36-2251 Management of Air Force

Training Programs ALL AFI 63-101 Integrated Life Cycle

Management ALL AFI 63-131 Modification Program

Management ALL AFI 91-102 Nuclear Weapon System Safety

Studies, Operational Safety Reviews, and Safety Rules

ALL AFI 91-103 Air Force Nuclear Safety Design Certification Program

ALL AFI 99-103 Capabilities-Based Test and Evaluation

ALL AFMAN 23-110 United States Air Force Supply Manual

ALL AFMC Supplement 1 to AFI 20-110

Nuclear Weapons-Related Materiel Management

ALL AFMCI 21-103 Reliability-Centered Maintenance (RCM) Programs

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 21 of 24

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

ALL AFMCI 99-103 Test Management ALL AFMCMAN 21-1 Air Force Materiel Command

Technical Order System Procedures

ALL AFNWCI 99-101 Nuclear Enterprise Test and Evaluation Management

ALL AFPAM 63-128 Guide to Acquisition and Sustainment Life Cycle Management

ALL AFPAM 63-1701 Program Protection Plan ALL AFPD 63-1/AFPD 20-1 Integrated Life Cycle

Management ALL ANSI/ASQ Q9001:2000 Quality Management Systems:

Requirements ALL ANSI/ASQ Q9001:2008 Quality Management Systems:

Requirements ALL ANSI/ASQ Z 1.13-1999 Quality Systems Guide for

Research ALL ASME NQA-1-2004 Quality Assurance Requirements

for Nuclear Facility Applications ALL CJCSM 6510.01

Enclosures B and C Information Assurance (IA) and Support to Computer Network Defense (CND)

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

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

ALL EO 13526 Classified National Security Information

ALL GEIA-STD-0007A Logistics Product Data

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 22 of 24

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

Latest Revision can be obtained by AFNWC/NIE

ALL ICBM-HDBK-01 Systems Requirement Analysis for ICBM Systems

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

ALL ICBMSD 62-CMP ICBM Configuration Management Plan

ALL ICBMSD OI 10-245 The Air Force Antiterrorism Program

ALL ICBMSD OI 10-2501 Emergency Management ALL ICBMSD OI 31-01 Information Security Program

Management ALL ICBMSD OI 31-04 Survivability and Vulnerability

Integration Center Entry Criteria at Little Mountain

ALL ICBMSD OI 62-01 Configuration Control Board (CCB)

ALL ICBMSD OI 62-02 Interface Control Management ALL ICBMSD OI 62-03 Configuration Management

Policies and Procedures ALL ICBMSD OI 62-04 Configuration Audits ALL ICBMSD OI 62-06 Engineering Orders

Policies/Procedures ALL ICBMSD OI 62-08 Requirements Validation Board ALL ICBMSD OI 62-10 Risk Management ALL ICBMSD OI 62-13 Software Configuration

Management ALL ICBMSD OI 99-02 Test and Evaluation Nuclear

Hardness Critical Item Parts Procurement

ALL ICBMSD OI 99-103 Test and Evaluation ALL MIL-HDBK-454 General Guidelines for Electrical

Equipment ALL MIL-HDBK-470 DOD Handbook – Designing

and Developing Maintainable Products and Systems

ALL MIL-HDBK-515 Weapon System Integrity Guide

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 23 of 24

ALL MIL-HDBK-61A(SE) Configuration Management Guidance

ALL MIL-PRF-49506 Performance Specification Logistics Management Information

ALL 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

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

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

ALL MIL-STD-1766 Nuclear Hardness and Survivability Program Requirements, ICBM Weapon Systems

ALL MIL-HDBK-1785 Defense Acquisition Guidebook (DAG)

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

ALL MIL-STD-464 Electromagnetic Environmental Effects Requirements for Systems

ALL MIL-STD-882 Department of Defense Standard Practice: System Safety

ALL NDIA Version 1.0 Engineering for System Assurance

ALL NIST IR 7622 Notional Supply Chain Risk Management Practices for Federal Information Systems

ALL Other Documents Current ICBMSD OIs ALL Public Law 112-81 Section 818, Counterfeit

Prevention Plan

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 7 SACCS – GSSC 2.0

Page 24 of 24

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

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

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

Item Unique Identification Marking Procedures

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

ALL Minuteman III Weapon System Sustainment Systems Engineering Plan 62-SEP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 1 of 22

ATTACHMENT 8

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

AIRBORNE LAUNCH CONTROL SYSTEM (ALCS)

TASK ORDER UNDER THE

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 2 of 22

ATTACHMENT 8 alcs pws ........................................................................................................... 5

1.0 SCOPE ............................................................................................................................. 5

1.1 DESCRIPTION OF SERVICES ...................................................................................... 5

1.2 BACKGROUND .............................................................................................................. 5

1.3 OBJECTIVES .................................................................................................................. 5

1.4 ASSUMPTIONS .............................................................................................................. 6

2.0 Description of Services .................................................................................................... 7

2.1 Technical/Engineering Services ....................................................................................... 7

2.1.1 E6-B Interface Specification ........................................................................................ 7

2.1.2 E-6B Joint Program Test Plan ...................................................................................... 7

2.1.3 E-6B Engineering Change Proposals ........................................................................... 7

2.1.4 Operational Engineering Support ................................................................................. 7

2.1.4.1 ALCS Engineering Baseline ........................................................................................... 7

2.1.5 Modeling & Simulations .............................................................................................. 8

2.1.5.1 Simulate Circuit Models ........................................................................................... 8

2.1.5.2 Mathematical Models ................................................................................................ 8

2.1.6 Probability of Correct Command Transmission (PCCT) Model .................................. 8

2.1.7 LF Link Model Refinement, Antenna Characterization & Status ................................ 9

2.1.7.1 Launch Facility (LF) Antenna Assessment Capability ............................................. 9

2.1.8 ALCS Engineering Change Proposals (ECPs) ........................................................... 10

2.1.9 ALCS Requirements Derivation and Allocation ........................................................ 10

2.1.10 Codes, Crypto and Nuclear Surety ............................................................................. 10

2.2 Logistics ......................................................................................................................... 11

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 3 of 22

2.2.1 Depot .......................................................................................................................... 11

2.3 Investigations/Studies/Analysis ..................................................................................... 11

2.3.1 ALCS Controller (ALCSC) Service Life Extension (SLE) Study ............................. 11

2.3.2 ALCS Controller (ALCSC) Replacement Feasibility ................................................ 11

2.3.3 Power and Grounding Study ...................................................................................... 12

2.3.4 Waveform Converter (WFC) SLE Study ................................................................... 12

2.3.5 Airborne Operational Program (AOP) Feasibility Study ........................................... 12

2.3.6 Circuit Card Assembly (CCA) Repair Feasibility ...................................................... 12

2.3.7 Visual Display Unit (VDU) SLE Study ..................................................................... 12

2.3.8 Demodulator/Decoder (D/D) SLE Study ................................................................... 13

2.3.9 Printer SLE Study ....................................................................................................... 13

2.3.10 ALCS LF Receiver SLE Study ................................................................................... 13

2.3.11 Failure Investigations ................................................................................................. 13

2.3.12 Navy Owned ALCS Equipment Interconnect Cables Investigation .......................... 13

2.3.13 Display Set Controller (DSC) SLE Study .................................................................. 14

2.3.14 Multifunction Selector (MFS) SLE Study .................................................................. 14

2.3.15 Tempest Isolation Filter (TIF) SLE Study .................................................................. 14

2.3.16 Code Retaining Power Supply (CRPS) SLE Study .................................................... 14

2.3.17 Mass Storage Device/Loader (MSD/L) SLE Study ................................................... 14

2.3.18 Portable Storage Unit (PSU) SLE Study .................................................................... 15

2.3.19 ALCS Power Supply Support Analysis ...................................................................... 15

2.4 Test ................................................................................................................................. 15

2.4.1 Operational & Certification Test Support .................................................................. 15

2.4.2 Engineering Test Lab .................................................................................................. 15

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 4 of 22

2.5 ALCS Tools.................................................................................................................... 16

2.5.1 Equipment Logs .......................................................................................................... 16

2.5.2 Software ...................................................................................................................... 16

2.6 Certification .................................................................................................................... 16

2.7 Meetings/Administrative ................................................................................................ 16

2.8 Travel ............................................................................................................................. 16

2.9 Data Rights ..................................................................................................................... 16

2.10 Deliverables ................................................................................................................ 17

2.10.1 Operational, Certification Testing and Failure Investigations .................................... 17

2.10.2 Service Life Extension Investigation & Risk Mitigation Initiatives .......................... 17

2.10.3 Depot Support ............................................................................................................. 17

2.10.4 Document Current ALCS Technical baseline and Requirements .............................. 17

2.10.5 Other Engineering Activities ...................................................................................... 17

3.0 Appendices .............................................................................................................................. 18

APPENDIX A: ACRONYMS AND ABBREVIATIONS ....................................................... 18

APPENDIX B: WORK BREAKDOWN STRUCTURE ......................................................... 19

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION ............ 20

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ....................................................................................................................... 21

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................. 22

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 5 of 22

ATTACHMENT 8 ALCS PWS

1.0 SCOPE

This Performance Work Statement (PWS) describes the services to be provided in this task order under the GSSC contract to ensure that the Airborne Launch Control System (ALCS) remains operational to meet warfighter requirements for at least the next decade. This task order will provide technical, engineering, and logistics services for the ALCS Sustainment program. This PWS will outline and specify the services for studies, analysis and investigations to be completed. This is a Level of Effort Task Order. While it is understood that any task within the general scope of this effort may be reprioritized, added, or removed entirely without changes to this PWS, it is currently anticipated that the scope of work will include, but is not limited to the tasks listed within this PWS.

1.1 DESCRIPTION OF SERVICES

The AFNWC/NIA ALCS Sustainment program requires technical and engineering services and logistical support to sustain the ALCS legacy system. The Contractor shall provide and manage support for logistic sustainment efforts, technical services, research, investigations and studies as further defined in this PWS. This includes providing reports, analysis and models as necessary. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, services and other items necessary to perform this task order, as further defined in this Performance Work Statement. The Contractor will coordinate with the Government to obtain access to AF facilities and equipment to support these tasks as necessary. The Contractor shall perform to the standards in this contract.

1.2 BACKGROUND

The Airborne Launch Control System (ALCS) was last fielded in the late 1980s as Common ALCS under Peacekeeper. Since then, the Air Force decommissioned Peacekeeper, the Minuteman III missile became the primary ICBM. The ALCS needs to be reallocated back into the MMIII weapon system baseline, and efforts need to continue to address aging components and system and subsystem performance anomalies to keep the system operational until the ALCS Replacement program is fielded.

1.3 OBJECTIVES

Maintain operability of ALCS until 2030. Execute investigations, trade studies, generate and update documentation and provide technical understanding of the operation of the system to the government in order to support decisions for repair or service life extension programs for the remainder of sustainment efforts. The contract is structured to provide flexibility in allocating assets to the highest priority risks. The initial scope of work includes the trade studies and investigations as described in this PWS. The Contractor shall support any emergency tasks which occur during the performance periods by reprioritizing current work load. Any tasks

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 6 of 22

identified in this PWS not completed in the current performance period may be either reprioritized into future performance option periods or to a future Task Order.

1.4 ASSUMPTIONS 1. This work to be accomplished by The Contractor only pertains to the legacy ALCS. This

work should not preclude The Contractor, in the form of an Organizational Conflict of Interest (OCI), from future work on other related efforts, such as GBSD or ALCS Replacement.

2. This effort may result in a modified end item as a proof-of-concept hardware platform, which does require an IUID.

a. Item unique identification (IUID): A system of establishing unique item identifiers (UII) within the DoD by assigning a machine-readable character string or number to a discrete item, which serves to distinguish it from other like and unlike items. (Ref: MIL-STD-130N Change 1)

b. Item: “Item” means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts. (Ref: DFARS 252.211-7003)

3. During the lifecycle of the assets that make up ALCS, the OEM and industrial base has changed and as such could result in the inability to qualify parts for certain requirements which could impact the outcomes of some of the efforts herein.

4. Recent analysis of data on ALCS assets indicates more work is needed to identify Service Life Extension activities beyond intermediate and depot level maintenance activities only.

5. ALCS was not designed to operate with modern automated testing equipment and as such the use of automated test equipment has the risk of not capturing, testing or checking all of the equipment issues or ailments of the aging equipment.

6. The Government shall provide coordination and interfaces to arrange time needed at the SMIC, ranges or other government facilities required to complete the outlined efforts.

7. The Government will work with the 625 STOS operators to coordinate the receipt of the crew logs and ALCS logs needed to perform the applicable outlined work efforts.

8. The Contractor shall work with the Government customer to coordinate schedules of the efforts.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 7 of 22

2.0 DESCRIPTION OF SERVICES

2.1 TECHNICAL/ENGINEERING SERVICES

2.1.1 E6-B INTERFACE SPECIFICATION

The Contractor will review the E-6B Interface Specification, capture the technical specification baseline, provide recommended changes to the specification as required by the Government, and provide recommendations and support to the Government, who will coordinate with the Navy PMA-271 and Air Force as required.

2.1.2 E-6B JOINT PROGRAM TEST PLAN

The Contractor will develop a joint test plan based on the E-6B Interface Specification, in coordination with the Air Force ALCS team and Navy PMA-271, to support development, qualification, and acceptance testing. This test plan encompasses the content of the interface document. (ie. power characterization, grounding, cabling, circuitry, environmental, noise, etc.)

2.1.3 E-6B ENGINEERING CHANGE PROPOSALS

The Contractor will support an Engineering Working Group to provide a platform to address ECP and other modifications, which require Air Force and Navy coordination. The Contractor will track and work action items generated by this working group as required. The Contractor will review any proposed changes or modifications to the ALCS and/or E-6B interfaces provided by the Air Force or Navy. The Contractor will verify the changes and identify any impacts to the ALCS, and recommend approvals or solutions as required.

2.1.4 OPERATIONAL ENGINEERING SUPPORT

The Contractor will provide to the Government, a data package (models, simulation results, reports, etc. for 625 Strategic Operations Squadron (STOS) operational engineering support, and onsite technical support for ALCS models as required.

2.1.4.1 ALCS ENGINEERING BASELINE

The Contractor will support reestablishing the ALCS Engineering Baseline by determining what artifacts exist for the Legacy ALCS system, assessing the current state and utility of those documents, and identifying where system knowledge gaps exists. The Contractor will develop a tool that identifies where ALCS artifacts are stored (e.g., JEDMICS, IDR, etc.). This tool will assist in data retrieval and help facilitate the evaluation of each artifact’s relevance, usability, currency, and traceability or pedigree. After capturing information on known artifacts, this tool will be updated periodically to include additional data as specific LRU, SRU, modules, components or other investigations and issues are pursued. The tool will be maintained by The Contractor under this PWS and will be made available to authorized ALCS users as directed by the AF.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 8 of 22

2.1.5 MODELING & SIMULATIONS

The Contractor will characterize the ALCS communications link and provide modeling with recommendations for requirements changes and system improvements to the Government, along with onsite technical support as required. The Contractor will provide technical support for ALCS models and will provide outputs from these models and simulations as needed for briefings, updates to stakeholders and pre- and post-test results. The Contractor will provide modeling and simulation support for Air Force operational tests as required that include, but are not limited to, Glory Trips, Giant Pace (SELM), Giant Ball, and SMIC Fly-over.

2.1.5.1 SIMULATE CIRCUIT MODELS

The Contractor will generate and maintain ALCS circuit simulation models for ALCS high risk assets or where technical data lacks enough information to characterize the operation in the execution of ALCS activities or as directed by the Government. The Contractor will use requirements, circuit diagrams/schematics, operation test data, characterization data, and other data as needed to generate the model. The Contractor will generate, plan, and execute model validation and continuous improvement activities. The goal is to execute simulations in order to understand the current operation and to identify improvement opportunities for hardware modification and update options as supporting data to the investigation/trade study/analysis projects.

2.1.5.2 MATHEMATICAL MODELS

The Contractor will generate and maintain ALCS mathematical models for components contributing to PCCT, including mean time between failure (MTBF) and reliability. The Contractor will use requirements, circuit diagrams/schematics, operational test data, characterization data, and other data as needed to generate the model. The Contractor will generate, plan, and execute model validation and perform continuous improvement activities as required.

2.1.5.3 Physical Configuration Models The Contractor will create and deliver CAD and 3D models of the physical layout of the various LRUs, SRUs and racks of the ALCS system to the Air Force as requested.

2.1.6 PROBABILITY OF CORRECT COMMAND TRANSMISSION (PCCT) MODEL

The Contractor will generate and maintain a PCCT evaluation model as defined in Operation Order Global Citadel. The Contractor will model both PCCT requirements and assessed ALCS capability and will use requirements, operational test data, characterization data, link model, and other data as needed to generate the model. The Contractor will generate, plan, and execute model validation and continuous improvement activities. The Contractor will support approval of the PCCT model as a MMIII Weapon System Reference Model. The Contractor will support briefings and other communications related to the generation and use of the PCCT Model and the

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 9 of 22

assessed ALCS capability. The model should support and provide input for every Weapon System Effectiveness Report (WSER).

2.1.6.1 ALCS Model

The Contractor will generate and maintain a classified ALCS model, taking into account factors such as weather, terrain, and time of day; simulate signal, air-to-ground communications to each Launch Facility (LF) from Operational Order Global Citadel-defined locations; and simulate E-6B flight conditions. The Contractor will provide simulation of the EWO environment. The Contractor will use operational test data, characterization data, the PCCT and link model, and other data as needed to generate the model.

2.1.6.2 Link Model

The Contractor will generate and maintain a signal Link model. The Contractor will use operational test data, characterization data, and other data as needed to generate the model. The Contractor will generate, plan, and execute model validation and continuous improvement activities. The model will support and be part of the overall PCCT Model. The goal is to provide a near-accurate model of the link for operational test and EWO environments for planning, execution and performance monitoring of ALCS.

2.1.7 LF LINK MODEL REFINEMENT, ANTENNA CHARACTERIZATION & STATUS

The Contractor will plan, perform, and report on performance measurements to increase effectiveness of the ALCS models’ predictions. The Contractor will address, but not limited to, the following items:

• LF antenna patterns • E-6B antenna patterns • Loss between the LF Antenna and the input to the LF Receiver Drawer • Circuit Analysis/Simulation

The Contractor will evaluate the status of the LF antenna and investigate mitigations for sustainability risks. The Contractor will investigate government provided LF antennas to calculate RF performance degradation and evaluate material deterioration. The Contractor will evaluate mitigations to address performance and availability. The Contractor will generate plans to mitigate sustainability and performance risks.

2.1.7.1 LAUNCH FACILITY (LF) ANTENNA ASSESSMENT CAPABILITY

The Contractor will prepare plans and tools to assess and sustain the health and performance of fielded launch facility (LF) antennas. The Contractor will also plan, analyze, and report on the health and performance of the LF antennas as directed by the Government. The Contractor will perform the following activities to support this effort:

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 10 of 22

• Develop and facilitate plans to assess the LF antennas, determine tools, build test fixtures, update antenna models and create test plans (including supporting documentation, presentations, schedules, IMPs, and tracking) to support antenna assessment activities.

• As required, coordinate and conduct destructive and non-destructive analyses for LF antennas, including Computed Tomography (CT, Computerized Axial Tomography), material assessment, corrosion, electrical, transmission, integrity capabilities and performance testing as applicable to assess the antennas’ serviceability.

• Collect antenna characterization data at the SMIC to refine Antenna models as needed. • Develop a plan, which may include source data for repair processes to sustain the fielded

LF antennas.

Assessments and evaluations will include identification of any sustainability risks, material degradation, reliability issues or performance anomalies that may impact fielded antennas. Evaluations will include potential mitigation strategies. The government will coordinate test plans, IMPs, access to Air Force facilities, as necessary, to facilitate accomplishing this task. The Contractor will report on the status of all antenna assessment activities at weekly ALCS IPT meetings. The Contractor will request Air Force assistance when necessary to facilitate progress on these activities.

2.1.8 ALCS ENGINEERING CHANGE PROPOSALS (ECPS)

The Contractor will generate, or provide on-call support to the government’s generation of, ECPs for recommended modifications to ALCS end item or subsystem, the ALCS technical baseline, system specification, including but not limited to: functional, product, allocated baseline or element, interface, system or subsystem specifications.

2.1.9 ALCS REQUIREMENTS DERIVATION AND ALLOCATION

The Contractor will analyze and identify system performance requirements, and design constraints at the Survivable Launch Control Element level, ALCS Airborne Subsystem level, and ALCS Ground Subsystem level which relate to the performance of the ALCS mission. The Contractor will address nuclear surety and code protection constraints, and airborne subsystem constraints imposed by the E-6B Weapon system Performance Specification (SD 569-1-4).

2.1.10 CODES, CRYPTO AND NUCLEAR SURETY

The Contractor will provide technical support, as required, for code/crypto related meetings with the NSA, nuclear surety related meetings with AFNWC, and E-6B/signal communications related meetings with US Navy PMA-271. The Contractor will support Technical Interchange Meetings (TIMs).

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 11 of 22

2.2 LOGISTICS

2.2.1 DEPOT

The Contractor will support depot stand up activities to include but not limited to Validation/Verification and aiding in troubleshooting issues and problems that need technical engineering support. The Contractor will recommend updates/corrections to technical data and support both GMATs testing and ALCS end item maintenance. The Contractor will provide updates to Test Support Equipment technical orders. The Contractor will identify maintenance improvements to improve ALCS sustainment. The Contractor will recommend and institute a method for analysis of GMATS test and trend analysis data. The Contractor will support the program office and supply chain determination of worldwide number of ALCS end items and subassemblies. The Contractor will support quarterly audits of spares as requested.

2.3 INVESTIGATIONS/STUDIES/ANALYSIS

The Contractor will perform analysis and studies. At a minimum, all studies and investigations shall include; impacts to system performance, risks, logistics, infrastructure, system architecture, manpower, documentation and drawings. The Contractor will ensure requirements are met with Nuclear Surety, Safety, and Hardness, where applicable, before executing significant testing or modification to any ALCS assets. The Contractor will be responsible for creation and/or management of the following: Integration Management Plan (IMP), Integrated Master Schedule (IMS), cost estimate for executing the study, Test Plan, Data Tools, Test Equipment, Report Writing, ALCS End Item, Drawings/Schematics and other items as needed. The reports and documentation shall be complete, detailed, actionable, and provide multiple options for every Investigation, Study and Analysis. The Contractor will support activities as needed in the execution of these tasks.

The following studies will be performed:

2.3.1 ALCS CONTROLLER (ALCSC) SERVICE LIFE EXTENSION (SLE) STUDY

The Contractor will provide integration and systems engineering support as outlined in 1.6.2 and 1.6.4.1 (excluding 1.6.4.1.13) in the GSSC PWS. The Contractor will perform a SLE Study to include updated circuitry, logic, and operation documentation. Following completion of the study, The Contractor will provide recommendations for mitigating strategy options to the Government for consideration and approval.

2.3.2 ALCS CONTROLLER (ALCSC) REPLACEMENT FEASIBILITY

The Contractor will perform investigation and demonstration for the feasibility of utilizing the EPU-166 to replace the ALCSC. The purpose of the investigation and demonstration will support development of detailed specifications, requirements, and other documentation as outlined in para 2.3. The goal of this effort is to see the technical feasibility of re-hosting the

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 12 of 22

Airborne Operation Program (AOP) onto the EPU-166 and assess functionality, interfaces, and performance compared to the ALCSC to provide sustainment options. (Deliver CLIN 41)

2.3.3 POWER AND GROUNDING STUDY

The Contractor will support testing and analysis to determine impacts to ALCS power supplies onboard the E-6B, if any. Following completion of the investigation and trade study, The Contractor will provide mitigation strategy options for any issues identified in the investigation and provide them to the Government for approval.

2.3.4 WAVEFORM CONVERTER (WFC) SLE STUDY

The Contractor will provide integration and systems engineering support as outlined in 1.6.2 and 1.6.4.1 (excluding 1.6.4.1.13) in the GSSC PWS. The Contractor will perform a SLE Study into the operation and state of the Waveform Converter. The SLE will include updated circuitry, logic, and operation documentation. Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval.

2.3.5 AIRBORNE OPERATIONAL PROGRAM (AOP) FEASIBILITY STUDY

The Contractor will provide integration and systems engineering support as outlined in 1.6.2 and 1.6.4.1 (excluding 1.6.4.1.13) in the GSSC PWS. The Contractor will perform an investigation and trade study on the AOP to determine feasibility of modifying or re-hosting the program. The Contractor will create test plans to test any designs or prototypes.

2.3.6 CIRCUIT CARD ASSEMBLY (CCA) REPAIR FEASIBILITY

The Contractor will provide integration and systems engineering support as outlined in 1.6.2 and 1.6.4.1 (excluding 1.6.4.1.13) in the GSSC PWS. The Contractor will perform an investigation and trade study into the multiple ALCS CCAs. These studies should detail and outline actionable steps to take to repair, procure, replace, modify or rebuild these circuit card assemblies. Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval.

2.3.7 VISUAL DISPLAY UNIT (VDU) SLE STUDY

The Contractor will investigate options to extend the service life of the Visual Display Unit (VDU), which could include but are not limited to, obsolescent parts replacement, cannibalization, repair, or replacement. The Contractor will investigate VDU test and maintenance procedures to determine options to improve diagnostic accuracy, repair capabilities to sustain operations and current inventory, and VDU performance as directed. Following completion of the investigation, The Contractor will provide mitigation strategy options to the Government for approval.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 13 of 22

2.3.8 DEMODULATOR/DECODER (D/D) SLE STUDY

The Contractor will provide integration and systems engineering support as outlined in 1.6.2 and 1.6.4.1 (excluding 1.6.4.1.13) in the GSSC PWS. The Contractor will perform a D/D SLE Study. The Contractor will provide engineering support for any testing and validation needed for the D/D replacement box to ensure it meets Nuclear Surety, Safety, Hardness, and/or other requirements in order to be properly fielded; provide engineering support should the D/D be re-hosted into the GMATS test station; or support activities for the removal of the D/D from the AOP and ALCS system.

2.3.9 PRINTER SLE STUDY

The Contractor will provide integration and systems engineering support as outlined in 1.6.2 and 1.6.4.1 (excluding 1.6.4.1.13) in the GSSC PWS. The Contractor will perform a Printer SLE Study. This should detail modifications to be performed, timeline and needed supportability equipment and parts for remainder of service life.

2.3.10 ALCS LF RECEIVER SLE STUDY

The Contractor will perform a Receiver Drawer SLE Study to include manufacturing of original parts, replacing obsolete subcomponents with modern technology, end-item and subassembly repair, and end-item cannibalization. The Contractor will investigate options to improve diagnostic accuracy and repair capabilities to sustain operations and current inventory on the Receiver Drawer maintenance procedures and processes. The Contractor will also investigate options to improve the Receiver Drawer performance as directed. Following the completion of the investigations, The Contractor will provide mitigation strategy options to the Government for approval. The Contractor will notify the Government if specific test equipment is required to test the receiver drawer.

2.3.11 FAILURE INVESTIGATIONS

The Contractor will support failure investigations that may arise during the course of this contract including performing a safety assessment and fault-tree analysis as required.

2.3.12 NAVY OWNED ALCS EQUIPMENT INTERCONNECT CABLES INVESTIGATION

The Contractor will obtain and analyze data for ALCS equipment interconnect cables that are owned and managed by the Navy to identify and address recurring performance issues. The Contractor will investigate maintenance procedures, assess repair data, and determine root causes and trends. Following the completion of the analysis, The Contractor will provide mitigation strategy options to the Government for approval.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 14 of 22

2.3.13 DISPLAY SET CONTROLLER (DSC) SLE STUDY

The Contractor will perform an investigation and trade study into the operation and state of the Display Set Controller (DSC). Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval that will address improvements to support test and maintenance equipment, such as GMATS, to ensure components and performance are tested correctly and accurately to sustain operations and current inventory.

2.3.14 MULTIFUNCTION SELECTOR (MFS) SLE STUDY

The Contractor will perform an investigation and trade study into the operation and state of the Multifunction Selector (MFS) in order to document where failures are originating. Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval that will address improvements to support test and maintenance equipment, such as GMATS, to ensure components and performance are tested correctly and accurately to sustain operations and current inventory.

2.3.15 TEMPEST ISOLATION FILTER (TIF) SLE STUDY

The Contractor will perform an investigation and trade study into the operation and state of the Tempest Isolation Filter (TIF) in order to document where failures are originating. Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval that will address improvements to support test and maintenance equipment, such as Adapter Test Set, to ensure components and performance are tested correctly and accurately to sustain operations and current inventory.

2.3.16 CODE RETAINING POWER SUPPLY (CRPS) SLE STUDY

The Contractor will perform an investigation and trade study into the operation and state of the Code Retaining Power Supply (CRPS) in order to document where failures are originating. Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval that will address improvements to support test and maintenance equipment, such as Adapter Test Set, to ensure components and performance are tested correctly and accurately to sustain operations and current inventory.

2.3.17 MASS STORAGE DEVICE/LOADER (MSD/L) SLE STUDY

The Contractor will perform an investigation and trade study into the operation and state of the Mass Storage Device/Loader (MSD/Lin order to document where failures are originating. Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval that will address improvements to support test and maintenance equipment, such as GMATS, to ensure components and performance are tested correctly and accurately to sustain operations and current inventory.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 15 of 22

2.3.18 PORTABLE STORAGE UNIT (PSU) SLE STUDY

The Contractor will perform an investigation and trade study into the operation and state of the Portable Storage Unit (PSU) in order to document where failures are originating. Following the completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval that will address improvements to support test and maintenance equipment, such as GMATS, to ensure components and performance are tested correctly and accurately to sustain operations and current inventory.

2.3.19 ALCS POWER SUPPLY SUPPORT ANALYSIS

The Contractor will perform an investigation and trade study on the operation and state of the ALCS Power Supply (ALPS) to document where failures are originating and identify other potential power supply issues. Following completion of the investigation and trade study, The Contractor will provide mitigation strategy options to the Government for approval. This effort may be conducted in conjunction with the Power and Ground study (Para 2.3.3).

2.4 TEST

2.4.1 OPERATIONAL & CERTIFICATION TEST SUPPORT

The Contractor will support data communications investigations (e.g. signal anomalies or attenuation, link analysis, connectivity) identified during operational test actions, SMIC overflights, and on-ground testing. The Contractor will perform investigations to determine root cause and failure mode for issues identified. The Contractor will also support operational test planning activities using the communications link model, provide on-site support to monitor ALCS data link transmission, and provide technical support during test events such as Giant Pace, Giant Ball, and Glory Trips. The Contractor will provide the Government with solutions and options for upgrading testing capability for the ALCS during testing activities.

2.4.2 ENGINEERING TEST LAB

The Contractor will develop and populate an Engineering Test Lab (ETL) for ALCS airborne and ground systems, and will implement the appropriate security measures IAW The Contractor processes and security guidance. The Contractor will produce and maintain documentation for the setup, ETL configuration, and security measures needed to support the ETL. The Contractor will host the ETL in an Engineering Development Area (EDA) and design required hardware and software components to accommodate ALCS Government Furnished Equipment (GFE) and The Contractor test and support equipment. The Contractor will facilitate test, evaluation, integration, and sustainment activities.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 16 of 22

2.5 ALCS TOOLS

2.5.1 EQUIPMENT LOGS

The Contractor will use the 625 STOS ALCS Alert Logs, failure data, and other applicable data source to generate and maintain an ALCS problem log, log ALCS equipment serial numbers installed on particular E-6Bs, and identify when changes are made with no remove and replace action logged in the NALDA system. The Contractor will identify issues and provide prioritization recommendations of ALCS problems on a quarterly basis, or as often as necessary as priorities change. The Contractor will deliver the problem log to the Government each quarter on dates directed by the Government.

2.5.2 SOFTWARE

The Contractor will maintain licensing and operation of software necessary to perform testing and data analysis. The software, scripts and code created for the purposes shall be provided to the government in a readable and usable format.

2.6 CERTIFICATION

The contactor will generate an IA package IAW Risk Management Framework and consider weapon system design, policies, and procedures. The Contractor will integrate nuclear surety and code protection processes where applicable.

2.7 MEETINGS/ADMINISTRATIVE

The Contractor shall provide support to meetings in the form of data, briefings and background papers as required. The Contractor shall participate in regular status meetings to include but not limited to:

• Local IPT’s • Technical Interchange and Design Meetings • Technical Interchanges with SMIC

2.8 TRAVEL

The Contractor shall travel as required and with the approval of the program office to support the functions and services outlined within this contract.

2.9 DATA RIGHTS

The government will retain full rights to all drawings, code, models and data generated under this contract.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 17 of 22

2.10 DELIVERABLES

During option year two, Northrop shall provide at a minimum, the following support and deliverables.

2.10.1 OPERATIONAL, CERTIFICATION TESTING AND FAILURE INVESTIGATIONS • Supports Fly-over, SELM, Giant Ball, Day to day ops, emergent needs

2.10.2 SERVICE LIFE EXTENSION INVESTIGATION & RISK MITIGATION INITIATIVES • Supports Depot activities, shape risk mitigation strategies, contributes to baseline

information

2.10.3 DEPOT SUPPORT • Supports Depot Maintenance Activation and maintenance activities, supply initiatives

and Tech Order updates

2.10.4 DOCUMENT CURRENT ALCS TECHNICAL BASELINE AND REQUIREMENTS • Provide Modeling & Simulation, documentation identification /development, reverse

engineering, interface specs, SLE data as needed to document the current ALCS technical baseline

2.10.5 OTHER ENGINEERING ACTIVITIES • Develop potential ALCS risk mitigation strategies.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 18 of 22

3.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 19 of 22

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 20 of 22

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 21 of 22

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 8 ALCS – GSSC 2.0

Page 22 of 22

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 1 of 8

ATTACHMENT 9

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

FLIGHT TEST, TELEMETRY AND TERMINATION (FT3)

TASK ORDER UNDER THE

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 2 of 8

Attachment 9 ................................................................................................................................... 3

1.0 FT3 PWS ................................................................................................................................... 3

1.1 Scope ..................................................................................................................................... 3

1.2 Purpose .................................................................................................................................. 3

1.3 Background ........................................................................................................................... 3

1.4 Requirements Summary ........................................................................................................ 3

1.5 Services Summary ................................................................................................................ 3

2.0 Appendices ................................................................................................................................ 4

APPENDIX A: ACRONYMS AND ABBREVIATIONS ......................................................... 4

APPENDIX B: WORK BREAKDOWN STRUCTURE ........................................................... 5

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION .............. 6

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ......................................................................................................................... 7

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................... 8

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 3 of 8

ATTACHMENT 9

1.0 FT3 PWS

1.1 SCOPE

The Flight Test, Telemetry and Termination (FT3) objective is successful integration and sustainment of the FT3 program updates. This requirement is still being defined and will be updated at draft RFP.

1.2 PURPOSE

1.3 BACKGROUND

1.4 REQUIREMENTS SUMMARY

1.5 SERVICES SUMMARY

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 4 of 8

2.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 5 of 8

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 6 of 8

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 7 of 8

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 9 FT3 – GSSC 2.0

Page 8 of 8

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 1 of 8

ATTACHMENT 10

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

DEPOT FIELD TEAM

TASK ORDER UNDER THE

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 2 of 8

Attachment 3 ................................................................................................................................... 3

1.0 DEPOT FIELD TEAM PWS .................................................................................................... 3

1.1 Scope ..................................................................................................................................... 3

1.2 Purpose .................................................................................................................................. 3

1.3 Background ........................................................................................................................... 3

1.4 Requirements Summary ........................................................................................................ 3

1.5 Services Summary ................................................................................................................ 3

2.0 Appendices ................................................................................................................................ 4

APPENDIX A: ACRONYMS AND ABBREVIATIONS ......................................................... 4

APPENDIX B: WORK BREAKDOWN STRUCTURE ........................................................... 5

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION .............. 6

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE) ......................................................................................................................... 7

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................... 8

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 3 of 8

ATTACHMENT 10

1.0 DEPOT FIELD TEAM PWS

1.1 SCOPE

The Depot Field Team objective is to gain the capability of providing Depot level support at Field locations. This requirement is still being defined and will be updated at draft RFP.

1.2 PURPOSE

1.3 BACKGROUND

1.4 REQUIREMENTS SUMMARY

1.5 SERVICES SUMMARY

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 4 of 8

2.0 APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

Reference Ground Subsystem Support Contract General Requirements Appendix A

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 5 of 8

APPENDIX B: WORK BREAKDOWN STRUCTURE

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 6 of 8

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Ground Subsystem Support Contract General Requirements Appendix C

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 7 of 8

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT (GFP/GFS/GFE)

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 10 DEPOT FIELD TEAM – GSSC 2.0

Page 8 of 8

APPENDIX E: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be provided with Draft RFP

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 11 SOFTWARE LAB RELOCATION – GSSC 2.0

Page 1 of 5

ATTACHMENT 11

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

SOFTWARE LAB RELOCATION

TASK ORDER UNDER THE

GROUND SUBSYSTEMS SUPPORT CONTRACT (GSSC) 2.0

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

14 May 2018

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.

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 11 SOFTWARE LAB RELOCATION – GSSC 2.0

Page 2 of 5

1.0 Software lab relocation ....................................................................................................... 3

1.1 Program Objective ................................................................................................................ 3

1.2 contract objective .................................................................................................................. 3

2.0 Appendices ................................................................................................................................ 5

APPENDIX A: CONTACT DATA REQUIREMENTS LIST (CDRL) .................................... 5

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 11 SOFTWARE LAB RELOCATION – GSSC 2.0

Page 3 of 5

Attachment 11 SOFTWARE LAB RELOCATION

1.0 SOFTWARE LAB RELOCATION

1.1 PROGRAM OBJECTIVE

The primary objective is to relocate software labs crtical to supporting the Minuteman III Ground Subsytem mission from multiple locations to one location, Hill AFB, UT.

1.2 CONTRACT OBJECTIVE

1.2.1.1 The contractor will provide a Transition, Integration, and Management (TI&M) plan for the remaining software labs to collocate to Hill AFB, UT

1.2.1.2 The TI&M plan shall evaluate the assumptions of the relocation plan, delivered previously, and provide feasibility of conclusions and assess the validity of assumptions and risk factors used in reaching the plan recommendations.

1.2.1.3 The plan for lab collocation shall identify knowledge transfer, destination facility requirements (e.g, power, environmental, security, networking, physical footprint, etc.), all Government Furnished Equipment (GFE) to be relocated, and potential schedule windows for actual transport of equipment to minimize MMIII cost and schedule impacts to contracts requiring the use of lab assets.

1.2.1.4 The engineering cost estimate will not include government costs to prepare the destination lab facility, and the staffing costs for the labs. The costs shall include teardown, packing, shipping, unpacking, and installation of all lab equipment. Troubleshooting and equipment repair costs will also be identified; however, supply system costs to replace GFE will be a government responsibility. Provide recommendations for contractual strategies.

1.2.1.5 Execution of the move plan is to begin at the discretion of the government on a separate contractual action.

1.2.2 Assumptions in 2021 – the Government will have:

• A relocation plan for remaining labs • AVE & WCPS will have moved to Hill AFB and operating without issue • Manpower/knowledge to maintain above said labs is in place and operating without issue • A facility at Hill AFB has been built/procured to locate all remaining labs to Hill AFB

1.2.3 Other considerations:

1. What are the inherent risks of a) Transportation of the labs

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 11 SOFTWARE LAB RELOCATION – GSSC 2.0

Page 4 of 5

b) Rebuild/set up of the labs c) Knowledge transfer (obtaining/retaining SMEs)

2. What is the required physical footprint of the lab a) Include desk/walking space that is ADA compliant b) Not only cube/footage for lab equipment c) Include raised floor for wires/cables/HVAC/etc

FA8214-20-D-XXXX 14 MAY 2018

ATTACHMENT 11 SOFTWARE LAB RELOCATION – GSSC 2.0

Page 5 of 5

2.0 APPENDICES

APPENDIX A: CONTACT DATA REQUIREMENTS LIST (CDRL)

To be provided with Draft RFP