NIST Special Publication 881-32

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 839C

Project Cost Reporting

Implementation Convention

QC

100

.U57

NO. 881 -32

1998

NBT

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology
rhe National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . . . needed to improve product quality, to modernize manufacturing processes,

to ensure product reliability . . . and to facilitate rapid commercialization ... of products based on new scientific

discoveries."

NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's

competitiveness; advance science and engineering; and improve public health, safety, and the environment. One

of the agency's basic functions is to develop, maintain, and retain custody of the national standards of

measurement, and provide the means and methods for comparing standards used in science, engineering,

manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal

Government.

As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and

applied research in the physical sciences and engineering, and develops measurement techniques, test methods, standards, and related services. The Institute does generic and precompetitive work on new and

advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.

Major technical operating units and their principal activities are listed below. For more information contact the

Publications and Program Inquiries Desk, 301-975-3058.

Office of the Director

• National Quality Program

• International and Academic Affairs

Technology Services

• Standards Services

• Technology Partnerships

• Measurement Services

• Technology Innovation

• Information Services

Advanced Technology Program

• Economic Assessment

• Information Technology and Applications

• Chemical and Biomedical Technology

• Materials and Manufacturing Technology

• Electronics and Photonics Technology

Manufacturing Extension Partnership

Program

• Regional Programs

• National Programs

• Program Development

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology'

• Optoelectronics'

Chemical Science and Technology

Laboratory

• Biotechnology

• Physical and Chemical Properties2

• Analytical Chemistry

• Process Measurements

• Surface and Microanalysis Science

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Optical Technology

• Ionizing Radiation

• Time and Frequency

1

• Quantum Physics'

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• NIST Center for Neutron Research

Manufacturing Engineering

Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Fabrication Technology

• Manufacturing Systems Integration

Building and Fire Research

Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Safety Engineering

• Fire Science

Information Technology Laboratory

• Mathematical and Computational Sciences 2

• Advanced Network Technologies

• Computer Security

• Information Access and User Interfaces

• High Performance Systems and Services

• Distributed Computing and Information Services

• Software Diagnostics and Conformance Testing

'At Boulder, CO 80303.

2 Some elements at Boulder, CO.
NIST Special Publication 881-32

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 839C

Project Cost Reporting

Implementation Convention

Electronic Commerce Acquisition Program Management Office

Standard Management Committee - Secretariat

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Editor: Dr. Jean-Philippe Favreau

January 1998

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Gary R. Bachula, Acting Under Secretary for Technology

National Institute of Standards and Technology

Raymond G. Kammer, Director
Reports on Information Technology

The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL)

develops standards and guidelines, provides technical assistance, and conducts research for computers

and resources. As part of the overall federal effort to establish a single face to industry for conducting

electronic commerce, ITL has been designated as the organization responsible for coordinating the

development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are defined by functional-area experts who create and select options from standard EDI Transaction Sets to

yield the implementations to be used for practical EDI. These ICs are made available to federal agencies

and industry by electronic means and this Special Publication Series.

National Institute of Standards and Technology Special Publication 881-32

Natl. Inst. Stand. Technol. Spec. Publ. 881-32, 43 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998
839 Project Cost Reporting

Functional Group ID=

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Project Cost Reporting

Transaction Set (839) for use within the context of an Electronic Data Interchange (EDI) environment. This

transaction set provides the transmission of cost and schedule information to support performance measurement

(earned value), program management reporting, and contract funds status reporting. This transaction set will also

support the Department of Defense (DoD), Department of Energy (DoE), NASA, and other government agency

Cost/Schedule Control Systems Criteria (C/SCSC) and funds status reporting requirements. It is designed to serve

the needs of government agencies, prime contractors, and their subcontractors.

Notes:

1. This implementation convention addresses how the 839 Project Cost Reporting transaction set can be used to send Cost Performance Report (CPR) Formats 1 through 5 or Cost/Schedule Status Report (C/SSR) data

electronically. This implementation convention assumes the data will be moving in one direction only - from the

contractor or organization performing the work on a contract to their customer.

2. A single transaction set may contain one or more ofthe Cost Performance Reportformats. Refer to the

implementation notes throughout this convention for more information about the specific requirementsfor each

reportformat.

3. This convention is designed to be used when a Contract Data Requirements List(CDRL) for a given contract

specifies the Data Item Description (DID) DI-MGMT-81466, Cost Performance Report (CPR) or DI-MGMT81467, Cost/Schedule Status Report (C/SSR).

4. The customer's receiving application may have certain data content requirements. Confirm ifthere are any

data content guidelines that need to befollowed in addition to the dataformat requirements described in this

implementation convention.

5. There are two appendicesfor this implementation convention. The example appendix provides additional

reference information on how this transaction set is used to exchange cost performance data electronically. The

other appendix includes a series oftables that provides cross reference details on how to use the 839 transaction

set. This includes a Segment and Data Element Matrix table for all the reportingformats and a Forms Cross

Reference table.

Must Use

Pos. No. 010Seg. IDST

Name

Transaction Set Header

Req.

Pes. MMax.Use

1

Loop Notes and

Repeat Comments

Must Use 020 BCS Beginning Segment for Project Cost Reporting M 1

030 REF Reference Numbers O 100

Must Use 040 DLV Deliverable Information O 10

Must Use 050 AMT Monetary Amount O 30

060 PCT Percent Amounts 0 30

Must Use 070 DTM Date/Time Reference 0 30

LOOP ID - CFT 100

Must Use 080 CFT Cost Reporting Format Type M 1

: '

085 CAL Calendar O 50

LOOP ID - BSD >1

Must Use 090 BSD Breakdown Structure Description O

"

1

100 REF Reference Numbers 0 100

003050F839C0 ' 15 July 1997
839C Project Cost Reporting

Not Used 105 DTM Date/Time Reference O 50

110 AMT Monetary Amount O 100

115 QTY Quantity O 100

120 PAM Period Amount O 100

Not Used 130 PCT Percent Amounts O 100

140 MSG Message Text O 1000

LOOP ID - Nl 200

Must Use 150 Nl Name M 1 nl

160 N2 Additional Name Information O 1

170 N3 Address Information O 1

180 N4 Geographic Location 0 1

Must Use 190 PER Administrative Communications Contact 0 10

Not Used 195 REF Reference Numbers 0 10

Must Use 200 DTM Date/Time Reference 0 10

Must Use 210 SE Transaction Set Trailer M 1

Transaction Set Notes

1. At least one iteration of the Nl loop is required to identify the contractor.

003050F839C0 2 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

ST Transaction Set Header

010

Mandatory

1To indicate the start of a transaction set and to assign a control number

1 The transaction set identifier (ST01) used by the translation routines of the

interchange partners to select the appropriate transaction set definition (e.g., 810

selects the Invoice Transaction Set).

Comments:

Must Use

Must Use

Ref.

Pes.

ST01

ST02

Data

Element

143

329

Data Element Summary

Name Attributes

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

839 X12.31 Project Cost Reporting

Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set A unique number assigned by the originator ofthe transaction set or by the

originator's application system. This number is the same as the number in

SE02.

003050F839C0 3 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

BCS Beginning Segment for Project Cost Reporting

020

Mandatory

