PUBLICATfONS

''^*«'»««*iiiisiitiilil

Special Publication 881-21

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003060 Transaction Set 841

Specifications/Technical Information

(Request for Technical Information)

Implementation Convention

Nisr

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

QC

100

.U57

NO.881-21

1997

NIST Special Publication 881-21

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003060 Transaction Set 841

Specifications/Technical Information

(Request for Technical Information)

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

May 1997

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Mary L. Gk)od, Under Secretary for Technology

National Institute of Standards and Technology

Robert E. Hebner, Acting Director
I'

i

Reports on Information Technology

I

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 j 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-21

Natl. Inst. Stand. Technol. Spec. Publ. 881-21, 29 pages (May 1997)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1997

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
841 Specifications/Technical Information

Functional Group ID=

Introduction:

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

Specifications/Technical Information Transaction Set (841) for use within the context of an Electronic Data

Interchange (EDI) enviroimient. The transaction set can be used to transmit or request specifications or technical

information between trading partners. It can be used to transmit engineering change and engineering change

requests. It can also be used to allow EDI trading partners the abiUty to exchange a complete or partial technical

description of a product, process, service, etc. over the same path as any other EDI transactioa The detail area can

include graphic, text, parametric, tabular, image, spectral, or audio data. A transmission includes identification

information to assist the receiver in interpreting and utilizing the information included in the transactioiLFurther

action as a consequence of the receipt and initial processing of the specification or other technical data may or may

not require human intervention. The transmission and receipt of the data may require private agreement between the

trading partners to automate the receipt of the data.The total transaction must be in the general form of all ASC X12

transactions so that an EDI computer system will be able to automatically recogiuze it as a Specification/Technical

Information Transaction Set and pass it on for processing of the data itself The transaction set is not media

dependent.The detail area of the Specification/Technical Information Transaction Set provides a structure which

allows for the exchange of a variety of specification information. For example, if the transaction contains

information describing a complete assembly, it would be necessary to include the assembly model, the models for

each of the individual parts, and the associated specifications. In the case of a process it may be necessary to transmit the specification of the product along with the specifications of the process and raw materials. This

transaction set can also be linked to other transaction sets.This transaction set is not Umited to a specific

transmission protocol and uses other standards as applicable where they do not conflict with these requirements for

specification transaction.

Notes:

1. The application namefor this implementation convention is REQUESTFOR TECHNICAL INFORMATION.

2. This implementation convention is used by a contractor as a general requestfor technical information, as a

requestfor technical information applicable to one or more solicitations, or as a requestfor technical information

applicable to an active contract.

3. This implementation convention is also used by the government to request technical informationfrom a

contractor orfrom another government organization such as a technical data repository.

4. When used by a contractor, each requestfor technical information may contain only one type, e.g., a requestfor an Engineering Data Lists (EDL), a requestfor drawings, or a requestfor product support documents, e.g.,

specifications, standards, engineering change orders, technical manuals, a list ofmaterials, etc.

Heading:

Pos. Seg. Req. Loop Notes and

Must Use

No. 010ID

ST

Name

Transaction Set Header

Des. M

Max.Use Repeat Comments

1

Must Use 020 SPI Specification Identifier M 1

N/U 030 RDT Revision Date/Time 0 >1

N/U 040 NTE Note/Special Instruction O >1

N/U 050 XI Export License 0 1

N/U 060 X2 Import License 0 1

NAJ 070 X7 Customs Information O 1

N/U 080 AMT Monetary Amount 0 >1

003060FED00A 24 JAN 1997
841 - Specifications/Technical Information (Reqiiest for Technical Information)

N/U 090 REF Reference Idennficaiion O 1 ipiiii^MiiiHiPill

N/U 100 DTM Date/Time Reference O >i

NAJ 110 PER

120 Nl Name o 1

130 N2 Additional Name Information o 2

140 N3 Address Information o 2

1 <f\ Geographic Location 1

160 REF Reference Identification 0 >1

170 PER Administrative Communications Contact o >1

Detail:

Pos. No.

Seg.

ID Name

Req.

Des. Max.Use Loop Notes and

Repeat Comments

Must Use 010 HL Hierarchical Level

LOC»tO-Si>I

M 1 nl, cl

>t

020 SPI Specification Identifier O 1

030 RDT Revision Date/Time O >1

NAJ 033 PRR Problem Report O >1 c2 NAJ 034 PRT Part Disposition O >1 c3 NAJ 035 PRS Part Release Status 0 1 c4

NAJ 040 LIN Item Identification O 1 c5

XT/T T NAJ 045 XT 1 Nl Name o >1

NAJ 046 PER Administrative Communications Contact o >1

