Exhibit_B _Data_Item_Descriptions.pdf

FA9101-14-R-0200

Exhibit B

Data Item Descriptions

DATA ITEM DESCRIPTION

Title: Program Progress Report

Number: DI-MGMT-80555A Approval Date: 14 Nov 2006 AMSC Number: 7640 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: The Program Progress Report provides the Government with the means to evaluate and monitor the progress made by the contractor of tasks in accomplishing the goals established for the program.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID is applicable when the monitoring for the progress of a program is required.

This DID supersede DI-MGMT-80555.

Requirements:

1. Reference documents. None.

2. Format. The Program Progress Report shall be in contractor’s format.

2.1 Title page. The title page shall contain the following:

2.1.1 Title. The title shall identify the subject of the report, program name, or task.

2.1.2 Name of contractor. The name of the contractor preparing the report.

2.1.3 Contract number. The procurement instrument identification number.

2.1.4 Key person. The individual assigned to the task or who produced the report.

2.1.5 Reporting period. The dates the reporting period begins and ends.

2.2 Paper size. The report shall be on 8 ½ x 11 inch or metric size A4 paper and typewritten of otherwise duplicated on nonfading ink.

Source: https://assist.dla.mil -- Downloaded: 2014-07-02T19:14Z

Check the source to verify that this is the current version before use.

DI-MGMT-80555A

3. Contents. The report shall contain the following:

3.1 Work summary. A brief summary of work performed during the reporting period providing positive or negative comments.

3.2 Schedule. A statement as to whether task or program is on schedule and if not, efforts planned to meet schedule shall be explained.

3.3 Studies. Discussion of all studies conducted during the reporting period and the results.

3.4 Experimental work/test procedures. An explanation of experimental work accomplished, description of test procedures applied (cite applicable military specification, paragraph number and test parameters), results of test and conclusions determined.

3.5 Designs. A description and illustration of all designs produced, along with required changes made to a previous design and a brief statement of any problems encountered.

3.6 Test equipment. Description, nomenclature and serial number of all test equipment used on the project including appropriate schematic or block diagrams.

3.6.1 List the serial number of all equipment(s) subjected to the testing.

3.6.2 Provide a brief description of all special test equipment designed of constructed for use on the project including appropriate schematic of block diagrams.

3.7 Test performed. Identification and description of all test (s) performed (cite applicable military specification, paragraph number, and test parameters).

3.7.1 Provide control settings of the test sample.

3.7.2 Resolutions of measurement equipment and range of input signals.

3.8 Failures. A brief explanation of any failures associated with test and appropriate photographs, sketches, etc. to show failures, their causes or other unusual conditions.

3.9 Difficulties/problems. Describe any difficulties or problems encountered or which previously existed which could alter the progression of work along with recommendations of resolution.

3.10 Plan. Steps followed during execution of tasks.

DI-MGMT-80555A

3.11 Completion dates. Projected completion dates for each task.

3.12 Percentage. Percentage of task completed to date and percentage of allocated funds expended on tasks.

3.13 Additional information. Other information which may cause a significant change in the work schedule.

4. END OF DI-MGMT-80555A

Title: OPERATIONS SECURITY (OPSEC) PLAN

Number: DI-MGMT-80934C Approval Date: 20101213 AMSC Number: 9178 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/I925 Applicable forms: N/A

Use/Relationship: The OPSEC Plan is used to identify and monitor a contractor’s OPSEC activities during the performance of a contract. It is intended to be a living document that will require periodic updates throughout the life of the contract. The OPSEC plan; (1) Describes the OPSEC environment to include identification of critical information, the OPSEC threat and vulnerabilities an adversary might exploit to acquire critical information, (2) Documents the OPSEC risk analysis, (3) Identifies proposed and actual OPSEC measures, (4) Defines and assigns specific OPSEC responsibilities and ties the OPSEC Plan to the contractor’s corporate OPSEC Program, and (5) Serves as a repository of the OPSEC history of the contract.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements delineated in the contract.

b. This DID is applicable only when the contracting activity determines that the sensitivity of the contracted effort warrants OPSEC protections.

c. The contractor’s implementation of the OPSEC Plan, approved by the contracting activity, is subject to joint audit and/or inspection by the Defense Security Service and the contracting activity.

d. This DID supersedes DI-MGMT 80934B.

Requirements:

1. Reference documents: The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices and revisions, shall be as specified in the contract.

a. “Applying OPSEC to U.S. Government Acquisitions and Contracts”. This document is available from the Interagency OPSEC Support Staff (IOSS) at the following web address:

www.ioss.gov.

b. Department of Defense Manual (DODM) 5205.02M, DOD Operations Security (OPSEC) Program Manual, dated November 3, 2008.

Source: https://assist.dla.mil -- Downloaded: 2014-07-02T18:58Z http://www.ioss.gov/

DI-MGMT-80934C

c. Department of Defense Contract Security Classification Specification (DD 254). This document is included as a part of all Request for Proposals (RFP) and Contracts involving classified data.

