Iillliii llii iiiiii 1 A111Q5 3SMfibO

' NtST

PUBLICATIONS

NIST Special Publication 881-28

i

1

MiHHHHiMiininmiB

1 1

Federal Implementation Guideline

for Electronic Data Interchange

ASC XI 2 003050 Transaction Set 836

Procurement Notices (Revision 1)

Implementation Convention

Nisr

QC

100

.U57

NO. 881 -28

1998

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology
rhe National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . . . needed to improve product quality, to modernize manufacturing processes,

to ensure product reliability . . . and to facilitate rapid commercialization ... of products based on new scientific

discoveries."

NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's

competitiveness; advance science and engineering; and improve public health, safety, and the environment. One

of the agency's basic functions is to develop, maintain, and retain custody of the national standards of

measurement, and provide the means and methods for comparing standards used in science, engineering,

manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal

Government.

As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and

applied research in the physical sciences and engineering, and develops measurement techniques, test methods, standards, and related services. The Institute does generic and precompetitive work on new and

advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.

Major technical operating units and their principal activities are listed below. For more information contact the

Publications and Program Inquiries Desk, 301-975-3058.

Office of the Director

• National Quality Program

• International and Academic Affairs

Technology Services

• Standards Services

• Technology Partnerships

• Measurement Services

• Technology Innovation

• Information Services

Advanced Technology Program

• Economic Assessment

• Information Technology and Applications

• Chemical and Biomedical Technology

• Materials and Manufacturing Technology

• Electronics and Photonics Technology

Manufacturing Extension Partnership

Program

• Regional Programs

• National Programs

• Program Development

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology'

• Optoelectronics'

Chemical Science and Technology

Laboratory

• Biotechnology

• Physical and Chemical Properties^

• Analytical Chemistry

• Process Measurements

• Surface and Microanalysis Science

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Optical Technology

• Ionizing Radiation

• Time and Frequency'

• Quantum Physics'

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• NIST Center for Neutron Research

Manufacturing Engineering

Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Fabrication Technology

• Manufacturing Systems Integration

Building and Fire Research

Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Safety Engineering

• Fire Science

Information Technology Laboratory

• Mathematical and Computational Sciences^

• Advanced Network Technologies

• Computer Security

• Information Access and User Interfaces

• High Performance Systems and Services

• Distributed Computing and Information Services

• Software Diagnostics and Conformance Testing

' At Boulder, CO 80303. ^Some elements at Boulder, CO.
NIST Special Publication 881-28

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 836

Procurement Notices (Revision 1)

Implementation Convention

Electronic Commerce Acquisition Program Management Office

Standard Management Committee - Secretariat

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Editor: Dr. Jean-Philippe Favreau

January 1998

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Gary R. Bachula, Acting Under Secretary for Technology

National Institute of Standards and Technology

Raymond G. Kammer, Director
Reports on Information Technology

The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL)

develops standards and guidelines, provides technical assistance, and conducts research for computers

and resources. As part of the overall federal effort to establish a single face to industry for conducting

electronic commerce, ITL has been designated as the organization responsible for coordinating the

development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are

defined by functional-area experts who create and select options from standard EDI Transaction Sets to

yield the implementations to be used for practical EDI. These ICs are made available to federal agencies

and industry by electronic means and this Special Publication Series.

National Institute of Standards and Technology Special Publication 881-28

Natl. Inst. Stand. Technol. Spec. Publ. 881-28, 39 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
836 Procurement Notices

Functional Group ID=rv\^

Introduction:

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

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

transaction set can be used by the buyer to notify the seller or other interested parties of the award or pending award

of a contract which may contain some indefinite features, such as delivery schedule, location, and/or quantities. This

transaction set can also be used for purchasing actions such as the notification of intent to award or actual award of a small business set-aside purchase, notification of being outside of the competitive range, notice of receipt of protest,

notice of receipt of a late bid, notice of bid rejection, notice of the disposition of an unsolicited proposal, public

notice of the abstract of bids, and the notification of the award of a requirements type contract.

Notes:

/. This transaction set can be used as an award announcement This notification will be publicly available to all

interestedparties and will provide the name ofthe party awarded the instrument and the price ofthe line items

awarded.

2. This transaction set can be used to provide publicly available data (BCOll is code 65) on a single award even

ifthe award was the result ofmore than one solicitation.

3. This transaction set can be also used by a buying activity as a preaward notification to bidders that their

proposals are no longer being consideredfor award; as a postaward notification to unsuccessful bidders; as a

notice ofintent to award a Small Business Set-Aside; as a notification to late bidders; as a notification ofa

receipt ofa protest; and as a notification ofdisposition ofan unsolicited proposal

Must Use

Pos. No. 005Seg. IDST

Name

Transaction Set Header

Req.

Pes. M

Max.Use

1

Loop Notes and

Repeat Comments

Must Use 008 BCO Beginning Segment for Procurement Notices M 1

Not Used 010 ITD Terms of Sale/Deferred Terms of Sale 0 5

Not Used 012 CTB Restrictions/ Conditions 0 5

Not Used 014 CTP Pricing Information 0 25

Not Used 016 FOB F.O.B. Related Instructions 0 I

018 AMT Monetary Amount 0 >1

020 QTY Quantity 0 >1

021 DTM Date/Time Reference 0 >I

Not Used 022 LDT Lead Time 0 >1

023 PWK Paperwork 0 >1

024 MSG Message Text 0 >I LOOP ID - Nl >1

025 Nl Name o

