N63394-23-R-0022_Exhibit A - DIDs.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

Source: https://assist.dla.mil -- Downloaded: 2022-06-01T00:12Z Check the source to verify that this is the current version before use.

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

DATA ITEM DESCRIPTION

Title: MEETING MINUTES

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

AMSC Number: F10264 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

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

Applicable Forms: N/A

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.

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.

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: 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 data reduction and analysis techniques that will be used to interpret the data.

4.8.11 Government or Contractor Test Facilities. Identify the specific Government or Contractor facilities used for each test. Identify Government or Contractor provided simulation capabilities needed for each test. Describe planned use of and requirements for range equipment including communication links and computer equipment.

4.8.12 Test Documentation: The test plan shall address development and delivery of the following as required:

• Test Description Document, Detailed Test Evaluation Plan, Pre-Test Analysis

Plan, Post-Test Analysis Board brief for each ground, flight and cyber test event.

• Detailed Test Plan, Data Management Plan and Detailed Test Design for each system test event.

• System Pre-Mission Test (SPMT) Test Plan, SPMT Report, System Post-Flight Reconstruction (SPFR) Test Plan, SPFR report, System Anomaly Response Plan, and Launch Commit Criteria for each system flight test.

• Certification Data Package for each applicable test.

• Quick Look Brief for each System flight, ground and cyber test. Quick Look Report for each System flight, ground and cyber test.

• Range Safety Data Package for each interceptor or boost vehicle flight test . Test Evaluation Report for each System test event.

End of DI-MGMT-82377

