DI-SESS-82361

Acquisition and Sustainment Data Package (ASDP) Technical Report

The ASDP Technical Report documents test, inspection, demonstration, and analysis results and findings to show contractor compliance with system requirements, performance objectives, specification requirements, and test plans.

Approval DateOctober 1, 2021

AMSC NumberF10272

Preparing Activity—

Project NumberSESS-2021-013

OPR11 (AFLCMC/EZSI)

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

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

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Acquisition and Sustainment Data Package (ASDP) Technical Report is used to document test, inspection, demonstration, and analysis results and findings to show contractor compliance with system requirements, performance objectives, specification requirements, and test plans. The definitions of test, inspection, demonstration, and analysis can be found in MIL-STD-961, Defense and Program-Unique Specifications Format and Content. (Copies of this document are available online at https://quicksearch.dla.mil.) In addition, this report documents the configuration of the system under test, inspection, demonstration, or analysis.

a. The ASDP Technical Report provides all collected data and communicates results and information gained through a process of technical or experimental work for a variety of disciplines and purposes, to include: software, firmware, hardware, and system verifications, validations, and accreditations.

b. This Data Item Description (DID) is applicable to engineering (developmental), preliminary qualification, qualification, and acceptance testing.

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

Preparation Instructions

1Reference documentsThe 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.

2Format

2.1The ASDP Technical Report shall be in the native formatThe Data Objects/Attributes and Associated Metadata (DOAM) listing shall be in a Microsoft Excel spreadsheet format in accordance with the template provided in the DOAM Specification attached to the contract. All data shall be in the English language. The final ASDP Technical Report shall have all outstanding changes incorporated into the data and shall be formatted as follows:

2.1.1The report shall be in the form of a document and a digital system model

2.1.2The report and all attachments shall be electronic and the attachments shall be fully identified and referenced in the report

2.1.3The report, including the attachments, shall be viewable on a government computer

2.1.4The data shall be fully identified and linked within the model

2.1.5Diagrams, models, tables, matrices, and other presentation styles are acceptable substitutes for textwhen data required by this DID can be made more readable using these styles.

2.1.6The digital system model shall be in its native formproviding traceability from the highest level to the lowest level.

2.1.7The data shall be exportable to a format viewable on a government device

2.2Title Page or IdentifierThe ASDP Technical Report shall include a title page, or equivalent, containing, as applicable: a report number; volume number; version or revision indicator; report date; report title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the report applies; Contract Data Requirements List (CDRL) item number; name and address of the preparing organization; and security markings, distribution statement, any data rights limitation, destruction notice, and export control warning statement. All data and models shall include portion markings in accordance with the program's Security Classification Guide (SCG) and Department of Defense Manual (DoDM) 5200.01, Volume 2 (V2), DoD Information Security Program: Marking of Information. (DoDM 5200.01 V2 is available online at https://www.esd.whs.mil.)

2.3Page Numbering and LabelingEach page shall contain a unique whole page number (no decimal-number sequences) and display the document number and version or revision indicator. For data provided in a model, database, or other alternative form, all files, views, and other elements shall include names or numbers assigned in such a way that the desired data can be indexed and accessed as referenced in the Government-provided style guide, if available.

2.4Response to Tailoring InstructionsIf a paragraph is tailored out of this DID, the resulting report shall contain the corresponding paragraph number and title, followed by "This paragraph has been tailored out." For data provided in a model, database, or other alternative form, this representation shall occur only in the table of contents, or equivalent.

2.5Multiple Sections, Paragraphs, and SubparagraphsAny section, paragraph, or subparagraph in the report may be written as multiple paragraphs or subparagraphs to enhance readability, as necessary.

2.6Standard Data DescriptionsIf a data description required by this DID has been published in a standard data element dictionary specified in the contract, reference to an entry in that dictionary shall be included instead of including the description itself.

3ContentThe ASDP Technical Report shall include the following:

3.1The term "document" in this DID shall mean a collection of data regardless of its mediumIn the case of a model, the terms "section" and "paragraph" in this DID shall mean the model element(s) that fulfill the section or paragraph's requirements.

3.2The report shall also include the type of test, inspection, demonstration, and analysis(e.g., first article inspection, acceptance test, qualification inspection and conformance inspection, developmental test, qualification test, environmental test); identification of item tested and inspected; date or period of test, inspection, demonstration, and analysis; name and address of requiring government activity; and security classification, downgrading, and declassifying information, if applicable.

3.3The following numbering, section titles, and content shall be used and included in the ASDP Technical Report

3.3.1ScopeThis section shall include the following paragraphs:

3.3.1.1IntroductionThis paragraph shall summarize the purpose and contents of the ASDP Technical Report. This paragraph shall provide the reader with an overview of why the work was performed, how the work was performed, and a brief summary of the results. This paragraph shall include a full description of the project and its requirements. This paragraph shall include a list of any assumptions that were made during the completion of the work discussed in the report.

3.3.1.1.1Verification ObjectivesThis paragraph shall state the specific test, inspection, demonstration, and analysis objectives per the contract. This paragraph shall include a top-level configuration identification of the item(s) tested, inspected, demonstrated, and analyzed, including the following for the item under test: Government-Assigned Nomenclature (in accordance with MIL-STD-1812, Aeronautical and Support Equipment Type Designation System, and MIL-STD-196, Joint Electronics Type Designation Automated System (Copies of these documents are available online at https://quicksearch.dla.mil.)), model number or part number, type of item (i.e., prototype, production item, laboratory model, etc.), and any applicable Engineering Changes. This paragraph shall include top-level test, inspection, demonstration, and analysis requirements.

3.3.1.1.2PurposeThis paragraph shall include a brief statement on the purpose of the system and the software to which this report applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other required documents related to the data deliverable.

3.3.1.2Configuration IdentificationThis paragraph shall provide a full description of the system, subsystem, software, or component's configuration to which this report applies. The configuration identification shall include for hardware, software, and firmware the applicable identification number(s), title(s), abbreviation(s), version number(s), release number(s), Government-Assigned Nomenclature (in accordance with MIL-STD-1812 and MIL-STD-196), National Stock Number (NSN), Computer Program Identification Number (CPIN), model number, part number(s), serial number(s), and lot number(s). If applicable, the type of item (i.e., prototype, production item, laboratory model, etc.), applicable engineering changes, production item specification, and date of manufacture shall be detailed, as well as the baseline release date.

3.3.1.2.1Test EquipmentThis paragraph shall include the complete identification of each item of test equipment used in the test, inspection, demonstration, and analysis, including the following: nomenclature, model number, serial number, manufacturer, calibration status, accuracy data, and comments, if applicable. This paragraph shall also include a complete description of the physical set-up used in conducting the test. Drawings, illustrations, and pictures shall be used for clarification.

3.3.1.3Requirements TraceabilityBidirectional traceability to all contractual requirements related to the test(s) being reported on shall be provided. For software, the report shall provide bidirectional traceability from the test cases to the requirements, software functions, and source code.

3.3.1.4Literature ReviewThis paragraph shall summarize and provide the sources of research that were used throughout the project that helped with its completion.

3.3.1.5Background TheoryThis paragraph shall explain the technical background of the work, to include the underlying theory(ies) needed to understand the rest of the Technical Report. The background theory shall include the mathematical equation(s), model(s), and formula(s) in their final form used to complete the work.

3.3.1.6DesignThis paragraph shall provide a clear description of the detailed development of any system and software design included in the Technical Report. This paragraph shall provide a description of the actual design tested and include a clear presentation of how the design was developed. In the case of software coding, this paragraph shall include any data that was used in the process of writing the code, to include the following:

3.3.1.6.1InputsDocument any values that are known before the code is written.

3.3.1.6.2OutputsDocument the significance of the outputs.

3.3.1.7Theoretical AnalysisThis paragraph shall provide details of all theoretical analyses performed. This paragraph shall include diagrams, graphs, tables, mathematics, and metrics (to include the associated value(s), measurement units, and tolerance bands).

3.3.2Results and DiscussionThis section shall provide a clear understanding of the results of the work performed supported by a description of how the results were obtained, what significance they hold, and how the designed system actually functions. This section shall include the following paragraphs:

3.3.2.1Software TestingThis paragraph shall provide an overall assessment of the software as demonstrated by the test results in the ASDP Technical Report, identifying specific software releases relative to its software requirements and deficiencies. This paragraph shall also identify any remaining software deficiencies, limitations, or constraints that were detected by the testing performed. For each remaining deficiency, limitation, or constraint, its impact on the software and system performance shall be described, including identification of requirements not met, the impact on software and system design to correct it, and a recommended solution and approach for correcting it.

3.3.2.2Modeling, Simulation, Experimentation, and TestingThis paragraph shall provide any relevant modeling and simulation (M&S) or experimental data used in obtaining the results presented in the ASDP Technical Report. Any source code or native source files uniquely developed to support the work described in the report, as well as the name and version of any commercial software that was used, shall be included. This paragraph shall include the following:

3.3.2.2.1Numerical AnalysisAny numerical calculations that were done through completion of the project. This includes such techniques as traditional mathematical methods, Finite Element Analysis (FEA), Artificial Intelligence/Machine Learning (AI/ML), and other computational techniques.

3.3.2.2.2Sample CalculationsIf models were used to complete the project, a sample calculation(s) walking through the equations or processes used to get the results shall be provided. At least one sample calculation that includes all inputs and outputs used shall be included.

3.3.2.2.3Engineering Design DataThe engineering design data for all assemblies, sub-assemblies, and parts included in the final assembly. This paragraph shall provide the engineering specifications for each item, highlight any design changes that occurred from a previous iteration (if applicable), and describe the rationale behind what went into each model.

3.3.2.2.4Animation AnalysisAll animations that are included in the project.

3.3.2.2.5Experimental, Simulation and Test ResultsExperimental and simulation data obtained during the project and a comparison of those results to predictive modeling techniques. All data shall annotate the agreed to collection conditions (e.g., temperature, pressure, cloud conditions, humidity, weather conditions), be expressed in standard units, and include error bars, where applicable.

3.3.2.3Test Plan and ProceduresThis paragraph shall provide a list of any test plans and procedures used to test a theory, verify a design, or conduct a process. The paragraph shall include a traceability matrix of all test plans and procedures used during any testing conducted in support of the work contained in the ASDP Technical Report. If a test plan and procedure has not been provided through other CDRLs or DIDs, this paragraph shall include a complete description of the procedures used in conducting the test, inspection, demonstration, and analysis, to include the following: item selection and inspection that verified suitability for test, inspection, demonstration, and analysis. A summarized sequence of testing and inspection steps, including a description of how the item under test was operated during the test, to include any control conditions imposed, shall be provided.

3.3.2.4Test Environment Constraint(s)This paragraph shall include an assessment of the manner in which the test environment is different from the operational environment and the effect of this difference on the test results.

3.3.2.5Issues and ResolutionsThis paragraph shall identify any problems that occurred throughout the project and describe how the problems were solved.

3.3.3Conclusions and RecommendationsThis section shall include a discussion of the project results. For test, inspection, demonstration, and analysis, the following shall be included:

3.3.3.1Acceptability of the item tested or inspected(i.e., pass or fail in accordance with specified test or inspection criteria).

3.3.3.2Additional test, inspection, demonstration, and analysis required

3.3.3.3Redesign required

3.3.3.4Problem resolution

3.3.3.5Procedure or facility improvements needed

3.3.3.6Disposition of items

3.3.3.7Documentation changes required

3.3.3.8Improvements suggested

3.3.3.9Rationale for recommendations

3.3.4Reference InformationThis section shall list the number, title, and revision of all documents referenced in the report and shall include the complete identification of all information referenced in the ASDP Technical Report, as applicable, including:

3.3.4.1Prior test, inspection, demonstration, and analysis reports for the same item or requirement

3.3.4.2Test, inspection, demonstration, and analysis plans and procedure documents

3.3.4.3Prior relevant certification(s) and the associated compliance standard(s)(e.g., government and commercial standards).

3.3.4.4Contractor's file designation where test, inspection, demonstration, and analysis records are maintained

3.3.4.5All other input parameters used to generate the report

3.3.5NotesThis section shall contain any general information that aids in understanding the ASDP Technical Report (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, their meanings, and a list of any terms and definitions needed to understand the ASDP Technical Report.

3.3.6AppendicesAppendices shall be included to provide information published separately for convenience in document maintenance (e.g., charts, classified data, long mathematical formulas, extensive calculations, and error analysis). As applicable, each appendix shall be referenced in the main body of the report where the data would normally have been provided and associated to the related model.

3.4DOAMThe completed ASDP Technical Report template, provided in the DOAM Specification attached to the contract, shall comply with the format requirements in 2. above so that it can be ingestible into a Product Lifecycle Management (PLM) solution to ensure proper tying, tracing, and linking to the lowest component of the end item to which the delivered ASDP Technical Report is applicable. Any field that is not applicable shall be marked "NA."

References

MIL-STD-961 https://quicksearch.dla.mil

MIL-STD-1812 and MIL-STD-196 https://quicksearch.dla.mil

DoDM 5200.01 V2 https://www.esd.whs.mil

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer