AM Metals Printer and Materials Qual RSO Gen Instructions and CDRL Packet.pdf

CONTRACT DATA REQUIREMENTS LIST

(CDRL)

GENERAL INSTRUCTIONS

FOR THE

Rapid Sustainment Office (RSO)

AM Metals Printer & Materials Qualification

Dated:

7 June 2023

Contract Number:

FA8684-XX-X-XXXX

PREPARED BY:

RAPID SUSTAINMENT OFFICE – AFLCMC/RO

WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-7249

CDRL MODIFICATION MATRIX

This matrix identifies the CDRL changes as implemented by contract modification.

PROPOSAL NO. CDRL REV

DATE CDRLS/PAGES REVISED

Contract Award Original June 2023 RSO General Instructions and CDRL

TABLE OF CONTENT

Table of Contents

No table of contents entries found.

1.0 SCOPE

2.0 REFERENCE DOCUMENTS

3.0 DATA DELIVERABLES

3.1 Delivery Dates

3.2 Tailored Data items

3.3 Approval of Data

3.4 Resubmittal of Data

3.5 Final Submittal of Data

3.6 DD Form 250 Requirements

3.7 Classified Data

4.0 ELECTRONIC DATA TRANSMISSION

4.1 Submission

4.2 Delivery Non-Compliance

4.3 Financial Information Format

5.0 LETTERS OF TRANSMITTAL (LT)

6.0 COMMON ABBREVIATIONS

7.0 MARKING DOCUMENTATION

7.1 Distribution Marking System

7.2 Marking Technical Data

7.3 Distribution Statements

7.4 Controlling Office

7.5 Export Control Warning

7.6 Destruction Notice

7.7 Classified Information

7.8 Controlled Unclassified Information

7.9 Marking Non-Technical Documentation

7.10 Marking Example

7.11 Intellectual Property Marking

8.0 MAILING LISTS

9.0 REFERENCE DOCUMENTS

10.0 ACRONYMS

1.0 SCOPE

The Contract Data Requirements List (CDRL) establishes the data to be delivered by the contractor, including the submittal, approval and distribution requirements. This document provides instructions and clarifications which apply to all of the CDRLs within the applicable contract, unless otherwise noted. CDRLs are accomplished on DD Form 1423-1.

2.0 REFERENCE DOCUMENTS

32 C.F.R. §117.15 National Industrial Security Program Operating Manual

(NIPSCOM)

DoDD 5230.25 Withholding of Unclassified Technical Data From Public Disclosure

DoD 5010.12-M Procedures for the Acquisition and Management of Technical Data

DoDI 5230.24 Distribution Statements on Technical Documents DoDM 5200.01 DoD Information Security Program: Protection:

Overview, Classification, and Declassification DoDI 5200.48 Controlled Unclassified Information (CUI) EIA 649-1 Configuration Management Requirements for Defense

Contracts DAFI 61-201 Management of Scientific and Technical Information

(STINFO)

DoDD 5230.9 Clearance of DoD Information for Public Release DoD 5400.7-R DoD Freedom of Information Act Program DoD 5220.22-M National Industrial Security Program Operating Manual DFARS 227.71 Rights to Technical Data DFARS 227.72 Right to Computer Software & Computer Software

Documentation

3.0 DATA DELIVERIES

The CDRL establishes the data to be delivered by the contractor. The CDRL also identifies the submittal, inspection, approval, acceptance, and distribution requirements of all the CDRL data items contained herein.

3.1 Delivery Dates

In the event a CDRL delivery date falls on a Saturday or Sunday, the delivery will be made by the next business day to be counted as an on-time delivery. Unless otherwise specified in Block 16 of the CDRL.

3.2 Tailored Data Items

Tailoring instructions are as described in Block 16 of each effected CDRL. If the data preparation instructions or requirements contained in Block 16 of the CDRL are different than the DID, the CDRL Block 16 shall govern.

3.3 Approval of Data

a. An "A" designator in Block 8 of the CDRL indicates the government will respond 30 calendar days, unless otherwise specified on the CDRL, Block 16.

b. In the event the Government requires additional time to review a CDRL, the Contracting Officer will notify the contactor via e-mail specifying a date. The Contractor shall not assume a CDRL is approved if the Government does not respond.

c. For those CDRLs with an "N/A" in Block 8, government approval of the content is not required; however, compliance with data item format and content requirements as specified in the DID, and as tailored in Block 16 of the CDRL, is mandatory. However, the government may not provide a formal response back to the contractor. The government has the right to reject/disapprove any data submittal(s) not in compliance with contract requirements. There are two (2) types of Government Disposition for Non-Approval Data Items:

1) Unacceptable – substantial and/or critical comments--identified as noncompliant a Contracting Officer will request revision submittal date.

2) Acceptable – administrative or no changes.

3.4 Re-submittal of Data

If re-submittal of a CDRL is required, it shall be re-submitted within 30 calendar days after CO notification, unless otherwise specified. Should the contractor disagree with the re-submittal requirements, they shall submit their comments to the CO within 30 calendar days of notification. Each page of a re-submittal shall have changes indicated by a vertical line down the outer right margin designating those areas that have been revised.

The document revision shall be indicated on the title page of the data item, each page, and a summary of document changes section contained within the document.

3.5 Final Submittal of Data

For the final delivery of each data item in the contract or delivery order, the contractor shall clearly state in the letter of transmittal (LOT), as defined in paragraph 5.0, when it is the last submittal being made, and that all contractual requirements concerning that data item have been fulfilled.

