Draft ISC PWS Dated 18 Nov_Posted 20111121.pdf

Page | 1

DRAFT 17

INTERCONTINENTAL BALLISTIC MISSILE (ICBM) 18

INTEGRATION SUPPORT CONTRACT (ISC) 19

PERFORMANCE WORK STATEMENT (PWS) 20

FOR 22

ICBM SPO – AFNWC/NWIX 24

NOVEMBER 18, 2011 26

Page | 2

TABLE OF CONTENTS 48

SECTION I - DESCRIPTION OF SERVICES 5 49

1.0 SCOPE 5 50

1.1 PURPOSE: 5 51

1.2 BACKGROUND: 5 52

1.3 OCI HARDWARE/SOFTWARE EXCLUSION: 7 53

1.4 FUTURE ICBM SUSTAINMENT AND ACQUISITION CONSTRUCT (FISAC) DESCRIPTION: 7 54

1.4.1 FISAC Structure: 8 55

1.4.2 FISAC Working Relationships: 8 56

1.4.2.1 ISC/SPO Relationship: 9 57

1.4.2.2 ISC/Subsystem Relationship: 9 58

1.4.2.3 ISC/Other SPO Managed Contracts Relationships: 9 59

1.4.2.4 ISC/576 FLTS Launch Analysis Group (LAG) Relationship: 10 60

1.4.3 Technical Council: 10 61

1.4.3.1 Government Members: 10 62

1.4.3.2 Associate Government Members: 10 63

1.4.3.3 Contractor Primary Members: 10 64

1.4.3.4 Associate Contractor Members: 11 65

1.4.3.5 Ground Rules: 11 66

1.4.3.6 Administration: 11 67

1.4.4 Subsystem Contractors: 11 68

1.4.5 Special Considerations: 11 69

1.4.6 Transition Strategy: 12 70

1.4.6.1 Notional Transition: 12 71

1.4.6.2 Transition Description: 12 72

1.5 APPLICABLE DOCUMENTS: 13 73

1.6 REQUIREMENTS: 13 74

1.6.1 WEAPON SYSTEM SUSTAINMENT: 13 75

1.6.1.1 System Engineering & Integration (SE&I): 14 76

1.6.1.2 Hardware and Software Sustaining Engineering: 36 77

1.6.2 PROGRAM MANAGEMENT SUPPORT: 45 78

1.6.2.1 Program Schedule Management: 45 79

1.6.2.2 Acquisition Program Documentation Preparation: 45 80

1.6.2.3 Program Risk Management: 46 81

1.6.2.4 Strategic Planning: 46 82

1.6.2.5 Earned Value Management: 46 83

1.6.2.6 Quality Assurance: 47 84

1.6.2.7 Logistics Planning: 47 85

Page | 3

1.6.2.8 Manufacturing and Production Support: 47 86

1.6.2.9 Business and Financial Management: 47 87

1.6.2.10 Data Rights: 49 88

1.6.2.11 Data Management: 49 89

1.6.2.12 Systems Engineering and Integration for Modification and Replacement Programs: 50 90

1.6.3 Air Force Global Strike Command (AFGSC) FDE Support 50 91

1.6.4 KNOWLEDGE TRANSFER (KT) 57 92

1.6.4.1 Program Objectives 58 93

1.6.4.2 Knowledge Transfer Training 58 94

1.6.5 TRANSITION 59 95

1.6.5.1 Transition Plan 59 96

1.6.5.2 Human Resource Plan 60 97

1.6.5.3 Data Transition and Hosting Plan 60 98

1.6.6 ASSOCIATE CONTRACTOR AGREEMENTS 61 99

1.6.7 TRAVEL 62 100

SECTION II - SERVICE SUMMARY 63 101

SECTION III - PROPERTY MANAGEMENT 66 102

3.1 Government Property IAW FAR 52.245-1 66 103

3.2 Nuclear Weapons Related Material (NWRM) 66 104

SECTION IV - GENERAL INFORMATION 70 105

4.1 Security Requirements: 70 106

4.2 Quality Control: 71 107

4.3 Quality Assurance: 71 108

4.4. Physical Security: 72 109

4.5 Hours of Operation: 72 110

4.6 Conservation of Utilities: 73 111

4.7 Records: 73 112

4.8 Environmental Controls: 73 113

4.9 Government Observations: 74 114

4.10 Safety Requirements: 74 115

Page | 4

4.11 ISC Key Personnel Qualifications Guidelines: 75 116

4.12 Partnering Agreement: 81 117

4.13 Antiterrorism Considerations: 82 118

4.14 Phase Out: 82 119

4.15 Publications: 82 120

4.16 Continuation of Essential DoD Contractor Services During Crisis: 82 121

SECTION V - APPENDICIES 83 122

APPENDIX A 83 123

Compliance Documents: 83 124

Reference Documents: 84 125

Model Appendix: 91 126

CDRL Reference Table: 94 127

APPENDIX B 102 128

ACRONYMS 102 129

APPENDIX C 108 130

SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION INDUSTRIAL SAFETY REQUIREMENTS 108 131

Page | 5

SECTION I - DESCRIPTION OF SERVICES 134

1.0 SCOPE 135

1.1 PURPOSE: 137

The purpose of this document is to provide a description of the types of services that the 138 Integration Support Contract (ISC) will perform, not to specify to the contractor how to perform 139 required services; it is in no way intended to suppress innovative ideas or approaches for 140 performing required services. Unless otherwise stated, the use of “contractor” refers to the ISC 141 contractor. All references to other contractors will be specifically stated (e.g. subsystem 142 contractors, NSCCA/PATE contractors, etc.). 143

1.2 BACKGROUND: 144

