TOLCMP LTRS 220808.pdf

UNCLASSIFIED

TECHNICAL ORDER LIFE CYCLE

MANAGEMENT PLAN (TOLCMP)

UNITED STATES SPACE FORCE

LAUNCH AND TEST RANGE SYSTEM (LTRS)

ORGANIZATIONAL/DEPOT

PREPARED BY: SLD 45/RM

DATE: 8 August 2022

This page is intentionally blank.

Submitted by

Don Hultgren

NH-03, DAF

TO Manager Launch Test Range Systems

Date

Approved by

John L. Wilkinson

NH-04, DAF

Product Support Manager Launch Test Range Systems

Date i

TABLE OF CONTENTS

Paragraph Page

1 Purpose

1.1 Introduction

1.1.1 Technical Data Life Cycle Changes

1.1.2 Recommended Change Processors

1.1.3 Technical Data User Changes

1.1.4 Technical Data Format/Delivery Changes

1.1.5 TO Concept of Operations (TO CONOPS)

1.2 Policy Specifications and Waivers

1.3 Program Summary

1.3.1 Weapon System Description

1.3.2 Key Features

1.4 TO Archiving Process

2 New Equipment Acquisition

2.1 Initial Planning

2.2 Scope of Requirements

2.3 Reviews

2.4 Data Formats

2.5 Type Manuals

2.6 TMCR

2.7 Other Contract Documents

2.7.1 Statement of Work

2.7.2 Special Contract Requirements (H-Clauses)

2.7.3 Data Rights

2.7.4 Schedules

2.7.5 Contract Deliverable Requirements List (CDRL)

2.7.6 Contractor Furnished Equipment Notice (CFEN)

2.7.7 Verifications

2.8 TO Live Cycle Verification Plan (TOLCVP)

2.9 Contractor Information

ii

3 Sustainment

3.1 Transition

3.2 Sustainment Overview

3.3 Responsibilities

3.3.1 LTRS TO Manager Sustainment Responsibilities

3.3.2 LTRS Logisticians and Equipment Specialists

3.3.3 Using and Lead Commands

3.4 Scope of TO Requirements

3.5 TO Preparation

3.5.1 Specification Interpretation Document (SID)

3.5.2 Development Flow

3.5.3 Reviews

3.5.3.1 In-Process Reviews (IPRs)

3.5.3.2 Pre-Publication Reviews (PPRs)

3.5.3.2.1 Formal PPRs

3.5.3.2.2 Informal PPRs

3.5.3.3 AFTO 252 Submission

3.5.4 Quality Assurance Process

3.5.5 Responsibilities

3.5.5.1 TO Manager Responsibilities

3.5.5.2 Technical Content Manager (TCM) Responsibilities

3.5.5.3 Engineering Responsibilities

3.5.6 Classified TO Reviews

3.5.7 Verifications, PTO, and Formalization Processes

3.5.7.1 TO Verification Process

3.5.7.2 PTO Process

3.5.7.3 Formalization Process

3.6 TO Security and Information Assurance

3.6.1 Classified Data Control, Controlled and Unclassified information

3.6.2 Cybersecurity Procedures

3.7 TO Change Process

3.7.1 OM&S TO Change Processes

3.7.1.1 TO Change/Revision

3.7.1.2 Rapid Action Change (RAC)

iii

3.7.1.3 AFTO 252 Change Process

3.7.2 Outside Contractor Change Processes

3.7.3 Weapon System TO Change Process

3.7.4 Inter-Service/FMS Relationships with TOs and TCTOs

3.8 Distribution Strategy

3.8.1 Distribution Contingency

3.9 Long-Term TO Management Strategy

3.10 Funding

4 TOLCMP Annual Review

5 System Retirement

6 Annex

6.1 Annex 1 – List of Acronyms

6.2 Annex 2 – Definitions of Common Terms

6.3 Annex 3 – Policy Specifications and Waivers

6.4 Annex 4 – TMCRs

6.5 Annex 5 – Technical Manual Organization Plan (TMOP)

6.6 Annex 6 – Flowcharts

6.7 Annex 7 – TO Concept of Operations

iv

1 Purpose This plan provides management policy, assigns responsibilities, defines terminology, and specifies procedures for the LTRS TO program. It includes basic instructions for accomplishment of the development, certification, verification, and formalization of LTRS TOs during initial acquisition and sustainment. This plan applies to all TO development, sustainment, and management activities, including those conducted at using command bases and contractor/subcontractor facilities. This plan was developed in accordance with TO 00-5-3 and is intended to cover the entire life cycle of the LTRS.

1.1 Introduction

The LTRS is currently in the Operations and Sustainment (O&S) phase and implements the Contractor Logistics Support (CLS) product support strategy with the LTRS Integrated Support Contract (LISC) providing operations, maintenance, and sustainment support. LTRS TO management and sustainment is performed by LISC. Development of new TOs is performed by LISC and other contracts.