d. Contract Data Requirements List (CDRL). This document is included as a part of all RFP and contracts containing data deliverable requirements.

e. National Industrial Security Program Operating Manual (NISPOM) 5220.22M, dated February 28. 2006.

2. Format: The OPSEC Plans shall be submitted in contractor determined format and, at a minimum, consist of the following sections listed in the Content Section below.

3. Content:

3.1 COVER PAGE

The cover page for an OPSEC Plan shall clearly present, at a minimum, the following information:

1. Title of the Acquisition Program

2. Title of the Document (i.e. “Operations Security Plan”)

3. Reference to the government contract number

4. Date of latest revision

5. Name, signature and title of the preparer of the OPSEC Plan

6. Name, signature and title of the approver of the OPSEC Plan.

7. Reference for whom the document was prepared (Contracting activity)

8. Reference by whom the document was prepared (Corporation)

9. All appropriate distribution or classification statements

3.2 TABLE OF CONTENTS PAGE

The Table of Contents for an OPSEC Plan shall outline each section contained in the OPSEC Plan.

3.3 PREFACE PAGE

The purpose of the Preface is to provide a brief, unclassified, overview of the program and the need for OPSEC measures. The specific objectives of the contracted effort shall be introduced with reference to all strategic participants and partnerships required to make the program a success. The anticipated development of any innovative concepts or technologies shall also be introduced in the Preface.

The Preface shall reference all links between the OPSEC Plan and any corporate OPSEC Program(s). The Preface may conclude by referencing requirement documents such as the contract number, Contract Security Classification Specification (DD254), Contract Data

Requirements List (DD1423) and any other pertinent guidance provided by the contracting activity. It shall also provide an OPSEC point of contact, with contact information, for additional guidance or assistance such as the OPSEC program manager or contractor program manager.

3.4 OPSEC PLAN INTRODUCTION

3.4.1 Purpose and Scope: The purpose of the OPSEC Plan shall be effectively communicated in this section and include a description of the scope of the OPSEC Plan (unique physical locations, subcontractors, suppliers, period of performance, etc.).

3.4.2 Authorities: The requirement to protect critical information shall be documented within this section. Documenting the requirement can be achieved by referencing the Corporate OPSEC Program (Policy) and Plan, DODM 5205.-2M, specific contract documents including the DD254 for contracts involving classified data, or other contracting activity specific guidance.

3.4.3 OPSEC Plan Major Activity Timeline: This section shall include a list of all major OPSEC Plan activities such as quarterly OPSEC Working Group Meetings, Annual Assessments, scheduled OPSEC awareness training, Sub-contractor OPSEC Assessments and Surveys, Threat and Vulnerability Reviews, etc. This section shall also include scheduled OPSEC Plan reviews.

3.4.4 Responsibilities: The OPSEC Plan shall identify whom is responsible for the major activities described in the Plan. For example (not intended as an inclusive list):

The OPSEC Manager shall be identified by name and include a list of duties that may include:

1. Coordinate all OPSEC policy responsibilities/ procedures within the program.

2. Revise the Program OPSEC Plan as necessary.

3. Convene and coordinate the annual Program OPSEC Assessment.

4. Disseminate updated threat information to program personnel.

5. Assist in the review of contract requirements for OPSEC considerations.

6. Conduct OPSEC briefing(s) upon customer approval of the plan.

7. Principal advisor to the Contractor Program Manager on all OPSEC matters.

8. Develop/Disseminate Program Critical Information List (CIL).

9. Promote OPSEC awareness within the program.

The Contractor Program Manager shall be identified by name and include a list of duties that may include:

1. Responsible for the overall implementation of the program/contract.

2. Ensure proper OPSEC procedures are implemented by program personnel.

3. Ensure all subcontractors and suppliers supporting the program develop and implement procedures in compliance with the Program OPSEC Plan.

4. Remain cognizant of emerging OPSEC threats and vulnerabilities that may adversely impact upon the success of the program.

5. Actively participate in periodic Program OPSEC assessments.

6. Remain cognizant of any changes in critical information and communicate them to the Program OPSEC Manager.

7. Promote OPSEC awareness within the program.

A short description of the expectations and responsibilities of all program personnel (including subcontractors and suppliers) shall be provided and may typically include:

1. Remain compliant with all applicable OPSEC Plans.

2. Maintain an awareness of all applicable CIL.

3. Attend all OPSEC program briefings.

4. Timely reporting of any OPSEC concerns to the Contractor Program Manager and/or the Program OPSEC Manager.

5. Generation of OPSEC Plans (sub-contractors or suppliers only).

3.4.5 Organizational OPSEC Communications and Interfaces: A description as to how the OPSEC Plan will be communicated to all personnel supporting the program (hardcopy, via a webpage, briefings, etc.).

3.4.5.1 Internal: In this section the OPSEC Plan shall identify all anticipated OPSEC interfaces internal to the corporation such as the senior corporate leadership, corporate OPSEC Working Group, OPSEC coordinators, program personnel, etc.

