NIST Special Publication 881-81

Nisr

QC

100

.U57

NO. 881-81

1998

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003060 Transaction Set 830W

Planning Schedule with Release

Capability (War Material Requirement)

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Teciinology
m he National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in

-M- 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 Properties^

• Analytical Chemistry

• Process Measurements

• Surface and Microanalysis Science

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Optical Technology

• Ionizing Radiation

• Time and Frequency'

• 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^

• 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. ^Some elements at Boulder, CO.
NIST Special Publication 881-81

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003060 Transaction Set 830W

Planning Schedule with Release

Capability (War Material Requirement)

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

August 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-81

Natl. Inst. Stand. Technol. Spec. Publ. 881-81, 22 pages (Aug. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998
830 Planning Schedule with Release Capability

Functional Group ID-PS

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule

with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI)

environment. The transaction set can be used to provide for customary and established business practice relative to the transfer of forecasting/material release information between organizations. The planning schedule transaction

may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the

buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used

as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative

quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.

Notes:

1. Organizations use this transaction set to report war reserve material (WRM) requirements data to integrated

material managers (IMMs)/inventory controlpoints (ICPs).

2. Use a single occurrence ofthis transaction set to transmit war reserve material requirements to one or more

organizations. Use one occurrence ofthis transaction set to transmit a single or multiple transactions.

Heading:

Pes. Seg. Req. No. ID Name Des. Max.Use

Must Use 010 ST Transaction Set Header M 1

Must Use 020 BFR Beginning Segment for Planning Schedule M 1

Not Used 025 XPO Preassigned Purchase Order Numbers 0 >1

Not Used 040 CUR Currency 0 1

Not Used 050 REF Reference Identification 0 12

Not Used 060 PER Administrative Communications Contact 0 3

Not Used 070 TAX Tax Reference O 3

Not Used 080 FOB F.O.B. Related Instructions 0 1

Not Used 090 CTP Pricing Information 0 25

Not Used 100 SAC Service, Promotion, Allowance, or Charge o 25

Information Not Used 110 CSH Sales Requirements 0 1

Not Used 120 ITD Terms of Sale/Deferred Terms of Sale 0 2

Not Used 130 DTM Date/Time Reference 0 10

Not Used 140 PID Product/Item Description 0 200

Not Used 150 MEA Measurements o 40

Not Used 160 PWK Paperwork o 25

Not Used 170 PKG Marking, Packaging, Loading o 25

Not Used 180 TDl Carrier Details (Quantity and Weight) 0 2

Not Used 190 TD5 Carrier Details (Routing Sequence/Transit 0 12 Time)

Not Used 200 TD3 Carrier Details (Equipment) o 12

Not Used 210 TD4 Carrier Details (Special Handling, or 0 5 Hazardous Materials, or Both)

Not Used 220 MAN Marks and Numbers 0 10

Loop

Repeat

Notes and

Comments

003060F830W0 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

LOOP ID -Nl

Must Use 230 Nl Name 0 1

Not Used 240 N2 Additional Name Information 0 2

Not Used 250 N3 Address Information 0 2

Not Used 260 N4 Geographic Location 0 1

Not Used 270 REF Reference Identification 0 12

Not Used 280 PER Administrative Communications Contact 0 3

Not Used 290 FOB F.O.B. Related Instructions 0 1

LOOP ID - LM >1

Not Used 300 LM Code Source Information 0 1

Not Used 310 LQ Industry Code M 100

Detail:

r Us. aeg. LfOOp I^UICA allU No. ID Name Des. Max.Use Repeat Comments

LOOP ID -LIN >1

Must Use 010 LIN Item Identification M I

Not Used 020 UIT Unit Detail 0 I

Must Use 021 DTM Date/Time Reference o 10

Not I Ised 030 CUR dirrencv 0 1

Not Used 060 P03 Additional Item Detail o 25

