Reference Reason for
Location Description Change
2/N1/180N103 | Add Code A2 MAPAC. To support
(page 46) current
functional and
legacy system
requirements,
See attachment
2.
2/N3/200 Add the following highlighted text to the existing note: To provide the
Segment Note manufacturer’s
(page 49) Use with 2/N101/180 Code DA to identify additional in-the-clear exception address
ship-to address information, with Code MF to identify the manufacturer’s information.
address information, and with Code ST to provide additional ship-to
information for excess plant property.
2/N4/210 Add the following highlighted text to the existing note: To provide the
Segment Note manufacturer’s
(page 50) Use with 2/N101/180 Code DA to identify in-the-clear exception ship-to geographical
geographical location information, with Code MF to identify the location
manufacturer’s geographical location information, and with Code ST to information.
provide the geographical location ship-to information for excess plant property
2/N4/210 N405 | Designate as segment “Use.” Administrative
(page 50) correction.
2/N4/210 N405__| Add Code CC and CVIN as follows: Administrative
(page 50) correction.
CC Country Required to
Use to identify the country if outside the U.S. identify the
country
associated with
aclear-text
exception ship-
to address,
2/N4/210 N406 | Open data element (no note required). Administrative
(page 50) correction.

10



RECORD OF CHANGE
DLMS 511R (Requisition)

Changes from the October 1997 Supply Process Review Committee Meeting

This memorandum constitutes the record of changes made to the DLMS 511R (Requisition)
implementation convention following the Supply Process Review Committee meeting held in Fort Belvoir,
VA, on October 27, 1997. Revisions and reasons for change are noted in the table with additional
supporting information in the attachments.

Reference Reason for
Location Description Change
1/BR/020 BRO2_ | Add Code AM and code value implementation note (CVIN) as follows: To support
(page 5) current
AM _ Requisition Modification functional and
Use to indicate the transaction set contains one or more modifications. legacy system
Use as requisition when no record of original requisition exists. Tequirements,
See attachment
1.
1/BR/020 BRO6 | Change from “Not Used” to “Use.”
(page 6)
1/BR/020 BRO6 | Add Code T and CVIN as follows: To support
(page 6) current
T Status Query functional and
Use with BRO2 Code AO to indicate the transaction set contains one or | legacy system
more followups. Use as requisition when no record of original requirements.
requisition exists. See attachment
1.
1/BR/020 BRO6 | Add Code RG and CVIN as follows: To support
(page 6) current
RG Refer functional and
Use with BR02 Code BN to indicate transaction set contains one or legacy system
more redistribution orders for retail material. requirements,
1/N1/070 N103 | Add Code A2 MAPAC. To support
(page 7) current
functional and
legacy system
requirements,
See attachment
2.

Enclosure



document: oct_pre wpd
Ellen Hilert ww
date: Nov 7, 19

coordination: een Admin
Mf Savage

bee: Hilert (2 copies) ¥
Savage

MFR: I modified the usual forma fisomewhat because I have the
entire MFR typed in cc:mail for fll e-mail distribution.

“ute peta Heenan someon LEI
RRS


Reference Reason for
Location Description Change
1/LQ/140 LQO1 | Code 85, Delete the words ... the coded address in ... Administrative
(pages 38 and correction,
39)
1/LQ/140 LQO1 | Code 95. Designate the existing CVIN as Note | and add the following as Note | To support
(page 39) 2. current
functional and
2. Code subject to modification. Use with BR0O2 Code AM to indicate modified | legacy system
data. , | fequirements,
1/LQ/140 LQO1 | Code A6. Designate the existing CVIN as Note 1 and add the following as Note | To support
(page 39) 2. current
functional and
2, Code subject to modification. Use with BR02 Code AM to indicate modified | legacy system
data. requirements,
1/LQ/140 LQO1 | Code A9, Delete the existing CVIN and add the following CVIN. To support
(page 40) current
Code subject to modification. Use with BRO2 Code AM to indicate modified functional and
data. legacy system.
Tequirements,
1/LQ/140 LQO1 | Code AK. Designate the existing CVIN as Note 1 and add the following as Note | To support
(page 40) 2. current
functional and
2. Code subject to modification, Use with BR02 Code AM to indicate modified | legacy system
data. requirements.
1/LQ/140 LQO1 | Code DE. Designate the existing CVIN as Note 1 and add the following as Note | To support
(page 40) 2. current.
functional and
2. Code subject to modification, Use with BRO2 Code AM to indicate modified | legacy system
data. requirements,
1/LQ/140 LQO1 | Code DF. Designate the existing CVIN as Note 1 and add the following as Note | To support
(page 40) 2. current
functional and
2. Code subject to modification. Use with BR02 Code AM to indicate modified | legacy system

