Line installation software for scopes measured in stations, not in square metres.

The line is modelled as stations and cells, each holding its mechanical assemblies, drives, robots, safety devices, sensors and control panels.

Layouts, equipment lists and I/O schedules are parsed into the register, so the I/O checkout list and the installation list are the same list.

Progress rolls up from device to station to line without anyone rebuilding a summary.

The site acceptance certificate lists exactly which records permitted it — I/O checkout, safety circuit validation, robot cell validation and the cycle-time proving run result — and which punch items were carried, with owners and dates against every one.

That is what turns final payment and rate qualification into a documented event rather than a dispute between the supplier and the plant.

Carried items stay live in the same register through ramp-up until they are closed.

Passing a single dry-run cycle is a very different claim from holding target cycle time across a shift, and a different claim again from surviving a product changeover without the cycle time collapsing. Buyers and plant managers who have been burned before know to ask for all three separately, and they ask for the changeover trial results by product variant, not as an average.

Deskely records the cycle-time proving run as its own test against the line, with the measured cycle time, the target, and the variant under test held on the record. Where the line runs multiple SKUs or vehicle variants, each changeover trial is its own record against the station and tooling involved, so a supplier cannot claim rate qualification on the strength of the one variant that ran cleanest.

That distinction is what protects the plant during final payment negotiation with the integrator: the site acceptance certificate proves the line was built and functions; the rate qualification record proves it will actually hit the number the business case was written against.