The User Interface is Evolving from User Interface Application to Role centric and now Activity centric!!

As discussed two weeks ago this is NOW not the case, a “day in the life” of a role in the plant, (e.g. process engineer, maintenance engineer, operator) today is transient in state. Today the knowledge worker in order to execute the activity they are responsible are often required to move  out from one state, say the control room, to a local operator station, then maybe mobile. Same can happen for other roles where they are still responsible for an activity or supporting the activity when they leave the plant, so may need mobile awareness, and interaction through the web.

This has shifted people to think that we should be designing the User Interface not based on App User Interface applications but based on role.

But in the last year there has been a shift beyond this to “Activity” based, this is significant move. Meaning that operational activities with their intelligence/ information and actions need to designed so that can execute on all User Interfaces (desktop and roaming devices). The change is that due to a workers location, and plant situation the worker may have to take on new activities which are typically outside of their defined role. Matching the growing demand for agility in operational roles.

But as discussed last week the requirement for natural training and certification becomes more critical, as a worker may take on an activity due to location, and they have not performed this activity for a while so the worker must be able access an online instruction, and sign off any required training before executing the activity. When I talk about this concept people say "this is not real, what about liability?" valid question. There are many activities that can performed in a timely manner that will reduce risk to safety , environment and therefore operational continuity. Yes it is key for the worker to be able to go through an online training and certification, the system will record all actions or audit.The worker may select a “best operational practice” and the system will guide the worker through the steps, with instructions to successfully execute the activity.

So I encourage to start thinking of Operational interfaces as an interface to execute Operational activities, and what would be the “day in life” of those who would typically responsible for it.

As we move forward with evolving the User Interfaces from Invensys, expect to see more and more collaboration services which start to deliver this activity based operational interaction. But today everything I have talked about here is possible with the current tools. 

Next week I will expand on a real situation of this evolution in an Upstream Scenario...

Traditional User Interfaces have been thought of as applications, e.g. InTouch, Suite Voyager, etc., we have seen people and vendors start moving to Role based, but today the Thought Leaders are going to Activity Based, What does this mean?

Traditionally we in product development / marketing no matter what company I have worked for, we have thought about functionality relative to User Interface products, e.g.  InTouch, Information Server, Fox View etc., this was correct for the time as roles in a plant tended to be dedicated to one type of user interface and we satisfied this market by delivering a particular user interface product.

The Perfect Storm in Industrial Operations = People Excellence

The most significant disruption in operational strategy thinking is happening in this post GFC (global financial crisis) era, in determining an operational execution environment enabling timely contributions by the operational team to plant execution. The focus is on currently on operational processes, but quickly this will drive a new operational experience to go with a new operational execution plan. Traditional user interfaces will not “cut” it both in products, or the way they have been implemented. Let me expand on my thoughts on this operational experience, which I refer to as “People Excellence” driving a new paradigm of operational empowerment for all roles in plant operations.

What can you expect from this Blog??

Why a blog, what value is it to me; should I read it on a regular basis? All valid questions, and ones you should ask in this age of too much information, and too many tasks to do.

So what can you expect from this blog?  A discussion and presentation of concepts and thoughts around the today and future automation/ operational management system; what are the challengers and forward thinkers I encounter challenging me with, what is my thinking and response.

As a “System Strategist” my role is to listen and guide the Enterprise Control System to be a system, to be aligned with how people trying to solve solutions, and look ahead 3 to 5 years on what needs to be thought of. Many people say I live 3 years away from today’s reality, probably a fair statement, so treat the concept and read as that.

I work in the Common Architecture Team, which looks across the whole of Research and Development at the projects and products to make sure the architecture and functions are aligned for when you, the end user, are composing a solution out of multiple components.

With the ArchestrA platform we are well-placed for scalable / agile solutions.

In this blog I want to test concepts: after listening to many people in the industry, looking at the projects being proposed in the industry, and understanding where the constraints are, are there other ways, if not - why not?

I will update this blog regularly at least once a week with concept/ idea, thought, or feedback, and I look forward to response and discussion.

Why Enterprise Control ? Why not a traditional automation / MES like system?

No longer can we think automation/ MES system as we did in the 90s and 2000s, they will not satisfy, more importantly we cannot have many systems working in isolation, there is too much data, and speed for decisions is critical. This does not mean replace these systems (they basically work, and execute) we need to UNIFY, extend and align these into one PROACTIVE OPERATIONAL SYSTEM. This could be across one plant or across and “Industrial Enterprise” made up of multiple plants that make up the supply chain, or the operational capacity for the enterprise.

“Products and services can be copied. Our business/ operational processes and our business models are our differentiators.” 

  CEO – Global Enterprise (2011)

This quote captures a lot, products and services are commodities in this “flat world”, the differentiator will be on business and operational processes. How dynamic the business is relative to how quickly they can adapt these processes from strategy to business and operational practices and rollout across their industrial capacity into executing practices that are consistently executed.