A GUIDE TO COLLECTION AND USE OF PAST PERFORMANCE INFORMATION (VER. 2) (MAY 2001), OFFICE OF THE DEPUTY UNDER SECRETARY OF DEFENSE FOR ACQUISITION REFORM., This guide is designed to articulate the key techniques and practices for the use and collection of past performance information. It provides guidance to encourage the use of innovative techniques in acquiring best value goods and services. Its purpose is to serve as a practical reference tool regarding the Department of Defense (DoD) past performance policy. This guide is designed for use by the entire acquisition workforce in both Government and industry. It explains best practices for the use of past performance information during the periods of source selection, ongoing performance, and collection of information. The guide is an ongoing joint effort of members from the Past Performance Integrated Product Team.

AMC-P 715-13/NAVSO P3647/AFMCP-65-101/BMDO 7008-G/DLAI 5000.7/DCAAP 7641.92/NSA/CSS N255-02, COST/SCHEDULE STATUS REPORT (C/SSR) JOINT GUIDE-COST/SCHEDULE MANAGEMENT OF NON-MAJOR CONTRACTS (1 MAY 1996)., This guide provides processes and procedures for the cost/schedule management of non-major contracts. This includes implementation and use of the Cost/Schedule Status Report (C/SSR) and the Cost Performance Report (CPR) when not associated with the use of the DOD Cost/Schedule Control Systems Criteria (C/SCSC). Users of this guide are encouraged to submit recommendations for changes through command channels to the appropriate Focal Points.

ATPD 2227, PURCHASE DESCRIPTION CARRIERS, COMMAND POST, LIGHT TRACKED: M577, M577A1, M577A2, AND M577A3; AND CARRIERS, COMMAND POST SYSTEM, STANDARDIZED INTEGRATED: M1068 AND M1068A3; PROCESSING FOR STORAGE AND SHIPMENT OF (9 JAN 1997) [SUPERSEDING MIL-DTL-46746E(AT)]., This purchase description covers the processing for storage and shipment of the M577, M577A1, M577A2, and M577A3 Light Tracked, Command Post Carrier and the M1068 and M1068A3 Standardized Integrated, Command Post System Carrier (see 6.1).

C/SSR JOINT GUIDE, COST/SCHEDULE MANAGEMENT OF NON-MAJOR CONTRACTS (AMC-P 715-13/NAVSO P3647/AFMCP-65-101/BMDO 7008-G/DLAI 5000.7/DCAAP 7641.92/NSA/CSS N255-02). In 1974, DOD recognized the need for a simpler approach for obtaining earned value performance data on "non-major" contracts -- contracts not requiring the discipline associated with the C/SCSC and the CPR. To meet this need, the C/SSR was created by modifying Format 1 of the CPR and adding a narrative section similar to the CPR Format 5. The C/SSR provides managers with familiar and useful CPR-like data while reducing the number of contract-unique reports. In addition, the C/SSR increases contractors' flexibility because it does not require them to establish, maintain or use a management control system that meets the C/SCSC. Instead, contractors must simply document and use their C/SSR management procedures when the C/SSR is a contract data requirement. The Government may conduct an on-site visit to understand and evaluate these procedures, and negotiate changes, if necessary. The C/SSR approach has led to more consistent performance reporting on non-major contracts while avoiding the increased discipline associated with C/SCSC compliance.

CJCSI 3170.01F, JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM (1 MAY 2007)., The purpose of this instruction is to establish the policies and procedures of the Joint Capabilities Integration and Development System (JCIDS).The procedures established in the JCIDS support the Chairman of the Joint Chiefs of Staff (CJCS) and the Joint Requirements Oversight Council (JROC) in identifying, assessing, and prioritizing joint military capability needs as specified in title 10, United States Code, sections 153, 163, 167, and 181 (reference a). Validated and approved JCIDS documents provide a record of the JROC’s advice and assessment in support of these statutory mandates. Additionally, the JCIDS is a key element in CJCS efforts to realize the initiatives directed in reference b. Specific procedures for the operation of the JCIDS and for the development and staffing of JCIDS documents can be found in reference c. Cancellation. CJCSI 3170.01E, 11 May 2005, “Joint Capabilities Integration and Development System” is canceled.

CJCSI 5122.01C, THEATER JOINT TACTICAL NETWORKS CONFIGURATION CONTROL BOARD (TJTN-CCB) CHARTER. This instruction facilitates implementation of the responsibilities established in reference a for the configuration control of theater joint tactical networks and the synchronization of programs associated with those systems for joint interoperability purposes. It empowers and institutionalizes the TJTN-CCB, to advise the Executive Agent for Theater Joint Tactical Networks (EA-TJTN) on coordinating initiatives regarding networked-communications systems within the joint communications community. This instruction delineates the TJTN-CCB’s responsibilities, composition, and basis for assembly. Refer to Enclosure A for the TJTN-CCB Charter.