data.

requirements,



Reference Reason for
Location Description Change
2/P01/030 Revise the second sentence of the data element level implementation note as Administrative
PO105 follows: correction,
(page 16)
For nonstandard material, use to identify an estimated unit price.
2/P01/030 Delete Code NE and replace with Code ES and revised CVIN as follows: Administrative
PO105 correction.
(page 16) ES Estimated
Use to indicate an estimated unit price for the nonstandard material.
2/P01/030 NOTE: The second sentence of this data element note should have been a global | Administrative
PO106 change identified by DLMSO (including commas) as follows: correction.
(page 16)
Must use National Stock Number (NSN), when known, except, when
appropriate, for brand name subsistence items identified by subsistence
identification number.
2/P01/030 Revise Code JP CVIN as follows: Administrative
PO108 correction.
(page 17) Must use to indicate Outside Continental United States (OCONUS) shipment. Original text
When used, the paired data element 234 will cite 1 indicating that packaging was misleading.
must meet OCONUS specifications.
2/AT/040 Add segment level Note 3 as follows: To support
(page 19) current
Data in this segment is subject to modification. Use with BRO2 Code AM to functional and
indicate modified data. legacy system
requirements.
2/AT/040 AT03 | Make DE “Use” vice “Must Use.” Administrative
(page 19) (NOTE: This change was identified in the ROC based on the LFWG (9/97) correction.

teview ; however, the IC was not updated.)



Reference Reason for
Location Description Change
2/N9/020 Revise Note 1(1) as follows: Administrative
(page 12) correction.
.. (1) the DoDAAC (or Security Assistance (SA) identification data), ...
2/N9/020 Note 2: Administrative
(page 12) correction.
Change ... the ILCO assigned addressing code ... to read ... the SA identification
data...
2/N9/020 Note 2: Add the following as the last sentence: Administrative
(page 12) correction,
Do not repeat any of this identification data in 2/LQ/140.
2/N9/020 Note 3: Administrative
(page 12) correction.
Change .., the ILCO assigned addressing code ... to read ... the SA identification
data ...
2/N9/020 Revise Note 4 to read as follows: Administrative
(page 12) correction.
4. Do not repeat any of this SA identification data in 2/LQ/140.
2/N9/020 N901_| Move Codes 43, W1, and WO with corresponding CVINs to N907 C04001. Administrative
(page 13) correction.
Revise the beginning of Code 43 CVIN to read ... Use with N901 Code TN... Makes
appropriate use
Revise the beginning of Code W1 CVIN to read ... Use with N901 Code TN... of composite
and provides
Revise the beginning of Code WO CVIN to read ... Use with N901 Code TN... | cross reference.
2/P0 1/030 Change ... not to exceed ... to read ... estimated, Administrative
PO104 correction,
(page 16) Corrects
enhanced data
to conform with

policy.



Reference
Location

Description

Reason for
Change

2/LIN/100
LINO2
Code MF

(page 28)

Revise CVIN as follows:

Use to identify the manufacturer’s make of the applicable end item for the
nonstandard material.

Moved the
identification of
the actual
manufacturer
under the N1
segment with
other
organizational
identification
information to
support current
functional and
legacy system
requirements to
include address
information
with
manufacturer’s
name when the
CAGE is not
available.

1/LQ/140 LQO1

Code 78, Designate the existing CVIN as Note 1 and add the following as Note
2.

2. Code subject to modification. Use with BRO2 Code AM to indicate modified
data.

To support
current
functional and
legacy system
requirements,

1/LQ/140 LQO1
(page 38)

