TOLCVP LTRS 220808.pdf

UNCLASSIFIED

TECHNICAL ORDER LIFE CYCLE

VERIFICATION PLAN (TOLCVP)

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

This page is intentionally blank.

i

TABLE OF CONTENTS

Paragraph Page

1 Introduction

2 Purpose

3 Scope

4 References

5 Verification Plan General Provisions

5.1 General

5.2 Organizational Structure

5.2.1 TO Acquisition Team

5.2.2 Verification Team Membership

5.3 Definitions

5.4 Policy

5.4.1 Contractor Certification

5.4.2 Verification Prerequisites

5.4.3 Verification Scheduling

5.4.4 Verification by Performance

5.4.5 Legacy Technical Data

5.4.6 Verification by Desktop Analysis

6 Responsibilities

6.1 LTRS TO Manager

6.2 Verification Team Manager (VTM)

6.3 Development Contractor Personnel

6.4 O&M Contractor Personnel

7 Procedures for Verification

7.1 General Procedures

7.2 Verification by Performance

ii

7.3 Verification by Desktop Analysis

7.4 Discrepancies

8 Administrative Procedures

9 Glossary

10 Forms

1 Introduction This plan establishes policy, defines terminology, assigns responsibility, and specifies process requirements for the Space Force TO Life Cycle Verification Program. This plan applies to all Launch and Test Range System (LTRS) TO verification activities, including those at using command bases, remote sites, depots, and contractor facilities.

2 Purpose The purpose of this plan is to establish LTRS objectives, requirements, responsibilities, and process requirements for the LTRS TOLCVP.

3 Scope This plan applies to the verification of contractor-approved Preliminary TOs (PTOs) for the LTRS.

4 References Launch and Test Range System (LTRS) Technical Order Life Cycle Management Plan (TOLCMP).

Launch and Test Range System (LTRS) Life Cycle Sustainment Plan.

5 Verification Plan General Provisions

5.1 General

This plan establishes the management relationship between SLD 45/RM; SLD 30/RM; using commands; development contractors; Operation, Maintenance and Sustainment (OM&S) contractors; and other stakeholder organizations. All LTRS TO verifications shall be managed in accordance with applicable references and this plan.

5.2 Organizational Structure

5.2.1 TO Acquisition Team

LTRS TO acquisition is performed by SLD 45/RM and SLD 30/RM. Key members of the team include the Space Force Project Manager, LTRS TO Manager, and applicable Integrated Logistics Support Manager (ILSM) and Equipment Specialist.

5.2.2 Verification Team Membership

The TO verification team includes the following members:

a. SLD 45/RM and/or SLD 30/RM

1. LTRS TO Manager

2. ILSM

3. Equipment Specialist

4. Maintenance Representative

b. Development Contractor

1. Technical Writer

2. Development Engineer

3. Logistician

c. OM&S Contractor

1. Operations and Maintenance (O&M) personnel

2. Integration Engineer (optional)

d. SE&I Contractor

1. SE&I Logistician or Equipment Specialist

5.3 Definitions

See paragraph 9.

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.

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.

5.4 Policy

Overall verification policy is specified in TO 00-5-3. Unless otherwise specified by the LTRS TO Manager, the Verification Team Manager (VTM) or designated representative has the authority to chair all verification meetings in accordance with approved schedules and this document. The goal is one hundred percent verification of all procedures prior to initial deployment of the system/commodity. Verification of procedures shall be accomplished in accordance with paragraph

5.4.4 unless otherwise authorized by the LTRS TO Manager. All verification changes shall be reviewed and approved/disapproved by the VTM.

5.4.1 Contractor Certification

Verification shall begin only after procedures/data have been certified by the contractor.

5.4.2 Verification Prerequisites

The following tasks/deliverables are required prior to conducting verification:

a. TO certification

b. Training

c. Delivery of Contractor Furnished Equipment Notice (CFEN) packages for all referenced COTS manuals

d. Functional Configuration Audit/Physical Configuration Audit (FCA/PCA)

e. Contractual requirements or waivers that impact verification

5.4.3 Verification Scheduling

Prior to scheduling a verification effort, the VTM shall ensure that all required assets and resources are available for the verification. The VTM or designated representative shall notify all participants of the scheduled verification.

5.4.4 Verification by Performance

Verification by actual performance shall be accomplished on all procedural data to the maximum extent possible; however, procedures that activate one-time devices, may result in equipment degradation or damage, or expose personnel to injury may be verified by simulation or desktop analysis. Troubleshooting procedures requiring destructive action to equipment shall not be accomplished by performance unless directed by the LTRS TO Manager.

5.4.5 Legacy Technical Data

Previously verified technical data converted into a new format (from Word to FrameMaker for example) will be re-verified in accordance with TO 00-5-3. Re-verification is the desktop comparison of existing information written in the original TO format against new TO format.

5.4.6 Verification by Desktop Analysis

Illustrated Parts Breakdowns (IPBs), theory of operation, and other non-procedural data shall be verified by desktop analysis.

6 Responsibilities

6.1 LTRS TO Manager

The LTRS TO Manager is responsible for the following:

a. Provide overall management for the acquisition of TOs required for the operation and maintenance of LTRS assets.

b. Update this plan as required.

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

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

e. Approve/disapprove recommendations for updates that the verification team cannot resolve.

f. Provide disposition on verification team recommendations that affect the contract.

g. Approve transition of PTOs to formal TOs based on Pre-Publication Review (PPR).