3.4.5.2 External: In this section the OPSEC Plan shall identify all anticipated external points of contact such as the contracting activity, Defense Contract Management Agency (DCMA), The Defense Security Service (DSS), Federal Bureau of Investigation (FBI) and local law enforcement and their primary role within the OPSEC program (i.e. DCMA audits acquisition management practices, DSS provides security oversight, FBI and law enforcement may provide threat data). Subcontractor and supplier OPSEC points of contact shall be similarly identified.

3.4.6 Marking, Handling and Distribution of Documents: This section shall provide a description of marking, handling, storage, access and transmission authorizations and procedures for any critical information provided to, or generated by, the contractor.

Reference to the program classification guide, Freedom of Information Act and any additional guidance provided by the contracting activity may be cited as applicable.

3.5 THREAT

3.5.1 General Threat: This section shall identify and demonstrate an understanding of the overall threat to program critical information throughout the anticipated duration of the contract/program. For example, an information systems program might note the following:

DSS analysis of 2008 threat data shows, “Information systems, especially C4ISR related systems remained the primary sought-after technology for East Asia and Pacific Region countries. Direct requests (often via the Internet) and other suspicious Internet activity continued to be the preferred method of collection. Information systems are primary targets for Near East adversaries of the United States. Near East commercial entity activity indicates a growing collusion between commercial entities and government associated entities such as universities, public agencies and research and development centers. Adversaries using HUMINT and OSINT collection methods represent a significant threat to program critical information. i

The section shall conclude with a brief description of all identified intelligence collection methods that may be expected to be used by an adversary to acquire critical information.

Note: A general description of intelligence collection methods may be found in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov.

3.5.2 Program Detailed Threat: This section shall be similar to section 3.5.1 above referencing any known direct threats to acquisition specific elements of critical information within the program/contract. As complete a description of each threat as possible shall be provided while maintaining the overall plan classification at the unclassified level. Since detailed threat information may derive from classified sources, reference to source documents as provided by the government contracting activity or other reputable source is permitted.

3.5.3 Threat Analysis: Each threat identified in sections 3.5.1 and 3.5.2 shall be analyzed to determine the level of threat to the corresponding critical information. The results of this analysis shall be presented in this section. A description of the specific threat analysis method used by the contractor to quantify each threat shall be included in this section.

Note: For additional guidance and a sample threat analysis methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.02.

3.5.4 Changes Within Threat Environment: The Threat section shall conclude with a statement that addresses how new threat data is to be received and incorporated into the OPSEC Plan to ensure OPSEC risk remains in compliance with all applicable guidance.

3.6 CRITICAL INFORMATION

3.6.1 General: Critical information shall be identified within this section of the plan and a comprehensive program Critical Information List (CIL) shall be included.

3.6.2 Critical Information List: Guidance on the creation of a CIL is contained within “Applying OPSEC to Government Acquisitions and Contracts,” available at www.ioss.gov, DODM 5205.02M, or may be provided by the contracting activity. Ideally the CIL shall remain unclassified to facilitate wide internal distribution, but may provide reference to classified information as applicable.

http://www.ioss.gov/

3.7 VULNERABILITY

3.7.1 General: The Vulnerability section of the OPSEC Plan shall describe the analysis of activities (indicators) that point to OPSEC vulnerabilities an adversary can exploit to acquire critical information. This section shall contain a list of all identified OPSEC vulnerabilities.

3.7.2 List of OPSEC Vulnerabilities: Each vulnerability shall be described in sufficient detail as to communicate to the contracting activity the extent of the vulnerability. The Vulnerability List shall remain unclassified, but may provide reference to classified information if applicable. Reference to classified reports and other information shall include an unclassified description of the documentation (report title, number, etc.) and the source responsible for publication of the information.

Note: A list of typical OPSEC vulnerabilities which may require OPSEC measures may be found within “Applying OPSEC to Government Acquisitions and Contracts”, available at www.ioss.gov or may be provided by the contracting activity. These sample vulnerabilities are not all inclusive and the submitted vulnerability list shall be tailored to the specific acquisition or contract.

3.7.3 Vulnerability Analysis: Once potential program vulnerabilities have been identified, the magnitude of each vulnerability shall be determined using a consistent methodology identified and documented in this section of the OPSEC Plan. The results of this analysis shall also be described in this section.

Note: For additional guidance and a sample vulnerability methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.0-2M.

3.8 RISK ASSESSMENT

3.8.1 General: The OPSEC risk of a program represents the probability of compromise of critical information and the impact to the program/contract taking into account the threat and vulnerabilities. The acceptable level of OPSEC risk (as determined by senior leadership, or the contracting activity) shall be described in this section in terms consistent with the selected OPSEC methodology.

3.8.2 Risk Assessment: The specific OPSEC risk shall be described in terms consistent with the OPSEC methodology selected for determining OPSEC threat and vulnerability.

