1 / 2

DMISA Asset Visibility

DMISA Asset Visibility. Non-reporting DMISA repair sites - AF (D035A) has no visibility that anything ships. The first indication is a D6 receipt transaction. - No PMR. D035A depends on transaction from repair site saying asset shipped to create PMR.

beata
Download Presentation

DMISA Asset Visibility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DMISA Asset Visibility • Non-reporting DMISA repair sites - AF (D035A) has no visibility that anything ships. The first indication is a D6 receipt transaction. - No PMR. D035A depends on transaction from repair site saying asset shipped to create PMR. - Retrograde tracking…makes computing retrograde metrics a time consuming/painful effort. - Non Reporting Sites (there may be more): - - M94602 Albany, GA - - N39712 Cherry Pt, NC - - N39823 Jacksonville, FL - - N60012 San Diego, CA • Each site has a collocated DSS storage facility. • For the Albany, GA site, the Air Force ships most of their retrograde assets to the DSS DODAAC (SW3121). These assets just "disappear" when local maintenance pulls them out of storage. • For the other three sites, Air Force does not ship retrograde assets to the DSS DODAAC. AF ships to a separate non-DSS (Navy) receiving location at Cherry Pt, Jacksonville, and San Diego.

  2. DZC Transaction • Issue: DZC transactions being used to change ownership between Services (by Services and DLA). For MSD materiel, DZC transaction does not generate the required receipt transaction to the gaining item manager's data system, so credit is not granted to losing item manager's system. - DZC is part of the MILSTRAP Logistics Reassignment process (part of a pair…DZC/DEE) - - Losing data system posts a D9E inventory loss, sends DZC to DSS and sends DEE to gaining system – (gaining system picks up assets using D8E inventory gain) - - DSS send history transaction showing inventory gain/loss. No credit logic tied to DZC. Credits are tied to D7P issue transactions and D6B or D6R receipt transactions. • Example: Both Corpus Christi and Tobyhanna are DOD SOR. All Services ship CC “F” assets to be repaired. If those assets get put in the wrong ownership, both sites demand “DZC” • Proposed Solution: • DZG reject transaction (defined in MILSTRAP). Storage activity uses this transaction (from Service) to reverse the D6 transaction with wrong ownership RIC and to post a corrected D6. AF (D035K) sends these reject transactions – DLA said don’t ignore rejects but doesn’t know where they go (took action in Sept 12 to investigate)

More Related