Since the commencement of the nation‟s land-based Intercontinental Ballistic Missile (ICBM) 145 program, the Air Force never intended to maintain 100% of the necessary technical capability 146 organically. The basis for this model was a 1954 Air Force Advisory Council determination that 147 the specialized and highly technical functions required to develop and sustain ICBMs would be 148 supported by a Systems Engineering/Technical Assistance (SE/TA) contractor. The Air Force 149 employed this SE/TA model for over 40 years, first with Space Technologies Laboratory (STL) 150 and then with Thompson, Ramo and Wooldridge (TRW). In 1997, the Air Force moved away 151 from the SE/TA construct to the ICBM Prime Integration Contract (IPIC). The IPIC model 152 called for much of the weapon system sustainment and program management to be performed by 153 the IPIC contractor. As a result, the Government has lost much of its former organic capacity to 154 integrate, sustain, and manage the weapon system and its associated programs. 155

The Minuteman III (MMIII) is a mature weapon system that is in the Operation and Support 156 Phase of its life cycle. The primary ICBM activity is the sustainment of the operational force in 157 a state of readiness such that national defense strategies involving these systems can be 158 successfully executed, if required. Top-level system performance parameters that reflect the 159 adequacy of the ICBM force readiness are availability, reliability, accuracy, and hardness. 160 Weapon System Sustainment includes: incorporation of changes to ICBM Systems in response to 161 requirements for performance improvements; to make appropriate use of advances in 162 technology; correction of system deficiencies; determining the need for and executing life 163 extension programs; implementation of policies mandated by Congress or directed by other 164 higher authorities; addressing threat or safety driven changes or other changes in the operational 165 or support environment. 166

Requirements for changes or modifications to fielded systems are usually applicable at the 167 subsystem or lower level and will be performed primarily by the subsystem contractors. 168 Satisfying these requirements involves acquisition activities that can potentially impact system-169 level performance. The ICBM System Program Office (SPO), with support from the contractor, 170 will manage the contracts required to integrate and incorporate changes and modifications, and 171 sustain ICBM systems. 172

The contractor will assist the SPO in its performance of tasks associated with Engineering and 173 Program Management services referenced above. The primary focus will be to ensure any 174

Page | 6 modifications or changes to the system will maintain and/or improve system-level performance. 175

Successful accomplishment of these tasks will ensure an effective process for weapon system 176 and subsystem performance assessment, systems requirement determination, trade studies, 177 subsystem/item specifications, configuration management and control, test and evaluation, and 178 the application of streamlined program management techniques. 179

The contractor will submit the following schedule and plans: Integrated Master Schedule (IMS), 180 Management Plan, Transition Plan and Contractor‟s Risk Management Plan. 181

The top-level system performance parameters associated with System Readiness are: availability, 182 reliability, accuracy, and hardness. As the ICBM force continues to age and is modified and 183 upgraded, opportunities for changes in capability and performance effectiveness are introduced. 184

At the subsystem/system-level, numerical values have been established for availability, 185 reliability, and accuracy. The actual numerical values are outside the classification scope of this 186 document and will not be specified herein. Hardness is specified at the subsystem-level and 187 there are no numerical threshold values established at the system-level for this performance 188 parameter. Hardness performance is based on subsystem analysis and testing. Reporting of 189 hardness will be provided by the ICBM product IPT organizations of the ground, guidance, 190 propulsion, and reentry vehicle/reentry subsystems. These parameters represent performance 191 values below which the system cannot be allowed to fall unless coordinated decisions are made 192 to allow such degradation based on funding and program considerations. 193

The contractor‟s responsibilities relative to these top level system performance parameters will 194 consist of assisting the Government to continually assess the operational performance of the 195 weapon system. The contractor will assist the Government in determining and reporting the 196 current performance capabilities of the ICBM weapon system relative to the baseline values. 197

They will also identify as early as possible in the assessment process potential areas of 198 performance degradation that would impact capability. Another key element of weapon system 199 sustainment will be to determine the basic causes of potential System Performance degradation. 200

This process, performed primarily at the subsystem-level, includes using engineering analysis 201 techniques such as design analysis, testing, evaluation of operational data, reliability modeling, 202

Failure Modes and Effects Analysis (FMEA), physical failure analysis and other conventional 203 engineering problem identification techniques. The contractor will perform these analyses if an 204 issue is determined to be at the system-level. In all other cases, the contractor will support the 205

SPO by validating the root causes identified by the IPTs and/or subsystem contractors and ensure 206 the problem is isolated to the lowest hardware and/or software levels possible. 207

The contractor will assist the Government in evaluating corrective actions developed by the IPTs 208 and/or subsystem contractors and in planning the resources necessary to implement the solution. 209

In those cases where the proposed solution involves actions outside the scope of contractor 210 responsibilities (Government Depot Maintenance, storage, supply, transportation, procurement of 211 replacement spares, materials, parts, and pieces to support maintenance or Government processes 212 and procedures) the Government will implement the solution. The contractor‟s role will be to 213 monitor and assess the effectiveness of the corrective action, reporting results to the SPM. In 214

Page | 7 cases where the proposed solution involves modification affecting interfaces (i.e. changes to the 215 form, fit, or function of the existing design) the contractor will, in consultation and cooperation 216 with the IPTs and/or subsystem contractors, verify correct allocations of the system performance 217 parameters to the hardware/software level requiring change and will provide integration support 218 where necessary. 219

Field operations introduce factors that are outside the control of designers (maintenance 220 management policies and procedures, storage, supply, transportation, procurement of 221 replacement spares, materials, parts, and pieces to support maintenance, utilization, and 222 environment). Because of this, operational values of reliability, maintainability, and availability 223 are typically not used directly for contractual requirements. Therefore, the contractor will 224 translate required operational performance parameters into inherent design performance 225 parameters that can be used to define, measure, and evaluate design (modification) programs. 226

