MIL-HDBK-59A APPENDIX A APPENDIX A CALS OVERVIEW 35 MIL-HDBK-59A APPENDIX A THIS PAGE INTENTIONALLY LEFT BLANK. 36 MIL-HDBK-59A APPENDIX A 10 SCOPE 10.1 Purpose. This appendix provides a detailed discussion of Computer-aided Acquisition and Logistic Support. 20 REFERENCED DOCUMENTS 20.1 Government documents. 20.1.1 Specifications, standards, and handbooks. Unless otherwise specified, the following specifications, standards, and handbooks of the issue listed in the current Department of Defense Index of Specifications and Standards (DoDISS) form a part of this handbook. SPECIFICATIONS MILITARY DOD-D-1000 Drawings, Engineering and Associated Lists MIL-D-5480 Data, Engineering and Technical Reproduction, Requirements for MIL-D-8510 Drawing, Undimensioned, Reproducibles, Photographic and Contact, Preparation of (ASG) MIL-M-9868 Requirements for Microfilming of Engineering Documents, 35mm MIL-D-28000 Digital Representation for Communications of Product Data: IGES Application Subsets MIL-M-28001 Markup Requirements and Generic Style Specification for Electronic Printed Output and Exchange of Text MIL-R-28002 Raster Graphics Representation in Binary Format, Requirements for MIL-D-28003 Digital Representation for Communication of Illustration Data: CGM Application Profile 37 MIL-HDBK-59A APPENDIX A MIL-T-29053 Requirements for Training System | Development | | MIL-M-29532(EC) Master Library Data Elements for | Technical Publications | | MIL-T-31000 General Specification for Technical | Data Packages | MIL-M-38761 Microfilm and Microfilm Frame Desk Used for Recording Engineering Drawings and Associated Data MIL-M-38784 Manuals, Technical: General Style and Format Requirements (Application for copies should be addressed to the Naval Publications and Forms Center (NPFC), 5801 Tabor Avenue, Philadelphia, PA 19120 or Defense Communications Agency, DDN PMO (B613), Washington, DC 20305.) STANDARDS FEDERAL STANDARDS FED-STD-1041 (FIPS PUB 100-1) Interface between Data Terminal Equipment and Data Circuit- Terminating Equipment for Operation with Packet-Switching Data Communication Networks. (Adoption of CCITT Recommendation X.25). FEDERAL INFORMATION PROCESSING STANDARDS FIPS PUB 127 Database Language - Standard Query | Language | FIPS PUB 146 Government Open System Interconnection Profile (GOSIP) FIPS PUB 156 Information Resource Dictionary System | (Application for copies should be addressed to the Superintendent of Documents, Government Printing Office (GPO), Washington, D.C. 20402, or the National Technical Information Service (NTIS) 5285 Port Royal Road, Springfield, VA 22161.) 38 MIL-HDBK-59A APPENDIX A MILITARY DOD-STD-100 Engineering Drawing Practices DOD-STD-963 Preparation of Data Item Descriptions | MIL-STD-188-114 Electrical Characteristics of Digital Interface Circuits MIL-STD-470 Maintainability Program for Systems and Equipment MIL-STD-499 Engineering Management MIL-STD-785 Reliability Program for Systems and Equipment Development and Production MIL-STD-804 Formats and Coding of Aperture Cards MIL-STD-1379 Military Training Programs MIL-STD-1388-1 Logistic Support Analysis MIL-STD-1388-2 DoD Requirements for a Logistic Support Analysis Record MIL-STD-1771 Value Engineering Program Requirement | MIL-STD-1777 Internet Protocol Standard MIL-STD-1778 Transmission Control Protocol Standard MIL-STD-1780 File Transfer Protocol MIL-STD-1781 Simple Mail Transfer Protocol MIL-STD-1782 TELNET Protocol Specification | MIL-STD-1785 System Security Engineering Program Management Requirements MIL-STD-1806 Marking Technical Data Prepared By Or For the Department of Defense MIL-STD-1840 Automated Interchange of Technical Information MIL-STD-2165 Testability Program for Electronic Systems and Equipments 39 MIL-HDBK-59A APPENDIX A HANDBOOKS MILITARY MIL-HDBK-217 Reliability Prediction of Electronic Equipment (Application for copies should be addressed to the Naval Publications and Forms Center (NPFC), 5801 Tabor Avenue, Philadelphia, PA 19120 or Defense Communications Agency, DDN PMO (B613), Washington, DC 20305.) 20.1.2 Other government documents. The following government documents and publications form a part of this military handbook to the extent specified herein. FEDERAL NSDD 145 National Policy on Telecommunications and Automated Information Systems Security MILITARY DDN X.25 Host Interface Specification, an implementation of CCITT Recommendation X.25 (Application for copies should be addressed to the Defense Communications Agency, ATTN: DDN PMO, Code B600, Washington, DC 20305.) DoD Directive 5010.12 DoD Data Management Program | DoD-5200.28-STD DoD Trusted Computer System Evaluation Criteria DoD-5220.22-M Industrial Security Manual NCSC STD-004-85 Guidance for Applying the Department of Defense Trusted Computer System Evaluation Criteria in Specific Environments NCSC TG-005 Trusted Network Interpretation of the Trusted Computer System Evaluation Criteria DoD 5200.28-STD Department of Defense Trusted Computer Evaluation Criteria 40 MIL-HDBK-59A APPENDIX A CSC-STD-002-85 Department of Defense Password Management Guideline CSC-STD-003-85 Computer Security Requirements: Guidance for the Department Trusted Computer Systems Evaluation Criteria in Specific Environments CSC-STD-004-85 Technical Rationale Behind CSC-STD-003- 85: Computer Security Requirements NCSC-TG-005 Trusted Network Interpretations of the Trusted Computer Evaluation Criteria (Application for copies should be made to the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402.) 20.2 Non-Government publications. The following documents form a part of this handbook to the extent specified herein. | The issues of the documents as adopted by DoD shall be the issue listed in the current Department of Defense Index of Specifications and Standards (DoDISS) and the supplement thereto. Electronic Industries Association (EIA) EIA RS-232-C Interface between data terminal equipment and data communication equipment employing serial binary data interchange. EIA RS-422-A Electrical Characteristics of Balanced Voltage Digital Interface Circuits. EIA RS-449 General purpose 37-position and 9-position interface for data terminal equipment and data circuit-terminating equipment employing serial binary data interchange. EIA RS-548 Standard for exchange of electrical/electronic item product data in Electronic Data Interchange Format (EDIF). (Application for copies should be addressed to the Electronic Industries Association, Standard Sales, 2001 I Street, NW, Washington, D.C. 20006.) 41 MIL-HDBK-59A APPENDIX A Institute of Electrical and Electronics Engineers (IEEE) IEEE-STD-1076 Standard for exchange of electrical/electronic item product data in VHDL format. (Application for copies should be addressed to the IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, Piscataway, New Jersey 08855 - 1331). Institute for Interconnecting and Packaging Electronic Circuits (IPC) IPC-D-350B Standard for exchange of electrical/electronic item product data in IPC format. (Application for copies should be addressed to IPC Inc., 7380 North Lincoln Avenue, Lincoln Wood, Illinois, 60646 - 1776) Network Information Center (NIC) Request for Change (RFC) 826 An Ethernet Address Resolution Protocol (IP address to media access control address translation). (Application for copies should be addressed to the ARPANET Network Information Center; SRI International, Menlo Park, CA 94025.) 20.3 Order of precedence. In the event of a conflict between the text of this handbook and the references cited herein, the text of this handbook shall take precedence. 42 MIL-HDBK-59A APPENDIX A 30 DEFINITIONS 30.1 Acquisition manager. The system/equipment program manager, the program manager's staff, and other DoD officials responsible for determining contract requirements for the generation, acquisition, and use of weapon system/equipment technical data, and having acquisition authority for weapon systems and equipment. 30.2 CALS Core Requirement. The set of documents that defines the environment necessary for Computer-aided Acquisition and Logistic Support (CALS) to function. These documents fall into three basic categories: functional standards, technical standards, and data standards. 30.2.1 Functional standard. A document that establishes and defines requirements for management, design processes, procedures, practices, methods, and data applicable to the creation of data products. 30.2.2 Technical standard. A standard that controls the medium or process of exchanging data between a sending and a receiving system. Data exchange is defined in terms of presentation formats and transformations of those presentation formats. Technical standards include document image standards; separate graphics, text, and alphanumeric standards; and integrated standards. 30.2.2.1 Document image standard. A technical standard describing the digital exchange format of a print/display file of a report or other document. (CCITT Group 4 and the proposed Standard Page Description Language are examples.) 30.2.2.2 Graphics standard. A technical standard describing the digital exchange format of graphics data. (CCITT Group 4 and CGM are examples.) 30.2.2.3 Integrated standard. A technical standard describing the exchange format of digital data which integrates text, gra- phics, alphanumeric, and other types of data in a single (compound) file. (ODA/ODIF is an example.) 30.2.2.4 Text standard. A technical standard describing the digital exchange format of textual data. (SGML is an example.) 30.2.3 Data standard. A specific set of data entities, relationships among data entities, and their attributes, often expressed in the form of a Data Dictionary and a set of rules that govern data definition, data integrity, and data 43 MIL-HDBK-59A APPENDIX A consistency. 30.3 Information systems. 30.3.1 Source system. The computer hardware and software that will structure technical information for interchange. 30.3.2 Destination system. The computer hardware and software receiving transferred data. 30.3.3 Government receiving system. The collective term for all government agencies and offices responsible for receiving, processing, reviewing, or approving technical data ordered on government contracts, including the destination system. 30.3.4 Integrated Weapon System Data Base (IWSDB). The | conceptual (logical) definition for and the total collection of | shared product definition and support data for a specific | weapon system. The IWSDB likely will be distributed on multiple | physical data base systems that may be accessed by Contractor | Integrated Technical Information Services (CITIS) and | government information systems throughout the weapon system | life cycle. | 30.3.5 Technical information systems. The generic term for the enterprise network of existing and augmented automated data processing systems used by government and contractors for management of technical information in support of the design, manufacture, and logistic processes for products such as weapon systems and related major equipment items. 30.3.5.1 Contractor Integrated Technical Information Services | (CITIS). CITIS is a computer-based information service that | draws upon integrated information from data bases throughout a | contractor's enterprise (contractor, sub-contractor, and | government) established and managed by the weapon system | contractor to receive, maintain, and provide access to | technical and support information on a military weapon system. | 30.3.5.2 Government Information Systems. The collection of automated data processing systems and applications used by government agencies and offices to enter, update, manage, retrieve, and distribute technical data from a specific Integrated Weapon System Data Base. 30.4 Forms of technical data. | | 30.4.1 Data. Recorded information, regardless of form or | method of the recording. | 44 MIL-HDBK-59A APPENDIX A 30.4.2 Technical data. Recorded information, regardless of | form or method of the recording of a scientific or technical | nature (including software documentation). The term does not | include computer software or data incidental to contract | administration, such as financial and/or management | information. | | 30.4.3 Engineering data. Any technical data (whether prepared | by the government, contractor, or vendor) relating to the | specification, design, analysis, manufacture, acquisition, | test, inspection, or maintenance of items or services. All | information which contains authoritative engineering definition | or guidance on material, constituent items, equipment or system | practices, engineering methods, and processes comprises | engineering data. | | 30.4.4 Product data. All engineering data, in processable | form, necessary to define the geometry, the function, and the | behavior of an item over its entire life span. The term | includes logistic data elements for quality, reliability, | maintainability, topology, relationship, tolerances, | attributes, and data elements necessary to completely define | the item for the purpose of design, analysis, manufacture, | test, and inspection. | | 30.4.4.1 Product design data. Product data that describes the | physical configuration and performance characteristics of an | item in sufficient detail to ensure that an item or component | produced in accordance with the data will be essentially | identical to the original item or component. | | 30.4.4.2 Product manufacturing or process data. Product data | that describes the steps, sequences, and conditions of | manufacturing, processing, or assembly used by the manufacturer | to produce an item or component or to perform a process. | | 30.4.4.3 Product logistic support data. Product data that | describes the equipment, tools, techniques, item | characteristics or analysis necessary to operate, maintain, or | repair the item by its end user. | | 30.4.5 Technical data package. A technical description that | is adequate to support acquisition of an item, including | engineering, production and logistic support. The technical | description defines the design configuration and procedures | required to ensure adequacy of item performance. It consists | of all applicable technical data, such as engineering drawings, | associated lists, product and process specifications and | standards, performance requirements, quality assurance | 45 MIL-HDBK-59A APPENDIX A provisions, and packaging details. | | 30.5 Contract data deliverables and access. | | 30.5.1 Document. Any subset of technical data that, packaged | for delivery on a single medium, meets the format, content, | consistency, and completeness requirements of a unified control | specification whether delivered in hard copy or digital form. A | document is a self-contained body of engineering data that | supports, alone or with other documents, an engineering or | maintenance function. | | 30.5.1.1 Human interpretable document. Traditional forms of | documents including specifications, drawings, lists, standards, | pamphlets, reports, and printed, typewritten, or other | information, relating to the design, procurement, manufacture, | test or inspection of items or services under the contract. | These sets of text or graphics engineering data are organized | and formatted for direct human interpretation and can be | delivered as printed pages or digitally in the form of composed | page images. | | 30.5.1.2 Processable data document. Technical data in digital | source form that is either organized and formatted so that an | automated data processing system can further structure or | restructure the data in a variety of ways, or is compatible for | direct processing by an automated design, engineering, or | logistic support system. Processable data can be updated or | transformed for other applications, such as, production of | document images. | | 30.5.2 Document Image File. A digital data file | representation of a human interpretable document. Examples are | raster image files and page description language files. | | 30.5.3 Processable Data File. Unlike human interpretable | documents or digitized document image files, processable data | files may contain information that is directly machine- | interpretable. Processable data files provide additional | flexibility of use because they consist of the digital source | data from which documents of varying types can be produced. | | 30.5.4 Interactive Access. The ability to access authorized | portions of the source data maintained in contractor or | government systems via on-line telecommunications data | transfers in real or near-real time using various types of | queries. Interactive access can be used to generate documents, | processable data files, or both. Data processing categories | for interactive access cover the entire range from view only to | 46 MIL-HDBK-59A APPENDIX A the full capability of down-loading data for subsequent | processing and transformation purposes. Interactive access | also includes on-line transactions which request transmittal of | information via physical media as documents or processable | files. | | 30.5.5 Working Data. Data for work in progress that has not | been "formally" submitted to the government but may be provided | for information purposes with the understanding that it is | preliminary and subject to further iteration. | | 30.5.6 Released Data. The configuration management controlled | version of the data that has been released in accordance with | government CM standards, after contractor internal review and | approval. Released data may be provided to the government for | purposes such as design review. | | 30.5.7 Submitted Data. The configuration management | controlled master version of the data "formally" submitted to | the government. | | 30.5.8 Approved Data. The configuration management controlled | master version of data formally submitted to and approved by | the government. | | 30.6 File types. | | 30.6.1 Alphanumeric File. A data file containing structured | numeric or alphanumeric fields. Data base files are | alphanumeric files. | | 30.6.2 Text file. A file which uses the American Standard | Code for Information Interchange (ASCII) or similar system to | represent the text of a document. Data within a text file are | delineated as human readable words, sentences, and paragraphs | rather than data elements. | | 30.6.3 Text/Graphics integration. The necessary indexing and | linkages between a computer readable text file and a separate | computer readable graphics file, or graphics subsection of the | same text file, such that both portions can be output or | updated as a single, apparently continuous, unit. | | 30.7 Item levels of equipment indenture. For the purpose of | defining regions of applicability, this military handbook has | classified equipment items into four levels of complexity and | integration. | | 30.7.1 System. A functionally complete assembly of | 47 MIL-HDBK-59A APPENDIX A components, boards, and boxes. Usually performs a complex | analog, digital, or mixed task. Examples include general- | purpose computer system, including memory disk, and other I/O | subsystems, a complete radar system, or the entire electronic | and electro-mechanical system of an aircraft. Includes the | sense of "group", "set", and "system" in DoD-STD-100 and MIL- | STD-280. | | 30.7.2 Box. An assembly of one or more boards to implement a | complex function. Includes back-plane or bus-oriented | assemblies, as well as direct-connect assemblies of boards or | substrate. Examples are the CPU box of a computer and front-end | of a radar system. Includes the sense of "unit" in DoD-STD-100. | | 30.7.3 Board. An assembly of components on a board or | substrate. Examples include single, double, and multilayer | board, ceramic, polyamide, silicon, and other substrate. | Includes the sense of "assembly" and "subassembly" as defined | in DoD-STD-100 and MIL-STD-280. | | 30.7.4 Component. Items that are usually packaged as an | indivisible unit to be assembled on a board or substrate. | Examples include IC's, resistors, capacitors, inductors, | transformers, discrete transistors, DIP switches, fuses, and | encapsulated relays. Includes the sense of "part" as defined in | DoD-STD-100 and MIL-STD-280. | | 30.8 Delivery, verification, and acceptance. | | 30.8.1 Acceptance. Acknowledgment that a product or data | conforms with contract content and quality requirements. | Acceptance may occur before, at, or after delivery. Upon | acceptance, customer assumes ownership. | | 30.8.2 Application certification. A formal statement by a | mutually approved and authorized agency that an application has | successfully undergone some conformance testing procedures. | | 30.8.3 Conformance test. The testing of a candidate product | for the existence of specific characteristics required by a | standard; testing the extent to which an item under test (IUT) | is a conforming implementation. | | 30.8.4 Contract delivery. Some form of transfer of contracted | product or performance of a contracted service. Contract | delivery may involve some physical transfer or relocation of | the data product. However, leaving data in place and tagging it | in such a way as to logically transfer designated data may also | be considered delivery. | 48 MIL-HDBK-59A APPENDIX A 30.8.5 Database partition. Logical or physical separation of | data elements which facilitates change control, security, | auditability, data usage control, computer resource control, | and/or cost accounting control as required by contract. | | 30.8.6 Validation. The effort required of the contractor or | preparing activity, during which the technical data product is | tested for technical adequacy, accuracy, and compliance with | the provisions of the specifications and other contractual | requirement. Validation is accomplished by comparing the data | product with the actual systems or equipment for which the data | product was prepared. Validation is normally conducted at the | preparing activity or vendor's facility. In extenuating | circumstances, validation may be conducted at an alternative | site. | | 30.8.7 Verification. A review process to ensure that a | deliverable meets all requirements stipulated in the contract, | is in compliance with applicable DoD standards and | specifications (unless waived by contract), and is complete and consistent with hardware/product configuration. 30.9 Acronyms and abbreviations. The acronyms and abbreviations used in this military handbook are defined as follows: ANSI - American National Standards Institute ASCII - American Standard Code for Information Interchange CAD - Computer-Aided Design CAE - Computer-Aided Engineering CALS - Computer-aided Acquisition and Logistic Support CAM - Computer-Aided Manufacturing | CCITT - International Consultative Committee on Telegraphy and Telephony CD-ROM - Compact Disk-Read Only Memory CDRL - Contract Data Requirements List CGM - Computer Graphics Metafile CIM - Computer Integrated Manufacturing | CITIS - Contractor Integrated Technical Information Services CM - Configuration Management DBMS - Data Base Management System | DDN - Defense Data Network DID - Data Item Description DLA - Defense Logistics Agency DoD - Department of Defense ECP - Engineering Change Proposal EDI - Electronic (business) Data Interchange EDIF - Electronic Data Interchange Format | FIPS - Federal Information Processing Standard 49 MIL-HDBK-59A APPENDIX A GOSIP - Government Open Systems Interconnection Profile GCO - Government Concept of Operations | IGES - Initial Graphics Exchange Specification ILS - Integrated Logistic Support IMIP - Industrial Modernization Incentives Program | IP - Internet Protocol IPC - Institute for Interconnecting and Packaging Electronic | Circuits | IRDS - Information Resource Dictionary System | ISD - Instructional Systems Design ISO - International Organization for Standards | IWSDB - Integrated Weapon System Data Base LAN - Local Area Network LSA - Logistic Support Analysis LSAR - Logistic Support Analysis Record MANTECH - Manufacturing Technology | MAP - Manufacturing Automation Protocol | ODA/ODIF - Office Document Architecture / Office Document Interchange Format OSD - Office of the Secretary of Defense OSI - Open Systems Interconnection PDES - Product Data Exchange Using STEP | PDL - Page Description Language R&M - Reliability and Maintainability RFP - Request for Proposal SGML - Standard Generalized Markup Language SOW - Statement of Work SPDL - Standard Page Description Language STEP - Standard for Exchange of Product Model Data | TCP - Transmission Control Protocol TDP - Technical Data Package TOP - Technical and Office Protocol | TQM - Total Quality Management | VE - Value Engineering | VHDL - VHSIC Hierarchical Definition Language | VHSIC - Very High-Speed Integrated Circuits | 50 MIL-HDBK-59A APPENDIX A 40 OVERVIEW OF COMPUTER-AIDED ACQUISITION AND LOGISTIC SUPPORT (CALS) 40.1 CALS overview. CALS is a DoD and industry initiative to | facilitate the integration of digital technical information for | weapon system acquisition, design, manufacture, and support | functions. The Deputy Secretary of Defense launched the DoD | CALS initiative in September 1985 and established a DoD | Steering Group to oversee its implementation. CALS is intended | to improve schedule, cost and quality throughout the weapon | system acquisition process through the creation and use of a | shared data environment, elimination of the development of | duplicate data used for separate processes, and improved design | and manufacturing capability where design changes will be | linked to computer-aided design and engineering processes. | Other improvements to be gained from CALS include reduced down- | time through the use of automated diagnostics and feedback, | improved responsiveness to industrial initiatives through the | development of integrated design and manufacturing | capabilities, reduction and eventual elimination of the costly | paper environment, and improved reliability, maintainability, | and combat effectiveness through the integration of automation | technology. | 40.1.1 CALS requirements. Both DoD and industry are investing in automation of a variety of functional areas to achieve productivity and quality gains. Existing islands of technical data automation within DoD, between DoD and industry, and within industry must be interfaced and integrated to reduce redundant data generation and maintenance, and to eliminate requirements for expensive hard copy output and reentry of data. CALS addresses requirements for an orderly transition from a paper and labor-intensive environment to the use of digital technical information for design, manufacturing, acquisition, and support processes. 40.1.2 CALS strategy. To achieve CALS benefits, a phased CALS strategy has been established by a team consisting of OSD, the military departments, DLA and industry. The key elements of that strategy are: a. Standards and integration requirements. Accelerate the development and testing of standards for digital technical data interchange and integrated data base access. Included in this element is support for | formal standardization efforts within acknowledged | standards organizations such as ANSI and ISO. | b. Weapon system applications. Implement CALS standards 51 MIL-HDBK-59A APPENDIX A in weapon system contracts and encourage industry modernization and integration. c. Technology development and demonstration. Sponsor the development and demonstration of the necessary technology for integration of technical data and processes in high risk areas. d. DoD systems. Implement CALS standards and integration requirements in DoD planning and infrastructure modernization programs. Infrastructure is the underlying framework of organizations, systems and processes within which DoD operates. 40.2 CALS concepts. The CALS system of systems approach, shown in Figure 2, consists of four key elements: a. Industrial systems (i.e., design, manufacturing, and customer support). b. Government systems, (i.e., acquisition and logistic support). c. Interfaces between industry and government. d. Interfaces within industry among prime contractors, subcontractors, and vendors. Information can pass among these systems, in both directions, in the form of documents, processable data files, and interactive access to data bases. 40.2.1 CALS standards. Three broad groups of requirements documents constitute the CALS interchange standards shown in Figure 2. They are: a. Functional Standards. A document that establishes and | defines requirements for management, design processes, | procedures, practices, methods, and data applicable to | the creation of data products. Includes military | standards and specifications, and Data Item | Descriptions (DID's) which define functional | processes, data requirements, data creation | procedures, and the content and format of data | products. | b. Technical Standards. A standard that controls the | medium or process of exchanging data between a sending | and a receiving system. Includes Federal standards, | 52 MIL-HDBK-59A APPENDIX A military standards and specifications, and other | relevant conventions (including their associated | DID's) for the management, formatting, and physical | media or telecommunications exchange of text, | graphics, alphanumerics, and other forms of digital | data. | FIGURE 2. Digital information exchange. c. Data Standards. A specific set of data entities, | relationships among data entities, and their | attributes, often expressed in the form of a Data | Dictionary and a set of rules that govern data | definition, data integrity, and data consistency. The | standards also include file structure definitions, | index keys, and other descriptive information needed | for access to data bases. | 40.2.2 Functional integration requirements. A major CALS 53 MIL-HDBK-59A APPENDIX A objective is a standardized approach for integrating technical data use within a weapon system program. Functional integration requirements are contractual tasks to be used in statements of work (SOW) or incorporated in functional standards articulating the required contractor capabilities for the integration of data systems and processes. These requirements specify the integration of design, manufacture, and support processes, as well as other elements of concurrent engineering, for the performance of DoD contracts. They also establish the means by which contractors will demonstrate the capability to access and share data bases among and between functional areas. These functional requirements will eventually be incorporated in updates to appropriate military standards and specifications. The model SOW language in this handbook is provided for use pending these updates. 40.2.3 Contractor Integrated Technical Information Services | (CITIS). As CALS capabilities evolve, data maintained in an | integrated data base environment (not necessarily physically | integrated) will be made available for automated access and | transfer to authorized users with a need to know. These | contractor developed and managed information services are | called CITIS. The services provided by CITIS include defining, | organizing, maintaining, and controlling access to integrated | information for the design, development, test, production, | operation, and life cycle support. CITIS will be used by | acquisition managers, logistics managers, and life-cycle | support managers as well as by various elements of the | contractor's (as well as sub-contractors) staff (i.e., design | team, reliability and maintainability engineers, human factors | and safety engineers, logisticians, etc.) | | The functional requirements of the CITIS to support a | weapon system will be specified in the contract, including | provisions for ensuring the accuracy, currency, and security of | the technical information contained in the integrated data | bases for the system. In addition to the integration of data | generated by the contractor during the development of the | weapon system, CITIS should also accept and integrate technical | information generated by the government on the weapon system | (i.e., performance requirements, physical constraints, | reliability and maintainability parameters, readiness | objectives, diagnostic capability, logistic constraints, etc.). | 40.2.4 Government technical information systems. The collection of automated data processing applications that are utilized by the government to generate, update, store, retrieve, and distribute data from technical data bases for a specific weapon system will exist on multiple distributed 54 MIL-HDBK-59A APPENDIX A automated data processing systems. It will cross functional boundaries and may combine data from more than one DoD component to support all requests for data from a single weapon system's user community. This degree of interchange and integration will require tight control and coordination of the separate physical data bases to allow transparent support to the user. The needed control and coordination within and among the contractor and government systems supporting a weapon | system will be provided by a logical data structure called the CALS Integrated Weapon System Data Base. 40.2.5 CITIS and government information system data for common items. Data for subsystems or components with multiple weapon system applications must be available to users without unnecessary storage redundancy. Hence, the issues of integration and standards for data exchange and access are just as applicable horizontally across weapon systems as they are vertically within the integrated technical data infrastructure for a single weapon system. CITIS will allow government furnished information to be stored, maintained and managed in contractor data systems that provide CITIS services to government users. Such information should be defined for the | contractor by the acquisition manager during the solicitation | process. In providing this capability, CITIS may be required | to accommodate data which is also available from a government | information system. Such redundancy may be necessary in order | to minimize telecommunications costs while maximizing data | accessibility. The relative merits of accessibility to, versus | redundancy of, such data should be evaluated by the acquisition | manager during development of the CALS strategy. | 40.2.6 Technical data and business data. CALS deals with technical data, which includes CAD/CAE/CIM and configuration management data, group technology and process planning/control data, engineering design and bill of materials data, inventory data, and technical publications data. Another key aspect of information interchange in digital form deals with business transactions for ordering, shipping, and making payment for the products described by CALS technical data. Business data in digital form is addressed by DoD's electronic data interchange (EDI) program, which also implements approved national standards (ANSI X.12) and reflects a common government and industry migration to a digital commercial environment. CALS will develop EDI transaction sets for accessing and ordering technical data from remote data bases, and for exchanging | technical data packages among dissimilar DoD and contractor | computer systems. | 40.2.7 Concurrent engineering. Concurrent engineering is a 55 MIL-HDBK-59A APPENDIX A systematic approach to create a product design that considers all elements of the product life cycle from conception through disposal. Concurrent engineering is an integrated design approach that takes into account all desired downstream characteristics during upstream phases to produce a more robust design that is tolerant of manufacturing and use variation, at less cost than sequential design. It affects all system procurement activities from Milestone 0 (concept definition and exploration) to the start of Milestone III (the end of full scale development). In so doing, concurrent engineering simultaneously defines the product, its manufacturing processes, and all other required life-cycle processes, such as logistic support. Concurrent engineering is not the arbitrary elimination of a phase of the existing, sequential, feed- forward engineering process, but rather the co-design of all downstream processes toward a more all encompassing, cost- effective optimum. Nor does concurrent engineering entail simultaneous design of the product and execution of the production process, an approach which is demonstrably unsound. There are three dominant approaches being taken by contractors today to implement elements of concurrent engineering: a. Engineering process initiatives to improve the organizations and procedures used to develop a product, such as formation of design teams that include people from multiple disciplines. b. Computer-based support initiatives such as improvement of computer-aided design tools, leading to the integration of various software applications and supporting data. This is part of a broader objective to create a data object once, and use it as a source for many functions and processes, including design synthesis and verification, production planning, and logistic support planning. c. Use of a variety of formal methods, including the application of special purpose tools for design and production support. Examples include statistical process control, design of experiments, design for assembly, and Taguchi quality engineering. CALS initiatives to improve technical data creation, management, and use provide an enabling environment that will accelerate the application of concurrent engineering concepts, and their consequent benefits. These benefits include the opportunity for significant reductions in product development cycles, a wide range of cost savings, and substantial 56 MIL-HDBK-59A APPENDIX A improvements in product quality. Specific CALS thrusts, such as integration of R&M, CAD, and CAE will directly contribute to application of concurrent engineering concepts. 40.2.8 Integration of R&M with CAD and CAE. Integration of R&M with CAD/CAE is a high-leverage, high-payoff CALS target that will provide significant improvements in the inherent reliability and maintainability characteristics of a weapon system's design. These gains will translate into greater operational effectiveness, and will decrease life cycle costs associated with the weapon system when deployed. Integration of R&M tools with the CAD/CAE process is a contributor to a comprehensive concurrent engineering strategy, whose objective is design optimization through integration of R&M and other domains within a cost effective engineering process. R&M integration with CAD/CAE will require changes to conventional post design analysis processes. These changes will consist primarily of the following: a. The development of user-friendly analytical tools that are tightly coupled to the product design data base and that can be rapidly executed by the designer to provide short-cycle feedback about the effectiveness of the design approach during the design process itself. b. The development of effective means to take advantage of lessons learned from prior design experience and field use in the form of design rules, expert systems, etc. c. The development of fully characterized component design, performance, and reliability data in a format readily accessible by these automated tools. For further details see Appendix C. 40.3 CALS implementation. CALS is organized into two overlapping phases which are characterized by the application of different levels of technology to technical data management, and by different degrees of impact on functions and processes allowed by this enabling technology. Near-term implementation focuses on converting current paper flows to digital form while beginning the integration process. Longer-term implementation focuses on replacing the parallel and duplicative requirements imposed by various acquisition disciplines and functions (e.g., design engineering, configuration management, integrated logistic support, test and evaluation, etc.) with requirements to develop integrated weapon system data bases that are 57 MIL-HDBK-59A APPENDIX A accessed and manipulated through CITIS. These CALS capabilities will allow technical data sharing at the data base level, rather than at the physical file level, with multiple formats of the same data from a common, configuration- controlled source available to different users. This will include the information needed for product design, engineering analysis, manufacture, and support, and will facilitate application of a comprehensive concurrent engineering strategy by making information accessible to a variety of industry and DoD users through automated and highly integrated means. However, CALS implementation will be characterized by a heterogeneous, mixed mode environment in which initiatives at different levels of technology often will be implemented in parallel as evolving capabilities allow. 40.3.1 Near term CALS capabilities. Initial implementation focuses on exploiting current and near-term technology to enhance the highest impact acquisition and logistics functions; specifically, it focuses on: a. Engineering drawings and other information used to support competitive spares procurement. b. Technical manuals and other information used to support weapon system maintenance. c. Logistic Support Analysis Records (LSARs) and other information used to plan logistic support. d. Life cycle configuration management of weapon system technical information. e. Automated interfaces among R&M data, logistics, system engineering, and CAD. 40.3.1.1 Near term CALS events. In these early implementation activities, application of technical standards will permit digital data interchange in neutral format within and among DoD components, and between DoD and industry. This interchange of technical data without resorting to paper products will result in increased accuracy and timeliness of data transfer at lower costs. Wherever possible, DoD is adopting approved national and international standards rather than creating unique DoD protocols to define this interface. From a technical perspective, CALS is applicable to equipment items at all levels of indenture, from the weapon system and weapon system platform to piece parts. However, CALS will find its most productive initial applications at the weapon system level, where the contractor and government infrastructures to use 58 MIL-HDBK-59A APPENDIX A these technical standards are already in place or planned. 40.3.1.2 Near term CALS mechanisms. The mechanism for implementing these near-term capabilities is a set of core requirements (i.e., sample contract language and technical standards) that will be used by the DoD components in near-term weapon system and data system acquisitions. The initial standards have been coordinated throughout DoD and the defense industry, and published as MIL-STD-1840 along with associated military specifications. Although it was published before CALS was established, MIL-STD-1388-2A is also considered to be one | of the CALS technical standards. This handbook is a companion document to the CALS standards that provides initial CALS implementation guidance to the acquisition manager. 40.3.1.3 CALS military specifications. CALS technical standards are being developed and published incrementally to provide additional levels of functional and technical | capability. MIL-STD-1840 provides data interchange and file management requirements for a family of supporting military specifications. The specifications already published include MIL-D-28000, MIL-M-28001, MIL-R-28002, and MIL-D-28003 (see 20.1.1). As other CALS military specifications are developed, this handbook will be updated to provide necessary application guidance. 40.3.2 Longer term CALS capabilities. While near term CALS implementation converts current paper flows to digital flows in a file transfer environment, longer term objectives target new functional capabilities that will be achieved through redesign, integration, and consolidation of the numerous parallel, duplicative processes that have grown up in our current paper- based culture. 40.3.2.1 CALS integrated data bases and processes. CALS will exploit the power of the computer by redesigning data formats and integrating what are now separate and often redundant | collections of data. These actions will fully integrate | support into the design process consistent with concurrent | engineering practices, and will link development of a variety | of logistic data products (e.g., technical publications, | drawings, support plans, etc.) with the design data base. This integration will produce large savings in productivity and result in improved readiness through much improved planning and support. CALS integrated data bases and processes will be designed to the extent feasible through industry cooperative efforts, because industry must implement most of the systems to create this capability. 59 MIL-HDBK-59A APPENDIX A 40.3.2.2 CALS Integrated Weapon System Data Base (IWSDB). The | conceptual (logical) definition and the total collection of | shared product definition, management, and support data used | throughout the life cycle of a weapon system is called an | IWSDB. Prime and subcontractor/vendor information should be | integrated within an ISWDB environment. Since physical location | of the data is likely to be distributed among contractor or | government automated data processing systems, strict controls | and coordination of an ISWDB will be required. The CALS IWSDB | structure is still evolving but the intent is to have it become | the basis for an integrated, shared data environment. Ideally, | an ISWDB will be governed by an active data dictionary | implemented through standards such as IRDS, and will be | consistent with the CALS data standards, including STEP. These | data standards will provide data element definitions, together | with the data relationships and rules for maintaining data | integrity and data consistency, and will accommodate changes in | user requirements and computer technologies that are inevitable | during the long lifespan of a weapon system. Ultimately, the | IWSDB distributed data base technology will enable an | authorized user to access information regardless of | geographical location and computer system configuration. | Ideally, this access can be initiated from and data returned to | application programs that the user exercises in his local | environment. | 40.3.2.3 CALS technology development. CALS must evaluate alternative technology approaches before committing to full- scale implementation of the IWSDB concept. This is being done through a series of technology R&D and demonstration programs that have been prioritized to facilitate the transition from interfaced to integrated systems and processes. Key development areas include advanced product data technology for CAD/CAE/CIM, electronic technical manual creation and delivery systems, concurrent engineering and integration of R&M with design, and telecommunications/gateway access to parts data bases. 40.3.2.4 IWSDB mechanisms. As with near-term implementation, the mechanisms for implementing longer-term CALS objectives will be a set of core requirements that address the functional and technical needs of acquisition managers. The difference will be the increasing emphasis on redefinition of functional requirements in a concurrent engineering environment, and on the application of appropriate supporting technology such as data management and access standards. The technology and standards for interfacing systems will be necessary but not sufficient for implementation of long term CALS objectives, and transition bridges between the capabilities of interfaced and 60 MIL-HDBK-59A APPENDIX A integrated systems will be needed. 40.3.2.5 Long-term CALS benefits. Achieving these long-term CALS objectives will yield the following benefits: a. More complete integration than is possible within interfaced "stovepipe" systems of contractor design, manufacturing, and support data systems based on advanced product data models. b. Near real-time updates of technical data to match weapon system configuration. c. On-line access by authorized government users to distributed contractor and government data bases. d. Data bases owned by DoD, but possessed and maintained either by DoD or by contractors. e. Improved authoring and delivery of technical manual and training material. f. Reduced leadtime for acquisition of spare parts. g. Improved R&M characteristics as a result of R&M integration with CAD/CAE design processes. h. Application of concurrent engineering strategies and programs to optimize product and acquisition process design and development. 40.3.3 CALS implementation schedules. Implementation of CALS requirements is technically and economically feasible now. Implementation of technology to interface contractor systems with government systems is already in process, and will continue into the mid-1990's and beyond. Planning and development for system integration has commenced; technology R&D activities are already underway, and implementation will start in the 1990's. DoD and industry will be implementing a mixture of system interfacing and system integration initiatives throughout the next decade. 40.3.4 CALS incentives mechanisms. Numerous contractual | incentive mechanisms are available to motivate contractors by | providing them with the opportunity to earn larger profits | through the application of CALS and the achievement of improved | performance. Table II presents the contractual incentive | mechanisms that may be used to incentivize contractors to | develop and apply CALS initiatives in a weapon system program. | 61 MIL-HDBK-59A APPENDIX A Contract incentives structures can be utilized to motivate | contractors to apply CALS initiatives to weapon system programs | at the various stages of the acquisition life cycle. | | 40.3.4.1 Fixed Price Incentive Fee. A Fixed Price Incentive | Fee (FPIF) can be applied to those programs where most | technical risk and uncertainty is low, as performance has | already been demonstrated, and where a CALS initiative could | enable the contractor to perform a cost savings. The FPIF | | TABLE II. Contract Incentives by Acquisition Phase | +---------------------------------------------------------------+ |TYPE OF | | | | | | |INCENTIVE | CONCEPT | DEMVAL | FSD | PROD | O&S | |===============================================================| |FIXED PRICE | | | | X | X | |INCENTIVE FEE | | | | | | | | | | | | | |COST PLUS | X | X | X | X | X | |INCENTIVE FEE | | | | | | | | | | | | | |COST PLUS | X | X | X | X | X | |AWARD FEE | | | | | | | | | | | | | |INDUSTRIAL | | X | X | X | X | |MODERNIZATION | | | | | | |INCENTIVES | | | | | | |PROGRAM | | | | | | | | | | | | | |VALUE | | X | X | X | X | |ENGINEERING | | | | | | +---------------------------------------------------------------+ contract includes a ceiling on the total price for performance | of the work. It also provides for an adjustment of profit and | the determination of the final contract price which does not | exceed the ceiling price by a cost sharing formula negotiated | by the government and contractor at the time of contract award. | The Contracting Officer and contractor negotiate a target cost, | a target profit and price. Through this incentive mechanism, | the risks and benefits of a CALS initiative would be shared by | the government and the contractor through a negotiated formula | of cost overruns and underruns. FPIF contracts are described | in FAR 16.403. | | 40.3.4.2 Cost-Plus-Incentive-Fee (CPIF). A Cost-Plus- | Incentive-Fee can be applied to those programs where | uncertainties in the performance of the contract preclude the | ability to reasonably estimate the cost of the effort. This | 62 MIL-HDBK-59A APPENDIX A means the contractor is paid allowable costs, however, a CALS | initiative could enable the contractor to perform at a lower | cost. At contract negotiation, the Contracting Officer and the | government negotiate a target cost and target fee together with | minimum and maximum fees. Cost overruns and underruns are then | shared in accordance with a negotiated formula until the | minimum or maximum fee is reached, as there is not a ceiling | price. This contract incentive is described in FAR 16.404-1 | and FAR 16.301-3. | | 40.3.4.3 Cost-Plus-Award-Fee (CPAF). A Cost-Plus-Award-Fee | can be applied to those level of effort procurements which are | not amenable to the establishment of specific contractual | performance, delivery or cost goals, but in which a CALS | initiative could enable the contract to improve performance. | At contract negotiation, a minimum and maximum fee and a set of | evaluating criteria to measure are established. As the | contract progresses, a government board, established under the | terms of the contract, evaluates the contractor's performance | using the established evaluation criteria to determine the | award portion of the fee earned through the level of effort | under review. The administrative work associated with the | implementation of a CPAF contract must be justified by the | expected benefits of this type of incentive. The contract type | is described in FAR 1604.2 and FAR 16.3013-3. | | 40.3.4.4 Industrial Modernization Incentives Program (IMIP). | The Industrial Modernization Incentives Program is an incentive | mechanism which may be appropriately applied to CALS | opportunities in certain instances. IMIP was formally | established as a DOD program in April of 1986 with the issuance | of DOD Directive 5000.44 and its associated guide (DOD 5000.44- | G). The IMIP provides industrial modernization incentives to | industry as described in the DOD FAR Supplement 15.872. The | objectives of IMIP are to encourage contractors, subcontractors | and vendors to: | | - Enhance productivity, reduce acquisition and other life | cycle costs, and improve product quality and reliability | as a function of the manufacturing process; | | - Invest in improved processes, methods, techniques, | facilities, equipment, software, and organization(s), | economical production and support of quality defense | material; | | - Shorten lead time and increase industry surge and | mobilization capability; | 63 MIL-HDBK-59A APPENDIX A - Accelerate the development and implementation of advance | manufacturing technology and provide maximum distribution | of the results; and | | - Implement manufacturing systems and related engineering | and management improvements based on a long-term | perspective and a plant-wide systems analysis. | | Through IMIP, contractors share in the savings resulting | from the modernization investment through the use of business | agreements. The business agreement is justified on the net | benefit to the government. | | IMIP can be a requirement contained in a weapon system | program's solicitation or it can be initiated through a mutual | government/contractor agreement during the performance of a | weapon system contract. Contractors can also propose IMIP | through an unsolicited proposal. | | The structured analysis associated with IMIP is beneficial | in delineating the costs and benefits associated with a CALS | capability in a particular program and comparing the CALS | opportunity with other modernization opportunities. IMIP is | also flexible in that the focus of the CALS application can be | program specific, organization-specific or factory-wide. | | The disincentives of program instability and cost-based | pricing are addressed through the shared savings incentive | payments of IMIP. A Productivity Savings Reward (PSR) allows | the contractor to receive an incentive from the identified | savings by maintaining an historical price level for a | negotiated period after the production cost reductions are | achieved. | | 40.3.4.5 Value Engineering Program. The Value Engineering | Program as set forth in FAR 48.102 is also an existing | incentive mechanism which may be applied to CALS opportunities. | Value engineering is an organized effort directed at analyzing | the function of systems, equipment, facilities, services and | supplies for the purpose of achieving the essential functions | at the lowest overall cost of ownership consistent with the | required performance, reliability, maintainability, | interchangeability, product quality assurance and safety. | | Value engineering is applied in two ways. The "incentive" | approach is when the contractor voluntarily suggests methods | for performing more economically. The "mandatory" approach is | when the contractor complies with contract clauses which | require a specific program be established to identify and | 64 MIL-HDBK-59A APPENDIX A submit to the government methods for performing more | economically. MIL-STD-1771 establishes the mandatory program | requirements for VE which is incorporated as a separately | priced line item of a contract. | | Contractors submit Value Engineering Change Proposals | (VECPs) under this program and share in the cost savings of | those that are accepted and implemented by the government. | There are two sources of savings to be shared under the VE | clauses: acquisition savings and collateral savings. | Acquisition savings include savings to in-place, concurrent and | future contracts. Collateral savings are savings to the | overall documentable projected cost of the operation, | maintenance, logistic support or government furnished property | realized through the implementation of a VECP. | | Value engineering can serve as a very useful tool for | incentivizing contractors to invest in CALS. Contractors can | examine the benefits to be derived by providing digital data | that is contractually requested, and they can also question the | need for all data. If they can demonstrate that some data is | not necessary, the life cycle savings from this data reduction | can be applied to the CALS investment. Another benefit of | value engineering is that acquisition savings are not the only | savings considered. The collateral savings realized through a | CALS investment may be much greater than acquisition savings. | In some cases, there may be no acquisition savings, but a | substantial reduction in logistic support costs. | | 40.3.4.6 Manufacturing Technology Program (MANTECH). The | Manufacturing Technology Program (MANTECH) may provide a source | of viable technology transfer for program specific CALS | initiatives. The MANTECH program was established by DOD to | develop or improve manufacturing processes, techniques, | materials and equipment to provide timely, reliable and | economical production of defense material. The purpose of the | program is to establish, validate, and implement advanced | manufacturing capabilities for producibility, productivity, | cost/price reduction and quality assurance. After DOD funds | the initial development and demonstration of the new or | improved technology, it expects that industry will apply the | technology in producing future weapon systems. The transfer of | technology related to CALS applications can be facilitated by | the program manager. | 40.4 CALS management organizations. The Deputy Secretary of Defense established a CALS Policy Office within the Office of the Assistant Secretary of Defense (Production and Logistics) to develop policy and plans for CALS implementation, develop 65 MIL-HDBK-59A APPENDIX A standards and corporate architecture elements, and facilitate accelerated implementation within industry. The Services and DLA, as identified in Table III have also designated CALS offices to meet the program objectives. The DoD CALS Steering Group established by the Deputy Secretary of Defense provides policy guidance and coordinates implementation activities. 66 MIL-HDBK-59A APPENDIX A TABLE III. CALS Points of Contact +--------------------------------------------------------------------+ | DEPARTMENT/ ADDRESS | | AGENCY COMMERCIAL AUTOVON | |====================================================================| | OSD DASD(PR)CALS 703-697-0051 227-0051 | | The Pentagon, Room 2B322 | | Washington, D.C. 20301- | | 8000 | | | | ARMY HQTRS, Dept. of the Army 703-614-3711 224-3711 | | Deputy Chief of Staff for | | Logistics (DCSLOG/PLC) | | Washington, DC 20310-0527 | | | | NAVY Office of the Chief of 703-695-3293 225-5728 | | Naval Operations (OP-403) | | Pentagon Room 4C535 | | Department of the Navy | | Washington, DC 20350 | | | | AIR FORCE HQTRS, Air Force Systems 301-981-3915 858-3915 | | Command, ATTN:PLXC | | Andrews AFB, DC 20334-5000 | | | | DEFENSE DLA-Z (DCLSO) 703-274-4210 284-4211/2 | | LOGISTICS 6301 Little River Turnpike | | AGENCY Beauregard Square, Suite | | 310 | | Alexandria, VA 22312 | +--------------------------------------------------------------------+ 67 MIL-HDBK-59A APPENDIX A THE DEPUTY SECRETARY OF DEFENSE WASHINGTON, D.C. 20301 MEMORANDUM FOR SECRETARIES OF THE MILITARY DEPARTMENTS DIRECTOR, DEFENSE LOGISTICS AGENCY SUBJECT: Computer-aided Acquisition and Logistic Support (CALS) To achieve productivity and quality improvements, my September 1985 letter on CALS set the goal of acquiring technical data in digital form (rather than paper) for weapon systems entering production in 1990 and beyond. We have now taken a major step toward routine contractual implementation. The Department of Defense (DoD) has coordinated with industry the first in a series of CALS issuances of national and international standards for digital data delivery and access. These standards have been published in MIL-STD-1840A, "Automated Interchange ofTechnical Information," and supporting military specifications. The CALS standards will enable either digital data delivery or government access to contractor-maintained technical data bases. Effective immediately, plans for new weapon systems and related major equipment items should include use of the CALS standards. Specifically: o For systems now in full-scale development or production, program managers shall review specific opportunities forcost savings or quality improvements that could result from changing weapon system paper deliverables to digital delivery or access using the CALS standards. o For systems entering development after September 1988, acquisition plans, solicitations, and related documents should require specific schedule and cost proposals for: (1) integration of contractor technical information systems and processes, (2) authorized government access to contrac- tor data bases, and (3) delivery of technical information indigital form. These proposals shall be given significant weight for their cost and quality implications in source selection decisions. The CALS standards shall be applied for digital data deliverables. DoD components shall program for automated systems to receive, store, distribute, and use digital weapon system tech- nical information, including achieving the earliest possible date for digital input to DoD engineering data repositories. These systems shall be conFigured or adapted to support the CALS FIGURE 3. CALS Implementation Requirements 68 MIL-HDBK-59A APPENDIX A standards. Plans for CALS implementation and productivity improvements will be addressed in Defense Acquisition Board and Major Automated Information System Review Council acquisition reviews, and in corresponding Service and Agency reviews. Each application decision shall be made on its own merits with respect to the productivity and quality improvementsexpected at either prime contractor or subcontractor level. The Under Secretary (Acquisition) will issue further guidance on contract requirements, such as CALS options, in invitations for bid; opportunities and safeguards for small business and other vendors and subcontractors; government and contractor incentives; and funding mechanisms for productivity-enhancing investments in automation and CALS integration by defense contractors. I believe that CALS is one of the most important and far reaching acquisition improvements we have undertaken. I wouldappreciate having the Assistant Secretary (Production and Logistics) receive your plan of action within 90 days, including identification of systems where opportunities exist for cost savings or quality improvement through application of CALS technology, the investment required to achieve these benefits, and proposed schedules for implementation. William H. Taft, IV cc: Under Secretary of Defense (Acquisition) Assistant Secretaries of Defense FIGURE 3. CALS Implementation Requirements - continued 69 MIL-HDBK-59A APPENDIX A THIS PAGE INTENTIONALLY LEFT BLANK 70