FMMUG - 2016 Janet Spencer and Galen Winchip April 2016
Key Accomplishments Two Universities, 50+ combined years: Three CMMS systems Implemented two CMMS systems GL interfaces Dimensional data warehouses Mobile utilities meter reading/billing Carpool reservations/billing Work planning and execution management Refrigerant tracking Mobile warehouse management Time and attendance/payroll Payroll interfaces Financial and accounting integration Budget reporting and management Purchasing/receiving/accounts payable Accounts payable reconciliation Payroll reconciliation Reporting and data analytics Asset data management PM program management Education and training Process improvement Shop inventory management Job estimating and costing Contractor services Mobile work management OMNI Class implementation Lost time injury/workers comp tracking Call center operations Heavy equipment reservations and billing Automated recurring financial transactions 2
Impetus Joel Schriever, AVP of Operations (May 2010- July 2014) Maximo Transactional data is insufficient 3
Assessment Process Interviews Hands-on testing 4
Assessment Findings Conclusion: Maximo mobile design was a poor fit. Design of Maximo mobile assumed best maintenance practices Plan and assign work well in advance Download to mobile and don t touch during the day Upload and assess progress at shift end Operational reality High volume of small unplanned work Frequently urgent Changing work assignments Developed look/feel prototype that was well received 5
Mobile Interface Wish List Supervisors Real-time execution feedback Easily assign one or more engineers Quiet the engineers rumblings Maintenance Engineers Simple intuitive interface Prioritized work queue Work order and asset details Start/stop clock Daily timesheet Real-time success/fail feedback Create work orders and follow-ups Easily share work order with co-worker 6
Re-Facing: Alternate, narrowly focused, user interface Make it so easy they won t want to do it any other way. 1) Limited scope/task-specific interface 2) Legacy application remains unchanged 3) Small and simple focus is on user interface and business rules 4) Forces the one best way without extensive SOP s and training 7
Pure Web Application Client needs only a web browser Coded in Java Directly queries Maximo database Updates via SOAP messages to Maximo Business Objects Maximo does not know the mobile application exists 8
Demo Work Order Life-Cycle 1. Create work order 2. Assign and approve 3. Clock-on 4. Find and assign a helper 5. View asset specs and history 6. Clock-off 7. Complete work order 8. Close work order 9
Implementation Pilot implementation electrical shop Phased in other shops one-by-one over about six months 24X7 usage, about 175 users Limited capabilities when Maximo is down 10
Tangible Business Benefits Performance Indicators Backlog reduction Cycle time reduction Increase in work order volume Mobile Application Transactions monthly averages 750 new/follow up orders 2,500 comments 5,400 status changes 94% of the labor transactions 11
Work Order Backlog 33% reduction # of Orders Work Order Backlog 800 700 600 600 500 400 300 400 200 100 0 May June July Aug Sept Oct Nov Dec Jan Feb Mar Apr 2014 2015 12
Work Order Cycle Time reduced by a factor of four # of Days Work Order Cycle Time 5.0 4.5 4.0 3.5 3.0 3.2 2.5 2.0 1.5 1.0 0.5 0.0 May June July Aug Sept Oct Nov Dec Jan Feb Mar Apr 2014 2015 0.8 13
New Work Orders 33% increase # of Orders New Work Orders 1,600 1,400 1,250 1,200 1,000 900 800 600 400 200 0 May June July Aug Sept Oct Nov Dec Jan Feb Mar Apr 2014 2015 14
Intangible Benefits Everyone is much more satisfied Maintenance Engineers Supervisors Directors & AVP Easily create special applications Improve productivity and data quality Simplify complex, awkward or error-prone activities 15
Contact Information Galen Winchip winchip@uchicago.edu 309-706-6490 Janet Spencer jspencer1@uchicago.edu 217-493-9166 With Special thanks to: Adam Davis, of Asset Partners, for technical support, and advice. adavis@assetpartners.com 16
Questions 17