CARCASS TRACKING

  • View
    66

  • Download
    0

Embed Size (px)

DESCRIPTION

Navy Supply Information Systems Activity. CARCASS TRACKING. Presented to: DLMSO PRC Committee Presented by: Gerald O’Sullivan . Ready. Resourceful. Responsive!. Agenda. Purpose of Carcass Tracking Overview of Repairable Process Item Pricing BK_ Processing - PowerPoint PPT Presentation

Text of CARCASS TRACKING

  • CARCASS TRACKINGReady. Resourceful. Responsive!Navy Supply Information Systems ActivityPresented to: DLMSO PRC CommitteePresented by: Gerald OSullivan

  • AgendaPurpose of Carcass TrackingOverview of Repairable ProcessItem PricingBK_ ProcessingCarcass Tracking Doc_ids BKR Rejection CodesBK3 Reason CodesBK4 Reason CodesCarcass Tracking References

  • Purpose of Carcass Tracking Ensures repairables are returned and received to the supply system in an expeditious manner while minimizing Fleet workload. Monitors retrograde turn-in and provides statistical information on the Fleet to Hub pipeline. Reduces the cost recovery rate (CRR) by ensuring lost carcasses are minimized. Generates retrograde management reports for the Fleet via SALTS and website. Triggers electronic follow-ups (BKs). Processes BK2 responses. Generates Carcass Value bills/credits. Generates System Losses.

  • NWCF"W" PURPOSE ISSUE FLOW

    Sheet1

    SQUADRON

    "DTO"JFK

    "5G" REQUISTIOND7A ISS TO SQUADRON

    A - COND

    A - PURP

    (no TIR to ICP)

    "'F" COND

    IMA

    ITEM REPAIRED AND

    NOYESPUT BACK IN 'W' PURP

    (no TIR to ICP)

    DECLARE BCM'F' CONDHUBHUB receives

    part- D6A "F" cond

    to ICP- close C.T.

    AIR STATIOND6R to C.T.(notification of shipment of "F" cond)

    D7A ISSUE

    A CONDStock replen to ICP

    W PURPVZ fund code

    TIR to ICP (DTO doc#)5X advice code

    0001-1999 serial doc #

    ICP

    BM to Navy FISCJFK

    Generate Net Price BillD7K , VZ fc, A purpD6K , VZ fc, W purp

    (opens S.I.T)(closes S.I.T)

    Start Carcass tracking

    S. I . T.

    IF HUB DOES

    NOT RECORD

    D6A 'F' COND

    CUSTOMER

    RECEIVES

    CARCASS

    BILL

    can I repair?

    W stock

    Sheet2

    Sheet3

    Sheet4

    Sheet5

    Sheet6

    Sheet7

    Sheet8

    Sheet9

    Sheet10

  • Two Price SystemSTANDARD PRICEBILLNon exchange requisition/issuesNET PRICEBILLExchange requisition/issuesCARCASS PRICEBILL Standard minus Net = Carcass BillExchange advice code with no turn-in

  • BK_ ProcessingUSERS/CUSTOMERSNAVICPBK2 RESPONSEBK1 INQUIRY 45 DAYSBKR REJECT OF BK2 RESPONSEBKA ACCEPTANCE OF BK2 RESPONSEBKD D6R PROCESSED AT ICPBK3 WITHIN 30 DAYS PROPOSED BILLACTUAL BILL AFTER 30 DAYSBK4 BK3/BILL REVERSALBK5 FOLLOWUP TO TRANS-SHIPPERBK6 RESPONSE TRANS-SHIPPERTrans-Shipment Activity

  • Carcass Tracking Doc_IDsBK1 - FOLLOW-UP TO CUSTOMERBK2 - RESPONSE FROM CUSTOMERBK3 - SECOND FOLLOW-UP/NOTIFICATION OF BILLBK4 - CARCASS VALUE BILL REVERSAL NOTIFICATION/BK3 SUPPRESSIONBK5 - FOLLOW-UP ON TRANS-SHIPMENTBK6 - RESPONSE FROM TRANS-SHIPPING ACTIVITY BKR - REJECT TO CUSTOMERS BK2 RESPONSEBKA - BK2 PROCESSED AT ICPBKD - D6R PROCESSED AT ICP

  • Carcass Tracking Doc_IDs

    BACKUP SLIDES

  • BKR Reject CodesA No record of REQ/issue on BK2 response DOC#B Invalid or blank fields in BK2 response areaC Second BK2 F or K responseD BK2 L response received; tracking record already contains a 5S/52 ADV code and/or the RFI ISSUE DATE is completedE BK2 N response received; tracking record already contains a 5R/5Y ADV code and/or the RFI ISSUE DATE is completedF BK2 B response cites an exchange DOC as turn-inG BK2 response cites an incompatible NIINH BK2 P response received; tracking record is not cancelledI Cust cited himself as the turn-in destinationJ Cust submitted another BK2 response after a BK2 C, D, or G response already postedK BK2 B response cites a non-exchange record as the turn-inL BK2 B response cites a matched receipt as turn-inM Cust submits a third BK2 responseN BK2 J response doesnt cite an exchange recordO BK2-B response citing a DOC# with a different UICP BK2 response cites a quantity greater than one eachR BK2 H response cites a tracking record or a matched receiptS BK2 B response cites a shipment DOC# w/a julian date that exceeds two year time frameT BK2 A response contains a rejected incompatible NIINU BK2 response received is an exact duplicate of a previously posted BK2 response

  • BK3 Reason Codes A - A BK2 C, D, OR G RESPONSE WAS RECEIVED AND A CARCASS VALUE BILL HAS BEEN GENERATED

    B - NO VALID BK2 / D6R / RECEIPT HAS BEEN RECEIVED

    C - A SECOND BK2 F OR K RESPONSE WAS RECEIVED AND REJECTED WITH A BKR C REJECT CODE

    E - A BK2 H RESPONSE WAS RECEIVED, NO D6A A CONDITION RECEIPT PROCESSED, A CARCASS VALUE BILL HAS BEEN GENERATED

  • BK4 Reason Codes A - A D6R, POSITIVE BK2 INDICATING TURN-IN, RECEIPT, OR CANCELLATION POSTED AGAINST A RECORD IN CARCASS VALUE BILL STATUS

    B - A D6R, POSITIVE BK2 INDICATING TURN-IN, RECEIPT, OR A CANCELLATION POSTED AGAINST A RECORD IN BK3 STATUS

    C - BK3 IS SUPPRESSED BECAUSE A B OR F REJECT OCCURRED

  • Carcass Tracking ReferencesNAVSUP P-485 Depot Level Repairables (DLRs) par.8300 NAVSUP 545 DLR Requisitioning, Turn-In and Carcass Tracking Guide NAVSUP Instruction 4419.6 (System Loss Reconciliation)

    BK1 45 days after Issue and no receipt of D6R receipt of carcass or BK2 from requisitioner.