The LTRS TO inventory is a mix of military standard (MIL-STD) TOs, Commercial off-the-Shelf (COTS) TOs, and legacy contractor-formatted Technical Manuals (TMs) that have been digitized and assigned a TO number. All LTRS TOs are currently in electronic, Type 1 Interactive Electronic Technical Manual (IETM) format.

1.1.1 Technical Data Life Cycle Changes

TOs are developed and modified to support modifications to the LTRS baseline configuration.

Projects that field new systems are delivered with new TOs. Projects that modify existing systems are delivered with changes or revisions to existing TOs.

TO development activities are performed concurrently with engineering development. TOs are delivered prior to Readiness Review Board (RRB) and Operational Acceptance (OA). TO content is based on engineering drawings, Logistics Support Analysis Record (LSAR) or Logistics Management Information (LMI) data, commercial technical data, and engineering and stakeholder input.

TO development review activities include TO Guidance Conferences (TOGCs), In-Process Reviews (IPRs), TO certifications, TO verifications, and Pre-Publication Reviews (PPRs). After initial delivery of TOs, changes may be initiated via Engineering Change Proposal (ECP), AFTO 22, AFTO 27, and

AFTO 252.

1.1.2 Recommended Change Processors

Changes to delivered TOs are performed by contractor organization that has Design Control Authority (DCA) of the TO.

When TOs are developed by an outside contractor (contractors other than the Operations, Maintenance, and Sustainment [OM&S] contractor), DCA typically transfers to the OM&S contractor after the DD250 is approved and the end item is added (transitioned) to the OM&S contract. Any required TO changes between initial delivery and transition are performed by the development contractor. After transition, TO changes are performed by the OM&S contractor.

When outside contractors initiate a change to an existing LTRS TO, the changes are initiated via AFTO 27 and implemented by the OM&S contractor. When this process is used, the development contractor is required to complete all verification activities and deliver all source and technical data required to perform the change.

1.1.3 Technical Data User Changes

Users initiate changes to existing LTRS TOs via AFTO 22 or Field Change Request (FCR).

FCRs are an OM&S contractor form that provides a simplified mechanism for users in the field to submit changes to LTRS TOs, SUMs, engineering drawings, and other technical data used for operation and maintenance of LTRS assets. FCRs are submitted to LISC Configuration Management for evaluation and implementation. When an FCR corrects an error or deficiency in a TO, it is processed via AFTO 22. When an FCR initiates a change to a TO that is not an error or deficiency, it is processed via the ECP process.

1.1.4 Technical Data Format/Delivery Changes

LTRS TOs are delivered and sustained in digital format. The delivery format is Indexed Portable Document Format (IPDF). Sustainment (source) file formats are identified in Table 2-1.

1.1.5 TO Concept of Operations (TO CONOPS)

Annex 9 contains the LTRS TO CONOPS. The objective of the LTRS TO CONOPS is to ensure that users have timely access to safe, accurate, and adequate information necessary to meet LTRS mission requirements.

1.2 Policy Specifications and Waivers

Contractors may request deviations from or waivers to requirements specified in the applicable Technical Manual Contract Requirements (TMCR). These requests must include objective justification and evaluation of the impact on: (1) time and material for the users (operating command or support agencies); (2) life-cycle cost of the publication and equipment covered by the publication; (3) acquisition cost; and (4) preparation and/or delivery in digital format. All deviations and waivers shall be submitted to the LTRS TO Manager for evaluation and coordination.

1.3 Program Summary

1.3.1 Weapon System Description

The LTRS provides the infrastructure used to provide safe and effective launch, testing, and tracking of Department of Defense (DoD), civil, and commercial spacelift vehicles, in addition to conducting ballistic missile, guided weapon, and aeronautical tests and evaluations. LTRS assets are organized into two ranges. The Eastern Range, which is operated by the SLD 45, is located at Cape Canaveral Space Force Station (CCSFS), Patrick Space Force Base (PSFB), Kennedy Space Center (KSC), and multiple remote operating locations. The Western Range, which is operated by the SLD 30, is located at Vandenberg Space Force Base (VSFB) and multiple remote operating locations.

1.3.2 Key Features

The LTRS consists of eleven subsystems: Communications, Data Handling, Positive Control, Optics, Radar, Range Safety, Surveillance, Modeling and Simulation, Telemetry, Timing and Sequencing, and Weather. Each subsystem contains Range Assets that operate as an integrated equipment group to provide a Range capability. For example, within the Radar Subsystem, the AN/MPS-39 Radar and

0.134 Radar are Range Assets.

1.4 TO Archiving Process

LTRS TOs are archived in the OM&S contractor’s Configuration Management (CM) status accounting tool, Windchill. Windchill stores the current, in-work, and historical versions of each TO. Data managed in each TO record includes the publication status; viewable TO in IPDF; TO source files;

applicable forms (AFTO 22, AFTO 27, and AFTO 252); and applicable ECP that initiated the new or updated publication.

2 New Equipment Acquisition

2.1 Initial Planning

