00-20-2.pdf

TO 00-20-2

TECHNICAL MANUAL

MAINTENANCE DATA DOCUMENTATION

(ATOS)

THIS PUBLICATION SUPERSEDES TO 00-20-2 DATED 1 MARCH 2003.

FOR QUESTIONS CONCERNING TECHNICAL CONTENT OF THIS TECHNICAL MANUAL, CONTACT HQ AFMC/ENBP, WPAFB, OH.

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited

Published under authority of the Secretary of the Air Force.

15 JUNE 2003 CHANGE 2 - 15 APRIL 2007

INSERT LATEST CHANGED PAGES. DESTROY SUPERSEDED PAGES.

LIST OF EFFECTIVE PAGES

NOTE: The portion of the text affected by the changes is indicated by a vertical line in the outer margins of the page. Changes to illustrations are indicated by shaded or screened areas, or by miniature pointing hands.

Dates of issue for original and changed pages are:

Original . . . . . . . . . . . . . . . . . . . . 0 . . . . . . . . . . . . . . 15 June 2003 Change . . . . . . . . . . . . . . . . . . . . 2 . . . . . . . . . . . . . 15 April 2007 Change . . . . . . . . . . . . . . . . . . . . 1 . . . . . . . . . . . 15 August 2004

TOTAL NUMBER OF PAGES IN THIS MANUAL IS 196, CONSISTING OF THE FOLLOWING:

Page *Change Page *Change Page *Change No. No. No. No. No. No.

Title . . . . . . . . . . . . . . . . . . . . . . . . . 2 G-6 - G-8 A . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 H-1 - H-3 i - iv . . . . . . . . . . . . . . . . . . . . . . . . . 1 H-4 Blank v . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0 I-1 - I-5 vi Blank . . . . . . . . . . . . . . . . . . . . . . 0 I-6 1-1 - 1-3 . . . . . . . . . . . . . . . . . . . . . 0 I-7 - I-15 1-4 Blank . . . . . . . . . . . . . . . . . . . . 0 I-16 Blank 2-1 - 2-8 . . . . . . . . . . . . . . . . . . . . . 0 J-1 - J-4 3-1 - 3-24 . . . . . . . . . . . . . . . . . . . . 0 K-1 - K-2 4-1 - 4-2 . . . . . . . . . . . . . . . . . . . . . 1 L-1 - L-2 4-2.1 Added . . . . . . . . . . . . . . . . . . 1 L-3 4-2.2 Blank . . . . . . . . . . . . . . . . . . . 1 L-4 - L-18 4-3 - 4-10 . . . . . . . . . . . . . . . . . . . . 0 L-19 4-11 - 4-12 . . . . . . . . . . . . . . . . . . . 1 L-20 Blank 4-13 - 4-15 . . . . . . . . . . . . . . . . . . . 0 M-1 4-16 Blank . . . . . . . . . . . . . . . . . . . 0 M-2 Blank 5-1 - 5-2 . . . . . . . . . . . . . . . . . . . . . 0 N-1 - N-10 Added 6-1 6-2 Blank 7-1 - 7-11 7-12 Blank 8-1 - 8-4 9-1 - 9-4 10-1 - 10-2 10-2.1 Added 10-2.2 Blank 10-3 - 10-5 10-6 Blank A-1 - A-18 B-1 - B-2 C-1 C-2 Blank D-1 - D-5 D-6 Blank E-1 - E-3 E-4 Blank F-1 - F-3 F-4 Blank G-1 - G-3 G-4 - G-5

*Zero in this column indicates an original page

A Change 2 USAF

TABLE OF CONTENTS

Chapter Page

INTRODUCTION .............................................................................................................................................................. v

1 OBJECTIVES AND USES OF THE MAINTENANCE DATA DOCUMENTATION PROCESS...........................1-1

1.1 Intent ..................................................................................................................................................................1-1

1.2 Objectives ..........................................................................................................................................................1-1

1.3 Concept ..............................................................................................................................................................1-1

1.4 Intended Uses of Data.......................................................................................................................................1-2

1.5 Accuracy of Data...............................................................................................................................................1-3

1.6 Data Edits and Standard Tables........................................................................................................................1-3

1.7 Benefits ..............................................................................................................................................................1-3

1.8 Automated MDD Systems ................................................................................................................................1-3

2 RELATED DATA SYSTEMS........................................................................................................................................2-1

2.1 Air Force Total Ownership Cost (AFTOC) Management System..................................................................2-1

2.2 REMIS (G099) ..................................................................................................................................................2-2

