Attachment_J3_Consolidated_Data_Item_Description_List-1.0.pdf

DATA ITEM DESCRIPTION

Title: DOD Risk Management Framework (RMF) Package Deliverables

Number: DI-MGMT-82001 Approval Date: 20151027

AMSC Number: 9595 Limitation:

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: AS Project Number: MGMT-2015-020

Applicable Forms:

Use/relationship: The RMF Package Deliverable data will be used to satisfy the requirements of the

RMF.

This Data Item Description (DID) contains the format, content, and intended use information for the data product resulting from the work task described by the contract.

Requirements:

1. Format. The RMF package artifacts shall be delivered in a format approved by the Government’s

Designated Accrediting Authority (DAA), Navy Authorizing Official (NAO) Authorizing Official

(AO), or Information Systems Security Manager (ISSM).

2. Content. The content of the RMF package artifacts shall contain the necessary artifacts required by the DAA, NAO, AO, or ISSM to successfully achieve Platform IT (PIT) Designation, Platform IT

Risk Approval (PRA), Interim Authority to Test (IATT), or Authority to Operate (ATO).

2.1 Introduction. This section shall contain a narrative of the RMF package deliverable content.

2.1.1 IATT Request. The IATT Request shall use the approved DAA, NAO, AO, or ISSM format.

The IATT Request shall use the approved Test Plan document to identify the ‘who’, ‘what’, ‘why’, ‘where’, ‘when’, and ‘how’ of the requested Test event. The IATT Request may require IA Test

Plan artifacts such as vulnerability scans and STIG checklists. The IATT Request shall be delivered not less than 30 days prior to the start of the Test Event to the Program Office.

2.1.2 Security Plan (SP). The SP shall use the approved DAA, NAO, AO, or ISSM format. The SP shall contain at a minimum, System Information, Mission Description, Concept of Operations

(CONOPS), Environment, Operating and Computing Environment, Physical Security Measures, Facilities Descriptions, Threat Analysis, System Architecture Description, Components, Configurations, Accreditation Boundaries, Connection Process Guide (CPG) Compliant Network

Diagrams, External Interfaces and Data Flow, Internal Data Flow, Contingency Plan, Incident

Response Plan, User Descriptions and Clearances, Security Roles, Hardware Lists, Software Lists, Ports, Protocols, and Services (PPS), Configuration Management Plan, Information Assurance

Vulnerability Management (IAVM) Plan, and A&ATasks and Milestones. The SP shall be approved and signed by the ISSM, User Rep, Program Manager (PM), and DAA, NAO, or AO.

2.1.3 Assessment and Authorization (A&A) Project Plan. The A&A Project Plan shall use the approved DAA, AO, or ISSM format. The A&A Project Plan is used to establish an executable

RMF project plan. The A&A Project Plan shall be approved and signed by the ISSM, Echelon II

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

M67854-19-R-7800 Attachment J3

DISTRIBUTION STATEMENT A. Approved for public release: distribution unlimited.

DI-MGMT-82001

Representative, and PM. The A&A Project Plan shall define the various A&A Tasks and Milestones needed to achieve PRA, IATT, or ATO.

2.1.4 Collaboration Brief. The Collaboration Brief is a summary of the System Overview, RMF

Package, and Residual Risk that is presented to the DAA, NAO, AO, Certification Authority (CA), or Security Control Assessor (SCA) during Collaboration. The Collaboration Brief shall use the approved DAA, NAO, AO, or ISSM format. The Collaboration Brief is submitted with the RMF package and is used to describe the System and Residual System Risk during the Collaboration meeting.

2.1.5 RMF Implementation Plan. The RMF Implementatn shall use the approved DAA, NAO, AO, or ISSM format. The DIP shall be used during the DIP Concurrence meeting with the Echelon II, Navy CA, and ODAA. The DIP shall define which IA Controls (IACs) will be ‘Implemented’, ‘Inherited’, ‘Non-Compliant’, or ‘Not Applicable’. The DIP shall be approved by the DAA, AO, and ISSM prior to execution of the IA Test Plan. The DIP must be approved before moving forward with IA Control Implementation.

2.1.6 PIT Implementation Plan (PIP). The PIP shall use the approved DAA, NAO, AO, or ISSM format. The PIP shall be used during the PIT Concurrence meeting with the Echelon II, Navy CA, and ODAA. The PIP shall define which IACs will be ‘Implemented’, ‘Inherited’, ‘Non-Compliant’, or ‘Not Applicable’. The PIP shall be approved by the DAA, AO, and ISSM prior to execution of the IA Test Plan. The PIP must be approved by the DAA, NAO, AO, CA, or SCA before moving forward with IA Control Implementation.

2.1.7 IA Test Plan. The IA Test Plan shall use the approved DAA, NAO, AO, or ISSM format. The

IA Test Plan shall define all required Vulnerability Scans, Security Technical Implementation Guides

(STIGs), Security Readiness Guides (SRGs), Secure Content Automation Protocol (SCAP) benchmarks, and other IA Controls or Security Overlays to be applied to the System. The IA Test

Plan shall be approved by the DAA, NAO, AO, and ISSM during the DIP or PIP Concurrence

