QB B SEP 1963
DLSSO-BM PAGE 4
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

precedence of processing JCS project code requisitions, the Marine Corps repre-
sentative was advised to use the procedure cited in chapter 3, paragraph A.3.,
to sequence requisitions for processing. The date of the requisition would be
the final determining factor on which requisition would be processed first.
The committee agreed to the following changes to the proposal and to issue an
RFID:

a Change the word “group” to “designator” in the edit criteria for
the "project" code or data element in figure 3-1, chapter 3.

b Change the edit criteria for the “priority” code or data element
in figure 3-1, chapter 3, to:

1. If expedited handling signal 999 is present in the RDD field
and PD is not 01-03, enter PD 03.

2. If an OSD/JCS project code is present in rp 57-59 and PD is
not 01-15, enter PD 03.

3. If NMCS/ANMCS indicator (N/E) is present in rp 62 and PD is
not 01-15, enter PD 08.

4. If rp 62 is A, S, or X, enter PD 15.
5. For all other conditions, if PD is not 01-15, enter PD 15.
(2) Disposition: An RFID will be issued with the changes cited above,
g. TOPIC 7. PMCL 9, Priority Designator Identification and Requirements.

{1} Discussion. PMCL 9 was staffed in compliance with an OASD (L/SD)
Memorandum for Deputy Assistant Inspector General for Auditing, 23 December 1987,
subject: Draft Report on the Audit of the Uniform Materiel Movement and Issue
Priority System (Project 7SL-915). A DoD IG report recommended that the Priority
Designator for ANMCS requisitions be determined under DoD Directive 4410.6
(UMMIPS). The OASD (L/SD) partially concurred in the recommendation in that
the priority designator for ANMCS requisitions should be no higher than #4,

The Navy and the Marine Corps did not agree that the priority
designator for ANMCS requisitions should be no higher than 94. The Navy and
the Marine Corps position is that UMMIPS under the definition of urgency of need
designator A allows for priority designator of $1, £2, 3, @7, and $8 for ANMCS
requirements.

The other S/A focal points agreed with the Navy and Marine Corps
comments .

{2) Disposition: The DoD MILSTRIP System Administrator will advise
OASD (L/SD) that MICSTRIP PMCL 9 will be withdrawn for the above cited reasons.



& SEP ig¢
DLSSO-BM PAGE 9
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

the AEQ status transaction to reject transactions that the DAAS cannot process.

(2} Disposition: DAASO will use AE9 transactions with MILSTRIP status
codes to reject transactions that the DAAS cannot process. DAASO will develop
the necessary procedures and, if necessary, request the establishment of new
status codes if the current codes are not applicable.

4, The focal points were thanked for their participation and the meeting was
adjourned on 26 August 1988.

xz, /
Cpt Ath
1 Attachment PHILIP M. SMITH

DoD MILSTRIP System
Administrator



& 8 SEP wa
DLSSO-BM PAGE 6 88
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

1 Are DI Codes AAP/ASQ necessary? PMCL 470A assigns DI Codes
ADR (for NSN), ABP {for part number), and AQQ (for other}, DoD 4160.21-M,
chapter XXII, attachment 1, JRA/JRC formats call for a NSN in rp 8-22. Para-
graph F.5.b. (last sentence), however, says “a separate JRC will be prepared
when different NSNs or manufacturers' part numbers apply to the item in the
group."

2 What DI Code should the requisitioner use on reclamation at
a DRMO if the item does not have an NSN? DoD 4160.21-M, chapter XXII, para-
graph L, states DI AMR will be used.

3 DoD 4160.21-", chapter XXII, paragraph I, states reclaimed
assets will be Condition Code A, F, or R. Condition Code & will be used
if reclaiming activity does not have the capability to verify the condition of
the reclaimed asset is equal to or better than that specified by the requisi-
tioner. MILSTRIP will require the reclaiming activity to cancel the requisition
(status code C8) and identify the correct condition code in the status transac-
tion, if the requested condition code is not available.

4 Dod 4169.21-M, chapter XXII, paragraph G.; Marine Corps
requests validation instructions be provided for this paragraph.