026 N2 Additional Name Information 0 2

027 N3 Address Information 0 2

028 N4 Geographic Location 0 1

Not Used 029 REF Reference Numbers 0 >1

Not Used 030 PER Administrative Communications Contact 0 >1

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

003050F836 1 15 July 1997
836 Procurement Notices

033 LM

Must Use 034 LQ

035 POl

Not Used 040 P03

050 CTP

Not Used 060 PID

Not Used 070 MEA

Not Used 080 PWK

090 REF

Not Used 100 PER

Not Used 101 ITD

102 DIM

Not Used 103 CTB

104 QTY

105 AMT

Not Used 110 SLN

Not Used 120 PID

130 Nl

140 N2

150 N3

160 N4

Not Used 170 REF

Not Used 180 PER

JNOi useo 1 C 1 rKjD

Not Used 182 DTM

Not Used 183 LDT

Not Used 184 MSG

185 LM

Must Use 186 LQ

Must Use 190 SE

LOOP ID - LM ftmy

>1

Code Source Information 0 I

Industry Code M >I

LOOP ID -POl >i

Baseline Item Data 0 1

Additional Item Detail 0 >1

Pricing Information 0 >1

Product/Item Description 0 >1

Measurements 0 >1

Paperwork 0 >1

Reference Numbers 0 >1

Administrative Communications Contact 0 >1

Terms of Sale/Deferred Terms of Sale 0 1

Date/Time Reference 0 10

Restrictions/ Conditions 0 1

Quantity 0 >1

Monetary Amount 0 >1 LOOP ID -SLN >1

Subline Item Detail 0 I

Product/Item Description 0 >1

LOOP ID - Nl >i Name 0 I

Additional Name Information 0 2

Address Information 0 2

Geographic Location 0 1

Reference Numbers 0 >1

Administrative Communications Contact 0 . >1

F.O.B. Related Instructions 0 >1

Date/Time Reference 0 >1

Lead Time 0 >1

Message Text 0 >1

LOOP ID - LM >i

Code Source Information 0

Industry Code M >i

Transaction Set Trailer M'

003050F836 1 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

005

Mandatory

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

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

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

selects the Invoice Transaction Set).

Data Element Summary

Ref. Data

Des. Element Name Attributes

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

Code uniquely identifying a Transaction Set

836 X12.54 Procurement Notices

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

Identifying control number that must be unique within the transaction set

fianctional group assigned by the originator for a transaction set This unique control number is assigned by the originator ofthe transaction

set or by the originator's application program. This same number is carried

in SE02.

003050F836 1 3 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

BCO Beginning Segment for Procurement Notices

008

Mandatory

1To indicate the beginning of the Procurement Notices Transaction Set and transmit

identifying numbers and dates

1 BCO03 is the date to be used for reference purposes in an RPQ and a response to RFQ.

2 BCO04 is the contract number.

3 BCO06 is the contract beginning date. 4 BCO07 is the contract expiration date. Comments:

Must Use

Ref.

Pes.

BCOOl

BCO02

BCO03

BCO04

Data

Element

353

586

373

127

Data Element Summary

Name Attributes

Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set 00 Original

Use to indicate an original notification.

01 Cancellation

'Use to indicate the cancellation ofa previously

transmitted notification.

07 Duplicate

Use to indicate a duplicate ofan original notification.

Request for Quote Reference Number O AN 1/45

Number assigned by the purchaser to identify his request for quote

% Use to identify the solicitation number, e.g., Invitation for Bid (IFB),

