NIST

PUBLICATIONS

H

i;

Nisr

Special Publication 881-22

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003060 Transaction Set 841

Specifications/Technical Information

(Provide Technical Information)

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

NIST Special Publication 881-22

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003060 Transaction Set 841

Specifications/Technical Information

(Provide 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. Good, Under Secretary for Technology

National Institute of Standards and Technology

Robert E. Hebner, Acting 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-22

Natl. Inst. Stand. Technol. Spec. Publ. 881-22, 36 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=SP

Introduction:

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

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

Interchange (EDI) environment. 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 transaction.Further

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 recognize 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 limited to a specific

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

specification transactioa

Notes:

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

2. This implementation convention is used by the government or a contractor to respond to a requestfor technical

information.

3. It can be used by the government to transmit technical information that is part ofa solicitation, aspart ofa

contract or contract modification, or to transfer technical information between government activities.

4. It can also be used by a bidder to provide technical information that is part ofa Response to a Requestfor

Quotation, 843 transaction set, or by a contractor to provide deliverables required by an award instrument, e.g., data required on a Contract Data Requirements List (CDRL), or to submit technical information as part ofa

requested change to a contract, e.g., an engineering change request.

5. When used to provide technical information in support ofResponse to a Requestfor Quotation (843 transaction

set), or to provide deliverables required by an award instrument, or to provide technical information as part ofa

requested change to a contract, the transaction set shall only transmit information applicable to a single quote or a

single award instrument.

Heading:

Must Use

Pos. No.

010

Seg.

ID

ST

Name

Transaction Set Header

Req.

Pes. MMax-Use

1

Loop

Repeat

Notes and

Comments

003060FED00A 24 JAN 1997
841 - Specifications/Techiiical Information (Provide Technical Information)

Must Use 020 SPI N/U 030 RDT

040 NTE

N/U 050 XI

N/U 060 X2

N/U 070 X7

080 A \ XT' AMI

090 REF

N/U 100 DTM

N/U 110 PER

120 XT! Nl

130 N2

140 N3

150 N4

160 REF

170 PER

Detail:

Pos. No.Seg.

ID

Must Use A 1 n ML

020 SPI

030 RDT

XT/T T N/U 033 PRR

XT/I T 034 rKl

XT/f T IN/U 035 rKa

N/U 040 LIN

N/U 045 Nl

N/U 046 PER

050 MSG

XT/T T A^A rWJ

XT/T T A^C rKLI

XT/I T ATA U/0 QTY

N/U 074 MEA

N/U 075 UTT

XTA T IN/U u/o

N/U 077 PWK

NAJ 078 PKG

N/U 079

080 REF

N/U 090 DTM

LOOPID-SPI

Specificaiion Idenufier M 1

Revision Date/Time O >1

Note/Special Instruction O >1

Export License 0 1

Import License O 1

Customs Information o 1

Monetary Amount

LOOflD-RfcF \

o >1

>i

Reference Idenuficaiion o 1

Date/Time Reference o >1

Administrative Communications Contact

lO0?li*-3Nt'<\ ------

o >1

>l

Name o 1

Additional Name Information o 2

Address Information o 2

Geographic Location o 1

Reference Identification o >1

Administrative Communications Contact o >1

Name

LOOPID-HL

Hierarchical Level

Req. Loop Notes and

Pes. Mai.Use Repeat Comments

.VAViV.-.-.W. M nl, cl LOOPED-S?!

Specificaiion Idenufier

Revision Date/Time

Problem Report

Part Disposition

Part Release Status

Item Identification Name

Administrative Communications Contact

Message Text

WJW.W.WVW.V o 1 O >1

O >1 c2 O >1 c3 O I c4 0 1 c5 O >1

O >1

O >1

Produci/Iiem Description

Packaging Description

Quantity

Measurements

Unit Detail

Location

Paperwork

v«- ^j-v J- o 1 o >1

o >1

o >1

o >1

o 1 o >1

LOOP PKG

Markmg, Packaging, Loading

Measurements

o

o

1

>1

Reference Identification

Date/Time Reference

.VJV.VAW.V.V.V.*. O

O

1

>1

003060FED00A 2 24 JAN 1997
841 - Specifications/Technical Ihfonnation (Provide Technical Information)

NAJ/U 100 PER Administrative Communications Contact O

N/U 103 LX

N/U 105 LIN

N/U 107 TMD

N/U 110 MEA

N/U 112 PSD

N/U 114 SPS

N/U 120 DTM

N/U 130 REF

140 EFI

Must Use 160 BIN

N/U 170 CID

N/U 180 urr

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

NAJ 283 LS

N/U 284 CID

N/U 285 MEA

N/U 286 STA

NAJ 287 LE

NAJ 290 EFI NAJ 310 BIN

Summary:

Must Use

Pos. No. 010

Seg.

ID

SE

>1

Assigned Number O

Item Identification O

Test Method O

Measurements M

Physical Sample Description O

Sampling Parameters for Summary Statistics O

Date/Time Reference O

Reference Identification O

Elearonic Format Identificauon

Binary Data

O

M

Charactenstic/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

Statistics

Date/Time Reference

Reference Identification

o

o

o

>

>

Condiuonal Samphng Frequency

Loop Header

O

O

LOOPID^CID

Characiensuc/Class ID

Measurements

Statistics

O

O

o

Loop Trailer O

Electronic Format Identification

Binary Data

O

M

w.v.'.w.Cv.-.v.'.wj'jCv.v

c6

n2

n3,c7

c9

clO

Name

Transaction Set Trailer

Req.

Des. MMax.Use

1

Loop

Repeat

Notes and

Comments

Transaction Set Notes

003O6OFEDO0A 3 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

1. To be meaningful, at least one of the SPI, PID, REF, MEA, EFl 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) fi-om 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

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

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 xised 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 frequency 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

