representative will coordinate with the other working group to define, explain, or actually
develop the work product, at the discretion of the other working group chair.

The development of new EDI transaction sets or messages will be undertaken by
the LFWG only after reaching consensus that existing standards cannot be used to satisfy
user requirements. In such cases draft or skeletonized ICs are helpful, but not required, as
a means of ensuring that all user functional requirements have been met. A more
structured and complete IC will be developed by the LFWG as the new draft standard
moves through the EDI standards body approval process. This practice will ensure that
limited resources are expended in the most appropriate manner consistent with the
development and approval of the new standard.

The co-chairs will submit concurrently to the FESMCC and DoD EDISMC all
work approved by the LFWG. The co-chairs will act as the advocates for all such work as
it progresses through the review and voting processes. All work products submitted will
be in the format prescribed by the FESMCC. Any changes resulting from this process will
be returned to the LFWG for consideration and incorporation by the LFWG.

(d) Conflict Resolution.

In progressing any work item the LFWG must satisfy all user business
requirements. This does not mean that the technical solution proposed by the submitter
must be adopted by the LFWG. An alternative solution may be proposed by the LFWG in
order to meet the user business need as well as the requirement to maintain consistency
among all logistics data exchanges. Should the submitter not agree with the LFWG
proposal, an appeal may be made to the co-chairs for reconsideration. In cases of appeal
disapproval by the LFWG, a final appeal may be stibmitted to the FESMCC by the user’s
voting representative.

7. Charter Updates. This charter will be updated as required to meet evolving
procedures, identified business needs, and direction from the FESMCC and DoD
EDISMC. Questions or comments associated with this Charter should be referred to the
current LFWG co-chairs.



Charter
Logistics Functional Working Group

1, Purpose. This document serves as the Charter for the Logistics Functional
Working Group (LFWG). It is a written understanding between the Federal Electronic
Data Interchange Standards Management Coordinating Committee (FESMCC) and the
Department of Defense (DoD) Electronic Data Interchange Standards Management
Committee (EDISMC) defining the LFWG objectives, scope, general terms of reference,
and general methods of operation. The FESMCC and DoD EDISMC agree that the
LFWG will consolidate the logistics support functions and responsibilities within a single
organization.

2. Authority, The FESMCC, under the authority of FIPS 161-2, establishes
interagency functional working groups for selected business areas including but not limited
to logistics; procurement; finance; transportation; and communications, control and
security , as required, to provide a focal point for development and maintenance of
implementation conventions. The FESMCC also coordinates the functional working
groups to ensure that they are working quickly and efficiently to provide useful
implementation conventions (ICs) for the Federal Departments and Agencies in
accordance with responsibilities detailed in the FESMCC Charter and Operating
Procedures.

Similarly, Defense Information Systems Agency (DISA) is the DoD Executive
Agent for managing DoD Information Technology (IT) standards, including ensuring
standardization across service systems and infrastructures. The Dol) EDISMC is the
principal DoD organization within which to develop and maintain a consistent,
comprehensive approach to electronic data exchange (EDI) issues and related IT matters.
Because of the diversity and scope of business areas and technical matters, the DoD
EDISMC charters a series of DoD functional working groups with the responsibility of
harmonizing business and EDI standards issues through the development of a consistent
approach to exchanging business data among the various trading partners.

Due to the need for close coordination and comparability of operating objectives
among Federal Departments and Agencies, including the DoD, agreement has been
reached that a single functional working group should be established to deal with logistics
matters. Accordingly, the Logistics Functional Working Group is established as a
combined Federal/DoD working group. It shall derive its authority jointly from its parent
bodies and will support the responsibilities of both the FESMCC and DoD EDISMC
through the resolution of standards-related issues affecting logistics functional
requirements.

The LFWG is responsible for overseeing all matters related to the exchange of
logistics business data. In performing these responsibilities it will follow procedures and

Y SITE e-
! Benawe @ CUTE |


Navarro, Irene Center for Standards DoD DISA.
10701 Parkridge Blvd

Reston, VA 22091

(703) 735-3528

Price, Sandra. = Army
USA MICOM
AMSMI-AIS-FS
Redstone Arsenal, AL
(205) 955-7178

Ripp. Arlene DeCA
(804) 734-9906

Spruill, LCDR Joe Navy NAVY Primary
NAVSUPSYSCOM

5450 Carlisle Pike

Mechanicsburg, PA

(717) 790-1741

Stanford, Brad Navy
Office of Naval Research
800 N. Quincy Street
Arlington, VA 22217
(703) 696-5420

Wesolowski, Donna Army DoD Co-Chair
HQ, 10C

AMSIO-SMM-S

Rock Island, IL 61299-6000

(309) 782-8071


include all Defense Logistics Standard Systems (DLSS)
publications: Eventually the home page will also serve as a
source of information for proposed and approved changes.

Action: DLMSO will provide, under separate cover, a step-by-step
guide to assist Components with start-up and navigation of the
home page. Basic information is as follows: URL is

http: //www.dasc.dla.mil/dimso. Use ACROBAT software (click on
ACROEAD) to convert text.

g. Federal/Defense Logistics Functional Working Group
(LFWG). Ms. Donna Wesolowski, Co-Chair, briefed the Committee on
the formal approval process each of the DLMS implementation
conventions (ICs) must undergo. Briefly, this includes a
detailed syntax and editorial review conducted by the Defense
Information Systems Agency (DISA) Electronic Data Interchange
Standards Management Committee (EDISMC). Corrected ICs are
submitted to the LFWG for review to insure that the standards are
applied properly against the business case. DLMSO
representatives are present to provide background and assist
those unfamiliar with the IC in deciphering the particular
application. When accepted by the work group, a 30-day public
review period follows and ultimately submission to the EDISMC for
approval as a federal standard. This approval process is
required under current DISA architecture. Enclousre 3 is a list
of the LFWG members and Enclosure 4 is the LFWG charter.

Action: Component functional experts were encouraged to attend
upcoming sessions of the LFWG. DLMSO is currently preparing
multiple supply ICs for the next work group session to be held in
Orlando, Florida, beginning October 21, 1996. DLMSO will assure
that Committee members are advised of the content and dates of
future meetings. (See Enclosure 5.)

