RFP_Attachment_19_TOLCMP_Guide.pdf

TOLCMP Rev 4. 15 June 2015

“DISTRIBUTION STATEMENT A. Approved for public release.”

Attachment 19

Technical Order Management Agency Guide for the Development and Sustainment of the

Technical Order Life Cycle Management Plan

This guide is intended to assist the Technical Order Management Agency (TOMA) with the development and sustainment of a comprehensive Technical Order Life Cycle Management Plan

(TOLCMP). It does not replace guidance in Technical Order (TO) 00-5-3. The intent is to provide a source of lessons learned from across the commands that facilitate the best documentation for development and sustainment of USAF TOs.

This guide provides instructions and requirements for completing the embedded TOLCMP template. It applies to all United States Air Force (USAF) TO production and/or sustainment organizations and programs. The TOLCMP template contains the minimum requirements;

therefore, all paragraphs are required to be completed. Paragraph numbering and titles may not be changed or modified. If information in a particular paragraph does not apply to a program, annotate with N/A next to it. Program unique requirements may be added to the end of each affected paragraph. The completed TOLCMP is a tailored document; therefore it is unnecessary to add a (T) to each paragraph to indicate additional tailoring.

Do not include any classified information in the TOLCMP. Modify acronyms and definitions of terms as needed at Annex 1 and 2.

NOTE: Read this guide in its entirety prior to writing the TOLCMP. Delete ALL italicized notes preceding final completion of TOLCMP.

1.0 PURPOSE

1.2 INTRODUCTION

1.2.1 Technical Data Life Cycle Changes

1.2.2 Recommended Change Processors

1.2.3 Technical Data User Changes

1.2.4 Technical Data Format/Delivery Changes “Improvements”

1.2.5 TO Concept Of Operations (TO CONOPS)

1.2.6 Common Source Database (CSDB)

1.3 POLICY SPECIFICATIONS and WAIVERS

1.4 PROGRAM SUMMARY

1.4.1 System Description

1.4.2 Key Features, KPPs and KSAs

1.5 AIR FORCE TO ARCHIVING PROCESS

1.5.1 Location / Name of Program Archive Repository

2.0 NEW EQUIPMENT ACQUISITION

2.1 INITIAL PLANNING

2.2 SCOPE OF TO 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 Objectives (SOO) / Statement of Work (SOW)

2.7.2 Special Contract Requirements (H-Clauses)

2.7.3 Data Rights

2.7.4 Schedules

2.7.5 Contract Deliverable Requirement List (CDRL)

2.7.6 Contractor Furnished Aeronautical Equipment/Contractor Furnished Equipment (CFAE/CFE)

Notices 10

2.7.7 Verifications

2.8 TOLCVP

2.9 CONTRACTOR INFORMATION

2.9.1 Contractor Developed Technical Manual Organization Plan (TMOP)

3.0 SUSTAINMENT

3.1 TRANSITION

3.2 SUSTAINMENT OVERVIEW

3.3 RESPONSIBILITIES

3.3.1 Sustainment Responsibilities for TOMA

3.3.2 Sustainment Responsibilities for Database Managers

3.3.3 Using and Lead Commands

3.3.4 TO Site Functional Office

3.4 SCOPE OF TO REQUIREMENTS

3.5 TO PREPARATION

3.5.1 Specification Interpretation Document

3.5.2 Developmental Flow

3.5.3 Reviews: IPR’s, Pre- and post-publication reviews

3.5.4 Quality Assurance Process

3.5.5 Responsibilities: TOMA, TCM, ES, Engineering, Editorial Support (Contractor/Organic) support

3.5.6 Classified TO Reviews

3.5.7 Verifications, Preliminary TO, Formalization

3.6 TO SECURITY and INFORMATION ASSURANCE

3.6.1 Classified Data Control, Controlled and Unclassified information

3.6.2 Cyber Security Procedures

3.7 TO CHANGE PROCESS

3.7.1 Weapon System TO Change Process

3.7.2 Inter-Service/FMS Relationships with TOs and TCTOs

