DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 1 February 24, 2022

650 Maintenance Service Order

Functional Group=MO

Purpose: This Draft Standard for Trial Use contains the format and establishes then data contents of the Maintenance Service Order

Transaction Set (650) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides a uniform,

singular medium for the exchange of maintenance related information among organizations involved in the reporting, requesting, scheduling,

planning, estimating, coordinating and performing of maintenance actions. It provides the structure to convey maintenance-related information,

including maintenance action directives, maintenance actions, cost estimates, maintenance action assignments, maintenance action status,

and completion reports. This transaction set can be used in a bi-directional environment alone or in conjunction with the Project Schedule

Reporting Transaction Set (806) to link schedule and maintenance action information as well as with the Specifications/Technical Information

Transaction Set (841) to link maintenance-related, media independent, technical data.

DLMS Note:

1. This transaction set is used by the Assembly Manager to provide Unit Assembly data to the Assembly Activity. The transaction may be

used by the Assembly Activity to enter corrections, provide missing data and may also be used to transmit local changes and history data to

the Assembly Manager. 

a. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS

2. This DLMS IC was developed in support of the U.S. Army Medical Materiel Agency (USAMMA) Enterprise Resource Planning (ERP)

modernization program. This functionality is an enhancement over current Defense Logistics Standard System (DLSS), and is not available

in the DLSS. This DLMS IC supports functionality of the non-DLSS C-Series Document Identifier codes C2A (Unit Assembly End Item

Data), C2B (Unit Assemblage Control Data), and C2D (Assembly Directive Component Item Data).

3. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. 

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data which is retained in the DLMS for a transition period to support transaction conversion in a mixed DLSS (and non-DLSS

C-series)/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment. 

c. Data elements which have an expanded field size above existing DLSS (or non-DLSS C-series) capability which may not be supported by

the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

4. This revision to the DLMS IC incorporates Proposed DLMS Change and Approved DLMS Change (ADC) listed. PDCs/ADCs are available

from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 149, DLMS Supplements 650A, Support of Medical Requirements for Assembly Component Maintenance Structure

- ADC 149A, Correction to DLMS Supplements 650A in Support of Requirements for the Medical Unit Assembly Program

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- Administrative update completed on October 05, 2011 to add migration code note for Hazardous Characteristics Code.

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on April 15, 2014.

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 21, 2016

- ADC 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

August 09, 2018

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on February 24, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

1. This transaction set is used by the Assembly Manager to provide Unit Assembly data to the Assembly Activity. The transaction may be

used by the Assembly Activity to enter corrections, provide missing data and may also be used to transmit local changes and history data to

the Assembly Manager. 

a. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS

2. This DLMS IC was developed in support of the U.S. Army Medical Materiel Agency (USAMMA) Enterprise Resource Planning (ERP)

modernization program. This functionality is an enhancement over current Defense Logistics Standard System (DLSS), and is not available

in the DLSS. This DLMS IC supports functionality of the non-DLSS C-Series Document Identifier codes C2A (Unit Assembly End Item

Data), C2B (Unit Assemblage Control Data), and C2D (Assembly Directive Component Item Data).

3. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. 

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data which is retained in the DLMS for a transition period to support transaction conversion in a mixed DLSS (and non-DLSS

C-series)/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment. 

c. Data elements which have an expanded field size above existing DLSS (or non-DLSS C-series) capability which may not be supported by

the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

4. This revision to the DLMS IC incorporates Proposed DLMS Change and Approved DLMS Change (ADC) listed. PDCs/ADCs are available

from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 149, DLMS Supplements 650A, Support of Medical Requirements for Assembly Component Maintenance Structure

- ADC 149A, Correction to DLMS Supplements 650A in Support of Requirements for the Medical Unit Assembly Program

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- Administrative update completed on October 05, 2011 to add migration code note for Hazardous Characteristics Code.

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on April 15, 2014.

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 21, 2016

