KPI tree and performance control
A good reporting structure is essential for more transparency and efficiency.
Simple key figure systems for the highest demands
Efficient performance management in a company requires more than just key figures and goals. It is crucial to make the reports are easily accessible, that opposing effects become transparent and that the key figures are interpreted in the same way across the various levels and departments. Real-time reporting, which is directly linked to the existing ERP & MES system, helps here.
The KPI tree structures the key figure system and enables smart applications such as drill-down dashboards. With the KPI driver tree, we manage to make it clear and understandable for everyone involved how the interrelationships of key figures are and how the essential can be extracted from the insignificant. We put the proper focus on the profitable activities and improvements.
The first implementation phase makes the KPIs available first in the direct areas – the shop floor and logistics are the first to be motivated to outperform the status quo within the KPI project.
Know-how for connection and implementation
Cooperative approach/development coordination of the target image with the operational units
Typical reporting problem areas and goals of smart reporting
|Production plants/logistics locations define KPIs differently||Uniform key figure definition|
|Data is prepared manually and copied together.|
Limited responsiveness, as current developments are not directly traceable.
|Certain key figures remain within the department, so you could promote processes across departments||Increase accessibility|
|No system of indicators based on a uniform database that aggregates information for each area and level and thus reduces it to the essentials.|
No cross-system key figures between ERP, MES, BDE lead to blind spots
|Reports are rigid, i.e. the clarification of a question induces a high need for coordination in the company||Enable interaction|
Interactive dashboards get to to the root of the problem
With the connection of the right BI tool for you to the ERP, MES or BDE systems, you benefit in the long term. Having a dashboard in which the relationships are summarized live and clearly is on one side. On the other hand, a well-thought-out structure of the dashboard is of crucial importance. Because this makes reports a solid tool for researching and combating causes!
If individual reports build on one another, an effect can be tracked at the top level in the levels below, and the origin or composition of the effect can be better understood. For example, productivity in a plant could have decreased. An SPQL dashboard summarizes the essential aggregated data on security, productivity, quality, and the supply chain for the internal processes. Information can be easily disseminated and made accessible through the browser-based dashboards of an established BI software. In addition, traceability is promoted and targeted adjustments are made possible.
We reflect the processes in charts and graphics
Through extensive implementations, we have the experience with your departments in the team to ensure optimal, user-friendly reporting. By connecting BI software, we also have a high level of technical understanding in production and logistics.
We pay special attention to problem interfaces typical for departments, such as sales volume vs production capacities (S&OP dashboards), as this often creates great potential in objectifying the discussion. In addition, our methodology for setting up the KPI tree ensures interactive reporting so that management through to workers and logisticians can act more responsively and efficiently.
We support you in setting up a comprehensive live analysis
Analysis & optimization of your BI solution
Choice and implementation of software that suits your company
Development of KPI trees
The right information in the right place from the shop floor to the management
With interactive live dashboards to the core of the discrepancy
Development of key figures
Systematic derivation of specific key figures
Internal know-how development through key user training
Understand the causes with interactive dashboards
We assume that a decrease in productivity has been identified in the SPQL dashboard below. For two scenarios, it is explained how you can identify a source of error using examples. Buttons and interactive diagrams are available for exploration – the data is mainly based on ERP, MES & BDE systems – if necessary, files from training systems, separate personnel systems, etc., are also stored on a server on a monthly basis.
Scenario A – Raw material quality deficiencies
In addition to the drop in productivity, we can see directly in the SPQL dashboard that there was an unusually huge number of Q messages simultaneously. Clicking on the Q messages opens a new view, and we see that a large part of the Q message „raw material defective“ has been posted. Thanks to the interactive dashboard, we can drill down one level. Here, for example, the materials and workplaces responsible for Q notifications are displayed in descending order of frequency – if the productivity analysis is carried out with a filter on the workplaces, the same productivity has been achieved as in the previous month. The connection is, therefore, clear. If necessary, measures regarding the quality must be taken with the suppliers.
Scenario B – Overworked workplace
In the SPQL dashboard, there are no other explanations apart from the drop in productivity. We go into the productivity analysis at the workplace level and see some unproductive workplaces. When changing the view to the worklist, a work centre is heavily overloaded. If we click on this, the job analysis shows us that the following jobs are those unproductive jobs. On the one hand, we now know where short-term counter-measures have to attack – at the bottleneck. On the other hand, in contrast to Scenario A, the disposition or a disturbance seems to be the background here. With another dashboard that shows the status distribution of the workplaces, we can refute the thesis of the malfunction. Because of the short-term drop in productivity, Scenario B is a unique scheduling situation.