Code 79. Designate the existing CVIN as Note 1 and add the following as Note
2.

2. Code subject to modification. Use with BR02 Code AM to indicate modified
data.

To support
current
functional and

legacy system
requirements,

1/LQ/140 LQO1
(page 38)

Code 80, Designate the existing CVIN as Note 1 and add the following as Note
2.

2. Code subject to modification. Use with BR02 Code AM to indicate modified
data,

To support
current
functional and
legacy system
requirements,



IN REPLY
REFER TO

DEFENSE LOGISTICS AGENCY
HEADQUARTERS
8725 JOHN J. KINGMAN ROAD, SUITE 2533
FT. BELVOIR, VIRGINIA 22060-6221

DLMSO

NOV 15 1997

MEMORANDUM FOR: SEE DISTRIBUTION

SUBJECT: Defense Logistics Management Standards (DLMS) Supply
Process Review Committee (PRC) Meeting, October 27,
1997

The attached minutes of the DIMS Supply PRC - Transaction
Set (TS) 511, Requisition, meeting are forwarded for your
information and appropriate action.

The DLMSO points of contact are Supply PRC Co-Chairs:
Ms. Ellen Hilert, at (703) 767-6117, DSN 427-6117, or e-mail:
ellen_hilert¢hgq.dla.mil; and Ms. Mary Jane Johnson, DSN 427-6123,
(703) 767-6123, or e-mail: maryjane_johnson@éhq.dla.mil.

Attachment
DISTRIBUTION:

ADUSD (L) MDM
Supply PRC Representatives

Federal Recycling Program z a Printed on Recycled Paper


Reference Reason for
Location Description Change
2/N1/180 N101_ | Code DA. Add the following to the end of the CVIN: Administrative
(page 45) correction.
... under authorized conditions.
(Note for SPRC members: There is no need to include “N102” in the CVIN
since the segment level Syntax Note 1 stipulates that at least one of N102 or
N103 is required.)
2/N1/180.N101 | Add Code MF and CVIN as follows: To support
(page 46) current
MF Manufacturer of Goods functional and
Use to identify the manufacturer’s name for nonstandard material. legacy system
requirements to
include address
information
with
manufacturer’s
name when the
CAGE is not
available,
2/N1/180N101 | Code ST. Designate the existing CVIN as Note 1 and add the following as Note | To support
(page 46) 2. current
functional and
2. Code subject to modification, Use with BRO2 Code AM to indicate modified | legacy system
data. requirements.
2/N1/180N101 | Delete Code Z2 and CVIN. Administrative
(page 46) correction. (RE:

AMCL 21)



Reference
Location

Description

Reason for
Change

QQTY/50
(page 41)

Close segment, Mark as “Not Used.”

Administrative
correction.
Data was
intended to
support AMCL
21 which is no
longer viable.

2/LM/160
(page 43)

Close segment. Mark as “Not Used.”

Administrative
correction.
(RE: AMCL
21)

2/LQ/170
(page 44)

Close segment, Mark as “Not Used.”

Administrative
correction.
(RE: AMCL
21)

2/N1/180 N101
(page 45)

Add Code 94 and CVIN as follows:

94 New Supply Source
Use to identify an alternative supply source or temporary holder of
material,

To support
current
functional and
legacy system.
requirements.
Required to
support lateral
redistribution,
e.g. SICA.

2/N1/180 N101
(page 45)

Code BS. Designate the existing CVIN as Note 1 and add the following as Note
2.

2. Code subject to modification. Use with BRO2 Code AM to indicate modified
data.

To support
current
functional and
legacy system
requirements,

2/N1/180 N101
(page 45)

Code BT. Designate the existing CVIN as Note 1 and add the following as Note
2.

2. Code subject to modification. Use with BR02 Code AM to indicate modified
data.

To support
current
functional and
legacy system
requirements,



