Transcript PPT Template

Slide 1
WW OPS-09
Model-Driven Operations Management
The Foundation for “Process Excellence”…
Tom Troy – Director, Ops & Execution Portfolio Segment
© 2012 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.
Model-Driven Operations Management
The Goal of this Session…
 Highlight some of the challenges customers
are still facing in the production and
manufacturing market space around
managing “execution-related” activities
 Discuss how we are addressing some of
these “execution” challenges by employing
a “model-driven” application framework that
leverages Wonderware Execution
applications and customer legacy
applications
Slide 3
“Unification” of Plant-Level Processes
Our Customer’s Challenges…
 Manufacturing business processes cross-over
functional domains and plant-level production
applications
 Lack of governance around manufacturing
business processes
 Need more agile manufacturing business
processes to support changing business needs
 Need more responsive manufacturing business
processes
 Need to increase the performance of their
people assets
Global pressure to improve safety, compliance, quality, productivity and cost are
forcing companies to evaluate and improve their business processes.
Slide 4
“Unification” of Plant-Level Processes
What’s the “Current State”??
 A significant number of “point solutions” in use
– on average, 50+ applications in the production
environment
 People bridging the information gaps and
process flows that exist between applications –
leveraging experience, paper, white boards, etc.
 Point-to-point integration between production
applications, as well as enterprise applications
 Rigid, inflexible production processes that span
across many applications and people
“Significant Number of Barriers that Impede Operational Excellence”
Slide 5
“Unification” of Plant-Level Processes
What’s the Scope of Unification??
Enterprise Apps:
 ERP
 PLM
 EAM
 WMS
 APS
People:
 Quality Assurance
 Maintenance
 Operations
 Engineering
 EH&S
 R&D
 3rd Party Vendors
& Suppliers
Slide 6
Production Apps:
 MES
 Quality
 LIMS
 Labor
 Scheduling
 Simulation
 Optimization
 Control
“Unification” of Plant-Level Processes
What’s the Need??
Unified Approach to Process Management
A unified approach for coordinating manual efforts (people-driven
processes), system-automated tasks and information flows.
Model-Driven Execution
Enable process owners (e.g. Operations, Maintenance, QA, IT) to
change processes collaboratively in support of volatile business
environments.
A highly “responsive” environment that coordinates and synchronizes
people and/or systems in an intelligent and effective manner.
Rapid Innovation
An easier way to change and innovate processes (e.g. Production,
QA, Maintenance, etc.), especially those that need to change often.
Slide 7
Current State of MES Today
What Needs to Improve Around Production Execution??
Conventional MES
production routings do
not establish all of the
processes and associated
stakeholders required to
support all of the
activities necessary to
produce semi-finished or
finished goods
Example – Process Order Initiation
Slide 8
Current State of MES Today
What Needs to Improve Around Production Execution??
Other examples of processes that extend beyond traditional
MES production execution boundaries:
●
●
●
●
●
Line startup & shutdown
Material staging
Quality hold/quarantine
LIMS samples
Order initiation &
completion
●
●
●
●
QA release
Emergency maintenance
Line clearance
Returning materials to the
warehouse
● …
MES business processes need to expand beyond their “Operations”
boundaries to coordinate resources and applications in other domains.
Slide 9
Current State of MES Today
Application Integration…
● MES applications are frequently required to interface and
exchange information with many different enterprise and
plant-level production applications
● MES integration scenarios
are primarily focused on
retrieving data from… or
transacting with external
applications
PLM
ERP
EAM
WMS
MES
LIMS
Labor
FCS
Slide 10
Current State of MES Today
MES App.
Quality
Detailed
Specs
Created
New Product
Plans
Reviewed
Engineering
MES application
integration is focused on
sending and receiving
information to/from
external applications – it
does not address any
workflow activities that
may be required as part of
the integration scenario
New Product
Created in
MES
New Product
Plans
Reviewed
Detailed
Recipes
Created
R&D
What Needs to Improve Around App. Integration??
New Product
Released to
Plant
Example – New Product Release to Plant
Slide 11
Current State of MES Today
What Needs to Improve Around App. Integration??
Other examples of MES integration scenarios that may require
workflows:
● Revised product
specifications from PLM
● Emergency maintenance
work order request to EAM
● Material receiving &
inspection information to
ERP
● Specification change
request to R&D/PLM
● Process/work order
reconciliation to ERP
● Schedule change request
to FCS application
● …
Workflows are necessary to support MES integration scenarios between
external applications such as ERP, PLM, EAM, etc.
Slide 12
Current State of MES Today
Advanced Analytics & Reporting…
● MES applications provide dashboards, analytics and
operational reports that give plant personnel visibility to
production related activities and data
● Plant personnel access this
information periodically to
view KPIs, production
status information, etc.
● Others use this information
help to support continuous
improvement programs
and initiatives
Slide 13
Current State of MES Today
EAM App.
Operations
Operations
Approves
Maint. Req.
Operations
Reviews Maint.
Request
Maintenance
MES analytics and
reporting applications
provide visibility to
production and nonproduction related KPIs,
metrics and data – they do
not automatically spawn
any actions based on
predefined thresholds
being exceeded
Maint. Work
Order
Request
Created
Reviews Data
to Determine
Root Cause
Submits Request
to Ops to Approve
Maint. Request
MES App.
What Needs to Improve Around Analytics & Reporting??
Downtime KPI
Threshold
Exceeded
Example – Production Downtime Threshold Exceeded
Slide 14
Current State of MES Today
How Can Customers Effectively
Manage These Extended MES
Processes that Cross-Over
Organizational Boundaries and
Applications?
Slide 15
Model-Driven Operations Management
Value Proposition:
 Process Governance
 Knowledge Management
 Process Agility
 Dynamic Change Mgt.
 Process Responsiveness
 Rapid Innovation
 Continuous Improvement
 People & System-Centric
