Scope
We agree what a pilot must prove, and on which devices.
- Device and protocol list
- Network and access check
- Written success criteria
Pilot
Prove It on Your Devices
A pilot reads your real equipment before anything larger is agreed. Four steps, written criteria, a clear decision.
Scope. Connect. Prove. Decide.
Connect
Drivers and profiles are set up against your real equipment.
- Gateway installed or enabled
- Profiles built and verified
- First readings flowing
Prove
We check readings against known values and watch real operation.
- Readings matched to the device display
- Dashboards and alerts live
- Gaps and quirks recorded
Decide
You see the results against the criteria and choose the next step.
- Results reviewed together
- Rollout plan if you proceed
- Clean exit if you do not
What We Need From You
A short list, so the first days are spent reading devices, not hunting for documents.
- The list of devices with makes and models
- The protocol each device speaks and where it connects
- Device manuals or register maps for Modbus equipment
- The exported ETS project for KNX installations
- Network access for a gateway or server
- One named contact on site
Pilot Questions
Do you need access to our live control systems?
No. A pilot is read-only unless you decide otherwise. We need network access for a gateway or server and the device details.
What does the pilot cost?
Scope and cost depend on the site. Tell us what is on site and we will propose a pilot with a defined scope before anything starts.
What if the pilot shows IoTServa is not a fit?
Then you have a clear answer against agreed criteria, and the gateway and profiles can be removed without touching your control systems.
Start With One Site. Prove It on Real Devices.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.