An EPLAN project is valuable when its documents agree with one another and can support review, panel build, field installation, checkout and maintenance. A visually complete schematic can still create rework if device tags, terminals, cables, PLC addresses and bill-of-material data are inconsistent.
The required package varies by client, jurisdiction and equipment, but the coordination principles are stable. Requirements and responsibilities should be agreed before release, including which party owns code compliance, certification, panel fabrication, field wiring and final as-built updates.
A good package also supports questions that occur after construction. Maintenance personnel should be able to trace a field wire to a terminal and PLC channel, identify the protective device serving a load and understand how a relay or safety device participates in the circuit. That supportability depends on consistent project data, not decorative sheet formatting.
Review milestones should match the consequences of change. Architecture and supply decisions belong early; device data, I/O and interface reviews follow; build-release review checks coordination and constructability; the final as-built review confirms field changes have returned to the source project. Each issue should have an owner and closure status so comments are not lost between PDF mark-ups and native EPLAN updates.
Project and power information
Start with title, revision, applicable standards, supply details, single-line information, protective devices and control-power distribution.
Begin with document control: project number, drawing index, revision, approval status, sheet function and applicable standards. Include the supply source, distribution concept, major loads, disconnecting and protective devices, control power and grounding or bonding approach. Design assumptions such as available fault current, environment, enclosure rating and upstream protection should be stated or requested rather than silently inferred.
Control schematics
Schematics should clearly show PLC I/O, safety functions, drives, motor starters, relays, instruments, networked devices and field connections using consistent device and wire references.
Control schematics should show functional relationships and practical wiring information. Use consistent device designations, cross-references, contact references, wire numbers, potentials and PLC addresses. Separate safety, standard control, power and communication circuits clearly. For intelligent devices, identify supply, network, enable, feedback and protective interfaces so panel builders and commissioning personnel do not need to reconstruct the intended architecture from multiple disconnected sheets.
Panel and terminal documentation
Panel layouts, terminal plans, cable information and device mounting details must agree with the schematics and bill of materials.
Panel layouts must be coordinated with actual component dimensions, wiring space, ducts, terminals, heat and service access. Review segregation, conductor routing, communication equipment, grounding points and door-mounted devices. Enclosure sizing should allow the panel to be built and maintained, not merely fit the nominal devices. Where thermal or short-circuit studies are outside the design scope, list the required inputs and responsible party.
- Enclosure and back-panel layout
- Heat and spacing considerations
- Terminal and connector plans
- Field cable and shielding information
- Network topology
Lists and schedules
A coordinated package typically includes device, cable, terminal, PLC I/O and parts lists. These should be generated and checked from the same controlled project data.
Terminal, cable and I/O reports are field documents, not automatic by-products. Check that terminal numbers, jumpers, spare points, shield treatment, cable cores, destinations and field device references match the schematics. PLC addresses and channel types should align with the software I/O list. A generated report is only reliable when the underlying device data and connection definitions have been reviewed.
Release and as-built control
Mark review status, construction release, field redlines and final as-built revisions explicitly. The drawing package is a controlled lifecycle record, not only a fabrication aid.
Release a coordinated revision and define the redline process before fabrication. Panel-shop substitutions, wiring changes and commissioning modifications need approval and must flow back to the source project. At handover, archive the native EPLAN project, released PDF, reports, component data and final revision record. The as-built package should describe the installed panel, not the design that existed before site changes.
Frequently asked questions
What should be provided before EPLAN design begins?
Provide the control philosophy, supply and load information, I/O, selected platform, device interfaces, enclosure environment, client standards and the responsibilities for protection and certification.
Is a PDF drawing set enough for handover?
A PDF is essential for controlled use, but the native EPLAN project and verified reports are also important for efficient future revision and data reuse.
Who owns SCCR and code approval?
Responsibility must be defined in the contract. Engineering can support component and protection coordination, while formal certification and inspection remain with the qualified parties and authorities assigned to the project.
How should field redlines be controlled?
Use one controlled mark-up set, identify the person and date, review technical impact, update the source project and issue a final as-built revision after verification.
Use the guide inside an approved work process
This guide supports planning and technical review; it does not authorize a change to live equipment. Before applying it, identify the system owner, production boundary, electrical and machine hazards, required permits, current backups and the person authorized to approve testing. Keep confirmed evidence separate from assumptions, and record any temporary simulation, force, inhibit or workaround under the site’s approved method.
If the installed condition does not match the available drawings or software, preserve the discrepancy and resolve ownership before downloading, energizing or bypassing a protective function. Final acceptance should reference the actual as-left configuration, executed test evidence, open actions and responsible approver.
Planning a related controls project?