The translation process will ensure traceability between the proposed design performance 227 parameters and the top-level system operational performance values. 228

1.3 OCI HARDWARE/SOFTWARE EXCLUSION: 229

In order to assure objectiveness of all ISC contractor recommendations to the Government, the 231 successful offeror for the ISC will have a hardware/software restriction imposed. See contract 232 clause for details. 233

1.4 FUTURE ICBM SUSTAINMENT AND ACQUISITION CONSTRUCT (FISAC) 235

DESCRIPTION: 236

The ICBM SPO must prepare a sustainment concept to ensure a safe, secure and reliable MMIII 238 weapon system until 2030. This activity designated the FISAC, will replace the current IPIC 239 when it ends 30 September 2012 and is described in detail below. 240

Page | 8

1.4.1 FISAC Structure: 242

Figure 1 244

1.4.2 FISAC Working Relationships: 245

Figure 2 247

Page | 9

1.4.2.1 ISC/SPO Relationship: 248

The contractor will assist the Government in performing its roles as ICBM weapon system 249 integrator and the program management office. The contractor‟s main functions will be in 250 support of weapon system integration to include Systems Engineering, Integration and Program 251 Management support. Most of these functions are being performed by the IPIC today. The role 252 envisioned is similar to the role TRW performed prior to IPIC. The contractor will, along with 253 the subsystem contractors, provide transition support of industrial ICBM technical expertise and 254 knowledge to the ICBM organic workforce. This contract will augment organic resources by 255 providing breadth and depth of capabilities for nuclear surety, system safety and security, system 256 engineering and integration, sustaining engineering, program management, risk management, 257 technical assessment, strategy development, interface with operations and logistics, business 258 analysis, mission effectiveness, and ICBM Demonstration/Validation (Dem/Val) Applications 259

Programs. This contract will be flexible and allow for adjustments to the contractor workforce to 260 gain efficiencies based on the changing requirements, policy, realities of the industrial base, and 261 the Government‟s capability to support MMIII. 262

1.4.2.2 ISC/Subsystem Relationship: 264

The subsystem support contractors will provide the preponderance of sustaining engineering 265 support to the subsystems. The contractor will provide subsystem expertise to validate 266 subsystem contractor analyses and produce requirements and other documentation for subsystem 267 acquisitions that would create an OCI if produced by the subsystem contractor. As programs are 268 initiated for the subsystems, new Contract Line Item Numbers (CLINs) will be added to the ISC 269 for tasks that specifically support those programs. This is required to ensure the proper 270 appropriations are used and each program pays for the additional support required associated 271 with their program. 272

In order to competently and conscientiously support MMIII, the AF requires its contractors and 273 their major subcontractors to effectively share information concerning the status of programs and 274 technical issues with the weapon system. This communication will need to occur with the 275

Government, whether represented by AF or contractor personnel, and among other system 276 support contractors to the maximum extent consistent with proper protection of classified and/or 277 other sensitive information. To achieve this, the contractor must be able to have appropriate 278 Non-Disclosure Agreements with subsystem contractors and subcontractors and demonstrate the 279 ability and willingness to communicate openly. The contractor will not provide contractual 280 direction to Government contractors. 281

1.4.2.3 ISC/Other SPO Managed Contracts Relationships: 282

The contractor will maintain awareness of the progress, technical issues and status of all F-900 283 and other SPO managed Non-FISAC programs (i.e. SACCS, MMPU, etc.) to ensure integration 284 with the weapon system and smooth transition to the follow-on phase(s). The relationships with 285 other contractors are the same as for the subsystem contractor relationship in paragraph 1.4.2.2. 286

The IPIC was structured with the F-900 clause to prevent disruption of ongoing efforts. 287 Performance will continue until completion of the task, subject to availability of funds, unless 288 terminated, regardless of whether or not a succeeding option for engineering services is 289

Page | 10 exercised. Additional tasks will not be added to the contract after the end of the period of 290 performance of the last exercised option. 291

1.4.2.4 ISC/576 FLTS Launch Analysis Group (LAG) Relationship: 292

The purpose of the LAG is to determine the root cause of a mission anomaly and interpret data. 294

The LAG will be comprised of, but not limited to, the following: 576 FLTS/TEMA, 30 SW/SE 295 representatives and AFNWC/NWI representatives. The National Nuclear Security 296

Administration (NNSA) and its associated laboratories and the Western Range and its associated 297 contractors may also be a part of the LAG composition. For anomalies, the LAG may obtain 298 additional expertise as necessary for the investigation. In the case of a mishap, the LAG will 299 provide and interpret the telemetry data and/or any other data to both the safety and accident 300 investigation board. The ICBM SPO and the ISC will support LAG anomaly investigations, as 301 requested. 302

1.4.3 Technical Council: 304

The contractor will act as the secretariat and be a participant on the ICBM Technical Council. 305

The ICBM SPO will establish and chair this council which will meet periodically, as determined 306 by the SPM, and be comprised of contractor and SPO representatives from each of the 307 subsystems. The Technical Council will provide a forum where the ICBM SPO and key 308 suppliers at various levels can directly, and on an equal level, engage on issues important to 309 ICBM systems. 310

1.4.3.1 Government Members: 311

System Program Manager (SPM) (Chair), Director of Engineering (Alt Chair), Technical 312 Director, ICBM Flight Systems, Technical Director, ICBM Ground Systems, Technical Director, 313

ICBM Systems Engineering, AFGLSC (748 SCMS/GUEA), AFGSC (HQ/OL-J), AFNWC/EN, 314

AFNWC/XR, AFPEO/SS, 309

th Maintenance Wing, and others as determined appropriate by the 315