h. Weapon System Identification. Mr. Charlie Strong,
DLMSO, briefed the Committee on proposed options for revising
MILSTRIP to carry weapon system identification and demand data.
The DLMS 2.0 was designed to accommodate stratification of weapon
system by quantity within the requisition, but implementation is
not a near-term possibility. Briefing charts are provided at
Enclosure 6. Discussion centered around the lack of a supporting
infrastructure within existing Component systems to provide and
effectively use the weapons system data. Beyond selecting a
suitable means of conveying the data, the DoD must also develop
and maintain a standard coding structure and modify automated


8 Charter Approval.and Ratification

Approved by: on bee deter Ce

Ratified by: SYEVED

@ fan aed
(insert DoD LFWG Chair name and title) (Approval Date)
Approved by: A] fost Gc P-2)-SL
(insert Fed ZFWG Chair name and title) (Approval Date)
APALG LIPO.
(insert DoD EDISMC Chair name and title) (Date)

Lome Ranoy Hokemsy
DISA /[TIEO

Ratified by: SIAM ED

APA SIGE

(insert FESMCC Chair name and title)
TERESA Son Eur

GSA

(Date)


Friday, Oct 25 ~

8:00 Wrap up open items/issues

09:00 Schedule next meeting and set draft agenda
10:00 Adjourn


Grant, Paul D. Federal ECA PMO
(202) 501-6998

Hood, Gary GSA _ Federal Co-Chair
Federal Supply Service

ATTN: FCSD

Washington, DC 20406

(703) 305-5516

Howard, Carolyn = Army

USA MICOM

ATTN: AMSMI-AIS-FA
Redstone Arsenal, All 35898-5110
(205) 955-8728

Johnson, Donna Navy
COMNAVSEASYSCOM
Code 04322

2531 Jefferson Davis Hwy
Arlington, VA 22242
(703)602-1060, X213

Keene, ILT Sean Air Force AIR FORCE Primary
HQ AFCA/XPRE

AF EDI Man. Team

(618) 256-5448

Kline, Sandra. NAVICP NAVY Alternate PO432.07-Navy
Philadelphia, PA 19111-5098
(215) 697-5233

Lamatrice, Mike NAVAIR
(703) 604-3611, X2558

Lotz, Judy Naval Air Systems Command
(703) 604-3090, X4180

Minnick, L. Joseph NAVY EDI
(717) 790-5737

Myers, Geoff Army

HQ, 10C

AMSIO-SMM-S

Rock Island, IL 61299-6000
(309) 782-5283



the resultant IC, the degree of relationship existing among the business functions, and the
acceptability of the product to the business trading partners.

(b) LFWG Meetings.

The co-chairs will schedule LFWG work items on the agenda, as required. In
developing meeting schedules the co-chairs will consider FESMCC, DoD EDISMC, ANSI
ASC X12, and UN/EDIFACT meeting schedules, standards publication schedules, and
user requirements. The LFWG will maintain a calendar identifying meetings and other
factors affecting the work of the LFWG.

LFWG meetings will be scheduled no less frequently than biannually. However, at
the discretion of the co-chairs, meetings may be held more frequently. Every attempt will
be made to provide LFWG members with a minimum 30 day advance notice of any LFWG
meetings, the anticipated work agenda, and work products consistent with their
availability.

Every attempt will be made to rotate meeting locations to centrally agreeable sites
to minimize the travel costs incurred by the LFWG members. Meeting duration will not
exceed one week in length.

(c) Procedures.

All logistics work requirements for the LFWG will be provided to the co-chairs via
the FESMCC or the DoD EDISMC, directly by a LFWG member, or directly by the Chair
of another Federal or DoD functional working group.

Acceptable work requirements may include, but are not limited to:

draft ICs for review or preview,
draft EDI standards data maintenance for review or preview,
other working group requirements to be incorporated into existing ICs
falling under the cognizance of the LFWG,

* other working group draft data maintenance for EDI standards falling
under the cognizance of the LFWG, and

* undeveloped work products or requirements.

In cases requiring extensive work beyond the normal LFWG meeting schedule the
co-chairs may authorize temporary ad hoc task groups for the purpose of completing this
work. Separate task group meetings are authorized at the discretion and availability of
task group members to meet projected user requirements.

Additional resources required to provide technical advice, support for work
development, etc. may be requested from the co-chairs by a LFWG representative.


87SZ-L9L (EOL) TO9T~L9L (£04) ISTH <

xf xp x [Tw eTp bywoxqtA yraqor 8US2-L2F TOOT-Lzh wid 0H OMATA Gog
6LbT-06L (LTL) 9TOL-O6L(LTL)

xf x} x {iw Anwu‘ ypeudotemeras uot 6LPT-O8b 9TOL-~OfF HOSWdD LAWN wezqs uoy
bO68-LSZ (ETS) L6bS-L57 (ETS)

x{ x [ru ge owze byereqrTeyyx 98TT-986 L6vS-L8L | WIDT/OWAY OH A8qTOH Juey
ZLPS-SLZ (EOL) SS¥8~SLZ (EOL)

x AoG* eupeleq3ozeu ZLEB-SEZ SGP8-SET (WSO) WW eqQ07eW Bop

Tru BSOL-O6L (LTL) HSOL-O6L(LTL) pueumop sweqsks Atddng reaen

x x | -Aaeu‘dnsaeupqjeysty drpttud PSOL-OEF 9ERE-OLF wetty-dns 33848Ta TTud

ZoReAASTUTUpY

Z9T9-L9L (EOL) LET9-~L9L (EOL) weashs qI¥LSTIW doa

x x [tu erp byooeSeaes ertpowres Z9T9-LEb LUT9-LEY OSWwId SBeaes eT TOW

Z9T9-L9L (EOL) €2T9-L9L(€0L) Dua Atddng ‘ateyg-op

x x [qu eTp byereuzey ouelArew COT9-LZP €CT9-LUY OsWwId xeujyeH euep Azew

fo Z9T9-LOL (EOL) LIT9-L9L (E04) Oua Atddng ‘ateyo-op

x x [rw erp byeqzetry wets ZOT9-LEP LUTS~LEP OsWId J23TTH USTTR

| ee
féz | ez if zz "IWIOaWHOD "IWIOUSHWOD
Nsa Nsa
ssauqqy TIWM-3 IOMNAS HOTEAO SHYN

SITINISOVA | HNOHGHIZL FOIOA

966T LSnoow
axLSOe ZONVGNALLIW

ONILASH (Dad) ARLLIWWOD MEIARUY SsHooud ATddas



1809 asow pun Ayipiqudns asoul Yjim Utsaypiu 0} AvaU UI |]qISDA.]

suoyisinbas ul sapoo suiajsAg Uodeas, jnd 0} sieuOHIsinbes souinboy = +
seBueyo susoysAs 10) ajqeyreae Ajipees spun} on +
(paeo sajtes|-G] 90q MeN) SeANped0Id GINS TIN }U9IIND 0} pesinbes suoisiAgy =
soBueyo ounba [jim swuaysAs payewioyne ajesojoyM/EJOY = «
VIN VSI .
shep 09-06 ul juowajdu ues OSyWd  °
uopisinbes ejBurs e YIM payelsosse oq ued spied Joey adnini°
uonisinbes ajBuis e ul weysXg uodeem ajdyinwi soy ARUenb Ayjuep!ueD +
waysks uodeaag Aq Gurjoey smojy +
ozs epoo wiaj}skg uodeagg ul Ayiqixesy +
(s,ubey jeo1pey)) spied sajresy sydoooe Ajueunds SINS +
SHDVINVACV °

