KPI 01
Read success rate
How many of the expected packets arrive on time, reported separately by coverage class.
PILOT PROGRAMME
Not a demo — a measurable pilot
The riskiest part of a smart metering investment is scaling assumptions that were never validated in the field. A pilot keeps that risk small and reversible.
WHY A PILOT
“Ask for a demo” replaced by “let us measure”
A demo shows what the device can do in a laboratory. A pilot shows what happens in your network, with your operator and at your difficult installation points. The decision needs the second one.
That is why we write the success criteria together before the pilot starts. If criteria are written afterwards, the result always looks successful — which is no help in deciding.
PILOT FRAMEWORK
A pilot in eight steps
The duration and scope of each step vary with project size; the sequence usually stays the same.
Target country, operator and SIM profile
Which operator, which band and which subscription model will be used is decided. Roaming coverage is settled where required.
Selecting installation points
Representative points are chosen in the easy, medium and difficult coverage classes. Difficult points are included deliberately; a pilot is not run only at the best locations.
Writing the success criteria
Which indicator must pass which threshold for the pilot to count as successful is written in advance, together with the measurement method.
Meter, valve and data testing
Index accuracy, completeness of data fields, alarm generation and valve command results are validated step by step.
OTA rollout trial
A firmware rollout is run on the pilot group; success rate, retry count and interruption behaviour are recorded.
Integration trial
Data is fed into the utility's HES/MDM, SCADA or GIS system. Field mapping, timestamp consistency and index reconciliation are checked.
Battery and signal measurement
A battery consumption model is derived for the chosen transmission profile alongside measured signal quality; difficult points are reported separately.
Result report and scaling decision
The outcome is assessed against the criteria written in advance. The report lists the scope to scale, the topics to fix and the open risks together.
PILOT KPIs
Indicators whose targets are written before the pilot
We do not publish target figures for these indicators. Targets are set together, based on the utility's current position and network conditions.
KPI 02
Data latency
P50 and P95 times between the moment of measurement and the data being visible centrally.
KPI 03
Missing and duplicate packet rate
A measure of data completeness; it directly affects how far analysis can be trusted.
KPI 04
Signal quality distribution
The distribution of measured signal values per point and the share classed as difficult.
KPI 05
OTA rollout success
The share of devices completing an update in one rollout and the size of the retry queue.
KPI 06
Valve command success
The rate at which commands are applied successfully and the time from command to a confirmed state.
KPI 07
Projected battery consumption
Measured consumption per device under the chosen transmission profile, and the life estimate derived from it.
KPI 08
Integration time
The working days needed before data flows into the target system, and the team effort spent.
KPI 09
Number of field interventions
How many events during the pilot required physical intervention, and the distribution of causes.
These indicators are not a performance commitment. Measurement method, sample and acceptance thresholds must be agreed in writing before the pilot begins.
OUR SIDE
What İnodya provides
- Pilot devices, the mounting guideline and antenna placement support
- Device service access, the data flow and OTA rollout execution
- Technical contact and field mapping support for integration
- A pilot report containing the measurement results and an open risk list
YOUR SIDE
What we ask from the utility
- Identification of installation points and access permission
- A decision on operator/SIM preference and the necessary approvals
- A technical counterpart on the target system (HES/MDM, SCADA, GIS) side
- Writing the success criteria together and an end-of-pilot review meeting
NEXT STEP
Start by measuring in your own network
Let us validate the coverage, data, battery and integration assumptions together in a limited pilot. We write the success criteria before the pilot begins.