Not Used 070 CTP Pricing Information o 25

Not Used 080 PID Product/Item Description o 1000

Not Used 090 MEA Measurements o 40

Not Used 100 rWK. Paperwork (J 25

Not Used 1 10 PKG Marking, Packaging, Loading 0 25

Not Used 120 P04 Item Physical Details 0 1

Not Used 130 PRS Part Release Status 0 1

140 REF Reference Identification 0 12

1 SO PFR A Hminictt"5itivp (^rttnmiiniPfitinnc C^nnfact -JJ

Not Used 170 SAC Service, Promotion, Allowance, or Charge 0 25

Information Not Used 180 ITD Terms of Sale/Deferred Terms of Sale 0 2

Not Used 190 TAX Tax Reference 0 3

Not Used 200 FOB F.O.B. Related Instructions 0 1

Not Used 210 LDT Lead Time 0 12

Not Used 220 QTY Quantity o >1 nl

Not Used 230 ATH Resource Authorization 0 20

Not Used 240 TDl Carrier Details (Quantity and Weight) 0 1

Not Used 250 TD5 Carrier Details (Routing Sequence/Transit 0 12 Time) Not Used 260 TD3 Carrier Details (Equipment) 0 12

Not Used 270 TD4 Carrier Details (Special Handling, or 0 5 Hazardous Materials, or Both) Not Used 280 MAN Marks and Numbers 0 10

Not Used 290 DD Demand Detail 0 10 LOOP ID - SLN 100

Not Used 300 SLN Subline Item Detail 0 1

Not Used 310 PID Product/Item Description o 1000

Not Used 315 NMl Individual or Organizational Name o 10

LOOP ID-Nl 200

003060F830W0 2 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Must Use 320 Nl

Not Used 330 N2

Not Used 340 N3

Not Used 350 N4

Not Used 360 REF

370 PER

Not Used 380 FOB

IVlUol UoC

Must Use 400 LQ

410 FST

Not Used 420 SDQ

430 LM

Must Use 440 LQ

Not I ked 450 SDP

Not Used 460 FST

Not Used 470 SHP

Not Used 480 REF

Summary:

Not Used

Pos. No. 010Seg.

ID

CTT

Must Use 020 SB

EOOP ID - SHP

Shipped/Received Information

Reference Identification

Name

Transaction Totals

Transaction Set Trailer

O

O

Name

Additional Name Information

Address Information

rrpnoranhif T nratinn

Reference Identification

Administrative Communications Contact o

o

o

o

o

o 1

2

2

1

12

3

F.O.B. Related Instructions 0 1

hUUf lU - LM >l

Code Source Information 0 1

Industry Code M 100

LOOP ID -FST >1

Forecast Schedule

Destination Quantity

0

0

1

50

n2

LOOP ID - LM >1

Code Source Information

Industry Code

0

M

1

100

LOOP ID - SDP 260

Ship/Delivery Pattern

Forecast Schedule

0 1 0 260

25

Req.

Pes. O

M

Max.Use

1

1

Loop

Repeat

Notes and

Comments

n3

Transaction Set Notes

1. QTY is used to specify supplemental quantities relevant to the forecast function. However, QTY is not related

to the actual forecast quantity in the FST segments.

2. At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two

loops are mutually exclusive.

3. Number of line items (CTTOl) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is the sum of the values of the quantities (FSTOl) for each FST segment.

003060F830W0 3 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Heading

Mandatory

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

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

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

selects the Invoice Transaction Set).

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use STOl 143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

830 X12.14 Planning Schedule with Release Capability

Must Use ST02 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 A unique number assigned by the originator ofthe transaction set, or by the

originator's application program.

003060F830W0 4 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

BFR

020

Beginning Segment for Planning Schedule

Heading

Mandatory

1To indicate the beginning of a planning schedule transaction set; whether a ship or deUvery based forecast; and related forecast envelope dates

1

12

3

5