Reference Reason for
Location Description Change
2/G62/080 Delete Code 01 and CVIN. To support
G6201 current
(page 25) functional and
legacy system.
requirements.
Current policy
does not
support use of
this code,
2/G62/080 Code 53. Designate the existing CVIN as Note 1 and add the following as Note | To support
G6201 2. current
(page 25) functional and
2. Code subject to modification. Use with BR02 Code AM to indicate modified | legacy system
data. requirements,
2/G62/080 Code 54, Designate the existing CVIN as Note 1 and add the following as Note | To support
G6201 2. current
(page 25) functional and
2. Code subject to modification. Use with BRO2 Code AM to indicate modified | legacy system
data. requirements,
2/G62/080 Code BD, Designate the existing CVIN as Note 1 and add the following as Note | To support
G6201 2. current
(page 25) functional and
2. Code subject to modification, Use with BRO2 Code AM to indicate modified | legacy system
data. requirements.
2/LIN/100 Note 1. Administrative
(page 27) correction.

Revise the end of the first sentence to read ... PO106 with Code FT or MG.



also mark as “not used” the non-DLMS data now included in the
standard IC. The PRC strongly supported development of such a
guideline.

Subsequent to the Meeting: During the meeting, PRC members
agreed to use the enclosure as a basis for their individual
Service/Agency (S/A) comments. Subsequently, Mr. Johnson,
Director, DLMSO, and Lt Col Braud, DLMSO LFWG member, recommended
that DLMSO employ a more efficient approach for public comment
submission. They suggested that a single Joint $/A coordinated
vesponse would greatly facilitate LFWG resolution of comments.
Additionally, they asked that the comments be forwarded to the
Logistics Management Institute (LMI) where the overall impact of
the changes might be assessed. The Supply PRC Co-chairs agreed
that a single coordinated document would simplify the process.
Success would depend upon LFWG support for their PRC members.

Action: DLMSO will forward the attachment to the Defense
Information Systems Agency (DISA) as a Joint S/A response, PRC
members should review the comments with their LFWG members in
advance of the next LFWG meeting. They should stress that this
coordinated document reflects their own S/A requirements and must
be supported during comment resolution.