3.8 TO DISTRIBUTION STRATEGY

3.8.1 Distribution Contingency

3.9 LONG TERM TO MANAGEMENT STRATEGY

3.10 FUNDING

3.11 APPROVAL

4.0 TOLCMP ANNUAL REVIEW

5.0 AIRCRAFT or SYSTEM RETIREMENT

6.0 ANNEX

1.0 PURPOSE

The TOLCMP provides management policy, assigns responsibilities, defines terminology and specifies unique procedures for the weapon System TO Program. The plan provides basic instructions for development, contractor Quality Assurance (QA), verification and formalization of weapon system TOs during the program acquisition phase, and maintenance/sustainment of the TOs after formalization. The plan applies to all acquisition activities, including those at using command bases, Air Logistics Center (ALC) /Complex and contractor/subcontractor facilities, and minor sustainment acquisition. The plan is developed in accordance with requirements of TO 00-5-3 and is intended to cover the entire weapons system life cycle from cradle to system retirement.

A TOLCMP is mandatory for all programs listed on the USAF Program Master List or

Acquisition Master List (AML) and highly encouraged for all other programs when TOs must be developed or are impacted. Any changes in scope or increase in requirements will be documented in your TOLCMP.

If a program is sustained organically, the TOLCMP should be written as per this guide adding any additional unique information. The TOMA must consult the TO Home or Functional Site office for advice, assistance and establishing coordination requirements when developing a

TOLCMP for TO requirements when acquiring technical data developed IAW S1000D.

If a program will be sustained by the contractor for life, the TOMA must engage with the

Contractor in writing the requirements using this guide and must also define the role of the

Contractor’s sustainment responsibility. Consideration must be given to the number of changes to be issued annually, a surge capability for Urgent or Emergency situations and the flow of recommended changes must be addressed.

1.2 INTRODUCTION

The TOLCMP should describe the programs/weapons system TOMA management approach to acquire and sustain TOs for their program life cycle. The plan should amplify the TO portion of the programs/weapons system Life Cycle Sustainment Plan (LCSP). It should outline management responsibilities, the program establishment, timelines, program guidelines, implementation procedures, initiatives and any other unique requirements. The plan will be developed and maintained by the TOMA in coordination with the Lead Command, based on the most current information available at the time of publication. It will be amended as the program changes affect TO management plans and as the program matures. Technical data has a life cycle that can span decades. From the time the data is initially conceived, created, tested, verified and deployed, it will go through a number of changes. The TOLCMP is not a static management document. Each time a change occurs the TOLCMP shall be updated as required and reviewed annually during the Comprehensive Air Force Technical Order Plan (CAFTOP) update IAW TO 00-5-3. Copies of the TOLCMP and all updates shall be sent to the TO

Functional Site Office at the PM location IAW TO 00-5-3.

1.2.1 Technical Data Life Cycle Changes

This section shall be used to describe the total TO Development flow. Provide any significant technical data life cycle changes for the TO program. As changes occur over time, provide notes linked to the affected paragraph describing situations that need to be addressed for that portion of the life cycle. Failure to address these issues within the document can lead to problems along the way if not aware of potential pitfalls through lack of experience. Some items to consider incorporating are:

Initial acquisition concept development

Preliminary engineering data

Contractor certification documents

Government verification of contractor certified data

Field suggested improvements

Technology insertions

Technical data delivery mechanisms

1.2.2 Recommended Change Processors

Describe key change processors consistent with the items below as appropriate:

Interim Contractor Support (ICS)

Original Equipment Manufacturer (OEM) commercial item sustainment

OEM sole source sustainment contract

Competitive contractor sustainment contract

Government use of task order contracts

Organic sustainment

1.2.3 Technical Data User Changes

Provide a description of technical data change responsibilities from Acquisition to Sustainment to include Depot and Flight Manuals from Operational Users, Lead/Using Command and Joint

Services IAW 00-5-1 or as applicable.

AFTO Form 22

AFTO Form 27

AFTO Form 107/202

AFTO Form 847

1.2.4 Technical Data Format/Delivery Changes “Improvements”

