Attachment 19 - ISC2.0 PWS ATO2 MMIII SUST.pdf

FA8207-20-R-0003 - ISC 2.0

Task Order 2: MMIII Sustainment PWS

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

INTEGRATION SUPPORT CONTRACT (ISC) 2.0

TASK ORDER 2: MINUTEMAN III (MMIII) SUSTAINMENT

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

MMIII SYSTEM PROGRAM OFFICE (SPO)

14 OCTOBER 2020

CONTENTS

1.0. ISC – MMIII SUSTAINMENT SUPPORT SCOPE

2.0. OVERARCHING REQUIREMENTS ................................... Error! Bookmark not defined.

3.0. GROUND ELECTRICAL SYSTEMS …………………………………………………..13

4.0. FIELD SUPPORT

5.0. GUIDANCE SYSTEMS

6.0. GROUND MECHANICAL SYSTEMS

7.0. PROPULSION SYSTEMS

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

9.0. ICBM INFRASTRUCTURE EQUIPMENT (IIE)

ACRONYM LIST ………………………………………………………………………………29

1.0. ISC – MMIII SUSTAINMENT SUPPORT SCOPE

MMIII Sustainment Description MMIII Sustainment ties together the components of the MMIII Work Breakdown Structure (WBS) (five MMIII Subsystems and ICBM Infrastructure Equipment (IIE)) and Field Support, to best sustain product delivery.

MMIII Sustainment Organization The MMIII Sustainment organization falls under the MMIII SPO. It consists of the Propulsion Subsystem, Guidance Subsystem, Reentry System/Reentry Vehicle (RS/RV) Subsystem, Ground Mechanical Subsystem, Ground Electrical Subsystem, IIE, and Field Support, each of which includes an Integrated Product Team (IPT). IPTs are organized around WBS products and serve a critical role as integrators between the areas. They aim to provide a stable approach to problem solving across the Weapon System (WS).

Section Chiefs serve as IPT Leads for their respective IPTs. They are responsible for product-level priority within their IPTs. They meet with higher leadership regularly to provide their priority recommendations. SPO leadership is 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 MMIII Sustainment Chief; however, the Chief can choose to delegate authority to another IPT leader.

Generally, IPT members are assigned as follows:

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

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

• Integration organization personnel participate in IPT(s) per the IPTs’ need for the High- Demand, Low-Density (HD/LD) services provided by the Integration organization (e.g.

Test, Nuclear Surety, Hardness, etc.).

IPT leadership holds authority to acquire, release, and/or share assigned Government 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

Note: IPT leadership’s authority to acquire, release, and/or share personnel applies to Government personnel only. See paragraph 2.1.14. below for Contractor responsibility when requirements are reprioritized.

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

Data Deliverables (Contract Data Requirements Lists [CDRLs]) A master list of potential DoD Form 1423s (DD 1423s), Contract Data Requirements Lists, is provided as Section J Attachment 6, Contract Data Requirements Lists (CDRLs).

Due to the quantity and diversity of the programs in the ICBM Organization, the type and magnitude of required support is different for each program. Each program will employ the tasks in this PWS to the extent needed by that program. This also means that data deliverable needs will vary based on the program. To this end, CDRLs are not referenced in this PWS after every paragraph in which they may be required.

CDRLs specifically referenced in this PWS are to be delivered every time the task required by the referenced paragraph is performed (e.g. monthly status reports, training materials, engineering documentation, etc.).

If a program determines that a formal data deliverable is needed for a paragraph without a CDRL reference (e.g. advice, recommendations, analysis reports, etc.), the Government representative will select the appropriate CDRL from the master list and specify the delivery date/address and any other necessary instructions on the DD 1423. Any additional tailoring will also be documented on the DD 1423 at that time. The CDRL number will be incorporated into the associated task assignment (see paragraph 4.9 of the Basic PWS).

