DI-SESS-81856
Contractual Baseline Report
Identifies the planned configuration of each individual end item being built under a specific Government contract and is used to track, reconcile, and audit contractor compliance with the Contractual Baseline.
Approval DateDecember 20, 2011
AMSC Number9236
Preparing Activity—
Project Number—
OPRAR
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantNo
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
The Contractual Baseline Report identifies the planned configuration of each individual end item being built under a specific Government contract. The planned configuration (i.e., Contractual Baseline) is defined by the contract and any subsequent modifications to the contract that result in configuration changes. The Contractual Baseline continuously changes throughout the life of a contract. The Contractual Baseline Report will be used to track and reconcile status of the Contractual Baseline. The Contractual Baseline Report will also be used to audit contractor compliance with the Contractual Baseline.
This Data Item Description (DID) contains the format, content and preparation instructions for the data product resulting from the work task specified in the contract.
Preparation Instructions
1Reference documentsThe applicable issue of any documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
2FormatThe Contractual Baseline Report shall be prepared in contractor format. The format shall allow the history of obsolete configurations to be retained in the report whenever changes in configuration are incorporated. Historical configurations shall be marked in an obvious manner (lining out, highlighting, color coding, etc.).
3ContentThe report shall contain a list of all drawings and specifications needed to fully define the planned configuration of each end item being built. For each document listed, the following information shall be provided for both the current configuration and historical configurations:
cNomenclature or description of the document
dIndenture level of the document within the product configuration tree
eLatest revision of the document that has been incorporated into the contract
fDistribution statement applicable for the document
gA list of any and all documentationA list of any and all documentation authorizing changes in configuration from that specified by the base document, to include:
iSection C of the original contract (exceptions to the Technical Data)
iiContractual Letters issued by the Procuring Contracting Officer (PCO)
iiiIncorporated Engineering Change Proposals (ECPs)
ivIncorporated Value Engineering Change Proposals (VECPs)
vApproved Requests for Deviation (RFDs)
hEffectivity date for when the configuration identifiedEffectivity date for when the configuration identified by items 3.a through 3.g was incorporated into the contract. Effectivity of a configuration change is the date established by the Procuring Contracting Officer in official correspondence.
Schema v3.0Community-maintained · Verify against ASSIST 