Updated MMIII Sust DRAFT v2.1.pdf

FA8204-XX-X-XXX

ATTACHMENT 2

MMIII SUSTAINMENT PWS- ISC 2.0

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

INTEGRATION SUPPORT CONTRACT (ISC) 2.0

MMIII SUSTAINMENT- PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM SYSTEMS DIRECTORATE (ICBMSD)

dd MMM 2019

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

1.0 ISC – MMIII SUSTAINMENT

1.1 Scope .................................................................................. Error! Bookmark not defined.

1.2 Purpose ............................................................................... Error! Bookmark not defined.

1.3 Background ........................................................................ Error! Bookmark not defined.

1.4 Requirements Summary ...................................................... Error! Bookmark not defined.

1.5 Property Management ................................................... Error! Bookmark not defined.

1.6 QUALITY ....................................................................... Error! Bookmark not defined.

1.7 Security .......................................................................... Error! Bookmark not defined.

1.8 CYBERSECURITY REQUIREMENTS ............................... Error! Bookmark not defined.

2.0 Appendices

APPENDIX A: ACRONYMS AND ABBREVIATIONS

APPENDIX B: WORK BREAKDOWN STRUCTURE

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT

(GFP/GFS/GFE)

APPENDIX E: CONTRACT DATA REQUIREMENTS LIST (CDRL)

ATTACHMENT 2 MMIII SUSTAINMENT

1. ISC – MMIII SUSTAINMENT SUPPORT SCOPE

a. MMIII Sustainment Branch Description

The MMIII Sustainment Branch ties together the components of the WBS (Propulsion, Guidance, RS/RV, Ground Mechanical, Ground Electrical, and IIE) and Field Support to best sustain product delivery.

b. Branch Structure

The branch falls under the MMIII SPO. It consists of seven sections, each of which includes an

Integrated Product Team (IPT).

The IPTs serve a critical role as integrators between the sections and are organized around Work

Breakdown Structure (WBS) products. They aim to provide a stable approach to problem solving across the weapon system.

Leadership

Section Chiefs serve as IPT Leads for their respective IPTs. They are responsible for product-level priority within their IPTs. They meet with branch leadership regularly to provide their priority recommendations.

Leadership from the three branches in the MMIII SPO are responsible for establishing system-level priorities and articulating branch perspectives while working together to balance system-level requirements. They review, deconflict and prioritize the IPTs’ recommendations.

IPT authority resides with the Sustainment Branch Chief; however, the Branch Chief can choose to delegate their authority to another IPT leader.

IPT Assignments:

Generally, IPT members are assigned as follows:

Sustainment Branch personnel are members of their Section’s IPT.

Acquisition Branch personnel are members of the IPT(s) associated with the content of their acquisition program.

Integration Branch personnel participate in IPT(s) per the IPTs’ need for the high-demand, low-density services provided by the Integration Branch (e.g. Test, Nuclear

Surety, Hardness, etc.).

IPT Leadership holds authority to acquire, release, and/or share assigned members based on organizational priorities.

Horizontal Sharing (e.g. IPT to IPT): assignment may be reallocated due to ad-hoc needs

Vertical Sharing (Branch to Branch within an IPT): Case-by-case personnel reallocation across Branches to align with Branch Leadership’s highest priorities

If personnel are assigned to multiple IPTs, their time is aligned with priorities set by

Division Leadership.

2. OVERARCHING REQUIREMENTS

2.1. General Requirements

2.1.1. All requirements in the Basic PWS of this contract apply to this Task Order

2.1.2. All work shall be performed in coordination and cooperation with pertinent overseeing goverment personnel. (The Gov Program Manager and Engineer are responsible for meeting the program’s cost, schedule, technical and performance objectives. As the system integrator, the Government is the decision authority.)

2.1.3. All work shall be performed in coordination with the Subsystem Support Contractor

(if applicable) and other contracted personnel.

2.1.4. The contractor shall collaborate with appropriate internal and external stakeholders as needed to accomplish requirements and tasks

2.1.5. All work shall be performed IAW applicable laws and regulations. The contractor shall NOT perform any Inherently Government Functions as defined in FAR XXX.

2.1.6. The contractor shall maintain ongoing communication within working groups to ensure tasks are completed with high efficiency and technical quality.

2.1.7. The contractor shall perform all tasks with a focus to increase cost effectiveness, quality, timeliness, and safety

2.1.8. The contractor shall conduct independent review of sustainment, procurement, acquisition, and modification efforts to identify resource duplication.

2.1.9. The contractor shall analyze, recommend, and incorporate (once approved) process and resource efficiencies (government and contractor), including application of streamlined program management techniques and other industry best practices.

2.1.10. The contractor shall continuously update government tracking and reporting systems and data repositories to ensure the latest DoD, USAF, and local

Instructions, Directives, and policies are captured (CDRL)

2.1.11. The contractor shall augment and fill knowledge/expertise gaps on Source Selection

Evaluation Boards (SSEBS) by acting as non-decision-making advisors for Source

Selections and related activities, IAW current DoD Source Selection procedures and the FAR as supplemented.

2.1.12. The contractor shall conduct technical evaluations of sole source proposals and cost estimates

2.2. Programmatic Support

2.2.1. The contractor shall provide direct and/or reach-back support for procurement program operations, project and/or program management tasks, acquisition programs, and organizational activities as directed.

2.2.2. The contractor shall provide general logistical, financial management, and other programmatic support.

2.2.3. Objectives and Key Results (OKRs)

IPTs are the most effective means to translate the mission (organizational direction) into tangible, executable OKRs (concrete tasks) at scale across a large number of people.

2.2.3.1. The Contractor shall support and help achieve all OKRs

2.2.3.2. Contractor personnel shall “flex” as requirement priorities are adjusted by the Government.

2.2.4. In support of each subsystem/section, the contractor shall perform programmatic, system engineering, and technical management processes, including

Requirements definition and analysis

Decision analysis

Requirements management

Risk management

Transition

Architecture design

Implementation

Integration

Verification and validation

Technical planning and assessment

Configuration management

Technical data management

Interface management

Flight Test Unique Equipment (FTUE) support

Force Development Evaluations (FDE) support

Vandenberg Operational Test Launch Working Group support

Etc.

2.2.5. The contractor shall provide input and assistance for procurements from pre-solicitation through delivery.

2.2.6. The contractor shall support potential pre-acquisition or modification program requirements

2.2.7. The contractor shall support technology, engineering, and manufacturing development

2.2.8. The contractor shall support production and deployment

2.2.9. The contractor shall provide operational support

2.2.10. Scheduling

2.2.10.1. The contractor shall create and maintain schedules for programs and projects as needed (CDRL)

2.2.10.2. The contractor shall integrate long and short term schedules

2.2.10.3. The contractor shall combine subsystem/section inputs for sustainment, procurement, acquisition, and modifications into the MMIII Integrated

Master Schedule.

2.2.11. Risk Management

2.2.11.1. The contractor shall perform Risk Management for the subsystems/sections, IAW applicable regulations and local processes.

2.2.11.2. The contractor shall kepp program risk mitigation plans current

2.3. Technical Support

2.3.1. The contractor shall provide Sustaining Engineering. The AFMC definition of

Sustaining Engineering is: “Engineering effort on systems, products, or materials, required to resolve technical or supportability deficiencies revealed in operational service.”

2.3.2. The contractor shall perform all associated efforts (e.g. engineering and technical data, modeling, simulation, testing, etc.) integral to completion of overall engineering tasks

2.3.3. The contractor shall perform all efforts necessary to support the government in sustaining the MMIII operational force, including:

Incorporation of changes to ICBM Systems in response to requirements for performance improvements

Appropriate use of advances in technology

Correction of system deficiencies

Determining 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

Assessing weapon system and subsystem performance

Performing systems requirement determination

Performing trade studies

Subsystem/item specifications

Configuration Management and control

Test and Evaluation

Etc.

2.3.4. The contractor shall assess weapon system status relating to key performance requirements, including

Assessing deficiency indicators

Defining characteristics and causes of deficiencies

Determining impact on affected product

Identifying and evaluating issues, alternative solutions and trade-off opportunities

Recommending preferred solution

Designing, integrating and validating the solution

Etc.

2.3.5. The Contractor shall continually assess operational performance based on top level system performance parameters

2.3.5.1. The contractor shall determine and report current performance capabilities of the MMIII weapon system compared to baseline values

2.3.5.2. The contractor shall identify as early as possible in the assessment process potential areas of performance degradation that would impact capability.

2.3.5.3. The contractor shall determine basic causes of potential System

Performance degradation if an issue is determined to be system-level.

2.3.5.4. The contractor shall use engineering analysis techniques as required to determine degradation causes, such as design analysis, testing, evaluation of operational data, reliability modeling, Failure Modes and Effects

Analysis (FMEA), physical failure analysis and other conventional engineering problem identification techniques.

2.3.5.5. If analysis is performed by another contractor, the ISC Contractor shall validate root causes identified by IPTs and/or subsystem Contractors, and ensure problems are isolated to the lowest hardware and/or software levels possible

2.3.6. The contractor shall determine root causes, develop corrective actions, and evaluate effectiveness of implemented solutions

