Pilot scoping & rollout
Scoping the first lines to instrument, specifying what to measure, and running the deployment through to live, trusted signals.
- Line & asset assessment
- Measurement plan
- Staged rollout to production
Expert hands,
when it counts.
Beyond the platform, Zoniax takes on direct engineering work — getting industrial monitoring deployed, keeping cloud systems healthy, and being on the line when something can't wait. The same engineers who build the product.
Priority support
The number you call
The number you call
at 03:00.
When a system is down, drifting, or behaving unsafely, you need an experienced engineer on the line — not a ticket in a queue. Zoniax offers priority consultation for live incidents across the platforms and systems we work with: industrial telemetry, cloud environments, and the infrastructure between them.
How it works
- Access
- A direct line to a senior engineer, available under a support retainer.
- Scope
- Live incidents — outages, unsafe drift, failed changes, security events.
- Response terms
- Response windows and coverage hours are agreed per retainer.
Getting monitoring into the plant.
Hands-on work to take an operation from unmonitored to instrumented — the engineering that sits around a Zoniax deployment.
Edge instrumentation
Specifying and commissioning sensors and edge gateways built for the dust, vibration, and heat of real production environments.
- Sensor specification
- Gateway commissioning
- Protocol bring-up
Systems integration
Connecting telemetry to the ERP, MES, and CMMS systems a plant already runs — so signals reach the people who act on them.
- ERP / MES / CMMS connectors
- Work-order automation
- Data-lake exports
Cloud systems, kept in trim.
General cloud and platform engineering — on Google Cloud, Microsoft Azure, and the systems around them — whether or not a Zoniax deployment is involved.
Cloud changes & migrations
Planned changes, migrations, and environment work across Google Cloud and Azure — executed with rollback paths, not crossed fingers.
- Google Cloud · Azure
- Migrations & upgrades
- Environment & tenancy work
Architecture & cost review
An independent read on how a cloud environment is built — for reliability, security posture, and the spend it generates.
- Architecture review
- Reliability & scaling
- Cost & right-sizing
Ongoing technical support
Continued engineering support for the platforms and systems your operation depends on — change management, maintenance, and fixes.
- Managed change windows
- Maintenance & patching
- Retainer or per-project
Audits that find the gap.
Independent review of where systems are exposed — in the cloud, and across the OT / IT boundary that industrial operations live on.
Cloud security posture
A structured audit of cloud accounts — identity, access, exposure, logging — measured against current good practice.
- Identity & access
- Network exposure
- Logging & detection
OT / IT boundary review
Examining the seam where plant networks meet corporate IT — the place industrial operations are most often quietly exposed.
- Segmentation review
- Remote-access paths
- Gateway & edge hardening
Hardening & remediation
Findings turned into a prioritized plan — and, where you want it, the hands to carry the remediation through.
- Prioritized findings
- Remediation plan
- Optional hands-on fix
Models, built to run.
The engineering behind a model, and the work that keeps it honest once it's in production. Available as an engagement in its own right — with or without a Zoniax platform deployment.
Custom model development
Models built for the question you actually have — forecasting, classification, anomaly detection, vision, and soft sensors that infer what a plant cannot measure directly.
- Forecasting & classification
- Vision & anomaly detection
- Soft sensors & process optimization
Training data & ML pipelines
The unglamorous half of the job: turning a plant's history into a training set that is clean, labelled, and reproducible — and keeping it that way as the process moves.
- Data & feature pipelines
- Labeling workflows, operator-in-the-loop
- Training infrastructure
MLOps & model operations
What happens after a model works once. Versioning, evaluation, drift monitoring, and retraining — so it stays right as the plant changes underneath it.
- Versioning & evaluation
- Drift monitoring
- Retraining & rollback
Three ways to engage.
Project
Fixed scope, fixed outcome. A migration, an audit, a deployment — defined up front and delivered to a plan.
ScopedFixed priceDefined exit
Retainer
Ongoing engineering capacity, including priority and emergency response. For systems that need a standing hand.
MonthlyPriority accessEmergency cover
Advisory
Review and guidance without taking the keys — a second opinion before a decision you can't easily reverse.
ReviewGuidanceNo lock-in
Tell us what's
not working.
Whether it's a plant to instrument, a cloud environment that needs attention, or an incident in progress — describe it, and we'll tell you plainly whether and how we can help.