A change record that can name what it changed.
Assets models the things an organization depends on, with relationships between them, and is now a platform app rather than a feature confined to service management. Our work is schema design, synchronization from systems of record, and connecting assets to change control.
Assets holds the objects your processes act on: devices, people, vendors, contracts, locations. It is what turns a change record from a form into evidence.
What it is
Assets models the things an organization depends on, with relationships between them, and is now a platform app rather than a feature confined to service management.
It is for organizations whose change process cannot currently answer what a change affected, which is most of them once the question is asked precisely.
What it does
Objects with relationships
Devices, people, vendors, and locations, modeled with the dependencies between them.
Synchronized rather than typed
Data arrives from the systems that already hold it, instead of being maintained by hand.
Attached to the work
An asset surfaces on the ticket and in the portal, where the decision is being made.
Where it fits
L3, governance and change. This is the layer where accountability is recorded. A change that cannot name the thing it changed produces a record with no evidentiary value, and an agent acting on the estate has nothing to reason about.
What we do with it
Schema and relationship design
Modeling what your processes actually act on, which is a design exercise before it is a configuration one.
Synchronization from systems of record
Scheduled import from endpoint and directory tooling, replacing scripts nobody maintains.
Connecting assets to change
So a change record names what it touched and an audit can follow it.
Where it earns its place
A carrier replacing scripted asset sync
Custom scripts moving endpoint data are a maintenance liability and a credential nobody reviews.
A manufacturer tracking calibrated equipment
Due dates, intervals, and ownership held where the audit already looks.
An estate where change records name nothing
The fastest way to make change control mean something is to give it objects.
Questions we get
Is this a CMDB?
Where does the data come from?
Licensing
Assets moving to a platform app changes where it is entitled from, which is worth confirming against what you currently hold. That reconciliation sits with the rest of the estate in licensing and renewals.