- ADC 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

August 09, 2018

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on February 24, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BGN Beginning Segment M 1 Must use

0300 REF Reference Identification O >1 Used

0400 DTM Date/Time Reference O >1 Used

LOOP ID - N1 LOOP ID - N1 >1 N1/0500L N1/0500L
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F650A0AA05 2 February 24, 2022

0500 N1 Name O 1 N1/0500 Used

* 0600 N2 Additional Name Information O 2

* 0700 N3 Address Information O 2

* 0800 N4 Geographic Location O 1

* 0900 PER Administrative Communications

Contact

O >1

* 1000 REF Reference Identification O >1

* LOOP ID - LM * LOOP ID - LM >1

* 1100 LM Code Source Information O 1

* 1200 LQ Industry Code M >1

* 1300 PER Administrative Communications

Contact

O >1

* 1400 REF Reference Identification O >1

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL >1 N2/0100L N2/0100L

0100 HL Hierarchical Level M 1 N2/0100 Must use

* 0200 SPI Specification Identifier O 1

0300 REF Reference Identification O >1 Used

0400 LIN Item Identification O >1 Used

* 0500 DTM Date/Time Reference O >1

0600 QTY Quantity O >1 Used

0700 YNQ Yes/No Question O >1 N2/0700 Used

0800 AMT Monetary Amount O >1 Used

* 0900 PCT Percent Amounts O >1

1000 MEA Measurements O >1 Used

* LOOP ID - CLI * LOOP ID - CLI >1

* 1100 CLI Cost Line Item O 1

* 1200 QTY Quantity O >1

* 1300 AMT Monetary Amount O >1

* 1400 RPA Rate Amounts or Percents O >1

LOOP ID - LM LOOP ID - LM >1 N2/1500L N2/1500L

1500 LM Code Source Information O 1 N2/1500 Used

1600 LQ Industry Code M >1 Must use

* 1700 REF Reference Identification O >1

* 1800 DTM Date/Time Reference O >1

* LOOP ID - NM1 * LOOP ID - NM1 >1 N2/1900L N2/1900L

* 1900 NM1 Individual or Organizational Name O 1 N2/1900

* 2000 N2 Additional Name Information O 2

* 2100 N3 Address Information O 2

* 2200 N4 Geographic Location O 1

* 2300 COM Communication Contact

Information

O >1

* 2400 REF Reference Identification O >1

LOOP ID - MTX LOOP ID - MTX >1

2500 MTX Text O 1 Used

* 2600 DTM Date/Time Reference O >1

* 2700 NM1 Individual or Organizational Name O >1

* 2800 REF Reference Identification O >1

2900 SE Transaction Set Trailer M 1 Must use
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 3 February 24, 2022

Notes: 

1/0500L The N1 segment identifies the organization originating and receiving the transaction set.

1/0500 The N1 segment identifies the organization originating and receiving the transaction set.

2/0100L The HL levels are group work candidate and work candidate. Valid HL parent-child relationships are 1) group work

candidate-group work candidate and 2) group work candidate-work candidate.

2/0100 The HL levels are group work candidate and work candidate. Valid HL parent-child relationships are 1) group work

candidate-group work candidate and 2) group work candidate-work candidate.

2/0700 The YNQ segment identifies conditions related to a maintenance or repair requirement.

2/1500L The LM loop identifies management data that pertains to each use of the HL loop.

2/1500 The LM loop identifies management data that pertains to each use of the HL loop.

2/1900L The NM1 segment identifies individuals and organizations involved in identifying, coordinating or performing maintenance.

2/1900 The NM1 segment identifies individuals and organizations involved in identifying, coordinating or performing maintenance.
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 4 February 24, 2022

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Must use

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

Semantics: 

1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction

set definition (e.g., 810 selects the Invoice Transaction Set).

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate

implementation convention to match the transaction set definition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 314, Included: 1)

Code Name

