Sec_J_Attch_2_Guidance_SSC_PWS_11_Feb_14.docx

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

GUIDANCE SUBSYSTEM SUPPORT CONTRACT (SSC)

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

ICBM Flight Systems Division (AFNWC/NIB) ICBM Guidance Branch (AFNWC/NIBA) 11 February 2014

Page | 97

TABLE OF CONTENTS

SECTION I - DESCRIPTION OF SERVICES

1.0 SCOPE

1.1 PURPOSE

The purpose of this document is to provide a description of the types of sustainment services the Guidance Subsystem Support Contract (Guidance SSC) contractor will perform, not to specify to the contractor how to perform required services. It is in no way intended to stifle innovative ideas or approaches for performing required services. Unless otherwise stated, the use of “contractor” refers to the Guidance SSC contractor. All references to other contractors will be specifically stated (e.g., Integration Support Contract (ISC) contractor, other subsystem contractors, etc.)

1.2 Subsystem Description

The Guidance Subsystem will include the following:

Missile Guidance Set (MGS) and components Operational and support equipment software Performance Assessment Data System (PADS) and Central Data Assessment System (CDAS) Mod 7 Instrumentation Wafer and ancillary equipment Instrumentation Wafer Replacement Program (IWRP) Flight termination systems Range tracking systems Telemetry systems Tests and support equipment Launch Support System/Support of launch countdown command and control Global Positioning System (GPS) Metric Tracking System Vandenberg Working Group

1.3 BACKGROUND

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

The Minuteman III (MMIII) is a mature weapon system that is in the Operations and Support Phase of its life cycle. The primary ICBM 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, if required. Top-level system performance parameters that reflect the adequacy of the ICBM force readiness are availability, reliability, accuracy, and hardness. Weapon system sustainment includes:

Incorporation of changes to ICBM systems in response to requirements for performance improvements To make appropriate use of advances in technology Correction of system deficiencies Determining the need for and executing life extension programs Implementation of policies mandated by Congress or directed by other higher authorities Addressing threat or safety driven changes or other changes in the operational or support environment Requirements for changes or modifications to fielded systems are usually applicable at the subsystem or lower-level and will be performed primarily by the subsystem contractors. Satisfying these requirements involves acquisition activities that can potentially impact system-level performance. The ICBM Systems Directorate (ICBMSD), with support from the contractor, will manage the contracts required to integrate and incorporate changes and modifications, and sustain ICBM systems.

The contractor will assist the Government in its performance of tasks associated with Engineering and Program Management Support services referenced above. The primary focus will be to ensure any modifications or changes to the system will maintain and/or improve system-level performance. Successful accomplishment of these tasks will ensure an effective process for:

Weapon system and subsystem performance assessment Systems requirements determination and management Trade studies Subsystem/item specifications Configuration management and control Test and evaluation The application of streamlined program management support techniques Maintaining and assessing weapon system survivability Risk management As the ICBM force continues to age and is modified and upgraded, opportunities for changes in capability and performance effectiveness are introduced. At the subsystem/system-level, numerical values have been established for availability, reliability, and accuracy. The actual numerical values are outside the classification scope of this document and will not be specified herein. Hardness is specified at the subsystem-level and there are no numerical threshold values established at the system-level for this performance parameter. Hardness performance is based on subsystem analysis and testing. Reporting of hardness will be provided by the ICBM Integrated Product Team (IPT) organizations of the Ground, Guidance, Propulsion, and Re-Entry System/Re-Entry Vehicle (RS/RV) Subsystems. These parameters represent performance values below which the system cannot be allowed to fall unless coordinated decisions are made to allow such degradation based on funding and program considerations.

1.4 Future ICBM Sustainment and Acquisition Construct (FISAC) Description The ICBMSD has prepared a sustainment concept to ensure a safe, secure, and reliable MMIII weapon system through 2030. This activity, designated the FISAC, will replace the IPIC which ended 30 September 2012 and is described in detail below.

1.4.1 FISAC Structure

Figure 1. is a graphical representation of the FISAC structure. The Technical (Tech) Council is not in the management chain. The box associated with the Tech Council identifies further details of the Tech Council. The box containing “Other ICBMSD led efforts” shows that the ICBMSD has other direct contracts supporting the ICBM weapon system.

Figure 1. FISAC Structure

1.4.2 FISAC Working Relationships

Figure 2. shows major functions of the ISC, ICBMSD, and subsystem contractor.

ICBM Systems Directorate Function: Weapon System Integrator BM Systems Directorate Function: Weapon System Integrator C ICBM Sy IC ICBM Systems Directorate Function: Weapon System Integrator BM Systems Directorate Function: Weapon System Integrator stems Directorate Function: Weapon System Integrator BM Systems Directorate Function: Weapon System Integrator ICBM Systems Directorate Function: Weapon System Integrator

