CANUS

Expansion & changes

One programme.Every phase.Every change.

One project can grow through several deliveries, equipment upgrades and new customers. CANUS keeps the agreed work connected through those changes. We identify which earlier evidence still applies, what needs checking again and who must approve the change. Each customer's requirements and results stay separate.

Delivery checks

HOW THE PROGRAMME IS STRUCTURED

One programme.Every change connected.

  1. 01

    Project agreement

    The work, responsibilities and delivery requirements agreed with the participating companies.
  2. 02

    Delivery checks

    Checks agreed for the relevant equipment, location and customer requirements. New or changed systems may need different work.
  3. 03

    Changes covered

    Additional capacity, new customers, equipment upgrades, changes to the setup, correcting delivery problems, and an agreed replacement option for the capacity source where the parties want one.
  4. 04

    Ongoing services

    Project coordination, delivery checks, record management and agreed support for the organisations using the results.
  5. 05

    Fees

    Agreed before work begins, based on project scale, work included and ongoing services. Fees do not depend on a favourable result or funding approval.
  6. 06

    Timing

    We agree the work, site access and timetable before it starts.
  7. 07

    What is needed

    A defined project, agreed delivery requirements and the necessary participation and permissions.
  8. 08

    What you receive

    Signed results linked to the project's delivery and change history.

NO PRICES ARE PUBLISHED. SCALE, SCOPE AND ONGOING SERVICES DETERMINE THE FEE, NEVER THE RESULT.

Every phase, every change

The record follows the hardware.

Refresh, reconfigure, fix, re-lease, or change where the capacity comes from. The history stays connected; nothing is erased.

  1. 01

    First delivery

    The first agreed phase is checked against the customer's requirements and the first record issues.
  2. 02

    Add capacity

    New capacity and the existing commitments it affects. A strong campus total never hides one customer's shortfall.
  3. 03

    Upgrade equipment

    Changed hardware and configuration checked against the requirements that apply, with fresh evidence where needed.
  4. 04

    Change the setup

    Changes to network, cooling, power modes or which customer uses which block, assessed for their effect. An agreed change of capacity source is handled the same way.
  5. 05

    Fix and recheck

    The adverse result is preserved; the corrected system is independently checked again.

Try the allocation

Drag the blocks. Each customer keeps its own result.

A shortfall for one customer is not hidden by the site's total. CANUS checks each customer's reserved capacity against that customer's own requirements, and links every result to the same project.

One project · 128 GPUs · one campus

One build.Several customers.

Each customer contracts for its own block of GPUs, keeps its own delivery requirements and receives its own result. A strong total never hides one customer's shortfall.

Customer A

64 GPUS

Customer B

32 GPUS

Customer C

32 GPUS

Own scope · Own term · Own result · Own sign-off

Quantities describe contract allocations, not counts inferred from electricity or a promise that every block starts billing together.

Keep evidence that still applies.Check what changes.

An earlier result stays part of the history. Using it for a new purpose requires suitable evidence and the relevant party's agreement. A changed system does not inherit an earlier approval.

See an example