Technical Order System Description - DTIC

2y ago
176 Views
8 Downloads
3.49 MB
96 Pages
Last View : 5d ago
Last Download : 3m ago
Upload by : Elise Ammons
Transcription

AD-A206 842f4United States Air ForceComputer-aided Acquisition &Logistics Support (CALS)Technical Order System DescriptionDoD-VA856-87-29*FINAL*October 1987REPORTDTIC E tECTEJohn LaPointeHSystems Automation Division*Prepared ByU.S. Department of TransportationResearch and Special ProgramsAdministrationTransportation Systems Center*Cambridge, MA 02142*I89Prepared ForU.S. Air Force Systems CommandHQ AFSCIPLXCAF CALS MIOAndrews AFI, DC 20334-5001

SECURITY CLASSIFICATION OF THIS PAGEForm ApprovedREPORT DOCUMENTATION PAGEl.OMB No. 0704-0188lb. RESTRICTIVE MARKINGSREPORT SECURITY CLASSIFICATIONUNCLASSIFIED2a. SECURITY CLASSIFICATION AUTHORITY3. DISTRIBUTION /AVAILABILITY OF REPORTUNLIMITEDUNCLASSIFIED2b. DECLASSIFICATION /DOWNGRADING SCHEDULE4. PERFORMING ORGANIZATION REPORT NUMBER(S)S. MONITORING ORGANIZATION REPORT NUMBER(S)DoD-VA856-87-29DoD-VA856-87-296s. NAME OF PERFORMING ORGANIZATION6b. OFFICE SYMBOLUS Department of Transporation(ifapplicable)6c. ADDRESS (City, State, and ZIP Code)7a. NAME OF MONITORING ORGANIZATIONUS Air Force Systems Command7b. ADDRESS (City, State, and ZIP Code)Research and Special Programs AdministrationTransportation Systems CenterCambride MA 02142-1093Sa. NAME OF FUNDING/SPONSORINGMGtIZAIONNzrorce Systems Command8b. OFFICE SYMBOL(If applicable)HQ AFSC/PLXCAF CALS MIOAndrews AFB DC 20334-50019. PROCUREMENT INSTRUMENT IDENTIFICATION NUMBERHO AFSC/PLXCSc. ADDRESS(City, State, and ZIP Code)10. SOURCE OF FUNDING NUMBERSPROGRAMELEMENT NO.AF CALS MIOAndrews AFB DC 20334-5001PROJECTNO.WORK UNITACCESSION NO.TASKNO.11. TITLE (Include Security Classification)United States Air Force Computer-aided Acquisition & Logistics Support (CALS)Tprhnni-hjl Ordpr12. PERSONAL AUTHOR(S)qrPTn f)P Q-rinftien -FINAL REPORTJohn LaPointe13a. TYPE OF REPORTTech Report13b. TIME COVEREDTOFROM15. PAGE COUNT14. DATE OF REPORT (Year, Month, Day)94October 1987I16. SUPPLEMENTARY NOTATION17.FIELDCOSATI CODESGROUPSUB-GROUP18. SUBJECT TERMS (Continue on reverse if necessary and identify by block number)19, ABSTRACT (Continue on reverse if necessary and identify by block number)The USAF Computer-aided Acquisition & Logistics Support Technical Order System Descriptionprovides readers with the current, logical view (as delineated by AF regulations, militarystandards, and applicable technical orders) of the Air Force Technical Order (TO) System.Discrepancies associated with the physical implementation of the TO system are footnotedthroughout the document. Each activity associated with the TO process has been functionalldescribed using the AF Integrated Computer Aided Manufacturing (ICAN) modeling techniques.Included in the document are matrix representations of TO organizational responsibility andregulatory controls.]Jj.)20.1ISTRIBUTION /AVAILABILITY OF ABSTRACT-- SAME AS RPT. UNCLASSIFIEDIUNLIMITED22a. NAME OF RESPONSIBLE INDIVIDUALAlthea PhillipsDD FormI 1473, JUN 86C21. ABSTRACT SECURITY CLASSIFICATIONUJ,1,LAS orIED /UNLIMITEDDTIC USERS22b. TELEPHONE (Include Area Code)(617) 494-2117Previous editions are obsolete.22c. OFFICE SYMBOLUS DOTSECURITY CLASSIFICATION OF THIS PAGE

