*DLM 4000.25, Volume 3, April 09, 2022*

*Change 8*

**C4. CHAPTER 4**

**TRANSPORTATION REFERENCE TABLES FOR DLMS TRANSACTIONS**

C4.1.  GENERAL.  This chapter documents procedures for the use and maintenance of transportation reference tables used in Defense Logistics Management Standard (DLMS) Supply transactions.  The USTRANSCOM Reference Data Management (TRDM) is the authorized data repository source for transportation reference tables.  The Logistics Data Repository Management System (LOGDRMS) maintains a list of authorized DLMS Logistics Qualifiers that are associated to selected TRDM reference tables.  To ensure synchronicity and ease of access to the code lists, this chapter outlines the transportation reference tables to be accessed in TRDM via LOGDRMS and documents the change management process for these tables.

C4.2.  APPLICABILITY AND SCOPE

	C4.2.1.  This guidance is applicable to DLMS Supply transactions that use certain transportation reference table information.

	C4.2.2.  See Table C4.T1 for the list of the applicable qualifiers and DLMS Supplement number references.

C4.3.  PROCESS OVERVIEW.  The DLMS logistics qualifier codes in Table C4.T1 are used in logistics DLMS transactions to identify transportation related information.

	C4.3.1.  LOGDRMS will maintain a list of authorized logistics qualifier codes associated with TRDM transportation reference tables.  The metadata in LOGDRMS will define the DLMS data element name, the TRDM table name as the alias, a definition along with any special business rules associated with the construct/use of the table, and the TRDM URL and table name containing the list of authorized code values.

	C4.3.2.  LOGDRMS will maintain the Transportation Method/Type Code and Type of Pack Conversion Guides, both metadata as defined in C4.3.1. and the code lists.

	C4.3.3.  TRDM will maintain the transportation reference tables and a website that is accessible by users from the logistics domain.

C4.4.  CROSS REFERENCE OF LOGDRMS AND TRDM TABLE NAMES

	C4.4.1.  Table C4.T2 establishes a cross reference of the LOGDRMS logistics qualifiers and table names to the TRDM table names.

	C4.4.2.  The DLMS data element, Air Commodity and Special Handling Code, is a concatenation of the TRDM air commodity code and the applicable special handling code tables.

	C4.4.3.  The DLMS data element, Water Commodity and Special Handling Code is a concatenation of the TRDM water commodity, water type cargo, and water special handling codes.

C4.5.  REFERENCE TABLE CHANGE MANAGEMENT PROCESS

	C4.5.1.  Logistics Domain-Requested Changes.  The change management process for DLMS standards is contained in DLM 4000.25, Volume 1, Chapter 3, Change Management.  The change management process for logistics domain-requested changes to these reference tables must be coordinated through the DLMS Supply Process Review Committee (PRC), USTRANSCOM and the TRDM Program Management Office (PMO).  The requested changes will be subject to the Proposed DLMS Change (PDC) process, and provided for review by the Supply PRC members.  USTRANSCOM is a voting member of the Supply PRC, and the TRDM PMO is on distribution for all DLMS changes.  The general rules that apply to the change management process for review of the proposed changes are as follows:

		C4.5.1.1.  Proposed DLMS Changes (PDC) must be submitted to DEDSO for coordination and comment with the Supply PRC, USTRANSCOM, and TRDM.

		C4.5.1.2.  Defense Enterprise Data Standards Office (DEDSO) will evaluate proposed changes and provide comments and analysis or recommendations.

		C4.5.1.3.  Staffing progress and current status of the proposed changes will be shown on the DEDSO website.

		C4.5.1.4.  There will be a resolution process for objections or comments of note, subject to the review of the Supply PRC members.

		C4.5.1.5.  Upon completion of the comment resolution process, proposed changes must be coordinated with USTRANSCOM and the TRDM PM.  Upon review and implementation approval by USTRANSCOM, an Approved DLMS Change (ADC) will be released to the Supply PRC, with concurrent configuration documentation released by the TRDM PMO to its stakeholders.

	C4.5.2.  Transportation Domain-Requested Changes.  The change management process for TRDM standards is documented in USTRANSCOM standard operating procedures.  Once the change is approved via the TRDM configuration management process and loaded into TRDM, DEDSO will receive an email notification from the TRDM website.

		C4.5.2.1.  Minor Changes to the Reference Table.  DEDSO will not prepare an administrative ADC to the Supply PRC announcing the change.  Logistics systems maintaining these tables for use by supply transactions may establish either a system-to-system interface or a subscription service to TRDM to ensure tables are kept current as TRDM publishes changes.  An example of a minor change is the introduction of a new code value or code definition to a table.

		C4.5.2.2.  Significant Changes to the Reference Table.  DEDSO will release a PDC to the Supply PRC for coordination.  PRC comments/non-concurrences must be coordinated with USTRANSCOM and the TRDM PMO for resolution.  Upon satisfactory resolution, DEDSO will release the ADC formally announcing the table changes to the Supply PRC.  If the results of comment resolution require a change by the TRDM PMO, the ADC will be released concurrent with the TRDM change.  An example of a significant change is a modification of the metadata (e.g., field length changed from two positions to three positions).

C4-1	CHAPTER 4