5 Dod 4169.21-M, chapter XXII, paragraph J., states requiring
activity will rejmburse the reclaiming activity for the cost of reclamation.
The reclaiming activity may waive reimbursement as appropriate. Question:
Are reclamation requisitions free issue or funded? MILSTRIP recommends free
issue similar to requisitions from disposal. If reclamation requisitions
are funded, RODS must be processed by reclaiming activities.

6 Dod 4160,21-M, chapter XXIT, attachment 2, urgency of
requirement codes need clarification, What is their relationship to MILSTRIP
requisitioning? Do they conflict with UMMIPS priority designators? Paragraph
F.6.g. Says an R4 requirement of the owning service will not take precedence
over an R1, R2, or R3 requirement of the other managing activity. How will the
owning service know the urgency of requirement code of the managing activity?

7 What documents are used by the owning service to communicate
with the reclaiming activity to determine if an end item is available to estab-
lish a reclamation project/program or if the ICP is considering establishing a
reclamation project?

8 The reclaiming activity must be able to process cancellations,
followups, and modifiers.

(b) The committee agreed to the following changes to the proposal:
1 Require the reclaiming activity to provide an AES transaction

for each condition code, by quantity available, for requisitions not filled
because the requested condition code was not available. The AE8 transaction will



% & SEP 1963
DLSSO-BM PAGE 5
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

h. TOPIC 8. PMCL 12, Transportation Control Number (TCN) Entry for Ship-
ments by Sma Package Carriers.

(1) Discussion: The committee reviewed the staffing results of this
proposed change which consisted of nine concurrences (one of which contained
comments) and two nonconcurrences. The comments and nonconcurrences were
resolved and the proposed change was approved based upon the agreed to revisions
as follows:

a Identify the source from which to obtain the Standard Carrier
Alpha Code (SCAC) Directory.

b Reference the AMCL 138, scheduled for implementation on
1 November 1989, which contains approved changes already made to the TCN entry
instructions,

¢ Revise procedures in paragraph 3. to show the TCN field of rp
60-76 in lieu of 62-76, to change the “daily record pickup number," to read
"package identification number," and to clearly identify record positions for
each entry.

qd Include appendix C36 with revised TCN entry instructions in the
approved change.

(2) Disposition: An RFID will be issued incorporating the agreed to
changes cited above.

i. TOPIC 9, PMCL 10, Assignment of OSD/JCS Project Codes.

{1} Discussion: The MILSTRIP System Administrator initiated PMCL 10
to clarify MILSTRIP instructions to S/As on how to request OSD/JCS project
codes and to identify the office responsible for issuing OSD/JCS project codes.
The focal points agreed with PMCL 10 clarification of MILSTRIP procedures. It
was also agreed that the sequence of instructions in the MILSTRIP Manual,
appendix B13, will be as follows: (1) assignment requests, (2) assignment
constraints, and (3) dissemination. The procedures for assignment requests
were expanded to include data requirements that are needed from the S/A
requestor to assign a project code.

(2) Disposition. An RFID will be issued with the changes cited above.
j. TOPIC 11. PMCL 470A, Requisitioning from Reclamation.

(1) Discussion: The Service/Agency comments on PMCL 470A were thor-
oughly reviewed and discussed. The MILSTRIP Focal Points were not in agreement
with provisions of PMCL 470A. The interface between the proposed procedures/
documentation and DoD 4160.21-M, chapter XXI1, must be clarified.

(a) The committee developed questions and identified areas that
require resolution by the DoD Reclamation Work Group (DRWG):


& 8 SEP 1963

DLSSO-BM PAGE 8
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

9 Add "Owning Service" before the words "ICP Processing," in
chapter 3, paragraph F.

10 Insert "Owning Service" between “the" and "ICP" in chapter 4,
paragraph H.9.

11 The format for the reclamation requisition will include a
field for the identification of the RI Code of the Owning ICP.

12 The following will be added to chapter 4, paragraph H.9.,
after the second sentence: “However, all transactions must be in computer
readable formats."

(2) Disposition: The DRNG will be invited to attend the next MILSTRIP
Focal Point Committee Meeting, 4-6 October 1988, to resolve the above questions.

