dod electronic data interchange (edi) convention dtic · application advice transaction set (824)...

AD-A263 404

Department"jiof

Defense

DoDElectronic Data

Interchange (EDI)ConventionASC X 12 Transaction Set 836Contract Award(Version 003010)

DTICDL203LN14 fl EL E C TE

APR2 & 1993 11E

January 1993

_&I ____________ublic____93-08759

BASELINE AS OF: JANUARY 29,1993 111111139° " " •4

DEPARTMENT OF DEFENSE CONTRACT AWARDDRAFT IMPLEMENTATION CONVENTION 836.003010DoD_

DraftDepartmentofDefense

DoDAccesion For

NTIS CRýA&IDTIC TAB Electronic DataU, announcedJustification ................................ In te rc h a n g e (E D I)By......

______ ConventioAvailability Codes Convention

Avail and/orDist Special ASC X 12 Transaction Set 836

'( IContract Award(Version 003010)

This docunwnt was prepared by the Logstist Management Institute for the Defense Logistic Agency underTask DL2U . The task was performed under Contract MDA903-90-C-0006 with the Department of Defense.Perrimluon to quote or reproduce any part of this document except for Government pu rpoes must beobtained rorn the Department of Defense Executive Agent for Electronic Comrnmerce/Electronic DataInterchange/Protection of Logistc Ulndassified/Sensitive Systenum

Executive Agent for EC/EDI/PLUS

Defense Logistics AgencyCameron StationAlexandria, VA 22304-6100

BASELINE AS OF: JANUARY 29,1993

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION CONVENTION

TABLE OF CONTENTS

1.0 INTRODUCTION ..................... 1.01

1.1 PURPOSE OF THE CONVENTION .... 1.0.1

1.2 SCOPE ..................... 1.0.1

1.3 RESPONSIBLE ENTITY ........... 1.0.1

1.4 HOW TO USE THE IMPLEMENTATIONCONVENTION ................... 1.0.2

1.4.1 Conventions, Standards, and Guidelines . . 1.0.21.4.2Documentation of Conventions ........ 1.0.3

2.0 MAINTENANCE ..................... 2.01

2.1 MANTAINING CONVENTIONS ...... 2.0.1

2.2 VERSION/RELEASE TIMING ........ 2.0.1

3.0 DoD CONVENTIONS FOR USING ASC X12TRANSACTION SETS 3.01

3.1 INTRODUCTION ................ 3.0.1

3.2 CONTROL SEGMENTS ............ 3.0.1

3.2.1Description of Use ................ 3.0.23.2.2Conu!o Segment Specifications ....... 3.0.5

3.3 EXAMPLE OF CONVENTION USE .... 3.0.15

3.4 DoD CONVENTION ............. 3.0.19

4.0 ASC X 12 FORMS .................... 4.01

5.0 GLOSSARY ......................... 5.01

5.1 X12 GLOSSARY ................ 5.0.1

5.2 DoD GLOSSARY ................ 5.0.6

SASEUNE AS OF: JANUARY 29,1993

I I I I I


iv BASEUNE AS OF: JANUARY 29,1993


1.0 INTRODUCTION

This chapter explains the purpose of the convention, the scope ofthe guidance, and provides an explanation of how to use theconvention.

1.1 PURPOSE OF THE CONVENTIONThe convention provides general guidance on the implementationof American National Standards Institute (ANSI) Accredited Stand-ards Committee (ASC) X12 electronic data interchange (EDI)standards within automated information systems (AIS) and infor-mation interchange procedures that require the collection, report-ing, and/or exchange of data needed to perform defense missions.

1.2 SCOPEThe guidance is provided for two components. First, it may beused by organizational elements of the DoD community. It mayalso be useful to organizations external to DoD that exchange datawith the DoD community in the course of their business relation-ships.

The DoD community encompasses the Military Services, Organiza-tions of the Joint Chiefs of Staff, Unified and Specified Commands,Office of the Secretary of Defense, and the Defense agencies. (Thatcommunity is collectively referred to as the DoD Components.)

Organizational entities external to DoD include (a) non-Govern-ment organizations, both commercial and nonprofit; (b) Federalagencies of the United States Government other than DoD;(c) local and state governments; (d) foreign national governments;and (e) international government organizations.

The draft convention published in this document is for trial useand comment. DoD Components must submit to the DoD EDIExecutive Agent (EA) their data requirements that are not coveredin the conventions as soon as possible, as indicated in Chapter 2.0,Section 2.1.

1.3 RESPONSIBLE ENTITYThe Defense Logistics Agency (DLA) is DoD's Executive Agentfor implementing and maintaining Defense-wide programs for(a) EDI in accordance with DepSecDef memorandum of May 24,1988, Subject: Electronic Data Interchange of Business-RelatedTransactions; and (b) Protection of Logistics Unclassified/Sensi-tive Systems (PLUS) in accordance with Assistant Secretary ofDefense (Production and Logistics) [ASD(P&L)] memorandum ofNovember 21, 1989, Subject: Production and Logistics TaskGroup for Data Protection. Publication of these conventions isbased upon this authority. See Chapter 2.0 Maintenance, Section 2.1for office point of contact.

BASEUNE AS OF: JANUARY 29,1993 1.0.1


1.4 HOW TO USE THE IMPLEMENTATIONCONVENTIONThe main topics and structures of this document conform to theEDI Implementation Reference Manual Guidelines document thatwas developed by a task group of the subcommittee on educationand implementation of the ASC X12. The purpose of havingagreed-upon topics and structure is to facilitate reference by themany industry and DoD personnel who are involved in implement-ing the uniform standards for electronic interchange of businesstransactions.

1.4.1 Conventions, Standards, and GuidelinesThe terms conventions, standards, and guidelines are usedthroughout the document and are defined as follows:

* Conventions are the common practices and/or interpretationsof the use of ASC X12 standards. Conventions define what isincluded in a specific implementation of an ASC X12 standard.

. Standards are the technical documentation approved byASC X12; specifically, transaction sets, segments, data ele-ments, code sets, and interchange control structure. Standardsprovide the structure for each ASC X12 document.

* Guidelines are instructions on the use of EDI. They provideadditional information to assist in conducting EDI. Guidelinesare intended to provide assistance and should not be your solesource of information.

1.4.1.1 Who Develops the Conventions?Conventions result from a joint effort between business, technical,and EDT ASC X12 standards experts. The business data require-ment is defined, a transaction set is selected, and the data require-ment is then identified with data elements in the transaction set.A convention is usually developed before any computer ED! sys-tems development work and serves as a design document when thedevelopment process begins.

1.4.1.2 Why Use a Convention?To create an ASC X12 transaction, a user must know the datarequirements, understand the ASC X12 standard, and be able touse that information to develop an interface program between thecomputer application and the ASC X12 translator. The necessaryinformation to perform this task is contained in the conventiondocument. Users who follow the convention will create a transac-tion set that all DoD users understand.

1.4.1.3 Who Needs a Convention?System analysts and application programmers who plan to createor read ASC X12 transactions use a convention to aid in interfacesoftware design. The convention will help the programmer andanalyst identify where their application data requirement should becarried in an ASC X12 transaction set.

1.0.2 BASEUNE AS OF: JANUARY 29,1993


1.4.4.4 Can I Develop a Convention?Conventions already exist for some of the most common businesspractices. Copies of existing conventions can be acquired throughyour organization's EDI coordinator at the start of an EDI project.If you find no conventions for the business practice you are aboutto implement, your EDI coordinator should contact the DoD Ex-ecutive Agent for EDI. See Chapter 2.0, Maintenance, Section 2.1for the point of contact.

1.4.2 Documentation of ConventionsConventions are adopted from, and are intended to be in confor-mance with, ANSI ASC X12 standards or ASC X12 Draft Stand-ards for Trial Use (DSTU).

1.4.2.1 Transaction SetFigure 1.4-1 provides an example of a transaction set table. Thetransaction set defines information of business or strategic sig-nificance and consists of a transaction set header segment, one ormore data segments in a specified order, and a transaction settrailer segment. The actual ASC X12 standard as it appears in theofficial ASC X12 standards manual is presented on the right sideof the page. This standard also includes both syntax notes andcomments. The specific DoD usage designator is presented on theleft side of the page.

The designation "N/U" appears in the left column if DoD does notuse the specific segment. A page number will appear if the segmentis used.

1.4.2.2 Transaction Set SegmentFigure 1.4-2 is an example of a transaction set segment.

DoD usage is specified on the left side of the page. For identifier(ID) - type data elements, acceptable code values are listed onthe right side of the page under the definitions of the element.

DoD notes, reflecting how the convention is to be used appear onthe right side of the page at the segment level or the data elementlevel.

The following definitions are for use in interpreting the dataelement requirement designators in the DoD-specific segmentdirectory section of the convention. For ASC X12 usage, see thedefinitions in X12.6 Application Control Structure.

* MandatoryMandatory data elements are defined by ASC X12.

OptionalOptional data elements are used at the discretion of the sendingparty or are based upon mutual agreement between tradingpartners.


DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION4 CONVENTION

DEPARTBENT OF DEFESEDRAFT WLEMWETATION CONVENTION

$24. APPULCATION ADVICE ANSI ASC X12 VERSlOMRELEIA E 003010000

824 Application AdviceThis standard provides the format and establishes the data contents of theApplication Advice Transaction Set (824) within the context of an ElectronicData Interchange (EDI) environment. This transaction set provides the abilityto report the results of an application system's data content edits oftransaction sets. The results of editing transaction sets can be reported at thefunctional group and transaction set level. in either coded or tree-form format.It is designed to accomodate the business need at reporting the acceptance,rejection or acceptance with change of any transaction set. The ApplicationAdvice should rnot be used in place of a transaction set designed as aspecific response to another transaction set (e.g., purchase orderacknowledgementl sent in response to a purchase order).

Table 1PhaEN PC a 2"W "M OKAl oft " Mi 1 LOOP awIA?

2 010 ST Transaction Set Header M 13 020 SON Begmnring Segment: M I

LOOPID tI 24 030 Ni Name 0 15 040 N2 Additional Name Information 0 26 050 N3 Address Information 0 27 060 N4 Geographic Location 0 18 070 REF Reference Numbers 0 129 060 PER Administrativa Communicatioins Contact 0 3

Table 2PW 8 ft SOS. 10. MAIN am 02L. "X oft LOOP A1

LOOPUD-@T 1010 010 OTI Origmal Transactlon Identification M12 020 REF Reference Numbers 0 1213 030 0711 Date/Tkme Ref erence 0 2N/U 040 PER Adrministrative, Commuvnications Contact 0 3N/U 050 AMT Monetary Amount 0 10N/U 060 OTY Quantit 0 10

LOOP WD-720 1000014 070 TED Technical Error Description 0 115 060 NT! Note/Special Instructin 0 10016 090 SE Transaction Set Trailer M I

1 DA41 -JANUARY 21 IM

Figure 1.4-1 Example of a Transaction Set Table

