Final Post: The Journey of Data Transformation to Wisdom to Enable Smart Work

Visit my final post until determine new approach to engage.

http://operationalevolution.blogspot.com.au/2016/09/final-post-journey-of-data.html

Here is an extract, click over and review

A Culture of Empowerment: Problem Solving at Source

As we observe the world around us change, and more and more the focus shifts to a “new way to operationally work”, we see leading thought companies start introducing innovations in their culture.

One of these we now seen in two leading manufacturing companies who are shifting to the “New World of Work” and introducing not just technology but key cultural changes. One of these is the “Empowerment Culture” one of the strategies these companies is shifting the problem solving to the source.

This overcomes the delays in decisions through having decisions go up the tree by increasing the skill of the workers closer to action, and empowering them to be able to make decisions. This means skill development, embedding knowledge and experience in the system to help facilitate the correct timely decision.

The diagram below shows the structure 

This allows the different levels, roles, and time horizons to focus on their problem solving optimizing the overall operational agility.

The “edge” worker on the front line is performing situational problem solving relative to production and asset at the NOW.

The plant supervisor have a wider time horizon of hours, and is looking at the plan, and adjusting thru “Systemic” thinking.

While management is then left with the bigger picture of strategic thinking, and problem solving, setting the overall direction.

Now if all decisions came to management they would be ‘firefighting” not free to think strategically and often the decisions would be delayed effecting production, efficiency and safety.

Industry 4.0 Provides a Framework for Agile Manufacturing/ both Discrete and Process

Industry 4.0 is a relevant and significant shift in how industrial automation and operations management software is implemented and used to deliver significant business improvements.  However, it is too simplistic to directly apply the Industry 4.0 concepts to all manufacturing industries, or without considering industrial requirements which are not addressed by this activity.  The following is a set of viewpoints which are discussed in this white paper:

• Industry 4.0 is about the transformation from controlling focusing on process to “controlling the product/ order” and the “product/ order being self aware”.
• Industry 4.0 is about operations transformation, not about technology.
• Industry 4.0 provides a practical strategic framework for “lean” and “agile” industrial operations.
• Industry 4.0 addresses the needs of discrete and batch manufacturing, but it needs some adaptation for the heavy process and infrastructure industries.

Cloud computing and IT/OT convergence are often linked to implementing Industry 4.0, but these needs some adaptation to address “trustworthiness” of the architectures.  One emerging topic is Fog computing.

The functions and requirements of automation and operation management technology are even more relevant than before (contrary to some of the recent vendor claims).

Information standards such as IEC 61850/ISO9506, ISA-95/ISO62264, PRODML etc. are even more relevant than before .

Industry 4.0 is about the transformation from controlling focusing on process to “controlling the product/ order” and the “product/ order being self-aware”

See the full blog on:
http://operationalevolution.blogspot.com/

Blog : Shifted to New Location http://operationalevolution.blogspot.com/

You may have been wondering what has happened to blog.
They switched it to a new location, but many people seem to not have as access, or awareness.

So where is the new link: http://operationalevolution.blogspot.com/

Sorry for the confusion.

ISA-95 and Operations Transformation

Tyhe questions around S95 where and how to use continue to grow, especially as the guidance for operational system alignment, we though it was time to give an update.

The ISA-95 standard has been in place for over 20 years, and recent progress in operations management transformation and Cloud adoption have triggered questions about this standard.  The author offers an observation:

·         ISA-95 is essential for higher performing operations who are implementing sustainable improvements, in conjunction with best practices such as lean.

Higher performing operations often have the capability to achieve and sustain best practices which directly produce best business performance.  A key enabler to this improvement is exchanging operations knowledge in more detail and more frequently.  Examples include:

•          Tracking of containers in high-volume continuous food cooking, so that successfully cooked containers can be recovered after a machinery failure with compliant tracking and reporting.
•          Assessment and tracking of ore grades in mining from the pit to the port, including in the stock piles and in the rail cars, so that yields and prices can be optimized.
•          Assessment and tracking of chemical components in petroleum refining and petrochemical manufacturing, so that yields and costs can be optimized.
•          Detailed and accelerated distribution of new manufacturing instruction in consumer-packaged goods, food and beverage and discrete/aerospace manufacturing, so that new products can be introduced much faster.

Each of the above examples depend upon exchanging “insight” in great detail throughout the manufacturing/processing and its associated supply chain.  Lean principles can be reliably applied, including eliminating wasted work; specialists can reduce time spent on producing useful information and focus on continuous improvement.