soduvy. waysig
uy Ang dd1A1ag

(sapoo uoytsod +f) uonrsinbay 0) suoHovsuvsy sapieay, pueddy “¢

| uonrayjo) ving 40f suondo
ysoddng wia3sks uodea WIG



nsodoad st Qmnauffip fo aaisaq

.

uSisapar w93sh¢ (IIgs SL) woursmbay sid yuomeyduy “p
Surumues301day suopismboy 0} suoyoesuvsy, spies, puaddy “¢
SuruesBordoy suiajskg uodeaaa 0} SWVGOd onbing Usissy “7

Y4AOA4 WNT A uonrsinboy draLS THA We4nD asp “|

| uoysayjo) ving sof suondg

yaoddng wia}sks uodvan WIG



PREPARE/REVIEW:
ELLEN HILERT _£/t— aor.)

Supply PRC Co-Chair

REVIEW:
VERMELLA savAcs Yaa
MILSTRIP System Administrator

APPROVE:
JAMES A. JOHNSO!

Director, me

Enclosures

F

REVIEW:

A

4
MARY JANE HEPNER ‘/ Ler
Supply PRC Co-Chair

JOSEPH PIPAN
DLMS Logistics Data Manager

REVIEW: ells


systems to incorporate weapon system identification in decision
support. ~

Action: The purpose of this briefing was informational. Follow-
up action is required at a higher management level before any
supporting action from the PRC is desired.

i. Additional Discussion Topics:

(1) DLMSO has prepared two followups memorandums
requesting semi-annual status on implementation of approved DLSS
and DLMS changes. Nonresponsive Components (Army, Marine Corps,
DLA, and JLSC) were asked to comply. Mr. Bob Vitko, DLA MMLSI,
questioned the benefit of producing the report at this time
since, with the exception of the few approved changes which DoD
has directed for implementation in the legacy systems, approved
changes with implementation dates of 1993 or later have not been
implemented. Implementation of approved changes in the legacy
systems had been “suspended” in support of their implementation
in the DoD standard logistics systems which were being developed
under the Corporate Information Management initiative. DLMSO
indicated that select Components may have implemented some
changes not directed by DoD and the status report will provide
visibility of those changes. It will also provide DLMSO with a
tool to evaluate the overall DoD position on implementation of
approved changes. With the acceptance of a standard logistics
system by all Components unlikely, DoD must reassess the open
approved changes and develop a revised implementation plan. The
status report provides a starting point for this effort.

(2) Recently this office has found it necessary
to chase after Component responses to DLMSO correspondence
concerning DLSS and DLMS Changes. Committee members were
informed that requests for extensions are generally accommodated
and an interim status gives us early notice of any problem areas.
Cooperation in this area would be greatly appreciated.

(3) DLMSO is in the process of preparing a
register of all DLSS and DLMS Component representatives including
names, communications numbers, and mailing addresses.
Distribution will be made shortly. Maintaining current
information is difficult and assistance from the Committee is
enlisted in notifying DLMSO when changes occurs.


Resources will bé provided by the co-chairs based upon availability and at the discretion of
the co-chairs.

All work requirements will be processed on a “first in, first out” basis unless the
co-chairs deem it appropriate to reorganize the workload based on user requirements and
any other appropriate factors.

Under normal circumstances, any work products that are ready to progress from
the LFWG to the FESMCC or to the DoD EDISMC will not be delayed in order to add
functionality requirements. However, if in the opinion of the co-chairs, the functional
requirement is so significant as to limit the usability of the work product, the product may
be delayed pending incorporation of the functionality. If the work product is not delayed,
the submitter of the added requirement will be so advised and will be asked to submit a
new work product proposing a change to the original work product.

Changes to existing ICs can be submitted to the LFWG at any time. However,
approval and subsequent incorporation of the change into the IC will be done consistent
with FESMCC and DoD EDISMC guidance regarding version/release updating to ICs.
This practice will be in effect as a means of ensuring a level of consistency and minimum
disruption to thé user population. Therefore, every effort should be made by LFWG
members to ensure the consistent attendance at LFWG meetings as well as a complete
staffing of all work products prior to their submission to the parent approving authority.
Every attempt will be made to inform the submitter of the approximate time for
functionality incorporation. :

Changes to existing EDI standards (including the development of new segments
which will be incorporated into an existing transaction set or message) for which an
approved IC already exists can be submitted to the LFWG at any time. Each such
submission should be accompanied by a complete business case supporting the change as
well as a draft change to the existing IC.

