DI-SESS-81830

As Built Configuration List - Common (ABCL-C)

Specifies the format and content preparation instructions for the As-Built Configuration List-Common (ABCL-C), which documents hardware and software configuration items for an end item as delineated in the contract.

Approval DateNovember 16, 2010

AMSC NumberN9176

Preparing Activity—

Project Number—

OPRSH/PEO IWS 3.0

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantNo

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

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

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

It is not intended that all the requirements herein should be applied to every program. Portions of this DID are subject to tailoring by deletion depending on the specific status reporting requirements of the project.

Preparation Instructions

1FormatAs-built configuration list format shall be an electronic comma separated variables (csv). Each text file shall contain 23 columns describing the attributes of each hardware and software configuration item for a single end item.

2ContentThe ABCL-C shall contain all of the information identified in Table 1 of this DID and the following information:

2.1File Construction

2.1.1Columns 1 and 2Columns 1 and 2 shall describe the program and shall be the same for all rows.

2.1.2Columns 3 through 18Columns 3 through 18 shall describe each reportable item. Rows are repeated for each unique combination of columns 21 through 23.

2.1.3Columns 19 and 20Columns 19 and 20 shall describe the end item and will be the same for all rows.

2.1.4Columns 21 through 23Columns 21 through 23 describe messages related to each reportable item. The number of unique messages for an item can range from 0 to 99. The first row of each message contains a message label in column 21, column 22 is blank and column 23 contains the number "1".

2.1.5Row oneRow one shall contain information for the end item (the highest level assembly in the file). Column 10 for this row is always the number "0".

2.2The report shall identify the end itemThe report shall identify the end item as the highest level assembly in the deliverable file.

2.2.1ItemItem shall be identified as a unique reportable individual missile, section, assembly, or component.

2.2.2NHANHA shall be identified as the Next Higher Assembly of an item.

2.2.3ManufacturerManufacturer shall be identified by indicating the specific vendor that produced the reportable item.

2.2.4CAGE CodeCAGE Code shall be identified as Commercial and Government Entity Code.

2.2.5CARLCARL shall be identified as the Configuration Accounting Requirements List. A collection of hierarchical configuration structures (indentured drawing trees) for each end item part number produced under the contract. The drawing tree for each end item part number will contain an indentured list of primary and alternate reportable part numbers. Additional configuration data delivery requirements may also be documented.

References

—

Figures

Figure 1. Content Definition

Schema v3.0Community-maintained · Verify against ASSIST

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