2.3.6.1. The Contractor shall evaluate corrective actions developed by IPTs and/or subsystem Contractors

2.3.6.2. The contractor shall manage efforts required to integrate and incorporate changes and modifications to fielded systems.

2.3.6.3. The contractor shall plan resources required to implement the corrective action

2.3.6.4. The contractor shall implement the government-approved solution.

2.3.6.5. In cases where the proposed solution involves actions outside the scope of

Contractor responsibilities, the Government will implement the solution.

The Contractor shall monitor and assess the effectiveness of corrective actions, and report results.

2.3.6.6. In cases where the proposed solution involves modification affecting interfaces (i.e. changes to the form, fit, or function of the existing design) the Contractor shall consults and coordinate with IPTs and/or subsystem

Contractors to verify correct allocations of system performance parameters to the hardware/software level requiring change and provide integration support where necessary.

2.3.6.7. The contractor shall ensure any modifications or changes to the system will maintain and/or improve system-level performance.

2.3.7. The contractor shall review and validate program requirements

2.3.8. The contractor shall assist the Government in interpretation of specifications, and development and publication of drawings and other technical data

2.3.9. The contractor shall ensure traceability between proposed design performance parameters and top-level system operational performance values.

2.3.9.1. The Contractor shall translate required operational performance parameters into inherent design performance parameters that can be used to define, measure, and evaluate programs.

2.3.9.2. The Contractor shall provide subsystem expertise to validate subsystem contractor analyses and produce requirements and other documentation for subsystem acquisitions that would create an OCI if produced by the subsystem contractor.

2.3.10. The contractor shall assist the Government in development of major and minor modifications to the weapon system and infrastructure.

2.3.11. The contractor shall perform analysis and resolution of other complex technical problems as required.

2.3.12. The contractor shall assist the government with implementation of MBSE processes and best practices.

2.3.13. The contractor shall assist the Government with technical requirements associated with replenishment of spares, procurement of replacement systems, and obsolescence management.

2.3.14. The contractor shall provide support for maintenance support equipment required by the weapon system.

2.3.15. Test Support

2.3.15.1. The contractor shall support testing and evaluation events

2.3.15.2. The contractor shall develop and implement test plans (CDRL)

2.3.16. Emerging Hardware Issues

2.3.16.1. The contractor shall assess deficiency indicators

2.3.16.2. The contractor shall define characteristics and causes of deficiencies

2.3.16.3. The contractor shall determine the deficiency impact on affected product

2.3.16.4. The contractor shall identify and evaluate alternative solutions to deficiencies

2.3.16.5. The contractor shall recommend a preferred solution for deficiencies

2.3.16.6. The contractor shall design, integrate and assist with validation of the solution (CDRL)

2.3.17. Analyses, Assessments, and Studies

2.3.17.1. The contractor shall plan and execute technical reviews and assessments

(e.g., System Requirements Review, Technology Readiness Assessment)

(80508B)

2.3.17.2. The contractor shall perform studies, assessments, and analyses, and develop and deliver reports to support sustainment (and associated procurement) as required, including: (CDRL)

Fault Tree Analysis

Probabilistic Risk Assessment

Unauthorized Launch Studies

Launch Action Studies

Assessments of Subsystem Contractor Deliverables and source data to

ICBM Technical Orders

2.4. Weapon System Software

Weapon system software includes Operational Software, Trainer Software, Test Facility

Software, Automatic Test Equipment software, Mission Application Software and Data System

Software.

2.4.1. The contractor shall perform systems engineering and integration of software programs.

2.4.2. The contractor shall use the government approved software configuration control system(s) to maintain configuration control of weapon system software and perform software analysis for appropriate integration into the weapon system, IAW ICBM

Configuration Management Plan (62-CMP).

2.4.3. The contractor shall perform software evaluation activities, which include analyzing requirements and determining whether software requirements have been met.

2.4.4. The contractor shall maintain software oversight

2.4.5. The contractor shall provide software support, including developing CPINs, validating code, etc. (CDRL)

2.4.6. The contractor shall ensure CPINs are maintained, current IAW Automated

Computer Program Identification Number (ACPIN) Data and Control Record, and that software in use is the authorized version IAW Software Version Description

(SVD).

2.4.7. The contractor shall, in consultation and cooperation with the IPTs and/or subsystem contractors, verify correct allocations of system software performance parameters to the level requiring change, and provide integration support.

2.4.8. The contractor shall translate required operational software performance parameters into inherent design performance parameters that can be used to define, measure, and evaluate software updates/changes

2.4.9. The contractor shall ensure traceability between proposed performance parameters and top-level system operational performance values.