NAJ 050 MSG A/ift^oaiTe Tevt o >1

V \

'

NAJ 060 PED Produci/Item Descnption o 1 NAJ 065 PKD Packaging Description o >1

NAJ 070 QTY Quantity o >1

NAJ 074 MEA Measurements o >1

NAJ 075 UTT Unit Detail o >1

NAJ 076 LOC Location o 1

NAJ 077 PWK Paperwork 0 >1

* ^ J

*• ^ ^

NAJ 078 PKG Marking, Packaging, Loading O ^^^^^^1

iVlCaoUI CIllCULd LOOPm-REF ' , ,

' -. , '

080 REF Reference Ideniificaiion o 1 NAJ 090 DTM Date/Time Reference o >1

NAJ 100 PER Administrative Communications Contact o >1

NAJ 103 LX Assigned Number o

' \

^ ^ > . >'-^'* V < t y

NAJ 105 LIN Item Identification o 1 NAJ 107 TMD Test Method o 1

T in \^AO oi If* Am c xtiVl >i

NAJ 112 PSD Physical Sample Description o >1

NAJ 114 SPS Sampling Parameters for Summary Statistics o >1

003060FED00A 2 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Date/Time Reference O

Reference Identification O

NAJ 120 DTM

N/U 130 REF

140 EFI

Must Use 160 BIN

NAJ 170 CID

N/U 180 UIT

N/U 190 TMD

N/U 200 PSD

N/U 201 CSS

N/U 210 SPS

N/U 220 MSG

N/U 230 MEA

N/U 240 DTM

N/U 250 REF

N/U 260 STA

N/U 270 DTM

N/U 280 REF

N/U 282 CSF

N/U 283 LS

N/U 284 CID

NAJ 285 MEA

IN/ STA

N/U 287 LE

N/U 290 EFI

NAJ 310 BIN

Summary:

Must Use

Pos. No. 010

Seg,

ID

SE

Electronic Formal Identification

Binary Data

O

M

LWl'lD-CaD

Charactensuc/Class ID O

Unit Detail O

Test Method O

Physical Sample Description O

Conditional Sampling Sequence O

Sampling Parameters for Summary Statistics O

Message Text O

Measurements

Date/Time Reference

Reference Identification

O

O

o

Siausiics

Date/Time Reference

Reference Identification

O

O

o

Conditional Sampling Frequency

Loop Header

O

O

Charactensuc/Class ID

Measurements

Statistics

O

O

o

Lx)op Trailer O

Electronic Format laentification

Binary Data

O

M

n3,c7

ii4,c8

c9

clO

Name

Transaction Set Trailer

Req.

Pes. M

Mai.Use

1

Loop

Repeat

Notes and

Comments

Transaction Set Notes

1. To be meaningful, at least one of the SPI, PHD, REF, MEA, EFI or CID loops must be present with each

occurence of the HL loop.

2. The sampling sequence specified in the CSS segment will take precedence over any other sampling rate (PSD03, PSD09, SPS06, CSF02, and CSF03) from the point the CSSOl event occurs until the specified

sequence is completed.

If no other sampling is specified, then only the sampling indicated in this segment is performed when the

CSSOl event occurs.

3. The sampling rate specified is the CSF segment It would take precedence over the normal sampling rate specified in PSD03 while the conditions of the CSF segment are satisfied, but would NOT take precedence

over the sampling sequence activated by the proposed CSS segment

003060FED00A 3 24 JAN 1997
I

841 - Specifications/Technical Information (Request for Technical Information)

If no other sampling rate is specified, then the only sampling indicated in the CSF segment is performed ' while the CSF conditions are met. Sampling will cease when the conditions are no longer met

Conditional values specified in DE 740 (Range Minimum) will be interpreted as "greater than or equal to this

value." Values specified in DE 741 (Range Maximum) will be interpreted to mean

'

" less than or equal to this

value." i 4. Either the MEA segment or the STA segment must occur, but not both.

'

Transaction Set Comments

1. The HL segment may be used to define the hierarchical relationship of product-related specifications reported

in the associated HL loop. Product-related specifications may refer to the product in its entirety or to subunits

of the product. For example, if the top level refers to an assembly, the second-level HL segment may refer to parts or subassemblies of the top assembly. This pattern may be repeated as often as required.

2. The PRR segment contains the reason for an engineering change.

3. The PRT segment is used to describe what should be done with the parts or assemblies specified in the

preceding SPI segment.

4. The PRS segment is used to tell the current status of the parts specified in the SPI segment required to make

the change.

5. The repeated pairs of 234 and 234 data elements in the LIN segment can be used to list where this modified

part or assembly is used.

6. The CID segment may be used to define either a general class of properties, such as physical properties, or an