k. TOPIC 11. PMCL 11, Source of Supply (SOS), Federal Supply Classifica-
tion (FSC), and National Item Identification Number (NIIN) Edit.

(1) Discussion: The committee discussed the staffing results of this
proposed change and expressed a desire to have DAAS reinstate this edit. The
DAAS discontinued performing the SOS, FSC, and NIIN edit due to outdated infor-
mation at the beginning of the month because of untimely receipt of trigger
actions (SOS updates) from the Defense Logistics Service Center (DLSC) (Defense
Integrated Data System (DIDS)). The DLSC has stated that these trigger actions
(SOS updates) could be generated to DAAS earlier than on the first of the month,
but this would require a Systems Change Request (SCR). The committee approved
the proposal after changes were made to figure 3-1 to eliminate references to
specific status codes. The committee also requested action be taken to pursue
the development of an SCR to the DIDS to have DLSC provide SOS updates to DAAS
4 days prior to the effective date.

(2) Disposition: An RFID will be issued with changes to figure 3-1 to
eliminate references to specific status codes. An SCR will be pursued with DLSC
(DIDS) to provide trigger actions (SOS updates) to DAAS at least 4 days prior
to the effective date. The DAAS will resume performing the SOS, FSC, and NIIN
edit upon receipt of timely trigger actions (SOS updates).

1. TOPIC 12. DAAS Return of Rejected Transactions by Narrative Message.

(1) Discussion: DAASO is currently using narrative messages to reject
transactions that are not processing through the DAAS. In the past, the receiv-
ing communication message center could receive these narrative messages and
punch out the message on key punch cards. The communication center no longer
has key punch capability and DAASO is not sure what is happening to the narra-
tive messages. In order to ensure their messages are going to the proper
activity, DAASO requested permission to create AE9 status transactions and use
existing MILSTRIP status codes to reject the incomplete or erroneous transac-
tions, The committee agreed that DAASO should use MILSTRIP status codes and


OFFICE OF THE SECRETARY OF DEFENSE

6301 LITTLE RIVER TURNPIKE, SUITE 210
ALEXANDRIA, VA 22312-5044

DEFENSE LOGISTICS
STANDARD SYSTEMS OFFICE

28
DLSSO-8 SEP 198g

SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4 (24-26 August 1988)

TO: Commander, U.S. Army Materiel Command

ATTN: AMCSM-MSM

Commander, Naval Supply Systems Command
ATTN: SUP 0323

Commander, Air Force Logistics Command
ATTN: AFLC/MMLSC

Commandant of the Marine Corps
ATTN: LPS-4

Commandant, U.S. Coast Guard
ATTN: G-ELM-2

General Services Administration, Federal Supply Service
ATTN: FCI, Room 590

Commander, Field Command, Nefense Nuclear Agency
ATTN: FCLMM

Director, National Security Agency
ATTN: L111

Diretor, Defense Logistics Agency
ATTN: DLA-OSC

U.S. Transportation Command, Director of Deployment
ATTN: TCJ6-DA

1. The enclosed memorandum for record is forwarded for your information.

2. The action officer for this subject is Philip M. Smith, AUTOVON 284-6062.

