AlllOS PUBLICATIONS

4

lIHIHIIIIiifllllM

Nisr

QC

100

.U57

NO. 881 -33

1998

NIST Special Publication 881-33

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 864

Text Message (Revision 1)

Implementation Convention

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

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 864

Text Message (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

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

Natl. Inst. Stand. Technol. Spec. Publ. 881-33, 14 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
864 Text Message

Functional Group ID= TX

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data content of the Text Message

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

transaction set can be used to provide users with a capability to electronically move messages, contracts,

explanations, and other one-time communications. It is the intent of this transaction set to provide electronic

communication (messages) for people, not for computer processing. The use of the transaction set to transmit quasi

or unique transaction set standards is discouraged. The use of the Text Message transaction set demands of the

sender certain detailed information about the recipient. The transaction set's purpose is to provide communication to the recipient in some human-readable form. The recipient's network will dictate what capabilities are available for

delivery of the information. It is the responsibility of the sender to obtain this information and include it in the

transmission.

Heading:

Pos. Seg. Req. Loop Notes and

1>0. Name ilCS. IVf ax.Usc Repeat Comments

Must Use 010 ST Transaction Set Header M 1

Must Use 020 BMG Beginning Segment For Text Message M 1

030 DTM Date/Time/Period 0 10 LOOP ID - Nl 200

040 Nl Name 0 1

Not Used 050 N2 Additional Name Information 0 2

Not Used 060 N3 Address Information o 2

Not Used 070 N4 Geographic Location u 1

080 REF Reference Numbers 0 12

090 PER Administrative Communications Contact 0 3

Detail:

Pos. Seg. Req. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

LOOP ID -MIT >1

Must Use 010 MIT Message Identification M 1 LOOP ID-Nl 200

Not Used 020 Nl Name 0 . 1

Not Used 030 N2 Additional Name Information 0 2

Not Used 040 N3 Address Information 0 2

Not Used 050 N4 Geographic Location 0 1

Not Used 060 REF Reference Numbers 0 12

Not Used 070 PER Administrative Communications Contact 0 3

Must Use 080 MSG Message Text M 100000

Summary:

Pos. Seg. Req. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

Must Use 010 SE Transaction Set Trailer M 1

003040F864 1 8 April 1997
864 Text Message

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).

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

864 X12.34 Text Message

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 to this transaction setfor controlpurposes.

Usually assigned by the translation software. This is the same number that

appears in the SE02.

003040F864 1 2 8 April 1997
864 Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

BMG Beginning Segment For Text Message

020

Heading

Mandatory

1To indicate the beginning of a Text Message Transaction Set

1 BMG02 contains the message subject.

Must Use

Ref.

Pes.

BMGOl

BMG02

Not Used BMG03

Data

Element

353

01

03

Data Element Summary

Name Attributes

Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set 00 Original

Use to indicate an original transmittal.

Cancellation

Use to indicate the cancellation ofapreviously

transmitted message text. Delete

Use to indicate the deletion ofa MITloopfrom a

previous message. When used, identify the previous

message in the l/REF/080 segment and identify the

original MITOl number being deleted in MITOl of

2/MIT/OlO segment State DELETED in MSGOl of

the 2/MSG/080 segment.

Replace

Use to indicate the replacement ofa MITloopfrom a

previous message. When used, identify the previous

message in the l/REF/080 segment and identify the

original MITOl number being replaced in MITOl of

2/MIT/OlO segment

Duplicate

Use to indicate the re-transmission ofa previousl^^^^'^^L

transmitted text information.

*

O AN 1/80

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

Use to provide a briefoverall subject ofthe text message.

Transaction Type Code O ID 2/2

Code specifying the type of transaction

Refer to 003040 Data Element Dictionary for acceptable code values.

05

640

07

352 Description

003040F864 1 3 8 April 1997
864 Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

DTM Date/Time/Period

030

Heading

Optional

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.

Ref.

Pes.

Must Use DTMOl

Not Used

DTM02

DTM03

Not Used DTM04

Not Used

DTM05

DTM06

Not Used DTM07

Data

Element

374

373

337

623

624

1250

1251

Data Element Summary

Name Attributes

Date/Time Qualifier M ID 3/3

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

097 Transaction Creation

Use to indicate the date the transaction set was

created.

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

Refer to 003040 Data Element Dictionary for acceptable code values.

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

