DOD 4140.01-M-1, COMPLIANCE FOR DEFENSE PACKAGING: PHYTOSANITARY REQUIREMENTS FOR WOOD PACKAGING MATERIAL (WPM) (7 SEP 2007)., Phytosanitary Requirements for Wood Packaging Material (WPM). This document provides guidance on the implementation of procedures for uniform compliance with international agreements on cross-border flows of 'Pest-Free" wood packaging materials.

DOD 4160.21-M-1, "DEFENSE DEMILITARIZATION MANUAL", OCTOBER 21, 1991; INCORPORATING CHANGE 1 - FEBRUARY 14, 1995., This Manual is issued under the authority of DoD Directive 4160.21, "DoD Personal Property Utilization and Disposal Program", December 5, 1980, and DoD Instruction 4160.27, "Demilitarization of Materiel", December 14, 1988. Its purpose is to set for DoD demilitarization policy, prescribe uniform procedures for assigning demilitarization codes to DoD property, and direct methods for completing demilitarization.

DoD 5015.02-STD. ELECTRONIC RECORDS MANAGEMENT SOFTWARE APPLICATIONS DESIGN CRITERIA STANDARD. This Standard is reissued under the authority of DoD Directive 5015.2, “Department of Defense Records Management Program,” March 6, 2000, (Reference (a)) which provides implementing and procedural guidance on the management of records in the Department of Defense. It sets forth mandatory baseline functional requirements for Records Management Application (RMA) software used by the DoD Components in implementing their records management programs; defines required system interfaces and search criteria that RMAs shall support; and describes the minimum records management requirements that must be met based on current National Archives and Records Administration (NARA) regulations.

DoD 3235.1-H (3rd Ed), TEST AND EVALUATION OF SYSTEM RELIABILITY, AVAILABILITY, & MAINTAINABILITY (A PRIMER). One step in the acquisition of military weapon systems and equipment is the verification that the candidate systems do, in fact, perform in accordance with previously specified operational requirements. The verification process involves the design of test programs which provide an adequate data base to support realistic assessments of hardware characteristics. This text outlines the concepts and techniques to be used in structuring such test programs and analyzing the resulting data. Since verifying the performance of every hardware item to be procured is neither practical nor possible, we base our projection of the entire population’s performance on the assessment of an available sample. This sample may consist of the first 10 preproduction aircraft of a projected buy of 725 or 50 percent of a lot of high-reliability pyrotechnic devices. In either case, we are utilizing statistical techniques to project or estimate the true value of some population’s characteristic, such as reliability, maintainability, weight, size, etc. The material contained in the following chapters is designed to familiarize the reader with the various statistical concepts and techniques required to thoroughly understand the relationships among test design, assessment and projection of population characteristics. The beginning chapters present background material on the three basic quantitative system parameters: reliability, availability and maintainability. The various definitions of these basic terms are discussed, as are the relationships among these parameters. The statistical concepts of confidence and producer’s and consumer’s risk are next introduced, with the majority of the text devoted to the practical application and significance of these concepts. The chapters utilize a combination of narrative and case studies to introduce and illustrate the usefulness of the concepts. It will prove quite useful to refer to the case studies while reading through the chapters. This study technique will prove especially helpful in Chapters 7 and 8, which present information on analyzing test data and structuring statistically adequate test programs. Chapter 9 contains an introductory discussion of the reliability growth concept. Chapter 10 presents qualitative aspects of test planning along with a description of data collection requirements.

DOD 4000.25-2-M, MILSTRAP - MILITARY STANDARD TRANSACTION REPORTING AND ACCOUNTING PROCEDURES (25 SEP 2001)., This manual is reissued under the authority of DoD Directive 4140.1, DoD Materiel Management Policy. Its purpose is to provide uniform procedures, formats, and codes governing the interchange of information for materiel in the inventory control and distribution systems of the DoD and other participating Agencies.

DOD 4120.15-L, "MODEL DESIGNATION OF MILITARY AEROSPACE VEHICLES" (12 MAY 2004)., The list is reissued under the authority of DoD Directive 4120.15, "Designating and Naming Military Aerospace Vehicles," May 2, 1985. Its purpose is to prescribe uniform procedures for designating and naming aerospace vehicles and to list approved designators and popular names.

DOD 4145.26-M, DEPARTMENT OF DEFENSE DOD CONTRACTORS SAFETY MANUAL FOR AMMUNITION AND EXPLOSIVES (SEP 1997). This Manual provides reasonable, standardized safety principles, methods, practices, requirements, and information for contractual work or services involving ammunition and explosives (A&E). Understanding and compliance with the applicable requirements of this Manual and additional safety requirements of the contract, if any, are intended to minimize the potential for mishaps that could interrupt Department of Defense (DoD) operations or delay production, damage or destroy DoD material, cause injury to DoD personnel, or endanger the general public. Adherence to the Manual's requirements and principles are intended to support DoD mission, provide a safe environment, and foster cooperation between contractor and DoD personnel.

DoD 4245.7-M TRANSITION FROM DEVELOPMENT TO PRODUCTION. A key to successfully managing cost and scheduling while producing high-quality products is the template approach. The assumptions for the template effort are different from most government improvement efforts. First, the template approach recognizes that weapons systems acquisition is an industrial process and not a purchasing process. Secondly, the template advocates believe that both government and industry employees really want to do their best, but do not know how to proceed. Thirdly, the template approach provides employees with the needed background to understand the engineering and management discipline behind the standards and regulations. The templates as defined in DoD 4245.7-M are not the final word on disciplined engineering practices or reducing technical risks. Instead, the templates are a reference and a model that engineers and managers apply to their own industrial processes. The DoD template approach addresses the need for good engineering discipline in all aspects of systems acquisition. The disciplined approach is essential for success in both the military and commercial arenas