�. ���/%������ ��(#����0!��,�� ����1,�����#��!',2� ���345�3678936:;5<�=58>6?�@7<<�A5�BC5D�?>�65E>6D�?45�8B68>C5�>F�?45�?678G�>AC56;:?7>HCG�:HD�:HI�:88<7E:A<5�E>HE<BC7>HC�>6�65E>JJ5HD:?7>HC�A:C5D�B8>H�?45�8B68>C5K���347C�LML�E>H?:7HC�?45�F>6J:?�:HD�E>H?5H?�8658:6:?7>H�7HC?6BE?7>HC�F>6�?45�D:?:�86>DBE?�N5H56:?5D�AI�?45�C85E7F7E�:HD�D7CE65?5�?:CO�65PB765J5H?�:C�D5<7H5:?5D�7H�?45�E>H?6:E?K�� �Q������'�,���RK�S>6J:?K�345�3678936:;5<�=58>6?�C4:<<�A5�7H�E>H?6:E?>6�F>6J:?K��TK�U>H?5H?K�345�658>6?�C4:<<�E>H?:7H�?45�F><<>@7HNV�:K�W:J5�>F�5J8<>I55�AK�L:?5XCY�>F�?678�EK�Z7?5�;7C7?5D�DK�[B68>C5�>F�?678�5K�=5<5;:H?�>AC56;:?7>HC�DB67HN�?45�?678�FK�=5<5;:H?�E>HE<BC7>HC965E>JJ5HD:?7>HC�A:C5D�>H�?45�?678��\K�]HD�>F�LM̂_MZÛ R̀ab\K�� � � � � cdefghi�jkklminnommpmkqrsoqtps�uu�vdwxsdorhri�yzyyuz{uz|}~�iz{��jhg��kjh�mdefgh�kd��hfp���kjok�kjpm�pm�kjh�geffhxk��hfmpdx��h�dfh�emhq

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 contract.

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:

Number: DI-MGMT-81864A Approval Date: 20170313 AMSC Number: N9774 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Preparing Activity: SH Project Number: MGMT-2017-019

Use/Relationship: This report indicates the progress of work and the status of the program and of the assigned tasks, reports costs, identifies and informs of existing or potential problem areas.

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

2. This DID may be applied in any contract and during any program phase.

1.

2. General instructions. The Contracting Report shall describe work accomplished in terms of technical accomplishments and expenditure data for each project area/task/technical instruction funded under the contract.

3. Content. The Report shall contain a title page identifying the following:

a.

b. Name and telephone number of preparer of the report;

c. Contract number;

d. Nomenclature of the system or program;

e. Date of the report;

f. Period covered by the report;

g. The title of the report;

h. Either the serial number of the report or the Contract Data Requirements List (CDRL) sequence number;

i. The security classification;

j. The name of the issuing Government activity

3.1 The report shall also contain the following sections:

3.1.1 Section 1 Work Summary. A brief summary of all funded tasks/projects/technical instructions under the contract. The summary shall identify Task Order period (Base, Option 1, etc.) and shall include the following:

DI-MGMT-81864A

a. Project name;

b. TI number (if applicable);

c. Funded amount;

d. Expenditures to date;

e. Funding balance.

3.1.1.2 The report shall include tables that demonstrate:

a. Ceiling hours;

b. Funded hours;

c. Current and cumulative hours separately identifying regular hours from UT/TTA hours charged to the labor category for current and completed CLINs;

d. Subtotals for key and non-key categories.

3.1.2 Section 2 Invoice Information shall identify the following:

3.1.2.1 Direct labor. The report shall identify:

a. Current and cumulative expenditures (both labor hours and dollars) invoiced by Cost Center where charges originated;

b. Totals for current and cumulative invoiced amounts by cost center.

3.1.2.2 Indirects. The report shall identify:

a. Indirect rate being invoiced with applicable Cost Centers as well as current and cumulative dollar amounts by Cost Center;

b. Total current and cumulative indirect costs.

3.1.2.3 Subcontractors/Consultants. The report shall include copies of invoices received for current

3.1.2.4 Fixed Fee / Target Fee. The report shall specify:

a. Each fee rate applied, together with current and cumulative dollar amounts;

b. The based to which each fee rate was applied.

3.1.2.5 Other Direct Costs. The report shall include:

a. List of expenses by category (airfare, per diem, supplies, etc.);

b. Current and cumulative expenditures for each category.

3.1.2.6 Total Expenditures. The report shall include total expenditures compared to those invoiced for the same period and differences explained.

3.1.2.7 Current CLIN. The report shall identify the current CLIN being performed and its period of performance.

3.1.2.8 The report shall contain the current CLIN modifications and shall be listed by number, date issued and description.

3.1.2.9 The report shall include a table that identifies the following:

a. Technical instructions/funded projects/work areas by number (where applicable);

b. Date issued;

c. Description;

d. Amount funded;

e. Total expenditures;

f. Funding balance;

g. Total invoiced to date;

h. Grand total.

3.1.2.10 The report shall include a discussion of the contract-wide spend rates (fully burdened) compared to contract-wide bid rate averages (fully burdened). Any variation of actual-to-bid rate averages greater than 10% shall be addressed.

3.1.2.11 A table of approved personnel identifying labor category, key or non-key, individual's name, employer, location (on-site/off-site).

3.1.3 Section 3 Detailed Information by Project/Work Area/Technical Instruction. This section shall contain:

a. Description of the progress made against milestones during the reporting period.

Specifically address the value-added tasks performed by the prime contractor when work is performed by a subcontractor; clearly identify the key and non-key personnel performing the tasks described.

b. Identification of problem areas affecting technical, scheduling or costs elements, with background and any recommendations for solutions beyond the scope of the contract.

Specifically, address results, positive or negative, obtained related to previously-identified program areas, with conclusions and recommendations for solutions.

c. Whether the task is on schedule, ahead of schedule, or behind schedule. Discuss what steps are being or will be taken to complete all requirements on time if possible, or provide a proposed revised schedule based on best current estimates if behind schedule.

d. The status of all assigned deliverables, including title, CDRL number, due date, date delivered, Contractor point of contact and description or title of deliverable(s). The report for each contract period shall include a cumulative list of all deliverable items provided.

e. A table of approved personnel identifying labor category, key or non-key, individual's name, employer, fully burdened labor rate, location (on-site/off-site), date resume submitted, date resume approved, and date removed shall be included. If a resume was submitted as a replacement for a Key Person approved at time of award, the name of the individual being replaced shall also be provided.

f. Include current and cumulative expenditures of both hours and dollars. Separately show expenditures by CLIN and SubCLIN (labor and ODC). Identify the amount funded and compute a funding balance. Present the current and cumulative total percentage of ODCs to labor.

g. Include graphs showing cumulative expenditures of both hours and dollars. Line graphs shall show planned cumulative expenditures as well as cumulative funded level(s). Include numerical values for all points graphed; quantities of labor hours shall show rounded to the nearest hour.

h. Include the names of all personnel charging. Organize these data by labor category, fully burdened labor rate (e.g. fee and prime pass-through, where applicable), and show current and cumulative hours charged for each individual. Separately show uncompensated hours/total time accounting (TTA) hours worked (if applicable). Labor categories shall be identified as to whether they are key or non-key categories. Subtotals shall be provided for key and non-key categories as well as total current and cumulative hours. Provide average hourly rates (fully burdened) for each labor category. These data shall include subcontractor/consultant hours in appropriate labor categories.

i. Include spend rates compared to average bid rate averages. Any variation of actual-to-bid rate averages greater than 10% shall be addressed.

j. Identify all items charged. Include description of item, quantity, purpose, vendor, unit price, extended price and disposition.

k. Identify all travel direct-charted during the period, for each:

(1) Destination

(2) Purpose of trip

(3) Number of travelers

(4) Length of trip

(5) Estimated cost of the trip

l. Identify any new subcontractors approved during the reporting period and any proposed subcontractors/consultants for the next reporting period. Their capability set and areas of expertise shall be thoroughly addressed.

m. Record of significant telephone calls and any commitments made by telephone shall be included.

n. Plans and recommendations for activities during the next reporting period;

o. Appendixes for any necessary tables, references, photographs, illustrations, and charts.

End of DI-MGMT-81864A

Title: Funds and Man-Hours Expenditure Report

Number: DI-FNCL-80331A Approval Date: 30 OCT 2006 AMSC Number: 7618 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02

Use/relationship:

This report provides Government visibility into contractor expenditures for labor, materials, travel and other contract charges. It tracks these expenditures against baseline values, and provides to-completion estimates.

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

This DID is applicable to time and material, research and development and other contracts where use of Cost Performance Reporting (CPR) or Cost/Schedule Status Reporting (C/SSR) are not appropriate. It is not applicable on fixed-price contracts. It is acquired on a periodic basis.

It is not intended that all the requirements contained herein should be applied to every contract or program phase. Portions of this DID are subject to deletion tailoring depending on the management requirements of the solicitation/contract in which it is applied.

This DID is related to DI-A-5016, Project Planning/Actual Progress Chart (Other than fixed price contracts), and DI-FNCL-80003, Man-Hour Expenditure Chart.

This DID supersede DI-FNCL-80331.

1. Reference documents. None.

engineer shop, etc), burden/overhead, material/parts, travel, subsistence, fringe, DI-FNCL-80331A