Figure 2. FISAC Component Functions

1.4.3 Guidance SSC Contractor/ICBMSD Relationship

The MMIII Guidance SSC contractor will assist the Government in fulfilling its role as the Guidance Subsystem Program Manager in Subsystem Assessment, Sustaining Engineering, and Program Management Support. The Guidance SSC contractor will also help transfer industrial ICBM technical expertise and knowledge to the ICBM organic workforce. The Guidance SSC 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 Guidance Subsystem. This contract will be flexible and allow for adjustments to the contractor workforce to gain efficiencies based on the changing requirements, policy, realities of the industrial base, and the Government’s capability to support MMIII.

1.4.4 Guidance SSC Contractor/ISC/ICBMSD Relationship

The subsystem support contractors provide the preponderance of sustaining engineering support to the subsystems. The ISC provides sufficient subsystem expertise to validate subsystem contractor analyses and produce requirements and other documents for subsystem acquisitions that would create an OCI if produced by the subsystem contractor. As Guidance Subsystem programs are initiated, new Contract Line Item Numbers (CLINs) will be added to the ISC for ISC tasks that specifically support those programs. This is required to ensure the proper appropriations are used and each program funds the additional support required.

In order to competently and conscientiously support MMIII, the USAF 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 will need to 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 achieve this, the Guidance SSC contractor will have appropriate Non-Disclosure Agreements (NDAs) with the ISC contractor. The Guidance SSC contractor must demonstrate the ability and willingness to communicate openly. The ISC will not provide contractual direction to Government contractors not subcontracted with the ISC. Likewise, the Guidance SSC contractor shall only provide contractual direction to contractors subcontracted with the Guidance SSC.

1.4.5 Guidance SSC Contractor/Guidance Repair Contractor Relationship Guidance repair is accomplished on a separate contract. The contractor will support repair in accordance with (IAW) 1.6.2.5 and 1.6.3.3.13 and have Guidance SSC team members on-site at the Guidance repair facility, whose supervisory channels avoid possible OCI concerns. To achieve this, the Guidance SSC contractor will have appropriate NDAs with the Guidance repair contractor. The Guidance repair contractor will not provide contractual direction to Government contractors not subcontracted with Guidance repair. Likewise, the Guidance SSC contractor shall only provide contractual direction to contractors subcontracted with the Guidance SSC.

1.4.6 Technical Council

The contractor will be a key participant on the ICBM Technical Council. The ICBMSD establishes and chairs this council which will meet at a minimum semi-annually and maximum quarterly, as determined by the Director, ICBMSD, and be comprised of contractor and ICBMSD representatives from each of the subsystems. The Technical Council will provide a forum where the ICBMSD and key suppliers at various levels can directly, and on an equal level, engage on issues important to ICBM systems.

1.4.6.1 Government Members

Director, ICBMSD (Chair), Director of Engineering (Alt Chair), Chief Engineer, ICBM Flight Systems, Chief Engineer, ICBM Ground Systems, Chief Engineer, Systems Engineering. 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), AFNWC Logistics Directorate (AFNWC/LG), AF Program Executive Officer, Strategic Systems (AFLCMC/SS), 309th Maintenance Wing, and others as determined appropriate by the ICBMSD.

1.4.6.2 Associate Government Members

Associate Government members are designated by the relevant IPT Chief or Director of Engineering.

1.4.6.3 Contractor Primary Members:

Contractor primary members are ISC, Guidance Subsystem, Ground Subsystems, Propulsion Subsystem, Reentry System/Reentry Vehicle Subsystem, and F-900 contractors.

1.4.6.4 Associate Contractor Members

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

1.4.6.5 Ground Rules

Meetings of the ICBM Technical Council are expected to be a place of frank and open discussion of ICBM issues. Classified discussion at the SECRET level may occur, requiring proper visitor clearances be on file with the ICBMSD security office. The Technical Council is not intended to be a decision making body, nor does it provide contractual direction. 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. Topics for discussion will be prioritized by the Director of Engineering. The Director of Engineering reserves the right to defer topics to another meeting to maintain focus on priority topics. Each meeting will allow time for review of all action items to ensure the proper personnel are assigned and aware.

1.4.6.6 Administration

The ICBMSD Director of Engineering is the process owner of the ICBM Technical Council. Technical Council meetings will initially be held semi-annually. The frequency and duration of meetings will be adjusted by the ICBMSD Director of Engineering in consultation with the Director, ICBMSD and the ICBM Technical Council members as the forum matures.

1.4.7 Subsystem Contractors