2.3 CAMS (G054) ...................................................................................................................................................2-4

2.4 Improved Maintenance Management Program (IMMP) ..................................................................................2-6

2.5 Precision Measurement Equipment Laboratory (PMEL) Automated Management System (PAMS)

(Q011) ...........................................................................................................................................................2-6

2.6 Core Automated Maintenance System for Airlift (G081) ...............................................................................2-7

2.7 CEMS (D042)....................................................................................................................................................2-8

3 MAINTENANCE DATA DOCUMENTATION PROCESS ........................................................................................3-1

3.1 Documentation Concept ....................................................................................................................................3-1

3.2 Rules for Documentation ..................................................................................................................................3-1

3.3 Troubleshooting and Removal to Facilitate Other Maintenance .....................................................................3-2

3.4 Validity and Reliability of Data........................................................................................................................3-2

3.5 Maintenance Actions Not Requiring MDD Reporting ....................................................................................3-2

3.6 Exempted Organizations and Equipment .........................................................................................................3-3

3.7 Input of MDD Directly to REMIS by Depot, Contractors, and Special Activities ........................................3-3

4 CODES AND ENTRIES USED IN THE MAINTENANCE

DATA DOCUMENTATION PROCESS ..................................................................................................................4-1

4.1 Use of Codes .....................................................................................................................................................4-1

4.2 JCN ....................................................................................................................................................................4-1

4.3 Workcenter Code............................................................................................................................................4-2.1

4.4 ID Number.........................................................................................................................................................4-3

4.5 MDS and/or TMS and/or TMSM .....................................................................................................................4-4

4.6 Federal Stock Class (FSC) ................................................................................................................................4-4

4.7 Part and/or Lot Number ....................................................................................................................................4-5

4.8 Serial Number or Operating Time....................................................................................................................4-5

4.9 Tag Number.......................................................................................................................................................4-5

4.10 Installed Item Part Number...............................................................................................................................4-5

4.12 Operating Time..................................................................................................................................................4-5

4.13 Discrepancy........................................................................................................................................................4-5

4.14 Corrective Action ..............................................................................................................................................4-5

4.15 Parts Replaced During Repair (BIT/PIECE Data) ...........................................................................................4-6

4.16 Standard Reporting Designator (SRD) .............................................................................................................4-6

4.17 Type Maintenance Code (TMC).......................................................................................................................4-7

Change 1 i

4.18 Component Position ..........................................................................................................................................4-7

4.19 Work Unit Codes (WUC). Reference MIL-PRF-38769D (USAF) .................................................................4-7

4.20 Action Taken Code (ATC)................................................................................................................................4-8

4.21 When Discovered Code (WDC) .......................................................................................................................4-9

4.22 How Malfunctioned Code ...............................................................................................................................4-10

4.23 Units.................................................................................................................................................................4-10

4.24 Category of Labor ...........................................................................................................................................4-11

4.25 Command and/or Activity Identification ........................................................................................................4-11

4.26 Employee Number...........................................................................................................................................4-11

4.27 Start and Stop Time ........................................................................................................................................4-12

4.28 Crew Size Entries ............................................................................................................................................4-12

4.29 Built-In-Test (BIT) Fault Reporting ...............................................................................................................4-12

4.30 Master Job Standard Numbers (MJSN)..........................................................................................................4-12

4.31 Logistics Control Number (LCN)...................................................................................................................4-15

5 REPORTING REQUIREMENTS FOR CANNIBALIZATION ACTIONS.................................................................5-1

5.1 General...............................................................................................................................................................5-1

5.2 Definition ...........................................................................................................................................................5-1

5.3 Documentation...................................................................................................................................................5-1

6 DOCUMENTATION OF SUPPORT GENERAL AND CONSOLIDATED MAINTENANCE EVENTS...............6-1

6.1 Consolidated Maintenance Data Collection Process/Event Consolidation......................................................6-1

6.2 Purpose...............................................................................................................................................................6-1

6.3 Application.........................................................................................................................................................6-1

6.4 Exceptions..........................................................................................................................................................6-1

6.5 Support General Documentation.......................................................................................................................6-1

7 DOCUMENTATION OF MAINTENANCE ACTIONS ON WEAPON SYSTEMS, END ITEMS, AS-

SEMBLIES, SUBASSEMBLIES, AND PARTS ......................................................................................................7-1

7.1 Purpose...............................................................................................................................................................7-1

7.2 General Documenting Rules .............................................................................................................................7-1

7.3 Documentation Rules for TCTO Actions.........................................................................................................7-1