Changes to existing EDI standards (including the development of new segments
which will be incorporated into an existing transaction set or message) for which no IC
has been approved will be developed and processed in conjunction with the development
of the IC. Each such submission should be accompanied by a complete business case
supporting the change as well as a draft change to the existing IC. Every effort should be
made by the submitter as well as the LFWG to correlate the projected implementation plan
tequirements for the IC with EDI standards body meeting and approval schedules.

All logistics work requirements (including IC changes, IC development, and data
maintenance to EDI standards) shall be introduced initially to the LFWG. Those
requirements approved for progression which fall under the cognizance of another
functional working group will be submitted to that working group in a manner and format
prescribed by that working group. Either the co-chairs or a designated LFWG


DAILY WRAP-UP SESSION/ADJOURN

AUGUST 29, 1996 BEGINNING 0800

0800-0900

FEDERAL/DEFENSE LOGISTICS FUNCTIONAL
WORKING GROUP (LFWG) BRIEFING

DONNA WESOLOWSKI/
LTCOL RICH BRAUD

0930-1030

10.

PREVIEW PROPOSAL OPTIONS TO REVISE MILSTRIP
TO CARRY WEAPON SYSTEM IDENTIFICATION AND
DEMAND DATA

CHARLES STRONG/
MELLA SAVAGE

FINAL WRAP-UP SESSION/ADJOURN MEETING



Federal/Defense Logistics Functional Working Group
Agenda
October 21-25, 1996

Monday, Oct 21

08:00 EDI 101 - Harry Featherstone
12:00 Lunch

13:00 Welcome and Introductions
13:15 Administrative Business

-- Review/Approve August 1996 Minutes
-- Review LFWG Calendar
-- Call for additional agenda items/changes

14:00 Old Business
-- Review list of LFWG cognizant transaction sets (TS Adds)
-- Summary status report on Ics in progress
Metall review scheduled separately)
196 IC Contractor Cost Data Reporting
- 511 IC Committment Document
- 806 IC Project Schedule Reporting
- 839 IC Contract Funds Status Reporting
- 839 IC Cost Performance Reporting
- 848 IC Material Safety Data Sheets
- 856 IC Ship Notice/Manifest (DD Form 250}
- 861 IC Receiving Advice/ Acceptance Certificate

15:00 Migration of 806 transaction set functionality to

UN/EDIFACT PROTAP message - Harry Featherstone
16:00 Summary of EDISMC & FESMCC August 96 Meetings
16:30 End of Business Day

Tuesday, Oct 22
08:00 Review of 861 IC - Application Advice - Steve Luster

09:00 -- Review of 869 IC - Order Status Inquiry (Requisition Inquiry) -
Vermella Savage
-- Review of 869 Order Status Inquiry (Cancellation) -
Vermella Savage
10:00 Report on Air Force Bar Code Project - 1LT Sean Keene

12:00 Lunch

Eual


N REPLY
REFER TO.

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

DLMSO SEP 30 19965

MEMORANDUM FOR: SEE DISTRIBUTION

SUBJECT: Defense Logistics Management Standards (DLMS) Supply
Process Review Committee (PRC) Meeting, Aug 27-29, 1996

The attached minutes of the DLMS PRC meeting are forwarded
for your information and appropriate action.

We anticipate scheduling the next PRC meeting for November
19-21, 1996. Confirmation and agenda will follow. Discussion
topics should be submitted to DLMSO by November 5, 1996.

The DLMSO points of contact are Ellen Hilert, Supply PRC
Chair at 703-767-6117, DSN 427-6117, or e-mail
ellen_hilert@hq.dla.mil, or Vermella Savage, MILSTRIP System
Administrator, at 703-767-6127, DSN 427-6127, or e-mail
vermella_savage@hq.dla.mil

Times of ; —
JAMES A. JouNSON

{_/Pixector
Defense ‘Logistics Management

Standards Office
Attachment
Distribution:

ADUSD (L) MDM
Supply PRC Representatives

Federal Recycling ronan ag rn on Racycied Paper



BZSZ-L9L (EOL) B09T-L9L(E0L)

x [tw etp byeotebueep sustzep 8CSE-LUP 809T-Leb USTWA-WId oTebuyed suetzeq
¥60S-LT9 (EOL) BLEB~LT9(E€0L)

x [rw Aw2e owe: byouext tr tw l P60S-LOL 8Lz8-L9L | WS-STONY ONY USATTTIW UYor
ZOSL-L9L (EOL) S9SL~L9L EOL)

x [Tw eTp byeuttzequry” epury ZOSL-L2b S9SL-LUY SNEWW WIG UTTzequTYy epuTy
9TSS-SOE (E04)

x ao: esbopooy’ AxeB dsda~-Ssa-wsp poo Azep

LOLZ~969(€0L) €LOT-969(€04) T-saT

x [yw ousn: ¢djms -Sbuetzze TAQ LOLZ~9%b ELOT-92b TSI ‘OWOH reTAL woe
6580-L09(€0L) L0L2-L09(€0L)

x 6S80-L2E LOLE~LEE a€L dNsavn yutnpeg Tua
9060-409 (£0L)

x 6S80-L7E 9060-47 YIL aNSAyN yoraepuey Aziey,

8£0S-¥S6 (SOF) O@T-IW

x x | sob tqool: trewoeummdeuoy tp wWwa/Lod Asuoy ta
vHOS-962 (ETS)

x| x] [tw ep’ seepeuerowt €6% IXH/PPOS-986 oswwa UeION “N 3zEqou
TB9S-96Z (ETS)

x x [Tw ep’ seepqumozgp @Lb IXH/TS9S-986 Isu/osvva UMOIG BAe
6z | sz] az "TWIOBENHOD IVIOWSHWOD
Nsa Nsa

— SSHUCQY ‘TIVH-a OGWAS HOTadO BRYN

SONVGNSLIN BIUINISOVE BNOH@HISL BOIOA

NI Sava



NI Sava

SITINISOVE

SNOHGHTEL FOIOA

6LOT-969 (£04) T9OT-969 (COL) t-dat
x 6LOT-92% I90T~9TF T3I OWOH Azouueya ‘W Azza x0lew
BZFE-LE9 (EOL) S¥TS~S69 (EOL)
x Thu" pso ‘boeepyedza tz GPTS-S2Z WCW ("I) GSO yotagedzqta utasy
A0B tq O€6E-bS6 (SOF) ¥TPS-bS6 (SOP) OTe-ZWy
x x x | oof [TewWOEMU@UOSTT TOI’ epuTT wwa/Lod UOSTTTOL eputy
Ao Z6ES-FS6 (SOF) Ozt-Zww
x x x1 *TqooC- TTeuoeumesouol uesns wed ‘Loa seuop uesns
€S9L5-492 (Z0Z) ZE66E-L9%(ZO0Z) tot-aaw
x x sob wey by’ Treu@ertoqsedo wwa/Lod szoqjseq Ay ED
A ESLS-L9Z (ZOZ) TH8B~L9Z(Z0Z) ZOt-aay
/ x x Ao8: vez by TTeueT Tryp wea / LOG TITH yerogeq
ZOSL-L9L (EOL) B0SL-L9L(E0L) SNGHW
x [tw eTp byezeseap TTepzem ZOSL-LEb B0SL-L2b wid OH eSeeD PIEM
9ETP-PS6 (SOF) 8T96-FS6 (EOL) TT9-IWY
x wid ‘Lod umojoW Arreyg
¥SO6-LTI (EOL) 8058-LT9 (EOL) WS -D'TIOWW
x x Ttw* Awre owebyostaepy © BS06-L9L B0S8-L9L Owy OH staeg Azraq,
8ZSZ-LOL (EOL) €09T-L94 (€0L) ISTAW
x TTweTp byesmopeew epuserq BSZ-L7P 909T-Ltb wid OH SMOPeSW “Y epuerg
ee] az] zz "IWIOYaNHOD "TWIOURHWOD
Nsa Nsa
bec heeneered ied SSaudav ‘TIWW-a "IOMMAS HOLTAAO aWYN
HONVONELIV



apqisnaf uoynjuawmadun ulsa}-plyy 0} 4vany

swiayskg uodean, 10} SOYYOO BuluBisse 10) suojsiaas yesnpesoid sasinbay = +
a}esajoym pue j1e}81 10} soBueyo suiaj}sAs payewozne suinbad IM «