3.6 DD Form 250 Requirements

Block 7 of the CDRL directs the inspection and acceptance of the submittal. Individual DD Form 250s are required only if indicated in Block 7. All other submittals shall be accompanied by a Letter of Transmittal (LOT).

3.7 Classified Data

Classified data shall be submitted in accordance with the requirements established by the DD Form 254. The contractor shall contact the CO for the mailing addresses for classified data.

4.0 ELECTRONIC DATA TRANSMISSION

4.1 Submission

a. The contractor shall submit all data deliverables in accordance with the specific submittal instructions indicated in Block 16 of each CDRL. The versions of the software used shall remain compatible with current program office software. Any submittals by other means shall require program office approval prior to delivery of data. Data to be submitted by Electronic Data Transmission (EDT) shall be identified in “Block 14.b. Copies, Final, Repro” of the CDRL

b. Electronic Delivery includes delivery or availability of data files via Government-approved website, web page, server, or via attachment of electronic files, as mutually agreed to between the Government and the contractor. Electronic data delivery and access is subject to Government protection and security requirements.

NOTE: The contractor and their sub-contractors shall not use special characters in the document filename with the following exceptions: dash or an underscore.

4.2 Delivery Non-Compliance

The contractor shall inform the program office if any of their data deliverables cannot comply with the required electronic formats. In such cases the contractor shall recommend, for program office approval, an alternative delivery format(s).

4.3 Financial Information Format

Financial information provided in Excel spreadsheets should be able to be manipulated.

5.0 LETTERS OF TRANSMITTAL (LOT)

All data deliveries shall include a LOT. The LT may be in the form of a letter or e-mail from the designated contractor representative. At a minimum, the LOT shall contain:

Contractor Point of Contact (POC) Contractor address Date Contract number and program name Letter control number Document control number Document revision level Document date CDRL sequence number DID Number Data Title/Subtitle Reason or frequency of submittal (monthly, draft, final, update, etc.)

b. If a paper copy of the LOT is prepared, a complete list of addressees shall be placed at the end of the LOT, annotating the recipients (as identified on the DD Forms 1423, Block 14) including the transmittal-letter-only recipients.

c. If submittal is made via e-mail, the list of addressees in the “TO” line shall include the complete list of addressees and shall be considered sufficient.

6.0 COMMON ABBREVIATIONS

Table: Common Abbreviations Block 8: A Approval

N/A Approval Not Required BLK16 See Block 16 for further instructions

Blocks 10, 11, 12, and 13 ANNLY Annually ASREQ As Required BLK16 See Block 16 for further instructions MTHLY Monthly N/A Not Applicable QTRLY Quarterly xx DAC xx Days after Contract Award

7.0 MARKING DOCUMENTATION

7.1 Distribution Marking System:

a. In accordance with Section 1.30 of Title 10, “United States Code” a DoD distribution marking system for technical data has been established by DoD Instruction 5230.24, “Distribution Statements on Technical Documents.” The intent of the system is to stem the flow of military-related technical data to our adversaries, without inhibiting technological growth or blocking the exchange of technical data that is vital to progress and innovation. The contractor shall mark all distribution statements and export-control statements, supplemental to any security markings, on all technical data to denote the extent of its availability for secondary distribution, release, and disclosure without need for additional approvals and authorizations from the controlling DoD office.

b. Required distribution statements are annotated in Block 9 of each CDRL. If the contractor feels that a different statement is required, it must notify the contracting officer with the recommended statement. The Government will review the request and determine which statement is the most appropriate and provide the contractor with an acceptance of the change or reason for not accepting the contractor’s request for change.

7.2 Marking Technical Data

a. The contractor shall mark all requested technical information, regardless of its medium, with a distribution statement. This includes technical reports, blueprints, drawings, technical orders, technical manuals, plans, instructions, computer software, viewgraphs, film, technical papers, photographs, etc. If the document contains export-controlled technical data, it also must be marked with an export control warning statement. Distribution statements can be applied to technical data that contain or reveal proprietary information used.

b. Technical data categorized as cryptographic/communications security, communications/electronic intelligence, and similar categories as may be designated by the Director, National Security Agency, whose distribution is limited through alternate methods, are exempt from these marking provisions.

c. The contractor shall mark Controlled Unclassified Information (CUI) in accordance with DoDI 5200.48, paragraph 3.4.

7.3 Distribution Statements

Table: Distribution Statement Summary

DFARS Subparts 227.71 and 227.72 stipulate control procedures for contractor controlled technical information in which the Government has limited rights. These procedures shall be followed as described in DoDI 5230.24.

7.4 Controlling Office

The following address will be used on all documentation for the “controlling DoD office” for this program:

DISTRIBUTION STATEMENT A: Approved for public release. Distribution is unlimited.

DISTRIBUTION STATEMENT B: Distribution authorized to U.S. Government agencies only (fill in reason) (date of contract award). Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (fill in reason) (date of contract award). Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only (fill in reason) (date of contract award).

Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT E: Distribution authorized to DoD Components only (fill in reason) (date of contract award). Other requests for this document shall be referred to (insert controlling DoD office).

DISTRIBUTION STATEMENT F: Further dissemination only as directed by (insert controlling DoD office) (date of contract award)) or higher DoD authority.

AFLCMC/RO

Rapid Sustainment Office (RSO) 1865 4th Street Bldg 14, Room 032

