Contracts
Record the service agreements you measure availability against, with their counterparty, sites, periods and guarantee.
A service contract is the agreement availability is measured against: who it is with, the sites it covers, how its periods are cut and what it guarantees. Its designation says how each kind of downtime counts, and its availability is computed from your downtime events for one period at a time.
Open Insight → Monitor → Contracts.

Who can do what
| Role | Contracts |
|---|---|
| Viewer | Read contracts, their designations and their availability, and export it |
| Operator, Admin | Also create contracts, edit their terms and add designation versions |
Creating a contract also needs the site directory. Writing a designation version needs an installed classification vocabulary you can read.
If your plan does not include Contracts, the page says Contracts is not included in your plan. If access could not be checked, it says Contracts access could not be checked. and offers Retry access check. Neither message means your contracts are gone.
The list
Each row shows the Contract name, the Counterparty and its role, the Sites it covers (the first two, then how many more), its Period, its Guarantee as a percentage of time or production availability, and its current Designation version, or None yet.
Use Covers site to list only the contracts that cover one site. The list is sorted by name, 50 contracts a page, with Previous and Next. The filter and page stay in the page URL.
A Synthetic data badge marks a contract whose name starts with SYNTHETIC. The outlined badge sits beside the name in the list and on the contract, and again above its availability figures. Such a contract is a test built from simulated data. Its figures test the model and are not evidence about your fleet.
Create a contract
- Choose New contract.
- Enter a Name of up to 200 characters.
- Under Counterparty, choose Existing counterparty and pick one, using Find by name to narrow the choices. Or choose New counterparty and enter its Counterparty name, its Role (Manufacturer (OEM), Service provider, Owner or Other role) and, if it helps, a Note (optional).
- Under Sites covered, select between 1 and 200 sites. Find a site narrows the list.
- Choose the Period: Monthly, Quarterly or Yearly. Availability is computed for one such period at a time.
- Enter Starts on and, for a contract with an end, Ends on (optional). Both dates count in full. Leave the end empty for an open-ended contract.
- Choose the month the Contract year starts. It must start a period: any month for a monthly contract, January, April, July or October for a quarterly one, and January for a yearly one.
- Under Guarantee, choose Time availability or Production availability, and enter the Guaranteed percent, from 0 to 100 with at most two decimals.
- Choose Create contract.

The period, the contract year and the start date are fixed once the contract exists, and so is the counterparty. A new contract has no designation yet, so its availability cannot be computed until you write a first version.
Read a contract
Select a contract's name to open it. The heading shows the name and who the contract is with. Terms shows the Guarantee, the Period with the month the contract year starts, the Dates (both count in full), when the terms were Last changed, and the Sites covered.

Below the terms come Availability and Designation.
Edit the terms
Choose Edit terms to change the name, the sites, the end date or the guarantee. The dialog shows the fixed terms separately: a different counterparty, period, contract year or start needs a new contract. Choose Save terms. If nothing changed, the dialog says Nothing changed. Edit a field before saving.
A change to the sites or the guarantee applies to every period you open from then on, including past ones, because availability is computed each time you open it.
When a save does not go through
Every refusal shows the reason first, then what to do about it.
- Someone else saved first. If the terms changed after you opened the dialog, nothing is sent and the dialog says when the other change was saved. If another change was saved at the same moment, yours is refused and nothing is written. Either way, choose Load current terms, then make your change again.
- The service was busy. The change may or may not have saved. Reload before retrying. When the page names a wait, try again after it.
- Outcome unknown. If no usable answer came back, the page says, for example, Contract terms: outcome unknown and pauses the same change so it is not made twice. Choose Reload contract, check the current terms, then decide again. A refresh of the page's data alone does not prove the request finished.
- Your session changed. Reload before saving.