SPO. 316

1.4.3.2 Associate Government Members: 317

Associate government members are designated by the relevant IPT Chief or Director of 319

Engineering. 320

1.4.3.3 Contractor Primary Members: 321

Contractor, Guidance System Contractor, Propulsion System Contractor, Reentry System 322 Contractor, Ground System Contractor, Partial Bridge Contractor, and F-900 Contractor. 323

Page | 11

1.4.3.4 Associate Contractor Members: 325

Associate contractor members are designated by the relevant government IPT SPO Director of 326

Engineering from among the contractors or subcontractors currently on contract to perform 327 ICBM support. Examples of expected members are inertial instrument designers and producers, 328 solid propulsion provider, liquid propulsion provider, flight control provider and Rapid 329 Execution and Combat Targeting (REACT) console provider. If an associate contractor is also a 330 subsystem contractor and primary technical council member, then additional membership is not 331 required. 332

1.4.3.5 Ground Rules: 333

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

1.4.3.6 Administration: 337

The SPO Director of Engineering is the process owner of the ICBM Technical Council. The 338 contractor will provide a secretary to record minutes, schedule meetings and file presentations 339 given at the ICBM Technical Council. The contractor will assist the SPM and SPO Director of 340 Engineering in updating the charter as required and coordinating it with the other Technical 341

Council members. Meetings will initially be held quarterly. The frequency and duration of 342 meetings will be adjusted by the SPO Director of Engineering in consultation with the SPM and 343 the ICBM Technical Council members as the forum matures. 344

1.4.4 Subsystem Contractors: 345

Each subsystem sustainment contract in the FISAC will include the sustaining engineering 346 efforts for that subsystem and any relevant Operations and Maintenance (O&M) support tasks 347 required to sustain the subsystem that are not accomplished on a different contract or by an 348 organic entity. For example, repair of the guidance subsystem is accomplished on a separate 349 government contract to the Boeing Guidance Repair Center (or its replacement), which also 350 includes inertial instrument repair for other weapon systems. Test equipment programs and 351 modifications may also be performed on the contract as long as the dollar threshold for the 352 contract is not exceeded. Software IV&V will be managed under a separate contract with 353 Nuclear Safety Cross Check Analysis (NSCCA/PATE) contractor. Major modifications, such as 354 a fuze replacement or Gyro Stabilized Platform replacement will be separately competed as these 355 programs will be ACAT 1D programs and are likely to provide an opportunity for innovation 356 from the larger industrial base to improve weapon system performance. However, ACAT II, 357

ACAT III and non-ACAT programs may be executed by a subsystem contractor. 358

1.4.5 Special Considerations: 359

The subsystem contractors will need to act in cooperation with the ISC and the Government for 360 the overall success of the total weapon system integration. The contractor will be required to 361 negotiate appropriate Non-disclosure Agreements (NDAs) with all subsystem contractors so that 362 information needed in support of ICBM weapon system can be freely shared between the 363 subsystem contractors and the ISC contractor. While the contractor maintains a close 364

Page | 12 relationship with the SPO, the contractor is not allowed to perform inherently governmental 365 functions. The responsibility to direct other contractors and ultimately approve or disapprove 366 reports and other products remains with the SPO. 367

1.4.6 Transition Strategy: 369

1.4.6.1 Notional Transition: 371

Figure 3. Notional Transition Timeline 373

1.4.6.2 Transition Description: 374

The SPO, with contractor and subsystem contractor support, will ensure a smooth transition for 375 the ICBM weapon system from the IPIC to the series of contracts awarded under the Future 376

ICBM Sustainment and Acquisition Concept (FISAC). 377 Upon execution of the ISC, each subsystem contract, and the Partial Bridge Contract (PBC), the 379 ISC contractor will be required to meet with the Government and the PBC contractor and/or 380 subsystem contractor to jointly plan transition of the workload from the PBC to the applicable 381 contract. The transitions will include all data, tools and models used in the execution of 382 engineering support to the weapon system or particular subsystem. The ISC or Subsystem 383

Transition Plan will clearly state the point at which responsibility for a task is transferred to the 384 new contractor. Responsibility transfer will be documented at transfer by the PBC contractor 385 and contractor or subsystem contractor. The contractor will support the Government in assessing 386 and monitoring progress on Subsystem Transition Plans created after ISC award. The PBC 387 contractor will present any issues regarding rights to the data, tools and models used in the 388

Page | 13 execution of engineering support to the Government Procuring Contracting Officer (PCO) in a 389 timely manner for resolution. The PBC contractor and contractor or subsystem contractor will 390 then execute to that transition plan once it has been approved by the Government. The PBC 391 contractor and contractor or subsystem contractor will report progress on the transition plan to 392 the Government. The PBC contractor and subsystem contractor will complete transition of all 393 subsystem tasks not later than six months after execution of the relevant contract. Transition of 394 system engineering tasks are detailed in section 1.6.5 TRANSITION. 395

1.5 APPLICABLE DOCUMENTS: 397

See Appendix A 399

1.6 REQUIREMENTS: 401

The requirements described in this section are intended to describe all capabilities potentially 402 necessary to sustain the weapon system and encompass the scope of effort expected to be 403 executed for this contract. Capabilities may be applied to future planning and analysis, 404 applications programs, technology insertion, major modifications competed separately from the 405

FISAC contracts, or requirements definition for a follow-on system. Use of ISC capabilities for 406 these future efforts would be incorporated as add-on CLINs as the tasks and/or funds are 407 identified and available. 408

1.6.1 WEAPON SYSTEM SUSTAINMENT: 409