Each subsystem sustainment contract in the FISAC shall include the sustaining engineering support for that subsystem and any relevant sustainment support tasks required to sustain the subsystem that are not accomplished on a different contract or by an organic entity. For example, repair of the MGS is accomplished on a separate Government contract to the Boeing Guidance Repair Center (or its replacement), which also includes inertial instrument repair for other weapon systems. Support and test equipment programs, modifications, and subsystem integration of weapon system modifications may also be performed on the Guidance SSC, as long as the dollar threshold for the contract is not exceeded. Software Independent Verification and Validation (IV&V) will be managed under a separate contract with Nuclear Safety Cross Check Analysis (NSCCA) and the Performance Analysis Technical Evaluation (PATE) contractor. Major modifications, such as Gyro Stabilized Platform replacement, will be separately competed as these programs will be Acquisition Category (ACAT) 1D programs and are likely to provide an opportunity for innovation from the larger industrial base to improve weapon system performance. ACAT 1D programs may not be executed under the Guidance SSC. However, subsystem integration support of ACAT 1D programs may be executed under the Guidance SSC. ACAT II and ACAT III programs and non-ACAT efforts may be executed under the Guidance SSC.

1.4.8 Special Considerations

The contractor and other FISAC subsystem contractors will need to act in cooperation with the ISC and the Government for the overall success of the total weapon system integration. The contractor will be required to negotiate appropriate NDAs with all FISAC subsystem contractors, Guidance repair contractor, and the ISC contractor so that information needed in support of ICBM weapon system can be freely shared between the subsystem contractors and the ISC contractor. While the contractor maintains a close relationship with the ICBMSD, neither the ISC nor the subsystem contractors are allowed to perform inherently governmental functions. The responsibility to direct other contractors and ultimately approve or disapprove reports and other products remains with the ICBMSD.

1.5 APPLICABLE DOCUMENTS

1.5.1 Compliance and reference documents related to specifications, standards, handbooks, regulations, instructions and tables applicable to the work required in the performance of this contract are listed in APPENDIX F: APPLICABLE DOCUMENTS. If vendors are knowledgeable of critical documents or requirements not listed in this draft PWS, it is expected they inform the Government to ensure adequate coverage.

1.5.2 The contractor will be responsible for using the latest version of compliance documents.

1.6 Requirements summary

Guidance Subsystem Sustainment The service requirements described in this section are intended to describe the scope of the effort necessary to sustain the Guidance Subsystem to be executed for this contract. Capabilities may be applied to future planning and analysis, applications programs, technology insertion, major modifications competed separately from the FISAC contracts, integration, or analysis for a follow-on system. Use of the Guidance SSC capabilities for future Guidance-related efforts would be incorporated as add-on CLINs as the tasks and/or funds are identified and available. The contract decision-point for future efforts will be at each respective acquisition planning meeting required by the AF Acquisition Process.

The Government does not own a complete data package for the Guidance Subsystem. In order to perform the requirements of the Guidance SSC, the contractor shall secure access to the required data or develop Government-approved solutions to data deficiencies (such as reverse engineering).

Basic Services

1.6.1.1 Integrated Product Team (IPT) Support

1.6.1.1.1 The contractor shall support the Guidance IPT according to the Work Breakdown Structure (WBS) in Appendix E, and will support the Government and ISC who are responsible for weapon system-level engineering and program management support.

1.6.1.1.2 The contractor shall coordinate and integrate with other Government ICBM IPTs, including Battery IPT, Software IPT, Ground IPT, and the Systems Engineering Level Evaluation and Correction Team (SELECT) as directed by the Government.

1.6.1.2 Functional Areas

The contractor role is to support the Government in the following functional areas: sustaining engineering and any relevant operations and maintenance (O&M) support tasks required for the Guidance Subsystem and are not accomplished on a different contract or by an organic entity.

1.6.1.3 Compliance

The contractor shall interface with official Government systems and databases to ensure compliance with the most current and accurate source/requirement documentation. This includes, for example: Life Cycle Management Plans, specifications, drawings, process orders, and technical orders.

1.6.1.4 Security Access

Due to the evolving nature behind Government information systems, a full access list is not provided within this document. The contractor responsibilities include coordinating with the Government and ICBMSD Security Manager to ensure its relevant personnel attain appropriate access levels to the applicable information systems. Access to Government information systems shall be restricted to contractor personnel requiring access to accomplish their primary Guidance SSC responsibilities and as documented in their DD Form 254, Department of Defense Contract Security Classification Specification.

1.6.1.5 Repair Support

The Government is responsible for depot maintenance and depot support of field level maintenance (i.e., technical data, support equipment management, engineering, and technical support for field problems, and training). The contractor shall support the Government in providing assistance to the Guidance repair contractor in repair efforts to Guidance components. These efforts include but are not limited to:

Failure Analysis Parts Evaluation Supporting documentation Multiple repair options when requested by the Government An initial assessment of the technical risks associated with the various repair options, including a use-as-is (non-repair) option Technical

1.6.1.6 Transition

1.6.1.6.1 The contractor shall cooperate with the Government, Partial Bridge Contract (PBC), Mod 7 Production contract (for required Government-furnished equipment (GFE) needed for the IWRP), and ISC contractors in order to ensure a smooth and seamless transition of support for the MMIII Weapon System from the PBC and Mod 7 Production contract to the contractor and Government.

1.6.1.6.2 Immediately following contract start date, the contractor shall meet with the Government (with ISC support), PBC, and the Mod 7 Production contractor to jointly plan transition of relevant workload or GFE from the PBC and Mod 7 Production contract to the contractor and Government.

1.6.1.6.3 The contractor shall submit the Guidance SSC Transition Plan and have it approved by the Government IAW CDRL A002, DI-MGMT-80790/T, Transition Plan.

1.6.1.6.3.1 The Transition Plan shall include a Transition schedule IAW CDRL A002, DIMGMT80790/T, Transition Plan, detailing identification, impacts, and mitigation(s) for on-going Guidance Subsystem efforts. The contractor, PBC, and Mod 7 Production contractor shall execute the Transition Plan and complete transition of all tasks not later than 6 months after the Contract Post Award Conference.

1.6.1.6.3.2 The contractor’s Transition Plan shall include all Government-furnished property (GFP) and tools used in the execution of sustainment and support for the subsystem and identify, at a minimum, the tasks to be transferred, the entrance and exit criteria for each task, the responsible person for the respective contractors, and the schedule for achieving transfer of responsibility. [CDRL A133, DI-MGMT-80004A/T, Hardware Movement Request Process (subtitle)]

1.6.1.6.3.3 The contractor shall present any issues regarding the transfer of data, data rights, tools, and models used in the execution of sustainment with recommended mitigation strategy to the Procuring Contracting Officer (PCO) for equitable resolution. [CDRL A039, DIMISC80508B/T, Data Transition & Hosting Plan (subtitle)]

1.6.1.6.3.4 The contractor is responsible for providing all facilities, including facilities for housing and operating the Guidance Subsystem GFP. If the contractor proposes alternative tools, models, equipment, etc., in supporting weapon system sustainment and acquisition; the verification, validation, and accreditation (VV&A) of those items must be included in the Transition Plan.

1.6.1.6.3.5 The contractor shall identify the risks for transitioning Guidance Subsystem tasks or GFE from the PBC and Mod 7 Production contract to the Guidance SSC/Government and provide ranking of the identified risks and the criteria used. The Transition Plan shall include recommended mitigation strategies to overcome the identified transition risks.

1.6.1.6.4 The contractor shall document responsibility transfer for each task with the PBC and Mod 7 Production contractor and Government. A copy of the transfer documents shall be provided to the Government PCO.

1.6.1.6.5 The contractor shall meet with the Government on an agreed upon schedule (weekly) to review, report status, track progress, and update the Transition schedule until transition is complete.

1.6.1.7 Guidance Subsystem Assessment

The contractor shall assess the “health” of the MMIII Guidance Subsystem in coordination with their Government counterparts and provide the assessment products and reports to the Government on a schedule coordinated to meet system-reporting requirements. [CDRL A017, DI-MISC-80508B/T, MGS Daily Status (including MGS Rejection Summary and MGS Field Deployment) (subtitle)] [CDRL A018, DI-MISC-80508B/T, Operational Test Launch MGS Daily Status (subtitle)] [CDRL A019, DI-MISC-80508B/T, Health of the Subsystem & Subsystem Assessment (subtitle)] [CDRL A030, DI-MISC-80508B/T, Special Studies & Analysis (subtitle)] [CDRL A132, DI-MGMT-80004A/T, Life Cycle Sustainment Plan (subtitle)] [CDRL A136, DI-RELI-80254, Corrective Action Plan] [CDRL A137, DI-RELI-80255, Failure Summary and Analysis Report]

1.6.1.7.1 Operational Readiness Assessments

The contractor shall support the Government in assessment of Guidance operational readiness. Measures that are used for operational assessment include: nuclear hardness and survivability, accuracy, reliability, availability, maintainability. Assessment activities include: anomaly resolution, trend analysis, and mass properties.

1.6.1.7.2 Nuclear Hardness and Survivability

1.6.1.7.2.1 The contractor shall assist the Government in assessing modifications, maintenance actions, and impacts on nuclear hardness and survivability.

1.6.1.7.2.2 The contractor shall support Government and ISC nuclear hardness and survivability assessments, evaluation of change proposals, and recommendation of nuclear hardness and survivability related changes to the Guidance Subsystem.

1.6.1.7.2.3 The contractor shall submit updates to the hardness data manual to reflect approved nuclear hardness and survivability related changes to the Guidance Subsystem. [CDRL A032, DI-MISC-80508B/T, Hardness Data Manual (subtitle)] [CDRL A112, DI-ENVR-80266, Nuclear Hardness and Survivability Design Analysis Report]