New TO acquisition processes vary based on project requirements. For systems fielded by the LISC, TOs are acquired in accordance with the contract’s TM-86-01 and Statement of Work (SOW). As part of the project planning process, the Government Integrated Project Team (IPT) works with LISC to determine what types of TOs will be delivered and the processes that will be used to develop, review, and deliver the TOs. For systems fielded by outside contractors (contractors other than LISC), the Government IPT tailors the TM-86-01 and SOW prior to release of the Request for Proposal (RFP).

2.2 Scope of Requirements

LTRS TO types, applicable specifications, and source data formats are listed in Table 2-1.

Table 2-1. TO Types and Data Formats

IETM

Type Description Specification Source Format

Delivery Format

1 Operation and Maintenance (O&M) Manual with Circuit Diagrams and Illustrated Parts Breakdown

MIL-STD-38784,

MIL-M38798B

Unstructured Adobe FrameMaker

IPDF

Inspection and Preventive Maintenance Work Cards

MIL-DTL-5096F

Work Unit Code MIL-DTL-38769G

Software User Manual (SUM) DI-IPSC-81443A Microsoft Word

Legacy O&M Contractor Format

COTS MIL-PRF-32216 Not applicable

2.3 Reviews

Standard TO review processes include the following activities:

• TO Guidance Conference (TOGC) – The purpose of the TOGC is to present the TO development plan for stakeholder review; agree upon what, where, and when milestones are to be met; and clarify development tasks and planning data resulting from the project’s business proposal and program requirements.

• 35% IPR – The purpose of the 35% IPR is to ensure that TO development is proceeding according to the project plan, that proposed content satisfies contractual requirements, and update the stakeholder community on remaining tasks. 35% IPR content requirements are specified in TO 00-5-3.

• 75% IPR – The purpose of the 75% IPR is to ensure that TO development is proceeding according to the project plan, that content satisfies contractual requirements, and update the stakeholder community on remaining tasks. 75% IPR content requirements are specified in TO 00-5-3.

• TO Certification – The purpose of the TO Certification is to ensure that TOs are ready for TO Verification. TO Certification is a contractor event witnessed by the Government.

Procedures are performed on the equipment to validate their technical accuracy. Non-procedural information is validated by reviewing the engineering drawings, LMI, and physical configuration of the equipment.

• TO Verification – The purpose of the TO Verification is to ensure that TOs are accurate, adequate, safe, and usable in the operational environment. TO Verification is a Government event supported by the contractor. Procedures are performed on operationally-configured equipment to validate their technical accuracy. Non-procedural information is verified by reviewing the engineering drawings, LMI, and physical configuration of the equipment.

• PPR – The purpose of the PPR is to ensure that all redlines and action items identified during TO Verification have been completed and that the TOs are ready for final publication.

2.4 Data Formats

LTRS TO source data formats are listed in Table 2-1.

2.5 Type Manuals

LTRS TO types are listed in Table 2-1.

2.6 TMCR

This plan applies to multiple contracts. For specific TMCR information, see the Contract Data Requirements List (CDRL) package for the applicable contract.

2.7 Other Contract Documents

2.7.1 Statement of Work

This plan applies to multiple contracts. For specific information, see the statement of work for the applicable contract.

2.7.2 Special Contract Requirements (H-Clauses)

This plan applies to multiple contracts. For specific information, see the applicable contract.

2.7.3 Data Rights

Data rights for developed TOs are obtained in accordance with TM-86-01, paragraph 8. Data rights for commercial technical manuals are requested in accordance with the DFARS clause 252.227 7015, Technical Data-Commercial Items (November 1995), and request the right to use, modify, reproduce, perform, display, and disclose technical data for Government and Government contractor use only.

Data rights are reviewed as part of the Contractor Furnished Equipment Notice (CFEN) process, delivered with other project technical data artifacts, and maintained by the OM&S contractor.

2.7.4 Schedules

TO development and review milestones are included in each project’s Integrated Master Schedule (IMS). For projects that do not have an IMS, TO development and review milestones are identified and agreed upon during the TO Guidance Conference or Integrated Logistics Support (ILS) Technical Interchange Meeting (TIM).

2.7.5 Contract Deliverable Requirements List (CDRL)

This plan applies to multiple contracts. For specific CDRL information, see CDRL requirements for the applicable contract.

2.7.6 Contractor Furnished Equipment Notice (CFEN)

CFENs are evaluated and submitted to the government for review in accordance with the applicable

TMCR.

2.7.7 Verifications

TO verifications are conducted in accordance with each project’s TMCR, the LTRS TO Life Cycle Verification Plan, and TO 00-5-3.

2.8 TO Live Cycle Verification Plan (TOLCVP)

The LTRS TOLCVP is provided in Annex 5.

2.9 Contractor Information

LTRS TOs are developed by multiple contractors.

3 Sustainment

3.1 Transition