6

At least one of BFR02 or BFR03 is required.

If BFROl contains the value "04" (Net Change), BFR09 is required.

BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.

BFR06 is the forecast horizon start date: The date when the forecast horizon

(envelope) begins.

BFR07 is the forecast horizon end date: The date when the forecast horizon

(envelope) ends.

BFR08 is the date forecast generated: The date the forecast data was generated.

BFR09 is the date forecast updated: The date the forecast was updated with "net change" data. (Used only when data element 353 in BFROl contains the value "04",

meaning net change.)

Comments:

Data Element Summary

Must Use

Ref.

Pes.

BFROl

Must Use BFR02

Not Used BFR03

Must Use BFR04

Must Use BFR05

Must Use BFR06

Data

Element

353

127

328

675

676

373

Name Attributes

Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set 00 Original

77 Simulation Exercise

Use to identify a simulated mobilization exercise

transaction set. Activities initiating simulated

mobilization exercises must ensure complete

coordination with all activities involved. All

transaction set recipients must use extreme caution to ensure that individual transactions do notprocess as

action documents which offectg^ffMfttable records.

Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Use code "Z"for this data element to satisfy XI2 syntax requirements.

Release Number X AN 1/30

Number identifying a release against a Purchase Order previously placed by

the parties mvolved in the transaction

Schedule Type Qualifier M ID 2/2

Code identifying the type of dates used when defining a shipping or delivery

time in a schedule or forecast

PR Planned Requirement Based

Use to indicate that requirements data reflect

forecasted requirements.

Schedule Quantity Qualifier M ID 1/1

Code identifying the type of quantities used when defining a schedule or

forecast

A Actual Discrete Quantities

Use to indicate that quantities reflect discrete

requirements.

Date M DT 6/6

Date (YYMMDD)

003060F830W0 5 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

BFR07 373

Must Use BFR08

Not Used BFR09

Not Used BFRIO

Not Used BFRll

Must Use BFR12

373

373

367

324

783

Must me to identify theforecastperiod start date.

Date

Date (YYMMDD)

O DT 6/6

Use to identify theforecast period end date. 4 P*-: - v-^i';" Date

Date (YYMMDD)

M DT6/6

Use to identify the transaction setpreparation date. This date corresponds to the Universal Time Coordinate (UTC).

Not Used BFR13 306

Date O DT 6/6

Date (YYMMDD)

Contract Number O AN 1/30

Contract number

Purchase Order Number O AN 1/22

Identifying number for Purchase Order assigned by the orderer/purchaser

Planning Schedule Type Code O ID 2/2

Code identifying type of planning schedule used

XF War Reserve Forecast

Must use to indicate the transaction is a war reserve material requirementsforecast

Action Code O ID 1/2

Code indicating type of action

003060F830W0 6 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment: Nl

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

NlOl

Not Used

Must Use

N102

N103

Name

230

N1 Optional (Must Use)

Heading

Optional (Must Use)

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

1 At least one of N102 or N103 is required.

2 If either N103 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 N1 05 and N1 06 further define the type of entity in N1 0 1

.

Must use this 1/N1/230 loop to identify the organization originating the transaction set.

Data

Element

98

93

66

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

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

41 Submitter

Entity transmitting transaction set Must use to identify the organization submitting war

reseryematerMl(WMM data.

Name X AN 1/35

Free-form name

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)

M4 Department of Defense Routing Identifier Code (RIC)

An integral and predetermined participant in an

established logistical system performing general logistic

control, distribution, and storage functions

Must Use N104 67 Identification Code

Code identifying a party or other code

X AN 2/20

Not Used N105 706 Entity Relationship Code

Code describing entity relationship

O ID 2/2

Must Use N106 98 Entity Identifier Code

Code identifying an organizational entity,

O ID 2/2 a physical location, or an individual

FR Message From

Must use to indicate the organization cited in N104 is originating the transaction.

