MESA Part 5 – Forging a Path Forward

This posting is a continuation of the “MESA to Change Direction?” posting.  This series discusses how to implement MES systems using a Business Process Management approach, looking at the manufacturing processes and then determining how to implement those processes through changes in how operators perform tasks and the technologies that enable those changes.

It’s not enough to simply hold workshops solve world hunger and sing Kumbaya.   Having a roadmap, a plan for change, and the business case to back up our claims for improvement can make it a reality.

Ok, so we’ve held the workshops…   WHOOHOO!   Exhausting as they are, we’re now armed with some fantastic information. Our four deliverables from those workshops look something like this:

To-Be Process

A process map of how each manufacturing activity will be performed in the Future State.

During the workshops, we sketched these on flip charts or whiteboards at a high level.  Afterwards, we need to create an electronic version with all the details, both in the form of a process flow map, and a textual document describing the process.  Route it through the participants and get their sign-off.   

System Footprint

A mapping of the capabilities defined in the above processes to existing systems and new systems that will be required to support the Future State.    This requires some analysis.  We’ll need to determine which capabilities (or pieces of capabilities) will be performed through modification of existing systems, and which will be performed through acquired systems.  We’ll need to identify those new systems.  How?  Because many of the MES application vendors (MES, LIMs, Data Historians, PLM, etc) have developed and market their products using the ISA-95 standard its usually a straight-forward process to map the future state processes with MES application capabilities.

Interfaces

A collection of “touch point” agreements between systems that specifies each specific interface called out in the To-Be process.   This provides the information we need to get the IT department in gear.  Probably the most important piece of this deliverable though is a Data Walk-Through.  This takes our future state process, assigns real values to the data transferred between systems so everyone can see how their processes will be expected to work.  I can’t emphasize enough how important this is.  Just seeing the real data will bring everyone down to the reality of how the new process will work.

Business Case

A high level business plan that contains:

• Description of the objectives
• A list of requirements
• A Gap Analysis
• A description of the change management issues
•  A migration plan
• Expected ROI’s by activity

Objectives – We’ve already collected these for the workshops, we just need to include them to frame the business case.  We can also provide some high level statements, from analysis of our future state and ROI, for how our new way of doing business will meet our objectives.

Requirements – Since we’ve conducted our workshops based on ISA-95 capabilities and functionality, we need to capture those capabilities and assign a priority value to each.  The intent here is to form the basis for selection of technologies and provide justification for changes in current business practices. 

Gap Analysis – Working from our list of shortfalls from the workshops we can now develop a gap analysis that describes how the new process addresses those shortfalls, or describes the mitigation plan where the processes do not address or solve the shortfalls.

Change Management – By including a change management champion in our workshop sessions, we’ve been able to collect change management issues, bring them into the discussions of future state, and begin the planning to address them.  The list of change management issues may surprise you but it’s imperative that the company is aware of and planning for the changes in how you will do business.  Change issues can range from simple tweaks to the way a department handles a transaction, to an overhaul in how documents are managed and employees are trained or certified.

Migration Plan – No matter how you will proceed, having a roadmap for how you will get there is critical.  A high level technical roadmap that calls out the order and timeframe of implementation of the systems needed to support your future state can provide the budgeting information you need to sell your program internally.   Don’t think it’s all about the budget either, having a plan for implementing fundamental capabilities or capabilities that have far reaching impact in your organization can help you transition smoothly and more efficiently.

Return on Investment – All the work we’ve done in the workshops to determine the costs of the shortfalls we’ve identified pays off here.  Remember that each workshop was set up for a particular set of capabilities or functions, and that we’ve collected the shortfalls, and the costs of those shortfalls for those capabilities.  In addition, we’ve identified estimates of lost opportunities during those workshops.  This defines our ROI for each of those activities.  Having this granular level of ROI allows us to do one very important thing, we can measure it.  Along with the identification of the ROI for each activity, we’re going to identify the KPI that measures how well we will accomplish the improvement we seek.

OK, that’s great!  We’ve got our workshop deliverables.  Now what do we do with them?

Next time – Making It Real

MESA Part 4 – Laying the Foundation for Change

This posting continues our discussion of how to apply Business Process Management methods to implementing MES. 

In previous discussions we talked about the materials we needed to prepare for a series of Consensus Workshops.  What are Consensus Workshops?  That requires a little background. 

What is a Consensus Workshop?

For the selected functional areas (see below) subject matter experts from each of the affected departments or functional areas are assembled to; review the current As-Is state and shortfalls, generate a To-Be state process flow, determine how the process flow addresses the shortfalls and the company objectives and strategy, develop a list of the gaps between the To-Be state and those shortfalls left unaddressed, and address the change management issues related to the future state processes.

What are the topics for the Workshops?

The full list of topics available for holding Workshops follows the ISA-95 Model:

1. Production Control
2. Quality Assurance
3. Maintenance Management
4. Material and Energy Control
5. Product Inventory Control
6. Production Scheduling
7. Procurement
8. R&D
9. Order Processing
10. Cost Accounting
11. Product Shipping

Some notes on this list:  You can usually combine Material and Energy Control with Production Inventory Control under a single topic Inventory Management (as it is in the MOM).  This allows you to address raw materials, WIP, and finished goods discussions in a single workshop.  If Energy Control is a significant topic, create a separate workshop for it.  Don’t discount the Cost Accounting and Order Processing discussions, they may be short but they can be significant.  For example, determining how product unit costs are evaluated can affect critical KPI’s and incentives.