CJCSI 6212.01D, INTEROPERABILITY AND SUPPORTABILITY OF INFORMATION TECHNOLOGY AND NATIONAL SECURITY SYSTEMS. This instruction a. Establishes policies and procedures for developing, coordinating, reviewing, and approving Information Technology (IT) and National Security System (NSS) Interoperability and Supportability (I&S) needs. b. Establishes procedures to perform I&S Certification and J-6 System Validation of Joint Capabilities Integration and Development System (JCIDS) Acquisition Category (ACAT) programs/systems cited in references a and b. c. Establishes procedures to perform I&S Certification and J-6 System Validation of Information Support Plans (ISPs) for all non-ACAT and fielded programs/systems (references c and d). d. Defines the four elements of the Net-Ready Key Performance Parameter (NR-KPP). e. Provides guidance for NR-KPP development and assessment. f. Establishes procedures for Joint Interoperability Test Command (JITC) Joint Interoperability Test Certification.

CJCSI 6215.01B, CHAIRMAN OF THE JOINT CHIEFS OF STAFF INSTRUCTION, POLICY FOR DEPARTMENT OF DEFENSE VOICE NETWORKS. This instruction establishes policy and prescribes responsibilities for use and operation of the DOD voice networks, specifically the DSN and the DRSN.

CJCSI 6510.01D, INFORMATION ASSURANCE (IA) AND COMPUTER NETWORK DEFENSE (CND). To provide joint policy and guidance for information assurance (IA) and computer network defense (CND) operations in accordance with (IAW) references (a-sss).

CJCSI 8010.01B JOINT COMMUNITY WARFIGHTER CHIEF INFORMATION OFFICER (8 SEPT 2006), This instruction assigns the position of Joint Community Warfighter (JCW) Chief Information Officer (CIO), establishes applicable policy, and outlines the duties and responsibilities of that position. Cancellation. Chairman of the Joint Chiefs of Staff Instruction (CJCSI)8010.01A, 13 June 2003, “Joint Community Chief Information Officer,” is canceled.

CJCSM 3170.01C OPERATION OF THE JOINT CAPABILITIES INTEGRATION AND DEVELOPMENT SYSTEM (1 MAY 2007), This manual sets forth guidelines and procedures for operation of the Joint Capabilities Integration and Development System (JCIDS) regarding the development and staffing of JCIDS documents in support of reference a. 2. Cancellation. CJCSM 3170.01B, 11 May 2005, “Operation of the Joint Capabilities Integration and Development System,” is canceled.

CJCSM 5712.01B, STANDARDS FOR VISUAL AIDS USED IN THE JOINT STAFF. This manual prescribes standards to be used in the preparation of automated presentations in the Joint Staff.

CJCSM 6231.02A, MANUAL FOR EMPLOYING JOINT TACTICAL COMMUNICATIONS (1 AUG 1998)., CJCSM 6231.02A provides information and guidance to personnel involved in the planning, engineering, installation, and management of circuit switches that are employed in support of joint exercises and contingency operations. The following major topics are addressed: a. Tactical circuit switch technical and functional descriptions and features. b. Numbering systems and plans and routing. c. Network planning considerations. d. Circuit switch planning and database entries. e. Telephone subscriber and circuit switch interfaces. f. AN/TTC-39 series switch trunk interfaces. g. Circuit switch interface planning guides. h. Red switch interconnectivity.

DISA ACQUISITION DESKBOOK - SOURCE SELECTION (MAR 2000)., This deskbook provides supplemental Agency procedures/guidance about the source selection process. Controlling procedures/guidance are found in the Federal Acquisition Regulation (FAR) Part 15; Defense Federal Acquisition Regulation Supplement (DFARS) Part 215 and Defense Information Systems Agency Acquisition Regulation Supplement (DARS) Part 15. For the purposes of future updates, this Deskbook is consistent with Federal Acquisition Regulation (FAR) (through Federal Acquisition Circular 97-15, effective 27 Dec 00); DFARS (through DFARS Change Notice 20000210, effective 10 Feb 00); and DARS (through DISA ACs 97-09 and 97-14). The FAR, DFARS and DARS are accessible on the D41 hompage. In the case of any conflicting guidance between these documents and this deskbook, the other documents are controlling.

