Test 924: IBM Maximo V5 Implementation

Section 1 - Architecture (15%)

1. Product architecture overview - elements of the core MAXIMO product architecture:
1. WebLogic
2. MXServer
3. Actuate
4. Database platform


2. Configuration
1. MXServer - properties file and its relationships to different elements of MAXIMO
2. Reports
3. Security access
4. Register a report
5. Tools used to create/modify a report for MAXIMO
6. Customize Online Help tools and where sources files are located
7. Application
8. Purpose and methods of cloning an existing application or creating a custom application
9. Set up – MAXIMO start up
10. Basic modification/configuration of application

-Tailoring presentation
> Adding labels
> Changing fields
> Applying lookup
- Value list – created and modified
- Financial periods
11. Signature Security
12. Purposes of groups, users
13. Privileges
14. Database configuration
15. Modify existing configuration – tables, columns
16. G/L account structure

Section 2 - Operations (10%)

1. Recognize how to use:
1. Craft records
2. Labor records
3. Tool records
4. Company records


2. Storerooms
1. Define storerooms and how they are related to sites
2. Grant user access to storeroom
3. Know the two different types of companies records and how to establish multiple addresses and contacts.
4. Failures classes and failure hierarchies


3. Actuate Report handling
1. Running reports and associated parameters
2. Request Page

Section 3 - Work Management (30%)

1. Recognize how to generate and use work orders:
1. How work orders are generated:

- Manual entry
- PM generation
- Condition monitoring
- Follow-Up work orders
- Duplicating work orders
- Work requests from “customers”
- Quick reporting
2. Work orders:

- Define work to be performed, location
- Select equipment item at location
- Identify who reported the work
- Tracking
- Select problem, cause and remedy codes and assign to work order
3. Tracking Labor

- Record labor for multiple work orders for an individual through the Labor Reporting application
- Record multiple labor transactions through work order application
4. How work orders are structured into hierarchy and working within hierarchy

- How costs can be captured
- How to perform cost roll-ups
- Changing status of work orders
5. Work order status

- How to set up
- How to change status
- Different work order status:
> Waiting Approval
> Approval
> Waiting Material
> Waiting Scheduling
> In Progress
> Complete
> Closed
> Cancel
> Use of synonyms
6. Assign and change work types
7. Assign and change work priorities
8. Approval of work orders with material estimates

- Automatically causes creation of materials reservations
- Know what happens to work order status when stock materials not available
9. Workflows can be defined to allow:

- Multiple approval levels and
- Routing between departments /individuals for work control
10. Job Plans

- Can be created for re-use
- How they are handled
- What they include
11. Safety Plans that link hazards, precautions, and lock-out/tag-out procedures can be created.
12. Downtime

- Process for recording equipment downtime
- Terminating downtime status
- Recording downtime cause
13. Work Plans – can be populated from:

- Job Plan
- Manually
14. Hazards

- How they can be defined
- Can be mitigated by
> Precautions
> Lock-out / Tag-Out procedures (sequence of tasks – linked to specific equipment/location /device items
15. Preventive Maintenance

- Plans
> Link job plans to equipment, locations, routes or GL accts
> Designed to support cyclical or recurring maintenance requirements
> Work orders can be generated in a status selected by user on the PM
- PM Plans FrequencyScheduling
> Plans can be defined to cause work order to generate based on frequency, multiple meter readings or a combination of both
> PMs can be seasonal
> Work orders are generated on a frequency determined by the user, and can be generated for a user-defined number of days in advance.
- Handing Master PM records
> Changes to Master PM records can be configured
> Does not create work orders when WOGEN is processed.
- Hierarchy of PM records
> Work orders generated by a route-based PM will be in work order hierarchy
> Can be established that will create a work order hierarchy when the PM work order generation process is executed
> PM records in the hierarchy can be linked to different job plans
> User cannot generate work orders against specific PM child records without generating the entire PM hierarchy into a Work Order

Section 4 - Supply Chain (22%)

1. Create items

- Create rotating items
- Recognize differences between an item and a rotating item
- Understand the receipt of rotating equipment.
2. Understand how lot numbering works
3. Know differences between stock categories (i.e. STK, NS, SP).
4. Create default bin numbers.
5. Understand and set up the parameters that control the reorder process (e.g., Minlevel, Maxlevel, Economic Order Quantity).
6. Assign one or more vendors and/or manufacturers to an item and select a default vendor.
7. Storerooms

- Assign an item to one or more storerooms.
- Issue a stocked item from a Storeroom. Understand what will prevent an issue (e.g. the person does not have storeroom permission).
- Return issued items to a Storeroom. Know what will prevent a return (e.g. the person does not have storeroom permission).
- Transfer items between storerooms.
- Adjust current balances in a storeroom.
- Modify the physical count for an item in a storeroom.
8. Handling Purchasing Transactions

- Create a PR with lines, approve it, and convert it to a PO.
- Perform purchasing transactions using purchasing card functionality.
- Create a PO from one or more PRs and update the PO status.
- Receive materials against a PO.
- Receive Services against a PO.
- Know the difference between a direct issue receipt and receipt to stock.
- Know that users can search for items, locations, or equipment based on the populated.
- Create an item assembly structure record and associate items and quantities.
9. Asset Catalog

- Create an asset catalog template to include: category, sub-category, and attributes for equipment, locations, and items.
- Create domains and valid values for attributes in asset catalog templates.
10. Know that users can search for items, locations, or equipment based on the populated specifications in the appropriate application.

Section 5 - Assets (23%)

1. Equipment Record
1. Difference between a location and an equipment record.
2. Assign an equipment record to a parent equipment record to create an equipment assembly structure.
3. Assign an item to an equipment record to identify that item as a spare part commonly used on the equipment item.
4. Benefits of assigning a Failure Class to an equipment record.
5. Assign an equipment priority to an equipment record
6. Understand how equipment priorities are utilized to determine calculated priorities.
7. Create multiple meters for an equipment record.
8. Assign an Item Number to an Equipment record

- how this allows the user to locate replacement equipment items
- how this is utilized to track maintenance costs by Equipment vs Location.
9. Create an equipment move transaction

- how these transactions link to the Location hierarchy
- how to display a history of those moves by each equipment item
- how an equipment move affects the location of children equipment if the children are at the same location, or at a different location.
10. Know that the user will be prompted when a work order is created on a piece of equipment under warranty.


2. Location/Location Hierarchy
1. Purpose of location and location hierarchy
2. Purpose and effect of hierarchies vs. networks.
3. How to define a new hierarchy
4. Add new locations
5. Assign locations to a single or multiple hierarchies.
6. Understand how to designate a system as the Primary hierarchy.
7. Primary location types: Operating, Storeroom, and Courier.
8. Assign priorities to Locations and how the priorities are utilized in the creation of work orders.
9. Know that the product can support network systems, and the impacts of utilizing them such as the inability to roll-up costs to segments of the network.


3. Condition Monitoring
1. Define a condition monitoring point
2. Understand how to establish warning and action limits
3. Set up the automatic generation of Work Orders when Condition Monitoring limits are exceeded.


4. Failure of Work Order Generation to generate work orders
1. Potential causes, e.g.,

- lack of a storeroom for a planned item
- invalid GL Accounts
- invalid financial periods, etc.


5. Route
1. Know how to create a route
2. A route stop can be defined as a piece of Equipment or a Location
3. How specific job plans can be assigned to each route stop.