2 

(2) The project approach is comprised of two phases. Phase I includes a look at retail 

stock transactions (e.g., DD 1348-1A), and Phase II will review nonstock transactions 

(DD 1149). 

(3) The Phase I approach focused on identifying the data requirements based on 

MILSTRIP guidance and existing nonstandard CMOS interfaces to retail supply 

systems (e.g., SBSS, CAS, DMLSS), identifying the candidate DLMS EDI/XML 

transactions, performing a gap analysis between the candidate transactions and the 

data requirements, and developing proposed courses of action in the near- and 

 long-term. 

(4) An underlying assumption to the proposed solution set is that it must entail no 

changes to legacy retail supply systems, and use existing legacy transactions to the 

maximum extent possible. 

(5) CMOS intends to implement the candidate DLMS EDI transactions in FY 2009 

(development work to go under contract in late FY 2008). DMLSS is planning to 

implement the candidate DLMS EDI transactions during the same timeframe. Other 

legacy retail supply AISs will be identified by CMOS and their trading partners and 

will be implemented when ready. 

d. Gap Analysis Validation 

(1) The group reviewed the presentation of the gaps identified by DLMSO. 

(2) Based on that review, the gaps were sorted into the following categories: 

(a) Required Legacy - Proposed DLMS Change (PDC): These gaps require a PDC 

very quickly to facilitate CMOS implementation of the candidate transactions 

with DMLSS and any legacy retail supply AIS. 

(b) Required Legacy - FLIS Web Service: These gaps require CMOS to establish a 

web service with DLIS to obtain item data associated with a particular National 

Item Identification Number (NIIN). DLIS point of contact information was 

provided to the CMOS PMO and HQ USAF via separate correspondence. 

(c) Required - CMOS Implementation: These gaps will require CMOS action to 

overcome through internal programming or manual user intervention. 

(d) Required DLMS - PDC: These gaps will require a PDC in the future when 

implementing DLMS-compliant AISs replacing legacy retail supply systems 

based on DLSS. 

(e) Required DLMS - 858B: These gaps are recommended to be filled by using the 

Defense Transportation Electronic Business (DTEB) Committee’s 858B 

transaction for the Transportation Control Movement Document. 

Attachment 1 

ATTENDEE LIST

Name Organization Note 

Ellen Hilert DLMSO 

Heidi Daverede DLMSO 

Bob Vitko DLMSO 

John Will US Transportation Command Telecon 

Dan Eastman LMI 

Frank Napoli LMI 

Harry Gore LMI 

Stuart Scott DAAS Telecon 

Bill Strickler RDSI 

Doug Mummert RDSI Telecon 

Mark Minch DAAS Telecon 

Karen Townley DAAS 

Allan Jones DAAS Telecon 

Steve Hermann DAAS Telecon 

Larry Allensworth DMLSS 

Monty Blucoft DMLSS 

Rex Geiser USAF CMOS (Gunter AFB) Telecon 

SSGT Izelu USAF CMOS (Gunter AFB) Telecon 

Gordon Allbritton USAF CMOS (Gunter AFB) Telecon 

Jim Wakeley HQ USAF 

Joe Rothrock HQMC LPD 

Sam Perez HQMC LPD 

Charlene Shannon NOLSC Telecon 

Elizabeth Mason-Jones LOGSA Telecon 

John Schwarz DLMSO 
Table of Contents (TOC)

#

2

3

4

5

6

7

10

17

18

19

20

21

22

23

24

25

26

27

28

29

30 

#

1

2

4

#

#

1

#

1

2

3

4

1 Hold Code SBSS SSC

Required DLMS - PDC

Required - CMOS Implementation

15 Item Nomenclature SBSS A2_, A4_, A5J; CAS CTR

16 Vehicle Reg, Wpns. No., SN SBSS A2_, A4_, A5J; CAS CTR

1 Demilitarization SBSS A2_, A4_, A5J; CAS CTR

8 NMFC/UFC SBSS A2_, A4_, A5J; CAS CTR

9 Type Cargo Code/Phrases

Data Source

Step 3b - Status Response (945A)

Required - CMOS Implementation

