Configuring Maximo using RulesManager

Michael Tubbs

• Using Maximo since July 2004.• Started with Ver. 5.2, currently on Ver. 6.1.• Currently using , Asset, PM, Work Order, and Planning

Modules.• Will be implementing Inventory Module soon.• Will be incorporating our Facilities Customer Service Center

and corresponding corrective maintenance in the coming year.

• Over 46,000 Assets, 95,000 Locations, 13,000 PM’s.• Some technicians are mobile, using Syclo on wireless laptops.

•Forces you to associate a location with a system hierarchy before saving.

•Builds Location, by concatenating Facility Code, Work Code, and a sequentially generated PM Unit Number.

•Validates Job Number against Location using a remote procedure call to Job Cost, our legacy billing system.

•Builds Job Number 2 from a calculated value if Job Number falls in a certain range

•Sets First Start Date to read only when the counter is greater than “0”. This allows a new PM to be set up with a manual First Start Date, but prevents First Start Date from being manipulated

•Builds Job Number 2 from Job Number, similar to in Asset Module.

•Sets Changed By and Last Changed to the user updating and the current time whenever the record is saved.

•Sets Previous Job Number (previous_jpnum) when a record is duplicated.•Sets Effective Date (effectivedate) and Retire Date (retiredate) when status is changed to active and inactive respectively.

•Sets Status to active on first save.

•Copies PM, Job Number, and Work Code, from parent work order, asset or PM based on rules. •Sets Priority, Job Number, Work Code, Work Group, and Facility Code, from original ticket

•Sets Maintenance Manager Name based on Facility Code•Sets GL Account components based on a calculation from other components, Work Type, Person Group

•Conditionally copies fields from Asset or PM•Validates Job Number against Location using remote procedure call to billing system, same as in Asset module

•Sets Work Order Assignments fields to read only depending on status of assignment

•Validates Work Order is not cancelled, resolved, or on hold.

•Validates work dates (Start Date and Finish Date) are within work order date range.•Requires Job Number for non-Utilities groups.

•Performs same Job Number / Job Number 2 calculation and remote procedure call as in Asset Module.

•Validates Job Number is correct for Estimating Tickets.

•Validate Ticket Number matches Work Order Ticket Number.

•Copies field values from Work Order

•Gets calculated Line Cost from mainframe billing system through remote procedure call.

•Sets Memo to the assets common name.

•Calculates Daily Total Hours for the Labor Code, for the date worked and displays it in a virtual field

•If Auto Route Stop Descriptions? is checked, the route stop Description auto fills with the root asset’s Location Description and Area Served.

Questions?

Contact info:

Michael Tubbse-mail – mtt34@cornell.edu