Item #

Location

DS 8461 Change Table
Asset Status Inquiry/Report

Reason

1/N106/080

Add new DLMS notes | and 2 to FR-Message From, and
renumber ting note as 2:

FR Message From

DLMS Notes:

I. Use to identify the activity preparing the asset status report,
except as noted at DLMS note 3 below.

2. For DLA industrial activity support agreement, cite code
‘SB’ to identify the DLA DSS storage activity preparing the
Asset Status Report on behalf of the owning ICP. The owning
ICP, when not the activity originating the transaction set,
appears in 2/N101/450

3. For Army/DLA DDKS interface in a mixed DLSS/DLMS
environment, based upon agreement, the DLA storage activity may
prepare the 8461 on behalf of the DLA ICP, with the DLA ICP RI
Code SMS entered as the ‘Message From’ activity originating the
transaction. This is an interim DDKS approach in the mixed
DLMS/DLSS environment to accommodate Army’s requirement
for the owning ICP to map to the DLSS DI Code DZA rp 67-69,
which is identified as the RI Code of the ICP preparing the
transaction. As Army transitions to DLMS, the 1/N106/080 FR
should reflect the true activity preparing the transaction set, and the
appropriate qualifier for storage activity or ICP preparing the
transaction should be used. The information on the owning ICP or
storage activity, when not the activity originating the transaction
set, should appear in 2/N101/450. See ADC 250. Any future DLA
Distribution Standard System (DSS) implementation should use the
alternative approach documented in ADC 250.

To accommodate BRAC
requirement for DLA DSS
storage activity to provide
Navy with asset status
information.

2/LIN02/10

Revise the data element level note and add the following
qualifiers and DLMS notes:

DLMS Note: 1. Use only one of Al, A2, A4, FB, FS, MG, YP or
ZR to identify the item reported. Must use National Stock Number
(NSN) when known except when appropriate brand name
subsistence items are identified by the Subsistence Identification
Number or when industrial activity materiel is identified by
Material Control Tracking (MCT) Tag Number.

ZR Service Control Identification

DLMS Note: Use to identify Materiel Control Tracking (MCT)
tag number. The MCT tag number is an authorized DLMS
enhancement for DLA industrial activity support agreement
only; see introductory DLMS note 4e, Refer to PDC 393 and
ADC 374.

Supports Navy BRAC Spiral
II requirements.

4o0f9

ADC 374 ATT



ORGANIZATION RESPONSE/COMMENT DLMSO RESOLUTION

DLMSO There is a conflict which the BRAC SS&D IMSP Team must For IMSP Team
resolve between the DLA and Navy responses to staffing notes | resolution. No known
below regarding the ‘end of day’ asset status report transaction impact to DLMS 8461
(the DLMS transaction accommodates either approach and no transaction.

change to the 846] is required):

End-of-day Processing Indicator (BIA06 Action Code EO)
A code indicating the Asset Status Report transaction is the result of end-of-day processing.

PDC STAFFING NOTE on End of Day transaction: As discussed during Navy BRAC IMSP SS&D Team meetings, DS
8461 transaction is capable of including all end of day asset status report transactions for a given recipient in a single 8461
transaction through transaction looping. Except that ‘unit of use’ asset status report transactions could not be combined
with asset status report transaction not associated with unit of use. This is because the unit of use flag will also be at the
beginning segment level (Refer to PDC 366A” for unit if use data/information).

DLMSO ADC NOTE: DLA and Navy provided conflicting responses to the staffing notes on use of looping for the
end-of-day 8461 Asset Status Report. The responses are highlighted in yellow below, and must be resolved by the
BRAC SS&D IMSP Team. The DLMS 846I transaction is capable of accommodating either approach.

PDC STAFFING NOTE FOR DSS on End of Day transaction: Request DSS comment on their capability to provide the
‘end of day’ asset status reports in a single 8461 for a given recipient (except for separation by unit of use as noted). DSS
RESPONSE: 5/19/2010 (Dave G) Changing the 8461 to a single looping transaction per recipient would cause significant
software changes for DSS that have not been planned for in the DSS 10.2 or 11.1 Release. At this point in time we don't
want to change to a single looping transaction.

