Draft RFP Package - TO 3 MMIII Acquitision Support PWS.docx

FA8207-XX-X-XXX

MMIII ACQUISITION TASK ORDER PWS- ISC 2.0

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

INTEGRATION SUPPORT CONTRACT (ISC) 2.0

MMIII ACQUISITION TASK ORDER

PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

MMIII SYSTEM PROGRAM OFFICE (SPO)

dd MMM 2020

Contents

1. ISC – MMIII ACQUISITION SUPPORT SCOPE

MMIII Acquisition Description Per DoDI 5000.02, all defense acquisition programs are designated by an Acquisition Category ACAT. ACAT level is based on the program’s estimated dollar value and type of funding. Thresholds are listed in Enclosure 1, Table 1, of DoDI 5000.02.

The MMIII SPO currently has programs of all ACAT levels used by the Air Force (I, II, and III).

MMIII Aquisition Organization The MMIII Acquisition organization falls under the MMIII SPO. It consists of three (3) sections: ACAT I & II, ACAT III, and Services. The mission of MMIII Acquisition is to mitigate sustainment risks through execution of ACAT programs. Acquisition programs operate in parallel to sustainment items, which in turn, are tied to MMIII Work Breakdown Structure (WBS) elements. The MMIII Sustainment organization includes Integrated Product Teams (IPTs) which are organized around WBS products and serve a critical role as integrators between the different areas of the MMIII Weapon System (WS). Acquisition personnel participate in the sustainment IPT(s) associated with the content of their acquisition program.

This body of this Task Order (TO) PWS defines overarching requirements for all MMIII acquisition programs. Appendices to this TO PWS define requirements specific to individual programs.

Note: While MMIII Acquisition also includes a Services section that is responsible for preparation and award of service contracts used by the ICBM organization at Hill AFB, due to Organizational Conflict of Interest (OCI) laws, the Services section will not use ISC support, and is therefore not included in this or any TO on the ISC 2.0 contract.

2. General Requirements

2.1. All requirements in the Basic PWS of this contract apply to this TO.

2.2. The contractor shall accomplish any and all of the requirements in this TO that are applicable to their assigned programs.

2.3. The contractor shall accomplish any program-specific requirements detailed in the applicable program appendix to this TO PWS.

2.4. All work shall be performed in coordination and cooperation with pertinent overseeing goverment 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.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 FAR #7.3.

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

2.7. The contractor shall provide support to Gov PMs and Engineers in meeting program cost, schedule, technical, and performance objectives throughout the acquisition phases of the program.

2.8. The contractor shall support acquisition planning and execution of acquisition phase activities consistent with DoD 5000 series directives, applicable AFIs, and any other laws and regulations relevant to ACAT acquisition and sustainment programs. This support includes:

· Program management

· Engineering analysis

· Risk management

· Logistics planning

· Document verification

· Determining requirements to meet acquisition milestones (e.g. Workloads, technical requirements, adequacy of technical submissions, schedules, test equipment, facilities, skills, training, etc.)

· Cost estimation and budget submissions

· Responding to deficiencies

· Analysis, planning, and reporting capability gaps or mission enhancements that may be mitigated/enhanced through materiel solutions

· Other requirements and tasks as circumstances dictate specific needs

3. PROGRAMMATIC REQUIREMENTS

3.1. The contractor may be required to serve as Deputy PM, depending on specific program requirements.

3.1.1. While serving as Deputy PM, the contractor shall ensure all Inherently Government Functions are accomplish only by Government personnel.

3.2. The contractor shall provide programmatic support for assigned programs during all phases of the acquisition lifecycle.

3.3. The contractor shall participate in activities of PMs, contracting officers, engineers, program control specialists, configuration managers, testing specialists and logisticians.

3.4. The contractor shall assist the government PM in day to day management and execution of the program.

3.5. The contractor shall assist the PM in developing and completing acquisition program planning and execution activities, sustainment planning, and other program management related requirements as needed.

3.6. The contractor shall represent the program and perform management activities during instances when the Government is not available.

3.7. The contractor shall perform analyses, assessments, trade studies, and forecasts. (81284)

3.7.1. The contractor shall provide information to facilitate program decisions. (81759)

3.7.2. The contractor shall monitor and analyze program performance and cost, and recommend efficiencies/opportunities.