Provide the programs description of data format/deliverable changes or improvements for formats such as Paper (mil-standard, commercial), PDF (standalone, indexed), Digital (HTML, SGML, XML) and embedded in equipment. If TOs cannot be delivered as originally scheduled, TOMA should update the TOLCMP reflecting the reasoning.

1.2.5 TO Concept Of Operations (TO CONOPS)

Provide the programs TO CONOPS. It should be developed for all new programs defining the users vision for operation and use of TO’s being developed and how the TOs will support operations and maintenance of the system. Attach at Annex 9.

1.2.6 Common Source Database (CSDB)

Describe how your program will maintain the CSDB for the life of the program and list the

CSDB manager’s responsibilities for maintaining it.

1.3 POLICY SPECIFICATIONS and WAIVERS

Contractors may request the TOMA to apply for deviations from or waivers to provisions in

Technical Manual Specifications and Standards (TMSS). These requests must include an objective justification and evaluation of the impact on: (1) time and material for the users

(operating command and 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. The TOMA will submit waiver requests IAW TO 00-5-3 and AFMCI 21-301. All waiver requests should be coordinated through local, TO site office, who in turn will coordinate with AFLCMC/LZSA Home Office and HQ A4FI. Provide TO Programs Policy Specifications and Waivers and attach at Annex 3.

1.4 PROGRAM SUMMARY

Provide in narrative form a program summary of the weapon/program being supported.

(Example): The XXX is intended to replace the USAF’s aging fleet of XXXX, which has been the primary refueling aircraft for more than 50 years. The XXX will be able to be refueled as well as refuel any fixed-wing receiver capable aircraft on any mission. Modifications make the

XXXX capable of aerial refueling United States, North Atlantic Treaty Organization (NATO) and allied aircraft requiring both hose and drogue. The XXX will also perform cargo, passenger and aeromedical evacuation, as well as Command, Control, Communications and Computers

(C4) augmentation secondary missions.

1.4.1 System Description

Provide a system description of the weapon system/ program being supported.

(Example): The XXX is based on the commercial XXX Extended Long Range Freighter aircraft and has been modified to enable aerial refueling. Compared to the XXX, it features increased refueling capacity; enhanced cargo and aeromedical evacuation capabilities; improved fuel efficiency; enhanced self-protection and defensive measures that will allow it to operate “closer to the fight”.

1.4.2 Key Features

Provide a brief description of your Aircraft or weapon system Key Performance Parameters

(KPPs) and Key System Attributes (KSAs).

(Example): The XXX is based on the commercial Boeing 767 to enable aerial refueling. KPPS and KPAs key features are Engines, APU, Cargo and fuel capacity, range, etc.

Engines. The XXX is equipped with two Pratt & Whitney PW4062 high-bypass turbofan engines generating 62,000 pounds of thrust each, mounted under 34-degree swept wings, providing increased fuel efficiency and sufficient takeoff power for gross weights up to 415,000 pounds.

1.5 AIR FORCE TO ARCHIVING PROCESS

Provide program archiving process. One copy of every published TO and TCTO increment

(basic, revision, change and supplement) must be preserved in an official Air Force (AF) TO archive to comply with record retention provisions of the Federal Records Act and to ensure preservation for AF needs. Archived files will only be the digital or printing source file (.pdf).

TO archiving must be compliant with TO 00-5-3 and Electronics Records Management (ERM)

T33-40 R03.00.

1.5.1 Location / Name of Program Archive Repository

Annotate the location(s) and name(s) of your archive repository used for your program TOs.

Programs not currently using one of the archive repositories listed below, will establish archive capability with Robins Air Force Base (RAFB) CTOR. All requests for archival TOs will be performed IAW TO 00-5-3.

Archive for all RAFB TO management programs is the Centralized TO Repository

(CTOR).

Programs utilizing IDM with content management may use the IDM environment as the archive.

The official classified digital archive is Robins Secure TO Repository (STOR).

Centralized Integrated Technical Order Management System (CITOMS).

All AF TOs in the 11N index will be officially archived by AFNWC.

Programs not currently using one of the above archive repositories will establish archive capability with Robins AFB CTOR. Contact the Robins TO Site Functional Office for assistance

2.0 NEW EQUIPMENT ACQUISITION

Describe the programs new equipment acquisition process to include program planning acquisition strategies and integral data management. TOMA must be very familiar with the approach taken with each program for the initial fielding, levels of maintenance, schedules, funding and all aspects of the TO program as it relates to the overall program life cycle.

Planning and knowing how each of these events impact TO management and development is crucial in avoiding any problems throughout the programs life cycle. Address policy and procedures for the development, acquisition, reproduction and distribution.

2.1 INITIAL PLANNING

Describe the initial planning process. The first step in this process should be reviewing program documentation and developing a preliminary plan of action. Consider reviewing documents such as the Initial Capabilities Document (ICD), Capability Development Document (CDD), Operational Concept, Maintenance Concept and other documents to determine the correct acquisition strategy for each new program. New acquisitions of equipment or weapons systems require careful planning on the part of the TOMA. The format of the data to be delivered with the equipment must be “defined in collaboration with” the Program Manager (PM) as soon as possible in the planning stage. Once the format has been decided, the other data acquisition requirements can be developed.

2.2 SCOPE OF TO REQUIREMENTS

Provide a brief description of the programs scope of TO requirements. Requirements should focus on enterprise standardization, how you will balance operational needs, budget constraints and maintain enterprise standardization. TO management decisions will be based on operational needs and budget constraints.

(Example): The XXX TO Program’s direction will blend existing XXX commercial data for the non-military aircraft and engines with the military-specification required data, resulting in a

Type 2 Interactive Electronic Technical Manual (IETM) which will fully support the XXX

System. Only two digital formats (PDF and IETM) of TOs are being developed for this program. Additionally, source data for various manuals is being developed as determined by

XXX impact to these manuals. The general characteristics of these formats, types of manuals, and listing of manuals are as follows: XXX

2.3 REVIEWS

The TOMA is responsible for scheduling and/or hosting a number of development reviews associated with new acquisition programs. The number and types of reviews are dependent upon the individual program. Provide an overview of your reviews to include frequency, entry and exit criteria. All reviews should mirror the programs Intergrated Master Schedule. A list of typical reviews conducted for most acquisition programs are listed below.

TO Guidance Conference

Certification/Verification

In Process Review

Pre-publication

Post-publication

Technical Data Assessment Review

2.4 DATA FORMATS

Describe what data formats the program is currently using such as commercial, paper/pdf., SGML, IETM and S1000D. For purposes of this guide, “data” refers to the TOs and source data necessary for or associated with product development and sustainment, including the data associated with system development.

2.5 TYPE MANUALS

Briefly describe the type manuals such as Operations, Organizational Level, Intermediate/Depot

Level, Component Maintenance, Engine Maintenance, Illustrated Parts Breakdown, Support

Equipment, Training, Software and Commercial that are used in the program and what led to the decision to utilize these. Data should be available in a format that is compatible with the intended user’s environment and a quality assurance program should be implemented to guarantee the accuracy and completeness of the data.

2.6 TMCR

If a program has multiple TMCR’s, reference the location in this document. The TMCR is the contractual authority for the programs/weapons system. This TOLCMP is intended to supplement and not replace the TMCR or any portion of it. Should there be a conflict between the TOLCMP and the TMCR, the TMCR shall take precedence. TO types are selected by tailoring the TMCR to reflect program needs based on operating and maintenance concepts. The

TOMA should tailor TMCR to meet program needs, especially those programs that use multiple

TMCR’s. Provide a copy of the TMCR at Annex 4.

2.7 OTHER CONTRACT DOCUMENTS

The TOMA or PM should be familiar with the contract documents listed below. Provide documentation and/or a reference for each item.

2.7.1 Statement of Objectives (SOO) / Statement of Work (SOW)

Provide an extract of the TO portion from SOW, either as a discrete entry when TOs represent a considerable risk to program funding or schedules, or as an element of the organic maintenance or supportability objectives when the risk is low.

2.7.2 Special Contract Requirements (H-Clauses)

(See TO 00-5-3 for applicability)

2.7.3 Data Rights

Provide a brief description of the data rights. Include commercial rights and secondary distribution rights you have for the program TO’s. A weapon system may remain in the defense inventory for decades. The decisions made at the time of acquisition can have far-reaching implications for weapon system support over the system’s life cycle and the failure to negotiate adequate technical data rights may impede the government’s ability to sustain the weapons system. It is during the development of the solicitation and the subsequent negotiation of a proposed contract that the government is in the best position to negotiate and secure required technical data rights.

2.7.4 Schedules

Provide schedule from the Initial TO Guidance Conference. These schedules may later be adjusted depending upon program needs. The schedules must match the Integrated Master

Schedule. Attach at Annex 8.

2.7.5 Contract Deliverable Requirement List (CDRL)

Reference the location of CDRLs which should specify inspection and acceptance requirements, distribution statements, delivery media, number and timing of deliveries.

2.7.6 Contractor Furnished Aeronautical Equipment/Contractor Furnished Equipment

(CFAE/CFE) Notices

Document the procedures for processing CFAE/CFE notices and update throughout the program life cycle.

2.7.7 Verifications

Most programs or modification of TOs require contractor support of the Government verification effort. Support may consist of Engineers and / or Editorial Support correcting detected TO errors, participation in TO review boards and travel to verification sites. The TOMA will document or reference all minutes for each verification. See example below.

(Example): The Contractor proposed support for the government TO Verification program will be evaluated for proper utilization of personnel, supplies, and support equipment, production-configured system or commmodity assets and spare parts. Proposed allocation of liability during combined contrator/government certification efforts will be evaluated. Procedures for incorporating updates developed during verification will be assessed.

2.8 TOLCVP

Attach a copy of Program’s TOLCVP at Annex 5.

2.9 CONTRACTOR INFORMATION

Provide a general description of all contractor information that pertains to the development of

TOs. If the program will be sustained by the contractor for life, TOMA must engage with the

Contractor in writing the requirements to define the role of the contractor sustainment responsibility. Since these arrangements require contractors to sustain technical manuals for the life of the program, the number of changes to be issued annually, a surge capability for Urgent or

Emergency situations and the flow of recommended changes must be addressed. Budgets must also be addressed to ensure PMs include all TO related cost in their Program Objective

Memorandum (POM) submittals.

2.9.1 Contractor Developed Technical Manual Organization Plan (TMOP)

The contract may include the development and delivery of a TMOP through the use of Data Item

DI-TMSS-81810. The contractor TMOP does not replace the requirement for a TOLCMP on programs. This TMOP, when developed, should be attached at Annex 6.

3.0 SUSTAINMENT

3.1 TRANSITION

Briefly describe the transition from Acquisition to Sustainment. Programs must begin planning for the seamless transfer from acquisition to sustainment phase as soon as possible after test and evaluation, TOMAs will document all transition history. During the transition from acquisition activity to sustainment or in support of a new sustainment contract, the TOMA should evaluate enhancing the sustainment section. The TOLCMP acquisition section should address the activities necessary during current activities for the transition. The TOLCMP sustainment section must describe the sustainment activities of the program and should support new contracting activities such as a new RFP, a new TMCR and new technical data users. The sustainment will address the CAFTOP, TO delivery, sustained engineering provider, areas of cognizant responsibility, in - service acquisition and transition and access to data across organizations. The transition description should also include acquisition TO sustainment process and transition process change history to include SGML to HTML, S1000D to contractor IETMS, pdf, or any changes to methodology during transition.

3.2 SUSTAINMENT OVERVIEW

Provide a brief overview of the sustainment effort. At the completion of the TO development and formalization process, the TO enters the sustainment phase of the TO lifecycle. It is the responsibility of the TOMA to ensure the sustainment process is implemented to guarantee currency, completeness and accuracy for support of affected equipment until equipment disposal.

Sustainment includes updating, numbering, indexing, publication (editing & printing), archiving and delivery to the user.

3.3 RESPONSIBILITIES

The purpose of this section is to provide a description of responsibilities during sustainment for the TOMA, Using/Lead Command and TO Site Functional Office. The description should include processes/coordination such as when there are cross commands, CAFTOP/Funding issues, unique requirements and Foreign Military Sales (FMS)/Case manager issues.

3.3.1 Sustainment Responsibilities for TOMA

3.3.2 Sustainment Responsibilities for Database Managers

3.3.3 Using and Lead Commands

3.3.4 TO Site Functional Office

3.4 SCOPE OF TO REQUIREMENTS

Describe the scope of the TO requirements focusing on enterprise standardization, how operational needs are balanced with budget constraints, regulatory and TMSS requirements.

Describe how overall TO guidance is coordinated with users and support agencies.

3.5 TO PREPARATION

Provide an overview of the TO Preparation process using such data as specifications, schematics, engineering drawings, engineering reports, vendor data, design data, engineering assembly and test procedures, manufacturing engineering procedures, support equipment procedures, data in

Supportability Analysis Reviews and other TOs.

3.5.1 Specification Interpretation Document

Describe the requirements and include references to the Specification Interpretation Document

(SID) and any other referenced documents identifying requirements with respect to technical data content, text and graphics. Identify the SIDs contained in the TMCR and other referenced directives (i.e., Mil-Specs, AFIs, TOs Department of Defense (DoD) guidelines and regulations) applied during the development of TOs.

3.5.2 Developmental Flow

Normally TOs are developed from data derived from various sources, such as, supportability analysis reviews, design data specifications, schematics, engineering drawings, vendor data, engineering reports, manufacturing engineering procedures, support equipment procedures, engineering assembly and test procedures. They are also developed in accordance with USAF needs and requirements as defined in the IMP, IMS, SOW, TMCR and various CDRLs as well as contractually referenced MIL-SPECs and AF standards. Provide your developmental flow process at Annex 7.

3.5.3 Reviews: IPR’s, Pre- and post-publication reviews

Provide an overview of how reviews are performed. Reviews should be proposed and conducted to ensure correct implementation of government requirements by the contractor and any subcontractors or vendors. The criteria should include both entry and exit conditions. Provide a schedule for all program reviews at Annex 8.

3.5.4 Quality Assurance Process

Provide a brief outline of the Quality Assurance (QA) process. Consider QA process for the following:

TOMA

TCM

ES

Engineering

Editorial Support (Contractor/Organic)

3.5.5 Responsibilities: TOMA, TCM, ES, Engineering, Editorial Support (Contractor/Organic) support

Describe the responsibilities during TO preparation for the above individuals.

3.5.6 Classified TO Reviews

Briefly describe the process and timeframe the program classified TO’s are being reviewed.

Review classified technical data during every TO update action or at least annually for possible classification downgrading according to the applicable SCG or DoDM 5200.01, Vol. 1. TCMs must ensure their TOs are reviewed in a timely manner. The task schedule should be set for less than one year to allow time to complete the review within the required one-year period. Initial data for overdue currency review tracking may be obtained from HQ AFMC/A4UE.

3.5.7 Verifications, Preliminary TO, Formalization

Describe or reference programs verification and formalization process.

3.5.7.1 Verification methods/processes used

Describe or may be referenced in TOLCVP.

3.5.7.2 Scheduling

Describe or may be referenced in TOLCVP.

3.5.7.3 Responsibilities: TOMA, TCM, ES, Engineering, Editorial Support

(Contractor/Organic)

Describe verification responsibilities or may be referenced in TOLCVP.

3.5.7.4 Support: Lead / Using Commands

Describe or may be referenced in TOLCVP.

3.6 TO SECURITY and INFORMATION ASSURANCE

Describe what type of security classifications are called out for the programs’ TOs.

3.6.1 Classified Data Control, Controlled and Unclassified information

Provide an overview of the programs Classified Data Control, Controlled and Unclassified information. Include the classified Editorial location and process to implement TO changes.

3.6.2 Cyber Security Procedures

Reference the overall program office Cyber security procedures.

3.7 TO CHANGE PROCESS

Briefly describe the programs TO change process stating how recommended changes are processed and types of changes and forms used.

3.7.1 Weapon System TO Change Process

Provide the change process flow diagram and attach it at Annex 7.

3.7.2 Inter-Service/FMS Relationships with TOs and TCTOs

Provide an overview of Inter-service/FMS relationships, processes and responsibilities with other agencies such as Army, Navy, Marine Corps and Defense Logistics Agency (DLA).

3.8 TO DISTRIBUTION STRATEGY

Enhanced Technical Information System (ETIMS) is the AF enterprise distribution system for digital, paper, Compact Disc-Read Only Memory (CD-ROM) and Digital Versatile Disc (DVD).

Describe and justify the programs decision to implement an alternative distribution strategy.

3.8.1 Distribution Contingency

Provide your programs contingency plans in the event ETIMS is down for an extensive period of time. Explain how you would you provide TO updates to include ISS, IOS, and TCTO’s.

3.9 LONG TERM TO MANAGEMENT STRATEGY

Provide a description of the TO programs long term management strategy to include strategy goal and process.

3.10 FUNDING

Provide an overall description of the TO program funding process to include all funding requirements such as printing, packing and shipping costs, TO Information Sheet (TOIS), CAFTOP, USAF Funding (3010, 3400), Transportation Working Capital Funding (TWCF), FMS Funding, Contractor cost and other components funding. Add funding flow chart at Annex

7.

3.11 APPROVAL

IAW TO 00-5-3, for AFLCMC managed programs, copies of the TOLCMP and TOLCVP and all updates shall be sent for review to the local TO Site Functional offices (Appendix B) at the location of the Program Office, and copy the TO Home Office. The local Site Functional Office will then upload current TOLCMP and TOLCVP for all programs to the AFLCMC LG

SharePoint.

https://cs4.eis.afmc.af.mil/sites/1334/Logistics%20Program%20Support/TOLCMP%20TOLCVP

/Forms/AllItems.aspx

For AFSC/LG and, AFNWC/LG managed programs the TOLCMP and TOLCVP will be sent to the appropriate Home Offices for approval. (Insert an approval signature page).

4.0 TOLCMP ANNUAL REVIEW

The TOLCMP is not a static management document. Each time a change occurs the TOLCMP shall be updated as required and reviewed annually during the CAFTOP update IAW TO 00-5-3.

(Insert an annual review date’s page).

5.0 AIRCRAFT or SYSTEM RETIREMENT

Briefly describe your plan to support Aircraft or System retirement/demilitarization. In addition to the TO archive procedures referenced in paragraph 1.5, identify any special or unique TO and/or data requirements needed.

6.0 ANNEX

The lists of Annex’s are the minimum requirements and must be attached to the Program’s

TOLCMP. If a particular Annex does not apply to a program, annotate with N/A next to it. (Do not delete). Add any other applicable Annex’s beginning at Annex 9.

ANNEX 1 - List of Acronyms (modify as needed)

ANNEX 2 - Definitions of Common Terms (modify as needed)

ANNEX 3 - Attach Policy Specifications and Waivers

ANNEX 4 - Attach TMCR https://cs4.eis.afmc.af.mil/sites/1334/Logistics%20Program%20Support/TOLCMP%20TOLCVP/Forms/AllItems.aspx https://cs4.eis.afmc.af.mil/sites/1334/Logistics%20Program%20Support/TOLCMP%20TOLCVP/Forms/AllItems.aspx

ANNEX 5 - Attach TOLCVP

ANNEX 6 - Attach TMOP

ANNEX 7 - Attach Flow Charts

ANNEX 8 - Attach Schedules

ANNEX 9- Attach TO CONOPS

THIS IS THE LAST PAGE OF THE TOLCMP GUIDE

CLICK ON ICON BELOW TO OPEN TOLCMP TEMPLATE

TO Life Cycle Management Plan Template 27 July 15.docx