2. General. The Funds and Man-Hours Expenditure Report shall contain the following data:

a. A tabular listing of funding and man-hour expenditures inclusive of the reporting period compared to original baseline values, including to-completion estimates.

b. A graphical plot of planned versus actual funding expenditures.

c. A graphical plot of planned and actual percentage of work completed.

3. Scope. Each task, job-order, sub-task, or unit of work will be separately addressed. If schedule or milestone reporting is also a reporting requirement under the contract; the breakdown of work task elements should be consistent with the reporting.

4. Format and Content. The report shall contain the following:

4.1 Funds and man-hour expenditure summary. This chart shall contain the following data elements (See Figure 1).

4.1.1 Original negotiated contract. A summary of all cost elements associated with the original negotiated contracts. This is defined as the contractor’s original cost proposal, as negotiated and accepted by the Government. It is that cost as it appears on the original contract document. Its elements shall contain the cost estimate breakdown by category (i.e., direct labor (Sr. Engineer, Jr Engineer, draftsman, General and Administration (G&A) fee, outstanding commitments, etc), as provided in the accepted proposal. Items and amounts specified in this entry shall remain constant on successive reports during the term of the contract.

4.1.2 Latest negotiated contract changes. A summary of the latest negotiated contract changes. It shall be a recapitulation of the 4.1.1 data elements reflecting all subsequent changes resulting for contract modifications. Breakdown by category shall be as provided in 4.1.1 unless altered by a contract modification. Indicated “none” if revised proposal has no effect.

4.1.3 Reporting period expenditures. Expenditure data for the current reporting period for the work task categories used in 4.1.1 or 4.1.2 (as applicable), and covering man hours, funds, and the change (new orders minus fulfilled orders) in outstanding commitments.

4.1.4 Cumulative expenditure to date. Cumulative man hour, funds and outstanding commitments expenditure data through the current reporting period for the work task categories used in 4.1.1 and 4.1.2 (as applicable). Additionally, show the cumulative costs as a percentage of the 4.1.1 of 4.1.2 costs.

4.1.5 Estimated cost-to-complete. The estimated costs required to complete the work task from the reporting date to the date of completion. This estimate shall be defined by categories as they appear in 4.1.1 of 4.1.2. All estimates shall be justified.

4.1.6 Latest cost estimate. An estimate of the final total cost at completion of the work effort. This is derived from 4.1.4 and 4.1.5. Deviations between the original contract and/or latest negotiated contract change shall be justified/explained in footnote remarks.

4.2 Funds expenditure graph. A funds expenditure graph shall be included. The graph shall be reproducible to enable periodic changes reflecting current contract funding status to be entered. The graph shall portray, on a periodic basis, the planned versus actual total dollar expenditures and the percentage of the total contract dollars that the expenditure represent (See Figure 2).

4.3 Work completed graph. A work completed graph shall be included that reflects the percentage of work completed by the contractor through the current reporting period.

The graph shall plot actual completion versus planned completion, and shall be maintained current and be fully legible and reproducible (See Figure 3).

5. END OF DI-FNCL-80331A

Title: CONTRACT STATUS REPORT

Number: DI-MGMT-81991 Approval Date: 20160119

AMSC Number: N9568 Limitation: N/A

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

Office of Primary Responsibility: SH Project Number: MGMT-2015-004

Use/Relationship: Contract Status Report provides the progress of work performed and the status of all program assigned tasks, cost and information and management of existing or potential problem areas.

This Data 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.

This DID supersedes DI-MGMT-81928.

1. Format. The Contract Status Report shall be in a format similar to that of Figures 1, 2, and 3 of this DID.

2. Content. The report shall contain a cover sheet identifying the following:

a. Title of the report

b. Contractor’s name and address

c. Contract Number

d. Date of report and period by the report

e. Data Item Number listed on the CDRL DD FORM 1423-1

2.1 The report shall include results positive and negative related to previously identified problem areas, with conclusions and recommendations.

2.2 The Report shall include an significant changes to the Contract’s organization, method of operation, and the project management network.

2.3 The report shall identify problem areas affecting cost elements, technical or scheduling elements, and shall in background and any recommendations for solutions beyond the scope of the contract for the following items:

a. Funding issues

(1) Shortfalls

(2) Overfunding

b. Task Area Issues

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

DI-MGMT-81991

2.4 The report shall contain cost curves showing actual projected conditions throughout the contract, any cost incurred for the reporting period and total contractual expenditures as of the reporting date.

2.5 The report shall contain Man-hours expended for the reporting period and cumulatively for the contract for the following areas:

a. Trip(s) outside the local area, site visited and purpose

b. Contract schedule status

c. Plans for activities during the following reporting period

d. Name and telephone number of signer of the report

e. Appendixes for any necessary tables, references, photographs, illustrations, and charts

2.6 The report shall contain all of the information specified in Figures 1, 2, and 3, and shall identify employee movement, color coded and highlighted in the comments column.

2.7 The report shall identify the following:

a. Title i.e.: Professional Support Services for the Program Executive Office (PEO)

Integrated Warfare System (IWS)

b. Contract Number

c. CLIN Number

d. Latest Contract Modification (# and Date)

e. Period of Performance

f. Reporting Period

g. Contractor’s POC

h. Government PM

i. Government COR

2.9 Financial/Labor Data. The report shall also include the following:

a. Contract Value

b. Funded to date

c. Cost of work performed during period (period to be defined as CY)

d. Planned travel for the upcoming Calendar Month to include location, number of contractor personnel and purpose

e. Actual: Monthly Hours Burned by each contractor/employee

f. Invoice Date/Amount/Number

3.0 Summary: The report shall contain a summary by Project, Work Area and Technical

Instruction.

3.1 A Description of the progress made during the reporting period, the value-added tasks performed by the prime contractor shall be specifically addressed, key and non-key personnel shall be clearly identified when work is performed by a subcontractor and key and non-key personnel performing the tasks shall be identified.

3.2 The status of all assigned deliverables, including title, CDRL number, due date, date delivered, Contractor point of contact and title of deliverable(s) shall be included.

3.3 The report for each contract period shall include a cumulative list of all deliverable items provided.

Task Sub-task Nr. Task Description Customer Name/Employee

Labor or ODCs (Fully

Burdened) Value Funded to Date

Funding

Required to End of CY

(Cost)

Required to End of CY

(Fixed Fee)

Required to

End of CY

(Total)

ACTUAL: Mthly

Hours Burned Invoice Number Invoiced Amount Invoiced To Date

Date Sub-contractor invoice approved by Corp

Recent Actual

Payments to Sub-

Contractor

Red indicates costs have exceeded funding

Yellow indicates costs are close to exceeding funding.

1.1 1.1.1

NMCI, NAVSEA CIO and Enterprise primary coordinator Jane Doe Labor

ODCs

1.1.2 Assist in Strategic Planning John Smith Labor

1.1.3 Portfolio Management. John Doe Labor

3.1 3.1.1 ACTD Operations Specialist support John Doe Labor

Totals

FINANCIAL/LABOR HOUR DATA BY TASK- FIGURE 1

WORK COMPLETED BY TASK

CLIN/SLIN ACRN PR Number Ref Doc/ACRN MOD Appropriation Subhead OBJ PARM RFM AAA TT PPA Project Unit Funded Expended Balance

Totals $ - $ - $ -

Grand Totals $ - $ - $ -

WORK COMPLETED BY CLIN/SLIN - FIGURE 2

STAFFING PLAN - FIGURE 3

NAME/EMPLOYEE LABOR TASK AREA CONTRACTOR / COMPANY GOVERNMENT FTE HOURS COMMENT

CATEGORY SUPPORTED SUBCONTRACTOR NAME SITE

Task 1 -

Task 2 -

Task3 -IWS Technical - Provide Support to PEO IWS Advanced Technology

End of DI-MGMT-81991

Title: CONTRACTOR HAZARDOUS MATERIAL INVENTORY REPORT

Number: DI-ENVR-82091 Approval Date: 20161208

AMSC Number: N9751 Limitation: N /A

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.

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

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.