Keep every customer site and asset in the right service context.

The same customer can contain many different service contexts.

A customer name alone does not tell the technician which building, plant room or equipment record the work belongs to. That hierarchy must remain clear through the visit and report.

Move from customer portfolio to the exact maintained asset.

The hierarchy narrows each job from the customer organization to the service site and then to the equipment with its own history.

• Keep the commercial relationship together. Group the service sites that belong to the same business customer under one directory record.
• Identify the service location. Store the building or operating location that gives the visit its physical context.
• Attach work to the maintained equipment. Keep work orders, completed visits and final reports with the exact asset serviced at that site.

One fictional customer with three distinct service sites.

This controlled ilarvo directory uses fictional companies, sites and equipment. It demonstrates the hierarchy and is not customer portfolio evidence.

• Customer: Atlas Property
• Sites: Atlas House · Riverside Depot · North Campus
• Selected asset: Air Handler 04 · Atlas House
• History: Completed work and final reports by asset
• Air Handler 04: AHU-04018 · roof plant room.
• Rooftop Unit 02: RTU-22007 · loading wing.
• Chiller 01: CH-11003 · central plant.

Prepare visits for several sites without mixing equipment histories.

The dispatcher reviews work for one property customer across three sites and opens the exact asset record before assigning each field visit.

• Each visit names the customer and precise service site.
• The work order remains attached to the selected asset.
• Completed evidence returns to that asset rather than a shared customer note.

A service hierarchy built for customer equipment.

The current model connects customers, their service sites and the assets maintained at each location.

• An asset belongs to a defined customer site in the service directory.
• Service history is maintained per asset, not inferred from another site.
• Your team remains responsible for accurate site and equipment records.

Frequently asked questions

Answers about this ilarvo workflow and its current product boundary.

• Can one customer have several service sites? Yes. The service directory groups multiple sites under a customer and keeps the assets assigned to their actual location.
• Is service history shared across every site? No. Completed work and final reports stay with the asset serviced at its defined site.
• Can the site hierarchy be imported? Yes. The standard CSV structure supports linked customer, site and asset records when the source rows pass validation.