MIST

PUBUCATiONS

NIST Special Publication 881-9

4 HIIMlillillilaiakiiiililliltililllillklil II iij;i;i;iitiiiiiiil lilllll I 1

NBT

QC

100

.U57

NO. 881 -9

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 836

Procurement Notices

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology
#he 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 Public Inquiries Desk, 301-975-3058.

Office of the Director

• Advanced Technology Program

• Quality Programs

• International and Academic Affairs

Technology Services

• f\/lanufacturing Extension Partnership

• Standards Services

• Technology Commercialization

• Measurement Services

• Technology Evaluation and Assessment

• Information Services

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability^

• Polymers

• Metallurgy

• Reactor Radiation

Chemical Science and Technology

Laboratory

• Biotechnology

• Chemical Kinetics and Thermodynamics

• Analytical Chemical Research

• Process Measurements

• Surface and Microanalysis Science

• Thermophysics^

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Molecular Physics

• Radiometric Physics

• Quantum Metrology

• Ionizing Radiation

• Time and Frequency^

• Quantum Physics^

Manufacturing Engineering Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Manufacturing Systems Integration

• Fabrication Technology

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields^

• Electromagnetic Technology^

• Optoelectronics^

Building and Fire Research Laboratory

• structures

• Building Materials

• Building Environment

• Fire Safety

• Fire Science

Computer Systems Laboratory

• Office of Enterprise Integration

• Information Systems Engineering

• Systems and Software Technology

• Computer Security

• Systems and Network Architecture

• Advanced Systems

Computing and Applied Mathematics

Laboratory

• Applied and Computational Mathematics^

• Statistical Engineering^

• Scientific Computing Environments^

• Computer Services

• Computer Systems and Communications^

• Information Systems

'At Boulder, CO 80303.

^Some elements at Boulder, CO 80303.
NIST Special Publication 881-9

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 836

Procurement Notices

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

February 1996

U.S. DEPARTMENT OF COMMERCE

Ronald H. Brown, Secretary

Technology Administration

Mary L. Good, Under Secretary for Technology

National Institute of Standards and Technology

Arati Prabhakar, Director
i

I

I

1

Reports on Computer Systems Technology

The National Institute of Standards and Technology {NIST)'s Computer Systems Laboratory (CSL)

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

related telecommunications systems to advance the effective utilization of information technology

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

commerce, CSL 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-9

Natl. Inst. Stand. Technol. Spec. Publ. 881-9, 40 pages (Feb. 1996)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1996

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

In a memorandum of October 26, 1993, the President sought to stimulate the Federal Government's deployment of

Electronic Conunerce in order to simplify and streamline the acquisition process. In this regard, the President set forth the following objectives:

0 Exchange acquisition information electronically between the private sector and the Federal Government to the

maximum extent practicable.

0 Provide businesses, including small, small disadvantaged, and woman-owned businesses, with greater access to Federal acquisition opportunities.

0 Ensure that potential suppliers are provided simplified access to the Federal Government's EC system.

0 Employ nationally and internationally recognized data formats that serve to broaden and ease the interchange of

data.

0 Use agency and industiy systems and networks to enable the govermnent and potential suppliers to exchange

information and access Federal acquisition data.

As part of the Federal Government wide effort to implement EC, NIST has been given the responsibility of coordinating

the development and promulgation of Implementation Conventions for the functional areas of EC which will be deployed

across the Agencies.

Various Agencies have been actively pursuing Electronic Data Interchange (EDI) for several years - the DoD, GSA,

Customs and HHS, for instance, have been particularly active in adopting ANSI XI2 standards, and looking aliead to EDIFACT. There became a danger that with fragmentation of usage across the Federal Government a significant burden

would be placed on many small businesses to support an unnecessary profusion offormats and conventions.

In the Presidential Memorandum, President CUnton required Federal agencies to implement tlie use of electronic commerce in Federal purchases as quickly as possible. As the initial step, the President's Management Council (PMC)