DLAM 4145.12, JOINT SERVICE MANUAL (JSM) FOR STORAGE AND MATERIALS HANDLING (12 APR 1994) [ARMY TM-38-400; NAVSUP PUB 572; AFMAN 23-210; MCO 4450.14]., This manual establishes uniform storage and materials handling policies, procedures, and responsibilities for use by the Department of Defense (DOD) supply installations involved in the receipt, storage, issue, and care of military supplies and equipment, except for preservation/packing and defense reutilization and marketing facilities, maintenance of bulk petroleum fuel handling facilities, and hazardous materials storage.

DMA TM-8358.1 (EDITION 1), DEFENSE MAPPING AGENCY TECHNICAL MANUAL 8358.1 DATUMS, ELLIPSOIDS, GRIDS, AND GRID REFERENCE SYSTEMS (20 SEP 1990)., This manual describes the basic principles of the Military Grid Reference System and the nonstandard reference systems. It describes the method for determining references on maps and charts at scales of 1:1,000,000 and larger. It contains identifications for the grid zone designations and for the 100,000 meter squares of the Universal Transverse Mercator Grid and the Universal Polar Sterographic Grid. It also contains the specifications and grid identifications for the various non-standard grids. It provides diagrams and textual information for delineating geodetic datums and ellipsoids. Subject Terms: Position location, military grid, geodetic datum, coordinate reference system, ellipsoid, spheroid, graticule, chart, projection.

JAG INSTRUCTION 5800.7E, MANUAL OF THE JUDGE ADVOCATE GENERAL (JAGMAN) (20 JUN 2007)., Purpose: to promulgate the Manual of the Judge Advocate General (JAGMAN), as authorized by the Secretary of the Navy. Cancellation: JAG Instruction 5800.7d of 22 March 2004 is hereby canceled.

JMH-2000, JOINT METEOROLOGY AND OCEANOGRAPHY (METOC) HANDBOOK (JMH) (3RD EDITION) (1 MAY 2000)., The Joint Meteorology and Oceanography (METOC) Handbook (JMH) was originally compiled to provide information to participants in U.S. Joint Forces Command training exercises and operations. The Services' METOC communities found the Handbook useful, and it is now distributed throughout the Services to aid those who may suddenly find themselves fulfilling the role of Joint Task Force (JTF) METOC Officer (JMO). This document does not constitute a requirements document or initial doctrine. This handbook intends to provide the JMO, his staff, and Service and functional component METOC personnel, an easy to use reference manual to assist the planning and execution of METOC support for joint operations. The Joint METOC Handbook describes existing joint structure, how METOC personnel and organizations are integrated into the combatant command and JTF structures, and what METOC resources are available. Separate chapters cover METOC capabilities and support to operational forces within Service organizational structures. It is important to understand the joint operational planning process and how the METOC officer fits into that process. The duties and responsibilities of the Senior METOC Officer (SMO) and JMO and their interaction during a joint operation are important concepts. The coordination between the JMO and his Service and functional component METOC units is vital to the success of joint METOC operations. The concept of “one theater, one forecast,” highlighted in Joint Publication 3-59, is the cornerstone of METOC support to a joint operation. Coordination is critical. METOC support to the overall joint operation as well as the JTF headquarters element is important. Joint METOC personnel should understand the capabilities of Service level METOC equipment and tactical and fixed communication systems for interoperability. The sources of METOC data and available products and services from various METOC production sites and theater level operational commands are useful for any military operation. The appendices provide Service METOC personnel and equipment information for Time Phased Force and Deployment Data and formats for METOC inputs to Operations Plans. A starting list of criteria for METOC impacts to operations is provided for many types of operations; during an actual operation, METOC personnel must tailor impacts to the mission and its critical thresholds. Examples of Joint Operational Area Forecasts (JOAFs), METOC Letters of Instruction (LOIs), and joint METOC briefing slides come from previous joint operations and exercises. METOC personnel wishing a copy of this handbook should contact their Service distribution point, listed in Appendix Z. Additionally, the handbook is located on USJFCOM’s METOC SIPRNET homepage, http://157.224.120.250/weathr.nsf/metoc (go to Pubs and Documents). The goal of the JMH is to provide an easy to use reference manual for all METOC personnel. Toward that goal, the USJFCOM SMO will attempt to revise this Handbook annually, so that new and important information can be incorporated into one document and provided to the METOC community at large.