sampUng 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 imphed 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 units of

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

003060FED00A 4 24 JAN 1997
841 - Specifications/Technical Information (Provide 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

Des. Element Name Attributes

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

Code uniquely identifying a Transaction Set

841 X12.51 Specifications/Technicallnformation

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

Identifying control number that must be imique within the transaction set functional group assigned by the originator for a transaction set This unique number is assigned by the originator ofthe transaction set. This

same number is carried in SE02.

00306OFED00A 5 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Monnation)

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

Name Attributes

003060FED00A

Security Level Code M ID 2/2

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

information following

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

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

the Detail Level to indicate the protection level ofindividual items.

2. When the transaction set is originated by a contractor, ifthe data have both a government security classification and a commercial protection requirement,

this data element will carry the government security classification code and the

commercial protection requirement code will be carried in SPI09.

3. When the transaction set is originated by the government, this data element

may carry either the government security classification or the commercial

protection requirement code , as applicable, with the government security

classification code taking precedence. In this instance, SPI09 may only cite code 99, when it is necessary to indicate that data referenced in the

transaction set is restricted to certified contractors.

4. Ifneither a government security classification nor a commercialprotection

requirement applies to the information, code 90 shall be cited.

06 Supplier Proprietary

1 1 Competition Sensitive

90 Government Non-Classified

92 Government Confidential

93 Govenunent Secret

94 Govenmient Top Secret

Reference Identification Qualifier X ID 2/3

Code Qualifying the Reference Identification

USE OF THISDATA 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

Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

USE OF THISDATA ELEMENTIS REQUIRED.

Transaction Set Purpose Code

Code identifying purpose of transaction set USE OF THIS DATA ELEMENTIS REQUIRED.

00 Original

6 24 JAN 1997

1/30

O ID 2/2
841 - Specifications/Technical Information (Provide Technical Information)

Use to indicate an original transmission when none of

the other codes apply.

08 Status

Use to indicate only a portion ofa request is being

satisfied Provide an explanation in the l/NTE/040

segment

12 Not Processed

Use to indicate a request could not be satisfied.

Provide the reason in the l/NTE/040 segment.

25 Incremental

Use to indicate 2 or more 841 transaction sets are being sent to transmit all technical information.

Identify the unique reference number ofthe previous

841 transaction set in the l/REF/090 segment using

code Q4.

53 Completion

When 2 or more 841 transaction sets are being sent to transmit all technical information, use to indicate the

final transaction set Identify the unique reference

number ofthe previous 841 transaction set in the

l/REF/090 segment using code Q4.

Must Use SPI08 755 Report Type Code O ID 2/2

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

USE OF THIS DATA ELEMENTIS REQUIRED.

AE Attachment