1To indicate the beginning of the project cost reporting transaction set, and information to identify a program name, number, contract type, and security classification.

1 BCS02 is the transaction set date. 2 BCS04 is the report effective date. 3 BCS06 is the program name.

4 BCS07 is the program number identification.

5 BCS 10 is the customer share ratio number.

6 BCS1 1 is the contractor share ratio number.

7 BCS 12 is the notation for the total project monetary costs. If BCS 12 is absent, the total project monetary costs are assumed to be whole dollar

amounts.

Comments:

Ref. Data

Pes. Element

Must Use BCS01 353

Data Element Summary

Name

Transaction Set Purpose Code

Code identifying purpose of transaction set

Attributes

M ID 2/2

00 Original

This code is typically usedfor transmitting the cost performance data.

05 Replace

Use this code to overwrite anypreviously transmitted

datafor a given reportingperiod -i.e., old data is deleted and new data is entered into the database.

14 Advance Notification

Use this code when preliminary cost performance data

must be transmittedfor a given reporting period. This

preliminary transmission is then followed with afinal

transmission (code 20) to provide thefinal cost performance data for the given reportingperiod.

20 Final Transmission

Use this code to transmitfinal cost performance data

when preliminary costperformance data (code 14) has

been sentfor a given reporting period.

Must Use BCS02

003050F839CO

22 Information Copy

3 1 Allowance/Addition

Use this code to transmit additional cost performance

reportformatsfor a given reportingperiod. This code

is typically only used when the various reportformats

are sent in separate transmissionsfor a given

reporting period

373 Date M DT 6/6

Date (YYMMDD)

Enter the date the data report was created. This date is usedfor reference

4 15 July 1997
839C Project Cost Reporting

Must Use BCS03 367

purposes only.

Contract Number

Contract number

Enter the contract number.

M AN 1/30

Must Use BCS04 373 Date M DT 6/6

Date (YYMMDD)

Enter the report effective date. This is the current reporting month for the

cost performance data.

Must Use BCS05 1166 Contract Type Code

Code identifying a contract type

O ID 2/2

CW

cx

CY

FD

FE

FI

FR

OC

Cost Plus Award Fee

Cost Plus Fixed Fee

Cost Plus Incentive Fee

Fixed Price Redetermination

Fixed Price with Escalation

Fixed Price Incentive

Firm Fixed Price

Other Contract Type

A type of contract which is neither covered by an

existing code nor previously mutually defined

Use the REF (1/030) segment to provide a description

ofthe contract type when this code is used.

Must Use BCS06 352

TM Time and Materials

Description O AN 1/80

A free-form description to clarify the related data elements and their content

Provide a name or short description ofthe program.

Must Use BCS07 127 Reference Number O AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Enter theprogram number.

Must Use BCS08 1193 Program Type Code O ID 2/2

Codes identifying a program type

The codes entered here can relate to the information entered in the DL V

(Deliverable Information (1/040)) segment. Refer to the notesfor the DLV

segment and data elementsfor more detail

01

02

Research, Development, Test & Evaluation (RDT&E)

Production

Use this codefor all types ofproduction as well as Low

Rate Initial Production (LRIP).

03

04

Both RDT&E and Production

Other

Use this code to indicate a mixture ofprogram types.

Use the REF (1/030) segment to provide a description

ofthe program type when this code is used.

003050F839C0

06 Advanced Design

Use this code to indicate Dem Val or Demonstration

5 15 July 1997
839C Project Cost Reporting

BCS09 786

BCS10 954

BCS11 954

Must Use BCS12 355

Validation in addition to the Air Force specific

"Advanced Design.

07 Full Scale Development

Generally, this code is only usedfor older contracts. Typically code 08, Engineering and Manufacturing

Development (EMD), is usedfor newer, or more

recent, contracts.

08 Engineering and Manufacturing Development (EMD)

Security Level Code O ID 2/2

Code indicating the level of confidentiality assigned by the sender to the

information following

Typically all data is assumed to be company proprietary information and is treated as government non-classified information (code 90). In the event

codes 92, 93, or 94 are used, additional security measures such as encryption are used to protect the data.

1 1 Competition Sensitive

90 Government Non-Classified

92 Government Confidential

93 Government Secret

94 Government Top Secret

Percent O R 1/10

Percentage expressed as a decimal

Enter the Contractor Above Share Ratio value if applicablefor the contract. A maximum ofthree numbers is allowed, whole numbers only, no decimals.

The sum ofBCSlO and BCS11 cannot be more than 100.

Percent O R 1/10

Percentage expressed as a decimal

Enter the Contractor Below Share Ratio value ifapplicablefor the contract. A maximum ofthree numbers is allowed, whole numbers only, no decimals.

The sum ofBCSlO and BCS11 cannot be more than 100.

Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

Use this data element to indicate all total contract monetary amounts have

been factored (for example, numbers represent dollars in thousands). Use

the CFT (Cost Reporting Format Type) segment to indicate the monetary

amountfactor usedfor a given cost performance report at the detail level.

DO Dollars, U.S.

Use this code when the monetary amounts have NOT

been factored.

HU Hundred

Use this code to indicate the monetary amounts have

been factored by a hundred - ue., hundreds ofdollars.

R5 Thousands of Dollars

R6 Millions of Dollars

003050F839CO 6 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Numbers

030

Optional

100

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

Use this segment to convey additional information about a contract, to provide

information about a related transaction set, or to provide Contractor Data

Requirements List (CDRL) references.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use REF01 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

72 Schedule Reference Number

Identifies a number for a program schedule (for

example, a logic type of network) or working schedule

to complete a specific task or set of tasks

Use this code to indicate there is a related Project

Schedule Reporting (806) transaction set(s) that

complements this transaction set. Enter the unique

806 transaction set reference number in REF02. The

unique reference number entered in REF02 should be

the same unique reference number entered in BPP09

(l/BPP/020) in the 806 transaction set.

84 Contractor Data Requirements List (CDRL)

Government or customer specific deliverables identified

by line item; referenced on shipping details, etc Use this code to convey CDRL reference(s) for the

contract Enter the number in REF02.

BE Business Activity

Use this code when BCS08, Program Type Code, is code 04for "Other" to describe what "Other" means. Enter the description in REF03. Use this code only

one time per transaction set

C4 Change Number

Use this code to convey the latest change or

modification numberfor the contract Enter the

number in REF02. Use this code only one time per

transaction set

CA Cost Allocation Reference

Use this code to provide a unique reference number

for this Project Cost Reporting (839) transaction set

This unique number is used to link related transaction

sets together (for example, with a Project Schedule

Reporting 806 or Specifications/Technical

Information 841 transaction set). Enter the unique

reference numberfor this transaction set in REF02.

003050F839C0 7 15 July 1997
839C Project Cost Reporting

Use this code only one time per transaction set.

CT Contract Number

Use this code when BCS05 is code "OC"for other

contract types to describe what "other" means. Enter

the description in REF03. Use this code only one time

per transaction set

Contract Reference

Use this code to provide a contract name. Enter the

contract name in REF03. Use this code only one time

per transaction set

Message Address or ID

Use this code to indicate there is a related Text

Message (864) transaction set(s) that complements this

transaction set. Enter the unique 864 transaction set reference number in REF02. The unique reference

