The deliverables workspace is the assembly and hand-over page, not a calculation: it runs no study of its own and sends no engineering request. From the scheme library it opens a scheme and collects what that scheme already produced - the priced bill of materials, the single-line diagram and the full drawing set of the configurator engine, the design-validation result, the load flow and losses, the protection settings schedule, the cable schedule, the I/O point list and the panel list - and presents them as one package with a link into the simulator for editing. It also creates signed share links (permanent, 7 days or 24 hours) for the frozen design document and attaches the scheme link to an inquiry, so a customer receives a complete, self-contained document instead of a set of separate exports. Exported files are produced in the browser and are not uploaded anywhere.

A scheme is only worth what can be handed over: the buyer needs the priced BOM to compare offers, the drawings to see the topology, the validation and cable and protection schedules to check the design, and a link that opens without an account. Collecting them into one page with one signed link removes the most common friction in a tender round - several exports, several versions and no record of what was sent.

Chain: the page reads the selected scheme from the scheme library, resolves the design document snapshot generated for that scheme by the configurator engine (which is where the BOM, the drawings, the validation, the load flow and losses, the protection schedule, the cable schedule and the I/O list are actually computed) and renders the package overview with links; when you create a share it calls the share service, which writes the frozen snapshot, signs it and returns the identifier, signature and expiry; the inquiry posts the scheme identity together with the share link. Output = the package overview, the links into the simulator and the configurator document, and a signed share link. There is no number on this page produced by the page itself: every engineering value comes from the engine run that generated the scheme. Linkage: changing the scheme in the simulator changes its BOM, drawings and schedules the next time the document is generated, while a link already issued keeps the frozen content it was signed with.