The method, and the results of the assessment, shall be presented in this section. The conclusion of the risk assessment shall result in an ordinal ranking of OPSEC risk (highest to lowest).

Note: Additional guidance and a sample risk methodology are available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.0-2M.

3.9 OPSEC MEASURES

3.9.1 General: This section of the OPSEC Plan shall identify specific OPSEC

Source: https://assist.dla.mil -- Downloaded: 2014-07-02T18:58Z Check the source to verify that this is the current version before use.

http://www.ioss.gov/

Measures proposed for mitigating OPSEC risk to acceptable levels including the cost to implement each measure. A sampling of common OPSEC measures is available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov . This list is not to be considered exhaustive and is provided as guidance for the development of the program/contract specific list of potential OPSEC measures.

3.9.2 Residual Risk: This section shall contain an analysis of residual OPSEC risk, in terms consistent with the OPSEC methodology selected, as a result of implementation of each OPSEC measure presented in section 3.9.1. This section shall identify which OPSEC measures will be implemented and the rationale for those that will not.

3.10 OPSEC Program Chronology: This section shall document significant program OSPEC events throughout the lifecycle of the program. Significant events may include changes to the CIL, changes in program leadership or results of program assessments and surveys (including subcontractors). At a minimum, this section shall include a brief description of the event, date of occurrence, actions taken by the contractor and final disposition. A known compromise of critical information need only be referenced in keeping with the intended classification of this document.

Note: The history contained herein may be used by the government as a part of an OPSEC or security audit conducted by the contracting activity, DSS or other authorized agency.

3.11 ACRONYMS: This section shall include a complete list of acronyms used in the Program OPSEC Plan (i.e., CDRL – Contract Data Requirements List, DID – Data Item Description, etc.).

3.12 REFERENCES: This section shall include a complete list of all references cited in the Program OPSEC Plan (i.e. DoD Manual 5205.02-M, dated November 3, 2008, Contract Number, Corporate OPSEC Plan(s)/Program(s), etc.).

i The specific example provided derives from annual documentation produced by the Defense Security Service, Counterintelligence Office in 2009. Current assessments may be found at https://www.dss.mil/isp/count_intell/count_intell.html.

4. END OF DI-MGMT-80934C.

Source: https://assist.dla.mil -- Downloaded: 2014-06-22T15:01Z

Title: Integrated Defense Plan (IDP)

Number: OT-2014-30014 Approval Date: 20140310

AMSC Number: N/A Limitation: FA9101-14-R-0200

DTIC Applicable: No GIDEP Applicable: No

Office of Primary Responsibility: AEDC/TSD

Applicable Forms: None

Use/relationship: The Integrated Defense Plan (IDP) codifies installation defense efforts among responsible internal/external agencies to ensure all aspects of Integrated Defense (ID) are accomplished, considered and compensated for, if necessary. It also provides an understanding of security requirements for all units involved in ID and describes how commanders employ available

ID forces, capabilities and concepts to accomplish the overall ID mission. The IDP consolidates all

