Maintenance Management Exam 3 Review Sheet

Private Anwar - Maintenance Management Exam 3 Review Sheet I) Intro to GCCS-MC - GCCS-MC = used for accounting - Deployable portfolio system - Technology backbone of a multi-year, multi-phase, corps-wide logistics program - Purpose: - Single point of entry for all requests (product, service) - Look up and down logistics chain - With greater asset visibility and access to reliable information, commanders can make better decisions - Designed to improve combat effectiveness of the MAGTF - Objectives: - Reduce customer wait time - Improve logistics response time - Decrease dependence on forward positioned stocks - Capabilities of GCSS: - Program Executive Officer for Enterprise Information Systems (PEO EIS) oversees GCSS-MC - Features: - Enterprise wide - visibility, accountability, responsibility of Marine Corps equipment - Automated service requests and requisitions - Automated PM scheduling - Extends equipment service life - Near real time reporting and view - Replaces daily/weekly reporting cycles - Command and Control (C2) Support - Increased effectiveness of the force through friendly situational awareness and combat support system planning - Open system design provides interoperability with MAGTF and joint coalition Command and Control (C2) Systems - User Productivity Kit (UPK) - Purpose: reinforce training with practical application activities - 5 playback modes: see, try, do, know, print - Self-Registration policies: - Required training, create secure password, CAC card with PKI certificate, BIC assigned by administration section of command clearance from UUAM (Using Unit Account Manager) - UUAM role = grant access to GCSS-MC app., after user requirements are met, UUAM will assign a username and password - Wild card: % is an infinite amount of characters, _ is a specific character/digit - MAR% = MAR​TIN​, MAR​TINEZ​, MAR​INE - MAR_ = MAR​S,​ MAR​C​, MAR​Y - Conduct a search - Query = pull data from a stored source

-

Universal Work Queue (UWQ) = used to access, organize, review, evaluate, and act upon different service requests - Purpose: access, organize, and act upon different types of work generated by the GCSS-MC System - 4 Types of Help Options - Help menu/Help Window, Oracle Application Library, Keyboard Help, About Oracle Application Library, Keyboard Help, About Oracle Applications - Remedy Help Desk: tool for GCSS-MC user to find help options for common problems that users can face II) Installed Base = life cycle tracking system - Facilitates enterprise-wide life cycle item management - Item instance: unique tracking number specific to one item - Capabilities - Records and tracks item instance from time its received in inventory - Tracking details include location, status, ownership, party, configuration data, contracts, modifications, and SR repairs - Purpose: maintain integrity of data contained within GCSS-MC - Responsibilities: - Commanders ensure that authorized end users within their command only use transactional and voucher able methods - Maintenance users - Use the IB for maintenance production - Use the IB for configuration management publication - Use IB for Modification Verification - New Equipment Fielding - Fielding Plans (FP) are reviewed to ensure maintenance resource planning is coordinated - Validate or initiate equipment life-cycle attributes within MAIS - Item Instance Notes: all required marks that don’t have a specific data entry point in GCSS-MC will be entered separately as notes in item instance notes III) Service Request - SR = foundation of all activities with GCSS-MC - Each task, repair order, supply request, etc., starts with a service request - Key Features: - Tracks and logs information and interaction - Communicate detail of problem issues - Each work item gets individual task - Automate routing of tasks to individuals and units - Maintenance - Different Maintenance Service Requests: CM, PMCS, SL-3, Cal, MODS, MISC - Supply - requisition equipment or supplies - Flow of Maintenance SR within GCSS-MC - Preparing Activity (initiates SR) - operator - Organizational Maintenance Section (reviews, accepts, updates, and conducts maintenance) - mechanic/technician - Quality control/maintenance chief

-

Job Status - Job status identifies what stage SR is in - UM 4000-125 p. 1096 - Commonly used: - Equipment accepted (Equip Accp) - Short parts - Repairs in progress - Electronic page 1130 has the job statuses of service requests in UM 4000-125 - Problem Codes: identify the specific/most critical defect of the equipment - UM 4000-125 p. 1062 - Primary Problem Code - explains most critical defect of equipment - Additional Problem Code - more descriptively explains problem - Copying a Service Request - Purpose: minimize data entry - Copying allows user to duplicate an already created SR - At top left corner of SR there’s an SR # which you should write down - Audit a SR (examine, verify, and correct deficiencies) - required fields are highlighted in yellow - Error messages will show on screen as they occur - Closing a SR - Once maintenance or service has been completed, maintenance chief or quality control will review the SR to ensure proper debriefing - Batch Service Requests - Gives user ability to create multiple SRs for like items (same NIIN) - Primarily used for: - Pre-fire inspections - Unlimited technical inspections IV) Task and Parts Requirements - UM 4000-125, electronic page 553 or page 520 explains maintenance tasks - Breakdown: - Tasks: - Owner - creates SR - Maintenance - Acceptance Phase (SL-3 statement: complete, list, no SL-3 accepted) - Visual Defects (none, list all defects) PMCS (either done or not done) - Modifications (installed or not installed, verified) - Maintenance Tasks: defects, parts requirement - Final Inspection: repairs inspected, modifications verified, QC Complete, - Owner Notified Task: name of individual in owning unit who was notified the work was completed; date notified; any additional notification attempts - *electronic page 556 in UM 4000-125 tells order of filling out SR Task Creation - Debriefing Tasks: method of recording service hours - Debrief of labor and debrief of materiel (debrief any material or parts used to support the task) - Marine Corps Supply System - consists of 3 elements/managerial levels: Marine Corps HQ, in-stores, out-of-stores functional elements - Sassy Management Unit (SMU) - system’s centralized record keeping, control, and data collection agency; responsible for full range of inventory management actions