Use to indicate miscellaneous information not

applicable to any other listed code is being provided

Bl Batch Report

Use to indicate technical information provided in

response to a request.

KA Contract Data Requirements List (CDRL)

1. Use to indicate an award instrument deliverable.

2. This code is only used by a contractor. KH Proposal Support Data

1. Use to indicate technical information in support of

proposal, i.e., 843 transaction set.

2. This code is only used by a contractor. KJ Change Proposal Data

Use to indicate information in support ofa requested

change (including waivers and deviations) to an award

instrument that is transmitted in an 860 or an 865

transaction set. PC Process Change Notice

1. Use to indicate information applicable to a contract

modification, i.e., an 860 transaction set

2. This code is used only by the government

PF Product Specification

1. Use to indicate technical information applicable to an award instrument, i.e., an 850 transaction set

2. This code is only used by the government.

SD Support Data for a Request for Quote

1. Use to indicate technical information applicable to a

solicitation, i.e., an 840 transaction set

003060FED00A 7 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

2. This code is only used by the government.

SPI09 786 Security Level Code O ID 2/2

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

information following

1. When the transaction set is originated by a contractor, use this data element

ONLY when SPIOl is Code 92, 93, or 94 and the information also has a

commercial protection requirement.

2. Codes 06 and 11 indicate the highest level ofcommercial security protection

assigned to the information beingprovided Use the SPI segment at the Detail

Level to indicate the commercial protection requirement ofindividual data

items.

3. When the transaction set is originated by the government, this data element

may cite only code 99, ifapplicable.

06 Supplier Proprietary

This code is only used by a contractor.

11 Competition Sensitive

This code is only used by a contractor. 99 Government Defined (Trading Partner Level)

1. Use to indicate that information referenced in this

transaction set is restricted to certified contractors.

2. This code is used only by the government.

003060FEDO0A 8 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

NTEOl

Must Use NTE02

NTE Note/Special Instruction

040

SPI

Heading

Optional

>1

To transmit information in a free-form format, if necessary, for comment or special

instruction

1 The NTE segment permits free-form information/data which, imder ANSI X12

standard implementations, is not machine processable. The use of the NTE segment

should therefore be avoided, if at all possible, in an automated environment

Use this segment to provide information applicable to the entire transaction set. To

provide information applicable to a specific item, use the 2/MSG/050 segment.

Data

Element

363

Data Element Summary

Name Attributes

Note Reference Code O ID 3/3

Code identifying the functional area or purpose for which the note appUes

Ifthe NTE segment is used, this data element is REQUIRED.

ACN

GEN

352 Description

Action Taken

When SPI07 is code 08 or 12, use to provide the reasonsfor not processing or satisfying the total

request

Entire Transaction Set

Use to indicate information related to the data in this

transaction set. M AN 1/80

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

003060FED00A 9 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

AMTOl

Must Use AMTOl

AMT Monetary Amount

080

SPI

Heading

Optional

>1

To indicate the total monetary amount

1. Use this segment to identify the cost associated with providing the information and the

balance ofthe requester's account.

2. This segment is only used by the government when responding to a requestfr-om a

contractor that contained codes 24, AE, KE, KG. or KI in SPI08 ofthe l/SPI/020

segment ofthe request

Data

Element

522

Data Element Summary

Name

Amount Qualifier Code

Code to qualify amount

Attributes

M ID 1/2

PB

T4

782 Monetary Amount

Monetaiy amount

Billed Amount

Use to indicate the amount charged the requesterfor

the information provided.

Total Current Balance

Use to indicate the current balance ofa requester's

account after the chargefor the information in this

transaction set has been deducted

M R 1/15