3.7.3. The contractor shall analyze, plan, and estimate financial forecasts, current year obligation and expenditure plans, and unfunded requirements.

3.8. The contractor shall perform risk management for the assigned program (e.g. plan and conduct risk assessments, provide mitigation recommendations, implement approved mitigations, track program risks, etc.).

3.9. The contractor shall accomplish Tech Refresh activities and documentation IAW specific program requirement. (81429)

3.10. The contractor shall have knowledge of life cycle sustainment requirements.

3.11. The contractor shall participate in planning for transition of future capabilities from acquisition to sustainment.

3.12. The contractor shall have knowledge of the Long Range Development Program (LRDP) process.

3.13. The contractor shall support and participate in the provisioning process as applicable.

3.14. The contractor shall support acquisition program contract preparation/requirements and other procurement activities.

3.14.1. The contractor shall prepare information/documents for RFPs. (81606)

3.14.2. The contractor shall act as advisors in the source selection process to review proposals and provide recommendations, IAW current DoD source selection regulations.

3.14.3. The contractor shall perform contract closeout activities as appropriate.

3.14.4. The contractor shall initiate, attend, and provide other needed support for Data Calls.

3.14.5. The contractor shall assist with Market Research.

3.15. Program Schedule

3.15.1. The contractor shall develop and maintain program schedules. (81623)

3.15.2. The contractor shall recommend and implement (after government approval) timely resolutions for schedule conflicts to minimize program impacts.

3.16. The contractor shall perform acquisition program logistics activities.

3.16.1. The contractor shall participate in planning for system sustainment and life cycle issues.

3.16.2. The contractor shall perform assessments, analyses, studies, etc. to inform logistics planning.

3.16.3. The contractor shall provide Supply Chain Management support.

3.16.4. The contractor shall perform suitable substitutes analysis and documentation.

3.16.5. The contractor shall perform spares analysis.

3.16.6. The contractor shall coordinate Tech Refresh installation activities and any other installation needs.

3.16.7. The contractor shall support inventory management of equipment with pertinent contractor(s).

3.16.8. The contractor shall perform deployment planning and scheduling activities.

4. engineering/Technical requirements

4.1. The contractor shall provide engineering support as prescribed by each specific acquisition program appendix to this TO PWS. Each acquisition program will require a different mix of contractor engineering support in areas such as Aerospace, Electrical, Mechanical, Software, Systems, Sustainment, Test, etc.

4.2. The contractor shall provide engineering support for assigned programs throughout all phases of the acquisition life cycle.

4.3. The contractor shall provide technical expertise to the PM for acquisition program planning and execution activities.

4.4. The contractor shall assist and serve as support to the Government engineer in managing the full scope of day-to-day engineering demands of the program.

4.5. The contractor shall assist the government program engineer with engineering/technical tasks and activities, and developing and completing technical planning and execution activities.

4.6. The Contractor shall assist the program engineer with writing, reviewing, and updating technical acquisition and program documents.

4.7. The Contractor shall assist the program engineer to review deliverables from other contractors as appropriate.

4.8. The contractor shall serve as a program technical focal point.

4.9. The contractor shall perform analyses, assessments, trade studies, evaluations, etc.

4.9.1. The contractor shall perform technical and engineering analyses (e.g. FRACAS analysis, RAM analysis, Failure Mode Effects Analysis (FMEA), etc.).

4.9.2. The contractor shall perform engineering assessments.

4.9.3. The contractor shall perform weapon system assessments (e.g. Deficiency Reporting, ETAR, 202, 107 Support, etc.).

4.9.4. The contractor shall perform environmental health and safety assessments.

4.9.5. The contractor shall investigate and evaluate deficiencies.

4.9.6. The contractor shall evaluate network topology and architecture development.

4.9.7. The contractor shall perform feasibility studies of proposed modifications.

4.9.8. The contractor shall model and/or simulate current and projected system functionality.

4.9.9. The contractor shall perform, develop, and/or evaluate trade-off studies and analyses.

4.9.10. The contractor shall perform other analyses, assessments, studies, and evaluations in support of the acquisition program.

4.10. The contractor shall provide technical expertise and participate in planning and execution of engineering-related activities.

