N63394-23-R-0022_Exhibit A - DIDs_3_13_23.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

DATA ITEM DESCRIPTION

Title: CONTRACTOR HAZARDOUS MATERIAL INVENTORY REPORT

Number: DI-ENVR-82091 Approval Date: 20161208

AMSC Number: N9751 Limitation: N /A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: SH Project Number: ENVR-2017-001

Applicable Forms: PSNS&IMF form 5090/132

Use/Relationship: Contractor Hazardous Material Inventory Report will be used to identify hazardous materials needing for approval by the government for use on the Naval Installation.

This DID contains the format and content preparation instructions for the data product generated by the discrete task requirement as delineated in the contract.

Requirements:

1. Format. The Hazardous Material Inventory Report shall be presented on PSNS&IMF form

5090/132 in this DID.

2. Content. The report shall contain all of the information specified in PSNS&IMF 5090/132.

End of DI-ENVR-82091

Source: https://assist.dla.mil -- Downloaded: 2022-05-31T22:28Z Check the source to verify that this is the current version before use.

DI-ENVR-82091

CONTRACTOR HAZARDOUS MATERIAL INVENTORY (CHMI)

Ref: NAVSEA Standard Items 009-97 and 009-02 NWRMC Local Standard Item 099-04NW

Document No.

CONTRACTOR – INITIAL REQUEST1 (Before moving any hazmat onto this Federal facility) **Refer to instructions on last page**

PRIME CONTRACTOR (KTR) (POC) SUB-CONTRACTOR (If Applicable) PRIME KTR CERTIFICATION SIGNATURE (sign or submit electronically) Print & sign

PHONE

Mr KTR NA Signature on File 555-232-2222

CONTRACT NUMBER PROJECT NAME2 WORKSITE LOCATION3 PROJECT EXECUTION START

DATE

PROJECTED

END5

N4523A-12-D-0003 USS Michigan Dry Dock 2 12/14/2015 04/03/2016

ENVIRONMENTAL, SAFETY, AND HEALTH (ESH) GOVERNMENT REPRESENTATIVE

CONTRACT OFFICE AGENCY (i.e., C/400, AIT)

ESH GOVERNMENT REPRESENTATIVE NAME PHONE FAX SUBMITTAL

DATE C/400/106.2 ESH SBS 360-535-2222

CODE 106.31 HAZARDOUS MATERIAL PROCESS MANAGEMENT BRANCH

106.31 NAME & INITIALS RECEIPT DATE REVIEW DATE

Trade Name6

Name on product & MSDS must match

For kits, list kit name, then list kit components individually

Manufacturer7

Name on product & MSDS must match

Process Code Number8

Use provided flow chart

Container Size & Type9

Enter size

SHIPYARD MSDS

Number10 (As assigned by Code 106.31)

SHIPYARD Assigned Stock Number (Assigned by Code 106.31)

Speclt SSPR 6PK Marking Fluorescent Green Spray Paint, #1989830

Rust-Oleum Corp. ID0507 11 oz AER See Attached SDS

CONTRACTOR HAZARDOUS MATERIAL INVENTORY (CHMI) CODE 106.31 Document No. Page 2 of 2

CONTRACTOR – INITIAL REQUEST (Before moving any hazmat onto this Federal facility)

Trade Name6

Name on product & MSDS must match

For kits, list kit name, then list kit components individually

Manufacturer7

Name on product & MSDS must match

Process Code Number8

Use provided flow chart

Container Size & Type9

Enter size

SHIPYARD MSDS Number10 (As assigned by Code 106.31)

SHIPYARD Assigned Stock

( assigned by Code 106.31)

PSNS & IMF 5090/132 (Rev. 04-13)

INSTRUCTIONS

Contractor: Fill out each section under the heading “CONTRACTOR” per the following instructions and footnotes. List all hazardous material (HM) that you, as the contractor, anticipate transporting from offsite onto the Federal property located at the Bremerton Naval Complex (BNC). Do not list HM obtained inside the BNC that has been labeled with the facility’s salmon colored supplemental barcode label. Use as many additional sheets as necessary to include all HM that you anticipate transporting onsite. Provide the most current MSDS for each product listed in the CHMI. If you are using a “Non-Road” engine do not forget to submit an O&M plan to Code 106.31 Air Department. For all marine coatings, provide a Volatile Organic Compound (VOC) certification sheet for each batch. If you have a Marine Coating that is