Final delivery of published TOs and source files is performed as part of the technical data transition process. Source files undergo a final Technical Data Assessment (TDA) to ensure that all required data is present to publish each delivered TO. After successful TDA, the published TO, source files, and approval artifacts are delivered to the OM&S contractor and Design Control Authority (DCA) transfers to the OM&S contractor.

3.2 Sustainment Overview

After transition, LTRS TOs are managed and sustained by the OM&S contractor for the life of the system. Configuration management is performed in the OM&S contractor’s CM status accounting tool, Windchill, versus the Enhanced Technical Information Management System (ETIMS).

Windchill stores the current, in work, and historical versions of each TO. Data managed in each TO record includes the publication status; viewable TO in IPDF; TO source files; applicable forms (AFTO 22s, AFTO 27s, and AFTO 252s); and applicable ECP information that initiated the new or modified publication.

When sustainment projects impact an existing TO, the OM&S contractor works with the government during project planning to define the scope of required TO changes and determine the most cost-effective and efficient method for implementing and reviewing the changes. The scope of TO changes and the processes used to review those changes vary based on project scope. When an outside contract impacts an existing LTRS TO, required changes are reviewed, certified, verified, and submitted to the OM&S contractor for implementation via AFTO 27.

When a system is divested, the OM&S contractor identifies TOs that require change or deactivation as part of the ECP process. When a TO is deactivated, its status in Windchill is changed from released to obsolete and all historical data is retained.

Delivery to the end user occurs electronically in Windchill. Users login to Windchill, locate, and download the latest released version of the TO.

3.3 Responsibilities

3.3.1 LTRS TO Manager Sustainment Responsibilities

The LTRS TO Manager is responsible for the following:

a. Providing overall management of LTRS TO acquisition and sustainment activities.

b. Providing TO policy guidance and procedural interpretation to LTRS managers, project officers, contractors, and other stakeholders.

c. Initiating agreements with the using command and support activities to resolve all TO risks and issues in a timely manner.

d. Ensuring that TOs are available to support the deployment of LTRS assets and associated commodities.

e. Approving transition of Preliminary Technical Orders (PTOs) to formal TOs based on Pre- Publication Review (PPR).

f. Conducting semi-annual TO Working Group meetings with LTRS TO stakeholders.

g. Updating this plan as required.

3.3.2 LTRS Logisticians and Equipment Specialists

LTRS logisticians and equipment specialist are responsible for the following on assigned projects:

a. Ensuring that technical manuals are accurate, safe, and meet LTRS operation, maintenance, and sustainment objectives.

b. Ensuring that operation and maintenance concepts documented in TOs are supported by other ILS elements, such as supply support, support equipment, and training.

c. Performing Verification Team Manager (VTM) responsibilities in accordance with the LTRS

TOLCVP.

3.3.3 Using and Lead Commands

The using commands are responsible for:

a. Representing Delta interests in program-level meetings, such as the TO Working Group.

b. Representing Delta interests in project-level meetings, such as the TO Guidance Conference, IPRs, and PPR.

c. Representing Delta interests during TO verification and providing Wing concurrence for TO verification.

d. Reviewing and providing Delta concurrence for AFTO 22 submissions.

3.4 Scope of TO Requirements

LTRS fields and manages TOs for organizational-level operation and maintenance. TOs are not developed or managed for depot-level maintenance. LTRS organizational-level TOs include the following types of Technical Manuals (TMs):

• O&M Technical Manuals with Circuit Diagrams and IPB. O&M TOs provide organizational-level operation and maintenance information for LTRS assets. Format requirements are based on MIL-STD-38784A and MIL-DTL-38807. Content requirements are based on MIL-M-38798B. When TM size warrants, Circuit Diagram TMs and the IPB TMs are delivered as separate manuals.

• Inspection and Preventive Maintenance Work Cards. Inspection and Preventive Maintenance Work Cards provide organizational-level inspection and preventive maintenance procedures. Content and format requirements are based on MIL-DTL-5096.

• Work Unit Code (WUC) TMs. WUC TMs provide WUCs for LTRS assets. Format and content requirements are based on MIL-DTL-38769G.

• COTS TMs. COTS TMs are used in conjunction with O&M TMs to provide operation and maintenance information for commercial products. COTS TMs are evaluated for use and delivered for LTRS use via the Contractor Furnished Equipment Notice (CFEN) process. The CFEN process ensures that data rights have been obtained; evaluates the safety and adequacy of the COTS TM in accordance with MIL-PRF-32216; identifies content that requires supplementation; and assigns the COTS TM a TO number.

• Legacy TMs. Legacy TMs are O&M TMs developed and delivered in contractor format prior to the introduction of TOs on the LTRS program (prior to 2000). Legacy TMs have been digitized and assigned TO numbers. Legacy TMs are sustained in their existing style and format.

• Software User Manuals (SUMs). SUMs are used to provide software operation and maintenance information. Content requirements are based on Document Item Description (DID) DI-IPSC-81443A and, when specified, MIL-STD-38784.