650 Maintenance Service Order

ST02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: A unique number assigned by the

originator of the transaction set, or the originator's

application program.

M AN 4/9 Must use

ST03 1705 Implementation Convention Reference

Description: Reference assigned to identify

Implementation Convention

DLMS Note: Use to indicate this transmission uses

the 650A DLMS Implementation Convention (IC). 

Enter the DLMS IC 004030F650A0AA00

O AN 1/35 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 5 February 24, 2022

BGN Beginning Segment Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 5

User Option (Usage): Must use

Purpose: To indicate the beginning of a transaction set

Syntax Rules: 

1. C0504 - If BGN05 is present, then BGN04 is required.

Semantics: 

1. BGN02 is the transaction set reference number.

2. BGN03 is the transaction set date.

3. BGN04 is the transaction set time.

4. BGN05 is the transaction set time qualifier.

5. BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

BGN01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 2)

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

Use to identify a simulated mobilization exercise transaction set. Activities initiating simulated

mobilization exercises must ensure complete coordination with all activities involved. All transaction set

recipients must use extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.

BGN02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

DLMS Note: Use code 'Z' for this data element to

satisfy mandatory X12 Requirements.

M AN 1/50 Must use

BGN03 373 Date

Description: Date expressed as CCYYMMDD

where CC represents the first two digits of the

calendar year

DLMS Note: This date corresponds to the Universal

Time Coordinate (UTC).

M DT 8/8 Must use

BGN07 640 Transaction Type Code

Description: Code specifying the type of

transaction

O ID 2/2 Used

CodeList Summary (Total Codes: 500, Included: 1)

Code Name

WO Work Order

DLMS Note:

For Medical use in transaction for transmission of a request for assembly maintenance action.

BGN08 306 Action Code O ID 1/2 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F650A0AA05 6 February 24, 2022

Description: Code indicating type of action

CodeList Summary (Total Codes: 311, Included: 3)

Code Name

2 Change (Update)

DLMS Note:

For Medical use in transaction for transmission of a request to add or change an assembly maintenance

action.

3 Delete

DLMS Note:

For Medical use in transaction for transmission of a request to delete an assembly maintenance action. 

Applies to Component data information.

17 Create

DLMS Note:

For Medical use in transaction for initial transmission of a request for assembly maintenance action.
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 7 February 24, 2022

REF Reference Identification Pos: 0300 Max: >1

Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

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

DLMS Note:

Must use this 1/REF/0300 to identify the Build Directive Number for this transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1631, Included: 5)

Code Name

89 Assembly Number

DLMS Note:

For Medical use in transactions to identify the Unit Assembly Number for medical/surgical component

assembly.

IQ End Item

DLMS Note:

1. For Medical use in transactions to identify the End Item Receipt Document Number for

medical/surgical component assembly.

2. End Item Receipt Document Number accommodates a DSCP requirement. The USAMMA ERP does

not use this data.

JB Job (Project) Number

DLMS Note:

For Medical use in transactions to identify the Project Order Number for medical/surgical component

assembly.

TN Transaction Reference Number

DLMS Note:

Use to identify the transaction number. This is the customer's document number.

WO Work Order Number

DLMS Note:

For Medical use in transactions to identify the Build Directive Number for medical/surgical component

assembly. 

A data maintenance action was approved in version 5010. The approved code/name is “BDN - Build

Directive Number”.

REF02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/50 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 8 February 24, 2022

DTM Date/Time Reference Pos: 0400 Max: >1

Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

2. C0403 - If DTM04 is present, then DTM03 is required.

3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date or time,

or both date and time

DLMS Note: The following codes are authorized.

M ID 3/3 Must use

CodeList Summary (Total Codes: 1226, Included: 1)

Code Name

RFD Requested Finish

DLMS Note:

For Medical use in transactions to identify the Build Completion Date for medical/surgical component

assembly.

DTM02 373 Date

Description: Date expressed as CCYYMMDD