2.0. 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 Government personnel. The Government Program Manager (PM) 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 Contractors (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 in accordance with (IAW) applicable laws and regulations. The Contractor shall NOT perform any inherently Government functions as defined in Federal Acquisition Regulation (FAR) 7.503.

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 Department of Defense (DoD), Air Force (AF), and local instructions, directives, policies, etc. are captured.

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 participate in Technical Evaluations of sole source proposals and cost estimates.

2.1.13. The Contractor shall support the Government’s strategic priorities. These include increasing operational credibility, strengthening partnerships, optimizing resources, implementing effective governance, and operating with deep knowledge, extreme tenacity, and radical teaming.

2.1.14. The Contractor shall provide continuous yet flexible support IAW the Government’s prioritization/reprioritization of requirements.

2.1.15. The Contractor shall provide Engineering, Program Management, Life Cycle Logistics, Equipment Specialist (ES) and other support as needed to the MMIII Sustainment branches.

2.2. Programmatic Support

2.2.1. The Contractor shall provide direct and/or reach-back support for procurement program operations, repair lines, project and/or Program Management tasks, acquisition programs, and organizational activities as directed.

2.2.2. The Contractor shall provide general logistical, Financial Management, ES, and other programmatic support.

2.2.3. In support of each subsystem/section, the Contractor shall perform programmatic, Systems Engineering (SE), and technical management processes, including:

• Requirements definition and analysis

• Decision analysis

• Requirements management

• Risk Management (RM)

• 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 (OTL) Working Group support

• Other processes as needed

2.2.4. The Contractor shall provide input and assistance for procurements from pre-solicitation through delivery.

2.2.5. The Contractor shall support potential pre-acquisition or modification program requirements.

2.2.6. The Contractor shall support technology, engineering, and manufacturing development.

2.2.7. The Contractor shall support production and deployment.

2.2.8. The Contractor shall provide operational support.

2.2.9. The Contractor shall maintain Integrated Product Team (IPT) charters and provide other administrative IPT support. (CDRL A059-5)

2.2.10. The Contractor shall update and edit program Roadmap information.

2.2.11. Scheduling

2.2.11.1. The Contractor shall create and maintain schedules for programs and projects as defined by WS risks as needed.

2.2.11.2. The Contractor shall integrate long and short term schedules.

2.2.11.3. The Contractor shall combine subsystem/section inputs for sustainment, procurement, acquisition, and modifications into the MMIII Integrated Master Schedule (IMS).

2.2.12. Risk Management (RM)

2.2.12.1. The Contractor shall perform RM for the subsystems/sections, IAW applicable regulations and local processes.

2.2.12.2. The Contractor shall keep program risk mitigation plans current.

2.2.13. The Contractor shall provide support/act as a liaison for the Government-approved task-based tracking system.

2.3. Technical Support

2.3.1. The Contractor shall provide Sustaining Engineering. The AF Materiel Command

(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 WS and subsystem performance

• Performing systems requirement determination

• Performing trade studies

• Subsystem/item specifications

• Configuration Management and control

• Test and Evaluation

• Other efforts as needed

2.3.4. The Contractor shall assess WS 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

• Others as needed

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 WS 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 consult 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.

2.3.9.3. Requirements and other documentation for subsystem acquisitions are normally produced by the Subsystem Support Contractors. In cases where production of this documentation would create an Organizational Conflict of Interest (OCI) if done by the Subsystem Contractor, the ISC Contractor shall produce requirements and other documentation for subsystem acquisitions.

2.3.10. The Contractor shall provide support to the Government as major and minor modifications to the WS and infrastructure are developed.

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 Model Based Systems Engineering (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 WS.

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 and procedures.

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

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 provide support for the design, integration, and validation of the solution.

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, etc.).

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:

• Fault Tree Analysis

• Probabilistic Risk Assessment

• Unauthorized Launch Studies

• Launch Action Studies

• Assessments of Subsystem Contractor Deliverables and source data to

ICBM Technical Orders

• Others as needed

2.3.18. The Contractor shall pull information from maintenance data systems: Joint Engineering Data Management & Information Control System (JEDMICS), Integrated Maintenance Data System (IMDS), Enhanced Technical Information Management System (ETIMS), and provide detailed analysis of the data, to be used in determining problems or concerns in the field.

2.3.19. The Contractor shall provide Engineering support to both contracted and organic repair lines currently being used to provide serviceable test equipment and devices used to sustain MMIII

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 SE 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 WS software and perform software analysis for appropriate integration into the WS, 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 Computer

Program Identification Numbers (CPIN), validating code, etc. (CDRL A054)

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

(ACPIN) Data and Control Record, and that software in use is the authorized version IAW the Software Version Description (SVD). (CDRL A054)

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 SE 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

• SRS

• SDD

• STP

• STD

• STR

• ACPIN

• Data and Control Record

• SVD

• 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 final Configuration Control Board (CCB) packages are 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.

2.4.20. Nuclear Surety Cross Check Analysis/Nuclear Safety Analysis and Technical Evaluation (NSCCA/NSATE)

2.4.20.1. The Contractor shall interface with the NSCCA Contractor and associated software developers.

2.4.20.2. The Contractor shall review and evaluate reports from the NSCCA

Contractor and associated responses from software developers.

2.4.20.3. The Contractor shall identify the impacts of issues identified in NSCCA/NSATE 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 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/NSATE documents and reports between the NSCCA 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), Defense Logistics Agency (DLA) requests (AF Form 339s), and other processes as required.

2.5.6. The Contractor shall support Operational Certification/Decertification (OPCERT/DECERT) Technical Order 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 [SEP], RM Plan, etc.).