2.4.10. The contractor shall perform systems engineering to transform an operational software updates/changes into a description of system performance parameters and a preferred system configuration through the use of an iterative process of functional analysis, synthesis, optimization, definition, design, test, and evaluation.

2.4.11. The contractor shall define and specify necessary embedded system and associated test system software changes after establishment of an initial software production baseline.

2.4.12. The contractor shall submit information for the following products:

Computer Program End Item Documentation

Software Requirements Specification (SRS)

Software Design Description (SDD)

Software Test Plan (STP)

Software Test Description (STD)

Software Test Report (STR)

Software Product Specification (SPS)

Other products as needed

2.4.13. The contractor shall support the government in verifying and validating that software products are satisfactory for the following requirements:

Computer Program End Item Documentation

Software Requirements Specification (SRS)

Software Design Description (SDD)

Software Test Plan (STP)

Software Test Description (STD)

Software Test Report (STR)

Automated Computer Program Identification Number (ACPIN)

Data and Control Record

Software Version Description (SVD)

Software Product Specification (SPS)

Other requirements as needed

2.4.14. The contractor shall ensure software changes are made IAW approved policy and guidance.

2.4.15. The contractor shall ensure Test Procedures and Test Plans adequately address the changes made to accommodate identified requirements.

2.4.16. The contractor shall ensure test results show that software is suitable for release to operational testing.

2.4.17. The contractor shall ensure the final CCB package is approved prior to fielding of new or modified software.

2.4.18. The contractor shall ensure an ACPIN is established for all newly developed or modified software and its supporting documentation.

2.4.19. The contractor shall generate and review changes to software/firmware documentation (81412)

2.4.20. NSCCA/PATE

2.4.20.1. The contractor shall interface with the NSCCA/PATE contractor and associated software developers

2.4.20.2. The contractor shall review and evaluate reports from the NSCCA/PATE contractor and associated responses from software developers.

2.4.20.3. The contractor shall identify the impacts of issues identified in

NSCCA/PATE reports to the Government engineering function and recommend possible courses of action.

2.4.20.4. The contractor shall coordinate test support with the NSCCA/PATE contractor (e.g. provision of tapes, test hardware, test facilities, etc).

2.4.20.5. The contractor shall administer the tool facilitating transfer of

NSCCA/PATE documents and reports between the NSCCA/PATE contractor and software developers.

2.5. Process Support

2.5.1. The contractor shall support Technical Engineering Review Board (TERB) processes

2.5.2. The contractor shall support Depot Source of Repair (DSOR) process

2.5.3. The contractor shall adjudicate System Integrity Verification (SIV) comments

2.5.4. The contractor shall investigate, answer, track, and provide engineering support for applicable technical assistance/information requests (e.g. Maintenance Assistance

Requests (MARs), Engineering Technical Assistance Requests (ETARs), AF Form

202 requests, Deficiency Reports (DRs), Engineering Orders (EOs), specification updates, etc.)

2.5.5. The contractor shall provide responses, tracking, and analysis for Technical Order changes (AF Form 252s), DLA requests (AF Form 339s), and other processes as required

2.5.6. The contractor shall support OPCERT/DECERT Technical Orders procedures for

ICBM Nuclear Critical Components IAW Technical Manual Contract

Requirements (TMCR 86-01).

2.5.7. The contractor shall assist the Government in performance of peer reviews

2.6. Documentation Support

2.6.1. The contractor shall develop documentation that is an inherent part of support activities (e.g. Systems Engineering Plan, Risk Management Plan, etc.) (81314)

2.6.2. The contractor shall develop/provide inputs to requirements documents and packages (e.g. PWS, GRID, etc.) (CDRL)

2.6.3. The contractor shall develop/provide inputs to contracting documentation when needed

2.6.4. The contractor shall develop and deliver reports, studies, and analyses to support sustainment as required (81313A)

2.6.5. The contractor shall create, sustain, modify, manage, and support publication of drawings, technical orders and other technical data. (80607)

2.6.6. The contractor shall draft and review changes to documentation (e.g. configuration documentation, technical orders, civil engineer manuals, nuclear surety documentation, etc.) and process change requests (CDRL)

2.6.7. The contractor shall develop technical documentation, including test plans, test reports, Technical Engineering Review Board (TERB) briefings, etc. (CDRL)

2.6.8. The contractor shall deliver engineering data in support of DoD and Air Force policies, generally including: (CDRL)

Certification Requirements Plan (CRP)

Nuclear Certification Plan (NCP)

Nuclear Certification Impact Statements (NCIS)

Nuclear Surety Evaluation Report (NSER)

Safety & Nuclear Surety Technical Memorandum

Briefing Materials (Nuclear Surety Briefings, Point Papers and White Papers)

Other policies as applicable