WPAFB, OH 45433

7.5 Export Control Warning

Authority to withhold and control the export of certain technical data with military or space application is determined in accordance with Title 10, United States Code section 130, “Authority to withhold from public disclosure certain technical data”, and implemented by DoDD 5230.25, if such data may not be exported lawfully outside the United States without an approval, authorization, or license under the Export Administration Act of 1979 or the Arms Export Control Act (both cited in the Export Control Warning). Such withholding and export control applies to Defense items listed in the United States Munitions List (USML), (which is part of the “International Traffic in Arms Regulations (ITAR),”—22 CFR 120-130); and 15 CFR 730-774 (the “Export Administration Regulations (EAR)”).

If a technical document, whether printed or electronic/digital, contains export-controlled technical data, it shall be marked with the export control warning statement prescribed in DoDI 5230.24 and shown below. When it is not feasible to use the entire statement, the abbreviated warning may be used, and a copy of the full warning added to the “Notice to Accompany the Dissemination of Export-Controlled Technical Data,” which is Enclosure E5 of DoDD 5230.25. For assistance in determining what is export controlled, consult the controlling DoD office. The warning notice may be used in conjunction with distribution statements B, C, D, E, and F. Distribution statement A, which denotes public release, cannot be used in conjunction with the export-control warning notice.

7.6 Destruction Notice

All unclassified technical data marked with distribution statements B, C, D, E or F shall be marked with the following Destruction Notice:

"WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C. App. 2401, et seq.), as amended.

Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with the provisions of DoDD 5230.25.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Classified data, including classified controlled technical data, shall be handled and destroyed in accordance with the procedures in DoDM 5200.01, Volume 3_AFMAN 16- 1404, Volume 3 and DoDM 5220.22_AFMAN 16-1406 Volume 2.

Destruction Notice for classified technical information:

DESTRUCTION NOTICE: Follow the procedures in DoDM 5200.01, Volume 3_AFMAN 16-1404, Volume 3, Information Security Program: Protection of Classified Information and DoDM 5220.22_AFMAN 16-1406, Volume 2, National Industrial Security Program: Industrial Security Procedures for Government Activities.

7.7 Classified Information

Documents containing classified information will be marked in accordance with DoDM 5200.01, Volume 2, “DoD Information Security Program: Marking of Information”.

7.8 Controlled Unclassified Information (CUI)

Unclassified information associated with a law, regulation, or government-wide policy and identified as needing safeguarding is considered CUI. CUI requires access control, handling, marking, dissemination controls, and other protective measures for safeguarding. Per DoDI 5200.48, mark these documents with “Controlled Unclassified Information (CUI)” or at a minimum “CUI” at the top and bottom of each page. Include a CUI Designation Indicator on the bottom right of the first page of CUI documents as shown below:

Line 1: Name of the DoD Component Line 2: Identification of the office creating the document Line 3: Identification of the categories contained in the document--see DoD CUI Registry for applicable category (multiple categories can be listed, if applicable) Line 4: Distribution Statement Line 5: Name, phone number or email of POC

When CUI is comingled with classified information, mark and protect classified materials according to DoDM 5200.01, Volumes 1-3_AFMAN 16-1404, Volumes 1-3.

7.9 Marking Non-Technical Documentation

Non-technical documentation that is associated with a law, regulation, or government-wide policy, and identified as needing safeguarding, is considered CUI and must be marked as such. Distribution statements are not used on non-technical documentation;

however, a Limited Dissemination Control (LDC) will apply in most cases. Contact the program office to make this determination. Reference the following link for a current listing:

CUI Registry: Limited Dissemination Controls | National Archives

Some examples of CUI categories that may pertain to non-technical data include:

General Proprietary Business Information, General Procurement and Acquisition, and Source Selection. A complete CUI Registry list of CUI categories can be found at:

https://www.dodcui.mil/Home/DoD-CUI-Registry/

Per DoDI 5200.48, mark these documents with “Controlled Unclassified Information (CUI)” or at a minimum “CUI” at the top and bottom of each page. Include a CUI Designation Indicator on the bottom right of the first page of CUI documents, as follows:

Line 1: Name of the DoD Component Line 2: Identification of the office creating the document Line 3: Identification of the categories contained in the document--see DoD CUI Registry for applicable category (multiple categories can be listed, if applicable) Line 4: For non-technical documentation enter either N/A or the appropriate LDC Line 5: Name, phone number or email of POC

CUI must be marked with the following Destruction Notice:

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

7.10 Marking Examples

The marking examples below are for reference. Specific information within the distribution statements and the CUI Designation Indicator will depend upon each individual case.

Marking example for non-technical CUI:

Destruction Notice for Controlled Unclassified Information (CUI)

DESTRUCTION NOTICE—Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

CUI Mark Top of Page https://www.archives.gov/cui/registry/limited-dissemination https://www.dodcui.mil/Home/DoD-CUI-Registry/

Marking example for technical CUI:

Marking example for export-controlled technical CUI:

Controlled by: USAF/AFMC Controlled by: AFLCMC/XXXX CUI Category: General Proprietary Business Information Distribution Statement: IAW DoDI

5200.48 Limited Dissemination

Controls are mandatory for non-technical CUI.

POC: Gov POC name and email

CUI Designation Indicator IAW DoDI 5200.48, 6 Mar 2020

CUI

Mark Bottom of Page

Complete DoDI 5230.24 Distribution Statement

Destruction Notice for Controlled Unclassified Information (CUI)