4.11. The contractor shall develop, review, analyze, and provide recommendations on system level requirements. (82007)

4.12. The contractor shall develop/refine program requirements and associated documentation. (80004)

4.13. The contractor shall review and provide feedback on Technical Data Packages (TDPs). (31000)

4.14. The contractor shall develop and recommend sustainment strategies. (881)

4.15. The contractor shall analyze supportability strategies.

4.16. The contractor shall identify technical risks, and develop and recommend mitigation strategies. (81399)

4.17. The contractor shall provide third party quality assurance oversight to hardware installation, hardware and software testing, and closure reporting.

4.18. The contractor shall manage development, testing, production, and delivery of replacement hardware/software, including facilitating fielding, system training, spares, technical orders, etc.

4.19. The contractor shall oversee the Radios Frequency Authorization (RFA) process, if necessary for the individual program.

4.20. The contractor shall support parts substitution, modifications, modification installations, etc.

4.21. The contractor shall accomplish Requests for Nomenclature (DD Form 61).

4.22. The contractor shall provide technical expertise and participate in planning and execution of System Engineering Technical Review (SETR) events (e.g. SRR, PCA, FCA, etc.).

4.23. The contractor shall participate in planning and accomplishing site surveys.

4.24. The contractor shall review and support configuration management activities (e.g. Engineering Change Proposals (ECPs), drawing reviews/redlines, etc.).

4.25. The contractor shall participate in planning and accomplishing Tech Refresh activities and documentation.

4.26. The contractor shall accomplish Value Engineering.

“Value Engineering” is a systematic method to improve the "value" of goods or products and services by using an examination of function, or the formal technique by which contractors may voluntarily suggest methods for performing more economically. Value engineering also attempts to eliminate, without impairing essential functions or characteristics, anything that increases acquisition, operation, or support cost.

4.26.1. The contractor shall continuously look for solutions in which the Government may receive best value or save cost without imposing unnecessary or burdensome technical, cost, or schedule risk.

4.27. The contractor shall collaborate and coordinate with government Cybersecurity personnel to accomplish Cybersecurity requirements for the programs, including research, answering questions, developing/gathering/reviewing/providing information and documentation, etc. (82143)

4.28. The contractor shall provide software support and documentation review/updates. (81756)

4.29. Test Support

4.29.1. The contractor shall assist with developmental and operational tests.

4.29.2. The contractor shall support First Article Acceptance Testing (FAAT).

4.29.3. The contractor shall support Initial Operational Test and Evaluation (IOT&E), Operational Utility Evaluation (OUE) and other testing as needed.

4.29.4. The contractor shall design tests, develop test procedures, write/review test plans, identify test facility requirements, schedule tests, and execute tests. (81284)

4.29.5. The contractor shall review and provide recommendations on system Test Plans (e.g. Test & Evaluation Program Plan, Master Test Plan, Detailed Test Plan, Test Procedure, Test/ Inspection Report, etc.). (81284)

4.29.6. The contractor shall review and analyze Prime contractor test plans for completeness, thoroughness, and correlation to applicable engineering specifications.

4.29.7. The contractor shall manage verification logic networks.

4.29.8. The contractor shall make statistically viable recommendations.

4.29.9. The contractor shall participate in and provide support for the program Integrated Test Team (ITT), including maintaining the charter, generating and distributing minutes, capturing and tracking action items, answering action items, etc.

5. Documentation Support

5.1. The appropriate functional contractor personnel shall create, develop, draft, review, update, maintain, provide input to, coordinate, etc. the program acquisition/milestone information requirements and documents required throughout the acquisition process IAW DoDI 5000.02, AFI 63-101, and other applicable regulation. These documents include: (CDRL)

· Affordability Analysis (82178)

· Acquisition Decision Memorandums (ADMs) (80748)

· Acquisition Program Baseline (APB) (81121A)

· Acquisition Strategy (82297)

· Corrosion Control Plan (81403A)

· Cybersecurity Strategy (CSS) (82002A)

· Exit Criteria (81945)

· Frequency Allocation Application (81174)

· Intellectual Property Strategy (82297)

· Item Unique Identification (IUID) Plan (81803)

· Life Cycle Sustainment Plan (LCSP) (82215)

· PESHE and NEPA Compliance Schedule (82239, 81840)

