We’re setting up performance analysis workflows in GPSF 2023.2 and debating between using the built-in KPI dashboard features versus developing custom reports through the workflow API. Looking for perspectives from others who have made this decision.
The built-in KPI dashboard has pre-configured metrics (OEE, cycle time, throughput, etc.) and seems easy to deploy. However, we have some unique performance metrics specific to our industry that may not fit the standard templates.
The custom reporting approach using the workflow API would give us complete flexibility to define exactly what we want to track and how it’s calculated. But it requires development effort and we’re concerned about maintenance overhead and whether we’d lose out on future enhancements to the built-in features.
What factors should we consider when deciding between these approaches? Has anyone successfully extended the built-in KPI dashboard to accommodate custom metrics, or is the workflow API the better path for specialized reporting needs?
I’d actually recommend a hybrid approach. Use the built-in dashboard for standard manufacturing KPIs that everyone understands - OEE, downtime, scrap rates. Then develop custom API-based reports for your specialized metrics. This gives you the quick wins from the dashboard while addressing unique needs through custom development. The workflow API integrates well with the dashboard, so you can even embed custom metrics into dashboard widgets.
We went with the built-in KPI dashboard initially and regretted it. The standard metrics were fine for basic monitoring, but as soon as we needed custom calculations or wanted to correlate data from multiple sources, we hit limitations. The dashboard is great for out-of-the-box scenarios but isn’t designed for complex analytics. We eventually built custom reports using the API anyway, so we wasted time on the dashboard implementation.
One consideration that often gets overlooked - think about who will maintain and update these reports over time. The built-in dashboard can be configured by power users without coding skills. Custom API reports require developer involvement for any changes. In our facility, the CI team wants to tweak KPI definitions frequently as we optimize processes. Having reports that require developer time for every change became a bottleneck. We migrated back to dashboard-based metrics where possible.
The hybrid approach sounds promising. Can you elaborate on how to embed custom metrics into the dashboard widgets? We’d like to maintain a unified view rather than having users switch between the standard dashboard and separate custom reports. Also, what’s the typical development effort for creating custom reports through the workflow API - are we talking days or weeks per report?