3 Hold Code SBSS SSC Required - CMOS Implementation

Required - DLMS PDC

11 Controlled Item Code SBSS A2_, A4_, A5J; CAS CTR

Gap Data Element

13 Shelf Life Code SBSS A2_, A4_, A5J; CAS CTR

14 Special Packing Instructs. SBSS A2_, A4_, A5J; CAS CTR

12 Quantity Unit Item Pack

Required DLMS - PDC

Required Legacy - FLIS Web Svc

Not required – MILS_DLMS

Required Legacy - FLIS Web Svc

Required DLMS - PDC

Required DLMS - PDC

Required Legacy - FLIS Web Svc

Required DLMS - PDC

Priority Designator

DoDIC

Inchecker Number

Shipped From

Assemblage Document #

Lead Document Number

Mark For

Extended Cost

Step 2 - Incheck/Hold Status (945A)

SBSS A2_, A4_, A5J

Various Transport Data

Gap Data Element Tab Location (Name) Data Source

Step 4b - Cancellation Response (945A)

Tab Location (Name)

Not Required - MILS_DLMS

Gap Data Element

Supply Response Status Required Legacy - PDC 

Required Legacy - PDC

Required DLMS - PDC

Required - CMOS Implementation

Required DLMS - 858B

Not required – MILS_DLMS

Not required – MILS_DLMS

Required Legacy - FLIS Web Svc

Required DLMS - PDC

Tab Location (Name) Data Source

SBSS A2_, A4_, A5J

CAS CTR

CAS CTR

Step 1 - Release Order (940R)

Gap Data Element

Consignor

TAC

RIC TO

Not required – MILS_DLMS

Required DLMS - PDC

SBSS A2_, A4_, A5J; CAS CTR

SBSS A2_, A4_, A5J

SBSS A2_, A4_

CAS CTR, CDD

SBSS A2_, A4_, A5J

CAS CTR, CDD

SBSS A2_, A4_, A5J; CAS CTR

Required Legacy - FLIS Web Svc

Required DLMS - PDC

Required Legacy - FLIS Web Svc

Required CMOS Implementation

Required DLMS - PDC

Required Legacy - FLIS Web Svc

Required Legacy - FLIS Web Svc

Required DLMS - PDC

Required DLMS - PDC

Required - CMOS Implementation

Ship To Name & Address Not required – MILS_DLMS SBSS A2_, A4_, A5J; CAS CTR

Net Explosive Weight Required DLMS 858B CAS CTR

Lot Number Required - CMOS Implementation CAS CTR

Required DLMS - 858B CAS CTR

Hazard Class/Division No. Required DLMS - 858B CAS CTR

UN/North America ID No. Required DLMS - 858B CAS CTR

Compatibility Group Code Required DLMS - 858B CAS CTR

Lot Pieces, Weight, Cube CAS CTR

Proper Shipping Name

Addt'l Req'd Hazmat Info

Container Info from TCMD

Required DLMS - 858B

Required DLMS - 858B

Required DLMS - 858B

Required DLMS - 858B CAS CTR

MILSTRIP/DLMS

SBSS SSC

Data Source

SBSS SSC

CAS CRD

SBSS A5J

DMLSS

Julian Date (Incheck Date)

Step 5 - Shipment Notification (945A)

Gap Data Element Tab Location (Name) Data Source

Cancellation Response Required Legacy - PDC MILSTRIP/DLMS

Tab Location (Name)

Inchecker Number Not Required - MILS_DLMS SBSS SSC; CAS CSI

Julian Date (Incheck Date) Not Required - MILS_DLMS SBSS SSC; CAS CSI

Lot Number Required - CMOS Implementation CAS CSI

Shipped From Required - CMOS Implementation CAS CSI

Page 1 of 1
Required Legacy - PDC

#

Assemblage Document #

Rationale

#

Supply Status response

Rationale

Recommended Solution

#

Cancellation Response

Rationale

PDC Requirement

Step 1 - Release Order (940R)

Gap Data Element

Perpetuate 940R looping association to the DTEB's 856A Due-in Notice.