Requestfor Quotation (RF0, or Requestfor Proposal (RFP), that is applicable to the information being provided in the transaction set. When

BCOll is code 63 or 65, and there is more than one solicitation applicable to the award, do not use this data element. In this instance, cite the solicitation

number applicable to the line item awarded in the l/REF/090 segment.

2. Use ofthis data element is REQUIRED in all instances other than when

BCOll is code 70 or code 63 or 65 and more than 1 solicitation is applicable

to the award.

Date O DT6/6

Date (YYMMDD)

Use to identify the date ofthe solicitation cited in BCO02.

Reference Number O AN 1/30

Reference number or identification number as defined for a particular

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

1. Use to identify the number ofthe instrument that was awarded. For a new award, cite the Procurement Instrument Identification Number (PUN).

For the award ofan order against a basic contract or a Federal Supply

Schedule (FSS), concatenate the PIIN ofthe basic instrument/FSS and the

Supplementary Procurement Instrument Identification Number (SPUN).

Not Used BCO05 846

2, This data element is used only when BCOll is code 65. Contract Status Code O ID 2/2

003050F836 1 4 15 July 1997
836 Procurement Notices

BCO06

BCO07

Not Used BCO08

BCO09

BCOlO

Must Use BCOll

Code designating the current status of the contract 373 Date O DT 6/6

Date (YYMMDD)

1. Use to identify the date the award instrument cited in BCO04 was signed

or executed.

2. This data element is used only when BCOll is code 63 or 65. 373 Date O DT 6/6

Date (YYMMDD)

1. Use to identify the effective date ofthe award instrument cited in BCO04

if different than the date cited in BCO06.

2. This data element is used only when BCOll is code 63 or 65. 587 Acknowledgment Type O ID 2/2

Code specifying the type of acknowledgment

128 Reference Number Qualifier O ID 2/2

Code quaUfying the Reference Number.

TN Transaction Reference Number

Use to indicate a unique reference number assigned to this transaction set. 127 Reference Number " ' q AN 1/30

Reference number or identification number as defined for a particular

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

640 Transaction Type Code O ID 2/2

Code specifying the type of transaction

Use is REQUIRED to identify the type oftransaction set. 62

63

64

65

66

67

69

Preaward Notification

Use to indicate a Preaward Notification in accordance

with FAR 15.1001(b). When this code is used,

revisions to the proposal will not be considered.

Postaward Notification

Use to indicate a Postaward Notification in

accordance with FAR 15.1001(c).

Small Business Award Notification

Vse to indicate a notification to unsuccessfvtl o^WSfs^

oftite apparent successful offerorfor a Small

Business Set-Aside in accordance with FAR

15.1001(2). When this code is used, revisions to the

proposal will not be considered and no response is required unless a basis exists to challenge the small

business size status ofthe apparent successful offeror.

Award Notification

Use to indicate a publicly available award notification

in accordance with FAR 4.504.

Notification to Late Bidders

Use to indicate a Notification to Late Bidders in

accordance with FAR 14.304-2.

Notification of Protest Receipt

Use to indicate a Notification ofProtest Receipt by the

Agency, the General Accounting Office (GAO) or the

General Services Board of Contract Appeals (GSBCA)

in accordance with FAR 13.103(b)(1), FAR

33. 1 04(a)(2) or FAR 33. 1 05(a)(2)(i) respectively.

Bid Rejection Notice

003050F836 1 15 July 1997
836 Procurement Notices

Use to indicate a Rejection Noiijfication ofan " "

individual bid in accordance with FAR 14.404-2.

70 Unsolicited Bid Notice

Use to indicate a notification ofdisposition ofan

unsolicitedproposal in accordance with FAR 15.506.

BC012 306 Action Code O ID 1/2

Code indicating type of action

p%e data element is used only when BCOll is code 70.

7 Request

Use to indicate additional information is requested

before an unsolicited proposal can beprocessed. Use

the l/MSG/024 segment to identify the required

information.

9 Not Capable of Taking Action

Use to indicate an unsolicited proposal is not being

processed by the receiving activity. Use the

l/MSG/024 segment to identify the reasons for not

processing the proposal.

AC Acknowledge

Use to indicate receipt acknowledgment and

processing ofan unsolicited proposal.

DS Discarded

Use to indicate a rejection ofan unsolicited proposal

Use the l/LM/033 loop to provide the reasonsfor

^ection.

003050F836_1 6 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use AMTOl

Must Use AMT02

Not Used AMT03

AMT Monetary Amount

018

Optional

>1

To indicate the total monetary amount

7. Use this I/AMT/018 segment to specific the total amount ofthe award instrument.

2. Use this segment only when BCOll is code 63 or 65.

Data Element Summary

Data

Element Name

522

782

478

Attributes

Amount Qualifier Code M ID 1/2

Code to qualify amount

TK Total Amount of Contract

Use to indicate the total amount of an award.

Monetary Amount M R 1/15

Monetary amount

Credit/Debit Flag Code O ID 1/1

Code indicating whether amount is a credit or debit

003050F836 1 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use QTYOl

Must Use QTY02

Not Used QTY03

QTY Quantity

020

Optional

>1

To specify quantity information

1. Use this l/QTY/020 segment to identify the number of offerors solicited and the

number ofproposals received, if applicable to all ofthe line items.

2. Ifthere is more than one solicitation applicable to the award, use the l/QTY/104

segment to identify the quantity ofofferors solicited and the quantities ofproposals

receivedfor each line item.

^. Use this segment only when BCOll is code 63 or 65.

Data Element Summary

Data

Element

673

Attributes

M ID 2/2

380

355

Name

Quantity Qualifier

Code specifying the type of quantity

87 Quantity Received

Use to indicate the number ofproposals received.

SB Solicited

Use to indicate the number ofofferors solicitedfor

other than EDIpublic solicitations.

Quantity M R 1/15

Numeric value of quantity

Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or maimer in

which a measurement has been taken

003050F836 1 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

DTM Date/Time Reference

021

Optional

>1

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

Must Use

Ref.

Pes.

DTMOl

DTM02

DTM03

DTM04

Data

Element

374

Data Element Summary

Name

Date/Time Qualifier

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

Attributes

M ID 3/3

050 Received

When BCOll is code 66, use to indicate the date and

time the bid was received.

097 Transaction Creation

Use to indicate the date ofthis transaction set. 099 Bid Open (Date Bids Will Be Opened)

When BCOll is code 66, use to indicate the bid

opening date and time.

432 Submission

Date on which claim billing information was sent to payer

When BCOll is code 67, use to indicate the date by

which relevant information regarding the protest is to be submitted to the party identified in the l/Nl/025

segment with NlOl citing code PJ.

373 Date X DT 6/6

Date (YYMMDD)

337 Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Use when BCOll is code 66. Specify the time only in HHMMformat

623 Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Use when BCOll is code 66. CT

ET

GM

LT

MT

PT

Central Time

Eastern Time

Greenwich Mean Time

Local Time

Use to indicate the time at the receivingfacility.

Mountain Time

Pacific Time

003050F836 1 9 15 July 1997
836 Procurement Notices

DTM05 624 Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Not Used DTM06 1250 Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Not Used DTM07 1251 Date Time Period X AN 1/35

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

003050F836 1 10 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

PWKOl

PWK02

Not Used PWK03

Not Used PWK04

Not Used PWK05

Not Used PWK06

PWK07

PWK Paperwork

023

Optional

>1

To identify the type and transmission of paperwork or supporting information

1 If either PWK05 or PWK06 is present, then the other is required.

1 PWK05 and PWK06 may be used to identify the addressee by a code number.

2 PWK07 may be used to indicate special information to be shown on the specified

report.

3 PWK08 may be used to indicate action pertaining to a report.

When BCOll is code 67, use to identify papemork that is being provided by the

firiginator ofthe transaction set

Data Element Summary

Data

Element Name

755

Attributes

Report Type Code M ID 2/2

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

P2 Protest Use to indicate a copy ofthe protest is being provided.

756 Report Transmission Code O ID 1/2

Code defining timing, transmission method or format by which reports are to be sent BE By Mail and Electronically

Use to indicate E-MaiL

BM By Mail

Use to indicate transmittal via the United States Postal

Service (USPS).

CF Courier

^tlse to indicate transmittal via commercial express

courier.

EL Electronically Only

Use to indicate that data was sent by a separate

Electronic Data Interchange (EDI) transaction set. When used, identify the XI2 transaction set designation and the unique number ofthe transaction

set in PWK07, e.g., 864P87120. g

FX By Fax

757 Report Copies Needed O NO 1/2

The number of copies of a report that should be sent to the addressee

98 Entity Identifier Code O ID 2/2

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

66 Identification Code Qualifier X ID 1/2

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

Code (67)

67 Identification Code X AN 2/20

Code identifying a party or other code

352 Description O AN 1/80

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

When PWK02 is code EL, use to identify the XI2 transaction set and the

transaction set unique number, e.g., 864 P87120.

003050F836 1 11 15 July 1997
836 Procurement Notices

Not Used PWK08 C002 Actions Indicated O

Actions to be performed on the piece of paperwork identified

Not Used C00201 704 Paperwork/Report Action Code M ID 1/2

Code specifying how the paperwork or report that is identified in the PWK

segment relates to the transaction set or to identify the action that is required

Not Used C00202 704 Paperwork/Report Action Code O ID 1/2

Code specifying how the paperwork or report that is identified in the PWK

segment relates to the transaction set or to identify the action that is required

Not Used C00203 704 Paperwork/Report Action Code O ID 1/2

Code specifying how the paperwork or report that is identified in the PWK

segment relates to the transaction set or to identify the action that is required

Not Used C00204 704 Paperwork/Report Action Code O ID 1/2

Code specifying how the paperwork or report that is identified in the PWK

segment relates to the transaction set or to identify the action that is required

Not Used C00205 704 Paperwork/Report Action Code O ID 1/2

Code specifying how the paperwork or report that is identified in the PWK

segment relates to the transaction set or to identify the action that is required

003050F836 1 12 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use MSGOl

Not Used MSG02

MSG Message Text

024

Optional

>1

To provide a free form format that would allow 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.

/. When BC012 is code 7, use this segment to iMntify the aMWrnMinfofmSSvon

required. When BC012 is code 9, use this segment to identify the reasons the

unsolicitedproposal is not being processed.

2, Use also when LQ02 in either the l/LQ/034 or 1/LQ/l86 segment is any code that

requires a more detailed explanation.

Data Element Summary

Data

Element Name

933 Free-Form Message Text

Free-form message text 934 Printer Carriage Control Code O ID 2/2

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

Attributes

M AN 1/264

003050F836 13 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl

025

Nl

Name

Optional

Optional

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

1 At least one of N102 or N103 is required.

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

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

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

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

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

1. Whenever possible, identification and address information should 'be provtd^Tmv^

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

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

E2. When BCOll is code 63, use ofthis segment is REQUIRED to identify the party

receiving an award but only if one party was awarded all ofthe line items in a

solicitation. Ifline items in a solicitation were awarded to various parties, use the

l/Nl/130 segment to identify the parties.

[5. When BCOll is code 64, and the total award is to be made to one small business

entity, use ofthis segment is REQUIRED to identify that entity. Ifmultiple small

business entities are to receive awards, use the l/Nl/130 segment to identify those

entities to be awarded specific line items.

4. When BCOll is code 65, this segment is REQUIRED to identify the party receiving an award.

Must Use

Data Element Summary

Ref. Data

Des. Element Name Attributes

NlOl 98 Entity Identifier Code M ID 2/2

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

21

7Q

BY

PJ

SE

TO

Small Business

When BCOll is code 64, use to indicate the apparent

successful offeror ofa Small Business Set-Aside.

Party to Whom Protest Submitted

When BCOll is code 67, use to indicate the

organization to whom a protest was submitted (either

Agency, GAO or GSBCA).

Buying Party (Purchaser)

When BCOll is code 62, 63, 64, 65, 66, 67, 69 or 70, use to indicate the organization providing the

notification or awarding the instrument.

Party to Receive Correspondence

When BCOll is code 67, use to indicate the party to whom information relevant to a protest should be

submitted.

Selling Party

When BCOll is code 63, or 65, use is REQUIRED to

cite the name ofthe party receiving an award.

Message To

When BCOll is code 62, 63, 64, 66, 67, 69, or 70, use

003050F836 1 14 15 July 1997
836 Procurement Notices

N102

Must Use N103

Must Use N104

Not Used N105

Not Used N106

to indicate the party to whom a hotiflcaiion is being'

sent

93 Name " X AN 1/35

Free-form name

When BCOll is code 63, 64, or 65, use is REQUIRED to cite the name of

the party receiving an award.

66 Identification Code Qualifier X ID 1/2

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

Code (67)

WItile 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 to new procurement actions.

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

IJse ofthe DUNS or 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 oftneDUNSdfDUWS^niimberis preferred

over other codes to identify an entity.

10 Department of Defense Activity Address Code

(DODAAC) ^ ^

Use to indicate a D'epafimmi ofDefense^oTC^Ui^^'^

Agency Activity Address code.

33 Commercial and Government Entity (CAGE)

67 Identification Code X AN 2/20

Code identifying a party or other code

706 Entity Relationship Code O ID 2/2

Code describing entity relationship

98 Entity Identifier Code O ID 2/2

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

003050F836 1 15 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N2 Additional Name Information

026

Nl Optional

Optional

2

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

This segment is not necessary when the entity cited in NlOl is described using a code

inN103/N104

Data Element Summary

Ref. Data

Des. Element Name

Must Use N201 93 Name

Free-form name

N202 93 Name

Free-form name

Attributes

M AN 1/35

O AN 1/35

003050F836 1 16 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use N301

N302

Address Information

027

Nl Optional

Optional

2

To specify the location of the named party

This segment is not necessary when the entity cited in NlOl is described using a code

mN103/N104

Data Element Summary

Data

Element Name Attributes

166 Address Information M AN 1/35

Address information

166 Address Information O AN 1/35

Address information

003050F836 1 17 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

N401

N402

N403

N404

Not Used N405

Not Used N406

N4 Geographic Location

028

Nl Optional

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

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

This segment is not necessary when the entity cited in NlOl is described using a code

inN103/N104

Data

Element

19

156

116

26

309

310

Data Element Summary

Attributes

O AN 2/30

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 government agency

Postal Code O ID 3/11

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States)

Country Code O ID 2/3

Code identifying the country

Location Qualifier X ID 1/2

Code identifying type of location

Location Identifier O AN 1/30

Code which identifies a specific location

003050F836 1 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LM Code Source Information

033

LM Optional

Optional

ITo transmit standard code list identification information

1 LM02 identifies the applicable industry code list source information.

1. Use this l/LM/033 loop to provide coded information identifying the reason a

proposal is unacceptable or to identify the solicitation method that resulted in an

award.

Must Use

Ref.

Pes.

LMOl

LM02

2. This segment is used only when BCOll is code 62, 63, 65, 69, or 70.

Data

Element

559

822

Data Element Summary

Attributes

M ID 2/2

Name

Agency Qualifier Code

Code identifying the agency assigning the code values

DF Department of Defense (DoD)

Source Subqualifier

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

When LQOl is code ZZ, identify the code list that contains the code cited in

LQ02.

O AN 1/15

003050F836 1 19 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

LQOl

LC^ Industry Code

034

LM Optional

Mandatory

>1

Code to transmit standard industry codes

1 If LQO 1 is present, then LQ02 is required.

This segment is used only when BCOll is code 62, 63, 65, 69, or 70 and the

information applies to all ofthe line items or the entire bid/proposal. When this

information varies by line item, use the l/LM/185 loop.

Data

Element

1270

LQ02 1271

Data Element Summary

Name Attributes

Code List Qualifier Code O ID 1/3

Code identifying a specific industry code list NL No Longer Considered for Award Reason

When BCOll is code 62, use to indicate the reason a

proposal is no longer being consideredfor award.

RF Failure to Award Reason

Wlten BCOll is code 63, use to indicate the reason a proposal is unacceptable.

RR Bid Rejection Reason

When BCOll is code 69, use to indicate the reason for

the rejection ofa bid.

SM Solicitation Method

When BCOll is code 65, use to indicate the method by

which offers were solicited, e.g., direct solicitation,

sole source, bulletin board, etc. UP Unsolicited Proposal Rejection Reason

When BCOll is code 70, use to indicate the reason an

unsolicited proposal was rejected.

ZZ Mutually Defined

Use to indicate that a code list is identified in LM02.

Industry Code X AN 1/20

Code indicating a code from a specific industry code list

1. Use to cite a codefrom the code list identified by the qualifier in LQOl.

2. When LQOl is code ZZ, use to cite a codefrom the code list identified in

LM02.

003050F836 20 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

POl Baseline Item Data

035

POl Optional

Optional

1To specify basic and most frequently used line item data

12

3

4

5

6

7

8

9

10

11

12

If POl 03 is present, then POl 02 is required.

If POl 05 is present, then POl 04 is required.

If either POl 06 or POl 07 is present, then the other is required.

If either POl 08 or POl 09 is present, then the other is required.

If either POl 10 or POl 1 1 is present, then the other is required.

If either POl 12 or POl 13 is present, then the other is required.

If either POl 14 or POl 15 is present, then the other is required.

If either POl 16 or POl 17 is present, then the other is required.

If either POl 18 or POl 19 is present, then the other is required.

If either POl 20 or P0121 is present, then the other is required.

If either POl 22 or POl 23 is present, then the other is required.

If either P0124 or P0125 is present, then the other is required.

1 See the Data Dictionary for a complete list of ID's. 2 POlOl is the line item identification.

3 POl 06 through POl 25 provide for ten (10) different product/service ID's per each

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

SKU.

Notes: L Use this l/POl/035 loop to provide award data for each line item in the solicitation

when BCOll is code 63 or 65.

2. When BCOll is code 62, use this loop only to identify those line items which the

offeror is no longer being consideredfor award.

3. When BCOll is code 64, use this loop only to identify those line items in a Small

Business Set-Aside that are being awarded to different small business entities.

4. When BCOll is code 69, use this loop to identify those line items that are being

rejected on an individual bid.

5. This loop is not used when BCOll is code 66, 67, or 70.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use POlOl 350 Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set Use to identify the line item numberfrom a solicitation, bid or proposal, as

applicable. Do not cite the line item numberfrom an award instrument.

PO102 330 Quantity Ordered X R 1/9

Quantity ordered

1. Cite the total quantity ofthe line item that was awarded, not solicited.

2. When BCOll is code 63 or 65, this data element is REQUIRED.

PO103 355 Unit or Basis for Measurement Code

^^^^^"^^^^^^^^ " " . - ^

id 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

1. Use any code, other than code ZZ.

2. When BCOll is code 63 or 65, this data element is REQUIRED.

003050F836 1 21 15 July 1997
836 Procurement Notices

KA

NC

NE

NS

TB

Must Use PO106

Must Use PO107

PO108

Refer to 003050 Data Element Dictionary for acceptable code values.

PO104 212 Unit Price X R 1/17

Price per unit of product, service, commodity, etc.

1. When PO105 is code NC, NS, or TB, cite the number "0".

2. When BCOll is code 63 or 65, this data element is REQUIRED.

PO105 639 Basis of Unit Price Code O ID 2/2

Code identifying the tj^e of unit price for an item

ES Estimated

FB Fabrication Cost

Use to indicate the price includes the incorporation of

Government Furnished Property (GFP).

Price with Government Furnished Property

'Use to indicate the price ofthe items includes the use of Government Furnished Property (GFP) to manufacture the item.

No Charge

Not to Exceed

Not Separately Priced

^se to indicate the item is not separatelypriced but is included in the price ofthe item to which it pertains.

When used, cite the number "0" in PO104,

To be negotiated.

235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

7. Use any code, other than code ZZ.

2. When BCOll is code 63 or 65, as a minimum, there must he one

occurrence of a 235/234 pair citing either code CN or SV. Other codes may

be used to further describe the line item but they must be the same as those

usedfor the corresponding item in the cited award instrument.

Refer to 003050 Data Element Dictionary for acceptable code values.

234 Product/Service ID X AN 1/40

Identifying number for a product or service

235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

PO109 234 Product/Service ID X AN 1/40

Identifying number for a product or service

POllO 235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

POlll 234 Product/Service ID X AN 1/40

Identifying number for a product or service

P0112 235 Product/Service ID Qualifier X ID 2/2

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

Product^Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

P0113 234 Product/Service ID X AN 1/40

Identifying number for a product or service

003050F836 1 22 15 July 1997
836 Procurement Notices

P0114 235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

P0115 234 Product/Service ID X AN 1/40

Identifying number for a product or service

P0116 235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

P0117 234 Product/Service ID X AN 1/40

Identifying number for a product or service

P0118 235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

P0119 234 Product/Service ID X AN 1/40

Identifying number for a product or service

PO120 235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

P0121 234 Product/Service ID X AN 1/40

Identifying number for a product or service

P0122 235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

P0123 234 Product/Service ID X AN 1/40

Identifying number for a product or service

P0124 235 Product/Service ID Qualifier X ID 2/2

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

Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

P0125 234 Product/Service ID X AN 1/40

Identifying number for a product or service

003050F836 1 23 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

CTP Pricing Information

050

POl Optional

Optional

>1

To specify pricing information

1 If either CTP04 or CTP05 is present, then the other is required.

2 If CTP06 is present, then CTP07 is required.

3 If CTP09 is present, then CTP02 is required.

4 If CTP 1 0 is present, then CTP02 is required.

1 CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90

would be the factor if a 10% discount is given.

2 CTP08 is the rebate amount.

1 See Figures Appendix for an example detailing the use of CTP03 and CTP04.

See Figures Appendix for an example detailing the use of CTP03, CTP04 and

CTP07.

1. Use this segment to provide additionalprice information related to the line item

awarded, e.g., step-ladder prices, delivery zone prices, packagingprices, etc.

2. This segment is used only when BCOll is code 63 or 65.

Data Element Summary

Not Used

Ref.

Pes.

CTPOl

CTP02

Data

Element

687

236

Attributes

O ID 2/2

X ID 3/3

Name

Class of Trade Code

Code indicating class of trade

Price Identifier Code

Code identifying pricing specification

^se to identify various prices applicable to the line item

ICL Unit Price Through Quantity

J. Use to indicate the end ofa quantity range

applicable to step ladder pricing.

2. Use in conjunction with codes PBQ and MAXfor

step ladderpricing. Step ladder pricing is defined as the price specifiedfor the quantity range containing

the quantity purchased, applying to all the items

purchased. Use ofcodes ICL, MAXand PBQ is in

contrast to use ofcode PAQ which identifies quantities

at which different prices are applied.

MAX Maximum Order Quantity Price

1. Use to indicate the end ofa quantity range

applicable to step ladder pricing.

2. Use in conjunction with codes ICL and PBQfor

step ladder pricing. Step ladderpricing is defined as

the price specifiedfor the quantity range containing

•the quantity purchased, applying to all the items

purchased. Use ofcodes ICL, MAXand PBQ is in

contrast to use ofcode PAQ which identifies quantities

at which different prices are applied.

PAP Protection Level Price

Use to indicate the pricefor thepackaging protection

level (preservation) cited in CTPIO. This amount is additive to the unit price cited in POl04 or to the zone

003050F836 1 24 15 July 1997
836 Procurement Notices

price cited in CTP03 (when CTP02 is code ZNP)

which are based on standard commercial preservation.

PAQ Price Break Quantity(s)

Use to indicate a quantity where an incremental price

break occurs. For example, ifprice breaks occur at

quantities 11, 21, 31, etc., then for a purchase quantity

of25, thefirst 10 units are at thefirst price, the next

10 units are at the second price and the last 5 units are

at the third price. This is in contrast to step ladder

prices where all 25 units are oneprice.

PBQ Unit Price Beginning Quantity

1. Use to indicate the beginning ofa quantity range M

applicable to step ladder pricing.

CTP03

CTP04

CTP05

Not Used CTP06

Not Used CTP07

Not Used CTP08

Not Used CTP09

CTPIO

2. Use in conjunction with codes ICL and MAXfor

step ladder pricing. Step ladder pricing is defined as

the price specifiedfor the quantity range containing

the quantity purchased, applying to all the items

purchased. Use ofcodes ICL, MAXand PBQ is in

contrast to use ofcode PAQ which identifies quantities

at which different prices are applied.

PPA Packing Level Price

Use to indicate the pricefor the packaging level cited

in CTPIO. This amount is additive to the unit price

cited in PO104 or to the zone price cited in CTP03

(when CTP02 is code ZNP) which are based on

standard commercial packaging.

ZNP Zone Price

Use to indicate the pricefor delivery to a zone cited in

CTPIO. This is the total price ofthe item and is based on standard commercial packaging andpreservation.

Ifa higher level ofpackaging andpreservation is required, use additional repetitions ofthis segment

citing code PAP and PPA in CTP02.

Ill Unit Price O R 1/17

Price per unit of product, service, commodity, etc. 380 Quantity X R 1/15

Numeric value of quantity

355 Unit or Basis for Measurement Code X ID 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

'Use any code, other than code ZZ.

Refer to 003050 Data Element Dictionary for acceptable code values.

648 Price Multiplier Qualifier O ID 3/3

Code indicating the type of price multiplier

649 Multiplier

Value to be used as a multiplier to obtain a new value

782 Monetary Amount

Monetary amount

639 Basis of Unit Price Code

Code identifying the type of unit price for an item

499 Condition Value

Identifies rate restrictions or provisions

When CTP02 is code PAP, PPA, or ZNP, cite the applicable protection level,

packing level or delivery zone to which the price in CTP03 applies. ^

X R 1/10

O R 1/15

O ID 2/2

O AN 1/10

003050F836 1 25 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Numbers

090

POl Optional

Optional

>1

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

1. Use this l/RiE'F/OWd segment when the solicitation varies by awarded line item.

When the solicitation is the samefor all ofthe awarded line items, cite the solicitation

number in BCO02.

Must Use

Ref.

Pes.

REFOl

Not Used

REF02

REF03

2. This segment is used only when BCOll is code 63 or 65 and the award was the

result ofmore than one solicitation.

Data

Element

128

127

352

Data Element Summary

Name

Reference Number Qualifier

Code qualifying the Reference Number.

KS Solicitation

Attributes

M ID 2/2

A discreet number assigned by the purchasing activity

to differentiate between different solicitations

Use to indicate the solicitation (IFB, RFF, or RFQ)

that contained the awarded line item.

Reference Number X AN 1/30

Reference number or identification number as defined for a particular

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

Description X AN 1/80

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

003050F836 1 26 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

DTM Date/Time Reference

Ref.

Pes.

Must Use DTMOl

DTM02

Not Used DTM03

Not Used DTM04

DTM05

Not Used DTM06

Not Used DTM07

102

POl Optional

Optional

10

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

1. Use this l/DTM/102 segment to iSFn^y We"^Me^of^^ cited fit REFOl/02.

2. This segment is only used when BCOll is code 63 or 65.

Data

Element

374

373

337

623

624

1250

1251

Data Element Summary

Name Attributes

Date/Time Qualifier M ID 3/3

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

642 Solicitation

lUse to indicate the date ofthe solicitation.

Date

^^^^ ^ DT6/6

Date (YYMMDD)

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = mmutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Date Time Period X AN 1/35

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

003050F836 1 27 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use QTYOl

Must Use QTY02

Not Used QTY03

QTY Quantity

Optional

104

POl

Optional

>1

To specify quantity information

1. Use this l/QTY/104 segment to identify the number ofofferors solicited and the

number ofproposals receivedfor the line item cited in POl01.

'^2. This segment is only used when BCOll is code 63 or 65.

Data Element Summary

Data

Element Name Attributes

673 Quantity Qualifier M ID 2/2

Code specifying the type of quantity

87 Quantity Received

Use to indicate the number ofproposals received.

SB Solicited

Use to indicate the number of offerors solicited for

other than EDIpublic solicitations.

380 Quantity M R 1/15

Numeric value of quantity

355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or maimer in

which a measurement has been taken

003050F836 1 28 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use AMTOl

Must Use AMT02

Not Used AMT03

AMT Monetary Amount

Optional

105

POl

Optional

>1

To indicate the total monetary amount

/. Use this l/AMT/105 segment to identify the total price ofthe line item awarded.

2. This segment is only used when BCOll is code 63 or 65.

Data Element Summary

Data

Element Name

522 Amount Qualifier Code

Code to qualify amount

1 Line Item Total

782 Monetary Amount

Monetary amount

478 Credit/Debit Flag Code

Code indicating whether amount is a credit or debit

Attributes

M ID 1/2

M R 1/15

O ID 1/1

003050F836 1 29 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

130

Nl Optional

Optional

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

1 At least one of N102 or N103 is required.

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

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

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

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

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

/. Use this segment only when BCOll is code 63 and the line items in a solicitation were awarded to different parties or code 64 and tite apparent small business

successful offeror is differentfor each line item.

2. Use ofthis segment is REQUIREDfor the conditions stated in note 1.

3. Wheneverpossible, identification and address information should be provided using

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

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

Ref.

Pes.

Must Use NlOl

Must Use N102

Must Use N103

Must Use N104

Not Used N105

Data

Element

98

93

66

67

706

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

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

21 Small Business

Use to indicate the apparent small business successful

offerorfor the line item.

SE Selling Party

Use to indicate the party awarded the line item.

Name X AN 1/35

Free-form name

Identification Code Qualifier X ID 1/2

Code designatitig 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 to new procurement actions.

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

Use ofthe DUNS orDUNS+4 number is preferred

over other codes to identify a namedparty.

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

Suffix

Use ofthe DUNS or DUNS+4 number is preferred

over other codes to identify a namedparty.

33 Commercial and Government Entity (CAGE)

Identification Code X AN 2/20

Code identifying a party or other code

Entity Relationship Code O ID 2/2

003050F836 1 30 15 July 1997
836 Procurement Notices

Code describing entity relationship

Not Used N106 98 Entity Identifier Code O ID 2/2

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

003050F836 1 31 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

N2 Additional Name Information

140

Nl Optional

Optional

2

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

Use this segment only ifthe name cited in N102 is longer than 35 characters.

Data Element Summary

Ref. Data

Des. Element Name

Must Use N201 93 Name

Free-form name

N202 93 Name

Free-form name

Attributes

M AN 1/35

O AN 1/35

003050F836 1 32 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use N301

N302

Address Information

150

Nl Optional

Optional

2

To specify the location of the named party

This segment is not necessary when the entity cited in NlOl is described using a code

in N103/N104

Data Element Summary

Data

Element Name Attributes

166 Address Information M AN 1/35

Address information

166 Address Information O AN 1/35

Address information

003050F836 1 33 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

N401

N402

N403

N404

Not Used N405

N4

160

Nl

Geographic Location

Optional

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

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

This segment is not ne,c,essary when the entity cited in NlOl is described using a code

in N103/N104.

Data

Element

19

156

116

26

Not Used N406

309

310

Data Element Summary

Attributes

O AN 2/30

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 government agency

Postal Code O ID 3/11

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States)