· Program Office Estimates (POE) (81468)

· Program Protection Plan (PPP) (81306)

· Radios Frequency Awareness (RFAs) (CDRL)

· Risk Management Plan (81808)

· Specifications (961)

· Spectrum Supportability Risk Assessment (SSRA) (81543A)

· System Engineering Plan (SEP) (81785A)

· Test and Evaluation Master Plan (TEMP) (81284)

· Other documents as needed

5.2. The contractor shall establish and maintain schedules to develop the documentation and ensure documentation is ready for program milestones. (82297)

5.3. The appropriate functional contractor personnel shall review and assess CDRLs/ deliverables from program Prime contractors, and provide acceptance/non-acceptance recommendations.

5.3.1. Review shall include assessment of format and content expectations.

5.4. The appropriate functional contractor personnel shall create, develop, draft, review, update, maintain, provide information for, coordinate, etc. program management documents, such as: (80004)

· CLIN Status Reports (80368A)

· Contract Funds Status Report (81468)

· Demilitarization & Disposal (81640)

· Horse Blanket (82215)

· LCSP (82215)

· Level II (82215)

· Monthly Activity Reports (80368A)

· Performance & Cost Report (80912A)

· Quality Assurance Program Plan (81794A)

· Schedules (e.g. Integrated Master Schedule, executive schedule, project schedules, deployment schedules, etc.) (82297, 881D)

· Sustainment forecasts (81468)

· Team Charters (80004A)

· Transition Plans (80790)

· Work Breakdown Structures (881D, 81334D)

· Other documents as needed

5.5. The appropriate functional contractor personnel shall create, develop, draft, review, update, maintain, provide information for, coordinate, etc. procurement documentation such as: (CDRL)

· Contract Modifications (81856)

· Letters of Clarification/Concern (CDRL)

· Market Research Reports (SD-5)

· Purchase Requests (1916)

· PWSs (81803)

· RFP Documentation (81606)

· Statements of Objectives (SOOs) (81803)

· Statements of Work (SOWs) (81606)

· Other documents as needed

5.6. The appropriate functional contractor personnel shall create, develop, draft, review, update, maintain, provide information for, coordinate, etc. engineering documents, such as:(CDRL)

· Detail Specification Documents (80776B)

· Engineering Change Proposals (80639)

· Interface Control Documents (81248B)

· Master Engineering Document Lists (82127)

· Performance Specification Documents (81465)

· Request for Nomenclature (DD Form 61) (81254C)

· Specification Change Notices (81493A)

· System/Subsystem Specifications (81431A)

· Technical Orders (38804D)

· TERB documentation (82238A)

· Other engineering and technical documents as needed (82238A)

6. Meeting Support

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

7.

SPECIFIC PROGRAM APPENDICIES

Appendix 1: Arm/Disarm Switch Replacement (ADSR) A1.1. ADSR Description The Arm Disarm Switch Replacement (ADSR) Program will replace the Arm/Disarm (A/D) Switch with a new design. The A/D Switch is an electromechanical switch that physically locks out several ordnance circuits on the MMIII. The switch will safe (disrupte the electrical pathway needed for the missle to arm), arm (facilitate the electrical pathway needed for the missle to arm), and facilitate execution of a number of critical weapon functions prior to and throughout the duration of missile flight, and is mandatory in both the missile operational and test configurations. There is one A/D switch in each interstage, one on the 2nd stage motor, and two on the PSRE for a total of five switches per missile.

The ADSR acquisition strategy will have up to three contractor’s complete designs and qualify the same. Once this has been completed any/all of the contractos which have successfully completed the qualification process will be allowed to bid on a larger competitive production order.

ADSR will primarily utilize DCA engineers from the program for engineering support.

APPENDIX 2: AUTOMATIC SWITCHING UNIT (ASU) REPLACEMENT PROGRAM

A2.1. ASU Description The ASU Replacement Program addresses obsolescence in the ICBM power distribution system and replaces the aging power switchgear with a modern Commercial-Off-The-Shelf (COTS) solution.

APPENDIX 3: BATTLESPACE AWARENESS