individual property within a class. The CID loop allows the user the ability to define specifications such as

the properties of the item or class, the environmental conditions imder which the specifications apply, the test methods to be used, and other parameters related to properties within the current HL hierarchical level.

7. Repetitions of the CSF loop allow several fi-equency changes (and the conditions that would trigger those

changes) to be specified.

If the conditions are such that several CSF values are activated at the same time, the value with the highest

sampling rate shall prevail.

8. The CID loop within the CSF loop is used to specify the conditions that will trigger activation of the

conditional value in the CSF segment

Repetitions of the CID loop will have an impUed logical AND between the conditions set in each iteration.

9. The elements of the CID segment identify the conditional property. If the property is a measurement from

within the manufacturing process of a plant environment, rather than the product, the segment also identifies

the location where the measurements are to be observed.

10. If the condition is based on single test measurements, the MEA segment is used to specify the imits of

measure, and the open or closed numeric range of the conditional test

003060FED00A 4 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

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

Pes. Element Name Attributes

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

Code imiquely identifying a Transaction Set

84 1 X1 2. 5 1 Specifications/Technical Information

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

Identifying control nimiber that must be unique within the transaction set functional group assigned by the originator for a transaction set

TJiis unique control number is assigned by the originator ofthe transaction set. This same number is carried in SE02.

003060FED00A 5 24 JAN 1997
841 - Specifications/Technical Infonnation (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SPI Specification Identifier

020

SPI

Heading

Mandatory

1To provide a description of the included specification or technical data items

1 If either SPI02 or SPI03 is present, then the other is required.

Ref.

Pes.

Must Use SPIOl

Data

Element

786

Data Element Summary

Must Use SPI02 128

Must Use SPI03

Must Use SPI07

127

353

Must Use SPI08 755

Name Attributes

Security Level Code M ID 2/2

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

information following

1. Use this data element to identify the highest level ofprotection (government

or commercial) assigned to the requested information. Use the SPI segment at

the Detail Level to indicate the protection level ofindividual items.

2. Ifneither a government security classification nor a commercial protection

requirement applies to the information, code 90 shall be cited

06

11

90

92

93

94

Supplier Proprietary

Competition Sensitive

Government Non-Classified

Government Confidential

Government Secret

Government Top Secret

Reference Identification Qualifier X ID 2/3

Code Qualifying the Reference Identification

USE OF THIS DATA ELEMENTIS REQUIRED.

TN Transaction Reference Number

Use to indicate the unique reference number ofthis

transaction set. This number is assigned by the

originator ofthe transaction set. Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

USE OF THIS DA TA ELEMENTIS REQUIRED.

Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set USE OF THIS DATA ELEMENTISREQUIRED.

13 Request

Use to indicate a requestfor technical data.

Report Type Code O ID 2/2

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

USE OF THIS DATA ELEMENTISREQUIRED.

23 Contractual Plan

1. Use to indicate a requestfor a Technical

Information Package (TIP), based on an active

solicitation or contract under which the contractor is performing.

003060FED00A 6 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

2. This code is used only by a contractor. 24 Non-Contractual Plan

1. Use to indicate a requestfor a Technical

Information Package (TIP), not based on an active

solicitation or contract under which the contractor is

performing.

2. This code is used only by a contractor. AE Attachment

Use to indicate a miscellaneous request not applicable

to any other listed code. When used, a cost is applicable to the information provided.

DW Drawing(s)

1. Use to indicate a requestfor a drawing, based on an

active solicitation or contract under which the

contractor is performing.

2. This code is used only by a contractor. KD Engineering Drawing List

1. Use to indicate a requestfor an Engineering Data

List (EDL), based on an active solicitation or contract

under which the contractor isperforming,

2. This code is used only by a contractor. KE Purchased Engineering Data List

1. Use to indicate a request for an Engineering Data

List (EDL), not based on an active solicitation or

contract under which the contractor is performing.

2. This code is used only by a contractor.

KF Support Documents

1. Use to indicate a requestfor product support

information, e.g., specifications, standards, engineering

change orders, technical manuals, software application

program, a list ofmaterials or some other type oflist, based on an active solicitation or contract under which

the contractor is performing.

2. This code is used only by a contractor. KG Purchased Documents

1. Use to indicate a requestfor product support

information, e.g., specifications, standards, engineering

change orders, technical manuals, software application

program, a list ofmaterials or some other type oflist, not based on an active solicitation or contract under

which the contractor is performing.

2. This code is used only by a contractor. KI Piu-chased Drawings

1. Use to indicate a requestfor a drawing, not based on an active solicitation or contract under which the

contractor is performing.

2. This code is used only by a contractor. TO Demand Report

Use to indicate a requestfrom one government activity

to anotherfor technical information.

VD Data Request for Vendor's Specifications or Drawings.

003060FEDOOA 7 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Infonnation)