uonisinbai ad apoo wiajsAs Uodeam au s}iUiT]«

peyoes} og 0} Wa}shg UuCdeejA YRS 105 NYVGOR enbiun ubisse ysnui sao1Aleag se

=] AdGVSIG «
. quewsjdu 0} yoInb Ajaanejoy = «
wajskg uodeay, Aq ajqejiene uoneuoju puewlEeg
waysks uodeay, Aq ajqepieae Ajipeas sioday +
wajshs uodeem anbiun 40} peynuep! Ajanbiun uonisinbeay =

STOVINVAGY +

sodueyo wioyshs
pue sainpavo.d 03

uy-Ang ad1Alag paen, | suonisinboy uiayshg wodea yy 03 SOVVAOG Ibiay UaIssy *Z

uonrajjo) ving 40f suondg
yroddng wo}sks uodea\ W1d


ajqusvaf uoynyuawualdun utsa} sayy

seBueyo suia3sAs payewojyne oinbeal IAA oe
sepoo we}shg uodeayy oy} UI Si9}ORIeYD JO JoquINU S}IWII]«

uontsinbai sed apoo waysAs uodeam ouo s}iwiy oe
suoiisinbes ul sapoo suieysAg uodea,g jnd 0} ssouonisinbos seuinbay =}

SSOVINVAQVSIC -

}usued 0} ulbeq seoiaies aye sAep o¢ ul eseqejyep Sqi] ayeindod ues oSyWa +
waysks uodeayy Aq eiqejiene uonHeuuojU! puewag «+
weyskg uodeay, Aq ayqeyreae opew syodey +
afqepeae uondojyseayoiny +
| \ SHDVINVACV °

soSuvya urajsAs

pue saanpas0ad 0}
uy-Ang aa}Areg paony (sapos uontsod ¢) uonisinboy dTLLS TDA 3892 asy “7

uo0urajj0) vig tof suondg
yaoddng wash uodvay, W1d



SUPPLY PROCESS REVIEW COMMITTEE MEETING

HOSTED BY THE

DEFENSE LOGISTICS MANAGEMENT STANDARDS OFFICE (DLMSO)
8725 JOHN J KINGMAN ROAD ROOM 1655

FORT BELVOIR VA 22060-6221

POD 5, CONFERENCE ROOM 2501, SECOND FLOOR
MEETING AGENDA
AUGUST 27, 1996 BEGINNING 1300
1300-1330

WELCOME/OPENING REMARKS/ INTRODUCTIONS

ELLEN HILERT

1330-1400

ADMINISTRATIVE REMARKS/MEETING AGENDA

MELLA SAVAGE

1400-1600

FORCE/ACTIVITY DESIGNATOR (F/AD) I USAGE
(DLMS MANUAL, CHAPTER 5)

ELLEN HILERT/
KEVIN FITZPATRICK

DAILY WRAP-UP SESSION/ADJOURN

AUGUST 28, 1996 BEGINNING 0800
0800-1000
PMC 40, PROCESSING CLSSA REQUISITIONS MELLA SAVAGE
1000-1130
PMC 41, DEPRA FOLLOW-UP TIME FRAMES MELLA SAVAGE

1300-1400

AMC 15, NEW OWNERSHIP CODE 0 (ZERO)

MARY JANE HEFNER

REVIEW ON-LINE VERSION OF MILSTRIP, SUP 1
(You may view the code list in advance of
the meeting on the Web under the Defense
Automatic Addressing System Center Home
Page at http://www.daas.dla.mil by
choosing the DAASC Bulletin Board button
then clicking on the bulletin board system
and selecting MILSTRIP Supplement 1.)

MELLA SAVAGE/
BOB MORAN

DLMS 2.0 MANUAL ON-LINE PRESENTATION

JOE PIPAN/
JIM MOFFETT

Enel \



Légistics Functional Working Group membership list. The primary and alternate voting
members are listed where known.

Donna Wesolowski
DoD LFWG Chair
(309) 782-8071

LOGISTICS FUNCTIONAL WORKING GROUP MEMBERS

Adams, May Defense Printing Service
HQ, DLA
Ft. Belvoir, VA 22060-6221

