Slide 1
INT-19 IntelaTrac and Workflow forWork Order Execution
David NichamoffGlobal Practice Lead
Jason VickManager, Technical Sales
Consultant
@InvensysOpsMgmt / #SoftwareRevolution
/Wonderware
/InvensysVideos
social.invensys.com
© 2013 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries.All third party trademarks and service marks are the proprietary marks of their respective owners.
David NichamoffGlobal Practice Lead
Jason VickManager, Technical Sales
Consultant
/Wonderware
/Group/Wonderware IntelaTrac User Community
Agenda
1. CMMS Integration
2. Mobile Work Requests
3. Mobile Work Order Execution
4. Mobile Work Order Execution w/ Workflow
Slide 3
1. CMMS Integration
2. Mobile Work Requests
3. Mobile Work Order Execution
4. Mobile Work Order Execution w/ Workflow
CMMS Integrations
CMMS Integrations
• Two Types of CMMS Integrations
• Work Order Notifications
Work Order Notifications (Scheduled, On Demand)
Equipment/Locations
Reference Values
• Work Order Execution
Complete CMMS Work Orders on the handheld
Update status, measurements points, etc.
• Integrations delivered or in progress for SAP, Maximo, Avantis, JDE,D7i
Slide 5
• Two Types of CMMS Integrations
• Work Order Notifications
Work Order Notifications (Scheduled, On Demand)
Equipment/Locations
Reference Values
• Work Order Execution
Complete CMMS Work Orders on the handheld
Update status, measurements points, etc.
• Integrations delivered or in progress for SAP, Maximo, Avantis, JDE,D7i
Mobile WorkRequests
SAP Work Notification Architecture
Priority codes
Notification types
Equipment
Locations
Cause Codes
Problem Codes
Object Parts
Creates:
Priorities.xml
NotificationTypes.xml
Equipment.xml
Locations.xml
ProblemCodes.xml
ObjectParts.xml
CauseCodes.xml
Scheduled
Trigger
IntelaTrac datatransformation services
import data into theIntelaTrac Database
TriggerTrigger
Time Interval
Slide 7
Priority codes
Notification types
Equipment
Locations
Cause Codes
Problem Codes
Object Parts
Creates:
Priorities.xml
NotificationTypes.xml
Equipment.xml
Locations.xml
ProblemCodes.xml
ObjectParts.xml
CauseCodes.xml
Work Order Notifications Creates:
Notification.xml
ScheduledIntelaTrac data
transformation servicesimport data into theIntelaTrac Database
Time IntervalEvery
Transfer
Work Order NotificationsUpdates SAP PM
On Demand IntelaTrac datatransformation services
outputs data
guid.xml
On DemandEvery
Transfer
Procedure Builder ConfigurationDesigned into
theworkflow
Action Namecarried overto WOR
Notes enteredcarried overto WOR
Slide 8
Designed intotheworkflow
Action Namecarried overto WOR
Notes enteredcarried overto WOR
Mobile - Create & View Work Requests• Review Existing Work
Requests
• Create an ad-hoc WorkRequest
• Lists defined by CMMS
• Work Request Triggeredfrom an Action
• Existing Requests aredisplayed for review
• Some fields are autopopulated
Slide 9
• Review Existing WorkRequests
• Create an ad-hoc WorkRequest
• Lists defined by CMMS
• Work Request Triggeredfrom an Action
• Existing Requests aredisplayed for review
• Some fields are autopopulated
Using Workflow for Alternative ApprovalProcess• Requirement for an email or form based Work Order Notification
process outside of SAP
• Wonderware Workflow can be used to trigger alternative approvaland notification steps
• The original submitter is notified of WON success or failure
• The following diagram clarifies the process:
Slide 10
• Requirement for an email or form based Work Order Notificationprocess outside of SAP
• Wonderware Workflow can be used to trigger alternative approvaland notification steps
• The original submitter is notified of WON success or failure
• The following diagram clarifies the process:
Start
Initiator
Notify
Area CTO OPMAN
A new anomaly request raised in theexternal system will trigger a workflow
Anomaly request details sent to maintenanceoperator through Skelta form for action
END
Discard
NotificationForm data with added comments
Notification
Notify
END
Slide 11
Start
Initiator
Notify
Area CTO OPMAN
A new anomaly request raised in theexternal system will trigger a workflow
Anomaly request details sent to maintenanceoperator through Skelta form for action
END
Discard
NotificationForm data with added comments
Notification
Notify
END
Mobile Work OrderExecution
Mobile WO Execution- Customer Value
Slide 13
• Compensate for deficiencies in the CMMS. Improved Material Coordination: Material Reservations from a mobile
environment enables customers to increase wrench time by allowing parts tobe ordered remotely and either delivered by a parts runner or picked upwhen order is ready instead of waiting for materials to be picked.
Improved Planning: IntelaTrac enables Intelligent workflow (e.g. Decisions, Conditional Tasks, Dynamic
Limits/Actions, etc.) Attachment of Digital copies of all relevant Manuals, Guides and Procedures
to be used on the mobile computer.
Mobile WO Execution- Customer Value• Compensate for deficiencies in the CMMS.
Improved Scheduling: IntelaTrac Schedule Manager provides workloadbalancing metrics to help ensure resources are not being overloaded.Additionally, more accurate job completion times enable Planners to moreaccurately estimate durations based upon historical WO data.
Increased Field Supervision: IntelaTrac enables procedural enforcement,data visibility at a granular level, and emailed exception reporting. Thisenables current Supervisors to work more efficiently thus reducing the needto add additional headcount.
Decreased Travel: Mobile environment allows Mechanics to have allrelevant reference materials at their fingertips including, trendable historicaldata of all tasks within the repair/pm procedure. Additionally, several WOscan be made available to Mechanics on the mobile allowing them to changeto a different WO if the equipment they are supposed to work on isunavailable. New WOs can be sent to the mobile while Mechanic is in thefield.
Measure Progress: IntelaTrac provides consistent and accurate updates ofWO history information to the CMMS. Additionally, the granular data that isonly available in IntelaTrac can be; Integrated into other 3rd party systems Trended Reported on (Exception, Compliance, Bad Actors, etc.)
Slide 14
• Compensate for deficiencies in the CMMS. Improved Scheduling: IntelaTrac Schedule Manager provides workload
balancing metrics to help ensure resources are not being overloaded.Additionally, more accurate job completion times enable Planners to moreaccurately estimate durations based upon historical WO data.
Increased Field Supervision: IntelaTrac enables procedural enforcement,data visibility at a granular level, and emailed exception reporting. Thisenables current Supervisors to work more efficiently thus reducing the needto add additional headcount.
Decreased Travel: Mobile environment allows Mechanics to have allrelevant reference materials at their fingertips including, trendable historicaldata of all tasks within the repair/pm procedure. Additionally, several WOscan be made available to Mechanics on the mobile allowing them to changeto a different WO if the equipment they are supposed to work on isunavailable. New WOs can be sent to the mobile while Mechanic is in thefield.
Measure Progress: IntelaTrac provides consistent and accurate updates ofWO history information to the CMMS. Additionally, the granular data that isonly available in IntelaTrac can be; Integrated into other 3rd party systems Trended Reported on (Exception, Compliance, Bad Actors, etc.)
CMMS Interface Scope (SAP)Asset HierarchyReference Data for WON
Component Lists (BOM)Asset TypesWork Order TypesWork Order StatusPlanner GroupsWork CentersFault CodesException and Exclusion Codes
SAP Master Data
Planned Preventive Maintenance
Mobile Work Orders for ExecutionMaterial ReservationsAttached Documents
Measurement Points (As FoundAs Left Conditions)Material ReturnsExceptions and Exclusions
Work Orders for ExecutionWork Order for ScopingMaterial ReservationsAttached Documents
Slide 15
SAP Master Data
Attached Documents*grouped by asset and document type
Document RepositoryCorrective Orders
Work Orders for ExecutionWork Order for ScopingMaterial ReservationsAttached Documents
Measurement Points (As FoundAs Left Conditions)Material Returns
Mobile Work Order Notifications
Work Notifications
Junot Middleware Based Architecture
Web Service Based Architecture
SAP Work Order Execution
Slide 16
The PM Operation can be associated to aChecklist Procedure in IntelaTrac.
By associating Procedures with SAPOperations, you combine the rich userexperience of an IntelaTrac round withexisting SAP WO Infrastructure.
SAP Work Order Execution1. Work Center – Determines
which Role the dynamicallycreated IntelaTrac round will bescheduled to.
2. Schedule Start – Determineswhen the Work Order will bescheduled in IntelaTrac forcompletion.
3. Actual Start/End- Data iscaptured on Mobile computer inIntelaTrac and later sent back toSAP as an update.
4. Equipment– Defines the Assetthat will be associated to theWork Order that is dynamicallycreated in IntelaTrac.
Slide 17
1. Work Center – Determineswhich Role the dynamicallycreated IntelaTrac round will bescheduled to.
2. Schedule Start – Determineswhen the Work Order will bescheduled in IntelaTrac forcompletion.
3. Actual Start/End- Data iscaptured on Mobile computer inIntelaTrac and later sent back toSAP as an update.
4. Equipment– Defines the Assetthat will be associated to theWork Order that is dynamicallycreated in IntelaTrac.
SAP Work Order Execution1. Confirmation– Confirmation isconfirmed on Mobile computerand SAP is updated upon thenext Mobile synchronization.
2. Actual Work– User entersActual Work on Mobile computer.This can be different than ActualStart/End times. SAP is updatedupon the next Mobilesynchronization.
3. Actual Duration- User entersActual Duration on Mobilecomputer. This can be differentthan Actual Start/End times.SAP is updated upon the nextMobile synchronization.
4. Work Start/End– User entersActual Start/End Times onMobile computer. This can bedifferent than Actual Start/Endtimes. SAP is updated upon thenext Mobile synchronization.
5. Custom Fields. Custom fieldsand enhancements can also beupdated.
Slide 18
1. Confirmation– Confirmation isconfirmed on Mobile computerand SAP is updated upon thenext Mobile synchronization.
2. Actual Work– User entersActual Work on Mobile computer.This can be different than ActualStart/End times. SAP is updatedupon the next Mobilesynchronization.
3. Actual Duration- User entersActual Duration on Mobilecomputer. This can be differentthan Actual Start/End times.SAP is updated upon the nextMobile synchronization.
4. Work Start/End– User entersActual Start/End Times onMobile computer. This can bedifferent than Actual Start/Endtimes. SAP is updated upon thenext Mobile synchronization.
5. Custom Fields. Custom fieldsand enhancements can also beupdated.
Mobile Work OrderExecution w/Workflow
Invensys Lubrication ManagementSystemThe LMS is being designed to allow technicians the ability to Prioritize,Collect, and Document Lubrication PMs in an efficient and logicalformat.
Slide 20
Invensys Lubrication ManagementSystem Work Process
Slide 21
Step 1 – Prioritize Activities
The flow of work will start with the LMS havingthe ability to prioritize specific lubricationactivities along with their assigned assets. Theprioritization process is to remain dynamichaving the ability to update automatically basedon completed activities and conditional basedfindings. Priorities will be based on but notlimited to the following criteria:
• Equipment Criticality
• Calendar/Run Based Timing since last activity
• Criticality of Activity
• Overdue Task Priority Progression
Slide 22
The flow of work will start with the LMS havingthe ability to prioritize specific lubricationactivities along with their assigned assets. Theprioritization process is to remain dynamichaving the ability to update automatically basedon completed activities and conditional basedfindings. Priorities will be based on but notlimited to the following criteria:
• Equipment Criticality
• Calendar/Run Based Timing since last activity
• Criticality of Activity
• Overdue Task Priority Progression
Work PrioritizationInputs into the system will be organized into a list of activities by priority e.g. H/M/L.Based on but not limited to the following factors;
• Equipment Criticality• Calendar/Run Based Timing since last activity• Criticality of Activity• Overdue Task Priority Progression• Event Driven
Slide 23
Round List PrioritizationOnce activities are prioritized, the work is then categorized by specific parametersdefined by the Technician or Planner:
• Operating/Permit Area• Lube Type• Activity Type• Required Tools• Required Materials• Craft Capable of Completing the Work• Man Hours per Activity• Proper Activity Status
Slide 24
Once activities are prioritized, the work is then categorized by specific parametersdefined by the Technician or Planner:
• Operating/Permit Area• Lube Type• Activity Type• Required Tools• Required Materials• Craft Capable of Completing the Work• Man Hours per Activity• Proper Activity Status
Summary
• Procedural Enforcement – Best Practices Execution
• Increased Mechanical Reliability – Timely and Accuratecompletion of PMs ensures High Asset Availability.
• PM Execution Optimization – Work Prioritization for PMCompliance.
• Reduced Wrench Time – Attached Documents andHistorical readings help Mechanics do their jobs moreefficiently.
• Continuous Improvement – Eliminate Paper, ReduceErrors, Deploy Changes Quickly
IntelaTrac Compliments the CMMS byProviding:
Slide 25
• Procedural Enforcement – Best Practices Execution
• Increased Mechanical Reliability – Timely and Accuratecompletion of PMs ensures High Asset Availability.
• PM Execution Optimization – Work Prioritization for PMCompliance.
• Reduced Wrench Time – Attached Documents andHistorical readings help Mechanics do their jobs moreefficiently.
• Continuous Improvement – Eliminate Paper, ReduceErrors, Deploy Changes Quickly
Slide 26