Skip to main content

The ProMISe method

Continuous improvement

Continuous Improvement by eliminating root causes and optimizing daily workflow.

ProMISe helps with incorporating Continuous Improvement as a way of working, as the improvement cycle PDCA is completely embedded in the system. It is an integral system with centralised information provision, actionlists that are transparant to everyone, and which makes datadriven work possible, or fact based management. Data is gathered by registering all disruptions in the production process. Improvement actions can be initiated based on analyses of these disruptions.

To successfully integrate Continuous Improvement in your organisation it is essential to make the employees aware of the importance of it. They are gathering the data on the workshop and can make improvement proposals. By stimulating them to gather this data as good as possible and to come with improvement proposals, in small steps you ensure greater involvement and an increased job satisfaction. A more efficient production and cost reduction are logical effects thereof.

Continuous improvement in three steps with ProMISe:

1. Collecting data

2. Verifying the data

3. Analyses and improvement actions

Collecting info

Collecting data

Improvement starts with collecting data. Registering what goes wrong as well as the effect of improvement actions. Operators register the disruptions and with their experience they can identify its root causes and suggest solutions. This can be done manually straight into the system or even make use of automated downtime registration by connecting to the PLC/SCADA systems of the machines. We also have the ProMISe App for quick and easy registration. Very useful for on-site workers.


Verifying the data

The daily meeting is an important part of the ProMISe method where knowledge and experience are being applied. Relevant employees attend this, like the production manager, head of technical services, team leaders, etc. Using their knowledge and experience they discuss the most important registrations of the previous day: were the root causes and solutions correct? Important is to give constructive feedback to the persons who made registrations. That way knowledge is shared and everybody learns from it. The logbook and action lists can be discussed, as well as iniitiating and assigning new actions.


Analyses and improvement actions

Collected information can now be converted to information by using simple but powerful analysis tools. These tools easily track down the biggest root causes of your downtime, or bottlenecks. Not only technical problems, but also logistic problems for example. ProMISe offers a holistic approach. When that is clear, you can take action to eliminate the problems and waste. This can be done periodically to initiate (bigger) improvement actions and to see afterwards if they had a positive impact. The PDCA (Plan Do Check Act) cycle is applied here. The specific OEE module quickly shows how effective the organisation operates and where the most improvement potential lies.


Improvement culture

We always advocate to create a working environment where employees are given the confidence and space to give their input for improvement and to be proactive. By having people that are motivated to do better every day an optimized production process and better results in production will automatically follow. This is the ProMISe way to create an improvement culture.

Pro's of ProMISe:

  • The improvement cycle is embedded in the system. Suitable for ISO 9001 certification.
  • It gives a holistic view of the organisation.
  • Fact-based management: Data driven production.
  • One system that gives a total view of production for the operations/plant manager.
  • ProMISe is flexible. Measure and register disruptions as YOU like.
  • Streamlined communication and provision of information via logbook and actionlists.
  • It stimulates teamwork and social interaction.
  • ProMISe is very user friendly.
  • The system is quite accessible for use for process optimization. Automation is not required for measuring disruptions.