Operator Rounds
EZMaxMobile MUWG Fall 2016
Agenda • • • • • • •
Product Selection / History EZMaxMobile Key Features Rollout Status Work Management Inventory Operator Rounds Support
Mobility Product Selection • Thorough Evaluation Process – – – – –
Requirements Gathering - 2013 Industry Benchmarking – 2014 Vendor Evaluation – 2014-15 Field Testing & Approvals – 2015 Configure / Deployment - 2016
• EZMaxMobile Selected Based On: – – – –
Cost Effectiveness Breadth of Capability Flexibility in Solution Vendor References and Responsiveness
Rollout Status • Phased Approach • Site by Site Launches – WM – Live at Barry / Daniel / Hatch / Wansley (8/15) – SCM – Will deploy in Phase 2 concluding early 2017 – Operator Rounds – Will deploy in Phase 2 concluding early 2017
EZMaxMobile Intro • High Points – – – – –
Platform Independent Hybrid Application Methodology Proprietary Application Front End Natively Integrated with Maximo Online / Offline Capable
Work Management – Mobile Functionality • SNC • Permits • Condition Reports • WO Lifecycle
• SCG • Condition Reports • WO Lifecycle
Note: Primarily used online with some offline capability
Hold for Feedback Demo
Inventory and Procurement – Mobile Functionality • • • • • • •
Physical Counts Attach Images to Item Master Sourcing Approvals Issues Transfers Receipts Returns
Note: Primarily used in online mode with offline mode used for p-counts.
Hold for Inventory Demo
Operator Rounds • Create and Execute Rounds • Create CR from within Rounds with a few taps • Review and Approval Note: Primarily executed using the offline functionality.
Operator Rounds – Condition Monitoring Points
Operator Rounds – Routes
Operator Rounds – Site Settings
Hold for Operator Rounds Demo
Support • Consistent with Maximo Support Model • Online Mode – Behaves and validates as ES Maximo does – Actions are happening in Real Time
• Limited Offline Support Capability for ESS – Non-Descript Error Messaging – Logging Access Required for meaningful issue resolution
• Troubleshooting Guide
Devices
Lessons Learned • Offline development consumes much more time than online development. • Narrow Device Options to avoid platform specific issues.
Agenda • • • • • • •
Product Selection / History EZMaxMobile Key Features Rollout Status Work Management Inventory Operator Rounds Support
Mobility Product Selection • Thorough Evaluation Process – – – – –
Requirements Gathering - 2013 Industry Benchmarking – 2014 Vendor Evaluation – 2014-15 Field Testing & Approvals – 2015 Configure / Deployment - 2016
• EZMaxMobile Selected Based On: – – – –
Cost Effectiveness Breadth of Capability Flexibility in Solution Vendor References and Responsiveness
Rollout Status • Phased Approach • Site by Site Launches – WM – Live at Barry / Daniel / Hatch / Wansley (8/15) – SCM – Will deploy in Phase 2 concluding early 2017 – Operator Rounds – Will deploy in Phase 2 concluding early 2017
EZMaxMobile Intro • High Points – – – – –
Platform Independent Hybrid Application Methodology Proprietary Application Front End Natively Integrated with Maximo Online / Offline Capable
Work Management – Mobile Functionality • SNC • Permits • Condition Reports • WO Lifecycle
• SCG • Condition Reports • WO Lifecycle
Note: Primarily used online with some offline capability
Hold for Feedback Demo
Inventory and Procurement – Mobile Functionality • • • • • • •
Physical Counts Attach Images to Item Master Sourcing Approvals Issues Transfers Receipts Returns
Note: Primarily used in online mode with offline mode used for p-counts.
Hold for Inventory Demo
Operator Rounds • Create and Execute Rounds • Create CR from within Rounds with a few taps • Review and Approval Note: Primarily executed using the offline functionality.
Operator Rounds – Condition Monitoring Points
Operator Rounds – Routes
Operator Rounds – Site Settings
Hold for Operator Rounds Demo
Support • Consistent with Maximo Support Model • Online Mode – Behaves and validates as ES Maximo does – Actions are happening in Real Time
• Limited Offline Support Capability for ESS – Non-Descript Error Messaging – Logging Access Required for meaningful issue resolution
• Troubleshooting Guide
Devices
Lessons Learned • Offline development consumes much more time than online development. • Narrow Device Options to avoid platform specific issues.