( Beek

1 Encl JAMES R. LEWIS
Chief

cc: Distribution Standard Systems Division
DASD(L)SD
MRSA (AMXMD-SM)
DAAS-VL
AF/SSC-SMSM
DPSC (HON)
nese (Hd)
USALOGC (ATCL-SAA)



2 8 SEF 13b0

DLSSO-BM PAGE 7
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

contain Status Code CB and the available condition code will be entered in rp 74.
If reported condition is acceptable, a new requisition will be submitted.

2 Remove condition codes from MILSTRIP and provide a reference

to MILSTRAP.

3 The owning ICP will have the capability to process cancella-
tion, modification, and followup documents against reclamation requisitions.

4 The owning ICP will be required to provide immediate status
in response to a reclamation requisition indicating the date by which notifica-
tion will be made on whether reclamation will or will not take place. The
final status will be provided NLT 60 days from the date of the requisition.

5 A new status code will be assigned to indicate the requisi-
tion is being processed against a reclamation project. The ESD for release of
materiel to the consignee will be contained in rp 70-73 of the status transac-
tion.

6 A complete reclamation requisition format will be defined
and made a part of appendix Cl of MILSTRIP.

7 The following will be added to chapter 2:
“RECLAMATION AUTHORIZED AT THE DRMO.

1. Normally, reclamation will be accomplished by a Service reclaiming activity;
however, reclamation of limited parts from usable property (such as a carburetor
from a vehicle) is authorized at the DRMO subject to the following constraints:

a. A separate requisition is required for each item to be removed. The
requisition will contain DI "AOR," "N" in rp 40 of the document number, and the
extended value in rp 70-80 (estimated if value unknown).

b. All requests and issues must be controlled by the applicable Military
Service Accountable Officer.

c. Parts requested will be limited to those not available on a timely basis
in wholesale system stocks but are needed promptly to meet priority requirements
(UMMIPS priority 01-08).

d. Removal of parts will be accomplished by the DoD activity requesting
the parts to include furnishing all necessary tools and equipment.

e. Reclamation requisitions for component parts to DRMOs must be manual
walk-in, hand carried documents."

8 Add "Owning Service ICP" and its explanation to the defini-
tions and terms section.


2 8 SEP 4993

DLSSO-BM PAGE 3
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

“TOPIC Ae ” MCL 6, Assets Sent to Other Services for Repair (1G 87-027).
Proposed MILS Change Letters (PMCLs) 6 (MILSTRIP) and 5 (MILSTRAP),
ng Item Accountability for Maintenance Actions.)

d