Meeting. The IA Test Plan must be approved by the DAA, NAO, AO, CA, or SCA prior to moving forward with IA Control Implementation.

2.1.8 PIT Designation Request. The PIT Designation Request shall use the approved DAA, NAO, AO, or ISSM format. The PIT Designation Request is the formal request to the DAA, NAO, or AO that the System meets the requirements of PIT and shall be designated as Platform IT (versus an

Information System (IS)). The PIT Designation Request shall be approved and a PIT Designation

Letter shall be signed by the DAA or AO prior to the execution of the IA Test Plan and implementation of IA Controls.

2.1.9 PIT Determination Brief. The PIT Determination Brief shall use the approved DAA, NAO, AO, or ISSM format. The PIT Determination Brief shall be used in conjunction with the PIT

Designation Request to formally request the System be designated Platform IT (versus and

Information System).

2.1.10 Plan of Action and Milestones (POA&M). The POA&M shall use the approved DAA, NAO, AO, or ISSM format. The POA&M shall be considered a ‘living’ document and shall regularly be updated throughout the entire lifecycle of the System through Decommission. The POA&M shall contain all Not Applicable (N/A) IA Controls, All Non-Compliant IA Controls, and all Non-

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

Compliant Vulnerability Findings as identified in the Vulnerability Scans, STIGs, SRGs, and SCAP

Benchmarks. At a minimum, the POA&M shall be updated monthly.

2.1.11 Privacy Impact Assessment (PIA). The PIA shall use the approved DAA, AO, or ISSM format. The PIA shall be approved and signed by the ISSM, PM, and the Command PIA Officer.

2.1.12 Vulnerability Scans. In accordance with the approved IA Test Plan, the System shall be scanned using the approved vulnerability scanning tools as identified by the DAA, AO, or ISSM.

The vulnerability scanner shall be updated with the latest signatures and scanning engines prior to the execution of each vulnerability scan. At a minimum, vulnerability scans shall be conducted monthly against the System. Non-compliant findings shall be documented in the System POA&M on a minimum monthly basis. At a minimum, vulnerability scans shall be submitted electronically to the

ISSM or uploaded into the RMF package (eMASS) or the Vulnerability Remediation Asset Manager

(VRAM). Vulnerability scans shall be handled and transmitted in accordance with the System’s classification level. Vulnerability reports shall be in a format approved by the DAA, NAO, AO, or

ISSM. Vulnerability scans shall be protected in accordance with the System’s classification.

2.1.13 Security Technical Implementation Guides (STIGs), Security Readiness Guides (SRGs), Secure Content Automation Protocol (SCAP) Benchmarks. In accordance with the approved IA

Test Plan, the System shall be hardened using the required and approved STIGs, SRGs, SCAP

Benchmarks, and other approved hardening tools. Non-compliant STIG, SRG, SCAP Benchmark, and other findings shall be documented in the System POA&M on a minimum monthly basis.

Updates to the STIGs, SRGs, and SCAP Benchmarks are released on a monthly, quarterly, and yearly basis. Updates to the STIGs, SRGs, and SCAP Benchmarks shall be implemented into the

System as they are released. Non-compliant STIG, SRG, and SCAP Benchmark findings shall be documented in the System POA&M on a minimum monthly basis. STIG, SRG, and SCAP

Benchmark artifacts shall be provided in a format approved by the DAA, NAO, AO, or ISSM.

STIG, SRG, and SCAP Benchmark artifacts shall be handled in accordance with the System’s classification level. At a minimum, STIG, SRG, and SCAP Benchmarks shall be submitted electronically to the ISSM or uploaded into the RMF/RMF Package on a minimum monthly basis.

STIG, SRG, and SCAP Benchmark results shall be protected in accordance with the System’s classification.

2.1.13 Scorecard. The Scorecard shall use the approved DAA, NAO, AO, or ISSM format. The

Scorecard shall be maintained and updated on a minimum monthly basis.

2.1.14 Contingency Plan. The Contingency Plan shall use the approved DAA, NAO, AO, or ISSM format. The Contingency Plan shall be submitted in conjunction with the System’s SP. The

Contingency Plan shall be approved and signed by the PM, ISSM, and DAA, NAO, or AO.

2.1.15 Information Assurance Vulnerability Management (IAVM) Plan. The IAVM Plan will define how the Developer and Program Office will track, notify, and implement security vulnerabilities as they are identified. The IAVM Plan shall use the approved DAA, NAO, AO, or ISSM format. The

IAVM Plan shall be submitted in conjunction with the System’s SP. The IAVM Plan shall be approved and signed by the PM, ISSM, and DAA, NAO, or AO.

2.1.16 Cyber Security Waiver Requests. Cyber Security Waiver Requests are an acknowledgement by the PM that compliance will not or can not be made during the life of the System due to technology or Programmatic constraints. Cyber Security Waivers shall use the approved DAA, Source: https://assist.dla.mil -- Downloaded: 2018-07-02T01:35Z Check the source to verify that this is the current version before use.

NAO, or AO format. All Cyber Security Waivers shall be approved and signed by the ISSM, PM, and First Flag or Equivalent prior to submission to the DAA or AO.

2.1.17 Cyber Security Waiver Extension Request. Cyber Security Waiver Extension Requests are an acknowledgment by the PM that compliance will be met beyond the stated compliance date. Cyber