where CC represents the first two digits of the

calendar year

X DT 8/8 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 9 February 24, 2022

N1 Name Pos: 0500 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

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

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

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

Comments: 

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

DLMS Note:

1. Must use the 1/N1/0500 loop to identify the organization to receive the transaction set and the organization originating the transaction set.

2. May use additional iterations of the 1/N1/0500 loop to identify other organizations associated the transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1446, Included: 3)

Code Name

ST Ship To

DLMS Note:

For Medical use in transactions to identify the assembly final destination.

WZ Final Maintenance Organization

DLMS Note:

1. For Medical use transactions to identify [final] assembly/maintenance organization for

medical/surgical component assembly. This organization will complete kit assemblies and ship to final

destination activity.

2. This qualifier represents the Assembly Activity.

Z4 Owning Inventory Control Point

DLMS Note:

1. For Medical use in transactions to identify the supply source.

2. This qualifier represents the Assembly Manager.

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Used

CodeList Summary (Total Codes: 223, Included: 2)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

M4 Department of Defense Routing Identifier Code (RIC)
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F650A0AA05 10 February 24, 2022

N104 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Used

N106 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

O ID 2/3 Used

CodeList Summary (Total Codes: 1446, Included: 2)

Code Name

FR Message From

DLMS Note:

Use with the appropriate 1/N101/0500 code to indicate that the organization cited in N104 is originating

the transaction set.

TO Message To

DLMS Note:

Use with the appropriate 1/N101/0500 code to indicate that the organization cited in N104 is the action

organization receiving the transaction set.
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 11 February 24, 2022

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 4

User Option (Usage): Must use

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL

segment and would be incremented by one in each subsequent HL segment within the transaction.

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

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in

the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring

to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

DLMS Note:

For use in End Item Data, Assemblage Control Data, and Component Data loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

HL01 628 Hierarchical ID Number

Description: A unique number assigned by the

sender to identify a particular data segment in a

hierarchical structure

DLMS Note: In the first 2/HL/0100 loop iteration,

cite numeric 1. In each subsequent loop iteration,

increase incrementally by 1.

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of the next

higher hierarchical data segment that the data

segment being described is subordinate to

O AN 1/12 Used

HL03 735 Hierarchical Level Code

Description: Code defining the characteristic of a

level in a hierarchical structure

M ID 1/2 Must use

CodeList Summary (Total Codes: 218, Included: 3)

Code Name

A Assembly

DLMS Note:

For Medical use in Assemblage Control Data (DIC C2B) loop.

F Component

DLMS Note:

For Medical use in Component Data (DIC C2D) loop. 

EN End Item

DLMS Note:

For Medical use in End Item Data (lDIC C2A) loop.

HL04 736 Hierarchical Child Code

Description: Code indicating if there are

hierarchical child data segments subordinate to the

O ID 1/1 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F650A0AA05 12 February 24, 2022

level being described

All valid standard codes are used. (Total Codes:

2)
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 13 February 24, 2022

REF Reference Identification Pos: 0300 Max: >1

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

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

DLMS Note:

For Medical use in Assemblage Control Data (C2B) loops and Component Data (C2D) loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1631, Included: 2)

Code Name

55 Sequence Number

DLMS Note:

For Medical use in Component Data loops to identify the Sort Sequence.

QQ Unit Number

DLMS Note:

For Medical use in Assemblage Control Data loops to identify the Assembly Control Number for

medical/surgical component assembly. 

A data maintenance action was approved in version 5010. The approved code/name is “CAN –

Assembly Control Number”.

REF02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/50 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 14 February 24, 2022

LIN Item Identification Pos: 0400 Max: >1

Detail - Optional

Loop: HL Elements: 6

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No.,

ISBN No., Model No., or SKU.

DLMS Note:

1. Use in 2/HL/0100 transaction loops to identify the materiel.