Electronic Commerce Task Force (ECTF), chaired by the Administrator, OfiBce of Federal Procurement Policy (OFPP),

chartered the Federal Electronic Commerce Acquisition Team (ECAT) to complete the first milestone of tlie President's

memorandum. The PMC assigned the Electronic Commerce Acquisition Team, composed of representatives from

various Federal departments and agencies, the task of defining the architecture for the government electronic commerce

acquisition system and identifying the executive departments or agencies responsible for developing, implementing,

operating, and maintaining the Federal electronic system.

Another key step in the implementation of EDI in the Federal Government relies on the definition of

Implementation Conventions (ICs). EDI syntax standards, both ASC X12 and UN/EDIFACT, accommodate a fiill range of business activities for all industries. A standard is the result of a consensus among a large number of

users, each with its own set of needs. It is a superset intended to meet the diverse requirements of all users. Standards commonly contain more data elements and structure options than any one user or industry needs. Far

too many opportunities exist for inefficient, or ambiguous transactions. Therefore, actual EDI business processes

require implementation conventions (ICs) to fully define transactions. ICs do that by tailoring the use of the

standards' segments, data elements, and code values and providing a subset menu of those distinct parts. This

Special Publication defines a Federal IC based on ASC X12 Version 3050 and is the result of coordinated

development and adoption within the Federal Government.
I
836 - Procurement Notices FEDl

836 Procurement Notices

Functional Group ID=rvV^

Introduction:

Tliis 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:

1. This transaction set can be used as an award armouncement. This notification will be publicly available to all interested parties and will provide the name of the party awarded the instrument and the price of the line items

awarded.

2. This transaction set can be used to provide publicly available data (BCOl 1 is code 65) on a single award even if the award was the result of more 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 considered for award; as a postaward notification to unsuccessfiil bidders; as a notice

of intent to award a Small Business Set-Aside; as a notification to late bidders; as a notification of a receipt of a

protest; and as a notification of disposition of an unsolicited proposal.

Pos. Seg. Req. No. ID Name Pes. Max.Use

005 ST Transaction Set Header M 1

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 o 25

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

018 AMT Monetary Amount o >I

020 QTY Quantity o >1

021 DTM Date/Time Reference o >1

Not Used 022 LDT Lead Time o >1

023 PWK Paperwork o >1

024 MSG Message Text o >1

Loop

Repeat

Notes and

Comments

^^^^^^^^

025 Nl Name O 1

026 N2 Additional Name Information O 2

027 N3 Address Information O 2

028 N4 Geographic Location O 1

Not Used 029 REF Reference Numbers O >1

Not Used 030 PER Administrative Communications Contact O >1

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

35FED836 1 October 3, 1995
836 - Procurement Notices FEDl

033 LM

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 DTM

Not Used 103 CTB

104 QTY

103 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

Not Used 181 FOB

Not Used 182 DTM

Not Used 183 LDT

Not Used 184 MSG

185 LM

186 LQ

190 SE

Industry Code

Additional Item Detail

Pricing Information

Product/Item Description

Measurements

Paperwork

Reference Numbers

Administrative Communications Contact

Terms of Sale/Deferred Terms of Sale

Date/Time Reference

Restrictions/ Conditions

Quantity

Monetary Amount

Subline Item Detail

Product/Item Description

O

O

o

o

o

o

o

o

o

o

o

o

o

o

o

1

>1

>1

>1

>1

>1

>1

>1

1

10

1

>1

>1

i

1

>1

Additional Name Information

Address Information

Geographic Location

Reference Numbers

Administrative Communications Contact

F.O.B. Related Instructions

Date/Time Reference

Lead Time

Message Text

1

2

2

1

>1

>1

>1

>1

>1

>1

Industry Code

1

>1

Transaction Set Trailer M

35FED836 2 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

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.

Pes.

» STOl

» STOl

Data

Element

143

329

Name Attributes