TO standardization is accomplished using a set of Adobe FrameMaker templates made available to all LTRS contractors. The templates, originally established at the beginning of program normalization in 2000, contain predefined formatting and content elements for each type of LTRS

TO.

Project-specific TO requirements are provided to development contractors in the applicable contract’s statement of work and TMCR. When clarification is required, additional guidance is provided at TO Guidance Conferences, TO review milestones, and TO Working Group meetings.

3.5 TO Preparation

TO preparation requirements are specified in the applicable TMCR.

3.5.1 Specification Interpretation Document (SID)

The LTRS does not use a SID.

3.5.2 Development Flow

LTRS TOs are developed from source technical data (engineering drawings, Logistics Management Information [LMI], and Original Equipment Manufacturer [OEM] data) and input from engineering and Operation and Maintenance (O&M) personnel.

For LISC projects, the development flow is dictated by the SOW TMCR, and individual project objectives, constraints, and milestones agreed upon during project planning. The development flow and milestones are intentionally flexible in order to facilitate the tailoring of project activities to the wide scope range of LISC projects. For outside contractors (contractors other than LISC), the development flow is dictated by the SOW and TMCR.

Flowcharts describing typical LTRS TO development flows are provided in Annex 7.

3.5.3 Reviews

3.5.3.1 In-Process Reviews (IPRs)

IPRs are conducted to evaluate the contractor’s progress and ensure that TOs meet contractual requirements, operation and maintenance requirements, and technical data sustainment requirements. IPRs are conducted in accordance with the contract’s SOW, CDRLs, and TMCR and include the following tasks:

a. The contractor delivers the review materials to the IPR Office of Primary Responsibility (OPR). The OPR is identified at the TO guidance conference and is typically the TO Manager or assigned project logistician or equipment specialist. Review materials include:

1. TOs being reviewed in deliverable format, IPDF.

2. Engineering drawings used as source data for the TO in Portable Document Format

(PDF).

3. Logistics data (Logistics Management Information [LMI], Logistics Support Analysis Record [LSAR], etc.) used as source data for the TO. Data may be provided in PDF or Microsoft Excel.

4. Source files required to perform a Technical Data Assessment (TDA).

b. The OPR posts the TO and source data for review in VisualRV.

Note Review details, such as personnel assignments and review duration, are determined by project requirements and agreed upon during the TO guidance conference.

c. Review personnel review the TO and enter comments, questions, and recommendations (hereafter referred to as IPR comments) into VisualRV. When a review is complete, the reviewer closes the review.

d. Once all reviewers have completed their review or the suspense date has been reached, the OPR closes the review and forwards the IPR comments to the contractor for disposition.

e. The contractor dispositions the IPR comments and includes them in the IPR meeting notice.

f. At the IPR, stakeholders review the IPR comments and dispositions.

g. After the IPR, the contractor updates IPR comment dispositions to reflect discussions conducted at the IPR.

h. After IPR comment dispositions are updated, the contractor forwards the draft IPR comment dispositions to the OPR for approval.

i. After OPR approval, the IPR comments are included in the IPR meeting minutes.

3.5.3.2 Pre-Publication Reviews (PPRs)

PPRs are conducted to review modifications to the TOs resulting from TO verification and verify that the completed TOs are ready for final publication.

3.5.3.2.1 Formal PPRs

Formal PPRs are conducted as follows:

a. The contractor delivers the review materials to the PPR OPR. The OPR is identified at the TO guidance conference and is typically the TO Manager or assigned project logistician or equipment specialist. Review materials include:

1. TOs being reviewed in deliverable format, IPDF.

2. Any engineering drawings used as source data for the TO that were updated as a result of the TO verification in PDF.

3. Any logistics data (LMI, LSAR, etc.) used as source data for the TO that were updated as a result of the TO verification. Data may be provided in PDF or Microsoft Excel.

4. Source files required to perform a TDA.

b. The OPR posts the TO and source data for review in VisualRV. PPR reviews are typically limited to the TO Manager and assigned logistician or equipment specialist.

Note Review details are determined by project requirements and agreed upon at the TO guidance conference.

c. Review personnel review the TO to ensure that verification comments have been successfully incorporated and that the TO is ready for final publication.

d. Review personnel enter comments, questions, and recommendations (hereafter referred to as PPR comments) into VisualRV. When a review is complete, the reviewer closes the review.

e. Once all reviewers have completed their review or the suspense date has been reached, the OPR closes the review and forwards the PPR comments to the contractor for disposition.

f. The contractor dispositions the PPR comments and includes them in the PPR meeting notice.

g. At the PPR, stakeholders review the PPR comments and dispositions.

h. After the PPR, the contractor updates IPR comment dispositions to reflect discussions conducted at the PPR.

i. After PPR comment dispositions are updated, the contractor forwards the draft PPR comment dispositions to the OPR for approval.

j. After OPR approval, the PPR comments are included in the PPR meeting minutes.