Although we're adding some data elements for the 8461 we don't want to modify the entire process to include looping. We
would also have to extensively test it for all our other trading partners that receive 8461s. We're not planning to develop a
special 8461 process for the Navy. The 940S is a new transaction specifically for the Navy so it doesn't have the impact that
modifying the 8461 process will have.

PDC STAFFING NOTE FOR NAVY on End of Day transaction: Request Navy comment on whether they would be
interested in receiving all ‘end of day’ asset status report transactions in a single 8461 (except broken out by ‘unit of use’ as

noted above, if DSS is able to provide it that way. If yes, would Navy want separate end-of-day transactions for DLA owned
assets and Navy owned assets?

NAVY RESPONSES:

FRC: 5/25/2010 (Teri H) - FRC would like one transaction for Navy owned, one transaction for DLA owned. DLA is sent
multiple times during the day, Navy and DLA are sent end-of-day. Unit of use does not apply to these. The transactions
should reflect the LSN and reference the NSN for the unit of use balances regardless of owner.

NSY: 5/26/2010 (Joe K) - They have three separate requirements

1) MSM non document both Navy and DLA owned quantities to update MSM quantities for beginning of next day operations
2) Navy owned and DLA owned document number material can be in one set (ensure that quantities and locations are current)
3) Two sets of 8461 a. MSM, b. documents

Critical Design | Navy FRC wants a single 8461 by owner/NIIN/Condition code (no location) | This issue is for
Review (CDR) but needs to confirm. This applies to daily and end-of-day 846Is. DSS will IMSP Team
Action Item #24 | ensure that end-of-day balances match FRC. Need to discuss/work out resolution. No
“looping” details between DSS and FRC/NSY. NSY also wants “looping”. | Known impact to
Chris Oxley will send data to Bob. DEMS ao
POC: Russ Taylor (J6U), Teri Hourihane (FRC), Chris Oxley (J6U), Brad | "@nsaction.
Overton (NSSG), Joe Kill (NSY), DLMSO

Enclosures

9 of 9
ADC 374 ATT



Item #

Location

DS 8461 Change Table
Asset Status Inquiry/Report

Reason

9.

2/REFO1/140

Add the following qualifiers and DLMS notes:

9R Job Order Number

DLMS Notes:

1. Use to identify Job Order (JO) Number. For use with Navy
Shipyards.

2, Authorized DLMS enhancement for DLA industrial activity
support agreement; see introductory DLMS note 4e. Refer to
ADC 374.

86 Operation Number

DLMS Notes:

1. Use to identify the key operation (KO) number. For use with
Navy Shipyards.

2, Authorized DLMS enhancement for DLA industrial activity
support agreement; see introductory DLMS note 4e. Refer to
ADC 374.

PWC. Preliminary Work Candidate Number

DLMS Notes:

1. Use to identify Requisition Alert Document Number, For use
with Navy Shipyards.

2, Authorized DLMS enhancement for DLA industrial activity
support agreement; see introductory DLMS note 4e. Refer to
ADC 374,

CO Customer Order Number

DLMS Notes:

1. Use to identify the Customer Order Acceptance Record
(COAR).

2. Authorized DLMS enhancement for DLA industrial activity
support agreement; see introductory DLMS note 4e. Refer to
ADC 374,

Supports Navy BRAC
Spiral II requirements.

€Adding COAR per
IMSP Team decision
during DSS Critical
Design Review (CDR).

2/REF04-
01/140

Open REF04 and add the following qualifier to REF04-01 with
DLMS note”

WS8 Suffix

DLMS Notes:

I, Use with REFO1 code PWC to identify the Requisition Alert
Document Number suffix. For use with Navy Shipyards.

2. Authorized DLMS enhancement for DLA industrial activity
support agreement; see introductory DLMS note 4e. Refer to
ADC 374.

Supports Navy BRAC
Spiral II requirements.

6 of9

