Node-A DLR collection, consolidation, and
transshipment point. The Node may be operated by a
freight agent or government personnel. The Node does
not perform validation of&awing/part number to stock
number or submit a TIR.
Managing the Turn-in
Strict discipline in tracking the movement of DLRs
is required at all supply system activities. The local
procedures must include monitoring of the DLR from
the time of requisition to the disposition of the turn-in.
The supporting supply activity must monitor the DLR
turn-in throughout the repair cycle in the intermediate
maintenance activity (MA). If the IMA repairs the
NRFI turn-in, the repaired item is returned to stock to
replace the asset that was issued to the customer. Ibis
process is considered as a closed loop with all actions
completed within the activity and does not require a
system carcass tracking.
System Carcass Tracking
A total system carcass tracking is required when an
NRFI turn-in cannot be repaired locally and must be
returned for repair at the depot repair facility. The total
system carcass tracking procedures also apply to the
DLR requisitions that are passed off station. These
requisitions are passed off station to replenish stock
assets or for direct turn over (DTO) to the customer,
The DTO requisitions are submitted because the
requisitioned item is not in stock/not carried (NIS/NC)
in the supporting supply activity. The DTO requisition
is submitted to the stock point or the inventory control
point. The total system carcass tracking employs
automated procedures involving CTRs to record the
actions necessary for effective monitoring.
Carcass Tracking Records (CTRs)
The carcass tracking records (CTRs) are the data
records for information essential to the effective
tracking or monitoring of DLR carcasses. Carcass
tracking records are established at the NAVICPs and
user (customer) activities that stock and issue DLRs.
NAVICP CARCASS TRACKING RECORD.
The purpose of the NAVICP CTR is to record and store
data that applies to the issue/return of DLRs to provide
proper inventory accounting of carcass returns. This
record serves as the basis to monitor the DLR carcass
turned-in by the user (customer). The NAVICP uses
this record to determine if other actions should be
performed concerning outstanding carcass turn-ins.
Some of these actions include generating follow-up
inquiries and forwarding additional billings to the
Each NAVICP maintains a master CTR containing
transactions received from user (customer) activities.
These transactions relate to the issue/receipt of DLRs
under the NAVICPs cognizance and a NRFI DLR
turn-in has been or will be turned-in as an exchange for
an RFI DLR. All transactions and reports citing an
exchange advice code received by the NAVICPs are
recorded on the CTR and will open a record on the
carcass tracking file. These transactions are identified
with document identifiers A0_ (requisitions), A4_
(referrals), D7_ (issue TIR), B7A (non-TIR issue
reports), D6_ (receipt TIRs), D6R (shipment
notification), and FTA (automatic material returns to
other services). In essence, an issue transaction or
requisition citing an exchange advice code will open a
record on the NAVICPs CTR. The matching receipt of
NRFI turn-in transaction record reported by the
DRP/DSP to the DRP will close the CTR.
If records are not closed within the specified time
frame, NAVICP-Phil will send a follow-up inquiry
using document identifier BK1 to the requisitioner.
The time frame for sending the follow-up for
requisitions citing advice codes of 5G, 5V, or 56 starts
from the date of requisition. For requisitions with
service code N, NAVICP-Phil sends the follow-up 45
days from the requisition date. For requisitions with R
or V service code, NAVICP-Phil sends the follow-up 60
days from the date of the requisition. The
NAVICP-Mech sends the follow-up 90 days from the
The time frame for sending the follow-up for
requisitions citing advice code of 5R, 5Y, 5S, or 52 starts
from the date of issue of an RFI DLR. For requisitions
with an N service code, NAVICP-Phil will send the
follow-up 45 days from the issue date of the RFI DLR.
For requisitions with service code R or V, NAVICP-Phil
sends the follow-up 60 days from the issue date of RFI
DLR. The NAVICP-Mech sends the follow-up 90 days
from the issue date of RFI DLR.
If the requisitioner fails to provide a satisfactory
response to the BK1 follow-up inquiry, an additional
billing to cover the carcass value could result. If the
CTR shows that a transshipper is involved, the NAVICP
sends a BK5 follow-up inquiry to the transshipper
instead of a BK1 to the requisitioner.
USER ACTIVITY CARCASS TRACKING
RECORD FILE (CTRF). User activities use this file