FISEKON GmbH · Fischer Elektrokonstruktion

16 · Services

Switching to EPLAN with migration from ELCAD and WSCAD

Switching to EPLAN rarely fails because of the software. It gets expensive when legacy projects are transferred without a plan, when the new standard is only created during the changeover, or when nobody is left to maintain the existing documentation in the old system until then. We design in ELCAD, WSCAD and EPLAN, so we know both sides of the switch.

When this service is needed

  • Customers or group standards require EPLAN, while existing plants are documented in ELCAD or WSCAD.
  • New designers work in EPLAN, while knowledge of the old system is retiring.
  • A large extension is due, and the open question is whether it goes into the old system or straight into EPLAN.
  • The switch has been decided, but nobody has time to plan it alongside daily business.

Result

  • Migration plan with sequence and effort per plant
  • Documented EPLAN standard
  • Transferred EPLAN projects with article references and checked reports
  • List of deviations between drawing and plant

Request a project

We take on the electrical design there is no time for in house.

Electrical design
Since 1998
Employees
15
CAE systems (EPLAN, WSCAD, ELCAD)
3
Projects since 1998
2,300+

Why FISEKON

  1. One contact, not a distribution list

    Whoever takes your project also works on it.

  2. Your CAE system, not ours

    EPLAN, WSCAD or ELCAD, using your part master.

  3. Existing plants are our everyday work

    Plant runs, documents do not match. That is where we start.

  4. Capacity without a permanent post

    Design capacity when you need it.

Process

How we work together

  1. 01

    Review the existing documentation

    Plants, drawing states, designation system, licences. You receive an overview of what has to be transferred, what can wait and what may stay in the old system.

  2. 02

    Define the standard

    Designations, article master data, macros and page layout in EPLAN, before the first legacy project is transferred. If an EPLAN standard already exists, we adopt it.

  3. 03

    Start with one plant

    A typical plant is transferred and checked first. After that it is clear which approach pays off for the rest and what it costs.

  4. 04

    Transfer in rhythm

    The remaining projects follow to plan, usually when work on the plant is due anyway. Until then the existing documentation stays editable.

Anyone moving from ELCAD or WSCAD to EPLAN Electric P8 usually has solid reasons. Customers or group standards require EPLAN, new designers bring EPLAN with them, or extensions become too laborious in the old system. Choosing the new system is the smaller part. The real work lies in deciding what happens to the existing documentation.

Not every existing plant has to move to EPLAN straight away. A staged approach is often more economical. New projects start in EPLAN from day one, existing plants are transferred when a larger change is due anyway and are maintained in the old system until then. Plants that hardly change any more may also stay there permanently.

The starting point is the EPLAN standard with its designation structure, article master data, macros, forms and page layout, not the first migrated project. Developing this standard during the transfer carries every ambiguity across, and every further project multiplies it. We also clarify whether the existing designation system is kept or converted to IEC 81346. A migration that touches the entire documentation anyway is the right moment for that.

For transfers from ELCAD there are tools that convert schematics into EPLAN projects. They save drawing work but do not replace checking. Cross-references, article references, terminals and cables must be right in the result, otherwise the reports produce wrong lists. Whether a plant is converted or re-engineered in a structured way is decided plant by plant, by scope, the state of the documents and how long the plant is to keep running.

Because we work in all three systems, we can accompany the transition completely. We maintain the existing documentation in ELCAD or WSCAD, build the EPLAN standard, transfer projects and train your team in EPLAN workshops. You have one contact throughout, from the first overview of the existing documentation to the last transferred project.

Frequently asked

Migration to EPLAN

You have a technical task? We will look at how it can be solved.

Discuss a project
01Do all legacy projects have to move to EPLAN?

No. Many plants run for years with few changes. As long as they are maintained, they can stay in the old system, and we continue to maintain ELCAD and WSCAD documentation. What is extended, changed frequently or newly built gets transferred.

02Can ELCAD projects be converted to EPLAN automatically?

Partly. There are converters that transfer ELCAD schematics into EPLAN projects. The result has to be checked and reworked, above all cross-references, article references and terminals. Whether that pays off or a structured re-engineering is more economical becomes clear with the first transferred plant.

03What happens to our existing designation system?

It is either kept or converted, but never halfway. A consistently continued system is worth more than a compliant one that applies to only part of the plants. If it is converted, then during the migration, because that touches the documentation completely anyway.

04Who maintains the existing documentation while the migration runs?

We do, if you wish. We continue to work in ELCAD and WSCAD and can incorporate changes to the existing documentation until each plant is transferred, permanently too under a maintenance agreement.

Contact

Tell us what it is about.

A phone call or three lines is enough. From the very start you talk to the people who will later work on your project, not to a distribution list.

Direct

Or write to us

We usually reply within one working day.

Write email

Opens your email program with the message already written. Read it, change whatever you like, and send it yourself, from your mailbox to ours.

Go to the contact form