A3.1. Battlespace Awareness Description WaRTAK provides a tactical, common operating picture via a secure, high-bandwidth, wireless radio network utilizing the Android Tactical Assault Kit (ATAK). ATAK enables sharing/ presentation for text chat, video, pictures, and an interactive, layered, shared, moving map, plus many other niche data types for the tactical user within a closed network. ATAK runs within a small, personal tablet (smartphone) in the Dismount Kits or larger tablets in vehicles and buildings. The user also has a headset for audio that connects to the radio. The rest of WaRTAK exists to support and route data between each persons’ ATAK application.

Remote Visual Assessment (RVA) CLS monitors top side activity at MMIII Launch Facilities (LFs) and provides CCTV capabilities back to the Missile Alert Facilities (MAF) thereby allowing security forces to facilitate site security from the MAF and the ability to perform tailored responses to sites within the missile fields dependent on the severity of the identified activties.

RVA II consists of a series of modifications/upgrades built on the foundation of the existing RVA system. The upgraded modifications to the system are: improved video to ground Security Forces (SF), Outer Zone/Inner Zone (OZ/IZ) activation alarm, extended 1-hour power backup, video to airborne SF, extended 7-day video archive, and enhanced cybersecurity.

A3.2. Program-Specific Requirements A3.2.1. The contractor Logistician shall coordinate P&D installation activities with RVA CLS activities.

A3.2.2. The contractor Logistician shall coordinate of transferring GFP from P&D contractor to CLS contractor.

A3.2.3. The contractor Logistician shall inventory RVA II equipment with the P&D contractor.

APPENDIX 4: Control Monitor procedures trainer (CMPT) A4.1. CMPT Description The CMPT Program will replace obsolete hardware and software on all CMPT systems across the ICBM Enterprise to increase supportability. This program is required to maintain required training levels on the CMPT to ensure compliance with current certification standards.

aPPENDIX 5: Fast Rising B-Plug (FRBP) PROGRAM A5.1. FRBP Description The Fast Rising B-Plug (FRBP) Service Life Extension Program (SLEP) was initiated in order to meet an Air Force Global Strike Command (AFGSC) requirement for B-Plug technology insertion to address system obsolescence, safety and reliability.

This program will replace the Actuator Locking Bar (ALB), Secondary Door Linear Actuator (SDLA), replace the Energy Storage System (ESS), integrate with legacy and replacement M1 Motor Drive solutions, software development for the Secondary Door Control Assembly (SDCA), and add a slow raise mode to the Site Activation Remote Controller (SARC).

APPENDIX 6: FLIGHT TEST, TELEMETRY, AND TERMINATION (FT3) PROGRAM

a6.1. FT3 Description The purpose of the Flight Test, Telemetry, and Termination (FT3) Program is to replace aging MMIII ICBM Flight Test Unique Equipment (FTUE). The replacement systems/subsystems must meet 30th Space Wing (SW) range safety requirements to ensure the future reliability of MMIII ICBM Operational Test Launches (OTL) and developmental flight test programs.

A6.2. Program-Specific Requirements A6.2.1. The contractor shall develop and maintain the FT3 Integrated Master Schedule (IMS) A6.2.1.1. The schedule shall combine the Guidance SSC IMS with government activities, ISC activities, and other activities as identified by the Government PM.

A6.2.1.2. The contractor shall provide reports, analyses, and summaries of the IMS as required. (881D, 81334D) A6.2.2. Associated Contractor Agreements. The contractor shall enter into agreements with the Guidance SSC and their subcontractors.

A6.2.3. Reference Models A6.2.3.1. The contractor shall perform assessments comparing FT3 configuration changes to baseline Reference Models.

A6.2.3.2. The contractor shall update the baseline models where necessary.

A6.2.3.3. The contractor shall provide updated Reference Models in support of ICBM operational software changes, using FT3 data provided by the Guidance SSC. (82099) A6.2.4. Information Technology (IT) and Cybersecurity.

Portions of FT3 systems will be considered IT according to DoDI 5000.02. Many IT requirements identified in Enclosure 11 of DoDI 5000.02 will apply.

A6.2.4.1. The contractor shall support the Government in achieving these requirements/attaining waivers A6.2.4.2. The contractor shall coordinate IT and Cybersecurity efforts with Guidance SSC.

A6.2.4.3. The contractor shall work with 30th Space Communications Squadron to coordinate usage and security requirements for using Minuteman Telemetry Transportation Network (MTTN) for LSS communications between LFs/MAF and base facilities.

