Report

This page turns one engine run into the design document of a scheme. The chapter skeleton is the one the engine declares, with a fixed eleven-chapter base (topology, basis, load flow, short circuit, withstand, harmonics, protection, motor starting, losses and economics, grid compliance, conclusions) to which the engine appends further chapters only when the matching data really exists — multiple sources and operating mode, loss allocation, the cable four-fold check, protection coordination, the DC network, three-phase unbalance, transformer thermal ageing, the time series, earthing safety and island operation. Every chapter is listed with its engine key and its basis statements and shows the engine fields it refers to together with the value the engine actually returned; the structured conclusions, the modelling assumptions and their boundaries, and the traceability block (engine version, code fingerprint, parameter fingerprint, data-source versions and duration) come from the same response. The page adds no chapter, no number and no wording of its own. One button writes the whole document to a self-contained HTML file with its own print stylesheet.

A calculation report is what a design review, a tender or a handover actually exchanges: it has to state what was calculated, on which basis, with which assumptions and with which version of the engine and the data, so that any number can be traced back to the run that produced it. Publishing the conclusions and the assumptions together is what stops an order-of-magnitude assessment from being read as a construction guarantee, and the traceability block is how two parties settle the question of which revision produced a figure.

Input: the topology and design basis, the operating case, and the study switches to include (cable four-fold check, maximum and minimum short-circuit comparison, protection coordination, DC network, time series, three-phase unbalance, transformer thermal ageing, earthing safety) → chain: one design call produces the short circuit, load flow, losses, economics and the optional study blocks, the report metadata module builds the chapter skeleton and attaches to each chapter the result fields it references, the conclusions module derives the structured conclusions and the assumptions with their boundaries, and the metadata module computes the traceability block — the engine version and code fingerprint, the parameter fingerprint over the topology and study inputs, the data-source versions and the duration → output: the chapter table with its references and the engine values, the conclusions, the assumptions, the fingerprint block, and the self-contained HTML document. Pressing the button again with the same scheme and the same switches hits the parameter-fingerprint cache and sends no request at all, and simply opening the page reads the scheme library once without running any calculation. Linkage: turning a study switch on adds its chapter and its conclusions, so the chapter count is whatever the engine reports rather than a fixed number; changing the topology or any parameter changes the parameter fingerprint and every referenced value together; and the loss allocation that appears here is the same one reconciled against the load flow on the losses page. Approximations, all disclosed: the deliverable is a feasibility-grade assessment for option comparison, selection and order-of-magnitude judgement, and the final calculation report still has to be produced by a licensed design institute; the only non-deterministic fields are the timestamps and the duration, which the engine declares explicitly; PDF export is deliberately not implemented — the HTML file prints to PDF from the browser.

The engine reference case (600 kW load, one 1000 kVA transformer, 150 kvar compensation) allocates 9.246 kW of losses against 9.240 kW of load-flow network loss — a 0.065% deviation, well inside the 0.5% reconciliation tolerance. On a multi-source test scheme with the report studies switched on, the same page reports the chapter count, the per-chapter field references, the conclusion and assumption counts and the parameter fingerprint of the run, all taken unmodified from the engine response. Everything is a feasibility-grade assessment: the numbers are for option comparison, selection and order-of-magnitude judgement, and the final calculation report still has to be produced by a licensed design institute.

The report itself carries no calculation of its own — it renders what the engine returns, so the standards are those of the underlying studies: IEC 60909 for short circuit, IEC 60076-1 / GB 20052 for transformer losses, IEC 61000 / IEEE 519 / GB/T 14549 / ER G5/5 for harmonics, IEC 60255-151 for protection curves, IEC 60076-7 for transformer thermal ageing, IEC 61660-1 for DC short circuit, GB 50054-2011 and IEC 60364-4-41 for earthing safety, and IEC 61082 / IEC 60617 for the accompanying drawing set. Every response states its engine version, its code fingerprint, its parameter fingerprint and the version of each data source, so any figure can be traced back to the run that produced it.

Does opening the report page run a calculation?

No. Opening the page sends zero engine calculation requests — at most it reads the scheme library once (a GET, not a calculation). Nothing is computed until you press “Generate report”, and pressing it again with the same scheme and the same switches hits the parameter-fingerprint cache and sends nothing at all.

Can I export a PDF?

PDF export is deliberately not implemented. The deliverable is a self-contained .html document with its own print stylesheet: open it and print to PDF from the browser if you need a fixed-layout file. This keeps one export path instead of two half-maintained ones.

How many chapters does the report have?

11 chapters form the fixed skeleton (topology, basis, power flow, short circuit, withstand, harmonics, protection, motor starting, losses and economics, grid compliance, conclusions); the engine appends further chapters only when the matching data really exists — multiple sources and operating mode, loss allocation, cable four-fold check, protection coordination, DC network, three-phase unbalance, transformer thermal ageing, time series, earthing safety and island operation. The page shows the count the engine reports, not a fixed number.