ADC 374 ATT



Ttem # Location DS 8461 Change Table Reason
Asset Status Inquiry/Report
fy 24LENO4H0 Add 4 Jifier RY for MCE+ a fF}; ith DLMS te: § upports IN ayy 3 RAL
RV Repair Fag Number
PES INE C6 E At MLE EEN Cote eRe terrncne SreneSaeee Deleting MCT Tag
fag.naniber sige Number Suffix per IMSP
Team decision.
6. | 2/DTMO1/ For existing qualifier 600, add new DLMS Note 4. To document that the ‘as of
100 date used in asset status report
600 As Of to support BRAC SS&D IMSP.
DLMS Notes:
1. Use for asset status reports to identify the date associated with This date is expressed in UTC.
the inventory information (date transaction was prepared). Express | The UTC is used almost
this date in Universal Time Coordinate. universally to designate
2. Used between the Army and DLA to determine the most current | “ate/time information that is
asset posture for assets stored under DLA/SMS ownership when He eal aa ie
more than one asset report is received within the same cycle. San an “a inting actual
3. Navy uses this date intra-Navy to determine the most current time in aE eckinie Zones, USS
asset posture when more than one asset report is received within the | orto will impact any system
same cycle. This equates to intra-Navy prescribed data in which has already implemented
MILSTRAP DZA multiuse field, rp 73-75. Refer to ADC 355. DS 8461 and did not use UTC.
4, Used to support DLA industrial activity support agreement.
7. | 2/DTM03/ Revise DLMS note 3 and add new DLMS note 5: To provide the time the
100 DLMS Notes: transaction was prepared.
1, Use in conjunction with DTMO1 code 600 only to identify the a P
time the transaction was prepared. , The UTC is used almost
2. Express time in a six-position (HHMMSS) format in UTC. universally to designate ,
3. Except as noted below, DLMS enhancement. See date/time information that is
introductory DLMS note 4.a. time sensitive and requires
4. Used between the Army and DLA to determine the most current | identification to a specific
asset posture for assets stored under DLA/SMS ownership when time zone for pin-pointing
more than one asset report is received within the same cycle. actual time in other time
5. Authorized for use to support DLA industrial activity zones.
support agreement; see introductory DLMS note 4e. Refer to
ADC 374.
8. | 2/REFOI/140 Revise DLMS note | and add new notes 2 & 3 for existing qualifier Supports Navy BRAC
Qualifier BO | ‘BO’: Spiral II requirements.
Pee ge cation Number DLA DSS will use this
1. Authorized for intra-Navy use only; to identify the warehouse field to pass the physical
bin location For-alLother-use-this-is-¢ DEMS-enhaneement; — | location of material at a
sec-introduetory DEMS -note4a, Refer to ADC 356. BRAC SS&D sites.
2, DLA uses to pass the physical location of material at SS&D
IMSP sites. Authorized for use to support DLA industrial
activity support agreement; see introductory DLMS note 4e.
Refer to ADC 374.
3. Except as noted above, this is this is a
DLMS enhancement; see introductory DLMS note 4a.

Sof9

ADC 374 ATT



ce, DAASC Mapping. Update DAASC maps to allow new data to pass any applicable edits.

d. DLMS Data Elements. See Enclosure 2 for DLMS Data Elements DLA identified for inclusion in 8461.

10. COMMENTS TO PDC 394 provided below:

ORGANIZATION RESPONSE/COMMENT DLMSO RESOLUTION
NAVY (NAVSUP) Navy concurs with PDC 394 as written and submits no Noted.

additional changes or amendments.

Navy Question

NAVY QUESTION: Do you have any documentation that reflects the Navy Owner RIC,
We're looking at the from's and to's within the transaction and are having difficulty making the
owner RIC fit into those scenarios."

DLMSO RESPONSE: When DSS is preparing the 8461, the RIC of the storage activity
creating the transaction will be in 1/N101/080/SB. The information on the owner, when the
owner is not the activity originating the transaction set, appears in 2/N101/450.

846] has the following qualifiers (KA and N4) at 1/N101/450 which can apply as follows:

When DSS is preparing the 8461 to send to FRC/NSY for NAVY owned materiel, qualifier Z4
applies with Z4 being both the TO RIC as well as the RIC of the owner. Qualifier KA is not
used in this scenario.

When DSS is preparing the 8461 to send to FRC/NSY for DLA owned materiel, then qualifier
ZA is used to identify the Navy RIC the transaction is being sent TO; and qualifier KA identifies

the DLA owner RIC (SMS).

DLA (DLA HQ J-33)

DLA concurs.

Noted.

DLA Comment as a 1. Asa result of IMSP Team discussion during the May 24-28, | Added COAR. See 8461
result of DSS Critical | 2010, DSS CDR, DLA identified requirement to include the Change Table, row 9 on
Design Review (CDR) | COAR in numerous transactions to include DS 8461. page 6 of this ADC.
and IMSP Team (IMSP Team requirement for COAR was identified for 511R, 511M,
Decisions 527D, 527R, 9471, 940R, 945A, 8671, 869A, 869C, 869F, 870S, 856S,
846P, 842C, 870M,846A, 8461, 940S and 943A. COAR will be added
to most transactions by ADC 381 (under development) which will
approve PDC 366A. Deleted MCT Tag,
2. IMSP Team decision: Delete MCT Tag Number Suffix. pidilbaesuiiihs, Secu
Change Table, row 5 on
page 5 of this ADC.
MARINE CORPS Concur without comment Noted.
DLMSO MILSTRAP Administrator revising DLMS notes for 2/N101/450 Revised DLMS notes for

qualifiers ‘KA’ and *Z4’ to replace the term "owning ICP" in the
DLMS notes with the word "owner".

RATIONALE: “Owner” is more generic and meets evolving
requirements of 846] Asset Status Report. Requirements for 8461
use have evolved beyond the original ICP to ICP requirement. This
revision provides a more generic DLMS note which accommodates
both the original MILSTRAP use and the evolving use of Asset
Status Report under DLMS.

BACKGROUND: “Owning ICP” terminology was originally used
when 8461 was developed because under MILSTRAP, the
corresponding DZA transaction was a wholesale transaction sent from
ICP to ICP.

2/N101/450 qualifiers
“KAY and ‘Z4’ as
discussed at left.

See 8461 Change Table,

row 11 on page 7 of this
ADC,

8 of 9

ADC 374 ATT



IN REPLY
REFER TO

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

DLMSO June 24, 2010

MEMORANDUM FOR NAVY AND DLA SUPPLY PROCESS REVIEW COMMITTEE (PRC)
MEMBERS

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 374, Revise
DLMS 846] Asset Status Report in Support of Navy BRAC SS&D/ IMSP (Supply)
(Staffed as PDC 394)

The attached change to DOD 4000.25-M, DLMS, is approved for implementation. The
updated DLMS Supplements will be posted to the Defense Logistics Management Standards Office
(DLMSO) Web site http:/Avww.dla.mil/j-6/dlmso/elibrary/TransFormats/formats.asp in conjunction
with other related changes supporting the Navy Base Realignment and Closure (BRAC). It is
anticipated that the finalized DLMS Supplements will be available in late June-early July. This change
is required for an upcoming release to support Defense Logistics Agency (DLA) and Navy BRAC
Retail Supply, Storage and Distribution (SS&D)/Inventory Management and Stock Positioning
(IMSP).

DLA J-33 will provide procedures for the Navy BRAC SS&D/IMSP processes for inclusion
in DOD 4000.25-M, DLMS, Volume 2. Depending on DLA's approach, the overall procedures will
either be published under a separate ADC as a chapter to the DLMS manual, or specific procedures for
each process may be published as addendums to the various BRAC SS&D/IMSP ADCs.

Addressees may direct questions to the DLMSO point of contact Ms. Mary Jane Johnson,
email: Mary.Jane.Johnson@dla.mil. Others must contact their Component designated Supply
PRC representative.

nal

ONALD C, PIPP