k. Once all comments are incorporated into the TO, the contractor delivers the final review copy and accompanying AFTO 252 to the OPR per paragraph 3.5.3.3.

3.5.3.2.2 Informal PPRs

When a formal PPR is not required, an informal PPR is conducted as follows:

Note Review details are determined by project requirements and agreed upon at the TO guidance conference.

a. The contractor delivers the review materials to the PPR OPR. The OPR is identified at the TO guidance conference and is typically the TO Manager or assigned project logistician or equipment specialist. Review materials include:

1. TOs being reviewed in deliverable format, IPDF.

2. Any engineering drawings used as source data for the TO that were updated as a result of the TO verification in PDF.

3. Any logistics data (LMI, LSAR, etc.) used as source data for the TO that were updated as a result of the TO verification. Data may be provided in PDF or Microsoft Excel.

4. Source files required to perform a TDA.

b. The assigned reviewers review the TO to ensure that verification comments have been successfully incorporated and that the TO is ready for final publication.

c. Review personnel discuss comments, questions, and recommendations directly with the contractor. If changes are required, the contractor completes the updates and delivers the updated TO to the OPR as required.

d. Once all comments are incorporated into the TO, the contractor delivers the final review copy and accompanying AFTO 252 to the OPR per paragraph 3.5.3.3.

3.5.3.3 AFTO 252 Submission

Upon completion of the PPR, the AFTO 252 is routed for approval as follows:

a. The contractor delivers the final review copy and AFTO 252 to the OPR, typically the assigned logistician or equipment specialist.

b. The OPR signs the AFTO 252.

c. The OPR forwards the AFTO 252 to the TO Manager for approval.

d. The TO Manager signs the AFTO 252 and retains a file copy.

e. The TO Manager returns the signed copy to the OPR and contractor.

f. Once the contractor receives the AFTO 252, the TO is approved for final delivery in accordance with applicable SOW, CDRL, and TMCR.

3.5.4 Quality Assurance Process

Government Quality Assurance (QA) is conducted via reviews (IPRs and PPRs) and TO verifications.

A detailed description of the IPR process is described in 3.5.3. A detailed description of the TO verification process is described in the LTRS TO Life Cycle Verification Plan.

3.5.5 Responsibilities

3.5.5.1 TO Manager Responsibilities

The LTRS TO Manager is responsible for the following:

a. Providing overall management of LTRS TO acquisition, sustainment, and management.

b. Initiating agreements with the using command and support activities to resolve all TO difficulties in a timely manner.

c. Ensuring that TOs are available to support the deployment of LTRS assets and associated commodities.

d. Chairing LTRS TO Working Group meetings.

e. Plan and implement updates to LTRS TO processes and requirements.

f. Update this plan as required.

3.5.5.2 Technical Content Manager (TCM) Responsibilities

The TCM is responsible for the following:

a. Ensuring that TO content is:

1. Accurate, safe, comprehensive, and adequate to support LTRS operation, maintenance, and sustainment requirements.

2. Consistent with associated technical data, such as engineering drawings and LMI/LSAR data.

3. Supports LTRS maintenance and supply support concepts defined in the LTRS Life Cycle Support Plan.

b. Coordinating with the TO Manager to conduct TO Guidance Conferences, IPRs, PPRs, and TO verifications.

c. Serving as the VTM in accordance with the LTRS TO Life Cycle Verification Plan.

d. Working with Government stakeholders during project planning to ensure that project-level requirements support LTRS TO program objectives.

3.5.5.3 Engineering Responsibilities

Engineering responsibilities include the following:

a. Ensuring that TO content is:

1. Accurate, safe, comprehensive, and adequate to support LTRS operation, maintenance, and sustainment requirements.

2. Supports LTRS maintenance and supply support concepts defined in the LTRS Life Cycle Support Plan.

b. Supporting TO Guidance Conferences, IPRs, PPRs, and TO verifications as required.

c. Working with Government stakeholders during project planning to ensure that project-level requirements support LTRS TO program objectives.

3.5.6 Classified TO Reviews

The LTRS does not perform classified TO reviews because all LTRS TOs are unclassified.

3.5.7 Verifications, PTO, and Formalization Processes

3.5.7.1 TO Verification Process

See the LTRS TO Life Cycle Verification Plan (TOLCVP).

3.5.7.2 PTO Process

See the LTRS TOLCVP.

3.5.7.3 Formalization Process

See paragraph 3.5.3.3.

3.6 TO Security and Information Assurance

LTRS TOs are unclassified.

3.6.1 Classified Data Control, Controlled and Unclassified information Because LTRS TOs are unclassified, there are no classified data control or update processes. LTRS TOs (and other technical data) are accessed via the OM&S contractor’s CM status accounting tool, Windchill. Access is requested via DD 2875, System Authorization Access Request (SAAR), and is granted on a need-to-know basis.

3.6.2 Cybersecurity Procedures

Cybersecurity processes are conducted in accordance with the LTRS Program Protection Plan, dated 20 July 2018.