M ID 3/3

M AN 4/9

Transaction Set Identifier Code

Code uniquely identifying a Transaction Set. 836 X12.54 Procurement Notices

Transaction Set Control Number

Identifying control number that must be unique within the transaction set functional 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.

35FED836 3 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

BCO Beginning Segment for Procurement Notices

008

Mandatoiy

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

identifying numbers and dates.

2

3

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

BCC)04 is the contract number.

BCO06 is the contract beginning date.

4 BCOO? is the contract expiration date.

Comments:

Ref.

Pes.

» BCOOl

Data

Element

353

BCO02

BCO03

BCO04

Data Element Summary

Name

Transaction Set Purpose Code

Code identifying purpose of transaction set. 00

Attributes

M ID 2/2

35FED836

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.

586 Request for Quote Reference Number O AN 1/45

Number assigned by the purchaser to identify his request for quote.

1. Use to identify the solicitation number (IFB, RFQ, or RFP) that is applicable to the information being provided in the transaction set. When

BCO11 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

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

to the award.

373 Date O DT 6/6

Date (YYMMDD).

Use to identify the date ofthe solicitation cited in BCO02.

Ill 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 PUN ofthe basic instrument/FSS and the Supplementary

Procurement Instrument Identification Number (SPUN).

2. This data element is used only when BCO11 is code 65.

4 October 3, 1995
836 - Procurement Notices FEDl

X BCO05

BCO06

846 Contract Status Code O ID 2/2

Code designating the current status of the contract.

Refer to 003050 Data Element Dictionary for acceptable code values.

373 Date O DT 6/6

Date (YYMMDD).

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

executed.

BCO07

X BCO08

BCO09

BCOlO

» BCOll

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.

Refer to 003050 Data Element Dictionary for acceptable code values.

128 Reference Number Qualifier O ID 2/2

Code qualifying the Reference Number.

TN Transaction Reference Number

Use to indicate a unique reference number assigned to

this transaction set. 127 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.

Transaction Type Code O ID 2/2

Code specifying the type of transaction.

Use to identify the type oftransaction set.

640

62

63

64

65

66

67

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

Use to indicate a notification to unsuccessful offerors

ofthe apparent successful offerorfor a Small Business

Set-Aside in accordance with FAR 15.1001(2). IVhen

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

35FED836 5 Octobers, 1995
836 - Procurement Notices FEDl

Agency, the GAO or the GSBCA in accordance with

FAR 13.103(b)(1). FAR 33.104(a)(2) or FAR

33.105(a)(2)(I) respectively.

69 Bid Rejection Notice

Use to indicate a Rejection Notification 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.

The data element is used only when BCOll is code 70. 7 Request

Use to indicate additional information is requested

before an unsolicited proposal can be processed. 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 reasonsfor 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

rejection.

35FED836 6 October 3. 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

AMT Monetary Amount

018

Optional

>1

To indicate the total monetary amount.

1. Use this l/AMT/018 segment to specify the total amomit of the award instrument.

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

»

»

Ref.

Pes.

AMTOl

AMT02

AMT03

Data Element Summary

Data

Element Name Attributes

522 Amount Qualifier Code M ID 1/2

Code to qualify amount

TK Total Amount of Contract

Use to indicate the total amount ofan award

782 Monetary Amount M R 1/15

Monetary amount.

478 Credit/Debit Flag Code O ID 1/1

Code indicating whether amoimt is a credit or debit

35FED836 7 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

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 of proposals received, if applicable to all of the line items.

2. If there is more than one solicitation applicable to the award, use the 1 /QTY/104

segment to identify the quantity of offerors solicited and the quantities of proposals

received for each line item.

Syntax Notes:

Semantic Notes:

Comments:

»

Ref.

Pes.

QTYOl

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

» QTY02

QTY03

Data

Element

673

380

355

Data Element Summary

Attributes

M ID 2/2

Name

Quantity Qualifler

Code specifying the type of quantify.