number entered in REF02 should be the same unique

reference number entered in REF02 (l/REF/080) in

the 864 transaction set (which also uses the ME code

in REFOJ).

NJ Technical Document Number

Use this code to indicate there is a related

Specifications/Technical Information (841)

transaction set(s) that complements this transaction

set. Enter the unique 841 transaction set reference

number in REF02. The unique reference number

entered in REF02 should be the same unique

reference number entered in SPI03 (l/SPI/020) in the

841 transaction set.

KL

ME

REF02 127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Use this data element when REF01 is code 72, 84, C4, CA, ME, or NJ.

REF03 352 Description X AN 1/80

A free-form description to clarify the related data elements and their content

Use this data element when REF01 is code BE, CT, or KL.

003050F839C0 8 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

DLV Deliverable Information

040

Optional (Must Use)

10

To identify the product to be delivered or the service to be performed

1. This segment is required. This segment can be repeated as needed to relate a

quantity to a specific product or service provided when a contract includes more than one product or service.

2. This segment can also be repeated as needed to indicate a specific quantity (typically a product ofsome type) associated with different phases ofa contract (the program

type code), such as RDT&E or Production. Use the DL V04 data element to relate a

specific quantity with a specific program type code.

3. The receiving application may have certain requirementsfor this segment. When

sending data to the customer, ensure all guidelines arefollowed.

Must Use

Ref.

Pes.

DLV01

Data

Element

330

Data Element Summary

Name Attributes

Quantity Ordered M R 1/9

Quantity ordered

Enter the quantity associated with a specific type ofproduct or service. It can also reflect a specific Program Type when DLV04 is used.

Must Use DLV02

Must Use DLV03

235 Product/Service ID Qualifier M ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234)

F7 End-Item Description

Item identifier describes an end-item associated with the use of the required material

234 Product/Service ID M AN 1/40

Identifying number for a product or service

Enter a short description ofthe product or service.

DLV04 1193 Program Type Code O ID 2/2

Codes identifying a program type

Typically BCS08 is used to identify the Program Type Codefor the contract. Use this data element when there is a mixture ofprogram types (BCS08 is code 03 or 04) and specific quantities need to be identifiedfor each program

type. For the quantity entered in DL V01, indicate the associated program

type with this data element.

01

02

06

Research, Development, Test & Evaluation (RDT&E)

Production

Advanced Design

Use this code to indicate Dem Vol or Demonstration

Validation in addition to the Air Force specific

"Advanced Design.

003050F839C0

07 Full Scale Development

9 15 July 1997
839C Project Cost Reporting

Generally, this code is only usedfor older contracts. Typically code 08, Engineering and Manufacturing

Development (EMD), is usedfor newer, or more

recent, contracts.

08 Engineering and Manufacturing Development (EMD)

003050F839C0 10 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

AMT Monetary Amount

050

Optional (Must Use)

30

To indicate the total monetary amount

This segment is required. Use this segment to provide all total contract monetary

amount information.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use AMT01 522 Amount Qualifier Code M ID 1/2

Code to qualify amount

Provide all monetary amountsfor the qualifier codes listed below. Ifa

qualifier does not apply to the contract (for example, Negotiated Cost is equal to zero), do not include it. Otherwise, consider all the qualifiers listed

here as REQUIRED.

26 Negotiated Cost

The estimated cost negotiated in a Cost-Plus-Fixed-Fee

contract or the negotiated contract target cost in either a Fixed-Price-Incentive contract or a Cost-Plus-IncentiveFee contract 27 Authorized Unpriced Work

Effort for which written authorization has been received

but defined costs have not been agreed to 28 Target Price

The negotiated contract cost plus profit or fee applicable

to the defined contract effort

29 Estimated Price

The latest revised estimate of the total cost at complete

for a contract 30 Contract Ceiling

The ceiling price applicable to defined effort

3 1 Estimated Contract Ceiling

The estimated ceiling price applicable to all authorized

contract effort (both defined and undefined)

32 Target Fee or Profit Amount

The fee (can also be percent) of profit that will apply to defined contract effort

Use this code when the Target Fee or Profit is a

monetary amount Use the PCTsegment when the

Target Fee or Profit is a percentage. Either method

can be used to describe this required information

(when applicable), but use ONLY ONE - Le., ifthis

code in the AMTsegment is used, DO NOT use the

following PCT segment

33 Original Contract Target Cost

Value of the original negotiated contract

003050F839C0 11 15 July 1997
839C Project Cost Reporting

34

35

36

45

46

47

48

49

50

Use this codefor the Original Negotiated Cost item on

the Cost Performance Report Format 3 as well as the

Original Contract Target Cost item on the

Cost/Schedule Status Report.

Negotiated Contract Changes

The cumulative cost (excludes fee and profit) applicable

to defined contract changes that have occurred since the

beginning of the contract Current Target Cost

Sum of Original Contract Target Cost and Negotiated

Contract Changes

Contract Budget Base (CBB)

Sum of Current Targent Cost and Estimated Cost of

Authorized, Unpriced Work

Cumulative Schedule Variance (SV)

The cumulative difference between the cumulative

Budgeted Cost for Work Performed and the cumulative

Budgeted Cost for Work Scheduled

Use this code to enter the schedule variance

adjustmentfor the total contract

Cumulative Cost Variance (CV)

The cumulative difference between the cumulative

Budgeted Cost for Work Performed and the cumulative

Actual Cost for Work Performed

Use this code to enter the cost variance adjustmentfor

the total contract.

Reprogram Cost Variance

Adjustments to previously reported variances due to reprograrnming efforts Use this code to enter the performance measurement

baseline reprograrnming adjustments cost variancefor

the contract.

Reprogram Budget

Adjustments to the budget due to reprograrnming efforts Use this code to enter the performance measurement

baseline reprograrnming adjustments budgetfor the

contract.

At Complete Budget (BAC)

The total budget assigned to a work package or task;

also, the total budget of any summary of these work

tasks

Use this code to enter the performance measurement

baseline budgeted cost at completion for the contract

At Complete Latest Revised Estimate (LRE)

Latest estimate of cost at completion including over or under runs for all authorized work; it is the sum or the

actuals to date plus the estimate of remaining work

(Estimate to Complete or ETC)

Use this code to enter the performance measurement

baseline estimated cost at completion for the contract

003050F839C0

52 Total Allocated Budget

12 15 July 1997
83 9C Project Cost Reporting

Sum of all budgets allocated to the performance of a contract 85 Optimistic Estimate at Complete (EAC)

Best case estimate of cost at the completion for risk

analysis calculations

Use this code to enter the best case Management

Estimate at Completion.

86 Pessimistic Estimate at Complete (EAC)

Worst case estimate of cost at completion for risk

analysis calculations

Use this code to enter the worst case Management

Estimate at Completion.

87 Most Likely Estimate at Complete (EAC)

Most likely estimate of cost completion for risk analysis

calculations

Use this code to enter the most likely Management

Estimate at Completion.

CY Cumulative Budget

Use this code to enter the performance measurement

baseline cumulative budget costfor the contract.

CZ Cumulative Earned Value

Use this code to enter the performance measurement

baseline cumulative earned value costfor the contract

D9 Cumulative Actual

Use this code to enter the performance measurement

