Back to Blog
June 22, 2026 Vidhasri Team

Understanding EPLAN Parts Management — Saving Hours on Every Project

A practical guide to EPLAN's parts management system — how the parts database works, why it is central to automated documentation, and how a well-built parts library saves hours on every electrical engineering project.

eplan eplan parts management parts database electrical design bom automation

Understanding EPLAN Parts Management — Saving Hours on Every Project

Ask any experienced EPLAN engineer what separates a high-performing EPLAN setup from a frustrating one, and the answer is almost always the same:

The parts database.

A well-built EPLAN parts library is one of the highest-leverage investments an engineering team can make. A poorly built — or neglected — one is the single biggest reason why EPLAN’s automation benefits fail to materialize.

This article explains exactly how EPLAN’s parts management system works, why it matters so much, and how to build and maintain one that saves real hours on every project.


What is the EPLAN Parts Database?

The EPLAN parts database is a structured repository of component records — one record for every type of electrical component you use in your projects.

Each component record stores:

  • Identification data — Manufacturer name, part number, article number, EAN/order code
  • Technical data — Voltage rating, current rating, power, IP rating, installation type
  • Physical data — Dimensions, weight, mounting type (DIN rail, panel mount, etc.)
  • Schematic data — Which EPLAN symbol represents this component, connection point definitions
  • Documentation data — Datasheet links, product images, certifications
  • Commercial data — Price, lead time, supplier information (optional)

When an engineer places a symbol on a schematic in EPLAN, that symbol is linked to a specific parts database record. From that moment, every downstream document — BOM, terminal plan, cable schedule, nameplate list — is automatically populated with accurate data from the parts record.

This is the engine behind EPLAN’s automated documentation. Without good parts data, the engine has nothing to run on.


Why Parts Management is Critical: The Cause-and-Effect Chain

Understanding the impact of parts management requires following the data through the entire project workflow:

Engineer places a symbol on schematic

Symbol links to a parts database record

BOM automatically includes that component with correct article number

Terminal plan shows the correct terminal type and connection capacity

Cable schedule references the correct conductor specifications

Procurement orders the right part, first time

Panel builder assembles with zero confusion

Now consider what happens when the parts record is incomplete or incorrect:

Engineer places a symbol — but the parts record has no article number

BOM shows a blank or placeholder — manual intervention required

Procurement cannot order — engineer must look up the part manually

Manual entry introduces errors — wrong part ordered

Rework at assembly, delay at commissioning, client complaint

The parts database is not an optional enhancement — it is the foundation of every automated output EPLAN produces.


The Three Layers of EPLAN Parts Data

To build a reliable parts library, you need to understand what data lives at each layer:

Layer 1: The Part Record (Article Master)

This is the core component record in the EPLAN parts database. Every unique component — every circuit breaker model, every terminal type, every relay — needs its own article record.

Key fields that must be populated:

FieldWhy It Matters
Part number / Article numberUsed in BOM generation — if missing, BOM line is incomplete
ManufacturerRequired for procurement — distinguishes identical-looking parts from different manufacturers
DescriptionAppears in BOM, reports, and documentation
Technical propertiesDrives terminal plan accuracy (terminal count, connection type, current rating)
Symbol assignmentLinks the article to the correct EPLAN schematic symbol
Connection point definitionsDefines which terminals on the real device map to which connection points on the symbol

Layer 2: The Function Definition

The function definition tells EPLAN how a component functions electrically — whether it is a normally open contact, a motor output, a fuse terminal, or a coil. This drives cross-reference generation, connection logic, and report output.

Getting function definitions wrong is a common source of cross-reference errors and project check failures.

EPLAN allows you to attach manufacturer datasheets, 3D models (for EPLAN Pro Panel), wiring diagrams, and certifications to each parts record. When this is populated, your documentation package is genuinely complete — the panel builder can access the right datasheet directly from the engineering data, not from a separate search.


The EPLAN Data Portal: Your Starting Point

Building a parts library from scratch is a significant undertaking. EPLAN addresses this with the EPLAN Data Portal — an online database containing millions of manufacturer-verified component records from hundreds of global suppliers including:

  • Siemens
  • Schneider Electric
  • ABB
  • Phoenix Contact
  • Pilz
  • Weidmüller
  • Rittal
  • Molex
  • TE Connectivity

Engineers can search the Data Portal, find the exact component they need, and import the complete parts record directly into their local EPLAN library — including schematic symbols, technical data, 3D models, and datasheet links.

This is a significant time-saver for building your initial library. However, the Data Portal should be treated as a starting point, not a complete solution:

  • Not every component you use will be in the Data Portal
  • Data Portal records may need to be customised to match your company’s article numbering or supplier codes
  • Imported records still need to be validated before being promoted to your production library

Common Parts Management Mistakes (and How to Fix Them)

Mistake 1: One Person Manages Parts, Everyone Else Waits

In many teams, the parts database is managed by one engineer — often informally. When that person is unavailable, project progress stalls. New parts cannot be added, existing records cannot be corrected.

Fix: Establish a clear Parts Owner role with documented responsibilities, plus a defined process for submitting and approving new parts requests. Any qualified team member should be able to create a draft record — but only the Parts Owner approves and publishes.

Mistake 2: Using Parts Records from Previous Projects Without Verification

Engineers often copy a previous project as a starting point for a new one. If the old project contained parts records with errors or outdated article numbers, those errors propagate into the new project.

Fix: Maintain a single, version-controlled master parts database. All projects draw from this master. Never use project-embedded parts as the authoritative source.

Mistake 3: Adding Parts Without Connection Point Definitions

A parts record without connection point definitions means the schematic symbol cannot be linked to the real device’s terminals. Terminal plans will be incomplete, and Pro Panel 3D wiring will not work.

Fix: Every new parts record must include complete connection point definitions before it is approved. This is a non-negotiable checklist item.

Mistake 4: Letting the Library Grow Without Pruning

Over time, parts databases accumulate duplicate records, superseded parts, regional variants, and placeholder entries that were never completed. A bloated, messy library is almost as bad as no library — engineers stop trusting it and start entering data manually.

Fix: Schedule a quarterly audit. Archive obsolete records (do not delete them — they may still be referenced in older projects). Flag and complete incomplete records. Remove true duplicates.

Mistake 5: No Approval Workflow for New Parts

If any engineer can add parts to the production library without review, quality degrades rapidly. Incorrect symbol assignments, wrong connection point counts, and typographic errors in article numbers will appear in live project BOMs.

Fix: Implement a two-stage workflow: engineers create parts in a staging area, the Parts Owner validates and publishes to the production library. Simple to implement, significant impact on quality.


Building Your EPLAN Parts Library: A Practical Approach

If your current parts library is incomplete or unreliable, here is a phased approach to rebuilding it systematically:

Phase 1: Audit What You Have

  • Export your current parts database to Excel
  • Identify records with missing article numbers, missing symbol assignments, or incomplete technical data
  • Classify components by frequency of use (high, medium, low)

Phase 2: Prioritise High-Frequency Components

  • Focus first on the 20% of components that appear in 80% of your projects
  • Motor starters, circuit breakers, PLC modules, terminals, contactors, safety relays
  • Get these right first — the productivity gains are immediate

Phase 3: Import from EPLAN Data Portal

  • Search the Data Portal for your preferred manufacturers and models
  • Import, review, and adapt records to match your company’s conventions
  • Validate by placing symbols in a test project and running a BOM check

Phase 4: Develop Your Proprietary Records

  • Components not in the Data Portal must be created manually
  • Use your manufacturer datasheets as the source of truth
  • Validate every new record with a full project check before approving

Phase 5: Establish Maintenance Processes

  • Define the Parts Owner role
  • Document the new parts request and approval workflow
  • Schedule quarterly audits
  • Set up a process for handling manufacturer part discontinuations

The Time Savings: What Good Parts Management Delivers

Here is what changes when your parts library is in good shape:

TaskWithout Good Parts DataWith Good Parts Data
BOM generation4–8 hours manual compilationUnder 5 minutes (automated report)
BOM error rate2–5% (manual entry errors)<0.1% (database-driven)
New project setupRe-entering component data project by projectInstant — all data is in the library
Procurement queriesFrequent — wrong parts orderedNear-zero — correct article numbers every time
Panel assembly confusionCommon — missing or unclear component dataRare — complete data package for every assembly
Design review timeExtended — chasing data errorsReduced — errors caught by project check

Across a team doing 20–30 projects per year, the cumulative time saving from a well-maintained parts database runs into hundreds of engineering hours annually.


How Vidhasri Technology Helps

Building and maintaining a high-quality EPLAN parts database requires deep technical knowledge of both EPLAN’s data model and your component portfolio. It is time-intensive to do properly — and the consequences of doing it poorly show up on every single project.

At Vidhasri Technology, we offer:

  • Parts Database Audit — Review your existing library, identify gaps, and produce a remediation roadmap
  • Parts Library Build-out — Create complete, verified records for your full component portfolio
  • Data Portal Integration — Import and customise manufacturer records to your company standard
  • Approval Workflow Setup — Implement a practical parts management process your team will actually follow
  • Ongoing Library Maintenance — Quarterly audits and updates as part of a managed service

Contact us to discuss your parts database — we can assess your current situation and give you a clear picture of what it would take to get it right.


Key Takeaways

  1. The parts database is the engine behind all of EPLAN’s automation. Without good data, automated BOMs, terminal plans, and cable schedules cannot function correctly.

  2. Every component record needs four things at minimum: a valid article number, a correct symbol assignment, complete connection point definitions, and accurate technical properties.

  3. The EPLAN Data Portal is your best starting point — but records still need validation and customisation before use in production.

  4. A Parts Owner role and an approval workflow are not optional — they are the minimum governance needed to keep a production library reliable.

  5. The time saving is measurable and significant. Teams with well-maintained parts libraries routinely cut BOM generation from days to minutes and reduce procurement errors to near zero.

  6. Start with your high-frequency components. Perfecting the parts records for your most common 50–100 components delivers 80% of the benefit immediately.

Ready to optimize your engineering workflows?

Get in Touch
Service Deep Dive

The Problem

Our Solutions

    Key Deliverables