1.0.4BASELINE AS OF: JANUARY 20,1M

DEPARWMN' OF DWEESEDRAFT UIPLEMENTAWION COWENITION

DEPARTUBIT OF DEFENSEDRAFT IMPLEUEKCTATIO#4 CONVENIfON4

524.- APPUCATIONd ADVICESGN - BEGINNIN4G SEGMENT ANSI ASC X12 VERSIONRELEASE 00301 0000

Segment: BGN Beginning Segw.. itLevel: Header

Loop:-Mande, Usage: Mandatory

Max Use: 1Purpose: To indicate the beginning of a transaction set.

Syntax: if BGN05 is used, BGNO4 is required.

Comments: 1. BGN02 is the Transaction Set Reference Numbqr.

2. BGN03 is the Transaction Set Date.3. BGN04 is the Transaction Set rime.

4. BGN05 is the transaction set time qualifier.

Data Element Summary

Mandeir 301401 353 Transaction Set Purfpoee Code M ID 212Code identifying purpose of transaction set.

00 Original01 Cancellation04 Change12 Not Procemsed

UMdmtmy 301402 127 Rebernce Number M AN 1130Reference number or identification number asdefined for a partkiculrTransaction Set, er as specified by the Reference Number Oualimer.

UWMaaaWY 30INW3273 DaOe N DT 615Dafts (YYMMOO).

C01041110011 301404 237 Time C TM 414Time expreasse in 244tour clock ftim (1*4MM, time range. 0000 though 2359).

h'psettlon Note:UseRHHM.

Not Used s0aw0 a23 Time Code 0 ID 2f2

3 DI-JMR 9I

Figure 1.4-2 Example of a Tuansaction Set Segment

SASELME AS OF: JANUARY 23, IMU 1A


"• Required

Required data elements are considered optional underASC X12 rules, but are required by DoD decision.

" RecommendedRecommended data elements are considered optional underASC X12 rules and by the DoD, but the industry recommendstheir use to facilitate EDI. Most companies in the industryare expected to use this data element.

"* Not Used"Not Used" data elements are those that the DoD does notuse.

* ConditionalConditional data elements depend on the presence of other data

elements in the transaction set.


DEPARTMENT OF DEFENSE

DRAFT IMPLEMENTATION CONVENTION

2.0 MAINTENANCE

This chapter describes the procedures for maintaining the DoDconventions. It also presents a section on version/release timiIg.

2.1 MAINTAINING CONVENTIONSThe DLA, as DoD's Executive Agent for EDI and PLUS, hasestablished a joint program office to oversee implementation ofEDI. Some of the functions of this program office are to maintainconfiguration control of related standards and common supportpackages (e.g., versions of ASC X12 standards and PLUS algo-rithms employed), participate in the standards-setting process, andensure compliance with approved EDI standards.

To accomplish these functions, the joint program office has estab-lished a conventions and standards development and maintenanceprocess whose objectives are: (1) to obtain ASC X12 data require-ments from the DoD Components and present the requirements tothe ASC X12 for consideration as ANSI standards, and (2) todevelop and maintain conventions for use by DoD Componentsand their potential trading partners.

To take advantage of, and not duplicate, existing data stan-dardization processes, the EA has established focal pointswithin the ASD Offices, the Military Services, and the DefenseAgencies from which EDI information is obtained and dissemi-nated.

The EA's primary source of information about DoD's data require-ments is the EDI User.

Changes to this publication and recommended changes to ANSIASC X12 should be forwarded through your organizational pointof contact for data standardization to:

EDI Standards CoordinatorATIN: DLA-ZCCameron StationAlexandria, VA 22304-6100

See Chapter 4 for reproducible ASC Xi2 Work Request forms.

2.2 VERSION/RELEASE TIMINGIdentification of the official "version" of a standard is critical tothe successful interchange of information. Each participant mustbe able to send and receive the same version to ensure the accuracyof the information exchanged.

The version is transmitted as a 12-character code in the FunctionalGroup Header segment (GS) in Data Element #480, Ver-sion/Release/lndustry ID. This 12-character code is used byASC X12 as follows:

BASELINE AS OF: JANUARY 29,1M3 2.0.1


DRAFT IMPLILMENT.TION CONVENTION

Position onen

1-3 Version number4-5 Release level of version

6 Subrelease7-12 DoD/Industry or Trade Association ID

ASC X12 assigns the codes in positions I through 6.

A major version (1-3) will change only after an official publicreview cycle, leading to republication of a new American NationalStandard.

Release. level of each new major version (4-6) will begin at "000"and incremented by 1 for each iew ASC X12 approved publicationcycle, usually once a year. The fifth character designates therelease and the sixth character designates the subrelease.

DoD/Industry/Trade Association ID (7-12) is used to identifyconventions. For this suffix, DoD will use "DoD_" with the 10thcharacter identifying successive publications. The 1lth and 12thcharacters may be used by the Military Departments or DefenseAgencies.

DoD conventions for using ASC X12 standards are publishedannually. Conventions developed for each release will be main-tained for 4 years. Military Services and DoD Agencies willdetermine which release to use on the basis of business need butwill not use any release more than 4 years old without approvalof the DoD EA.



836. CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD_

3.0 DoD CONVENTIONS FOR USINGASC X12 TRANSACTION SETS

This chapter defines the DoD transaction set conventions. Itincludes the instructions for implementing the control structure anddefinitions of the usage indicators and applicable codes.

3.1 INTRODUCTIONThe power of the ASC X12 standard is in its building blockconcept, which standardizes the essential elements of businesstransactions. It is analogous to a "standard bill of materials andthe construction specifications," which gives the architectflexibility in what can be designed with standardized materials andprocedures. The EDI system designer, like the architect, uses theASC X12 standards to build business transactions that are oftendifferent because of their function and yet utilize the ASC X12standards. The "bill of materials and the construction specification"of ASC X12 are the standards found in the published technicaldocumentation.

ASC X12.3 - The Data Element Dictionary specifies the dataelements used in the construction of the segments that comprisethe transaction sets developed by ASC X12.

ASC X12.5 - The Interchange Control Structure provides theinterchange control segment (also called an envelope) of a headerand trailer for the electronic interchange through a data transmis-sion; it also provide a structure to acknowledge the receipt andprocessing of the envelope.

ASC X12.6 - The Application Control Structure defines the basiccontrol structures, syntax rules, and semantics of EDI.

ASC X12.22 - The Data Segment Directory provides the defini-tions and specifications of the segments used in the constructionof transaction sets developed by ASC X12.

The DoD convention in Section 3.4 conform to the above standardsand each transaction set is a complete document to the extentpossible. For further clarification of acronyms, abbreviations, andcodes, refer to ASC X12 published technical documentation. Con-tact the DoD EDI Executive Agent for copies or the Data Inter-change Standards Association, Inc., Suite 355, 1800 DiagonalRoad, Alexandria, VA 22314.

3.2 CONTROL SEGMENTSIn addition to the communication control structure, the EDI structureprovides the standards user with multiple levels of control to ensuredata integrity. It does so by using header and trailer control segments

BASELINE AS OF: JANUARY 29,1993 3.0.1


836 - CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD_

designed to identify uniquely the start and end of the interchangefunctional groups and transaction sets. The relationship of thesecontrol segments is shown in Figure 3.2-1. Control Segmentspecifications are defined in Section 3.2.2.

3.2.1 Description of UseThe interchange header and trailer segments surround one or morefunctional groups or interchange-related control segments and per-form the following functions:

"* Define the data element separators and data segment ter-minators

"* Identify the sender and receiver

"* Provide control information

"* Allow for authorization and security information.

The Interchange Acknolwedgment Segment is used to acknowledgeone interchange header and trailer envelope where the envelopesurrounds one or more functional groups. (No acknowledgment ismade for the interchange acknowledgment.)

The interchange control number value in the acknowledgment(TAI segment) is the same as that for the ISA segment that isbeing acknowledged. The control number serves as a link betweenthe interchange header and trailer and the acknowledgment of thatheader and trailer.

The interchange acknowledgment does not report any status on thefunctional groups contained in the interchange and is separatefrom the communication system's error procedures.

The preparer of the interchange header and trailer indicates thelevel of acknowledgment in Data Element 113, AcknowledgmentRequested. If an acknowledgment is requested, then the recipientmust return an acknowledgment. If not requested, none should begiven.

The interchange acknowledgment control segments are placed afterthe interchange header and before the first functional group orbefore the interchange trailer if there are no functional groups.

Control segments are standard for all implementation conventionsproduced for the Department of Defense. Some codes associatedwith individual data elements within the control segments areunique to the individual transaction set. Others, identify the ANSIversion and release in which the convention is written.



636 • CONTRACT AWARD ANSI ASC X12 VERSIONIRELEASE 003010DOD

/Communications Transport ProtocolISA /interchange control Header

GS // Functional Group Header

ST / -Transaction Set HeaderDetail Segments I

(e.g., Purchase Order) I

SE X Transaction Set Trailer 0

ST Transaction Set Header _n

Detail Segments , %(e.g.. Purchase Order) C

SE \ Transaction Set Trailer _

GE Functional Group Trailer 2E

GS Functional Group Header -

ST Transaction Set Header

__ _ _ _ __ _ _ _ _ IDetail Segments(e.g., Receiving Acdvice)

SE Transaction Set Trailer

GE Functional Group Trailer

lEA Interchange Control Trailer

Communications Transport Protocol

Figure 3.2-1. Hierarchical Structure

BASELINE AS OF: JANUARY 29, IMP 3.0.3


836 • CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD_



836 CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 093010DOD

3.2.2 Control Segment Specifications



836 • CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD

3.0.8 BASELINE AS OF: JANUARY 29, 1993


001 - CONTROL SEGMENTS 836 CONTRACT AWARDISA INTERCHANGE CONTROL HEADER ANSI ASC X12 VERSION/RELEASE 003010DOD

segment: ISA Interchange Control HeaderPurpose: To start and identify an interchange of one or more functional groups

and interchange-related control segments.

Data Element SummaryREF. DATADES. ELENT NAME ATT"•UTES

Mandatory ISA01 101 Authorization Information Qualifier M ID 2/2Code to identify the type of information in the Authorization Information.

00 No Authorization Information Present (No Meaningful Information in 102)

Mandatory ISA02 102 Authorization Information M AN 10/10Information used for additional identification or authorization of the sender or thedata in the interchange. The type of information is set by the AuthorizationInformation Qualifier.

Implementation Note:If no authorization information is agreed to by trading partners, fill field with blanks.

Mandatory ISA03 103 Security Information Qualifier M ID 2/2Code to identify the type of information in the Security Information.

01 Password

Mandatory ISA04 104 Security Information M AN 10/10This is used for identifying the security information about the sender or the datain the interchange. The type of information is set by the Security InformationQualifier.

Implementation Note:An agreed upon password. If no security information is agreed to by trading partners,fillfield with blanks.

Mandatory ISA05 105 Interchange ID Qualifier M ID 2/2Qualifier to designate the system/method of code structure used to designate thesender or receiver ID element being qualified.