Use to indicate a request by a government activity to a

vendorfor technical information.

SPI09 786 Security Level Code O ID 2/2

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

infonnation following

Use to identify that access to the requested data is restricted to certified contractors. 99 Goveniment Defined (Trading Partner Level)

Use to indicate data access is restricted to certified contractors. When usedprovide the certified

contractor's certification number in the l/REF/160

segment.

003060FED00A 8 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

120

Nl

Heading

Optional

1To identify a party by type of organizatioii, 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 NI05 and NI06 fVuther define the type of entity in NIO I. Whenever possible, identification and address information should be provided using

NIO], N103, andN104. Use N102 and segments N2 through N4, as applicable, when

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

Must Use

Ref.

Pes.

NlOl

Data

Element

98

Data Element Summary

N102

N103

Name Attributes

Entity Identifier Code M ID 2/2

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

BY Buying Party (Purchaser)

Use to indicate a government activity that is originating a requestfor technical information.

KY Technical Office

Use to indicate a government activity that is the

recipient ofa requestfor technical information.

SE Selling Party

Use to indicate a commercialparty that is either

originating or receiving a requestfor technical

information.

ZD Party to Receive Reports

Use to indicate the party to whom the technical

information is to be sent ifdifferent than the requesting

party.

93 Name X AN 1/35

Free-form name

When NlOl is code ZD, use to provide the name ofthe party to receive the

technical information ifthat party cannot be identified by a code in N102/04.

66 Identification Code Qualifier X ID 1/2

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

Code (67)

While thefederal EDIprogram uses the DUNS number, other government

users ofthis implementation convention may require the use ofother and

additional numbersfor a transition period in order to cross reference existing

data bases.

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

Use ofthe DUNS and DUNS +4 number is preferred over other codes to identify an entity.

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

Suffix

Use ofthe DUNS and DUNS +4 number is preferred over other codes to identify an entity.

10 Department of Defense Activity Address Code

(DODAAC)

003060FED00A 9 24 JAN 1997
84 1 - Specifications/Technical Information (Request for Technical Mbraiation)

33 Commercial and Govermnent Entity (CAGE)

N104 67 Identification Code X AN 2/20

Code identifying a party or other code

003060FED00A 10 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N2 Additional Name Information

130

Nl

Heading

Optional

2

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

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

additional name information.

Ref.

Pes,

Must Use N201

N202

Data Element Summary

Data

Element Name

93 Name

Free-form name

93 Name

Free-form name

Attributes

M AN 1/35

O AN 1/35

003060FED00A 11 24 JAN 1997
841 - Specifications/Technical Monnation (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N3 Address Information

140

Nl

Heading

Optional

2

To specify the location of the named party

This segment should only be used when Nl 02 is used

Must Use

Ref.

Pes.

N301

N302

Data

Element

166

166

Data Element Summary

Name

Address Information

Address information

Address Information

Address information

Attributes

M AN 1/35

O AN 1/35

003060FEDO0A 12 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N4 Geographic Location

150

NX

Heading

Optional

1To specify the geographic place of the named party

1 If N406 is present, then N405 is required.

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

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

This segment should only be used when N102 is used

Ref.

Pes.

N401

N402

N403

N404

Data

Element

19

156

116

26

Attributes

O AN 2/30

Data Element Summary

Name

City Name

Free-form text for city name

State or Province Code O ID 2/2

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

Postal Code O E) 3/15

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States)

Country Code O ID 2/3

Code identifying the coimtry

003060FED00A 13 24 JAN 1997
841 - Specifications/Technical Monnation (Request for Technical Monnation)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Identification

160

Nl

Heading

Optional

>1

To specify identifying information

1 At least one ofREF02 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.

When NlOl is code SE and the selling party is requesting technical data, use this

segment to identify reference numbers applicable to the selling party.

Ref.

Pes.

Must Use REFOl

Data

Element

128

Data Element Summary

Name

Reference Identification Qualifier

Code Qualifying the Reference Identification

Attributes

M ID 2/3

OC

EL

Certification Number

When SPI09 in the l/SPI/020 segment is code 99 and

NlOl is code SE, (a commercial party is requesting

technical information), use to indicate the certification

number assigned to a selling party to permit access to restricted drawings.

Electronic device pin number

1. Use to indicate the identification number assigned to a contractor at the time ofregistration.

2. Use ofthis code is REQUIRED when a contractor is requesting information restricted to certified contractors. TJ Federal Taxpayer's Identification Nmnber

W7 Commercial and Govenmient Entity (CAGE) Code