1.6.1.7.2.4 The contractor shall support hardness surveillance of the Guidance Subsystem, including the NS-50 Hardness Surveillance Program.

1.6.1.7.2.5 The contractor shall ensure all products provided to the Government under the Guidance SSC are compliant with MIL-STD-461, Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment.

1.6.1.7.3 Accuracy

The contractor shall assist the Government in assessing mission accuracy. This includes accuracy analysis on selected flights, management, and periodic reporting of the guidance error model, error budget, and capability estimate; and assessment of specific error contributors including their causes, measurement capability, reliability, and reporting IAW CDRL A021, DIMISC80508B/T, Guidance Accuracy Report Error Model/Error Budget/Capability Estimate, CDRL A060, DI-MISC-80508B/T, Flight Accuracy Evaluation (subtitle), CDRL A136, DI-RELI-80254, Corrective Action Plan, CDRL A137, DI-RELI-80255, Failure Summary and Analysis Report.

1.6.1.7.4 Reliability

1.6.1.7.4.1 The contractor shall assist the Government in assessing mission reliability.

1.6.1.7.4.2 The contractor shall assist the Government in providing an accurate, cost-effective evaluation of MMIII Guidance-related system and component reliability.

1.6.1.7.4.3 The contractor shall assist the Government in flight tests and correlating data collecting and processing.

1.6.1.7.4.4 The contractor shall review and analyze test data to determine if there are adverse trends.

1.6.1.7.4.5 The contractor shall assist the Government in ensuring data is added to a Government approved, interface-friendly central database for future analysis.

1.6.1.7.4.6 The contractor shall conduct failure modes and effects analyses (FMEA) on system hardware to determine what failures could occur and the effect such failures would have on the weapon system. The FMEA shall also include sneak circuit analysis and worst-case analysis. [CDRL A023, DI-MISC-80508B/T Tradeoff Studies & Analysis]

1.6.1.7.5 Availability

The contractor shall assist the Government in calculating: percentage of available Guidance Subsystems; mean time between failures (MTBF); operational hours; operational and nonoperational rejections (including normal timers, zero timers, and short timers); rejections by wing and by symptom; startup rejections; repeat rejection symptoms average rejections per month; serviceable spares at operational wings; and mean time between recycles (MTBR). [CDRL A017, DI-MISC-80508B/T, MGS Daily Status (including MGS Rejection Summary and MGS Field Deployment) (subtitle)] [CDRL A025, DI-MISC-80508B/T, Monthly MGS Summary (subtitle)] [CDRL A029, DI-MISC-80508B/T, MGS Diagnostic Information Document Recommendations (subtitle)]

1.6.1.7.6 Maintainability

1.6.1.7.6.1 The contractor shall assist the Government in improving the ease and efficiency with which servicing, preventive, and corrective maintenance can be conducted.

1.6.1.7.6.2 The contractor shall address maintainability for future modification and replacement programs.

1.6.1.7.6.3 The contractor shall consider maintainability improvements when the opportunity exists to change depot processes and products.

1.6.1.7.7 Anomaly Resolution

The contractor shall assist the Government in resolving anomalies, utilizing analysis, historical data, trending data, drawings, available MM original build data and design data, simulations, models, and other tools, and testing at Government facilities to include the Strategic Missile Integration Complex (SMIC) and Little Mountain Test Facility (LMTF). [CDRL A059, DI-MISC-80508B/T, Flight Investigation/Anomaly Report (subtitle)]

1.6.1.7.8 Trend Analysis

The contractor shall review, provide service life assessments, and detect trends as early as possible, using the following data sets and test results: flight test results, operational wing inertial measurement unit performance data, Vandenberg AFB (VAFB) pre-flight test data, postmortem analysis, and depot repair data. [CDRL A024, DI-MISC-80508B/T, Trend Analysis (subtitle)] [CDRL A028, DI-MISC-80508B/T, Inertial Measurement Unit Performance Data Diagnostic Information Document for Minuteman III Missile Guidance Sets (subtitle)] [CDRL A046, DI-MISC-80508B/T, Service Life Assessment Report (SLAR) (subtitle)]

1.6.1.7.9 Mass Properties

1.6.1.7.9.1 The contractor shall conduct mass properties analysis. Results of the analysis shall be delivered IAW CDRL A033, DI-MISC-80508B/T, Mass Properties Analysis Report (subtitle). Coordinate with ISC contractor to ensure the results delivered are in a format that is compatible with Government approved, interface-friendly database.

1.6.1.7.9.2 The contractor shall develop and maintain models for mass properties analysis as directed by the Government. The contractor shall deliver models IAW CDRL A067, DI-SESS-81000E/T, Product Drawings/Models and Associated List.