2.6.9. The contractor shall generate and review nuclear hardness and electromagnetic interference evidence and documentation (81411)

2.6.10. The contractor shall review deliverables from other contractors and provide feedback, expert opinions, and recommendations for direction as appropriate

(CDRL)

2.7. Meeting Support

2.7.1. Appropriate functional contractor personnel shall participate in, contribute to, and provide technical and programmatic expertise for meetings, reviews, and boards involving the program, IAW the basic PWS paragraph #-#

3. GROUND ELECTRICAL SYSTEMS

Ground Electrical Systems Description

Programs include

Airborne Launch Control System (ALCS)

Codes, Communications, Command and Control

Ground Minuteman Automatic Test System (GMATS)

Guided Missile Launch Electrical Circuit (GMLEC)

Simulated Electronic Launch Minuteman (SELM)

Higher Authority Communication /Rapid Message Processing Element (HAC/RMPE)

ICBM Operational Software Sustainment (IOSSP)

MMP/MMPU

Power

SACCS

Security

Trainers

Weapon System Control Console (WSCC)

3.1. General Requirements

3.1.1. All tasks shall be performed in coordination with the Ground Electrical Subsystem

Support contractor and overseeing government personnel.

3.2. Program-Specific Requirements: Airborne Launch Control System (ALCS)

Sustainment Program

3.2.1. The contractor shall provide engineering and logistics support for Operational

Ground Equipment (OGE) and airborne weapon system equipment included the

ALCS system. This support includes:

Part Supportability studies

Supplier qualification

Test support

Performance trend analysis

Technical Order changes and updates

Other taskings as identified by the operation of the system

3.3. Program-Specific Requirements: Codes, Communications, Command And Control

3.3.1. The contractor shall provide field support for Operational Ground Equipment

(OGE) and weapon system equipment included in Codes, Command, Control and

Communications (C3) equipment working groups.

3.3.2. The contractor shall pull information from maintenance data systems (JEDMICS, IMDS, ETIMS etc) and provide detailed analysis of the data, to be used in determining problems or concerns in the field. (CDRL)

3.4. Program-Specific Requirements: Test And Training Equipment

3.4.1. SELM Support

3.4.1.1. The contractor shall review Air Force generated SELM test sequence documents

3.4.1.2. The contractor shall perform SELM test dry runs at Hill AFB test facilities

3.4.1.3. The contractor shall perform fault isolation and checkout of SELM unique test equipment

3.4.1.4. The contractor shall provide on-site engineering support during conduct of

SELM tests at operational field locations

3.4.1.5. The contractor shall participate on SELM anomaly analysis teams to determine root cause of test anomalies discovered during SELM testing

3.4.1.6. The contractor shall provide technical support during SELM posture/ deposture activities

3.4.1.7. Pre-SELM, the contractor shall assist Wing SELM support staff with

Mobile Test Unit (MTU) inventory and hand receipt equipment to wing

3.4.1.8. Post-SELM, the contractor shall assist wing with MTU inventory and sign for equipment

3.4.1.9. When traveling to/from each test location and Hill AFB, the contractor shall use the SELM MTU as the primary mode of transportation.

ICBMSD will provide the contractor with a DOD Fleet Management card for fuel and services when operating the MTU outside the organization‘s Permissible

Operating Distance (POD), IAW AFI24-302, Vehicle Management, Attachment 10.

3.4.1.10. The contractor shall comply with AFI24-301, specifically paragraph 8.10.

Licensing Contractor Personnel. (The MTU has a declared Gross Vehicle

Weight of 25,000 lbs; no Commercial Driver’s License (CDL) required.)

3.4.1.11. The contractor shall conduct familiarization training for each designated operator.

3.4.1.12. The contractor shall support Hardness Surveillance Electromagnetic Pulse

(EMP) Program (HSEP) testing. This support may include:

Reviewing test equipment designs

Developing schedules and upgrade plans

Developing strategies to reduce program production, repair and sustainment costs

Performing anomaly resolution investigation

Etc.

3.5. Program-Specific Requirements: Trainers

3.5.1. The contractor shall perform necessary software updates to MPT/APT/CMPT/

MMT (all trainers)

3.5.2. The contractor shall support reviews of source code

4. FIELD SUPPORT

Field Support Description

The Field Support Section is an aligned workforce that provides critical field support and timely responses on prioritized tasks to deliver mission ready capabilities to maintain 400 combat capable Minuteman III missiles through effective Integrated Product Teams.

Field Support is the door for enterprise partners (Air Force Global Strike Command, 20th Air

Force, 576 FTS, AFSC, DLA, and Navy Crane) to the MM III Sustainment Branch, acting as the filter/shock absorber to Engineering and Supply Chain issues that will arise within the weapon system.