When Nl01 is code SE and the selling party is

requesting technical information, use to indicate the

CAGE code ofthe selling party ifNl 03 is other than

code 33.

REF02 127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

003060FED00A 14 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

PER Administrative Communications Contact

170

Nl

Heading

Optional

>1

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

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

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

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

Ref.

Pes.

Must Use PEROl

PER02

PER03

PER04

PER05

Data

Element Name

Data Element Summary

366

93

365

364

365

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 the requester's point ofcontact. Name O AN 1/35

Free-form name

1. Use to provide the name ofthe point ofcontact.

2. Cite last namefirstfollowed byfirst name. Ifthe whole name is longer than

35 characters, truncate or use initialsfor thefirst name. Communication Number Qualifier X ID

Code identifying the type of conmiunication number

2/2

AU Defense Switched Network

EM Electronic Mail

FT Federal Telecommunications System (FTS)

FX Facsimile rr International Telephone

TE Telephone

Use to indicate a commercial telephone number.

Include the area code.

003060FED00A

Communication Number X AN 1/80

Complete communications number including coimtry or area code when

applicable

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Use to identify a second communication numberfor the party cited in PER02.

For example, ifPER03/04 cites a telephone number, PER05/06 could cite a FAXnumber.

AU Defense Switched Network

EM Electronic Mail

EX Telephone Extension

Use only ifPER03 cites code TE.

FT Federal Telecommimications System (FTS)

FX Facsimile

IT International Telephone

TE Telephone

Use to indicate a commercial telephone number.

Include the area code.

15 24 JAN 1997
841 - Specifications/Technical Infonnation (Request for Technical Information)

PER06 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

PER07 365 Communication Number Qualifier X ID 2/2

Code identifying the type of coimnimication number

Use to identify a third communication numberfor the party cited in PER02.

AU Defense Switched Network

EM Electronic Mail

EX Telephone Extension

Use only ifPEROS cites code TE.

FT Federal Telecommunications System (FTS)

FX Facsimile

IT International Telephone

TE Telephone

Use to indicate a commercial telephone number.

Include the area code.

PER08 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

PER09 443 Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

Use to identify the title or office symbol ofthe party identified in PER02.

003060FED00A 16 24 JAN 1997
841 - Specifications/Technical Infonnation (Reqxiest for Technical Infonnation)

Segment: HL Hierarchical Level

Position: 010

Loop: HL

Level: Detail

Usage: Mandatory

Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data

segments

Syntax Notes:

Semantic Notes:

Comments: 1 The HL segment is used to identify levels of detail information using a hierarchical

structure, such as relating line-item data to shipment data, and packaging data to lineitem data.

2 HLOl shall contain a unique alphanumeric number for each occurrence of the HL

segment in the transaction set For example, HLO1 could be used to indicate the

number of occurrences of the HL segment, in which case the value of HLOl would

be "1" for the initial HL segment and would be incremented by one in each

subsequent HL segment widiin the transactioiL

3 HL02 identifies the hierarchical ID niunber of the HL segment to which the current HL segment is subordinate.

4 HL03 indicates the context of the series of segments following the ciurent HL

segment up to the next occurrence of an HL segment in the transactioa For example,

HL03 is used to indicate that subsequent segments in the HL loop form a logical

grouping of data referring to shipment, order, or item-level information.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related

to the current HL segment.

When requesting multiple items that may or may not have a hierarchical relationship,

repeat the HL loop as many times as required to specify all levels and use as many

iterations ofthe HL, SPI, andREF loops as necessary.

Notes:

Must Use

Ref.

Pes.

HLOl

HL02

Must Use HL03

Data

Element

628

734

735

Data Element Summary

Name Attributes

Hierarchical ID Number M AN 1/12

A unique number assigned by the sender to identify a particular data segment

in a hierarchical structure This is a unique andprogressive number assigned by the originator ofthe

transaction set starting with the number 1 andfollowing with whole numbers

2, 3, 4, etc. Hierarchical Parent m Number O AN 1/12

Identification number of the next higher hierarchical data segment that the data

segment being described is subordinate to Use ofthis data element is REQUIRED when the current HL segment is subordinate to another HL segment For example, the second HL segment may

be subordinate to thefirst HL segment, therefore, the number 1 would be cited; or the sixth HL segment may be subordinate to thefourth HL segment,

therefore, the number 4 would be cited Ifan HL segment is not subordinate to another HL segment, this data element is left blank.

Hierarchical Level Code M E) 1/2

Code defining the characteristic of a level in a hierarchical structure Use any appropriate listed code to indicate the hierarchical level ofthe

requested information.

A Assembly

DG Drawing

ED Engineering Data List

F Component

FR Frame