Security Waiver Extensions shall use the approved DAA, NAO, or AO format. All Cyber Security

Waiver Extensions shall be approved and signed by the ISSM, PM, and First Flag or Equivalent prior to submission to the DAA or AO.

End of DI-MGMT-82001

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

Title: ACCIDENT INCIDENT REPORT

Number: DI-MGMT-82188 Approval Date: 20180322

AMSC Number: N9905 Limitation: N/A

DTIC Applicable: N/A GIDEP Applicable: N/A

Preparing Activity: SH Project Number: MGMT-2018-018

Applicable Forms: N/A

Use/Relationship: The Accident Incident Report provides the government with notification of incidents that happen accidentally, are not in the usual course of operations, are not according to expectations, and are not routine. The report covers incidents resulting in any one or more of the following: personnel injury, property damage, security violation, or other significant incidents.

This data item description (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 report shall be presented in a format similar to that in Figure 1. 1.

Content. The report shall contain all of the information in Part 1 through Part 4 of Figure 1. 2.

2.1 The Report shall identify incidents resulting in any one or more of the following:

a) Personnel Injury

Any incident that involves injury that could result in loss of time from work and requires medical treatment beyond first aid.

b) Property Damage or Loss

1) All property damage or loss regardless of dollar value.

2) Any accident that involves vehicle damage or property damage caused by a vehicle.

c) Security Violation / Incident

1) Any incident involving protection of Tactical Training Range facilities, computer networks, or computer environments.

2) Any incident that involves the loss, compromise, or suspected compromise of classified or sensitive information.

3) Any incident that involves unauthorized changes to the Information Assurance posture of a computer network as defined in the respective SSAA will be considered a violation.

d) Other:

1) Any incident the submitter is unable to resolve under the three other categories.

2) Any incident that occurs on the range where the Contract Site Manager (CSM) or

Range System Manager (RSM) determine that an Accident/Incident Report is

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

DI-MGMT-82188

warranted to preclude a similar occurrence on the Combined Tactical Training

Ranges (CTTR).

2.2 A summary of what happened in the incident shall be included.

2.3 The events preceding the investigation shall be specified in reverse order of occurrence, starting with the event and moving backward in time. A reconstruction of the steps that led to the investigation shall also be included.

2.4 Causal factors of the chain of events leading to the accident or incident shall be included.

2.5 The report shall include actions and corrective actions that have been or will be taken to prevent re-occurrence, the timeframe for performing all actions and corrective actions, as well as the associated work order that will be used to track cost.

End of DI-MGMT-82188

Source: https://assist.dla.mil -- Downloaded: 2018-05-15T20:31Z

Figure 1 – Accident/Incident Report (Sample)

Title: TRIP/TRAVEL REPORT

Number: DI-MISC-81943 Approval Date: 20130827

AMSC Number: N9428 Limitation: N/A

DTIC Applicable: N/A GIDEP Applicable: N/A

Office of Primary Responsibility: SH/NSWCDD/K03

Applicable Forms: N/A

Use/relationship:

The Trip/Travel Report will be used to record the purpose of the trip, observations, and any applicable conclusions or recommendations based upon the purpose.

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 Trip/Travel Report shall be in contractor format.

2. Content. The report shall contain the following:

a. Name of employee

b. Date(s) of trip

c. Site visited

d. Purpose of trip

e. Relevant observations during the trip

f. Relevant conclusions/recommendations based on the trip

3. End of DI-MISC-81943.

Source: https://assist.dla.mil -- Downloaded: 2017-06-21T19:00Z Check the source to verify that this is the current version before use.

Title: Management Plan

Number: DI-MGMT-80004A Approval Date: 30 OCT 2006 AMSC Number: 7621 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: The management plan describes the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs.

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 may be applied in any contract or program phase where the contract management is under the direction and control of the contractor.

Requirements:

1. Reference documents. None.

2. Format. The plan shall be in a format that the contractor devises and conforms to the following:

a. Identification. The plan shall be identified with the preparing office or contractors title, the identifying numbers or designation of the Contract/Procurement Request, the identify and/or nomenclature of the system/component/program/project, the security classification and the Government activity issuing the controlling contract.

b. Descriptive material. As may be needed to clarify or explain matters in the text, the plan may include descriptive material, sketches, drawings, photographs, tables, forms, graphs, worksheets, charts, etc.

c. Page size. The plan may be typewritten or printed on standard size paper, e.g., 8 ½ x 11 inches or metric A4. The pages shall be sequentially numbered and security bound together. As necessary, graphic material may be one-way fold-outs. All attachments shall be identified and referenced in the text. Each section and paragraph shall be numbered.

d. Table of contents and index. Plans of more than 30 pages in length shall contain a

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

h. delivery procedures

DI-MGMT-80004A

table of contents. Plans more than 120 pages in length shall also include an Index.

e. Legibility. The document shall be legible and reproducible.

3.1 General. The Management Plan shall consist of the organizational structure, the assignment of functions, duties, and responsibilities, the procedures and policies and the reporting requirements that are established for the initiation, monitoring, control, completion, test and verification, and reporting of contractual tasks, projects, and programs.