4.1. Programmatic Support

4.1.1. All tasks shall be performed in coordination with cognizant Field Support government personnel.

4.1.2. The contractor shall review and validate field support requirements

4.1.3. The contractor shall act as the IMDS Subject Matter Expert for the Field Support section

4.1.4. The contractor shall navigate and data mine IMDS for downloads of MMIII maintenance actives

4.1.5. The contractor shall provide data management and analysis for studies (CDRL)

4.1.6. The contractor shall use data sources to identify programmatic needs, insuring goals are documented, and perform data validation and QA checks

4.1.7. The contractor shall maintain assigned projects

4.2. Engineering Support

4.2.1. The contractor shall apply technical and procedural products, such as Technical

Orders, Operating Instructions (OIs), regulations, publications, etc.

4.2.2. The contractor shall guide and direct junior engineers with technical problems

4.3. System Engineering Level Evaluation Correction Team (SELECT)

SELECT Description

During the developmental, operational, and sustainment phases of ICBM weapon systems, the

ICBM Systems Division is responsible for obtaining and maintaining system-level engineering support. This support includes the capability for analysis, evaluation, and resolution of weapon system problems associated with procedures, hardware, and software functions. This type of engineering support is required when the resolution of field, depot, or in-house problems exceed the scope of those covered by standard processes and procedures.

SELECT is a joint team composed primarily of contracted system engineers from multiple

ICBM defense contractors. In order to accommodate the use of existing weapon system test facilities, the primary location of the SELECT organization is at Hill AFB. Due to the direct interface between contracted engineers and Air Force field personnel, a government point of contact is assigned as the SELECT manager. SELECT engineers are dispatched as teams when directed by the SELECT manager.

SELECT also provides engineering support for the conduct of the Simulated Electronic Launch

Minuteman (SELM) program.

4.3.1. SELECT Requirements

4.3.1.1. The contractor shall assess and solve system level problems that are not necessarily confined to one subsystem

4.3.1.2. The contractor shall accomplish system level testing and fault isolation in a developmental, assembly and checkout (A&CO), or operational weapon system environment.

4.3.1.3. The contractor shall perform the following using government furnished special test hardware and software, certified for SELECT use only:

4.3.1.4. Isolate, identify and resolve technical problems

4.3.1.5. Break out and monitor selected subsystem interfaces

4.3.1.6. Monitor and collect data from weapon system equipment in support of analysis, evaluation, and resolution of weapon system problems.

4.3.1.7. The contractor shall conduct special studies and/or analyses based on system engineering-level requests for assistance from the field, depots, ICBM test facilities, or ICBMSD

4.3.1.8. The contractor shall support SELM test activities, which include:

Review of Air Force-generated SELM test sequence documents

Perform SELM test dry runs at Hill AFB test facilities

Perform fault isolation and checkout of SELM unique test equipment

Provide on-site engineering support during conduct of SELM tests at operational field locations

Participate on SELM anomaly analysis teams to determine root cause of test anomalies discovered during SELM testing

Provide technical support during SELM posture/deposture activities

Other test activities as needed

4.3.1.9. The contractor shall conduct a Personnel Reliability Program (PRP) based on AFMAN 10-3902 requirements for all personnel who are technically qualified to serve on SELECT and who must have access to operationally certified nuclear critical components

4.3.1.10. SELECT personnel shall travel in support of field fault analysis and resolution efforts and in support of SELM test activities

4.3.1.11. SELECT personnel shall rapidly dispatch (within 48 hours of request) to problem sites in order to evaluate and resolve critical technical problems in a timely manner

4.3.1.12. The contractor shall submit engineering reports to document SELECT support activities (CDRL)

4.4. Tech Engineering (TE) at 4 Operating Locations (OLS): Malmstrom, Minot, FE

Warren, and Vandenberg AFBs

OL TE Description

During the developmental, operational, and sustainment phases of ICBM weapon systems, the

ICBM Systems Division is responsible for obtaining and maintaining system-level engineering support. This support includes the capability for analysis, evaluation, and resolution of weapon system problems associated with procedures, hardware, and software functions. This type of engineering support is required when the resolution of field, depot, or in-house problems exceed the scope of those covered by standard processes and procedures.

TE is a team composed primarily of military and civilian engineers to include military and civilian technical engineers. In order to facilitate on-site technical support to maintenance operations at the wings or test flight support, the primary location of the TE organization is at the

4 OLs. TE engineers are dispatched as teams.

4.4.1. TE Requirements

4.4.1.1. The contractor shall assess and solve system level problems that are not necessarily confined to one subsystem

