WSC study guide

¡Supera tus tareas y exámenes ahora con Quizwiz!

Equipment Configuration Status Accounting

(1) Configuration status accounting, or the ability to accurately document, track, and maintain the configuration of a ship's systems is a critical factor in maintaining proper shipboard logistics support. NAVSEASYSCOM maintains a central database with the ships' configuration data. (2) For each ship class, a single activity called a Configuration Data Manager (CDM), has been designated the control authority for accuracy and completeness of the configuration information. Prior to ship delivery, the SYSCOM and the delivering activity are responsible for the initial accuracy and completeness of the central database. After delivery, it is imperative that the ship maintains and updates its configuration data in the Ship's Equipment File (SEF), through the submission of configuration change reports. (3) An item is considered to be a Configuration Worthy Item (CWI) if one or more of the following criteria are met: (a) Any item that is bought from an outside activity, (b) Any item, including software that has a separate specification, (c) Any item that has a separate drawing, (d) Any item that is a separate line item or sub line item on a purchase order or contract, (e) Any item that has or requires any form of separate technical or logistics document (e.g., supply support, test equipment requirement, calibration standard requirement, technical manuals and/or repair standards, PMS, etc.), Maintenance Assist Modules (MAMs), intermediate and/or depot level maintenance plans or drawings, installation or configuration control drawings and/or selected records, or (f) Any item needed to support software tracking. This means that nearly every part of a ship or system is configuration worthy if it supports the Navy's need to treat the item as a separate configuration item; nothing is too small or too large. Examples of Configuration Worthy Items are systems, subsystems, equipment, subassemblies, piping segments between valves, electrical cables between junction boxes, stuffing tubes/boxes, ventilation ducts between inlets/blowers/outlets, tanks, voids, compartments, masts, booms, padeyes, lifelines, ladders, foundations, sea chests/suctions, underwater hull areas, sacrificial anodes, bunks, lockers, furniture, machine shop tools/attachments/accessories, anything with a separate serial number and anything with life limit or containing life limited components. Alteration installation activities are required to provide configuration change data to the ship's 3M manager upon completion of equipment installation. Configuration changes made by the ship are reported through the Ships' 3-M System. For ships with Maintenance Support Centers (MSCs), the MSC will research and approve all configuration change requests.

what are the Shipboard procedures for implementation of force revisions?