003060F830W0 7 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LIN Item Identification

010

LIN Mandatory

Detail

Mandatory

1To specify basic item identification data

12

3

4

5

6

7

8

9

10

11

12

13

14

1 LINOl is the line item identification

1 See the Data Dictionary for a complete list of IDs. 2 LIN02 through LINS 1 provide for fifteen different product'service IDs for each item.

For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

1. Must use the 2/LIN/OlO loop to identify the type of WRMand information related to the requirementforecast

If either LIN04 or LINOS is present. then the other is required.

If either LIN06 or LIN07 is present. then the other is required.

If either LINOS or LIN09 is present. then the other is required.

If either LINIO or LINll is present. then the other is required.

If either LIN12 or LIN13 is present, then the other is required.

If either LIN14 or LIN15 is present. then the other is requu-ed.

If either LIN16 or LIN17 is present, then the other is requu^ed.

If either LIN18 or LIN19 is present, then the other is required.

If either LIN20 or LIN21 is present. then the other is required.

If either LIN22 or LIN23 is present. then the other is required.

If either LIN24 or LIN25 is present. then the other is required.

If either LIN26 or LIN27 is present. then the other is required.

If either LIN28 or LIN29 is present. then the other is required.

If either LIN30 or LIN31 is present. then the other is required.

2. Detailed WRMdata identifies incremental monthlyforecast quantitiesfor a single

line item stratified by type of WRMor by type of WRMandproject code.

3. When stratifying only by type of WRM(for other than Pre-Positioned War Reserve

(PWR) requirements), use a single iteration ofthe 2/LM/390 loop to identify a single

War Reserve Material Requirement Code and use multiple iterations ofthe 2/FST/410

loop to identify incremental monthlyforecast quantities. Do not use the 2/LM/430 loop.

This stratification method requires multiple iterations ofthe 2/LIN/OlO loopfor a

single line item to identify each type of WRM.

4. When stratifying by type of WRMandproject code (for other than PWR

requirements), use a single iteration ofthe 2/LM/390 loop to identify a single War

Reserve Material Requirement Code; use multiple iterations ofthe 2/FST/410 loop to identify incremental monthlyforecast quantities; and use a single iteration ofthe

2/LM/430 loopfor each iteration ofthe 2/FST/410 loop to identify the project code

associated with the quantity. This stratification method requires multiple iterations of

the 2/LIN/OlO loopfor a single line item to identify each type of WRM.

5. For PWRforecast requirements, do not use the 2/LM/390 loop to identify the War

Reserve Material Requirement Code. Instead, use two iterations ofthe 2/FST/410 loop

to identify applicable incremental monthlyforecast quantities; and use a single

iteration ofthe 2/LM/430 loop, for each iteration ofthe 2/FST/410 loop, to identify the

War Reserve Material Requirement Code and/orproject code associated with the

quantity.

Not Used

Ref.

Pes.

LINOl

Data Element Summary

Data

Element

350

Name Attributes

Assigned Identification O AN 1/20

Alphanumeric characters assigned for differentiation within a transaction set

003060F830W0 8 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Must Use LIN02 235

Must Use LIN03

LIN04

234

235

LINOS

Not Used LIN06

Not Used LIN07

Not Used LINOS

Not Used LIN09

Not Used LINIO

Not Used LINll

Not Used LIN12

234

235

234

235

234

235

234

235

Product/Service ID Qualifier M ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

/. Use only one of codes Al, A2, A4, FB, FS, MG, or YP to identify the

material Must use National Stock Number (NSN) when known.

2. When citing a manufacturer's part number (code MG), always use code

ZB in LIN04 to identify the manufacturer's commercial and government

entity (CAGE) code.

A1 Plant Equipment Number

Item identifier is a plant equipment number

A2

'pse to identify plant equipment

Department of Defense Identification Code (DoDIC)

Qualifies a code that uniquely identifies a type of