No change to MILS mappings; no room in A2_, A4_, A5_ to carry this.

Issue

Recommended Solution

Not in MILSTRIP A2_, A4_, A5_

PDC Requirement

Data Source

Step 2 - Incheck/Hold Status (945A)

Gap Data Element

4

Need to distinguish 945A/AE6 status responses that are self-initiated by transportation 

versus those in response to a 940R/AF6 follow-up request

945A: Add X12 code "NO - Notice" to authorized code list for W0611. User note should 

convey that this is used by transportation to report cargo processing status prior to 

material release confirmation.

Allow AE6/945A without a related AF6/940R

Data Source

PDC Required MILSTRIP/DLMS

Disposition

PDC Required DMLSS

Gap Data Element

Step 4b - Cancellation Response (945A)

DMLSS needs to distinguish document number assigned to assemblage (kit) from multiline item contents with various NSNs, part numbers.

Not in 940R

Maintain linkage to original requisition for assembly and provide content visibility to what 

makes up the assembly at the individual line item level.

Perpetuate document number from original requisition in 940R.

Create loops to identify each of the line items by a new identification number and 

NSN/part number.

Issue

Recommended Solution

Disposition Data Source

PDC Required MILSTRIP/DLMS

Allow W0611 = NR & NT for AE6

Use LQ01 = 81/LQ02 = BF (No record of document for AC_ submitted), BQ (Cancellation 

confirmed; no longer being processed for shipment), B8 (Cancellation not processed; 

material already shipped). Use other status codes as necessary to indicate cancellation 

action taken by the transportation office.

1

30 

(New)

Create DAAS map for 945A (W0611 = NO) to AE6

940R: To be determined. Consider use of LS subloop to carry the NSN or part number 

information associated with the assembly identified in the W01 (position 200) segment.

Issue

PDC Requirement

Disposition

Be able to provide transportation processing status for incheck of cargo for transportation 

planning and transportation hold actions

Provide in processing status information to supply system prior to material release 

confirmation transaction

Create DAAS map for 945A (W0611 = NR, NT) to AE6 for transportation response to 

cancellation requests by storage activity

Need to be able to provide status codes in the cancellation response

AG6/AGJ do not allow for status codes

Be able to acknowledge action taken on a cancellation request

Use AE6 vice AG6/AGJ

Page 1 of 1
Required Legacy - FLIS Web Svc

#

Demilitarization Code

Rationale

PDC Requirement

NMFC/UFC

Rationale

PDC Requirement

Type Cargo Code/Phrases

Rationale

PDC Requirement

Controlled Item Code

Rationale

PDC Requirement

Quantity Unit Pack Code

Rationale

PDC Requirement

Shelf Life Code

Rationale

PDC Requirement

Special Packaging Instr. Nos.

Rationale

PDC Requirement

N/A

14

11

Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Option 2 - DAAS do FLIS lookup and add to 940R

N/A

9

Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Option 2 - DAAS do FLIS lookup and add to 940R

Option 3 - Manual lookup by transportation AIS user

FLIS Web Service SBSS A2_, A4_, A5J; CAS CTR

Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Option 2 - DAAS do FLIS lookup and add to 940R

Option 3 - Manual lookup by transportation AIS user

N/A

Not in MILSTRIP A2_, A4_, A5_, A5J

SBSS A2_, A4_, A5J; CAS CTR

Option 2 - DAAS do FLIS lookup and add to 940R

Issue

Recommended Solution

N/A

FLIS Web Service

Needed for freight documentation

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Option 2 - DAAS do FLIS lookup and add to 940R

Option 3 - Manual lookup by transportation AIS user

Step 1 - Release Order (940R)

Gap Data Element

Not in MILSTRIP A2_, A4_, A5_

Not in 940R (W0506 = NA, NE, NI)

Issue

Option 2 - DAAS do FLIS lookup and add to 940R

Option 3 - Manual lookup by transportation AIS user

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Needed by transportation for USML identification (SED processing)

Recommended Solution

1

13

Issue

Recommended Solution

Recommended Solution

12

8

N/A

FLIS Web Service

Disposition

FLIS Web Service

Data Source

