SHIPS 3-M MANUAL

SECTION 1 1-2 c. Scheduling and control of the performance of tasks.

d. Description of the methods, materials, tools, and personnel needed for maintenance.

e. Detection of hidden failures or malfunctions.

f. Test procedures to determine material readiness. 1-4 SHIPBOARD 3-M ORGANIZATION AND RESPONSIBILITIES 1-4.1 Commanding Officer The Commanding Officer has overall responsibility for ensuring ship maintenance is accomplished following 3-M System and quality maintenance procedures and that the 3-M System functions effectively within the command. The Commanding Officer shall ensure appropriate personnel receive adequate formal 3-M training, and shall have frequent meetings with the Executive Officer and the 3-M System Coordinator to discuss 3-M System matters and to provide necessary guidance and coordination. The Commanding Officer shall conduct periodic checks to ensure that the 3-M System is functioning properly aboard ship. An effective maintenance program aboard ship must involve all levels of management, from the Work Center Supervisor up to and including the Commanding Officer. To this effect, the command must have an aggressive spot check program. It is mandatory that all levels of shipboard management know the material condition of the equipment aboard ship and the extent to which PMS is being accomplished. The Commanding Officer has the responsibility for establishing and conducting a spot check program at his/her command. The Commanding Officer shall ensure that all documentation deferring maintenance is reviewed and approved at a responsible level and that 3-M submissions are being made as required. 1-4.2 Executive Officer The Executive Officer is the Ships' 3-M System manager and is responsible to the Commanding Officer for the overall management of the Ships' 3-M System program. The Executive Officer shall:

a. Be knowledgeable of current 3-M System policies and directives.

b. Chair periodic 3-M System meetings with Department Heads and the 3-M System Coordinator.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-3 c. Monitor the operation of the 3-M System program to ensure compliance with current directives.

d. Brief the Commanding Officer at regular intervals on the status of 3-M.

e. Integrate 3-M System training into the ship's training and qualification program. Ensure personnel receive adequate and effective 3-M System training.

f. Act as final review officer for maintenance responsibility shifts between departments.

g. Ensure the effectiveness of the command 3-M spot check/self evaluation program. 1-4.3 3-M System Coordinator The 3-M System Coordinator is the functional manager of the 3-M System and is responsible to the Executive Officer for the coordination and direct supervision of all administrative facets of the Ships' 3-M System program. This position will be assigned in writing as the PRIMARY DUTY of an officer, Chief Petty Officer or Petty Officer First Class (who has been assigned a secondary Navy Enlisted Classification (NEC) of 9517). As an exception to this policy, ships not having an allowance for a 3-M System Coordinator will assign these duties in writing as the most significant of collateral duties of an appropriately qualified officer, Chief Petty Officer or Petty Officer First Class. Office space of sufficient size is to be provided to permit effective performance of duties. Each command is responsible to ensure personnel assigned to the 3-M System Coordinator billet have adequate experience, training, and time to perform the responsibilities of the position effectively. The 3-M System Coordinator shall:

a. Serve as the principal 3-M System assistant to the Executive Officer.

b. Review 3-M documentation submissions for accuracy, completeness, and timeliness. Included in this duty is a requirement to ensure all required 3-M submissions are made, and that 3-M data returned for correction is promptly revised and resubmitted.

c. Ensure the Ships’ 3-M System program is kept current and any revisions are promptly distributed.

Downloaded from https://www.everyspec.com

SECTION 1 1-4 d. Advise, monitor, and assist Department Heads, Division Officers, Departmental 3-M System Assistants, and Work Center Supervisors in matters concerning the 3-M System.

e. Manage the functions of the 3-M System office. These functions are:

(1) Maintain a file of 3-M System directives, newsletters, notes, and correspondence containing current 3-M program information. Ensure distribution to Work Center personnel.

(2) Manage the PMS Master file that contains information relative to PMS requirements for specific equipment including the associated Equipment Guide Lists (EGLs).

(3) Ensure the command 3-M System training program, both onboard and off-ship, is adequate to meet the needs of the command. The 3-M System Coordinator should attend meetings of the periodic planning or readiness boards.

(4) Coordinate with Automated Data Processing (ADP) personnel for support of 3-M system software.

(5) Screen, serialize, and date all PMS feedback reports leaving the ship.

(6) Establish and maintain a file of outstanding PMS feedback reports and responses.

(7) Establish procedures for routing and/or explaining PMS changes to all concerned, and maintain a master accountability log of these changes.

(8) Maintain a file of configuration changes submitted to establish coverage on equipment not currently covered by PMS, until coverage is established.

(9) Ensure 3-M Maintenance Data System (MDS) data element validation is conducted in accordance with the 3-M validation specifications.

f. Screen 3-M documents for legibility and completeness. Forward 3-M documents to the designated data processing activity within 4 working days of Department Head approval or as operationally feasible.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-5 g. Ensure the timely processing of Automated Shore Interface (ASI) configuration and logistic data.

h. Ensure timely up-line reporting of Current Ship's Maintenance Project maintenance transactions, ship's equipment file corrections and Coordinated Shipboard Allowance List (COSAL) feedback reports.

i. Supervise the command’s spot check/self evaluation program. Provide a weekly status report to the System manager. 1-4.4 Department Head Each Department Head is responsible to the 3-M Manager for the effective operation of the 3-M System within the department. The Department Head will:

a. Supervise maintenance scheduling within the department and other departmental 3-M functions. Review and approve cycle schedules.

b. Review annotations of maintenance actions that were not fully accomplished during the quarter and close out Quarterly schedules.

c. Ensure departmental personnel are properly trained and motivated in the effective operation of the 3-M System.

d. Conduct periodic meetings with Division Officers and Work Center Supervisors and keep the Executive Officer informed of the status of the 3-M System within the department.

e. Ensure the following action is taken when equipment is added, deleted, or modified:

(1) Coordinate with the Supply Officer to ensure shipboard allowances, including tools, parts, materials, and test equipment needed for PMS are updated.

(2) Ensure all material deficiencies are properly and promptly documented.

(3) Ensure all required 3-M System documents are submitted to the 3-M System coordinator within 4 working days of the date of origination.

(4) Determine equipment Inactive Equipment Maintenance (IEM) status. Downloaded from https://www.everyspec.com

SECTION 1 1-6 1-4.5 Departmental 3-M Assistant Department Head’s may assign an officer, Chief Petty Officer or Petty Officer First Class, trained in and knowledgeable of the 3-M System, to provide help with the coordination and supervision of the department's 3-M program. This assignment will be made in writing. 1-4.6 Division Officer The Division Officer is responsible to the Department Head and will be qualified in the 3-M System. The Division Officer assists in managing the maintenance required for the equipment within division responsibility. Division Officer responsibili- ties are:

a. Ensure 3-M documents generated within the division are complete, accurate, and promptly prepared and submitted.

b. Review and approve quarterly schedules. Ensure the divisional quarterly schedule is updated weekly.

c. Conduct spot-checks as directed by the Command’s policy to ensure required maintenance is being properly performed as prescribed by Maintenance Requirements Cards (MRCs).

d. Incorporate 3-M System training into the divisional training plan. Ensure maximum use of PMS as an aid in training personnel in maintenance procedures for equipment within the Work Center

e. Work in conjunction with the 3-M System Coordinator in matters concerning the 3-M program.

f. Meet frequently with divisional Work Center Supervisors and inform the Department Head each week of the status of the 3-M System within the division. 1-4.7 Group Supervisor Shipboard divisions may have Chief Petty Officers who are responsible for multiple Work Centers. These Chief Petty Officers shall be referred to in this manual as "Group Supervisors" and will be responsible to the Division Officer for the proper performance of the 3-M System functions within their respective Work Centers. Group Supervisors, if assigned, will be assigned in writing. Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-7 1-4.8 Work Center Supervisor Work Center Supervisors will be qualified and designated in writing. He/she is responsible to the Division Officer via the Group Supervisor, if applicable, for the effective operation of the 3-M System within his/her respective Work Center. Work Center Supervisor responsibilities are:

a. Maintain a detailed working knowledge of all equipment deficiencies within the Work Center. The Work Center Supervisor will use the Current Ship’s Maintenance Plan (CSMP) as a daily working document for the scheduling of any maintenance actions not included on the PMS schedules.

b. Schedule weekly Work Center maintenance and supervise its proper accomplishment.

c. Ensure the status of Work Center planned maintenance is correctly reflected on the PMS schedules.

d. Ensure the Division Officer or Group Supervisor, if applicable, is advised of all 3-M System activity within the Work Center.

e. Maintain an adequate supply of 3-M System materials within the Work Center.

f. Ensure prompt reporting of all material deficiencies and completed maintenance actions as required.

g. Ensure all 3-M System documents submitted from the Work Center are correct, legible, and promptly prepared and submitted.

h. Ensure maximum use of PMS as an aid for training personnel in maintenance procedures for equipment within the Work Center.

i. Ensure 3-M System Work Center files, publications, MRC decks, Tag Guide Lists (TGLs), and EGLs are complete and current.

j. Review MRCs and promptly submit a PMS FBR whenever maintenance requirements are not fully understood, errors are believed to exist, maintenance requirements appear inadequate or excessive, additional coverage is needed, or performance of the maintenance requirement would cause a hazardous condition to exist. Downloaded from https://www.everyspec.com

SECTION 1 1-8

k. Ensure PMS covers all equipment in the Work Center. Maintain an accurate and current List of Effective Pages (LOEP) by comparing the documentation with the actual equipment configuration. Submit PMS FBR when changes to the LOEP are required. Submit configuration change requests when appropriate.

l. Ensure programmed Periodic Maintenance Requirements (PMRs) scheduled for ship's force accomplishment are completed and reported in strict accordance with the PMR, if applicable.

m. Ensure proper testing and inspection of work done by outside activities prior to job acceptance.

n. Ensure delivery of test and measurement equipment and other portable support equipment to testing and calibration Work Centers as indicated on scheduling reports. 1-4.9 Maintenance Personnel Maintenance personnel are responsible to the Work Center Supervisor. Their 3-M System duties include, but are not limited to the following:

a. Perform assigned scheduled maintenance requirements using MRCs, TGLs, and EGLs b. as indicated by the weekly schedule.

c. When performing PMS, promptly notify the Work Center Supervisor when:

(1) Anything on an MRC is not fully understood, appears to be incorrect or cannot be accomplished as written.

(2) Tools, materials, etc., prescribed by the MRC are not available.

(3) Any doubt exists about capability, training, or experience to properly perform the maintenance requirement as prescribed.

(4) Factors exist which would make performance of the maintenance requirement unwise or dangerous (e.g., disassembly of equipment needed for operations, radiation when prohibited, situations causing safety hazard to exist, etc.)

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-9 (5) Equipment deficiencies or casualties are discovered.

d. Inform the Work Center Supervisor when planned maintenance requirements are completed and sign the accountability log. The Work Center Supervisor must be informed of any problems encountered under current schedules and/or MRCs.

e. When performing corrective maintenance (repair):

(1) Notify the Work Center Supervisor of the details of the corrective action. Particular attention must be given to the cause code and remarks/description entries.

(2) Report all deficiencies found to the Work Center Supervisor.

(3) Initiate or update all 3-M documents as required.

f. Prepare the documentation for reporting deferrals, completions, material usage, and PMS feedback for review by the Work Center Supervisor. 1-5 PMS FUNCTIONAL OPERATIONS 1-5.1 PMS Master File The PMS Master File contains information relative to PMS requirements for specific equipment for which the command is responsible. The master contains, but is not limited to:

a. Additional instructions, information, and data provided to assist in implementation and accomplishment of PMS. Supplementary information includes changes received between force revisions (FR), information not contained on the master PMS CD-ROM, such as, classified MRCs, EGLs, and TGLs (if applicable). Also included are feedback reports and responses, and OPNAV 4790/CKs or Work Candidates affecting PMS until resolution.

b. List of Effective Pages (LOEP). The LOEP (Report No. PMS 5) (see Figure 1-1) provides a listing of the Maintenance Index Pages (MIPs) and system equipment not requiring PMS assigned to each Work Center. The LOEP is a part of the PMS Master file and contains:

(1) Report Date (Date LOEP produced).

Downloaded from https://www.everyspec.com

SECTION 1 1-10 (2) Force Revision (FR) Number.

(3) Type Commander (TYCOM).

(4) Unit (Ship's hull number, Unit Identification Code (UIC), and name); shore activity (UIC).

(5) Work Center (listing of Work Centers within each department).

(6) Maintenance Index Page (MIP) Number.

(7) Nomenclature (brief description of the system/equipment).

(8) Equipment Status. Codes that may be listed are:

(a) EGL (Equipment Guide List). Refer to paragraph 1-5.5 for additional information and use of the EGL.

(b) MRS (Maintenance Requirement Substantiated). Refer to paragraph 1-6.1 for classification definition.

(c) NIR (No Individual Requirement). Refer to paragraph 1-6.1 for classification definition.

(d) NMR (No Maintenance Requirement). Refer to paragraph 1-6.1 for classification definition.

(e) LATD (Lacks Adequate Technical Data). Refer to paragraph 1-6.1 for classification definition.

(f) Adds/Changes. A dash (-) denotes MIP issue changes included in the FR. A slash (/) denotes MIP additions distributed by special issue and not as part of the FR. A slash also denotes a change to a LOEP line entry; this change does not affect the MIP since the last FR.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-11

Figure 1-1: LOEP Example

c. MIPs. MIPs are prepared and issued for each installed system/equipment for which PMS support has been established. MIPs are basic PMS reference documents. Each is an index of a complete set of Maintenance Requirement Cards (MRCs) applicable to a ship system, subsystem, or equipment. MIPs (see Figures 1- 2, 1-3, and 1-4) contain the following information:

(1) SYSCOM MIP Control Number. Three SYSCOM MIP control numbering systems have been developed based on changing PMS philosophy and are currently in use. These are Conventional, Surface Missile System (SMS), and Reliability Centered Maintenance (RCM).

(a) For Conventional MIP cataloging, a four segment code is used. The first segment identifies the equipment group and may contain from one to four characters followed by a dash (-). The second segment identifies a specific subgroup/component number within an equipment group and may contain from one to four characters followed by a slash (/). The third segment identifies a distinct version within that equipment subgroup and may contain from one to three characters followed by a dash (-). The fourth segment contains two characters identifying the month and year the MIP was prepared Downloaded from https://www.everyspec.com

SECTION 1 1-12 (in all SYSCOM MIP control numbers, 1 through 9 are used for the months January-September and letters A through C for the months of October-December; the final character is a number indicating the last digit of the year).

(b) For SMS MIP cataloging a three segment code is used. The first segment identifies the equipment group and contains seven alpha-numeric characters followed by a slash (/). The second segment identifies the equipment configuration and contains three characters [if first character is "U", this is unscheduled maintenance (UM); otherwise this is scheduled maintenance] followed by a dash (-). The third segment contains two characters which identify the month and year the MIP was prepared.

(c) For MIPs developed using the Reliability Centered Maintenance (RCM) analysis concept a three segment code is used. The first segment contains four numeric characters followed by a slash (/) and identifies the system or functional grouping of items on which the maintenance procedures provided by this MIP are to be performed. The numeric characters in this segment are normally the same as the Ship Work Authorization Boundary (SWAB) number. The second segment identifies the sequence of maintenance requirements development for this functional grouping or system, and may contain from one to three characters, followed by a dash (-). The third segment contains two characters which identify the month and year the MIP was prepared (see Figure 1-2)

(d) Preliminary MIPs are identified by a "P" code and number following the slash of the SYCOM MIP control number (see Figure 1-5). The third segment contains two characters which identify the month and year the MIP was prepared.

(2) Date. Preparation date of the MIP by month and year.

(3) Ship System, System, Subsystem, or Equipment. Description of equipment by noun name/AN nomenclature/Mark, Mod.

(4) Reference Publications. Those publications pertaining to the system, subsystem, or equipment.

(5) Configuration. Applicability of MIP to system/ equipment changed as described.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-13 (6) Scheduling Aids. Amplifying instructions are noted in the maintenance requirement description block (see MIP Figures 1-2, 1-3, and 1-4).

(7) Other column and SYSCOM MRC Control Number:

(a) These codes are assigned for administrative use by FTSCLANT/FTSCPAC and may contain a one or two character code as follows:

Code Description

H Denotes a Calibration Maintenance Requirement developed under the cognizance of the COMNAVSEASYSCOM calibration program K Denotes a Maintenance Requirement and/or inspection developed under the cognizance of NAVSEA 07T, the Hull, Mechanical and Electrical Engineering Division. The “K” MRC’s are monitored by the submarine Performance Monitoring Team’s (PMT) for CBM analysis and failure identification. M Denotes a Maintenance Requirement developed under the cognizance of NSWC CD SSES Code 9161, for the Assessment of Equipment Condition (AEC) Program. RC Denotes a maintenance requirement on a Deep Submergence System (DSS) asset or system/equipment that is within the Scope of Certification (SOC) where Re-entry Control (REC) documentation is required. This MRC is Confidential. N Denotes a maintenance requirement on Moored Training Ship (MTS) systems/equipment that requires Moored Training Ship Support Yard (MTSSY) concurrence and NAVSEASYSCOM approval. C Denotes Confidential classification. S Denotes Secret classification. X Denotes a maintenance requirement on a Deep Submergence System (DSS) asset or system/equipment that is within the Scope of Certification (SOC) where no Re-entry Control (REC) documentation is required. XR Denotes a maintenance requirement on a Deep Submergence System (DSS) asset or system/equipment that is within the Scope of Downloaded from https://www.everyspec.com

SECTION 1 1-14 Code Description

Certification (SOC) where no Re-entry Control (REC) documentation is required. This MRC is Confidential.

(b) SYSCOM MRC Control Number. Used to identify those MRCs listed on MIP. First two digits of the SYSCOM MRC Control Number underlined indicates a new and/or revised MRC.

(8) Maintenance Requirement. Brief description of each maintenance requirement.

(9) Periodicity Code. Delineates how frequently the maintenance requirement must be performed (refer to paragraph (1-5.4b).

(10) Rate (Skill Level). Identifies the recommended skill level of the person(s) considered capable of performing the maintenance requirements. Qualified personnel other than the rate/rating specified may be assigned. When a Navy Enlisted Classification (NEC) is assigned or DCPO, substitution of other personnel is not allowed with the exception of civilian personnel whose Position Description (PD) requires the performance of PMS. Civilian personnel must be qualified through the 3M Personnel Qualification Standard (PQS) and are authorized to perform maintenance actions associated with their PD. This includes the performance of Maintenance Requirement Cards (MRCs) that require specific NECs, providing they are qualified for the specific equipment through PQS or a Job Qualification Requirement (JQR).

(11) Man-Hours (MH). The average time, per equipment, per person, needed to perform the maintenance requirements, not including time for tool preparation and return, tag out, or time needed for removal and/or replacement of interference.

(12) Related Maintenance.

(a) Mandatory related maintenance; Maintenance requirements that must be accomplished concurrently with another maintenance requirement (e.g., M-3# (# symbol indicates mandatory related)). Mandatory related maintenance from another MIP is indicated as: IC-017/003:M-4#.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-15 (b) Convenience related maintenance; Maintenance requirements that can be accomplished concurrently with another maintenance requirement (e.g., M-3 (# symbol is omitted)). Convenience related maintenance from another MIP is indicated as: EL-10:M-4.

(c) No related maintenance; This is indicated as "None."

(13) Inactive Equipment Maintenance (IEM). Reduced maintenance requirements for extended periods of equipment inactivity (refer to Section I Chapter 1 Paragraph 1-7).

Downloaded from https://www.everyspec.com

SECTION 1 1-16

Figure 1-2: HM&E MIP Example Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-17

Figure 1-3: Ordnance MIP Example Downloaded from https://www.everyspec.com

SECTION 1 1-18

Figure 1-4: Electronic MIP Example Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-19

Figure 1-5: An Example of A Preliminary MIP with MRCs Downloaded from https://www.everyspec.com

SECTION 1 1-20 1-5.2 Use of the PMS Master File The PMS Master File is maintained by the 3-M System Coordinator. Information contained in the master will pertain to all equipment for that organization. The organization's PMS requirements (MIPs/MRCs) for specific equipment, and additional supplementary information is provided by FTSCLANT/FTSCPAC on CD- ROM for the purpose of duplicate issue. The CD-ROM does not contain all of the PMS Master File data requirements (refer to paragraph 1-5.1). Any changes received between CD-ROM distributions must be retained on file until the changes are reflected on an updated CD. 1-5.3 Work Center PMS Manual The Work Center PMS Manual reflects that portion of the PMS Master File that contains only the planned maintenance requirements applicable to a particular Work Center. It is designed to provide a ready reference of planned maintenance requirements for the Work Center Supervisor, and will be retained in the working area near the Weekly PMS Schedule. 1-5.4 Maintenance Requirement Card (MRC) MRCs (see Figure 1-6) provide detailed procedures for performing maintenance requirements and describes who, what, how, and with what resources a specific requirement will be accomplished. MRCs contain the following information and instructions:

a. Date. This block contains the month and year when the MRC was prepared.

b. MRC Code. The code assigned to the MRC consists of two parts. The first part of the MRC code is the MIP series code. MRCs applicable to more than one MIP series will have each MIP series entered in this block. If more than four MIP series are applicable, reference will be made to a note in the procedure block. The second segment is the maintenance requirement periodicity code. The only authorized periodicities are as follows:

Periodicity Codes

D - Daily Q - Quarterly 2D - Every 2nd day S - Semiannually 3D - Every 3rd day 9M - Every 9th month W - Weekly A - Annually 2W - Every 2nd week xM - Every x months Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-21 Periodicity Codes

3W - Every 3rd week "x"= number of months M - Monthly 2M - Every 2nd month

NOTE:

An asterisk (*) following the periodicity code indicates a Safety of Ship item and requires the ship/or user to comply with reference (e).

Maintenance requirements with calendar periodicity’s greater than every 60 months may be developed for applicable ship classes in extended operability programs up to the length of the maintenance cycle. These periodicity’s must be evenly divisible by six months (i.e., 66M, 72M, 78M, 84M, etc.).

Non-Calendar Periodicity

R - Situation Requirement U - Unscheduled Maintenance

Inactive Equipment Maintenance (IEM)

LU - Lay-Up PM - Periodic Maintenance SU - Start-Up OT - Operational Test

The periodicity code also includes a number for specific identification. When more than one MRC of the same periodicity exists in the same MRC set, the MRCs in most cases, will be numbered consecutively, e.g., "D-1," "D-2," "D-3," or "M-1," "M- 2," etc. An existing MRC may be reapplied to a revised MIP even though the periodicity code of the reapplied MRC may not fall within the normally sequential numeric periodicity codes. For example, W-1, W-2, W-3, W-6 may appear on a MIP, where W-6 was an existing MRC that was reapplied to this equipment. Technically, valid MRCs will not be reprinted merely to change the periodicity code number. Non-sequential numbers will not affect scheduling or management control.

Dual periodicity codes are used when configurations or utility differences of a permanent nature exist between installations of the same system or equipment. A dual periodicity code may be assigned if no other aspect of the MRC requires modification to fit both periodicities. For example, equipment installed in an Downloaded from https://www.everyspec.com

SECTION 1 1-22 SSN or in a surface unit may see daily use, while the same equipment installed in an SSBN may be idle for long periods of time, creating a situation where it is unnecessary to perform the described maintenance as frequently. In this case, a dual periodicity code such as M-1/Q-1 or Q-1/S-2 may be assigned. When a dual periodicity code is assigned, a note on the MIP and MRC will specify which periodicity code to schedule.

Situation requirement codes may be used with a calendar periodicity code in certain circumstances. These situations apply when both the situation and the calendar periodicity govern the scheduling of the requirement. Examples include:

(1) (M-1R): Monthly or every 600 operating hours, whichever occurs first.

(2) (W-3R): Weekly or after each use, whichever occurs first.

(3) (S-1R): Semiannually or during each upkeep period, which ever occurs first.

(4) (Q-1R): Quarterly or prior to getting underway, whichever occurs first.

(5) (R-1W): When a situation occurs, accomplish weekly.

When the periodicity code includes a situation requirement (e.g., R-1D, R-1W) a note of explanation is required in addition to the basic code. This note shall be the first entry in the procedure block.

Unscheduled maintenance requirements are those documented actions required to restore a system/equipment to an operational condition within predetermined tolerances or limitations. Unscheduled maintenance requirements evolve from system/equipment failures or other indications of system/equipment degradation, and include alignment, adjustment, and repair. Unscheduled maintenance procedures are described on unscheduled MRCs (see Figure 1-7), and listed on appropriate MIPs.

c. Location. This block contains the specific location, EGL, or TYCOM authorized check off list detailing equipment location. Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-23 d. Ship System, System, Subsystem, and Equipment. Identification of the ship system (functional group), system, subsystem, or equipment involved.

e. Rates. Identifies the recommended skill level of the person(s) considered capable of performing the maintenance requirements. Qualified personnel other than the rate/rating specified may be assigned. When an NEC is assigned, substitution of other personnel is not allowed with the exception of civilian personnel whose Position Description (PD) requires the performance of PMS. Civilian personnel must be qualified through the 3M Personnel Qualification Standard (PQS) and are authorized to perform maintenance actions associated with their PD. This includes the performance of Maintenance Requirement Cards (MRCs) that require specific NECs, providing they are qualified for the specific equipment through PQS or a Job Qualification Requirement (JQR).

f. Man-Hours (M/H). The average time per equipment required of each rate listed in rates block to perform the maintenance, listed in hours and tenths of an hour. When more than one person in the same rate is required and time requirements are equal, M/Hs listed are the sum of their requirements. When more than one person in the same rate is required and time requirements are not equal, M/Hs are listed for each person separately. Total M/H is the sum of all entries in the M/H block, not including time for tool preparation and return, tag out, or time needed for removal and/or replacement of interference.

g. Maintenance Requirement Description. A brief definition of the PMS action to be done.

h. Safety Precautions. A listing of those precautions and references which direct attention to possible hazards to personnel while doing maintenance.

i. Tools, Parts, Materials, Test Equipment.

(1) Standard PMS Item Name (SPIN) numbered Tools, Parts, Material, and Test Equipment. Test equipments, materials, parts, tools, and miscellaneous requirements necessary for the maintenance action are listed and categorized in order (see Figure 1-6). Items within the category are numbered and identified by the applicable SPIN number in brackets. Entries in this block can be referenced to the Standard PMS Materials Identification Guide (SPMIG) for stock Downloaded from https://www.everyspec.com

SECTION 1 1-24 number identification. Stock numbers are also listed in the Hazardous Materials User's Guide (HMUG) for Personal Protective Equipment (PPE). The five basic categories are as follows:

(a) Category I-Test Equipment. Category I is used only for Portable Electric/Electronic Test Equipment (PEETE) listed in the Test Equipment Index (TEI), NAVSEA-TM- STOOO-AA-IDX-010/PEETE. All items are assigned a Sub-category (SCAT) code, which groups test equipment models having the same test capability into one code. Aboard ship, the Ships Portable Electrical/Electronics Test Equipment Requirements List (SPETERL) establishes allowances for PEETE within each SCAT code. MRC test equipment requirements are synchronized with the SPETERL.

(b) Category II-Materials. Materials include a wide range of administrative and housekeeping items, which may not be consumed entirely. Some consumable items (grease, oils, solvents, etc.) are consumed each time the maintenance action is performed, whereas, others (buckets, funnels, ladders, etc.) are not.

(c) Category III-Parts. Parts are defined as any items, which are an integral part of the equipment. For example: gaskets, mechanical seals, packing material, O-rings, filters, etc. The medium for identification of PMS part requirements in the Navy Supply System is the Allowance Parts List (APL). Ship unique repair parts are not listed in the SPMIG.

(d) Category IV-Tools. Category IV covers common hand tools of all types except "special tools."

(e) Category V-Miscellaneous. Category V covers all equipage items as well as any other special tools/materials not otherwise covered under categories I through IV. As a general rule, all items, which are identified and supported through Allowance Equipage Lists (AELs), will be considered Category V. Special tools are equipment-unique tools that are designed for a particular piece of equipment by the manufacturer. Such tools always have a manufacturer's part number and Commercial and Government Entity (CAGE). Per NAVSEASYSCOM/Naval Supply Systems Command (COMNAVSUPSYSCOM) policy, special tools will be listed on the APL and are, therefore, classified as repair parts. Equipage items are Category V even though some may be used as a tool; for example, jacking gear. Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-25

(2) Non-SPIN Tools, Parts, Materials, Test Equipment. Stock numbers, manufacturer's instructions, etc., for entries not covered by the SPIN/SPMIG or GPEETE Index are identified on the MRC.

j. Procedure. This block details the sequence of steps to be followed in performing the maintenance action. Reference to other approved procedures may be included on the MRC. As data may vary between ships, the MRC may contain blanks in which ship's company must supply the data necessary to properly do the work, e.g., pressure settings, temperature settings, brush tension, limiting speed, tolerances, and levels. The necessary data can generally be found in the equipment/system technical manual, ship's information book, ship's and equipment drawings, Naval Ships' Technical Manual, or Operational Sequencing System (OSS). If the data necessary to fill in the blanks is not available to ship's company, a PMS Feedback Report requesting the required data should be submitted.

Safety precautions will be listed prior to applicable steps and/or procedural actions. Specific categories are:

(1) Warning: Death or injury may result if the operating/handling procedures and practices are not correctly followed.

Warning text should be listed in the safety precautions' block and will be repeated preceding the procedure involved.

(2) Caution: Damage to equipment may result if the operating procedures and practices, etc. are not correctly followed.

Cautions are not listed in safety precautions block but will precede the instruction for the procedure involved.

The word "NOTE:" will precede procedural advisories.

k. SYSCOM MRC Control Number. This block contains the three segment code used in cataloging MRCs.

When MRCs are classified, an unclassified locator card (see Figure 1-8) is provided. The locator card duplicates the information in all of the MRC blocks except the procedures block, and includes one of the following statements:

Downloaded from https://www.everyspec.com

SECTION 1 1-26 "Maintenance procedure with the requirement is CONFIDENTIAL. Maintenance Requirement Card is stowed in _______________."

"Maintenance procedure with the requirement is SECRET. Maintenance Requirement Card is stowed in _______________."

The classified MRC is printed on pink stock with the classification indicated at the top and bottom of each page. Classified MRCs will be handled per reference (b). Refer to reference (c) for the handling procedures for classified information on compact discs.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-27 Figure 1-6: A Maintenance Requirement Card (MRC)

Downloaded from https://www.everyspec.com

SECTION 1 1-28

Figure 1-7: Example of an Unscheduled MIP Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-29 1-5.5 Equipment Guide List (EGL) The EGL (OPNAV 4790/81, Figure 1-9) is used with a controlling MRC when the MRC applies to a number of identical items (i.e., motors, controllers, life rafts, valves, test equipment, small arms, etc.). Each listed item will have a unique identifier assigned. Each ship prepares its own EGLs.

The amount of time it takes to perform maintenance on each item should be considered to determine the number of items to include on an EGL. Each EGL should contain no more than a single day’s work. If more than 1 day is required, separate EGLs are prepared for each, and numbered consecutively. MRC’s with mandatory related maintenance should use the same EGL’s to coordinate completion.

In some instances it may be unnecessary or impractical to list equipment on EGLs. For instance, if the equipment is listed on a TYCOM directed check-off list, a Calibration Recall Program, or Periodic Maintenance Requirement (PMR) is in effect, a notation of the applicable instruction in the location block of the MRC is all that is required.

In addition to the standard EGL, a limited number of specialized EGLs are available from FTSCLANT/FTSCPAC. A listing by applicable MIP/MRC may be obtained by PMS feedback report. Examples are the Damage Control Petty Officer (DCPO) compartment/space inspection EGL and the degaussing current EGLs. 1-5.6 Tag Guide List The TGL (OPNAV 4790/107, Figure 1-10) contains the information necessary for equipment tag-out incidental to PMS accomplishment. The TGL contains the number of tags required, location of tags, position of the tagged item (open, shut, off, on, etc.) and permission or notification requirements. Each ship prepares its own TGLs. TGLs are prepared and used for laminated PMS Tag-out as regulated by reference (d). 1-5.7 Location and Use of MRCs, EGLs, and TGLs A master EGL/TGL file shall be maintained. Each master file is to contain applicable EGLs and TGLs for every applicable MRC. A complete Work Center file of applicable MRCs with associated EGLs and TGLs will be located in each Work Center. Maintenance personnel will use these to perform assigned planned maintenance as follows: Downloaded from https://www.everyspec.com

SECTION 1 1-30

a. Select the MRC scheduled for accomplishment from the Work Center file. Ensure that any associated EGLs and/or TGLs are also selected.

b. Obtain the required tools/parts/materials and calibrated test equipment listed on the MRC. EXCEPTION: Obtain hazardous material (HAZMAT) only when required to complete the maintenance.

c. Perform maintenance as stated on the MRC, observing safety precautions and notes as indicated.

d. Notify the Work Center Supervisor immediately whenever one or more of the following conditions exist:

(1) Any information on a MRC, EGL, or TGL is not fully understood or appears to be incorrect.

(2) Tools, parts, materials, or calibrated test equipment prescribed by the MRC are not available.

(3) Capability, training, or experience to properly perform the maintenance requirement (MR) as prescribed is doubted.

(4) Factors which would make performance of the MR, including the equipment tag-out unwise or dangerous (e.g., disassembly of equipment needed for operations, radiation when prohibited, situations causing safety hazards to exist, etc.) are identified.

(5) Equipment deficiencies or casualties are discovered.

(6) Any provisions or requirements on the MRC cannot be strictly adhered to or accomplished as prescribed.

e. Return the MRC and any associated EGLs/TGLs to the Work Center file upon completion of the requirement.

f. Report completed planned maintenance actions to the Work Center Supervisor who will update the Weekly PMS Schedule. Maintenance actions not fully completed will be reported to the Work Center Supervisor for rescheduling if still within periodicity, or listed as to the reason why it was not completed, as applicable. However, if material deficiencies or Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 1-31 casualties which are unrelated to that maintenance requirement are discovered, the maintenance requirement can be X'd off (provided the MR was fully completed), but the discrepancy must be reported as specified in Section I Chapter 3. MRCs conducted by outside activities are listed on ship's force MIPs and are indicated by a letter code designation in the "Other" column (refer to paragraph 1-5.1c). These MRCs are to be maintained in the PMS Master File and in the applicable Work Center file for informational purposes, to facilitate the scheduling of maintenance actions related to ship visits and should be documented as complete when the check has been completed. EGLs and TGLs are not required for MRCs assigned to outside activities. Downloaded from https://www.everyspec.com

SECTION 1 1-32

Figure 1-8: Single-Page Locator Card for Classified MRC Downloaded from https://www.everyspec.com

Figure 1-9: Equipment Guide List (EGL) 1-33 NAVSEAINST 4790.8B Downloaded from https://www.everyspec.com

Figure 1-10: Tag Guide List 1-34 SECTION I DRAFT Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-35 1-5.8 Shipboard Changes to MRCs a. The only modifications which shipboard personnel may make to the MRCs are as follows:

(1) Tools, Parts, Materials, and Test Equipment.

(a) Common hand tools and basic housekeeping items may be appropriately substituted or added, by the Work Center Supervisor, without changing the MRC.

(b) Approved parts or materials substitutes from the supply system, technical manual, or MIL-SPEC, etc., may be used.

(c) Test equipment or certified tools, which meet or exceed the SCAT code requirements may be used.

NOTE:

It must be ensured that substitutions satisfy both the basic maintenance and safety requirements of the MRC. If there is any doubt, a PMS Feedback Report (FBR) should be submitted specifying substitution desired and reason.

b. In the "Procedure" block, Work Center Supervisors may line out the non-applicable line items (alternate procedures) that do not pertain to current equipment/configuration when the step is followed with the words "if applicable" or a note identifying steps to be omitted. As these changes are Work Center specific, submission of a FBR is not required.

c. If a change to a maintenance procedure or periodicity for a specific MRC appears necessary or desirable, a FBR suggesting the change is to be forwarded to the FTSCLANT/FTSCPAC. MRCs affected shall be fully identified by citing the SYSCOM MRC control number, subsystem, equipment, the applicable MRC code, and complete SYSCOM MIP control number. Recommended changes should include all information available.

d. Each command has the prerogative to increase the frequency of performance of specified planned maintenance actions to meet local conditions.

e. There may be instances where an obvious typographical error has been made on the MRC (example: Turn Switch to ON; Downloaded from https://www.everyspec.com

SECTION 1 1-36 however, switch may already be ON and card should read Turn Switch to OFF). This type of error should not prevent the scheduling or performance of maintenance.

NOTE:

Extreme caution shall be taken when reviewing MRCs for this type of error. Errors must be obvious typographical errors, and a PMS FBR must be submitted immediately when discovered. Do not permanently alter the MRC until authorized by the applicable SYSCOM/ISEA/FTSCLANT/FTSCPAC. 1-5.9 PMS Trend Data If directed by the Fleet Commanders (FLTCs) and subordinate commanders, trend data records will be established and maintained for designated equipment. The purpose of this data is to record readings or other historical data over a continuing period of time (e.g., bearing clearances, resistance test readings, etc.). 1-5.10 Preliminary PMS Documentation Preliminary documents provide new or changed procedures that have not been given a final engineering validation. This documentation falls into two categories.

a. Preliminary MIPs without MRCs. Preliminary MIPs without MRCs are forwarded by the SYSCOMs via the FTSCs and provide guidance in maintaining equipment not covered by PMS. Their purpose is to aid the ship in identifying and scheduling maintenance. The ship is responsible for developing interim MRC procedures based on experience and applicable technical manuals in support of these MIPs. Before scheduling preliminary MIP requirements, the Work Center Supervisor and the Department Head shall verify their applicability to installed equipment. Preliminary MIPs are identified by a "P" code and number following the slash of the SYSCOM MIP control number.

b. Preliminary MIPs with MRCs. Preliminary MIPs with MRCs are provided by the SYSCOMs via FTSCLANT/FTSCPAC to provide the ship with advance coverage for use while the MIPs/MRCs are undergoing final technical review. Preliminary MIPs are identified by a "P" code and number following the slash of the SYSCOM MIP control number. Preliminary MIPs/MRCs are technically reviewed/approved by the cognizant SYSCOMs/BUMED. The approved MRCs will be provided following approval with the next update. Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-37 1-5.11 Advance Change Notices (ACNs). PMS ACNs are authorizations for and a record of changes to an existing MIP or MRC, or the addition of a new MRC. Applicable SYSCOMs/BUMED (Cognizant Design Activity or In-Service Engineering Agent (ISEA)) will issue message pen changes correcting errors in PMS documentation that affect the safety of personnel or can cause possible damage to equipment in the fleet. Pen corrections are interim measures only for urgently required changes. The FTSCs will distribute the revised MIP/MRC reflecting the changes indicated by the message to all affected MIP holders. Shipboard accountability for ACNs shall be accomplished by annotating the PMS Master File and the Work Center PMS Manual. The ACN reflecting the change must be kept on file until receipt of revised documentation. Types of changes indicated on PMS ACNs include:

a. Periodicity of accomplishment;

b. Deletion or modification of an existing maintenance requirement;

c. Addition or modification of a MRC procedure note to clarify the context or description of a procedure step;

d. Procedure step modification to correct maintenance technical data, e.g., frequency, pressures, voltages, current, decibels, resistance values, clearance, test data, etc;

e. Addition, deletion, or modification of an MRC procedure step which significantly improves the technical accuracy of the task.

f. Addition or modification to the list of tools, parts, materials and test equipment. 1-5.11.1 Control and Tracking of ACNs. Control and tracking of each ACN will be accomplished in the following manner:

a. A PMS ACN will refer to a specific MIP and MRC, the location of the revision will be indicated by a vertical block change bar outside the border of the ACN. A new MRC will be provided for each MRC affected by the ACN.

Downloaded from https://www.everyspec.com

SECTION 1 1-38 b. Each PMS ACN is serialized. The serial number consists of the originating activity code, MIP number, serial number, log number and date.

c. FTSCLANT/FTSCPAC will maintain accountability of all outstanding ACNs by MIP/MRC. The revised MIP will incorporate superseded ACNs.

The 3-M System Coordinator shall record the receipt of each ACN and distribute a copy to the appropriate Work Center files. 1-5.12 PMS Schedules The use of SKED Version 2.1 or higher for PMS Scheduling constitutes full compliance with all administrative provisions of this chapter. Guidance for use of SKED is provided in the Help menus and Wizards associated with SKED. Guidance for the manual preparation of PMS Schedules is contained in Appendix G. PMS Schedules are categorized as cycle, quarterly, and weekly schedules. 1-5.12.1 Cycle PMS Schedule The Cycle PMS Schedule (Figure 1-11) displays the planned maintenance requirements to be performed over long periods of time in the maintenance life cycle of the ship. The PMS Cycle will be determined by using Inter-Deployment Training Cycles (IDTCs). Each PMS Cycle, for ships, will consist of three IDTCs. The Cycle PMS Schedule shall also be reset after a Docking Availability. Multi-month requirements shall be scheduled relative to the first quarter after IDTC reset. A shore command’s PMS Cycle shall be 20 quarters. Multiple month maintenance requirements will have the quarter indicated in parentheses, 30M-1(4)(14), for the periodicity. Any multiple month checks that have not been accomplished in this PMS Cycle period will be scheduled during the first quarter of the new Cycle PMS Schedule. 1-5.12.1.1 Content of Cycle PMS Schedule The following information is to be included in the block/column indicated:

a. Ship. This block contains the ship's name and hull number.

b. Work Center. This block contains the applicable Work Center designator, and page number (e.g., "(pg. 1 of 1)".

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-39 c. Schedule Quarter after Overhaul as Indicated. This block contains annual, semiannual, multiple-month (4M and greater) maintenance requirements. Mandatory related maintenance checks, which are to be completed during the quarter are indicated by the pound sign symbol "#". The # sign, placed next to a primary check, indicates that there is mandatory related maintenance associated with that maintenance requirement. The MIP scheduling aids must be consulted when drafting the Quarterly Schedule to determine what mandatory checks apply and need to be scheduled.

d. Approval Signature/Date. This block contains the Department Head's signature and the date the Cycle schedule was approved.

NOTE:

A printed Cycle schedule with Department Head’s signature and date is not required when using SKED. The Department Head finalizing the schedule constitutes the approval signature.

e. MIP. This block contains a listing of the MIP codes for the PMS requirements to be scheduled on the Cycle schedule.

f. Component. This block identifies the related system, subsystems, or equipment of the scheduled PMS requirements.

g. Each Quarter. This block contains MRs with periodicities of 2W, 3W, M, and 2M, and any associated related maintenance checks (indicated by the "#" symbol). It also includes all situation requirements regardless of periodicity to be completed during each quarter.

Downloaded from https://www.everyspec.com

SECTION 1 1-40 1-5.12.2 Quarterly PMS Schedule The Quarterly PMS Schedule (Figure 1-12) displays the Work Center's PMS requirements to be performed during a specific 3- month period. This schedule, updated weekly, provides a ready reference to the current status of PMS for each Work Center. SKED performs this update based upon the Weekly Schedule. This schedule represents a divisional directive and, once approved, may be changed only with Division Officer approval. 1-5.12.2.1 Content of Quarterly PMS Schedule a. Space is provided for entering the Work Center, year, quarter after overhaul, Division Officer’s signature, date prepared, and months covered.

NOTE:

A printed Quarterly schedule with Division Officer’s signature and date is not required when using SKED. The Division Officer finalizing the schedule constitutes the approval signature.

b. Thirteen columns (15 columns for SSBNs), one for each week in the quarter, are used to schedule maintenance requirements. Columns are provided for the complete MIP number and any PMS requirements that may require to be rescheduled in the next quarter.

c. Use of the Quarterly PMS Schedule The Quarterly PMS Schedule serves as a directive for Work Center Supervisors for scheduling weekly maintenance. 1-5.12.3 Weekly PMS Schedule The Weekly PMS Schedule (Figure 1-13) displays the planned maintenance scheduled for accomplishment in a given Work Center during a specific week. The Weekly PMS Schedule provides the Work Center Supervisor a management tool for planning maintenance requirements. A Weekly PMS Schedule created in SKED by the Work Center Supervisor is used to assign and monitor the accomplishment of required PMS tasks by Work Center personnel. The creation of the Weekly PMS Schedule also produces a 13 Week Accountability log. When using SKED, there is no requirement to print the PMS Weekly Schedule. Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-41 1-5.12.3.1 Content of Weekly PMS Schedule The following items will be included in the weekly schedule:

a. Work Center code.

b. Date of current week.

c. MIP number minus the date code.

d. A list of applicable components.

e. Maintenance responsibilities assigned, by name.

f. The periodicity codes of maintenance requirements to be performed, listed by columns for each day.

g. Outstanding repairs and applicable PMS checks due in next four weeks. 1-5.12.4 13-Week Accountability Log The Work Center Supervisor shall maintain a 13-Week Accountability Log. SKED will produce this log. This log will be printed and posted in each Work Center for maintenance personnel to obtain PMS assignments. It will consist of the last 13 completed weeks of maintenance and the current week. At the end of the week the Division Officer will review and sign the log. The following information will be contained in the accountability log:

a. The printed name, date, and legal signature of the maintenance person actually accomplishing the maintenance. The maintenance person shall sign this log immediately upon completion of the maintenance action. If multiple maintenance persons are assigned to a single maintenance action, the Petty Officer in Charge or the most senior person assigned must sign the 13 Week Accountability Log.

b. Detailed reasons for non-accomplishment of maintenance requirements should be entered by the maintenance person in the 13 Week Accountability Log immediately after informing the Work Center Supervisor of the non-accomplishment of the maintenance action.

NOTE: Downloaded from https://www.everyspec.com

SECTION 1 1-42

Material deficiencies or casualties discovered, which are unrelated to that maintenance requirement, must be reported to the Work Center Supervisor. 1-5.12.5 Annotation of Weekly PMS Schedule The Weekly PMS Schedule must be updated with the status of Maintenance Requirements. The Work Center Supervisor will annotate the Weekly PMS Schedule as follows:

X = Fully Accomplished. The symbol "X" is the mark used to indicate completion of a maintenance requirement. Fully accomplished MRCs will be X'd off separately on the quarterly schedule. Ensure that situation requirements which were accomplished are added and X'd off separately.

O = Not Fully Accomplished. A circled requirement indicates a requirement that was not accomplished or only partially accomplished following the applicable MRC. A circle with a short arrow will be used to indicate rescheduled MRs.

¢ = Satisfied by Higher Level Test. Upon successful completion of the system (higher) level test, an "X" is marked over the system level test requirement listed on the quarterly schedule. The symbol is used to mark scheduled equipment or lower level MRC requirements that have been satisfied by the successful completion of the parent system test. A brief explanation of the parent system test (including the MIP, who performed the maintenance, and when) is required on the reverse side of the quarterly schedule. (The MRCs that are so satisfied are identified on the applicable system level test MIP.)

If not fully accomplished, the maintenance requirement is circled and rescheduled. PMS requirements (other than daily checks) accomplished during the prescribed week, but not on the day specified, shall be considered completed on schedule and X'd off.

Downloaded from https://www.everyspec.com

Figure 1-11: Cycle PMS Schedule

1-35 NAVSEAINST 4790.8B Downloaded from https://www.everyspec.com

Figure 1-12: Quarterly PMS Schedule

1-35 NAVSEAINST 4790.8B Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-45 1-5.13 Shift of Maintenance Responsibility Individual ships sometimes consider it desirable or necessary to shift maintenance responsibility from one Work Center to another, to combine two or more existing Work Centers, or to split an existing Work Center. Requests for changes of PMS maintenance responsibility should not be submitted to accommodate a temporary situation such as short-term assignment of two Work Centers to one supervisor. Transfer of maintenance responsibility from one Work Center to another requires changes in LOEP and PMS distribution, and can represent a considerable administrative burden.

The following factors should be carefully considered before submitting such requests:

a. Composition of Work Centers by size and ratings.

b. Scope of maintenance responsibilities.

c. Work Center workload.

d. Ease of administration of a Work Center as a cohesive maintenance group.

e. Importance of Work Center grouping to equipment maintenance responsibilities, PMS scheduling, MDS reporting, and Current Ship Maintenance Project (CSMP) listings.

When changes in maintenance responsibility are considered necessary, the following procedures apply:

a. Submit a PMS FBR (category B). Indicate from which Work Center(s) equipment is to be deleted and to which it is to be transferred. All FBRs requesting a shift of maintenance responsibility must be signed by the Executive Officer.

b. Work Center or equipment changes will be reported via the OPNAV 4790/CK or Work Candidate (as applicable) or equipment file configuration update. All outstanding equipment deficiencies for the equipment, which was moved, will also be transferred to the new Work Center.

c. After the FBR is signed by the Executive Officer, the following actions are authorized prior to receipt of the Force Revision (FR) reflecting the change:

Downloaded from https://www.everyspec.com

SECTION 1 1-46 (1) Delete equipment from the present PMS master file, LOEP and Work Center manuals. Add the equipment to the appropriate LOEP of the department and Work Center receiving the responsibility. Annotate the FBR serial number on the affected line item on the LOEPs. The PMS master file must contain a record of deleted equipment until the change is reflected in the next update.

(2) Transfer the affected MIPs, MRCs, and EGLs to the Work Center receiving maintenance responsibility. Prepare new TGLs as necessary.

(3) In SKED, delete the equipment from the current schedule. For manually generated PMS schedules, line out equipment on the present Cycle PMS Schedule with one single line and annotate the FBR serial number reflecting that the maintenance responsibility has been transferred (identify receiving Work Center and date of transfer). Make the same change on the Quarterly and Weekly PMS Schedules.

(4) In SKED, add the equipment on the current schedule. For manually generated PMS schedules, add equipment on the Cycle PMS Schedule of the Work Center receiving the maintenance responsibility and date the schedule at the extreme left. Schedule MRs on the Cycle PMS Schedule. Make the same changes on the Quarterly and Weekly PMS Schedules.

Downloaded from https://www.everyspec.com

Figure 1-13: Weekly PMS Schedule

1-35 NAVSEAINST 4790.8B Downloaded from https://www.everyspec.com

SECTION 1 1-48 1-5.14 Scheduling Exceptions Upon review of a MIP, it may be determined that certain maintenance requirements are not applicable to equipment/systems. In such instances, if authorized by a “scheduling aid” entry on the MIP, strike a line through the requirement on the MIP.

If not authorized by a scheduling aid, submit a PMS Feedback Report identifying the reason for non-applicability. No change shall be made to the MIP until authorized; however, performance of affected MRs will be discontinued. Document the non- accomplishment of the MR on the quarterly close out.

There are instances in which a MIP includes a requirement for more than one Work Center to participate in the performance of specified maintenance actions. When this occurs, a decision is required by the command concerned as to whether the MIP will be split or will be scheduled singly by one Work Center and work accomplished through coordination by Work Center Supervisors. There must be a necessity for a complete requirement to be accomplished by the other Work Center before splitting the MIP. If the MIP is split, the following procedures apply:

a. Submit a category B PMS FBR reporting the decision to split the maintenance responsibility. If the ship cannot generate its own additional copies of the required MIPs and MRCs, include a request for the additional PMS documentation to ensure an adequate number for the Work Center/departments.

b. The FBR must be approved by the Executive Officer.

c. Distribute the MIPs, MRCs, and EGLs to the Work Center concerned. Insert the MIPs into the PMS Work Center files, and add the equipment to the applicable LOEPs. Tailor the MIPs to each Work Center by lining out on the MIP the MRCs for which the Work Center is not responsible.

d. If the Cycle PMS Schedule for each affected Work Center does not reflect the equipment, add the equipment to the schedule. Schedule only the periodicity codes that pertain to that Work Center. For manually developed PMS Schedules, make the appropriate changes to the Quarterly and Weekly PMS Schedules.

Concurrent scheduling and accomplishment of PMS MRs which require system/equipment deactivation can improve system Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-49 availability by reducing the time it would be unavailable to perform its functions if PMS tasks were scheduled and accomplished sequentially. Scheduling of maintenance by a lead Work Center can avoid excessive system non-availability due to PMS requirements, which may occur if several Work Centers separately schedule the PMS for which they are responsible. It may be necessary and desirable for the Executive Officer to provide overall guidance and for the 3-M System Coordinator and Department Heads to coordinate the scheduling and accomplishment of PMS performed by more than one Work Center or department. 1-5.15 PMS Feedback Report (FBR) Form (OPNAV 4790) The PMS FBR is used to notify FTSCLANT/FTSCPAC of matters related to PMS. The FBR form is composed of an original and four copies. Instructions for preparation and submission of the form are printed on the back of the last copy. While the FBR will provide initial PMS coverage and changes, submission of an OPNAV 4790/CK form is required to initiate the logistic support change process (see Section I Chapter 3). Automated forms for FBR submission, may be transmitted electronically, via the SKED Feedback Report Wizard (preferred) or the FTSC website at https://ftsc.navy.mil/pmsdb/tfbrform.cfm or the Anchor Desk website at http://anchordesk.navy.mil, click on Enter the Portal, Submit a deficiency report and PMS Technical Feedback form. 1-5.15.1 PMS Feedback Reports There are three types of FBRs: Category A, Category B, and Urgent.

a. Category A - This type of FBR is non-technical in nature and is intended to meet PMS needs which do not require technical review, including changes in Work Centers. Category A FBRs are submitted to request classified or other PMS documentation, which cannot be obtained locally (see Figure 1- 14). With the ship's master PMS requirements on compact disk (CD-ROM), replacement copies will be generated with the print- on-demand capability.

b. Category B - This type of FBR (Figure 1-15) is technical in nature, and is used to report:

(1) Technical discrepancies inhibiting PMS performance.

(2) Shift of maintenance responsibilities.

Downloaded from https://www.everyspec.com

SECTION 1 1-50 NOTE:

Figure 1-16 shows the reverse side of the FBR form and provides the instructions for preparation and submission.

c. Urgent FBR – An FBR will be considered URGENT when the reason for submission of a PMS FBR involves safety of personnel, ship, or potential for damage to equipment and relates to the technical requirements of PMS. Urgent FBRs will be forwarded by naval message containing a PMS Feedback Serial Number, to both FTSCLANT and FTSCPAC, info cognizant SYSCOM/BUMED/NAVSAFECEN/ TYCOM. The message shall describe the unsafe procedures or conditions, and shall identify the MIP/MRC involved (Figure 1- 17). 1-5.15.2 FBR Processing/Response 1-5.15.2.1 3-M System Coordinator shall: a. Screen PMS FBRs to ensure they are complete and that resolution is not feasible on board the ship. Ensure MIP has been reviewed for scheduling aids and information pertaining to deleting MRCs.

b. Serialize and forward within four days of receipt. The FBR serial number will consist of two parts separated by a dash: a four-digit sequence number and the last two digits of the calendar year. The date will change on 1 January of each year, but the number sequence will continue, i.e., 4241-99, 4242-00. The sequence number will start with 1 and not repeat until 9999 has been reached.

c. Maintain accountability of all PMS FBRs submitted and action taken by the FTSCs, SYSCOM, etc, until corrected PMS documentation is received. The FBR accountability record may be disposed of upon receipt of a feedback reply rejecting the suggested change. SKED also contains a FBR accountability and tracking function that can be used in place of paper records.

d. Ensure the originator of each FBR and all other applicable Work Centers are kept appraised of action taken on the FBR, and that all materials and information received in response are distributed accordingly. Ensure that the originating Work Center and other applicable Work Center Supervisors implement the changes/corrections received.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-51

1-5.15.2.2 FTSCLANT/FTSCPAC Actions (See Appendix H for additional information)

a. Category A FBRs for replacement of missing classified MIPs/MRCs shall receive expeditious handling by the FTSCs.

b. Category B FBRs where resolution by FTSCLANT/FTSCPAC is possible, will be answered by electronic means, if possible. Paper responses will be a last resort.

c. Related changes in documentation shall be reflected in the LOEP provided with the subsequent Force Revision.

d. Category B FBRs, where resolution by FTSCLANT/FTSCPAC is not possible, shall be processed as follows:

(1) The FBR will be electronically forwarded to the applicable technical review activity for resolution.

(2) FTSCLANT/FTSCPAC will maintain the PMS MIS copy.

(3) An electronic notice will be provided the ship identifying what action is pending and by whom.

e. Related changes in documentation shall be reflected in the LOEP provided with a subsequent revision. 1-5.15.2.3 Technical Review Activities. The cognizant Technical Review Activity receiving technical FBRs for resolution shall analyze, categorize, and process these FBRs as follows:

a. URGENT Feedback Reports. (See paragraph 1-5.15.1c) SYSCOM/BUMED/NAVSAFECEN technical review activities shall provide a preliminary response to the originator by message, info applicable TYCOMs, SYSCOM/BUMED, NAVSAFECEN Norfolk, and FTSCLANT and FTSCPAC within 1 working day of receipt. TYCOM shall provide copies of Urgent FBR resolutions to all holders of the affected MIPs/MRCs.

b. Routine Technical Feedback Reports. The technical review activity shall provide the resolution to the question asked in the FBR to FTSCLANT/FTSCPAC by direct entry into the PMS MIS or other electronic means. The response may contain corrections to PMS documentation incorporating approved revised Downloaded from https://www.everyspec.com

SECTION 1 1-52 procedures, and superseding documentation held by the ship, or an explanation of the reasons for non-concurrence or deferring concurrence with the ship's recommendation or request. Electronic responses are preferred over paper. FTSCLANT/FTSCPAC will provide an electronic response to the originator.

NAVSEA has established a goal of providing the answer to a TFBR in one day. While it is realized that some TFBRs will require more extensive research, the majority of TFBRs received can and should be answered in one day.

When the technical review activity concurs with a PMS FBR, FTSCLANT/FTSCPAC will provide all holders of the affected MIP/MRC with updated PMS in the next force revision.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-53

Figure 1-14: PMS Feedback Report, Category A REPORT SYMBOL OPNAV 4790-4 SEE INSTRUCTIONS ON BACK OF GREEN FROM (SHIP NAME AND HULL NUMBER) USS NEVERWAS FFG 999 SERIAL # 1074-00 DATE 09 MAR 00 TO NAVAL SEA SUPPORT CENTER ____________________________ (Category A) TYPE COMMANDER (Category B) X PACIFIC SUBJECT: PLANNED MAINTENANCE SYSTEM FEEDBACK REPORT SYSTEM, SUB-SYSTEM, OR COMPONENT SONAR RECEIVING SET APL/CID/AN NO./MK. MOD AN/SQR-18A(V)1 SYSCOM MIP CONTROL NUMBER 4621/23-23 SYSCOM MRC CONTROL NUMBER VARIOUS DESCRIPTION OF PROBLEM X MIP/MRC REPLACEMENT TECHNICAL TYCOM ASSISTANCE OTHER (Specify) REMARKS REQUEST TWO COPIES EACH OF FOLLOWING CLASSIFIED MRCs: 72 EZV9 N C9 EZV0 N 10 EZW5 N TOTAL OF 6 MRCs REQUESTED. ADEQ UATE SECURE STORAGE PER OPNAVINST 5110.1H IS AVAILABLE. CATEGORY A CATEGORY B DIV. OFFICER DEPT. HEAD 3-M COORDINATOR Originator do not write below. For TYCOM use only. TYCOM CONCUR DO NOT CONCUR TAKES ACTION PASSES FOR ACTION TYCOM REP SIGNATURE DATE OPNAV 4790/7B (Rev. 9-89) S/N 0107-LF-007-8000 EDITION OF 3-84 MAY BE USED UNTIL EXHAUSTED ACTION COPY PAGE ______ OF ______ ORIGINATOR & WORK CENTER CODE ET (SW) Johnson EE01 LT Linda Dawson I. M. Daboss, CDR, USN GMC (SW) Glen Hayes 11 Downloaded from https://www.everyspec.com

SECTION 1 1-54

REPORT SYMBOL OPNAV 4790-4 SEE INSTRUCTIONS ON BACK OF GREEN PAGE FROM (SHIP NAME AND HULL NUMBER) USS NEVERWAS (FFG-999) SERIAL # 0011-00 DATE 04 APR 00 TO NAVAL SEA SUPPORT CENTER ____________________________ (Category A) TYPE COMMANDER (Category B) SUBJECT: PLANNED MAINTENANCE SYSTEM FEEDBACK REPORT SYSTEM, SUB-SYSTEM, OR COMPONENT Auto Ballast Comp Sys APL/CID/AN NO./MK. MO SYSCOM MIP CONTROL NUMBER F-37/2-60 SYSCOM MRC CONTROL NUMBER T 44 E12F N DESCRIPTION OF PROBLEM MIP/MRC REPLACEMENT TECHNICAL TYCOM ASSISTANCE OTHER (Specify) REMARKS Before testing setting on relief valve, we need calibration steps for Leslie-Matic controller. This step in not contained on the present MRC. This ship does not have any pub or tech manual showing the steps that should be taken in checking the Leslie-Matic controller for accuracy. CATEGORY A CATEGORY B DIV. OFFICER DEPT. HEAD 3-M COORDINATOR Originator do not write below. For TYCOM use only. TYCOM CONCUR DO NOT CONCUR TAKES ACTION PASSES FOR ACTION TYCOM REP SIGNATURE DATE OPNAV 4790/7B (Rev. 9-89) S/N 0107-LF-007-8000 EDITION OF 3-84 MAY BE USED UNTIL EXHAUSTED ACTION COPY PAGE ______ OF ______ ORIGINATOR & WORK CENTER CODE P. R. Saunders EB14 Lt W. M. Smith D. R. Campbell Michael Manlove 11 X X

Figure 1-15: PMS Feedback Report Category B Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-55

1. ORIGINATOR

a. Typewritten copies are preferred, however, handprinted copies are acceptable. Use ballpoint pen and ensure all copies are legible.

b. EQUIPMENT IDENTIFICATION: Fill in titled blocks that apply. Give as much information that can be determined. Ensure that correct APL number is used for hull, mechanical or electrical equipment or electronic/weapons equipment which does not have an Army-Navy number or mark/mod designation.

c. DESCRIPTION OF PROBLEM: Check the appropriate box.

Category A

(1) MIP/MRC REPLACEMENT: Ensure that PMS documentation request is current in accordance with latest SFR. For missing MIPs/MRCs, give SYSCOM control numbers when they can be determined. If SYSCOM control numbers cannot be determined, provide as much nameplate data as can be obtained. When ordering a variety of missing/worn MIPs/MRCs, the subject section shall be left blank.

Category B

(2) TECHNICAL:

(a) Identify specific discrepancy discovered in PMS by MRC control number, step number, etc.

(b) For publication discrepancies identify publicatio n by number, volume, revision date/number, change number, page, paragraph and or figure as appropriate.

THIS FORM WILL NOT BE USED TO ORDER PUBLICATIONS.

(3) TYCOM ASSISTANCE: Includes clarification of 1-M instructions and other matters related to PMS administration.

(4) OTHER: Identify in detail any problem not covered by (1) through (3) above. Shifts of maintenance responsibility will be reported under this item. Ensure that all Work Centers involved in the change are identified by Work Center code. Approval by the Executive Officer will be shown in the "Remarks".

d. REMARKS: Provide brief, but complete, description of problem or requirement. Executive Officer indicate approval of maintenance responsibility shift by endorsement. Use additional forms if more space is required. Mark additional forms, "page 2 of 2", "page 2 of 3", etc. Staple additional forms behind basic form.

e. ORIGINATOR IDENTIFICATION: Sign and insert Work Center code in appropriate space.

2. DIVISION OFFICER: Review for accuracy and completeness and sign in the space provided.

3. DEPARTMENT HEAD: Review for accuracy and completeness and sign in the space provided.

4. 1-M COORDINATOR:

a. Serialize, date and sign in the appropriate spaces.

b. ROUTING INSTRUCTIONS: For Category "A" FBRs, forward the white and yellow copies to the appropriate NAVSEACEN and the pink copy to the TYCOM. For Category "B" FBRs, forward the white, yellow and pink copies to the TYCOM. Retain blue copy in suspense file. Return green copy to the originator.

Figure 1-16: FBR Preparation Downloaded from https://www.everyspec.com

SECTION 1 1-56

ADMINISTRATIVE MESSAGE PRIORITY P 112259ZJAN00 FM ORIGINATING ACTIVITY//CODE// TO FTSCLANT NORFOLK VA//CODE// FTSCPAC SAN DIEGO CA//CODE// INFO COMNAVSEASYSCOM WASHINGTON DC//CODE// NAVSAFECEN NORFOLK VA//CODE// COGNIZANT TYPE COMMANDER//CODE// CHAIN OF COMMAND//CODE// BT UNCLAS //N04790// MSGID/GENADMIN/ORIGINATING ACTIVITY// SUBJ/URGENT PMS FBR SERIAL 1827-00// RMKS/ 1. SYSCOM MIP CONTROL NR 5553/026-43. 2. MRC CODE 5553 60M-2R. 3. SYSCOM MRC CONTROL NR 218QZPN. 4. IAW SHIPALT 961-00670K, PHNSY HAS INSTALLED HALON SYSTEMS IN JP-5 PMP RM AND 3 GTG RM. SYSTEMS HAVE 1 1/2 INCH FLEX HOSES INSTALLED ON DISCHARGE SIDE. PER INGALLS PLANNING YARD LIAISON ACTION RECORD 670-990-3513, HOSES ARE TO BE HYDRO TESTED TO 1600 PSI (135 PERCENT DESIGN PRESSURE). 5. PER MRC 5553/026-43 60M-2R, 1 1/2 INCH FLEX HOSES ARE TO BE HYDRO TESTED TO 1750 PSI (150 PERCENT DESIGN PRESSURE). 6. CONDITIONS UNSAFE TO PERSONNEL AND EQUIPMENT MAY EXIST IF GAS CHARGED, HIGH PRESSURE SYSTEM IS NOT TESTED TO PROPER SPECIFICATIONS. 7. REQUEST TEST PSI CONFIRMATION/RESOLUTION AND CORRECTIVE ACTION REQUIRED.// BT

Figure 1-17: Urgent Feedback Report (Sample) Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-57 1-5.16 PMS Force Revision After PMS has been installed, it is necessary to ensure that the installed PMS packages are periodically updated to reflect changes in system/equipment and package configuration and to provide PMS documentation (new issues and revisions). 1-5.16.1 Work Center Verification. It is important that all MIPs/MRCs received by a Work Center are carefully reviewed by a senior petty officer to verify:

a. That the equipment identified on the MIP is in fact installed in/assigned to the Work Center.

b. That the MIP/MRC is applicable to the system/ equipment (APL, correct manufacturer, model, MK-MOD, alteration, etc.) that is installed.

c. That the requirements/provisions (procedures, tools, skills, man-hours, elapsed time) listed on the MRC are correct, adequate, safe, feasible, logical, reasonable, simply stated, and not excessive. 1-5.16.2 Revision Package Contents Each PMS Force Revision package contains:

a. Automated Library Issue Document (ALID) that identifies:

(1) the applicable force revision

(2) applicable ship hull number

(3) superseded MIPs

(4) superseding MIPs

(5) applicable Work Center codes

(6) quantities

(7) added/deleted MIPs.

b. The List of Effective Pages (LOEP), Report PMS 5 (see Figure 1-1).

Downloaded from https://www.everyspec.com

SECTION 1 1-58 c. PMS MIP to Work Center File, Report PMS 4 (see Figure 1-18). This report provides the ship accountability and control of current MIP to Work Center assignments.

d. Technical Feedback Status Report, Report PMS 22 (Figure 1-19). This report contains outstanding/completed Technical Feedback Reports received by FTSCLANT/FTSCPAC. Category A FBRs will not be reflected on this report. 1-5.16.3 Revision Procedures Force revision procedures are as follows:

a. PMS revision package will be addressed "Attention: 3-M System Coordinator."

b. The Force Revision number is listed in the upper right-hand corner of the Automated Library Issue Document (ALID). This number will be the same for all ships and will identify each Force Revision in the calendar year. For example, the first package issued in calendar year 2000 was assigned the number 1-00.

c. Commands having no additions or changes will receive a copy of the ALID with a statement, "No Ship’s Master File changes reflected by this Force Revision."

d. Ships in overhaul will receive Force Revision packages. Updating procedures for PMS packages during overhaul are contained in Section I Chapter 2.

e. Shipboard procedures for implementation of force revisions are as follows:

(1) Force Revisions are normally effective on the first Monday of the quarter and are mailed prior to the beginning of a quarter to allow adequate preparation prior to the scheduled implementation date. When a Force Revision is not received in time to permit implementation on the first Monday of the quarter, the actual date of implementation will be designated by the Executive Officer. When a Force Revision is received, only safety-related PMS updates are required to be implemented within 2 to 5 working days of receipt, with the remainder of the PMS updates being implemented on the effective date for the Force Revision. Safety-related changes will be marked with a vertical line on the PMS Quarterly Schedule for the day directed by the Executive Officer for command wide Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-59 implementation. The line should be labeled "INSTALLED REVISION".

(2) The 3-M System Coordinator shall enter the Force Revision number from the ALID in the Change Service Accountability Log (Figure 1-20) prior to routing the change documentation to work centers. Two examples of PMS Change Documentation Routing Memorandum are shown in Figures 1-21 and 1-22. The Change Service Accountability Log is explained further in paragraph 1-5.17.

(3) The Work Center Supervisor, upon receipt of the change document from the 3-M system coordinator, shall take the following actions:

(a) LOEP Changes

(b) When a MIP is superseded in its entirety, line out the complete number of the superseded MIP, enter the number of the new MIP, and annotate with the revision serial number.

(c) When a MIP number is partially updated (e.g., revision date change, and preliminary to permanent MIP), line out only that portion of the MIP number, which is changed, and write in the updated portion of the MIP number.

(d) When a new MIP is issued, enter the new MIP number and applicable equipment information at the end of the current LOEP for the applicable Work Center.

(e) Changes resulting from force revisions. Replace the superseded LOEP in the PMS Master and Work Center files. SKED users will update their schedules using the CD-ROM. Steps (f) and (g) apply to paper users. All changes will be made in ink.

(f) Each will compare existing cycle schedules with the LOEP to identify new, deleted, or revised MIPs. New MIPs will be added to the bottom of cycle schedules. Deleted MIPs will be lined out and the force revision number noted by the line out.

(g) Revised MIPs will be compared with old MIPs to identify changes in periodicity. Required changes will be shown on the cycle schedule.

Downloaded from https://www.everyspec.com

SECTION 1 1-60 (h) MIP Changes

1. Remove superseded MIPs from Work Center files add new MIPs. (If an updated PMS Master File on compact disk is received as a replacement to the PMS Master, the new MIPs will already be included.)

2. Destroy superseded MIPs. Compact disks will be destroyed as directed by reference (c).

(i) MRC Changes

1. Remove superseded MRCs from MRC files; add new MRCs. If an updated PMS Master File is received, the new MRCs will already be included.

2. Prepare/revise associated EGLs and TGLs as necessary. TGL revisions will require the Commanding Officer's approval.

3. Destroy superseded documentation.

(j) Update the Cycle PMS Schedule

1. Update the Cycle PMS Schedule by using the FR CD-ROM and the SKED program.

(k) Prepare a new Quarterly PMS Schedule.

(l) Prepare a new Weekly PMS Schedule. Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-61

Figure 1-18: PMS MIP to WC File, Report No. PMS 4 Date: 06/02/00 Planned Maintenance System Page: 1

Time: 14:24:15 MIP to Work Center (PMS 4) FR: 2-00

Unit: DDG 0053 UIC: R21313 USS JOHN PAUL JONES

Work Center MIP Nomenclature Distribution ___________ ______________________________ _____________________

1230/001-C9 TANKS, VOIDS, AND TRUNKS EM04 1501/001-B9 SUPERSTRUCTURE & FITTINGS ER01 OD01 1631/004-C9 SEA CHESTS EA01 EM01 EM02 1651/005-10 SONAR DOME RUBBER WINDOW CA01 1671/001-10 ARMORED DOORS & HATCHES ER09 1671/005-C9 WTRTT, DR, TORPEDO MAGAZINE ER09 1672/001-10 ARMORED DOORS & HATCHES ER09 1681/002-13 DECKHOUSE ST RUCT CLOSURES ER09 1701/001-13 MAST 7 KINGPOSTS CE01 1921/001-A9 COMPARTMENT TESTING ER01 2000/001-A2 MACHINERY LUBRICATING OIL EM01 EM02 EM04 2340/004-10 MAIN PROPULSION GAS TURBIN EM01 EM02 2400/011-10 XMSN & PROPULSOR SYSTEMS EM01 EM02 2411/015-10 PRPLN REDUCTION GEARS EM01 EM02 2421/002-C9 PROPULSION CLUTCH COUPLING EM01 EM02 2451/006-B9 PROPELLERS AN D PROPULSORS EM01 EM02 2513/007-A9 COMBUSTION AIR SYSTEM EM01 EM02 2521/051-B9 AUTO PROPULSION CTRL SYS EM03 2560/006-10 CRCLT AND COOLING SW SYS EA01 EM01 EM02

2591/001-10 UPTAKES AND BAFFLES EM01 EM02 2610/059-C9 FUEL SERVICE SYSTEM EM01 EM02 EM04 2620/011-10 MAIN PROPULSION L O SYSTEM EM01 EM02 EM03 2640/012-20 L O FILL XFR PURIFICATION EM01 EM02 EM03 3000/001-20 MISC SHIPBOARD ELECT EQUIP EE01 EM03

3001/002-30 MISC CONTROLLERS EE01 EM03 3002/001-30 MISC AC/DC MOTORS EE01 EM03 3113/004-C9 S/S GAS TURBINE GEN SET EM01 EM03 3131/005-10 BATTERY/SERV FACILITIES EE01 3140/R51-B9 POWER AND CONVERSION CF02 3201/002-30 POWER CABLES (CASUALTY) EE01 3241/051-30 SWITCHGEAR AN D PANELS CF02 EE01 EM03

Downloaded from https://www.everyspec.com

SECTION 1 1-62

Figure 1-19: Outstanding TFBR Status by Hull

Date: 01/02/00 Planned Maintenance System Page: 1 Time: 16:04:50 TFBR Status by Hull (PMS-22) FR: 1-00 Report Period 09/01/99-01/01/2000

Outstanding TFBR's for Naval Surface Force Pacific Ship ID: DDG-53

Date TFBRIL/XMTL ISEA Revised Doc Days Serial # Received Serial # Date Sent ISEA Responsible Due Date Revised Delinquent ________ ________ ___________ _________ ________________ ________ ___________ __________

001793 01/03/94 001-14-3113 01/04/94 NAVSSES 141B 02/14/94 190 002693 01/03/94 911X/S7107 01/03/94 NSWC/PHD 5B41 02/13/94 191 008393 01/12/94 02/09/94 195 008493 01/10/94 911X/S7124 01/10/94 NSWC/PHD 5B41 02/20/94 184 009194 01/26/94 02/23/94 181 0211-94 07/19/94 911X/S8055 07/19/94 NSWC/PHD 5B41 08/29/94 0 0212-94 08/02/94 911X/S8162 08/02/94 NSWC/PHD 5B41 09/12/94 0 0221-94 07/19/94 08/16/94 7

Total Outstanding TFBR's: 8

Completed TFBR's for Naval Surface Force Pacific

Date TFBRIL/XMTL Resolution Response Serial # Received Serial # Date Sent ISEA Responsible Letter Date ________ ________ ___________ _________ ________________________ ______________ __________

001893 01/03/94 001-14-3431 01/04/94 001993 01/03/94 002-14-3113 01/04/94 008693 01/11/94 911G/004 01/18/94 008793 01/11/94 911G/0008 01/18/94 008993 01/11/94 911G/0009 01/18/94 0120-94A 07/21/94 911X/S8101 07/21/94 NSWC/PHD 5B41 0214-94 07/19/94 911-518-74-3113 07/20/94 0225-94 08/08/94 032325/0244 08/10/94 0226-94 08/08/94 032311/0172 08/11/94 0227-94 08/08/94 032311/0171 08/11/94

Total Completed TFBR's: 10

E N D - O F - R E P O R T

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-63

Figure 1-20: Accountability Log Downloaded from https://www.everyspec.com

SECTION 1 1-64

Figure 1-21: PMS Change Documentation Routing Memorandum (Sample #1) Date

MEMORANDUM

From: 3-M System Coordinator To: Division Officer Via: Department 3-M Systems Assistant

Subj: FEEDBACK REPORT REPLY FORCE REVISION PACKAGE SPECIAL ISSUE NEW ITEMS 4790/2L REPLY

1. The following material has been received from the Fleet Technical Support Center:

Response Ltr Serial No. Date F.B. replies Serial No. Nomenclature Action taken:

2. Corrections, including those to MIP, LOEP and MRC, should be made immediately. Complete page 2 and return via the department 3-M Systems assistant as soon as all changes have been entered.

3. Action is/is not required by Work Center(s)

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-65

Figure 1-22: PMS Change Documentation Routing Memorandum (Sample #2)

P M S C H A N G E C H E C K - O F F S H E E T

From: Department ( ) (WORK CENTER) To: 3-M System Coordinator

Subj: CHANGE OR INSTALLATION OF PMS IAW REFERENCE (A) (Complete paragraphs 1 and 2) ACKNOWLEDGMENT OF THE REPLY OF REFERENCE (A) (Paragraphs 1 and 2 not required)

Ref: (a) Your memo of (DATE)

COMPLETED N/A 1. Department Level

a. Enter new LOEP in place of old one _______________ _______ b. Correct appropriate Maintenance Index Pages (MIP) _______________ _______ c. Change master MRC deck _______________ _______ d. Enter changes on cycle schedule _______________ _______ e. Enter changes on quarterly schedule _______________ _______

Date of changes

Completed or acknowledged by:

2. Work Center

a. Enter new LOEP in place of old one in W/C manual _______________ _______ b. Correct appropriate Maintenance Index Page (MIP) _______________ _______ c. Change MRC deck _______________ _______ d. Enter changes on weekly schedule _______________ _______

Signature of Department 3-M Systems Date of changes: ___________________________

Assistant ______________________________ Completed or acknowledged by:

____________________________________________

RETURN TO 3-M SYSTEM COORDINATOR NLT Downloaded from https://www.everyspec.com

SECTION 1 1-66 1-5.17 Change Service Accountability Log A Change Service Accountability Log (Figure 1-20) shall be maintained. Upon receipt of PMS changes, the 3-M System Coordinator shall maintain the identification number and other pertinent data in an accountability log prior to routing the documentation to the cognizant Work Center. After ensuring accountability, change documentation is passed to the applicable Work Center.

The 3-M System Coordinator completes the entry in the Change Service Accountability Log after the Work Center Supervisor has indicated that all appropriate change steps have been completed. After all work Centers have reported completion, the transmittal letter may be discarded. Change Service Accountability Log sheets should be retained for one year. 1-5.18 Documentation Provided TYCOMs via Force Revisions The following PMS documentation is provided by FTSCLANT/FTSCPAC to the TYCOMs with each force revision:

a. A complete record of all MIPs/MRCs for each hull.

b. List of Effective Pages (LOEP) PMS-5 for each ship (Figure 1-1).

c. Listing of Outstanding (Category B) TFBRs, Report PMS 22 (Figure 1-19).

NOTE:

Besides the standard shipboard reports, others are available upon request from FTSCLANT/FTSCPAC to assist the TYCOM. An example is the MIP to Hull File, Report PMS 2, which identifies each hull to which a given MIP is applicable within that TYCOM. Contact FTSCLANT/FTSCPAC for additional information on reports available. 1-6 EQUIPMENT NOT COVERED BY PMS There are items of equipment in the fleet which do not have PMS coverage. Reasons for this are numerous and include:

a. Insufficient funds for development of PMS.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-67 b. Non-delivery of technical documentation for equipment previously delivered and installed.

c. Absence of a system for identifying and assigning priorities to outstanding fleet PMS requirements.

d. Determination that planned maintenance is not required. 1-6.1 Classification of Equipment Not Covered by PMS The terms listed below have been established for use in PMS to aid in the classification of equipment or system status. SYSCOMs/BUMED, INSURV, and fleet units will be provided a status report of such equipment for use as a reference in determining the scope of PMS coverage and/or deficiencies in coverage.

a. Maintenance Requirement Substantiated (MRS). An equipment classified MRS has been analyzed by technical representatives of the cognizant SYSCOM/BUMED, and the need for PMS requirements established. A requirement then exists for final development, and the equipment is so identified for SYSCOM/BUMED action and is also listed in the PMS automated LOEP for each ship in which the equipment is installed.

b. No Maintenance Required (NMR). The term NMR can be assigned to equipment only if no maintenance other than normal housekeeping actions are required to keep the equipment in good operating condition. Technical review activities shall provide a RCM analysis to justify a NMR determination.

c. No Individual Requirement (NIR). NIR will be assigned to those equipments which do not require specific planned maintenance requirements of their own because the planned requirements for a higher assembly, of which the equipment is a part, satisfies the need. Technical review activities shall provide a RCM analysis to justify a NMR determination.

d. Lacks Adequate Technical Description (LATD). Items are so classified to reflect that insufficient descriptive information is available to determine PMS status.

1-6.2 Responsibilities for Providing Coverage When a ship or TYCOM considers there is a need for PMS equipment coverage, the following steps will be taken:

Downloaded from https://www.everyspec.com

SECTION 1 1-68 a. The ship will notify FTSCLANT/FTSCPAC by PMS FBR Category B of the need for maintenance requirements.

b. If through the development process planned maintenance tasks have been identified, FTSCLANT/FTSCPAC will forward preliminary MIPs and/or MRCs to the applicable ships for those items coded "MRS" (copy to TYCOM). The covering transmittal letter will include the status of final coverage and other comments considered appropriate.

c. If preliminary MIPs and/or MRCs are not provided, the command will develop interim MIP and MRC procedures based on applicable technical manuals/documentation and quality maintenance processes. MRC procedures will be locally developed and scheduled. These locally developed procedures shall be submitted to the SYSCOM/BUMED as recommendations for the development of formal PMS. No local procedures will be incorporated into PMS without RCM analysis developed and submitted by a technical review activity. TYCOMs will screen and, if applicable, approve locally prepared shore command generated planned maintenance. Shore stations locally generated planned maintenance will not be incorporated in PMS. 1-7 INACTIVE EQUIPMENT MAINTENANCE (IEM) 1-7.1 Implementation and Responsibility To implement procedures for the accomplishment of PMS for equipment declared in an inactive status, current PMS schedules are modified to annotate the requirements listed in the IEM section of the Maintenance Index Page (MIP) (Figure 1-22). For advance planning and scheduling of maintenance to take place, it is necessary to determine and identify the extent that ship's force personnel will apply PMS during an inactive period. MIPs in each Work Center will be reviewed to determine if equipment has IEM coverage, if the coverage is adequate, and what procedure to follow if there is no IEM coverage on the MIP in question. The Department Head is responsible for determining equipment IEM status. 1-7.2 Definition of Equipment Status The applicability of IEM procedures is dependent on determination of equipment status using the following definitions:

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-69 a. Status I. Equipment that will remain on board and will be inactive for thirty days or longer and is not scheduled for corrective maintenance or overhaul.

b. Status II. Equipment that is inactive for thirty days or longer and is directly subject to corrective maintenance, overhaul, or removal for safe storage/replacement. 1-7.3 Inactive Equipment Maintenance (IEM) Documentation IEM procedures are added to the end of existing MIPs and are separated from operational PMS by double horizontal lines (see Figure 1-22). The IEM procedures are titled "Inactive Equipment Maintenance" and are prefaced by the following statement:

"The following requirements will be scheduled when equipment is inactivated for periods of prolonged idleness."

Maintenance actions for inactivated equipment are grouped on the MIP under the following categories (see Figure 1-22):

a. Lay-Up Maintenance (LU)

b. Periodic Maintenance (PM)

c. Start-Up Maintenance (SU)

d. Operational Test (OT)

When no IEM requirements are justified during IEM analysis, no categories will be listed on the MIP and the words "None required" will appear under the Inactive Equipment Maintenance Section of the MIP. When there is no indication of IEM requirements, or when IEM procedures are inadequate, the ship should consider all factors that affect equipment deterioration and take necessary precautionary measures. These factors include environmental conditions, equipment location, susceptibility to damage, or other factors that can not be anticipated when IEM procedures are originally developed by the cognizant In-Service Engineering Agent (ISEA) or design activity. 1-7.3.1 IEM Operational Periodicity Codes. IEM utilizes operational periodicity codes for all IEM actions available on the MIP supplemented by IEM periodicity (LU, PM, SU, OT) for newly developed MRCs applicable to IEM only. Each periodicity code will be supported by an MRC in the applicable Downloaded from https://www.everyspec.com

SECTION 1 1-70 set unless indicated otherwise on the MIP. New MRCs are generated only when:

a. An IEM action is required that is not available in operational PMS.

b. A scheduling MRC is necessary because of the number of PMS actions required and complex scheduling notes pertaining to support factors must be considered. A note on the MIP will specify that this MRC is used for scheduling only (see Figure 1- 23). Scheduling MRCs are held to a minimum. 1-7.3.2 IEM Scheduling Situations. The following situations may occur in IEM and may apply to any of the following four categories:

a. If the maintenance required is available in operational PMS, it is repeated in IEM followed by a note specifying the MRC to be used (see Figure 1-23).

b. If the maintenance action required does not exist in operational PMS, a new MRC is developed and listed on the MIP using LU, PM, SU, or OT as the periodicity designator (see Figure 1-23).

c. If more than one maintenance requirement appears on the operational MRC, one or more of the requirements will be designated for accomplishment by a note on the MIP (see Figure 1-23).

d. If a scheduling MRC is developed it will list numerous MRC periodicities to be scheduled and performed (see Figure 1- 23).

Downloaded from https://www.everyspec.com

Figure 1-23: Maintenance Index Page Indicating IEM 1-35 NAVSEAINST 4790.8B Downloaded from https://www.everyspec.com

SECTION 1 1-72 1-7.4 Categories of IEM 1-7.4.1 Lay-Up Maintenance (LU) Lay-up maintenance actions prepare the equipment for periods of prolonged idleness, and are usually performed only once at the beginning of the inactive period.

1-7.4.2 Periodic Maintenance (PM)

Periodic maintenance actions are accomplished on a recurring basis during the inactive period to prevent equipment deterioration. These maintenance actions are operational PMS performed at either the same periodicity with a note specifying the MRC to be used (Figure 1-23), or at a different periodicity with a note specifying the MRC to be used and the modified periodicity (Figure 1-23).

1-7.4.3 Start-Up Maintenance (SU)

Start-up maintenance actions ensure that equipment is in a condition suitable for operation or to reactivate an equipment or system that has been inactivated for a prolonged period. Start-up maintenance consists of performing turn-on procedures and restoring the equipment to its ready-for-service condition (Figure 1-24).

1-7.4.4 Operational Test (OT)

Operational test actions are those conducted to determine the operational condition of the equipment, its ability to function as designed, and to be integrated with other equipment to form a system. 1-7.5 IEM MRCs IEM maintenance requirement cards are assigned SYSCOM MRC control numbers in the same manner as PMS MRCs. The SYSCOM MRC control number, periodicity indicator, skill level, and man- hours information, normally located adjacent to a maintenance requirement on the MIP, will not be repeated when an operational MRC is used for IEM.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-73

Figure 1-24: Start up MRC Downloaded from https://www.everyspec.com

SECTION 1 1-74 1-7.6 IEM SCHEDULING

At the conclusion of IEM, routine PMS maintenance requirements shall be scheduled as prescribed in Section I. SKED provides the capability to perform IEM scheduling.

NOTE:

Ships completing overhaul late in the quarter are not expected to do all planned maintenance scheduled during that quarter, but should do a certain amount based on the time remaining in the quarter.

The scheduling of maintenance for inactive equipment utilizes conventional PMS scheduling techniques.

Figure 1-25 is a sample quarterly schedule for an inactive period and portrays an equipment declared inactive in one maintenance quarter and returned to an operational status the following quarter. It also shows an item of equipment, which remained operational.

To schedule inactive equipment maintenance, determine the status of the equipment as described in paragraph 1-7.2 and prepare schedules as follows:

a. The cycle schedule will remain the same.

b. For paper users, on the quarterly schedule:

(1) Indicate vertically to designate the start of IEM. If only some of the items of the equipment are to be placed on inactive maintenance. The vertical line should be drawn only through the affected MIP line of the schedule for the inactive equipment maintenance (see Figure 1-25, item 1).

(2) At the beginning of IEM, to the left of the vertical line, list IEM Status I or II as appropriate (see Figure 1-25, item 1).

(3) Mark horizontally through all previously scheduled operational PMS requirements within the inactive period to signify cancellation (see Figure 1-25, item 2).

(4) From the IEM section of the MIP, schedule all lay-up and periodic requirements. Note the method of scheduling periodic maintenance of a different periodicity than that Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-75 specified on the MRC. Example: R-1(M) is a situation requirement extended to a monthly PMS requirement for IEM (see Figure 1-25, item 3).

(5) When the inactive period continues into the following quarter, operational PMS maintenance is not required to be scheduled until after the inactive period. Instead, inactive equipment maintenance requirements will be scheduled. When equipment remains in Status I or II through the beginning of a new quarter, indicate the status code in the first week on the appropriate line (see Figure 1-25, item 4).

(6) Schedule operational PMS requirements for those items of equipment not declared for inactive maintenance.

(7) Schedule the start-up requirements and, if required, operational tests toward the end of the inactive period (see Figure 1-25, item 5).

(8) At the end of the inactive period, mark vertically to indicate the stop of IEM and schedule operational PMS (see Figure 1-25, item 6). To avoid redundant scheduling when making the transition to operational PMS, do not reschedule those requirements already accomplished as part of the IEM actions.

(9) Identify the applicable external repair activity on the MIP line for equipment that is in overhaul and is considered an outside activity's responsibility (see Figure 1- 25, item 7).

(10) Mark horizontally through all previously scheduled IEM requirements to signify cancellation if the equipment has been removed from the ship and is no longer ship's force responsibility.

Downloaded from https://www.everyspec.com

SECTION 1 1-76

Figure 1-25: Sample IEM Schedule Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-77 1-8 SUPPLY MATERIALS REQUIRED PRIOR TO INACTIVATION Certain advance preparations are necessary to properly prepare for IEM. Reference documents such as Current Ship's Maintenance Project (CSMP), Ship Alteration and Repair Package (SARP), LOEPs, MIPs, and MRCs should be reviewed by the shipboard maintenance manager well in advance of planned idle period. A comprehensive list of the needed equipment and materials required may be prepared by reviewing the IEM MRCs for the items called out under "Tools, Parts, Materials, Test Equipment."

Meeting IEM requirements in some cases will require that portable equipment such as exhaust blowers, heaters, and dehumidifiers are available. In other situations, special materials for protecting idle ship equipment must be used. Many items required in implementing IEM are normally used or stocked on the ship and are, therefore, readily available. Lubricants, cleaning agents, rags, hand tools, and test equipment are typical among these items.

Arrangements for loan and extended use of portable equipment during an overhaul period should be made with a tender or other repair/overhauling activity. In assessing equipment requirements, duplication of effort and equipment redundancy should be avoided. For instance, a particular overhaul action under shipyard responsibility may include provision of equipment, material, or services, otherwise assumed to be part of IEM requirements. In such cases, yard and ship responsibility must be determined.

Care must be exercised in the selection of cleaning agents, detergents, solvents, adhesives, cements, and similar materials to avoid the use of materials which, are not authorized. For example, on submarines, refer to the effective edition of the Material List for Operating Submarines and to NAVSHIPS 0938-LP-011-5010, Technical Manual, Nuclear Powered Submarine Atmosphere Control (CONF).

Downloaded from https://www.everyspec.com

MAINTENANCE AND MATERIAL MANAGEMENT (3-M) MANUAL

SECTION I

Chapter 2

INITIAL PLANNED MAINTENANCE SYSTEM INSTALLATION AND UPDATE DURING OVERHAUL

Downloaded from https://www.everyspec.com

SECTION I 2-i SECTION I

Chapter 2

REFERENCES

REFERENCE INSTRUCTION NO. SUBJECT

None. No instructions referenced in Chapter 2.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

2-ii

SECTION I

Chapter 2

INITIAL PLANNED MAINTENANCE SYSTEM INSTALLATION AND UPDATE DURING OVERHAUL TABLE OF CONTENTS

Paragraph Title Page

2-1 PLANNED MAINTENANCE SYSTEM (PMS) INSTALLATION (SHIPBOARD).2-1 2-1.1 Preparation of Materials................................2-1 2-1.2 PMS Installation........................................2-1 2-1.2.1 Preliminary PMS Installation..........................2-2 2-1.2.2 Final PMS Installation................................2-2 2-1.2.3 Installation Briefings................................2-2 2-1.3 Inventory of PMS Installation Package...................2-3 2-1.3.1 Inventory of Preliminary PMS Package..................2-3 2-1.3.2 Inventory of Final PMS Package........................2-3 2-1.4 PMS Package Installation Completion Check List..........2-3 2-2 UPDATE OF SHIPBOARD PMS PACKAGE DURING OVERHAUL PERIOD....2-4 2-3 SCHOOLS/TRAINING COMMANDS.................................2-5

LIST OF FIGURES

Figure

Title Page Figure 2-1: PMS Documentation Support During Overhaul .......2-6

Downloaded from https://www.everyspec.com

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

2-1 CHAPTER 2

INITIAL PLANNED MAINTENANCE SYSTEM INSTALLATION AND UPDATE DURING OVERHAUL

2-1 PLANNED MAINTENANCE SYSTEM (PMS) INSTALLATION (SHIPBOARD) Type commanders (TYCOMs) are responsible for ensuring the proper installation and operation of PMS within the ships under their command. The importance of the PMS installation cannot be overemphasized. 2-1.1 Preparation of Materials Prior to the PMS installation, equipment configuration information will be verified by the Configuration Data Manager (CDM). The PMS Maintenance Index Page/Maintenance Requirement Card (MIP/MRC) documentation will be certified by the Fleet Technical Support Center, Atlantic/Fleet Technical Support Center, Pacific (FTSCLANT/FTSCPAC), as appropriate. Following the validation, the applicable FTSCLANT/FTSCPAC will assemble the PMS documentation, equipment listings, schedules, and forms required for the installation package. Each PMS installation package is ship tailored. Installation packages consist of:

a. A transmittal letter with an inventory of installation materials.

b. Two copies of the List of Effective Pages (LOEP).

c. One PMS Master File. The PMS Master File contains information relative to PMS requirements for specific equipment for which the command is responsible.

d. One Work Center PMS Manual for each work center. The Work Center PMS Manual reflects that portion of the PMS Master File that contains only the planned maintenance requirements applicable to a particular work center and includes decks of associated MRCs and PMS Feedback Report (FBR) forms.

e. A PMS delivery/installation reporting card.

2-1.2 PMS Installation The FTSCLANT/FTSCPAC have the responsibility for installing PMS aboard ship. The installation of PMS is done in two phases; preliminary and final. Downloaded from https://www.everyspec.com

SECTION I 2-2 2-1.2.1 Preliminary PMS Installation A preliminary, time phased PMS package, tailored to the ships manning and compartment acceptance plan will be built and installed as the ship construction continues. Close coordination between the Supervisor of Shipbuilding (SUPSHIP), FTSCLANT/FTSCPAC, and the ship, monitored by TYCOM, will continue through final PMS installation. Periodicities of PMS may be altered to accommodate manning phases. The goal is to bridge the gap between acceptance of a space and PMS installation, minimizing damage to equipment/systems during this transition period. 2-1.2.2 Final PMS Installation A final formal ship-wide PMS installation, which represents the full PMS package installation will correspond with the ships commissioning plan. The FTSCLANT/FTSCPAC will notify the ship via the telephone giving a proposed final PMS installation date, the names and security clearances of team members, and a brief resume of the procedures. The following provides a general time frame for installations:

a. Submarines and nuclear powered surface ships. Approximately 2 weeks prior to placing the ship IN SERVICE. (This also applies to other submersible vehicles.)

b. Surface Ships. Approximately 2 weeks prior to commissioning for all non-nuclear-powered ships.

c. A briefing will be conducted by FTSCLANT/FTSCPAC during the PMS installation and repeated during the final installation process. A TYCOM representative will be present at these briefings. 2-1.2.3 Installation Briefings a. The Top Management Level Briefing. The installation team leader will conduct this briefing for the benefit of the Commanding Officer, Executive Officer, 3-M System Coordinator, and Department Heads. The purpose of the briefing will be to provide refresher training in the concept and management aspects of PMS. The briefing will be scheduled once the majority of Department Heads are aboard the pre-commissioning unit in accordance with the ship's commissioning plan.

b. Briefing for personnel below Department Head level. The installation team will conduct the Division Officer and Work Center level briefing. This briefing will consist of PMS Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

2-3 concepts and detailed procedures directed to the working level. It will be held once the majority of Division Officers and Work Center Supervisors have reported aboard. Additional briefings will be conducted by TYCOM as required during initial preliminary periods.

c. FTSCLANT/FTSCPAC will brief the 3M Coordinator during the formal full PMS package installation. 2-1.3 Inventory of PMS Installation Package 2-1.3.1 Inventory of Preliminary PMS Package The FTSCLANT/FTSCPAC will provide a copy of the latest PMS package appropriate for the class ship on CD-ROM. The ship will monitor the pre-commissioning space acceptance progress and inventory equipment associated with spaces to be accepted. The ship will use the PMS package to identify applicable PMS and will coordinate with FTSCLANT/FTSCPAC to acquire applicable PMS documentation for those equipment/systems under ship's force control. FTSCLANT/FTSCPAC will assist the ship if PMS cannot be identified for a system to be accepted. It is the ship's responsibility to validate the PMS for their hull. 2-1.3.2 Inventory of Final PMS Package Final PMS Package. The PMS installation team, in conjunction with ship personnel, shall conduct an inventory of the installation package received from FTSCLANT/FTSCPAC. This will be done to ensure the package contains all materials necessary for the PMS installation. The installation team will compile a list of all deficiencies and discrepancies. The installation team will forward this list directly to the FTSCLANT/FTSCPAC as appropriate for immediate corrective action. 2-1.4 PMS Package Installation Completion Check List During the preliminary PMS package build, the installing activity will develop a check list to use during the PMS installation. This check list will be used to ensure that:

a. All PMS Work Center Supervisors are instructed in using the Automated Scheduling Program on how to do their PMS schedules and instructed in the preparation of Equipment Guide Lists (EGLs).

b. Supply personnel are familiar with the Standard PMS Item Name (SPIN), Standard PMS Material Identification Guide Downloaded from https://www.everyspec.com

SECTION I 2-4 (SPMIG) and other responsibilities in support of Ship's 3-M Systems.

c. The 3-M Coordinator, Division Officers, CPOs, and LPOs that can access Local Area Network (LAN) and the Internet from their work stations demonstrate the ability to connect to the RAD WEB, CDMD-OA and on-line 3-M Manual as required.

d. An adequate number of the Ships' 3-M Manual, OPNAV 4790 forms, and TYCOM 3-M Systems instructions are available on board. 2-2 UPDATE OF SHIPBOARD PMS PACKAGE DURING OVERHAUL PERIOD The following procedures establish the general guidelines within which the FTSCLANT/FTSCPAC, overhaul activity, TYCOM, and ship will function to ensure that an adequate and accurate PMS update is accomplished prior to completion of a regular overhaul or any lengthy availability:

a. Three months prior to the start of overhaul (SOH) the responsible Integrated Logistics Overhaul (ILO) activity will initiate a letter of request to FTSCLANT/FTSCPAC as appropriate for a PMS update package. (When the availability/overhaul date is not known 90 days prior to SOH, the request will be made as soon as possible.) Thirty days prior to SOH and after receipt of the ILO request, the FTSCLANT/FTSCPAC will provide the following: PMS 4 (MIP to Work Center Lists), PMS 5 (List of Effective Pages (LOEP)), and one set of all updated MIPs and unclassified MRCs.

b. The ILO activity in conjunction with ship's force shall verify the PMS 4 and 5 listings with on board equipment configuration, and identify adds, changes, and deletes per Fleet ILO Activity Procedure Manual, Volume 8 (Planned Maintenance System Procedures). The total update package (Annotated PMS 5 (LOEP) and LOEP update list) shall be sent to FTSCLANT/FTSCPAC and the ship periodically during overhaul, but definitely by the end of the overhaul. This will allow the ship to begin PMS coverage prior to receipt of the Force Revision. Data submitted will be incorporated into the next Force Revision (FR). Items lacking PMS coverage but needing planned maintenance shall be added to the Maintenance Requirements Substantiated (MRS) listing.

c. When tasked and funded, the FTSCLANT/FTSCPAC shall coordinate the development of PMS requirements for MRS items.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

2-5 d. The appropriate FTSCLANT/FTSCPAC shall provide the updated PMS documentation directly to the ILO activity, and the ship via the normal force revision (FR) cycle until the end of overhaul, at which time only the ship will continue to receive PMS documentation via FR updates.

e. The PMS update process cycle for overhaul periods is shown in Figure 2-1. 2-3 SCHOOLS/TRAINING COMMANDS Installation teams are not provided to training commands and schools for installing or updating PMS as is provided to fleet units. Sufficient training, however, is available on both the east and west coasts to assist the training activities in readying staff and instructor personnel for the receipt, distribution of materials, and the execution of the PMS program in the individual commands. These training courses are delineated in Section IV, Chapter 1.

The schools/training commands are responsible for the same functions specified for shipboard PMS installation and updates. Following receipt of a PMS package or Force Revision (FR) update from FTSCLANT/FTSCPAC, implementation of new and updated PMS documentation shall be accomplished using existing procedures for both PMS installation and shipboard updates as described in chapter 1 of this section. Downloaded from https://www.everyspec.com

SECTION I 2-6

Figure 2-1: PMS Documentation Support During Overhaul

FTSC'S FILE * WHEN TASKED AND FUNDED: - REVIEW AND VERIFY PMS DOC BASED UPON CONFIG DATA - COORDINATE PMS DEVELOPMENT OF MRS ITEMS - DEVELOP PMS MRS ITEMS * DISTRIBUTE PMS DOCUMENTATION TO SHOP AND ILO SHIP * SHIPS PMS SUPPORTED BY FR IAW OPNAVINST 4790.4C CONFIGURATION CHANGE DATA FROM OTHER SOURCES: SLCC, OPNAV 4790/CK, 180/360 DAY LETTER, COP * SUMMARY LIST OF COMPONENT CHANGES (SLCC) * SHIP CONFIGURATION CHANGE OPNAV 4790/CK * NAVSEASYSCOM 180/360 DAY LETTER * COSAL OVERHAUL PLANNING (COP) DOCUMENTATION FTSC'S * PROVIDE ILO SITES WITH PMS-9, PMS-10, CERTIFICATION FILES AND SEMIANNUAL UPDATES FTSC'S * PMS-9 HULL/MECH/ELEC CERTIFICATION FILE * PMS-10 ELECTRONICS CERTIFICATION FILE * PMS-11 WEAPON CERTIFICATION FILE ILO * INTEGRATED LOGISTICS OVERHAUL (ILO) * LIAISON BETWEEN THE SHIP AND FTSC'S ILO * INITIATE LETTER TO RESPECTIVE FTSC'S TO PROVIDE PMS DOCUMENTATION FOR SHIPS IN OVERHAUL UNDER THEIR COGNIZANCE. LETTER SHALL BE NLT 90 DAYS PRIOR TO START OF SHIP'S OVERHAUL. FTSC'S * PMS SHIP MASTER FILE * PMS COMMODITY SPECIALIST * PMS DOCUMENTATION AND DISTRIBUTION FTSC'S * IAW LETTER FROM RESPECTIVE ILO PROVIDE VIA LTR - UPDATED LOEP (PMS-5) - UPDATED PMS-4 - APROPRIATE MIPs & MRCs * FORWARD PACKAGE TO RESPECTIVE ILO 60 DAYS FROM RECEIPT OF THE ILO LTR ILO/SHIP DEPOT AVAILABILITY SITE ILO/SHIP * VERIFY PMS-4, PMS-5 WITH ON BOARD EQUIPMENT - IDENTIFY ALL ADDS, CHANGES, DELETES IAW COMNAVSEASYSCOM POLICY AND PROCEDURES MANUAL VOL IV (PMS PROCEDURES FOR ILO) - SEND PMS UPDATE PACKAGE (ANNOTATED LOEP AND LOEP UPDATE LIST) TO APPROPRIATE FTSC'S PERIODICALLY DURING OVERHAUL. DATA SUBMITTED TO FTSC'S WILL BE INCORPORATED INTO THE NEXT FR. FTSC'S * VERIFY APPLICABLE PMS * COORDINATE PMS DEVELOPMENT * DISTRIBUTE PMS DATA * DEVELOP/REVISE PMS FTSC'S * REVIEW AND VERIFY APPLICABLE PMS DOCUMENTATION BASED UPON CONFIGURATION DATA - DATA NOT SUPPORTED IN CERTIFICATION FILES FORWARDED TO RESPECTIVE COGNIZANT TECHNICAL CODE - UPDATE SHIP MASTER FILE _ VERIFY MIP/MRC FROM PMS DOC - PROCESS PMS DOCUMENTATION DETERMINED BY COG TECH CODE * DISTRIBUTE PMS DOCUMENTATION TO SHIP AND ILO (OVERHAUL PERIODS VARY) END OF OVERHAUL (SHIP OPERATIONAL CYCLE) CURRENTLY ONGOING 3 MO PRIOR TO SOH 1 MO PRIOR TO SOH START OF OVERHAUL Downloaded from https://www.everyspec.com

MAINTENANCE AND MATERIAL MANAGEMENT (3-M) MANUAL

SECTION I

Chapter 3

ORGANIZATIONAL LEVEL MAINTENANCE DATA SYSTEM INTERFACE

Downloaded from https://www.everyspec.com

SECTION I 3-i SECTION I

Chapter 3

REFERENCES

REFERENCE INSTRUCTION NO. SUBJECT

(a) SPCCINST 4441.170A COSAL USE AND MAINTENANCE MANUAL

(b) NAVSEA TECHNICAL SPECIFICATION 9090-700 Series SHIPS CONFIGURATION AND LOGISTICS SUPPORT INFORMATION SYSTEM (SCLSIS)

(c) NAVSEA TECHNICAL SPECIFICATION 9090-310 Series ALTERATIONS TO SHIPS ACCOMPLISHED BY ALTERATION INSTALLATION TEAMS

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 3-ii

SECTION I

Chapter 3

ORGANIZATIONAL LEVEL MAINTENANCE DATA SYSTEM INTERFACE TABLE OF CONTENTS

Paragraph Title Page

3-1 PURPOSE...................................................3-1 3-2 SCOPE.....................................................3-1 3-3 OBJECTIVE.................................................3-1 3-4 3-M ORGANIZATIONAL (O) LEVEL MAINTENANCE DATA SYSTEM......3-2 3-4.1 Central Shore Databases.................................3-2 3-4.1.1 Maintenance Data......................................3-3 3-4.1.2 Configuration and Logistics Data......................3-3 3-4.2 Ship Configuration and Logistics Support Information System (SCLSIS)................................................3-3 3-4.2.1 Shipboard Benefits of SCLSIS..........................3-4 3-4.2.2 Ship Responsibility...................................3-4 3-4.2.3 Certification of Shipyard Installed Alterations.......3-5 3-4.3 3-M Reporting Requirements..............................3-6 3-4.3.1 Reporting Methods.....................................3-6 3-4.3.1.1 Data Elements.......................................3-7 3-4.4 Work Candidate/Job Sequence Number (JSN) Log............3-7 3-4.5 Deferred Maintenance Action.............................3-7 3-4.6 Completed Maintenance Actions...........................3-8 3-4.7 Reporting a Completed Maintenance Action that was Related to an Alteration, or Resulted in a Configuration Change3-11 3-4.8 Documenting a Periodic Maintenance Requirement (PMR)...3-12 3-4.9 Configuration File Correction..........................3-13 Downloaded from https://www.everyspec.com

SECTION I 3-iii 3-4.10 Documenting Changes, Additions, or Deletions to previously reported maintenance actions .......................... 3-14 3-5 SELECTED LEVEL REPORTING (SLR) .......................... 3-14 3-5.1 Selected Equipment Indicator (SEI) .................... 3-14 3-5.2 Selected Level Reporting Categories ................... 3-15 3-5.3 Level 3 Specialized Reporting Template ................ 3-16 3-5.4 SLR Nominations/Deletions/Changes ..................... 3-17 3-5.5 SLR Data Analysis ..................................... 3-18 3-5.6 SLR Record Identification in CDMD-OA .................. 3-18 3-5.7 Three-year Limitation ................................. 3-18 3-5.8 Semiannual Update ..................................... 3-19 3-6 SCREENING AND SUBMISSION PROCESS ........................ 3-19 3-6.1 Transaction and Error Report .......................... 3-19 3-7 CURRENT SHIP'S MAINTENANCE PROJECT (CSMP) ............... 3-19 3-7.1 CSMP Aboard Ship ...................................... 3-20 3-7.2 CSMP Use by Outside Activities ........................ 3-21 3-7.3 Automated CSMP Reports ................................ 3-21 3-7.3.1 CSMP Summary Reports ................................ 3-23 3-7.3.2 CSMP Detailed Reports ............................... 3-24 3-8 Shipboard Assessment of MDS Performance ................. 3-24

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 3-iv SECTION I

Chapter 3

ORGANIZATIONAL LEVEL MAINTENANCE DATA SYSTEM INTERFACE LIST OF FIGURES

Figure Title Page

Figure 3-1: Work Candidate/Job Sequence Number (JSN) Log ...3-10 Figure 3-2: Letter Transmittal from Non-automated Activities .....................................3-22 Figure 3-3: Certification of Alteration Installation (Sample Letter) ........................................3-26 Figure 3-4: 1st Endorsement to Alteration Certification Letter .........................................3-27

Downloaded from https://www.everyspec.com

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B 3-1 CHAPTER 3

ORGANIZATIONAL LEVEL MAINTENANCE DATA SYSTEM INTERFACE

3-1 PURPOSE The purpose of this chapter is to provide the 3-M Program’s Maintenance Data System (MDS) policy and guidelines in support of organizational (O) level shipboard maintenance and material reporting. MDS provides the maintenance and material managers throughout the Navy with the means to plan, acquire, organize, direct, control, and evaluate manpower and material resources expended or planned for expenditure in support of maintenance. It allows for information collected by maintenance personnel to be recorded only once, and the maintenance database thereafter will provide information to all who have a need for it. 3-2 SCOPE This chapter specifies and standardizes the requirements for O- level MDS reporting. It requires the reporting of maintenance actions and configuration changes on all categories of equipment. Maintenance data collection or reporting requirements, not specified in this manual, will not be levied on fleet units by the shore establishment without prior approval of the Chief of Naval Operations (N43). 3-3 OBJECTIVE 3-M Organizational Level Maintenance provides a means to effectively manage and control organizational maintenance. It is primarily managed via the Current Ship's Maintenance Project (CSMP). A thorough and accurate CSMP reflects the material condition of the ship. This objective is achieved by:

a. Reporting maintenance actions.

b. Reporting configuration changes.

c. Producing Current Ship's Maintenance Project (CSMP) reports.

d. Producing work requests/work candidate.

e. Producing deficiency documents for use by the Board of Inspection and Survey (INSURV).

Downloaded from https://www.everyspec.com

SECTION II 1-i SECTION II

CHAPTER 1

REFERENCES

REFERENCE INSTRUCTION NO. SUBJECT

(a) OPNAVINST 4730.5 SERIES TRIALS AND MATERIAL INSPECTIONS (MI) OF SHIPS CONDUCTED BY THE BOARD OF INSPECTION AND SURVEY (b) SECNAVINST 5040.3 SERIES INSPECTIONS WITHIN THE DEPARTMENT OF THE NAVY (c) CINCLANTFLT/CINCPACFLT INST 4790.3 SERIES JOINT FLEET MAINTENANCE MANUAL

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-ii

SECTION II CHAPTER 1 INSURV INSPECTION PROCEDURES TABLE OF CONTENTS

Paragraph Title Page

1-1 PURPOSE...................................................1-1 1-2 INSURV MISSION............................................1-1 1-3 INSURV DOCUMENTATION PROCEDURES...........................1-1 1-4 PROCEDURES BEFORE INSURV INSPECTION.......................1-2 1-4.1 Ship Responsibilities...................................1-2 1-4.2 Intermediate Unit Commander (IUC)/Immediate Superior in Command (ISIC)..........................................1-2 1-4.3 Deficiencies to be Reported.............................1-2 1-5 PROCEDURES DURING INSURV INSPECTION.......................1-2 1-6 INSURV NUMBERING PROCEDURES...............................1-3 1-6.1 INSURV Assigned Numbers (Blocks 19-24)..................1-3 1-6.1.1 Starred Cards (Block 19)..............................1-3 1-6.1.2 INSURV Identification Number (BLOCK 20)...............1-4 1-6.1.3 SUFFIX (BLOCK 21).....................................1-6 1-6.1.4 MISSION DEGRADE (BLOCK 22)............................1-7 1-6.1.5 SAFETY (BLOCK 22).....................................1-7 1-6.1.6 RELIABILITY/MAINTAINABILITY (Block 24)...............1-7 1-7 PROCEDURES AFTER INSURV INSPECTION........................1-7

Downloaded from https://www.everyspec.com

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-1 SECTION II CHAPTER 1 INSURV INSPECTION PROCEDURES

1-1 PURPOSE

This chapter describes the Maintenance and Material Management (3-M) related actions required prior to, during, and following an inspection conducted by the Board of Inspection and Survey (INSURV). 1-2 INSURV MISSION

The Board of Inspection and Survey (INSURV) was established by Congress as a board to advise the Secretary of the Navy regarding acceptance of newly constructed ships and to periodically examine naval vessels and make recommendations to the Secretary if any should be stricken from the Naval Vessel Register. Per references (a) and (b), INSURV has been tasked with added specific functions including the following:

a. determining vessels fitness for further service, b. identifying material conditions that limit performance, compiling statistical information, and d. providing assurance to higher authority that mechanisms to identify, document and resolve material deficiencies are adequate and that these systems are being judiciously executed.

The examination of naval vessels is conducted as a Material Inspection (MI), which consists of operational tests or demonstrations of major systems and equipment. The formative basis for the MI is a command’s own self-awareness to its material condition and readiness. It is therefore incumbent upon each command being inspected to demonstrate a thorough knowledge of its material condition through accurate records and operational demonstrations. 1-3 INSURV DOCUMENTATION PROCEDURES

The INSURV Board prepares material deficiency documents to record conditions found during the inspection. These inspection deficiency items will be written on OPNAV/2Ks to be reviewed and later input into the Maintenance Data System. At approximately six (6) weeks prior to the scheduled MI and to aid in inspection preparation, ship’s force should review the preparation guidelines available at INSURV’s homepage Downloaded from https://www.everyspec.com

SECTION II 1-2 http://www.spawar.navy.mil/fleet/insurv/. The ship being inspected will prepare material deficiency documents as directed within reference (c). It is especially noteworthy that at the INSURV website are details regarding recent material problem areas and trends. Ship’s force should routinely take advantage of this information to learn and correct material problems/trends that are being discovered elsewhere. 1-4 PROCEDURES BEFORE INSURV INSPECTION 1-4.1 Ship Responsibilities The specific actions of the Commanding Officer and ship’s force are noted in reference (c). The INSURV inspection provides an opportunity for the ship to demonstrate a high material self- awareness as reflected in accurate documentation of it’s deficient conditions (CSMP, CASREPs). The ship’s 3-M Coordinator along with Work Center Supervisors should routinely be reviewing work candidates that are old, appear duplicated or have repairs completed to ensure they are appropriately removed from the CSMP. Additionally, standard equipment operating procedures are expected to be current and easily executed when called upon by board members. 1-4.2 Intermediate Unit Commander (IUC)/Immediate Superior in Command (ISIC) Specific actions are denoted within reference (c). The IUC/ISIC shall pay particular attention to ensuring that the mechanisms to identify, document and correct material deficiencies identified by ship’s force or others are accurately reflected within the CSMP. Additionally, the IUC/ISIC should ensure that deficiencies are being continuously prosecuted and adjudicated with the appropriate priority and assignment. 1-4.3 Deficiencies to be Reported Per reference (c), the CSMP is “the sole source of work to be accomplished by industrial activities, FMA’s, and organizational level activities” and therefore should reflect the deficient material items requiring maintenance action. Reference (c) outlines expected items to be noted within the CSMP. 1-5 PROCEDURES DURING INSURV INSPECTION

Documentation of INSURV inspection deficiencies will be accomplished in accordance with reference (c).

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-3 1-6 INSURV NUMBERING PROCEDURES INSURV will assign numbers to applicable deficiencies identified during inspection. The following paragraphs describe the input to the appropriate BLOCK NUMBERS of the OPNAV 4790/2K numbering system. 1-6.1 INSURV Assigned Numbers (Blocks 19-24) The INSURV number is assigned to each deficiency identified during an inspection or trial to:

a. Uniquely identify a deficiency; b. Indicate the relative importance of a deficiency; c. Identify special classes of deficiencies; and d. Specify required time of correction by "starring" deficiencies (Acceptance Trials only).

* 1 K 0 0 1 H B BLOCK NR: 19 20 21/22/23/24

1-6.1.1 Starred Cards (Block 19) Asterisks (stars) designate a completion requirement and are used on Acceptance Trials (AT), Underway Trials (UT), Combined Trials (CT), and Guarantee Material Inspections (GMI). 1-6.1.1.1 Single Starred Deficiencies: (*) A deficiency which, in INSURV's judgment, requires resolution or waiver by the CNO before the ship is delivered to the Navy and which:

(a) Significantly degrades a ship's ability to perform an assigned primary or secondary Required Operational Capability (ROC);

(b) Prevents the crew from safely operating or maintaining ship systems;

(c) Prevents the crew from safely living or messing on board;

(d) Precludes safe navigation, effective damage control or fire fighting operations, or adequate physical security; or

Downloaded from https://www.everyspec.com

SECTION II 1-4 (e) Prevents the ship from complying with environmental or NAVOSH regulations. 1-6.1.1.2 Double Starred Deficiencies: (**) A deficiency applicable only to ships constructed, converted, or modernized with a separate fitting-out period assigned away from the building site, and represent a deficiency which, in INSURV's judgement, requires resolution or waiver by the CNO prior to the ship's departure from the building yard. 1-6.1.2 INSURV Identification Number (BLOCK 20). The seven spaces of this block are filled in as follows:

1 K 0 0 1 H B 1 2 3 4 5 6 7 1-6.1.2.1 Importance (Space One) A numeral located in Space One indicates the relative importance of the deficiency. This is called the "PART" number and the number can be either PART 1, 2, or 3. 1-6.1.2.1.1 PART 1 PART 1 deficiencies are those that in INSURV’s judgment are likely to:

- Cause the ship to be unseaworthy, or

- Substantially reduce the effectiveness of personnel or essential material, or

- Reduce the ability of the ship to carry out its assigned mission or to perform in a primary mission area, or

- Cause injury to personnel or damage to vital material. This includes significant deficiencies to the ship's safety equipment and devices. 1-6.1.2.1.2 PART 2 PART 2 deficiencies are those that in INSURV’s judgment are less important and do not meet the criteria for a PART 1 deficiency, but should be corrected to restore the ship to required specifications.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-5 1-6.1.2.1.3 PART 3 PART 3 deficiencies are those that in INSURV’s judgment will require either a major alteration to correct (design related) or modifications that are too costly to effect during the life cycle of the ship (i.e., passageway too narrow, overhead too low, insufficient equipment). These are documented to identify design changes required on future ships. These deficiencies are generally coded “9( in BLOCK 45 (TYCOM SCREENING) and passed to machinery history files. The deficiency will appear on the INSURV deficiency list. PART 3 deficiencies may include:

- Items beyond current technical authority but which should be corrected in future ship designs, or

- Items not in compliance with current technical authority but may be impractical and/or too costly to correct on the ship inspected, or

- A recommended alteration or addition that would be beneficial but for which there is no written requirement or reference. Such a deficiency will also be designated “A” for “alteration” in space 2 as explained in the next section, or

- Information used by INSURV for statistical analysis or documentation purposes. 1-6.1.2.2 Responsibility (Space Two) The single capital letter "K", "G," or "A" is used to indicate responsibility for corrective action. This space should normally be left blank, and the designations “K” or “G” are used by INSURV on new construction trials and may be later modified by Program Managers and/or Supervisors of Shipbuilding based on review of construction contracts. The following definitions apply to “A”, “K” and “G” designations:

- "K" indicates that, in the reviewer's opinion, correction of the deficiency is the responsibility of the contractor because he or his subcontractors or vendors failed to meet the requirements of the contract.

- "G" indicates that in the reviewer’s opinion correction of the deficiency is the responsibility of the government.

- "A" designates an "Alteration Card" which requires a design action or configuration change not authorized or not yet accomplished on the ship inspected. This may include applicable Downloaded from https://www.everyspec.com

SECTION II 1-6 SHIPALTs, ORDALTs, MACHALTs, Field Changes, or other configuration changes that are not complete or not scheduled for this hull, recommended alterations not previously documented, and/or changes which require design action by NAVSEA. Alteration Cards should include recommendations for how correction can be accomplished either by referencing a previously engineered alteration or by detailing possible corrective action in the remarks section. A PART 3 Alteration Card (“3A”) indicates a change that might contribute to the ship, but because of the ship’s age or other consideration is unlikely to be accomplished or is low priority. A PART 3 Alteration Card (“3A”) could indicate an area where an older ship does not comply with current specification, standards or instructions, but that the effort to engineer and install the required changes are unlikely due to cost or other factors. INSURV expects that a “3A” deficiency will be passed to history without action on the ship being inspected. 1-6.1.2.3 Sequential Number (Space 3, 4, and 5) This is a sequential number or alphanumeric assigned to each deficiency by INSURV which, along with the department code, uniquely identifies each deficiency. 1-6.1.2.4 Department (Space 6 and 7) A combination of two capital letters is used to identify the INSURV department having primary cognizance as follows:

DEPARTMENT SYMBOL DEPARTMENT SYMBOL

ASW AS INFORMATION SYSTEMS IS AVIATION AV MEDICAL/DENTAL MD AUXILIARIES AX MINE COUNTERMEASURES MN BOILERS BR MAIN PROPULSION MP COMM, COMMAND & CONTROL CC NAVIGATION NV DAMAGE CONTROL DC OCCUPATIONAL SAFETY OH DECK DK OPERATIONS OP DIVING DV REPAIR RP ELECTRICAL EL REACTORS RX ENVIRONMENTAL PROTECTION EP SUPPLY SP HABITABILITY HP WEAPONS WP

1-6.1.3 SUFFIX (BLOCK 21) In special cases, a one letter Suffix is included after the INSURV number to further identify subsets of an INSURV item. Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

1-7 1-6.1.4 MISSION DEGRADE (BLOCK 22) This block identifies certain PART 1 deficiencies that are considered as preventing the ship from carrying out some part of its mission, and is filled in with "U" when applicable. 1-6.1.5 SAFETY (BLOCK 23) The suffix "S" is added to indicate that this deficiency is identified as a safety hazard. 1-6.1.6 RELIABILITY/MAINTAINABILITY (Block 24) The suffixes “R” and “M” are added by INSURV to indicate:

- “R” is assigned to deficiencies related to an equipment or component that displays low reliability requiring frequent corrective maintenance or replacement.

- “M” is assigned to indicate that the equipment or component requires excessive maintenance, that the deficiency is related to the Planned Maintenance System (PMS), or that the deficiency represents a problem with Integrated Logistics Support. 1-7 PROCEDURES AFTER INSURV INSPECTION Post INSURV action items are outlined in reference (c). Due to its importance, note the action to appropriately CASREP applicable “PART 1” deficiencies. A “PART 1” deficiency is an important deficiency that is likely to:

a. cause the ship to be unseaworthy, b. substantially reduce the ability of the ship to carry out an assigned mission, c. substantially reduce the effectiveness of personnel or essential material, and/or d. cause serious injury to personnel or serious damage to important material.

This includes significant deficiencies to the ship’s safety equipment and devices.

As noted in reference (c), INSURV and the TYCOM will work collaboratively to input inspection deficiencies into the CSMP within 30 days of MI completion.

Downloaded from https://www.everyspec.com

MAINTENANCE AND MATERIAL MANAGEMENT (3-M) MANUAL

SECTION II

CHAPTER 2

ASSIST VISITS AND TYCOM ASSESSMENTS

Downloaded from https://www.everyspec.com

SECTION II 2-i SECTION II CHAPTER 2

REFERENCES

REFERENCE INSTRUCTION NO. SUBJECT

(a) CINCLANTFLT/CINCPACFLT INST 4790.3 SERIES CINCLANTFLT/CINCPACFLT JOINT FLEET MAINTENANCE MANUAL Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

2-ii SECTION II CHAPTER 2

ASSIST VISITS AND TYCOM ASSESSMENTS

TABLE OF CONTENTS

Paragraph Title Page 2-1 INTRODUCTION..............................................2-1 2-2 ASSIST VISITS.............................................2-1 2-3 TYCOM ASSESSMENTS.........................................2-1 2-3.1 PMS Assessment..........................................2-2 2-3.1.1 PMS Assessment Objectives.............................2-2 2-3.2 MDS Assessment..........................................2-3 2-3.2.1 MDS Assessment Objectives.............................2-3 2-3.3 Definitions.............................................2-3

Downloaded from https://www.everyspec.com

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

2-1 SECTION II CHAPTER 2

ASSIST VISITS AND TYCOM ASSESSMENTS 2-1 INTRODUCTION The Ships' 3-M System enhances force readiness and helps identify material problems. TYCOMs are responsible for ensuring that each command under their cognizance effectively uses the 3- M system. When the 3-M system is effectively used, a higher degree of equipment readiness will be achieved. Through assessments of the 3-M system and assist visits, TYCOMs can recognize problems the command may be having in effectively identifying, scheduling, performing, and documenting maintenance actions. For problems identified, corrective action can then be initiated.

Each TYCOM will establish, train, and maintain a team consisting of qualified 3-M system coordinators responsible for monitoring PMS installations, providing assistance when requested, and performing 3-M assessments. 2-2 ASSIST VISITS The TYCOM shall schedule assist visits to each ship as requested. The purpose of an assist visit is to aid managers by determining how efficiently the command's 3-M program is operating, and help identify areas with potential problems. The assist team will take the appropriate measures to identify the areas that need attention and the type of assistance desired. An assist visit is instructional and provides training and assistance to the requesting activities.

Assistance in the form of briefings or group discussions shall be provided to clarify any problems that become apparent during an assist visit. Each assist visit shall include a debriefing period with the commanding officer prior to concluding the visit. These assist visits will include advice concerning management of PMS and MDS, as well as advice regarding other significant 3-M system problems. 2-3 TYCOM ASSESSMENTS The purpose of an assessment is to determine the effectiveness of the command's 3-M program in managing the accomplishment of the maintenance. A TYCOM assessment is a comprehensive audit of the Ships' 3-M Program. Emphasis is to be given to the effectiveness of maintenance management and maintenance accomplishment. Included in the assessment will be the adequacy of the PMS installation and the effectiveness of the shipboard training program.

Downloaded from https://www.everyspec.com

SECTION II 2-2 TYCOMs shall conduct, at intervals of not greater than 24 months, a comprehensive assessment for each ship and applicable shore activity to determine the effectiveness of the 3-M program. A grade of less than 80 percent for any assessment area (PMS Performance Rate (PPR), MDS Performance Rate (MPR), and 3-M Performance Rate (3MPR)) is considered unacceptable. An assessment will not be converted to an assist visit for any reason.

To ensure standardization of the measurement of 3-M program performance, and to enhance communications at all levels of command, the procedures described herein are the minimum to be adhered to during assessments. Refer to reference (a) and TYCOM maintenance instructions for Fleet assessment requirements, standard assessment definitions, and evaluation criteria and calculations for both PMS and MDS. 2-3.1 PMS Assessment Proper PMS performance is critical to maintaining acceptable equipment performance levels required in today's tactical environment. Additionally, personnel and environmental safety is paramount in conducting routine preventive maintenance aboard ships. It is the Commanding Officer's responsibility to ensure the following PMS objectives are met in accordance with Fleet and TYCOM directives. 2-3.1.1 PMS Assessment Objectives a. Ensure the PMS performed matches the installed equipment.

b. Ensure PMS completed was done correctly in accordance with the MRC. "Correctly" includes but is not limited to:

(1) safety precautions were observed,

(2) proper tools and materials were used,

(3) tag-out procedures were correct when applicable,

(4) if hazardous material (HAZMAT) was used, personal protective equipment used was applicable for the HAZMAT involved and in good material condition. HAZMAT disposal conducted correctly.

c. Analyze the recorded reasons for non-accomplishment of PMS to determine ship-wide and departmental trends, and actions taken to improve PMS.

Downloaded from https://www.everyspec.com

NAVSEAINST 4790.8B

2-3 2-3.2 MDS Assessment Documentation and validation of MDS Data is the cornerstone of configuration management resulting in improved logistics and repair support aboard ship. MDS spot checks, similar to PMS spot checks, will be conducted. Refer to reference (a) and TYCOM maintenance instructions for Fleet assessment require- ments, standard assessment definitions, and evaluation criteria and calculations for both PMS and MDS. 2-3.2.1 MDS Assessment Objectives MDS Objectives include:

a. Shipboard Ships Configuration and Logistics Support Information System (SCLSIS) file matches installed equipment.

b. Logistics Support Data (LSD) matches installed equipment.

c. CSMP provides correct information to allow effective planning and estimating of deferred maintenance actions.

d. Shipboard pre-transmittal review, up-line reporting and Automated Shore Interface (ASI) processing (COSAL maintenance processing for non-automated ships) is accomplished in a timely manner. 2-3.3 Definitions a. PMS Performance Rate (PPR). A numerical evaluation of the performance and documentation of planned maintenance.

b. MDS Performance Rate (MPR). A numerical evaluation of the performance and documentation of maintenance.

c. 3-M Performance Rate (3-MPR). A composite evaluation of the performance and documentation of PMS and MDS. Downloaded from https://www.everyspec.com

MAINTENANCE AND MATERIAL MANAGEMENT (3-M) MANUAL

SECTION II

CHAPTER 3

SUBMARINE PERFORMANCE MONITORING TEAM (PMT) MAINTENANCE AND INSPECTION PROCEDURES

Downloaded from https://www.everyspec.com