7.4 Documentation Rules for Serially Controlled, Warranty Tracked Items and Time-Change Items................7-1

7.5 Documentation of Training Equipment Maintenance ......................................................................................7-2

7.6 On-Equipment Maintenance Documentation for Aircraft, Air Launched Missiles (Except

ICBMS), Drones, and Related Training Equipment ...................................................................................7-2

7.7 Maintenance Documentation for ICBM ...........................................................................................................7-3

7.8 On-Equipment Maintenance Documentation for NOCM Materiel, RV/RS, and Related Test and

Handling Equipment (Excluding Nuclear Weapons) ..................................................................................7-5

7.9 On-Equipment Maintenance Documentation for SE and AGE.......................................................................7-5

7.10 On-Equipment Maintenance Documentation for C-E and CEM Equipment and COMSEC.........................7-6

7.11 Off-Equipment Maintenance Documentation for Shopwork and TMDE .......................................................7-8

7.12 Miscellaneous MDD Actions ............................................................................................................................7-9

8 AFTO FORM 350 ENTRIES .........................................................................................................................................8-1

8.1 General...............................................................................................................................................................8-1

8.2 Condition Status Tags .......................................................................................................................................8-1

8.3 Front Side, Part I ...............................................................................................................................................8-2

8.4 Front Side, Part II..............................................................................................................................................8-3

8.5 Reverse Side, Part I...........................................................................................................................................8-4

8.6 Reverse Side, Part II .........................................................................................................................................8-4

8.7 Marking of Classified Components ..................................................................................................................8-4

8.8 Automated AFTO Form 350 ............................................................................................................................8-4

9 TCTO STATUS REPORTING.......................................................................................................................................9-1 ii Change 1

9.1 Purpose...............................................................................................................................................................9-1

9.2 Scope..................................................................................................................................................................9-1

9.3 Status Accounting Systems ...............................................................................................................................9-1

9.4 Documentation of TCTO Kit Proof Testing ....................................................................................................9-1

9.5 Security Assistance Program (SAP) TCTO Reporting ....................................................................................9-1

9.6 Transferring Equipment.....................................................................................................................................9-2

9.7 Error Correction.................................................................................................................................................9-2

9.8 Administrative TCTO Supplements..................................................................................................................9-2

9.9 Manual Reporting ..............................................................................................................................................9-2

9.10 Applicability ......................................................................................................................................................9-2

9.11 Procedures for Recording and Determining TCTO Compliance.....................................................................9-2

9.12 AFTO Form 95 TCTO Entries .........................................................................................................................9-3

9.13 Maintaining TCTO Entries ...............................................................................................................................9-3

9.14 TCTO Status Reports ........................................................................................................................................9-4

9.15 Annual TCTO Status Review ...........................................................................................................................9-4

10 AFMC ACTIONS IN SUPPORT OF MDD................................................................................................................10-1

10.1 General.............................................................................................................................................................10-1

10.2 Single Manager Responsibilities.....................................................................................................................10-1

10.3 Air Logistics Centers and Contractor Maintenance Data Documentation Responsibility............................10-2

10.4 AFMC/EN Responsibilities.............................................................................................................................10-3

10.5 Configuration Management/TCTO Reporting................................................................................................10-4

10.6 Depot Maintenance Documentation................................................................................................................10-4

A WORKCENTER CODES ..............................................................................................................................................A-1

B COMMAND CODES..................................................................................................................................................... B-1

C CATEGORY OF LABOR CODES............................................................................................................................... C-1

D COMPATIBILITY EDITS.............................................................................................................................................D-1

E ACTION TAKEN CODES ............................................................................................................................................ E-1

F TYPE MAINTENANCE DESIGNATORS....................................................................................................................F-1

G HOW MALFUNCTION CODES..................................................................................................................................G-1

H WHEN DISCOVERED CODES ...................................................................................................................................H-1

I SUPPORT GENERAL CODES...................................................................................................................................... I-1

J ABBREVIATIONS AND DEFINITIONS ..................................................................................................................... J-1

K TIME-COMPLIANCE TECHNICAL ORDER CODES..............................................................................................K-1

L AIR FORCE STANDARD ALGORITHMS................................................................................................................. L-1

M MAINTENANCE DATA DOCUMENTATION POLICY ......................................................................................... M-1

Change 1 iii

N Master Job Standard Number (MJSN) Procedures........................................................................................................N-1

LIST OF ILLUSTRATIONS

Number Title Page

