Skip to content
Case StudyNov 20228 min read

Case Study: GPI — Smart Factory Monitoring for a Precision Manufacturing Operation

Smart FactoryVX-Olympus
smart-factorycase-studyprecision-manufacturingfuel-transactionsmulti-role-hierarchyvx-olympusequipment-monitoringindustrial-iot

Background

Great Plains Industries (GPI) has been designing and manufacturing precision flow measurement equipment since 1968. Their meters, pumps, and fluid management products operate in some of the most demanding industrial environments in the world — fueling operations, chemical processing, agricultural distribution, and oil and gas transfer. Accuracy is the product.

Running a precision manufacturing operation that makes fluid measurement equipment creates a certain operational irony: the company that builds meters for fluid accountability needed better fluid accountability in its own manufacturing environment.

But the operational challenge at GPI extended beyond fluid transactions. They needed a platform that could manage a multi-role operational hierarchy — different visibility and control permissions for operators, supervisors, managers, and executives — while providing unified equipment monitoring, transaction logging, and operational analytics across their facility.

Their existing systems addressed these problems in silos. Fluid dispensing was managed by one system. Equipment status was maintained in another. Operational reporting was assembled manually. No single view connected all three.


The Challenge

GPI’s operational requirements mapped to three distinct problem areas:

1. Fluid Transaction Accountability

GPI operates multiple fluid dispensing systems across their manufacturing environment — machine coolants, hydraulic fluids, and process fluids. Each dispensing event needs to be attributed to a specific work order, a specific machine, and a specific operator for cost allocation and inventory accountability.

Without transaction-level attribution, fluid costs were allocated to manufacturing overhead as a lump sum — invisible at the cost-per-unit or cost-per-machine level. Process improvement decisions required knowing where fluids were actually going, not just how much was dispensed in total.

2. Multi-Role Operational Hierarchy

GPI’s operational structure requires different information and control access across roles:

  • Floor operators: Need to log fluid transactions, view their assigned machine status, and report issues. Do not need — and should not have — access to facility-wide equipment data or cost analytics.
  • Line supervisors: Need visibility into all machines in their production zone, active alerts, and transaction logs for their team.
  • Facility manager: Needs full equipment visibility, maintenance history, transaction analytics, and alert management.
  • Operations director: Needs aggregate metrics, cost analytics, and exception reporting — without being buried in individual machine alerts.

No single system they evaluated provided this level of granular role-based access control over an integrated operational data set.

3. Equipment Visibility and Maintenance Coordination

Equipment downtime visibility was reactive. When a machine stopped, the line supervisor found out when production stopped. Maintenance response was initiated through informal communication (verbal reports, radio calls) rather than a systematic workflow.

GPI’s maintenance team spent 30–45 minutes of every downtime event diagnosing the problem — with no prior visibility into the equipment’s recent operational history, recent alerts, or previous maintenance actions.


The Solution

VX-Olympus was selected after a 6-week evaluation process that included one in-house development estimate (18-month timeline, $1.2M) and two alternative platform evaluations.

The deployment was structured in two phases:

Phase 1: Fluid Transaction Monitoring (Weeks 1–6)

VX-Olympus integrated with GPI’s fluid dispensing systems via Modbus interface — reading dispense event triggers, volume measurements, and dispenser ID from each dispensing point. Each dispense event was enriched by the operator scanning their badge at the dispenser terminal (integrated with the existing badge reader system via webhook), creating a transaction record with:

  • Operator ID
  • Dispenser location
  • Volume dispensed
  • Timestamp
  • Associated work order (entered by operator on a simple touch-entry panel at the dispenser)

These transaction records flowed into VX-Olympus in real time. The facility manager’s dashboard showed total dispensing by fluid type, dispenser, and operator for any time period. End-of-month reconciliation — previously 8–12 hours — reduced to a report export.

Phase 2: Equipment Monitoring and Role Hierarchy (Weeks 7–16)

VX-Olympus connected to production equipment via Modbus and OPC-UA:

  • CNC machine tools: Running/stopped status, fault codes, spindle hours, cycle counts
  • Coolant systems: Coolant temperature, flow rate, pump status
  • Compressors and air systems: Pressure, temperature, motor current
  • Assembly line equipment: Production counter, cycle time, fault status