Badgett, Shiela DISA DISA Alternate DITCO IDT31
2300 East Drive

Scott AFB, IL 62225-5406

(618) 256-9314

Berkoff, Linda P. Fed ECA PMO
(202) 501-6876

Boeckmann, Lisa DISA DISA Primary DITCO IDT41
2300 East Drive

Scott AFB, IL 62225-5406

(618) 256-9587

Braud, LTC Richard DL MSO DUSD(L) Primary
8725 John J. Kingman Rd.

Ft. Belvoir, VA 22060-6221

(703) 767-6158

DSN 427-6158

Buttrey, Diana DFAS-HQ/DDE
Finance Working Group Chair
(703) 607-0355

Clark, Don NAVAIR
(703) 604-3611

Cogdill, Gene DLA
DSN 427-2608

Felix, Donna Army
STRICOM

12350 Research Parkway
Orlando, FL 32826-3224
407-384-3799, DSN 970.



DONNA:
I HAVE MADE ARRANGEMENTS FOR THE OVER HEAD AND SCREEN, PLUS THE
BUTCHER BLOCK PAPER.

HOTEL ADDRESS:
SHERATON INN

1724 ALAFAYA TRAIL
ORLANDO, FL

(407) 658-9008

PER DIEM FOR ORLANDO IS $65.00 AND $34.00
ROOMS ARE $65.00
HOTEL HAS RESTAURANT & LOUNGE:

CLOSE BY:

APPLEBEE’S

CHILES

OLIVE GARDEN

SHONEY’S

BERGER KING

WENDY’S

SEVERAL PLACES IN THE STRIP MALL ACROSS THE STREET FROM THE HOTEL
GREAT LITTLE PIZZA SHOP

CHINESE

LET ME KNOW IF THERE IS ANYTHING ELSE I CAN DO...
NANCY COX

E-MAIL ADDRESS:
COX1@STRICOM.ARMY.MIL


Action: The Committee accepted the proposed change with one
minor revision which is to generate the initial follow-up when
supply status BA or CB is not received within 10 days instead of
5 days. DLMSO will issue the Approved Change with implementation
to occur 60 days from the date of the change memorandum.

d. Approved MILSTRAP Change 15, New Ownership Code 0
(Zero) to Identify DoD Special Operations Forces (SOF) Ownership.
This change adds a new Ownership Code 0 providing an automated
means to identify and account for SOF assets. Army has reported
that implementation in their legacy system would be problematic,
and cost prohibitive. Army recommended deferring implementation
until DLMS and using project codes to identify SOF assets in the
interim. Navy and Air Force nonconcurred in the recommendation
to use a project code citing that project codes have not provided
adequate visibility/accountability for SOF assets. Navy and Air
Force had recommended a November 1996 implementation date for
Ownership Code 0. Marine Corps had not responded to the proposed
change or the request for implementation date.

Action: Mr. Milliken, AMC AMCLG-SM, agreed to investigate the
situation, reevaluate the Army position, and provide a response
by October 15, 1996. Based on his initial inquiries into the
issue, a favorable reply for DLSS implementation is possible.

Mr. Ron Tyler, HQMC LPS-1, also agreed to evaluate the change and
provide the initial Marine Corps response by October 15, 1996.

e. Review of On-Line MILSTRIP, Supplement 1, Routing
Identifier and Distribution Codes. Mr. Moran, DAASC,
demonstrated the on-line supplement available through Internet
access. The Committee agreed that this could prove to be a
valuable tool; however, limited access to Internet within the
Components will not support elimination of the paper document at
this time.

Action: DAASC will investigate possible enhancements and
increased flexibility of the current display and search
mechanisms.

f. Review of On-Line DLMS Manual. Mr. Pipan, DLMSO,
with technical support from Mr. Moffett, DASC-N, provided a
demonstration which included a look at the DLMSO Internet home
page and capabilities for viewing the DLMS Version 2.0 manual.
DLMSO is in the process of expanding this valuable resource to


The LFWG 7s responsible for overseeing all matters related to the exchange of
logistics business data. In performing these responsibilities it will follow procedures and
direction adopted by the FESMCC, to include IC formats, common methodologies and
constructions, etc. When necessary the LFWG will coordinate functional area
requirements among the other FESMCC and DoD EDISMC functional working groups,
as required, to ensure a consistent approach to all such matters.

The signing of this Charter by the Chair, FESMCC and the Chair, DoD EDISMC
formally recognizes this body as a Federal Civilian working group level forum jointly
working with the DoD.

3. Qbjectives. The primary goal of the LFWG is to act as a single forum for all
Federal Departments and Agencies as well as the DoD member Services and Agencies to
participate in a dialog and resolution of all matters related to the use of EDI as an enabling
technology in the conduct of all logistics business areas. This will be accomplished
through the following objectives:

© Increase the use of electronic commerce (EC) and EDI among the Federal
Government logistics community

¢ Support the implementation of new and evolving business processes and
practices, utilizing EC and EDI to the maximum extent possible as a means of
achieving operating efficiencies

¢ Promote an orderly approach toward business process transitions in order to
maintain user satisfaction through the implementation process

¢ Utilize EDI standards in a consistent manner

e Promote and develop a standard methodology for communicating logistics
business information

¢ Satisfy all user requirements in a timely manner

4, Scope. The LFWG assumes responsibility for all logistics matters not specifically
assigned to other functional working groups including, but not limited to, supply,
inventory management, maintenance, program management, environmental, and
administration functions. It will serve as the forum as well as the sanctioning body for the
development and acceptance of Federal Government and/or DoD-wide agreements on
logistics business matters. Specifically, the LFWG scope of responsibility will include:

* Ensure that all logistics business requirements are met within a timely manner
through the use and development of EC and EDI standards

* Maintain a working knowledge of both the American National Standards
Institute (ANSI) Accredited Standards Committee (ASC) X12 and United
Nations Electronic Data Exchange for Administration, Commerce and
Transport (UN/EDIFACT) EDI standards used in the conveyance of logistics
business data