explosive or ammunition

Use to identify ammunition items.

Subsistence Identification Number

Item identifier is a brand-name resale subsistence item

Vse to identify subsistence items. S

Form Number

Vse to identify theform stock number.

National Stock Number

Must use the NSN when known.

Manufacturer's Part Number

Use to identify nonstandard material

Publication Number

Use to identify the publication stock number.

M AN 1/40

A4

FB

FS

MG

YP

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

ZB Commercial and Government Entity (CAGE) Code

A code that identifies a commercial contractor

authorized to do business with the U.S. government

Use with LIN02 code MG to uniquely identify a

manufacturer's part number.

Product/Service ID X AN 1/40

Identifying number for a product or service

Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service

Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service

Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service

Product/Service ID Qualifier X ID 2/2

003060F830W0 9 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Not Used LIN13 234

Not Used LIN14 235

Not Used LIN15 234

Not Used LIN16 235

Not Used LIN17 234

Not Used LIN18 235

Not Used LIN19 234

Not Used LIN20 235

Not Used LIN21 234

Not Used LIN22 235

Not Used LIN23 234

Not Used LIN24 235

Not Used LIN25 234

Not Used LIN26 235

Not Used LIN27 234

Not Used LIN28 235

Not Used LIN29 234

Not Used LIN30 235

Not Used LIN31 234

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

Product/Service ID Qualifier

Code identifying the type/source of the descriptive

Product/Service ID (234)

Product/Service ID

Identifying number for a product or service

number used in

X

X

number used in

X

mmiber used in

X

number used in

number used in

number used in

number used in

number used in

number used in

AN 1/40

ID 2/2

AN 1/40

ID 2/2

AN 1/40

ID 2/2

AN 1/40

ID 2/2

AN 1/40

ID 2/2

AN 1/40

ID 2/2

AN 1/40

ID 2/2

AN 1/40

ID 2/2

AN 1/40

ID 2/2

number used in

X AN 1/40

003060F830W0 10 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

DTM Date/Time Reference

021

LIN Mandatory

Detail

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.

Must use to identify the date oftransaction preparation.

Data Element Summary

Must Use

Must Use

Not Used

Not Used

Not Used

Ref.

Pes.

DTMOl

DTM02

DTM03

Not Used DTM04

DTM05

DTM06

DTM07

Data

Element

374

373

337

623

624

1250

1251

Name Attributes

Date/Time Qualifler M ID 3/3

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

097 Transaction Creation

Use to identify the date oftransaction preparation.

Date X DT6/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 fu-st 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

003060F830W0 11 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

REF Reference Identification

140

LIN Mandatory

Detail

Optional

12

To specify identifying information

1 At least one of REF02 or REF03 is required.

2 If either C04003 or C04004 is present, then the other is required.

3 If either C04005 or C04006 is present, then the other is required.

1 REF04 contains data relating to the value cited in REF02.

Ref.

Pes.

Must Use REFOl

Data

Element

128

Not Used

Not Used

Not Used

Not Used

Not Used

Not Used

Not Used

Not Used

REF02

REF03

REF04

C04001

C04002

C04003

C04004

C04005

C04006

127

352

C040

128

127

128

127

128

127

Data Element Summary

Name Attributes

Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

TN Transaction Reference Number

'kJse to identify the transaction number.

Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

Description X AN 1/80

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

Reference Identifier O

To identify one or more reference numbers or identification numbers ds

specified by the Reference Qualifier

Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

003060F830W0 12 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

320

Nl Optional (Must Use)

Detail

Optional (Must Use)

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

1 At least one of N1 02 or N1 03 is required.

2 If either N1 03 or N1 04 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.

N105 and N106 further define the type of entity in NlOl.

Must use one iteration ofthis 2/N1/320 loop to identify the organization to receive

the transaction.

^. Use additional iterations to identify other organizations associated with the

transaction.

Data Element Summary

Must Use