baseline cumulative actual costfor the contract.

Must Use AMT02 782 Monetary Amount M R 1/15

Monetary amount

For all monetary amounts, ifenteringfactored monetary amounts such as thousands ofdollars (notation from BCS12), use only one decimal place

when applicable.

Not Used AMT03 478 Credit/Debit Flag Code O ID 1/1

Code indicating whether amount is a credit or debit

003050F839CO 13 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

PCT Percent Amounts

060

Optional

30

To qualify percent amounts and supply percent amounts

/. The maximum usefor this segment is 1. Use this segment when the Target Fee or

Profit is defined as a percentage. Use the previous AMTsegment when the Target Fee

or Profit is defined as a specific monetary amount. Ifthis segment is used, DO NOT

use the AMTsegment to provide Target Fee or Profit information.

2. Include the Target Fee or Profit when this information applies to the contract. If it applies, it is required information. This information must be provided using either the

previous AMTsegment or this PCT segment.

Must Use

Ref.

Pes.

PCT01

Must Use PCT02

Data

Element

1004

954

Data Element Summary

Name Attributes

Percent Qualifier M ID 1/2

Code to qualify percent

05 Target Fee or Profit

The negotiated contract fee or profit applicable to one

defined contract effort

Percent M R 1/10

Percentage expressed as a decimal

A maximum offive characters is allowed, with up to one decimalplace.

003050F839C0 14 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

DTM Date/Time Reference

070

Optional (Must Use)

30

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

This segment is required. Use this segment to provide all total contract date

information.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use DTM01 374 Date/Time Qualifier M ID 3/3

Code specifying type of date or time, or both date and time

Provide all datesfor the qualifier codes listed below. Ifa qualifier does not

apply to the contract (for example, Over Target Baseline Month), do not

include it Otherwise, consider all qualifiers listed here as REQUIRED.

090 Report Start Use codes 090 and 091 to define the specific start and

stop dates for the current reportingperiod.

091 Report End

196 Start Use this code to indicate a work start date when the

work start date is differentfrom the contract start date

(code 276).

245 Estimated Completion

The revised plan or estimate of the complete date for a task or activity

276 Contract Start The start date for a contract 277 Contract Definition

The date the contract was definitized

Use this codefor the contract definitization date.

278 Last Item Delivery

The date the last item will be delivered to the customer

Use this codefor the Planned Completion Date item on the Cost Performance Report Format 3.

279 Contract Completion

The finish date for a contract 28 1 Over Target Baseline Month

The date a budget baseline went over the target budget

amount

Use this code in the event an over target situation is encountered on the contract. Enter the over target

baseline month ending date in DTM02.

003050F839C0 15 15 July 1997
839C Project Cost Reporting

Must Use DTM02

Not Used DTM03

Not Used DTM04

373

337

623

Not Used DTM05 624

Not Used DTM06 1250

Not Used DTM07 1251

Date X DT 6/6

Date (YYMMDD)

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003050F839C0 16 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

CFT Cost Reporting Format Type

Mandatory

080

CFT

Mandatory

1To identify the cost reporting type, type of units reported, and funds details for the

Contract Funds Status Report (CFSR)

1

2

3

4

If CFT01 equals CY, then CFT03, CFT04, CFT05, CFT06, CFT07 and CFT08 are required.

CFT02 is the notation for the report monetary costs or quantities.

If CFT02 is blank, the report monetary costs are assumed to be in whole dollar

amounts.

CFT04 and CFT05 are used for the funds appropriation start date.

CFT06 and CFT07 are used for the funds appropriation end date.

Comments:

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use CFT01 755 Report Type Code M ID 2/2

Code indicating the title or contents of a document, report or supporting item

CX Cost/Schedule Status Report (C/SSR)

Contract status report showing budget, performance,

actual, cost variance, schedule variance, budget at complete, estimate at complete, and variance at complete at specified levels of the work breakdown

structure Fl Cost Performance Report (CPR) Format 1

Detailed contract status report including current

reporting month values at specified levels of the work

breakdown structure F2 Cost Performance Report (CPR) Format 2

Detailed contract status report at specified levels of the

organization breakdown structure F3 Cost Performance Report (CPR) Format 3

Contract baseline report that summarizes changes to the contract over a given reporting period with beginning

and ending values

F4 Cost Performance Report (CPR) Format 4

Contract resource summary report that forecasts labor

requirements for the remainder of a contract F5 Cost Performance Report (CPR) Format 5

Contract summary or detail report explaining significant cost or schedule variances

LP Labor Plan

Use this codefor the working months or hours Budget

at Complete (BAC) Format 4 type ofdetail reportfor

each functional category. This is an optional report

format.

VA Variance Analysis

Use this code onlyfor reporting variance analysis

details for the Cost/Schedule Status Report (C/SSR).

003050F839C0 17 15 July 1997
839C Project Cost Reporting

CFT02 355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

1. Use this data element to indicate the monetary amountfactor or quantity

typefor the given format reporting element details. For the Cost

Performance Report Formats 1, 2, and 3, and the Cost/Schedule Status

Report, indicate the monetary amountfactor used such as dollars in

thousands. For the Cost Performance Report Format 4, indicate the

quantity type used - Le., working months or hours. This code is requiredfor

theseformats.

2. This data element can also be used to indicate the monetary amountfactor

usedfor Cost Performance Report Format 5 or the Variance Analysis

information for the Cost/Schedule Status Report in the event monetary

amounts are includedfor these reports.

DO Dollars, U.S.

Use this code when the monetary amounts have NOT

been factored.

HR

HU

Hours

Hundred

Use this code to indicate the monetary amounts have

been factored by a hundred - Le., hundreds ofdollars.

Not Used CFT03 1198

Not Used CFT04 374

Not Used CFT05 373

Not Used CFT06 374

Not Used CFT07 373

Not Used CFT08 1199

R5 Thousands of Dollars

R6 Millions of Dollars

WM Working Months

Contracting Funding Code O ID 2/2

Code identifying the funding type

Date/Time Qualifier O ID 3/3

Code specifying type of date or time, or both date and time

Date O DT 6/6

Date (YYMMDD)

Date/Time Qualifier O ID 3/3

Code specifying type of date or time, or both date and time

Date O DT 6/6

Date (YYMMDD)

Appropriation Code O ID 2/2

Code indicating the funds appropriation

003050F839C0 18 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

CAL Calendar

085

CFT Mandatory

Optional

50

To identify the calendar and working shift details for the plan or schedule

1 If either CAL14 or CAL 15 is present, then the other is required.

1 CAL01 identifies whether a reference number is a calendar or shift.

J, This segment is REQUIREDfor the Cost Performance Report Formats 3 and 4 to describe the summary period groups applicablefor the report described in the CFT

(Cost Reporting Format Type) segment.

2. This segment is used to provide the projected and at complete column information on the reportformats. Repeat this segment as needed (typically five or six times) to describe the projected and at complete columns. This segment is also used to define

how many reporting periods are represented in the projected and at complete columns.

3. The calendar information entered here should match the period ending date

information entered in the PAM (Period Amount) segment (PAM08 data element) for

the projected and at complete columns on Formats 3 and 4.

4. The receiving application may limit the number ofprojected columns that need to be