003060FEDO0A 10 24 JAN 1997
841 - Specifications/Technical Infonnation (Provide Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Identification

090

REF

Heading

Optional

1To specify identifying information

1 At least one of REF02 or REF03 is required.

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

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

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

Use this l/REF/090 segment to identify reference numbers applicable to the technical

information being provided in this transaction set.

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

39 Proposal Number

Use to indicate either a contractor originated change

proposal number, found in an 865 transaction set or a

draft contract modification number, found in an 860

transaction set to which the information provided in this

transaction set applies. When used, a secondREF

segment citing code CT in REFOl must be transmitted

C4 Change Number

Use to indicate the award instrument modification

number assigned in an 860 transaction set to which the

information provided in this transaction set applies.

When used, a second REFsegment citing code CT in

REFOl must be transmitted.

CT Contract Number

Use to indicate the award instrument number to which

the information provided in this transaction set applies.

DO Delivery Order Number

Use to indicate a delivery order number, call or release

to which the information provided in this transaction set

applies. When used, a second REFsegment must be

transmitted citing code CT in REFOl to identify the

basic award instrument applicable to the delivery, call or release.

KS Solicitation

Use to indicate the solicitation number to which the

information provided in this transaction set applies.

PR Price Quote Number

1. Use to indicate the bid, quote or proposal number to which the information provided in this transaction set

applies.

003060FED00A 11 24 JAN 1997
841 - Specifications/Technical Infonnation (Provide Technical Information)

2. This code is only used by a contractor when SPI08 in

the l/SPI/020 segment is code KH.

Q4 Prior Identifier Number

When SPI07 is code 25 or 53, use to indicate the unique

reference rmmber ofthe prior transaction set that

transmitted a portion ofthe requested information. If

more than one transaction set has been transmitted, cite

the unique reference number ofthe last transmission.

TN Transaction Reference Number

Use to indicate the reference number ofthe transaction

set to which this transaction set is responding.

REF02 127 Reference Identification X AN 1/30

Reference infonnation as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

003060FED00A 12 24JANri997
841 - Specifications/Technical Infonnation (Provide Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

NlOl

N102

N103

N104

Nl Name

120

Nl

Heading

Optiooal

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

1 At least one of N102 or N103 is required.

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

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

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

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

2 N105 and N106 further define the type of entity in NIO 1

Whenever possible, identification and address infiyrmation should be provided using

NlOl, N103, and N104. Use N102 and segments N2 through N4, as applicable, when

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

Data

Element

98

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

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

BY

KY

SE

93

66

Buying Party (Purchaser)

Use to indicate a government activity that is receiving

technical information.

Technical Office

Use to indicate a government activity that is transmitting technical information.

Selling Party

Use to indicate a commercial party that is either

transmitting or receiving technical information.

X AN 1/35

1/2

1

67

Name

Free-form name

Identification Code Qualifier X ID

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

Code (67)

While thefederal EDIprogram uses the DUNSnumber, 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.

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

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

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.

Department of Defense Activity Address Code

(DODAAC)

Commercial and Government Entity (CAGE)

Identification Code X AN 2/20

Code identifying a party or other code

10

33

003060FED00A 13 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Infoimation)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N2 Additiona] 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 N102 is used and it is necessary to provide

additional name information.

Ref.

Pes.

Must Use N201

N202

Data

Element Name

Data Element Summary

93 Name

Free-form name

93 Name

Free-form name

Attributes

M AN 1/35

O AN 1/35

003060FED00A 14 24 JAN 1997
841 - Specifications/Technical Information (Provide 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 paity

This segment should only be used when N102 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

00306OFEDO0A 15 24 JAN 1997
841 - Specifications/Technical Infonnation (Provide Technical fofonnation)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N4 Geographic Location

150

Nl

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 N40 1 through N404, or N405 and N406 may be adequate to specify a location.

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

This segment should only be used when N102 is used.

Data Element Summary

Ref. Data

Des. Element Name Attributes

N401 19 City Name O AN 2/30

Free-form text for city name

N402 156 State or Province Code O ID 2/2

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

N403 116 Postal Code O ID 3/15

Code defining international postal zone code excluding pimctuation and blanks

(zip code for United States)

N404 26 Country Code O ID 2/3

Code identifying the coimtry

003060FED00A 16 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

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 of REF02 or REF03 is required.

2 If either C04003 or CX)4004 is present, then the other is required.

3 If either C04005 or CX)4006 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 transmitting technical information, use

this segment to identify reference numbers applicable to the selling party.

Must Use

Ref.

Pes.

REFOl

Data

Element

128

Data Element Summary

Name

Reference Identification Qualifier

Code Qualifying the Reference Identification

EL

Attributes

M ID 2/3

Electronic device pin niunber

7. Use to indicate the identification number assigned to a selling party at the time ofregistration.

2. Use ofthis code is REQUIRED when the selling

party is transmitting technical information.