Refer to 003040 Data Element Dictionary for acceptable code values.

Date Time Period X AN 1/35

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

003040F864 1 4 8 April 1997
864 Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Nl Name

040

Nl Optional

Heading

Optional

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 N1 05 and N1 06 further defme the type of entity in N1 0 1

.

Must Use

Ref.

Pes.

NlOl

N102

N103

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

FR Message From

TO Message To

Name X AN 1/35

Free-form name

Wheneverpossible, identification and address information should be

provided using NlOl, N103 and N104. Use N102 when the address cannot

be provided using one ofthe codes listed in N103.

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

Use ofthe DUNS or DUNS+4 number is preferred over any other coded number to identify an entity.

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

Suffix

Use ofthe DUNS or DUNS+4 number is preferred over any other coded number to identify an entity.

10 Department of Defense Activity Address Code

(DODAAC)

Use when a Federal Agency is known only by its DoDAAC or Civilian Agency Activity address Code

when NlOl cites either code FR or TO. Use ofthe

DUNS or DUNS+4 number is preferred.

33 Commercial and Government Entity (CAGE)

Use when a commercial or government entity canriW^

be identified by a DUNS or DUNS+4 number.

Identification Code X AN 2/17

Code identifying a party or other code

Entity Relationship Code O ID 2/2

Code describing entity relationship

Refer to 003040 Data Element Dictionary for acceptable code values.

Entity Identifier Code O ID 2/2

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

Refer to 003040 Data Element Dictionary for acceptable code values.

003040F864 1 5 8 April 1997
864 Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Numbers

080

Nl Optional

Heading

Optional

12

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

1. Use to identify a transaction set to which the text message applies.

2. Use also to provide a unique reference numberfor this transaction set.

3. There must be at least 2 occurrences ofthis REFsegment with code TN and ME

cited in REFOl to identify the unique reference number ofthe transaction set to which

this message applies and to identify this transaction set.

Must Use

Ref.

Pes.

REFOl

REFOl

Data

Element

128

127

Data Element Summary

Name

Reference Number Qualifier

Code qualifying the Reference Number.

ME

Attributes

M ID 2/2

Message Address or ID

Use to indicate the unique reference number ofthis

transaction set When this 864 transaction set refers

to another 864 transaction set, use another iteration of

the REF segment with code TN to identify the other

864 transaction set. TN Transaction Reference Number

Use to indicate the unique reference number ofthe

transaction set to which this text message applies. Cite

the reference number in the REF02 and identify the

transaction set in REF03.

W7 Commercial and Government Entity (CAGE) Code

Code that identifies a commercial contractor authorized

to do business with the U.S. Government

Use, as applicable, to identify the code ofa party other

than a Federal Agency, either originating or receiving

the text message.

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. When transmitting the unique reference number ofan 810 transaction

set, cite the number in BIG02 ofthe 810 transaction set.

2. When transmitting the unique reference number ofan 820 transaction

set, cite the number in the TJRN02 ofthe 820 transaction set that is qualified

by code 1 in TRNOl.

3. When transmitting the unique reference number ofan 824 transaction

set, cite the number in the BGN02 ofthe 824 transaction set.

4. When transmitting the unique reference number ofan 832 transaction

set, cite the number in the BCT02 ofthe 832 transaction set.

5. When transmitting the unique reference number ofan 836 transaction

set, cite the number in the BCOlO ofthe 836 transaction set.

003040F864 1 6 8 April 1997
864 Text Message

6. When transmitting the unique reference number ofan 838 transaction

set, cite the number in the BTP02 ofthe 838 transaction set

7. When transmitting the unique reference number ofan 840 transaction

set, cite the number in the BQT02 ofthe 840 transaction set,

8. When transmitting the unique reference number ofan 841 transaction

set, cite the number in the SPI02 ofthe 841 transaction set.

9. When transmitting the unique reference number ofan 843 transaction

set, cite the number in the REF02 (l/REF/050) ofthe 843 transaction set that is qualified by code PR in REFOl.

10. When transmitting the unique reference number ofan 850 transaction

set, cite the number in BEG03 ofthe 850 transaction set. Ifa number is cited in both BEG03 and BEG04 ofthe 850 transaction set, concatenate

these numbers.

11. When transmitting the unique reference number ofan 855 transaction

set, cite the number in BAK03 ofthe 855 transaction set