ACKNOWLEDGEMENT**I am indebted to the many people who have assisted me in the preparation of thisdocument. In particular, I wish to thank Mr. James Porterfield (TSC) and Mr. RobertGilUett (Unisys) for their laborious efforts in the IDEF modeling of the Air ForceTechnical Order System and Ms. Susan McCarthy (Dynatrend) for undertaking thethankless jobs of typing, editing, and compiling this document. Finally, I am deeplygrateful to Professor Arthur Munguia (AFIT) for providing extensive information on theTechnical Order System.SS.0Accession ForNTISGRA&IDTIC TAFUr Lrr.naoLin1c c dJu2.iIf cat oi[]By . . .lon I-Di.tributDIStI11O 1/AFTOSpagei

UNITED STATES AIR FORCECOMPUTER-AIDED ACQUISITION AND LOGISTICS SUPPORT (CALS)TECHNICAL ORDER SYSTEM DESCRIPTIONTABLE OF CONTENTSSectionPage1.0CALS Overview1-i2.0Air Force Technical Order System2-13.0Technical Order Process3-i4.0Create TOs4-15.0Deploy TOs5-I6.0Manage TOs6-17.0Organizational Assessment7-18.0Regulatory Controls8-1ADoendicesAAir Force Technical Order System Types of Technical Order PublicationsA-iBTechnical Order System ReferencesB-iCForms Used In the Technical Order SystemC-iDExceptions to Technical Order SystemD-iEAir Force Air Logistics Center Functional ChartE-iFAir Force Technical Order System DimensionsF-IGAir Force Technical System Current InconsistenciesG-1HAcronymsH-iAFTOSpage ii

TABLE OF CONTENTS (Cont.)FifurePawe1Air Force Technical Order Process1-42Technical Order Process3-23Create TOs4-24Plan TOs4-55Develop TOs4-96Review TOs4-127Deploy TOs5-28Print TOs5-59Distribute TOs5-710Use TOs5-1011Modify TOs5-1412Manage TOs6-213Budget TOs6-414Catalog TOs6-7TablePage1Computer-aided Acquisition & Logistics Support (CALS)Modular Planning Process Overview1-32Participating Organizations/Lists7-23Node AO - Technical Order Process7-4AFTOSpage iii

TABLE OF CONTENTS (Cont.)STable**Page4Node Al - Create TOs7-55Node All - Plan TOs7-66Node A12 - Develop TOs7-77Node A13 - Review TOs7-88Node A2 - Deploy TOs7-99Node 21 - Print TOs7-1010Node A22 - Distribute TOs7-1111Node A23 - Use TOs7-1212Node A24 - Modify TOs7-1313Node A3 - Manage TOs7-1414Node A31 - Budget TOs7-1515Node A32 - Catalog TOs7-1616Regulatory Controls8-2pAFTOSpage iv

