The platform through the user's eyes: who signs in where, what they see, what they do.
The platform models a distribution company's operating structure as four units. Each service has its own menu and its own permissions; one sign-in is valid across all of them. At sign-in you are shown the services you are entitled to.
Every unit in its own console, on one sign-in.
General Operations
- Pool: work orders not yet routed
- Board: the five unit queues at a glance
- Alarms: faults, tampering, communication
- Map: meter and work order locations
- Read quality and SLA report
Field Management
- Assigned to me / assigned to my team
- Start · hold · complete · result note
- Meter selection on installation and removal
- Photos, seal number, index entry
- Team and chief management
Depot Management
- Intake depot: lot acceptance and stock
- Inspection depot: examination and exit decision
- Calibration: inspection calendar and result
- Supplier Return and Scrap: shipment and disposal
- Exports and depot reports
Technical Operations
- Command centre: valve, clock, parameters
- Firmware: signed campaigns, pilot and rollout
- Inside the meter: connection, keys, diagnostics
- Dual approval: the preparer cannot approve
- Data request work orders
Every job enters by the same door and passes through the same chain.
Alarm, field finding, subscriber request or planned maintenance — it makes no difference: every job lands in the General Operations pool. From there it is routed to a unit; the unit manager assigns it to a team or straight to a person, the team chief assigns it to a person, that person carries it out and writes the result, and Operations closes it. If the source was a subscriber request, the subscriber is notified at closure.
- 01Pool
- 02Route
- 03To the team
- 04To a person
- 05Carry out
- 06Close
Sees the whole unit and assigns.
Sees their own team and assigns.
Does what falls to them and writes the result.
In a unit with no teams defined, everyone sees the unit queue.
Five depots, one door.
Every meter removed from the field (calibration removals aside) enters the Inspection depot and can go nowhere until it has been examined. The examination has four exits: Intake (sound, back to stock), Calibration (measurement in doubt), Supplier Return (warranty), Scrap. A meter suspected of theft or tampering is locked with a hold flag until the legal process ends.
| Depot | In | Out |
|---|---|---|
| Intake | New acceptance, returns from the manufacturer, sound units from Inspection | Installation in the field |
| Inspection | Every removal other than calibration | Intake · Calibration · Supplier Return · Scrap |
| Calibration | Expired validity, measurement in doubt | Passed → Intake; failed → Return / Scrap |
| Supplier Return | Warranty, manufacturing fault | Shipment; a returned meter enters Intake as a new acceptance |
| Scrap | End of life | Disposal record |
Your administrator opens the account; you choose the password.
No temporary password circulates, one session is valid across every console, and two-step verification can be made mandatory by company policy.
- Invitation
A link and a six-digit code arrive by e-mail and you set your own password. For staff without an e-mail address, their manager issues a single-use activation code.
- Sign-in
E-mail, phone or employee number, plus a password. If you are entitled to more than one console you pick a service; the choice is remembered and can be changed from the top bar.
- Two-step verification
Set up from Settings with an authenticator app; eight recovery codes are issued. Company policy can make it mandatory for managers or for everyone.
- Forgotten password
A code is sent to the registered e-mail address; a new password closes every open session.
- Password rule
At least 12 characters; it cannot contain your name or e-mail address and cannot appear in known breach lists. No complexity rules and no forced periodic change.
Touch the meter and it leaves a trace in four places.
Tampering is not a single alarm. It starts in the meter, is seen in the field, is protected in the depot and is constrained on the command side. All four are part of the same record and none stands in for another.
- Top cover, battery cover and magnet are each recorded separately
- An attempt counter rises with every event
- Reverse flow, air and out-of-range are flagged metrologically
- Only an authorised operation clears the record
- The technician closes the finding with a photo
- The seal number is written onto the work order
- The removal reason is chosen from a coded list
- A suspect meter stays in the Inspection depot
- A hold flag locks it in place
- It cannot go to scrap or the manufacturer until the legal process ends
- Whoever prepares a valve command cannot approve it
- The command is signed on the server and verified in the meter
- Who, when and why — all in the audit log
A one-page answer for a tender specification.
| Heading | Platform |
|---|---|
| Meter type | Smart gas meter; measured (Vm) and converted (Vb) volume |
| Protocol | REST (signed) and DLMS/COSEM · IEC 62056 |
| Communication | NB-IoT cellular; optical port for local service |
| Data objects | UNI/TS 11291 event and data objects |
| Meter security | Secure element, ECDSA packet signature, signed firmware, tampering recorded from four sources |
| Server separation | Meter core and console server are separate, with a one-way relationship |
| Console security | Accounts by invitation, two-step verification, single sign-on, idle limit |
| Authorisation | Four units, three grades, separation of duties, dual approval on critical actions |
| Depot model | Five depots: Intake · Inspection · Calibration · Return · Scrap |
| Verification | Per-meter validity date, a calendar out to ninety days, bulk removal |
| Integration | Master data file, period index file, REST API, webhooks |
| Records | Audit log and API usage ledger, exportable |
| Deployment | Cloud service; with master data ready, company setup and first load the same day |
From lot acceptance to disposal, every step on record.
Every step produces a movement record and an audit entry; inspection validity is tracked on the calendar.