OFFICE OF THE SECRETARY OF DEFENSE
WASHINGTON, DC 20301~1000

DEFENSE LOGISTICS
STANDARD SYSTEMS OFFICE
CAMERON STATION
ALEXANDRIA, VA 22304-6100 0 3 NOV 1887

OLSSO-B

SUBJECT: MILSTRIP Focal Point Committee Meeting 88-1

TO: Commander, U.S. Army Materiel Command
ATTN: AMCSM-PDP
Commander, Nava! Supply Systems Command
ATTN: SUP 0323
Commander, Air Force Logistics Command
ATTN: AFLC/MMLSC
Commandant of the Marine Corps

ATTN: LLS-4
Commandant, U.S. Coast Guard
ATTN: G-FLP-1

General Services Administration, Federal Supply Service
ATTN: FCI, Room 500
Commander, Field Command, Defense Nuclear Agency

ATTN: = FCLMM
Director, National Security Agency
ATTN: L 1111

Executive Director, Supply Operations, DLA
ATTN: DLA-OS

U.S. Transportation Command, Director of Deployment
ATTN: TCJD-SA

1. The enclosed Memorandum for Record is forwarded for your information.

2. The action officer for this subject is Mr. Philip M. Smith, AUTOVON

284-6062.

1 Encl C Bik Luee
JAMES R. LEWIS .*

DASO(L/SO) Chief &
Distribution Standard

MRSA (AMXMD-SM)

DAAS-VL Systems Branch

AF/SSC-SMS


OFFICE OF THE SECRETARY OF DEFENSE
WASHINGTON, DC 20301-1000

DEFENSE LOGISTICS
STANDARD SYSTEMS OFFICE
CAMERON STATION
ALEXANDRIA, VA_ 22304-6100

DLSSO-BM 0 3 NOV 1887
MEMORANDUM FOR RECORD
SUBJECT: MILSTRIP Focal Point Committee Meeting 88-1 (6-8 Oct 87)

1. Subject meeting was convened at 0900 hours, 6 October 1987, 6301 Little
River Turnpike, Alexandria, VA. A list of attendees is enclosed at
attachment 1.

2. The focal point committee discussed Proposed MILSTRIP Change Letter
PMCL 477A, Control of Access to DoD Materiel inventories Required by Defense
Contracts. Each paragraph of PMCL 477A was discussed and changes made where
applicable. The following is a synopsis of the discussion on this PMCL:

a. It was agreed that the procedures for processing and controlling
GFM requisitions be included in one chapter of MILSTRIP.

b. It was agreed that a method must be developed to identify con-
tractors associated with “other DoD activities”. The first two positions
of the DoDAAC will be used to identify these other DeD contractors. The
DoDAAD System Administrator has agreed to reserve “HG" for assignment as the
first two position of the DoDAAC for contractors associated with “other DoD
activities". Appendix B2, MILSTRIP, will be changed to reflect this
information.

c. The committee developed definitive procedures for the submission,
processing, and post validation of urgent off-line contractor requisitions.

d. The procedures for identifying requisitions that must be processed
under GFM controls were clarified.

e. The procedures were amended to allow the submission of part number
requisitions for GFM.

f. The procedures were amended to allow internal transactions for the
validation process between the ICP and the MCA when the ICP and the MCA are
collocated.


0 8 NOV 1887
g. The procedures were amended to allow, as an option of the Service/
Agency, the use of a three position Manufacturers Directive Number to
identify the requisition to an appropriate contract.

bh. The procedures were amended to remove the requirement to always
use M&S code F on GFM requisitions.

i, The procedures were amended to require an additional edit
on the signal code and fund code to distinguish GFM requisitions
from CFM requisitions.

Jj. The procedures were amended to allow the submission of modifier
documents to change the project code, Priority Disignator, Required
Delivery Date or Advice Code. All other modifications of contractor GEM
requisitions are prohibited.

k. The procedures were amended to identify the ICP actions that will be
taken in processing the MCA GFM validation response if there was no record
of an {CP GFM validation request or there was no record of a valid
requisition. The procedures were also amended to describe what actions
would be taken if the MCA GFM validation response did not provide a valid
advice code.

1. The definition of status code CR was revised to read: “Rejected.
invalid DIC for GFM".

m. The procedures were amended to more clearly state what actions are
to be taken by the MCA, during the ICP/MCA validation process, if there was
no record of a valid requisition.

n. The definition of status code BF was revised to include its use
during the ICP/MCA GFM validation process. If the ICP receives an MCA GFM
validation response but has no record of an ICP GFM validation request and
no record of a valid requisition, a supply status transaction with status
code BF will be generated.

o. The definitions for advice codes 2U and 2V were revised to more
clearly reflect their usage.

p. The procedures were amended to include a new status code that will
be used to advise the requisitioner that the requisition has been cancelled
because the MCA failed to validate the GFM requisition.

3. The focal points were thanked for their participation and advised that
an RFID on AMCL or PMCL 477A will be issued. The meeting was adjourned on
8 October 1987.

G fbi eZee —
1 Attachment PHICIP Mi. SMITH

DoD MILSTRIP System
Administrator