Country Code O ID 2/3

Code identifying the country

Location Qualifier X ID 1/2

Code identifying type of location

Location Identifier O AN 1/30

Code which identifies a specific location

003050F836 1 34 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

LMOl

LM02

LM Code Source Information

185

LM Optional

Optional

1To transmit standard code list identification information

1 LM02 identifies the applicable industry code list source information.

/. Use this l/LM/185 loop to provide coded information to identify the reason the line

item in the proposal is no longer being consideredfor award; why the proposalfor the

line item was unacceptable; why the line item bid was rejected, or the solicitation

method applicable to the line item.

i. This segment is used only when BCOll is code 62, 63, 65, or 69.

Data Element Summary

Data

Element

559

822

Attributes

M ID 2/2

Name

Agency Qualifier Code

Code identifying the agency assigning the code values

DF Department of Defense (DoD)

Source Subqualifier

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

When LQOl is code ZZ, identify the code list that contains the code cited in

LQ02.

O AN 1/15

003050F836 1 35 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

LQOl

LQ02

LC^ Industry Code

186

LM Optional

Mandatory

>1

Code to transmit standard industry codes

1 If LQOl is present, then LQ02 is required.

This segment is used only when BCOll is code 62, 63, 65, or 69, and the information

varies by line item. When this information applies to all ofthe line items, use the