TJ Federal Taxpayer's Identification Number

W7 Commercial and Govermnent Entity (CAGE) Code

When NlOl is code SE and the selling party is transmitting technical information use to indicate the

CAGE code ofthe selling party ifN103 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 17 24 JAN 1997
841 - Specifications^echnical Mbnnation (Provide Technical Infonnation)

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 office to whom administrative communications should be directed

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

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

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

Ref.

Pes.

Must Use PEROl

PER02

PER03

PER04

PER05

Data

Element

366

Data Element Summary

93

365

364

365

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 the information point ofcontact at the

location ofthe party transmitting the technical data.

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 communication number

2/2

AU Defense Switched Network

EM Elecfronic 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 Telecommunications System (FTS)

FX Facsimile rr International Telephone

TE Telephone

Use to indicate a commercial telephone number.

18 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

Include the area code.

PER06 364 Communication Number X AN 1/80

Complete communications nmnber including country or area code when

applicable

PER07 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication nimiber

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 Telecommimications 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 coimtry or area code when

applicable

PER09 443 Contact Inquiry Reference O AN 1/20

Additional reference mraiber or description to clarify a contact number

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

003060FED00A 19 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

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:

Notes:

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

structure, such as relating Une-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, HLO 1 could be used to indicate the

nimiber 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 within the transactioa

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

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

segment up to the next occurrence of an HL segment in the transactioiL 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.

1. When transmitting 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, SPL andREF loops as necessary.

2. Eachfile or image transmitted in the BINsegment must be a separate HL loop.

Must Use

Ref.

Pes.

HLOl

HL02

Must Use HL03

Data

Element

628

734

735

Data Element Summary

Name Attributes

003060FED00A

Hierarchical m 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 H) 1/2

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

transmitted data.

26 Member

Use to indicate a section or portion ofan award

instrument deliverable. A portion ofthe deliverable is a

separatefile which is referenced by the base document

The separatefile is included in the base document when

20 24 JAN 1997
84 1 - SpecificationsTTechnical Information (Provide Technical Monnation)

it is processed by the appropriate software. Used only

by a contractor when SPI08 in the l/SPI/020 segment is code KA.

A Assembly

DG Drawing

ED Engineering Data List

F Component

FR Frame

Use to indicate a drawing sheetfi^ame.

I Item

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

IB Contract

RP Report

Use to indicate an award instrument deliverable. This

document is the entire deliverable or it is the base

document which references additional sections or

portions ofthe document in other HL loops where HL03

cites code 26. Ifthis is the base document, the other

portions are included when the base document is processed by the appropriate software. Used only by a

contractor when SPI08 in the l/SPI/020 segment is code KA.

SD Support Docimient

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 Child 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 21 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

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 commercialprotection level applicable to the referenced item.

Data

Element

786

128

Data Element Summary

Name Attributes

Security Level Code M ID 2/2

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

information following

1. When this transaction set is originated by a contractor, ifthe information

represented by the identified hierarchical level has both a government security

classification and a commercial protection requirement, this data element will

carry the government security classification code and the commercial

protection code will be carried in SPI09. Ifthe item being transmitted has only one protection requirement, then this data element can carry either the

government security classification code or the commercial protection code.

2. When the transaction set is originated by the government, this data element

may carry either the government security classification or the commercial

protection requirement code , as applicable, with the government security

classification code taking precedence. In this instance, SPI09 may only cite

code 99, when it is necessary to indicate that data referenced in the

transaction set is restricted to certified contractors.

3. The identified security classification or commercial protection requirement

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

II Competition Sensitive

90 Government Non-Classified

92 Govenunent Confidential

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

7M

List of Materials

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

ofMaterials (BOM) number. Identify the contractor

applicable to the LOMor BOMin the 2/REF/080

segment citing either code W7 or ZZ in REFOl.

2. Use when HL03 is code SD.

Frame

I. Use to indicate a drawing sheetframe number.

003060FED00A 22 24 JAN 1997

I

i
841 - Specifications/Technical Information (Provide Technical Information)

2. Use when HL03 is code FR.

TP Sheet

1. Use to indicate a drawing sheet number.

2. Use when HL03 is code SH.

7Q Engineering Change Order

1. Use to indicate an Engineering Change Order

number.

2. Use when HL03 is code SD.