General Use and the VOC’s are above 340g/l you must submit separate paperwork to Code 106.31 Air department. All HM must be approved by the Code 106.31 before bringing material onsite. Low Use

Exempt materials may also be processed on this form. Upon completion of all Contractors required items submit the completed CHMI form to your Government Environmental, Safety, and Health representative.

* Prime Contractor Certification Statement: I hereby certify that the submitted information contained in the attached document(s) is true, complete and accurate, and all material listed has been approved by

Code 106.31.

Designated Government Environmental, Safety, and Health Representative: Complete Designated Government ESH section. Submit completed CHMI to Code 106.31 for review and approval.

FOOTNOTES

This is for the initial request. Use the Receipt & Monthly Usage Form to report monthly HM usage by the 5 th calendar day of the following month. Negative usage reports are required. If no usage, enter 0 in applicable field or leave blank and submit report.

Identify Project (e.g. – ship hull number or name, etc).

Identify Worksite Location (e.g. – Hull number, bldg. 431 5th floor, Dry

Dock 2, Pier D, etc).

The date that the contractor is to start work on the project.

The planned (best estimation) completion date for work on the project.

Provide a separate line for each product and/or container size that will be used. When reporting kits, list each component on separate lines. If part numbers are included in the Trade Name block, it will be helpful in processing the CHMI faster.

Reference example below.

Trade Name Manuf acturer

Container

Size & Type

MSDS

Stock

Buff Base Part

A PPG 0.8 gal CN

Converter Part

B PPG 0.2 gal CN

Welding electrodes 7018 ESAB 10lb

Table 1 – Container Type

Descripti on

Aeros ol Can

Ba g

Bottle Bo x

Cartri dge

Can Contain er

Cylind er

Drum

Code AER BG BT B

X

CA CN CO CY DR

Descripti on

Each Jar Package Ki t

Rod Spool Tank Tube

Code EA JR PG K

T

RD SP TK TU

Manufacturer, product name on container and company name must all match.

To determine the proper Process Code Number use the attached Hazardous Material Process Code Selection Flow Chart.

Report container size(s) in quantifiable units (e.g., weight or volume) such as a 3 lb. jar or a 16 fl oz bottle. For compressed gas cylinders, report the quantity of gas in cubic feet or units such as pounds (e.g., 150 cu-ft or 100 lb cylinder). For bulk material (e.g., diesel fuel) or material without a specific container size (e.g., welding rod or wire), use the units in which the material is commonly sold to consumers (e.g., use gallon for diesel fuel or pound for welding rod or wire). For kits, list both the kit size and each individual component size. Reference Footnote 6 for reporting kits. See Table 1 for the applicable container type. Enter container type code.

Provide the Shipyard approved Material Safety Data Sheet (MSDS) number (if known) or include a MSDS for each product (Code

400 projects only). Sending a Technical Data Sheet with the MSDS will be helpful in processing the CHMI faster. When sending an MSDS ensure that it is no older than 5 years old, the MSDS must be a representative of the material being used.

