Electrical Detailed Design Autodraft
Electrical Detailed Design Autodraft places HV and LV assets—transformers, switchgear, distribution boards, cable runs, and lighting circuits—onto the architect’s washed-base DWG against the firm’s standard asset library and the authority’s submission template. It runs inside AutoCAD via AutoLISP and .NET, reads the washed base, applies the right layers and blocks, and writes a permit-ready electrical DWG as a Labs engagement under MSA + Appendix.
- HV and LV asset placement on the washed-base DWG against the firm’s standard library and naming rules.
- AutoLISP and .NET integration runs inside AutoCAD, so drafters stay in the DWG environment they already use.
- Layer, line-weight, and block conventions match the authority’s submission template for permit-ready electrical drawings.
From hand-placed circuits to read-the-base
Workflow today
-
01
Architect issues washed-base DWG
On Day 0 the architect issues a washed-base DWG: architectural plan drained to a background layer, Xrefs cleaned, and title block frozen. The electrical engineer receives the working file and starts setting up HV and LV layers, viewports, and plotting styles. Any mismatch with the authority’s submission template is fixed manually at this stage.
Day 0 -
02
Engineer writes / reuses AutoLISP scripts
During Week 1+, senior drafters maintain a patchwork of AutoLISP routines for asset placement, panel tagging, and layer assignment. Each new project forces tweaks to layer names, block attributes, and insertion rules. Knowledge sits with one or two senior people who remember which script works for transformers, which for DBs, and which breaks on mixed HV/LV layouts.
Week 1+ -
03
Manual placement of every asset
From Week 1–4, transformers, switchgear, ring main units, LV distribution boards, cable trays, and lighting circuits are placed by hand against the washed base. Standard-library symbols are dropped onto the right layers, rotated to match walls, and aligned with grids. Revisions from the architect mean repeated rework on the same bays, with no persistent memory of previous placement logic.
Week 1–4 -
04
QA against authority template
In Week 4–5, a senior drafter audits every layer, line-weight, linetype, and title-block field against the authority’s submission template. They check that HV and LV assets sit on the correct layers, that block attributes match naming rules, and that plot styles read correctly. Resubmit cycles are common when a single layer name or symbol style drifts from the approved pattern.
Week 4–5
Workflow with VitruAI
-
01
Run the agent against the washed base
On Day 1, a drafter runs the electrical detailed design autodraft workflow inside AutoCAD, pointing it at the washed-base DWG, the firm’s HV and LV asset library, and the authority template. The workflow sits alongside the broader AutoCAD integration and the general AutoCAD permit drawing generation pattern. AutoLISP and .NET hooks read layers, blocks, and Xrefs before any placement happens.
Day 1, ~30 min -
02
Agent places assets
Across Day 1–2, the agent places transformers, switchgear, ring main units, LV DBs, cable runs, and lighting circuits at the correct stations on the correct layers. It applies the firm’s block library, attribute templates, and naming rules, and keeps HV and LV conventions separate. Existing AutoLISP routines are called where they already work, while new placement logic fills the gaps in mixed-use or irregular floor plates.
Day 1–2 -
03
Drafter reviews flagged decisions
On Day 2–3, the drafter reviews a list of flagged decisions: ambiguous cable routes, congested risers, or clashes with mechanical ducts identified using patterns similar to the MEP routing review workflow. Questionable placements are highlighted in the DWG for manual adjustment. Any repeated edit feeds back into the firm’s rules during the Labs engagement, tightening future runs.
Day 2–3 -
04
Submit
By Day 3–5, the drafter exports a permit-ready electrical DWG that matches the authority’s template for layers, line-weights, and symbols. The same pattern can hand off to Document AI for title-block checks or to the mechanical drawing PDF parsing workflow when upstream information only exists as scanned PDFs. AutoLISP knowledge now lives in the agent configuration rather than in one senior drafter’s head.
Day 3–5
Electrical detailed design autodraft — common questions
-
How does this work with our existing AutoLISP scripts?
Existing AutoLISP routines stay in place; the ai autocad drafting agent calls them where they already perform reliably and adds new placement logic where the scripts gap. Each Labs engagement starts with a ~1-week audit of your AutoLISP and .NET automation to map which commands handle transformers, DBs, or naming rules. From there, the workflow wraps those routines so drafters trigger a single electrical detailed design autodraft run instead of a dozen separate scripts.
-
Does this work for HV and LV both?
Yes, both HV and LV are in scope, with separate calibration per library and authority template. HV assets such as transformers, switchgear, and ring main units follow one set of layers, colours, and naming rules, while LV assets such as DBs, lighting circuits, and small power follow another. During Labs, the configuration is tuned per firm so mixed HV/LV layouts and shared risers behave predictably across projects.
-
What about cable sizing and circuit calculations?
Cable sizing and circuit calculations sit outside this autodraft workflow and remain with your electrical design tools such as ETAP or AmTech. The agent assumes pre-sized circuits and uses that information to place assets, assign circuit IDs, and route indicative cable paths on the DWG. When upstream calculations change, the workflow re-reads the inputs and updates placements rather than attempting to recalc load or fault levels itself.
-
How does this fit with the AutoCAD permit drawing pattern?
This workflow is the electrical-discipline-specific pattern within the broader DWG-to-permit approach described in the AutoCAD permit drawing generation use case. The general pattern covers title blocks, viewports, and multi-discipline sheets; electrical detailed design autodraft focuses on HV/LV asset placement and layer discipline. Firms typically pair both so architectural, mechanical, and electrical sheets follow one submission standard across a project.
-
How does a Labs engagement work?
A Labs engagement runs 4–8 weeks under MSA + Appendix and focuses on one or two representative projects. VitruAI calibrates the workflow against your HV/LV asset library, AutoLISP routines, authority submission template, and any document inputs that may later pass through Document AI. The engagement ships a working agent for a live project and folds the lessons into a configuration that can be rolled out across future AutoCAD jobs.