Collaboration
 Real-time Decision-Support
Transforming our Advanced Portfolio into “Process-Oriented” Applications
Slide 16
Model-Driven Operations Mgt.
Key Elements
Business Rule/Process Management
 Composite solution business rules managed in an
intuitive, visual workflow-modeling environment
 Out-of-the-box configurable workflow activities
for common MES, Quality, Labor, Maintenance,
etc. transactions
 Out-of-the-box workflows for standard
configuration and runtime tasks associated with
MES, Quality, Labor, Maintenance, etc. functions
 Ability to add and manage custom workflow
activities for our customers legacy applications
Single Framework to Manage “Solution Business Rules” that Cross-Over
Production Application and Organizational Boundaries
Slide 17
Model-Driven Operations Mgt.
Key Elements (cont.)
Slide 18
Model-Driven Operations Mgt.
Key Elements (cont.)
Forms/UI Management
 Model simple or complex forms to collect or
visualize data in support of composite business
rules/processes
 Out-of-the-box forms for standard MES, Quality,
Labor, Maintenance, etc. functions
 Support composite application development (e.g.
forms can host data from multiple data sources,
etc.)
 Forms should be accessible via many channels
(e.g. web client, mobile client – multi platform,
ArchestrA graphic, etc.)
Single Framework to Manage “Solution User Interfaces” that Cross-Over
Production Application Boundaries
Slide 19
Model-Driven Operations Mgt.
Key Elements (cont.)
Slide 20
Model-Driven
Operations Mgt.
End-user will be able to
Invensys will provide
out-of-the-box “application
workflows” that can be
extended to embrace
existing software assets
leverage out-of-the-box
Composite App.
Framework – Modeling Experience
forms provided for Invensys
applications… or configure
composite forms
End-user shall be able to
configure composite
“solution business rules”
that support the task
End-user will be able to
configure the flow of the
user-experience for the
composite solution
Slide 21
Model-Driven Operations Mgt.
User Experience – Browser UI
Process Orders
Start
Pause
Slide 22
Stop
Model-Driven Operations Mgt.
User Experience – Mobile UI on Apple iOS
Slide 23
Model-Driven Operations Mgt.
User Experience – Mobile UI on Apple iOS
Slide 24
Model-Driven Operations Mgt.
User Experience – Composite UI (MES & EAM)
Slide 25
ArchestrA Workflow Software & MES
“Key Values”
 Provides for real time, end-to-end institutionalization of
MES business processes across disparate hierarchies
(people) and systems in an organization
 Enables knowledge management across the enterprise by
providing standardized approaches to normal, unscheduled
or disruptive events in your operations processes
 Enables process agility, allowing for dynamic change
management for all processes within an organization
 Drives higher levels of people-centric and system-centric
collaboration to allow people, teams, organizations and
systems to work together more effectively
Slide 26