7-17
Priority Designator
The priority designator (PD) is a two-digit number
(01, the highest, to 15, the lowest). The PD is
determined by using the table of priority designators
(fig. 7-14). The table is easy to use. For example, if your
activity is assigned an F/AD of II and your requirement
is of a routine nature, the priority to be assigned would
be 12.
In addition to providing standardized criteria for
assigning priorities, UMMIPS provides acceptable
maximum processing times for use by supply activities
in furnishing material. NAVSUP P-485 contains the
processing time standards and additional codes used in
MILSTRIP and UMMIPS.
CASUALTY REPORTING (CASREP)
The casualty report (CASREP) is designed to
support the Chief of Naval Operations (CNO) and fleet
commanders in the management of assigned forces. The
effective use and support of Navy forces requires an up-
to-date, accurate operational status for each unit. An
important part of operational status is casualty
information. The CASREP system contains four types of
reports: initial, update, correct, and cancel. These reports
are described in general in the following paragraphs.
CASREPs are not a substitute for, but are in addition to
and complement, 3-M data. For more complete
information on the preparation and submission of
CASREPs, see Operational Reports, NWP 10-1-10.
Initial Casualty Report (INITIAL)
An INITIAL CASREP identifies the status of the
casualty and any parts or assistance needed. Operational
and staff authorities use this information to set priorities
for the use of resources.
Update Casualty Report (UPDATE)
A unit uses an UPDATE CASREP to submit
changes to previously submitted information.
Correction Casualty Report (CORRECT)
A unit submits a CORRECT CASREP when
equipment that has been the subject of casualty reporting
is repaired and is back in operational condition.
Cancellation Casualty Report (CANCEL)
A unit submits a CANCEL CASREP when
equipment that has been the subject of casualty reporting
is scheduled to be repaired during an overhaul or some
other scheduled availability. Outstanding casualties that
will not be repaired during such availability will not be
canceled and will be subject to normal follow-up
casualty reporting procedures as specified.
MANDATORY TURN-IN
REPAIRABLES (MTR)
You will, no doubt, encounter the terms mandatory
turn-ins and repairables in the process of obtaining
replacement parts from supply. Therefore, you need to
understand your responsibilities in regard to mandatory
turn-in repairable items (MTR).
When any of your equipment fails, your primary
concern is to locate the trouble, correct it, and get the
equipment back on the line. In most instances you first
trace the trouble to a defective part and then prepare a
NAVSUP 1250-1 (or DD 1348) to obtain the
replacement part from the supply storeroom. Next you
install the replacement part and throw away the defective
part. However, when the defective part is expensive and
repairable, it becomes a part of the repairables program.
A large number of parts can be economically
repaired when they fail. This results in savings of dollars
and time. Repairing an item is quicker and cheaper than
contracting for and buying a new oneprovided the old
item is promptly returned in repairable condition.
For the program to work as intended, you and others
have certain responsibilities. At the time you submit
your request for a mandatory turn-in item, supply will
tell you to return the defective item. Your
responsibilities begin at this point. You must remove the
defective part and give it adequate protection to prevent
further damage before turning it in to supply. The most
effective way to protect the defective part is to place it in
the same container in which you received the
replacement part. The defective part or equipment must
be accompanied with a copy of the OPNAV 4790/2K,
Work Request form describing the failure of the part or
equipment. Your protection of the part will help the
designated overhaul point (DOP) diagnose and repair the
defective component and return the part to service more
quickly. Do not cannibalize components you might use
sometime in the future.