ID actions into one plan (i.e., those actions identified in the former Installation Security Instruction

(ISI) and Installation Security Plan (ISP). Installation Commanders issue and approve the IDP and its subsequent implementation actions.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents: AFI 31-101 and AFI 10-401

2. Format. The IDP shall be written in the standard five-paragraph operations order format using the guidance in AFI 10-401, Air Force Operations Planning and Execution, and Attachment 5 to

AFI 31-101. Write each part of the plan assigning tasks to organizations so the tasks and responsibilities become explicit and concise orders for commanders. Include introductory statements in the plan summary explaining the purpose of the plan and its intended use. The

Installation Commander or designee signs a letter of transmittal when the plan is complete and ready for publication. Units tasked in the plan will ensure their personnel are capable of meeting the tasking. Tasked units normally accomplish this through publication of unit instructions and exercises. The IDP will be a limited release document and contain the installation The Integrated

Defense Risk Management Process (IDRMP). Installations should consult their MAJCOM‘s security classification guide to determine the level of security for the completed plan. Note: If topics from mutually supporting plans overlap (e.g., Anti-Terrorism Plan or Comprehensive

Emergency Management Plan 10-2), the IDP may reference applicable appendices or annexes from other plans to streamline planning efforts.

3. Content. The IDP shall contain the following:

OT-30014

3.1. As a minimum, the IDP will include: The Integrated Defense Risk Management Process.

The IDRMP in Chapter 3 of AFI 31-101 is the foundation upon which risk acceptance is determined and the IDP is developed.

3.2. For each asset with a Protection Level designation (whether on the installation or a dispersed site/GSU supported by the installation)

4. End of OT-30014.

Title: Blood Borne Pathogens Exposure Control Plan

Number: OT-2014-30042 Approval Date: 0410204 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/TSD Applicable Forms: None

Use/relationship: The plan outlines the mandatory requirements for all security guards with the potential for exposure to Blood Borne Pathogens (BPP) during the performance of their assigned duties.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents: AFI 31-118 Security Forces Standards and Procedures, Attachment 5, Figure A5.1.

2. Format: The plan shall be in the Contractor’s format. (Review plan annually and update as necessary to reflect new or modified exposure determinations. Coordinate with local medical liaison to ensure relevancy and accuracy.)

3. Content: The plan shall contain the following as a minimum and be made readily available to all security guards:

3.1. The exposure determination of personnel (those reasonably anticipated, as a result of performing their day-to-day duties, to have potential skin, eye, mucous membrane contact with blood or other potentially infectious fluids or materials). This determination includes:

3.1.1. A list of all duty positions in which personnel in those positions are likely to be exposed to contaminated material.

3.1.2. A list of all tasks and procedures, or groups of closely-related tasks and procedures, in which exposure may occur; tasks and procedures will be performed by personnel who handle contaminated material.

3.1.3. The methods available to prevent contact with blood and other potentially infectious fluids or materials.

3.1.4. Procedures for those who reasonably believe they have contacted a potentially infectious fluid or material.

OT-2014-30042

3.1.5. Procedures for placing warning labels on containers or plastic bags containing blood or other potentially infectious material. Labels must comply with Occupational Safety and Health Agency (OSHA) Standard 1910.1030.

3.1.6. Procedures for keeping records of all incidents and occupational exposures per OSHA

Standard 1910.1030.

3.1.7. Procedures for evaluating circumstances surrounding exposure incidents.

4. End of OT-2014-30042

Title: DAILY EVENTS LOG

Number: OT-2014-30061 Approval Date: 20140619

DTIC Applicable: No GIDEP Applicable: No

Use/relationship: This data item description is used to provide the Government with information about Operations, Maintenance, Information Management, and Support of the Arnold

Engineering Development Center.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for

1. Reference documents: None

2. Format: The Contractor’s electronic format is acceptable.

3. Content: The log shall contain the following for each event recorded: Date / time, author, and a summary of the event. The log documents all activities / events reported to AEDC

Operations Center. The following activities are required to be reported to the Operations

Center:

a. Test starts/stops (outages, major maintenance and investment projects).

b. Significant accomplishments/milestones related to test, maintenance, test support and/or completions of these activities.

c. Any unscheduled event which stops or delays testing (scheduled activities) for ½ hour or more.

d. Foreign Object (FO)/Foreign Object Damage (FOD) discovered.

e. Daily status updates including resume-morning reports for test activities and verbals/emails on other maintenance/investment activities.

f. Utility requirements (power, water, high pressure air, fuel, steam, etc.) – weekly forecast and actual within 24 hours of intended use.

g. Hazardous substance spills of all sizes and nature.

h. Any event requiring a decision to proceed with or terminate scheduled activities.

i. Any scheduled activity changes that occur within current and next day’s schedule.

4. End of OT-2014-30061

Title: DAILY MORNING REPORT

Number: OT-2014-30062 Approval Date: 20140619

DTIC Applicable: No GIDEP Applicable: No about Test, Operations, and Maintenance information for previous days testing activities/events.

3. Content: The report shall contain the following:

3.1. Operations

a. Previous Days Test

i. Flight Systems

ii. Space & Missile Systems

iii. Aeropropulsion Systems

b. Forecasted Test Schedule

3.2. Daily Utility Requirements

c. Power Forecast

d. Natural Gas Forecast

3.3. Safety/Environmental

e. Incidents/Injuries

f. Foreign Object Damage

g. Spills

h. Miscellaneous

3.4. Weather

i. Today

j. Tonight

k. Tomorrow

OT-2014-30062

3.5. Maintenance Items

l. Flight Systems

m. Space & Missile Systems

n. Aeropropulsion Systems

o. Utilities

3.6. Long Term Issues

p. Test

q. Investments

r. Maintenance

3.7. Other Items of Interest

4. End of OT-2014-30062

Title: OPERATIONS CENTER TRAINING PLAN

Number: OT-2014-30063 Approval Date: 20140619

DTIC Applicable: No GIDEP Applicable: No about the locally developed Training Plan for the Operation Center Training and Operational

Reporting

1. Reference documents: AFI 10-207 Exception to Policy Memo

3. Content: The plan shall contain the following:

a. Training Standard

b. Initial Qualification Training

c. Recurring Training

i. Quarterly Evaluations

ii. Self-Study

d. Frequency of Training

e. Performance Standards

4. End of OT-2014-30063

Title: OPERATIONAL REPORTS

Number: OT-2014-30064 Approval Date: 20140619

DTIC Applicable: No GIDEP Applicable: No about Operational Reporting that is to be accomplished by AEDC Operations Center that is deemed reportable according to the AFI and Supplements.

1. Reference documents: AFI 10-206, Operational Reports, and AFMC Supplement to AFI 10-

206.

2. Format: The reports shall be IAW AFI 10-206 and AFMC Supplement to AFI 10-206.

3. Content: The following types of reports will be submitted when deemed reportable by the

Operations Center through the AEDC Commander:

a. Operational Reports (OPREPs)

i. Pinnacles

ii. Beeline

b. Commander’s Critical Information Reports (CCIRs)

c. Situation Reports (SITREPS)

4. End of OT-2014-30064

Title: QUICK REACTION CHECKLIST (QRC) NOTIFICATIONS

Number: OT-2014-30065 Approval Date: 20140619

DTIC Applicable: No GIDEP Applicable: No about activities/events/accidents/incidents/and etc. occurring on/off base that are affiliated with the base, personnel, equipment, and etc.

3. Content: The report shall contain the following:

a. Time of activities/events

b. Summary of the activities/events

4. End of OT-2014-30065

Title: Test Security Plan for Collateral Classified and Commercial Test

Number: OT-2014-30067 Approval Date: 20140703 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/TSD-IP Applicable Forms: None

Use/relationship: A test security plan will be prepared for all commercial, unclassified, and collateral classified research, development, test and evaluation (RDT&E) test programs conducted at AEDC. This plan will be used by the test team and identifies all security requirements related to specific test efforts. The test security plan provides all employees supporting a test with test-specific security guidance and procedures. If necessary, it also contains a Foreign National Visitor Control Plan as an annex. This Plan does not apply to SCI or Special Access Required (SAR) test programs.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents. Reference documents are contained in the Performance Work

Statement, The DD 254, Contract Security Specifications, and specific Security Classification Guides (SCG).

2. Format. The test security plan shall be prepared in electronic form and available to authorized users via electronic and hardcopy forms. The format shall comply with reference documents.

3. Content. As a minimum, the plan shall:

a. Identify the test program and provide an overview of the test

b. Identify the customer/sponsor and test facility

c. Identify classification, specific guidance, related SCGs, and any Technical Assistance Agreements, Technology Control Plans

d. Identify Baseline Protection Requirements for Data and the test areas (Physical Space)

e. Identify the Risk Assessment Authorization (RAA), if required:

i. Identify any foreign national involvement and subsequent visitor control procedures

OT-2014-30067

ii. Identify any CUI and specific guidance

iii. Identify any OPSEC concerns and provides and specific measures and/or guidance

iv. Identify any Critical Program Information (CPI) and specific Program Protection Plan requirements or guidance

f. Provide data marking guidance, including distribution limitations, export control, and/or any dissemination markings to be included with classification marking

g. Provide all physical security and AIS requirements and a checklist on how to implement them; including detailed diagrams or drawings

h. Provide standard requirements for each test program (test photography, etc.).

i. Identify other Test, Industrial, Information, Personnel or Physical Security requirements

j. Provide a list of definitions

k. Contain signature approval blocks for the Government Project Manager, Information Systems Security Officer, FSS Facility Security Officer and Servicing Security Activity (TSD-IP).

4. End of OT-2014-30067

Title: STANDARD PRACTICE PROCEDURES (SPP)

Number: OT-2014-30069 Approval Date: 20140725 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/TSD-IP Applicable Forms: None

Use/relationship: This data item description is used to ensure effective implementation of the requirements of DOD 5220.22-M, National Industrial Security Operating Manual (NISPOM).

The SPP will contain specific guidance for the Contractor's operations and involvement with classified information at the Contractor's facility/areas located at AEDC. The Contractor shall implement all applicable terms of the NISPOM at each of its established areas.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents. Reference documents are contained in the NISPOM., The

Performance Work Statement, The DD 254, Contract Security Specifications, and specific Security Classification Guides (SCG).

2. Format. The Contractor’s electronic format is acceptable. The SPP shall be available to authorized users via electronic and hardcopy forms

3. Content. The SPP content shall comply with all reference documents including DoD

5220.22-M, be consistent with the required level of detail, consistent with task delineation, and address all security requirements IAW government direction and applicable standards.

The SPP shall contain signature approval blocks for all FSS “Key Management Personnel” and Servicing Security Activity (TSD-IP).

4. End of OT-2014-30069.

Title: RF RADIATION EMITTER AND LASER INVENTORY

Number: OT-2014-30070 Approval Date: 20140725 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/TSD Applicable Forms: None

Use/relationship: This inventory shall provide information on all radio frequency emitters and lasers used on the installation.

This DID contains the format, content, and intended use information for the data product

1. Reference documents. None.

2. Format. The Contractor’s electronic format is acceptable.

3. Content. The inventory shall contain specific information on each radio frequency radiation emitter and laser device on the installation. Information will include title or name of the device, location, serial number, property number, responsible individual, operational characteristics such as operating range or output power, and any necessary precautions relating to use or personnel exposure.

4. End of OT-2014-30070.

Title: Information Protection Standard Operating Procedures

Number: OT-2014-30071 Approval Date: 20140725 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/TSD-IP Applicable Forms: None

Use/relationship: A written Standard Operating Instruction/Procedure (SOI/SOP) provides instructions and guidance to ensure compliance with requirements contained in applicable NISPOM, Air Force, program, and other cognizant security agency directives for “Closed and Restricted” and Commercial Test Areas. The security SOI/SOP is a living document that will require periodic updates throughout the life of the area.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents: Reference documents are contained in the Performance Work

Statement, The DD 254, Contract Security Specifications, and specific Security Classification Guides (SCG).

3. Content: The security SOI/SOP content shall:

a) Comply with all reference documents