1.0 CALS OVERVIEWon"Intr'odctieThe Air ForceComputer-aided Acquisition and Logistics Support (CALS) Program hasbeen established to improve weapon system reliability and maintainability, whilereducing the costs of weapon system acquisition and support. Of paramount importanceto CALS is the delivery and handling of a large quantity of9technical -data. Theautomation process is intended to make a significant reduction in paper and in labornecessary to enter, manipulate, transfer, and interpret data. The technical informationto be digitized in the form of text or images includes: maintenance procedures, testprocedures, engineering drawings, design criteria models, etc. The program is strivingto replace the current paperwork process by automating (or digitizing) the flow of thetechnical information.Air Force Policy and ObjectivesThe October 18, 1985 Air Force Program Management Directive (PMD) established aCALS Management Integration Office (MIO) and directed the following additional tasks:* To plan for the integration of existing Automated Technical Information (ATI)projects with each other and with a standard information systems framework; todetermine the full range of CALS objectives and management concepts; and toplan for large scale demonstrations and implementation of CALS technology on anacquisition program for a weapon system.* To ensure that system structures are consistent and compatible with Air Forceguidelines." To perform analyses comparing the costs and present methods of managingtechnical information and the costs of ATI for comparable elements of theprogram, and to analyze the return on investment for incremental capabilitiesdeveloped under ATI." To prepare and maintain an ATI and CALS Program Management Plan (PMP) whichwill address program integration and will consolidate: 1) current and proposedCALS critical schedule and event relationships for CALS program objectives; and2) plans and opportunities for incorporating improved ATI capabilities in weaponsystem acquisition programs.The Air Force established a Management Integration Office (MIO) at HQ USAF/AFSC tooversee the CALS program. Specifically, the MIO is responsible for planning, oversight,and coordination of the CALS initiatives, but not the specific systems.TheTransportation Systems Center (TSC) is providing the systems engineering support to theAFSC/MIO in creation of automation plans directed at the fulfillment of the CALSobjectives.Initially, the MIO has identified four Air Force areas to investigate opportunities forimprovements:Technical Orders (TOs), Engineering Drawings, Logistics SupportAnalysis (LSA), and Unified Life Cycle Engineering (ULCE).AFTOSpage 1-1

Modular Planning ProcessIn order to satisfy the requirement activities associated with the CALS initiatives areas,TSC, with support from Unisys Corporation and RIS Associates, developed aninformation engineering systematic approach entitled Modular Planning Process (MPP).The MPP was devised by integrating elements from strategic planning and informationengineering methods.The principal drivers in the evolution of the MPP were:" A process was needed to focus on technical plans that would not be outdated priorto implementation;" A process was needed to incorporate transition systems;" A process was needed to serve diverse information distribution and user demands;and" A process was needed to deal with the needs of decentralized organizationsresponsible for the various related weapons system acquisition and logisticssupport functions.The MPP has evolved into three phases:* An examination of the environment" A study of opportunities" A plan of future direction.Table 1 represents an overview of the MPP along with its component tasks within thethree aforementioned phases. This document is a product of the completion of the tasksassociated with phase I of the MPP.PurposeThe purpose of this document is to provide to the readers with the current, logical view(as delineated by the Air Force regulations, military standards, and applicable technicalorders) of the Air Force Technical Order System (AFTOS) - one of the four initial CALSinitiative areas. Discrepancies associated with the physical implementation of theAFTOS have been footnoted throughout the document.A modeling technique developed during the Air Force Integrated Computer AidedManufacturing (ICAM) in the mid-to-late 1970s will be used to functionally describe theactivities associated with the Technical Order Process (see Figure 1). Known as theICAM Definition or IDEF, the Technical Order IDEF model will consist of flow chartsand a glossary describing each flow chart.In an effort to provide more detailinformation, matrix representation of organizational responsibilities vs. AFTOSactivities and regulatory controls vs. AFTOS activities are included in the document.AFTOSpage 1-2

TABLE 1. COMPUTER-AIDED ACQUISITION & LOGISTICS SUPPORT (CALS)MODULAR PLANNING PROCESSOVERVIEWSTUDY THE OPPORTUNITIESEXAMINE THE ENVIRONMENTPLAN THE DIRECTIONInitiate the ProcessAssess TechnolocyFormulate AlternativesPerform Initial Assessment* Create Preliminary Description ofEnvironment" Identify Organization Expectations" Establish PrioritiesIdentify Existing Technologies. Review Current Environment0 Review Ongoing Projects. Identify Existing TechnologiesResearch Future TechnologyAssess Critical Issues. Examine Objectives. Identify Technologies. Review Organizational IssuesPropose Initial AlternativesDevelop Specific Procedures" Establish Management Plan. Identify Advisory Group" Prepare Project PlansConduct Structured AnalysisDescribe Current Environment* Create Functional Model* Identify Major Data Elements* Describe the OrganizationalInfrastructure.9.OpportunitiesSelect Technology AreasConsult with Technology ExpertsExamine Similar ApplicationsReview Development TrendsEstablish Technology Alternatives0 Quantify Directions. Specification of ImplementationIssues* Examine Benefits and Costs. Select Future Requirements0 Identify Technologies. Structure ProposalsReview and Modify AlternativesReview Criteria**Identify Relationships withTransitional ProjectsDefine Policies and OrganizationsInvolvedDevelop Consensus* Identify Major Information FlowParametersProject Future RequirementsForecast Requirements* Identify Discussion Topics andAssess Transitional Projects" Identify Objectives* Describe Functions and Data* Identify Technologies" Identify Infrastructure Affected* Review Applicable ScenariosPriorities. Evaluate Current Environment. Establish Objectives. Provide Access to InformationDevelop Common Understanding9 Conduct Discussions with MAJCOMs* Forecast Process Changeso Assess infrastructure ConstraintsExamine Feasible Alternatives* Determine Feasibility issues" Review Industry TrendsReview Progress with Advisory Group. Review Future Requirements. Evaluate Recommended Solutions Examine Feasibility IssuesDefine Future StateExpand Advocacy NetworkDescribe Future Environment* Define the Impact of Technology onCurrent State" Define Projected OrganizationalResponsibilities* Define Relevant InterfaceRequirements*Create Future Functional Model* Develop a Description of Future State* Identify Prolected Major InformationFlow Parameters. Establish Evaluation Criteria Develop Implementation ProceduresDevelop Organization PlanConfirm Major MilestonesIdentify implementation Agencies Select Appropriate Forums* Communicate the PlansPrepare Implementation PlanDefine Activity DescriptionsEstablish Implementation Guidelines** Establish Transition Plan* Identify OrganizationalResponsibilitiesEstablish Corstituency" Gain Management Acceptance ofPlan* Obtain a Commitment for ExecutionCreate Documentation* Establish Goals* Define Resource Requirements* Recommend Technologies* Define Organizational Impacts* Establish Financial ParametersAFTOSpage 1-3

IISI-0 UII*-l11 l-!iI.4A50.I!l2I4A 0e ot Iizw; !!Iiil iI-!u-2!tI-AI t-"IIIII- !IIIIORDER PROCESSFIGURE 1. AIR FORCE TECHNICALAFTOSpage 1-4

2.0 AIR FORCE TECHNICAL ORDER SYSTEMBackgroundThe Air Force Technical Order (TO) System was established by Air Force Regulation(AFR) 8-2, Air Force Technical Order System, as the official medium for disseminatingtechnical information, instructions, and safety procedures pertaining to Air Forcesystems and equipment.According to AFR 8-2, TOs must have the following attributes:"constitute a military order"issued in the name of the Chief of Staff, USAF*by order of the Secretary of the Air Force*compliance is mandateryCurrently, there exists five types of TOs used throughout the Air Force:1) Technical Manuals - These are documents which cover installation, operation,maintenance, and handling of Air Force equipment and material.2) Abbreviated Technical Orders - These are primarily work-simplificationchecklists,Examples are:devices produced from a technical manual.inspection workeards, or sequence charts.3) Time Compliance Technical Orders - These documents provide the instructionsfor modifying equipment (other than temporary modifications authorized inAFR 57-4, Modification Program Approval and Management) and performing,or initially establishing, one-time inspections.4) Methods and Procedure Technical Orders - These are documents whichestablish policy and provide information and instruction on maintenancemanagement or administration, configuration management, etc. They aregeneral in content and are not issued against specific systems or equipment.5) Index Technical Orders - These reference documents provide personnel with ameans of selecting TOs, show the status of each TO, and, in certain instances,group the TOs pertaining to specific items of equipment.Appendix A, Types of Technical Order Publications, outlines categories within each typeof TO.AFTOSpage 2-1

