Designations

A contract's designation decides how each downtime event counts against it. Its rules are tried in order, and an event counts in the bin of the first rule it matches. Two contracts can count the same event differently: a fault the manufacturer caused can be charged under a warranty and excused under a service agreement.

There are four bins:

Read the designation

Designation, at the bottom of a contract, shows the current version. Provenance says where its rules came from: Copied from template with the template's name and pack, or Written as explicit rules, and when it was written. Time formula and Production formula name the formulas the version computes availability with.

The rules table lists each rule's Order, what it matches under When the event matches, and the bin under It counts as. A rule matches one of:

• Category: the event's confirmed category, and every category beneath it.
• Responsibility: the event's confirmed responsibility party.
• Event origin: how the event began, for example Planned. This is how an event nobody has classified yet still takes a bin.

The last row, No rule matches, gives the bin for every event no rule matches.

When you cannot read the installed vocabulary, the rules show their codes without labels.

Versions

A designation is a series of versions. Saving adds a version; no earlier version is ever changed. Each version takes effect on a date, and on any day the version in force is the one with the latest effective date on or before it. Of two versions with the same date, the higher number governs.

All versions lists every version, highest number first:

A range ends the day the next later version takes over, which need not be the next number. A backdated correction changes how earlier periods count from its effective date on, without editing the version it corrects, so the version history still shows what was in force before.

Formulas

Each version fixes two formulas when it is saved.

P is the counted unit-time. E_pot is the potential production, L_C the charged lost output and L_X the excused lost output, all in the pack's unit. A period whose versions use different formulas is reported per version, not as one figure. See Availability.

Write a new version

1. On the contract, choose New version. The dialog, New designation version, names the version number it will save.
2. Under Rules from, choose A pack template or Explicit rules.
3. For a template, choose the Pack, then the Template. The dialog shows the template's description and rules. To adjust them, choose Edit as explicit rules; the copy is then written as explicit rules, not as the template.
4. For explicit rules, set what each rule matches on (Category, Responsibility or Event origin), the code it matches, and the bin it counts as. The controls are labelled by rule, for example Rule 1 matches on and Rule 1 counts as. Use the arrows to move a rule up or down, Add rule for another, and choose the bin When no rule matches, it counts as.
5. Enter the date it Takes effect on. The version applies from local midnight at each site.
6. Choose the Time formula and the Production formula.
7. Choose Save version and its number, for example Save version 4.

A category rule also matches every category beneath it, so put a rule on a narrower category above its parent's to override it. When a later rule could never apply, the dialog says Never applies and names the rule that matches first.

As you choose the date, the dialog says which version this one replaces from that date and, when a later version exists, until when. When the date falls before a later version's date, it adds This is a backdated correction: availability for periods from this date is read under it.

After saving, the page says, for example, Version 4 saved, in force from 1 Nov 2026.

When a version is refused

Refusals appear on the field they belong to, and nothing is written:

• A version cannot take effect before the contract starts on the date it names. Choose that date or a later one.
• Version 3 already takes effect on the date you chose. No two versions take effect on the same date; choose another.
• A rule names a category or responsibility party your organization no longer has. The rule is marked; nothing is written.
• In your installed pack a rule on a parent category comes first, so a later rule could never apply.

If another version was saved after you opened the dialog, it says A newer version was written since you opened this form and keeps your draft. Choose Review against the latest versions, check the draft against them, then save again.

If no usable answer came back, the page says New designation version: outcome unknown and pauses writing a version so it is not saved twice. Choose Reload contract and check All versions before you decide again.