DOD 4400.1-M, "DEPARTMENT OF DEFENSE PRIORITIES AND ALLOCATIONS MANUAL", (21 FEB 2002)., This Priorities and Allocations Manual is issued under the authority of DoD Directive 4400.1, "Defense Production Act Programs," October 12, 2001. This DPAS Manual prescribes uniform procedures to be followed by all persons delegated priorities and allocations authority, including those persons involved with awarding or administering contracts for research, development, engineering, acquisition, production, manufacturing, or construction.

DOD 4500.36-R, MANAGEMENT, ACQUISITION, AND USE OF MOTOR VEHICLES (16 MAR 2002)., This regulation is reissued under authority of DoD Directive 4500.36, :Management, Acquisition, and Use of Motor Vehicles, August 3, 2004. It delineates authorities and responsibilities concerning DoD-owned or -leased vehicles.

DoD 5000.04-M-1, COST AND SOFTWARE DATA REPORTING (CDSR) MANUAL (18 APR 2007)., This Manual reissues DoD 5000.4-M-1 (Reference (a)) pursuant to the authority of DoD Directive 5000.04 (Reference (b)) and DoD Instruction 5000.2 (Reference (c)). It cancels the interim guidance established in a February 20, 2004, memorandum from the Director, Program Analysis and Evaluation (Reference (d)). This Manual serves as the primary requirements document for the development, implementation, and operation of the contractor cost data reporting (CCDR) and software resources data reporting (SRDR) systems, collectively referred to as the cost and software data reporting (CSDR) system. It provides background information and detailed requirements for implementing the mandatory CCDR and SRDR policies established in References (b), (c), and DoD 5000.4-M (Reference (e)). It also prescribes procedures and instructions that DoD stakeholders in the CCDR and SRDR processes must follow. The procedures in this Manual apply to the Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other organizational entities within the Department of Defense (hereafter referred to collectively as the “DoD Components”). The requirements in this Manual ensure that the data reported through the CSDR system are accurate and consistent and are quickly made available to DoD cost and software estimators.

DOD 5000.4-M-1M, CONTRACTOR COST DATA REPORTING (CCDR) MANUAL (APRIL 16, 1999). The Contractor Cost Data Reporting (CCDR) system, as it exists today, is the product of over 50 years of events and decisions within the defense community that have affected the quality and utility of the data it contains. This Manual, developed jointly by the Office of the Secretary of Defense (OSD) and the Services with industry participation, serves as the primary source of information about operation and use of the CCDR system. It is the result of a major re-engineering effort to update the CCDR Pamphlet, which has not been changed since it was first issued in 1973. In addition to restating the mandatory guidance found in DoD 5000.2-R, the new manual contains recommended guidelines for contractors, program offices, and other stakeholders to facilitate CCDR planning and reporting. Mandatory contractor and subcontractor guidance is based on requirements stated in their contracts and subcontracts, respectively. A primary focus of this Manual is to ensure adequate contract planning that results in the appropriate contractual language to make the intended reporting requirements contractually binding. Appendix 1 describes the circumstances that gave rise to the demand for the cost information reported in the CCDR and explains how this form of cost reporting evolved.

DOD 5000.4M, DOD COST ANALYSIS GUIDANCE AND PROCEDURES (11 DEC 1992)., This Manual is issued under the authority of DoD Directive 5000.4, "OSD Cost Analysis Improvement Group (CAIG)," November 24, 1992. This Manual establishes: * Guidance on the preparation of the "Cost Analysis Requirements Document (CARD)." The CARD is to be prepared by the program office (or an office designated by the sponsoring DoD Component if the program office does not exist) describing the complete program and will be used as the basis on which the program office and DoD Component cost analysis teams prepare the program life-cycle cost estimates. * Guidance on the scope of the cost analysis, the analytical methods to be used in preparing cost estimates, and the procedures and presentation of the estimates to the Cost Analysis Improvement Group. * Definitions for seven cost terms and provides an understanding as to how they relate to life-cycle cost categories, work breakdown structure elements, and appropriations. 4. The requirements, objectives, uses, and administration of the "Visibility and Management of Operating and Support Costs (VAMOSC) Program."

DoD 5000.59-P, MODELING AND SIMULATION (M&S)MASTER PLAN. The DoD Modeling and Simulation Master Plan is authorized by DoD Directive 5000.59, "DoD Modeling and Simulation (M&S) Management," January 4, 1994. The DoD M&S policies, organizational responsibilities, and management procedures are outlined in DoD Directive 5000.59. This Plan is the Department of Defense’s first step in directing, organizing, and concentrating its M&S capabilities and efforts on resolving commonly shared problems. The immense breadth and scope of DoD M&S uses, combined with the relative immaturity of many segments of the larger DoD M&S community and its technology, ensure this first iteration is incomplete. Over time, with the active participation and support of the DoD M&S community, this plan will mature to address the full range of issues confronting DoD M&S. Many policy and technical issues may not be identified or resolved; however, this plan, with the management framework and policies established in DoD Directive 5000.59-P, provides a means to achieve common technical and policy consensus. This plan is intended to be dynamic and flexible, a living document that will evolve as technology matures and consensus develops on policy and programmatic issues.

DOD 5010.12-M, PROCEDURES FOR THE ACQUISITION AND MANAGEMENT OF TECHNICAL DATA. This Manual is applicable to the acquisition and management of data within the Department of Defense. This includes data both in paper and digital format and data to which the Department of Defense has access via contractor-provided services.

