MEMORANDUM FOR HQ DLA/DLMSO

FROM: HQ AFMC/LGIA
4375 Chidlaw Road, Suite 6
Wright-Patterson AFB OH 45433-5006

SUBJECT: MILSTRIP Change Proposal Request for Removal of Air Force “FM”
Accounts from the DoD Materiel Obligation Validation (MOV) Program

1. Originator:

a. Service/Agency: USAF

b. Originator: Bobbie Ziolek, HQ AFMC/LGIA, DSN 674-0096 (Commercial 937-
904-0096), FAX DSN 986-2079 (Commercial 937-656-2079), Email:
Ziolekb@wpgatel .wpafb.af.mil

2. Functional Area:
a. Primary: Supply
b. Secondary(ies): Financial

3. Requested Change:

a. Title: Removal of Air Force “FM” Accounts from the DoD MOV Program

b. Description of Change: The Air Force has temporarily requested DAASC to
provide automatic responses for their “FM” accounts. Request this temporary fix be
continued until further notice -- when the new DoD medical community system is
fielded.

c. Procedures: DAASC is currently providing automatic responses for AF FM
accounts by taking the “AN” document and returning it to the ICP with the “AP”
document.

d. Alternatives: For MOV cycles until the new system is fielded, the AF could
request before cach cycle that the temporary solution be continued, but the length of time
to field the new system makes this temporary solution unsatisfactory.

4. Reason for Change: DoD 4000.25-1-M, Chapter 7, prescribes policies and procedures
for user validation of the continuing need for overage requisitions and for supply source
reconciliation of MOV records with those carried as due-ins by the requisitioner.
Paragraph D states “Deployed units, afloat units, and CONUS/OCONUS locations which
are unable to acknowledge receipt, or to respond by the prescribed date, may request the
DAASO to temporarily provide responses to MOV requests. ..... The DAASC will not
generate MOV responses for any subsequent MOV cycle unless a separate message is
received.” We need DAASC to continue this automatic MOV response for FM accounts



manual accounts with no mechanized means of backorder reconciliations and no
projection for mechanizing them in the future.

5. Advantages and Disadvantages

a. Advantages: By excluding these accounts from the MOV program, overage
requisitions will be retained in the system, not automatically canceled due to non-
response. .

b. Disadvantages: None known.

6. Impact:

a. Transaction Set(s): 517

b. Publication(s): DoD 4000.25-M, Volume 1, Chapter 7. Add the following
sentence to Chapter 7, Section I, Paragraph B, Exclusions from Section I:

“Air Force “FX” Accounts are excluded from these procedures.”
Include the change in DoD 4000.25-M, Volume 2, Chapter 9, Paragraph 9.1.1.2, when
necessary.

ROBERT H. BRANT
Chief, Inventory Management Policy Branch
Ttem Management Division

ce:
HQ USAF/ILSP