(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 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. (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 SKED users will use the Force Revision CD-ROM and update their schedules. (b) 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). (c) 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. (d) Update the PMS Schedules using SKED.

what are the responsibilities of MARMC and SWRMC 3-M?

(1) Provide PMS products for all PMS installations, new construction and major conversion ships. (2) Provide TYCOMs with PMS reference information. (3) Provide schools and material support commands and activities with documentation necessary to establish and maintain PMS. (4) Provide documentation to users, who are not holders of equipment, on a reimbursable basis. (5) Process non-Technical Feedback Reports and conduct technical review and resolve Technical Feedback Reports (TFBRs). Unresolved TFBRs will be transmitted to the cognizant technical authority. (6) Maintain liaison with TYCOMs and assist with shipboard PMS installations and equipment verifications as requested by them. (7) Develop and revise PMS documentation as directed and funded by SYSCOMs, Bureau of Medicine and Surgery (BUMED), and/or In-Service Engineering Agents (ISEAs). (8) Standardize, maintain accountability and distribute changes of all PMS documentation. (9) Review and evaluate existing PMS maintenance requirements as requested. (10) Assist in PMS verification and installation in newconstruction/major conversion ships as directed. Function as PMS coordinating activity responsible for coordinating review and approval of PMS development documentation to ensure compliance with this instruction and reference (d). (11) Provide guidance to PMS developers to ensure compliance with this instruction and references (c) through (e).

what are some Shipboard Changes to MRCs?

(1) Tools, Parts, Materials, and Test Equipment. (2) Common hand tools and basic housekeeping (3) items may be appropriately substituted or added, by the Work Center Supervisor, without changing the MRC. (4) Approved parts or materials substitutes from the supply system, technical manual, or MIL-SPEC, etc., may be used. (5) Test equipment or certified tools, which meet or exceed the SCAT code requirements may be used.

what do Automated Library Issue Documents (ALID) identify?

(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.

CSMP Report 1

(produced in six options). Each option presents a single line summary of each non-completed deferred maintenance action: a. "Summary by Type Availability", is provided on an "as requested" basis. This report provides a single-line description of each deferred maintenance action sequenced by ship, work center, type availability, and JSN. A work center summary line on the CSMP provides the number of man-hours, by IMA, depot, and ship's force. At the end of the report is a summary of estimated man-hours by type availability for each work center and department, and a line for the ship total. b. "Summary by Work Center", available on an "as requested" basis contains the same information as Option A, but sorted by SHIP, WORK CENTER, and JSN. c. "Summary by INSURV Number", is provided routinely to the ship as directed by TYCOM after an INSURV inspection. It is restricted to only those items on the CSMP that has been assigned an INSURV number that is sequenced by the ship, INSURV number, work center, and JSN. It contains similar information to Option A. Man-hour estimates and summaries are not shown. d. "Summary by Safety Related Deficiencies", available on an "as requested" basis is restricted to only those actions listed on the CSMP which have been assigned a safety hazard code. Sequenced by ship, work center, type availability, and JSN, it contains the same information as Option A for safety related deferred maintenance actions. No man-hour estimates, summaries, or list of additions and deletions are shown. e. "Summary by EIC", available on an "as requested" basis is sequenced by ship, EIC, work center, JSN and contains the same information as Option A, and includes man-hour estimates summarized in EIC sequence at the system level. f. "Summary by INSURV Number and Type Availability", available on an "as requested" basis contains the same information as Option C sorted in a ship, INSURV number, type availability sequence. g. "Summary by SWAB/SWLIN", available on an "as requested" basis contains the same information as option "A" 3-24 including only those JCNs that have a SWAB/SWLIN assigned. The information is sorted by ship, SWAB/SWLIN, Work CENTER/JSN.

why are there 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 configuration and to provide PMS documentation (new issues and revisions).

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. To schedule inactive equipment maintenance, determine the status of the equipment as described. a. The cycle schedule will remain the same. b. SKED on the quarterly schedule: (1) Indicates a vertical line to designate the start of IEM. The vertical line will be drawn only through the affected MIP line of the schedule for the inactive equipment maintenance. (2) At the beginning of IEM, to the left of the vertical line, the IEM Status I or II as appropriate will be listed . (3) Previously scheduled operational PMS requirements within the inactive period will be marked horizontally to signify cancellation. (4) From the IEM section of the MIP, all lay-up and periodic requirements will be scheduled. (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, the status code will be indicated in the first week on the appropriate line. (6) Operational PMS requirements for those items of equipment not declared for inactive maintenance will be scheduled. (7) The start-up requirements and, if required, operational tests will be scheduled at the end of the inactive period. (8) At the end of the inactive period, SKED will mark vertically to indicate the stop of IEM and schedule operational PMS. 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.

what does each Revision Package Contain?

Automated Library Issue Document (ALID)

Ship Responsibility

Automated and non-automated ships maintain a copy of their own configuration and logistics database. This database is the same as the unit's section of the master CDMD-OA database. The two databases are kept in synchronization through the SCLSIS management process. To ensure timely receipt of accurate configuration data, logistics support data and COSAL/supply support data, the ship must: a. Promptly report equipment installed, removed, or modified by ship's force using a Configuration Change OPNAV 4790/CK form. b. Review all configuration change maintenance actions, equipment file corrections, logistics support transactions, and Automated COSAL Improvement Program (ACIP) transactions before transmitting them for shore processing. c. Process all Automated Shore Interface (ASI) data into their automated system promptly in accordance with the SCLSIS Technical Specification. Ships without an automated system installed are responsible for reporting equipment/component changes detected or accomplished by ship's force, Intermediate Maintenance Activities (IMAs), or Alteration Installation Teams (AITs). Shipboard personnel report the configuration changes to the TYCOM via a completed OPNAV 4790/CK Form or Work Candidate.

CSMP Detailed Reports

CSMP Report 2 (produced in three options). Each option presents detailed information regarding the ship's deferred maintenance. a. "Detail Listing by JCN" displays a detailed record of the ship's deferred maintenance by JSN within the work center. If a deferred maintenance action has been documented as a safety hazard, the words "SAF HAZ" appear in the "comment" column. If the maintenance action has been assigned an INSURV number, this number will appear in the "comment" column. b. "Detail Listing by SWAB" displays a detailed record of the ship's deferred maintenance by SWAB. If a deferred maintenance action has been documented as a safety hazard, the words "SAF HAZ" appear in the "comment" column. If the maintenance action has been assigned an INSURV number, this number will appear in the "comment" column. c. "Detail Listing by EIC", is sequenced by JSN within a work center within an EIC.

Automated CSMP Reports

Current automated systems produce both summary and detail printed CSMP reports. Since software applications may differ, check the applicable system's user manuals and guides for available report formats. CSMP reports are produced in a variety of options, with selected sequences and totals. Summary reports are single-line summaries of the uncompleted deferred maintenance actions in the CSMP and are available by type availability, work center, INSURV number, safety-related deficiencies and EIC. Detail reports show the complete record for these actions. CSMP detail reports call for sorts by JCN, EIC, and by SWAB. The following information is provided: a. Unit Identification Code: b. Number of Deferred Maintenance Actions: c. Number of Completed Maintenance Actions (2Ks): (Non-configuration changes) d. Number of Completed Maintenance Actions (CKs): (Configuration changes) e. Number of Correction Documents: f. Total number of documents submitted: CSMP Summary Reports CSMP Report 1

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.

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.

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#.

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.

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 or at a different periodicity with a note specifying the MRC to be used and the modified periodicity.

SELECTED EQUIPMENT LIST

Selected equipment under an intensive management program requiring additional usage data to be collected. METER READING: If the equipment has a time meter and is on the SEL, the reading (to the nearest whole hour) is entered in thisblock. If the equipment has more than one meter, designate the meter being recorded in Block 35 "REMARKS" using the letters "METRED" followed by the meter designator. An asterisk (*) must precede and follow the meter designation. Example: *METRED- 1A2M1*

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.

Shipboard Assessment of MDS Performance

The Commanding Officer is responsible for the assessment of MDS performance onboard their command. The Commanding Officer may request assist visits from the type commanders who can recognize problems the command may be having difficulty in effectively identifying, scheduling, performing, and documenting maintenance actions. For problems identified, corrective actions can be recommended by the TYCOM.

what are the 2 Regional Maintenance Centers (RMCs)?

The Mid Atlantic Regional Maintenance Center (MARMC) and the South West Regional Maintenance Center (SWRMC) are field activities of the FLTCs. Each provides a logistic support group that supports 3-M.

Shipboard Benefits of SCLSIS

The SCLSIS process allows ships to maintain an on-line source of their SCLSIS information allowing them to locate and determine configuration, logistics, and supply data associated with all installed equipment. This information can then be used to fill in Maintenance Data System actions (OPNAV 4790/2Ks, 4790/CKs, and Work Candidate) without having to refer to a series of manual or off-line reference books and files. The on-line system also allows the maintenance personnel to identify the repair parts associated with the equipment/systems that they are maintaining and to order these parts on-line. Since the bulk of the configuration data in the NTCSS Shipboard Non-tactical Automated Data Processing Program (SNAP) database or the NTCSS Organizational Maintenance Management System - Next Generation (OMMS-NG) database is provided, the shipboard personnel need only report the information relevant to the actual maintenance of the equipment. Supply and maintenance worthy configuration changes shall be reported and processed by the Configuration Data Manager (CDM) for Logistics Support Documentation (LSD). The CDMD-OA database provides information used by Navy Inventory Control Point (NAVICP), Mechanicsburg, for calculation of the allowances for repair parts carried onboard. The ship's database, SNAP or OMMS-NG, is periodically updated as a part of the SCLSIS process. This enables the supply department aboard ship to easily maintain its COSAL and order repair parts. The CDMD-OA database is also used to identify which technical manuals, Planned Maintenance System (PMS) documents, and test equipment are necessary to support the on-board equipment and systems. Accurate reporting of configuration data is critical to ensure on-board logistics documentation and parts support is available.

Central Shore Databases

The ability to accurately document, track, and maintain the configuration and maintenance history of ships' systems is critical for maintaining proper shipboard logistics support. The Naval Sea Logistics Center (NAVSEALOGCEN) 3-M Systems Central Database is the focal point for receipt and distribution of maintenance and material data. The Configuration Data Managers Database - Open Architecture (CDMD-OA) database serves as the Navy's central repository for Ship Configuration and Logistic Support Information (SCLSI). This information also assists in Battle Damage Assessment (BDA) and repair.

CURRENT SHIP'S MAINTENANCE PROJECT (CSMP)

The purpose of the CSMP is to provide shipboard maintenance managers with a consolidated listing of deferred maintenance to identify the material condition of the ship. A complete master CSMP may be held by the ship or other location as directed by TYCOM. The CSMP includes, but is not limited to: a. The "automated CSMP" which is the computer-produced listing of deferred maintenance and alterations that have been identified through the submission of OPNAV 4790 documents. In addition to the maintenance actions added by ship's force, outside activities may request that they be allowed to add items to the CSMP. b. The suspense file of OPNAV 4790 documents for maintenance items that have been submitted but are not reflected in the CSMP reports, or have not appeared in the MDS Transaction and Error Identification Report as having been accepted. c. The Work Candidate/Job Sequence Number (Work candidate/JSN) Log which is the work center's list of all material discrepancies to be corrected either by ship's force or an outside activity.

CSMP Use by Outside Activities

There are other activities that use CSMP reports for financial, industrial, operational, and analytical purposes in support of ships. The CSMP is used to plan for repair action in support of individual ships, especially for repair actions requiring a long lead-time. The unit's chain of command uses it to review and provide directions and recommendations concerning a ship's maintenance problems in relation to tender availability, etc.. Type commanders use the CSMP to determine force-wide maintenance problems and trends to develop future maintenance budgets and scheduling of availability. SYSCOMs use it to determine fleetwide maintenance problems and trends in order to initiate corrective actions (redesign, substitutions, increased support, etc.)

To aid in accuracy of the accountability sheets, the following standard entries will be utilized for all flip page reports

Those entries shall begin with either rescheduled, out of periodicity or non-accomplished, followed by the detailed remarks explaining why check was not completed. If situation warrants and in most situations, Job Sequence Numbers (JSNs) and or requisition numbers from supply will be used. Every check that is rescheduled will have the reason that the MR was rescheduled annotated on the flip page

what are the responsibilities/actions of SYSCOMS/BUMED

To Ensure appropriate PMS packages are delivered simultaneously with equipment. Ensure that PMS packages are delivered to the RMCs for inclusion in the master data file. To Ensure that MDS data is used to measure equipmentreliability, maintainability, and operational availability in the fleet; in order to identify deficiencies correctable by SYSCOMs, BUMED or other activities, and to monitor the effectiveness of corrective actions taken. To Supervise efforts of field activities involved in providing, processing, and/or using 3-M System information. To Take action on PMS Feedback Reports (FBR) submitted by fleet personnel. To review existing pms documentation to ensure technical validity and prompt accomplishments of required changes.

what are the responsibilities of Fleet Commanders (FLTCs)?

To Exercise overall responsibility for Ships' 3-M System operation. To Ensure quality, completeness, and timely submission of data collected within their respective fleets. To Ensure personnel assigned to the 3-M staff have the necessary skills to administer the program. To Ensure the scope of Ships' 3-M System training at fleet schools reflects the required quantity and quality of 3-M training. To Provide fleet maintenance and management personnel with the necessary skills to successfully support the Ships' 3-M System. To Advise and assist NAVSEASYSCOM in the execution of Ships' 3-M System responsibilities as required. To Coordinate and control fleet Automated Data Processing (ADP) facilities necessary to process 3-M System information To obtain CNO (N43) approval before implementing management applications which require CNO-funded computer program modification. This does not preclude development of additional applications to resolve management problems providing such development does not require changes to the existing Ships' 3-M System. To Maintain an adequate 3-M staff to administer the Ships' 3-M System. To Jointly (COMLANTFLT and COMPACFLT) develop quantitative assessment criteria, guidelines, and procedures. To Task Operational Commanders to provide sufficient time for ships to conduct 3-M functions. Operational orders, letters of instructions, and other operational directives will recognize and provide for the accomplishment of 3-M requirements.

what are the responsibilities of Type Commanders (TYCOMS)?

To Exercise primary responsibility for the effective operation and support of the Ships' 3-M System under their claimancy. This responsibility includes shore activities under their cognizance where the Ships' 3-M System is applicable. The Commanding Officer of Naval Bases, Naval Stations, and other activities that do not report directly to a TYCOM, shall exercise TYCOM 3-M System responsibilities. To Ensure personnel assigned to the 3-M staff have the necessary skills to administer the program. To Provide qualified teams to conduct Ships' 3-M System training assists and installations. To Conduct review of submitted 3-M data (MDS documents, etc.). Ensure prompt submission and accurate processing of 3—M data. To Provide adequate Ships' 3-M System training to maintenance and maintenance management personnel. To Monitor and participate in the development of 3-M management tools. To Conduct appropriate review of Casualty Reports (CASREPS), Safety Advisory and Mishap Reports, and Material Inspection Reports. To Certify the functional adequacy of the installed Ships' 3-M Systems. To Promote the use of the Internet to access and use 3-M products and tools.

what are the responsibilities of Commander Fleet Forces Command (CFFC)?

To Implement, manage, coordinate and maintain the Ship's 3-M system program for all ships and commands under its cognizance. To Review the personnel and monetary resources required for the operation, improvement, and support of the 3-M System by all levels of management afloat and ashore; and supporting requirements in the budget effort. Submit the program requirements to CNO (N43) for review and validation. To Ensure personnel assigned to the 3-M staff have the necessary skills to administer the program. To Advise and assist NAVSEASYSCOM in the execution of Ships' 3-M System responsibilities as required. To Provide a single point of contact for Atlantic and Pacific Fleets for all 3-M issues to include: policy, training, assessment criteria and procedures. To Obtain CNO (N43) approval before implementing management applications that require CNO-funded computer program modification. This does not preclude development of additional applications to resolve management problems providing such development does not require changes to the existing Ships' 3-M System. To Task Fleet Commanders to provide sufficient time for ships to conduct 3-M functions. Operational orders, letters of instructions, and other operational directives will recognize and provide for the accomplishment of 3-M requirements.

what are the responsibilities of Naval Sea Systems Command (COMNAVSEASYSCOM)?

To Manage and direct the development, implementation, operational maintenance, and improvements of all aspects of the Ships' 3-M System throughout the Navy, both PMS and MDS. To Provide instruction and technical direction for the management of the Ships' 3-M System consistent with policy established by CNO and the requirements of the Fleet Commanders and TYCOMs. To Provide technical direction of the Ships' 3-M System functional efforts at the Naval Sea Logistics Center (NAVSEALOGCEN). To Manage and approve development of Selected Level Reporting (SLR) and Equipment Identification Codes (EICs). To Direct and control revisions of the Ships' 3-M System. To Develop and maintain Ships' 3-M System manuals and other maintenance and material reporting documents. To Direct and maintain detailed documentation policy and procedures for reporting configuration changes to equipment ashore and afloat through the Ships' 3-M System. To Develop and maintain a system to track from submission to completion PMS Feedback Reports (FBR) submitted by fleet personnel. To Develop PMS procedures for specific equipment using Reliability-Centered Maintenance (RCM) procedures and standard formats for all afloat equipment and identical equipment used ashore in accordance with reference (d). To Coordinate PMS matters and provide PMS support for ships and shore activities having identical equipment used aboard ship. PMS support for non U.S. Navy ship type equipment such as documentation development, revision, printing, loading, and maintaining, etc., shall be provided by NAVSEASYSCOM on a reimbursable basis. To Institute a process to continually improve PMS documentation for effectiveness, applicability and affordability using RCM principles in accordance with references (d) and (e). To Develop and coordinate all organizational, intermediate, and depot level Ships' 3-M System functional matters. To Direct parts usage reporting under the Ships' 3-M System. To Coordinate the development of the Ships' 3-M System training for systems command managers. To Oversee the interface of the Ships' 3-M System with other applicable ADP systems. To Monitor, evaluate, and improve the completeness, accuracy, and usefulness of the Ships' 3-M System reporting throughout the Navy. To Identify resource requirements for the Ships' 3-M System matters for inclusion in the Program Objective Memorandum (POM) guidance, budget submissions, and other resource documents. To Provide policy, instruction, and technical direction for shipboard Technical Manual Management. To Provide reliability, maintainability, and availability (RM&A) analysis of systems and equipment to determine operational readiness characteristics. To Create and maintain a central database with each ship's configuration data.

INACTIVE EQUIPMENT MAINTENANCE (IEM)

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-23). 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 and the scheduling and accomplishment of applicable Lay-Up (LU) and Start-Up (SU) maintenance requirements. The applicability of IEM procedures is dependent on determination of equipment status using the following definitions: 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. Inactive Equipment Maintenance (IEM) Documentation IEM procedures are added to the end of existing MIPs and are separated from operational PMS by a single horizontal line 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-23): 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. 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 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. 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 . 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 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 d. If a scheduling MRC is developed it will list numerous MRC periodicities to be scheduled and performed

what are the responsibilities Chief of Naval Operations (CNO)(N43)?

To sponsor the Ships' 3-M System. To develop and implement the overall policy governing management of the Ships' 3-M System, its development, coordination, and maintenance. To Review the total personnel and monetary resources requested for the operation, improvement, and support of the 3-M System by all levels of management afloat and ashore and supporting requirements in the budget effort. The program requirements will be submitted by Commander, Fleet Forces Command (CFFC) to OPNAV N43 for review and validation. To Approve management applications of the MDS and PMS.

packages

Updating procedures for PMS packages during overhaul are contained in Section I Chapter 2.

what are some 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 sall be made to the MIP until authorized; however, performance of affected MRs will be discontinued. Document the nonaccomplishment 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.

Satisfied by Higher Level Test

Upon successful completion of the system (higher) level test, an "¢" 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.)

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. 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.

Force revision procedures

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."

what should Work Center Verifications ensure?

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.

The CSMP is utilized

a. The ship's Commanding Officer and Executive Officer use the CSMP reports to: (1) Determine the effects of deferred maintenance that limit the ship's capability (2) Potential casualty report (CASREP) situations (3) The material condition of each individual work Center (4) What kind and how much outside assistance is needed to complete the deferred maintenance (5) Weakness or shortages in skill levels and/or resources required to do the deferred maintenance (6) What kind of upkeep and cold iron time needed by the ship for maintenance b. The Department Head/Division Officer uses the CSMP reports for the same information as the Commanding Officer and Executive Officer, but may be restricted to their applicable department/division rather than the entire ship. CSMP reports can assist them in determining plans of action for accomplishing the deferred maintenance and evaluating the performance of work center supervisors in the management of their work centers. c. The Work Center Supervisor uses the CSMP reports for managing the work center maintenance.

Monitored maintenance checks

are accomplished by watching the maintenance person perform the maintenance action. Monitored maintenance checks are a valuable tool that can be used by the command to validate and/or train the maintenance personnel.

Technical Feedback Status Report, Report PMS 22

contains outstanding/completed Technical Feedback Reports received by NAVSEALOGCEN Det Norfolk/NAVSEALOGCEN Det San Diego. Category A FBRs will not be reflected on this report.

The Board of Inspection and Survey (INSURV)

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. 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.

three types of spot checks

historical maintenance validation spot checks monitored maintenance checks.

what does the PMS Master File contains

it 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 MaintenanceIndex 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). (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.

Lay-up(LU)

maintenance actions prepare the equipment for periods of prolonged idleness, and are usually performed only once at the beginning of the inactive period.

what are the responsibilities/actions of naval education training command (netc)?

to ensure that training efforts in support of the ships 3-m system support the requirements of the FLCTS, and the necessary follow-on training is provided to fleet personnel To initiate periodic reviews of the ships 3-m system training curricula to ensure compliance with current directives. To ensure school reports configuration changes on any of their shipboard identical equipment that has been changed, modified or deleted; and submit file corrections when applicable To maintain shipboard applicable training equipment in accordance with reference (c)

Historical spot checks

validate preventive maintenance that has been completed.

Maintenance Validation spot checks

validate preventive maintenance that has been reported as complete. The maintenance person will perform the maintenance action. Maintenance Validation spot checks are a valuable tool that can be used by the command to validate their maintenance personnel.

when are Dual periodicity codes 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 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.

TYCOM

will focus on the MDS administration and use of the CSMP. MDS assist visit objectives are to: a. Ensure that the shipboard SCLSIS file matches installed equipment. b. Ensure that Logistics Support Data (LSD) matches installed equipment. c. Verify the CSMP provides correct information to allow effective planning and estimating of deferred maintenance actions. d. Ensure that Shipboard pre-transmittal review, up-line reporting and ASI processing (COSAL maintenance processing for non-automated ships) is accomplished in a timely manner.


Conjuntos de estudio relacionados

Rutgers Anatomy and Physiology Exam Review

View Set

ACTG 307 - Auditing - Audit Evidence (Ch. 7)

View Set

Live Virtual Machine Lab 3.4: Module 03 Configuring and Maintaining DNS Servers

View Set

Chapter 14 Nursing Management During Labor and Birth

View Set