DOD 5100.76M, DEPARTMENT OF DEFENSE PHYSICAL SECURITY OF SENSITIVE CONVENTIONAL ARMS, AMMUNITION, AND EXPLOSIVES. In accordance with DoD Directive 5100.76 (reference (a)), this Manual prescribes minimum standards and criteria for the physical security of DoD sensitive conventional arms, ammunition, and explosives (AA&E), including non-nuclear missiles and rockets, as categorized in Appendix 1, in the custody of any DoD Component or DoD contractor. Arms, ammunition, and explosives in the custody of contractor-owned, contractor-operated facilities (COCOs) shall be protected only in accordance with the provisions of Appendix 2 of this Manual. Any additional requirements imposed by a DoD-procuring command or activity shall be specified in Section H, "Special Clauses Section," of the contract. Implementing guidance issued by the DoD Components shall be furnished to the Office of the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (OASD(C3I)).

DoD 5200.1-M, DEPARTMENT OF DEFENSE ACQUISITION SYSTEMS PROTECTION PROGRAM. In accordance with DoD Directive 5200.1 (reference (f)), and DoD Instruction 5000.2 (reference (g)), and DoD 5400.7-R reference (h)), this Manual prescribes standards, criteria, and methodology for the identification and protection of DoD Essential Program Information, Technologies, and/or Systems (EPITS) within DoD acquisition programs. Any additional guidance issued by the DoD Components to implement the requirements contained in this Manual shall be furnished to the DASD(I) within 6 months of the date of this Manual or following the issuance of additional guidance. The standards and criteria in this Manual are intended to protect against loss and unauthorized disclosure of EPITS throughout the acquisition process at all involved locations or facilities. They will also identify and reduce projected operational system susceptibility to damage, compromise, or destruction. The ultimate goal is to selectively and effectively apply security countermeasures to protect the EPITS and reduce costs by applying risk management.

DoD 5220.22-M, NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL (NISPOM) (28 FEB 2006)., This Manual is issued in accordance with the National Industrial Security Program (NISP). It prescribes the requirements, restrictions, and other safeguards to prevent unauthorized disclosure of classified information. The Manual controls the authorized disclosure of classified information released by U.S. Government Executive Branch Departments and Agencies to their contractors. It also prescribes the procedures, requirements, restrictions, and other safeguards to protect special classes of classified information, including Restricted Data (RD), Formerly Restricted Data (FRD), intelligence sources and methods information, Sensitive Compartmented Information (SCI), and Special Access Program (SAP) information. These procedures are applicable to licensees, grantees, and certificate holders to the extent legally and practically possible within the constraints of applicable law and the Code of Federal Regulations.

DOD 5230.25-PH, "CONTROL OF UNCLASSIFIED TECHNICAL DATA WITH MILITARY OF SPACE APPLICATION", (MAY 1985)., This pamphlet provides background on the problem of technology, outlines key provisions of the statues and directives aimed at reducing the loss, and spells out specific actions to be taken by person working with military related technical data. It is intended as a ready reference for all those who originate, disseminate or use DoD technical data.

DoD 8580.02-R, DoD HEALTH INFORMATION SECURITY REGULATION. This Regulation is issued under the authority of DoD Directive 5136.1 (Reference (a)). It assigns the Assistant Secretary of Defense for Health Affairs (ASD(HA)) the authority, direction, and control to establish policies, procedures, and standards that shall govern DoD medical programs. This Regulation is approved for public release with unlimited distribution and is available via the World Wide Web at: http://www.dtic.mil/whs/directives.

DOD ARCHITECTURE FRAMEWORK DESKBOOK (VERSION 1.0), DOD ARCHITECTURE FRAMEWORK WORKING GROUP (15 AUG 2003)., The Department of Defense (DoD) Architecture Framework (DoDAF), Version 1.0, defines a common approach for DoD architecture description development, presentation, and integration. The Framework enables architecture descriptions to be compared and related across organizational boundaries, including Joint and multinational boundaries. The Framework is partitioned into two volumes and a Deskbook. Volume I provides definitions, guidelines, and some background material. Volume II contains descriptions of each of the product types. This third volume is the DoD Architecture Framework Deskbook and provides supplementary guidance to Framework users. The Deskbook presents several techniques for developing and using architectures. These various techniques were developed by different segments of the DoD community and do not represent coordinated community positions. Volumes I and II presented mandatory guidance to the DoD community. The techniques presented in this Deskbook are not mandatory but are provided for their insights and potential utility to the reader. However, readers should determine the applicability of a technique to their individual situation. Because this Deskbook is being published as part of the DoDAF, the techniques herein were developed during the time that the C4ISR Architecture Framework was operative. Some, but not all, of the material ha s been updated to reflect the DoDAF. The reader may see some material that is C4ISR Architecture Framework specific. These small discrepancies should not interfere with the DoDAF-related value of the material. The Deskbook also provides additional material for topics that were introduced in Volumes I and II. This material includes the All-DoD Core Architecture Data Model (CADM), architecture tools, Federal Enterprise Architecture Reference Models, and Universal Reference Resources.

DOD DIRECTIVE 5000.1, THE DEFENSE ACQUISITION SYSTEM (12 MAY 2003)., This Directive: 1.1. Reissues reference (a) and authorizes publication of reference (b). 1.2. Along with reference (b), provides management principles and mandatory policies and procedures for managing all acquisition programs.

DOD GUIDE FOR ACHIEVING RELIABILITY, AVAILABILITY, AND MAINTAINABILITY (RAM GUIDE) (3 AUG 2005)., The primary objective of Department of Defense (DoD) acquisition is to acquire quality products (systems) that satisfy user needs with measurable improvements to mission capability and operational support in a timely manner, and at a fair and reasonable price.1 This guide supports that objective. It addresses reliability, availability, and maintainability (RAM) as essential elements of mission capability. It focuses on what can be done to achieve satisfactory levels of RAM and how to assess RAM.