Becatise of the wide range of logistics business areas, voting members are not
expected to be functional experts in all matters falling under the purview of the LFWG.
Accordingly, each LFWG member may augment attendance at any meeting with functional
business experts and observers in order to ensure that a sufficient degree of expertise and
consideration is provided to the subject under review. Nevertheless, voting responsibility
continues to reside only with the voting representative.

The LFWG recognizes that substantial work, including policy development and
system design, is underway in a number of Federal Departments and Agencies and DoD
organizations which will impact the work of the LFWG and other functional working
groups. The LFWG will consult with representatives from any such organization as
technical experts and advisors in order to ensure that all LFWG work products are
consistent with overall Federal and DoD policy and IT initiatives.

Each LFWG member organization will hold one vote. Approval of any matter
under vote will result from a simple majority of votes cast by LFWG members in
attendance at the time a vote is taken. No provisions will be made for providing proxies
or accepting votes from members not in attendance. Votes from the co-chairs will only be
cast whenever a voting matter has not reached a simple majority.

6. Method of Operation,
(a) Cognizance.

The LFWG will establish, maintain, and publish a list of ANSI ASC X12
Transaction Sets for which it has primary cognizance as designated by the corresponding
parent body. Corresponding UN/EDIFACT messages are also deemed the responsibility
of the LFWG. Where ongoing Federal, Service or Agency business areas are known but
where no supporting transaction sets or messages exist, the LFWG will retain primary
cognizance in those business areas for all EC and EDI standards work products.

In certain business scenarios multiple business disciplines will utilize the same
transaction set or message to convey functional business information. When multiple
functional working groups utilize the same transaction set or message to convey business
information, unless specifically directed to the contrary by the FESMCC, the LFWG will
retain primary cognizance over the standards and will coordinate the development of a
consistent approach to usage and data exchange.

Cognizance is deemed to include development of new EDI standards, data
maintenance to existing standards, and ICs.

The LFWG will determine the number of business functions to be included in any
single IC. In making this determination, the LFWG will endeavor to minimize the number
of ICs being issued for each transaction set. However, other factors related to a decision
to combine business functions within a single IC will include the complexity and clarity of


2

using F/AD 1 priorities. Unauthorized use allocates potentially
scarce resources to activities that would otherwise have a lesser
priority. To correct this situation, OSD working with the Joint
Staff developed a process which will automatically validate F/AD
1 usage. A table of authorized activity DoDAACs will be
maintained by the DSDC/Defense Automatic Addressing System Center
(DAASC) for the purpose of automatically downgrading the
requistiion priority of those which do not pass validation. The
Committee provided support in developing procedural steps
necessary to accomplish this process. However, the members
expressed concern that the planned automated process may have
some implementation problems and will not adequately address the
larger issue. Proper assignment of F/AD and Urgency of Need
presents a difficult enforcement problem. Additionally, current
F/AD definitions are open to variying interpretation by the
Services. Mr. Fitzpatrick assured the Committee that action is
underway to redefine the F/AD categories (potentially restricting
F/AD II for combat support). The planned automated process
should be regarded as a “first step” with expanded policy and
procedures to follow.

Action: OSD will direct, by memorandum, the implementation of
enforced F/AD 1 compliance via automated processing. DLMSO will
develop the supporting Proposed MILSTRIP Change to be coordinated
under a 60-day evaluation and staffing period. Implementation
will occur 60-days from the date of the Approved MILSTRIP Change.

b. PMC 40, Processing Cooperative Logistics Supply
Support Arrangement (CLSSA) Requisitions. This change clarifies
policy relative to use of Not Mission Capable Supply/Anticipated
Not Mission Capable Supply (NMCS/ANMCS) and expedite handling
codes as they apply to Foreign Military Sales. Discussion
revealed significant differences in current Service
interpretation and practices.

Action: No action can be taken until Services complete
evaluation and provide responses to the PMC. Nonresponsive
Components (Army, Marine Corps, and Coast Guard) agreed to
investigate and provide a timely response to DLMSO.

c. PMC 41, Defense Program for Redistribution of
Assets (DEPRA) Follow-up Timeframes. This proposal reduces the
DEPRA follow-up timeframes to 5 days and the overall suspense
period to 30 days.


13:00

15:00
4:30

New Business
-- Hazardous Waste Disposal Project Business Case - Shari
Underwood
- 856 IC - Ship Notice /Manifest - Don Egan
- 861 IC - Receiving Advice/Acceptance - Don Egan

Presentation of 852 IC - Product Activity Data - Gary Hood

End of Business Day

Wednesday, Oct 23

08:00

10:00

12:00

1:00

4:30

DLMS Material Obligation Validation Process - Vermella Savage

-- 517/LS18 IC Material Obligation Validation - MOV Reply and
Reinstatement Request

-- 517/LS45 IC Material Obligation Validation - MOV Notice
Acknowledgement

DLMS Material Returns Process - Vermella Savage

-- 180/LS28 IC - Return Merchandise Authorization and.
Notification - Material Returns Reporting

-- 870/LS24 IC - Order Status Report - Material Returns Supply
Status

Lunch

Continue review of DLMS Material Returns Process

-- 856/LS23 Shipment Notice/Manifest - Material Returns
Shipment Status

End of Business Day

Thursday, Oct 24

8:00

12:00
1:00

4:30

DLMS Material Reporting Process - Harry Featherstone

-- 830/LS46 IC Planning Schedule with Release Capability -
War Material Reporting

-- 830/LS47 IC Planning Schedule with Release Capability -
Special Program Requirements

Lunch

Continue review of DLMS Material Reporting Process

-- 867/LS26 IC Product Transfer and Resale Report -
Demand Reporting

-- 867/LS49 IC Product Transfer and Resale Report -
Issue

End of business day


V REPLY
REFER TO

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

SEP 27 195

DLMSO

MEMORANDUM FOR RECORD

SUBJECT: Defense Logistics Management Standards (DLMS) Supply
Process Review Committee (PRC) Meeting, Aug 27-29, 1996