DISTRIBUTION STATEMENT E. Distribution authorized to DoD components only; Administrative or Operational Use; 27 August 2021. Other requests for this document shall be referred to AFLCMC/XXXX, Gov address.

Controlled by: USAF/AFMC

Controlled by AFLCMC/XXXX CUI Category: Controlled Technical Information Distribution Statement: E POC: Gov POC name and email

CUI Designation Indicator IAW DoDI 5200.48, 6 Mar

7.11 Intellectual Property/Marking

Any markings that are added to documents for review purposes must be removed prior to formal submittal. If a document still requires a marking (i.e., proprietary) not addressed in the contract, the contractor must provide a justification for the marking.

8.0 MAILING LISTS

The Government will provide the following information for each recipient identified in Block 14: mailing address, office symbol, and point of contact e-mail address.

Mailing Address Office Symbol Point of Contact

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C. App. 2401, et seq.), as amended.

Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with the provisions of DoDD 5230.25.

Complete DoDI 5230.24 Distribution Statement

Destruction Notice for Controlled Unclassified Information (CUI)

DISTRIBUTION STATEMENT E. Distribution authorized to DoD components only; Administrative or Operational Use; 27 August 2021. Other requests for this document shall be referred to AFLCMC/XXXX, Gov address.

Controlled by: USAF/AFMC Controlled by AFLCMC/XXXX CUI Category: Controlled Technical Information Distribution Statement: E POC: Gov POC name and email

CUI Designation Indicator IAW DoDI 5200.48, 6 Mar

DODI 5230.24 Export Control Warning

Brianne Guy

AFLCMC/RO(RSO)

Rapid Sustainment Office 1865 4th Street Bldg 14

WPAFB, OH 45433-7126

AFLCMC/RO brianne.guy@us.af.mil

Configuration/Data Manager

AFLCMC/RO(RSO)

Rapid Sustainment Office 1865 4th Street Bldg 14

WPAFB, OH 45433-7126

AFLCMC/RO AFLCMC.RO.ConfigMgmt@us.af.mil

9.0 ACRONYMS

CDRL Contract Data Requirements List CUI Controlled Unclassified Information DID Data Item Description EAR Export Administration Regulations ITAR International Traffic in Arms Regulations LDC Limited Dissemination Control LOT Letter of Transmittal PCO Procuring Contracting Officer POC Point of Contact mailto:brianne.guy@us.af.mil mailto:AFLCMC.RO.ConfigMgmt@us.af.mil

6/8/2023 12:37:14 PM CDT CDRL Table of Contents AM Metals Printer & Material Qualification

CONTRACT #:

CONTRACTOR: TBD

SET NAME: Experimental Purposes- AM SYSTEM ITEM:

PROGRAM: AFLCMC-RO

DATA ITEM REQUIRING OFFICE AUTHORITY/TITLE/SUBTITLE SOW PARAGRAPH

A001 AFLCMC/RO Di-MISC-80508B/T Sow Para: 3.1.c, 3.1.d, 3.1.f, 3.1.g, Technical Reports / Study Services 3.1.h, 3.1.i, 3.1.m

N/A

A002 AFLCMC/RO Di-SESS - 81704/T 3.1.E

Test Plan / Test Procedures

N/A

A003 AFLCMC/RO DI-MGMT-81605 SOW Para: 3.1.J, 3.1K, 3.1.L, 3.1.N

Briefing Materials

N/A

A004 AFLCMC/RO DI-MISC-80048 Sow Para: 3.1.N

Scientific & Technical Reports Summary

N/A

A005 AFLCMC/RO DI-ILSS-80872 SOW Para: 3.1.L

Training Materials

N/A

A006 AFLCMC/RO DI-MGMT-81861C SOW Para: 3.3

Integrated Program Management Data & Analysis Report

IMS

A007 AFLCMC/RO DI-ADMIN-81250C SOW Para: 3.3

Meeting Minutes

N/A

A008 AFLCMC/RO DI-MGMT-80934C SOW Para: 3.6

OPSEC Plan

N/A

A009 AFLCMC/RO DI-MGMT-80368A SOW Para: 3.3

Status Report

N/A

A010 AFLCMC/RO DI-MGMT-82001A SOW Para: 3.4

Risk Management Framework

RMF

AM Metals Printer & Material Qualification

(1 Data Item)

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER OTHER

D. SYSTEM/ITEM

Metals Printer / Material

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Technical Reports / Study Services

3. SUBTITLE

N/A

4. AUTHORITY (Data Acquisition Document No.)

Di-MISC-80508B/T

5. CONTRACT REFERENCE

Sow Para: 3.1.c, 3.1.d, 3.1.f, 3.1.g, 3.1.h, 3.1.i, 3.1.m

6. REQUIRING OFFICE

AFLCMC/RO

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK 16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

BLK 4: This DID is tailored as follows: Government RSO Test Plan Template format for reports.

BLK. 9: (1) DISTRIBUTION STATEMENT C: Distribution authorized to the Department of Defense and U.S. DoD contractors only for administrative or operational use. Other requests shall be referred to the Rapid Sustainment Office (RSO)

(2) DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

(3) RESTRICTED MARKINGS: There should be no restrictive markings, such as "limited," "Government Purpose," "proprietary," or "Intellectual Property" on the documents unless the contractor has asserted these rights through a formal list agreed to upon contract award.

The Contractor shall submit reports for each as follows:

Para 3.1.C - AM Processes: Draft submission NLT 120 calendar days after Contract award, Final submission NLT 180 calendar days after Contract award.

Para 3.1.D - Establishment of Limits for Printable Feature Angles:

Draft submission NLT 120 calendar days after Contract award. Final submission NLT 180 calendar days after Contract award.

Para 3.1.F - Powder Characterization & Specification- Draft submission NLT 270 calendar days after Contract award. Final submission NLT 365 calendar days after Contract award.

Para 3.1.G - Mechanical Properties - Draft submittal NLT 120 calendar days prior to the end of the base year contract Period of Performance (PoP). Final submission NLT 60 calendar days prior to the end of the base year Contract Period of Performance (PoP).

Para 3.1.H - Material Specification - Draft submission NLT 90 calendar days prior to the end of the base year Contract Period of Performance (PoP). Final submission NLT 30 calendar days prior to the end of the base year Contract Period of Performance (PoP).

Para 3.1.I - Operating Procedures Specifications - Draft submissions NLT 60 calendar days prior to the end of the base year Contract Period of Performance (PoP). Final submission NLT 30 calendar days prior to the end of the base year Contract Period of Performance (PoP).

Para 3.1.M - Validate Technologies - Draft submission NLT 90 calendar days prior to the end of the base year Contract Period of Performance (PoP). Final submission NLT 30 calendar days prior to the end of the base year Contract Period of Performance.

AFLCMC/RO (CM) 1 1

AFLCMC/RO (PM) 1 1

15. TOTAL 2 2 0

G. PREPARED BY

dorton.harry.e.jr.1076051670

H. DATE

2023/06/06

I. APPROVED BY J. DATE

18. ESTIMATED

TOTAL PRICE

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 1 of 1 Pages

17. PRICE GROUP

[Capability] Test Report

Prepared for:

Department of the Air Force

Contract No. [XXXXX-xxxxx]

Document Number:

Version:

Date:

ii

CHANGE HISTORY

DOCUMENT CHANGE HISTORY

VERSION CHANGE DESCRIPTION (Required for changes affecting Requirements, Configuration, Cost & Schedule)

No. Date Section Narrative (of items affected) Author iii

TABLE OF CONTENTS

1 Executive Summary

1.1 Background

1.2 Purpose

1.3 Project Overview

2 Referenced Documents

3 Project Classification

4 System Under Test

4.1 Software Items

4.2 Hardware Items

4.3 Firmware Items

4.4 Other Test Items

5 Test Resources

5.1 Key Test Personnel

5.2 Test Data

5.3 Test Equipment

5.4 Test Location(s)

6 Overview of Test Objectives/Methodology

6.1 Test Objectives

6.2 Test Execution Schedule

7 Test Data/Results

7.1 Overview and Results

7.1.1 Test Objective

7.1.1.1.1 Test Overview

7.1.1.2 Test Results

7.1.1.2.1 Observations or Discussions

7.1.1.3 Conclusion

8 Conclusions and Recommendations

8.1 Conclusions

8.2 Recommendations

8.3 Deficiencies

9 Acronyms and Abbreviations

Appendix A DETAILED METHOD OF TEST iv

LIST OF TABLES

Table 1: Referenced Documents

Table 2: Key Test Personnel

Table 3: Acronyms and Abbreviations

LIST OF FIGURES

No table of figures entries found.

1 Executive Summary

[This section is used to give a high level overview of the Test Report. When writing this section, a reader should be able to understand what happened during test and any conclusions that were made without having to read the rest of the document. Think briefing a General.]

1.1 Background

[Provide context about the system under test and relevant information about any related systems.]

1.2 Purpose

[This section shall explain the purpose for writing this Test Report. This section should include a summary of any previous testing. Consider the following: Is the testing a milestone, deliverable, end of project evaluation, or user acceptance of system?]

1.3 Project Overview

[This section shall provide a brief overview of the system to be tested. Generally, this is a high level overview of the project taken from proposals or contract.]

2 Referenced Documents [Table 1 identifies all referenced documents utilized within this Test Report.]

Table 1: Referenced Documents

Document Name Version Date

3 Project Classification [This section is to describe the type of project being executed. Is it an IT system, and if so, what kind of IT system?]

4 System Under Test

[This section shall describe the Item(s) tested (system under test). A clear understanding of the conditions under which the test was conducted must be stated. The goal of this section is to take what is listed here and be able to reproduce the environment in which testing occurred.]

4.1 Software Items

[This section shall describe the software that was tested. List all software including Operating systems, patches, browsers and software you intend to install for testing. The section goal is to take what is listed here and be able to reproduce the environment in which testing occurred. If there are no software items were tested, enter N/A for this section.]

4.2 Hardware Items

[This section shall describe the requirements for the hardware environment (platform, communications, configurations, etc.). List computer models and brands. The section goal is to take what is listed here and be able to reproduce the environment in which testing occurred. If there are no hardware items required, enter N/A for this section.]

4.3 Firmware Items

[This section shall describe the requirements for the firmware. The section goal is to take what is listed here and be able to reproduce the environment in which testing occurred. If there are no firmware items required, enter N/A for this section.]

4.4 Other Test Items

[This section shall describe the requirements any other test items that are required. The section goal is to take what is listed here and be able to reproduce the environment in which testing occurred. If there are no other items required, enter N/A for this section.]

5 Test Resources [This section shall describe any data, equipment and locations used during the testing. It will also detail the staff members who were involved in the test and what their roles are. Any deviations from the Test Plan should be noted.]

