The inventory and the ticket in the same record.
Asset management and service management are usually two tools, two databases and a reconciliation nobody owns. Here they are one platform: the computer that raised the alert, the case it opened, the person responsible for it and the licence it consumes are one set of related records.
Two disciplines, deliberately kept apart.
An asset and a configuration item are not the same object. One carries administrative and lifecycle control — purchase, owner, location, cost centre, warranty, contract, movements, disposal. The other carries technical and service state — what it depends on, what depends on it, what version is running. The same physical machine may be represented by both.
Dexon maintains them as distinct records connected by a governed relationship, rather than collapsing them into one. That is a deliberate choice: merging them looks tidier in a demonstration and makes both disciplines unusable, because administration and operations need different lifecycles on the same object. And because the CMDB lives in the same repository as the business architecture, the impact of a change reaches the services those items support and the business capabilities those services implement.
What it does
From the scan to the disposal certificate
The whole life of a computer, in the same platform where its incidents, changes and requests already live.
Agent-based inventory
Hardware, software, operating system, services and network of every computer, kept up to date by the Dexon Agent — an in-house agent, not a third-party scanner resold with the suite — which creates and updates the asset with its model, serial and tag, with the full hardware and software detail in the computer’s web record.
A CMDB that maintains itself →
CI classes in a hierarchical tree, explicit promotion with no duplicates, a typed and directed dependency graph and baselines the current state is compared against. Every write from the agent inventory or from an integration that brings third-party data updates the state of its item — a class configured this way keeps itself current.
Network monitoring and alarms that open cases
Network devices monitored over SNMP v1, v2c and v3: the process server, inside your network, reads them in a periodic scan, inventories them by MAC and receives their traps, which open cases by filter — devices, scan, traps and OID catalogue configured in the web console. Agent events open a case from its template, or update the open case of the same device instead of duplicating it, with an owner, a service level and an indicator. Agent alarms configured from the web: available from December 2026.
Software asset management →
Installed against licensed against used, on a licence dashboard in the web. Usage is not estimated: the agent records, per machine and per program, how many times it ran, its processor time and its first and last use — and installations unused for 30, 90 or 180 days are listed, ready to reclaim. That is what lets you negotiate a renewal on data.
Lifecycle and movements →
Status, location, unit, cost centre and owner; movements with a delivery record; entries from invoice lines — all fed by the agent inventory and gathered in the asset’s web record, with its warranties and contracts and their coverage status: active, about to expire or expired. A list shows the coverages about to expire, movements carry a signed delivery record, and consumable stock is consulted with its kardex and reorder point.
Disposal governance →
A pre-disposal workflow can require licence recovery, data sanitisation, reconditioning assessment, approval and provider coordination, holding the transition until the evidence is attached. Disposal records the method, the responsible party, the dates and the certificate.
Remote control, on the record →
Started from the computers board or from the case that has the device as related data, so the technician never leaves the tool they work in. It requires its own permission, its credential is valid for the day, and the session is recorded on the case.
Remote administration
Select one or many computers in the web console and send them an action — connectivity checks, command execution, a file explorer over the computer’s folders and remote control, each sensitive action under its own permission per profile. Full remote administration from the web: available from November 2026.
The architecture
One outbound connection, approved in one meeting
In an operation with dozens or hundreds of sites, how the agent connects decides whether the deployment is a meeting with the security team or a months-long network project.
| Question | How it works |
|---|---|
| Who opens the connection | The Dexon Server in the customer’s network, outbound, as a secure WebSocket over HTTPS on port 443, kept open — no inbound port, fixed IP, public name or own certificate, and it works behind NAT and proxy |
| Who talks to the agent | Never the browser: the screen queues the work, the Dexon Server takes it through the tunnel, runs it and writes the result, which the screen shows live |
| If the tunnel drops | The mechanism degrades to polling and nothing is lost |
| What is recorded | Every order: who asked for it, when, on which computers and with which result |
| How it is validated | Twice — the user’s permission when the work is queued, and the server’s identity when it is executed |
Precision
The distinctions this module preserves
Pairs of terms used as synonyms that are not — and asset management depends on keeping them apart.
On the roadmap
What arrives next, and when
Each item is available for a demonstration or a proof of concept from the month shown.
Full remote administration from the web
The complete set of remote agent actions over computers, from the web console.
Monitoring alarms configured in the web
Monitoring alarms that create or update tickets, configured from the web.
The proof
Certified as ITSM, on these same records
IT asset management and configuration management are two of the twelve processes Pink Elephant certified in Dexon BPM. The certification covers the same asset and configuration records described here, related to the same incidents, changes and requests — which is what “the inventory and the ticket in the same record” means in practice. And the scale is proven: an electricity company centralised the management of more than 80,000 workstations on the platform.
See the twelve certified processes →The other capabilities of Dexon BPM
Workflow
Conditional routing, parallel tasks, dynamic approvers, deadlines on business calendars and append-only history — the same engine across every record type.
ETL & integration
REST API, scheduled and event-driven exchange with databases, files and web services, plus directory, email and discovery — with the authoritative source of every attribute on record.
Documents
Version trees, permissions, search by content, signature with time stamp — with document requirements enforced as gates the workflow will not pass without.
BI & KPIs
Scorecards under strategic objectives, targets by period, drill-down from the aggregate to the source record, and projection that never overwrites a measurement.
Bring your reconciliation problem
The inventory that disagrees with the CMDB, which disagrees with finance. We would rather look at where the three diverge than tell you a single tool fixes it on its own.