b) Be consistent with the required level of detail, consistent with task delineation

c) Address all security requirements IAW government direction and applicable standards

d) Include Entry/Exit Control procedures for use by owner/users or area custodians of controlled areas established for classified operations

e) Include procedures for Installation Random Antiterrorism Measures (IRAMs) and entry and exit checks

f) Contain Signature Approval Blocks for the FSS Facility Security Officer and Servicing

Security Activity (TSD-IP)

4. End of OT-2014-30071.

Title: INDUSTRIAL HYGIENE SURVEY REPORT

Number: OT-2014-30072 Approval Date: 20140728 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/TSD Applicable Forms: None

Use/relationship: The industrial hygiene survey report describes conditions in the workplace, health hazards present, and the impact of those hazards on the workers.

This DID contains the format, content, and intended use information for the data product

2. Format. The Contractor’s electronic format is acceptable.

3. Content. The report shall contain the following:

a. Title. The title shall identify the subject of the report, the workplace surveyed, the date of the survey, and the organization to which the workplace supervisor reports.

b. References. List source materials used in preparing the report.

c. Key Person. The person conducting the survey.

d. Operations Summary. A summary of the operations performed in the surveyed area.

Include duties, operations performed, and sources of health hazard exposures.

e. Exposure Summary. Specify hazards and data collected to indicate levels of worker exposure.