DOD INTEGRATED PRODUCT AND PROCESS DEVELOPMENT (IPPD) HANDBOOK (AUGUST 1998). The 5000.2-R regulation describes the DoD acquisition process for MDAPs and MAIS acquisition programs incorporating IPPD principles. It defines IPPD as— A management technique that simultaneously integrates all essential acquisition activities through the use of multidisciplinary teams to optimize the design, manufacturing and supportability processes. IPPD facilitates meeting cost and performance objectives from product concept through production, including field support. One of the key IPPD tenets is multidisciplinary teamwork through Integrated Product Teams (IPTs). This handbook expands upon the government and industry guidance provided in the DoD Guide to IPPD by providing suggestions and examples of specific ways to implement IPPD. Like the DoD Guide to IPPD, it is non-directive. It suggests solutions to difficulties that might be encountered in IPPD implementation and explains tools and techniques that can be used throughout a product’s life cycle. It is not, however, an in-depth application manual for specific tools, nor does it attempt to cover all of the tools available—only representative ones from many different categories.

DOD-5015.02-STD, ELECTRONIC RECORDS MANAGEMENT SOFTWARE APPLICATIONS DESIGN CRITERIA STANDARD (25 APR 2007)., This Standard is reissued under the authority of DoD Directive 5015.2, “Department of Defense Records Management Program,” March 6, 2000, (Reference (a)) which provides implementing and procedural guidance on the management of records in the Department of Defense. It sets forth mandatory baseline functional requirements for Records Management Application (RMA) software used by the DoD Components in implementing their records management programs; defines required system interfaces and search criteria that RMAs shall support; and describes the minimum records management requirements that must be met based on current National Archives and Records Administration (NARA) regulations.

DOD-5015.2-STD, DESIGN CRITERIA STANDARD FOR ELECTRONIC RECORDS MANAGEMENT SOFTWARE APPLICATIONS (19 JUN 2002)., This Standard is reissued the authority of DoD Directive 5015.2 , “Department of Defense Records Management Program,” March 6,2000 which provides implementing and procedural guidance on the management of records in the Department of Defense. It sets forth mandatory baseline functional requirements for Records Management Application (RMA) software used by the DoD Components in the implementation of their records management programs; defines required system interfaces and search criteria to be supported by the RMAs; and describes the minimum records management requirements that must be met, based on current National Archives and Records Administration (NARA) regulations.

DODD 3200.11, DEPARTMENT OF DEFENSE DIRECTIVE, MAJOR RANGE AND TEST FACILITY BASE (MRTFB) (1 MAY 2002)., This Directive applies to the Office of the Secretary of Defense, the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other organizational entities within the Department of Defense (hereafter referred to collectively as "the DoD Components").

DODD 4630.5, DEPARTMENT OF DEFENSE DIRECTIVE, INTEROPERABILITY AND SUPPORTABILITY OF INFORMATION TECHNOLOGY (IT) AND NATIONAL SECURITY SYSTEMS (NSS) (5 MAY 2004)., This Directive applies to: 2.1. The Office of the Secretary of Defense, the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Inspector General of the Department of Defense, the Defense Agencies (see paragraph E2.1.5.), the DoD Field Activities, and all other organizational entities in the Department of Defense (referred to collectively as "the DoD Components").

DODD 5000.1, DEPARTMENT OF DEFENSE DIRECTIVE, THE DEFENSE ACQUISITION SYSTEM (12 MAY 2003)., This Directive applies to the Office of the Secretary of Defense, the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all organizational entities within the Department of Defense (hereafter collectively referred to as "the DoD Components").

DODD 5101.7, DEPARTMENT OF DEFENSE DIRECTIVE, DOD EXECUTIVE AGENT FOR INFORMATION TECHNOLOGY STANDARDS (MAY 21, 2004)., This Directive applies to the Office of the Secretary of Defense, the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other organizational entities in the Department of Defense (hereafter collectively referred to as the "DoD Components").

DODD 5105.19, DEPARTMENT OF DEFENSE DIRECTIVE, DEFENSE INFORMATION SYSTEMS AGENCY (DISA) (25 JUL 2006)., This Directive applies to the Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other organizational entities in the Department of Defense (hereafter referred to collectively as the “DoD Components”). The term “Military Services,” as used herein, refers to the Army, the Navy, the Air Force, and the Marine Corps.

DODD 5141.2, DEPARTMENT OF DEFENSE DIRECTIVE, DIRECTOR OF OPERATIONAL TEST AND EVALUATION (DOT&E) (MAY 25, 2000)., This Directive applies to the Office of the Secretary of Defense, the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, and the DoD Field Activities, and all other organizational entities within the Department of Defense (hereafter referred to collectively as "the DoD Components").

DODD 5200.28, DEPARTMENT OF DEFENSE DIRECTIVE NUMBER 5200.28, SECURITY REQUIREMENTS FOR AUTOMATED INFORMATION SYSTEMS (AISs) (21 MAR 1988)., This Directive: 1.1. Reissues and revises reference (a) to update uniform policy in addition to the policy set forth in reference (b) for the safeguarding of classified, sensitive unclassified, and unclassified information processed in AISs. 1.2. Updates the DoD-wide program for Automated Information System (AIS) security. 1.3. Provides mandatory, minimum AIS security requirements. More stringent requirements may be necessary for selected systems based on an assessment of acceptable levels of risk. 1.4. Promotes the use of cost-effective, computer-based (e.g., hardware, software, and firmware controls) security features for AISs. However, it is emphasized that system users have a personal responsibility to protect classified information under subparagraph 10-101.a. of reference (b). 1.5. Requires a more accurate specification of overall DoD security requirements for AISs that process classified or sensitive unclassified information. 1.6. Stresses the importance of a life-cycle management approach to implementing computer security requirements.

DODD 5200.40, DEPARTMENT OF DEFENSE DIRECTIVE, DOD INFORMATION TECHNOLOGY SECURITY CERTIFICATION AND ACCREDITATION PROCESS (DITSCAP) (30 DEC 1997)., Applies to the Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Inspector General of the Department of Defense (IG, DoD), the Defense Agencies, and the DoD Field Activities (hereafter referred to collectively as “the DoD Components”), their contractors, and agents.