How do we select the topics?

As you prepare the As-Is state process flows and gather shortfalls for the way you currently do business, a picture emerges of areas that need attention or present opportunities.  You could hold a workshop for each area of the ISA-95 model, one for all the activities in Production Control, one for all the activities in Quality Management, one for all the activities in Procurement, etc.  Do you need to hold a workshop for every area?  That depends on how comprehensively you intend to apply an MES system.  Another way to look at it is to identify those areas with the most problems and the most opportunity for payback.  It’s a trade-off, expediency and short-term payback versus comprehensiveness and longer term payback.

A few of the advantages of selecting a limited number of areas are;

• It is usually easier to determine the true ROI for change.
• It’s easier for participants to understand the value of the change. 
• It requires fewer resources to implement.  

Remember it’s a trade-off.  There are also advantages to the comprehensive approach;

• Having a full picture of the numerous and various interfaces between systems and implementing them one time is much more efficient, 
• Even if you don’t implement all of the future state or To-Be processes you will have a long-term plan to work towards,
• It’s easier to implement full-scale change while you have your foot on the gas.

Next Time:  Creating the Framework for Change

MESA Part 2 – Business Process and MES

This posting is a continuation of the “MESA to Change Direction?” article that pointed out the results of an Aberdeen Group survey suggesting MESA may want to emphasize Business Process Management approaches to MES implementation.

It’s Not an IT Initiative

Most MES practitioners have been through the following scenario…. The client asks you to implement an MES package and gives you a set of requirements for configuration.  The IT Team is the only source of information you have.  It’s an IT initiative.  Requests for Production, Quality, Maintenance, and Engineering participation fall on deaf ears, token attendance at meetings is the best they can do.  You know it will be a disaster.  IT will love it, production won’t use it, cost accounting could care less, quality is mad, and engineering will do everything in its power to subvert it.  It will be dead before it hits the first terminal.   Besides the change management issues here, there is an obvious gap between the top floor and the shop floor.  Production, Quality, Engineering, and Maintenance not only need to be part of the change, they need to be driving the change.  Methods for Business Process Management really can help.  Combining BPM with the ISA-95 model is even better.  The ISA-95 model (part 1 and part3) does a great job of outlining the manufacturing activities that 99% of all manufacturers do now, or should do.  They also suggest how those activities might interact with others.  This is the real power of the ISA-95 standard, it provides a basic template to help companies organize, review, and improve how they do business.

Game Plan

Combining the ISA-95 model and Business Process methods is really very straight forward:

• Provide Focus – Get the company objectives and strategies from the top.
• As-Is State – Determine how manufacturing activities are currently performed
• Future State – Hold Consensus Workshops to determine how activities will be performed in the future
• Roadmap – Develop high-level process flows, requirements, and how they fit into a timeline

Providing Focus

Effective BPM relies on a cohesive and coherent framework.  It is absolutely critical that top management provide that framework in the form of goals and objectives for manufacturing.  For example, the VP of Operations may have objectives related to product mix and manufacturing flexibility.  The VP of Quality may have objectives related to minimizing and tracking product escapes.  Those objectives provide the constraints and focus for consensus workshops used to develop new or improved manufacturing/business processes.  This seems extremely obvious, but the simple process of getting the message from the top and using it to provide focus during discussions is invaluable. 

As-Is State

There are three universal truths about a Company’s thinking on the way they currently do business:   1) They’re pretty sure the right people know how it works, 2) It isn’t true, and 3) They really hate putting it down on paper.

The second item becomes clear when a company actually does put it down on paper.  Yes, Betty in procurement knows exactly how to order inventory restock from consumed inventory last month.  She doesn’t know how Bill the Production Manager counts production and consumes inventory.  Getting it down on paper lets both parties see the bigger picture.  This is key if you want both parties to understand the value of information exchanged between functions.   And you do.  Determining the impact of shortfalls and improvements requires this more holistic view.

Using the ISA-95 activity model is a great place to start discussions on the As-Is state.  As an example, consider the following activity descriptions:

2.0 Production Scheduling	Description
2.1 Availability	The ability to determine the availability of all resources required to produce items contained in a production order.  This may include raw materials, labor, and equipment availability and/or capacity.
2.1.1 Provide finished goods availability to Order Processing	The ability to provide the availability of finished goods inventory items.  This allows the planner to plan production for the shortfall between requested sales order quantities and existing finished goods quantities for that item.
2.1.2 Provide available production capacity to Order Processing	The ability to determine the capacity of the available equipment necessary to produce a given item.

 

These activity descriptions provide a guide and a focus for subject matter experts , SMEs, during discussions and laying out the process flow for each activity.  What’s a process flow?  It’s a way to graphically represent what’s going on in each activity.  Here’s an example:

 

Process flows show the high-level activities and how they exchange information with different functions and resources.  It’s a great way for SMEs from adjacent functions to understand what is happening without getting bogged down in the details.

An important second step in putting together an As-Is state is identifying the shortfalls.  This should be an issues list with examples.  Assigning a SME to determine the costs associated with a shortfall, based on the example, is a great way to begin to identify both the cost of doing business, and the potential ROI for future change.

Next time:  Developing the future state.