2.6.2. The Contractor shall develop/provide inputs to requirements documents and packages (e.g. PWS, Government Rights in Data and Software [GRIDS], etc.).

2.6.3. The Contractor shall develop/provide inputs to contracting documentation when appropriate.

2.6.4. The Contractor shall develop and deliver reports, studies, and analyses to support sustainment as required.

2.6.5. The Contractor shall create, sustain, modify, manage, and support publication of drawings, technical orders and other technical data.

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.

2.6.7. The Contractor shall develop technical documentation, including test plans, test reports, TERB briefings, etc. (CDRLs A003, A060, A061, A062)

2.6.8. The Contractor shall deliver Engineering data in support of DoD and AF policies, including:

• 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/White Papers, etc.) (CDRL

A003)

• Other policies as applicable

2.6.9. The Contractor shall generate and review nuclear hardness and electromagnetic interference evidence and documentation.

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

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.9. (CDRLs A002, A003, A004, A059-73)

3.0. 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)

• Minimum Essential Emergency Communications Network (MEECN)

• Minuteman MEECN Program/Minuteman MEECN Program Upgrade (MMP/MMPU)

• Power

• Strategic Automated Command and Control System (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 cognizant Government personnel.

3.2. Program-Specific Requirements: ALCS Sustainment Program

3.2.1. The Contractor shall provide Engineering and logistics support for Operational

Ground Equipment (OGE) and airborne WS 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 OGE and WS equipment included in

Codes, Command, Control and Communications (C3) equipment working groups.

3.4. Program-Specific Requirements: Test and Training Equipment

3.4.1. The Contractor shall support the Hardness Surveillance Electromagnetic Pulse

(EMP) Program (HSEP). This support includes:

• Reviewing test equipment designs

• Developing schedules and upgrade plans

• Developing strategies to reduce program production, repair and sustainment costs

• Performing anomaly resolution investigation

• Other support as needed

3.5. Program-Specific Requirements: Trainers

3.5.1. The Contractor shall perform necessary software updates to Missile Procedures

Trainer (MPT)/Airborne Procedures Trainer (APT)/Control Monitor Procedures Trainer (CMPT)/Missile Maintenance Team (MMT) trainers.

3.5.2. The Contractor shall support reviews of source code.

3.6. Specific Qualifications

3.6.1. Contractor personnel assigned to any Ground Electrical System program shall have knowledge and experience with the ICBM Ground Electrical Subsystem, support equipment, and associated parts.

3.6.2. Contractor personnel assigned to ALCS Sustainment Program shall have knowledge and experience in design and performance of Ultra High Frequency (UHF) communication.

3.6.3. Contractor personnel assigned to Power Systems shall have knowledge and experience in design and performance of power generation, regulation, control, and distribution for power systems and batteries as applied to Armament Systems.

3.6.4. Contractor Software Engineers for the HAC/RMPE and IOSSP software efforts shall have knowledge and experience in modeling and simulation software design and implementation.

3.6.5. Contractor personnel assigned to Test and Training Equipment shall have:

3.6.5.1. Knowledge and experience in test equipment and related tasks such as:

• Reviewing test equipment designs and developing schedules and upgrade plans

• Developing strategies to reduce program production, repair and sustainment costs

• Anomaly resolution investigation

3.6.5.2. Knowledge and experience in test equipment to support HSEP testing and requirements

3.6.6. Contractor personnel assigned to Trainers shall have knowledge and experience with sustaining and updating software for the MPT/APT/CMPT/MMT.

4.0. FIELD SUPPORT

Field Support Description Field Support 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 MMIII missiles through effective IPTs.

Field Support is the door for Enterprise partners, such as AF Global Strike Command (AFGSC), 20th AF (20AF), 576 Flight Test Squadron (FTS), AF Sustainment Center (AFSC) (including the 414th, 406th, and 420th Supply Chain Management Squadrons (SCMS), 309th Missile Maintenance Group (MMXG), etc.), and DLA, to the MMIII Sustainment organization, acting as the filter/shock absorber to Engineering and Supply Chain issues that arise within the WS.

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 (SME) 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.

4.1.6. The Contractor shall use data sources to identify programmatic needs, insuring goals are documented, and perform data validation and Quality Assurance (QA) checks.

4.1.7. The Contractor shall maintain assigned projects.

4.1.8. The Contractor shall maintain currency of Sustainment Dashboard and provide changes and updates necessary for IPT workload management.

4.1.9. The Contractor shall be capable of trend analysis utilizing Government approved software for Engineering documents (202s, ETARs, MARs) and other supporting documents (1067, EOs, DRs, etc.) as deemed necessary by Sustainment IPTs.

4.1.10. The Contractor shall provide support in the management of the Missile Mishap Response Working Group (MMRWG) in handling Missile Potential Hazards and activating the Network (MPHN) in support of Station G’s capabilities to provide a technical solution to a field emergency.

4.1.11. The Contractor shall provide support to the MMIII Hotline in being the doorway to the SPO for both routine and emergency inquiries of the MMIII directorate.

4.1.11.1. As our military will cover the 24 hour/7 days a week coverage, the

Contractor shall provide analytical support in tracking of inquiries and support to enhance capabilities to the Nuclear Enterprise.

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. Systems Engineering Level Evaluation Correction Team (SELECT) SELECT Description During the developmental, operational, and sustainment phases of ICBM WSs, the ICBM organization is responsible for obtaining and maintaining system-level Engineering support. This support includes the capability for analysis, evaluation, and resolution of WS 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 team composed primarily of contracted Systems Engineers. In order to accommodate the use of existing WS test facilities, the primary location of the SELECT organization is at Hill Air Force Base (AFB). Due to the direct interface between contracted Engineers and AF 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 SELM program.

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

4.3.2. The Contractor shall accomplish system level testing and fault isolation in a developmental, Assembly & Checkout (A&CO), or operational weapon system environment.

4.3.3. The Contractor shall perform the following using Government furnished special test hardware and software, certified for SELECT use only:

• Isolate, identify and resolve technical problems

• Break out and monitor selected subsystem interfaces

• Monitor and collect data from WS equipment in support of analysis, evaluation, and resolution of WS problems.

4.3.4. The Contractor shall conduct special studies and/or analyses based on SE-level requests for assistance from the field, depots, ICBM test facilities, or ICBM SPOs.

4.3.5. The Contractor shall support SELM test activities, which include:

• Review of AF-generated SELM test sequence documents.

• Performance of SELM test dry runs at Hill AFB test facilities.

• Performance of fault isolation and checkout of SELM-unique test equipment.

• Providing on-site Engineering support during conduct of SELM tests at operational field locations.

• Participating on SELM anomaly analysis teams to determine root cause of test anomalies discovered during SELM testing.

• Providing technical support during SELM posture/deposture activities.

• Pre-SELM, assisting Wing SELM support staff with Mobile Test Unit (MTU) inventory and hand receipt equipment to the Wing.

• Post-SELM, assisting the Wing with MTU inventory and sign for equipment.

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

The MMIII SPO 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 AF Instruction (AFI) 24-302, Vehicle Management, Attachment 10.

4.3.5.2. The Contractor shall comply with AFI 24-301, specifically paragraph

8.10. Licensing Contractor Personnel. (The MTU has a declared Gross Vehicle Weight of 25,000 lbs; no Commercial Driver License (CDL) required.)

4.3.5.3. The Contractor shall conduct familiarization training for each designated operator.

4.3.6. The Contractor shall conduct a Personnel Reliability Program (PRP) based on AF Manual (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. (CDRL A059-6)

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

4.3.6.2. 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.6.3. The Contractor shall submit Engineering reports to document SELECT support activities.

4.3.7. In addition to providing operational field and SELM support, SELECT personnel shall support the wider ICBM community (e.g. Depot, 414th Supply Chain Management Squadron, AF Global Strike Command, 20AF, etc.) with SE expertise in areas such as:

• Depot problem analysis and resolution

• Acquisition program support

• Sustainment/Integration Branch support

• Review of Engineering data for technical adequacy

• WS performance test and analyses

• Other support as required

4.4. Technical Engineering (TE) at Operating Locations (OL)

OL TE Description During the developmental, operational, and sustainment phases of ICBM WSs, the ICBM organization is responsible for obtaining and maintaining system-level Engineering support. This support includes the capability for analysis, evaluation, and resolution of WS 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 four (4) OLs: Malmstrom, Minot, FE Warren, and Vandenberg AFB’s. 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, A&CO, or operational WS environment.

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

• Isolate, identify and resolve technical problems

• Break out and monitor selected subsystem interfaces

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

4.4.1.4. The Contractor shall conduct special studies and/or analyses based on SE-level requests for assistance from the field, depots, ICBM test facilities, or the MMIII SPO.

4.4.1.5. The Contractor shall conduct a 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. (CDRL A059-6)

4.4.1.6. 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 WS parts.

4.5.2. Health, Engineering, and Supply Chain Analytics

4.5.2.1. The Contractor shall perform the following analytics in support of the Field Support Dashboard:

• Health Analytics

• ETAR Analytics

• MAR Analytics

• 202 (Depot Engineer Technical Assistance Request) Analytics

• 339 (DLA Engineer Technical Assistance Request) Analytics

• 1067 (Weapon System Modification Request) Analytics

• Discrepancy Report (DR) Analytics

• Mission Impaired Capability Awaiting Parts (MICAP) Analytics

• Other analytics required for the Field Support Dashboard

4.5.2.2. The Contractor shall develop and deliver the reports/requests listed in paragraphs 4.5.2.1. above when Government personnel are unavailable.

4.5.2.3. The Contractor shall provide recommendations for continuous improvement of the processes listed in paragraphs 4.5.2.1. above.

4.6. Specific Qualifications

4.6.1. Contractor personnel assigned to Field Support shall have knowledge and experience with the ICBM WS from a maintenance perspective including problems and solutions of lead command issues experienced in past decades.

4.6.2. Contractor Program Managers assigned to Field Support shall have:

• Knowledge and experience utilizing IMDS

• Experience with Visual Basic for Applications (VBA)

4.6.3. Contractor Analysts assigned to Field Support shall have:

• Knowledge of utilizing the IMDS

• Exposure to VBA

4.6.4. The Contractor Lead Engineer assigned to Field Support shall:

• Have 6 years ICBM experience

• Know how to read manuals and drawings, understand technical terms, and interpret MMIII problem sets including field, depot, and supply chain concerns.

• Be able to address Engineer assistance requests (ETAR, MAR, 202, DR)

• Be able to comprehend and apply both technical and procedural products

• Be able to guide and direct junior Engineers with technical problems

4.6.5. Contractor personnel assigned to the SELECT and TE teams shall:

• Have at least 10 years of technical experience in the MMIII WS

• Have comprehensive WS knowledge of:

o WS design parameters o WS requirements o WS interface data o Use of special test equipment certified for SELECT/TE use only o SELM test program (SELECT team only) o Diagnostic data analysis capabilities to assess and solve system level problems that are not necessarily confined to one subsystem

• Obtain and maintain Top Secret security clearance with access to Critical

Nuclear Weapon Design Information (CNWDI) and NC2-ESI

• Be certified under the PRP IAW AFMAN 10-3902

• Be qualified to accomplish system-level testing and fault isolation in a developmental, A&CO, or operational WS environment

• Be qualified to support SE level requests for assistance from the field, depots, ICBM test facilities, or the ICBM SPOs to conduct special studies and analyses

• Be capable of rapidly dispatching (within 48 hours of request) to problem sites in order to evaluate and resolve critical technical problems in a timely manner

4.6.6. Contractor personnel assigned to support SCM shall have:

• Proficiency in the Standard Base Supply System (SBSS)

• Knowledge and experience with SCM-related numbers and codes, such as

National Stock Number (NSN) structure, Budget codes, Expendability, Recoverably, Reparability Codes (ERRCs), etc.

• Experience navigating 23-series regulations for SCM guidelines

• Knowledge and experience with connections between retail and wholesale supply chain organizations

• Knowledge of and experience with Demilitarization processes

• Experience with Item Manager duties and responsibilities

• Knowledge and experience with MICAP processes

5.0. 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 the Global Positioning System (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:

• 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

• GPS Metric Tracking System

• Vandenberg Operational Test Launch 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 Government oversight.

5.1.2. The Contractor shall participate in management of Guidance-related WS risks.

5.1.3. The Contractor shall provide full time Information Systems Security Officer (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 FTUE/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, including asset selection through reliability and accuracy determination.

5.3. Test Support

5.3.1. The Contractor shall provide FTUE and OTL support.

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

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

5.4. Specific Qualifications

5.4.1. Contractor personnel assigned to Guidance Systems shall have:

• Knowledge and experience to efficiently and effectively deliver SE capability in support of the MGS and its inertial guidance instruments

• Knowledge and experience in acquisition processes, FTUE, and OTL support

• Knowledge and experience in application and execution of the following SE technical and technical management processes:

o Requirements definition/analysis o Architecture design o Implementation o Integration o Verification and validation o Transition o Decision analysis o Technical planning o Technical assessment o Requirements management o RM o Configuration management o Technical data management o Interface management

• The ability to plan and execute technical reviews and assessments (e.g. SRR, TRA) and document development (e.g. SEP, RM Plan) that are an inherent part of the activities and processes listed above

6.0. GROUND MECHANICAL SYSTEMS

Ground Mechanical Description Ground mechanical responsibilities include 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 MMIII WS.

6.1. Requirements

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

Subsystem Support Contractor and with Government oversight.

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 TERB processes, including the Ground Mechanical

Review Board (GMRB).

6.1.5. The Contractor shall provide Hardness support.

6.1.6. The Contractor shall support all Ground Mechanical and subcomponents as required.

6.1.7. The Contractor shall support evaluations as directed.

6.1.8. The Contractor shall provide onsite Engineering support at depot shops, wings, and other facilities as required.

6.1.9. The Contractor shall provide input and assistance for the PDM process.

6.1.10. The Contractor shall provide in-depth research/analysis (e.g. white papers) on specific Ground Mechanical related topics required by the AF to perform integration.

6.1.11. The Contractor shall provide Engineering support for Depot Support Equipment traceability and specification reviews.

6.1.12. The Contractor shall provide technical expertise to transition the MMIII Ground Mechanical Subsystem to the Ground Based Strategic Deterrent (GBSD).

6.2. Specific Qualifications

6.2.1. Contractor personnel assigned to Ground Mechanical Systems shall have knowledge and experience in 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

• All associated support equipment, test equipment, and special tooling

7.0. 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 (PSRE). 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 provide onsite Engineering support at depot shops, wings, and other facilities as required.

7.1.4. The Contractor shall provide input and assistance for the PDM process.

7.1.5. The Contractor shall support FDE MMIII flight test missions from Vandenberg

AFB by providing asset input, Engineering assessment, and required hardware to support flight test unique requirements, including pre- and post-launch activities as directed.

7.2. Specific Qualifications

7.2.1. Contractor personnel assigned to Propulsion Systems shall have knowledge and experience in:

• Design, development, and sustainment of propulsion systems for rocket guided weapon systems, including:

o…