DODD 5230.25, DEPARTMENT OF DEFENSE DIRECTIVE, WITHHOLDING OF UNCLASSIFIED TECHNICAL DATA FROM PUBLIC DISCLOSURE (6 NOV 1984)., Applies to the Office of the Secretary of Defense (OSD) and activities supported administratively by OSD, the Military Departments, the Organization of the Joint Chiefs of Staff, the Defense Agencies, and the Unified and Specified Commands (hereafter referred to collectively as "DoD Components").

DODD 8100.3, DEPARTMENT OF DEFENSE DIRECTIVE, DEPARTMENT OF DEFENSE (DOD) VOICE NETWORKS (16 JAN 2004)., The Office of the Secretary of Defense, the Military Services, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies (see paragraph E2.1.8., below) the DoD Field Activities, and all other organizational entities in the Department of Defense (referred to collectively as "the DoD Components").

DODD 8320.2, DEPARTMENT OF DEFENSE DIRECTIVE, DATA SHARING IN A NET-CENTRIC DEPARTMENT OF DEFENSE (2 DEC 2004)., This Directive applies to: 2.1. The Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD Field Activities, and all other organizational entities in the Department of Defense (hereafter referred to collectively as the “DoD Components”). 2.2. All data assets and information that are or may be available within the GIG.

DODI 5000.2, OPERATION OF THE DEFENSE ACQUISITION SYSTEM (12 MAY 2003)., This Instruction: 1.1. Reissues reference (a) and cancels reference (b). 1.2. Implements reference (c), the guidelines of references (d) and (e), and current laws. 1.3. Establishes a simplified and flexible management framework for translating mission needs and technology opportunities, based on approved mission needs and requirements, into stable, affordable, and well-managed acquisition programs that include weapon systems and automated information systems (AISs). 1.4. Consistent with statutory requirements and reference (c), authorizes Milestone Decision Authorities (MDAs) to tailor procedures to achieve cost, schedule, and performance goals.

E3 AND SM ASSESSMENT GUIDE FOR OPERATIONAL TESTING (13 JUN 2001)., This guide establishes Electromagnetic Environmental Effects (E3) and Spectrum Management (SM) assessment criteria for acquisition programs to assist Director, Operational Test and Evaluation (DOT&E) assessors, Operational Test Agencies (OTAs), and acquisition Program Managers (PMs) in executing the DOT&E “Policy on Operational Test and Evaluation of Electromagnetic Environmental Effects and Spectrum Management” (See Appendix A). Through the use of this guide, adverse E3 and SM issues can be identified during the early lifecycle phases of the acquisition process. E3 is defined as the impact of the electromagnetic environment upon the operational capability of military forces, equipment, systems, and platforms. It encompasses all electromagnetic disciplines, including electromagnetic compatibility (EMC)/electromagnetic interference (EMI); electromagnetic vulnerability (EMV); electromagnetic pulse (EMP); electronic protection (EP); hazards of electromagnetic radiation to personnel (HERP), ordnance (HERO), and volatile materials (HERF); and natural phenomenon effects of lightning and precipitation static (PStatic). SM is defined as planning, coordinating, and managing the use of the electromagnetic spectrum through operational, engineering, and administrative procedures, with the objective of enabling electronic systems to perform their functions in the intended environment without causing or suffering unacceptable interference. The major components of SM are spectrum certification (SC) and frequency assignment. SC is the process (called the JF-12 Process) by which spectrumdependent systems/equipment are certified to operate in a portion of the electromagnetic spectrum. Frequency assignment is the operational process that gives the users the authority to operate a fielded, spectrum-dependent system2 at specific locations on assigned frequencies within the allocated frequency band. In military operations, the control of E3 and the application of SM are concerned with promoting efficient, compatible use of the electromagnetic spectrum among military forces.

EVMIG (DEPARTMENT OF DEFENSE EARNED VALUE MANAGEMENT IMPLEMENTATION GUIDE - OCT 2007). This guide provides the uniform procedures which have been approved by the Director, Defense Contract Management Agency (DCMA) under assigned authority as the Department of Defense’s Executive Agent for Earned Value Management Systems (EVMS). This document has been coordinated by SAF/AQ, SAF/FM, ASA (ALT), ASN (RD&A), MDA/PO, NSA/CSS, and DCAA. This document provides guidance to be used during the implementation and surveillance of EVMS established in compliance with DoD Guidelines. Users of this guide are encouraged to submit recommendations for refined procedures to DCMA for consideration

This guide is intended to assist government and industry personnel in applying flexible packaging practices to meet the requirements of new and legacy equipment. It can be used as a tool for program managers, logistics managers, contracting officers, packaging subject matter experts, DCMA personnel and industry personnel to leverage commercial packaging practices, where possible, to meet defense packaging requirements. To retain a professionally competent workforce, it is imperative that knowledge about packaging practices be preserved. As an integrated resource tool across multi-functional lines, this guide will provide sufficient information to meet the needs of a large segment of readers with its contents. For others, the intent is to identify the additional resources and governing documentation that are relevant to the packaging body of knowledge. INTEGRATED DOD GUIDE TO PERFORMANCE-BASED PACKAGING PRACTICES, OSD, AT&L (OCT 2002)., This guidebook also includes an extensive list of appendices designed to serve as a quick reference dealing with issues discussed in the text. This document is for guidance only and not to be cited on contracts.

INTEGRATED MANGEMENT PLAN (IMP) AND INTEGRATED MASTER SCHEDULE (IMS) PREPARATION AND USE GUIDE. The guide provides guidance for the preparation and implementation of a program's Integrated Master Plan (IMP) and Integrated Master Schedule (IMS). The IMP and IMS are fundamental management tools that are critical to performing effective planning, scheduling, and execution of work efforts.