provided (for example, period number 1, 2, 3, and 4 along with At Complete details).

When sending data, ensure all data content guidelines arefollowed.

Must Use

Ref.

Pes.

CAL01

Must Use CAL02

Data

Element

128

127

Data Element Summary

Name Attributes

Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

70 Calendar Number

Identifies a working calendar (for example, Monday

through Friday) for a company, division, or labor group

Reference Number M AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Enter theperiod number "1", "2", "3", "4", "5", or "At Complete" to identify the projected and at complete timeframes. When period numbers 1

through 5 are used, period number 5 is used to represent the remainder of

the contract (to complete information). For contracts that are close to completion, the last period number applicable can also be used to represent

the remainder ofthe contract.

Not Used CAL03

Not Used CAL04

Not Used CAL05

Not Used CAL06

Not Used CAL07

003050F839C0

344

374

373

337

O ID 2/2

623

Unit of Time Period or Interval

Code indicating the time period or interval

Date/Time Qualifier

Code specifying type of date or time, or both date and time

Date

Date (YYMMDD)

Time

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

O ID 3/3

O DT 6/6

O TM 4/8

19 15 July 1997
839C Project Cost Reporting

Not Used CAL08 678

Not Used CAL09 374

Not Used CAL10 373

Not Used CAL11 337

Not Used CAL12 623

Not Used CAL13 678

Must Use CAL14 673

Must Use CAL15 380

CAL16 369

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Ship/Delivery or Calendar Pattern Code O ID 1/2

Code which specifies the routine shipments, deliveries, or calendar pattern

Date/Time Qualifier O ID 3/3

Code specifying type of date or time, or both date and time

Date O DT 6/6

Date (YYMMDD)

Time O TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Ship/Delivery or Calendar Pattern Code O ID 1/2

Code which specifies the routine shipments, deliveries, or calendar pattern

Quantity Qualifier X ID 2/2

Code specifying the type of quantity

10 Calendar Units

The number of calendar units such as 1 per day or 1 per

week

Quantity X R 1/15

Numeric value of quantity

Enter the number ofreporting months (or periods) for the projected time

frame.

Free-form Description O AN 1/45

Free-form descriptive text Enter a short description ofthe projected timeframe; for example, "FY97"

forfiscal year '97, or "RYRS" for remainingyears on a contract A

maximum offour characters is recommendedfor this data element Provide

this description when CAL02 is "1", "2", "3", "4", or "5". Leave this data

element blank when CAL02 is "At Complete".

003050F839CO 20 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

BSD Breakdown Structure Description

090

BSD Optional (Must Use)

Optional (Must Use)

1To define discrete line items within industry or government reports

1 At least one of BSD02 or BSD03 is required.

1 BSD05 is the summary level structure code reference.

1 BSD07 is the summary level reporting structure identification.

This segment is required. This segment is used to define the reporting structures

(Work Breakdown or Organization Breakdown) for the contract. CDRL and receiving

application requirements will determine the level ofdetail required (for example,

lowest level elements only). Confirm what data elements need to be includedfor the

customer. Associated cost, quantity, and text details for each reporting element are

described using theAMT, QTY, PAM, and MSG segments in this BSD segment loop as

needed.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use BSD01 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

74 Work Breakdown Structure (WBS)

A product-oriented family tree composed of hardware,

software, services, and data that completely defines the

project or program

Use this codefor the Cost Performance Report

Formats 1, 3, and 5, as well as the Cost/Schedule

Status Report and related Variance Analysis

information.

75 Organization Breakdown Structure

A functionally oriented family tree that shows

organization relationships and is used as the framework

for assigning work responsibilities

Use this codefor the Cost Performance Report

Formats 2 and 4. This code can also be used when

Organization Breakdown Structure element codes are used to convey Cost Performance Report Format 5

information.

Must Use BSD02 127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

1. Enter the appropriate Work Breakdown Structure (WBS) or Organization

Breakdown Structure (OBS) element code.

2. The receiving application may have certain requirementsfor the element

codes usedfor bottom line totals for Cost Performance Report Format lora

Cost/Schedule Status Report. Specific element codes may be requiredfor

such items as Overhead, Cost ofMoney, Undistributed Budget, and

Management Reserve. When sending data to the customer, ensure all element code requirements and guidelines arefollowed.

3. Specific element codes may also be requiredfor the Cost Performance

Report Format 3. This includes the codes usedfor beginning period

003050F839C0 21 15 July 1997
839C Project Cost Reporting

BSD03 352

BSD04 1178

BSD05 127

BSD06 1196

information, end ofperiod information, and baseline changes. Again,

confirm any element code requirements with the customer.

Description X AN 1/80

A free-form description to clarify the related data elements and their content

Enter a description ofthe element. This data element is optional, but the

receiving application may need this information. Confirm with the customer

whether this description needs to be provided.

Level O AN 1/3

Reporting structure identification

Enter the reporting structure level numberfor the element code entered in

BSD02. This is REQUIREDfor the Cost Performance Report Formats 1, 2,

and 4, and the Cost/Schedule Status Report.

Reference Number O AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Enter the parent element codefor the element code entered in BSD02. This

is REQUIREDfor all lower level element codesfor the Cost Performance

Reports 1, 2, and 4, and the Cost/Schedule Status Report. This data element

is left blankfor theseformats (Le., no entry is required) when a level 1

element code is entered in BSD02, as it does not have a parent element code.

Breakdown Structure Detail Code O ID 2/2

Codes identifying details relating to a reporting breakdown structure tree Use this data element to describe cost element detailsfor a given element

code or to provide additional cost element detailsfor bottom line totalsfor

Cost Performance Report Formats 1 and 2 or Cost/Schedule Status Report.

01

02

03

04

05

06

07

09

10

26

27

Labor

Direct labor costs

Material

Direct material

Other Direct Costs (ODC)

Other costs associated with a contract such as freight,

travel, postage

Subcontract

Direct subcontract

Labor and Material

Sum of labor and material items

Labor Overhead

Indirect costs associated with direct labor

Material Overhead

Indirect costs associated with direct material

Total Overhead

Total of all indirect costs incurred on a contract

Total General and Administrative

Total of all general and adminstrative types of indirect costs incurred on a contract Recurring

Costs that will incurr continually over the life of the

contract Nonrecurring

003050F839C0 22 15 July 1997
839C Project Cost Reporting

BSD07 1178

Not Used BSD08 786

Costs that will only be incurred once

28 Total

39 Other Costs

53 Production Related

Level O AN 1/3

Reporting structure identification

Enter the reporting structure level numberfor theparent element code

entered in BSD05. This data element is recommended when there is an entry

in BSD05. This data element is left blank when BSDOS is blank.

Security Level Code O ID 2/2

Code indicating the level of confidentiality assigned by the sender to the

information following

003050F839C0 23 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

REF01

REF Reference Numbers

100

BSD Optional (Must Use)

Optional

100

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

Use this segment to provide any reference details associated with a reporting element

described in the BSD (Breakdown Structure Description) segment.

Data Element Summary

Data

Element Name Attributes

128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

3J Office Number

Use this code to identify a Project or Program Office.

79

AT

Cost Account

A management control point for cost and schedule

planning and control; it represents that work assigned to one responsible organization element and to one work