5.1 Key Test Personnel

Table 2: Key Test Personnel

Role Title/Rank Name Organization Phone Email

5.2 Test Data

[This section shall describe any required data resources used for testing.]

5.3 Test Equipment

[This section shall describe any required equipment used for testing.]

5.4 Test Location(s)

[This section shall describe any facilities or locations that were used for testing.]

6 Overview of Test Objectives/Methodology

6.1 Test Objectives

[A Summary of test objectives should be stated here. Be sure to mention each objective separately and concisely.]

6.2 Test Execution Schedule

[A Schedule of testing events should be documented here. Recommendation is to use a table format.

List all days that testing occurred with descriptions of testing that was completed on that day.List any deviations from the original Test Plan Schedule]

7 Test Data/Results

7.1 Overview and Results

7.1.1 Test Objective

[This section shall describe the planned objectives of the test event.]

7.1.1.1 Test Overview

[This section shall describe the quality and effectiveness of the testing in relation to the Test Objectives. It should cover the planned activities and any changes to those, especially areas in which effort exceeded planned effort. Include reasons for the variances and possible impacts. ]

7.1.1.2 Test Results

[This section shall report on overall testing success and issues identified during test. This section should include the Detailed Method of Test (DMOT) with results. If DMOT exceeds 1 page in length, the information should be presented in an Appendix. See Appendix A.

Items for consideration in this section:

Total number of tests

• Passed

• Failed

Total Issues

• by severity and priority

Defect Patterns

Unresolved issues]

7.1.1.2.1 Observations or Discussions

[This section should describe any observations noted during test and any discussions about test that occurred during the test.]

7.1.1.3 Conclusion

[This section will provide a brief description of any conclusions made during testing.]

[Repeat sections 7.1.1 – 7.1.1.31 for each objective.]

8 Conclusions and Recommendations

8.1 Conclusions

[This section should be an objective summary of the overall quality based on section 7 It should include any impacts to next milestones or follow on work.]

8.2 Recommendations

[Based on section 7 any recommendations for further testing or impact resolutions should be detailed here.]

8.3 Deficiencies

[This section should have a complete listing with details of issues reported during test. Include issue details or attach issue report to document for reference.]

9 Acronyms and Abbreviations [This section shall list and write out full terminology of acronyms and abbreviations used within the Test Plan.]

Table 3: Acronyms and Abbreviations

Acronym/Abbreviation Definition

Appendix A DETAILED METHOD OF TEST

1.0 [Test Approach Title]

# Test Point / Description Method Expected Test Result Remarks

1.1

[Insert title of test point and description]

[Insert detailed method of test / test procedures.

Specify test set up and procedures (refer to maintenance manuals, instructions, Standard Operating Procedures (SOP), or other publications whenever possible) and data collection techniques.]

[Insert expected test result] [Discuss any specific configurations desired or required for the test. Define equipment/data requirements (e.g.

camera, measuring devices, etc.) and specific test point go/no-go criteria.]

Evaluation Issue Identified Issue Resolution Actual Test Result

Evaluation Satisfactory Marginal Poor

No Yes

High Medium Low Enhancement

Comments:

(1 Data Item)

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP TM OTHER OTHER

D. SYSTEM/ITEM

Metals Printer / Material

E. CONTRACT/PR NO. F. CONTRACTOR

TBD

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Test Plan / Test Procedures

3. SUBTITLE

N/A

4. AUTHORITY (Data Acquisition Document No.)

Di-SESS - 81704/T

5. CONTRACT REFERENCE

3.1.E

6. REQUIRING OFFICE

AFLCMC/RO

7. DD 250 REQ

LT

9. DIST STATEMENT

REQUIRED

C

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK 16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

BLK 4: This DID is Tailored as follows: Government RSO Test Report Templates provided

BLK. 9: (1) DISTRIBUTION STATEMENT C: Distribution authorized to the Department of Defense and U.S. DoD contractors only for administrative or operational use. Other requests shall be referred to the Rapid Sustainment Office (RSO)

(2) DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

(3) RESTRICTED MARKINGS: There should be no restrictive markings, such as "limited," "Government Purpose," "proprietary," or "Intellectual Property" on the documents unless the contractor has asserted these rights through a formal list agreed to upon contract award.

BLKs 10,11,12 &13:

The Contractor shall deliver Draft submission NLT 45 days prior to start of planned testing. Final submission NLT 15 calendar days prior to start of planned testing.

AFLCMC/RO (CM) 1 1

AFLCMC/RO (PM) 1 1

15. TOTAL 2 2 0

G. PREPARED BY

dorton.harry.e.jr.1076051670

H. DATE

2023/06/06

I. APPROVED BY J. DATE

18. ESTIMATED

TOTAL PRICE

Him, Test Plan

Prepared for:

Department of the Air Force

Contract No. [XXXXX-xxxxx]

Test Plan

Executive Summary [This section should be limited to one page. Include a short background, and project purpose. This section is used to give a high level overview of the Project. When writing this section, a reader should be able to broadly understand what will take place during test.. Think briefing a General.]

CHANGE HISTORY

DOCUMENT CHANGE HISTORY