ZZ Mutually DefinedCode Value Implementation Note:An agreed upon designation of DoD Activity Address Code (DoDAAC) or other code coordinatedwith the value-added network (VAN).

Mandatory ISA06 106 Interc.ange Sender ID M ID 15/15Identification code published by the sender for other parties to use as thereceiver ID to route data to them. The sender always codes this number in thesender ID element.

Implementation Note:DoD activities use Department of Defense Activity Address Code (DoDAAC) or other code coordinated withthe value-added network (VAN). Non-DoD activities use identification code qualified by ISA05 andcoordinated with the VAN.

Mandatory ISA07 105 Interchange ID Qualifier M ID 2t2Qualifier to designate the system/method of code structure used to designate thesender or receiver ID element being qualified.

7Z Mutually Defined

BASEUNE AS OF: JANUARY 29,1993 DI103 3.0.7


836 CONTRACT AWARD 001 - CONTROL SEGMENTSANSI ASC X12 VERSION/RELEASE 003010DOD ISA - INTERCHANGE CONTROL HEADER

Code Value Implementation Note:An agreed upon designation of DoD Activity Address Code (DoDAAC) or other code coordinatedwith the value-added network (VAN).

Mandatory ISA08 107 Interchange Receiver ID M ID 15/15Identification code published by the receiver of the data. When sending, it isused by the sender as their sending ID, thus other parties sending to them willuse this as a receiving ID to route data to them.

Implementation Note:DoD activities use Department of Defense Activity Address Code (DoDAAC) or other code coordinated withthe value-added network (VAN). Non-DoD activities use identification code qualified by ISA05 andcoordinated with the VAN.

Mandatory ISA09 108 Interchange Date M DT 6/6Date of the interchange.

Implementation Note:Assigned by translation software. YYMMDD

Mandatory ISA10 109 Interchange Time M TM 4/4Time of the interchange.

Implementation Note:Assigned by translation software. HHMM

Mandatory ISAll 110 Interchange Control Standards Identifier M ID 1/1Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailer.

U U.S. EDI Community of ASC X1 2, TDCC, and UCS

Mandatory ISA12 Ill Interchange Control Version Number M ID 5/5This version number covers the interchange control segments and the functionalgroup control segments.

00301 Draft Standard for Trial Use Approved for Publication by ASC X1 2 ProceduresReview Board Through October 1990

Code Value Implementation Note:Version ID as defined or agreed upon by the trading partners.

Mandatory ISA13 112 Interchange Control Number M NO 9/9This number uniquely identifies the interchange data to the sender. It is assignedby the sender. Together with the sender ID it uniquely identifies the interchange

data to the receiver. It is suggested that the sender, receiver, and all third partiesbe able to maintain an audit trail of interchanges using this number.

Mandatory ISA14 113 Acknowledgment Requested M ID 1/1Code sent by the sender to request an interchange acknowledgment.

0 No Acknowledgment Requested

1 Interchange Acknowledgment Requested

Mandatory ISA15 114 Test Indicator M ID 1/1Code to indicate whether data enclosed by this interchange envelope is test orproduction.

P Production Data

T Test Data

3.0.0 BASEUNE AS OF: JANUARY 29, 1993 • D103


001 CONTROL SEGMENTS 836 CONTRACT AWARDISA INTERCHANGE CONTROL HEADER ANSI ASC X12 VERSION/RELEASE 00301 ODOD_

Code Valua Implementation Note:Assigned by translation software.

Mandatory ISA16 115 Subelement Separator M AN 1/1This is a field reserved for future expansion in separating data elementsubgroups. (In the interest of a migration to international standards, this should

be different from the data element separator).

Implementation Note:Use character"<".

BASEUNE AS OF: JANUARY 29, 1993 • D103 3.0.9


836 CONTRACT AWARD 001 • CONTROL SEGMENTSANSI ASC X12 VERSION/RELEASE 0030101DOD GS FUNCTIONAL GROUP HEADER

Segment: GS Functional Group Header

Purpose: To indicate the beginning of a functional group and to provide controlinformation

Syntax: The data interchange control number (GS06) in this header must beidentical to the same data element in the associated Functional GroupTrailer (GE02).

Comment: A functional group of related transaction sets, within the scope of X1 2standards, consists of a collection of similar transaction sets enclosed bya functional group header and a functional group trailer.

Data Element SummaryREF. DATADES. ELEMT NAME AT!RMUTES

Mandatory GSO1 479 Functional Identifier Code M ID 2/2Code identifying a group of application related Transaction Sets.

Implementation Note:Choose the code value appropriate to the information content of the functional group. See X12 Dictionary forsource code list.

RQ Request for Quotation (840) and Contract Award (836)

Mandatory GS02 142 Application Sender's Code M AN 2115Code identifying party sending transmission. Codes agreed to by tradingpartners.

Implementation Note:DoD activities use Department of Defense Activity Address Code (DoDAAC). Non-DoD activities useidentification code assigned by DoD activity. Recommend for increased security that non-DoD code differfrom that used in ISA06.

Mandatory GS03 124 Application Receiver's Code M AN 2/15Code identifying party receiving transmission. Codes agreed to by tradingpartners.

Implementation Note:DoD activities use Department ofDefense Activity Address Code (DoDAAC). Non-DoD activities useidentification code assigned by DoD activity. Recommend for increased security that non-DoD code differfrom that used in ISA08.

Mandatory GS04 29 Group Date M DT 6/6Date sender generated a functional group of transaction sets.

Implementation Note:Assigned by translation software.