3-1 AFTO Form 349, Maintenance Data Documentation Record ..............................................................................3-22 3-2 AFTO Form 350, Reparable Item Processing Tag ...............................................................................................3-23 3-3 AFTO Form 350, Reparable Item Processing Tag (Reverse) ..............................................................................3-24 4-1 Sixth and Seventh Position JCN Entries ...............................................................................................................4-14 N-1 REMIS GUI MJSN Maintenance (GM 1080)........................................................................................................N-5 N-2 MJSN Build Process................................................................................................................................................N-9 N-3 MJSN Change Process ..........................................................................................................................................N-10

LIST OF TABLES

Number Title Page

3-1 Determining Which References To Use.....................................................................................................................3-6 3-2 Convenience of Making Repair..................................................................................................................................3-7 3-3 Selection of Which AFTO Form to Use at the Home Station for the MDD System..............................................3-9 3-4 Maintenance Items to Document for On-Equipment Data***................................................................................3-10 3-5 Maintenance Items Documentation of On-Equipment Data* .................................................................................3-12 3-6 Maintenance Items Documentation for Off-Equipment Data*** ...........................................................................3-13 3-7 Maintenance Items Documentation for Off-Equipment Data** .............................................................................3-14 3-8 Number of Action Lines to Use for Both On and Off-Equipment Documentation ..............................................3-15 3-9 Maintenance Items Documentation for a tracked Item in the WUC Table............................................................3-16 3-10 Documentation for TCTOs.......................................................................................................................................3-19 4-1 Assignment of JCNs MA..........................................................................................................................................4-13 5-1 Preparation of AFTO Form 349 and AF Form 2414 when automated systems are not available..........................5-2 N-1 Type Equipment Codes..............................................................................................................................................N-3 N-2 Category MJSNs ........................................................................................................................................................N-4 N-3 Type Intervals.............................................................................................................................................................N-6 N-4 Type Inspection Codes...............................................................................................................................................N-7 N-5 TCI Formats ...............................................................................................................................................................N-7 N-6 DOM/DOI Indicators.................................................................................................................................................N-8 iv Change 1

INTRODUCTION

1. PURPOSE.

The purpose of this Technical Order (TO) is to provide a broad understanding of the objectives, scope, concept, and policy of Maintenance Data Documentation (MDD), and some intended uses of the data it contains. It prescribes the rules for documenting entries on weapon systems, support systems, and equipment that has been selected for reporting by the equipment manager, as indicated by the MICAP/MDD/TCTO settings on the Standard Reporting Designator (SRD). This TO also explains the Visibility and Management of Operating and Support Cost (VAMOSC), Core Automated Maintenance System (CAMS), Improved Maintenance Management Program (IMMP), Precision Measurement Equipment Laboratory Automated Management System (PAMS), CAMS for Mobility (GO81), Reliability and Maintainability Information System (REMIS), and Comprehensive Engine Management System (CEMS). It provides an authoritative source for certain codes used and entries required in the MDD process, reporting rules, and documentation for cannibalization actions.

TO 00-20-2 provides policy and/or guidance for the individual maintenance activities (Chapter 8) for the collection and documentation of maintenance data. Maintenance personnel using this TO should be familiar with their related major command implementing directives, TOs, user’s manuals, and the following:

• AFCSM 21-5XX, Vol. 2 CAMS

• AFI 21-101 Maintenance Management Policy (MMP)

• AFI 21-108 Space Command

• AFI 21-114 ICBM

• AFI 21-116 Maintenance Management of Communications-Electronics (C-E)

2. SCOPE.

The MDD process begins with the follow-on Operational Test and Evaluation (OT&E) cycle (AFI 99 series), and extends through the operational phase of the life cycle of equipment. Additional rules and procedures are in Air Force documents, users manuals, and major commands implementing directives that further bound the scope of the MDD process as it applies to base-level maintenance production involving labor.

The scope of MDD includes all functions outlined in AFI 21-series and major commands implementing directives; functions maintaining training equipment listed as MDD reportable in the SRD table; contractors, if specified in the contract; depot activities, when accomplishing maintenance on MDD reportable equipment; historical documentation; and rules for reporting maintenance activities on direct labor, on and off-equipment maintenance, serially controlled items, peculiar maintenance actions and time-change items.

v/(vi blank)

CHAPTER 1

OBJECTIVES AND USES OF THE MAINTENANCE DATA DOCUMENTATION

PROCESS

1.1 INTENT.