2. For Medical use in End Item Data (C2A) loop, Assemblage Control Data (C2B) loops and Component Data (C2D) loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

CodeList Summary (Total Codes: 505, Included: 3)

Code Name

A3 Locally Assigned Control Number

DLMS Note:

Must use with the Assemblage Control Data (C2B) loop, to identify the Assemblage Identification

Number (AIN).

FS National Stock Number

DLMS Note:

Must use with the Component Data (C2D) loop only, to identify the stock number.

SW Stock Number

DLMS Note:

Must use with the End Item Data (C2A) loop only, to identify the End Item Stock Number.
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 15 February 24, 2022

LIN03 234 Product/Service ID

Description: Identifying number for a product or

service

M AN 1/48 Must use

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: For Medical use in End Item Data and

Component Data loops.

X ID 2/2 Used

CodeList Summary (Total Codes: 505, Included: 1)

Code Name

OE Original Equipment Number

DLMS Note:

Use in Component Data loops to identify the Original Component Stock Number for medical/surgical

component assembly.

LIN05 234 Product/Service ID

Description: Identifying number for a product or

service

DLMS Note: For Medical use in the Component

Data loop.

X AN 1/48 Used

LIN06 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: 1. For Medical use in the Component

Data loop.

2. The following codes are authorized.

X ID 2/2 Used

CodeList Summary (Total Codes: 505, Included: 3)

Code Name

N4 National Drug Code in 5-4-2 Format

DLMS Note:

Use only to identify a National Drug Code. NSN must be identified in LIN02/03.

VC Vendor's (Seller's) Catalog Number

DLMS Note:

Use only to identify the Prime Vendor's Catalog Number. NSN must be identified in LIN02/03.

VP Vendor's (Seller's) Part Number

DLMS Note:

Use only to identify the Prime Vendor's Part Number. NSN must be identified in LIN02/03.

LIN07 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 16 February 24, 2022

QTY Quantity Pos: 0600 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

1. R0204 - At least one of QTY02 or QTY04 is required.

2. E0204 - Only one of QTY02 or QTY04 may be present.

Semantics: 

1. QTY04 is used when the quantity is non-numeric.

DLMS Note:

1. Use in 2/HL/0100 transaction loops to identify the quantity being requested.

2. For Medical use in End Item Data (C2A) and Component Data (C2D) loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

QTY01 673 Quantity Qualifier

Description: Code specifying the type of quantity

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

CodeList Summary (Total Codes: 976, Included: 4)

Code Name

63 On Order Quantity

DLMS Note:

1. Use to identify the number of assemblies being requested, Total Number of Assemblages in End Item

Data loop. 

2. Use to identify the quantity of each component that is to be placed in an assembly, Basic Quantity in

the Component Data loop.

AP Order Quantity Multiple

DLMS Note:

Use to identify the Extended Quantity of a component part in an assembly in the Component Data loop.

SH Shortage

DLMS Note:

Use to identify the Quantity Authorized Short of a component part in an assembly in the Component

Data loop.

T5 Total Number of Units

DLMS Note:

Use as needed in the end item data loop to identify the total number of lines in the Assemblage

Identification Number (AIN).

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Express as whole number with no

decimals.

2. A field size exceeding 5 positions may not be

received or understood by the recipient's automated

processing system. See introductory DLMS note 3c.

X R 1/15 Used

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for examples of

O Comp Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F650A0AA05 17 February 24, 2022

use)

QTY03-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

measurement has been taken

DLMS Note: 1. Use to identify the unit of issue for

materiel requested.

2. For use with QTY01 codes 63, AP, and SH. 

3. DLMS users see the DLMS Unit of Issue and

Purchase Unit Conversion Table for available codes.

M ID 2/2 Must use

QTY03-04 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

measurement has been taken

DLMS Note: 1. For Medical use in Component Data

loops to identify the Unit of Measure for materiel

requested. Use in conjunction with QTY01 code

'63'.

