DI-SESS-81938A

Performance Analysis Report

Documents the methods, assumptions, and results for system level modeling and simulation performance analysis performed during design of equipment.

Approval DateApril 8, 2024

AMSC NumberN10465

Preparing ActivityAS

Project NumberSESS-2024-017

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

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

Supersedes

DI-SESS-81938

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

Performance analysis report is the primary documentation for system level modeling and simulation analysis performed during design of equipment. Within this document reside the methods, assumptions, and results for system level performance analysis.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract Statement of Work (SOW).

This DID supersedes DI-SESS-81938.

Preparation Instructions

1Reference documentsNone.

2FormatContractor format.

3Content

3.1Title PageTitle Page, containing the following:

3.1.1Title/identification of the system/component/program/project

3.1.2Title of CDRL and CDRL number

3.1.3Contract number

3.1.4Preparing activity or contractor's title

3.1.5Security classification, when required

3.1.6Distribution Statement

3.2Table of ContentsThe document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix.

3.3ScopeThis section shall be divided into the following paragraphs:

3.3.1IdentificationThis paragraph shall contain a full identification of the system and the components to which this document applies, including, as applicable, part numbers.

3.3.2System overviewThis paragraph shall briefly state the purpose of the system and the components to which this document applies. It shall describe the general nature of the system and components of interest; 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 relevant documents.

3.3.3Document overviewThis paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

3.4Referenced documentsThis section shall list the number, title, revision, and date of all documents referenced in this document. This section shall also identify the source for all documents not available through normal Government stocking activities.

3.5General approachThis section shall detail the general approach for assessing system capability with respect to governing performance requirements. This section shall also include what software tools are used for which assessing which requirements.

3.6Analytical PlanThis section shall detail the cases to be analyzed and justification for selection and or exclusion. This section shall justify grouping of analysis for simplification if applicable.

3.7Physics based methodsThis section shall provide description and justification for all physics based calculations and processes used within the performance assessment.

3.8Rule based methodsThis section shall provide description and justification for all rule based calculations and processes used within the performance assessment.

3.9AssumptionsThis section shall list all relevant assumptions and provide justification. As necessary sensitivities to demonstrate, significance of parameters shall be provided in this section.

3.10ResultsThis section shall provide results of analysis. This shall include relevant tables, figures, and conclusions.

3.11Software artifactsThis section shall include all source code, macros, or other mechanisms required to conduct the performance assessment.

3.12NotesThis section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.

3.13AppendixesAppendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).

References

—

Schema v3.0Community-maintained · Verify against ASSIST

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