1.6.1.7.10 Subsystem Component Assessment

The contractor shall identify, as a candidate for assessment, any component of the Guidance Subsystem that may affect weapon system performance that is launch essential or mission critical. Assessment areas shall include accuracy, hardness surveillance, availability, and reliability.

1.6.1.7.11 Systems Requirements Determination

1.6.1.7.11.1 The contractor shall provide systems requirements determination inputs upon Government request to support weapon system-level Government requirements determination efforts. [CDRL A020, DI-MISC-80508B/T, System/Subsystem-Level Requirements Recommendations (subtitle)]

1.6.1.7.11.2 The contractor shall assist the Government with processes and procedures required to test, monitor, analyze, evaluate, and report capabilities of the Guidance Subsystem or Guidance Subsystem-related components.

1.6.1.7.11.3 The contractor shall provide input to the Government on current and projected condition of the Guidance Subsystem and recommended actions required to maintain operational readiness. Items with adverse conditions (i.e., insufficient spares, excessive downtime, and decreasing MTBF) or increasing failure trend shall be reported. This information shall be consolidated into annual subsystem Weapon System Effectiveness Report (WSER) inputs and Guidance Minuteman III Weapon System Effectiveness Data Book. [CDRL A019, DI-MISC-80508B/T, Health of the Subsystem & Subsystem Assessment (subtitle)] [CDRL A043, DI-MISC-80508B/T, Guidance Weapon System Effectiveness Data Book (subtitle)]

1.6.1.7.11.4 The contractor shall conduct continual evaluations to determine which materials or components change with age and the likelihood of failures resulting from continued use of aged materials or components. [CDRL A047, DI-MISC-80508B/T, Aging Surveillance Plan (subtitle)]

1.6.1.7.12 Determine Accomplishment of Specified Requirements The contractor shall assist the Government in assessing whether or not the assessment requirements listed in paragraph 1.6.3.2 have been adequately satisfied. This assistance may include testing, performance monitoring, modeling, simulation, and analyses as required.

1.6.1.8 Sustaining Engineering

1.6.1.8.1 Sustaining Engineering Requirements

1.6.1.8.1.1 The contractor shall transform Government identified operational need(s) into a description of system performance parameters and a preferred system configuration through the use of an iterative process of functional analysis, synthesis, optimization, definition, design, modeling and simulation, test, and evaluation.

1.6.1.8.1.2 The contractor shall develop, maintain, and implement an integrated Systems Engineering Management Plan (SEMP) across their program team (including subcontractors). 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. The SEMP shall be maintained consistent with other contractor plans (e.g. Risk Management Plan, Software Development Plan (SDP), Configuration Management Plan, Test Plans, Data Management Plan, Contractor’s Corrective Action Plans, etc.) and integrate related technical parameters and assure compatibility of all physical, functional, and program interfaces in a manner that maintains efficient total Guidance Subsystem definition and design. [CDRL A065, DI-SESS-81785/T, Systems Engineering Management Plan (SEMP)]

1.6.1.8.1.3 The contractor shall integrate reliability, maintainability, logistics support, safety, producibility, security, survivability, structural integrity, human factors, and other related specialties into the total Guidance engineering effort.

1.6.1.8.1.4 The contractor shall assist the Government in assessing deficiency indicators, defining the characteristics and causes of deficiencies, determining the impact on the affected product, identifying and evaluating alternative solutions, determining the preferred solution, and designing, integrating, and validating the solution. [CDRL A113, DI-ALSS-81535 & Ref: T.O. 00-35D-54, Deficiency Report (DR)] [CDRL A132, DI-MGMT-80004A/T, Life Cycle Sustainment Plan (subtitle)] [CDRL A136, DI-RELI-80254, Corrective Action Plan] [CDRL A137, DI-RELI-80255, Failure Summary and Analysis Report]

1.6.1.8.1.5 The contractor shall perform technical services to support the Government and ISC Program Managers in their systems engineering responsibilities, in the following areas:

Integration Test and Evaluation (T&E) Force Development Evaluation (FDE) support Hardware Software Guidance Subsystem/end item specifications Operational safety, suitability, and effectiveness (OSS&E) Determine support requirements Trade studies Field support TO support Maintenance support Disposal Nuclear surety Configuration management

1.6.1.8.2 Integration

1.6.1.8.2.1 The contractor shall fully support and adequately staff all Guidance Subsystem integration efforts by performing activities to include: assessing and managing requirement changes; addressing and documenting internal and external interfaces; designing, testing and integrating, and validating hardware, software, and documentation changes; accomplishing all associated verification and validation activities, as directed by the Government; and supporting integration working group meetings as defined elsewhere in the PWS.

1.6.1.8.2.2 The contractor shall collaborate with the Government, ISC, PBC, and all other subsystem contractors in the process of ensuring full compatibility with the subsystem and the weapon system.

1.6.1.8.2.3 The contractor shall assess all modifications to include replacements, life extensions, and any changes proposed by the contractor or their subcontractors for any potential integration impact(s) on the subsystems or the weapon system as a whole.

1.6.1.8.2.4 The contractor shall ensure assessment and analysis of modifications are accomplished by referencing Government integration processes as defined in the following documents: ICBMSD Operating Instruction (OI) 62-08, Requirements Validation Board; ICBMSD OI 6319, Data Management; and all other relevant systems integration guidance that may apply at a future date.

1.6.1.8.2.5 The contractor shall proactively engage with the Government, ISC contractor, other subsystem contractors, and those contractors awarded future modification efforts to ensure any proposed modifications to include replacements, life extensions, and any changes will not have any negative impact on the subsystem or the weapon system as a whole.

1.6.1.8.2.6 The contractor shall establish NDAs with the ISC contractor and the other subsystem and acquisition contractors, as required, to enable successful integration efforts.

1.6.1.8.2.7 The contractor shall be a technical expert on the integration of the various components within the Guidance Subsystem.

1.6.1.8.2.7.1 The contractor shall successfully integrate within the Guidance Subsystem to include hardware, software, interfaces, aerospace vehicle equipment (AVE), and support equipment.

1.6.1.8.2.7.2 The contractor shall be knowledgeable on the overall Guidance Subsystem so that changes, issues, and problems that could potentially affect another part of the Guidance Subsystem shall be realized, assessed, and resolved.

1.6.1.8.2.7.3 The contractor shall act in cooperation with the Government, original equipment manufacturers, Guidance repair contractor, and other contractors as needed to successfully resolve Guidance Subsystem integration issues.

1.6.1.8.2.8 The contractor shall be a technical expert on the integration of the Guidance Subsystem with the overall weapon system.

1.6.1.8.2.8.1 The contractor shall successfully integrate the Guidance Subsystem (to include hardware, software, interfaces, AVE, and support equipment) with the weapon system.

1.6.1.8.2.8.2 The contractor shall be knowledgeable on the overall weapon system to the extent that Guidance Subsystem’s changes, issues, and problems that could potentially affect the weapon system shall be realized, assessed, and resolved.

1.6.1.8.2.8.3 The contractor shall act in cooperation with the Government, ISC contractor, and other subsystem contractors to successfully resolve integration issues.

1.6.1.8.3 Test and Evaluation (T&E)

1.6.1.8.3.1 The contractor shall provide technical support to the Government for T&E of both hardware and software associated with the Guidance Subsystem. [CDRL A051, DI-MISC-80508B/T, Test & Evaluation Master Plan (TEMP) (subtitle)] [CDRL A086, DI-IPSC-81438A, Software Test Plan (STP)] [CDRL A087, DI-IPSC-81439A, Software Test Description (STD)] [CDRL A088, DI-IPSC-81440A, Software Test Report (STR)] [CDRL A090, DI-MISC-81807, Software/Firmware Change Request]

1.6.1.8.3.2 The contractor shall utilize T&E data to verify the required performance of all critical characteristics of a design solution/product.

1.6.1.8.3.3 The contractor shall support product improvement or modification testing designed to enhance performance, correct identified deficiencies, improve reliability and maintainability, reduce life cycle costs, or ensure reparability.

1.6.1.8.3.4 The contractor shall provide the Government (along with the ISC) Guidance Subsystem-related systems engineering support for the following:

Test requirements Test plan development IAW ICBMSD OI 99-103 [CDRL A061, DI-NDTI-80566A, Test Plan] [CDRL A062, DI-NDTI-80603A, Test Procedure] [CDRL A063, DI-NDTI-80809, Test/Inspection Report] Test integration, scheduling and conduct (execution)

FDE

Simulated Electronic Launch Minuteman (SELM) problem resolution Simulated environment testing

1.6.1.8.3.5 The contractor shall support the Government in assisting AFGSC in performing the following FDE activities:

Report measures of effectiveness.

Address critical operational issues.

Identify and report operational capabilities deficiencies.

Recommend and evaluate changes in Guidance Subsystem configuration.

1.6.1.8.3.6 The contractor shall provide information for developing, assessing, and refining:

Logistics and software requirements Tactics, training techniques, and doctrine Software maturity estimates and supportability Security procedures and countermeasures Operations and support cost estimates Adequacy of technical publications and support equipment Weather and environmental constraints Capability to operate in planned environment System compatibility and interoperability Controls of residual hazards Integration of human factors

1.6.1.8.4 Force Development Evaluation (FDE) Support

The contractor shall assist the Government in supporting the ISC and Government systems engineering in the determination of requirements by providing the following FDE data:

