Koldheim · Jade

Assets

Operations

A register that keeps itself current.

Know what you own, who has it and when it is next due a service.

Tag, serial, warranty, condition, who holds it and where it is. Receive, assign, service and retire as guided steps, each recorded against the asset, with services raising their own task before they are due.

Book a demo Try the rule What it costs

The problem

“I do not know what we own, who has it, or when it was last serviced, and the auditors ask every year.”

What it runs

Four guided steps, not one process

Assets is unusual among the services: it is four short pipelines rather than one long one, and only the last of them needs an approval.

4 steps

Receive: what arrived, its cost and warranty, the next service computed, into store.
Assign: to whom and where, condition set to in use, the person told.
Service: what was done, and the next service date recomputed from it.
Retire: why and how. An asset manager has to agree before it is marked retired.

It opens on these

Service due in 30 days
In repair
In use
Value on the register

Every figure opens what it counts and offers the next action. Nothing here is compiled at month end.

Try the rule

Set the interval. Watch the service start.

The next service is worked out from the last one, and its run starts by itself 14 days before it is due. Retiring an asset needs an asset manager who did not ask for it.

What happens

Thu 15 Oct 2026Due within 14 days: the service run started on Thu 1 Oct 2026

Last serviced: Wed 15 Apr 2026
Service every: 6 months
Next service due: Thu 15 Oct 2026
Its run starts: Thu 1 Oct 2026

Next service worked outWed 15 Apr 2026 plus 6 months: Thu 15 Oct 2026.
The run has started by itselfOn Thu 1 Oct 2026 the daily check found it due within 14 days. It starts once; the next day's check starts no second run.
Asset managers told"Service due" for this asset, on Thu 15 Oct 2026.
An asset manager records the serviceWhat was done, when, by whom and what it cost.
Next due moves onRecorded on Mon 5 Oct 2026, the next service is Mon 5 Apr 2027: the date it was done plus 6 months. The asset stops matching the check.

Who sets what

Yours to change, and ours

Most vendors are vague about this line. Yours is everything about how your organisation works. Ours is the shape of the process itself.

Your administrators change these

Categories, and locations that nest inside one another
The service interval on each asset
Who holds the asset manager role

Authored with the service

That retiring needs an approval and the other three do not

A change here is a draft, checked and published. Work already under way stays on the version it started on.

Where it stops

The part most pages leave out

A service that only ever says yes is not evidence. This is the place it deliberately refuses, and the suite that proves it still does.

Refuses, on purpose

A service has to be started on an asset

The service pipeline opens with a rule that it was started from an asset, so starting it by hand from the service page cannot record a service against nothing.

Proof