A6.2.4.4. The contractor shall provide cybersecurity support and documentation for the Authorization and Accreditation (A&A) process to achieve/obtain an Authority to Operate (ATO) or Interim Authority to Operate (IATO) for FT3 systems. (82002A)

Appendix 7: ICBM Cryptography Upgrade II (ICU II) program A7.1. ICU II Description The ICU II Program will modify the MM III WS to use the KS-60’s Irreversible Transformation functionality to mitigate risks associated with current Enable and Launch command authentication. The ICU II Program will also mitigate risks associated with the current manual code change approach by implementing a Remote Code Change (RCC) capability, which will allow LCCs to securely encrypt code updates to the LFs, allowing the LFs to remain physically secured during code change. The ICU II Program also implements a more robust and cost effective response. The ICU II Program replaces WSP TDS with a more robust Continuous Signal Lock Out (CSLO) capability A7.2. Program-Specific Requirements A7.2.1. The contractor shall provide support for engineering efforts related to Depot Support Equipment and Guided Missile Launch Electric Circuit (GMLEC) Test Set.

A7.2.2. The contractor shall provide logistics services to plan and coordinate A4 Drawer hardware Operational Certification (OPCERT) and Decertification (DECERT) processes.

A7.2.3. In the EMD Phase, the contractor shall:

· Assess readiness for production

· Support development of a detailed production design

· Support design and evaluation of design producibility

· Analyze manufacturing processes and equipment

· Evaluate producibility engineering and production planning A7.2.4. In the P&D Phase, the contractor shall:

· Maintain production surveillance

· Support quality assessment determinations

· Perform engineering analysis in support of depot maintenance, product support, or sustainment engineering

· Accomplish second sourcing/component breakout

· Complete industrial preparedness planning

· Assist in planning for the accomplishment system transition from acquisition to sustainment

APPENDIX 8: LAUNCH CONTROL CENTER BLOCK UPGRADE (LCCBU) PROGRAM

A8.1. LCCBU Description The LCCBU program will design, develop, procure, fabricate, integrate, test, and document design solutions for four components in the LCC, and associated trainers and support equipment. The program will mitigate supply chain risks for the Floppy Disk Drive (FDD), Journal Memory Loader (JML), Oxygen Regeneration Unit (ORU), and the Weapon System Control Console (WSCC) Printer.

APPENDIX 9: LGM-30G AIRBORNE PROCEDURES TRAINER REPLACEMENT (APT-R) PROGRAM

A9.1. APT-R Description The APT-R program provides a training capability to support the Airborne Launch Control System (ALCS) mission and is driven by the loss of the legacy APT due to historic March 2019 flooding at Offutt AFB. The APT-R program will design, develop, produce and deploy a trainer used to train ALCS crews on missile launch procedures, emergencies, malfunctions, and in-flight operations as well as Nuclear Certification training.

APPENDIX 10: PAYLOAD TRANSPORTER REPLACEMENT (PTR) PROGRAM

A10.1. PTR Description The PTR program is a replacement MMIII Payload Transporter. The objective of the program is to provide a replacement payload transport capability with security upgrades. The security upgrades include an armored crew cab and an armored protection system for the Re-entry System (RS).

A10.2. Program-Specific Requirements A10.2.1. The contractor shall serve as the PTR Deputy PM.

A10.2.2. Contractor support shall encompass all Integrated Logistics Support (ILS) elements necessary to allow the PM and engineer to maintain Operational Safety, Suitability, and Effectiveness (OSS&E) of the PTR system.

A10.2.3. The contractor shall develop program documentation, support milestone decision reviews, and oversee Prime contractors. (82297) A10.2.4. The contractor shall provide Program Management and WS Sustainment support to sustain legacy Transportation and Handling (T&H) equipment items that will be used in the PTR acquisition program.

A10.2.5. The contractor shall have access to engineering software at their duty location.

A10.2.6. The contractor shall support both Government and Contractor engineers as a technical consultant for test and evaluation activities.

A10.2.6.1. The contractor shall review, comprehend, and assess test documentation. (80284B) A10.2.6.2. The contractor shall modify test and evaluation plans and procedures. (81284) A10.2.6.3. The contractor shall witness PTR testing as directed by the government, and develop and coordinate associated test reports. (81440A, 80809) A10.2.7. In the EMD Phase, the contractor shall:

