NIST Special Publication 881-82

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 852

Product Activity Data

(Revision 1)

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

Nisr

QC

100

' . U57

MO. 881 -82

1998
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-82

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 852

Product Activity Data

(Revision 1)

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-82

Natl. Inst. Stand. Technol. Spec. Publ. 881-82, 14 pages (Aug. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998
852 Product Activity Data

Functional Group ID=

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Activity Data

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

transaction set can be used by a distributor, warehouse, or retailer to advise a trading partner of inventory, sales, and

other product activity information. Product activity data enables a trading partner to plan and ship, or propose

inventory replenishment quantities, for distribution centers, warehouses or retail outlets. The receiver of the

transaction set will maintain some type of inventory/product movement records for its trading partners to enable

replenishment calculations based on data provided by the distributor, warehouse or retailer.

Notes:

/. Organizations use this transaction set to provide asset balance andpoint ofsale information to vendors

responsiblefor replenishing distribution centers, warehouses or retail outlets.

2. Use a single occurrence ofthis transaction set to report asset balance andpoint ofsale information to a single

vendorfor a single distribution center, warehouse or retail outlet.

Heading:

Must Use

Pos. No. 010Seg.

ID

ST

Name

Transaction Set Header

Req.

Des. MMax.Use

1

Loop

Repeat

Notes and

Comments

Must Use 020 XQ Reporting Date/Action M 1

Must Use 030 XPO Preassigned Purchase Order Numbers O >1

Not Used 040 N9 Reference Number 0 >1

Not Used 050 PER Administrative Communications Contact 0 3 LOOP ID -Nl 200

060 Nl Name 0 1 nl

Not Used 070 N2 Additional Name Information 0 1

Not Used 080 N3 Address Information 0 2

Not Used 090 N4 Geographic Location 0 1

Not Used 100 FOB F.O.B. Related Instructions o 1

Not Used

Not Used

110

120

TD5

DTM

Carrier Details (Routing Sequence/Transit

Time)

Date/Time/Period

o

0

1

>1

Not Used 130 N9 Reference Number 0 >1

Not Used 140 PER Administrative Communications Contact 0 3

Detail:

Pos. No.

Seg.

ID Name

Req.

Des. Max.Use

Loop

Repeat

Notes and

Comments

LOOP ID - LIN 999999

Must Use 150 LIN Item Identification O 1

Not Used 160 CTP Pricing Information 0 25

Not Used 170 P04 Item Physical Details 0 1

Not Used 171 N9 Reference Number 0 >1

003040F852 1 1 June 1998
Not Used 175 AMT Monetary Amount O 10 1,00PID-ZA 99

Must Use 180 ZA Product Activity Reporting M 1 n2

Not Used 190 CTP Pricing Information 0 25

Not Used 200 SDQ Destination Quantity 0 >1

Summary:

Pes. Seg. Req. Loop Notes and

No. IB Name Des. Max.Use Reoeat Comments

Must Use 210 CTT Transaction Totals 0 1 n3

Must Use 220 SE Transaction Set Trailer M 1

Transaction Set Notes

The reporting location is required. The reporting location is specified explicitly in the Nl segment using the

code RL in NlOl, or implicitly using the SDQ segment (Table 2) with the location data elements. They are mutually exclusive (the SDQ and the Nl with NlOl containing RL).

The quantity for the item identified in the LIN segment is required. Quantity is specified either in the ZA

segment (ZA02) or in the SDQ segment, but not in both.

The number of line items (CTTOl) is the accumulation of the number of LIN segments. Hash total (CTT02)

is not used in this transaction set. When sending item and activity data in the LIN loop, the CTT segment is required.

003040F852 1 2 1 June 1998
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 (STOl) used by the translation routines of the

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

selects the Invoice Transaction Set).

Must Use

Must Use

Ref.

Pes.

STOl

ST02

Data

Element

143

329

Data Element Summary

Name Attributes

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

852 X12.52 Product Activity Data

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

003040F852 1 3 1 June 1998
Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Reporting Date/Action

020

Heading

Mandatory

1To specify reporting date and action to be taken

1 XQ02 is the reporting date. If reporting a date range, then XQ02 is the start date and

XQ03 is the end date.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use XQOl 305 Transaction Handling Code M ID 1/1

Code designating the action to be taken by all parties

F Plan and Submit Suggested Purchase Order(s)

G Plan Order(s) and Ship Product

H Notification Only

Must Use XQ02 373 Date M DT 6/6

Date (YYMMDD)

Not Used XQ03 373 Date O DT 6/6

Date (YYMMDD)

003040F852 1 4 1 June 1998
Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

XPO

030

Preassigned Purchase Order Numbers

Heading

Optional (Must Use)

>1

To transmit preassigned purchase order numbers

1 If either XPO03 or XPO04 is present, then the other is required.

1 XPOOl is the preassigned purchase order number. If a range of purchase order

numbers is to be transmitted, use XPOO 1 for the first number and XPO02 as the

ending number.

1 XPO03 and XPO04 specify the location that the purchase order numbers apply to.

Must Use

Not Used

Not Used

Ref.

Pes.

XPOOl

XPO02

XPO03

Not Used XPO04

Data

Element

324

324

66

67

Data Element Summary

Name Attributes

Purchase Order Number M AN 1/22

Identifying number for Purchase Order assigned by the orderer/purchaser

Agency preassignedpurchase order number. There will be a separate

purchase order numberfor each warehouse receiving location.

Purchase Order Number O AN 1/22

Identifying number for Purchase Order assigned by the orderer/purchaser

Identification Code Qualifier X ID 1/2

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

Code (67)

Identification Code X AN 2/17

Code identifying a party or other code

003040F852 1 5 1 June 1998
Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

NX Name

060

Nl Optional

Heading

Optional

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.

2 N1 05 and N1 06 further define the type of entity in N1 0 1

.

Must Use

Not Used

Must Use

Ref.

Pes.

NIDI

N102

N103

Must Use

Not Used

Not Used

N104

N105

N106

Data

Element

98

93

66

67

706

98

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

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

RL Reporting Location

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)

54 Warehouse

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

Identification Code X AN 2/17

Code identifying a party or other code

Enter the code applicable to the warehouse reporting location.

Entity Relationship Code O ID 2/2

Code describing entity relationship

Entity Identifier Code O ID 2/2

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

003040F852 1 6 I June 1998
Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

LIN Item Identification

150

LIN Optional (Must Use)

Detail

Optional (Must Use)

1To specify basic item identification data

12

3

4

5

6

7

8

9

10

11

12

13

14

1

12

If LIN04 is present, then LIN05

If LIN06 is present, then LIN07

If LINOS is present, then LIN09

If LIN 10 is present, then LINl 1 If LIN 12 is present, then LIN 13

If LIN 14 is present, then LIN 15

If LrN16 is present, then LIN 17

If LIN 18 is present, then LIN 19

If LIN20 is present, then LIN21

If LIN22 is present, then LIN23

If LIN24 is present, then LIN25

If LIN26 is present, then LIN27

If LIN28 is present, then LIN29

If LINSO is present, then LIN3

1

LINOl is the line item identificat

s required,

s required,

s required,

s required,

s required,

s required,

s required,

s required,

s required,

s required,

s required,

s required,

s required,

s required.

ion

See the Data Dictionary for a complete list of ID's. LrN02 through LIN31 provide for fifteen (15) different product/service ID's for each

item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No.,

SKU.

Data Element Summary

Ref.

Des.

Must Use LINOl

Must Use LIN02

Must Use LIN03

Data

Element

350

235

234

Not Used LIN04 235

Not Used LIN05 234

Not Used LIN06 235

Not Used LIN07 234

Name Attributes

Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set Enter Agency unique system assigned number.

Product/Service ID Qualifier M ID 2/2

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

FS National Stock Number

SK Stock Keeping Unit (SKU)

UA U.P.C./EAN Case Code (2-5-5)

UD U.P.C./EAN Consumer Package Code (2-5-5)

UI U.P.C. Consumer Package Code (1-5-5)

Product/Service ID M AN 1/30

Identifying number for a product or service

Enter the code ofthe product whose activity is being reported

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234)

Product/Service ID X AN 1/30

Identifying number for a product or service

003040F852 1 1 June 1998
Not Used LINOS 235

Not Used LIN09 234

Not Used LINIO 235

Not Used LINll 234

Not Used LIN12 235

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

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234)

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234)

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234)

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234)

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234)

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234)

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

Product/Service ID X AN 1/30

Identifying number for a product or service

Product/Service ID Qualifier O ID 2/2

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

003040F852 1 8 1 June 1998
Product/Service ID (234)

Not Used LIN31 234 Product/Service ID X AN 1/30

Identifying number for a product or service

003040F852 1 9

1 June 1998
Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ZA Product Activity Reporting

180

ZA Mandatory

Detail

Mandatory

1To provide activity details concerning product being reported

1 If either ZA02 or ZA03 is present, then the other is required.

2 If either ZA04 or ZA05 is present, then the other is required.

3 If either ZA06 or ZA07 is present, then the other is required.

Data Element Summary

Must Use

Ref.

Pes.

ZAOl

Must Use

Must Use

ZA02

ZA03

Not Used

Not Used

Not Used

Not Used

ZA04

ZA05

ZA06

ZA07

Data

Element

859

380

355

374

373

128

127

Name

Activity Code

Attributes

M ID 2/2

Code identifying activity details for the product being reported

Enter QA in first iteration ofZA loop. Enter QS in second iteration ofZA

loop. Enter QL ifrequired in third iteration ofZA loop. Enter QMif

required in fourth iteration ofZA loop. QUQMentries specify the quantity

range vendor is required to maintain.

QA Current Inventory Quantity Available for Shipment or

Sale

Indicates the quantity currently available to be sold or shipped

QL Minimum Inventory Quantity

The minimum inventory quantity for replenishment

purposes

QM Maximum Inventory Quantity

The maximum inventory quantity for replenishment

purposes

QS Quantity Sold

Quantity X R 1/15

Numeric value of quantity

Enter Quantity applicable to QA/QS/QL/QM.

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

Enter unit ofissuefor item being reported.

Refer to 003040 Data Element Dictionary for acceptable code values.

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)

Reference Number Qualifier X ID 2/2

Code qualifying the Reference Number.

Reference Number X AN 1/30

Reference number or identification number as defmed for a particular

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

003040F852 1 10 1 June 1998

j

i:
Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

CTT Transaction Totals

210

Summary

Optional (Must Use)

1To transmit a hash total for a specific element in the transaction set

1 If CTT03 is present, then CTT04 is required.

2 If CTT05 is present, then CTT06 is required.

1 This segment is mtended to provide hash totals to validate transaction completeness

and correctness.

Data Element Summary

Must Use

Not Used

Not Used

Not Used

Not Used

Not Used

Not Used

Ref.

Pes.

CTTOl

CTT02

CTT03

CTT04

CTT05

CTT06

CTT07

Data

Element Name Attributes

354 Number of Line Items M NO 1/6

Total number of line items in the transaction set Enter the number ofoccurrences ofLIN.

347 Hash Total O R 1/10

Sum of values of the specified data element. All values in the data element will

be summed without regard to decimal pomts (explicit or implicit) or signs.

Truncation will occur on the left most digits if the sum is greater than the

maximum size of the hash total of the data element.

Example:

-.0018 First occurrence of value being hashed. .18 Second occurrence of value

being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth

occurrence of value being hashed. 1855 Hash total prior to truncation.

855 Hash total after truncation to three-digit field. 81 Weight O R 1/10

Numeric value of weight

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

183 Volume O R 1/8

Value of volumetric measure 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

352 Description O AN 1/80

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

003040F852 1 11 1 June 1998
Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

220

Summary

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

Des. Element Name Attributes

Must Use SEOl 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 Enter the same number cited in ST02.

003040F852 1 12 1 June 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

Instimte'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 arid 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.
oU -oc _ S o c?5 c o E 3

CUi—i

O)—

Q

S . o • TO P Z

oooI ON

ON

00o(N

oo

J -5 « S ^ -£ — U O a.