Major ReferencesThere are eleven major documents that govern (control) the TO system:AFR 8-2, Air Force Technical Order System, establishes the technical order system forthe Air Force. This regulation explains the TO system by delineating the process foracquiring new TOs (including a description of the type of data to be included in a TO)and by assigning the basic responsibilities for management and improvement to the TOsystem.TO 00-5-1, AF Technical Order System, prescribes the concept and management of theAir Force TO system as established by AFR 8-2. Furthermore, this TO provides policyand assigns responsibility related to the acquisition and use of TOs. The various types ofTOs are identified and described.TO 00-5-2, Technical Order Distribution System, creates the TO distribution system.This TO contains the policies and procedures on the TO distribution system for use bythe Air Force and other organizations requiring TOs.TO 00-5-15, Time Compliance Technical Order (TCTO), establishes the TCTO systemfor the Air Force and prescribes the policies and procedures for its management. TheTCTO is the primary means of initiating equipment modification.TO 00-5-16, Computer Program Identification Numbering System (CPIN).ITO 00-5-17, Computer Program Identification Numbering System (CPIN).lTO 00-5-18, Technical Order Numbering System, prescribes the TO numbering systemused for assignment of technical order numbers.TO 00-5-19, Security Assistance Technical Order Program, contains policy andprocedures for US Air Force management of TO requirements to support USGovernment approved sales of weapons system and equipment.TO 0-1-01, the index of TO Indexes, and TO 0-1-02, the index of General TOs, are keyindexes in the Air Force TO system. There is a separate TO index for each category ofTOs which lists TO status and provides a basis for determining initial distributionTO 0-1-01 contains prefacerequirements and updating TO files and records.information that applies to all indexes.TO 0-1-01 contains preface information that applies to all indexes, whereas TO 0-1-02 isa listing of general Air Force TOs.TMCR 86-01, AF Technical Manual Contract Requirement - Preparation Instructions,establishes the requirements for acquisition of technical manuals (including TOs) and alltypes of equipment. TMCR 86-01 supersedes the use of the data item description (DID)and listing on the contract data requirements list (CDRL).Appendix B, Technical Order System References, identifies the various Department ofDefense/Air Force documents and regulations that govern or guide the Technical OrderSystem.1 TOs 00-5-16 and 00-5-17 are not major documents that govern the TO system.are user manuals for the CPIN system but impact the TO process.AFTOSTheypage 2-2

Technical Order System FormsAFR 0-9, Numerical Index of Departmental Forms, lists 300-plus Air Force TechnicalOrder (AFTO) forms that pertain to any one, several, or all TOs. Also, numerousDepartment of Defense (DoD), Air Force (AF), Air Force Logistics Command (AFLC),and Air Force Systems Command (AFSC) forms pertain to TOs. Appendix C, Forms Usedin the Technical Order System, lists those forms that are considered noteworthy to theTO system.General PolicyThe TOs are published under the authority of the Secretary of the Air Force inaccordance with AFR 8-2 and are distributed, maintained, and filed in accordance withTO 00-5-2, Technical Order Distribution System. Policy concerning the TO system isdetermined by HQ USAF/LEYE, and HQ AFLC/MMT manages the TO system. OCALC/MMED manages and publishes TO 00-5-1, AF Technical Order System, and TO 005-2, whereas WR-ALC/MMED manages and publishes TO 00-5-15, Time ComplianceTechnical Order. Each TO, issued within the system, is assigned a unique alpha/numericidentifier by OC-ALC. There are 10 types of Air Force technical documents (listed inAppendix D, Exceptions to Technical Order System) that are excluded from the TOsystem.IDEF Model of Air Force Technical Order SystemThe Integrated Computer Aided Manufacturing Definition (IDEF) modeling technique isbeing used to graphically represent and describe the various functions and associatedactivities of the Air Force TO system. Essentially, this section depicts an IDEF0 modelof the current TO system which Includes the major TO functions which are decomposedinto their component sub-functions (or activities).For IDEFO, each node (i.e., function), every box (i.e., sub-function or activity)pictorially depicted has it own set of ICOMs 2 (Inputs, Controls, Outputs, andMechanisms). Furthermore, a box that can be decomposed into more detailed subfunctions will be considered a node at the next lower level of decomposition.Allfunction and component sub-functions (i.e., activities) along with their associatedICOMs are described in the contiguous Glossary.Inputs are data that are required t