4.4.1.2. The contractor shall accomplish system level testing and fault isolation in a developmental, assembly and checkout (A&CO), or operational weapon system environment.

4.4.1.3. The contractor shall perform the following using government furnished special test hardware and software to:

4.4.1.4. Isolate, identify and resolve technical problems

4.4.1.5. Break out and monitor selected subsystem interfaces

4.4.1.6. Monitor and collect data from weapon system equipment in support of analysis, evaluation, and resolution of weapon system problems.

4.4.1.7. The contractor shall conduct special studies and/or analyses based on system engineering-level requests for assistance from the field, depots, ICBM test facilities, or ICBMSD

4.4.1.8. The contractor shall conduct a Personnel Reliability Program (PRP) based on AFMAN 10-3902 requirements for all personnel who are technically qualified to serve on TE and who must have access to operationally certified nuclear critical components

4.4.1.9. TE personnel shall rapidly dispatch (within 48 hours of request) to problem sites in order to evaluate and resolve critical technical problems in a timely manner

4.5. Supply Chain Management (SCM) Support

SCM Support Description

SCM supports end users (AFGSC warfighters, 309 Depot Maintenance, 414 SCMS, and

DLA) and provides SCM analytical data, ensuring status is available to decision makers for part support.

4.5.1. SCM Requirements

4.5.1.1. The contractor shall support and/or perform management of the AF

Supply Chain system for cradle to grave management of MMIII weapon system parts.

5. GUIDANCE SYSTEMS

Guidance Description

The Guidance subsystem performs the necessary guidance, navigation, and control functions of the MMIII missile. The Missile Guidance Set (MGS) works with the Operational Ground

Program (OGP) and Operational Flight Program (OFP), flight controls and RS/RV hardware to initiate, guide, and end missile flight and payload deployment. The NS50 guidance system is a pure inertial system and does not use any external references (such as GPS) to determine position and velocity of the vehicle during flight. The inertial navigation system includes a computer and stabilized instrument platform containing accelerometers to measure linear acceleration and gyroscopes to measure heading attitude.

The Guidance System includes the following:

Missile Guidance Set (MGS) and components

Operational and support equipment software

Performance Assessment Data System (PADS)

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

Flight Assessment including reliability and accuracy determinations

Major components in the MGS include:

Missile Guidance Computer (MGC)

Missile Guidance Set Control (MGSC)

Gyro Stabilized Platform (GSP) and associated electronics SE437C flight battery

Power Distribution Unit (PDU) and interconnecting cables

Missile Wafer (CD2-3A) that houses the MGS elements

5.1. Programmatic Support

5.1.1. All tasks shall be performed in coordination with the Guidance Subsystem Support contractor and overseeing government personnel.

5.1.2. The contractor shall maintain the section Integrated Product Team (IPT) charter.

5.1.3. The contractor shall participate in management of Guidance-related weapons systems risks.

5.1.4. The contractor shall provide full time ISSO support for ICBM Telemetry Integrated

Processing System (ITIPS) and PADS

5.2. Engineering/Technical Requirements

5.2.1. The contractor shall support Guidance Engineering testing, including the MGS wafer and its subcomponents, Hardness surveillance activities, FDE/OTL testing and Flight Unique Equipment/Components, etc.

5.2.2. The contractor shall support FDE, including pre and post launch activities

5.2.3. The contractor shall provide onsite engineering support at shops, wings, and contractor facilities as required.

5.2.4. The contractor shall provide input and assistance for the Programmed Depot

Maintenance (PDM) process

5.2.5. The contractor shall support the FDE pre/post flight analysis, to include but not limited to asset selection through reliability and accuracy determination

5.3. Test Support

5.3.1. The contractor shall provide Flight Test Unique Equipment and Operational Test

Launch support.

5.3.2. The Contractor shall provide support to the Operational Test Launch (OTL) working group, track and help resolve action items, and assist with stakeholder communication needed to resolve issues.

5.3.3. The contractor shall support the government in managing the Vandenberg OTL database, including training, verification of data, etc.

6. GROUND MECHANICAL SYSTEMS

Ground Mechanical Description

Ground mechanical responsibilities includes design and development of special purpose tractors and semitrailers, hydraulic systems, suspension and shock absorption systems, pneumatic systems, environmental control systems, coolant systems, electrical and mechanical security systems, crew support systems, corrosion inhibition systems, and all associated support equipment, test equipment, and special tooling as related to the sustainment of the Ground

Mechanical Subsystem of the Minuteman III weapon system.

6.1. Requirements

6.1.1. All tasks shall be performed in coordination with the Ground Mechanical

Subsystem Support contractor and overseeing government personnel.

6.1.2. The contractor shall review and validate Ground Mechanical requirements

