Bid package — one-click export (ZIP)

Workspace id: —

Your schemes in this browser are filed under this id. It is set automatically, kept for one year and shared with the simulator and the configurator — no sign-up, nothing to copy.

Only schemes with saved parameters can be recomputed; a scheme that stored simulation results only cannot be packaged.

Everything on this page is packaged inside your browser (jszip in memory → Blob download): no server-side API is involved, so the export also works on the statically exported site. The scheme list and every engine read go to the same origin.

This page turns one saved scheme into a tender-ready ZIP. It reads the scheme from the scheme library, recomputes it on the engine, and packages five deliverable groups: drawings (vector SVG plus DXF R12 converted from the same sheets), the calculation report (every chapter the engine produced, with its basis lines and the engine fields each chapter references), the priced quotation, the bill of materials and the quantity statistics, and the grid-code compliance checklist. The file list shown here is produced by the same builder that writes the archive, and the archive carries the identical list inside _manifest.json.

A tender asks for a package, not for five separate downloads: sheets, calculations, prices, quantities and compliance have to arrive together, in a fixed order, in both languages, and they have to agree with each other. Packing them from one engine run removes the mismatch risk of exporting each artefact separately, and the manifest makes the hand-over checkable — every entry carries its byte count and its data source.

Pick a scheme (the same list the deliverables page shows) and the package language, press "Build checklist" to see exactly what will be inside, then press "Export ZIP". The archive is built in your own browser, on this page: it calls the design engine (short circuit, load flow, quantity statistics, grid-code screening) and the configurator calculation engine (sheets, priced BOM) for the same scheme, then converts each sheet to DXF, writes the report, the CSVs and the manifest, and compresses everything with a ZIP library (jszip) in memory — the finished bytes are handed straight to the browser as a Blob download. No server-side API is involved, which is why the export also works on the statically exported site. Missing data is written as an explicit DATA UNAVAILABLE note instead of an empty file, so the checklist and the archive always stay the same length.

Scope: scheme-level tender documents produced by the configurator and design engines for this scheme. The calculation report is a feasibility-grade document and does not replace construction drawings or a licensed design institute submission.