Director
Defense Logistics Management
Standards Office

Attachment

ce:

AUSD(L&MR)SCI

Supply PRC members for remaining DOD Components
Joint Physical Inventory Working Group (JPIWG)


ENCLOSURE 2 TO ADC 374

The following new DLMS data elements identified for 8461 Asset Status Report [PDC 366A‘

addresses DS 846] requirement for a unit of use data to include a unit of use flag and associated

materiel identification, which is not identified in this ADC):

8461 Location DS 8461 Data Usage Notes/ Field
Content Definition for Unique or Non-Standard Data Elements Length
1/BIA06/EO Action tndicator A code indicating the Asset Status Report transaction is the result of end- | 2
EO-End of Day | End-of-day of-day processing.
Processing. Processing Indicator
2/REFO1/140/9R | Job Order (JO) JO Number: Used at by NSY maintenance activity identifying a particular 10
Number? package of work. The first two positions are the Work Category Number, the
next three positions are the Availability Number, and the remaining five
digits make up the Work Breakdown Structure.
Original Requisition alert Document number, suffix code and JO will be key
data elements to releasing protected stock at Naval Shipyards.
Alpha/Numeric Field
Mandatory, applicable to both funded and unfunded requisitions at NSY sites.
2/REFO1/140/86 | Key Operation (KO) | KO Number. The logical division of a JO which may be scheduled to be 3
Number performed without significant interruption, and which can be closed out to
further charges upon completion. This value will be a reference field on all
transactions.
Alpha/Numeric Field
Mandatory, applicable to both funded and unfunded requisitions at NSY sites.
2/LINO2/10 Material Control Material identification number applicable to items in courtesy storage (e.g. 32
Tracking (MCT) Tag | Ripout, prefab) on behalf of the Navy while specific maintenance is being
Number performed.
Will be on 940R, 945A, 8671, 527D, and 527R for Navy owned assets on
DSS records (Refer to PDC 393) and it will be on 940S and 943A (Refer to
PDC 384)
This field will not be used when the LSN or NSN is the primary material
identification.
2/LINO4H0 Material Control Suffi to MCE numbers £ om iat iit a
Tracking (MCB) d-from-the-original- component-it th IL MCE tac
Tag Number Suffix | tracking purposes—This-data-el twill ted jated-d " .
in- the MCT-number-field-with-a-hyph dine-the-data-el ean
phen pi
Will be on 940R945A_ 8674 S27D_and S27R for Navy owned assets on
PDE384)
This-field-will noth d-when-the LSN-or NSN-is-the-primary-material
identification!
IMSP Team decision was to delete MCT Tag Number Suffix.
' PDC 366A (reference 3c) adds the unit of use ‘flag’ and unit of use materiel identification to numerous DLMS
Supplements (DS) including 8461.
PDC 366A (reference 3c) identifies numerous additional DLMS transaction to have the JO and KO number.
> PDC 393 (reference 3d) addresses use of the MCT Tag number and suffix, under Navy BRAC SS&D IMSP.
lof 2
ADC 374

Enclosure 2



ENCLOSURE 1 TO ADC 374
Process Flow

12.3: Inventory On Hand Update — FINAL

Pull DZA (846!)

| el,
EE |

DZA(8461) MRPII
2 IF24

DZA
8461

eo—_T]

Funded
Requjgiton

} Dss
1A Worksite

Receiving

ee a cre

20100603_Inventory_On_Hand_Upate_FINAL

1. DSS generates 8461 DZA (to include physical location, document number and JO/KO as
applicable) and passes to DAASC -> 2

a. DSS will provide individual 8461 (DZA) as the result of balance affecting transactions by
owner RIC during daily processing and updates. To include those balances going to zero qty.

b. DSS will provide end-of-day 8461 (DZA) as a snap shot “in time” of all assets stored by
owner RIC within the DSS IA Worksite

2. DAASC receives and passes the 8461 ->2a, 2b
2a. DAASC will pass NSY 846I’s to the NSY pull queue -> 2a1
2b. DAASC will pass FRC 8461's to IF24 -> 2b1

