What InnovaEdge actually does.

Devices announce themselves and are adopted into an organization. Ownership is an explicit, auditable record; unknown or conflicting identities go to quarantine rather than into an arbitrary account.

A device reports the identity it will actually publish under rather than being told what it is, and the first configuration is triggered from the device side once it lands. The path from unconfigured hardware to a device reporting home completes without a person stepping in at each stage, and a device that arrives under the wrong identity is realigned rather than left in a silent deadlock.

A device is addressed by the identity the industry already uses for it, and that is the identity it publishes and is billed under. Vendor-specific keys — a manufacturer serial, a cloud provider's internal id — are resolved at the boundary and never become the identity your fleet is organised by, so moving a device between paths does not rename it.

Every device carries a hardware fingerprint and a queryable capability set, so "which of these can do X" is a query rather than a guess.

Reusable profiles applied and published to many devices, and smart groups that address sets of devices by what they are rather than by list.

An evidence-gated discovery run learns what is on a device's bus — CAN, or Modbus stations and registers probed in batches — and promotes what answered into a draft profile. Publishing that profile creates the matching twin equipment type as well, so one act fills both what the device reads and what the ontology knows the equipment is. The recipe library grows itself.

Per-device recovery actions, LED indicator programs, WiFi profile workflows with retry and cancel, and a connectivity self-heal watchdog on the device itself. A field bootstrap credential can be minted, rotated and revoked so a device that has lost its way home can be brought back without a site visit.

A device whose clock is unset or skewed misdates every row it lands, silently corrupting every time-ordered read. Those devices are flagged with the consequence stated, not left to poison the history.

Stepped scan and explore routines per device, so an unfamiliar vehicle is characterised rather than assumed. Raw and decoded byte access.

PID discovery, probing, and per-device sweeps that walk the supported PID set and record what actually answers.

Fleet-wide position reporting on a live map, from native telemetry and from tracker hardware through the Teltonika gateway.

Geofences evaluated on the device as well as centrally, so entry and exit still fire when the link is down — stronger than the usual server-only model.

Position history segmented into trips on a reporting gap, with a bounding-box test that discards the path a parked device accumulates from GPS jitter rather than reporting it as travel. Selecting a trip draws it on the map and a slider scrubs a marker along its fixes. A trip is a view over landing telemetry rather than a stored record: the device drawer reads the last 48 hours and any window is cut off at 5,000 fixes, so a fast-reporting device is read back over less elapsed time than a slow one.

Harsh braking, harsh acceleration and idling detected from the same position stream trips are built from, weighted into a 0–100 score over the same 48 hours the device drawer asks for, with speed taken from the device's own channel or derived from consecutive fixes where it reports none. Speeding is a fourth event the scorer can count, but only against a limit passed on the API call — the panel does not ask for one and no posted limit is held per device or per asset, so in the console the scorecard is three event types. An empty window means there was no speed data in range, not a clean driver.

A vehicle's current OBD-II fault codes read off its latest telemetry and classified by system, by generic against manufacturer-specific, and by severity. A watch pass diffs each device's code set against the set it last saw and raises the transition — a fault that appeared, a fault that cleared — rather than the same codes again on every heartbeat. The severity ranking is a documented heuristic, since OBD-II defines none, and a device whose config does not report a fault register has nothing to classify.

User-defined equipment and location types built from a closed primitive set, with references, GeoJSON geometry and versioning. Model and instance are separate, as they are in a plant historian.

Asset instances with a navigable relationship graph and lineage, and a single-home device-to-equipment edge so it is never ambiguous which asset a reading describes.

Every change to a twin object or the device-to-equipment graph flows through one typed action rather than a scatter of bespoke endpoints. Each call is validated, permissioned, and written to the organization audit trail with its provenance, so what changed, who changed it and why is answerable after the fact.

Attach geofences and thresholds to a location or equipment type rather than to a device, and let the platform fan them out to every device that resolves to it. Author once, watch the whole class.

Rules defined per table and evaluated continuously, with detected anomalies queryable per table rather than only surfaced as a notification.

Offline devices, stale or rejected state, runtime faults and missing telemetry raise alerts with hysteresis, so a flapping link does not generate a pager storm.

Webhook, Slack, PagerDuty, email and SMS channels you can create, update and send a test through before trusting them. An SMS number is checked as E.164 when the channel is saved rather than when it is needed, and the provider credentials it sends through are encrypted at rest and never read back out.

Charts served inside the platform under the same login, with identity forwarded. No second user directory to keep in sync and no separate sign-in.

Daily or weekly digests of any authored table, rendered as a summary with a CSV attached and delivered through the same notification channels your alerts use. A failed delivery is recorded against the schedule rather than silently retried into a gap.

Recurring service tasks filed against the equipment rather than against the device bolted to it, due on a calendar interval, on a meter such as engine hours or odometer, or on whichever of the two comes first. Swapping the box on an asset does not take the asset's service history with it. A due item fires once per cycle through the same notification channels your alerts use — the last completion is latched, so a reminder that has already gone out does not go again on the next pass. An item can be filed on a device that is not on equipment yet, and if it triggers on a meter you are told at that point that the trigger cannot be evaluated until the device is placed and only the calendar interval applies.

A metrics catalog, background job status, fleet engine status and infrastructure health, so the platform's own condition is inspectable rather than inferred.

A per-organization bundle that packages a problem together with its context, so a question can be handed over without a round of screenshots.

Every request resolves against your organization. Fleet, tables, charts and audit are scoped to it, each organization owns a stable physical telemetry namespace, and device ownership is fail-closed.

Argon2id passwords, verified email, invitations, four roles, TOTP MFA, and OIDC single sign-on scoped to your organization so access follows the directory you already run.

A per-organization audit event stream over the state-changing surface, plus failed authorization and failed sign-ins. Exportable as a support bundle.

Broker messages, bytes, sink storage and active devices metered per organization and visible to you, so what you are billed for is something you can check rather than take on trust.

Long-lived keys for scripts and integrations, separate from login sessions. A key carries scopes that can only narrow the permissions of the person who issued it, is shown once and stored as a hash, so an integration credential can never quietly outrank its owner.

SCIM-style membership administration, enterprise SSO connectors and passkey authentication.