Deployment
A deployment is this system, in this place, with these people near it. It holds one tier for the whole of the work, and it is the unit everything else hangs from — the item set, the record, the subscription.
New deployment
Tier
Four statements about your own site, answered before bids open. Each tier is the one below it plus one further statement, and the deployment sits at the highest tier whose statement holds of it.
Z-1 — what the system is to do
in your own words, before the statementsQ0 asks what the system affects in performing these tasks. Until they are written there is nothing for the statements to be true of, and no tier — which is what Clause 4.1 says: the task sets the answers, so the tier waits for it as the assessment does.
Form 1 — the tier
generated from the answers aboveTender list
Every item asked at this tier, with the letter that says what an unsatisfactory answer costs at this tier. The four columns show what the same item costs at each rung, so a bidder can see what changes if the site does.
| Tag | The question an assessment puts | T0 | T1 | T2 | T3 | Answers | Stage |
|---|
What you have to supply before a supplier can answer
These items are the supplier’s to answer and cannot be answered until you have furnished something. Nobody finds this out until the tender stalls.
Responses
Bidders answer their part; you see who has answered what, and what is waiting on you. Not built yet — here is what it will hold and why it is shaped this way.
How a bidder gets in
The standard decides this, not convenience. X-1 is mandatory at all four tiers: where you buy through an agent or distributor, the manufacturer countersigns the answers on D1, D3, D5 and change control, or answers them directly. And Clause 20.1 makes every answer a representation incorporated into the contract. An answer with no identified person behind it is neither a signature nor a representation — so an anonymous link cannot carry one.
Comparison
One item, every bidder, and the standard’s own yardstick above them. Not built yet.
What it will do
- Every bidder’s answer to one item, side by side, with that item’s acceptable and failing limbs printed above them as the yardstick.
- Filter to the items where the bidders differ — the only rows a procurement committee needs to read.
- Mark each answer accepted or rejected, in your name, with your reason.
Record
What was asked, what was answered, when, by whom, and what you accepted or rejected. Not built yet.
What it will hold
- The whole trail, with answers versioned and never overwritten — a correction is a new version, because Clause 20.1 makes an answer a representation in a contract and one that can be silently edited is not one.
- The ceilings under C6, computed rather than typed: the tier below the lowest tier at which the item is mandatory, unless the item states its own — and seventeen of them do.
- Export of the whole record, at any moment, in a form you can take away.
- Run again against today’s configuration. Clause 1.3 says how far this standard reaches in time: 131 items are answered at bid and 32 at acceptance, none in service. The remedy it names is the standard applied again — the four statements answered afresh, the items put again against the configuration now in service. Here that is one button and a copy of the deployment with a new date.