breakdown structure element

Appropriation Number

Use this codefor the appropriation identification. Use

this code only one timefor each BSD reporting

element

Must Use REF02

Not Used REF03

C7 Contract Line Item Number

KU Office Symbol

A number assigned for reference to a specific office

within an organization

127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

352 Description X AN 1/80

A free-form description to clarify the related data elements and their content

003050F839C0 24 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

AMT Monetary Amount

110

BSD Optional (Must Use)

Optional

100

To indicate the total monetary amount

This segment is requiredfor the Cost Performance Report Formats 1, 2, and 3, and the

Cost/Schedule Status Report. For the Cost Performance Report Format 3, this

segment is used in combination with the PAM(Period Amounts) segment.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use AMT01 522 Amount Qualifier Code M ID 1/2

Code to qualify amount

1. For the Cost Performance Report Formats 1 and 2, and the Cost/Schedule

Status Report, typically only the cumulative to date Budget, Earned Value,

and Actual data plus at complete data are requiredfor a specific reporting

element (codes CY, CZ, D9, 49, and 50). As an option for Formats 1 and 2,

currentperiod Budget, Earned Value, and Actual data can be included along

with the cumulative to date information (codes B5, CW, and CX). Current

period information is not neededfor the Cost/Schedule Status Report. Use

codes 47 and 48 to provide Reprogramming amount details ifapplicable.

2. For the Cost Performance Report Format 3, when baseline changes are

included, use any amount qualifier listed here to identify the amount(s)

associated with the line item. The MSG segment can be used to describe the

change ifneeded. Codes B5, CY, and MB are typically usedfor the Begin of

Period and End ofPeriod amount details.

3. Typically values that can be calculated (for example, cost and schedule

variances) are not transmitted. The qualifier codesfor these values are included in the event a customer specifically requests them.

30 Contract Ceiling

The ceiling price applicable to defined effort

32 Target Fee or Profit Amount

The fee (can also be percent) of profit that will apply to defined contract effort

35 Current Target Cost

Sum of Original Contract Target Cost and Negotiated

Contract Changes

3 6 Contract Budget Base (CBB)

Sum of Current Targent Cost and Estimated Cost of

Authorized, Unpriced Work

40 Current Schedule Variance (SV)

The difference between the Budgeted Cost for Work

Performed and the Budgeted Cost for Work Scheduled

41 Current Cost Variance (CV)

The difference between the Budgeted Cost for Work

Performed and the Actual Cost of Work Performed

45 Cumulative Schedule Variance (SV)

003050F839C0 2? 15 July 1997
839C Project Cost Reporting

46

47

48

49

50

51

B

B5

The cumulative difference between the cumulative

Budgeted Cost for Work Performed and the cumulative

Budgeted Cost for Work Scheduled

Cumulative Cost Variance (CV)

The cumulative difference between the cumulative

Budgeted Cost for Work Performed and the cumulative

Actual Cost for Work Performed

Reprogram Cost Variance

Adjustments to previously reported variances due to reprogramming efforts Reprogram Budget

Adjustments to the budget due to reprogramming efforts At Complete Budget (BAC)

The total budget assigned to a work package or task;

also, the total budget of any summary of these work

tasks

At Complete Latest Revised Estimate (LRE)

Latest estimate of cost at completion including over or under runs for all authorized work; it is the sum or the

actuals to date plus the estimate of remaining work

(Estimate to Complete or ETC)

At Complete Variance

The difference between the Budget at Complete and the

Estimate at Complete

Estimated

Indicates the estimated amount

Budgeted

Use this codefor currentperiod budget values.

BM

CW

Adjustments

Earned Value

Use this codefor currentperiod earned value values.

CX Actual

Use this codefor current period actual values.

CY

CZ

D9

MB

MR

ZZ

Cumulative Budget

Cumulative Earned Value

Cumulative Actual

Undistributed Budget

Budget applicable to contract effort, but not yet

assigned to a specific task or activity

Management Reserve

An amount of the total allocated budget withheld for

management control purposes

Mutually Defined

Use this codefor escalation or escalation recovery

values.

Must Use AMT02 782 Monetary Amount M R 1/15

Monetary amount

For all monetary amounts, ifenteringfactored monetary amounts such as thousands ofdollars (notation from CFT02), use only one decimalplace

when applicable.

003050F839C0 26 15 July 1997
839C Project Cost Reporting

Not Used AMT03 478 Credit/Debit Flag Code O ID 1/1

Code indicating whether amount is a credit or debit

003050F839C0 27 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

QTY Quantity

Optional (Must Use)

115

BSD

Optional

100

To specify quantity information

1. This segment is requiredfor the Cost Performance Report Format 4 and is used in

combination with the PAM(Period Amount) segment. This segment is used to convey

working month or hour labor quantities. The qualifier entered in CFT02for Format 4

indicates ifthe values entered in QTY02 are working months (code WM) or hours

(code HR).

2. This segment can also be usedfor Cost Performance Report Format 1, 2, or 3 when

hour quantities are required in addition to monetary amount details (AMT segment).

Must Use

Ref.

Pes.

QTY01

Data

Element

673

Data Element Summary

Name

Quantity Qualifier

Code specifying the type of quantity

Attributes

M ID 2/2

II

37

Completed

The amount finished

Use this codefor currentperiod earned value values.

Work In Process

Use this codefor cumulative to date earned value

values.

A5

AT

AU

AV

AW

AZ

Adjusted Quantity

Actual

Use this codefor current period actual values.

Cumulative Actual

Budget

Use this codefor currentperiod budget values.

Cumulative Budget

Forecast at Complete

Use this codefor Estimate at Complete values.

BC Budget At Complete

Must Use QTY02 380 Quantity M R 1/15

Numeric value of quantity

QTY03 355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

Use this data element only when the quantities entered in QTY02 are factored (hundreds ofhours or thousands ofhours). Use the same qualifier

codefor ALL quantity valuesfor the given reportformat (CFT01). Leave

this data element blank ifworking months or hours are NOTfactored.

003050F839C0 28 15 July 1997
839C Project Cost Reporting

HU Hundred

Use this code to indicate quantities (working months

or hours) arefactored by a hundred - ue., hundreds of

hours.

TH Thousand

Use this code to indicate quantities (working months

or hours) arefactored by a thousand - Le„ thousands

ofhours.

003050F839C0 29 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

PAM Period Amount

120

BSD Optional (Must Use)

Optional

100

To indicate a quantity, and/or amount for an identified period

12

3

4

5

6

7

8

9

10

1

If any of PAM01 PAM02 or PAM03 is present, then all are required.

At least one of PAM02 or PAM05 is required.

If either PAM04 or PAM05 is present, then the other is required.

If either PAM06 or PAM07 is present, then the other is required.

If PAM07 is present, then at least one of PAM08 or PAM09 is required.

If PAM08 is present, then PAM07 is required.

If PAM09 is present, then PAM07 is required.

If PAM10 is present, then at least one of PAM1 1 or PAM12 is required.

If PAM1 1 is present, then PAM10 is required.

If either PAM13 or PAM14 is present, then the other is required.

PAM10, PAM1 1, or PAM12 are used when two dates are required.

1. Use this segmentfor the Cost Performance Report Formats 3 and 4 to describe the