2a1. PSI/OF transfers to MAT. -> 2a2
2a2. MAT updates inventory balance. -> END
2b1. IF24 updates MRP Il with inventory balance -> END

lof
ADC 374
Enclosure 1
Process Flow


Ttem # Location DS 8461 Change Table Reason
Asset Status Inquiry/Report
11} 2/N101/450 Revise DLMS notes for existing qualifier Z4 as follows: Supports Navy BRAC

Z4 Owning Inventory Control Point

DLMS Note:

1. Use to indicate the owning inventery-contrel point owner or
other activity to which the transaction is being forwarded.

2. When the activity to which the transaction is being
forwarded is not the ewaing ICP owner, then qualifier KA must
also be used to identify the ewning ICP owner.

KA Item Manager
DLMS Note:

Use for asset status reports to identify the owning ICP owner
when different from the 1/N101/080 organization originating the
transaction set, and the 2/N101/450/Z4 organization is not the
owning ICP owner.

Spiral II requirements.

MILSTRAP Administrator
revising term “owning
ICP” to “owner” for more
generic terminology
supporting evolving use of
Asset Status Report.

(See paragraph 10 below,
‘Comments to PDC 394’,
DLMSO comment at row 6.)

5. ALTERNATIVES: None identified.

6. REASON FOR CHANGE: DLA requires ability to pass on-hand asset balances to the Navy
BRAC SS&D sites on a regular basis to continue with the planning applications to process
correctly within the Navy systems.

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Enterprise Business System (EBS), Material Access Technology (MAT),
Material Resource Planning (MRP) II and Distribution Storage System (DSS), will be able to
comply with DLMS standards for the BRAC IMSP Spiral 2 process.

b. Disadvantages: None identified.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: DLA and Navy planned
implementation date is December 2010.

9,

IMPACT:

a. Publications:

(1) Requires update to DLMS 8461 Asset Status Report transaction.

(2) Requires update to DOD 4000.25-M, DLMS, to add procedures for the BRAC SS&D/
IMSP process described by this PDC. DLA J-33 to provide procedures for the DLMS manual, Vol 2.

b. Automated Information Systems (AIS): DLA Distribution Storage System (DSS), Navy
Material Access Technology (MAT), and Navy Material Resource Planning (MRP) II systems.

Tof9

ADC 374 ATT



‘balance affecting’ transaction set. A beginning segment Action Code ‘EO-End of Day Processing’

is being added to the 846] to identify when an end-of-day Asset Status Report transaction is being
provided.

STAFFING NOTE: The end of day 8461 (MILSTRAP DZA functionality) Asset Status Report does not
replace the DOD Physical Inventory Control Program (PICP) End of Day process! whereby the storage
activity submits the daily closing on-hand balance to each affected owner/manager using DLMS 846R
(MILSTRAP DZH) Location Reconciliation Request Transaction, The PICP end of day process would not
provide Navy on-hand balance information for DLA owned assets. The PICP program does provide the on
hand balance information for Navy owned assets at DLA storage activities.

(7) Balances for DLA owned assets are reflected at the material number and condition code level.
There will be instances when DLA has re-identified the material to an LSN to accommodate the unit of
use requirement to issue material at less than the standard FLIS unit of issue.” The 8461 will contain a
unique flag indicating both the LSN and associated NSN are reflected in the transaction(s). The NSY or
FRC system will map the applicable material number to appropriately reflect the on-hand balance.

(8) The requirement is to provide the actual physical warehouse location of the assets for both FRC
and NSY sites. The associated requisition alert document number and JO number are also required at NSY
sites. These data elements are being added to 8461.

d. Revise DS 846I Asset Status Report as shown in Change Table (includes administrative
changes made to change the term ‘BRAC SS&D/IMSP?’ to ‘DLA industrial activity support agreement’):

Item # Location DS 8461 Change Table Reason

Asset Status Inquiry/Report

1. | DLMS 374 to DLMS Introductory note 6. To identify DLMS changes
Introductory ise DLMS 8461, Asset Status Report, in Support of included in the DS.
Note 6. Navy BRAC SS&D/IMSP (Supply).