87 Quantity Received

Use to indicate the number ofproposals received.

SB Solicited

Use to indicate the number ofofferors solicitedfor

other than EDIpublic solicitations (one-to-all).

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 manner in

which a measurement has been taken

35FED836 8 Octobers, 1995
836 - Procurement Notices FED 1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

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.

»

Ref.

Pes.

DTMOl

Data

Element

374

DTM02

DTM03

DTM04

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.

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 Central Time

ET Eastern Time

GM Greenwich Mean Time

LT Local Time

Use to indicate the time at the receivingfacility.

35FED836 9 Octobers, 1995
836 - Procurement Notices FEDl

X DTM05 624

X DTM06 1250

X DTM07 1251

MT Mountain Time

PT Pacific Time

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.

35FED836 10 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

»

X

X

X

X

X

X

X

Ref.

Pes.

PWKOl

PWK02

PWK03

PWK04

PWK05

PWK06

PWK07

PWK08

C00201

PWK Paperwork

023

Optional

>1

To identify the type and transmission of paperwork or supporting information

When BCOl 1 is code 67, use to identify paperwork that is being provided by the

originator of the transaction set. 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.

Data

Element

755

756

757

98

66

67

352

C002

704

Data Element Summary

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

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

CF Courier

EL Electronically Only

Use to indicate Electronic Data Interchange (EDI).

FX By Fax

Report Copies Needed O NO 1/2

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

Entity Identifier Code O ID 2/2

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

Refer to 003050 Data Element Dictionary for acceptable code values.

Identification Code Qualifier X D) 1/2

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

Code (67).

Refer to 003050 Data Element Dictionary for acceptable code values.

Identification Code X AN 2/20

Code identifying a party or other code.

Description O AN 1/80

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

Actions Indicated O

Actions to be performed on the piece of paperwork identified

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.

35FED836 11 October 3, 1995
836 - Procurement Notices FEDl

Refer to 003050 Data Element Dictionary for acceptable code values.

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.

Refer to 003050 Data Element Dictionary for acceptable code values.

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.

Refer to 003050 Data Element Dictionary for acceptable code values.

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.

Refer to 003050 Data Element Dictionary for acceptable code values.

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.

Refer to 003050 Data Element Dictionaiy for acceptable code values.

35FED836 12 Octobers, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

»

Ref.

Pes.

MSGOl

MSG02

MSG Message Text

024

Optional

>1

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

1. When BC012 is code 7, use this segment to identify the additional information

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

unsolicited proposal is not being processed.

2. Use also when LQ02 in either the l/LQ/034 or l/LQ/186 segment is any code that

requires a more detailed explanation.

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

page, advance a line, etc.

Data Element Summary

Data

Element

933

934

Name Attributes

Free-Form Message Text M AN 1/264

Free-form message text.

Printer Carriage Control Code O ID

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

Refer to 003050 Data Element Dictionary for acceptable code values.

2/2

35FED836 13 October 3, 1995
836 - Procurement Notices FEDl

Segment: Nl Name

Position: 025

Loop: Nl

Level:

Usage: Optional

Max Use: 1 Purpose: To identify a party by type of organization, name and code

Notes: 1. Whenever possible, 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 of the codes listed in N103.

2. When BCOU is code 63, use of this segment is REQUIRED to identify the party

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

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

l/Nl/130 segment to identify the parties.

3. When BCOl 1 is code 64, and the total award is to be made to one small business

entity, use of this segment is REQUIRED to identify that entity. If multiple small

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

entities to be awarded specific line items.

Syntax Notes:

Semantic Notes:

Comments:

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

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 efiicient 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 N105 and N106 further define the type of entity in NlOl.

Data Element Summary

»

Ref.

Pes.

NlOl

Data

Element Name Attributes

98 Entity Identifier Code M ID 2/2

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

21

7Q

BY

PJ

SB

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.

35FED836 14 October 3, 1995
836 - Procurement Notices FEDl

