Oi!!PA~TMIUiT OF THE: NAVY N"-4"¥-;l\.L. $Ur'P'J..t' SYtii'f.f::M IS- lir@MM~'N'Q

®.>til:¢ e~tn ... a,;n •.. c ~~It~ ~"@©£~I)$¢

M-.£.t!~Jt1'*!hCS~l-HlG ~JJ, 'l1-'$l!li$,*1"bt

NJfl.tStiP!N:ST 4440, 182A NAVSUP NJl

OCT 30 2013

From z Comm~u:tde:r, Naval Supply S}tsti'Nns Command

' Subj t ~fAIN~IN·I?UCE LIST FOR NAVS:U? WEAPON SYSTEMS SUPPORT

FOR DEPOT LEVEL RltiPAIAAaUS

Ref: {a) OPNAV!NST UOO.:!IC \b) UJ:!N.A\IlN~'l' 4U!J. :d!>A (c) NAV!CI?INST 4400.140 {d) NAVlCf;liNST 4440.79D

lmcl: (1} RIP Request SubmisS~ion Flowcha.R•"••••••••• {:;!;) Aviation Ul? Chang~ Request (ll:rnail Format} CH Surface RIP Change Request (Message Format} ( 4} Surface' RIP Change Request (Email Form <at:)

l. i>UE'J20:f>,:!. Iftsue pql.icy and procedures necei!ilaacy to !:Hstablblt and maintain a Rem:ain~i:n-Flace (RIP'} List for Aviation and Marit.ime Depot Level Repi!l.i:rables (O:LR4il) managed by ~r:ava.l Supply Systems Command Weapon Systems Support (NAVSUl? WSS) , References {aJ th:rough {d) apply.

3. Scope and AJ2pl:lcaJ::dl,~S:t· This instruction pertains to all NAVSII!? wss managed :OLRs in support of aviation, ahi.ps, submarines and sho:r.'e activities ""'ithin the Naval Supply Comtn.1md (NAVSOP) EnterPrise.

4. Bac!s.gxoun,S. Situations where a failed DLR should not or cannot be removed if a :replou:::ement is not imftledU.t.!ly avail!bl~ constitute a condition where a $tiP de:t:tignation is appropriate. Only DLRs meeting the criteria outlined in paragraph 6. a \dll qualify al'3 valid RIP Dt.Rs. When requi.sitio.ning DLRs chat have received a RIP designation, customers will cit!l$ Advice Code 5S/52 on their ;requirement, thus eHminating processing delays £\nd prcma,turo oaroac:uw ilib:kil.Ji.nS~•

\llil!tftf NAIIWI" Hlll!'it ,.lii:'II'!NIII.f'lll!i!lt!p,IIWI):JW !l";;n On<!i food% S<i!lt'lr '*' lQ w•m.no"1l"!!·rm~ll-wtl!

NAVSUPINST 4440.182A OCT 3 0 2013

5. Objective. This instruction was created with Navy-wide application to readily identify Aviation and Maritime repairable items authorized to be retained in place pending receipt of a replacement .. In addition, the supply system utilizes the In­Service Engineering·Activity (ISEA) provisioning.review t:o determine impact to Repair Turnaround Times (RTAT), stock level increases and budget requirements.

6. Information

a. RIP items identified wi~h RIP Codes c, M, P, s, v, or Y, defined below, are authorized to be temporarily retained upon failure when they are in an installed equipment and,can be ordered citing Advice Code ss. Items with a RIP code of N, X or blank will not be retained, and will be ordered citing Advice Code SG/SR/SV/SY/56. The list below provides a definition of each RIP code:

(1) Containerization (RIP Code C) . Definition: Material requires a special reusable container. Upon receipt of replacement part, shipping container of replacement will be used to return Not~Ready-For-Issue (NRFI) item to the supply system.

(2) Maintenance (RIP Code M) •. Definition: Removal of the item involves exchange of numerous fittings or linkages; exposes the installed system to water intrusion, corrosion or mechanical damage; or precludes operation of installed system to facilitate other maintenance.

(3) Partial Equipment Operation (RIP Code P) . Definition: Retention of the item permits operation of the equipment in a degraded mode.

(4) Safety (Non-Operational) (RIP Code S) . Definition: With the item removed, the installed system is in an unsafe configuration (weight and balance, structural limits and personnel hazard) .

(5) Mobility (Equipment) (RIP Code V). Definition: With the item removed, the installed system cannot immediately be moved in the event of an emergency.

(6) Any Other Reason (RIP Code Y). Defin~tion: Remain-in-Place authority granted.

(7) Not RIP Worthy (RIP Code N or Blank) . Definition: Item need not be retained pending receipt of replacement' item.

2

NAVSUPINST 4440.182A

OCT 3 0 2013 (8) Not RIP Worthy (RIP Code X) Under Technical Review.

Definition: The technical investigation has not been completed.

7. Discussion

a. Identification of RIP Items for New Equipment. The Hardware Systems Command (HSC), Naval Sea Systems Command (NAVSEA), Space and Naval Warfare Systems Command {SPAWAR), and Naval Air Systems Command (NAVAIR) will en~ure that all . contracts procuring Provisioning Technical Documentation ·(PTD) contain a requirement to supply RIP reason codes for all DLRs. Technical provisioning activities will approve the RIP reason code contained in the PTD, which will be provided to NAVSUP WSS as part of the provisioning cycle.

b. NAVSUP WSS will identify Existing Equipment and forward potential RIP candidates to the cognizant HSC for technical review under the criteria established above. The HSC certification of an item as either RIP or non-RIP will be recorded in Navy Enterprise Resource Planning (ERP) Systems, Applications & Products (SAP) in Data Processing files and will be reflected in all publications identified in paragraph ?.c. Items not reviewed by the HSCs may be recommended for RIP under the provisions of paragraph ?.f.

c. Identification of RIP Data. RIP items will be identified in the following publications:

(1) ERP. ERP is the system of record for management information recorded against National Stock Numbers (NSN~) managed by NAVSUP WSS. The Remain-in-Place Indicator Code can be obtained via ERP transaction MM03 using the NIIN and selecting Navy Basic Data 3. The RIP code is listed under General Data.

(2) One Touch Supply (OTS) . Using the NIIN and selecting the Stock Check option, OTS will identify the RIP Indicator Code.

(3) Master Repairable Items List (MRIL). RIP items are identified by a designation "RMN IN PLACE" in the "NOTE" field of the NIIN sequence listing per reference (d) . Monthly issues of the MRIL will include any RIP designation changes which have occurred since the previous issue. Items will be deleted from RIP upon joint NAVSUP wss and HSC decision, obsolescence or COG migration.

3

NAVSUPINST 4440.182A

OCT 3 0 2013 {4) Defense Logistics Agency {DLA) Federa~ Logistics

Data {FEDLOG). FEDLOG contains management, part/reference number, supplier, Commercial and Government Entity {CAGE), freight, Interchangeability and Substitutability {I&S) and characteristics information recorded against NSNs. The RIP reason code will be loaded into the ERP MRIL (the system of Record for RIP data) of the NAVSUP WSS ERP MRIL table to indicate the reason an item was so designated, or to identify those NIINs under technical review. ERP will feed this data to FEDLOG. The following RIP reason codes will be reflected in FEDLOG:

(a) C - Containerization

{b) M - Maintenance

(c) N - Not RIP-Worthy

(d) P - Partial Equipment Operation

(e) S - Safety Consideration {non-operational)

{f) V - Mobility (equipment)

(g) Y - Any Other Reason

{h) X - Under Technical Review

d. Processing/Validation of SS'Advice Code sales orders. If the appropriate Navy ERP SAP files do not contain RIP Codes C, M, P, s, V or Y for a DLR order using a RIP certification advice code, the sales order will be treated as if an immediate exchange advice code was utilized once validated by NAVSUP WSS Navy In Transit Accountability (NITA) . Th~ customer mus~ then follow the appropriate turn-in procedures for an immediate exchange advice coded sales order. NAVSUP wss is authorized to make this adjustment for those items not identified as RIP items in NAVSUP wss files. Under no circumstances will sales order processing be circumvented.

e. Modification of Stock Levels for RIP Items. Increased stock levels for RIP items will be budgeted and executed to facilitate delay retrograde returns by the activity pending receipt of the Ready-for-Issue (RFI) material.

f. RIP Designation Review Request

4

{l} Aviation Cog (7:R) DLRe.. Act::ivity RI.l? request will be submitted t:o the appl.ical:J.le 'I'Yl?EWINGs (CVWs) or Aircraft Culi!tOdians (ACes) tor review as outlined in ene:losu:rll'! (:2) ,

Tl:1ose approved wi 11 be forwarded to NAVAIR {Code 6. 1. :2) for RIP review consideration via email: (navairi>Grip.fctlilln.avy,mU). Those d.isapproved will be r®.turned to the submitting activity. Note; ) .. ~ TYCOM RIP :Incoming mailbox:. U · · sage fot't'tla.t will suffice.

(2) Mhtritime Cog review request will be submitted to NAVSW W:SS Mechanicsburg via Naval Mesaage {enclolS!u:t·e (3.1} or Email {enclosure (4.) t. Note: (dVS!upwd~_r'ip', NAVSOP_wss Incoming ll:rlf M<tilbox.

a. Policy. In consonance wit following guidelines a:re app

a, Reqtu:mti.ng Ae:tivitie

{l) Limit the use of Advice Code ss in'iiiC:~ti that a repairru:Jle carcass is being retained .in place. to only !those instances wn.ere the MI\IL indicates that the item is RIP and no on,board replacemem; ie available.

(2) Ba.!!Hrtd upon the COG, forward requests ,far RIP code changes as identit:ied above in paragraph {7, f .l or 7. f. 2}.

b. ~ Commanders/Aircraft Cui!Jtodia:ns (TYCOMs(ACCs) J~Wh.all promulgate guidance and amend ~Xi$itlng iMtructions, as neceaEuiry, to 'li!m.Jure c~liance with thi~J instruction.

U l Einsl;l:re RIP components for new equipment: under their cognizance are identif:hni in thE~ PTD by RIP reason code and that the RIP designation b app:rove:d and sUbmitted to the appropriate NAVSOP IVS.S Activity Integrated Weapon Systems Team {!WST} for coordination.

{2} Ret1:;rn all RIP IJ,Pdates/revisiona to NAVSUP wss Philadelphia (:POlS/ 0.32/034) or NAVSOP WBS Mecll!Jtnicsburg (t>iOl42/eJ/8.5/B'7} via Naval Message or :Smail {~~I!\!W~Ii'i,;.;r:l.:plfri.Qi;'~1J!:'1 ae ot: updating Navy ERP SAP Files,

NAVSUPINST 4440.1S2A

d. NAVSUP WSS shall: OCT 3 0 2013

(1) Review all current instructions and revise and align responsibilities and duties accordingly.

(2) Process all incoming RIP requests submitted for existing equipment, per enclosures (1) through (4).

(3) Make changes based upon approved change requests or other official actions such as cognizance symbol migration in Navy ERP SAP files and the MRIL.

(4) Ensure RIP Indicator Codes are posted for new eqUipment provisioned DLRs, as identified per incoming PTD and , other official correspondence.

(5) Use the RIP indicator in Navy ERP SAP files to validate, through the retrograde cycle, sales orders submitted with RIP certification. For items failing validation, NAVSUP wss will:

(a) Change Advice Code from. ss to SG,

(b) Notify customer of the change, and

(c) Assure subsequent carcass value billings are affected when necessary.

e. NAVSUP WSS IWST shall:

(1) Conduct a technical review of requests for changes concurrently with the HSC review and advise! the HSC in cases where NAVSUP WSS review does not agree with the HSC request.

(2) Conduct a\logistical review of requests for changes to the RIP code to determine if this action will have a negative logistical impact. If there is a negative logistical impact, the applicable HSC will be notified.

(3) Assure all newly provisioned systems DLRs are RIP coded.

(4) Ensure stock levels are budgeted and executed to provide for the extended retrograde-pipeline requirement and a sufficient safety level to ensure that the risk of stock-out is minimized by the NRFI item being retained on-board pending receipt. of RFI material.

6

NAVSUPINST 4440.l82A

OCT SO 2013 (5) Establish a systematic RIP review for newly

provisioned items entering the system and those established DLRs that have not had RIP validation criteria applied.

9. Records Management. Records created as a result of tpis instruction~ regardless of media and format

1 shall be managed

per SECNAV Manual 5210.1.

Distribution: Electronic only via NAVSUP Naval Logistics Library (NLL) https://nll.ahf.nmci.navy.mil

7

RIP Request Process Format/Process Aviation/Surface

NAVSUPINST 4440.l82A

OCT 30 2013

Enclosure (1)

............. ----------------------~--~-

NAVSUPINST 444CL 182A

3 0 2013 NAVSUP WEAPON SYSTEMS SUPPORT ACTIVITIES RIP LIST CHANGE REQUEST

From: Activity/Ship - [Example: USS GEORGE WASHINGTON]

To: xrcnaln417rip@navy.mil

[Identify other activity email addresses want included for status distribution)

Subj: REQUEST CHANGE TO CONSOLIDATED REMAIN-IN-PLACE LIST FOR NSN• 7Rl620017922655/USS GEORGE WASHINGTON

Ref: (a) OPNAVINST 4440.25A

1. Per reference {a), requested that the following item be [added to/deleted] from the Consolidated Remain-in- List (

a.

b. Nomenclature: --------------------------c. NSN:

d. Part Number:

2. Justifi (Must specify one or more of the following cri and include additional amplifying details in paragraph 4 below. J

a. Safety (non- ) . With the removed, aircraft is in an unsafe iguration [weight and balance, structural 1 , personnel hazard] .

b. Mobility. With the item removed, aircraft can not immediately be moved in the event of an emergency.

c. Maintenance. Removal of the item involves exchange numerous f or linkagesi exposes the aircraft to water intrusion, corrosion or mechanical damage; or precludes turn-up to facilitate other maintenance.

Enclosure (2)

NAVSUPINST 4440.182A

OCT It 2013 d. PMCS Flight. Removal of the item precludes flight, but

retention permits flight with degraded mode condition of installed system.

3. Reason for Deletion.

4. Remarks. [Additional amplifying details].

Signature/Name/Title

Enclosure (2)

NAVSUPINST 4440.182A

OCT 8 0 2013 NAVSUP WEAPON SYSTEMS SUPPORT ACTIVITIES RIP LIST CHANGE REQUEST

NAVAL MESSAGE FORMAT

FM: USS SAN FRANCISCO TO: NAVSUP WEAPON SYSTEMS SUPPORT MECHANICSBURG PA or

NAVSUP WEAPON SYSTEMS SUPPORT PHILADELPHIA PA INFO: [Identify any other activity PLAD you want included for status distribution.] BT UNCLAS MSGID/GENADMIN/MIL-STD-6040(SERIES)/B.O.Ol.OO/NAVSUP WSS MECHANICSBURG/PHILADELPHIA/PA/015/033/034/83/85/87/USA/UNCLASS// SUBJ/REMAIN IN PLACE CHANGE REQUEST: 7Hl620017922655MS/USS SAN FRANCISCO// REF/A/NAVSUP/NAVSUPINST 4440.182A/REMAIN-IN-PLACE INSTRUCTION /29JULY2013// GENTEXT/REMARKS/1. PER REFERENCE, (A), IT IS REQUESTED THAT THE FOLLOWING ITEM BE ADDED TO/DELETED FROM THE RIP LIST: A. SYSTEM/EQUIPMENT IDENTIFICATION APPLICATION (INSTALLED SYSTEM): B. UNIT/MODULE/PART IDENTIFICATION: C. REFERENCE SYMBOL NUMBER (WHERE APPROPRIATE): D. COG/MCC/NSN: I

E. VENDER/CAGE/FSCM AND,PART NUMBER: 2. JUSTIFICATION FOR ADDITION: MUST SPECIFY ONE OR MORE OF THE FOLLOWING CRITERIA AND INCLUDE ADDITIONAL AMPLIFYING DETAILS IN PARAGRAPH 6.A.l-6. 3. REASON FOR DELETION: 4 .· REMARKS/AMPLIFYING DETAILS: 5. ACTIVITY POINT OF CONTACT:

A. NAME: B. BILLET: C. EMAIL ADDRESS: D. PHONE:

BT

Enclosure (3)

NAVSUPINS'I' 4440 .lS2A

OCT 80 Z013 NAVSUP WEAPON SYS'l'IMS SUPPORT ACTIVITIES RIP LIST CHANGE REQUEJS'l'

FROM: Activity/Ship - (Example: USS

ro: navsur:rwss::_ ~ip ~ fot-.vy ,m~i:

Info; (Identify any activity eroaU addresses you want included for distribution purposes]

SOBJ; REMAIN-IN-PLACE! CHANGE R!QtmST; 7Hl6200l79226SS/ OSS SAN FRANCISCO

1. IAW NAVSUPINS'l' 4440.18.2A, IT IS RSQUESTED THAT 'l'HE FOLLOWING ITEM BEl ADDEID TO/DELETED FROM THE RIP LIST; A. SYSTEM/EQUIPMENT .IDENTIFICATION APPLICA'l''ION (INSTALLJW SYSTEM}: B. UNI'l'/M01Xl't.E/PART IDENTIFICATION: C. REFBRlmCE SYMBOL NUMBER (WHERE APPROPRIA'I'El} : D , <::.'ClO/MCC/NSN: E. VENDl'm/CAGi:/FSCM 1\ND PART Nt.JlG:ER: 2 • JUSTIFICATION fOR WDITION: MOST SFICIFY ONE OR .M:ORE OF THE FOU..OWIOO CRI'l'ERIA Am:l INCWDE ADDITIONAL AMPLIFYING DETAILS IN PARAGRAPH o.A.l-6. 3. REASON FOR DELETION: 4. RmltARKS/AMPLIFY'ING DETAILS: 5. ACTIVITY !?OINT OF CONTACT:

A. N»m: B. BILLET: C. EMAI.L ADDRESS: D. PHONE~

Enclosure ( 4)