Hardware-Agnostic Chemical Program Optimization: Why the Software Layer Matters
Two ways to build a chemical program stack: buy a monitoring platform tied to its own sensors, or run software that takes data from any device and adds what sensors cannot measure. Prodesy is the second kind.
Two ways to build the stack
Hardware-first platforms start with a tank monitor or pump controller and add software to display it. The software is very good at showing what that device measures. Software-first platforms start with the program model, injection points, targets, products, lab tests, production, and treat every device as a data source. Prodesy is software-first and sells no hardware, so it has no reason to prefer one sensor over another.
What hardware-first platforms do well
Tight device integration, reliable telemetry on their own equipment, remote pump control, fast alerts on their own tanks. If a field is fully instrumented with one vendor’s devices and the only question is whether pumps are running, a hardware-first platform answers it well.
Where they stop
- Other people’s hardware. The previous program’s pump controllers, the SCADA on the battery and the marginal wells with no instrumentation are outside the picture.
- Lab data. Residuals, ATP, coupons, H2S readings and BS&W are not sensor outputs. Without them, the platform reports injection, not results.
- Production allocation. PPM needs the fluid volume per treatment point. A monitoring platform shows litres per day; it cannot tell you whether that was the right number.
- Vendor benchmarking. Comparing vendors needs one independent model across all of them, regardless of whose devices they installed.
- Lock-in. Optimization limited to one vendor’s hardware means the hardware decides the program.
Side by side
| Capability | Hardware-first platforms | Prodesy (software-first) |
|---|---|---|
| Telemetry sources | Own devices | Any manufacturer, plus mobile capture |
| Hardware required | Yes, theirs | None; uses what is installed |
| Lab analysis workflow | No | Water, bacteria, corrosion, residuals, H2S, BS&W |
| Production allocation and PPM | Limited | Accounting and SCADA volumes allocated per point |
| Vendor benchmarking | No | Across all vendors and all hardware |
| Client portal for vendors | Sometimes | White-label, unlimited logins |
| Cost per BOE | No | Standard dashboard |
| Scope of optimization | Injection on their devices | The whole program |
When hardware-first is the right call
A small, fully instrumented field with one vendor’s devices, no lab program to speak of and a single question, are the pumps running, is well served by the device vendor’s platform. Prodesy can still ingest that platform’s data later if the program grows.
Evidence
A Western Canadian vendor cut net treatment variance by more than 90% on mixed, existing hardware. A major producer eliminated $660,000 a month in cost variance with production data integrated, something no sensor provides. See telemetry integration and production data integration.
Frequently asked questions
Does Prodesy work with our existing monitoring platform?
Usually yes. Prodesy ingests data from device vendors’ platforms through their APIs and treats them as one source among several.
Do we have to replace hardware to use Prodesy?
No. Prodesy sells no hardware and integrates what is installed.
Is software-first slower to deploy?
No. Onboarding is 30 days because no hardware is installed; integration is configuration.
What about wells with no telemetry?
They are captured on Prodesy Mobile and can be instrumented later without changing the program.
See your chemical program in Prodesy
A 30-minute online demo using your injection points, vendors and lab data. You leave knowing where variance and cost are hiding.
Book a demo