6.2 Verification Team Manager (VTM)

The VTM is responsible for the following:

a. Implement this TOLCVP for all LTRS TOs.

b. Serve as the focal point for TO verification.

c. Assist the LTRS TO Manager as applicable.

d. Ensure that all required resources are in place to support verification.

e. Convene pre-verification meetings to plan actions and assign tasks.

f. Supervise TO verification to ensure maximum completion of TO verification prior to formalization.

g. Convene post-verification meetings to discuss and resolve discrepancies.

h. Submit TO verification status updates to LTRS TO manager and designated recipients when requested by the LTRS TO Manager or Space Force Project Manager.

i. Chair meetings when requested by the LTRS TO Manager.

6.3 Development Contractor Personnel

The development contractor is responsible for scheduling, staging, and coordinating resources required for TO verification. This includes, but is not limited, to the following:

a. Technical Data

1. Certified PTOs

2. COTS TOs

3. Software User Manuals (SUMs)

4. Engineering drawings

5. Logistics Management Information (LMI)

b. Equipment

1. Site access

2. Operationally-configured Prime Mission Equipment (PME)

3. Support equipment

4. Spares (when required to verify post-replacement configuration procedures)

c. Personnel

1. Representative with contractor signature authority for technical updates

2. Engineering personnel support

3. Technical writing personnel support

4. Logistics personnel support

5. Operations and Maintenance (O&M) personnel support

6. Depot personnel support

6.4 O&M Contractor Personnel

The O&M contractor is responsible for providing:

a. Access to equipment and materiel required to conduct the verification.

b. Personnel resources required to perform the verification. For example, in the event that a verification requires a communications technician, telemetry technician, and system administrator, all personnel shall be available to support the verification.

7 Procedures for Verification

7.1 General Procedures

a. The VTM and contractor representative shall establish the verification schedule based on the availability of contractor-approved PTOs and required verification resources. The verification schedule should, at a minimum, consider the following resource requirements:

1. Access to PME

2. Support equipment requirements

3. Spares (required for post-replacement configuration)

4. O&M personnel skill sets and quantities required for each day (types and number of O&M personnel required to support scheduled verification activities)

5. Development contractor personnel skill sets and quantities (types and number of development contractor personnel required to support scheduled verification activities)

b. Verification shall be accomplished on-site using paper copies. Verification of electronic functionality, such as bookmarks and hyperlinks, shall be accomplished off-site.

c. Unresolved or contractual issues shall be sent to the LTRS TO Manager for disposition.

7.2 Verification by Performance

a. All procedural information shall be verified in accordance with paragraph 5.4.4.

b. Read steps aloud, and then perform the step.

c. Perform one step at a time.

7.3 Verification by Desktop Analysis

a. All non-procedural information shall be verified by desktop analysis.

b. Verification by inspection is the equivalent of desktop analysis.

c. IPBs shall be verified using the physical configuration, engineering drawings, and LMI.

d. Equipment elevations shall be verified using the physical configuration and engineering drawings.

e. Controls and indicators shall be verified using the physical configuration.

f. Circuit diagrams shall be verified using the physical configuration and engineering drawings.

g. Work Unit Codes (WUCs) using the draft Reliability and Maintainability Information System (REMIS) table.

7.4 Discrepancies

a. The contractor shall annotate discrepancies in the contractor master copy.

b. The VTM shall annotate discrepancies in the government master copy.

c. If discrepancies are extensive, the VTM may request incorporation of redlines during the verification event in order to support re-verification of corrected information.

d. Engineering drawing discrepancies shall be addressed by contractor engineering personnel.

e. LMI, support equipment, supply support, and other product support discrepancies shall be addressed by contractor logistics personnel.

f. Participating verification team members shall coordinate on discrepancies and corrective actions during post-verification meetings.

g. All discrepancies and corrective actions shall be addressed prior to PPR.

8 Administrative Procedures

a. The VTM is responsible for completing AFTO 27s for each TO being verified.

b. At the successful conclusion of TO verification, the TO verification team documents their approval on the AFTO 27.

c. The contractor master copy documenting verification discrepancies shall be retained until successful completion of PPR.

d. The government master copy documenting verification discrepancies shall be retained until successful completion of PPR.

e. Completed AFTO 27s shall be retained in OM&S contractor’s configuration management status accounting tool, Windchill, with the applicable TO record.

9 Glossary

Term Meaning

AF Air Force

CFEN Contractor Furnished Equipment Notice

COTS Commercial off-the-Shelf

FCA/PCA Functional Configuration Audit/Physical Configuration Audit

IETM Interactive Electronic Technical Manual

ILSM Integrated Logistics Support Manager

IPB Illustrated Parts Breakdown

LMI Logistics Management Information

LTRS Launch and Test Range System

O&M Operation & Maintenance

OM&S Operation, Maintenance & Sustainment

PDF Portable Document Format

PME Prime Mission Equipment

PPR Pre-Publication Review

PTO Preliminary Technical Order

REMIS Reliability and Maintainability Information System

SF Space Force

SUM Software User Manual

TCTO Time Compliance Technical Order

Term Meaning

TO Technical Order

TOLCMP Technical Order Life Cycle Management Plan

TOLCVP Technical Order Life Cycle Verification Plan

VTM Verification Team Manager

WUC Work Unit Code

10 Forms

Form Title

AFTO 27 Preliminary Technical Order (PTO) Publication Change Request (PCR)/TO Verification Record/Approval

Signature 2 Date: 10/18/22