DI-SESS-81646D

Configuration Audit Plan

Provides information required for conducting Functional Configuration Audits (FCA) and Physical Configuration Audits (PCA) of hardware and software configuration items.

Approval DateJanuary 19, 2024

AMSC NumberN10458

Preparing ActivityNM

Project NumberSESS-2023-026

OPR—

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

DI-SESS-81646C

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Configuration Audit Plan provides information required for conducting Functional Configuration Audits (FCA) and Physical Configuration Audits (PCA).

This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in EIA-649-1 and the principles of EIA-649 (copies of these standards are available online at www.sae.org or from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel 877-606-7323 [inside USA and Canada] or 724-776-4970 [outside USA]). It is not intended that all the requirements contained herein should be applied to all configuration audits. Portions of this DID are subject to tailoring, depending on the scope of the particular audit.

This DID supersedes DI-SESS-81646C.

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.

2FormatThe Configuration Audit Plan shall be in contractor format unless otherwise designated in the contract.

3ContentThe Configuration Audit Plan shall include the following data.

3.1Purpose of the AuditState the purpose and objectives of the audit in terms of the contract requirement for the audit.

3.2Hardware Configuration Items (HWCI) to be AuditedIdentify each HWCI by:

aNomenclature

bSpecification identification number

cSerial number

dOther application identification numbers

3.3Computer Software Configuration Items (CSCI) to be AuditedIdentify each CSCI by:

aSoftware title

bCode identification number

cSoftware inventory numbering system

dSpecification identification number

eOther applicable identification numbers

fSoftware Development Plan or Software Project Management Plans review

gSoftware or firmware item version

hSoftware or firmware item description

iSoftware tools

jSource code and artifacts

kExecutables

lTest descriptions

mTest reports

nPeer review records

oAll other artifacts required for defining the product baseline

pCSCI, software, or firmware version date(This is requiring the contractor to identify the CSCI with the date that the revision/version was established.)

qVendor/developer/maintainer name

rAddress/location of vendor/developer/maintainer(This is requiring the contractor to identify the CSCI with the physical address of the vendor or developer that created the specific portion of the software code that establishes the CSCI.)

sAddress/location of configuration management facility(This is requiring the contractor to identify the CSCI with the physical address of the entity responsible for managing the configuration/revision of this specific CSCI.)

tConfiguration management identification

uPlanned earliest date of disposal

vCategory (Developmental, Commercial-Off-the-Shelf [COTS], Government Furnished Software [GFS], Government Furnished Information [GFI])

3.4Information Items to be AuditedIdentify the following as applicable:

aEngineering drawings

bApplicable specifications

cEngineering change proposals

dTest plans and procedures

eOperating and support manuals

fConfiguration documentation release procedures

gQuality assurance documentation and procedures

hRequests for variance (deviation and waivers)

iSoftware descriptions flow charts, manuals, and lists

jDigital models

3.5Reference MaterialsIdentify the following supporting documentation as applicable:

aSystems engineering technical data

bTrade study results

cProducibility analysis results

dRisk analysis results

eReports

fHardware and software mockups

gVariance (deviation and waiver) lists

hMinutes of related prior reviews

iVerification and validation results

3.6Scope of AuditInclude the following:

aSummary of the hardware and software contractual requirementsSummary of the hardware and software contractual requirements against which the audit will be conducted as specified in work statements, specifications, and approved plans.

bOutline of the proposed audit procedure for each item to be audited

3.7Location(s) and Date(s)Identify proposed date(s) and location(s) for the audit(s).

3.8Team CompositionIdentify:

aContractor representatives and their function in the audit

bProposed Government participation and functions in the audit

3.9Administrative RequirementsInclude:

aDescription of facilities and support equipment to be used in the audit

bAdministrative support to be used in the audit

cSecurity requirements to support the audit

dMetrics and reports

References

SAE International https://www.sae.org

Schema v3.0Community-maintained · Verify against ASSIST

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