12. When transmitting the unique reference number ofan 856 transaction

set, cite the number in BSN02 ofthe 856 transaction set.

13. When transmitting the unique reference number ofan 864 transaction

set, cite the number in REF02 (l/REF/080) ofthe 864 transaction set that is qualified by code ME in REFOl.

REF03 352 Description X AN 1/80

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

Wse to identify the transaction set applicable to the unique reference number

cited in REF02, e.g. 810 Invoice (Commercial Invoice) transaction set, 838

Trading Partner Profile (Registration) transaction set, etc.

003040F864 1 7 8 April 1997
864 Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

PER Administrative Communications Contact

090

Nl Optional

Heading

Optional

3

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.

Must Use

Ref.

Pes.

PEROl

PER02

PER03

PER04

PER05

Data

Element

366

93

365

364

365

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

IC Information Contact

Use to indicate a point ofcontactfor this transaction

set. Name O AN 1/35

Free-form name

Cite the last namefollowed by thefirst name. Do not truncate the last name

ifthe whole is greater than 35 characters. Instead, truncate thefirst name or use the initial ofthefirst name. Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

AU Defense Switched Network

Department of Defense telecommunications system and

successor of the Automatic Voice Network

(AUTOVON)

ED Electronic Data Interchange Access Number

EM Electronic Mail

FX Facsimile

IT International Telephone

Include country code.

TE Telephone

Use to indicate the commercial telephone number of

the namedparty.

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

AU

ED

EM

FX

IT

TE

003040F864 1

Defense Switched Network

Department of Defense telecommunications system and

successor of the Automatic Voice Network

(AUTOVON)

Electronic Data Interchange Access Number

Electronic Mail

Facsimile

International Telephone

Include country code.

Telephone

8 8 April 1997
864 Text Message

PER06

Use to indicate the conimercial telephone number of

the namedparty, ^

364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

)

003040F864 1 9 8 April 1997
864 Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

MIT Message Identification

010

MIT Mandatory

Detail

Mandatory

1To identify the beginning of a specific message and to allow the identification of a subject for the message

1 MITOl contains the message number.

2 MIT02 contains the message subject.

1 MIT03 default is 80 characters.

2 MIT04 default is 66 lines. Use this segment to identify a more detailed subject ofthis text message.

Must Use

Ref.

Pes.

MITOl

Data

Element

127

Data Element Summary

Name Attributes

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.

1. A unique number assigned by the originator ofthe message to identify

multiple messages contained within this transaction set. For example, the

number 001 can be used to refer to a message with the subject Packing

Requirements, cited in MIT02 and the number 002 can be used in another

iteration ofthis MIT segment to identify a second message with the subject

Testing Procedures.

2. When BMGOl is code 03 or 05, cite the original MITOl number used in

the previous message,

MIT02 352 Description O AN 1/80

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

Use to provide a more detailed subject ofthe message.

Not Used

Not Used

MIT03

MIT04

931

932

Page Widtii O NO 1/3

Definition of the maximum number of characters per line that can be expected

in the message text Page Length Lines O NO 1/3

Definition of the maximum number of lines per page that can be expected in

the message text

003040F864 1 10 8 April 1997
864 Text Message

Segment: Message Text

Position: 080

Loop: MIT Mandatory

Level: Detail

Usage: Mandatory

Max Use: 100000

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

Syntax Notes:

Semantic Notes:

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

page, advance a line, etc. Notes: Usefull 264 character capability ofdata element 933 (MSGOl) unless specifically

advised by the tradingpartner to limit length ofany one iteration ofthe segment to 80

fharacters.

Data Element Summary

Must Use

Ref.

Pes.

MSGOl

Data

Element

933 Free-Form Message Text M AN 1/264

Free-form message text When BMGOl is code 03, cUe DELEtm.

Printer Carriage Control Code O ID 2/2

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

Refer to 003040 Data Element Dictionary for acceptable code values.

Name Attributes

Not Used MSG02 934

003040F864 1 11 8 April 1997
864 Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE

010

Transaction Set Trailer

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).

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

003040F864 1 12 8 April 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. Handboolis—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.
wu

a>

o

E -H 1 o =^ ON

ON

00o

o 55 <N c o Q E = >> S <U 00 C

epar 1

Inst

hnolo sburg

Busi

Q

g Tec .2

.S. atio T3

E 3 Z C

t«

O

o

o