89 Assembly Number

Use when HL03 is code A.

90 Subassembly Number

Use when HL03 is code U. 97 Package Number

1. Use to indicate a Technical Information Package

(TIP).

2. Use when HL03 is code I. CT Contract Number

Use when HL03 is code IB. DD Document Identification Code

When HL03 is code 26 or RP, use to indicate the

number assigned to the deliverable or portion/section of

the deliverable. The identifying numberfor an award

instrument deliverable is the Exhibit Line Item Number

(ELIN) that requires the deliverable. Ifnecessary, cite

the name ofthe deliverable in SPI04.

DG Drawing Niunber

1. 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 REFOI.

2. When used there must be at least one 2/REF/080

segment with REFOI citing code KV.

HF 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

REFOI.

2. Use when HL03 is code ED.

DC Item Nimiber

1. Use to indicate the number ofa component

2. Use when HL03 is code F. KS Solicitation

1. Use to indicate the solicitation technical data

package number.

2. Use when HL03 is code SL.

MU Military Specification (MILSPEC) Number

Use when HL03 is code SD.

NI Military Standard (MIL-STD) Number

Use when HL03 is code SD.

003060FED00A 23 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical

NJ

S3

VW

Information)

Technical Document Number

1. Use to indicate the number ofa technical manual.

2. Use 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 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 when HL02 is code SD.

W2 Weapon System Number

1. Use to indicate the number ofa system.

2. Use when HL03 is code SY.

WF Locally Assigned Q)ntrol Number

Use to indicate another type oflist, e.g., list ofcircuits

that comprise a network. Use only ifappropriate when

HL02 is code SD. Identify the name ofthe list in SPI04.

ZS Software Application Nimiber

I. 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 REFOI.

2. Use when HL03 is code SD.

ZZ Mutually Defined

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

SPI06 792 Entity Status Code O ID 1/1

Code indicating the current status of the data item specified by the electronic

data item

I. When SPI02 is code DD, use to identify the status ofa deliverable or ofa

portion/section ofthe deliverable.

003060FED00A

2. When SPI02 is code DG, use to identify the status ofa drawing, i.e., current

drawing or proposed drawing.

24 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Mbnnation)

A Approved Version

1. When SPI02 is code DD use to indicate afinal

deliverable.

2. When SPI02 is code DG, use to indicate a current

approved drawing.

J Proposed

1. When SPI02 is code DD, use to indicate a draft

deliverable.

2. When SPI02 is code DG, use to indicate a proposed

drawing.

SPI09 786 Security Level Code O ID 2/2

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

information following

1. When the transaction set is originated by a contractor, use this data element

ONLY when SPIOl is Code 92, 93, or 94 and the infiyrmation also has a commercial protection requirement.

2. The identified commercial protection level represents the highest

classification ofthe specified hierarchical level.

3. When the transaction set is originated by the government, this data element

may cite only code 99, ifapplicable.

06 Supplier Proprietary

This code is used only by a contractor.

11 Competition Sensitive

This code is used only by a contractor. 99 Government Defined (Trading Partner Level)

1. Use to indicate that information referenced in this

transaction set is restricted to certified contractors.

2. This code is used only by the government.

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

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

RDTOl

RDT02

RDT03

RDT04

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.

Data Element Summary

Data

Element Name Attributes

795

796

374

373

Revision Level Code O ID 1/1

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

referred to by the specification nimiber

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 engiaeeruig change level of the data items referred to by the

specification number

Date/Time Qualifier O ID 3/3

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

171 Revision

Use to indicate the date ofthe revision.

405 Production

When SPI02 is code HF, use to indicate the preparation

date ofan EDL.

824 Version

Use to indicate the date ofthe version.

Date X DT 6/6

Date (YYMMDD)

003060FED00A 26 24 JAN 1997

I
841 - Specifications/Technical Information (Provide Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

MSG Message Text

050

SPI

Detail

Optional

>1

To provide a jfree-form format that allows the transmission of text information

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

page, advance a line, etc.

1. Use this segment to transmit information applicable to a specific data item.

2. When transmitting an EDL, ifthe data item on the EDL is not availablefrom the

government, use this segment to provide that information and to identify, ifknown, where

the item can be obtained

3. Do not use this segment to provide specifications, standards, manuals, instructions,

lists, SOWs or any other type oftechnical information that can be provided in the BIN

segment.

Ref.

Pes.

Must Use MSGOl

Data

Element

933

Data Element Summary

Name

Free-Form Message Text

Free-form message text

Attributes

M AN 1/264

003060FEIX)0A 27 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Identification