JSGS-87231A (NOTICE 1), JOINT SERVICES GUIDE SPECIFICATION ENGINES, AIRCRAFT, TURBINE (6 FEB 2001) [S/S BY JSSG-2007]., JSGS-87231A, dated 11 January 1995, is hereby cancelled. Future acquisition should refer to JSSG-2007, “Engines, Aircraft, Turbine”.

JSGS-87231A, JOINT SERVICES GUIDE SPECIFICATION ENGINES, AIRCRAFT, TURBINE (11 JAN 1995) [SUPERSEDING MIL-E-87231] [S/S BY JSSG-2007]., This specification establishes the item definition, performance, operating characteristics, reliability, maintainability, subsystems, physical characteristics, general design, installation, and interface requirements for manned aircraft gas turbine engines. This specification also establishes the analysis, inspections, demonstrations, and test procedures required by the Using Service for satisfactory completion and acceptance, of engine qualification Milestones IFR, FFR, ISR, and OCR for aircraft gas turbine engines. This specification also establishes the content and format to be used by the Using Service and/or contractor for the preparation of the acquisition and/or model specifications.

JSSG-2000B, DEPARTMENT OF DEFENSE JOINT SERVICE SPECIFICATION GUIDE, AIR SYSTEM (21 SEPT 2004)., This Joint Service Specification Guide (JSSG) establishes general requirements and verification parameters, integration, performance, and functions for the preparation of an air system program-unique specification. The program specification developed from this JSSG will be used for contractual commitments between the Government and the prime contractor for the procurement of an air system.

JSSG-2001B, DEPARTMENT OF DEFENSE JOINT SERVICE SPECIFICATION GUIDE, AIR VEHICLE (30 APR 2004)., This Joint Service Specification Guide (JSSG) establishes general requirements and verification parameters, integration, performance, and functions for the preparation of an air vehicle program-unique specification. The program specification developed from this JSSG will be used for contractual commitments between the Government and the prime contractor for the procurement of an air vehicle.

JSSG-2006, DOD JOINT SERVICE SPECIFICATION GUIDE, AIRCRAFT STRUCTURES (30 OCT 1998)., This guide establishes the joint structural performance and verification requirements for the airframe. These requirements are derived from operational and maintenance needs and apply to the airframe structure which is required to function, sustain loads, resist damage and minimize adverse operational and readiness impacts during usage for the entire service life. This usage pertains to both land and ship based operations including take-off, catapult, flight, landing, arrestment, ground handling, maintenance, and flight and laboratory tests. This specification also provides for trade studies and analyses to identify and establish certain structural design parameters and criteria which, as a minimum, are necessary to enable the airframe to meet these structural performance requirements, consistent with the program acquisition plan for force level inventory and life cycle cost.

JSSG-2009, DEPARTMENT OF DEFENSE JOINT SERVICES SPECIFICATION GUIDE AIR VEHICLE SUBSYSTEMS (30 OCT 1998)., This specification establishes the item definition, performance, operating characteristics, reliability, maintainability, physical characteristics, general design, installation, and interface requirements for Air Vehicle Subsystems. This specification also establishes the analysis, inspection, demonstrations, and test procedures required by Using Service for satisfactory completion and acceptance of subsystem component qualification Milestones SFR, PDR, CDR, FF, and SVR. This specification also establishes the content and format to be used by the Using Service or contractor for preparation of the acquisition or model specification.

JSSG-2010-10, DEPARTMENT OF DEFENSE JOINT SERVICE SPECIFICATION GUIDE, CREW SYSTEMS OXYGEN SYSTEMS HANDBOOK (30 OCT 1998) [SUPERSEDING AFGS-87226A AND MIL-STD-1776A(USAF)]., This handbook provides the guidance for the development requirements and verifications for an aircraft oxygen system and its components. This handbook is for guidance only. This handbook cannot be cited as a requirement. If it is, the contractor does not have to comply.

JSSG-2010-12, DEPARTMENT OF DEFENSE JOINT SERVICE SPECIFICATION GUIDE, CREW SYSTEMS DEPLOYABLE AERODYNAMIC DECELERATOR (DAD) SYSTEMS HANDBOOK (30 OCT 1998) [SUPERSEDING AFGS-87141B, MIL-P-85710(AS) AND MIL-STD-1776A(USAF)]., This handbook provides the guidance for the development requirements and verifications for deployable aerodynamic decelerator (DAD) system or subsystem. Previously these requirements have been applied strictly to parachute systems however, the term DAD has been used to encompass any deployable aerodynamic decelerator, flexible or rigid. However, since many of the requirements and guidance have been developed for specific parachute applications, the term "parachute" is still used frequently throughout the text. For the purposes of the generic requirements and guidance, the terms "decelerator" and "parachute" are synonymous. This handbook is for guidance only. This handbook cannot be cited as a requirement. If it is, the contractor does not have to comply.

JSSG-2010-5, DEPARTMENT OF DEFENSE JOINT SERVICE SPECIFICATION GUIDE, CREW SYSTEMS AIRCRAFT LIGHTING HANDBOOK (30 OCT 1998) [SUPERSEDING AFGS-87240A, MIL-L-85762A AND MIL-STD-1776A(USAF)]., This handbook provides the guidance for the development requirements and verifications for interior and exterior airborne lighting equipment, including specific requirements for interior lighting compatible with type I or II and class A or B night vision imaging systems (NVIS). This handbook is for guidance only. This handbook cannot be cited as a requirement. If it is, the contractor does not have to comply.