VERSION CHANGE DESCRIPTION (Required for changes affecting Requirements, TABLE OF CONTENTS

1 Introduction

1.1 Background

1.2 Purpose

1.3 Project Overview

2 Referenced Documents

3 Project Classification

4 Test Item Description

4.1 Software Items

4.2 Hardware Items

4.3 Firmware Items

4.4 Other Test Items

5 Test Resources

5.1 Key Test Personnel

5.2 Test Data

5.3 Test Equipment

5.4 Test Location(s)

6 Test Approach

6.1 General Information

6.1.1 Test Objectives

6.1.2 Test Methodology

6.1.2.1 [Test Approach 1]

6.1.2.2 [Test Approach 2]

6.1.3 Success Criteria

6.1.4 Evaluation Criteria

6.1.5 Data Requirements

6.1.6 Data Analysis Plan

6.1.7 Issue Tracking

7 Test Safety

8 Security

9 Readiness Review

10 Risks and Assumption s

11 Requirements Traceability

12 Test Schedule

13 Acronyms and Abbreviations v

LIST OF TABLES

Table 1: Referenced Documents

Table 2: Key Test Personnel

Table 3: Readiness Review

Table 4: Requirements Traceability

Table 5: Acronyms and Abbreviations

1 Introduction

[This section is used to give a high level overview of the Test Plan. When writing this section, a reader should be able to understand what will be tested.]

1.1 Background

[Provide context about the system under test and relevant information about any related systems.]

1.2 Purpose

[This section shall explain the purpose for writing this Test Plan. This section should include a summary of any previous testing. Consider the following: Is the testing a milestone, deliverable, end of project evaluation, or user acceptance of system?]

1.3 Project Overview

[This section shall provide a brief overview of the system to be tested. Generally, this is a high level

2 Referenced Documents [Table 1 identifies all referenced documents utilized within this Test Plan. Documents such as contracts and any relevant technical documents should be listed here]

Table 1: Referenced Documents

Document Name Version Date

Issue Tracking Form v1.0 1 8/4/2020

Test Hazard Analysis 1 8/23/2021

3 Project Classification

[This section is to describe the type of project being executed. Is it an IT system / manufacturing / printing etc…? If so, what kind of IT system?]

4 Test Item Description

[This section shall describe the Items that will be tested. In order for each test to be properly conducted, a clear understanding of the conditions under which the test is conducted must be stated and followed.]

4.1 Software Items

[This section shall describe the software that will be tested under this plan. If there are no software items required, enter N/A for this section.]

4.2 Hardware Items

[This section shall describe the requirements for the hardware environment (platform, communications, configurations, etc.). If there are no hardware items required, enter N/A for this section.]

4.3 Firmware Items

[This section shall describe the requirements for the firmware. If there are no firmware items required, enter N/A for this section.]

4.4 Other Test Items

[This section shall describe the requirements any other test items that are required. The section goal is to take what is listed here and be able to reproduce the environment in which testing occurred. If there are no firmware items required, enter N/A for this section.]

5 Test Resources [This section shall describe any data, equipment and locations needed for the test. It will also detail the staff members who are involved in the test and what their roles are.]

5.1 Key Test Personnel

Table 2: Key Test Personnel

Role Title/Rank Name Organization Phone Email

5.2 Test Data

[This section shall describe any required data resources needed for testing]

5.3 Test Equipment / Instrumentation

[This section shall describe any required equipment of instrumentation required for testing.]

[This section shall describe any facilities or locations that are needed for testing.]

6 Test Approach

6.1 General Information

6.1.1 Test Objectives

[This section shall describe the objectives supported by the Test Plan.]

6.1.2 Test Methodology

[This section shall describe the overall approach to testing. For each major group of features or feature combinations, specify the approach which will ensure that these feature groups are adequately tested.

Specify major activities, techniques, and tools which are used to test the designated groups of features.

Test events are categorized as inspection (e.g. measuring a dimension or observing without operating), demonstration (e.g. showing a process or function operates as designed), analysis (e.g. employing mathematics, modeling, or simulation without actually operating the system under test), or testing (e.g.

operating the system under varying conditions and recording results). Test event actions are defined as observing, comparing, demonstrating, determining, evaluating, and verifying. Each test approach should define the type of test event and its specific action required to address the stated objectives.

6.1.2.1 [Test Approach 1] [This section shall describe the selected approach in sufficient detail to permit identification of the major tasks and estimation of the time required to do each. List the responses, conditions/factors, and any constraints and/or limitations for each event. The event category dictates the volume of testing required.

For example, a detailed test across many conditions might justify a design of experiments approach, whereas a demonstration may only require a few repeated runs at a couple conditions. Edit title of section to identify the test approach. For detailed test methods and procedures exceeding 1 page in length, the information should be presented in an appendix (see Appendix A for an example).]

6.1.2.2 [Test Approach 2] [This section shall describe the selected approach in sufficient detail to permit identification of the major tasks and estimation of the time required to do each. Edit title of section to identify the test approach. For detailed test methods and procedures exceeding 1 page in length, the information should be presented in an appendix (see Appendix A for an example).]

6.1.3 Success Criteria

[This section shall describe the criteria defined for successful testing. For example: “Successful testing is defined by:”]

6.1.4 Evaluation Criteria

[This section shall define how scenarios/issues are evaluated during testing event.]

Any issues reported will be defined and categorized into one of the following:

High – Not functional and may impact other functionality. No workaround defined.

Medium - Causes undesirable behavior, but system is still functional. Possible workaround found.

Low - Mainly a cosmetic and/or minor inconvenience. System is still functional and workaround available.

Enhancement - Something that would make the tool more useful or would be nice to have.

6.1.5 Data Requirements

[This section shall describe the data sources needed to execute your data analysis plan ie.]

6.1.6 Data Analysis Plan

[This section shall describe the criteria by which each objective is evaluated.]

Satisfactory – defined by no re-occurrences of discrepancies

Marginal - defined by the ability to perform test with alternative methods

Poor – defined by no work-around method available to test

6.1.7 Issue Tracking

[This section shall describe the process to track and resolve issues during testing. The following template is provided to log Issue.]

Issue Tracking Form

- V1.0.docx

7 Test Safety [This section describes the test hazards and test safety protocols. If specific test hazards are identified a test hazard matrix should be provided in table format as follows:

Hazard Number Hazard Cause Effect

Precautionary Measures

Corrective Actions

Risk Category

1 List a single hazard specific to the test.

Identify the direct cause(s) of the hazard listed. Causes should not be confused with additional hazards, but rather focus on the root cause(s) and their associated effect(s) that could lead to the presence of an identified hazard.

List the effects resulting from the hazard remaining uncontrolled.

(i.e. what happens if the hazard happens?)

Identify all precautions that can eliminate the causes leading to the potential hazard or which can reduce the probability of the hazard occurring. Each precautionary measure should be tied to a listed cause.

List the actions to be taken to minimize the severity of the effects if the hazard occurs.

List the residual hazard severity and probability (next tab), as well as the resultant Risk Category.

Risk Category is calculated based on Hazard Probability and Hazard Severity. Definitions for these can be found in the following attachment.]

Test Hazard Analysis.xlsx

8 Security [This section shall describe the cyber security and/or physical security of the system under test and/or security of the testing location. This should include documentation on any certifications, waivers and artifacts produced from security review/authorization.]

9 Readiness Review [This Section outlines the necessary review steps taken before testing begins. While the following table may not be completed when the Test Plan is delivered, it should be completed and reviewed before any testing occurs]

The Test Readiness review will be completed prior to first testing event.

Table 3: Readiness Review

Readiness Check Complete Date

Test Objectives are clearly defined

Test Scenarios and/or methods are documented

Test Documentation has been delivered for review prior to test

Test Hazard Analysis has been completed (if applicable)

Risk Mitigation has been identified

Contingency Planning has been defined

Test Materials have been identified and secured

Test Facilities have been scheduled

Test Support Staff are available to support testing activities

Performance metrics have been defined

Technical Performance Measurements have been met

10 Test Assumptions [This section identifies the high-risk assumptions of the Test Plan and outlines specific contingency plans for each item.]

11 Requirements Traceability [This section maps the program requirements (objectives) to the testing that validates the requirements.]

Table 4: Requirements Traceability

Objective/Requirement Technical Focus Area Test Point

12 Test Schedule [This section shall describe the schedule of testing events to include delivery of Test Report and any scheduled DEMOS.]

13 Acronyms and Abbreviations [This section shall list and write out full terminology of acronyms and abbreviations used within the Test Plan.]

Table 5: Acronyms and Abbreviations

A-1

APPENDIX A

DETAILED METHOD OF TEST

1.0 [Test Approach Title]

# Test Point / Description Method Expected Test Result Remarks

1.1

[Insert title of test point and description]

[Insert detailed method of test / test procedures.

Specify test set up and procedures (refer to maintenance manuals, instructions, Standard Operating Procedures (SOP), or other publications whenever possible) and data collection techniques.]

[Insert expected test result] [Discuss any specific configurations desired or required for the test. Define equipment/data requirements (e.g.

camera, measuring devices, etc.) and specific test point go/no-go criteria.]

Evaluation Issue Identified Issue Resolution Actual Test Result

Evaluation Satisfactory Marginal Poor

No Yes

High Medium Low

Prepared for:

Department of the Air Force

Contract No. [XXXXX-xxxxx]

Document Number:

CHANGE HISTORY

DOCUMENT CHANGE HISTORY

VERSION CHANGE DESCRIPTION (Required for changes affecting Requirements, TABLE OF CONTENTS

1 Executive Summary

1.1 Background

1.2 Purpose

1.3 Project Overview

2 Referenced Documents

3 Project Classification

4 System Under Test

4.1 Software Items

4.2 Hardware Items

4.3 Firmware Items

4.4 Other Test Items

5 Test Resources

5.1 Key Test Personnel

5.2 Test Data

5.3 Test Equipment

5.4 Test Location(s)

6 Overview of Test Objectives/Methodology

6.1 Test Objectives

6.2 Test Execution Schedule

7 Test Data/Results

7.1 Overview and Results

7.1.1 Test Objective

7.1.1.1.1 Test Overview

7.1.1.2 Test Results

7.1.1.2.1 Observations or Discussions

7.1.1.3 Conclusion

8 Conclusions and Recommendations

8.1 Conclusions

8.2 Recommendations

8.3 Deficiencies

9 Acronyms and Abbreviations

Appendix A DETAILED METHOD OF TEST

LIST OF TABLES

Table 1: Referenced Documents

Table 2: Key Test Personnel

Table 3: Acronyms and Abbreviations

1 Executive Summary

[This section is used to give a high level overview of the Test Report. When writing this section, a reader should be able to understand what happened during test and any conclusions that were made without having to read the rest of the document. Think briefing a General.]

1.1 Background

[Provide context about the system under test and relevant information about any related systems.]

1.2 Purpose

[This section shall explain the purpose for writing this Test Report. This section should include a summary of any previous testing.