2. | 1/BIA06/20 Open the BIA06 Action Code, add qualifier ‘EO’ with DLMS notes: | To accommodate Navy
BRAC requirement for an

EO End of Day Processing end of day Asset Status
DLMS Notes: 1. Use to identify that an end-of-day Asset Status | Report in addition to the
Report transaction is being provided. Authorized DLMS reports submitted throughout
enhancement for use by DLA industrial activity support the day.

agreement; see introductory DLMS note 4e. Refer to ADC 374.
2. Implementation Note: This is an X12 migration code
approved for use in version 5030. Implementers must manual
update 4010 software to recognize this code.

3. DLMS enhancement, except as noted for DLA industrial
activity support agreement. See introductory DLMS note 4a.

' Refer to DOD 4000.25-M, DLMS, Volume 2, chapter 6, or DOD 4000.25-2-M, MILSTRAP, Chapter 7 for Physical
Inventory Control procedures. Both DOD manuals are available at: https:/Avww.dla.mil/j-
6/dimso/eLibrary/Manuals/dimso_pubs.asp.

? PDC 366A (reference 3c) adds the unit of use ‘flag’ and unit of use materiel identification to numerous DLMS
Supplements (DS) including 8461.

3 0f9
ADC 374 ATT



The intent of the directive is to significantly improve combat effectiveness while reducing costs by
developing a world-class, cost-effective supply chain focused on readiness; taking every opportunity
to eliminate waste, reduce touches, reduce cost, and improve readiness. DLA has the requirement to
provide on-hand asset balances to both FRC and NSY systems, and the capability to provide these
balances for both DLA owned and local Navy owned assets for informational purposes multiple
times daily, when a balance is updated. The FRC has requested only DLA assets with an on-hand
balance change be reported during an update prior to end-of-day processing. NSY sites have
requested both DLA and Navy owned assets with an on-hand balance change be provided prior to
end-of-day processing. Both FRC and NSY will be provided asset balances for both DLA and Navy
owned assets during the end-of-day processing.

c. Detailed Procedures:

(1) NSYs and FRCs have scheduled maintenance periods dictated by JCS, NAVSEA and
NAVAIR requiring material to be on-hand in ready for issue condition for the artisan to begin and
complete the maintenance on time. DLA has a requirement to provide NSY and FRC sites with the on-
hand balance information of inventory stored in the Industrial Activity (IA) worksite on a daily basis.
The physical location will be included on the 846I transaction to both FRC and NSY, while the
requisition alert document number and associated job order (JO) number will be provided to NSY sites.