3.2 Specific contents. The Management Plan shall cover the organizational structure, program management methodology, personnel, security, and the reports as described herein. Other subjects to be included are as follows:

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

i. tests

j. certifications

k. packaging

l. shipping

m. other

3.3 Organizational structure. The plan shall present an organizational chart and supporting narrative portraying the contractor’s business (corporate) structure. It shall describe the functional relationships and responsibilities among the organizational elements that will participate in the accomplishment of the contractual commitments.

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

DI-MGMT-80004A

3.4 Program management. The plan shall present an organizational chart and supporting narrative describing the management office the contractor establishes to manage the contractual commitments. The plan shall define the direct lines of control, responsibilities, functional relationships, and authority between the management office and the contractor’s other organizational elements. The plan shall also describe all interfaces between the contractor and the Government and between the contractor and other contractors which are necessary and pertinent to the accomplishment of contractual tasks, projects and programs.

3.5 Methodology.

a. The plan include a narrative description of the technical approach or methods the contractor will employ to accomplish contractual tasks, projects, and programs, including, as applicable, development, tests, manufacture, construction, formulation, installation, logistics support, training, maintenance documentation, and configuration controls.

b. The plan shall include a milestone chart graphically depicting the schedule of events associated with accomplishing each contractual commitment.

3.6 Personnel.

a. The plan shall list the personnel staffing of the contractor’s management office that directs the contractual tasks, projects, and programs and assist in completing the contract. The listing shall include the education, training, skills, experience, and security clearance that personnel require to fill each such position and shall state the identity, background, and work experience of the personnel assigned to fill these positions.

b. The plan shall also describe the staffing required for proper accomplishment of each contractual task by skill type, skill level, number of personnel, and security clearance. When submitted as part of a proposal, the plan shall state how many such personnel are currently available and how many new hires are required to staff fully to accomplish each task as scheduled.

3.7 Security.

a. Provide a Standard Practice Procedure (SPP) which fully describes the security program, safeguards emergency procedures to be established to the protection of Government-furnished and contractor-developed classified materials prepared In conjunction with the project. The SPP shall be prepared in accordance with guidelines contained in the Industrial Security Manual, Purchase Description, and such additional requirements as may be stipulated by the cognizant security compliance organization. The SPP shall require approval by the Government.

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

DI-MGMT-80004A

b. Develop a comprehensive security accreditation plan to demonstrate how the computer security requirements stipulated in the PD, as applicable, have been accounted for in the system design, and how satisfaction of each requirement will be explicitly demonstrated in the test program. This plan shall also identify any specific support equipment or software to be provided for demonstration of design compliance and/or system compliance with the planned security requirements. The plan shall require approval by the Government prior to implementation.

c. Reports. The plan shall describe the management methods the contractor will employ to ensure meeting all preparations, format, and submittal requirements established by the CDRL (DD Form 1423) for data to be delivered to the Government.

4. END OF DI-MGMT-80004A

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

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:47Z

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:47Z

Title: CYBER SECURITY WORKFORCE (CSWF) REPORT

Number: DI-MGMT-82160 Approval Date: 20171002

AMSC Number: N9862 Limitation: N/A

DTIC Applicable: N/A GIDEP Applicable: No

Preparing Activity: SH Project Number: MGMT-2017-056

Use/Relationship: The Cyber Security Workforce (CSWF) Report will be used to track and report individuals working on contract who are IA/cyber security trained and certified.

This DID contains the format, content, and intended use information for the data product generated by the specific and discrete task requirement as delineated in the contract.

Format. The CSWF Report shall be in the format of Figure 1 to this DID.

Content. The CSWF Report shall include all the information specified in Figure 1 of this DID.

The report shall identify training, certification, and categorization information.

Source: https://assist.dla.mil -- Downloaded: 2018-05-15T20:22Z

Figu re 1

C o n tract N

#####‐##‐#‐####/ TO

P erio d o f P erfo rm an ce: [m m

/d d

/yy] to [m m /d d /yy]

TO

C o m p letio n D ate: [m m

/d d

/yy]

D I-M

G M

T -8

SW

F R ep o rt C

O R

: [First n am e Last n am e]

W o rk P h o n e: ###‐###‐#### File N am e: [co n tract n u m b er-TO n u m b er]_[co n tracto r n am e]_C

SW