SBSS A2_, A4_, A5J; CAS CTR

SBSS A2_, A4_, A5J; CAS CTR

N/A

Issue

Recommended Solution

FLIS Web Service SBSS A2_, A4_, A5J; CAS CTR

Issue

Recommended Solution

Option 3 - Manual lookup by transportation AIS user

N/A

FLIS Web Service SBSS A2_, A4_, A5J; CAS CTR

Issue Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

FLIS Web Service SBSS A2_, A4_, A5J; CAS CTR

Issue

Recommended Solution

Option 2 - DAAS do FLIS lookup and add to 940R

Option 3 - Manual lookup by transportation AIS user

Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Not in 940R

Needed for freight documentation

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Option 3 - Manual lookup by transportation AIS user

Page 1 of 2
Required Legacy - FLIS Web Svc

#

Step 1 - Release Order (940R)

Gap Data Element Disposition Data Source

Item Nomenclature

Rationale

PDC Requirement

Recommended Solution

N/A

15

Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Option 1 - Transportation AIS develop web service with FLIS for lookup (preferred)

Option 2 - DAAS do FLIS lookup and add to 940R

Option 3 - Manual lookup by transportation AIS user

FLIS Web Service SBSS A2_, A4_, A5J; CAS CTR

Issue

Page 2 of 2
Required - CMOS Implementation

#

RIC TO

Rationale

Recommended Solution

Vehicle Reg, Wpns No., SN

Issue

Rationale

Recommended Solution

Lot Number

Issue

Rationale

Priority Designator

Issue

Rationale

# Disposition

Julian Date (Incheck Date)

Rationale

Hold Code

Rationale

Recommended Solution

Recommended Solution

Issue

2

Step 2 - Incheck/Hold Status (945A)

Gap Data Element Data Source

Contributes to CWT

Use G6201 (Pos: 50) = BR segment to record incheck date. This segment already 

carries the date of the transaction, which was confirmed by CMOS PMO to equate to the 

incheck date when this transaction is generated.

DAAS will need to convert the CCYYMMDD from the 945A G6201 = BR segment to a 

Julian Date in the AE6 transaction, record position 62-64.

CMOS Implementation CMOS/SBSS (SSC)

28

Not in MILSTRIP A5J

MILSTRIP does not carry the supply priority for disposal release orders, since the 

underlying assumption is that it is a low priority requirement.

Manual entry by CMOS user from accompanying documentation

Use 940R LQ01 = 79 segment (position 1300) if supply system is DLMS compliant to 

carry the priority designator.

19

Not in MILSTRIP A2_, A4_, A5_

Required for CMOS freight documentation

Use 940R N901 = BT segment (position 150) if supply system is DLMS compliant to carry 

the lot numbers.

Recommended Solution Manual entry by CMOS user from accompanying documentation for other than CAS 

CMOS Implementation CAS CTR

16

Not in MILSTRIP A2_, A4_, A5_, A5J

Need to convey the vehicle registration number and serial numbers to transportation for 

inclusion in freight documentation

Manual entry by CMOS user from accompanying documentation

CMOS Implementation SBSS A2_, A4_, A5J; CAS CTR

Step 1 - Release Order (940R)

Gap Data Element

5

RIC To identifies the storage site receiving the release order from the ICP (RIC From)

Need logic for DAAS to route copies of specific transactions to certain CMOS sites

Ensure CMOS receives the release orders at the correct CMOS site

CMOS and DAAS develop RIC-DODAAC cross reference identifying which RIC TOs are 

routed to a particular CMOS DODAAC

CMOS Implementation SBSS A2_, A4_, A5J

Issue

Disposition Data Source

Issue

CMOS Implementation SBSS A5J

Recommended Solution

Need date to record when delivery process was started

Not in MILSTRIP

3

Need code in AE6 and 945A status transactions to relate that there is a delay in 

transportation processing

Normally transportation hold is conveyed in the AR_ or 945A (W0611 = NJ, NM) 

transactions

Provide in processing status information to supply system prior to material release 

confirmation transaction

As an interim solution to the legacy MILS environment, either use a status code of BD to 

