process change is the approval/disapproval and prioritization of changes to the Defense Logistics Management Standards (DLMS),
achieved through DoD
Component coordination and consensus, thereby promoting an integrated
approach to the standardization and modernization of the DoD
logistics business process. Control of changes includes documentation, justification, systematic evaluation, coordination, release, implementation,
and publication. Major functions of change control are change control configuration status accounting, reporting, functional change control
reviews, and baseline reviews.
Change Proposal Template
Instructions and format for change proposal submission.
DLMS Change Status Reviews
1000-Series DLMS Change Status Review
Legacy DLMS Change Status Review (2018 and prior)
The annual status reviews from previous years are also available:
and 2015 (legacy)
and 2014 (legacy)
2012 (1000 series)
Proposed DLMS Changes (PDC)
A Proposed DLMS
change is received from a Component, documentation is prepared, and then distributed for comment. These are posted to the Proposed change page.
Approved DLMS Changes (ADC)
Once inputs are received and changes are made to the proposed change documentation, changes are published and
distributed to the Components. These are posted to the Approved change page.
Other PDC/ADC (Withdrawn/Deferred/On-Hold/Disapproved/Requests for Implementation Date)
is staffed and is not approved or
a decision is withdrawn by the submitter after staffing. A PDC
be placed on hold pending resolution of a key issue, for a later review, or for re-write. An ADC may be withdrawn prior to implementation.
PDCs/ADCs which fall into these various scenarios are posted to the "Other" page where their applicable status is identified.
DLMS Version Control
The official American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 version of a standard transaction set
is a key ingredient in the successful application of DLMS Implementation Conventions (ICs) to Federal implementation conventions (ICs). Version control
is implemented by assigning specific numbers/letters (code) to a multi-position file name for each transaction set. The files associated with the
change control/management process and implementing DSs
and changes thereto are available on the approved changes
and the ICs