080

REF

Detail

Optional

1To specify identifying information

1 At least one of REF02 or REF03 is required.

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

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

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

7. Use to identify reference numbers applicable to the item specified in SPI02/03.

2. When SPI02 is code DG, use ofthis segment is REQUIRED with REFOl citing code

kv.

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

2M Federal Communications Commission (FCC) Identifier

Use to indicate a circuit number.

78 Drawing Type

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

interpretation, installation, etc. Identify the type of

drawing in REF03

C7 Contract Line Item Number

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

solicitation.

F3 Submission Number

When SPI02 is code DD, use to indicate the submission

number ofthe deliverable, e.g., 1, 2, 3, etc., if

applicable.

GO Exhibit Identifier

When SPI02 is code DD, use to indicate the exhibit

letter to which the deliverable applies.

KV Distribution Statement Code

Use to indicate the Distribution Statement Code that is required on all drawings.

L6 Subcontract Line Item Number

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

solicitation.

NS National Stock Nimiber

QZ Reference Drawing Number

Use to indicate the reference numberfound on an

Engineering Data List (EDL).

W7 Commercial and Government Entity (CAGE) Code

When SPI02 is code 7K, DG, S3, VW, or ZS, use to indicate the CAGE code ofthe manufacturer applicable

to the document.

7Z Mutually Defined

When SPI02 is code 7K, DG, S3, VW, orZS, use to indicate the DUNSnumber ofthe manufacturer

applicable to the document.

003060FEDO0A 28 24 JAN 1997
841 - SpecificationsTTechnical Infonnation (Provide Technical Mbnnation)

REF02 127 Reference Identification X AN 1/30

Reference infonnation as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier

REF03 352 Description X AN 1/80

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

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

003060FED00A 29 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

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 information about the electronic format of the interchange data

1 If EFI05 is present, then EFI04 is required.

2 If EFI07 is present, then EFI06 is required

3 If EFI09 is present, then EFI08 is required.

4 If either EFI15 or EFI16 is present, then the other is required.

Use this segment to provide information applicable to data being transmitted in the BIN

segment or to identify the media andformat in which a document is available.

Must Use

Ref.

Pes.

EFIOl

EFI02

Data

Element

786

933

Data Element Summary

Name Attributes

Security Level Code M ID 2/2

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

information following

1. The security level code specified here relates to the specific binary data

provided in the BINsegment.

2. The security code providedfor the binary data being transmitted in the BIN

segment is the highestprotection level assigned to the data. Ifthe data have

both a government security classification and a commercial security protection

requirement, the government security classification takes precedence and shall

be provided in this data element.

06 Supplier Proprietary

11 Competition Sensitive

90 Govenmient Non-Classified

92 Government Confidential

93 Govenmient Secret

94 Government Top Secret

Free-Form Message Text O AN 1/264

Free-form message text

1. When an Engineering Data List (EDL) is being provided within the

transaction set, use to identify the media in which the data identified on the

EDL is available. Use only thefollowing words:

EFI04 799

CARD

DIGIT

PAPER

to indicate data is only available on an aperture card

to indicate the data is available as a digitalfile that can be

provided on a CD-ROMor transmitted over the DoD network

architecture

to indicate the data is only available in hard copyform

2. When identifying the media in which data is being provided, use only the

following words:

NET to indicate transmission via the DoD network architecture

CD-ROM to indicate data provided on CD-ROMand delivered by mail

CARD to indicate an aperture card is beingprovided by mail

PAPER to indicate the data is beingprovided in hard copyform

Version Identifier X AN 1/30

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

003060FED00A 30 24 JAN 1997
841 - Speciflcations/Techiiical Information (Provide Technical Information)

Use to specify the version, e.g., 2.0, 3.2, etc., ofthe program being used to create the data transmitted in thefollowing BINsegment. This data element

pertains to the program identifier specified in EFI05.

EFI05 802 Program Identifier O AN 1/30

Identifies the name of the software program from which the technical data