until the DoD medical community fields its new system (planned in 2003). When the
new system is up, it will then provide the capability to reinstate valid requisitions [IAW
AMCL 150C.

The Air Force tracked the loss to the medical “FM” supply community when
cancellations occurred due to non-response during the last MOV cycle and found they
lost over $542,000 as a result of these types of cancellations.

5. Advantages and Disadvantages

a. Advantages: By excluding these accounts from the MOV program, overage
requisitions will be retained in the system, not automatically canceled due to non-
response.

b. Disadvantages: None known.

6. Impact:

a. Transaction Set(s): 517

b. Publication(s): DoD 4000.25-1-M. Add the following sentence to Chapter 7,
Section I, Paragraph B, Exclusions from Section I:

“Air Force “FM” Accounts (Medical) are excluded from these procedures until
further notice.”
Include this change in DoD 4000.25-M, Volume 2, Chapter 9, Paragraph 9.1.1.2, when.
necessary.

ROBERT H. BRANT
Chief, Inventory Management Policy Branch
Item Management Division

cc:

HQ USAF/ILSP


MEMORANDUM FOR HQ DLA/DLMSO

FROM: HQ AFMC/LGIA
4375 Chidlaw Road, Suite 6
Wright-Patterson AFB OH 45433-5006

SUBJECT: Request for DAAS Edit of All DoD Requisitions for Invalid/Expired CJCS
Project Codes

1. Originator:

a. Service/Agency: USAF

b. Originator: Bobbie Ziolek, HQ AFMC/LGIA, DSN 674-0096 (Commercial: 937-
904-0096), DSN Fax 986-2079 (Commercial 937-656-2079) Email address:
ziolekb@wpgate1.wpafb.af.mil

2. Functional Area: Primary: Supply

3. Requested Change:

a. Title: Request for DAASC Edit of All DoD Requisitions for Invalid/Expired
Project Codes.

b. Description of Change: DoD policy directs that customers determine and
communicate relative precedence of materiel requirements by application of priority
designators, required delivery dates, and approved OSD/CJCS project codes. However,
there is currently no mechanism in place in the requisition process to validate “approved.
OSD/CICS project codes.” A DAASC edit for invalid/expired project codes would
validate correct codes for continued requisition processing.

c. Procedures: The Air Force recommends that the Supply PRC approve DAASC
editing all DoD requisitions for invalid/expired CJCS project codes. If this is approved,
the PRC should determine whether the edit should reject requisitions with invalid/expired
project codes back to the requisitioner for correction; or blank the project code of the
requisition, forward it for processing, and report back to the requisitioner in an AE_
transaction that the project code was edited out because it was invalid/expired.

In order for DAASC to have the latest Project Code list from which to validate
during requisition processing, the Air Force recommends that the J4 build and maintain
an electronic database of current Project Codes, Uses/References, and Duration Dates
(other information, if needed) for DAASC to access. By accessing this electronic
database, the DAASC will be able to develop and be current in its validation edit criteria.
Until this data file is developed for DAASC access, however, the J4 should provide
DAASC the current list of Project Codes, etc., by including DAASC in its messages


(quarterly or as needed) identifying additions/deletions/corrections to Project Code
information.

4. Reason for Change: The Air Force conducted a test on Project Codes in May 98 by
directing DAASC to edit all Air Force “A0_”, “AM_”, and “AT_” transactions based on
the latest J4 message of valid CICS project codes. This edit rejected requisitions with
invalid/expired CICS project codes and provided data that showed AF compliance/non-
compliance with current policy. DoD 4140.1-R, directs that customers determine and
communicate relative precedence of materiel requirements by application of priority
designators, required delivery dates, and approved OSD/CJCS project codes. In addition
DoD 4000.25-1-M (Appendix B13) specifies criteria, responsibilities, controls, and
methodology for determining assignment and use of CJCS project codes. The monthly
reports to Air Force from their test resulted in changes to training programs and
significantly reduced the number of invalid/expired CJCS project codes on AF
requisitions. Since there were significant numbers of requisitions affected for the AF, we
feel there are also numbers of requisitions with invalid/expired CJCS project codes from
other DoD requisitions that are still being processed through the existing, non-edited
requisition process.

5. Advantages and Disadvantages:

a. Advantages: CICS Project Code messages state: “For processing purposes,
requisitions with CICS Project Codes will be ranked above all others with the same issue
priority designator when system wide supply inventory levels do not permit positive
supply action on all requisitions.” Therefore, since the Project Code is a determinant for
relative precedence of material requirement, such an edit would ensure that the
requisition data for that code is valid.

b. Disadvantages: None known.

6. Impact: Publications

Include information about the edit procedure and the J4 Project Code electronic
database in DoD 4000.25-1-M, Appendix B13 as they are developed and in DoD
4000.25-M, DLMS, as necessary.

ROBERT H. BRANT
Chief, Inventory Management Policy Branch
Item Management Division

ce:
HQ USAF/ILSP
HQ AFMC/LGSW


MEMORANDUM FOR HQ DLA/DLMSO

FROM: HQ AFMC/LGIA
4375 Chidlaw Road, Suite 6
Wright-Patterson AFB OH 45433-5006

SUBJECT: MILSTRIP Change Proposal Request for Removal of All Air Force “FX”
Accounts from the DoD Materiel Obligation Validation MOV) Program

1. Originator:

a. Service/Agency: USAF

b. Originator: Bobbie Ziolek, HQ AFMC/LGIA, DSN 674-0096 (Commercial
937-904-0096), FAX DSN 986-2079 (Commercial 937-656-2079), Email:
Ziolekb@wpgatel .wpafb.af.mil

2. Functional Area:
a. Primary: Supply
b. Secondary(ies): Financial

3. Requested Change:

a. Title: Removal of All Air Force “FX” Accounts from the DoD Materiel
Obligation Validation (MOV) Program

b. Description of Change: The Air Force has temporarily requested DAASC to
provide automatic responses for their “FX” accounts. Request a permanent change to
exclude ALL AF FX Accounts from the MOV Program.

c. Procedures: Instead of the temporary fix (DAASC is currently providing
automatic responses by taking the “AN” document and returning it to the ICP with the
“AP” document), supply sources would program an edit into their systems to preclude
generation of the AN_ transaction for all FX accounts.

d. Alternatives: The AF could request the temporary solution be continued
indefinitely.

4. Reason for Change: DoD 4000.25-1-M, Chapter 7, prescribes policies and procedures
for user validation of the continuing need for overage requisitions and for supply source
reconciliation of MOV records with those carried as due-ins by the requisitioner.
Paragraph D., states “Deployed units, afloat units, and CONUS/OCONUS locations
which are unable to acknowledge receipt, or to respond by the prescribed date, may
request the DAASO to provide responses to MOV requests. ..... The DAAS will not
generate MOV responses for any subsequent MOV cycle unless a separate message is
received.” We need a permanent exemption because the FX accounts are currently