3.7 TO Change Process

3.7.1 OM&S TO Change Processes

The LTRS employs multiple change processes in order to support rapid and cost-effective delivery of TO sustainment updates to the LTRS user community. During project planning, the Delta, development contractor, and OM&S contractor evaluate the scope of work and determine the appropriate TO change process based on the scope of work and mission requirements. Available TO change processes are described below.

3.7.1.1 TO Change/Revision

The TO Change/Revision Process is used to complete TO changes whose scope or complexity require discrete review milestones. The TO Change/Revision Process includes a TO Guidance Conference, 75% IPR, TO Certification, TO Verification, and PPR. TO Certification and TO Verification may be conducted as separate events or combined into a single event. When a combined event is proposed, all requirements associated with TO Verification shall apply to the combined event. PPR may be conducted as a formal or informal event based on project requirements.

3.7.1.2 Rapid Action Change (RAC)

The RAC Process is used to complete TO changes that require procedural changes that are small in scope or require rapid delivery to the LTRS user community. The RAC Process includes a TO Guidance Conference, contractor dry-run of procedural information, TO Verification, and informal

PPR.

3.7.1.3 AFTO 252 Change Process

The AFTO 252 Change Process is used to complete non-procedural TO changes. The AFTO 252 Change Process includes a desktop TO Verification and informal PPR.

3.7.2 Outside Contractor Change Processes

When an outside contract (a contractor other than the OM&S contractor) impacts an existing LTRS TO, required changes are reviewed, certified, verified, and submitted to the OM&S contractor for implementation via AFTO 27. The Outside Contractor Change Process includes a TO Guidance Conference, 75% IPR, TO Certification, TO Verification, and PPR. After the AFTO 27 is approved by the Government, the changes are implemented by the OM&S contractor.

3.7.3 Weapon System TO Change Process

The weapon system TO change process is identical to the TO change/revision process described in paragraph 3.7.1.1.

3.7.4 Inter-Service/FMS Relationships with TOs and TCTOs

LTRS assets are managed solely by the Space Force and do not currently require Inter-Service or Foreign Military Sales (FMS) coordination. In the event that common equipment within LTRS assets are impacted by a Time Compliance Technical Order (TCTO), equipment modifications and TO changes are implemented using LTRS CM change processes.

3.8 Distribution Strategy

Delivery of LTRS TOs to the end user occurs electronically in the OM&S contractor’s CM status accounting tool, Windchill. Users login to Windchill, locate, and download the latest released version of the TO. TOs may be accessed via searches by TO number, TO title, applicable ECP, and work center.

A cost benefit analysis was conducted on the use of ETIMS during the SLRS contract. The cost benefit analysis concluded that requiring the OM&S contractor to capture and prepare metadata for import into ETIMS and subsequently managing over 7,000 TOs in two systems (Windchill and ETIMS) duplicates distribution and management costs with no benefit to the LTRS program and that benefits to non-LTRS users did not justify the costs.

3.8.1 Distribution Contingency

Windchill is the primary distribution mechanism for LTRS TOs. Windchill is hosted in a virtual environment in order to mitigate potential service interruptions caused by inoperable hardware or software. Prior to the current OM&S contract, printers were procured for work sites to enable printing of hard copy TOs to support usability and disaster mitigation.

3.9 Long-Term TO Management Strategy

The long-term LTRS management strategy is composed of two high-level objectives and a number of enabling objectives. High-level objectives include:

• Ensure that LTRS users possess the information they need to effectively and safely operate, maintain, and sustain LTRS assets.

• Employ flexible, agile processes that right-size TO deliverables to meet mission, cost, and schedule constraints.

Enabling objectives include:

• Standardization and automation of TO development activities across the enterprise with the goal of delivering effective TOs quickly and at the lowest possible life cycle costs.

• Refinement of TO content requirements to ensure that only essential mission content is provided. Non-essential content will be eliminated in order to improve usability while delivering capabilities faster and at lower life cycle costs.

• Training and mentoring LTRS personnel, both Government and contractor, so that all stakeholders understand program goals, contract requirements, and available trade space.

The program’s long-term strategy is reviewed on an annual basis and subsequent short-term strategies are recommended and pursued via regularly scheduled TO Working Group meetings chaired by the TO Manager.

3.10 Funding

LTRS TO funding is provided by a combination of Comprehensive Technical Order Plan (CAFTOP), 3010, and 3400 funding. The OM&S contract includes CAFTOP fuding within CLIN 2 to fund management and sustainment or LTRS TOs.

Development of new TOs for Government-funded projects is funded from 3010 and 3040 funds based on project type.

4 TOLCMP Annual Review

Table 4-1. TOCLMP Annual Review

Year Revision Date

2022 Initial Release 8 August 2022

Year Revision Date

5 System Retirement When a range asset is removed from the LTRS baseline configuration, all technical data is updated to reflect divestiture of the range asset. TO updates include TO changes and TO deactivation. When a TO is deactivated, its state in Windchill is changed from released to obsolete. Obsolete TOs are retained in Windchill indefinitely.