originates

Use to specify the application software program used to create the data being

transmitted in thefollowing BINsegment, e.g., TruckCad, ClassSCad, etc. EFI06 799 Version Identifier X AN 1/30

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

Use to identify the specific version ofthe interchange standard used to transmit the data in thefollowing BIN segment This data elementpertains to the interchangeformat specified in EFI07.

EFI07 801 Interchange Format O AN 1/30

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

Use to identify theformat in which the item is available or is being transmitted.

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

associated code. Other values may be used only ifmutually agreed between

the tradingpartners.

CODE FORMAT

ANSI

ASCII

BMP

C4

dBASE

EXCEL

GIF

Harvard

HTML

ISO-10918

KODAK

LOTUS

MAC

MSDOS

MIL-D-28000

MIL-R-2800I

MIL-R-28002

MIL-D-28003

ISO-Ill 72

PDES

PDF

PPOINT

PROJECT

RTF

TIFF

WINDOWS

WORD

WORDP

ANSI Text - (entire ANSI character set))

ASCII TEXT- (letters and numerals only)

Windows Bitmap

JEDMICSproprietaryformat

Borland dBASE

Microsoft Excel

Graphics Interchange Format

Software Publishing Company Harvard Graphics

HyperText Markup Language

Joint Photographies Expert Group (JPEG) - Lossy

compression ofphotographic images

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 WindowsApplication Program

Microsoft Word

Novell WordPerfect

EFI08 799 Version Identifier X AN 1/30

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

Use to identify the version ofthe program used to compress the data

003060FED00A 31 24 JAN 1997
841 - Specifications/Technical Monnation (Provide Technical liiformation)

transmitted in thefollowing BINsegment. This data elementpertains to the

compression technique program specified in EFI09.

Compression Technique O AN 1/30

Identifies the digital data compression means and the type

Use to identify the compression method, ifany, applied to the data transmitted

in thefollowing BINsegment Examples include TR, Moyer, Fish, PKZIP, etc. Drawing Sheet Size Code O AN 2/2

Code indicating the drawing size and orientation of a technical drawing as

specified and described in the current version of standards ANSI Y14.1 and

ISO 5457 (E); see the listed ANSI and ISO standards for the maximimi lengths

for rolled sheets *

1. Use to specify the drawing sheet size.

EFI09

EFIIO

800

789

EFIll 803

EFI13 787

2. Use any code.

Refer to 003060 Data Element Dictionaiy for acceptable code values.

File Name O AN 1/64

Name assigned or declared for a file or used by a program to identify a file; exact format of the name depends on the computer operating system being

used; name also may be known as the file's "data set name"

Format ofthefile name must conform to ISO 9660 standard, i.e., 8.3format (8

characterfile namefollowed by a 3 character extension with the dotpassed.

Leading spaces are notpassed).

Record Length O N 1/15

Quantity of characters or bytes in a record. Synonyms are "logical record

length" and "record size"

Use to identify the size ofafile.

!

003060FED00A 32 24 JAN 1997
Position: 160

Loop: EFI

Level: Detail

Usage: Mandatory

Max Use: 1 Purpose: To transfer binary data in a single data segment and allow identification of the end of the

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

binary data in this segment

Syntax Notes:

Semantic Notes:

Comments:

Data Element Summary

Must Use

Ref.

Pes.

BINOl

Data

Element

784 Length of Binary Data M NO 1/15

The length in integral octets of the binary data

Pf'Tien SPI02 is code HF, 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 fi^om hexadecimal 00 to

Name Attributes

Must Use BIN02 785

FF

When SPI02 is code HF, cite the number zero (0) to comply with the

mandatory nature ofthis data element

003060FED00A 33 24 JAN 1997
841 - Specifications/Technical Information (Provide Technical Information)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

010

Summary

Mandatory

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

segments (including the begiiming (ST) and ending (SE) segments)

SE is the last segment of each transaction set.

Ref.

Pes.

Must Use SEOl

Must Use SE02

Data

Element

96

329

Data Element Summary

Name Attributes

Numberof Included Segments M NO 1/10

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

segments

Transaction Set Control Number M AN 4/9

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

I

I

003060FED00A 34 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

f)erformance 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.
9iUo

S ^ S O 00 S 3

OS

OS

oooP

O 60

c >