f. Training Requirements. Identify worker training requirements for this workplace based on potential health hazard exposure

g. Survey Findings. Address the following areas and include measurements and determinations as they relate to worker exposure: noise, ventilation, atmospheric contaminants, blood-borne pathogens, hazardous material exposure, indoor air quality, hazardous waste, hazard communication, heat, humidity, cold stress, oxygen deficient atmospheres, radiation hazards, laser sources, ergonomics, confined space, respiration protection, and personal protective equipment available.

h. Data Summary. Summary of data collected by direct or indirect instrumentation, an interpretation of the results, and conclusions on exposure history.

i. Studies Needed. Indicate whether further studies or follow-up surveys are required to completely assess worker exposure.

j. Recommendation. List recommendations that would reduce worker exposures, follow-up actions the supervisor must perform, and other items that affect occupational well-being of all personnel.

4. End of OT-2014-30072

Title: FIRE PROTECTION

Number: OT-2014-30073 Approval Date: 20140728 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/TSD Applicable Forms: AF Form 1487

Use/relationship: This data is used to document the results of the fire prevention inspections.

This DID contains the format, content, and intended use information for the data product

2. Format. The report shall be provided using AF Form 1487.

3. Content. The report shall provide the data as identified on AF Form 1487. Attach clarifying data as deemed necessary.

4. End of OT-2014-30073

Title: SAFETY INSPECTION REPORT

Number: OT-2014-30077 Approval Date: 20140728 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/SE Applicable Forms: None

Use/relationship: The Safety Inspection Report is used to document and report facility and program safety inspections. This data item description documents the results of a base safety inspection program.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

1. Reference documents: AFI 91-202, The USAF Mishap Prevention Program, Chapter 3.

2. Format: The report shall be provided in MS Word, and contain information IAW AFI 91-

202, The USAF Mishap Prevention Program, Chapter 3.

3. Content: Safety facility inspection and safety program assessment report for each workcenter within and outside the fence on AEDC property, to include GSUs, unless otherwise specified by a memorandum of understanding/agreement, occupied or operated by AEDC operating contractors and/or DoD personnel. It shall include:

a. Area inspected

b. Inspector

c. POC

d. Findings

e. ICM

f. Cause for RAC 1-3 findings

4. End of OT-2014-30077

Title: PROPERTY DAMAGE INVESTIGATION REPORT

Number: OT-2014-30078 Approval Date: 20140728 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/SE Applicable Forms: None

Use/relationship: This data item description documents the results of quality and timely Class D and E property mishap investigations. This DID shall contain mishap investigations, reports, briefs and tracking recommendations until closed.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

2. Format: The Contractor’s electronic format is acceptable as defined in the Content section below.

3. Content: Mishap Investigation reporting shall be provided as defined below:

a. Applicable Class D and E property damage mishap investigations and reports completed and delivered in MS Word format to AEDC/SE within 25 days of mishap.

b. Brief applicable Class D and E property damage mishaps to leadership using MS PowerPoint, upon request.

c. Provide tracking of property damage mishap recommendations using Excel/Access/Word until closed. Provide monthly updates to AEDC/SE.

4. End of OT-2014-30078