Ref.

Des.

NlOl

Not Used

Must Use

N102

N103

Must Use

Not Used

N104

N105

N106

Data

Element

98

Name Attributes

Entity Identifier Code M ID 2/2

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

KA Item Manager

The address of the person responsible for the

management of an item of supply

Must use to indicate the IMM/ICP.

ZD Party to Receive Reports

The organization designated to receive reports

Use to indicate the organization(s) to receive reports. ;> 93 Name X AN 1/35

Free-form name

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)

M4 Department of Defense Routing Identifier Code (RIC)

An integral and predetermined participant in an

established logistical system performing general logistic

control, distribution, and storage functions

67 Identification Code X AN 2/20

Code identifying a party or other code

706 Entity Relationship Code O ID 2/2

Code describing entity relationship

98 Entity Identifier Code O ID 2/2

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

TO Message To

Must use with 2/N101/320 code KA to indicate the^

organization cited in N104 is receiving the

transaction.

003060F830W0 13 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LM Code Source Information

390

LM Optional (Must Use)

Detail

Optional (Must Use)

1To transmit standard code list identification information

1 LM02 identifies the applicable industry code list source information.

/. Use the 2/LM/390 loop to identify coded information maintained in department or agency documentation.

2. Use the 2/LM/390 loop to stratifyforecastsfor other than PWR requirements by type

ofWar Reserve Material Requirements Code. Cite the associated quantities in one or more iterations ofthe 2/FST/410 loop.

3. Do not use to identify the War Reserve Material Requirement Codefor PWR

requirements.

Must Use

Not Used

Ref.

Pes.

LMOl

LM02

Data

Element

559

822

Data Element Summary

Name Attributes

Agency Qualifier Code M ID 2/2

Code identifying the agency assigning the code values

DF Department of Defense (DoD)

Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source Qualifier

003060F830W0 14 13 April 1998
83 OW - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

LQOl

Must Use LQ02

Industry Code

400

LM Optional (Must Use)

Detail

Mandatory

100

Code to transmit standard industry codes

1 If LQOl is present, then LQ02 is required.

Use to identify codes, as appropriate, consistent with management information

requirements.

Data Element Summary

Data

Element

1270

Name Attributes

O ID 1/3

1271

Code List Quaiifler Code

Code identifying a specific industry code list 0 Document Identification Code

Codes that subclassify a transaction

LZ War Reserve Material Requirement Code

Must usefor otJier than PWR requirements to identify

the type of war reserve requirementfor which the

forecast applies. M&amaM ,»» Industry Code X AN 1/30

Code indicating a code from a specific mdustry code list

003060F830W0 15 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

FSTOl

Must Use FST02

Must Use FST03

Must Use FST04

FST Forecast Scliedule

410

FST Optional

Detail

Optional

1To specify the forecasted dates and quantities

1 If either FST06 or FST07 is present, then the other is required.

2 If either FST08 or FST09 is present, then the other is required.

1 If FST03 equals "F" (indicating flexible interval), then FST04 and FST05 are

required. FST04 would be used for the start date of the flexible interval and FST05

would be used for the end date of the flexible interval.

1 As qualified by FST02 and FST03, FST04 represents either a discrete forecast date,

the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start date

of a flexible interval.

2 FST06 qualifies the time in FST07. The purpose of the FST07 element is to express

the specific time of day in a 24-hour clock to satisfy "just-in-time" requirements. As

an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as a.m. or p.m.

/. Use multiple 2/FST/410 loop iterations to identify incremental monthlyforecast

quantitiesfor other than PWR requirements associated with the War Reserve Material

Requirements Code identified in the 2/LM/390 loop.

2. Use only two iterations ofthe 2/FST/410 loop when identifying the PWR

requirement One occurrence must include a FST02 code ofD and the second must

include a FST02 code ofS.

Data Element Summary

Data

Element

380

680

Name Attributes

M R 1/15