The intent of this Technical Order (TO) is to provide policy and/or guidance to the functional user for the use and operation of the Maintenance Data Documentation (MDD) process. This TO also provides for the collection and storage of maintenance data for aircraft, spacelift assets, air launched and Intercontinental Ballistic Missiles (ICBMs), drones, engines, Communications-Electronics (C-E) to include AFSPC satellite ground stations, mobile stations and radar systems, and C-E meteorological (CEM) equipment, Support Equipment (SE), Aerospace Ground Equipment (AGE), Nuclear Ordnance Commodity Management (NOCM) materiel, Reentry Vehicles and Reentry Systems (RV/RS), related training, test, handling and support equipment, Real Property Installed Equipment (RPIE) utilizing the Core Automated Maintenance System (CAMS), and other reporting systems.

1.1.1 This TO is to be used in conjunction with the appropriate data system user’s manual to ensure proper procedures are applied.

1.1.2 This TO does not address the operation of the input and retrieval procedures. The mechanics of those processes are covered under major command directives, user’s manuals, and guide books.

NOTE

All users of MDD systems must ensure that records do not include classified information. Major commands are responsible for providing guidance for reporting MDD during deployments or contingency operations when current data or locations may be detrimental to operations security. Handle data IAW AFPD 31-4.

1.2 OBJECTIVES.

1.2.1 The objectives of the MDD process are to provide a vehicle for: collecting, storing, and retrieving base-level, depot-level, and contractor-type maintenance data. Data is used in support of the USAF equipment maintenance program, reliability and maintainability improvement program, and the maintenance management system procedures.

1.3 CONCEPT.

The MDD process includes collection, storage and retrieval. The process provides for the data collection and monitoring of maintenance discrepancies. Rules and regulations govern the operations of each process. There are, however, several systems that are utilized for the input of MDD data. While each of these systems must follow the basic rules for the composition of the data elements and data entries, the procedures for data entry and operation of the following systems are contained in their user manuals and related documents:

• G081 CAMS for Mobility

• G054 CAMS

• G099 REMIS

• A400 IMMP

• D042 CEMS

• Q011 PAMS

1.3.1 As the processes operate within specified rules and procedures, essentially the following takes place:

1.3.1.1 During the collection process, data about maintenance production is entered and verified for accuracy.

1.3.1.2 This process allows for short and long term (historical) storage of data and the on-line and hard copy retrieval of data through user inquiry.

1-1

1.4 INTENDED USES OF DATA.

MDD data is intended for use at the site where data is collected and off site by Air Force Management and Engineering Agency (AFMEA), major commands, and DoD.

1.4.1 On the base, the intended use of the base-level maintenance production data is to provide information feedback to base managers and supervisors for controlling the maintenance operation.

1.4.1.1 In CAMS, this information can be obtained through use of standard reports. Tailored reports may also be obtained through use of a Query Language Processor (QLP), and the Interactive Query Utility (IQU). Examples of information that can be retrieved are:

1.4.1.1.1 Production information about the type of work accomplished, the work center that did the work, and the equipment on which the work was accomplished.

1.4.1.1.2 Equipment maintenance schedules and inventory information for maintenance actions that are required on a calendar basis.

1.4.1.1.3 Productive and labor hour expenditures in either detailed or summary form. This includes labor expended to support other organizations or special projects.

1.4.1.1.4 Equipment failures and discrepancy information. This information is available in composite form by type of equipment and for individual equipment items.

1.4.1.1.5 A by-product of MDD is the maintenance of the actual configuration as it pertains to serial tracked and time-change items. Through MDD the current configuration status of the weapon system is maintained.

1.4.1.1.6 In addition, base maintenance managers and supervisors may obtain information concerning operational and support costs, except for C-E equipment, and ICBMs from the VAMOSC system which is described in Chapter 2 of this TO.

1.4.1.1.7 Base maintenance managers and supervisors may also query REMIS for like equipment maintenance and operational data at its own or other base locations.

1.4.1.1.8 In G081, reports can be generated in the FOCUS program.

1.4.2 Off base, the intended use of the data within the MDD process is for information to manage various programs established by AF and major air command regulations and manuals.

1.4.2.1 The AFMC has been designated as overall materiel manager for AF systems/equipment. This management requires all levels of maintenance production data. The data is used to:

1.4.2.1.1 Identify reliability, maintainability, and availability problems on AF equipment.

1.4.2.1.2 Establish priorities for product improvement actions.

1.4.2.1.3 Account for modifications to AF equipment and evaluate the effectiveness of modifications.

1.4.2.1.4 Validate inspections and time-change requirements and/or intervals.

1.4.2.1.5 Identify safety deficiencies and monitor corrective actions.

1.4.2.1.6 Validate or adjust calibration intervals.

1.4.2.1.7 Validate spares requirements.

