Concept map

This page shows how the parts of the app fit together. Each concept has its own page with the details.

The parts in one line

Concept	What it is
Company	TBA, a client or a provider.
User	A person from a company who logs in to the app.
TBA contract	The framework contract between TBA and a client.
Service contract	The contract with a provider for one service type on one or more assets.
Asset	A building, or a floor or premises inside one.
Installation	A specific piece of equipment in an asset: a lift, a boiler, the fire-detection system.
Maintenance plan	The schedule that generates the preventive maintenance jobs.
Maintenance job	An intervention by a technician. It can be preventive, corrective or predictive.
Inspection	A regulatory check by an inspection body.
Document	A quote, a report, a certificate or an invoice that the FM validates.
Invoice	What the provider bills TBA for a contract instalment or for an approved quote.
Alert	A warning about something that falls due soon.
Provider evaluation	The score TBA gives a provider.

Three rules that explain almost everything

1. The FM validates everything. Each document a provider uploads waits for validation by TBA's facility manager. Without validation, the job does not close and the invoice does not go to the client.
2. States are calculated. Nobody changes a state by hand. The app works it out from the dates and the documents.
3. Nothing is deleted. Records are terminated or cancelled with a reason. Rejected documents stay, and their replacement appears next to them.