The AFMC definition of Sustaining Engineering is: “Engineering effort on systems, products, or 410 materials, required to resolve technical or supportability deficiencies revealed in operational 411 service.” For ICBMs, a major portion of Sustaining Engineering efforts are dedicated to 412 assessment of ICBM weapon system status relating to key performance requirements. It includes, 413 but is not limited to: assessing deficiency indicators; defining the characteristics and causes of 414 deficiencies; determining the impact on the affected product; identifying and evaluating 415 alternative solutions; recommending preferred solution; and designing, integrating and validating 416 the solution. It includes all associated efforts (e.g., engineering and technical data, modeling, 417 simulation, and testing) which are integral to the completion of the overall engineering task as 418 well as the engineering effort necessary to define and specify necessary embedded system and 419 associated test system software changes after establishment of an initial software production 420 baseline. 421

The contractor shall perform the following sustaining engineering activities as they apply to 422 weapon system-level and shall support the SPO for sustainment activities at the subsystem-level. 423 The activities fall into two broad areas: Systems Engineering and Integration; and, Hardware and 424 Software Sustaining Engineering. The particular activities pursued at a given time will be 425 consistent with workload resources and priorities. 426

Page | 14

1.6.1.1 System Engineering & Integration (SE&I): 428

The contractor shall perform technical services related to SE&I as directed by the Government. 429

The Systems Engineering process consists of evolving functional and design requirements. It has 430 as its goal the achievement of the proper balance between operational, economic, and logistics 431 factors. It employs a sequential and iterative methodology to reach cost effective sustainment 432 solutions. Information developed from this process is used to plan and integrate the engineering 433 effort for the system as a whole. Systems engineering is the application of scientific and 434 engineering effort to: 435

- Transform an operational need into a description of system performance parameters and a 436 preferred system configuration (both hardware and software) through the use of an 437 iterative process of functional analysis, synthesis, optimization, definition, design, test, 438 and evaluation. 439

- Integrate related technical parameters and assure compatibility of all physical, functional, 440 and program interfaces in a manner that optimizes the total system definition and design. 441

- Integrate reliability, maintainability, logistics support, safety, producability, security, 442 survivability, structural integrity, human factors and other related specialties into the total 443 engineering effort. 444

For both contractor activities and Intercontinental Ballistic Missile Systems Division (ICBMSD) 445 activities, the contractor shall provide support to maintain the process architecture, map Systems 446 Engineering Assessment Model (SEAM)/AS9100 requirements, maintain command media, 447 identify process area gaps, establish process ownership, develop and update operating 448 instructions and plans, develop and implement awareness training for operating instructions. 449

For both contractor activities and ICBMSD activities, the contractor shall identify SEAM key 450 performers, develop SEAM overview briefs, conduct SEAM overview briefs, collect and update 451 SEAM evidence, conduct SEAM self assessments, identify gaps and develop actions, facilitate 452 external SEAM validations, identify gaps and continuous process improvement action plans, and 453 share results in the SEAM. 454

The contractor shall conduct Technical Peer Reviews on appropriate deliverables including but 455 not limited to documents, trade studies, requirements, presentations and any other product 456 delivered or formally presented to the government. The Technical Peer Reviews shall include 457 subcontractors, government personnel and other key parties that contribute at a working group 458 type level. 459

The contractor shall participate in the identification of, planning for, conduct of and review of 460 technical design reviews identified in MIL-STD-1521 and the Integrated Defense Acquisition, 461 Technology, and Logistics Life Cycle Management System process chart. 462

Page | 15

1.6.1.1.1 Nuclear Surety: 464

The Air Force uses the DoD definition for Nuclear Weapons Surety as: Materiel, personnel, and 465 procedures which contribute to the security, safety, and reliability of nuclear weapons and to the 466 assurance that there will be no nuclear weapon accidents, incidents, unauthorized weapon 467 detonations, or degradation in performance at the target. As such, the contractor shall integrate 468 nuclear surety requirements into the ICBM System Engineering process. 469

The contractor shall, in coordination and cooperation with subsystem contractors, support the 470 ICBM SPO in maintaining its nuclear weapon system surety program in accordance with 471 Department of Defense (DoD) requirements detailed in DoD 3150.2-M and DoDD 3150.2. 472

Air Force implementation of DoD requirements are described in AFPD 91-1 and further detailed 473 in: AFI 91-101, AFI 91-102, AFI 91-103, AFI 91-104, AFI 91-105, AFI 91-106, AFI 91-107, 474 AFI 91-114, AFI 91-117, AFMAN 91-118, AFMAN 91-119, AFMC and AFNWC supplements. 475

The above policies are tailored for applicability to new or modified ICBM and Air Launch 476

Control System (ALCS) (installed in Navy E-6B aircraft) hardware and software components, 477 subsystems and systems, support equipment, ICBM facilities, special test and maintenance 478 programs. Engineering data delivered in support of the DoD and Air Force policies may include: 479 Nuclear Certification Impact Statements (NCIS), Certification Requirements Plan (CRP) Nuclear 480 Certification Plan (NCP), Nuclear Surety Evaluation (NSE) Report, Fault Tree Analysis, 481

Probabilistic Risk Assessment, Unauthorized Launch Studies, Launch Action Studies, Briefing 482 Materials (Nuclear Surety Briefings, Point Papers and White Papers), Safety & Nuclear Surety 483

Technical Memorandum, Assessments of Subsystem Contractor Deliverables and source data to 484 ICBM Technical Orders and OPCERT/DECERT Technical Orders procedures for ICBM 485 Nuclear Critical Components according to Technical Manual Contract Requirements (TMCR 86-486

01). 487