ISA-95 provides an information exchange model, and standardizes how activities are defined and relate to each other, such as quality, inventory, maintenance, production and the notion of “work”.  Sets of information are exchanged as “events”, and the relationships between activities and events are standardized.  Without this information exchange model, knowledge workers don’t have a sustainable operations management system, and as a result, the organization doesn’t have sufficiently useful information.

How can architecture decisions be made?  Consider the following information model in light of the 3 implementation options summarized above:

Wherever these functions are implemented in different locations (with or without Cloud), what mechanisms are necessary for requirements such as “business continuity”, “access control” etc.?  How much context must be exchanged between sites and the Cloud to recover from network and Cloud outages?  Only an appropriately detailed and standardized information model can help.

ISA-95 focuses on the functions of operations management; it is independent of the implementation, including technology and location.  It is the foundation of high performance operations management transformation.

Operations Innovation & Transformation – Flexible Teams

The 4 quadrants described in the article “Operations Innovation & Transformation – the 4 Types” positions the lower right quadrant as a strategy for using a team of human assets in a new way.

In this quadrant, teams of specialists (with the same or different areas of specialization) are grouped to provide value improvement to a group of physical assets, and the group of physical assets can be used as a “fleet” or as a “chain”.  This is much more than a passive “help desk”.  One example is where specialists use real-time benchmarking and other tools, working with new business processes with the physical assets and the dedicated workers, to unlock value of themselves and the physical assets.

In the following diagrams, a team is located in different sites at the moment.  This example has 4 physical assets, A through D, and specialist 1 is mobile (working from a hotel, home or in an office within the enterprise), and specialist 3 is in an operations center.  In the left-hand diagram, specialist 1 is supporting or improving the performance of physical assets A and B, and specialist 3 handles the physical assets C and D.  In the right-hand diagram, a change in performance in asset B triggers a workflow and specialist 2, who is on call or is assigned by the team supervisor, handles asset B.  Specialist 1 does not receive workflows for asset B unless the team supervisor changes the assignments.  Overlapping assignments are also used, especially when multiple disciplines or specializations are involved.  Both use the same integrated and federated information, and these specialists become champions to help all like operations and equipment improve performance.

In the following diagram, a workflow “brings the work to the worker”, using the same integrated and federated information, on-line performance applications, and human workflow.  The supervisor(s) can easily change assignments, and the workflow can include escalation, which can be guided by the performance applications’ output compared to thresholds (simple calculations of time to reach a threshold).

The strength of these workflow is to help specialists intervene early enough, using standardized and trustworthy data, focused on trends.  This processing of information is automated as much as possible.

The specialists spend most of their time working on improvements instead of processing data and analyzing previous performance problems, and their decisions.  As a result, major overhauls are safely and reliably delayed, equipment performance is improved, and operators trust the equipment more to help increase performance at each physical asset.

Why is the (Level 2-3) platform key to the future state?

I seem to end up in many discussions between IT/OT, the convergence that is required in order to achieve today’s agility. It is really is the transition of existing operational / business systems from “open Loop” to “Closed Loop”. For many of us from the control world this is just extending the “closed loop” control approaches to the supervisory/ operational architectures, but with longer periods.

As stated many times we have 4 pillars of change occurring:

•        Demand Driven supply driving agility
•        Changing work force to a Dynamic/ collaborative workforce
•        Changing Workspace and process “way of working”
•        Changing technologies with Big data/ Internet of things

Driving the creation of integrated, flexible platform that bridges knowledge management, and information / decision support, while naturally absorbing change through Model Driven Architectures.

The key is applications, and capabilities will constantly evolve, change, this should not restrict the agility of the system to adopt through a platform allows new processes and loops to be put in place, but easily adopted.

The shift to closed loops where a “process” is applied to reducing variation in the speed a decision is made vs the action that is taken, and that the execution of these processes can be monitored and tuned even if it just executed across humans. Correct action maybe improving the transfer of “knowledge” so people or systems involved in the process execution have the knowledge to make the decision and act in a timely manner.  

The required platform between automation/ and business must eliminate:

•        Silos of information and control/ elimination of disconnects.
•        Elimination of disconnects thru contextualization across systems so transparency of understanding can achieved across systems.
•        Elimination of delays thru aligned kpis and targets and decision across the different levels of business control. Removing isolation of decisions and actions through integrated bossiness and control loops.

This does not mean we replace existing automation and operational systems, it means we applying new technologies to federate systems where possible, into a hybrid solution thru standards, and managed processes that can be evolved over time.