next six reporting periods, theprojected summary timeframes and at complete time

frame as well as provide the monetary amounts or quantities associated with each time

frame. This segment is used to convey the monetary amounts (and hour quantities if

applicable) for Format 3 and working month or hour quantitiesfor Format 4.

2. This segment is repeatedfor each timeframe column (next six reporting periods, 4

or 5 projected, and at complete)for each applicable reporting element code (BSD

segment). Theprojected and at complete time groups directly relate to the timeframes

described in the CAL segmentfor the given reportformat.

Data Element Summary

Ref.

Pes.

PAM01

Data

Element Name

673

Attributes

Quantity Qualifier X ID 2/2

Code specifying the type of quantity

This data element is requiredfor Cost Performance Report Format 4. This

data element may be usedfor the Cost Performance Report Format 3 in the

event hour details need to be included

AV Budget

Use this codefor Format 3 for the current reporting

periodplus 1 through 6 months, and the projected

timeframe quantitiesfor each reporting structure

element (BSD segment). This code can also be used

for the Budget at Complete optional Format 4 (CFT01

is code LP)for the current reporting period plus 1

through 6 months, and the projected timeframe

quantitiesfor each reporting structure element (BSD

segment).

AY Forecast

Use this codefor Format 4for the current reporting

periodplus 1 through 6 months, and the projected

timeframe quantities for each reporting structure

element (BSD segment).

003050F839C0

AZ Forecast at Complete

30 15 July 1997
839C Project Cost Reporting

BC Budget At Complete

PAM02 380 Quantity X R 1/15

Numeric value of quantity

This data element is requiredfor Cost Performance Report Format 4. This

data element may be usedfor the Cost Performance Report Format 3 in the

event hour details need to be included.

PAM03 355 Unit or Basis for Measurement Code X ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

1. This data element is requiredfor the Cost Performance Report Format 4. The code entered here MUST be the same as the code entered in CFT02.

2. This data element may be usedfor the Cost Performance Report Format 3

in the event hour details need to be included. Use code HR.

HR Hours

WM Working Months

PAM04 522 Amount Qualifier Code X ID 1/2

Code to qualify amount

This data element is requiredfor Cost Performance Report Format 3.

49 At Complete Budget (BAC)

The total budget assigned to a work package or task;

also, the total budget of any summary of these work

tasks

Use this codefor the At Complete monetary amounts

for Format 3. It is used only one timefor each BSD

segment.

B5 Budgeted

Use this codefor the current reportingperiodplus 1

through 6 months and theprojected timeframe

monetary amountsfor Format 3.

PAM05 782 Monetary Amount X R 1/15

Monetary amount

This data element is requiredfor Cost Performance Report Format 3.

Must Use PAM06 344

Must Use PAM07 374

003050F839CO

Unit of Time Period or Interval X ID 2/2

Code indicating the time period or interval

Use the code that best applies. Codes "CY" and "FY" can also be used to represent the remaining number ofreporting periodsfor a calendar orfiscal

year. Codes "CY" and "FY" should also be used to represent the balance of

reporting periodsfor the remainder ofthe contract.

CY

FY

MO

QY

SA

Calendar Year

Fiscal Year

Month

Quarter of a Year

Semiannual

WmSBmSmSBBmSSm

Date/Time Qualifier

Code specifying type of date or time, or both date and time

1 74 Month Ending

Use this code when PAM06 is code MO.

31

X ID 3/3

15 July 1997
839C Project Cost Reporting

194 Period End

Use this code when PAM06 is code CY, FY, QY, or

SA.

Must Use PAM08 373 Date

Date (YYMMDD)

Enter the month orperiod ending date.

X DT 6/6

Not Used PAM09 337

Not Used PAM10

Not Used PAM11

Not Used PAM12

374

373

337

Not Used PAM13 1004

Not Used PAM14 954

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Date/Time Qualifier X ID 3/3

Code specifying type of date or time, or both date and time

Date X DT 6/6

Date (YYMMDD)

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Percent Qualifier X ID 1/2

Code to qualify percent

Percent X R 1/10

Percentage expressed as a decimal

003050F839C0 32 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

MSG Message Text

Optional (Must Use)

140

BSD

Optional

1000

To provide a free form format that would allow the transmission of text information.

1 MSG02 is not related to the specific characteristics of a printer, but identifies top of

page, advance a line, etc.

1. Use this segmentfor the Cost Performance Report Format 3 to describe baseline

changes if needed. Only one repetition may be usedfor each reporting structure

element reference (BSD segment) for thisformat, a maximum of50 characters is recommended.

2. This segment can be usedfor the Cost Performance Report Format 5 or Variance

Analysis report narrative. For theseformats, use normal sentence structure, 80

characters per line is fine. A maximum of100 repetitions is allowedfor each reporting

structure element (BSD segment).

3. This segment can also be used to provide a briefnarrativefor the Cost Performance

Report Formats 1, 2, or 4, or the Cost/Schedule Status Report. Only one repetition

may be usedfor each reporting structure element reference (BSD segment).

Data Element Summary

Must Use

Not Used

Ref.

Pes.

MSG01

MSG02

Data

Element

933

934

Attributes

M AN 1/264

Name

Free-Form Message Text

Free-form message text

Printer Carriage Control Code O ID 2/2

A field to be used for the control of the line feed of the receiving printer

003050F839C0 33 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

150

Nl Mandatory

Mandatory

1To identify a party by type of organization, name, and code

1 At least one of N102 or N103 is required.

2 If either N1 03 or N104 is present, then the other is required.

1 This segment, used alone, provides the most efficient method of providing

organizational identification. To obtain this efficiency the "ID Code" (N104) must

provide a key to the table maintained by the transaction processing party.

2 N105 and N106 further define the type of entity in N101.

Wheneverpossible, identification and address information should be provided using

N101, N103, and N104. Use N102 and segments N2, N3, and N4 as applicable when

this information cannot be provided by using one ofthe codes listed in N103.

Must Use

Ref.

Pes.

N101

Data

Element

98

Data Element Summary

Name Attributes

Entity Identifier Code M ED 2/2

Code identifying an organizational entity, a physical location, or an individual

FR

TO

ZD

Message From

Use this code to identify the organization sending the

cost performance data.

Message To

Use this code to identify the organization receiving the

cost performance data.

Party to Receive Reports

The organization designated to receive reports

Use this code to identify the organization that receives an information copy ofthe cost performance data.

Not Used

Not Used

N102 93 Name X AN 1/35

Free-form name

N103 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

1 D-U-N-S Number, Dun & Bradstreet

9 D-U-N-S+4, D-U-N-S Number with Four Character

Suffix

10 Department of Defense Activity Address Code

(DODAAC)

33 Commercial and Government Entity (CAGE)

N104 67 Identification Code X AN 2/20

Code identifying a party or other code

N105 706 Entity Relationship Code O ID 2/2

Code describing entity relationship

N106 98 Entity Identifier Code O ID 2/2

Code identifying an organizational entity, a physical location, or an individual

003050F839C0 34 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

N2 Additional Name Information

160

Nl Mandatory

Optional

1To specify additional names or those longer than 35 characters in length

This segment should only be used when N102 is used and it is necessary to provide

additional name information.

Data Element Summary