1.6.1.1.1.1 The contractor shall, in cooperation and coordination with subsystem contractors, 489 support the ICBM SPO in maintaining the nuclear certification program and 490 preserving the nuclear certification of MMIII. The nuclear certification program 491 shall be in accordance with AFI 63-125. Applicable certification criteria shall be 492 derived for new or modified ICBM hardware and software components, 493 subsystems and systems, support equipment, facilities, special test and 494 maintenance programs. The contractor shall review and provide assessment of 495 deliverables to include: Nuclear Certification Impact Statement (NCIS), 496 Certification Requirements Plan (CRP) Ground Launched Missile Nuclear Safety 497 Analysis Report (NSAR), Nuclear Surety Evaluation (NSE) Report, Briefing 498 Materials (Nuclear Surety-Briefings, Point Papers and White Papers), Safety & 499

Nuclear Surety Technical Memoranda, source data for ICBM Technical Orders 500 IAW TMCR 86-01, Changes to the ICBM Items in the Master Nuclear 501 Certification List (MNCL), Nuclear Certification Plan (NCP), Engineering 502

Evaluation Report (EER) (Nuclear Surety), Aircraft Nuclear Safety Analysis 503 Report (NSAR) for (Flight Safety Analysis) & (Nuclear Safety Analysis Report 504 and Software Certification Plan (SCP). 505

1.6.1.1.1.2 The contractor shall prepare Nuclear Certification actions that document: 507

Page | 16

1.6.1.1.1.2.1 Adverse effects on primary safety devices and ICBM weapon system features 509 which control the following nuclear critical functions: Authorization, Pre-arming, 510 Launching, Releasing, Arming, and Targeting as detailed in AFI 91-107. 511

1.6.1.1.1.2.2 Compliance with AFI 91-107 Table 1 which gives the Air Force established 513 numerical probability requirements for obtaining an unintentional significant 514 nuclear yield because of faults and failures in the ICBM system. 515

1.6.1.1.1.2.3 Compliance with AFI 91-107 Table 2 which gives the Air Force established 517 numerical probability requirements for preventing inadvertent critical function 518 activation because of system faults and failures. 519

1.6.1.1.1.3 The contractor shall support the ICBM System Integrity Verification (SIV) team 521 by providing nuclear surety support and monitoring for compliance of applicable 522 AFI 91 series policies. 523

1.6.1.1.1.3.1 The contractor shall support the review of: ICBM TO change recommendations 525 produced by field units, SPO, AFGLSC, ICBM Depot organizations, and/or 526 subsystem contractors; TO data produced by ICBM modification programs; field 527 or SPO generated -107 ETAR requests per TO 00-25-107; depot generated 528

AFMC IMT/Form 202 requests; field generated -107 Maintenance Assistance 529 Requests (MAR) requests per TO 00-25-107; depot generated AFMC IMT/Form 530 202 requests; Test Directives, Test Plans and engineering procedures developed in 531 support of depot and operational test and maintenance projects. 532

1.6.1.1.1.4 The contractor shall provide nuclear surety support to: 534

1.6.1.1.1.4.1 Complete assigned ICBM SPO action items from ICBM mishaps. Support shall 536 include tracking, providing detailed recommendations to close all assigned action 537 items from DULL SWORD Deficiency Reports, High Accident Potential (HAP) 538

Report, Safety Investigation Board (SIB) Reports, Operational Review Board 539 (ORB) Reports, Discrepancy Reports (DR), Potential Code Compromise (PCC) 540

Reports, and Code Related Event (CRE) Reports. The actions will be used to 541 develop ICBM trend data to identify and correct problems before they 542 occur/recur. 543

1.6.1.1.1.4.2 Special ICBM test and maintenance programs such as Rivet Minuteman 545

Integrated Life Extension (MILE), Hardness Surveillance Electromagnetic Pulse 546

(EMP) Program (HSEP), and SELM test or other special test or maintenance 547 action required in the operational ICBM fleet. Support shall include development 548 of assessments and reports such as: Status Reports for Compliance of Nuclear 549 Surety & Safety Support to AFI 91 Series Polices; Briefing Materials for 550 Compliance of Nuclear Surety & Safety Support to AFI 91 Series Polices. 551

1.6.1.1.1.4.3 Working groups. These include: AFNWC/NWIEV Safety IPTs, ICBM Nuclear 553

Surety Working Group (NSWG), Air Force NWSSG (Nuclear Weapon System 554

Page | 17

Safety Groups), ICBM POG (Project Officers Working Group), ALCS Nuclear 555

Surety Working Group (AINSWG) with US Navy, Nuclear Command and 556 Control (NC2)/Nuclear Command, Control, and Communications (NC3) study 557 groups, Nuclear Security Working Groups, and ICBM Codes Conference. 558

Support shall include developing working group Meeting Agendas, preparing and 559 consolidating Briefing Materials from other ICBM SPO IPTs, Status Reports on 560 Engineering Assessments or Answers to Assigned Action Items that have been 561 assigned to other ICBM SPO IPTs and providing Meeting Minutes to participants. 562

1.6.1.1.1.4.4 The contractor shall provide nuclear surety support to a Special Access Program 564 (SAP) in a government cleared facility. Level of support will be established post 565 contract award. 566

1.6.1.1.2 System Safety Program and Safety Risk Management Process: 568

1.6.1.1.2.1 The contractor shall support the ICBM SPO System Safety Program to identify and 570 control ICBM hazards, to prevent mishaps and track mishaps IAW System Safety 571

Program Plan, Safety Study Plan and Safety Study Report. This task is in support of 572 the ICBM SPO efforts to comply with requirements tailored from MIL-STD-882D, 573 AFPD 91-2, AFI 91-202, AFI 91-204 and AFMAN 91-221 Air Force policies. 574

1.6.1.1.2.2 The contractor shall support the ICBM SPO to maintain its Safety Risk Management 576

Program IAW MIL-STD-882D and Safety Risk Management Plan. The contractor 577 shall review and provide an assessment of subsystem contractor deliverables to 578 include Risk Assessment Studies, System Safety Hazard Analysis Report (SSHAR), 579

Safety Assessment Reports (SAR), Risk Acceptance Recommendations, Threat 580

Hazard Assessment, Briefing Materials (Briefings, Point Papers and White Papers), 581 Safety & Nuclear Technical Memoranda, source data for ICBM Technical Orders 582 IAW TMCR 86-01and Changes to the ICBM Items in the MNCL when risks are 583 addressed at the subsystem-level. The contractor shall produce any of the listed 584 deliverables when the risk requires system-level resolution. The contractor shall 585 maintain the AF Safety Risk management official files of all risk 586 assessment/acceptance. 587

1.6.1.1.2.3 The contractor shall support the ICBM SIV team by providing system safety, ground 589 safety, and weapons safety support and monitoring for compliance of applicable AFI 590 91 series policies. 591

1.6.1.1.2.3.1 The contractor shall support the review of: ICBM TO drawing and spec changes 593 produced by field units, SPO, AFGLSC, ICBM Depot organizations, and/or 594 subsystem contractors; TO data produced by ICBM modification programs; field 595 or SPO generated -107 ETAR requests per TO 00-25-107; depot generated 596 AFMC IMT/Form 202 requests; field generated -107 Maintenance Assistance 597 Requests (MAR) requests per TO 00-25-107; Test Directives, Test Plans and 598 Engineering Procedures developed in support of depot and operational test and 599 maintenance projects. 600

Page | 18

1.6.1.1.2.4 The contractor shall, in coordination and cooperation with subsystem contractors as 602 required, provide safety support to: 603

1.6.1.1.2.4.1 Complete assigned ICBM SPO action items from ICBM mishaps. Support shall 605 include tracking, providing detailed recommendations to close all assigned action 606 items from DULL SWORD Deficiency Reports, High Accident Potential (HAP) 607 Report, Safety Investigation Board (SIB) Reports, Operational Review Board 608 (ORB) Reports, Potential Code Compromise (PCC) Reports, Code Related Event 609

(CRE) Reports and Contractor‟s Corrective Action Plan. The actions will be used 610 to develop ICBM trend data to identify and correct problems before they 611 occur/reoccur. 612

1.6.1.1.2.4.2 Special ICBM test and maintenance programs such as Rivet MILE, HSEP, and 614 SELM test or other special test or maintenance action required in the operational 615

ICBM fleet. Support shall include development of assessments, reports and 616 briefings to verify compliance with applicable AFI 91 series IAW Compliance of 617

Nuclear Surety & Safety Support to AFI 91 Series Policies. 618

1.6.1.1.2.4.3 Working groups. These include: Program IPTs, AFNWC/NWIEV Safety IPTs, 620

ICBM POG (Project Officers Working Group), ICBM Codes Conference. 621 Support shall include developing working group Meeting Agendas, preparing and 622 consolidating Briefing Materials from other ICBM SPO IPTs, engineering 623 assessments or answers to assigned ICBM SPO action items and reporting to the 624 Government via Engineering Assessments for Working Groups, and providing 625

Meeting Minutes to participants. 626

1.6.1.1.3 Ground Safety Program: 628

The contractor shall support the ICBM Program Office Ground Safety program. This 629 support shall include: 630

- Mishap investigation support IAW Mishap Risk Assessment Report (MRAR) 631

- Operational safety inspection 632

- Operational hazard identification, mitigation and closure IAW System Safety 633

Hazard Analysis Report (SSHAR) 634 -Trend Analysis and reporting 635 -Accident/Incident Report 636

1.6.1.1.4 Evaluate Systems Effectiveness: 638

The contractor shall lead and coordinate a Weapon System Performance Assessment Team. The 639 team will consist of subsystem contractors and ISC experts to perform Minuteman flight system 640 modeling in the following modeling categories: Earth Coordinates, Aerodynamics, Missile 641 Separation, Gravity, Post Boost Reentry Drag, Structural Dynamics, Flight Dynamics, 642 Atmosphere, Chaff Deployment, Propellant Residual, Climatology, RV Reentry, Boost Steering, 643 Propulsion, IM-Flight, Coordinate Systems, Mass Properties*, Control Systems, Guidance 644 Computer, and Parameter Perturbation. Models shall be maintained current, run when new data 645 is available, and used to evaluate flight test results, trends, and system reliability. The contractor 646

Page | 19 shall assemble subsystem inputs and any system-level analysis into the final engineering report 647 via Service Engineering Report (SER). Other models shall be developed if required to evaluate 648 test data and predict system and component performance. Higher level system models will be 649 required to effectively perform telemetry data evaluation, simulate flight performance, and 650 integrate output from other models. 651 (Note*: Mass properties includes a database of component and system mass properties and a 653 model capable of predicting the weight and center of gravity of the flight vehicle at any time 654 during flight.) 655

1.6.1.1.4.1 The contractor shall serve as a technical expert on the integration of the overall 656 weapon system. The contractor shall also provide expertise in individual subsystem areas to 657 assist the Government in assessing the impact of subsystem results at the weapon system-level 658 while avoiding any duplication of subsystem contractor efforts. The contractor shall, with input 659 from IPTs/subsystems, maintain a database of all Air Vehicle Equipment down to the 660 Configuration Item level and be able to evaluate the availability and reliability of any specific 661 missile configuration in the field. 662

1.6.1.1.4.2 The contractor shall continually evaluate reliability and potential problem areas and 664 shall generate and present the annual Weapon System Effectiveness Report (WSER) and meet 665 with the Government, to include the SPO and AFGSC, to discuss and evaluate those findings. 666

1.6.1.1.4.3 Post flight, the contractor shall lead and coordinate a team including subsystem 668 contractors to reduce flight data and evaluate system-level performance using models such as: 669 Earth Coordinates, Aerodynamics, Missile Separation, Gravity, Post Boost Reentry Drag, 670

Structural Dynamics, Atmosphere, Chaff Deployment, Propellant Residual, Climatology, RV 671

Reentry, Boost Steering, Propulsion, IM-Flight, Coordinate Systems, Mass Properties, Control 672

Systems, and Guidance Computer. If model results differ from actual performance and mass 673 properties, the contractor shall evaluate the flight to determine whether the differences lay with 674 flight performance anomalies or inaccuracies in the models. After the flight, the contractor shall 675 assemble subsystem inputs and any system-level analysis into the final, deliverable performance 676 report which shall be published and models updated if necessary. An overall weapon system 677 effectiveness report shall be assembled, including subsystem inputs, presented to the SPO and 678 AFGSC, and published annually. 679

1.6.1.1.5 Risk Management and Technical Weapon System Analysis: 681 The contractor shall, in coordination and cooperation with IPTs and subsystem contractors (after 683 subsystem contract awards), implement and maintain a Risk Management Program IAW 684

Weapon System Risk Management Plan to identify and assess risks that could have negative 685 impact to the weapon system, plan to mitigate their chance of occurring or the consequence 686 should they occur, and manage risks to a successful resolution. The contractor shall ensure all 687 risk management activities clearly state the adverse weapon system condition which is being 688 considered. Each set of mitigation actions recommended shall reflect the expected reduction in 689 risk on a realistic program schedule. The contractor‟s risk management program shall replace 690 the ICBM SPO risk management program currently employed through IPIC and shall 691 incorporate risks opened by subsystem contractors. Risk management shall include participating 692

Page | 20 in or performing force impact studies, performance effectiveness evaluations, performance and 693 flight analysis, risk assessment, and risk mitigation. The contractor shall follow the standardized 694 DoD process to ensure consistent and thorough identification, assessment, mitigation, 695 management, and reporting of risks IAW Mishap Risk Assessment Report (MRAR). Best 696 practices from industry and government shall be used where appropriate. Risk management 697 efforts shall maintain an appropriate balance between risk management and an affordable 698 weapon system Life Cycle Cost. The end goal is to identify risks lead time away from weapon 699 system impact. 700

1.6.1.1.6 System Requirements Analysis and Determination: 702

System requirements are characteristics of the system that identify the accomplishment levels 703 needed to achieve specific objectives for a given set of conditions. Technical requirements are 704 stated in approved specifications. In all cases the contractor shall ensure requirements 705 recommended are the optimum cost effective solution to achieve the required system 706 performance while maintaining nuclear surety. The contractor shall perform the following tasks 707 associated with System Requirements Determination: Requirements Analysis, Requirements 708 Allocation, and Requirements Definition. The contractor, in consultation with the ICBM 709 SPO/SPO Director of Engineering, shall perform translation of system operational and 710 maintenance factors into specific qualitative and quantitative system design requirements using 711 ICBM-HDBK-01 as a reference. Generally, the contractor will allocate weapon system 712 requirements to the appropriate subsystem and allow the subsystem contractors to allocate and 713 define requirements within the subsystem. In these cases, the contractor shall support the SPO in 714 validating and verifying the allocations and requirements are in compliance with system-level 715 performance requirements. In specific cases, the Government could determine that having the 716 subsystem contractor allocate and define requirements within the subsystem could create an 717

Organizational Conflict of Interest in implementing the change or modification. In these cases, if 718 directed by the Government, the contractor shall perform the allocation and requirements 719 definition even at the subsystem-level. Logical functional analysis and allocation processes 720 shall be used to determine system requirements IAW Systems Requirement Document (SRD). 721 SRD performance will include, at the system-level generally or subsystem-level only if a 722 potential OCI situation exists as described previously, the determination of: 723

1.6.1.1.6.1 Functional requirements--The necessary system tasks, actions, or activities that must 724 be accomplished 725

1.6.1.1.6.2 Design requirements--The “build to”, “code to”, and “buy to” requirements for 727 products. 728

1.6.1.1.6.3 Process requirements--The “how to execute” requirements for processes. 730

1.6.1.1.6.4 Performance requirements-The quantitative measures characterizing physical or 732 functional attributes relating to execution of a mission or function. This includes 733 quantity, quality, coverage, timeliness, and readiness. Performance requirements are 734 initially defined through requirements analyses and trade studies using customer 735 need, objective, and or requirement statements. They are defined for each identified 736

Page | 21 customer mission and for each identified function as required. They are assigned to 737 lower level systems functions through top down allocation, and are assigned to 738 system elements, configuration items and the system through synthesis (the 739 translation of functions and requirements into possible solutions, resources, and 740 techniques, satisfying basic requirements). They are found in ICBM-HDBK-01. 741

1.6.1.1.7 Recommendation of Requirements: 743

The contractor shall make System Level Requirement Recommendations for Government 744 approval and shall support the SPO in evaluation of subsystem contractor requirements 745 recommendations. The contractor shall also make recommendations for subsystem requirements 746 if the Government determines a subsystem contractor would have an OCI by making the 747 recommendation. The recommendations will be developed through continuous monitoring of the 748 weapon system using formal assessment and surveillance programs in conjunction with direct 749 interface with users. Requirements are determined in support of buy and repair responsibilities. 750 This activity includes recommending requirements for: 751

1.6.1.1.7.1 Depot maintenance conversion of repairable assets to serviceable assets. 752

1.6.1.1.7.2 Materials and parts to support the maintenance process. 754

1.6.1.1.7.3 Field…