TECHNICAL ORDER SYSTEM DESCRIPTION TABLE OF CONTENTS Section Page 1.0 CALS Overview 1-i 2.0 Air Force Technical Order System 2-1 3.0 Technical Order Process 3-i 4.0 Create TOs 4-1 5.0 Deploy TOs 5-I 6.0 Manage TOs 6-1 7.0 Organizational Assessment 7-1 8.0 Regulatory Controls 8-1 ADoendices .Author: John LaPointePublish Year: 1987Explore furtherTechnical Orders - Tinker Air Force Basewww.tinker.af.milTechnical Orders - Robins Air Force Basewww.robins.af.milAF TECHNICAL ORDER SYSTEMwww.tinker.af.milAFSAC Online Tech Ordersafsac.wpafb.af.milAIR FORCE TECHNICAL ORDER LIFE CYCLE MANAGEMENTwww.tinker.af.milRecommended to you b

Related Documents:

Document revision 1.10 (June 22, 2007, 16:49 GMT) This document applies to MikroTik RouterOS V3.0 Table of Contents Table of Contents Summary Description System Backup Description Command Description Example Example Exporting Configuration Description Command Description Example Importing Configuration Description Command Description Example .

mitsubishi electric wind baffle - wb-pa3 mr. slim p-series pumy-60 submittal wb-pa3 description description c description d description e description f description g description proprietary and confidential the information contained in this drawing is the sole property

order. If your order was placed through the Oracle Store, the effective date is the date your order was accepted by Oracle. Unless otherwise stated in the order, Oracle technical support terms, including pricing, reflect a 12 month support period (the "support period"). Once placed, your order for technical

TABLE OF CONTENTS . Page . INTRODUCTION . Purpose. 1 . Background 1 DISCUSSION 1 Methodology 1 . Description of Engine Description of Test Procedure . 1 2 . Description of Maintenance Procedures . 2. Description of Test Cell . 2. Test Conditions. 5 . EMISSION SAMPLING SYSTEM . 5 . Description of Sampling Probe . 5 . Description of Mobile .

Description of HSPI functions, hardware connection and API functions. Chapter 9 I2C User Guide Description of I2C functions, master interface and demo. Chapter 10 I2S Module Description Description of I2S functions, system configuration and API functions. Chapter 11 UART Introduction Description

Stop Limit Sell Order (Will only be granted upon request) To stop potential losses by executing stop loss sell order. Stop Limit order is available for Normal Order only and not for Odd Lot order. How to execute Stop Limit order 1. - On right top corner of order entry box, click on the drop down arrow

Addy Notes_ Change Order to a PO Page 1 of 8 5/18/2017 Change Order to a Purchase Order . This Addy Note describes how to add money to a line on an existing purchase order (PO), also known as a change order to a PO. To make a change order to a PO, you’ll need to create a new requisit

opinions about the courts in a survey conducted by the National . criminal justice system, and that black women are imprisoned at a rate seven times greater than white women. The report indicates there has been an increase in their incarceration rate in excess of 400% in recent years. Further, three-fourths of the women, according to the report, were mothers, and two-thirds had children .