1. X12 Standards in the DLMS—Forward Codes and Delimiters
Frank Napoli, LMI
November 16, 2017

2. Topics Forward Codes Delimiters
Decoupling Code Versions from Transaction Versions
Delimiters
Allowed Delimiter Characters in DLMS X12-based Data Exchanges

3. Forward Codes Background:
X12 versions published annually—“carved in stone”
Published versions include code values
DLMS ICs based on Version/Release 4010 (1997) and 4030 (1999)
Two types of codes:
Internal (e.g., Identification Code Qualifier, DE 66; 10=DoDAAC)
External (e.g., Zip Code, DE 116; Code Source: 51 USPS National Zip Code and Post Office Directory)

4. Forward Codes Background (continued)
New business requirements need new codes (e.g., Work Order Number—SLOA Code)
New codes added to “future” version of X12
Codes approved today would be added to 7050
DOD unlikely to migrate to newer version X12 Standards
New codes added to current (4010/4030) ICs with DLMS note identifying them as “Migration” codes
Currently this is non-compliant with the X12 Standard

5. Forward Codes Current status: “Words” solution:
Add the following paragraph to X12 guideline “Compliance in X12”
“While compliant code values for each version of X12 are documented in the published standard, new emerging business requirements often necessitate that trading partners exchange code values that are published in versions of the X12 Standard other than what is specified in the GS08 of the transmission. X12 recognizes that this business requirement is met by specifying those codes in an industry-approved implementation guide or by mutual trading partner agreement prior to use.”
* (highlighting added)

6. Forward Codes Great News for DOD! Caveats:
Approved by all X12 subcommittees
Published for member vote by X12 PRB
voting closes 11/22/17
Caveats:
“Compliance in X12” is out for member vote
X12 Guidelines not part of the X12 Standard, but are approved by X12 membership at large
Codes must be added to (future) X12 Standards, and codes must be explicitly enumerated in the DLMS ICs—both are DLMS standard practices

7. Allowed DLMS Delimiters
PDC Bottom Line:
Allowed DLMS Delimiters
&
Ampersand *
Asterisk {
Open Bracket }
Closed Bracket ^
Caret “
Double Quote !
Exclamation Mark
>
Greater Than
<
Less Than %
Percent Sign |
Pipe (Vertical Bar) ;
Semicolon ‘
Single Quote ~
Tilde
Newline (Line Feed/Carriage Return) *
* Newline is an unprintable character; senders may use it only as segment terminator in X12-based DLMS transactions.

8. DLMS X12 Team Contact
Sylvia Williams DLMS Data Manager (804) Frank Napoli DLMS X12 Contractor Support (703) Group