Composite Frameworks What are They, the shift to Model Driven vs Custom: How do they Play?

As we look at MES and Operational solutions the role of the consistent operational execution and experience is key to achieving operational consistency. No matter the product at the back end the "operational experience" must be role based and transverse the products in the back end, and transform the experience from application configuration to "task/activity" based experience.

Traditionally companies have built User Interfaces to an API, with the calls needed to execution actions and transactions; these have worked well especially within a plant. But a key to operational systems being effective and agile is their ability to adapt on a regular basis, this requires a sustainable and evolving system. This is especially important in form/ transaction activities where information is provided and where actions/ data input, and procedures  that need to be carried out. But the challengers of operational procedures:

1. Operational Process cross-over functional domains and applications
2. Lack of governance
3. AgilityResponsive manufacturing business processes
4. Increase the performance of their people assets
5. Too much Custom Code, making it unmanageable and evolutionary

So like the Business System who started introduce BPM (Business Process Modeling) leading companies in the industrial space are looking and asking why they cannot apply the same techniques in the Industrial/ production sector.

There is no reason why not! Yes the time line is more real time, triggers are real-time, and we many roles with different time dimensions. But this also aligns with what the industrial world is very comfortable world with that of “stable in control loops” we do this in automation with feedback (information) and correction (actionable procedures), what we are looking at are “operational loops”.

Providing a graphical configuration environment for the capture and defining of operational process including the validation of data input, and guide actions, working inline with the user Interface/ forms etc. Providing a framework for building of reusable forms, and reusable procedures that can be managed as templates and standards to enforce consistent operational practices. Empowering the operational domain people to develop, evolve and manage their procedures.

Most of all empowering the different roles in the plant, that operational close loop moving to an “activity” centric system where information, and action is driven from a consistent operational model and practices.

A New Approach is Required to Enable It/OT, with Information Driven Systems!

Two weeks ago I wrote about IT/OT convergence, and some thoughts, while the convergence has been happening for years.It seems only lately that we running into the significant step of changing the organization from tradition structures to a modern / new generation Operational IT approach. But the interest in that blog post was significant, with many hits, and many direct emails on ideas, comments.

The fact that 4 significant companies I have visited lately that we find that the head of the traditional IT team, and strategy is someone from Operations, with limited traditional IT experience, but huge amount of Operational and Business experience. The strategies are now not about the technology they lead by an business/ operational value, and how do deliver solutions fast, and efficiently, with technology and systems that are sustainable, and evolutionary.

In the information driven space this is giving rise to a different approach:

Strategies are more than technology, the key is operational cultural transformation that includes device, equipment integration, with people, and alignment and repeat ability through process integration. Leading to strategies as seen below.

The strategies require a focus on accessing the correct information, in context, and understanding the business process design, building on repetitive foundation of standards that can evolved. Understanding that standards and a platform is key to maintaining the evolution over multiple vendors.

Below shows a concept of the three levels of maturity on the journey that is required to bring information under control and effective. This aligns with the “Knowledge/ Wisdom” discussions we have had at the end of last year.

How many of you are moving to platforms for aligning multiple vendors, while moving away from custom code to configured standards for information context and procedures?