Ref. Data

Pes. Element Name

N201 93 Name

Free-form name

N202 93 Name

Free-form name

Attributes

M AN 1/35

O AN 1/35

003050F839CO 35 15 July 1997
83 9C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N3 Address Information

170

Nl Mandatory

Optional

1To specify the location of the named party

This segment should only be used when N102 is used.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use N301 166 Address Information M AN 1/35

Address information

N302 166 Address Information O AN 1/35

Address information

003050F839C0 36 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

N4 Geographic Location

180

Nl Mandatory

Notes:

Optional

1To specify the geographic place of the named party

1 If N406 is present, then N405 is required.

1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2 N402 is required only if city name (N401) is in the USA or Canada.

This segment should only be used when N102 is used.

Data Element Summary

Must Use

Must Use

Must Use

Not Used

Not Used

Ref.

Pes.

N401

N402

N403

N404

N405

N406

Data

Element

19

156

116

26

309

310

Attributes

O AN 2/30

Name

City Name

Free-form text for city name

State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate government agency

Postal Code O ID 3/11

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States)

Country Code O ID 2/3

Code identifying the country

Location Qualifier X ID 1/2

Code identifying type of location

Location Identifier O AN 1/30

Code which identifies a specific location

003050F839C0 37 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

PER Administrative Communications Contact

190

Nl Mandatory

Optional (Must Use)

10

To identify a person or office to whom administrative communications should be directed

1 If either PER03 or PER04 is present, then the other is required.

2 If either PER05 or PER06 is present, then the other is required.

3 If either PER07 or PER08 is present, then the other is required.

At least one repetition ofthe PER segment is requiredper transaction set to identify a

contact person for the report. This should be a specific individual's name.

Must Use

Ref.

Pes.

PER01

Data

Element

366

Data Element Summary

Name Attributes

Contact Function Code M ID 2/2

Code identifying the major duty or responsibility of the person or group named

AA

BD

Authorized Representative

Use this codefor the sending contractor's contact

person 's name. This code is required.

Buyer Name or Department

Use this code to identify the sending contractor's

organization or department. This code is optional

PP Program Manager

Use this code to identify the receiving Program

Manager or Program Office person 's name. This code

is optional

Must Use PER02 93 Name O AN 1/35

Free-form name

1. When PER01 is code AA or PP, enter the person 's name. Provide the last

name,first name, and middle initial if available. Include blank spaces

between name components andperiods after initials. Omit the comma

between the last name andfirst name.

2. When PER01 is code BD, enter the sending contractor's organization code

or department reference.

PER03 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

EM Electronic Mail

FX Facsimile

TE Telephone

PER04 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

PER05 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

EM Electronic Mail

003050F839C0 38 15 July 1997
839C Project Cost Reporting

PER06 364

PER07 365

PER08 364

PER09 443

EX Telephone Extension

FX Facsimile

TE Telephone

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

EM Electronic Mail

EX Telephone Extension

FX Facsimile

TE Telephone

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

Use this data element when PER01 is code AA or PP to enter the title ofthe

person named in PER02.

003050F839C0 39 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

DTM Date/Time Reference

200

Nl Mandatory

Optional (Must Use)

10

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

This segment is required.

Ref. Data

Pes. Element

Must Use DTM01 374

Data Element Summary

Name Attributes

Date/Time Qualifier M ID 3/3

Code specifying type of date or time, or both date and time

275 Approved

Date report was approved by contractor representative

Use this code to indicate the date the data was

approvedfor submission.

Must Use DTM02 373 Date X DT 6/6

Date (YYMMDD)

Not Used DTM03 337 Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Not Used DTM04 623 Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Not Used DTM05 624 Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Not Used DTM06 1250 Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Not Used DTM07 1251 Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003050F839C0 40 15 July 1997
839C Project Cost Reporting

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

210

Mandatory

1To indicate the end of the transaction set and provide the count of the transmitted

segments (including the beginning (ST) and ending (SE) segments).

1 SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use SE01 96 Number of Included Segments M NO 1/10

Total number of segments included in a transaction set including ST and SE

segments

Must Use SE02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set SE02 is the same number as the number in ST02.

003050F839C0 41 15 July 1997

Technical Publications

Periodical

Journal of Research of the National Institute of Standards and Technology—Reports NIST research

and development in those disciplines of the physical and engineering sciences in which the Institute is

active. These include physics, chemistry, engineering, mathematics, and computer sciences. Papers cover a broad range of subjects, with major emphasis on measurement methodology and the basic technology

underlying standardization. Also included from time to time are survey articles on topics closely related to the Institute's technical and scientific programs. Issued six times a year.

Nonperiodicals

Monographs—Major contributions to the technical literature on various subjects related to the

Institute's scientific and technical activities. Handbooks—Recommended codes of engineering and industrial practice (including safety codes) developed in cooperation with interested industries, professional organizations, and regulatory bodies.

Special Publications—Include proceedings of conferences sponsored by NIST, NIST annual reports, and

other special publications appropriate to this grouping such as wall charts, pocket cards, and bibliographies.

National Standard Reference Data Series—Provides quantitative data on the physical and chemical

properties of materials, compiled from the world's literature and critically evaluated. Developed under a worldwide program coordinated by NIST under the authority of the National Standard Data Act (Public

Law 90-396). NOTE: The Journal of Physical and Chemical Reference Data (JPCRD) is published

bimonthly for NIST by the American Chemical Society (ACS) and the American Institute of Physics (AIP).

Subscriptions, reprints, and supplements are available from ACS, 1155 Sixteenth St., NW, Washington, DC

20056.

Building Science Series—Disseminates technical information developed at the Institute on building

materials, components, systems, and whole structures. The series presents research results, test methods, and

performance criteria related to the structural and environmental functions and the durability and safety

characteristics of building elements and systems.

Technical Notes—Studies or reports which are complete in themselves but restrictive in their treatment of

a subject. Analogous to monographs but not so comprehensive in scope or definitive in treatment of the

subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of

other government agencies.

Voluntary Product Standards—Developed under procedures published by the Department of Commerce

in Part 10, Title 15, of the Code of Federal Regulations. The standards establish nationally recognized

requirements for products, and provide all concerned interests with a basis for common understanding of

the characteristics of the products. NIST administers this program in support of the efforts of private-sector

standardizing organizations.

Order the following NIST publications—FIPS and NISTIRs—from the National Technical Information

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FIPS PUB)—Publications in this series

collectively constitute the Federal Information Processing Standards Register. The Register serves as the

official source of information in the Federal Government regarding standards issued by NIST pursuant to the Federal Property and Administrative Services Act of 1949 as amended, Public Law 89-306 (79 Stat. 1127), and as implemented by Executive Order 11717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTIR)—A special series of interim or final reports on work performed by

NIST for outside sponsors (both government and nongovernment). In general, initial distribution is handled

by the sponsor; public distribution is by the National Technical Information Service, Springfield, VA 22161,

in paper copy or microfiche form.
uu

o>s

Oo

E

tandard

o1 eU

tea

-6680

O on

in

en

Ou

Q

£ 3

par

Inst nolo ?urg

Q na

o

o

g ,e

-a '3 3 z c

r5

a

om

V?

<u D

Si « i it pa s

.2O

£