N102

» N103

» N104

X N105

X N106

TO Message To

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

to indicate the party to whom a notification is being

sent. 93 Name X AN 1/35

Free-form name. When BCOU is code 63, 64, or 65, use is REQUIRED to cite the name ofthe

party receiving an award.

66 Identmcation Code Qualifier X ID 1/2

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

Code (67).

While the federal 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 number is preferred over other codes

to identify a namedparty.

10 Department of Defense Activity Address Code

(DODAAC)

Use to indicate a Department ofDefense or Civilian

Agency Activity Address code.

33 Commercial and Government Entity (CAGE)

67 Identification Code X AN 2/20

Code identilying a party or other code.

706 Entity Relationship Code O ID 2/2

Code describing entity relationship.

Refer to 003050 Data Element Dictionary for acceptable code values.

98 Entity Identifier Code O ID 2/2

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

Refer to 003050 Data Element Dictionary for acceptable code values.

35FED836 15 Octobers, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N2 Additional Name Information

026

Nl

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 in

N103/N104

»

Ref.

Pes.

N201

N202

Data

Element

93

93

Data Element Summary

Name

Name

Free-form name. Name

Free-form name.

Attributes

M AN 1/35

O AN 1/35

35FED836 16 Octobers. 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N3 Address Information

027

Nl

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

»

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

35FED836 17 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N4 Geographic Location

028

Nl

Optional

1To specify the geographic place of the named party

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

N103/N104

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 cify name (N401) is in the USA or Canada.

Data Element Summary

X

Ref.

Pes.

N401

N402

N403

N404

N405

N406

Data

Element Name Attributes

19 City Name O AN 2/30

Free-form text for city name.

156 State or Province Code O ID 2/2

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

116 Postal Code O ID 3/11

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States).

26 Country Code O ID 2/3

Code identifying the countiy.

309 Location Qualifier X ID 1/2

Code identifying type of location.

Refer to 003050 Data Element Dictionary for acceptable code values.

310 Location Identifier O AN 1/30

Code which identifies a specific location.

35FED836 18 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

Ref.

Pes.

» LMOl

LM02

LM Code Source Information

033

LM

Optional

1To transmit standard code list identification information

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

proposal is imacceptable or to identify the solicitation method that resulted in an award.

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

LM02 identifies the applicable industry code list source information.

Data Element Summary

Attributes

Data

Element Name

559 Agency Qualifier Code M ID 2/2

Code identifying the agency assigning the code values.

DF Department of Defense (DoD)

822 Source Subqualifier O AN 1/15

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

35FED836 19 Octobers, 1995
836 - Procurement Notices FEDl

Segment: LQ Industry Code

Position: 034

Loop: LM

Level:

Usage: Mandatory

Max Use: >1

Purpose: Code to transmit standard industry codes

Notes: This segment is used only when BCOl 1 is code 62, 63, 65, 69, or 70 and the

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

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

Syntax Notes: 1 If LQOl is present, then LQ02 is required.

Semantic Notes:

Comments:

Data Element Summary

Ref. Data

Pes. Element Name Attributes

LQOl 1270 Code List Qualifier Code O D) 1/3

Code identiiying 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

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

LQ02 1271 Industry Code X AN 1/20

Code indicating a code from a specific industry code list

35FED836 20 October 3. 1995
836 - Procurement Notices FED 1

Segment: POl Baseline Item Data

Position: 035

Loop: POl

Level:

Usage: Optional

Max Use: 1 Purpose: To specify basic and most frequently used line item data

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

when BCOl 1 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 considered for award.

3. When BCOl 1 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 BCOl 1 is code 69, use this loop to identify those line items that are being

rejected on an individual bid.

Syntax Notes:

Semantic Notes:

Comments:

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

1 If PO103 is present, then PO102 is required.

2 If PO105 is present, then PO104 is required.

3 If either PO106 or PO107 is present, then the other is required.