Use to indicate a drawing sheetfi-ame.

003060FED00A 17 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

I Item

1. Use to indicate an item technical information

package (TIP). The TIP includes EDLs, drawings,

specifications, standards, etc. and may also contain a

statement ofwork (SOW).

2. This code may only be used when SPI08 in the

l/SPI/020 segment is code 23, 24, TO, and VD.

IB Contract

SD Support Document

Use to indicate a specification, standard, engineering

change order, bill ofmaterials, technical manual,

software application, or other type oflist. SH Sheet

Use to indicate a drawing sheet.

SL Solicitation

SY System

U Subassembly

ZZ Mutually Defined

1. Use to indicate a miscellaneous hierarchical level

that cannot be identified by use ofany other listed code.

When used, this is a stand alone hierarchical level, i.e.,

it may not be subordinate to any other hierarchical

level and cannot have any subordinate hierarchical

levels.

2. This code is only used when SPI08 in the l/SPI/020

segment is code AE.

Must Use HL04 736 Hierarchical ChUd Code O ID 1/1

Code indicating if there are hierarchical child data segments subordinate to the

level being described

1. Use to identify whether or not there are subordinate HL segments.

2. Use ofthis data element is REQUIRED.

Refer to 003060 Data Element Dictionary for acceptable code values.

003060FED00A 18 24 JAN 1997
841 - Specifications/Technical Mbrmation (Request for Technical Infonnation)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

SPIOl

SPI02

SPI Specification Identifier

020

SPI

Detail

Optional

1To provide a description of the included specification or technical data items

1 If either SPI02 or SPI03 is present, then the other is required.

Use this segment to provide identifying reference numbersfor the hierarchical level

specified in the HL segment and to identify the government security classification or commercial protection level applicable to the referenced item.

Data

Element

786

128

Data Element Summary

Name Attributes

Security Level Code M E) 2/2

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

information following

1. Use this data element to identify the highest level ofprotection (government or commercial) assigned to the requested information.

2. Ifneither a government security classification nor a commercial protection

requirement applies to the information, code 90 shall be cited

3. The identified security classification or commercial protection level

represents the highest classification within the specified hierarchical level. 06 Supplier Proprietary

11 Competition Sensitive

90 Government Non-Classified

92 Government Cotifidential

93 Government Secret

94 Government Top Secret

Reference Identification Qualifier X ID 2/3

Code Qualifying the Reference Identification

Use to identify, by a number, an item represented by the hierarchical level

specified in the preceding HL segment.

7K List of Materials

1. Use to indicate a List ofMaterials (LOM) or a Bill

ofMaterials (BOM) number. Identify the vendor or

contractor applicable to the LOMor BOMin the

2/REF/080 segment citing either code W7 or ZZ in

REFOL

7M

TP

TQ

2. Use, ifapplicable, when HL03 is code SD.

Frame

1. Use to indicate a drawing sheetframe number.

2. Use when HL03 is code FR.

Sheet

L Use to indicate a drawing sheet number.

2. Use when HL03 is code SH.

Engineering Change Order

1. Use to indicate an Engineering Change Order

number.

003060FED00A 19 24 JAN 1997
841 - Specifications/Technical Mbnnation (Request for Technical Information)

89

90

97

CT

DG

HF

IX

KS

MU

NI

NJ

S3

vw

W2

003060FED00A

2. Use, ifapplicable, -when HL03 is code SD.

Assembly Number

Use when HL03 is code A.

Subassembly Number

Use when HL03 is code U. Package Number

7. Use to indicate a Technical Information Package

(TIP).

2. Use when HL03 is code I. Contract Number

Use when HL03 is code IB. Drawing Number

Use when HL03 is code DG. Identify the contractor

applicable to the drawing in the 2/REF/080 segment

citing either code W7 or ZZ in REFOl.

Engineering Data List

1. Use to indicate a Engineering Data List (EDL)

number. Identify the manufacturer applicable to the

EDL in the 2/REF/080 segment using code W7 or ZZ in

REFOl.

2. Use when HL03 is code ED.

Item Number

1. Use to indicate the number ofa component.

2. Use when HL03 is code F.

Solicitation

1. Use to indicate the solicitation Technical

Information Package number.

2. Use when HL03 is code SL.

Military Specification (MELSPEC) Number

Use when HL03 is code SD.

Military Standard (MEL-STD) Number

Use, ifapplicable, when HL03 is code SD.

Technical Document Number

L Use to indicate the number ofa technical manual.

2. Use, ifapplicable, when HL03 is code SD.

Specification Niunber

1. Use to indicate a contractor specification number.

Identify the contractor in the 2/REF/080 segment using

code W7 or ZZ in REFOl.

