FISEKON GmbH – Fischer Elektrokonstruktion

03 — Services

Article master data & macros

Nobody enjoys maintaining article master data. It is invisible, it appears in no project calculation, and it costs the most time exactly when you have the least – in the middle of a project. That is precisely why outsourcing this work pays off.

We build and maintain the data foundation your design office works from: article master data with complete technical attributes, component libraries, product and window macros for recurring plant sections.

The effect does not show on the first project but on the second. A cleanly built macro saves the same time again on every reuse – a poorly maintained article base costs it again just as reliably. So this is less about volume than structure: consistent naming, rigorous function definitions, maintained accessory assignment.

We create new articles and rework grown data alike – including the thankless task of finding duplicates, retiring obsolete records and checking manufacturer data instead of importing it unseen.

Where suppliers deliver data, we check it before adoption. An imported article base is not data maintenance but a building site with a delay built in.

When this service is needed

  • The article base has grown over years and contains duplicates and legacy records.
  • Identical plant sections are redrawn on every project.
  • Manufacturer data is to be adopted but checked first.
  • The design office should focus on design, not on data maintenance.

Process

How we work together

  1. 01

    Review

    We look at the existing base: how many articles, how many actually in use, how consistently are they set up?

  2. 02

    Rules

    Naming, classification and mandatory fields are agreed. Without these rules the same mess reappears within six months.

  3. 03

    Build

    Articles and macros are created or cleaned up – prioritised by what is actually used day to day.

  4. 04

    Maintenance

    New articles and changes are kept up continuously. On request under a maintenance agreement with a fixed scope.

Result

What you have at the end

A macro is only finished when someone can use it without asking a question. Anything else is a template you will open again next time.

  • Maintained article database in your system environment
  • Macro library for recurring plant sections
  • Written rules for naming and classification
  • Overview of cleaned and merged records

Frequently asked

Is this worthwhile for smaller design teams?

Usually yes, but for a different reason. For small teams it is less about scale than resilience: if knowledge of the article base sits with one person, documented rules are worth more than any time saving.

Do you take data directly from manufacturers?

Where available, yes – but checked. Manufacturer records vary in quality, and an unchecked import brings back exactly the inconsistency you wanted to remove.

What happens to our legacy data?

Nothing is deleted silently. We flag what should be retired and you decide. Cleanup only happens after your approval.

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.

Your contact

Portrait of Olaf Kreith

Olaf Kreith

Head of Sales · Braunschweig

Head office switchboard

Locations

Head officeStellmacherstr. 7
33428 Marienfeld (Harsewinkel)
Gütersloh officeWagenfeldstr. 2
33332 Gütersloh

Or write to us

We usually reply within one working day.

Go to the contact form