A beverage manufacturer replaced scattered Excel reports with a shared KPI system, first in the quality team and later across the plant, using ERP integration and a clear ROI case to justify the change.
Company Profile: Beverage Manufacturing Company
This case describes a U.S.-based beverage manufacturer producing beverages for major retail customers and regional clients from one production facility.
The company employs about 230 people and produces roughly 90 million gallons per year. Raw materials arrive at the plant, beverages are produced on site, and finished goods are shipped nationwide.
Major Challenges: Shared KPI Definitions and Audit Readiness
The company had production data, shipping data, and quality data. The problem was that each department tracked performance differently, which made company-wide reporting unreliable.
- Different KPI tracking methods. Departments used their own spreadsheets or reports.
- No shared definitions. The same metric meant different things in different teams.
- Manual reporting. Managers spent hours merging Excel files every month.
- Audit readiness gaps. Evidence for quality metrics was stored separately from KPI reports.
The situation was summarized by the client:
“Each department is in some way tracking certain things, but company wide we don’t have visibility of everybody’s metrics.”
Pilot in the Quality Department and Building the Business Case
The company began with one department to prove value before rolling out the system more widely. The quality team was chosen because it had clear metrics, frequent audits, and a heavy reporting workload.
During the pilot, managers needed to explain to leadership how the change would affect cost, time, and risk. The team used the BSC Designer ROI calculator as an example model and then measured the savings in their own environment to validate the numbers. The areas in focus were:
- Reporting time. Hours spent preparing and checking spreadsheets, measured at at least 7 hours per quality employee per week.
- Error cost. Rework caused by inconsistent numbers.
- Audit preparation. Time spent collecting documents for customer or quality reviews.
The pilot showed practical improvements.
- Shared KPI definitions. Departments reported the same metrics in the same way.
- Reporting time reduction. Spreadsheet preparation in the quality team dropped by about 70-80%.
- Better audit readiness. Time needed to find supporting evidence dropped by about 90%, and internal surveys confirmed higher confidence in audit readiness.
- Better coordination. Production, logistics, and quality used the same numbers.
These quantified results helped managers present a clear case for expanding the system.
After the pilot showed clear results, the same approach was used in logistics, production, and maintenance. Scorecards for these departments were connected using the alignment functionality of the platform so management could see how departmental results supported company goals.
Evidence-Based Performance Reporting
The quality team kept evidence such as inspection reports, notes, or scanned checklists in separate folders and email threads. Finding the correct version during an audit was difficult and time consuming.
An evidence framework was defined for each KPI so teams knew what documents were required, what was optional, and when evidence had to be uploaded before a KPI update was accepted.
This reduced time spent searching for documents and improved confidence in reported results.
Connecting KPIs to ERP Data
The company exported operational data from its ERP system to CSV files and used those exports in department spreadsheets. The same files were used to populate KPI scorecards during the pilot. The following improvements allowed more stable integration:
- Connect databases directly. Reporting tables were linked so KPI values came directly from controlled data sources.
- Use API integration. Automated updates were configured so ERP data fed KPIs without manual steps.
This approach allowed the KPI system to work with existing data sources without changing how ERP transactions were recorded.
How to Justify Moving from Excel to a KPI Platform
One of the key moves in this case was the pilot with the quality department that helped quantify expected outcomes and savings and gave senior management clear reasons to move away from spreadsheets. Here are steps other organizations can follow:
- Start with one department. Choose a department with clear metrics and reporting workload.
- Measure saved time and fewer errors. Use an ROI calculator to estimate financial impact.
- Connect data gradually. Begin with exports, then automate with API integration.
- Use BSC Designer as the KPI platform. It provides structured KPI tracking, evidence links, and alignment across departments without replacing existing systems.
BSC Designer is strategy execution software that enhances strategy formulation and execution through KPIs, strategy maps, and dashboards. Our proprietary strategy implementation system guides companies in practical application of strategic planning.