6.1.3. The contractor shall assist the government with maintenance of configuration management

6.1.4. The contractor shall support Technical Engineering Review Board (TERB) processes, including the Ground Mechanical Review Board (GMRB)

7. PROPULSION SYSTEMS

PROPULSION DESCRIPTION

The major components of the propulsion systems are three independent solid propellant stages, the liquid propellant post-boost vehicle, flight control equipment, raceway cabling, and integrating hardware including batteries and ordnance. The system is generally referred to as two main subsystems; the Booster and the Propulsion System Rocket Engine. These are tied together with inter-stage kits and raceway cables.

7.1. Requirements

7.1.1. All tasks shall be performed in coordination with the Propulsion Subsystem Support contractor and overseeing government personnel.

7.1.2. The contractor shall support Aging Surveillance of all four stages and subcomponents as required to include affiliated ground battery/systems and

Vandenberg unique, Launch Facility, and RS/RV ordnance as directed.

7.1.3. The contractor shall support Force Development Evaluations including pre and post launch activities as directed.

7.1.4. The contractor shall provide onsite engineering support at depot shops, wings, and other facilities as required.

7.1.5. The contractor shall provide input and assistance for the Programmed Depot

Maintenance (PDM) process

7.1.6. The contractor shall support Force Development Evaluation (FDE) MMIII flight test missions from Vandenberg Air Force Base by providing asset input, engineering assessment, and required hardware to support flight test unique requirements.

7.1.7. The contractor shall maintain the section Integrated Product Team (IPT) charter.

8. REENTRY SYSTEMS/REENTRY VEHICLE (RS/RV)

RS/RV DESCRIPTION

The major components that make up the RS/RV subsystem are the MK12A and MK21 re-entry vehicles and the re-entry system. Additional equipment supported includes field and depot support equipment that tests RS/RV components. Supports Force Development Evaluation

(FDE) MMIII flight test missions from VAFB by providing asset input, engineering assessment, required hardware to support flight test unique requirements and reliability assessment testing via

Service Star and Aging Surveillance programs.

8.1. General Requirements

8.1.1. The contractor shall provide Engineering, Program Management, Lifecycle

Logistics, and Equipment Specialist (ES) support to the MMIII RS/RV subsystem.

8.1.2. All tasks shall be performed in coordination with the RS/RV Subsystem Support contractor and overseeing government personnel.

8.2. Programmatic Requirements

8.2.1. The contractor shall provide support/act as a liaison for the government approved task-based tracking system.

8.2.2. The contractor shall update and edit program Roadmap information. (CDRL)

8.2.3. The contractor shall provide support for and update HEDGE-models as needed.

8.3. Technical Requirements

8.3.1. The contractor shall provide technical expertise to facilitate and integrate DOE requirements. (CDRL)

8.3.2. The contractor shall provide Model Based Engineering and drafting support by validating models, inputting approved changes, developing drawing files, etc.

(CDRL)

8.3.3. The contractor shall provide in-depth research/analysis (e.g. white papers) on specific RS/RV related topics required by the AF to perform integration. (CDRL)

8.3.4. The contractor shall support Depot Support Equipment refurbishment efforts, including document generation, document review, vertical and horizontal coordinations, etc.

8.3.5. The contractor shall provide engineering support for Depot Support Equipment traceability and specification reviews.

8.3.6. The contractor shall provide support for Flight Hardware and Support Equipment

(Equipment Specialist (ES) task).

8.3.7. The contractor shall provide technical expertise to transition the MMIII RS/RV subsystem to GBSD, and new MMIII fuze replacement.

9. ICBM INFRASTRUCTURE EQUIPMENT (IIE)

IIE DESCRIPTION

IIE includes design and development of:

Hydraulic systems

Suspension and shock absorption systems

Pneumatic systems

Environmental control systems

Electrical and mechanical security systems

Power generation and distribution, water supply, distribution and waste, facility structural systems

Fuel monitoring storage and distribution systems

Elevator and crew support systems

All associated support equipment, test equipment, special tooling and tech data related to the sustainment of the Minuteman III weapon system

9.1. Requirements

9.1.1. All tasks shall be performed in coordination with the cognizant IIE government personnel.

9.1.2. The contractor shall assist the Government with technical requirements associated with replenishment of spares, procurement of replacement systems, and obsolescence management

APPENDICES

APPENDIX A: ACRONYMS AND ABBREVIATIONS

APPENDIX B: WORK BREAKDOWN STRUCTURE

APPENDIX C: SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

Reference Integration Support Contract Basic PWS - Appendix C

APPENDIX D: GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT

(GFP/GFS/GFE)

APPENDIX E: CONTRACT DATA REQUIREMENTS LIST (CDRL)