· Assess readiness for production

· Support development of a detailed production design

· Support design and evaluation of design producibility

· Analyze manufacturing processes and equipment

· Evaluate producibility engineering and production planning A10.2.8. In the P&D Phase, the contractor shall:

· Maintain production surveillance

· Support quality assessment determinations

· Perform engineering analysis in support of depot maintenance, product support, or sustainment engineering

· Accomplish second sourcing/component breakout

· Complete industrial preparedness planning

· Assist in planning for the accomplishment system transition from acquisition to sustainment A10.2.9. The contractor shall submit monthly cost information to assist the government Program Manager with forecast of planned contractor obligations and expenditures (80912A)

APPENDIX 11: STRATEGIC AUTOMATED COMMAND AND CONTROL SYSTEM REPLACEMENT (SACCS-R) PROGRAM A11.1. SACCS-R Description SACCS is a terrestrial, non-survivable NC3 system providing the capability to compose, transmit, receive, process, readdress, and acknowledge time-critical Higher Authority Command Emergency Action Messages (EAMs), Force Direction Messages (FDMs), Force Status Reporting (FSR), Nuclear Executing and Reporting Plan, and non-nuclear EAMs in support of AF nuclear forces including tankers, bombers, MUNS, Recon, COCOMs, and ICBMs. SACCS-R is the replacement effort to address obsolescence issues, Diminished Manufacturing Sources and Material Shortages (DMSMS), challenges interfacing with advancing telecommunication and enterprise networks, and sustainment costs.

SACCS-R consists of three Builds.

Build 1.0: Time-Domain Multiplexing to Internet Protocol (TDM-IP) is the risk mitigation effort within TMRR to address the following risk reduction actions: OMNI and Promina obsolescence, TDM, WIN10 Secure Host Baseline (SHB), and cybersecurity. TDM-IP consists of two Builds. Build 1.1 is the hardware solution to eliminate OMNI & Promina obsolescence risk. Build 1.2 is the software solution to mitigate cybersecurity risk.

Build 2.0 (Ares) is the full replacement of SACCS by developing and fielding a modular, reliable, cost-efficient solution, which meets/exceeds technical performance requirements; improves reliability, availability, maintainability, and support current user interfaces; and addresses DMSMS.

A11.2. Program-Specific Requirements A11.2.1. The contractor shall provide the support necessary to review and evaluate network architectures of proposed solutions in support of SACCS messaging requirements, including assisting with interfaces for messages and their products, etc.

APPENDIX 12: TRANSPORTATION ERECTOR REPLACEMENT PROGRAM (TERP)

A12.1. TERP Description TERP is a replacement MMIII solid rocket booster Transportation Erector (TE) tractor trailer truck. The TE is the AF’s single system capable of removing and emplacing MMIII solid rocket booster at the launch facility. The objective of TERP is to deliver an obsolescence-free, technology refreshed, sustainable TE system.

The TERP P&D phase consists of Acceptance Testing and Full-Rate Production and Deployment (FRP&D). The purpose of this phase is to achieve operational capability in sufficient quantities to satisfy full mission need.

A12.2. Program-Specific Requirements A12.2.1. The contractor shall provide Program Management and WS Sustainment support to sustain legacy Transportation and Handling (T&H) equipment items (e.g. hoists, actuators, etc.) that will be used in the TERP acquisition program.

A12.2.2. The contractor shall serve as the Deputy TERP PM.

A12.2.2.1. The contractor shall develop program documentation, support milestone decision reviews, and oversee Prime contractors. (82255, 82297) A12.2.2.2. The contractor shall develop plans, execute daily activities, and report status to the TERP PM. (80368A) A12.2.4. The contractor shall serve in the capacity of Deputy TERP program engineer/ T&H subsystems engineer.

A12.2.4.1. The contractor shall manage sustainment for Tractors, Trailers, and commodity handling support equipment items (e.g. hoists, winches, carriages, jacks, test equipment, environmental control systems, generators, etc.).

A12.2.5. The contractor shall provide reach-back support for TERP as needed, performing work under the guidance of the Lead TERP program engineer.