F_[yyyym m d d (en d d ate o f rep o rtin g p erio d

Em p lo yee N am e

(Last, First)

Lab r C atego ry

(IA

W

B asic C o n tract)

S D esign ato r

S Level/P o sitio n C atego ry an

Sp ecialty C o es

S D u ty H o u rs

S C ertificatio

D ate O b tain ed

(m m

/d d

/yy)

D ate

Exp ires

(m m

/d

/yy)

O eratin g System

(O S)/ C o m p u tin g

En viro n m en t (C

E) C ertificatio n o r Train in g ertificates

V en d o r w h ro vid n o r

Train in g

N u m b er o r ID

D ate O b tain

/d d

/yy)

D ate

Exp ires

(m m

/d d

/yy)

Sco p e o f P rivilege

A ccess

A greem en t (P

A A

P sign

/d d

/yy)

D ep t /C O

D E

A ssign

P ro ficien cy

Level

E d o f D I-M

G M

T -8

Source: https://assist.dla.mil -- Downloaded: 2018-05-15T20:22Z

Title: Other Direct Costs (ODCs) Report

Number: DI-FNCL-81866 Approval Date: 20120629

AMSC Number: N9270 Limitation: N/A

DTIC Applicable: N/A GIDEP Applicable: N/A

Office of Primary Responsibility: SH/ SEA 21AL

Use/relationship: This information will be used by the Government to monitor monthly other direct cost

(ODCs), including travel costs, in comparison against total labor funding percentage.

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.

1. Format. The report shall be presented in a format similar to that of Figure 1.

2. Content. The report shall contain all information specified in Figure 1 and shall also include the following:

a. Incurred cost to the contract line item number (CLIN) funding source level for total labor cost

b. Information technology (IT) costs

c. Travel costs

d. Miscellaneous material cost

e. The percentage of (IT) costs, travel costs and miscellaneous material costs compared to total labor costs.

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:48Z

DI-FNCL-81866

Page 2 of 2 Pages

OTHER DIRECT COSTS (ODCs) CLIN

TOTAL

LABOR

COST IT COSTS

% OF

TOTAL

LABOR

TRAVEL

COSTS

% OF

TOTAL

LABOR

MISC

MATERIAL

COSTS

% OF

LABOR

CUMULATIVE

OTHER

DIRECT

% OF

TOTAL

LABOR

SHIP/AVAILABILITY PRODUCT WORK 0001 #DIV/0! #DIV/0! #DIV/0! #DIV/0!

ALTERATION WORK 0002 #DIV/0! #DIV/0! #DIV/0! #DIV/0!

EXPANDED EXPLANDED (EX)2 PLANNING YARD WORK 0003 #DIV/0! #DIV/0! #DIV/0! #DIV/0!

PROVISIONED ITEMS ORDERS (PIO) 0005 #DIV/0! #DIV/0! #DIV/0! #DIV/0!

TOTAL COSTS

% OF TOTAL LABOR #DIV/0! #DIV/0! #DIV/0! #DIV/0!

Sample Form

Figure 1

3. END OF DI-FNCL-81866.

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:48Z Check the source to verify that this is the current version before use.

Title: Contract Invoicing and Payment Report

Number: DI-MGMT-81651 Approval Date: 14 January 2005 ASMC Number: A7545 Limitation: NA DTIC Applicable: NA GIDEP Applicable: NA Office of Primary Responsibility: AR Applicable Forms: NA Use/relationship: The Contract Invoicing and Payment Report collects financial and accounting information associated with contract line item numbers (CLINs) and accounting requirements classification numbers (ACRNs) within an awarded contract, which will be used to manage obligations, disbursements, un-liquidated obligations, and canceling accounts associated with appropriated funds.

This Data Item Description (DID) contains the content, preparation instructions and intended use information for the data product resulting from the work task described in the contract.

Requirements:

1. Format. Data will be submitted electronically and may be in contractor format.

2. Content. This report shall include:

a. A listing of each CLIN and subline item number (SLIN) along with the following information for each CLIN/SLIN:

1. ACRN for the CLIN/SLIN.

2. Total CLIN/SLIN value as contained in the contract.

3. CLIN/SLIN funded amount.

4. Cumulative amount invoiced for the CLIN/SLIN.

5. CLIN/SLIN funds remaining. (Difference between CLIN/SLIN funded and invoiced amounts)

6. Percent invoiced of funded amount. (Invoiced amount as a percentage of funded amount)

7. Deductions for the period. (Amount of any performance deductions taken against the

CLIN/SLIN during the reporting period)

8. Cumulative total of all deductions taken against the CLIN/SLIN.

9. Amount of payment received against the CLIN/SLIN.

b. Totaled amounts for all entries for items a.2 through a.9.

3. End of DI-MGMT-81651

Source: https://assist.dla.mil -- Downloaded: 2017-07-06T22:18Z Check the source to verify that this is the current version before use.

Title: Phase-Out Transition Plan

Number: DI-MGMT-81945 Approval Date: 20130916

AMSC Number: N9430 Limitation: N/A

DTIC Applicable: N/A GIDEP Applicable: N/A

Office of Primary Responsibility: AS/PMA-207

Applicable Forms: N/A

Use/relationship:

The Phase-Out Transition Plan provides a detailed description of the transfer of full assumption of duties at each site to the follow-on contractor.

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 and described in the Performance Work Statement (PWS). It should be tailored to the minimum data requirements of the applicable contract or purchase order.

1. Format. Contractor format is acceptable.

2. Content. The Phase-Out Transition Plan shall include:

a. A written comprehensive plan explaining actions required to complete the total transition effort within a sixty (60) calendar day transition period.

b. Details of accounts and subscription services to be terminated or transferred.

c. Process to conduct a full joint inventory and transference of all Government

Furnished Material inventory including all records.

d. Status of all items in inventory as well as the items that have been inducted into repair facilities, being modified or are being purchased.

e. Details for the removal of all contractor owned items.

f. Critical path schedule for risk mitigation of the transition period.

g. Plan to make training and certification records available of contractor personnel who are considering employment with the succeeding contractor.

3. End of DI-MGMT-81945.

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:49Z

Title: CONTRACTOR'S PERSONNEL ROSTER

Number: DI-MGMT-81834A Approval Date: 20130118 AMSC Number: N9316 Limitation: N/A DTIC Applicable: No GIDEP Applicable: N/A Office of Primary Responsibility: SH/MS10 Applicable Forms: N/A

Use/relationship:

This roster shall be used to list all contractor personnel assigned to the contract.

This Data Item Description (DID) contains the content and preparation instructions for data product resulting from the work task specified in the contract.

Requirements:

1. Format. The Roster shall be in contractor’s format.

2. Content. The Roster shall contain an alphabetical listing of the names of all contractor personnel assigned to the contract.

2.1 The roster shall identify the following for each employee:

a. Change Status: Add/Change/Remove

b. Start Date

c. End Date

d. First Name

e. Middle Name

f. Last Name

g. Position Title

h. Email Address

i. Work Phone Number

j. Physical Work Location – Base Name

k. Physical Work Location - City

l. Physical Work Location - State

m. Physical Work Location – Building Number

n. Physical Work Location – Room Number

o. Contract Number

p. Contract Name

q. Contracting Supervisor

r. Government Support POC

s. Supporting Code

2.2 The roster shall identify work schedules for full time and part time employees and shall include current CAC and clearance information for each.

3. End of DI-MGMT-81834A.

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:50Z

Title: CONFERENCE AGENDA

Number: DI-ADMN-81249B Approved Date: 20160524

AMSC Number: F9658 Limitation:

DTIC Applicable: GIDEP Applicable:

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

Applicable Forms: None

Use/Relationship: The Conference Agenda provides information concerning purpose, location, and schedule of conferences required to manage the acquisition of systems equipment, related items, and services.

a. This Data Item Description (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.

b. This DID supersedes DI-ADMN-81249A.

Requirements:

1. Reference documents. None.

2. Format. Contractor format is acceptable.

3. Content. The agenda shall include the following, where applicable:

a. The purpose and objective of the conference.

b. The conference location, date, and duration.

c. A daily chronological listing of each major topic or subtopic to be discussed and the time to be devoted to each topic.

d. A list of activities to be represented and identification of their responsibilities.

e. A list of subcommittees to be established during the conference and the proposed activity representation for each subcommittee.

f. Reference to and brief description of the results of previous meetings, when relevant.

g. Location, schedule, and purpose or subject area to be covered by each subcommittee, when applicable.

h. Names of the conference chairperson, co-chair, and subcommittee chairs, when applicable.

i. Information on billeting, messing, transportation, and administrative services available to conference attendees.

j. Complete list of all documentation to be available for review.

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:51Z Check the source to verify that this is the current version before use.

k. Brief description of progress on actions or problems identified at previous meetings, when applicable.

l. Other pertinent information such as Forms to be used, identification of any deviations or waivers, security classification, and clearance requirements.

End of DI- ADMN-81249B

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:51Z

Title: CONFERENCE MINUTES

Number: DI-ADMN-81250B Approved Date: 20160524

AMSC Number: F9659 Limitation:

DTIC Applicable: GIDEP Applicable:

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: ADMN-2015-001

Applicable Forms:

Use/Relationship: Conference minutes provide documentation of technical information provided and decisions and agreements reached at meetings.

a. This Data Item Description (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.

b. This DID supersedes DI-ADMN-81250A.

Requirements:

1. Reference documents: None.

2. Format. Contractor format is acceptable.

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

a. A title page containing the following:

(1) Title – type of meeting and date.

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

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

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

b. The purpose and objective of the conference.

c. The conference location.

d. A summary of the discussions, decisions, agreements reached, and directions of the conference or individual subcommittees thereof.

e. A list of attendees by name, rank, grade or position, activity represented, activity symbol/code, phone numbers, and emails, as appropriate.

f. Action items resulting from the conference.

g. Briefing charts, if presented, shall be attached to the minutes for information only.

End of DI- ADMN-81250B

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Source: https://assist.dla.mil -- Downloaded: 2017-02-23T13:52Z

Title: Briefing Material

Number: DI-MGMT-81605 Approval Date: 15 February 2001 AMSC Number: G7425 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: No

Office of Primary Responsibility: G/TS-ALS

Applicable Forms: None

Use/relationship:

The Briefing Material shall provide the Government with the necessary briefing materials to conduct a formal or informal briefing.

Requirements:

l. Contract. This data item is generated by the contract which contains a specific and discrete work task to develop this data product.

2. Content. The content of the briefing material shall address those areas of the contractual effort identified by the Government on the DD Form 1423, Contract Data Requirements List (CDRL).

3. Format. The format for the briefing material shall be in contractors format unless otherwise specified by the DD 1423, or the COR.

End of DI-MGMT-81605

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

Title: TRAINING SYSTEMS UTILIZATION REPORT

Number: DI-PSSS-82161 Approval Date: 20171026

AMSC Number: N9864 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: MC Project Number: PSSS-2017-031

Use/relationship: The Training Systems Utilization Report (TSUR) provides the data necessary to determine the cost benefit of training, cost avoidance, track training efficiencies, operational availability of training systems, and enhance training records. The TSUR contains the training data required perform analyses of the training accomplished.

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

b. It is not intended that all the requirements contained herein be applied to every program or program phase. Government may tailor or delete portions or individual data requirements of this DID as needed.

1. Reference Documents. None.

2. Format. The TSUR shall be delivered in MS Excel. The format shall be approved by the

Government. The approved format shall be used for all subsequent submissions. Revisions to format shall be approved by the Government.

3. Content. The TSUR shall contain the following training data:

a. Training Events & Exercises

(1) Dates

(2) System/Training Name/Identifier utilized for training

(3) Location

(4) Number of trainees trained (per device as applicable)

(5) Total hours operated (per device as applicable)

(6) Type of exercise

(7) Units trained: Identify which units received training

(8) Weapons utilized: Identify which weapons are utilized in training per training event

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

DI-PSSS-82161

(9) Ammo utilized: Identify ammo quantity by type that is utilized in training per blanks, and simulated rounds

(10) Trainees per system: Identify quantity of trainees trained on each system

(11) Miles driven: Identify quantity of miles driven per simulated vehicle

(12) Scenarios trained: Identify quantity for each scenario used for training

(13) Mission Essential Tasks (METs) and Training and Readiness (T&R) events trained

(14) Scenarios failed by trainees: Identify quantity for each scenario of trainees that fail scenarios

b. Formal Training Courses

(1) Units scheduled: Unit designations (unit name and organization)

(2) Unit no show: Units who register for and schedule training, but do not show up or cancel less than forty eight (48) hours before training commencement.

(3) Individuals scheduled: Number of trainees who register for and schedule academic or practical device training.

(4) Individual no show: Number of trainees who register for and schedule training but do not show up.

(5) Training disqualification: Number of trainees who do not commence training due to disqualification.

(6) Commence: Number of trainees that show up training

(7) Percentage of non-USMC (U.S. Military): Non-USMC trainees out of the total number trainees that “commence” the training

(8) Non-USMC commence (Joint Forces): Number of non-USMC, Joint Forces trainees who show up for training

(9) Percentage of non-USMC (Joint Forces): Non-USMC, Joint Forces trainees out of the total number trainees that “commence” the training.

(10) Unit recall: Number of trainees who commence a training course, but are recalled from the training from their unit, leave the training site, do not attempt to complete the entire training, and do not complete the course.

(11) Med drop: Number of trainees who commence a training course, but leave the training site due to medical reasons, does not attempt to complete the entire training, and do not complete the course.

(12) Drop on request: Number of trainees who commence a training, but provide notice during the training that they will not continue the training, do not attempt to complete the entire training, and do not complete the course.

(13) No return: Number of trainees, who commence training, but leave or fail to return to the training site, do not attempt to complete the entire training, do not complete the course, and do not provide an explanation.

(14) Total pass: Number of trainees who participate in an entire course, master all course objectives and exercises, and complete the course.

(15) Late: Number of trainees who schedule training and show up 30 minutes or more beyond the scheduled training commencement time.

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

DI-PSSS-82161

c. Operational Hours

(1) Training system operational availability (%) based on contractual definition of operational availability.

(2) Training systems hours available

(3) Training systems hours utilized for training

(4) Training systems non-operational hours by type

(a) Preventative maintenance hours

(b) Corrective maintenance hours

(c) Other non-operational hours

End of DI-PSSS-82161

Source: https://assist.dla.mil -- Downloaded: 2018-07-02T01:49Z

TITLE: TRAINING CONDUCT SUPPORT DOCUMENT

Number: DI-PSSS-81523C Approval Date: 20141120 AMSC Number: N9492 Limitation:

DTIC Applicable: No GIDEP Applicable: No Office Of Primary Responsibility: Navy-AS PMA205 Applicable Forms: None

Use/relationship: The Training Conduct Support Document provides specific definition and direction to the instructor and trainees on learning objectives, equipment, and instructional media for use during the conduct of training. It also provides updates to course materials for life cycle maintenance of the training course.

a. This Data Item Description (DID) contains the preparation instructions for the content and format of the Training Conduct Support Document.

b. This DID contains the format, content, and intended use information for the data product resulting from the performance requirements described by 3.2.7 of MIL-PRF- 29612B, and is applicable to the acquisition of training data products. Data product performance evaluation criteria are specified in 4.3.7 and 4.3.9 of MIL-PRF-29612B.

c. It is not intended that all the requirements contained herein be applied to every program or program phase. Any individual data requirement contained in this DID is subject to deletion tailoring.

d. This DID supersedes DI-SESS-81523B.

Requirements:

1. Format. The contractor format is acceptable. Standard digital data, when specified, must be in compliance with the content and format requirements specified in the DoD Data Architecture (DDA) and the Defense Data Dictionary System (DDDS).

The deliverable of the product required by this DID meets the intent and requirements of DoDINST 5000.2.

2. Content. The Training Conduct Support Document shall contain the following:

2.1 Front matter. Front matter shall consist of the following:

2.1.1 Cover. The cover shall provide information relevant to the identification of the training document as follows:

a. Course title.

b. Course number.

c. Document number.

d. Date of preparation.

e. Training document type name (e.g., lesson plan, trainee guide).

f. The “prepared for” block shall identify the using activity and career field.

g. The “prepared by” block shall identify the company/agency that developed the training document.

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

h. The contract number shall identify the contract under which the training document was procured.

i. Distribution statement and destruction notice.

j. The publication by direction statement shall identify the contracting activity.

k. Logos shall be as Service or command specified.

l. Supersession statement.

m. Foreign disclosure statement.

n. Security classification.

2.1.2 List of effective pages. This data shall be provided in Volume I and shall include the listing of pages provided in all volumes.

2.1.3 Letter of promulgation. The letter of promulgation will be furnished by the Government.

2.1.4 Change record. This data shall be included in each separate volume. Volume I shall include the listing of pages provided in all volumes.

2.1.5 Hazard awareness notice. This data shall provide safety and environmental precautions for the protection of personnel, equipment and instructions for the reporting of hazards and safety violations. Hazard awareness statements shall cover relevant documentation references, general and specific precautions, hazard reporting criteria, and shall include the following:

a. The documentation statement shall identify relevant documentation containing specific safety precautions and preventive measures that are applicable to particular equipment.

b. The general information statement shall identify hazards to personnel or equipment.

c. The specific precautions statement shall identify specific direction to personnel concerning safety. Statements shall inform personnel that death, personal injury, and equipment damage can result from carelessness, failure to comply with approved procedures, or violations of WARNINGS, CAUTIONS, and safety regulations.

d. The hazard reporting statement shall identify the requirement of personnel to report all hazards, safety violations, environmental considerations, and the activity to which such reports should be sent.

2.1.6 Foreword/preface. This data shall contain the scope, purpose and applicability of the publication and any other information the reader requires as an introduction to the document.

2.1.7 Definitions. This data shall include definitions of those words that are unique to the training document.

2.1.8 Table of contents. This data shall list all contents of the training document and shall include the paragraph number, paragraph title, and corresponding page number. It shall also include a list of figures and tables and shall include the figure and table number, title, and corresponding page number. Each volume in a set of documents shall

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

contain its own list of figures and tables. In addition, Volume I shall contain a list of figures and tables for all volumes in the set.

2.1.9 How to use the training document. This data shall include descriptions of the following:

a. Composition.

b. Function.

c. Use.

d. Assignments.

e. Equipment requirements.

f. Instruction sheets.

g. Test requirements.

h. Division of materials into functional parts.

2.1.10 Executive Summary. This data shall be developed using clear, concise narrative statements describing the methodology for data accumulation and analysis, the target population, the results of the analysis, and recommendations as required.

2.2 Part 1: Lesson plan data requirements. The lesson plan contains data requirements that provide specific definition and direction to the instructor on learning objectives, equipment, instructional media requirements, and the conduct of training.

Lesson plan data requirements shall include:

2.2.1 Front matter. Front matter shall be as defined in 2.1.

2.2.2 Administrative data. This data shall provide information required to prepare for, and conduct the lesson. Administrative information shall consist of:

a. Course title.

b. Document number.

c. Course number.

d. Curriculum name.

e. Unit title.

f. Unit number.

g. Lesson title.

h. Lesson number.

i. Responsible authoring activity.

j. Date of preparation.

k. Effective date.

l. Approval date.

m. A list of topics and tasks to include task number, title, conditions, and standards.

n. Security classification.

o. Time breakdown (e.g., overall, classroom, laboratory).

p. Student allotted lesson time.

q. A list of references.

r. A description of commonality.

s. A description of instructional format.

t. A list of learning objectives.

u. A list of teaching points.

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

v. A list of equipment required for the instruction.

w. A list of instructional aids.

x. A description of testing requirements.

y. A list of supporting papers.

z. Revision dates.

aa. A list of trainee instructional materials.

ab. A description of multiple instructor requirements.

ac. A description of instructional guidance.

ad. A description of classroom, laboratory, training area, and range requirements.

ae. A description of ammunition requirements.

af. A description of prerequisites.

ag. A list of source documentation.

ah. A list of environmental considerations.

ai. A description of additional support personnel requirements.

aj. A description of training portal infrastructure operations to include:

(1) Learning Management Systems (LMS).

(2) Course Management System (CMS).

(3) Courseware development/authoring tools.

(4) Communication tools.

(5) Resource references.

ak. For Advanced Distributed Learning (ADL), a description of hardware and software requirements for administrators, instructors, and students.

2.2.3 Instructional data. This data shall provide information to be presented during a course of instruction and shall include:

a. Overview.

b. Lesson strategy.

c. Statement for student motivation.

d. Statement for gaining student attention.

e. Statement of the learning objectives.

f. Safety precautions and hazard awareness notices related to the lesson topic.

g. Review of materials previously presented and related to the new lesson topic.

h. Discussion points.

i. Instructional activities (e.g., lecture, discussion, demonstration, illustration, practice exercises, assignments, etc.).

j. Teaching points.

k. Application.

l. Procedures.

m. Evaluation.

n. Intermediate summaries as required.

o. Related instructor activities.

(1) Media cues.

(2) Helps.

(3) Questions.

(4) Answers to questions.

(5) Supporting papers.

p. Learning objectives data shall consist of the following:

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

(1) Learning objective number and type.

(2) The learning objective statement.

(3) The instructional method(s).

(4)…