Candidate selection for FDEs [CDRL A052, DI-MISC-80508B/T, MGS Candidate List for Force Development Evaluation Flights (subtitle)] Spares Candidate List [CDRL A053, DI-MISC-80508B/T, MGS Spares Candidate List for Vandenberg AFB (subtitle)] Configuration certification [CDRL A054, DI-MISC-80508B/T, MGS Configuration Certification for Force Development Evaluation Flights (subtitle)] Pre-Flight Reviews [CDRL A055, DI-MISC-80508B/T, MGS Force Development Evaluation T-30 Day Review Evaluation (subtitle)] [CDRL A056, DI-MISC-80508B/T, MGS Force Development Evaluation Pre-Flight Review Evaluation (subtitle)] Post-Flight Reviews [CDRL A057, DI-MISC-80508B/T, MGS Force Development Evaluation Post-Flight Review Evaluation (subtitle)] [CDRL A058, DI-MISC-80508B/T, Flight Performance Reports (subtitle)] FDE Anomaly Investigation [CDRL A059, DI-MISC-80508B/T, Flight Investigation/Anomaly Report (subtitle)] Flight Accuracy Evaluation [CDRL A060, DI-MISC-80508B/T, Flight Accuracy Evaluation (subtitle)]

1.6.1.8.4.1 Operational Test Launches

1.6.1.8.4.1.1 The contractor shall provide support as required for all anticipated Guidance Subsystem flight test programs. [CDRL A018, DI-MISC-80508B/T, Operational Test Launch MGS Daily Status (subtitle)]

1.6.1.8.4.1.2 The contractor shall provide support for all applicable future modification or acquisition programs associated with Guidance Subsystem flight test programs.

1.6.1.8.4.1.3 See 1.6.5 for VAFB Flight Test FDE support.

1.6.1.8.4.2 Simulated Electronic Launch Minuteman (SELM) Testing The contractor shall provide technical support to the Government by assisting in identifying, troubleshooting, and correcting anomalies related to the Guidance Subsystem that occur during SELM testing.

1.6.1.8.5 Hardware

1.6.1.8.5.1 The contractor shall support the Government with hardware analysis, development recommendations, integration, supporting documentation, and technical data. The contractor shall provide [CDRL A114, DI-QCIC-80127A, Government Industry Data Exchange Program (GIDEP) Annual Progress Report] [CDRL A119, DI-MFFP-81403, Corrosion Prevention & Control Plan]:

Hardware upon Government request Depot repair problems evaluation Hardware test and repair Design change degradation assessment Design change integration Environmental assessment Commercial item issue corrosion assessment and recommendations Technical reviews of new materials, processes, and technologies Materiel Review Board (MRB) Parts Working Group

1.6.1.8.5.2 The contractor shall support hardware T&E on existing support and test equipment designed to support Guidance sustainment, including hardware problem evaluation and resolution in support of field/VAFB to include SMIC and LMTF.

1.6.1.8.5.3 The contractor shall support the Government by analyzing failures and planning corrective actions, utilizing closed loop failure analysis methods. [CDRL A044, DI-MISC-80508B, Closed Loop Failure Analysis (subtitle)]

1.6.1.8.6 Software

1.6.1.8.6.1 The contractor shall support the following software applications: operational, support equipment, test equipment, diagnostic, assessment, depot, data production, and data storage.

1.6.1.8.6.2 The contractor shall ensure deficiency tracking capabilities exist for contractor-developed software or Commercial Off-The-Shelf (COTS) software recommendations. The contractor shall track all software change requests IAW CDRL A090, DI-MISC-81807, Software/Firmware Change Request.

1.6.1.8.6.3 The contractor shall support software T&E on existing support equipment designed to support Guidance Subsystem maintenance and/or assessment. The contractor shall deliver software T&E documents IAW CDRL A086, DI-IPSC-81438A, Software Test Plan (STP); CDRL A087, DI-IPSC-81439A, Software Test Description (STD); and CDRL A088, DI-IPSC-81440A, Software Test Report (STR).

1.6.1.8.6.4 The contractor shall support and coordinate with the Government in software analysis, development, integration, and configuration management.

1.6.1.8.6.5 If NSCCA/PATE requirements are levied against any Guidance Subsystem effort, the contractor shall provide support to the Government and the NSCCA/PATE software contractor, who will provide an independent assessment of weapon system software nuclear surety and functionality.

1.6.1.8.6.6 The contractor shall comply with Technical Order (TO) 00-5-16, Software Managers Manual USAF Automated Computer Program Identification Number System (ACPINS).

1.6.1.8.6.6.1 The contractor shall deliver software. The contractor shall deliver Automated Computer Program Identification Number (ACPIN) data IAW CDRL A080, DI-MISC-81454B,…