(Joi
Main

(1) Discussion: The committee discussed the staffing results of this
proposal, Comments included recommendations to expand procedures to identify
the responsible activity for preparing and receiving the DI FTA. The Navy
Focal Point expressed difficulty in staffing proposals which impact other
commands or higher echelons. Reference was made to the DoD Directive 4000.25
which states, in part, that the focal point office, as designated by the Service
or Agency, has responsibility for providing the Service or Agency position on
system/program changes and has authority to make decisions for the Service or
Agency. Copies of the ASD(P&L) letter, dated 22 January 1988, were provided to
the committee for their information or use in obtaining the necessary intra-
Service/Agency comments on the proposals. The letter was addressed to the
Service Assistant Secretaries informing them of DLSSO's joint proposals covering
subject topic. The DoD MILSTRAP System Administrator informed the committee
that extensive comments were received on the MILSTRAP proposal. After analyzing
the staffing results, the committee decided that detailed procedures covering
MILSTRAP should not be placed under MILSTRIP; however, MILSTRIP should cite
MILSTRAP, where applicable.

(2) Disposition: The MILSTRIP proposal will be rewritten to identify
the preparer and the receiver of DI.FIA transactions and will cite MILSTRAP,
when necessary, in reference to specific procedures concerning the account-
ability for maintenance actions. The proposals will be restaffed jointly as
MILSTRIP PMCL 6A and MILSTRAP PMCL 5A.

e. TOPIC 5. PMCL 489A, Bar Coded Foreign Military Sales (FMS) Data on
DD Form T346-1A, Issue Release/Receipt Document (IRRD).

(1) Discussion: The Services/Agencies comments on PMCL 489A were
thoroughly reviewed and discussed. As a result of the review and discussion,
the committee agreed to change the entries for block 26 to be the unit of issue
(two positions), quantity (five positions), condition code (one position), unit
price (seven positions), and the supplementary address (four positions - the
first and last three record positions of the supplementary address from the
source document). These will be the entries in block 26 for FMS issues. The
first position of the supplementary address is necessary to identify the Service
because the case numbers (last three positions of the supplementary address)
are duplicated within the Services.

(2) Disposition: An RFID will be issued with the changes cited above.
f. TOPIC 6. PMCL 8, Priority Designator for JCS Project Code.

(1) Discussion: The Service/Agency comments on PMCL 8 were thoroughly
reviewed and discussed. In regards to the Marine Corps comments on the priority



2 8 SEP i998

DLSSO-BM PAGE 2
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

a Add the procedure for preparation of subsistence requisitions
to chapter 2, paragraph A.9.b., in lieu of adding the procedure as a new para-
graph B. in chapter 2.

‘b Add the words “for subsistence" after the acronym "RDD" in the
first sentence, fifth line, of paragraph A.3., chapter 3.

© Substitute the words "figure 3-2" for the word "below" in the
second sentence, fourth line, of paragraph C.1., chapter 3.

d Delete any change to the current paragraph A.3.g., chapter 3.

e Add "If blank, compute SDD" as the last sentence to the new
entry 4 for data element "Required Delivery Date" in figure 3-1, chapter 3.

(2) Disposition: An RFID will be issued with the changes cited above.

c. TOPIC 3. PMCL 4, Provide 100 percent Shipment Status to the Ship-to
Activity Designated by the Signal Code. (Joint Proposed MILS Change Letters
(PMCLs) 4 (MILSTRAP) and 4 (MILSTRIP), Expanded Materiel Receipt Acknowledg-
ment Requirements.)

(1) Discussion: The Service/Agency comments on MILSTRIP PMCL 4 were
thoroughly reviewed and discussed. As a result of the review and discussion,
the Navy withdrew their comments, and the committee agreed to change the
proposal as follows and issue an RFID:

a Change chapter 4, paragraph H., subparagraph 2., to require ship-
ment status for exception ship-to addresses to be provided to the activity
identified in record positions 30-35 of the requisition.

b Revise the last sentence of the proposed change to chapter 4,
paragraph H.2.a., to read: “In addition, DAAS will furnish shipment status
to all valid status recipients."

c No changes will be made to the current chapter 4, paragraph M.

d Revise the proposed change to appendix B4, paragraph 2., sub-
paragraph a.{4)(a), to read: "the mandatory provision of shipment status to
all valid status recipients."

e Revise the proposed changes to the explanations for M&S Codes
@ and Y so that a new sentence begins after the words “signal code."

(2) Disposition: An RFID will be issued with the changes cited above.


OFFICE OF THE SECRETARY OF DEFENSE

6301 LITTLE RIVER TURNPIKE, SUITE 210
ALEXANDRIA, VA 22312-5044

DEFENSE LOGISTICS
STANDARD SYSTEMS OFFICE

DLSSO-BM 2 8 SEP 199g
MEMORANDUM FOR RECORD
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-4, 24-26 August 1988

1. Subject meeting was convened at 1300 hours, 24 August 1988, 6301 Little
River Turnpike, Alexandria, VA. A list of attendees is at enclosure 1.

2. The focal points were reminded of the need to provide copies of their
responses to PMCLs and RFIDs to the other Services/Agencies MILSTRIP Focal
Points.

3. The following topics were discussed by the committee:

a. TOPIC 1. Joint Proposed MILS Change Letter (PMCLs) 3 (MILSTRIP) and
3 (MILSTRAP), Date Packed/Expiration Date for Subsistence Items.

(1) Discussion: The Service/Agency comments on MILSTRIP PMCL 3 were
thoroughly reviewed and discussed, As a result of the review, the committee
agreed to change the location of the three digit code from record positions 52,
53, and 70 to record positions 22, 52, and 53. The change will only apply to
subsistence transactions generated at the wholesale level. The committee also
agreed to include, in the procedures, that Management Denial Code 3 would be
used for materiel release denials for which there is no stock for the date
packed/expiration date cited on the materiel release order.

(2) Disposition: An RFID will be issued with the changes cited above.

b. TOPIC 2. PMCL 5, Required Delivery Date (RDD) for Subsistence Requisi-
tions.

(1) Discussion: The Service/Agency comments on PMCL 5 were thoroughly
reviewed. The DPSC representatives informed the committee that all subsistence
requisitions have an RDD entry. This is true for all the Services/Agencies
preparing and submitting requisitions for subsistence. Therefore, the S/A
would not have to make any programming changes to their computer system to
implement this change. The DPSC representatives also stated that if by chance
a requisition was received without an RDD, an SDD would be computed and the
requisition would be processed, The committee agreed to the following changes
to the PMCL and to issue an RFID: