Automation
How Structured Electrical Drawings Generate BOMs, Wire Lists and PLC I/O Reports
A report becomes dependable when it is another view of the engineering project—not a separate spreadsheet that someone must remember to maintain after every drawing change.
Electrical drawings already contain much of the information needed for project documentation. The challenge is whether that information exists only as visible text and lines, or as connected objects that reporting logic can understand.
01 · The data behind the drawing
Report automation begins before the report is opened.
A line on a canvas does not automatically know that it is a conductor. A rectangle with text does not necessarily identify a device, and a terminal number typed beside a symbol may have no relationship with a terminal-strip record. Reports become possible when the project stores those meanings explicitly.
Structured objects connect graphical representation with engineering identity. A device can carry a tag and component reference; a wire can retain its number, size and endpoints; a PLC channel can retain its I/O address, terminal and signal description. The drawing remains visual, but its important facts are available as data.
Does each device, terminal, cable and conductor have a stable identity instead of only a graphical label?
Can the system follow a conductor through routing symbols and terminals to its meaningful endpoints?
Are tags, part numbers, ratings, descriptions and wire properties stored as structured fields?
Can a reviewer trace every reported value back to the drawing data from which it was generated?
02 · Bill of materials
A BOM should be derived from selected project equipment.
When placed devices reference structured components, the project can group repeated items and present useful purchasing fields such as item description, make, part number, details, specification and quantity. The report no longer depends on a designer counting graphical blocks and copying values into another file.
A drawing change can leave the purchasing list incomplete or out of date.
The report can be regenerated after the source equipment information changes.
Grouping rules still need care. Two devices that look similar may have different ratings or manufacturers, while inconsistent component data can split one product into several rows. A generated BOM improves traceability, but disciplined component records remain essential.
03 · Wires, cables and terminals
Connectivity turns drawn conductors into installation information.
Wire lists, cable schedules and terminal reports depend on more than visible wire numbers. The system must understand which pins are joined, how a route passes through conductive helpers or terminals, and which device exists at each meaningful endpoint.
- Wire list: conductor number, from and to endpoints, size, color and description.
- Cable summary: cable tag, construction, used cores, spare cores and description.
- Cable schedule: each core with its wire number, endpoints, intermediate terminals and review status.
- Terminal report: terminal-strip position, page placement and the connections on both sides.
Ambiguous or incomplete connections should not be silently converted into confident documentation. A useful report identifies rows that require review so the designer can resolve the source data.
04 · PLC I/O list
PLC documentation needs module and channel context.
A PLC I/O list can combine module identity, page, I/O type, logical address, terminal label, signal description, wire number, destination and connection status. This makes the output useful for engineering review, commissioning preparation and coordination with control-system documentation.
The report must distinguish digital and analog inputs and outputs while retaining non-channel connections such as communication, power and common terminals. Spare and unconnected channels should remain visible rather than disappearing from the schedule.
05 · Report lifecycle
Generated outputs need a clear relationship with their source.
PDF is useful for review and formal issue, while CSV supports filtering, checking and controlled downstream use. A report inserted into the drawing can become part of the page set, but it should remain a generated view rather than editable duplicate data.
When source equipment or connection fields change, an inserted report should be marked out of date. An explicit update action can then save the latest project, regenerate the rows, recalculate pagination and replace the existing generated pages. This is more predictable than rebuilding pages continuously while the engineer is editing.
Once a PDF or CSV leaves the live project, it will not update automatically. Revision, issue and transmittal procedures must identify which exported output is current.
06 · The ElecDraw model
How ElecDraw connects drawings with engineering reports.
ElecDraw stores devices, components, wires, cables, terminals and PLC module configuration as project data. Its report tools use those relationships to generate a BOM, terminal report, cable summary and schedule, list of wires, and PLC I/O list.
Reports can be downloaded in PDF or CSV form. A BOM can also be inserted into a dedicated report folder inside the drawing, where its generated pages remain locked and can be refreshed when the source data changes.
Generated documentation reduces transcription work; it does not certify the engineering design. Qualified professionals must validate devices, quantities, ratings, conductor data, terminal assignments, PLC signals and applicable safety requirements before manufacture or installation.