JOINT TEST AND EVALUATION HANDBOOK (REV. 1) (29 JUN 2007)., The Joint Test and Evaluation (JT&E) Program objective is to find ways for warfighters to do their jobs better with today’s equipment, organization, and doctrine. This objective is achieved after successfully evaluating new concepts and addressing needs and issues that occur in joint military environments. The program includes the nomination process; the joint feasibility study process, which determines whether selected nominations are operationally needed and technically feasible; and, when making such a determination, the execution of a JT&E project chartered by the Director, Operational Test and Evaluation. The process and procedures for nominating and conducting a quick reaction test are also included. Department of Defense Directive (DOD Directive) 5010.41, “Joint Test and Evaluation (JT&E) Program,” describes the JT&E Program purpose, identifies the principal participants and their responsibilities, and outlines the framework within which each Service supports the program. Service support is described in detail in applicable Service directives. This handbook and the separately published JT&E Style Guide replace all previously issued handbooks, policies, and standing operating procedures. This handbook provides the JT&E business model and Office of the Secretary of Defense (OSD) guidance, policies, and direction, as well as general JT&E information, references, and procedures to the Joint Test Director, Services, combatant commands, defense agencies, the Joint Staff, and OSD Staff relative to the execution of a JT&E project.

JOINT TEST AND EVALUATION PROGRAM STYLE GUIDE, SUPPLEMENT TO THE JOINT TEST AND EVALUATION PROGRAM HANDBOOK (29 JUN 2007)., 1.0 Introduction The Joint Test and Evaluation (JT&E) Program Style Guide is designed to ensure the consistency of all JT&E Program documentation. This guide is for use by the JT&E Program Office (JPO); JT&E-Suffolk, and all JT&E projects, including joint feasibility studies (JFS), joint tests (JT), and quick reaction tests (QRT).

MARITIME SIGINT ARCHITECTURE (MSA) TECHNICAL STANDARDS HANDBOOK (VER. 1.0) (23 AUG 1999)., The Maritime SIGINT Architecture Technical Standards Handbook (MSH) provides essential information for acquisition managers, engineers and other individuals responsible for acquiring, developing or modernizing tactical Maritime SIGINT Systems (MSS). Collaboratively developed by elements of the U.S. Navy, U.S. Marine Corps, U.S. Special Operations Command, and the National Security Agency, it is the first effort by the maritime partners to establish cohesive standards for their tactical SIGINT systems. Consistent with the Joint Technical Architecture and the Unified Cryptologic Architecture (UCA), the MSH bridges the standards gap between the tactical maritime Services and the national SIGINT community. It provides a technical foundation for the interoperability and seamless flow of information between tactical and national SIGINT systems, as well as among tactical SIGINT systems and their host Command, Control, Communications, Computer, Intelligence, Surveillance, and Reconnaissance (C4ISR) systems. It constitutes both the cryptologic subset of the Naval C4ISR Technical Architecture and the maritime component of the UCA Technical Architecture. Moreover, it is the technical complement of the Maritime Cryptologic Architecture's (MCA) Operational View and, in its next iteration, will become the MCA's Technical View. The MSH contains common standards and specifications which will reduce development costs, facilitate the leveraging of SIGINT functionality across maritime programs, and increase interoperability between them. More specifically, it: · Identifies and mandates minimum standards and technical guidelines for MSS · Determines essential data formats and protocols · Selects and defines standards to migrate MSS to an open systems environment · Incorporates new and emerging standards to keep pace with technology Use of the MSH by acquisition managers and system developers will greatly facilitate attainment of Department of Defense objectives for interoperability, connectivity and modernization among tactical SIGINT systems.

MIL-BUL-147, MILITARY BULLETIN SPECIFICATIONS AND STANDARDS OF NON-GOVERNMENT ORGANIZATIONS RELEASED FOR FLIGHT VEHICLE DESIGN AND CONSTRUCTION (14 APR 1989)., This bulletin lists non-Government specifications and standards approved as indicated for use in new design of structure, airframe, and related fluid systems on aerospace vehicles.

TAFIM, VOLUME 1: OVERVIEW, DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation. ., The purpose of this DoD HCI Style Guide (or the Style Guide) is to provide a common framework for HCI design and implementation. Through this framework, the long-term functional goals, objectives, and requirements of the HCI will be defined and documented. Volume 8 1-2 Version 3.0 DoD Human Computer Interface Style Guide 30 April 1996 Interface implementation options will be standardized, enabling all DoD applications to appear and operate in a reasonably consistent manner.

TAFIM, VOLUME 2: TECHNICAL REFERENCE MODEL, DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation. ., The purpose of this DoD HCI Style Guide (or the Style Guide) is to provide a common framework for HCI design and implementation. Through this framework, the long-term functional goals, objectives, and requirements of the HCI will be defined and documented. Volume 8 1-2 Version 3.0 DoD Human Computer Interface Style Guide 30 April 1996 Interface implementation options will be standardized, enabling all DoD applications to appear and operate in a reasonably consistent manner.

