Does this create a second equipment database?

No, and that is the point. These are ordinary register rows against the customer site's stable id — no separate store, no second Asset universe, no customer equipment object. A second inventory of the same thing is how two lists come to disagree.

Can I record the nameplate details?

Yes — make, model and serial as the plate reads, plus your own label for the unit. The label is display text; the row belongs to the site by its stable id.

Does it schedule the next service?

No. It states no interval and schedules nothing. Use the service agreement or plan register for what you agreed with the customer.

Two customers have a site with the same name. Do they mix?

No. Sites are separated by stable id, never by name, so two sites called Cedar House are two registers.

Where is the data kept?

In this browser on this device.

Customer equipment register

What you look after at a customer's site — known before somebody climbs the ladder.

Known before the visit, not during it

What is on the roof, what model it is, where the access is, who installed it. The technician who has that before they arrive brings the right part; the one who does not makes a second trip.

It is a register view, not a second database

These are ordinary register rows against the customer site's stable id. There is no CustomerAsset store, no second Asset universe and no customer equipment object anywhere in this product — nothing here duplicates or competes with the equipment registry your own buildings use, because a second inventory of the same thing is how two lists come to disagree.

It schedules nothing

No service interval, no next-due date and no condition determination. What each unit needs is on its own documentation and in whatever you agreed with the customer.

Kept alongside: Service agreement register · Warranty claim log · Service plan renewal register

A register of equipment at a customer's site, kept on your device as ordinary register rows against the site's stable id. It is a register view, not a second equipment database: there is no separate store, identity model or asset record behind it. CompliMaint states no service interval, schedules nothing, and makes no determination about condition, remaining life or suitability. Everything runs on your device.

Questions people ask

Does this create a second equipment database?: No, and that is the point. These are ordinary register rows against the customer site's stable id — no separate store, no second Asset universe, no customer equipment object. A second inventory of the same thing is how two lists come to disagree.
Can I record the nameplate details?: Yes — make, model and serial as the plate reads, plus your own label for the unit. The label is display text; the row belongs to the site by its stable id.
Does it schedule the next service?: No. It states no interval and schedules nothing. Use the service agreement or plan register for what you agreed with the customer.
Two customers have a site with the same name. Do they mix?: No. Sites are separated by stable id, never by name, so two sites called Cedar House are two registers.
Where is the data kept?: In this browser on this device.