A lot of reactions to last 3 weeks of blogs, interest and
discussion, but that discussion has been direct with me on email or face to
face, pity as many you miss out.
The discussions reinforced that the time of model driven
operational solutions is here and not for one reason but many, and that it
really is the only way to develop an architecture that can grow in
functionality and agility and size. As well as deal with the transformation of
the operational workforce, and the new paradigm this will bring with the dynamic,
short tenure ship.
Combine this with the agility to evolve, add differential
value through the capture best operational practices, embedded them, and evolve
them.
Time and time again CEOs and COOs say as they move to off
the shelf products, their differentiation will be based on the operational
practices that put into practice.
Last week I discussed the critical move away from customization
in solutions to configuration, within the framework of the tools. A lot of the feedback,
this week, was in agreement that their existing MES type solutions either
custom( internal) or first or second generation MES with significant customization
have worked well in a STABLE operational environment. Over and over again the
comment came that it is time for change, to a system that can:
1/ Enable evolution of operational practices by capturing
the best practices
2/Rapid product introduction and evolutions
3/ the ability to scale over multiple sites in a
sustainable way with common product definitions across the sites.
4/ transparency across site and multi site eg the value
chain
5/ empowerment of decisions in the NOW and consistency of
actions across different roles, shifts
Two feedbacks this week relative to the modern
operational system:
1/ MES functionality as defined by Mesa and ISA95 is a
commodity
2/ assume operational/ production change 3/ assume
operational workforce, people transition and evolution
These are key comments when we consider why the 3rd
generation MES based upon core MES functionality in a scalable architecture
naturally extended with model driven (workflow) operational practice capture.
So I get shocked when I hear that people are still saying develop a custom MES/ MOM system, why waste the energy on a mature technology, and focus your energy on differentiating through the capture and embedding of operational practices and actions, while empowering decisions in the NOW across the operational community in the organization.?
No comments:
Post a Comment