4 If either PO108 or PO109 is present, then the other is required.

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

6 If either PO1 1 2 or PO1 1 3 is present, then the other is required.

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

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

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

10 If either PO120 or P0121 is present, then the other is required.

11 If either P0122 or P0123 is present, then the other is required.

12 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 PO101 is the line item identification

3 PO106 through P0125 provide for ten (10) different product/sendee ID's per each

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

SKU.

Data Element Summary

»

Ref.

Des.

POlOl

PO102

PO103

Data

Element

350

330

355

Name Attributes

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.

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.

Unit or Basis for Measurement Code O ID 2/2

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

which a measurement has been taken

35FED836 21 Octobers, 1995
836 - Procurement Notices FEDl

I. Use any code.

PO104

PO105

» PO106

» PO107

PO108

PO109

POllO

POlll

P0112

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

Refer to 003050 Data Element Dictionary for acceptable code values.

212 Unit Price X R 1/17

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

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

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

639 Basis of Unit Price Code O ID 2/2

Code identifying the type of unit price for an item.

ES Estimated

FB Fabrication Cost

Use to indicate the price includes the incorporation of

GFE, GEM, or GFP.

KA Price witli Government Furnished Property

Use to indicate the price ofthe items includes the use ofGFP, GFE, or GEM to manufacture the item.

NC No Charge

NE Not to Exceed

NS Not Separately Priced

Use to indicate the item is not separately priced but is included in the price ofthe item to which it pertains.

When used, cite the number "0" in POI04.

TB To be negotiated.

235 Product/Service D) Qualifier X ID 2/2

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

Product/Service ID (234).

1. Use any code.

2. When BCOIl is code 63 or 65, as a minimum, there must be one occurrence ofa 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.

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.

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

35FED836 22 October 3, 1995
836 - Procurement Notices FEDl

Refer to 003050 Data Element Dictionary for acceptable code values.

P0113 234 Product/Service ID X AN 1/40

Identifying nimiber for a product or service.

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

35FED836 23 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

CTP Pricing Information

050

POl

Optional

>1

To specify pricing information.

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

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

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

12

3

4

1

2

1

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

If CTP06 is present, then CTP07 is required.

If CTP09 is present, then CTP02 is required.

If CTPIO is present, then CTP02 is required.

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.

CTP08 is the rebate amount.

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.

Ref.

Pes.

CTPOl

CTP02

Data

Element

687

236

Attributes

O ID 2/2

CTP03

CTP04

Data Element Summary

Name

Class of Trade Code

Code indicating class of trade.

Refer to 003050 Data Element Dictionary for acceptable code values.

Price Identifier Code X ID 3/3

Code identifying pricing specification.

Use to identify various prices applicable to the line item.

ICL Unit Price Through Quantity

When citing pricesfor a quantity range, use to indicate

the end ofthe range.

MAX Maximum Order Quantity Price

When citing pricesfor a quantity range, use to indicate

the quantity above which the price does not change.

PAP Protection Level Price

Use to indicate the pricefor the packaging protection

level (preservation) cited in CTPIO.

PBQ Unit Price Begiiming Quantity

When citing pricesfor a quantity range, use to indicate

the beginning ofthe range.

PPA Packing Level Price

Use to indicate the price for the packing level cited in

CTPIO.

ZNP Zone Price

Use to indicate the price for the delivery zone cited in

CTPIO.

O R 1/17

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

212 Unit Price

380

35FED836 24 October 3, 1995
836 - Procurement Notices FEDl

X

X

X

CTP05

CTP06

CTP07

CTP08

CTP09

CTPIO

355

648

649

782

639

499

Numeric value of quantity.

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.

Refer to 003050 Data Element Dictionary for acceptable code values.

Price Multiplier Qualifier O ID 3/3

Code indicating the type of price multiplier.

Refer to 003050 Data Element Dictionary for acceptable code values.

O R

O ID

Multiplier 1/10

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

Monetary Amount