For Usage remember you are reporting for the size requested and it is listed on the form. When reporting round up to the nearest tenth, use percentages (i.e. do not use: 3 gal of a 10 gal container, use: .3

When Reporting Partial Usage, Use Decimals to Represent the Fraction of Container Used.

EXAMPLE:

Use 0.8 to indicate 3/4 usage of a container

Do Not Enter as Lbs, Gallons, Ounces etc.

Round Up to Nearest Tenth.

Use 0.3 to indicate 1/4 usage of a container Use 0.8 to indicate 3/4 usage of a container

PSNS 5090/132 (Rev. 04-13)

Source: https://assist.dla.mil -- Downloaded: 2022-05-05T04:30Z

Source: https://assist.dla.mil -- Downloaded: 2022-05-05T04:30Z

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: 2022-04-19T19:38Z

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.

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

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.

Title: TEST AND INSPECTION PLAN (TIP)

Number: DI-MGMT-82062

AMSC Number: N9711

DTIC Applicable: No

Preparing Activity: SH

Applicable Forms: N/A

Approval Date: 20161003

Limitation: N/A

GIDEP Applicable: No

Project Number: MGMT-2016-049

Use/Relationship: This DID is used to identify all inspections and tests required by zero-tier references and first tier references, as well as symbols (I)(V)(Q) test/inspections and (G) government notification identified in the Work Item, and any additional tests and inspections the contractor deems necessary to substantiate product conformance.

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

Format. The TIP shall be in the contractor’s format.

Content. The TIP shall include the following information:

Ship’s name/hull number

Work Item number

Work Item Paragraph number

Identification of item/component to be inspected/tested

Standard Item Number

Standard Item Paragraph

Location

Sub-Contractor (if applicable)

Inspection Symbol (I, V, Q, G)

Accept/Reject Criteria

Test Result (Accept or Reject)

Notify Date

Notify Time

Request Date

Request Time

Inspection Date

Name of Person Notified

Name of Government Representative at Inspection

Name of Contractor’s authorized representative who witnessed/performed test.

End of DI-MGMT-82062

Source: https://assist.dla.mil -- Downloaded: 2022-05-05T04:37Z

Source: https://assist.dla.mil -- Downloaded: 2022-04-26T22:56Z

Source: https://assist.dla.mil -- Downloaded: 2022-06-01T00:12Z

Title: MEETING MINUTES

Number: DI-ADMN-81250C Approval Date: 20210730

AMSC Number: F10264 Limitation: N/A

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: ADMN-2021-002

Use/Relationship: Meeting minutes provide documentation of technical information provided, and decisions and agreements reached, at meetings and conferences. For the purposes of this DID, a conference is considered to be a type of meeting.

a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

b. This DID relates to DI-ADMN-81249, Meeting Agenda. (Copies of this document are available online at https://quicksearch.dla.mil.)

c. This DID supersedes DI-ADMN-81250B.

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.

2. Format. Contractor format, compatible with government applications, is acceptable.

3. Content. The meeting minutes shall include the following:

a. A title page containing the following:

(1) Meeting title, type of meeting, and meeting date(s).

(2) Identification of the system, equipment, o r contract number for which the meeting was held.

(3) Space for signatures of the designated representatives of the contractor and government activity.

(4) The name of the contractor and address to which the government activity will acknowledge receipt of comments.

b. The purpose and objective of the meeting.

c. The meeting location (or virtual conferencing application, if applicable).

d. A summary of the discussions, decisions, a n d agreements reached during the meeting or during individual subcommittee meetings.

e. A list of attendees by name, rank, grade or position, activity represented, activity symbol or code, phone number, and email address, as appropriate.

f. Action items resulting from the meeting, including, for each action item: a description, responsible party, suspense date, closure criteria, and status.

g. Briefing charts, if any were presented, shall be provided for information only.

Source: https://assist.dla.mil -- Downloaded: 2022-04-27T19:14Z

DI-ADMN-81250C

h. A list of documents reviewed during the meeting, where applicable.

3.1 Distribution Statement. The applicable Distribution Statement, as necessary, in accordance with Department of Defense Instruction (DoDI) 5230.24, Distribution Statements on Technical Documents, Enclosure 4. (Copies of this document are available online at www.esd.whs.mil/DD.)

3.2 Classification Marking. The applicable classification marking, as necessary, in accordance with Department of Defense Manual (DoDM) 5200.01, Volume 2, DoD Information Security Program: Marking of Information, or Controlled Unclassified Information (CUI) markings (when applicable) in accordance with DoDI 5200.48, Controlled Unclassified Information (CUI).

(Copies of these documents are available online at www.esd.whs.mil/DD.)

End of DI-ADMN-81250C.

Title: Repair Parts Report

Number: DI-MGMT-81868 Approval Date: 20120802 AMSC Number: N9274 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Office of Primary Responsibility: SH/NSWC Applicable Forms: N/A

Use/relationship: The Repair Parts Report will provide the Government with the information needed to monitor repairs and delivery of repaired parts.

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

Requirements:

1. Format. The Repair Parts Report shall be in the Contractor’s format.

2. Content. The Report shall contain a list of parts undergoing repair and it shall also identify the following information for each part repaired:

a. Name

b. Serial number

c. Source (where shipped from)

d. Status of repairs shall be identified as applicable:

(1) Repair Not In-Process

(2) Repair In-Process, or

(3) Repair Complete

e. Initial projected delivery date

f. Actual shipping date for the completed part

2.1 The Report shall contain a description of evaluations conducted, failure modes determined and repairs affected.

2.2 The Report shall contain cumulative cost of evaluation and repair, to reflect the total repair cost for completed repairs.

2.3 The Report shall also identify:

a. Ceiling amount for the Contract Line Item Number (CLIN).

b. Funded amount for the CLIN.

c. Contract Modification number on which the funded amount is based.

d. Cumulative expenditure amount by CLIN as of the report date.

e. Total monthly expenditure amount for that month, including labor, a list of labor categories, labor hours, and fully burdened labor rates.

Source: https://assist.dla.mil -- Downloaded: 2022-05-03T21:42Z

DI-MGMT-81868

Page 2 of 2 Pages

f. A list of the items, quantity, unit price, and total price for materials.

g. Any other expenditures being directly charged to the CLIN.

3.0 End of DI-MGMT-81868.

Title: MEETING MINUTES

Number: DI-ADMN-81250C Approval Date: 20210730

AMSC Number: F10264 Limitation: N/A

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: ADMN-2021-002

Use/Relationship: Meeting minutes provide documentation of technical information provided, and decisions and agreements reached, at meetings and conferences. For the purposes of this DID, a conference is considered to be a type of meeting.

a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

b. This DID relates to DI-ADMN-81249, Meeting Agenda. (Copies of this document are available online at https://quicksearch.dla.mil.)

c. This DID supersedes DI-ADMN-81250B.

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.

2. Format. Contractor format, compatible with government applications, is acceptable.

3. Content. The meeting minutes shall include the following:

a. A title page containing the following:

(1) Meeting title, type of meeting, and meeting date(s).

(2) Identification of the system, equipment, o r contract number for which the meeting was held.

(3) Space for signatures of the designated representatives of the contractor and government activity.

(4) The name of the contractor and address to which the government activity will acknowledge receipt of comments.

b. The purpose and objective of the meeting.

c. The meeting location (or virtual conferencing application, if applicable).

d. A summary of the discussions, decisions, a n d agreements reached during the meeting or during individual subcommittee meetings.

e. A list of attendees by name, rank, grade or position, activity represented, activity symbol or code, phone number, and email address, as appropriate.

f. Action items resulting from the meeting, including, for each action item: a description, responsible party, suspense date, closure criteria, and status.

g. Briefing charts, if any were presented, shall be provided for information only.

DI-ADMN-81250C

h. A list of documents reviewed during the meeting, where applicable.

3.1 Distribution Statement. The applicable Distribution Statement, as necessary, in accordance with Department of Defense Instruction (DoDI) 5230.24, Distribution Statements on Technical Documents, Enclosure 4. (Copies of this document are available online at www.esd.whs.mil/DD.)

3.2 Classification Marking. The applicable classification marking, as necessary, in accordance with Department of Defense Manual (DoDM) 5200.01, Volume 2, DoD Information Security Program: Marking of Information, or Controlled Unclassified Information (CUI) markings (when applicable) in accordance with DoDI 5200.48, Controlled Unclassified Information (CUI).

(Copies of these documents are available online at www.esd.whs.mil/DD.)

End of DI-ADMN-81250C.

Title: Repair Parts Report

Number: DI-MGMT-81868 Approval Date: 20120802 AMSC Number: N9274 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Office of Primary Responsibility: SH/NSWC Applicable Forms: N/A

Use/relationship: The Repair Parts Report will provide the Government with the information needed to monitor repairs and delivery of repaired parts.

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

Requirements:

1. Format. The Repair Parts Report shall be in the Contractor’s format.

2. Content. The Report shall contain a list of parts undergoing repair and it shall also identify the following information for each part repaired:

a. Name

b. Serial number

c. Source (where shipped from)

d. Status of repairs shall be identified as applicable:

(1) Repair Not In-Process

(2) Repair In-Process, or

(3) Repair Complete

e. Initial projected delivery date

f. Actual shipping date for the completed part

2.1 The Report shall contain a description of evaluations conducted, failure modes determined and repairs affected.

2.2 The Report shall contain cumulative cost of evaluation and repair, to reflect the total repair cost for completed repairs.

2.3 The Report shall also identify:

a. Ceiling amount for the Contract Line Item Number (CLIN).

b. Funded amount for the CLIN.

c. Contract Modification number on which the funded amount is based.

d. Cumulative expenditure amount by CLIN as of the report date.

e. Total monthly expenditure amount for that month, including labor, a list of labor categories, labor hours, and fully burdened labor rates.

DI-MGMT-81868

Page 2 of 2 Pages

f. A list of the items, quantity, unit price, and total price for materials.

g. Any other expenditures being directly charged to the CLIN.

3.0 End of DI-MGMT-81868.

Title: TECHNICAL DATA PACKAGE (TDP)

Number: DI-SESS-80776B Approval Date: 20190801

AMSC Number: 10057 Limitation:

Preparing Activity: MI Project Number: SESS-2019-028

Applicable Forms:

Use/relationship: A TDP is the authoritative technical description of an item which is clear, complete, and accurate, and in a form adequate for its intended use. This technical description supports the acquisition, production, inspection, engineering, and logistics of the item. The description defines the design, configuration, performance requirements, and procedures necessary to ensure essential interface and effective item performance. It consists of applicable technical data, such as: models, drawings, associated lists, engineering design data, specifications, standards, performance requirements, quality assurance provisions, software documentation, and packaging detail.

a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in paragraph 5.4 TDP elements, MIL-STD-31000B, Technical Data Packages (available online at https://quicksearch.dla.mil), to the extent required by the

b. This DID supersedes DI-SESS-80776A.

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.

2. Format. Deliverable TDP elements shall be in the Government’s format as specified on the TDP Option Selection Worksheet incorporated into the contractor or purchase order, or contractor format.

3. Content. The TDP shall include one or more of the following elements:

a. Conceptual engineering design data in accordance with MIL-STD-31000B paragraph 5.4.1.1,

b. Developmental engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.1.2,

c. Product engineering design data and associated lists in accordance with MIL-STD-31000B paragraph

5.4.1.3. The product design data shall document directly or by reference the following, as applicable:

(1) Details of unique processes, i.e., not published or generally available to industry, when essential to design and manufacture.

(2) Performance ratings.

(3) Dimensional and tolerance data.

(4) Critical manufacturing processes and assembly sequences.

Source: https://assist.dla.mil -- Downloaded: 2022-04-19T17:17Z

DI-SESS-80776B

(5) Toleranced input and output characteristics.

(6) Diagrams.

(7) Mechanical and electrical connections.

(8) Physical characteristics, including: form, finishes, and protective coatings.

(9) Details of material identification, including material condition, and mandatory treatments and coatings.

(10) Inspection, test, and evaluation criteria.

(11) Equipment calibration requirements.

(12) Quality assurance requirements.

(13) Hardware marking requirements.

(14) All required certifications, special inspections, and other environmental, operational and functional testing necessary to ensure intended performance.

(15) Vendor substantiation data.

(16) Requirements for programming software into devices or assemblies including: a description of the input media and procedures for validating that the software has been installed correctly.

(17) Special consideration items and processes.

d. Commercial engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.1.4,

e. Special Inspection Equipment (SIE) engineering design data and associated lists in accordance with

MILSTD-31000B paragraph 5.4.2,

f. Special Tooling (ST) engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.3,

g. Specifications in accordance with MIL-STD-31000B paragraph 5.4.4,

h. Software documentation in accordance with MIL-STD-31000B paragraph 5.4.5,

i. Special Packaging Instructions (SPI) engineering design data and associated lists in accordance with

MIL-STD-31000B paragraph 5.4.6,

j. Quality Assurance Provisions (QAPs) in accordance with MIL-STD-31000B paragraph 5.4.7.

End of DI-SESS-80776B.

Title: TECHNICAL DATA PACKAGE (TDP)

Number: DI-SESS-80776B Approval Date: 20190801

AMSC Number: 10057 Limitation:

Preparing Activity: MI Project Number: SESS-2019-028

Applicable Forms:

Use/relationship: A TDP is the authoritative technical description of an item which is clear, complete, and accurate, and in a form adequate for its intended use. This technical description supports the acquisition, production, inspection, engineering, and logistics of the item. The description defines the design, configuration, performance requirements, and procedures necessary to ensure essential interface and effective item performance. It consists of applicable technical data, such as: models, drawings, associated lists, engineering design data, specifications, standards, performance requirements, quality assurance provisions, software documentation, and packaging detail.

a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in paragraph 5.4 TDP elements, MIL-STD-31000B, Technical Data Packages (available online at https://quicksearch.dla.mil), to the extent required by the

b. This DID supersedes DI-SESS-80776A.

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.

2. Format. Deliverable TDP elements shall be in the Government’s format as specified on the TDP Option Selection Worksheet incorporated into the contractor or purchase order, or contractor format.

3. Content. The TDP shall include one or more of the following elements:

a. Conceptual engineering design data in accordance with MIL-STD-31000B paragraph 5.4.1.1,

b. Developmental engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.1.2,

c. Product engineering design data and associated lists in accordance with MIL-STD-31000B paragraph

5.4.1.3. The product design data shall document directly or by reference the following, as applicable:

(1) Details of unique processes, i.e., not published or generally available to industry, when essential to design and manufacture.

(2) Performance ratings.

(3) Dimensional and tolerance data.

(4) Critical manufacturing processes and assembly sequences.

DI-SESS-80776B

(5) Toleranced input and output characteristics.

(6) Diagrams.

(7) Mechanical and electrical connections.

(8) Physical characteristics, including: form, finishes, and protective coatings.

(9) Details of material identification, including material condition, and mandatory treatments and coatings.

(10) Inspection, test, and evaluation criteria.

(11) Equipment calibration requirements.

(12) Quality assurance requirements.

(13) Hardware marking requirements.

(14) All required certifications, special inspections, and other environmental, operational and functional testing necessary to ensure intended performance.

(15) Vendor substantiation data.

(16) Requirements for programming software into devices or assemblies including: a description of the input media and procedures for validating that the software has been installed correctly.

(17) Special consideration items and processes.

d. Commercial engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.1.4,

e. Special Inspection Equipment (SIE) engineering design data and associated lists in accordance with

MILSTD-31000B paragraph 5.4.2,

f. Special Tooling (ST) engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.3,

g. Specifications in accordance with MIL-STD-31000B paragraph 5.4.4,

h. Software documentation in accordance with MIL-STD-31000B paragraph 5.4.5,

i. Special Packaging Instructions (SPI) engineering design data and associated lists in accordance with

MIL-STD-31000B paragraph 5.4.6,

j. Quality Assurance Provisions (QAPs) in accordance with MIL-STD-31000B paragraph 5.4.7.

End of DI-SESS-80776B.

Title: TEST PLAN

Number: DI-MGMT-82377 Approval Date: 20220113 AMSC Number: 10297 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: MDA Project Number: MGMT-2021-015 Applicable Forms: N/A

Use/relationship: The test plan outlines the plans and performance objectives at every level of testing on systems or equipment. It provides the procuring activity with the test concept and objectives to be satisfied, test methods, elements, responsible activities associated with the testing, measures required and recording procedures.

This Data Item Description (DID) is applicable to system, component, and sub-component design evaluation tests, engineering tests, preliminary qualification tests, formal qualification tests, human factors tests, operational tests and acceptance tests.

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

Requirements

1. Reference documents. None.

2. General. The test plan shall document in detail the Contractor’s plan for conducting tests and analyzing the test results to show how the system/component/sub-component, when fielded, will satisfy the requirements of the applicable design specification. This test plan shall cover all system testing and associated activities to include support to other activities including, but not limited to:

real world, operational exercise type events; cyber & Fast-type events; Warfighter Tactics, Techniques and Procedures development events; Targets of Opportunity (TOOs); component tests;

Element or other agency integration activities; and external element upgrades and trial periods. For each type of test event, this test plan shall describe planning, test resources/infrastructure/test ranges, readiness reviews, data management, analyses, reporting, and associated activities.

3. Format. The plan shall be in Contractor’s native format. Deliverable must be compatible/readable with Government IT systems

4. Contents. The plan shall contain the following:

4.1 Title page. The title page shall include the following:

a. Contractor’s name

b. Contract Number

c. Security Classification

d. Distribution Statement

4.2 Introduction. This shall include an overview of the objectives of the test plan, including flow diagrams, milestones, personnel participation, locations, schedules, and security measures to be observed. The plan shall include the following: scope of the test program, relationship of the test plan to other element program documents, the test management approach and the organizational test responsibilities.

Source: https://assist.dla.mil -- Downloaded: 2022-05-03T21:34Z

DI-MGMT-82377

4.3 Flow Diagram and Test Processes. This plan shall include an overall flow diagram of each test type.

4.4 Participation. Identifies the Government and Contractor participation roles and responsibilities.

4.5 Location. Identifies the facilities where the testing will be performed.

4.6 Schedule. Identifies when flight, ground and cyber testing is planned to be performed (referenced to test completion – e.g., Runs for Record or Launch), identifies key interdependencies driving the planned flight, ground and cyber test schedules, and identifies flight, ground and cyber test schedule risk. Identifies the nominal planned and expected completion timeline for each type of ground, cyber and flight test event.

4.7 Security. Identify and state briefly any security measures or guidelines to be observed.

4.8 Master Test List. Identifies the major types of system flight, ground and cyber tests and support to other activities including, but not limited to: real world/operational exercise type events such as Fast-type events; Warfighter Tactics, Techniques and Procedures (TTPs) development events; TOOs, external element upgrades and trial periods; and component tests.

References shall be made to the test requirements and include a contract direction log. This Master Test List shall be contained in an appendix [or appendices] and list all tests to be accomplished in the order they are to be performed. A separate listing for each location shall be provided. Each listing shall include the following:

4.8.1 Test description. Name and brief description of test to be performed.

4.8.2 Applicable specification (s). The specifications shall be identified as follows:

a. Title and identification number.

b. Paragraph number associated with the tests.

4.8.3 Parameters. Specify the critical factors to be evaluated for test events; identify the M&S parameters to be collected in test events. Identify the process for determining the required data to be collected in order to evaluate critical factors specified.

4.8.4 Test objectives. Describe the objectives of each test performed, including the criteria, baseline, duration, and number of times each test should be performed.

a. Success/failure criteria.

b. Baseline

c. Duration

d. Quantity of tests

4.8.5 Test Configuration. Identify the hardware/software configurations for element/components under test; describe functionality to be evaluated for “first-time” testing of hardware/software upgrades; and, the configuration/name of the threats(s) for the test event.

4.8.6 Test Support Requirements. Identify and describe technical, logistical and personnel support requirements.

DI-MGMT-82377

4.8.7 Special test equipment. List all special test equipment required to be designed or fabricated for use on the program as follows:

a. Description.

b. Nomenclature

c. Date required

4.8.8 Approach. Briefly summarize the approach these tests (e.g., ground, cyber, flight etc.) will use to verify a requirement or specification is met.

4.8.9 Data Requirements and Instrumentation. Identify the process for determining data required to be collected in order to evaluate test objectives, critical factors, and M&S parameters. For each data requirement, indicate the type of instrumentation to be used to collect the data.

4.8.10 Data reduction and analysis. Describe data to be collected and the…