2. Use, ifapplicable, when HL03 is code SD.

Standard

1. Use to indicate a contractor standard number.

Identify the contractor in the 2/REF/080 segment citing

either code W7 or ZZ in REFOl.

2. Use, ifapplicable, when HL03 is code SD.

Weapon System Nimiber

1. Use to indicate the number ofa system.

2. Use when HL03 is code SY.

20 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

WF Locally Assigned Control Number

1. Use to indicate another type oflist, e.g., list of

circuits that comprise a network. Identify the type of

list, by name, in SPI04.

2. Use, ifapplicable, when HL03 is code SD.

ZS Software Application Number

1. Use to indicate a software application. If

applicable, identify the contractor applicable to the

software application in the 2/REF/080 segment citing

either code W7 or ZZ in REFOl.

2. Use, ifapplicable, when HL03 is code SD.

ZZ Mutually Defined

I. Use to indicate another type ofreference number not

associated with any other code. When used, a number

or name must be cited in SPI03. SPI04 should be used

ifnecessary, tofurther identify the referenced item.

SPI03

SPI04

2. This code will typically be used when HL03 is code

ZZ.

127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

790 Entity Title O AN 1/132

Title of the data entity

1. When HL03 is code ZZ, use to identify, by name, the item applicable to the

hierarchical level.

2. Ifnecessary, use to identify the noun name applicable to any item number

cited in SPI03.

SPI09 786 Security Level Code O ID 2/2

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

information following

Use to identify that access to the identified information is restricted to certified contractors. 99 Government Defined (Trading Partner Level)

Use to indicate information access is restricted to

certified contractors.

003060FED00A 21 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

RDT Revision Date/Time

030

SPI

Detail

Optional

>1

To specify the revision level of the electronic data item

1 If RDTO1 is present, then RDT02 is required.

2 If RDT03 is present, then at least one of RDT04 or RDT05 is required.

3 If RDT06 is present, then RDT05 is required.

This segment is used to identify a revision or a version ofthe data item cited in SPI03. If

multiple revisions or versions are being requested and they cannot be identified by use of

the specific words in RDT02, use as many repetitions ofthe RDTsegment as required to identify them.

Ref.

Pes.

RDTOl

RDT02

RDT03

RDT04

Data

Element

795

796

374

373

Data Element Summary

Name Attributes

Revision Level Code O ID 1/1

Code indicating the revision or engineering change level of the data items

referred to by the specification number

E Revision Level

Use, ifapplicable, to indicate a revision ofany

document, e.g., drawing, standard specification, etc. H Version Level

Use when SPI02 is code ZS.

Revision Value X AN 1/30

Revision or engineering change level of the data items referred to by the

specification number

Cite the actual number or letter ofthe revision/version or one ofthe

appropriatefollowing words to indicate the requested revision:

"Latest": to indicate the latest revisionA>ersion is requested

"All": to indicate all revisionsA^ersions are requested

"After": to indicate all revisions/versions after the date specified in RDT04 are requested

Date/Time QuaUfier O ID 3/3

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

1. Use only to identify the date ofa specific revision/version.

2. This data element is REQUIRED when RDT02 cites the word "After". 171

824

Date

Date (YYMMDD)

Revision

Use to indicate the date ofthe requested revision.

Version

Use to indicate the date ofthe requested version.

X DT 6/6

003O6OFEDOOA 22 24 JAN 1997
841 - Specifications/Technical Mbrmation (Request for Technical Information)

Segment: REF Reference Identification

Position: 080

Loop: REF

Level: Detail

Usage: Optional

Max Use: I Purpose: To specify identifying information

Syntax Notes: 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.

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

Comments:

Notes: Use this segment to identify reference numbers applicable to the data item cited in SPI03

ofthe same HL loop.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use REFOl 128 Reference Identification Qualifier M ID 2/3

Code Qualifying the Reference Identification

7S Drawing Type

Use to indicate a type ofdrawing, e.g., assembly,

interpretation, installation, etc. Identify the type of

drawing in REF03

83 Extended (or Exhibit) Line Item Nimiber (ELIN)

Use to indicate an exhibit line item in either a contract or a solicitation.

CI Contract Line Item Number

Use to indicate a line item in either a contract or a

solicitation.

L6 Subcontract Line Item Number

Use to indicate a sub line item in either a contract or a

solicitation.

W7 Conunercial and Govenmient Entity (CAGE) Code

Use only when SPI02 in the 2/SPI/020 segment is code

7K,DG,S3,VW,orZS.

ZZ Mutually Defined

1. Use to indicate a DUNS number or a DUNS+4

number.

2. Use only when SPI02 in the 2/SPI/020 segment is

code 7K, DG, S3, VW, or ZS