2. DLMS users see the DLMS Unit of Issue and

Purchase Unit Conversion Table for available codes.

O ID 2/2 Used

QTY03-06 649 Multiplier

Description: Value to be used as a multiplier to

obtain a new value

DLMS Note: For Medical use in Component Data

loops to identify the Measurement Quantity for

materiel requested. Use in conjunction with QTY01

code '63'.

O R 1/10 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 18 February 24, 2022

YNQ Yes/No Question Pos: 0700 Max: >1

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

Syntax Rules: 

1. E010910 - Only one of YNQ01, YNQ09 or YNQ10 may be present.

2. P0304 - If either YNQ03 or YNQ04 is present, then the other is required.

3. C0908 - If YNQ09 is present, then YNQ08 is required.

Semantics: 

1. YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N"

indicates the statement is denied.

2. YNQ10 contains a free-form question when codified questions are not available.

DLMS Note:

For Medical use in Component Data (C2D) loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

YNQ01 1321 Condition Indicator

Description: Code indicating a condition

X ID 2/2 Used

CodeList Summary (Total Codes: 1250, Included: 1)

Code Name

ZZ Mutually Defined

DLMS Note:

Use in Component Data (C2D) loops to identify the Inspection Required Indicator for medical/surgical

component assembly.

A data maintenance action was approved in version 5030. The approved code/name is "CAI –

Component Assembly Inspection Required".

YNQ02 1073 Yes/No Condition or Response Code

Description: Code indicating a Yes or No condition

or response

M ID 1/1 Must use
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 19 February 24, 2022

AMT Monetary Amount Pos: 0800 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To indicate the total monetary amount

DLMS Note:

For Medical use in End Item Data (C2A) loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

AMT01 522 Amount Qualifier Code

Description: Code to qualify amount

DLMS Note: The following codes are authorized.

M ID 1/3 Must use

CodeList Summary (Total Codes: 1696, Included: 1)

Code Name

TC Proposed Cost

DLMS Note:

Use in End Item Data loop to identify the Assembly Estimated Cost.

AMT02 782 Monetary Amount

Description: Monetary amount

M R 1/18 Must use

AMT03 478 Credit/Debit Flag Code

Description: Code indicating whether amount is a

credit or debit

O ID 1/1 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 20 February 24, 2022

MEA Measurements Pos: 1000 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights(See Figures Appendix for

example of use of C001)

Syntax Rules: 

1. R03050608 - At least one of MEA03, MEA05, MEA06 or MEA08 is required.

2. C0504 - If MEA05 is present, then MEA04 is required.

3. C0604 - If MEA06 is present, then MEA04 is required.

4. L07030506 - If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 is required.

5. E0803 - Only one of MEA08 or MEA03 may be present.

Semantics: 

1. MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.

Comments: 

1. When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot

be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value.

DLMS Note:

1. Use multiple repetitions to identify any measurement/dimensions

2. For Medical use in the Component Data (C2D) loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

MEA01 737 Measurement Reference ID Code

Description: Code identifying the broad category to

which a measurement applies

DLMS Note: The following codes are authorized.

O ID 2/2 Used

CodeList Summary (Total Codes: 157, Included: 2)

Code Name

PD Physical Dimensions

DLMS Note:

Use in the Component Data loop to define the Unit Cube being passed in MEA03.

WT Weights

DLMS Note:

Use in the Component Data loop to define the Assembly Unit of Issue Weight being passed in MEA03.

MEA02 738 Measurement Qualifier

Description: Code identifying a specific product or

process characteristic to which a measurement

applies

DLMS Note: 1. Use to identify the specific

dimension/measurement quantified in MEA03.

2. The following codes are authorized.

O ID 1/3 Used

CodeList Summary (Total Codes: 959, Included: 2)

Code Name

U Weight per Unit

DLMS Note:

Use in the Component Data loop to define the Assembly Unit of Issue Weight being passed in MEA03.
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