l/LQ/034 segment

Data

Element

1270

1271

Data Element Summary

Name Attributes

Code List Qualifier Code O ID 1/3

Code identifying a specific industry code list NL No Longer Considered for Award Reason

When BCOll is code 62, use to indicate the reason a

line item is no longer being consideredfor award.

RF Failure to Award Reason

Wlten BCOll is code 63, use to indicate the reason a

proposalfor a line item was unacceptable.

RR Bid Rejection Reason

When BCOll is code 69, use to indicate the reason for

the rejection ofa line item bid.

SM Solicitation Method

When BCOll is code 65, me to indicate the method by

which offers were solicitedfor the line item, e.g., direct

solicitation, sole source, bulletin board, etc. ZZ Mutually Defined

'iJse to indicate that a code list is identified in LM02.

Industry Code X AN 1/20

Code indicating a code from a specific industry code list

1. Use to cite a codefrom the code list identified by the qualifier in ig^lT"^^

2. When LQOl is code ZZ, use to cite a codefrom the code list identified in

LM02.

003050F836 36 15 July 1997
836 Procurement Notices

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

190

Mandatory

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

segments (including the beginning (ST) and ending (SE) segments).

1 SE is the last segment of each transaction set.

Must Use

Must Use

Ref.

Pes.

SEOl

SE02

Data

Element

96

329

Data Element Summary

Name Attributes

Number of Included Segments M NO 1/10

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

segments

Transaction Set Control Number M AN 4/9

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

003050F836 1 37 15 July 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 (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.

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 (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.
s

Oo

B

tandard 1 oU

Cm

0899-

O 1/2

en

O

aj

Q

E 3

par Inst nolo )urg

a> j= Q na .2

t/5

a 3 z c

a

oo

or) D 1 £

CO

.2 >^ o — £ c o £