Monetary amount.

Basis of Unit Price Code

Code identifying the type of unit price for an item.

Refer to 003050 Data Element Dictionary for acceptable code values.

Condition Value O AN

Identifies rate restrictions or provisions

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

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

1/15

2/2

1/10

35FED836 25 October 3, 1995
836 - Procurement Notices FEDl

Segment: REF Reference Numbers

Position: 090

Loop: POl

Level:

Usage: Optional

Max Use: >1

Purpose: To specify identifying numbers.

Notes: 1. Use this l/REF/090 segment when the solicitation varies by awarded line item.

When the solicitation is the same for all of the awarded line items, cite the solicitation

number in BCO02.

Syntax Notes:

Semantic Notes:

Comments:

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

result of more than one solicitation.

1 At least one of REF02 or REF03 is required.

Ref.

Pes.

» REFOl

X

REF02

REF03

Data

Element

128

127

352

Data Element Summary

Name

Reference Number Qualifier

Code qualifying the Reference Niunber.

KS Solicitation

Attributes

M ED 2/2

A discreet number assigned by the purchasing activity

to differentiate between different solicitations

Use to indicate the solicitation (IFB, RFP, 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.

35FED836 26 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

DTM Date/Time Reference

102

POl

Optional

10

To specify pertinent dates and times

1. Use this l/DTM/102 segment to identify the date of the solicitation cited in

REFOl/02.

Syntax Notes:

Semantic Notes:

Comments:

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

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

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

»

X

X

X

Ref.

Pes.

DTMOl

Data

Element

374

DTM02

DTM03

373

337

DTM04 623

DTM05

DTM06

DTM07

624

1250

1251

Data Element Summary

Name

Date/Time Qualifier

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

Attributes

M ID 3/3

642

Date

Date (YYMMDD)

Time

Solicitation

Use to indicate the date ofthe solicitation.

X DT 6/6

X TM 4/8

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

S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

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

in hours in relation to Universal Time Coordinate (UTC) time. Since + is a

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

Refer to 003050 Data Element Dictionary for acceptable code values.

Century O NO 2/2

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

Date Time Period Format Qualifier X ED 2/3

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

Refer to 003050 Data Element Dictionary for acceptable code values.

Date Time Period X AN 1/35

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

35FED836 27 Octobers. 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

QTY Quantity

104

POl

Optional

>1

To specify quantity Information.

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

number of proposals received for the line item cited in POIOI.

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

»

Ref.

Pes.

QTYOl

» QTY02

QTY03

Data

Element

673

380

355

Attributes

M ID 2/2

Data Element Summary

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 (one-to-all).

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 manner in

which a measurement has been taken

Refer to 003050 Data Element Dictionary for acceptable code values.

35FED836 28 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

AMT Monetary Amount

105

POl

Optional

>1

To indicate the total monetary amount.

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

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

Data Element Summary

»

»

Ref.

Pes.

AMTOl

AMT02

AMT03

Data

Element

522

782

478

Name

M R

Amount Qualifier Code

Code to qualify amount

1 Line Item Total

Monetary Amount

Monetary amount.

Credit/Debit Flag Code

Code indicating whether amoimt is a credit or debit

Refer to 003050 Data Element Dictionary for acceptable code values.

Attributes

M ID 1/2

1/15

O ID 1/1

35FED836 29 October 3, 1995
836 - Procurement Notices FEDl

Segment: Name

Position: 130

Loop: Nl

Level:

Usage: Optional

Max Use: 1 Purpose: To identify a party by type of organization, name and code

Notes: 1. Use this segment only when BCOl 1 is code 63 and the line items in a solicitation were awarded to different parties or code 64 and the apparent small business successful

offeror is different for each line item.

2. Use of this segment is REQUIRED for the conditions stated in note 1.

3. Whenever possible, 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 of the codes listed in N103.

Syntax Notes:

Semantic Notes:

Comments:

1 At least one of N102 or N103 is required.

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

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

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

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

2 N105 and N106 further define the type of entity in NlOl.

Ref.

Pes.

» NlOl

Data

Element

98

»

»

N102

N103

93

66

» N104

N105

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

SE

Small Business

Use to indicate the apparent small business successful

offerorfor the line item.

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 designating the system/method of code structure used for Identification

Code (67).

While the federal 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

33

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

Use ofthe DUNS number is preferred over other codes

to identify a namedparty.

Commercial and Government Entity (CAGE)

Identification Code X AN 2/20

Code identifying a party or other code.

Entity Relationship Code

Code describing entity relationship.

Refer to 003050 Data Element Dictionary for acceptable code values.

O ID 2/2

35FED836 30 October 3, 1995
836 - Procurement Notices FED 1

X N106 98 Entity Identifier Code O ID 2/2

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

Refer to 003050 Data Element Dictionary for acceptable code values.

35FED836 31 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N2 Additional Name Information

140

Nl

Optional

2

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

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

Data Element Summary

»

Ref.

Pes.

N201

N202

Data

Element

93

93

Name

Name

Free-form name. Name

Free-form name.

Attributes

M AN 1/35

O AN 1/35

35FED836 32 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N3 Address Information

150

Nl

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.

»

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

35FED836 33 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N4 Geographic Location

160

Nl

Optional

1To specify the geographic place of the named party

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

N103/N104.

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 US or Canada.

Data Element Summary

Ref.

Pes.

N401

N402

N403

N404

N405

N406

Data

Element

19

156

Name

116

26

309

310

Attributes

City Name O AN 2/30

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 Qualifler X ID 1/2

Code identifying type of location.

Refer to 003050 Data Element Dictionary for acceptable code values.

Location Identifier O AN 1/30

Code which identifies a specific location.

35FED836 34 October 3, 1995
836 - Procurement Notices FEDl

Segment: LM Code Source Information

Position: 185

Loop: LM

Level:

Usage: Optional

Max Use: 1 Purpose: To transmit standard code list identification information

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

item in the proposal is no longer being considered for award; why the proposal for the

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

method applicable to the line item.

2. This segment is used only when BCOl 1 is code 62, 63, 65, or 69.

Syntax Notes:

Semantic Notes:

Comments:

»

Ref.

Pes.

LMOl

LM02

LM02 identifies the applicable industry code list source information.

Data Element Summary

Attributes

M ID 2/2

Data

Element Name

559 Agency Qualifier Code

Code identifying the agency assigning the code values.

DF Department of Defense (DoD)

822 Source Subqualifier O AN 1/15

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

35FED836 35 October 3, 1995
836 - Procurement Notices FEDl

Segment: LQ Industry Code

Position: 186

Loop: LM

Level:

Usage: Mandatory

Max Use: >1

Purpose: Code to transmit standard industry codes

Notes: Tliis segment is used only when BCOl 1 is code 62, 63, 65, or 69, and the information

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

l/LQ/034 segment.

Syntax Notes: 1 If LQOl is present, then LQ02 is required.

Semantic Notes:

Comments:

Data Element Summary

Ref. Data

Des. Element Name Attributes

LQOl 1270 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

When BCOlI 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, use to indicate the method by

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

solicitation, sole source, bulletin board, etc. LQ02 1271 Industry Code X AN 1/20

Code indicating a code from a specific industry code list

35FED836 36 October 3, 1995
836 - Procurement Notices FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

»

»

Ref.

Pes.

SEOl

SE02

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

SE is the last segment of each transaction set.

Data Element Summary

Data

Element

96

329

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.

35FED836 37 Octobers, 1995



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

<uE . oo E ^ o1

of

Co

Standa

-6680

$300

c

o

Q

D

E

"3 ate <Uc >

epar 1

Insti

hnolo sburg

Busi

for

Pri

Q ? O w. .2 >»

.S. atio!

H SI

G

c

ffi

Pena

S z § O

O