1.4.2.1.8 Identify programmed depot maintenance requirements.

1.4.2.1.9 Evaluate deficiency reports and modification proposals from other commands or industry.

1.4.2.1.10 Compute the cost for billing the Air Mobility Command and the Air National Guard (ANG) for reimbursable depot-level maintenance.

1.4.2.1.11 Determine TCTO kit distribution requirements and TCTO rescission dates.

1-2

1.4.2.1.12 Evaluate compliance with warranties.

1.4.2.1.13 Provide for configuration control and/or management.

1.4.2.1.14 Determine Test Measurement and Diagnostic Equipment (TMDE) maintenance intervals.

1.4.2.2 In addition to using the data for internal AFMC management of AF equipment, AFMC provides:

1.4.2.2.1 Data on the performance and support requirements of current inventory equipment for industry to use in developing new systems and equipment.

1.4.2.2.2 Data for reports requested by HQ USAF, the Departments of the Army and the Navy, the Inspector General (IG) (for accident investigation) and the major commands.

1.4.2.2.3 Data sent to appropriate agencies requiring comparable data used by AFMC.

1.4.2.2.4 Data on AF-wide repair capability to bases, major commands, and HQ USAF for the assessment and improvement of maintenance repair capabilities.

1.4.2.3 Data for Operational command and control systems.

1.4.2.4 Data for HQ USAF accounting and finance for determining the cost of base-level maintenance operations.

1.4.3 At one time MDD was also used to determine manpower requirements. Although it is still a consideration in these computations it is not the primary source for decisions. MDD man-hours must NOT be used for manning decisions.

Maintenance man-hours are used to determine repair times and cost to operate systems. Work centers must not inflate repair actions to account for personnel as this data is used for other management decisions.

1.5 ACCURACY OF DATA.

For MDD to be useful to its many users, it is essential that the data in the system be accurate. To ensure accuracy and completeness, workcenter and shift supervisors are responsible for reviewing (on a daily basis) the data entered into the system by personnel under their control.

1.6 DATA EDITS AND STANDARD TABLES.

REMIS transmits the following edit tables to field Maintenance Management Information Systems (MMIS): action taken, command, how malfunction, when discovered, type maintenance, work unit, Master Job Standard Number (MJSN) and SRD codes. REMIS tables will take precedence whenever a conflict arises between the published table and the REMIS tables. If there are questions between the data in the MMIS and the TO, contact the work unit code (WUC), MJSN or SRD focal point at the appropriate Center and HQ AFMC/ENB for other tables.

1.7 BENEFITS.

The information provided through the MDD process is used in the management decision making process which results in many tangible benefits to the Air Force. These benefits are not always readily apparent to the individual involved in the documenting of data. However, a large portion of the cost of the MDD process is returned through improved reliability, maintainability, and availability of AF equipment.

1.8 AUTOMATED MDD SYSTEMS.

When automated MDD systems are available, data will be input using procedures outlined in appropriate user manuals or directives. When an automated system is not available, manual methods will be used in conjunction with manuals or directives to the greatest extent possible.

NOTE

Tables used throughout this TO are included both to indicate documentation rules and denote non-automated methods.

1-3/(1-4 blank)

CHAPTER 2

RELATED DATA SYSTEMS

2.1 AIR FORCE TOTAL OWNERSHIP COST (AFTOC) MANAGEMENT SYSTEM.

2.1.1 Purpose: The Visibility and Management of Operating and Support Cost (VAMOSC) system was developed to improve management’s decision making capability by compiling, consolidating, and maintaining a broader range of historical Operating and Support O&S cost data. VAMOSC provides the visibility of weapon systems’ O&S cost so that others may manage these costs within the life cycle cost process. It uses information provided by the MDD process to achieve this purpose.

2.1.2 Objectives: The objectives of the VAMOSC system are:

2.1.2.1 To provide the DoD and USAF with visibility of O&S costs at the Mission, Design, and Series (MDS) and component WUC levels for aircraft, and the Type, Model, and Series (TMS) level for ground C-E equipment.

2.1.2.2 To provide the means to collect, maintain, and portray historical O&S cost data for weapon systems in terms of cost elements most useful to DoD and AF management requirements that are related to the Cost Analysis Improvement Group (CAIG) format.

2.1.2.3 To expand AF weapon system O&S cost Management Information Systems (MIS) to obtain detailed data on weapon systems, subsystems, and replaceable component maintenance costs for use in making equipment replacement or modification decisions. Maintenance cost elements (labor, materiel, and support) must be identified for the subsystem and replaceable components which comprise system maintenance costs.