6 Annex

6.1 Annex 1 – List of Acronyms

Term Meaning

ACAT Acquisition Category

AF Air Force

CAFDEx Centralized Access of Data Exchange

CCSFS Cape Canaveral Space Force Station

CDR Critical Design Review

CDRL Contract Data Requirements List

CFEN Contractor Furnished Equipment Notice

CLS Contractor Logistics Support

CM Configuration Management

CONOPS Concept of Operations

COTS Commercial off-the-Shelf

CSDB Common Source Database

DCA Design Control Authority

DoD Department of Defense

DT&E Developmental Test & Evaluation

ERCDM Eastern Range Command Destruct Modernization

ECP Engineering Change Proposal

ETIMS Enhanced Technical Information Management System

FCA Functional Configuration Audit

FCR Field Change Request

Term Meaning

FMS Foreign Military Sales

FY Fiscal Year

GOES-R Geostationary Operational Environmental Satellite R Series

IETM Interactive Electronic Technical Manual

IPB Illustrated Parts Breakdown

IPDF Indexed Portable Document Format

IPR In-Process Review

IPT Integrated Project Team

IRR Installation Readiness review

KSC Kennedy Space Center

LISC Launch and Test Range System Integrated Support Contract

LMI Logistics Management Information

LSAR Logistics Support Analysis Record

LTRS Launch and Test Range System

MIL-STD Military Standard

O&M Operation & Maintenance

O&S Operation and Sustainment

OA Operational Acceptance

OEM Original Equipment Manufacturer

OM&S Operation, Maintenance & Sustainment

OPR Office of Primary Responsibility

PSFB Patrick Space Force Base

PCA Physical Configuration Audit

PDF Portable Document Format

PME Prime Mission Equipment

PPR Pre-Publication Review

PTO Preliminary Technical Order

RAC Rapid Action Change

RFP Request for Proposal

RRB Readiness Review Board

SAAR System Authorization Access Request

SID Specification Interpretation Document

SOW Statement of Work

Term Meaning

SSC Space Systems Command

SUM Software User Manual

TBD To be determined

TCTO Time Compliance Technical Order

TDA Technical Data Assessment

TIM Technical Interchange Meeting

TM Technical Manual

TMCR Technical Manual Contract Requirements

TMOP Technical Manual Organization Plan

TO Technical Order

TOGC TO Guidance Conference

TOLCMP Technical Order Life Cycle Management Plan

TOLCVP Technical Order Life Cycle Verification Plan

WMN Western Range Modernization Network

VSFB Vandenberg Space Force Base

VTM Verification Team Manager

6.2 Annex 2 – Definitions of Common Terms

Term Meaning

Certification Contractor written assurance that manuals and source data are current, adequate, accurate, safe, and conform to contract requirements

Commercial off-the- Shelf Manuals

Commercial off-the-Shelf (COTS) manuals are manuals available off-the-shelf from a commercial source that include operation, maintenance, or other information for commercial equipment.

Commercial manuals are prepared to support the equipment in the commercial market.

IPDF Indexed Portable Document Format is a PDF that possesses the following navigation features:

• Text-searchable

• Chapter and paragraph heading bookmarks

• Hyperlinked cross-references

• Hyperlinked table of contents, list of illustrations, and list of tables entries

Term Meaning

Preliminary Technical Order

Preliminary Technical Orders (PTOs) are in-work drafts of TOs from initial assignment of TO numbers until formalization/publication.

PTOs are assigned a TO number and are identified by a warning and the word PRELIMINARY on the title page. PTOs will contain Verification Status Pages documenting the verification status of the PTOs content.

Pre-Publication Review A final review of a TO, prior to formalization/publication, to ensure that all verification comments have been incorporated and that the TO conforms to all specification and contract requirements.

Verification Verification is the process through which Space Force personnel evaluate and prove that TOs, TO updates, and Time Compliance Technical Orders (TCTOs) are adequate, accurate, safe, and usable to support the using command’s operation and maintenance concepts.

6.3 Annex 3 – Policy Specifications and Waivers

The attached waiver is currently in coordination. It updates and formalizes previous AFSPC approval to maintain LTRS TOs outside of ETIMS.

TO Waiver - PSM Signed.pdf

6.4 Annex 4 – TMCRs

LISC

TMCR LISC.pdf

WMN

TMCR WMN.pdf

6.5 Annex 5 – Technical Manual Organization Plan (TMOP)

TMOPs are not currently required on the LTRS program.

6.6 Annex 6 – Flowcharts

Figure 6-1. Typical TO Milestones

Figure 6-2. AFTO 252 Process

Figure 6-3. AFTO 27 Outside Contractor Process

Figure 6-4. Outside Contractor TO Transition Process

6.7 Annex 7 – TO Concept of Operations

TO CONOPS.pdf

1.4 TO Archiving Process

3.5.3.3 AFTO 252 Submission