JSSG-2010-7, DEPARTMENT OF DEFENSE JOINT SERVICE SPECIFICATION GUIDE, CREW SYSTEMS CRASH PROTECTION HANDBOOK (30 OCT 1998)., This handbook establishes guidance for the development requirements and verifications for occupant crash protection and for crash protective aspects of seating, restraint, and crewstation and passenger/troop station design. This handbook is for guidance only. This handbook cannot be cited as a requirement. If it is, the contractor does not have to comply.

N-0105/01, NATIONAL IMAGERY TRANSMISSION FORMAT STANDARD (NITFS) STANDARDS COMPLIANCE AND INTEROPERABILITY TEST AND EVALUATION PROGRAM PLAN. This document establishes the National Imagery Transmission Format Standard (NITFS) Standards Compliance and Interoperability Test and Evaluation Program for achieving and sustaining NITFS based interoperability by all fielded and developmental digital imagery implementations. It describes the processes and procedures for obtaining testing of an imagery implementation for compliance with the NITFS and interoperability within the United States Imagery and Geospatial System (USIGS). It also prescribes NITFS Test and Evaluation Program policies, defines roles and responsibilities of participating organizations, and provides test funding guidance.

N-0105/98, NATIONAL IMAGERY TRANSMISSION FORMAT STANDARD (NITFS) STANDARDS COMPLIANCE AND INTEROPERABILITY TEST AND EVALUATION PROGRAM PLAN. This document establishes the National Imagery Transmission Format Standard (NITFS) Standards Compliance and Interoperability Test and Evaluation Program for achieving and sustaining NITFS based interoperability by all fielded and developmental digital imagery implementations. It describes the processes and procedures for obtaining testing of an imagery implementation for compliance with the NITFS and interoperability within the United States Imagery and Geospatial System (USIGS). It also prescribes NITFS Test and Evaluation Program policies, defines roles and responsibilities of participating organizations, and provides test funding guidance.

PMBOK GUIDE (1ST EDITION), U.S. DEPARTMENT OF DEFENSE EXTENSION TO: A GUIDE TO THE PROJECT MANAGEMENT KNOWLEDGE BODY OF KNOWLEDGE (PMBOK GUIDE). This document is the first edition (2003) of a U.S. Department of Defense (DoD) Extension to the Project Management Institute’s (PMI®) A Guide to the Project Management Body of Knowledge (PMBOK® Guide) 2000 Edition. The primary purpose of this document is to identify and describe defense applications of the core project management knowledge areas contained in the PMBOK® Guide, as well as those defense-intensive knowledge areas not contained in the Guide. It is important to understand that this is an extension to the PMBOK® Guide, and is not intended to be a stand-alone document. The PMBOK® Guide is a valuable document in its own right and its principles need to be understood and practiced by DoD Program Managers (PM). This Extension generally follows United States Department of Defense (hereinafter referred to as DoD) acquisition system policies and procedures (principally found in the DoD 5000 series directives – DoDD 5000.1, DoDI 5000.2, and Interim Defense Acquisition Guidebook (IDAG)). However, many of the concepts are generic to defense acquisition worldwide.

PROCUREMENT CUSTOMER GUIDE, DEPARTMENT OF DEFENSE EDUCATION ACTIVITY (28 OCT 2005)., This guide is intended to provide non procurement personnel with a better understanding of the Federal procurement process. The first section provides an overview of the entire acquisition cycle from cradle to grave. The second section provides guidance for planning your procurement. This section should answer the question “What do I do now, and how do I do it?” Section One, The Procurement Process Section Two, User’s Manual, provides a useful listing of steps and resources available to assist in the contracting process. This understanding allows you, as an acquisition team member, to participate more effectively during the contracting process. Greater understanding among team members contributes to the successful acquisition of supplies and services.

PROGRAM MANAGER'S DESKTOP GUIDE FOR CONTINUOUS ACQUISITION AND LIFE-CYCLE SUPPORT (CALS) IMPLEMENTATION (14 MAR 1997)., This guide provides information and guidance for applying the CALS strategy to the acquisition, management, and use of digital data in support of defense weapon systems and equipment. Service specific information is provided in the appendices of this guide.

RISK MANAGEMENT GUIDE FOR DOD ACQUISITION (MAR 1998)., This Risk Management Guide is designed to provide acquisition professionals and program management offices with a reference book for dealing with system acquisition risks. It is intended to be useful as an aid in classroom instruction and as a reference book for practical applications. Most of the material in this guide is derived from the Defense Acquisition Deskbook. Readers should refer to Paragraph 2.5.2 of the Deskbook for any new information.

RISK MANAGEMENT GUIDE FOR DOD ACQUISITION, SECOND EDITION (MAY 1999). This Risk Management Guide is designed to provide acquisition professionals and program management offices (PMOs) with a reference book for dealing with system acquisition risks. It is intended to be useful As an aid in classroom instruction and as a reference book for practical applications. Most of the material in this Guide is derived from the Defense Acquisition Deskbook. Readers should refer to Paragraph 2.5.2 of the deskbook for any new information.

RISK MANAGEMENT GUIDE FOR DOD ACQUISITION, SIXTH EDITION (Ver, 1.0. The purpose of this guide is to assist DoD and contractor Program Managers and Integrated Product Teams in effectively manageing risk during the entire acquisition process, including sustainment.

SD-15, DEFENSE STANDARDIZATION PROGRAM, PERFORMANCE SPECIFICATION GUIDE (JUN 29, 1995). On June 29, 1994, the Secretary of Defense directed sweeping reform of military specifications and standards. The Secretary directed the Department of Defense to make greater use of performance and commercial requirements in the acquisition process. Performance specifications are preferred over detail specifications. This document offers guidance on how to write performance specifications. The information is applicable to all types of materiel: systems, subsystems, assemblies, components, and parts. It is not meant to be a “cookbook” approach to developing performance specifications, but a guidance tool to provide direction and to shape the overall thought process. The SD-15 is intended to be a “living document” that will undergo changes as required. If you have any recommendations on improving this document, please send your comments to: Office of the Assistant Secretary of Defense (Economic Security) Standardization Program Division 5203 Leesburg Pike, Suite 1403 Falls Church, VA 22041-3466

SD-19, LIFE CYCLE COST SAVINGS THROUGH PARTS MANAGEMENT (JUN 2001)., This publication provides government and industry managers a pragmatic approach toward parts management to keep weapon system acquisition cost, total ownership cost, and supportability cost at a manageable level. This document is intended to be used by contractors. However, the acquisition activity or customer may also use it as a tool for evaluating contractor parts management performance. When used in conjunction with MIL-HDBK-512, Parts Management, the guidance herein will help achieve successful parts management support to acquisition strategy .This document offers guidance to individuals who are defining parts management needs in contracts; establishing a parts management process for prime contractors, suppliers and subcontractors; and looking for an efficient and a manageable part selection process. Additional guidance can be found in the Defense Acquisition Deskbook at http://web.deskbook.osd.mil, section 26G, Parts Control Program

SD-2, BUYING COMMERCIAL AND NONDEVELOPMENTAL ITEMS: A HANDBOOK (APR 1996)., This handbook is a guide for acquisition managers and personnel in other functional areas who are involved in buying commercial and nondevelopmental items (NDI). It is intended to help you buy these items without inhibiting your use of creative and innovative strategies. You should tailor the guidance provided to the circumstances of your particular acquisitions. We address the entire spectrum of acquisitions from systems to items, so you will also need to use sections of this handbook selectively. For example, the section on market research is generally applicable to all acquisitions while the chapter on logistics support is more relevant to system and repairable item acquisitions than consumable items. Many acquisition principles are the same for commercial items and NDI because for both types of items: · the basic design is set. · design changes are not controlled by the buyer. · the maximum use of commercial practices is desired. However, additional considerations apply when buying commercial items. Sections in this handbook that apply specifically to commercial items are so noted.

SD-21, LISTING OF SPECIFICATIONS AND STANDARDS MANDATED FOR USE BY THE DEPARTMENT OF DEFENSE BY PUBLIC LAWS OR GOVERNMENT REGULATIONS (LISTING LAST UPDATED MAY 2007)., The purpose of this document is to provide a list of known specifications and standards whose use by Department of Defense (DoD) program offices, buying activities, and contractors is mandated by Public Law or Government regulation. This information is intended for guidance only. Users must consult the actual Public Law or Government regulation in order to determine the applicability of a specification or standard, and if a waiver process exists to exempt mandatory use of a specification or standard. For this document, a specification or standard is defined as any document developed or adopted under the Defense Standardization Program (DSP) as described in DoD 4120.24-M, “Defense Standardization Program Policies and Procedures” and includes non-Government standards, defense specifications and standards, federal specifications and standards, commercial item descriptions, data item descriptions, and international standardization agreements. A major body of mandated documents not included in this listing because of the frequency of changes and the volume of documents are those specifications and standards in the DoD Information Technology Standards Registry (DISR).

SOFTWARE SYSTEMS SAFETY HANDBOOK (SSSH)- A TECHNICAL & MANAGERIAL TEAM APPROACH - DOD JOINT SOFTWARE SYSTEMS SAFETY. The purpose of the SSSH is to provide management and engineering guidelines to achieve a reasonable level of assurance that the software will execute within the system context with an acceptable level of safety risk.

STDI-002, THE COMPENDIUM OF CONTROLLED EXTENSIONS (CE) FOR THE NATIONAL IMAGERY TRANSMISSION FORMAT (NITF). This Controlled Extension (CE) compendium provides the approved CE specifications to be used with the National Imagery Transmission Format (NITF) versions 2.0 (NITF2.0) or 2.1 (NITF2.1). This compendium is an unclassified companion to STDI-0001, National Support Data Extensions (SDE) (Version 1. 3) for the National Imagery Transmission Format Standard (NITFS), 2 October 1998. The documents do not overlap or conflict. SDE implementation requirements are defined in N0105-98, NITFS Standards Compliance and Interoperability Test and Evaluation Program Plan, 25 August 1998.

SYSTEMS ENGINEERING PLAN (SEP) PREPARATION GUIDE (VER. 1.02) (10 FEB 2006)., This document guides program teams in generating their program’s Systems Engineering Plan (SEP) regardless of the acquisition category (ACAT) level of the program. This Guide provides an approach for organizing, compiling, and writing a SEP. It describes the key information to include in a SEP; it is not a tutorial on how to accomplish the technical activities discussed in the Plan. The SEP is a “living” document that captures a program’s current and evolving systems engineering strategy and its relationship with the overall program management effort. The SEP purpose is to guide all technical aspects of the program. It should be established early in the Concept Refinement phase, updated continually, and disseminated to the relevant team members.

SYSTEMS ENGINEERING PLAN (SEP) PREPARATION GUIDE (VER. 2.0) (OCT 18, 2007)., ODUSD (A&T) Systems and Software Engineering/Enterprise Development; This second version of the Department of Defense (DoD) Systems Engineering Plan (SEP) Preparation Guide clarifies the DoD guidance for systems engineering (SE) planning, or technical planning, for acquisition programs. The guide is separated into three sections tailored to respective milestones and acquisition phases: Milestone A and Technology Development (TD); Milestone B and System Development and Demonstration (SDD); and Milestone C and Production and Deployment (PD) / Operations and Support (O&S). The guide presents a sample SEP format for each milestone and suggests details to include and sources to consult for specific SEP paragraphs. This new version more clearly outlines the strategy for developing a program’s technical approach and offers a simplified framework for the program to organize, compile, and document technical planning. This guide is appropriate for all acquisition category (ACAT) programs and is applicable to each component of a