The multi-role hierarchy was configured:

Role Scope Access
Floor Operator Assigned machines only View status, log transactions, submit maintenance requests
Line Supervisor Production zone All machines in zone, alerts, transaction logs, maintenance queue
Facility Manager Full facility All equipment, maintenance history, cost analytics, alert management
Operations Director Executive view KPIs, cost analytics, exception reports, trend analysis

Alert routing was configured to match the role hierarchy:

  • Machine-level fault: floor operator and line supervisor notified immediately
  • Unacknowledged fault (30 minutes): facility manager notified
  • Production impact (line stopped): operations director notified

VX-Olympus’s Node-RED rule chains handled the escalation logic — no custom code required.


The Results

Fluid Transaction Accountability

End-of-month fluid reconciliation time dropped from 8–12 hours to under 30 minutes. The monthly reconciliation report now showed:

  • Volume dispensed by fluid type (coolant, hydraulic, process)
  • Volume attributed by work order (what percentage of each fluid type was attributed versus unattributed)
  • Volume by machine — which machines were consuming the most coolant, flagging machines with abnormal consumption for maintenance review
  • Operator-level transaction logs for accountability auditing

Unattributed dispense events (transactions without a work order association) dropped from 23% of total dispense events to under 4% within 60 days — as operators understood the attribution expectation and the floor-level workflow made attribution easy.

Equipment Visibility and Maintenance Response

Average downtime-to-notification time dropped from 30–45 minutes to under 3 minutes — alert fires immediately on fault detection.

The maintenance team, arriving at a machine with a VX-Olympus fault alert in hand, had context before they arrived: the fault code, the timestamp, and the machine’s recent operational history (last 4 hours of telemetry visible in the alert detail view). Diagnostic time at the machine — the 30-minute problem-identification period — compressed to 5–10 minutes in most cases.

VX-Olympus rule chains flagged equipment drawing elevated current (a bearing wear or lubrication issue indicator) before fault codes fired. In the first 3 months post-deployment, 4 maintenance actions prevented downtime before failure occurred.

Role Hierarchy Adoption

The multi-role hierarchy was adopted with minimal training friction. GPI had a history of staff complaining about information overload in operational systems. The role-scoped views addressed this directly: operators saw exactly what they needed (their machines, their transaction history) without the noise of facility-wide alerts that were not their responsibility.

A floor supervisor commented that the change was immediately useful: “Before, I had to either walk the line or call someone to know the status of my zone. Now I open the dashboard and it’s there.”


Implementation Notes

What Worked Well

The Modbus and OPC-UA integration was straightforward — GPI’s newer CNC machines were well-documented and the engineering team provided register maps. Legacy equipment (one compressor system from 2003) required a VIA instrument integration to expose its operational data via a Modbus gateway.

The badge reader integration for operator identification at dispensing points was a 2-day integration effort with the existing access control system vendor. This was critical for attribution accuracy — without automatic operator identification, the burden of transaction attribution would have been entirely on operators to self-report.

What Required Adjustment

The initial escalation timing on fault alerts — 30 minutes to facility manager — was too long for some production-critical equipment. GPI reconfigured their most critical machines (the 5-axis CNC centers) to notify the line supervisor at 5 minutes and the facility manager at 15 minutes if unacknowledged.


Timeline

timeline title GPI Deployment Timeline Weeks 1-6 : Phase 1 — fluid transaction monitoring live Weeks 7-10 : Equipment connectivity and role hierarchy Week 10 : Full production operation Month 3 : 4 proactive maintenance actions from current alerts
Scroll to see full diagram

Conclusion

GPI’s VX-Olympus deployment solved a specific set of problems that the company had been managing manually: fluid transaction attribution, multi-role operational visibility, and equipment monitoring with appropriate alert routing.

The deployment from pilot to full production in 10 weeks — significantly faster than any in-house development path. The platform’s multi-tenant RBAC, multi-protocol connectivity, and visual rule chain configuration handled GPI’s requirements without custom development.

For a precision manufacturing environment where accountability and operational rigor are core values, VX-Olympus provided the operational layer that made those values executable — not just aspirational.


Talk to our team about a smart factory monitoring deployment for your manufacturing environment.

Ready to see how this applies to your operations?

Every article describes real capabilities you can deploy today.