Purpose: The Defense Logistics Management Standards Office
(DLMSO) hosted a Supply PRC meeting on August 27-29, 1996, at the
Headquarters Complex, Ft. Belvoir, VA. The purpose of this
meeting was to discuss the inappropriate use of Force/Activity
Designator (F/AD) I and develop standard procedures for
monitoring F/AD I usage; resolve outstanding issues related to
Proposed MILSTRIP Changes (PMCs) 40 and 41 and Approved MILSTRAP
Change 15; discuss weapons system identification options; and
share information concerning on-line access to MILSTRIP Sup 1,
the DLMS 2.0 manual, and the implementation convention review
process. The agenda is shown at Enclosure 1. A list of
attendees is shown at Enclosure 2.

Brief Summary of Discussion: Ms. Ellen Hilert, Supply PRC
Chair, and Ms. Vermella Savage, MILSTRIP System Administrator
provided opening remarks and reviewed the meeting agenda.

Agenda Items:

a. F/AD I. Mr. Kevin Fitzpatrick, OSD(L)MDM, led a
discussion of current deficiencies in the existing procedures and
practice regarding F/AD I usage. By design, this designation is
reserved for the highest national priorities and can be assigned
only by Presidential authority, by the Secretary of Defense, the
Chairman of the Joint Chiefs of Staff (CUCS), or as authorized by
the CUCS. Criteria for assignment are maintained in DoD 4140.1-
R, DoD Material Management Regulation. On an annual basis the
Joint Staff audits F/AD usage to ensure continued validity.
Requisitioning data is captured over a review period, and the
Services are required to validate use by activity. Audits
continue to find a significant number of unauthorized activities

Printed on Recycled Paper

Federal Recycling rowan



Aunqudns ynf yim utsay Zuo] ul uonvjuawuajduy

suojisinbs: ul sopoo swajyshg uodeasg 3nd 0} sisuonisinbel salinbey
$}]so0o uonejusWajduy
swiss payewojne syesajouyy pur jlejay Aq sabueyo eaisue}xQ

SS9OVINVAGVSIC

uojisinbas ajBurs e ul wa3shg uodeay, yore 40} AYQUenb AyQuep]
uonisinba ojHuls e ul sulaysAg uodeayg ofdyinus Ayyuep]
8ZIs aBpoD Wasshs UodeanA U! ARIIGIXE}4
uojoesues auo ul Suonisinbas afdynW

waysks uodean, Aq Gunjoes} smo

9901nOs auUO Ul E}ep pueUlap jo UOHeEIYHUApI [ING

8661 LOO
Aq wounejuomodur

Joy suraysAs
uSisapas 0} sao1A10g (IIs SL) uonrsmbay swt uamodary “+

uonrayjo7 ving 40f suondg

°

SHOVINVAGV

jAoddng wiaj3sks uodean WId


sauo dpay9 aap asayy ng Syouny aaaf ou St asay],

sjrodoy puv urajshg jroddng uotstaaq

Bye wajskg UodKIA 10J 99.MOS BISUIS «

3.1njoIn.Ys SuIpod uaysAs uodvom prvpueys syusuOdUI0D Cog «

Ayeoyi19
pue snje}s urojshs UodvaA JO MOTA [[NJ OATS 0} IVP [RUOHIPpY

‘SCaaN
Sjuawaounyuy pup
sjuamasmbay uoyrayjop ving

yoddng wajsks uodean WIG

En e Lb l


x [tw erp by@Buezqs setaeyo OsSWwIg Buezys atrtzeyD
LST9-L9L (€0L) 8ST9-L9L (E04)

x [yw etp byopnezq preyots LST9-Leb BST9-LEb oswid Tooat ‘pnezg yota
TLOS-7BL (60€)

x [tw Awe * Tye - eT AOMOTOSemMp TLOB~£6L AUT TXSMOTOSEM eUUOGg
G00Z-L94(E0L)

x ‘ [Tw etp byeqqegyou sewel SOOC-LE A-OSwa JI9FFOW WTL
Z9T9-L9L (EOL) 60T9-L94 (£04)

x [tw erp byauedtd ydesol Z9T9-LEb 60TI~LEb oswid uedtg aop
6z || sci] 2z "IWIOWSNHOD IWIOUSHHOD
Nsq Nsa

ssauqay TIWW-x IOGWAS HOTAIO SYN

SONVONALIV SITINISOWE ENOHGZTSL SOTO

NI savad

IL



e Resolve technical differences among the LFWG membership in order to
achieve consensus for the development, portrayal, and conveyance of logistics
business information

« Review and approve ICs, data maintenance or other work products prepared
by Departments, Services and Agencies for purposes of EC and EDI
implementation prior to submission to the appropriate parent body

© Act as the advocate of all LFWG work products reviewed and voted upon by
the parent body

e Ensure that all IC and data maintenance work is consistent with EDI standards,
structures, usage, and formats

e Ensure that all IC and data maintenance work is consistent with prescribed
formats and requirements

° Accept, coordinate, and develop solutions for specific work requests presented
to the LFWG when sufficient resources are made available from either the
parent body or requesting organization

* Preview and provide recommendations to submitters of logistics work
products prior to formal submission to the LFWG

e Preview and coordinate an LFWG position on work products developed by

other working groups

5. Membership and Voting. The LFWG will have co-chairs elected by their
respective LFWG memberships and confirmed by their respective parent bodies. Co-
chairs are elected for a period of two years. Membership in the LFWG is automatically
conveyed to a single voting representative from each member organization of their
respective parent bodies. (Note. The DoD FESMCC representation to the LFWG will be
satisfied through DoD EDISMC membership and participation.)

Organizations not holding membership on either the FESMCC or the DoD
EDISMC may request membership in the LFWG by submission of a written request to
either co-chair. The request should document the nature of the organization’s
involvement in logistics matters, confirming that such membership does not conflict with
representation from the existing FESMCC or DoD EDISMC member Department,
Agency or Service, and a designation of a primary and alternate organization
representative(s). Acceptance of the request for LFWG membership will be discretionary
for the co-chairs based upon an assessment of the submission request and as ratified by the
LFWG membership.

The primary organizational representative (including government civil servants or
uniformed members) as well as a designated alternate voting member, shall be identified in
writing to the co-chairs. The LFWG will maintain an active list of all working group
members. Organizations are encouraged to promote continuity of representation to this
position in order to ensure a knowledgeable and consistent approach to the work of the
group.