REF02 127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

REF03 352 Description X AN 1/80

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

When REFOl is code 7S, use to identify the type ofdrawing.

O03O60FEDO0A 23 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Infonnation)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

EFI Electronic Format Identification

140

EFI

Detail

Optional

1To provide basic infonnation about the electronic format of the interchange data

1 If EFI05 is present, then EFI04 is required.

2 If EFI07 is present, then EFT06 is required.

3 If EFI09 is present, then EFI08 is required.

4 If either EFI1 5 or EFI1 6 is present, then the other is required.

Use this segment to identify the media andformat in which the requested data is to be

provided.

Must Use

Ref.

Pes.

EFIOl

EFI02

EFI06

EFI07

Data

Element

786

Data Element Summary

933

799

801

Name Attributes

Security Level Code M ID 2/2

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

information following

Use only the listed code to comply with the mandatory nature ofthis data

element.

05 Personal

Free-Form Message Text O AN 1/264

Free-form message text Use to identify the requested media in which the item is to be provided. Use

only thefollowing words:

NET - to indicate transmission via the DoD network architecture

CD-ROM - to indicate data will be written to a CD-ROMand delivered by

mail

CARD - to indicate an aperture card will be produced and delivered by

mail

PAPER - to indicate a hard copy will be produced and delivered by mail

Version Identifier X AN 1/30

Revision level of a particular format, program, technique or algorithm

Use to identify the version oftheformat requested in EFI07.

Interchange Format O AN 1/30

Industry or proprietary standard used to identify the format of the data

Use to identify the requestedformat in which the item is to be provided When

the dataformat is one oftheformats in thefollowing list, use the associated

code. Other values may be used only ifmutually agreed between the trading

partners.

CODE FORMAT

ANSI ANSI Text - (entire ANSI character set))

ASCII ASCII TEXT - (letters and numerals only)

BMP Windows Bitmap

C4 JEDMICSproprietaryformat

dBASE Borland dBASE

EXCEL Microsoft Excel

GIF Graphics Interchange Format

Harvard Software Publishing Company Harvard Graphics

HTML HyperTextMarkup Language

ISO-1 0918 Joint Photographies Expert Group (JPEG) - Lossy

003060FED00A 24 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

compression ofphotographic images

KODAK

LOTUS

MAC

MSDOS

MIL-D-28000

MIL-R-28001

MIL-R-28002

MIL-D-28003

ISO-] 11 72

PDES

PDF

PPOINT

PROJECT

RTF

TIFF

WINDOWS

WORD

WORDP

Kodak Photo-CDformat

Lotus 123

Macintosh Apple Application Program

Microsoft DOSApplication Program

IGESformat

SGML

CALS/Rasterformat

Computer Graphics Metafile (CGM)

Motion Pictures Experts Group (MPEG) - Lossy

compression ofvideo

Product Data Exchange Standard - STEP

Adobe Portable Document Format

Microsoft PowerPoint

Microsoft Project

Rich Text Format

TaggedInterchange File Format

Microsoft Windows Application Program

Microsoft Word

Novell WordPerfect

003060FED00A 25 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

BIN Binary Data

160

EFl

Detail

Mandatory

1To transfer binary data in a single data segment and allow identification of the end of the

data segment through a coimt; there is no identification of the internal structure of the

binary data in this segment

Use only to comply with the mandatory nature ofthis segment

Data Element Summary

Ref.

Des.

Must Use BmOl

Must Use Bm02

Data

Element Name

784

785

Attributes

Length of Binary Data M NO 1/15

The length in integral octets of the binary data

Cite the number one (1) to comply with the mandatory nature ofthis data

element

Binary Data M B 1/1

A string of octets which can assume any binary pattern from hexadecimal 00 to FF

Cite the number zero (0) to comply with the mandatory nature ofthis data

element.

003060FED00A 26 24 JAN 1997
841 - Specifications/Technical Information (Request for Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

010

Summaiy

Mandatory

1To indicate the end of the transaction set and provide the coimt 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

Identiiying control number that must be unique within the transaction set fimctional group assigned by the originator for a transaction set Cite the same number carried in ST02.

003060FED00A 27 24 JAN 1997



Technical Publications

Periodical

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

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

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

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

Nonperiodicals

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

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

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

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

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

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

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

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

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

20056.

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

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

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

characteristics of building elements and systems.

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

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

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

other government agencies.

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

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

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

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

standardizing organizations.

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

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FTPS 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.

1 127), and as implemented by Executive Order 1 1717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NIS'llK)—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.
9iWUBBoo 55 c o S 3

Dan Q S . o • cS ^ Z 8

ON

ooo

OX) . C > Ob 3 £

SoO (Si