Engine-driven
Diagram nodes and conductors update automatically when the calculator output changes. No drift between the math, the PDF, and the SLD.
Schematic SVG
Pure-SVG output: scales without quality loss, prints clean, embeds inside every PDF report, and degrades safely on any browser.
NEC-aware annotation
Conductor sizes, OCP, EGC, and SPD callouts are labelled with the rule reference — 230.67, T250.122, 240.6(A), and so on.
Reference diagrams
Loading…
How EEP renders SLDs
The renderer takes a JSON graph ({ nodes, edges, notes }) and lays it out in horizontal tiers — utility at the top, then service entrance, then panels, then loads. Symbols are drawn from a publication-grade vector library (utility, transformer, switchgear, panel, motor, EVSE, PV, generator, generic load). Edges carry conductor specs, OCP ratings, lengths, and protection-device glyphs (CB, fuse, disconnect, GFCI, ATS).
The data comes directly from the calculation engine — for example the EX-A001 dwelling SLD reads runExA001().outputs.serviceConductor for its service-conductor label. If you change the calculator inputs, the diagram changes. There is no separate drafting step that can drift out of sync.
Limitations. EEP SLDs are schematic-grade. They are clear enough for design review and report attachments, but a permit-grade drafted SLD typically uses CAD blocks and a title block tied to the firm's drawing standard. EEP outputs the schematic and exports it as SVG; the Engineer of Record adapts it into the firm's CAD set as needed.