681

Not Used FST05

373

373

Quantity

Numeric value of quantity

Use to identify the monthlyforecast quantity. Express as a whole number

with no decimal

Forecast Qualifier M ID 1/1

Code specifying the sender's confidence level of the forecast data or an action

associated with a forecast

D Planning

Usefor all Other War Reserve Material Requirements

(OWMR), repairable return, and Pre-positioned War

Reserve Material Requirements (PWRMR) (nonprotected) transactions to indicate the requirement

reflects aplanning requirementforecast.

S Strike Protection

Usefor all PWRMR (protected) transactions to indicate the requirement reflects aprotected

requirementforecast. |

Forecast Timing Qualifier M ID 1/1

Code specifying interval grouping of the forecast

M Monthly Bucket (Calendar Months)

Use to indicate quantities are reflected in monthly

increments.

Date M DT6/6

Date (YYMMDD)

Use to identify the specific month oftheforecastperiodfor which the

quantity applies: Assume that thefirst day ofthe month applies.

Date O DT 6/6

003060F830W0 16 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Not Used FST06

Not Used FST07

Not Used FST08

Not Used FST09

Not Used FSTIO

Date (YYMMDD)

374 Date/Time Qualifier X ID 3/3

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

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)

128 Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

783 Planning Schedule Type Code O ID 2/2

Code identifying type of plarming schedule used

003060F830W0 17 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

LM Code Source Information

430

LM Optional

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use LMOl

Not Used LM02

Detail

Optional

1To transmit standard code list identification information

1 LM02 identifies the applicable industry code list source information.

/. Use this 2/LM/430 loop to identify coded information maintained in departmental or agency documentation.

2. Use this 2/LM/430 loopfor OWMR and repairable return transactions to stratify

monthlyforecasts by project code.

3. Use this 2/LM/430 loopfor PWR transactions to stratify monthlyforecasts by type of

WRMand/orproject code.

Data Element Summary

Data

Element Name

559

Attributes

Agency Qualifier Code M ID 2/2

Code identifying the agency assigning the code values

DF Department of Defense (DoD)

822 Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source Qualifier

003060F830W0 18 13 April 1998
830W - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

LQOl

Must Use LQ02

LC^ Industry Code

440

LM Optional

Detail

Mandatory

100

Code to transmit standard industry codes

1 If LQOl is present, then LQ02 is required.

Use to identify codes, as appropriate, consistent with management information

requirements.

Data

Element

1270

1271

Data Element Summary

Name Attributes

Code List Qualifier Code O ID 1/3

Code identifying a specific industry code list 78 Project Code

Codes that relate a transaction to special programs,

exercises, projects, operations, or other purposes

Use as needed to identify the applicable war reserve project code,

LZ War Reserve Material Requirement Code

%ust use to identify PWR requirementforecast.

Industry Code X AN 1/30

Code indicating a code from a specific industry code list

003060F830W0 19 13 April 1998
83 OW - Planning Schedule with Release Capability (War Material Requirement)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

020

Summary

Mandatory

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

segments (including the beginning (ST) and endmg (SE) segments)

1 SE is the last segment of each transaction set.

Data Element Summary

Must Use

Must Use

Ref.

Pes.

SEOl

SE02

Data

Element

96

329

Name Attributes

Number of Included Segments M NO 1/10

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

segments

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 Cite the same number as the one cited in ST02.

003060F830W0 20 13 April 1998


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 or Internal Reports (NISTIR)—The series includes 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 handled by sales through the National Technical

Information Service, Springfield, VA 22161, in hard copy, electronic media, or microfiche form. NISTIR's

may also report results of NIST projects of transitory or limited interest, including those that will be

published subsequently in more comprehensive form.
sBoU

T3

T3C

O C/3

'ft

C

O

e 3

0«i—'

<u

—

Q

g . o

o?

00o04Q 0 00 1 ^ oo

6^

o