2.1.2.4 To provide improved logistics support cost information for use in acquisition planning, tradeoff analysis studies, and budget requirements submissions.

2.1.2.5 To provide the capability to display this information in standard report formats and also provide demand type reports reflecting only particular user requirements to fulfill a specific purpose.

2.1.2.6 To contribute to the reduction of initial support costs by providing the capability to assimilate, portray, and retain for historical reference the cost of resources (labor, materiel, services, and overhead) directly and indirectly associated with base and depot logistics of aircraft subsystems and components.

2.1.2.7 To maintain a historical database for a minimum of 10 years.

2.1.2.8 To provide cost information to improve logistics policy decisions.

2.1.2.9 To identify system component reliability, effectiveness, and costs so that high support cost items may be identified and addressed.

2.1.3 Scope: There are three components in the VAMOSC. These components are the Weapon System Support Cost System (WSSCS), the Component Support Cost System (CSCS), and the C-E system which is currently suspended. VAMOSC is a MIS for collecting O&S costs and relating them to the MDS and/or TMS level for aircraft and C-E systems. In addition, it relates costs to components for aircraft and engines through use of a National Stock Number (NSN) and/or WUC cross reference file. The system is available to all DoD components for on-line access cost reports on menu driven interface.

2.1.4 Concept: Certain incoming data for the C-E, WSSCS, and CSCS systems are edited, validated, selected, and rearranged through a preprocessor subsystem called Visibility and Management Overhead (VAMOH) subsystem. VAMOH accepts input data at designated times during the year in order to produce current data at the annual processing time.

VAMOH is used to build consolidated data files into logical groups for processing. It should be noted that there are differences among the three VAMOSC systems in compiling costs. WSSCS, CSCS, and C-E systems use different sources and algorithms in making cost collections and apportionments. WSSCS reports costs according to the CAIG cost categories and CAIG cost definitions. CSCS does not report by the CAIG elements since it deals with aircraft component, maintenance, and materiel costs. C-E does not report in accordance with the CAIG cost categories, but is closely aligned to those categories. WSSCS portrays partial costing on almost all aircraft in the active inventory. The number of aircraft for which total costing is shown is driven by the Weapon System Cost Retrieval System (WSCRS, H036C). Depot maintenance costs, 2-1 and therefore total costing, is available for approximately 100 MDSs. Partial costing is available for approximately 50 other MDSs. Component support cost system provides cost on 120 aircraft. The aircraft that are costed were identified by HQ ITSAF and correspond to the standard and/or actual table contained in the product performance system. WSSCS, CSCS, and C-E are not complementary systems. For example, MDS costs obtained from WSSCS at the MDS level cannot be supported with like data from the CSCS system because cost contents and methods of calculation are different. C-E collects costs by TMS and likewise uses different sources and methods of calculation.

2.1.5 Intended Uses of Data: The VAMOSC program has been developed as a repository of information for personnel throughout the AF as a tool to aid in accomplishing the following:

• Force and/or support program balance.

• Weapon system comparisons.

• Support resource planning.

• Design trade studies to set Reliability and Maintainability (R&M) goals.

• Logistics support alternatives.

• Affordability studies.

• Warranty and/or contractor support analysis.

• Equipment maintenance management.

2.1.6 Accuracy of Data: For VAMOSC, the control of accuracy is the selection of the most correct data sources to feed the system. If the source data systems are accurate, then VAMOSC will also be accurate. The MDD system is a key source of information used by the VAMOSC system. The WSSCS uses MDD data to allocate maintenance man-hours and costs to the correct MDS. The CSCS uses MDD data to allocate direct maintenance man-hours to the cost of operating and supporting aircraft components. The C-E system uses MDD data to correctly cost the maintenance effort to the applicable TMS.

2.1.7 Benefits: VAMOSC will provide decision makers a visibility of O&S costs that has never before been available. This visibility will enhance the decisions made by DoD and AF when attempting to identify the cost drivers of systems and subsystems that are experiencing a growth in O&S cost expenditures.

2.2 REMIS (G099).

2.2.1 Purpose: REMIS is designed to accumulate data and provide information necessary to support the AF equipment maintenance program outlined in AFI 21-101. REMIS will provide accurate, near-real-time data accessibility to all levels of management. Selected weapon system data from the MMISs will be transmitted electronically to REMIS. Increased data accuracy, timeliness, and accessibility will facilitate USAF development, implementation, and utilization of readiness initiatives, R&programs, and other equipment maintenance management systems which keep AF equipment in serviceable condition, safely operable, and properly configured to meet mission needs.