(2) Inventory balances in DLA ownership physically located within the [A worksite will be
provided to FRC multiple times daily, to include balances which have reached a zero quantity. The
end-of-day balances will reflect only positive balances in both DLA and local Navy ownership. Re-
warehousing request resulting in an increase or decrease in a balance within the IA worksite should
be included in the ‘balance affecting’ transaction set.

(3) Inventory balances in DLA and the local Navy ownership physically located within the
IA worksite will be provided to NSY multiple times daily, to include balances which have reached a
zero quantity. The end-of-day balances will reflect only positive balances in both DLA and local
Navy ownership. Re-warehousing request resulting in an increase or decrease in a balance within
the IA worksite should be included in the ‘balance affecting’ transaction set.

(4) NSY systems will use the on-hand inventory to determine stock availability in support
of specific maintenance jobs associated with document number and JO number combinations (Key
Operation (KO) number will also be provided for information as applicable). NOTE: NSY sites
will use the Asset Report Status/Inquiry (8461) to determine availability of Navy owned Mission
Support Material (MSM) balances not tied to Document number and JO until Navy owned assets
have been exhausted.

(5) FRC systems will use the on-hand inventory provided as a result of the daily processing
as informational data to assist the Planners in scheduling maintenance jobs. Balances provided
during the end-of-day processes will be used to perform the nightly netting process and generate
requisition alerts.

(6) Balances being provided during daily processes will be generated as the result of DSS
process balances affecting transactions. e.g., receipts, issues, inventory adjustments and denials.
Re-warehousing request resulting in the balance within the IA worksite should be included in the

20f9
ADC 374 ATT


ATTACHMENT TO ADC 374
Revise DLMS 846I Asset Status Report in Support of Navy BRAC SS&D/IMSP (Supply)

1. ORIGINATOR:
a. Service/Agency: Defense Logistics Agency
b. Originator: DLA J-331, 703-325-1924 (DSN 427)

2. FUNCTIONAL AREA: Primary: Supply/Logistics.
3. REFERENCES:

a. Functional Requirements for DLA’s implementation of Base Realignment and Closure (BRAC)
Retail Supply, Storage And Distribution (SS&D)/Inventory Management and Stock Positioning
(IMSP) Spiral 2

b. DLMSO memorandum, April 8, 2010, subject: PDC 360A, Establishment of DLMS
Supplement (DS) 832N, Catalog Data Support for Navy BRAC SS&D Inventory Management and
Stock Positioning (IMSP), available at http:/Awww.dla.mil/j-6/dlmso/eLibrary/Changes/proposed.asp

c. DLMSO memorandum, May 6, 2010, subject: PDC 366A, Procedures and Additional Data Content
supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy BRAC
SS&D/IMSP (Supply/Finance), available at http:/Avww.dla.mil/j-6/dlmso/eLibrary/Changes/proposed.asp

d. DLMSO memorandum, April 16, 2010, subject: PDC 393, Document Process for Material
Control Tracking (MCT) Tag Number and Revise DLMS 527D, 527R, 8671, 940R, and 945A in
Support of Navy BRAC SS&D/IMSP, available at http:/Avww.dla.mil/j-
6/dimso/eLibrary/Changes/proposed.asp

e. AT&L Memorandum transmitted April 21, 2010, subject: Proposed Changes in support of Navy
BRAC IMSP Spiral II. This memo documents ADUSD(L&RM)SCI direction provided to DLA and Navy
authorizing immediate implementation of this DLMS change

4, REQUESTED CHANGE: Significant revisions subsequent to PDC 394 staffing are highlighted
in yellow.

a. Description of Change: This change request is for modification to the current process for the
DLMS 846] Asset Status Reporting, and for additional data elements to support the maintenance
mission at the BRAC SS&D sites. Refer to Enclosure 2 for the associated process flow.

b. Background: Asa result of the 2005 BRAC decision, retail supply, storage and distribution
functions and associated infrastructure supporting the Navy industrial/maintenance sites will transfer
to DLA. The Navy sites consist of 2 Naval Shipyards (NSY) and 3 Fleet Readiness Centers (FRCs).

1 of 9
ADC 374
Attachment


8461 Location DS 8461 Data Usage Notes/ Field
Content Definition for Unique or Non-Standard Data Elements Lengths
2/REFO1/140/ Requisition Alert Document number reflected on the initial requisition alert which is an 14
PWC Document Number* | unfunded request used only by the Navy (FRC/NSY) in support of the DLA-
Navy BRAC interface.

2/REF04- Requisition Alert This is the suffix code reflected on the original requisition alert. 1
01/140/ W8 Document Suffix Code
2/REF01/140 Customer Order COAR, this will reflect the Work Category Number (position 1-2) and the 5

Acceptance Record
(COAR)

Availability Number (position 3-5). Alpha Numeric field. Customer order
for which reporting is required.

New requirement subsequent to PDC, added as a result of DSS Critical
Design Review IMSP Team discussion/decision May 24-28, 2010.

* PDC 366A (reference 3c) provides procedures and content for the requisition alert transaction. The requisition alert
allows Navy BRAC IMSP sites to notify DLA of their requirements in advance of the funded requisition, thereby allowing

DLA to procure and position materiel appropriately to support prompt order fulfillment. PDC 366A identifies numerous

additional DLMS transaction to have the requisition alert document number.

2 of 2

ADC 373
Enclosure 2