signify delay or use a status code of BA with a revised estimated ship date in the G6201 

= 17 (position 50)

CMOS Implementation SBSS SSC

Page 1 of 2
Required - CMOS Implementation

#

Hold Code

Rationale

Recommended Solution

#

Shipped From

Rationale

Recommended Solution

PDC Requirement

Lot Number

Rationale

Recommended Solution

1 CMOS Implementation SBSS SSC

Issue Need code in AE6 and 945A status transactions to relate that there is a delay in 

transportation processing

Normally transportation hold is conveyed in the AR_ or 945A (W0611 = NJ, NM) 

transactions

Provide in processing status information to supply system prior to material release 

confirmation transaction

Step 3b - Status Response (945A)

3

Identify the "shipped from" source

To be determined

To be determined

CMOS Implementation CAS CSI

Issue

Not in MILS 

CMOS to verify what information is normally conveyed in this data element (i.e., 

ammunition bunker or traffic management office)

Disposition Data Source

Disposition Data Source

Step 5 - Shipment Notification (945A)

Gap Data Element

Gap Data Element

As an interim solution to the legacy MILS environment, either use a status code of BD to 

signify delay or use a status code of BA with a revised estimated ship date in the G6201 

= 17 (position 50)

4 CMOS Implementation CAS CSI

Provide visibility as to which lot numbers for a particular release order shipped on which 

day

Not all lot numbers may ship on the same day.

Keep CAS interface operational until they are DLMS compliant. Then use 945A N901 = 

BT segment (position 120) to carry the lot numbers.

Issue Not in MILSTRIP AR_

Page 2 of 2
Required DLMS - PDC

#

Demilitarization Code

Rationale

Recommended Solution

Rationale

PDC Requirement

NMFC/UFC

Rationale

Recommended Solution

Type Cargo Code/Phrases

Rationale

Recommended Solution

Lead Document Number

Rationale

Recommended Solution

PDC Requirement

Controlled Item Code

Rationale

Recommended Solution

Quantity Unit Pack Code

Rationale

Recommended Solution

Shelf Life Code

Rationale

13 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue

940R: Add LQ01/LQ02 segments for Quantity Unit Pack Code. Use X12 qualifier JD 

(Quantity Unit Pack Code). Use for W0506 = NA, NE, and NI.

No change to MILS mappings, no room in A2_, A4_, A5_, A5J to carry this.

PDC Requirement

Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

12 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Add to 940R for use by DLMS compliant systems

PDC Requirement 940R: Add LQ01/LQ02 segments for CIIC. Use X12 qualifier EQ (CIIC). Use for W0506 

= NA, NE, and NI.

No change to MILS mappings, no room in A2_, A4_, A5_, A5J to carry this.

11 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Add to 940R for use by DLMS compliant systems

PDC Requirement 940R: Add LQ01/LQ02 segments for type cargo code. Use X12 qualifier NT (Type 

Cargo Code). Use for W0506 = NA, NE, and NI.

No change to MILS mappings, no room in A2_, A4_, A5_, A5J to carry this.

To be determined.

Issue

9 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Add to 940R for use by DLMS compliant systems

PDC Requirement 940R: Add W0110 and W0111 segments for commodity code identification. Use X12 

