Showing posts with label operational safety. Show all posts
Showing posts with label operational safety. Show all posts

Tuesday, April 24, 2012

Activities Behavior Starts to become Reality
As I flex back from South Africa last week I was listening to an interview on innovation, and there was interview with Microsoft Manager for Australia, and she talked about the change in culture they have implemented in the Australian offices. Switching to Activity based officers meaning that no one has a permanent seat or desk, you go in a morning and select a desk based upon the activity you are doing that day. As you may be on the road, you may be do activities that do not need you in the office, you maybe at other offices. She talked about it as a significant change in culture but it allows agility and focus to adapt your day and role based upon activities not a role.
This is the same I see in my own life and how I have discussed realtive to the Flexible Operational Team in the industrial space, these can only be achieved when people and the culture support an Activity Based thinking and Approach. In South Africa last week, I continued to see the evolution towards this thinking in mining, and food and beverage as I spoke with customers, many do not realise they on this path, yet their actions and ideas are heading in this direction.

This is no different in my life every day, I talk about my work life being in my back pack, with my lap top, IPad, mobile cell, and mobile  wireless hotspot. Based upon the activities I have that day, meetings, calls, site visits, PowerPoint presentation preparations, technology knowledge catch up, interviews,  strategy brainstorming, these are distinct activities require different modes of thinking, I choose the best environment and location for doing these.
This is very different to the way I worked 10 to 15 years ago in an office and defined role, today my activities and role change daily based on the situation and achieving our business goals and the contribution I can make each day to that, certainly my agility, and effective working time and delivery has increased.
This is the same for the industrial world and the changing approach I am seeing in the industrial place, where companies are going to the Flexible Operational Team, as mentioned a couple of weeks ago, can only be truly achieved when people are working against activities vs roles. Key to evolution is that there will be a management of activities, both planned and reactionary, which will be acted upon by the best person, or team in order to respond as fast as possible. This does not mean that people are assigned to a certain interface/ roles,  they should be able to go to best location in the plant in order to execute that activity. This is why the whole operational control is evolving to a an aligned set of systems, that allow people to access, understand and take action in the most effective place possible.


 I was in South Africa at the annual conference there, as usual I saw a lot of innovation, and thought leadership, building on what I have seen in Western Australia in the last 6 months. The big discussion was around effectively using the human asset, through "time to Experience shortening" knowledge access, and actions, and collberation.
 But you see this continued evolution from:
Applications        to        Roles        to         Activities
Activities require a change in thinking:
·         How align information and actions from different systems to enable a co-ordinated and assignable activity.
·         How the UI changes to activities with the information, ability drill and understand and then the associated actions, which may require multiple people and certain procedure.
·         Plus a culture that allows roles and people to be flexible to take on different activities in a must more agile process.
I will expect to see this activity thinking and approach accelerating over the next year but as I have said this means aligned systems, access, and contextualization in order to make it fully effective.  

Sunday, March 18, 2012

Business Control Loop Concept Critical for Continued Process Improvement.
Nearly all customers/ end users I am talking with across multiple industries have a “lean/ performance program” looking at business processes and supply chain. Many have adopted techniques such as Lean/ Six Sigma, and many have a dedicated team investigating and driving performance thinking across the different aspects of the business.
The diagram below came from ARC on a survey they did, but it is the best depiction I have seen how the leading customers gain an advantage by embedding processes vs just training and manual implementation. The leading companies are looking take this embedded process, to the operational space, and again this becomes critical in the “rotating” worker world.
In the last 5 years we have seen significant increase in so called MES applications been applied, this could be in Batch, MES, Quality, KPIs, but really what is happening is that a “Business Control Loop” is being implemented. Based on a business process the operational execution procedure best practice is implemented in a workflow/ process. This is then rolled out across multiple sites/ or like processes. This does now restrict the freedom on how to execute this process, but in turn you gain the consistency in execution, and ability to understand execution and where to improve by reducing variation. This naturally solves to issues:
·         The ability to gain consistent execution over different sites/ cultures
·         The consistency of execution across shifts/ operational teams, but most of all as we go into the transition of staff through rotating roles (discussed in early blogs “The Perfect storm in Industrial Operations= People Excellence Feb 2012”). As one customer stated we have design to assume limited experience, through embedded procedures you immediately solve this by an worker being able to understand a situation, and the associated activity and be provided with recommended procedures to work them through this.
These procedures can and should have built in help and self-training even built in certification if needed so there is a record that the worker has gone through the online training, and now the procedure will guide him through.
The leading companies are now building this capture of best practices into “embedded processes” as they learn them, even dedicating the more senior members of the team to document their experience in procedures that can be then embedded. In many ways traditional MES products with their routes and operations enforce this process in the product execution, but we now finding this happening in process and utilities.
This is why we saw the need to build in ArchestrA Workflow as a natural extension to the ArchestrA application model, not an add-on, not a BPM (Business Process tool) but as an operational process extension to the real-time supervisory and control system. Just a simple thing as an alarm can now have workflow monitoring it, based on other conditions and alarm could be generated but due to the other conditions in the plant a workflow may automatically escalate the situation and notify potentially others. What we have done is taken knowledge and built a situational aware capability, which aligned with the best practices the company wants to implement. We are seeing the same approach on NPI (new product introduction) where one of the biggest challengers is to enter the correct set-up data across multiple operational systems. The room for error is huge and lost time in revalidating and fault finding not counting lost production time and waste. Implementing procedures and alignment of data models is a big step in the correct direction. The whole focus on "Operational Safety" that naturally embeds best practices into day to day operations to avoid safety sistuations, is another example.
So when you looking at designing operational/ supervisory systems, you need to think of it not as a project but a journey. Yes the initial project gets you to a certain value and point, but the culture should be a continuous one of looking to capture best practices and embed them (so this must be a natural act not an exception), so the new value and improvements are gained for all as you learn. This requires a change in both the products vendors supply and the way in which endusers and engineering houses go about implimenting operational execution programs, but there is no choice if they are stay compeditive.