Title: INJURY AND PROPERTY DAMAGE CHARTS

Number: OT-2014-30079 Approval Date: 20140728 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/SE Applicable Forms: None

Use/relationship: This data item description documents the results of an effective mishap prevention program. This DID shall require quarterly Total Recordable Incident Rate (TRIR) and Days Away Restricted Transfer (DART) rates for injuries and property damage numbers.

This DID contain the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents: None.

2. Format: Electronic version using MS PowerPoint.

3. Content: Injury and Property Damage charts shall be provided as defined below:

a. Quarterly DART and TRIR mishap rates on a chart with summaries reflecting back to beginning of contract in backup.

b. Quarterly Class A/B/C/D&E property damage numbers on a chart(s) with summaries reflecting back to beginning of contract in backup.

c. Quarterly injury and property damage trend analysis.

4. End of OT-2014-30079

Title: HAZARD ABATEMENT PLAN

Number: OT-2014-30080 Approval Date: 20140728 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/SE Applicable Forms: AF Form 3

Use/relationship: This data item description documents the base hazard abatement program used to document, track, prioritize and help advocate for funds to abate these hazards. This DID shall contain the Base Master Hazard Abatement Plans for RACs 1-3, Abatement Plans for RACs 4 and 5, End of Year Summary and Semi-Annual Reviews using the AF Form 3. This includes all hazard information across the base and all operating contracts.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents: Chapter 12 in AFI 91-202, The US Air Force Mishap Prevention

Program

3. Content: The Hazard Abatement Program shall be provided as defined below:

a. Master Hazard Abatement Plan for RACs 1-3

b. Abatement Plans for RACs 4 and 5

c. End of Year Summary in accordance with AFI 91-202

d. Semi-Annual Reviews using the AF Form 3 in accordance with AFI 91-202

4. End of OT-2014-30080

Title: AEDC SHE STANDARDS

Number: OT-2014-30081 Approval Date: 20140728 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/SE Applicable Forms: None

Use/relationship: The AEDC Safety, Health, and Environmental (SHE) Standards are used to define safety, health, and environmental policy. This data item description documents the requirements of periodic reviews and implementation of the AEDC SHE Standards.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents: AEDCI 91-5, Instructions Compliance

2. Format: The Contractor’s electronic format IAW AEDCI 91-5, Instructions Compliance.

3. Content: Each AEDC SHE Standard shall be written IAW AEDCI 91-5, Instructions

Compliance, and shall include:

a. Introduction/Scope/Applicability

b. Basic Hazards/Human Factors

c. Definitions

d. Requirements/Responsibilities

e. Training

f. Inspection/Audits

g. References

h. Annex(es)

i. Supplement(s)

j. Applicable charts, tables, checklists, or forms relating to the topic of the specific standard

4. End of OT-2014-30081

Title: SPOT SAFETY INSPECTIONS

Number: OT-2014-30082 Approval Date: 20140812 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: AEDC/SE Applicable Forms: None

Use/relationship: This data item description documents the results of a spot inspection program used to gauge the effectiveness of the base safety program.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference documents. AFI 91-202, The USAF Mishap Prevention Program, Chapter 3.

2. Format. The report shall be provided in MS Word, and contain information IAW AFI 91-

202, The USAF Mishap Prevention Program, Chapter 3.

3. Content. Conduct, record, track, and trend a minimum of 100 spot inspections each six month period, with 10% outside normal duty hours. Conduct a minimum of 20 high interest spot inspections each six month period. (High interest areas are areas that contain greatest risk to life and property. The list of high interest areas may change periodically due to perceived risk, as determined by FSS Safety). Each report shall include:

a. Area inspected

b. Inspector

c. POC

d. Findings

e. ICM

f. Cause for RAC 1-3 findings

4. End of OT-2014-30082

Title: HAZARDOUS WASTE MANAGEMENT PLAN

Number: OT-2014-30083 Approval Date: 20140812 AMSC Number: N/A Limitation: FA9101-14-R-0200 DTIC Applicable: No GIDEP Applicable: No

Use/relationship: This data item description is used to provide guidance on proper procedure for management of hazardous waste (HW), reflecting Air Force, DoD, and regulatory requirements, installation HW activities, incorporating pollution prevention practices and waste minimization into HW management activities.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract PWS. This DID is for one-time use for AEDC solicitation FA9101-14-R-0200 Facility Support Services.

Requirements:

1. Reference Documents. AFI 32-7042, Waste Management, and AFPAM 32-7043, Hazardous Waste Management Guide.

3. Content. The content shall comply with the requirements for a Hazardous Waste

Management Plan in AFI 32-7042, AFMC Supplement 1 to AFI 32-7042, and AFPAM 32-7043, and shall include the elements listed on the example Table of Contents from the current edition of the AEDC Hazardous Waste Management Plan located on pages 2-4 of this DID.

OT-2014-30083

TABLE OF CONTENTS

1.0 INTRODUCTION AND…