El [AVS
ELLEN HILERT
Supply PRC Co-Chair

APPROVE:
JAMES A. JOHNSON wynly & /

Director, DLMSO

Enclosure


Modification/Follow-Up Requirement:
Requisition Modification:

Part 1 - Current functional requirements allow the modification of specific data elements previously
transmitted in a requisition.

Part 2 - Current functional requirements allow the automatic processing of a modification (DI Code AM_)
as a requisition when there is no record of the original requisition in the supply source files.

Requisition Followup:

Current functional requirements allow the automatic processing of a followup transaction (DI Code AT_)
as a requisition when there is no record of the original requisition in the supply source files.

Rationale:

The DLMS IC functionality must support legacy system conversion requirements; such as, containing the
data to allow for conversion between the DLMS and the DLSS. In addition, requisitions and related
transactions must support the Logistics Response Time (LRT) requirements; for example, the time
computation derived from registration of the original requisition versus the time registration based on an
AM_or AT_used as the requisition. Under legacy systems (specifically), these time differences can be
significant.

11


document: oct_prevy d/oct_prcec.wpd
Ellen Hilert in
1

date: Nov 7, yoy
— . pbialt
coordination: iat
Ld dijosavase

bec: Hilert (2 copies)
Savage
MJ Johnson
Braud

‘UMAR die





DEFENSE LOGISTICS AGENCY
HEADQUARTERS
8725 JOHN J. KINGMAN ROAD, SUITE 2533
FT. BELVOIR, VIRGINIA 22060-6221

IN REPLY DLMSO
REFER TO

MEMORANDUM FOR RECORD

SUBJECT: DLMS Supply Process Review Committee (PRC) Meeting,
October 27, 1997

Purpose: The Defense Logistics Management Standards Office
(DLMSO) hosted a Supply PRC ~ Transaction Set (TS) 511, Requisition,
meeting at Headquarters Complex, Ft. Belvoir, VA. The purpose of
this meeting was to review the TS 511 implementation convention (IC)
as accepted by the DoD/Federal Logistics Functional Work Group
(LFWG) for the public comment phase of the approval process. The
following representatives were in attendance:

Ellen Hilert DLMSO
Vermella Savage DLMSO

CW3 Sterling Hunt Army
Teri McGinnis Army

John Milliken Army

Phil Fiskett Navy
Bobbie Ziolek Air Force
Bob Vitko DLA

Gary Hood GSA

Dave Brown DAASC (DBTCI)
Janice Muse NSA
Alisa Thomas NSA

Brief Summary of Discussion:

a. The PRC conducted a detailed review of the IC. In
the process, numerous administrative and several substantive
changes were identified. The most significant of the changes
recommended are inclusion of current MILSTRIP functionality for
requisition modification and followup; restoration of the MAPAC;
deletion of the funding citation expiration date; and correction
of the “not to exceed” price to an “estimated” price for

requisition of non-standard material.

DLMSO agreed to document

the comments at Enclosure 1 for the public comment submission.

b. The PRC discussed the potential benefit of preparing
a DIMS implementation guideline in the IC format. The guideline
could include additional guidance using DLMS terminology which
would not be appropriate for the DoD/Federal standard IC. It could

Federal Recycling Program or on‘Recycled Paper

{
|
i
i
i
|


Reference
Location

Description

Reason for
Change

2/N1/180 N101
(page 46)

Delete Code ZE and CVIN.

Manufacturer’s
make for the
applicable end
item moved
under
2/LIN/100
LINO2 Code
MF to be
consistent with
other
nonstandard
material
identification
information,

2/N1/180 N102
(page 46)

Revise data element Note 1 as follows:

Use with N101 Code MF to identify the manufacturer’s name and address
(including ZIP code) when the CAGE is not available.

To support
current
functional and
legacy system
requirements to
include address
information
with
manufacturer’s
name when the
CAGE is not
available.

2/N1/180 N102
(page 46)

Add data element Note 4 as follows:

Use with N101 Code Z7 to identify in the clear the recipient of material when

coded data is not available,

To support
current
functional and
legacy system
requirements.
Required to
support Mark-
for party clear
text
identification,



MAPAC Requirement:

The Implementation Conventions (IC) must identify MAPAC to "SHIP" material to the correct FMS or
Military Assistance addressee or provide "Status To" as described by 13 TAC Addresses in the MAPAF,

It is safe to assume the Camps, Posts Stations and Air Bases will not have a capability of decoding the
Transaction Set to determine the MAPAC. Further if we are to use the same rules for developing the
implementation Convention for the future we must concern ourselves with the idea that Shipments will be
made by Commercial Activities which will need the MAPAC to access the Data Warehouse where the
MAPAF is stored. It is correct to assume the data necessary to construct a MAPAC are in the DLMS 2.0
IC, however, to develop the MAPAC will be cumbersome at best. It will be necessary to read the following
LQ segment data elements to construct a MAPAC:

LQ01=67 to determine Type Assistance Code to determine if is FMS or MAP/GA.

LQO1=71 to determine the Country Service and the first character in the MAPAC.

LQ01=85 to determine Country Code.

LQ01=95 to determine Offer and Release Option Code. LQ01= A2 to determine Customer Within Country
Code. LQ01=A3 to determine Delivery Term Code.

LQ01=A6 to determine Freight Forwarder Number.

The first read will be the LQ01=67 to determine if the requirement FMS or MAP/GA which have two
differently constructed MAPACs,

When using these Data Elements a lot of questions have to be asked such as “is the country "CN" for
Canada which requires a two character Freight Forwarder Number.

Translating to determine Customer Within Country Requires an X or W in RP 47 of the MILS Document
which directs you to RP 33 for this determination. The LQ01=A2 will not necessarily indicate that a "X" or
"W" was entered in RP 47 of the MILS Document or is just entered or a'"0" may be entered in RP 33, In
any event this will require at least two reads to make this determination.

The DAASC processing rules require if the document is FMS or MAP/GA, it must be sent to the ILCO
first before entering the DOD Logistics Supply System. This determination would be made by reading the
NI06 "FR".

The N1 Segment in the 511 Transaction Set is Mandatory thus when there is a MAPAC which can no
longer be entered we will need to fill the field with "Z's" to fill the ANSI X.12 Mandatory Requirements. It
is also important to have the MAPAC in the 870 Supply Status Document which will indicate the

"TO" Addressee.

12