Code Name

004030F650A0AA05 21 February 24, 2022

UCB Cube

DLMS Note:

Use in the Component Data loops to define the Unit Cube being passed in MEA03.

MEA03 739 Measurement Value

Description: The value of the measurement

X R 1/20 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 22 February 24, 2022

LM Code Source Information Pos: 1500 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use this 2/LM/1500 loop to identify coded information maintained in department or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LM01 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

M ID 2/2 Must use

CodeList Summary (Total Codes: 187, Included: 1)

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 23 February 24, 2022

LQ Industry Code Pos: 1600 Max: >1

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

1. Use to identify codes, as appropriate, consistent with management information requirements.

2. For Medical use in the End Item Data (C2A), Assemblage Control Data (C2B), and the Component Data (C2D) loops as required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

DLMS Note: The following codes are authorized.

O ID 1/3 Used

CodeList Summary (Total Codes: 769, Included: 7)

Code Name

0 Document Identification Code

DLMS Note:

1. The DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS

environment. Continued support of the DIC in a full DLMS environment will be assessed at a future

date.

2. Use in the End Item Data, Assemblage Control, and Component Data loops.

3. Future streamlined data; see introductory DLMS note 3b.

33 Air Commodity and Special Handling Code

DLMS Note:

Use in the Component Data loop to identify the Air Commodity and Special Handling Code.

34 Water Commodity and Special Handling Code

DLMS Note:

Use in the Component Data loop to identify the Water Commodity and Special Handling Code.

AL Special Requirements Code

DLMS Note:

1. Use to identify precedence, special handling, and processing requirements.

2. Use in the Component Data loop to identify the Special Requirements Code.

EQ Controlled Inventory Item Code

DLMS Note:

Use in the Component Data loop to identify the Controlled Inventory Item Code.

FE Shelf Life Code

DLMS Note:

Use in the Component Data loop to identify the Shelf Life Code.

HMC Hazardous Material Content Code 

DLMS Note:

1. Use in the Component Data loop to identify the "Hazardous Characteristics Code”.

2. Implementation Note: This is an X12 Migration Code approved for use in Version 5020. 

Implementers must manually update 4030 software to recognize this code.
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 24 February 24, 2022

LQ02 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 25 February 24, 2022

MTX Text Pos: 2500 Max: 1

Detail - Optional

Loop: MTX Elements: 2

User Option (Usage): Used

Purpose: To specify textual data

Syntax Rules: 

1. C0102 - If MTX01 is present, then MTX02 is required.

2. C0302 - If MTX03 is present, then MTX02 is required.

3. C0504 - If MTX05 is present, then MTX04 is required.

Semantics: 

1. MTX05 is the number of lines to advance before printing.

Comments: 

1. If MTX04 is "AA - Advance the specific number of lines before print", then MTX05 is required.

DLMS Note:

For Medical use in End Item Data (C2A) and Component Data (C2D) loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

MTX01 363 Note Reference Code

Description: Code identifying the functional area or

purpose for which the note applies

O ID 3/3 Used

CodeList Summary (Total Codes: 342, Included: 1)

Code Name

IID Inventory (Stock) Description

DLMS Note:

1. Use to identify the Assembly Nomenclature in the End Item Data loop.

2. Use to identify the Component Nomenclature in the Component Data loop.

MTX02 1551 Message Text

Description: To transmit large volumes of message

text

X AN 1/4096 Used
DLMS Implementation Convention (IC) 650A Assembly Component Maintenance

Structure

ADC 149A, 436, 1043C, 1254, 1367 and 1412 DLM

4000.25

004030F650A0AA05 26 February 24, 2022

SE Transaction Set Trailer Pos: 2900 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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

(SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SE01 96 Number of Included Segments

Description: Total number of segments included in

a transaction set including ST and SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: Cite the same number as the one cited

in ST02.

M AN 4/9 Must use