reface
TRANSCRIPT
Re-facing Maximo Mobile Work Planning/Execution Management
Galen Winchip and Janet Spencer
University of Chicago
1
Accomplishments
Two Universities, 50+ combined years:
Three CMMS systems
Implemented two CMMS systems
Multiple 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
Multiple 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
Mobile Interface Goals
Supervisors
Real-time execution status
Easy/multiple work assignments
Expedite urgent orders
Quiet grumblings from engineers
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
3
Developed via Application Re-Facing
Simple, operationally effective user interface
Curtail flexibility: “One Best Way”
In-context privileges (data D user)
De-normalized presentations of data
“Make it so easy they won’t want to do it any other way!”
4
Re-Facing Benefits
1) Optimized to specific operational requirements
2) Legacy application unchanged, leverages investment
3) Quicker to develop; user interface and business rules
4) Process consistency without SOP’s
Maximo is an ideal candidate for re-facing!
5
Pure Web Application
Client web browser
ZERO modifications to Maximo
Maximo integration points “Few” and “Shallow”
Directly queries Maximo database via views
Updates Maximo via SOAP messages to MBO’s
Maximo has no idea the application exists
6
Application Components and Environment
• Technology Components:
HTML, JavaScript, Java Servlets, Ajax, SQL, Web Services/SOAP
Caches data to improve performance and concurrency
Cached entities are synchronized
At each “touch”
Periodically via background threads
No third-party frameworks or tools
• Run-Time Environment
Windows or Unix server
Apache Tomcat (open source, public domain)
1GB memory
Deployed as single WAR file (no external dependencies)
Accesses Maximo database via JDBC
Updates Maximo MBO’s via Web Services/SOAP messages
About a dozen additional database tables (most very small)
7
Interfaces
• Mobile Interface
Designed for small screens such as smart phones
Provided smart phones for all users
Most users choose to use their personal phones
• Work Manager Interface
Designed for larger screens (PC’s, tablets)
8
Special Extensions
• Multi-Asset/Multi-Location Inspections
Check-lists
Auto-creation of follow-up work orders
• Periodic Surveillance
High-frequency, repetitive tasks
Hourly to weekly
Optional data collection
• Inventory
Restocking, receiving, put-away, pick requests, picking, counts, moves
• Procurement
Punch-outs
9
Demo
Work Order Life-Cycle
1. Create work order
2. Assign, approve and expedite
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
Asset Inspections
PM Analysis
10
Implementation
Pilot implementation – one shop
Phased in other shops one-by-one over about six months
24X7 usage, about 200 users
Significant capabilities even when Maximo is down
11
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
12
Work Order Backlog – 33% reduction
13
0
100
200
300
400
500
600
700
800
May June July Aug Sept Oct Nov Dec Jan Feb Mar Apr
# of Orders Average Work Order Backlog
400
600
2014 2015
Work Order Cycle Time – reduced by a factor of four
14
0.0
0.5
1.0
1.5
2.0
2.5
3.0
3.5
4.0
4.5
5.0
May June July Aug Sept Oct Nov Dec Jan Feb Mar Apr
# of Days Median Work Order Cycle Time
0.8
2014 2015
3.2
New Work Orders – 33% increase
15
0
200
400
600
800
1,000
1,200
1,400
1,600
May June July Aug Sept Oct Nov Dec Jan Feb Mar Apr
# of Orders Average New Work Orders
1,250
2014 2015
900
Intangible Benefits
Everyone is much more satisfied
Maintenance Engineers
Supervisors
Upper management
Easily create special applications
Improve productivity and data quality
Simplify complex, awkward or error-prone activities
16
Contact Information
Galen Winchip
309-706-6490
Janet Spencer
217-493-9166
Special thanks to:
Adam Davis, Asset Partners, for Maximo technical support and advice.
17