2.2.2 Objectives:

2.2.2.1 Enhance front-end design and increase the readiness and sustainability of USAF weapon systems by improving the availability, accuracy, and flow of essential equipment maintenance information.

2.2.2.2 Develop REMIS as part of an overall AF equipment maintenance management information program under the Logistics Information Management Support System (LIMSS) architecture.

2.2.2.3 Designate REMIS as the primary AF database for collecting and processing equipment maintenance information and supporting the objectives of the R&M 2000 program.

2.2.2.4 Structure REMIS by weapon system or major equipment category (e.g., engines) using distributive processing techniques.

2.2.3 Scope: The three application subsystems of REMIS (Equipment Inventory, Multiple Status, Utilization Reporting Subsystem (EIMSURS), Product Performance Subsystem (PPS), and Generic Configuration Status Accounting Subsystem (GCSAS)) will provide uniform user interface, processing, and reporting capabilities. The EIMSURS, PPS, and GCSAS subsystems receive inputs from on-line users: CAMS, contractors, and other AF data systems, in both batch and on-line modes. AF organizations may query the database, update validation tables, download data, and perform other functions within the security and/or access limits established by their approved user Identifications (IDs) and database views. This is accomplished through the use of a menu-driven process with on-line help screens. REMIS maintains detailed and summary data on-line. Archived historical data is also available by contacting REMIS PMO.

2.2.4 Concept: The following discussion applies to the three application software programs: EIMSURS, PPS, and GCSAS.

2-2

2.2.4.1 EIMSURS - The EIMSURS will provide both detailed data and summary and/or historical data for all items of aerospace vehicles, Automatic Test Equipment (ATE), C-E, and selected SE, aerospace ground equipment, and missiles for all AF organizational levels that report equipment maintenance data. This subsystem performs the following four functions:

inventory reporting, status reporting, utilization reporting, and Inventory/Status/Utilization (I/S/U) integration.

2.2.4.2 PPS - The PPS will provide the capability to evaluate maintenance actions, weapon system effectiveness and materiel deficiencies, thereby allowing management to identify equipment that requires corrective actions. This data will be primarily used by System Program Directors (SPDs), Item Managers (IMs), Equipment Specialists (ESs), and R&M analysts for identifying and resolving specific problem areas and for the improvement of resource utilization. The three main functions of PPS are MDD, equipment availability, and aircraft debriefing.

2.2.4.3 GCSAS - The GCSAS is a single unified information source for all AF weapon system configuration data. The GCSAS updates and integrates the functions of the Standard Configuration Management System (SCMS), the Advanced Configuration Management System (ACMS), the Commodity Configuration Management System (CCMS), and the B-1B Configuration Status Accounting System (CSAS). It absorbs the Embedded Computer System (ECS) software, the TCTO management and tracking software, and provides Computer Program Identification Number (CPIN) status and tracking.

2.2.5 Intended Uses of Data: The REMIS program has been developed as a repository of R&M information for personnel throughout the AF as an aid in accomplishing the following:

2.2.5.1 EIMSURS:

2.2.5.1.1 Allocate flying hours and/or sorties per MDS and Program Element Code (PEC).

2.2.5.1.2 Monitor the utilization and/or operation of the fleet.

2.2.5.1.3 Determine aircraft configuration identification.

2.2.5.1.4 Provide selected weapon system status information.

2.2.5.2 PPS:

2.2.5.2.1 Failure analysis and/or trending.

2.2.5.2.2 Warranty and/or guarantee tracking support.

2.2.5.2.3 Evaluate equipment maintenance concepts and plans.

2.2.5.2.4 Identify causes of high downtime or excessive support impacts.

2.2.5.2.5 Gauge weapon system support.

2.2.5.2.6 Aircraft debriefing analysis.

2.2.5.3 GCSAS:

2.2.5.3.1 Provide cradle-to-grave tracking of serially-controlled configuration items.

2.2.5.3.2 Administration and management of TCTO data.

2.2.5.3.3 Administration and management of approved configuration data.

2.2.5.3.4 Administration and management of actual configuration and time-change inspection data.

2.2.6 Accuracy of Data: CAMS data will be validated prior to entry into the database by tables pushed down to the source of entry. Mathematical calculations will be one hundred percent accurate to four positions right of any decimal point, when the numbers are expressed in scientific notation. It is the intent of the AF that all MDD systems should have the same edits and use the same push down tables.

2-3

2.3 CAMS (G054).

2.3.1 Purpose: CAMS is the AF primary, production-oriented, base-level automated MMIS.