EPLAN P8 — Project Reports Reference Guide
| Complete guide to every report type | Configuration | Filtering | Output conventions | Industry-specific usage | Expert settings |
Table of Contents
- Fundamentals — What Are EPLAN Reports?
- Report Generation — How It Works
- Report Page Types Overview
- Table of Contents
- Parts List & Summarised Parts List (BOM)
- Device Tag List
- Terminal Diagram
- Terminal Strip Overview
- Terminal-Connection Diagram
- Terminal Line-Up Diagram
- Connection List
- Cable Diagram
- Cable Overview
- Cable-Connection Diagram
- Cable Assignment Diagram
- Plug Overview
- Plug Diagram
- Pin-Connection Diagram
- PLC Overview & PLC Address Overview
- PLC Card Overview
- Potential Overview
- Revision Overview
- Mounting List
- Manufacturer / Supplier List
- Structure Identifier Overview
- Enclosure Legend & Cut-Out Legend
- Distributed Device List
- Project Options Overview
- Placeholder Object Overview
- Assembly / Module Overview
- Forms Documentation & Plot Frame Documentation
- Topology Reports
- P&I Diagram Reports
- Pre-Planning Reports
- Report Filtering — Structure-Based
- Report Output Formats
- Report Templates & Forms
- Industry-Specific Report Sets
- Report Sequence — Recommended Order
- Common Mistakes
- Expert Tips
Fundamentals — What Are EPLAN Reports?
EPLAN reports are automatically generated pages that extract, compile, and present data from the schematic. They are not drawn manually — they are produced by EPLAN reading the properties of every device, terminal, cable, and connection in the project and rendering the results into formatted output pages.
The Core Principle
1
2
3
4
| Schematic data → EPLAN engine → Report pages
If it's in the schematic correctly → it appears in reports automatically
If it's missing from the schematic → it's missing from reports
|
Why Reports Matter
1
2
3
4
5
6
| ✔ Terminal diagrams drive cabinet wiring — errors here cost money during installation
✔ Parts lists / BOM drive procurement — wrong parts = delays
✔ Cable lists drive site installation — wrong cable IDs = wrong terminations
✔ Device tag lists drive commissioning — engineers need to find every device
✔ Connection lists drive testing — every wire must be verified
✔ PLC I/O lists drive software engineering — signal names must match
|
Reports vs Schematics
1
2
3
4
5
6
| Schematics: Drawn by engineer — show DESIGN INTENT
Reports: Generated by EPLAN — show ACTUAL DATA in schematic
The report IS the quality check.
If the terminal diagram looks wrong → the schematic has errors.
Fix the schematic → regenerate the report.
|
Report Update Behaviour
1
2
3
4
5
| Manual update: Engineer triggers "Update reports" — reports regenerate
Auto update: Reports update on every schematic change (can be slow on large projects)
Frozen reports: Reports locked — do not update (used for issued-for-construction drawings)
Best practice: Update all reports immediately before issuing for review or construction.
|
Report Generation — How It Works
Accessing Report Generation
1
2
3
4
5
| EPLAN menu path:
Utilities → Reports → Generate
Or via project navigator:
Right-click on project → Reports → Generate all
|
Report Placement Options
1
2
3
4
5
6
7
8
9
10
11
| Option 1 — At end of project
All reports placed after last schematic page
Most common — keeps schematics and reports separated
Option 2 — After structure node
Reports placed after each = or + group
Useful for per-panel terminal diagrams
Option 3 — Manual placement
Engineer drags reports to specific location
Used for custom document structures
|
Filtering Reports by Structure
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
| Reports can be filtered so each generated report covers only part of the project:
Filter by location (+):
Generate terminal diagram for +MCC1 only
Produces one terminal diagram per panel — correct for panel builders
Filter by function (=):
Generate parts list for =CTRL only
Produces one BOM per system — useful for modular projects
Filter by page range:
Generate reports for pages 1000–1099 only
Useful for section-by-section issue
No filter:
Report covers entire project
Useful for summary-level reports (total BOM, master cable list)
|
1
2
3
4
5
6
7
8
9
10
11
| Every report uses a FORM — a template that controls:
- Page size (A3, A4, A1, etc.)
- Title block layout
- Column headers and widths
- Font sizes and styles
- Company logo position
- Fields displayed (which properties shown)
Forms are stored in: EPLAN master data → Forms
Standard EPLAN forms: F01_001 to F01_xxx (out of the box)
Custom forms: Created in forms editor — company-specific layouts
|
Report Page Types Overview
| Report | Page Type | IEC 61355 | Primary Use |
|---|
| Table of contents | Table of contents | EAB | Document index |
| Parts list | Parts list | EPB | BOM / procurement |
| Summarised parts list | Summarised parts list | EPA | Material summary |
| Device tag list | Device tag list | EPB | Device register |
| Terminal diagram | Terminal diagram | EMA | Cabinet wiring |
| Terminal strip overview | Terminal-strip overview | EMA | Terminal index |
| Terminal-connection diagram | Terminal-connection diagram | EMA | Full termination detail |
| Terminal line-up diagram | Terminal line-up diagram | EMA | Terminal arrangement |
| Connection list | Connection list | EMA | Wire-by-wire schedule |
| Cable diagram | Cable diagram | EMB | Cable wiring detail |
| Cable overview | Cable overview | EMB | Cable schedule |
| Cable-connection diagram | Cable-connection diagram | EMB | Cable termination schedule |
| Cable assignment diagram | Cable assignment diagram | EMB | Cable-to-terminal mapping |
| Plug overview | Plug overview | EMA | Connector summary |
| Plug diagram | Plug diagram | EMA | Connector detail |
| Pin-connection diagram | Pin-connection diagram | EMA | Pin-level terminations |
| PLC diagram | PLC diagram | EFF | PLC I/O diagram |
| PLC overview | Overview | EFF | PLC module summary |
| PLC card overview | PLC card overview | EFF | PLC I/O card list |
| PLC address overview | PLC address overview | EFP | I/O address list |
| Potential overview | Potential overview | EFP | Potential/net list |
| Revision overview | Revision overview | EBH | Change history |
| Mounting list | Mounting list | ETL | Panel layout list |
| Manufacturer list | Manufacturer / supplier list | EPD | Vendor register |
| Structure identifier overview | Structure identifier overview | EAC | Project structure map |
| Enclosure legend | Enclosure legend | ELU | Panel legend |
| Cut-out legend | Cut-out legend | ELU | Panel cut-out reference |
| Distributed device list | Distributed device list | EPB | Devices by location |
| Assembly / module overview | Assembly/Module overview | EPB | Module register |
Table of Contents Report
What It Is
An automatically generated index of all pages in the project, showing page number, page type, description, and structure identifiers.
Configuration
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
| Filter options:
All pages → Complete project TOC
By structure node → TOC for a specific section
Exclude report pages → TOC for schematics only
Exclude admin pages → TOC for working drawings only
Typical columns displayed:
Page number
Page type (icon or text)
Page description
Function identifier (=)
Location identifier (+)
Revision
Date
Sheet (for multi-sheet drawings)
|
Industry Usage
1
2
3
4
| Machine building: One TOC for entire project — typically 1–2 pages
Panel building: One TOC per panel, or one master TOC
Process plant: One master TOC + optional per-unit TOC
Large projects: TOC often spans 3–10 pages
|
Expert Settings
1
2
3
4
5
6
7
| ✔ Always place TOC at page 2 (after cover sheet)
✔ Configure to show structure identifiers in separate columns
✔ Set sort order to match page numbering strategy
✔ Use "Show only schematics" filter for client-facing TOC
✔ Use "Show all including reports" for internal complete TOC
✔ Set page reference format to match drawing numbering (e.g. 001, 1.1, etc.)
✔ Auto-update TOC whenever pages are added or renumbered
|
Parts List & Summarised Parts List (BOM)
What They Are
1
2
3
4
5
6
7
8
9
| Parts list: Lists every component instance with full detail
One row per device placement in schematic
Shows: tag, description, manufacturer, part number,
quantity (always 1 per row), location, function
Summarised parts list: Consolidates identical parts across the project
One row per unique part number
Shows: total quantity, part number, description,
manufacturer, unit price (if set)
|
Typical Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
| Parts list:
Device tag (-designation)
Description (from device properties)
Manufacturer
Part number / article number
Order number
Type designation
Function (+= combined)
Location (+)
Page reference
Quantity (always 1 per row)
Summarised parts list:
Part number / article number
Description
Manufacturer
Order number
Total quantity across project
Unit price (optional)
Total price (optional)
Delivery unit (e.g. 1 per, 100m reel)
|
Filtering for Panel Building
1
2
3
4
5
6
7
8
9
10
11
12
| Per-panel BOM:
Filter by +MCC1 → generates BOM for MCC1 only
Filter by +MSB1 → generates BOM for MSB1 only
One BOM per panel → used for fabrication and procurement per assembly
Summary BOM:
No filter → total project material list
Used for overall procurement and cost estimation
Spare parts list:
Filter for devices tagged as spares
Requires custom property "Spare part = Yes" on components
|
Common Report Variants
1
2
3
4
5
6
| As-built BOM: Includes all devices including field instruments
Electrical BOM: Excludes mechanical and civil items
Procurement BOM: Grouped by manufacturer for ordering
Installation BOM: Grouped by location for site delivery
Panel BOM: Grouped by panel (+ filter) for fabrication shop
Spare parts BOM: Only items flagged as recommended spares
|
Expert Settings
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
| ✔ Map manufacturer and order number fields to macro database properly
— if not mapped, BOM has blank columns
✔ Set "Ignore if quantity = 0" to suppress placeholder rows
✔ For summarised BOM, verify "Group by" fields are correct
— common error: grouping by description instead of part number
— two parts with same description but different P/N merge incorrectly
✔ Use article master data (EPLAN Data Portal) for consistent part data
✔ Set cable as separate section — cables often need separate BOM
✔ Configure terminal blocks carefully — EPLAN counts each terminal
individually; client usually wants total quantity per type
✔ Add "Location" column to parts list — allows sorting by panel
✔ Export to Excel for cost estimation (File → Export → Excel)
✔ For large projects, split BOM into:
— Panel BOM (electrical components)
— Cable BOM (cables and cable accessories)
— Instrument BOM (field instruments)
— Hardware BOM (panel structure, DIN rail, ducting)
|
Per-Panel BOM Structure Example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
| MCC1 — Bill of Materials
────────────────────────────────────────────────────────
MCCB — Schneider NSX250F 3P 250A — Qty 1 (Incomer)
MCCB — Schneider NSX100F 3P 100A — Qty 8 (Motor feeders)
Contactor — Schneider LC1D40 40A — Qty 8
Overload relay — Schneider LR9F5369 — Qty 8
Selector switch — Schneider XB4BD33 — Qty 8
Push button START — Schneider XB4BA31 — Qty 8 (Green)
Push button STOP — Schneider XB4BA42 — Qty 8 (Red)
Indicator lamp RUN — Schneider XB4BVB3 — Qty 8 (Green)
Indicator lamp TRIP — Schneider XB4BVB4 — Qty 8 (Red)
Terminal block — Phoenix 3036038 — Qty 120
Din rail 35mm — Phoenix 1206166 (1m) — Qty 3m
Cable duct 40x40 — Schneider — Qty 5m
|
Device Tag List
What It Is
A tabular list of every device in the project with its complete designation, description, location, function, and cross-reference to where it appears in the schematic.
Typical Columns
1
2
3
4
5
6
7
8
9
10
| Complete device tag (= + location + device)
Device designation (- only)
Function identifier (=)
Location identifier (+)
Description (short)
Type designation
Manufacturer
Part number
Page reference (schematic page where device appears)
Number of placements (terminals, etc.)
|
Filtering
1
2
3
4
5
| By location: All devices in +MCC1 → commissioning checklist per panel
By function: All devices in =CTRL → system-level device list
By type: All contactors only (filter by symbol type)
By manufacturer: All Siemens devices only
Full project: Complete device register
|
Industry Usage
1
2
3
4
5
6
7
8
| Machine building: Device list used for commissioning walkdown
One row per device — engineer checks off each one
Panel building: Device list used as manufacturing checklist
Wirer uses to verify every component is installed
Process plant: Device list = instrument index (with ISA tags)
Used by instrument engineers for calibration records
Substation: Device list used for IED inventory and settings schedule
Commissioning: Device list used for pre-commissioning inspection sheets
|
Expert Settings
1
2
3
4
5
6
7
8
| ✔ Include page reference column — essential for finding devices quickly
✔ Sort by location (+) then device tag — logical order for wiring
✔ Export to Excel for commissioning sign-off sheets
✔ Add "Installed" and "Tested" columns in Excel for site use
✔ For instruments, include "Calibration required Y/N" custom field
✔ Filter out terminals (XT) and cables (W) — usually too many rows
✔ Include function text (rung comment) from schematic if available
✔ Cross-reference to cable list using device tags
|
Terminal Diagram
What It Is
The most critical report for panel builders and site electricians. Shows every terminal strip with all connections — what’s connected on the left (internal wiring) and right (external / field cables), wire numbers, cable references, and cross-references to the schematic.
Structure of a Terminal Diagram
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
| Terminal strip header: Terminal strip designation (X1, X_DI, etc.)
Location (+MCC1, +CP1, etc.)
Per terminal row:
Left side (internal): Wire/connection coming from inside panel
- Source page reference
- Potential / signal name
- Wire number
- Source device and pin
Terminal block graphic: Visual representation of terminal
- Terminal number
- Terminal type (standard, fused, PE, N, bridge, etc.)
- Terminal part number / type
Right side (external): Wire/connection going to field
- Cable reference
- Conductor (core) number / colour
- Destination page reference
- Destination device and terminal
Notes column: Special instructions, loop number, etc.
|
Terminal Types Shown
1
2
3
4
5
6
7
8
9
10
| Standard terminal XT — general purpose signal/control
Fused terminal FT — with integrated fuse (for field loop power)
PE terminal PE — protective earth (green/yellow)
N terminal N — neutral
Bridged terminals Group of terminals internally connected
Double-deck terminal Two-level terminal
Feed-through terminal Pass-through (jumpered both sides)
Disconnect terminal Terminal with integrated isolator
Marking terminal Label / marker terminal (no connection)
End bracket / stopper Panel structure component
|
Filtering — Critical for Panel Builders
1
2
3
4
5
6
7
8
9
10
11
12
13
14
| One terminal diagram per panel:
Filter = +MCC1 → produces terminal diagram for MCC1 only
Filter = +MCC2 → produces terminal diagram for MCC2 only
Each panel gets its own terminal diagram page(s)
One terminal diagram per terminal strip:
Filter = X1 → all connections on terminal strip X1
Produces one section per strip within the panel
Sub-section by I/O type:
X_DI section → all digital input terminals
X_AI section → all analog input terminals
X_SAFE section → all safety terminals
Colour-coded terminal types help identification
|
Industry Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
| Panel builder / wirer:
Terminal diagram is the primary wiring document
Used side-by-side with schematic during wiring
Used for wire-count and wire-labelling preparation
Site electrician:
Uses terminal diagram to land field cables
Left side already landed (internal wiring done in factory)
Right side is their job — field cables incoming
Commissioning engineer:
Uses terminal diagram for loop verification
Checks destination against instrument loop sheet
Cross-references to cable schedule
Maintenance:
Uses terminal diagram to trace faults
Identifies which terminal to probe for which signal
|
Expert Settings
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
| ✔ Generate one terminal diagram per + location (panel)
— File → Generate → Filter by location
✔ Sort terminals by terminal number (not alphabetically)
— Correct: X1/01, X1/02, X1/03
— Wrong: X1/1, X1/10, X1/11, X1/2 (alphabetical sort chaos)
✔ Set form to A3 landscape — more columns, better readability
✔ Show cable references on right side — essential for tracing
✔ Show potential/signal names — helps commissioning
✔ Show cross-reference page numbers — links back to schematic
✔ Set terminal bridge grouping to show jumper bars correctly
✔ Include PE and N terminals — often missed
✔ Add "Spare" rows for unused terminals (set in terminal properties)
✔ Show shield/screen terminals separately (designated TS or XS)
✔ For safety terminals (blue), use separate X_SAFE section and
colour-code or mark clearly on the diagram form
✔ For IS (intrinsically safe) terminals, ensure blue or ex-specific
section is used — mandatory for hazardous area compliance
|
Terminal Strip Overview
What It Is
A summary list of all terminal strips in the project — not the individual connections, but the strips themselves with their location, number of terminals, and basic information.
Typical Columns
1
2
3
4
5
6
7
8
| Terminal strip designation (X1, X_DI, etc.)
Location (+)
Number of terminals
Terminal type / series
Manufacturer
Part number
Description / purpose
Page reference (where terminal diagram is)
|
Usage
1
2
3
4
5
6
7
8
9
| Used to:
— Overview all terminal strips at project level
— Check that all strips are accounted for
— Quick reference for ordering terminal blocks
— Input to panel hardware BOM
— Used for DIN rail space planning
Filtered by +location → shows all strips in one panel
Full project → master terminal strip inventory
|
Terminal-Connection Diagram
What It Is
A more detailed version of the terminal diagram showing the complete wire path from source device to terminal to destination device, including all intermediate connections. Used for complex multi-panel wiring.
When to Use
1
2
3
4
5
6
7
8
9
10
| Use when:
— Cables run between multiple panels
— Multi-core cables with many conductors need tracking
— Inter-panel connections must be verified (e.g. MCC1 to CP1)
— Customer requires from-to wiring schedule format
More detail than terminal diagram:
— Shows complete wire path (not just panel view)
— Includes cable identification through entire route
— Used for complex control systems with many inter-panel cables
|
Terminal Line-Up Diagram
What It Is
A graphical representation showing the physical arrangement of terminal blocks on a DIN rail, used for panel layout planning and as a manufacturing guide.
What It Shows
1
2
3
4
5
6
7
8
9
| Visual DIN rail with:
— Terminal block symbols in order
— Terminal numbers
— Terminal type (standard, fused, PE, N, bridge, end bracket)
— Colour coding by type
— Label / tag carrier position
— Bridge connections shown graphically
— End brackets and stoppers
— DIN rail length calculation
|
Usage
1
2
3
4
5
6
7
8
9
10
11
12
| Panel builder / designer:
— Plans DIN rail layout before fabrication
— Calculates DIN rail length required
— Verifies terminal arrangement matches order (fused before standard, etc.)
Procurement:
— Used alongside parts list to order correct terminal types and quantities
— Identifies bridge bars needed
Manufacturing:
— Assembly drawing for terminal rail
— Wirer assembles rails according to this document
|
Connection List
What It Is
A tabular, wire-by-wire list of every connection in the project. Each row represents one end of one wire, showing source device/pin, destination device/pin, wire number, potential, and cable reference.
Typical Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
| Connection ID / wire number
Potential name / signal name
Source:
— Page reference
— Device tag
— Pin / terminal number
Destination:
— Page reference
— Device tag
— Pin / terminal number
Cable reference (if routed through a cable)
Core number (within cable)
Wire colour
Wire cross-section (mm²)
Length (if set)
|
1
2
3
4
5
6
| Full connection list: Every connection in project — very long for large projects
Filtered by panel: All connections within +MCC1
Filtered by cable: All connections on a specific cable
Cross-panel connections: Only connections that cross between two + locations
Field wiring only: Only connections from panel to field
Internal wiring only: Only connections within one panel
|
Industry Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| Testing lab / FAT:
— Point-to-point continuity testing guide
— Each row verified with multimeter
— "Tested" column added in Excel for sign-off
System integrator:
— Identifies all cross-panel connections requiring cables
— Used to generate cable schedule
Site commissioning:
— Field connection verification
— Cross-references back to schematic page
Maintenance:
— Fault tracing — trace signal from source to destination
— Identify all connections on a specific potential/signal
|
Expert Settings
1
2
3
4
5
6
7
8
9
| ✔ Include potential name column — engineers search by signal name
✔ Sort by source page then source pin — logical reading order
✔ Export to Excel — used for testing sign-off sheets
✔ Filter "cross-location only" for inter-panel cable schedule input
✔ Use connection list as input to cable schedule preparation
✔ For large projects, split by area / function — one list per MCC
✔ For IS circuits, mark connections with IS colour flag
✔ Show wire colour code — especially important for 24VDC (blue = neg)
✔ Show cross-section (mm²) for site inspection compliance
|
Cable Diagram
What It Is
A detailed schematic-style diagram showing a specific cable — its cores, source terminals, destination terminals, and how each core is connected at both ends.
Structure of a Cable Diagram
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
| Cable header:
Cable reference / tag
Cable type (e.g. 7C × 1.5mm² SWA PVC)
Length
Route (from location → to location)
Per core row:
Core number / colour
Source: panel + terminal
Destination: panel + terminal
Signal name / potential
Cross-section
Unused cores shown as spare
Shield/screen core shown separately
|
Usage
1
2
3
4
5
6
7
8
9
10
11
| Site electrician / cable puller:
Identifies which core goes to which terminal at each end
Used at both glanding points simultaneously
Termination supervisor:
Verifies all cores landed and correct
Core-by-core verification document
Testing:
Used for meggering (insulation resistance testing) identification
Used for continuity verification before energisation
|
Expert Settings
1
2
3
4
5
6
7
8
| ✔ Show cable direction — make it obvious which end is "source" and which is "destination"
✔ Include length on every cable diagram — used for ITP inspection
✔ Mark spare cores clearly
✔ For multi-pair instrument cables, show pair numbers as well as core colours
✔ Include cable type specification on header (voltage rating, armoured, etc.)
✔ Reference back to cable overview with cable tag
✔ For Ex-rated cables, note Ex certification on header
✔ For IS circuits, show blue core identification
|
Cable Overview
What It Is
A master cable schedule — one row per cable showing all cables in the project with routing information, type, length, and termination details.
Typical Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
| Cable tag / reference
Cable type (e.g. 4C × 2.5mm² SWA XLPE/PVC)
Voltage rating (e.g. 0.6/1kV)
Number of cores
Cross-section (mm²)
Armoured Y/N
From location (+)
From device / terminal
To location (+)
To device / terminal
Route / cable tray reference
Length (calculated or manual)
Installed length (actual — added at site)
Gland size (source end)
Gland size (destination end)
Remarks / notes
Status (issued / installed / tested)
|
Variants
1
2
3
4
5
6
7
8
| Full cable schedule: All cables in project
Power cables only: Filter by cable type → HV/LV power
Control cables only: Filter by cable type → multi-core control
Instrument cables only: Filter by cable type → signal / instrument
Fibre cables: Filter by type → fibre optic
Inter-panel cables: Cross-location connections only
Field cables: From panel to field only
Cable tray cables: Filter by route / tray reference
|
Industry Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
| Cable installer / puller:
Uses as pull schedule — each row pulled in sequence
Cable drum number added on site
Site electrical supervisor:
ITP checklist — each cable inspected, meggered, signed off
Status column (drummed / routed / pulled / glanded / terminated / tested)
Commissioning:
Cross-reference to terminal diagram and connection list
Verify cable identification tags match schedule
Client handover package:
As-built cable schedule included in O&M manual
Includes actual installed lengths (field-measured)
Maintenance:
Cable identification — find cable by tag when fault tracing
Replacement specification from cable type column
|
Expert Settings
1
2
3
4
5
6
7
8
9
10
11
12
13
| ✔ Set cable length calculation method:
— Manual entry (most reliable — based on route survey)
— Topology-based (requires EPLAN Topology — automatic from routing model)
— Add 10% contingency factor for manual lengths
✔ Export to Excel for site tracking and status updates
✔ Include gland sizes — saves time on site
✔ Add "As-built length" column for site to fill in
✔ Sort by "from location" then cable tag — grouped by departure panel
✔ Include cable tray / conduit reference for ITP inspection
✔ For armoured cables, note armour continuity requirement
✔ For cables to hazardous areas, mark clearly (Ex designation)
✔ Include cable drum number field — filled in at delivery
✔ For large projects, split by area / section
|
Cable-Connection Diagram
What It Is
Combines the cable schedule with termination detail — shows each cable with its complete core-by-core termination at both ends in a tabular format.
When to Use
1
2
3
4
5
| Use instead of cable diagram when:
— Many cables need to be documented efficiently
— Tabular format preferred over graphical cable diagram
— Used for multi-pair instrument cables (many cores to document)
— Client specification requires "cable termination schedule" format
|
Cable Assignment Diagram
What It Is
Shows which cables are assigned to which devices or terminals, presented in a matrix or tabular format showing the cable-to-device relationship.
Usage
1
2
3
4
5
| Used for:
— Verifying every device has a cable assigned
— Multi-conductor cable core assignment verification
— Useful for complex multi-panel projects where cables serve multiple devices
— Input for cable tray fill calculations
|
Plug Overview
What It Is
A summary of all plugs and connectors in the project — one row per connector showing the plug tag, type, number of pins, and location.
Typical Columns
1
2
3
4
5
6
7
8
| Plug / connector tag
Connector type (M12, D-Sub, Harting Han, IEC 60320, etc.)
Number of pins / contacts
Gender (plug / socket)
Location (+)
Connected device
Page reference
Part number
|
Usage
1
2
3
4
5
6
7
8
9
| Machine building: Machine connectors (M12, Harting, circular)
Panel building: Panel connectors for field connection
Marine: Weatherproof connectors (IP67+)
Automotive: High-density connectors
Used for:
— Connector procurement
— Connector assembly work order
— Verifying correct connector type per location
|
Plug Diagram
What It Is
A detailed wiring diagram for a specific connector showing each pin, its signal/wire, source, and destination.
Structure
1
2
3
4
5
6
7
8
9
| Connector graphic (showing pin layout)
Per-pin table:
Pin number
Signal name / potential
Wire colour
Cross-section
Source device and terminal
Destination device and terminal
Remarks
|
Usage
1
2
3
4
| Cable assembly: Wiring guide for cable harness assembly
Testing: Pin-by-pin continuity verification
Maintenance: Fault tracing at connector level
Machine builder: Used for machine interconnection harnesses
|
Pin-Connection Diagram
What It Is
Shows the detailed pin-level connections for multi-pin connectors, similar to the plug diagram but presented in a connection-list style. Used for high pin-count connectors.
Usage
1
2
3
4
5
| Used for:
— PLC backplane connectors
— High-density I/O connectors (50-pin D-Sub, etc.)
— Custom connector assemblies
— Fieldbus connector pin assignments (PROFIBUS DB9, etc.)
|
PLC Overview & PLC Address Overview
PLC Overview
A graphical layout showing the PLC rack(s), all module slots, module types, and a summary of I/O channels per module.
1
2
3
4
5
6
7
8
9
| Shows:
PLC rack layout (slots 0..n)
Per slot:
Slot number
Module type (CPU, DI, DO, AI, AO, CM, etc.)
Module article number
Number of channels
Address range (byte.bit format)
Channel usage (how many channels used / total)
|
PLC Address Overview
A tabular I/O list showing every PLC channel with its address, signal name, connected device, and schematic cross-reference.
1
2
3
4
5
6
7
8
9
10
11
| Typical columns:
PLC rack and slot
Module type
Channel number
Absolute address (e.g. I0.0, Q4.3, IW256, MW100)
Symbolic address / tag name (e.g. M01_RUN_FDBK)
Signal description (plain language)
Connected device tag (sensor / actuator)
Signal type (24VDC, 4-20mA, PT100, etc.)
Schematic page reference
Remarks / notes
|
Industry Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| Software engineer / PLC programmer:
PLC address overview = I/O list for programming
Signal names in EPLAN should match variable names in PLC code
Export to Excel → import into TIA Portal, Studio 5000, etc.
Commissioning engineer:
Uses address overview to force/monitor signals during loop checks
PLC address → physical field device cross-reference
Machine builder:
Standard deliverable — client needs I/O list for machine acceptance
Often part of functional specification acceptance criteria
Process plant:
I/O list is a contractual deliverable — checked against DCS datasheet
Signal count per module verified against project specification
|
Expert Settings
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
| ✔ Ensure symbolic addresses (tag names) in EPLAN match PLC variable names
— Mismatches cause confusion during commissioning
✔ Export address overview to Excel for programmer's use:
Utilities → Reports → Export → Excel
✔ Sort by rack/slot/channel — reflects physical module layout
✔ Include signal type column — programmer needs to know input range
✔ Include "Wired Y/N" and "Loop checked Y/N" columns in Excel
for commissioning sign-off use
✔ For HART devices, note HART tag in remarks column
✔ Separate DI / DO / AI / AO sections within the report
✔ For safety I/O, use a separate section or separate report
— safety I/O addresses are a separate document for SIS validation
✔ For redundant CPUs, show A-side and B-side addressing
✔ Use consistent channel numbering: channel 0 or channel 1 as first?
— decide at project start and stick to it
|
PLC Card Overview
What It Is
A summary list of all PLC cards / modules across the project — one row per module showing type, slot, location, channel count, and part number.
Typical Columns
1
2
3
4
5
6
7
8
9
| PLC system / rack
Slot number
Module type (CPU, DI, DO, AI, AO, CM, etc.)
Article number / part number
Manufacturer
Number of channels
Address range
Location (+)
Page reference
|
Usage
1
2
3
4
5
6
7
8
9
10
11
| Hardware engineer:
Verifies module count and types against specification
Used for procurement order
Commissioning:
Module inventory check on site delivery
Verifies correct module in correct slot
Software engineer:
Hardware configuration reference
Used to set up hardware configuration in TIA Portal / Studio 5000
|
Potential Overview
What It Is
A list of all electrical potentials (nets / signals) in the project showing every connection point on each potential and where it appears in the schematic.
Typical Columns
1
2
3
4
5
6
| Potential name (e.g. +24VDC, -24VDC_GND, L1, N, PE, SIG_FT101)
Potential type (power, signal, safety, etc.)
Number of connection points on this potential
List of all connection points:
— Device tag and pin
— Schematic page reference
|
Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| Design verification:
— Check all intended connections share the same potential name
— Identify unintended shared potentials (wiring errors)
— Verify power distribution (is +24VDC reaching all devices?)
Commissioning:
— Find all devices on a specific supply potential
— Identify which devices lose power if a fuse trips
Testing:
— Identify all measuring points on a specific signal potential
— Used for signal tracing
DCS / PLC integration:
— Verify that signal potential names match PLC tag names
— Potential name = signal identifier connecting EPLAN to PLC database
|
Expert Settings
1
2
3
4
5
6
7
8
9
| ✔ Use consistent potential naming from project start
— +24VDC not "24V", "24VDC", "+24V" (all different potentials)
✔ Use signal tag names as potential names for instrumentation
— Potential name "FT101" traces the 4-20mA loop for FT101
✔ Set potential type properties to classify (power, safety, signal)
✔ Review potential overview before issuing for construction
— Unexpected single-connection potentials = unconnected wire ends
— Unexpected multi-connection potentials = unintended bridges
✔ Export for network/net list comparison with PLC configuration
|
Revision Overview
What It Is
A tabular list of all revisions made to the project, showing what changed, when, who made the change, and what was affected.
Typical Columns
1
2
3
4
5
6
7
8
| Revision number (A, B, C or 01, 02, 03)
Date
Description of change
Changed by (drafter)
Checked by
Approved by
Pages affected
Change reference (ECN number, RFI number, etc.)
|
Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| Document control:
— Formal revision history for issued drawings
— Links to engineering change notices (ECN)
— Required for ITP and QA documentation packages
Client:
— Identifies what has changed between revision issues
— Avoids re-reviewing unchanged pages
Site:
— Checks if drawings they hold are current revision
— Identifies if changes affect work already done
Maintenance:
— Historical record of design changes
— Explains why something is different from original design
|
Expert Settings
1
2
3
4
5
6
7
8
9
10
| ✔ Populate revision block on every individual page — not just revision overview
✔ Set EPLAN to auto-update revision date and number on modified pages
✔ Use revision clouds on schematics to show what changed on each page
✔ Revision overview should match revision blocks on individual pages
✔ For formal issue, update revision status:
A = Preliminary / for review
B = For approval
C = For construction (IFC)
D, E... = As-built revisions
✔ Export revision overview to client as transmittal supplement
|
Mounting List
What It Is
A list of all devices to be mounted in a panel or enclosure, showing mounting position (DIN rail number, position), device tag, type, and dimensions.
Typical Columns
1
2
3
4
5
6
7
8
9
10
| Device tag (-)
Description
Manufacturer
Type
Width (mm)
Height (mm)
DIN rail reference
Position on DIN rail (from left, mm)
Location (+)
Page reference
|
Usage
1
2
3
4
5
6
7
8
9
10
11
12
| Panel builder / designer:
— Input for panel layout drawing (mechanical drawing)
— DIN rail fill calculation
— Enclosure size verification
Procurement:
— Hardware list for non-electrical items (DIN rail, duct, backplate)
EPLAN Pro Panel:
— Mounting list data feeds directly into 3D panel layout
— Automatically places devices based on mounting list
— Used for enclosure design and drilling template generation
|
Manufacturer / Supplier List
What It Is
A list of all manufacturers and suppliers referenced in the project, used for procurement and vendor qualification.
Typical Columns
1
2
3
4
5
6
| Manufacturer name
Products supplied in this project
Number of items from this manufacturer
Supplier / distributor (if different)
Contact information (optional)
Lead time notes (optional)
|
Usage
1
2
3
4
5
6
7
8
9
10
11
12
| Procurement:
— Identifies all vendors to contact for pricing
— Input to vendor qualification process
— Used for "approved vendor list" compliance check
Client review:
— Client checks manufacturers against their approved vendor list (AVL)
— Flags substitutions required before procurement
Project management:
— Supply chain risk assessment
— Identifies single-source or long lead items
|
Structure Identifier Overview
What It Is
A list of all structure identifiers (= and + values) used in the project with their descriptions — essentially a legend for the project tree.
Typical Columns
1
2
3
4
5
| Structure identifier (= or +)
Identifier type (function / location)
Description (plain language)
Number of pages under this identifier
First page reference
|
Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
| New engineer onboarding:
— First document to read when joining a project
— Explains what every folder in the project tree means
Client review:
— Client understands the project organisation before reviewing schematics
— Confirms structure matches plant layout and functional areas
Document control:
— Verifies all expected structure identifiers are present
— Checks for unintentionally created identifiers (typos)
ITP / audit:
— Confirms project structure matches specification
— Traceability between functional areas and drawing structure
|
Enclosure Legend & Cut-Out Legend
Enclosure Legend
A legend page for a panel or enclosure showing all devices installed, their positions, and identification tags.
1
2
3
4
5
6
7
8
| Shows:
Panel front / back view (or 3D view from Pro Panel)
Device positions with labels
Device tag cross-reference list
Component identification table
Enclosure type and dimensions
IP rating
Installation details
|
Cut-Out Legend
Documents all cut-outs and holes required in panel doors, gland plates, and surfaces.
1
2
3
4
5
6
| Shows:
Hole dimensions (diameter, cutout shape)
Position (from reference point, in mm)
Device fitted (what goes through each hole)
Device tag
Tooling required (drill size, nibbler, chassis punch)
|
Usage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
| Mechanical fabrication:
— Cut-out legend drives all drilling and punching
— Enclosure legend shows final fitted appearance
Panel assembly:
— Enclosure legend used to verify all devices installed correctly
— Position check before wiring starts
Client:
— Enclosure legend appears in O&M manual
— Allows maintenance team to identify components on panel door
EPLAN Pro Panel:
— Both reports generate automatically from 3D panel layout
— Cut-out templates exported as DXF for CNC machining
|
Distributed Device List
What It Is
A list of all devices distributed across multiple locations — particularly useful for showing all devices of a specific type regardless of where they are installed.
Typical Columns
1
2
3
4
5
6
| Device tag
Device type
Location (+)
Function (=)
Description
Page reference
|
Usage
1
2
3
4
5
6
| Useful for:
— Finding all motors across a plant
— Finding all safety devices (e-stops, light curtains) by location
— Verifying all remote I/O drops are accounted for
— Site cable pull planning — know all devices at each location
— Cross-checking against client's instrument or motor schedule
|
Project Options Overview
What It Is
Documents all option variants configured in the project (if EPLAN Options are used). Shows which variants are active and which pages are included or excluded per option.
When to Use
1
2
3
4
5
6
7
8
9
10
11
12
13
14
| Machine variants: Same base machine with optional features
— Base machine always included
— Option A: extended axis (included only if Option A selected)
— Option B: vision system (included only if Option B selected)
Product families: Multiple product models from one EPLAN project
— Model 100: basic configuration
— Model 200: extended configuration
— Model 300: full configuration
Client-specific variants:
— Standard version
— Ex-rated version (hazardous area)
— High-temperature version
|
Expert Settings
1
2
3
4
5
| ✔ Set up options at project start — very difficult to retrofit
✔ Use descriptive option names (not just "Option 1")
✔ Document options in project structure description page
✔ Test all option combinations before issuing
✔ Export different option sets as separate PDF packages for different clients
|
Placeholder Object Overview
What It Is
Lists all placeholder objects in the project — objects that represent undefined or generic components awaiting final specification.
When to Use
1
2
3
4
5
6
7
8
9
10
11
12
13
| Concept design phase:
— Placeholder motor (size TBD)
— Placeholder valve (type TBD)
— Generic sensor (instrument TBD)
Macro-based design:
— Reusable macros with placeholder devices
— Final article numbers assigned from placeholder list
— Used in conjunction with EPLAN macro library
Template projects:
— Base template uses placeholders
— Project-specific data fills in placeholders
|
Assembly / Module Overview
What It Is
A list of all assemblies or modules defined in the project — grouped components treated as a single purchasable unit.
Usage
1
2
3
4
5
6
| Used for:
— Motor starter assemblies (contactor + overload + pushbuttons as one unit)
— PLC rack assemblies (CPU + I/O modules as one assembly)
— Field instrument assemblies (transmitter + manifold + impulse line)
— Procurement of pre-assembled units
— Checking assembly completeness
|
Documents all EPLAN forms used in the project — the templates that control report layout and page layout.
Plot Frame Documentation
Documents all plot frames (title blocks / borders) used in the project.
Usage
1
2
3
4
5
6
7
8
9
10
11
| Quality management:
— Verifies correct company-standard forms are used throughout
— Checks for unapproved or non-standard forms
New projects:
— Reference for selecting the correct forms
— Input to project setup checklist
EPLAN master data management:
— Documents which forms are in use
— Identifies forms that need updating if standards change
|
Topology Reports
Only available if EPLAN Topology module is active
Available Topology Reports
1
2
3
4
5
6
7
8
9
10
11
12
| Topology: Topology path list
— Lists all topology paths (cable routes) defined in the project
— Shows path name, length, start node, end node
Topology: Routing path diagram
— Graphical diagram showing routing paths through the facility
— Cable tray / conduit routes shown schematically
Topology: Routed cables / connections
— Lists all cables assigned to specific routing paths
— Cable length calculated from path geometry
— Used for cable schedule population with accurate lengths
|
Industry Usage
1
2
3
4
5
6
7
8
9
10
11
12
| Process plant:
— Defines cable tray routes between buildings and equipment
— Automatic cable length calculation from routing model
Substation:
— Cable routes between relay panels, battery room, and switchyard
— Trench routing documentation
Large projects:
— Replaces manual length estimation
— Cable length accuracy for procurement
— Input to tray fill calculation
|
P&I Diagram Reports
Only available if EPLAN Fluid or P&ID module is active
Available P&ID Reports
1
2
3
4
5
6
7
| P&I diagram: Piping overview
— Summary of all piping lines defined in P&ID pages
— Line number, pipe spec, size, medium, insulation
PCT loop legend
— Legend for P&ID loop symbols used in the project
— Cross-reference between loop tags and instrument designations
|
Pre-Planning Reports
Only available if EPLAN Pre-Planning module is active
Available Pre-Planning Reports
1
2
3
4
5
6
7
8
9
10
11
| Pre-planning: Structure segment overview
— Lists all structure segments defined in pre-planning
— Used in early engineering phase before detailed design
Pre-planning: Planning object overview
— Lists all planning objects (high-level functional items)
— Motor, valve, instrument before detailed schematic exists
Pre-planning: Segment template overview
— Lists reusable templates used for pre-planning
— Standard motor circuit, standard instrument loop, etc.
|
Report Filtering — Structure-Based
Filtering Principles
1
2
3
4
5
6
7
8
| Every report in EPLAN can be filtered by:
= Function identifier
+ Location identifier
Page range
Page type
Device type
Custom property values
Revision status
|
Recommended Filter Sets by Report
| Report | Recommended Filter | Output |
|---|
| Terminal diagram | Per + location | One terminal diagram per panel |
| Parts list | Per + location | One BOM per panel |
| Cable overview | No filter (full project) | Master cable schedule |
| PLC address overview | Per PLC rack location | One I/O list per PLC system |
| Device tag list | Per = function | Device list per system |
| Connection list | Per + location | Connection list per panel |
| Revision overview | No filter | Full project revision history |
| Table of contents | No filter | Full project TOC |
| Manufacturer list | No filter | Full project vendor list |
Filter Configuration in EPLAN
1
2
3
4
5
6
7
8
9
10
11
| Utilities → Reports → Generate
→ Select report type
→ Settings → Filter
→ Add filter criterion
→ Select property: "Location designation"
→ Operator: "="
→ Value: "+MCC1"
→ OK
→ Generate
Save filter as named preset for reuse
|
PDF Output (most common)
1
2
3
4
5
6
7
8
9
10
11
| Utilities → Export → PDF
→ Select pages (all, schematics only, reports only, selection)
→ Select PDF settings (colour, black/white, A3, A4)
→ Set filename
→ Export
Recommended for:
— Issuing to client for review
— IFC (issued for construction) package
— O&M manual insertion
— Email distribution
|
Excel / CSV Export
1
2
3
4
5
6
7
8
9
10
11
12
| Utilities → Reports → Export to Excel
Used for:
— BOM for procurement team
— I/O list for PLC programmer
— Cable schedule for site tracking
— Terminal schedule for commissioning sign-off
— Device list for asset register import
Configure export mapping:
EPLAN property → Excel column header
Save as export template for reuse
|
DXF / DWG Export
1
2
3
4
5
6
| File → Export → DXF/DWG
Used for:
— Sending to client who uses AutoCAD
— Archiving in client's AutoCAD-based document management system
— Cut-out templates (from Pro Panel) for CNC machining
|
Printing
1
2
3
4
5
6
7
8
9
| File → Print
→ Select printer / plotter
→ Select page range or named report set
→ Scale: 1:1 for A3/A4
→ Fit to paper or print at exact scale
For large format (A0/A1 site drawings):
— Export PDF first, print from PDF with scaling
— Ensures correct scale on printed drawing
|
1
2
3
4
5
6
7
| F01_001 Standard report form (A4 portrait)
F01_002 Standard report form (A3 landscape)
F01_003 Terminal diagram form (A3 landscape — wide columns)
F01_004 Cable overview form
F01_005 Parts list form
F03_001 Schematic form A3 (10×10 grid references)
F03_002 Schematic form A4
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
| Forms editor: Utilities → Forms → Edit form
Customise:
— Company logo (insert as image)
— Title block fields (project name, client, revision, date, drawn by)
— Column widths and headers for report columns
— Font types and sizes
— Border and grid style
— Page size (A4, A3, A2, A1, A0 — or custom)
— Orientation (portrait / landscape)
Save custom form to master data:
Options → Settings → Directories → Forms
Copy custom form to company master data directory
Available to all users on company network
Best practice:
Create and lock company-standard forms before any project starts
Never modify a form mid-project — all reports reformat
|
1
2
3
4
5
6
7
8
9
10
11
12
| Each title block field is linked to a project property:
Project name → [Project.Name]
Client name → [Project.Customer]
Project number → [Project.Number]
Drawn by → [Page.CreatedBy]
Date → [Page.ModifiedDate]
Revision → [Page.Revision]
Page description → [Page.Description]
Sheet number → [Page.Number]
Total sheets → [Project.TotalPages]
Map these correctly in form editor to auto-populate title blocks
|
Industry-Specific Report Sets
Machine Builder — Minimum Report Set
1
2
3
4
5
6
7
8
| 1. Table of contents
2. Parts list (per panel / summarised)
3. Device tag list
4. Terminal diagram (per panel)
5. Cable overview
6. PLC address overview / I/O list
7. Connection list
8. Revision overview
|
Panel Builder — Minimum Report Set
1
2
3
4
5
6
7
8
9
10
11
| 1. Table of contents
2. Parts list (per panel)
3. Summarised parts list (total material order)
4. Terminal diagram (per panel — most important)
5. Terminal strip overview
6. Terminal line-up diagram
7. Cable overview (inter-panel cables)
8. Mounting list
9. Enclosure legend
10. Cut-out legend
11. Revision overview
|
Process Plant — Full Report Set
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
| 1. Table of contents
2. Structure identifier overview
3. Revision overview
4. Summarised parts list (total project)
5. Parts list (per functional area)
6. Device tag list / instrument index
7. Distributed device list (motors, valves, instruments by area)
8. Manufacturer / supplier list
9. Terminal diagram (per cabinet / JB)
10. Terminal strip overview
11. Connection list (per panel)
12. Cable overview (master cable schedule)
13. Cable diagram (per cable — for complex multi-core)
14. Cable-connection diagram
15. PLC address overview (I/O list)
16. PLC card overview
17. Potential overview
18. Mounting list (per panel)
19. Enclosure legend (per panel)
|
Substation / Power — Full Report Set
1
2
3
4
5
6
7
8
9
10
11
12
13
14
| 1. Table of contents
2. Revision overview
3. Structure identifier overview
4. Parts list and summarised parts list
5. Device tag list
6. Terminal diagram (per panel — relay panels, DC board)
7. Terminal strip overview
8. Cable overview (DC auxiliary cables)
9. Connection list (protection relay wiring)
10. PLC / RTU address overview
11. Potential overview (DC circuits especially)
12. CT / VT schedule (from device tag list filtered)
13. Protection relay schedule (from device tag list)
14. Manufacturer / supplier list
|
Oil & Gas — Full Report Set
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
| 1. Table of contents
2. Revision overview
3. Structure identifier overview
4. Instrument index (device tag list — ISA format)
5. I/O list (PLC/DCS address overview)
6. Motor / drive schedule (device tag list filtered)
7. Valve schedule (device tag list filtered)
8. Cable schedule (cable overview)
9. Terminal diagrams (per LER / JB)
10. Connection list
11. Parts list (per LER)
12. Summarised parts list (total project)
13. SIS I/O schedule (separate — safety marked)
14. Cause and effect matrix (manual — not auto-generated)
15. Earthing schedule (from connection list filtered)
16. Area classification drawing reference
17. Manufacturer list
|
SCADA / RTU — Minimum Report Set
1
2
3
4
5
6
7
8
| 1. Table of contents
2. Device tag list (all RTU hardware)
3. I/O list per RTU (address overview)
4. Terminal diagram per RTU panel
5. Cable overview (comms cables especially)
6. Parts list per RTU site
7. Network cable schedule
8. Revision overview
|
Report Sequence — Recommended Order
For Final Document Issue (IFC Package)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
| Position in document set:
01 Title page / cover sheet ← Always first
02 Table of contents ← Always second
03 Revision history ← Third
04 Symbol legend / abbreviations ← Admin
05 Structure identifier overview ← Admin
06 General notes ← Admin
07 Applicable standards list ← Admin
─────────────────────────────────────────────
08 Electrical SLD overview ← Design overview
09 Control system architecture ← Design overview
10 Network topology ← Design overview
─────────────────────────────────────────────
11 Schematics (by structure node) ← Main content
─────────────────────────────────────────────
REPORTS SECTION:
12 Terminal diagrams (per panel) ← Connection reports
13 Terminal strip overviews ← Connection reports
14 Cable overview / cable schedule ← Cable reports
15 Connection list ← Connection reports
16 Cable diagrams (if required) ← Cable reports
17 PLC address overview / I/O list ← PLC reports
18 PLC card overview ← PLC reports
19 Potential overview ← Signal reports
20 Parts list (per panel) ← BOM reports
21 Summarised parts list ← BOM reports
22 Device tag list ← Device reports
23 Distributed device list ← Device reports
24 Mounting list (per panel) ← Layout reports
25 Enclosure legend (per panel) ← Layout reports
26 Cut-out legend (per panel) ← Layout reports
27 Manufacturer / supplier list ← Procurement
─────────────────────────────────────────────
Last: Appendices (vendor data sheets, standards, etc.)
|
Common Mistakes
| ❌ Wrong | ✅ Correct | Reason |
|---|
| Generating reports without updating schematics first | Always update schematics → then generate reports | Stale data in schematics = wrong reports |
| One terminal diagram for entire project | One terminal diagram per + location (panel) | Single document is unusable for large projects |
| Parts list with blank manufacturer / part number | Populate article master data for all devices | Blank BOM cannot be used for procurement |
| Terminal diagram not showing cable references | Configure form to show cable column | Electrician cannot trace without cable ref |
| Sorting terminals alphabetically | Sort by terminal number (numeric) | Alphabetical: X1/1, X1/10, X1/11, X1/2 — wrong order |
| Issuing reports before schematic is complete | Reports are only as good as the schematic | Incomplete schematic = incomplete reports — misleading |
| Not freezing reports at IFC issue | Freeze/lock reports at IFC stage | Reports must not change after construction starts without formal revision |
| Using default EPLAN forms with no company branding | Create custom company-standard forms | Unprofessional — client will reject non-branded drawings |
| Cable overview with no cable lengths | Enter cable lengths (manual or topology-based) | Cable schedule without lengths = cannot order cable |
| PLC address overview not matching PLC tag names | Set EPLAN potential names = PLC variable names | Mismatch causes chaos during software loading and commissioning |
| Report pages scattered through schematic | Group all reports at end of project | Standard structure — reports at end, schematics in middle |
| Never updating TOC after adding pages | Regenerate TOC before every issue | TOC must reflect actual page structure at time of issue |
| Exporting BOM without checking quantities | Review summarised BOM for obviously wrong quantities | Duplicate symbols = double-counted devices in BOM |
Expert Tips
1. Reports are only as good as the schematic — fix the source, not the output
If a terminal diagram shows an error, go back to the schematic and fix it there. Never manually edit a report page — it will be overwritten on the next generation. The schematic is the master.
Not once at the start and once at the end — every time you issue drawings for review, approval, or construction. A 10-minute regeneration prevents a contractor using outdated cable schedules or BOMs.
3. Set up report filters once and save them as named presets
Creating a filter to generate terminal diagrams per panel takes 5 minutes the first time. Save it as a named preset — “Terminal diagram per location”. Next project, load the preset. Over a career this saves days.
Panel builders and site electricians depend on it more than any other document. Invest time getting the form, column widths, sorting, and filtering perfect. A good terminal diagram form, once created, is used on every project.
5. Export the I/O list to Excel before the software engineer starts
PLC programmers need the I/O list before they can write code. Export the PLC address overview to Excel as early as possible — even from a draft schematic. Signal names in EPLAN must match variable names in TIA Portal / Studio 5000 exactly.
Before issuing for construction, review the potential overview. Any potential with only one connection is an unconnected wire. Any potential shared by more devices than expected may be a wiring error. This catches mistakes no visual schematic check finds.
7. Cable length estimation requires a methodology — agree it early
Manual length estimate: measure route on layout drawing + 10% contingency + allowance for bends and glands. Document the methodology. Clients and auditors ask. EPLAN Topology automates this — worth the investment on large projects.
8. Always include a “status” column in exported cable schedules
Add columns: Drummed / Routed / Pulled / Glanded / Terminated / Tested / Signed-off. Site supervisors track installation progress against this. Export from EPLAN, track in Excel on site, import as-built data back for record drawings.
9. Lock / freeze reports at the IFC (Issued for Construction) milestone
Once drawings are issued for construction, reports should not update automatically. Either lock the report pages or note the IFC revision clearly. Any change after IFC requires a formal revision with revision cloud and updated revision block.
10. Build a standard report generation checklist for your company
Every project should generate the same core set of reports in the same order. Create a one-page checklist: “Reports to generate before issue”. Tick each one. Include: TOC updated ✓, terminal diagrams per panel ✓, cable overview ✓, BOM ✓, I/O list ✓, revision overview ✓. Prevents the situation where a commissioning engineer arrives on site and asks for the cable schedule that was never generated.
Based on IEC 61355 | IEC 81346 | IEC 61439 | ISA-5.1 | IEC 60617 | IEC 62271 Expert conventions compiled from panel building, machine building, process engineering, power, automation, instrumentation, and commissioning disciplines