TAFIM, VOLUME 3: ARCHITECTURE CONCEPTS AND DESIGN GUIDANCE, DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation. ., The purpose of this DoD HCI Style Guide (or the Style Guide) is to provide a common framework for HCI design and implementation. Through this framework, the long-term functional goals, objectives, and requirements of the HCI will be defined and documented. Volume 8 1-2 Version 3.0 DoD Human Computer Interface Style Guide 30 April 1996 Interface implementation options will be standardized, enabling all DoD applications to appear and operate in a reasonably consistent manner.

TAFIM, VOLUME 4: DOD STANDARDS-BASED ARCHITECTURE PLANNING GUIDE, DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation.

TAFIM, VOLUME 5: PROGRAM MANAGER'S GUIDE FOR OPEN SYSTEMS, DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation. ., The purpose of this DoD HCI Style Guide (or the Style Guide) is to provide a common framework for HCI design and implementation. Through this framework, the long-term functional goals, objectives, and requirements of the HCI will be defined and documented. Volume 8 1-2 Version 3.0 DoD Human Computer Interface Style Guide 30 April 1996 Interface implementation options will be standardized, enabling all DoD applications to appear and operate in a reasonably consistent manner.

TAFIM, VOLUME 6: DEPARTMENT OF DEFENSE (DOD) GOAL SECURITY ARCHITECTURE, DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation. ., The purpose of this DoD HCI Style Guide (or the Style Guide) is to provide a common framework for HCI design and implementation. Through this framework, the long-term functional goals, objectives, and requirements of the HCI will be defined and documented. Volume 8 1-2 Version 3.0 DoD Human Computer Interface Style Guide 30 April 1996 Interface implementation options will be standardized, enabling all DoD applications to appear and operate in a reasonably consistent manner.

TAFIM, VOLUME 7: ADOPTED INFORMATION TECHNOLOGY STANDARD (AITS), DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation.

TAFIM, VOLUME 8: DOD HUMAN COMPUTER INTERFACE STYLE GUIDE, DEFENSE INFORMATION SYSTEMS AGENCY CENTER FOR STANDARDS DEPARTMENT OF DEFENSE TECHNICAL ARCHITECTURE FRAMEWORK FOR INFORMATION MANAGEMENT (TAFIM) (VER 3.0) (30 APR 1996)., The TAFIM provides a set of volumes for guiding the evolution of the DoD’s technical architecture, which consists of multiple environments with each environment accommodating one or more ISAs. The TAFIM consists of multiple volumes in various states of development and maturity. The volumes that constitute Version 3.0 of the TAFIM are listed below: Volume 1: Overview; Volume 2: Technical Reference Model provides the conceptual model for information system services and their interfaces; Volume 3: Architecture Concepts and Design Guidance provides concepts and guidance needed to support the development of technical architectures in the DoD; Volume 4: DoD Standards-Based Architecture Planning Guide provides a standards-based architecture planning methodology that will help architects, technical integrators, and developers to plan and build information systems that meet mission, functional, and application area requirements. The methodology provides a translation of functional requirements to the selection of services, standards, components, configurations, their phasing, and the acquisition of products that implement them; Volume 5: Program Managers Guide for Open Systems describes how to use the TAFIM guidance in the acquisition of IT and IM products; Volume 6: DoD Goal Security Architecture (DGSA) addresses security requirements commonly found within DoD organizations’ missions or derived as a result of examining mission threats. Further, the DGSA provides a general statement about a common collection of security services and mechanisms that an information system might offer through its generic components. The DGSA also specifies principles, concepts, functions, and services that target security capabilities to guide system architects in developing their specific architectures. The generic security architecture provides an initial allocation of security services and functions and begins to define the types of components and security mechanisms that are available to implement security services. In addition, examples are provided of how to use the DGSA in developing mission-level technical architectures; Volume 7: Adopted Information Technology Standards (AITS) is the definitive set of IT standards to be used in DoD. It is intended to guide DoD acquisitions and the migration of legacy systems and, by providing definitive standards, to support broader TAFIM objectives such as interoperability, reduced life-cycle costs, and security; Volume 8: DoD Human Computer Interface (HCI) Style Guide provides a common framework for HCI design and implementation. ., The purpose of this DoD HCI Style Guide (or the Style Guide) is to provide a common framework for HCI design and implementation. Through this framework, the long-term functional goals, objectives, and requirements of the HCI will be defined and documented. Volume 8 1-2 Version 3.0 DoD Human Computer Interface Style Guide 30 April 1996 Interface implementation options will be standardized, enabling all DoD applications to appear and operate in a reasonably consistent manner.