qualifiers D (DOD Unique Commodity Code, N (NMFC), T (STCC), and U (UFC). Use for 

W0506 = NA, NE, and NI.

No change to MILS mappings, no room in A2_, A4_, A5_, A5J to carry this.

8 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Add to 940R for use by DLMS compliant systems

PDC Requirement 940R: Modify LQ01 = FD user note to expand usage to material release orders (W0506 

= NA) and redistribution/lateral distribution orders (W0506 = NI) in addition to current 

usage for disposal release orders (W0506 = NE). 

No change to MILS mappings; no room in A2_, A4_, A5_ to carry this.

Recommended Solution

940R: Add FA201 = TA with applicable TAC entered into FA202.

TAC SBSS A2_, A4_

1 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue Not in MILSTRIP A2_, A4_, A5_

Not in 940R (W0506 = NA, NE, NI)

Needed by transportation for USML identification (SED processing)

Add to 940R for use by DLMS compliant systems

4

Not in MILSRIP A2_, A4_

Not in 940R

Only Air Force has NSN to TAC code logic embedded in item data

Option 1: CMOS develop TAC code logic (see how DSS did it)

Option 2: CMOS user enter manually

Option 3: Future DLMS-DLMS implementation

Issue

Future Requirement

10

Not in the MILSTRIP A2_, A4_, A5_

Not known when the ICP releases the MRO to the storage point

CMOS needs to know which MRO is the lead document number so they create the TCN 

correctly.

To be determined.

Future Requirement CAS CTR, CDD

Not in the 940R

Step 1 - Release Order (940R)

Gap Data Element Disposition Data Source

Page 1 of 2
Required DLMS - PDC

Recommended Solution

Special Packaging Instr. Nos.

Rationale

Recommended Solution

Item Nomenclature

Rationale

Recommended Solution

Vehicle Reg, Wpns No., SN

Rationale

PDC Requirement

#

Hold Code

Rationale

Recommended Solution

PDC Requirement

#

Hold Code

Rationale

Recommended Solution

PDC Requirement

Needed for freight documentation

Add to 940R for use by DLMS compliant systems

Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

Needed for freight documentation

Add to 940R for use by DLMS compliant systems

PDC Requirement

PDC Requirement 940R: Add LQ01/LQ02 segments for Special Packaging Instructions. Use X12 qualifier 

ZZ (Mutually Defined). Use for W0506 = NA, NE, and NI.

No change to MILS mappings, no room in A2_, A4_, A5_, A5J to carry this.

940R: Modify W0106 = CN user note to eliminate restriction to use when W0104 = FT 

(FSC Identification). Use for W0506 = NA, NE, and NI.

No change to MILS mappings, no room in A2_, A4_, A5_, A5J to carry this.

940R does not carry unique qualifier for vehicle registration number

Need to convey the vehicle registration number and serial numbers to transportation for 

inclusion in freight documentation

Use the LS loop for conveying UIT information, serial numbers and vehicle registration 

numbers.

15 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue Not in MILSTRIP A2_, A4_, A5_, A5J

Not in 940R

14 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

Issue

16 Future Requirement SBSS A2_, A4_, A5J; CAS CTR

940R: Add N907 segment to carry the UII Type per UID guidance.

Issue

Recommended Solution

Serial number can be carried in the N901 = SE segment (position 150)

Vehicle registration number can be carried in the N901 = U3 (position 150)

Not in MILSTRIP A2_, A4_, A5_, A5J

PDC Requirement 940R: Add LQ01/LQ02 segments for Shelf Life Code. Use X12 qualifier FE (Shelf Life 

Code). Use for W0506 = NA, NE, and NI.

No change to MILS mappings, no room in A2_, A4_, A5_, A5J to carry this.

Add to 940R for use by DLMS compliant systems

3 CMOS Implementation SBSS SSC

Issue Need code in 945A (W0611 = NO) transactions to relate that there is a delay in 

transportation processing

Normally transportation hold is conveyed in the AR_ or 945A (W0611 = NJ, NM) 

transactions

Provide in processing status information to supply system prior to material release 

confirmation transaction

Allow use of transportation hold codes to be passed in the 945A (W0611 = NO) to 

identify the nature of the delay.

945A: For W0611 = NO transactions, add LQ01 = BC to identify the use of a 

transportation hold code and pass the actual hold code in the LQ02 using the 

transportation hold code table in TMDS

Step 2 - Incheck/Hold Status (945A)

Gap Data Element Disposition Data Source

Step 3b - Status Response (945A)

Gap Data Element Disposition Data Source

3 CMOS Implementation SBSS SSC

Issue Need code in 945A (W0611 = NL) transactions to relate that there is a delay in 

transportation processing

Normally transportation hold is conveyed in the AR_ or 945A (W0611 = NJ, NM) 

transactions

Provide in processing status information to supply system prior to material release 

confirmation transaction

Use transportation hold codes to be passed in the 945A (W0611 = NL) to identify the 

nature of the delay.

945A: For W0611 = NL transactions, add LQ01 = BC to identify the use of a 

transportation hold code and pass the actual hold code in the LQ02 using the 

transportation hold code table in TMDS

Page 2 of 2
Required DLMS - 858B

#

Net Explosive Weight

Rationale

DoDIC

Rationale

Hazard Class/Division No.

Rationale

UN/North America ID No.

Rationale

Compatibility Group Code

Rationale

Lot Pieces, Weight, Cube

Rationale

Proper Shipping Name

Rationale

Addt'l Req'd. Hazmat Info

Rationale

Recommended Solution

Issue

Recommended Solution

Issue

Recommended Solution

Issue

Recommended Solution

Issue

Recommended Solution

CAS CTR

Modified 858B CAS CTR

Modified 858B CAS CTR

Disposition Data Source

Modified 858B CAS CTR

21

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Issue

Recommended Solution

20

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Issue

Recommended Solution

Modified 858B

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Issue

Recommended Solution

Step 1 - Release Order (940R)

Gap Data Element

22

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

18

23

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Modified 858B CAS CTR

24

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Modified 858B CAS CTR

Issue

25

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Modified 858B CAS CTR

26

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Modified 858B CAS CTR

Page 1 of 2
Required DLMS - 858B

# Data Source Disposition

Step 1 - Release Order (940R)

Gap Data Element

Container Info from TCMD

Rationale

Various Transport Data Elmts

Rationale

Issue

Recommended Solution

Issue

Recommended Solution

27

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Modified 858B CAS CTR

29

Not in MILSTRIP A2_, A4_, A5_

Not in 940R

Required for freight documentation

Migrate to 858B (TCMD)

Modified 858B CAS CRD

Modify 858B BX01 segment to add a value of "14" for advance notification, to distinguish 

this from regular 858B transactions

Page 2 of 2
Not Required - MILS_DLMS

#

Shipped From

Issue

Rationale

Recommended Solution

Issue

Rationale

Recommended Solution

Extended Cost

Rationale

Recommended Solution

Rationale

Recommended Solution

Ship to Address & Name

Issue

Rationale

#

Inchecker Number

Rationale

Recommended Solution

#

Inchecker Number

Rationale

Recommended Solution

Julian Date (Incheck Date)

Issue

Rationale

Recommended Solution

Not Required SBSS SSC

Not in MILSTRIP

Not in DLMS

Used by CMOS to process transfer of material accountability

Consider use of AIT to satisfy requirement

Issue

Step 5 - Shipment Notification (945A)

Gap Data Element

7

Step 1 - Release Order (940R)

Step 2 - Incheck/Hold Status (945A)

Mark For

Consignor

Recommended Solution

17

Not in MILSTRIP A2_, A4_, A5J

Used by CMOS to generate freight documentation

Option 1: Obtain from DODAAF

Option 2: Obtain from TMDS/TRDM

Not Required SBSS A2_, A4_, A5J; CAS CTR

Issue

Not Required SBSS A2_, A4_, A5J

Not in MILSTRIP A2_, A4_, A5J

Not in 940R

Goes on military shipping label

Delete from required data element list

Issue

6

Not in MILSTRIP A2_, A4_, A5J

Not in 940R

Air Force Unique requirement

Recommend CMOS do the math internally by multiplying W10101 * AMT02

Not Required SBSS A2_, A4_, A5J

3

Not in MILSTRIP 

Used by CMOS in DD1348-1A reprint process only

Delete from required data element list

Not Required CAS CTR, CDD

Gap Data Element

2

Not in MILSTRIP A2_, A4_, A5J

Delete from required data element list

SBSS A2_, A4_, A5J

Disposition Data Source

Not Required

Used by CMOS in DD1348-1A reprint process only

Disposition Data Source

Disposition Data Source

Gap Data Element

1 Not Required SBSS SSC

Issue Not in MILSTRIP

Not in DLMS

Used by CMOS to process transfer of material accountability

Consider use of AIT to satisfy requirement

2

Not in MILSTRIP

Contributes to CWT

Already transmitted in 945A from Step 2

1 Not Required SBSS SSC

Page 1 of 1