Mandatory GSO5 30 Group Time M TM 4/4Time (HHMM) when the sender generated a functional group of transaction sets(local time at sender's location).


Mandatory GS06 28 Group Control Number M NO 119Assigned number originated and maintained by the sender.

3.0.10 BASEUNE AS OF: JANUARY 29,1993 • D103


001 CONTROL SEGMENTS 836 CONTRACT AWARDGS • FUNCTIONAL GROUP HEADER ANSI ASC X12 VERSION/RELEASE 003010DOD


Mandatory GS07 455 Responsible Agency Code M ID 1/2Code used in conjunction with Data Element 480 to identify the issuer of thestandard.

X Accredited Standards Committee X1 2Code Value Implementation Note:Indicates that an ANSI X12 standard is being transmitted.

Mandatory GS08 480 Version/Release/Industry ID Code M ID 1/12Code indicating the version, release, subrelease and industry identifier of the EDIstandard being used. Positions 1-3, version number; positions 4-6, release andsubrelease level of version; positions 7-12, industry or trade association identifier(optionally assigned by user).

003010 Draft Standards Approved By ASC X1 2 Through June 1990.Code Value Implementation Note:Code value agreed to by trading partners. See X12 Dictionary for source code list.

BASEUNE AS OF: JANUARY 29,1993 - D103 3.0.11


836 CONTRACT AWARD 001 • CONTROL SEGMENTSANSI ASC X12 VERSION/RELEASE 003010DOD GE FUNCTIONAL GROUP TRAILER

Segment: GE Functional Group TrailerPurpose: To indicate the end of a functional group and to provide control

information

Syntax: The data interchange control number (GE02) in this trailer must beidentical to the same data element in the associated Functional GroupHeader (GS06).

Comment: The use of identical data interchange control numbers in the associatedfunctional group header and trailer is designed to maximize functionalgroup integrity. The control number is the same as that used in thecorresponding header.

Data Element SummaryREF. DATADES. ELMUENT NAME ATRMIUTES

Mandatory GEO1 97 Number of Transaction Sets Included M NO 1/6Total number of transaction sets included in the functional group or interchange(transmission) group terminated by the trailer containing this data element.


Mandatory GE02 28 Group Control Number M NO 1/9Assigned number originated and maintained by the sender.

Implementation Note:Assigned by the translation software. This control number must match the control number of the precedingGS06 control number.

3.0.12 BASELINE AS OF: JANUARY 29,1993 - D103


001 . CONTROL SEGMENTS 836 CONTRACT AWARDlEA- INTERCHANGE CONTROL TRAILER ANSI ASC X12 VERSION/RELEASE 00301 ODOD_

Segment: lEA Interchange Control TrailerPurpose: To define the end of an interchange of one or more functional groups

and interchange-related control segments.

Data Element SummaryREF. DATADES. ELUMDfr NME ATTRMUT6S

Mandatory IEAO1 116 Number of Included Functional Groups M NO 1/5A count of the number of functional groups included in a tran-,mission.


Mandatory IEA02 112 Interchange Control Number M NO 9/9This number uniquely identifies the interchange data to the sender. It is assignedby the sender. Together with the sender ID it uniquely identifies the interchangedata to the receiver. ft is suggested that the sender, receiver, and all third partiesbe able to maintain an audit trail of interchanges using this number.

Implementation Note:Assigned by the translation software. This number must match the number that occurs in ISA13.

BASELINE AS OF: JANUARY 29,1993 • D103 3.0.13


836 • CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD

3.0.14 BASELINE AS OF: JANUARY 29,1993


836. CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD

3.3 EXAMPLE OF CONVENTION USE




3.0.16 BASEUNE AS OF: JANUARY 29, 1993



EXAMPLE . CONTRACT AWARD TRANSACTION SET (836)

ASC X12 FD[ FORMAT

ST*836*AI234 N/L THIS IS AN 836 CONTRACT AWARDTRANSACTION SET WHOSE CONTROLNUMBER IS A1234.

BCO-00*N0001992Q30100921031*l*-930120 N/L THIS IS AN ORIGINAL CONTRACT AWARDWITH AN REQ NUMBER OF N0001992Q3010DATED OCTOBER 31. 1992. THE CONTRACTAWARD DATE IS JANUARY 20.1993. BY THEREQUIREMENTS OF THIS CONVENTION. THENUMBRAL I IS USED INSTEAD OF THECONTRACT NUMBER IN BCOO04.

NI*SE*16*22026 N/L THE CONTRACT WAS AWARDED TO THESELLING PARTY WHO HAS A ZIP CODE OF22026.

RE'65*A 1234 N/L THE UNIQUE TRACKING NUMBER FOR THISTXANSACTiON SET IS A1234

POI*00*20*EA*50 N/L THE AWARD WAS FOR 20 EACH OF LINEITEM 0001 OF THE REQ AT A UNIT PRICE OF550.

SE*6*AI234 N/L THE TRANSACTION SET HAS 6 SEGIM0DAND THE CONTROL NUMBER IS A1234.

NOTE: ALL NUMBERS ARE NOTIONAL AND USED FOR ILLUSTRATION PURPOSES ONLY.

BASELNE All OF: JANUARY 23, 1N 3.0.17


836. CONTRACT AWARD

ANSI ASC X12 VERSION/RELEASE 003010DOD_

3.4 DoD CONVENTION



836 - CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 00301ODOD_




836 Contract AwardThis standard provides the format and establishes the data contents of theContract Award Transaction Set within the context of an Electronic DataInterchange (EDI) environment. The Contract Award Transaction Set can beused by the buyer to notify the seller or other interested parties of the awardof a contract which contains some indefinite features, such as deliveryschedule, location, and/or quantities. This transaction set is intended to bethe notification of the award of a requirements type of contract.

Table 1PAGES PO. $EG. ID NAME REQ. DES. MAX USE LOOP REPEAT

2 010 ST Transaction Set Header M 13 020 BCO Beginning Segment For Contract Award. M 1

.....O P... .D ...........5 021 NI Name 0 16 022 N2 Additional Name Information 0 27 023 N3 Address Information 0 28 024 N4 Geographic Location 0 19 025 REF Reference Numbers 0 :1N/U 026 PER Administrative Communications Contact 0 >1

10 030 P01 Purchase Order Baseline Item Data M 1N/U 040 P03 Additional Item Detail 0 >1N/U 050 CTP Pricing Information 0 >1N/U 060 PID Product/Item Description 0 >1N/U 070 MEA Measurements 0 >1N/U 080 PWK Paperwork 0 >1N/U 090 REF Reference Numbers 0 >1N/U 100 PER Administrative Communications Contact 0 >1

X , .........

N/U 110 SLN Subline Item Detail 0 1N/U 120 PID Product/Item Description 0 >1.1

N/U 130 NI Name 0 1N/U 140 N2 Additional Name Information 0 2N/U 150 N3 Address Information 0 2N/U 160 N4 Geographic Location 0 1N/U 170 REF Reference Numbers 0 >1N/U 180 PER Administrative Communications Contact 0 >112 190 SE Transaction Set Trailer M 1

1 0DC01. JANUARY 29 1993


836 . CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD_ ST- TRANSACTION SET HEADER

Segment: ST Transaction Set HeaderLevel: Header

Loop:Mandatory Usage: Mandatory

Max Use: 1

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

Comment: The transaction set identifier (ST01) is intended for use by the translationroutines of the interchange partners to select the appropriate transactionset definition (e.g., 810 selects the invoice transaction set).

Data Element SummaryREF. DATADES. ELOAM0T NAME A'ILfUTES

Mandatory ST01 143 Transaction Set Identifier Code M ID 3/3Code uniquely identifying a Transaction Set.

836 X1 2.54 Contract Awarez

Mandatory ST02 329 Transaction Set Control Number M AN 419Identifying control number assigned by the originator for a transaction set.

I 1 3DC01 • JANUARY 29 1993 2


836- CONTRACT AWARDBCO - BEGINNING SEGMENT FOR CONTRACT AWARD. ANSI ASC X12 VERSION/RELEASE 00301 ODOD_

Segment: BCO Beginning Segment For Contract Award.

Level: Header

Loop:Mandatory Usage: Mandatory

Max Use: 1

Purpose: To indicate the beginning of the Contract Award Transaction Set and totransmit identifying numbers and dates.

Comments: 1. BCO04 is the contract number.

2. BCO06 is the contract beginning date.

3. BCO07 is the contract expiration date.

Data Element Summary"EI. DATA

DES. ELEMENT NAME ATTRIlUTES

Mandatory BCO01 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.

Implementation Note:Use only those codes indicated.

00 Original01 Cancellation02 Add03 Delete04 Change07 Duplicate

Mandatory BCO02 586 Request for Quote Reference Number M AN 1/45Number assigned by the purchaser to identify his request for quote.

Implementation Note:If there was no RFQ and a notice of award is still to be transmitted, insert the letter Z in this data element.

Mandatory BCO03 652 Request Quotation Control Date M DT 6/6Date to be used for reference purposes in an RFQ and a response to RFQ.

Implementation Note:If there was no RFQ and a notice of award is still to be transmitted, insert six numbers in this data element.

Mandatory BCO04 127 Reference Number M AN 1/30Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

Implementation Note:The contract, purchase order, or federal supply schedule number will not be tran.mitted in this transactionset. Replace instead with the numeral 1.

Not Used BCO05 846 Contract Status Code 0 ID 2/2

Required BCO06 373 Date 0 DT 6/6Date (YYMMDD).

3 DC01 JANUARY 29 1993


836 - CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD BCO - BEGINNING SEGMENT FOR CONTRACT AWARD.

Implementation Note:Date of award of the contract, order, or schedule.

Not Used BCO07 373 Date 0 DT 6/6

Not Used BCO08 587 Acknowledgment Type 0 ID 2/2

DC01 • JANUARY 29 1993 4


836. CONTRACT AWARDNI -NAME ANSI ASC X12 VERSIONIRELEASE 003010DOD

Segment: N1 Name

Level: Header

Loop: N1 Repeat: >1Required Usage: Optional

Max Use: 1

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

Syntax: 1. At least one of N1 02 or N1 03 must be present.

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

Comment: This segment, used alone, provides the most efficient method ofproviding organizational identification. To obtain this efficiency the "IDCode" (N104) must provide a key to the table maintained by thetransaction processing party.

Implementation Note:Addresses will typically be defined using N101, N103, and N104. N2-N4 should be used when theselling party address cannot be described using a zip code.

Data Element SummaryREF. DATA

DES. ELEMENT NAME ATTRiUTES

Mandatory N101 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity or a physical location.

SE Selling Party

Conditional N102 93 Name C AN 1/35Free-form name.

Conditional N103 66 Identification Code Qualifier C ID 112Code designating the system/method of code structure used for IdentificationCode (67).

16 ZIP Code

Conditional N104 67 Identification Code C ID 2/17Code identifying a party.

5 DC01 - JANUARY 29 1993


836 • CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD N2 ADDITIONAL NAME INFORMATION

Segment: N2 Additional Name InformationLevel: Header

Loop: NiOptional Usage: Optional

Max Use: 2

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

Data Element SummaryREF. DATADES. ELIMENT NAME A"TtSlJTES

Mandatory N201 93 Name M AN 1/35Free-form name.

Optional N202 93 Name 0 AN 1/35Free-form name.

DC01 - JANUARY 29 1993 6


836. CONTRACT AWARDN3 . ADDRESS INFORMATION ANSI ASC X12 VERSION/RELEASE 003010DOD

Segment: N3 Address InformationLevel: Header

Loop: N1Optional Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party

Data Element SummaryREF. DATADES. ELEnMET NAME AI"mUUTES

Mandatory N301 166 Address Information M AN 1/35Address information

Optional N302 166 Address Information 0 AN 1/35Address information

7 DC01 • JANUARY 29 1993


836. CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD N4 GEOGRAPHIC LOCATION

Segment: N4 Geographic LocationLevel: Header

Loop: NiOptional Usage: Optional

Max Use: 1

Purpose: To specify the geographic place of the named party

Syntax: 1. At least one of N401 or N405 must be present.

2. If N401 is present, then N402 is required.

3. If either N405 or N406 is present, then the other is required.

Comments: 1. A combination of either N401 through N404 (or N405 and N406) maybe adequate to specify a location.

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

Data Element SummaryREF. DATADM 5. ELMENT NAME ATTMUUTES

Conditional N401 19 City Name C AN 2/19Free-form text for city name.

Conditional N402 156 State or Province Code C ID 2/2Code (Standard State/Province) defined by appropriate governmental agencies.

Optional N403 116 Postal Code 0 ID 4/9Code defining international postal zone code excluding punctuation and blanks(zip code for United States).

Implementation Note:Use only when the address of the selling party has no ZIP code but may have another type of postal code(e.g., in a foreign country).

Optional N404 26 Country Code 0 ID 212Code identifying the country.

Implementation Note:A translation table will be required to convert those standard codes used by ANSI to those use,! by the DoD,as contained in DoD Manual 5000.12-M.

Not Used N405 309 Location Qualifier 0 ID 1/2

Not Used N406 310 Location Identifier C AN 1/25

DC01 • JANUARY 29 1993 8


836. CONTRACT AWARDREF. REFERENCE NUMBERS ANSI ASC X12 VERSION/RELEASE 003010DOD_

Segment: REF Reference NumbersLevel: Header

Loop: NIOptional Usage: Optional

Max Use: >1

Purpose: To specify identifying numbers.

Syntax: Either REF02 or REF03 is required.

Implementation Note:One iteration of REFOI/02 is required in order to carry the Unique Tracking Number (UTN)forthe transaction set.

Data Element SummaryNEF. DATADESl. ELINT NAME ATTRIUTES

Mandatory REF01 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.

Implementation Note:Use code 65 for the Unique Transaction Number.

65 Total Order Cycle Number

Required REF02 127 Reference Number C AN 1/30Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

Not Used REF03 352 Description C AN 1/80

9 DC01 - JANUARY 29 1993


836. CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 00301ODOD PO1. PURCHASE ORDER BASELINE ITEM DATA

Segment: P01 Purchase Order Baseline item Data

Level: Header

Loop: P01 Repeat: >1Mandatory Usage: Mandatory

Max Use: 1

Purpose: To specify basic and most frequently used purchase order line item data

Syntax: 1. If P0105 is present, then P0104 is required.

2. If P0106 is present, then P0107 is required.




6. If P01 14 is present, then P0115 is required.



9. If P01 20 is present, then P0121 is required.

10. If P01 22 is present, then P01 23 is required.


Comments: 1. See the Data Dictionary for a complete list of ID's.

2. P0101 is the line item identification

3. P0106 through P0125 provide for ten (10) different product/serviceID's per each item. For example: Case, Color, Drawing No., UPC No.,ISBN No., Model No., SKU.

Implementation Note:The POI segment is used to indicate the award data for each line item awarded from a singlerequest for quote, to a single vendor.

Data Element SummaryREF. DATADES& ELEMENT NAME ATTISMUTES

Required PO101 350 Assigned Identification 0 AN 1/6Alphanumeric characters assigned for differentiation within a transaction set.

Implementation Note:The line item of the item being reported on in this notice of award, taken from the original RFQ.

Mandatory P0102 330 Quantity Ordered M R 119Quantity ordered.

Mandatory P0103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit of measurement.

Implementation Notes:I. Conversion to and from the unit of issue codes in DoD 5000.12-M will be required.

2. Any code can be used.

DC01 .JANUARY 29 1993 10


836 • CONTRACT AWARDPO1 • PURCHASE ORDER BASEUNE ITEM DATA ANSI ASC X12 VERSION/RELEASE 003010DOD

Required P0104 212 Unit Price C R 1/14Price per unit of product, service, commodity, etc.

Not Used P0105 639 Basis of Unit Price Code 0 ID 2/2

Not Used P0106 235 Product/Service ID Qualifier 0 ID 2/2

Not Used P0107 234 Product/Service ID C AN 1/30













Not Used P0120 235 Product/Service ID Qualifier 0 ID 2)2




Not Used P0124 235 Product/Service ID Qualifier 0 10 2/2


S1 DC01 JANUARY 29 1993


836 . CONTRACT AWARDANSI ASC X12 VERSION/RELEASE 003010DOD SE TRANSACTION SET TRAILER

Segment: SE Transaction Set TrailerLevel: Header

Loop: -

Mandatory Usage: Mandatory

Max Use: 1

Purpose: To indicate the end of the transaction set and provide the count of thetransmitted segments (including the beginning (ST) and ending (SE)segments).

Comment: SE is the last segment of each transaction set.

Data Element SummaryREF. DATADES. ELEMENT NAME ATTRIBUTES

Mandatory SEO0 96 Number of Included Segments M NO 1/6Total number of segments included in a transaction set including ST and SEsegments.

Mandatory SE02 329 Transaction Set Control Number M AN 4/9Identifying control number assigned by the originator for a transaction set.

Implementation Note:This is the same number as the one in ST02.

DC01 JANUARY 29 1993 12


DRAFT IMPLEMENTATION CONVENTION

4.0 ASC X 12 FORMS

In this chapter, applicable ASC X12 forms are presented.

BASELUNE AS OF: JANUARY 29,1993 4.0.1


22111ADI MAM~iULamiL

~~ ASC X12 Woek ReAim Poem

ASC X12 New Pojac PMPW~p Form

ASC X12 New Tranhaion Sot DevWpy"e Poem

Foffm fOr Now or R~ve Append A Code Source Ratremm

Docuniev Proparum ftr riepre ftgfr Guidileswm m Corml Swxanas

8affpb TruramliW Poem

ASO X12 Balot Conuneut Reopone Lette Forivw

ASC X12 Starndsi; Order Form

PALLn ieeVUI.

BASELINE AS OF: JANUARY 23,12IM 4.02

DOW ? wTA1Um COWARTIO

ft..5/10/ga DM NUMBER_______DATE SUBMfITED ASC X1 2 (SewW Only)

WORK REQUEST FORM

AL-I REOUESTS, MUST S3E TYPED or pIrb3s 1e@9by in black hkk Comnplats both side.

1. TO USE THIS FORM OR SUPPORTMIS DATA MA04TENANCE FOR A NEW ORAFT STAN4OAM OR X12 IN I ITATION. UrM 40iotesirent an ONE temn. Urn avwn - neamemesy. Ust * INaa no eemeb Ammen lw do ueimme onW/eaeeeo eeThen Meim'i evona woft euhanwoo~und doi weiemen/eeee/.edeouweeL Thengv~l (esyenr e.g.. XILS. X12P.8)

I. TO USE THIS POWi TO PEOUEST A CKWUO TO AN~ coSTI S7ADAoFO. um a upwara VA*qer Pen,, Fwis N aN wetena beawUseSenee~ neeamee.en eneem w amat re.eone d emoreni. M laemonemieeam pietid. 9o'tnr Amo mavny beed

ber omnuaden end sowul be nuntbete.

&. TO USE THIS FORMi TO PEOUES A PROPOSED NEW X12 PrOXECT. oo 10l81 Sadden A. Pmvwd a psapoeee/empe at ewA b tne feaftwee inveloe in Seeden 2. Piedde a eIp1le -N of go business need and juaftealen ber mew rwPH*"ein hiSaften C/Put L TheVf*AcPeueet wlIbe beawded tiatapp ip ilu X12oumbenwilmefoe b aiye aepreenn a p- pejalenpeapeb.

Circle One: (1) Now Standard Suppmftht Date Mainfenince (use attachmients)(2) EAlm~g Starldad Maliesnce Request (aseSeon0(3) Requst for NowX12Projeot

Aen1Pne/beSIAeNMA e 1ane ~e fdde 910e ebtWdMW VAdNN~eIf s tes WSMuM be dlmat e01 1ned Pruwe Opp 0d- AnedeWWMmma. ienee for 01 *malypubbeted eade -m itid wimpe beta or Item elfi hadequmqIn Si d be me glte requemedwel be shote fime ONubnuttr.

A. SUBMITTER INFORMATION

SubmIfter. Namorris_________________

Address __ _ _ __ _ _

Address/3P _______________________

Indicate the X12 subcommftte or task grup wtoe position is represented hereI declare tha thi0 reesnwts the official po~iton f X12 WORK GROUP: __________

establishved at the meeting dated _______

B. PROPOSED WORK: LINt the specifc chrage to the standards being requested. Give Me names andassociated Wdentmur d the standards, segments dat elemns and codes faffctd.

4.04BASELINE AS OF: JANUARY 23, 9911

DEPARTW OF DW9iSEDRAFT UPLEMOiTATMO COW40MN

Page Two

C. REASON FOR CHANGE:Putl 1: Ust the vmsion/relems of the atandard you ame uslg or using as a reference. Name the &Bnsactl on ethat Is being/w~ll be used emt diciates the requested changed. List affected segments and da" glemnta oretherstandards. Provide only reference numbers/Il~

Reference Sam. Version 2/R1elease__Transactio Set Used______ _________

SegameiAffecte ______________

Data Elemntri Affectel ____________

Other Sandard________________

Part 11: Explai why you need the prpsd clg. Provide a comnplete sceralo that tid wtat the businessfunctiMon. petonor problmis tatwE besatsfedby a cngeto the standa. The XI2J TechkcAssessmnent Subcmmitte requre enough irftmuton in Othi Panl 11to be able to propos an allainaes setian 9necessay.

ID. RAMWICATON: It you circed (2) an Page- i. complete VUl ssctil TO ensure VW at -, 11caim a at yawrpropose- change wre recorded and OW yoaw requs is complg.efte.cle below al sactiar off steandardseaelected by fth proposed changs

TRANSACTION SET Nine Aiusm/Sus Tab Hin/Couwwnm"-tom" ftdisn am~ k. Ws

Lsp ftsg Lamp Sm~as AN &qmme

SEGMENT Wse4w Ot"n DOWN".Ami OmmN 09pufthm in tqmu

-t". ow pa mm So 010"ma

DATA ELEMENT N~WW Damwgn w

CODE Add 080 ~ b Comi coo ft Ckme

OTHER (e.g.. XI 2.5. X12.6):

ERRORS NOTED IN THE STANDARD (Oft P"g no, and owhe iderercilon

SASILDS *5F: JANUARY 3,131 4.0.5

DWR•AMINT OF OSUM

DRAFT EPLEM.NTAtOW CONVENTION

ft,. 4/1/20

PP No.(Secretariat Only)

ASC XI2

NEW PROJECT PROPOSAL FORM

PROCEDURE Only X12 subcommrites may use this form to register new development activities as X12 projectproposals (PPs). Complete all pages. PPs approved by the X12 Procedures Review Board will be registered andassigned a PP number by DISA, and a Transmittal Form will be issued.

Date and complete the form below. Type or print legibly in black Ink and number all attachment pagesconsecutively. Submit to DISA prior to an ASC X12 meeting, or to X12J Technical Assessment Subcommitteeduring the subcommitteWs agenda period at an ASC X12 meeting.

Date Submitted:Date Approved by Subcommittee:Subcommittee Name:

Task Group Name/No.:

Joint Development Subnommilee (It any):

Circle one: (a) Transaction Set (b) Guideline (c) Other

Project Working Tite:

Official Delegate(s) for This Project To Be Named on Transmittal Form:

Name Name_'_ _

Company Company

Address Addres_

Addre/ZIP Addless/ZIP

Twelone Telephne

4.0.C DASELIE AS OF: JANUARY 29,131I

oinPAaTMmf OF DEFNSORA"T 111UP.ITATION CONVENTION

A. PURPOSE AND SCOPE FOR THE PROPOED WORK: Provide a wall4danhd purpos/scope tor tfeprOPOWe work. See, X12 Oesip~ Ruse and Guidslkwe for requrmneftL

S. SACKGROUND: Provide deWk UWWA be heiphi In rev~wkg oe proposel Whom We to mseaid wrs?1`1W vA 12he stmdId be uWed Whet bwlns f$W*Icn) doss I sen.?. 9 the p 'oposed mnded overiaps the

CQ OTER STANDARD IVOLVEWD N Mapplm WeM~Y "rW W Wmsr f Oftbu I'rw Ma indou 11 OW esnirrv/rualed tola Dieproo- and iwime ndards developers (e~g.. ANSI Awurditd Standards Camnlmlsees

whOse aiMef nay be Waved or allaied.

0. EXPECTED COUTEI4T/GE4RL ECI0l (OPTIOAL) SUWONmilry mach a Prel*nky draft othe proposed stndard or odwe supprthm doowesso m OhsCuu new esmwI dM elemernm emwrdUruckres and ctmng to X12.S or X12.6 UW we reqired or anaotoged. (Q.Me gfchftiU)

UANLINK All OF:.JANARY 2,1SIM 4.0.7

DEPARIMET OF WDNSEDRAFT PLMSINTATION CONVBION

4/1/10

FORM FOR NEW OR REVISED

APPENDIX A CODE SOURCE REFERENCE

INSTRUCTIONS: Complete this form whenever a new data element or data element code is requested to be

added which references a code list published by an external (non-X1 2) organization. Use one form for each new

reference. This form may be used to revise current references; fill out the appropriate areas below.

CIRCLE ONE, COMPLETE AS APPROPRIATE:

(1) NEW REFERENCE(2) REVISED REFERENCE. Current reference number/name

REFERENCE TITLE: If there is only one source for codes for the data element. the title should be the same as thedata element name. If ther are multiple codes referencing external code sources for the same data element, twdeshould approxiTmte the code defition.

REFERENCE TITLE:

DATA ELEMENTS USED IN: Give the data element reference number ind name which directs the usar to tsAppendb A code source meferen. GIve the code I (11 assigned) I this IS for a specl code of the data ewlm.

USED IN: DE No. , Code ID

SOURCE: Provide the name of the publication which contains the coda referenced.

PUBUSHED IN:

AVAILABLE FROM: Give the publisher, or other contact, from whom the user can obtain the document

Name/Ann of

Address

AddressAddres/ZIP

ABSTRACT: Briefly describe the publication. Its purpose. and indicate what codes It containL.

ABSTRACT:

4.0.• SASELDIE As OF: JANUARY 21, 1Ies


DOCUMENT PREPARATION FOR/s

INTERPRETATIONS, GUIDELINES AND CONTROL STANDARDS

Thes instructions arm provided to assist developers of interpretations5. guidelines arid conrolc structure which awenot transaction sets (for transaction sets use the New Transaction Set Development Form).

GENERAL- DISA provides tite pogs sand front matter for publications and copyedits the document according toDISA house a"~1.

REVISIONS: If the documnent Is a revision ofa previously published interpmettion, guideline or starndard, provide aoumr f the changes to the original that are contained in the document.

I INTERPRETATIONSA formal Interpretation of an XI 2Th1 Standard is considered piat of the body df standards when it I@ approved forpublication The interpretation draf t should state the issui presented by the requsator. state the proposed, 1mrp IseIaton arnd show as attachments any Work Requests tha nay be nimeesay to effet the Interpretationwithin the subject standarid. The draft Interprouatlon is processed Nok any other subeomnulte documnirt

* GUIDELINESFor publication purposes, guidelines ws treated like a $journ article. Basic Fqreqmnwts are given below.

ABSTRACT: Thi is a precise sumaumry of the Purpoee/ Scope (see below), and may be identical to it 9 thast is brief(two piu1graphs); otherwise sunwuriss the purpois/scope. It should r a hd enough h fwt. on about the

docmem to eamble a risder detanrmine what the guidelin is Intended to accomplish wti~in an EDI anvirorment.

PURPOSE AND SCOPE- This staternnrt nos kidicate purpose df the guitidsurw e~g.. the business function orope-ratio addressed. Scope arid any speclc mtations of scope shosi be defined.

BODY OF TE~ff: This may beea numnber of subsections logical orgLanzed. provide sections for forewodhinroduction. definition of terms and concepts, reflerences and related s~~vtadds methodology. specifications,requirements, discussin and conclusions, as appropriate to the sublecL

ART AND GRAPHICS: Graphics or artwork necessary to Ilustrate fth docurme are encouraged. providecamera-needy copy N thee are not already prepared and delivere on a wP diskeftt to OISA.

FOREWORD. FOOTNOTES. APPENDICES: These may be used for purposes of clarity, Euwtation or generalIrkmtio,, not as *Panro the guidalne. A soement Indicating the mtno"i Is for Wnornmaton purposes orty aridnot ptof the gidline eI$ appeerat tlhebginnig ofaforword or appexNdi

OfI CONTROL STRUCTURES AND OTHER STANDARDSFor publication purposes these documents are neoted like guidelines (see Section 11 above). The requirements arethe same, with the addition of the kfolwkg

NEW SEGMENTS AND DATA ELEMENTS: These may be defined within the tot however, since the reprfesetchanges to X12.22 and X113.3 the should bee speiloe on a Work Request Form attached to the drWL.

RELATED X12TMSTANDARDS AND OTHER REFERENCES: These shal be idenified Ina $asction wthi "theoi&

BASELINE AS OF: JANUARY 25, IM5 4.0.9

DRAFT UPLEMENTATION CONV91TION

Page1 TWO

FORMAT: Orhi OndI Sadeid for TiW U@e CaiWaln ft k 10F WW and W eg118~ CM dW W dee f te________Trmmaiav Set Lj for we wUIoi fte cema d an' BEarax Omw Imtwdun (WD)

e'w~ramMew The nwucdon so (=ni be wed to .. )

C. PURPOSE$ AND RCON This WgeMe mug W4=0c~ ame d .ugi m pebiAn of the Wansum M aOWwho the eender/ eeamsw Expigk fth bu~Ie hoic"i or opwaoon Owt is sdaree. Fdlaw AIC X12OsWV Rum and Guideline wd wse Oft foram

FORMAT: 6Thtjsgafide dmpo~suntIomiet an WeIftb§wthedee Cmas dte _____TuwUUclfaSet will" fte earau d an Geavo. OMs Irmeraun (ECK) w*OItmme Tfth frmictgla as (can be wed Wto~

0. T1RANSACTION SErAUX (S) Far inch itR'e ~Od5te blo WAng 'UWul@tS FOMIAT:

TABLE X

POSITION SEOKNDT REQ. VAX. LOOP 3ZPZAT NOTENo. TB ?!TLE pII uS! MyN it".010 ST Transaction Set Header H I. NotelI020 B5 Beginning Sequent for If I C@@nt Ietc.

NOW 1: T76 b a nowe NOTES we Wu d fthen (muibred.Commits A. Thm a a aolirww. COMMENT an not pen of fte eandd Ovuud).

L APPENIM EXAM-PLES 1W11nw am uwd to we fte mekat go th prape vwinod@ w~ eqton It towere At lMW one mw" ba ivwfeyV No vucogdebl propr inmn enuy be wed In u'y m - pe.

FIGURE 1: (P~oed Urn aYl - PI -e docuwiN wing mo~ dwa V wsed. die tWe be amwotal imppedto FlWft 2 HOW gnugphle noU bencd p I- -1/W 11soM aotenbe pled.

FIGURE2(or EXAMPLE): The thIwued poviea luelwnernewbiotosil tow the wde whim bagoinon in te wiiple Add Urnmnoe: nV~ mwipI r 1 ~ ' epesetedeeet meer rN/L chwacter iqxree ft Urnqepeu twnb~w.* Ptuee. EDO Munuaheio dft and ft mer*I in two eoiwnmraldeby-eldeZ w =r odes mu dbomunged atm dthe usobineu In an o~bnuwy m~ m le 6 r. FORMAT:

BUSINESS SCENAPJO- In~fo Sm u onemm *mthe uderkaX12Real CuterwW te rceverlm Im upper.Farlasfc Produmt MenshaofgtIc..e

EQt TRANSMISSION DATA (TRASACTION SET "MaOSE DATA

ST*SXX*0005 NIL Begin Transaction Set $XX; ControlNo. 000539*O1*79800' N/L original Transuission; Ref. No.79800etc.

4.0.10 BASELUfE A3 OF: JANUARY 29, 1M

DEPARTMENT OF DEFENSEDRAFT IMPLEMENTATION CONYIVETION

ro. 5/10/00

DM. Number____ _____(Secrtsarit Ord;),

Documnwt No.__ _ _ _(Devoper Obtains from DISA)

ASC X1 2NEW TRANSACTION SET DEVELOPMENT FORM

INSTRUCTIONS: Use this fam~ to subMA a draft transaction sot for revlew by X12J Techinical Assesaernan unti ft istest processe by DISA. Use a now Transaction Set Developmnent Form wheneve revisions are proposed "n atM fe asnt aboen prepared by DISA.

ATTACHMENTS: Attach &I pages. use this form as the first. Follow thee., instructions for preparing mwWAtel

The uinmer mis obtain a document nwmber assignme fromn 01SA. Post it to this form (aboe).

Attach a List of Revision I the draft was previously reviewe by X12.1 or I this is a revised/redesignedI -nsactin set SendwU requiri X12 bait

Use ONE Work eusest Form to Me al suppo"tn data malinteangnce for the transaction sat and astch ktto this form. Propose new or revised codes for 0E1143 anW 01E479 at a mi*nimu I required.

A Trnmmnlfla Ferm mus accornpany this document when kt is sibnfte to DISA for distrbution

Use the most recen X12TM Standards Developmnent Workbook to chemck, your documnent for accuracy.

A. SUBMITTER INFORMATION-

Submdfer NO rne_______________ _______

comp any ___

Address __ __

Addres/ZIP ________________________

Indicate the Xt2 suitcommltee or task group whose position is represented hers.I declare that this repreasen fth Official Position of X12 WORK GROUP:__________eslabkhed at the fmeetin dated_____________

11. ASISTRACT The Atmmbmc Is regiWserd with the Americn National Starclards institute. ft is a precises sumrnaryof the Purpoee/ Sope (Use Section C below). Itt may be Identical to the Purpoee/ Scope I that is brie (twoparagrphs) otherwise siuvvwlzfe the purpose/scope, It shwi contain enough~ k~ofrwwton about the standardto enable a potentia user detmernine what equivalent paper transaction ft represents or what the standard isintended to do. Follow the borma on paeg two.

BSEILINE AS OF: JANUARY 29.13Wf..1

DEPARTMENT OF DEIPRSEDRAFT IMPLEMENTATION CONVENTION

-. y. S/1•O/DSAMPLE TRANSMITTAL FORM

inftlliedKEY DATE: Febnuary 15, 190I

DELEGATES NAME John DoeRESPONSIBLE SUBCOMMITTEE/TG* ASC Xl 20 XX Subcommittee/TG4

TRANSACTION SET/GUIDEUNE TITLE Xl2.X ABC/XYZ TRANSACTION SET (SWX)

BALLOT Document No.Current Document No. ASC Xl2Q/90-lPreioum Document No. ASC X120/90-004Project Proposal No. PP-mAssocited WR/DM No. DM 012-190

PROJECT PROPOSALPP Review by X12J (DATE) 2/7/90PRB Approva PP (DATE) 2/9/90

DEVELOPMENT PHASE: Pmject pOAPO SPPfV through ara for X12 vote.

Document Submitted for DISA Ted Pmceaein (DATE) ,SubcommiToee Appove Draft for Review by X12J, Tech Ammesmef V (DATE)X12J Tech Assesment Review (DATE) ,PRO Approves DocumeOt for X12 VoW (DATE)

ORIGINAL BALLOT DATA (DISA):

Ballot Closed Date (DATE)Tally/Comments Sent to Chair/Delegteo (DATE)Tally Stats (Numbr md Percent)

Ballom Maled (IW%)Ballots RouRe L...)

- Approved L%App w/Camamnt (_%)

- DiWpoved L__)Abstained L

4.6.12 SASEL3N AS OF: JWARUVY a,.13M


Page Two

COMMENT RESOLUTION PHASE: See Sections A. 8 and C. f the subcommittee at any trns decides to rebalatthedocumerit. PRB approval is require and response letters are not necessary.

A. COMMENT RESPONSE LETTERS: An Open Forum mxst be scheduled at the red X12 meeting folowin Ieobaflt closing date. AN those who commerfed rscsivs a cotmmiisi responise letter frorn the developingsu*commnntee. DISA records thi process arid aeie die nulig

Open Forum Date (DATE) ______

Response Latters Malled Out by DISA (DATE)_ ___Rebutal Perid (30 days) Closeas (DATE)______

ADJUSTED BALLOT DATA (DISA):30-Day Respose Review Close Deus (DATE)______TalY/Commeng Sang to Chair/Delegates (DATE)_ ___Tally Stats (Number and Puretwo

- Salts Male (100%)Sallots Returned L_%)Approved ( %

-App w/Commsrt L_%)

Abstained )

B. SUBSTANTIVE REVISION: It ballot conernits result in s~ubsaritivs revision to fth documeMi dime arereviewe by XI2Jad procsse by DISA. The reise doWcunte Is subfMite to X12 voerss for a 30-day reviewperimd. DISA recoPds uVs procsee/hendles ruling Subcommitltees should conduct 30-day reviews for respornslaUw/revised docurnera oorcwiendy.

Subcommuittee Appr"ovafe Revisions (DATE)_ ___X12J Review ol Revisons (DATE)_ ___DISA Malls Revised Docurnrmt (DATE)____SWUbatave Revisio 30-Day Review Cioo" (DATE)______

ADJUSTED BALLOT DATA (DISA):W-Oey Substantive ChwWg Review Closed Dute (DATE) ______

Taliy/Comnmetil SaM to Cheir/Delegaes (DATE)____Tally Stats (Numnber and Percert)

Beaets Maled (100%)Beallts Returned L_.%)

- Approved L %-App w/Commerg (_%)- Disapproved L~

Abstaied (%

BSELINE AS OF: JANUARY 20, IMS401


Page Three

C. CONTINUING OBJECTIONS. If there are continuing disapprovuls after the 30-day review period, thedocunmen/dlspprovals/rusponfll/COfdkltifnfg objections are mnalld to X12 members who originally cast a ballot.for another 30-day review, to give then' an opportunity to change their vote.

Continuing Objections Malled to Chair/Delegate by DISA (DATE)_ ____DISA Malls Document (DATE)______30-Day Review Cowe (DATE)______

FINAL ADJUSTED TALLY (DISA): Whenever any disapprovals are withdrawn, a letter to Othi effect must bereceived in writing by DISA.

Fina Tally Results Sent to Chewr/Delegate (DATE) ______

30-Day Review Siam (Ad justed TallyBallots Malled (100%)Bellow Returned )Approved

- App w/Comnmet LDisappoved %Abstained ( )

PlRI APPROVAL PHIASE: After the comment resolution period, the aubcomrntee vowe to subMi the docmentto the PRB for approal to puliK

Subcomi N-ttee Votes to Release to PRB (DATE)______PRB Approves Publication (DATE)______

FOR DRAFT STANDARDS FOR TRIAL USE:VERSION/RELEASE/SUBRELEASE ID CODE ASSIGNED:______

4.&.14 BASELINE AS OF: JANUARY 2, ism


Page Fuew

TRANSMrfTAL FOR M MIE~UCTHON:

GENERAL TN.t Trwwraym Farm Is TURNAROUND DOCUMENT whh deord Ifti Ihiory/cwwr stftus of gWrIeM dOcumMu It b uud to srchung kWamuaon behwe sohe Socrouift mid Ow cwwumi~u d X11mWonatian 6 =aMingg"v (W n#. Thi, lom b mohched to the documm whinaw It kbuild for d~rfb0on (3 Inrrimet"W for uAxmlfti documrts to DISA X12J Tectu*U Aiisinit and the PRI). DopiDISI CIUci

mxfl*61 wve st0 me~ed an socl documeMt and now nwnbers are mquhvd whenever Is m rkbe.

KEY DATE Thb b wed to Werily fta 1tem vmn~a of the documert (date ausoab vte Ifto tag r c ver 5wmIWform upd").

DWELEGTE Each ubcomnftne duigrmn an bxb*Wi (ddegmte) krm Owe graip aupnb' for fit prlomeThe Serafgtwomube ldarm Eftie kegeclubs

INUflTMO: Pibawy dm b regan ided by DUS an fte I -ed farm gfte Vfe prajeM ~p , p b approved by the

We reso*niWe kir r cc dh mg ft. appraprbte PA~gmwbe appmvii deti. The dv*/deog wE me"ev a copdl Owe updmed wwwm farm wtmisvek II b red by DWOA

UPDAT"N: At SOch apoIMt 111aP. DISA wE POST frevh dfa to Vie form. ADDOw Vie opp a ppIopib fteW s tofie form% OW SEND k to Vie subonwAmmm cvir/duleme at gooli~ ueh cLub The deispl mum POS fie

farm witNO fres st ON*l $M &lu far ~hc Vie obcombeeb iespme mqwfid SEWD It vt Viea Wrpit doeuwier to Vie Secsagumt.

BASEUANE AS OF: JANUARY 26,5IM 4.0.1

DEPARTMENT OP 08MMSDRAFT UPLEMSITATIO#4 CONVENTION

&UM ASC X1 2 BALLOT COMMENTRESPONSE LETTER FORMAT

olauuuaAuolm

AFTE AN 12 IALLO,rIIU RUONNUE UUSO=rUMITTE (ril DIONTERTAS ROU M~MUT musai hinwumigd

wo, no& -9e DWuaso & Pima~u mm" uwa suP) ms Sm ou we ros muted a oumq a gmae aubumww- sw awti kmee 4aa of am immaues am mpwm I ILThe OPU am IM at mnnemmaopwAt. Solt be owiind

vi' m " ubmwmaf choi.

Tham am ooo Imom Mut Wbaum SmA ~ 0 dhb: a gmin bt MWi ~E vbe ow a d nfuawmm. &W a'hadoup.'.. a0 som ammma. See hasudam balio Saw so un1AM.

OPTION1: GOW4E LETTER (MA.?!, LETIER TO ALL OOUMIOISYou owy pus-m ouw b to smi demoammas E'y mmmutadWdsa beo aind i wWbu. Pu ~m--WA ram. ow owmwmw (Xil ammb~srosua owne) ad ft aM Nmmmd IW ta Lftyasu spame urn mmmi. gymdmae m upgIip ye. mi o *ap em ami ~ in isWW &W o da aup $no aUn. ma rowe 1my smoA So aaoppAgd main be

GPTIN 2: SDmOUAL gaIER To £" COMMEERI

PSafM em memd Suiom buvt sale aid em u wAy#w mdaS labsowso. orui W~w* bowtoW fo Vowi bew~ Iapami W

* es ymaid man Im I bI aW dise aonmw.m em deawma owe wm snow--IpIdo em ftOf but I U bme by ir A(o. AMC XImrSYT012mA~t f wm aau by a IP (eLg. AMC X1IFi~bo-ML-U) ow.

WOE 2: Chsoem wW fot o bud (am Oa" Irl biumdan a~m

STE 4: PIpm f MW 11-0 em 1 s. bft GUMMg a8W ill G uae fbut~ INAM %.a. Pumft a wow 'mm (aebur) hin ftm f"p e m b" d to hoolU. hadwf phat mamim.b. PW to em um. md omftpi -w 3mW boaded be..a. Pnmr dow em ,m , em mumutm ~m.d. Afeem I*6W19toMOAort a emf Wowed b gse bakl man ameme bw ad Muom &a.&. hifte an bl~mjaMy pwqqi, w O emw bast popas WwWlb f adiem a e.I. You amymA ah 1 em ft 6" 1 (bwr pyew Timmauw pam) ow em bilubm"im oft Ut. r

STEP4: ouaiemw fb~mi aemSsmeubjA.Amows.' v Sae la a...h@w~ 1,t a a btteiabgdW~bAb U em m-bWe~a) ps haow Promd WIMi em bue hWAr be.4060 ih SOme pupa ftM a ad m~mufti alar at mown. ma d

umwMad Poem ~d hom em amw" ad SOW 36 om~ paWb dm" dw pmm

Almeauta: XIIAW La ""dIftw-oif Momw -tp wL-olf bWSW" Ladw

4.0.15 SAEUNE AS OF: JANUARY 2S, IMI

DEPARTMENT OF DEFENSEDRAFT NPLEMENTATION CONVENTION

ASC Xl 2-ELECTRONIC DATA INTERCHANGE (EDI] (999 999.9999

ooerutg iaw~~I~ ar~eo~rs 01U~e(999) 9994999ACflefclUd Nacaont SCwau mzj

Oocu.memn NoASC X1ZC= 20/90.999

fusle 25, 1990

TO- X12 Members Who Commented on Modjilazims toX12.in Control Structum

RE. Response to Comments on December BallotDMs 20M22, 2252, 317299

Thank you for your comments. This ballt involved modilletion to Xam. Of the 327 beamlt maled, L59 ballt werereturned. Of theme 11I appoved, 15 approved with commenc, 20 disaproved with omemeot and 37 abstaised.

12 SOMeAL the vote mponsu were is favo of the modfickaiou. The majesty of the maecus foamsed on the im~apsof these modifleatiaa os the presentation of information is the XI2Z Sepum DiutesM. The proposed modiffcadamnod the reuting Prnseatia4 0 the aeVOnt darestary ha bee inWerk is MWspom to the come enlb A revisedmodiffication to Xlii. wis revien by Technica Assesmen at the Jame ASC X12 meeft Modfifatioms, to thedoaament have bees &Ad& whih reftet responses to the comments from thi balot, and a revised copy of X11. axibeing dkwatrae to all who voted on this is.., fW 3.da review of mv~to@L

Spaweii responses to comments follw.

COMMENT: Automobile Caorparaus*Add the f108owi0g amo to arPs"PO 3.3: NOTE- CommuniatiorI prto olhruters should be enduded from thecharactelr sw

RESPONSE-The coMe lester sea out with the voling padcage mplind thnt the finenet wu to obtain uaim~ as the proposedmsodilatiass to X12.u. X1i. is a dlifficulstandard to amend. We reques tha ballo rspoases be onudered as themerits Of the reommended modialatim and not as the standrd as a whole. Yaw cmman was outide the scope ofthe requested modificatioss.

BASELINE AS OF: JANUARY 21, ion.,1

DEPARTM T OF DEFENSE

DRAFT IPLEMENTATlON CONVENTION

Pap Two

COMMENT: Airaft Engine Corporation"S=me consideration for AbstIaA SymmX Notation One (ASNI) should be aowe

1 ASN.1 is capable of defini all of the necessaaz inter-relations needed by X12 trusaiouL

2. ASN, requires .eu chanacten to define the same information.

3. ASN.I is the encoding scheme used by most OSl woW.

RESPONSE:The recommendation to consider amp a( ASN.1 en•od*g reaches far beyod the scope of the modfications reqstedian this ballot. Adivities such as this am best submitted as separate work requeas.

COMMENT: Some Software hn.*Conditionaliy of data elements should be lft to the discretion of implemeation guidefines and apeemens There ismuch discussion at times as far as whether certain dafta elements should be mandatory or wKt many application s)Vemsare incapable of providing cntain' madatoq information and, as such, ier-rtype dat mnst be i -

RESPONSE.The issue oa data element coditionality as a whole is a much broader subjeet thanas inWended to be addressed wi"ithe scope of this ballm. This baot was iunded to provide a means for a•sutewt documentatm and application ofakemay MI codition stumuCt . If the COmmentor believm that the codiomal structure should be removed &romthe stadard, the task roup recommends that this be submitted as a separate work requat.

Etc.

4..1S BASELINE AS OF: JANUARY 2., IM


ASC X1 2-ELECTRONIC DATA INTERCHANGE (EDI]Accr~Wd SwarMm C&iiuMeM Joe Somsebodyam au uI .tod ae a= m of- a*Cair TO 19. X12CA~v NetrW Swraw~s -='u*e (999) M""99

Document NoASC X=2CfF0890-99&

ML aw ocAUguM AD 1990

Amman lanikOft Cmtral PlateMiddle Amesuk MO "999

RIL Respas to B~at Comments asASC X12 Model Guidelin

Dow MW Doe:

Sdwommkwec X12C bat empowered its Task Group 19 toProvide respoins to the cmaca m onh" beflo Themembers ofTGI9 wish to dhank AD =l members who wook the time snd edan to 'ac an the gidehe. WeusPeiafly than cadh bnnlvWu w~ho provid coameata, whther as approval or disapproval of the goidelise. Wemucovipm sd appredtew yaw careful review of thks docmeat.

Ow respans is kgyad to the smibered tems a the umnew suattahed to yomw baf&t

L We Was with yoaw gome. is Sgedo. 4.2., we hew rephed -ft mcfe MWb _ with ovule _ amubdhed.

2.ruThe a imsbetween Sectias 4.3 andSeeios6.2 only dsbecam ofd teumaple we chas m. the kmscme rok.~io a hypothetical ape.ala ipl'fledmodeL Headersaand em canbe poad onthewoaetmatALL levels. nd drn so msocuani coespoomd to ASC X12 heade s aid tawlerL

I We agroe wih yaw mmmwm. Secdoo 6.2 has been changd so that Vohe tabliknea of -0 was added to ktem1 and 4.

BASELINE AS OF: JANUARY 23,13 IM.1


5.0 GLOSSARY

This chapter contains ASC X12 and DoD specific glossaries.

5.1 X12 GLOSSARY

ANSIAmerican National Standards Institute

ANSI StandardA document published by ANSI that has been approved throughthe consensus process of public announcement and review. Eachof these standards must have been developed by an ANSI commit-tee and must be revisited by that committee within 5 years forupdate. See Draft Standard for Trial Use (DSTU).

Area Transaction SetIdentifies a predefined area within a transaction set (header, detail,summary) containing segments and their various attributes.

ASC X12Accredited Standards Committee, X12 comprises industry mem-bers who create EDI standards for submission to ANSI for sub-sequent approval and dissemination; or for submission to theUN/ECE for approval and submission of UN/EDIFACT stan-dards.

AuthenticationA mechanism which allows the receiver of an electronic transmis-sion to verify the sender and the integrity of the content of thetransmission through the use of an electronic "key" or algorithmwhich is shared by the trading partners. This is sometimes referredto as an electronic signature.

Compliance CheckingA checking process that is used to ensure that a transmissioncomplies with ANSI X12 syntax rules.

Conditional (C)A data element requirement designator which indicates that thepresence of a specified data element is dependent on the value orpresence of other data elements in the segment. The conditionmust be stated and must be computer processable.

Control SegmentA Control Segment has the same structure as a Data Segment butis used for transferring control information for grouping datasegments. Control Segments are Loop Control Segments (LS/LE),Transaction Set Control Segments (ST/SE), and Functional GroupControl Segments (GS/GE), defined in X12.6, and InterchangeControl Segments (ISA/IEA/TAI) defined in X12.5.

BASEUNE AS OF: JANUARY 29,1993 S.0.1


Data Element

The basic units of information in the EDI standards containing aset of values that represent a singular fact. They may be single-character codes, literal descriptions, or numeric values.

Data Element LengthThis is the range, minimum to maximum, of the number of char-acter positions available to represent the value of a data element.A data element may be of variable length with range from mini-mum to maximum, or it may be of fixed length in which theminimum is equal to the maximum.

Data Element Reference NumberReference number assigned to each data element as a uniqueidentifier.

Data Element Requirement DesignatorA code defining the need for a data element value to appear in thesegment if the segment is transmitted. The X12 codes are man-datory (M), optional (0), or conditional (C). DoD may "require"a segment which is optional by X12 standards.

Data Element SeparatorA unique character preceding each data element that is used todelimit data elements within a segment. Dod uses "*" as thedelimiter.

Data Element TypeA data element may be one of six types: numeric, decimal,identifier, string, date, or time.

DelimitersThe delimiters consist of two levels of separators and a terminator.The delimiters are an integral part of the transferred data stream.Delimiters are specified in the interchange header and may not beused in a data element value elsewhere in the interchange. Fromhighest to lowest level, the separators and terminator are segmentterminator and data element separator.

DISA

Data Interchange Standards Association. A nonprofit organizationfunded by ASC X12 members which serves as the Secretariat forX12.

DSTUDraft Standard for Trial Use. Represents a document approved forpublication by the full X12 committee following membership con-sensus and subsequent resolution of negative votes. (Final Reportof X12 Publications Task Group). The Draft EDI Standard forTrial Use document represents an ASC X12 approved standard foruse prior to approval by ANSI. See ANSI Standard.



EDIElectronic Data Interchange. The computer application to com-puter application exchange of business information in a standardformat.

Electronic EnvelopeElectronic information which binds together a set of transmitteddocuments being sent from one sender to one receiver.

Element DelimiterA single-character which follows the segment identifier andseparates each data element in a segment except the last.

Functional GroupA group of one or more transaction sets bounded by a functionalgroup header segment and a functional group trailer segment.

Functional Group SegmentsGS/GE segments identify a specific functional group of documentssuch as purchase orders.

Industry ConventionsDefines how the ASC X12 standards are used by the specificindustry

Industry GuidelinesDefines the EDI environment for using cnnventions within anindustry. It provides assistance on how to unplement X12 stand-ards.

Interchange Control SegmentsISA/IEA segments identify a unique interchange being sent fromone sender to one receiver (see electronic envelope).

Interchange Control StructureThe interchange header and trailer segments envelop one or morefunctional groups or interchange-related control segments and per-form the following functions: (1) defines the data elementseparators and the data segment terminators, (2) identifies thesender and receiver, (3) provides control information for the inter-change, and (4) allows for authorization and security information.(X12.5)

LoopA group of semantically related segments; these segments may beeither bounded or unbounded (X12.6). The NI loop is an exampleof a loop, which includes segments NI to PER for name andaddress information.

Mandatory (M)A data element/segment requirement designator which indicatesthe presence of a specified data element is required.



MappingThe process of identifying the standard data element's relationshipto application data elements.

Max UseSpecifies the maximum number of times a segment can be used atthe location in a transaction set

MessageEntire data stream including the outer envelope

Optional (0)A data element/segment requirement designator which indicatesthe presence of a specified data element/segment is at the optionof the sending party which can be based on the mutual agreementof the interchange parties.

QualifierA data element which identifies or defines a related element, setof elements, or a segment. The qualifier contains a code takenfrom a list of approved codes.

Repeating SegmentA segment that may be used more than once at a given locationin a transaction set. See Max Use.

SecuritySystem screening which denies access to unauthorized users andprotects data from unauthorized uses

SegmentSegments consist of logically related data elements in a definedsequence. A data segment consists of a segment identifier, one ormore data elements each preceded by an element separator, andends with a segment terminator.

Segment DirectoryProvides the purpose and format of the segments used in theconstruction of transaction sets. The directory lists each segmentby name, purpose, identifier, the contained data elements in thespecified order, and the requirement designator for each dataelement.

Segment IdentifierA unique identifier for a segment composed of a combination oftwo or three upper-case letters and digits. The segment identifieroccupies the first-character positions of the segment. The segmentidentifier is not a data element. The segment identifier inEDIFACT is a component data element - part of a compositedata element consisting of a segment identifier and an explicitlooping designator.



Segment TerminatorA unique character appearing at the end of a segment to indicatethe termination of the segment. e.g., N/L.

SyntaxThe grammar or rules which define the structure of the EDIstandards (i.e., the use of loops, qualifiers, etc.). Syntax rules arepublished in ANSI X12.6.

Transaction SetThe transaction set unambiguously defines, in the standard syntax,information of business or strategic significance and consists of atransaction set header segment, one or more data segments in aspecified order, and a transaction set trailer segment.

Transaction Set IDAn identifier that uniquely identifies the transaction set. Thisidentifier is the first data element of the transaction set headersegment.

TranslationThe act of accepting documents in other than standard format andtranslating them to the standard.

Version/Release

Identifies the publication of the standard being used for the genera-tion or the interpretation of data in the X12 standard format. Maybe found in the Functional Group Header Segment (GS) and in theInterchange Control Header Segment (ISA). See Control Segment.

VICS CommitteeVoluntary Interindustry Communications Standards for ElectronicData Interchange

X12

The ANSI committee responsible for the development and main-tenance of standards for electronic data interchange (EDI).

X12.5Interchange Control Structure. This standard provides the inter-change envelope of a header and trailer for the electronic inter-change through a data transmission, and it provides a structure toacknowledge the receipt and processing of this envelope.

X 12.6Application Control Structure. This standard describes the controlsegments used to envelop loops of data segments, to enveloptransaction sets, and to envelop groups of related transaction sets.

BASEUNE AS OF: JANUARY 29,1993 $.0.

i l ii I I I I I• . . .


5.2 DoD GLOSSARY

AIS

Automated Information Systems

ASD(P&L)Assistant Secretary of Defense (Production and Logistics)

DESData Encryption Standard

DISADefense Information Systems Agency

DLADefense Logistics Agency

ISAInterchange Control Header Identifier

NISTNational Institute of Standards and Technology

NTENote Identifier

PLUSProtection of Logistics Unclassified/Sensitive Systems

UN/EDIFACTEDIFACT; Electronic Data Interchange for Administration, Com-merce, and Transport


Form ApprovedREPORT DOCUMENTATION PAGE OPM No. 0704-0188

Public reporting burden for this collection of information is estimated to average I hour per response, including the time for reviewing instructions, searching existing data sourcesgathering, and maintaining the data needed, and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection ofinformation. including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for information Operations and Reports. 1215 Jefferson Davis Highway, Suite1204, Arlington. VA 22202-4302, and to the Office of Information and Regulatory Affairs. Office of Management and Budget, Washington, DC 20503.

1. AGENCY USE ONLY (Leave Blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED

Jan 93 Draft

4. TITLE AND SUBTITLE 5. FUNDING NUMBERS

DoD Electronic Data Interchange (EDI) Convention: C MDA903-90-C-0006ASC X12 Transaction Set 836 Contract Award (Version 003010) PE 0902198D

6. AUTHOR(S)

Stephen LusterRichard Modrowski

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) S. PERFORMING ORGANIZATION

Logistics Management Institute REPORT NUMBER

6400 Goldsboro Road LMI-DL203LN14Bethesda, MD 20817-5886

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING/MONITORING

DoD Executive Agent for EC/EDU/PLUS AGENCY REPORT NUMBER

Defense Logistics AgencyDLA-ZIE, Cameron StationAlexandria, VA 22304

11. SUPPLEMENTARY NOTES

Prepared in cooperation with Data Interchange Standards Association, the Secretariat and administrative arm of the Accredited Standards

Committee X12

12a. DISTRIBUTION/AVAILABILITY STATEMENT 12b. DISTRIBUTION CODE

A: Approved for public release; distribution unlimited

13. ABSTRACT (Maximum 200 words)

This is an Electronic Data Interchange (EDI) systems design document that describes the standards or "convention" the Department of

Defense I DoD) will use to transmit a Contract Award using the ASC X12 Transaction Set 836 Contract Award (003010).

14. SUBJECTTERMS 15. NUMBER OFPAGES

Electronic Data Interchange; EDI; DoD EDI Convention: Electronic Commerce; ANSI X 12; X 12; electronic 70

standards; electronic business standards. computer-to-computer exchange of data; electronic documents; 16. PRICE CODEelectronic records; paperless environment; conventions

17. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 19. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACTOF REPORT OF THIS PAGE OF ABSTRACT L

Unclassified Unclassified Unclassified

NSN 7540-01-280-5S00 Standard Form 295. (Rev. 2 -89)Prescribed by ANSI Sto. 239 16M99-01

dod electronic data interchange (edi) convention dtic · application advice transaction set (824)...

Documents