Knowledge base for mechanical engineering when you need the old parameter settings and the programmer is about to leave.

System documentation, parameter sets, modification reports and manufacturer documentation in one place, every answer with its source, so knowledge stays findable in the company even when someone leaves. The demo uses sample documents; you see whether it works with your reports in the first weeks after go-live.

Everyday question

“How was the customer’s system parameterised during the last modification?”

The answer is in

Commissioning report · Parameter set

1 Source in one click

Day to day

Sound familiar?

  • How did we parameterise the customer’s system during the last modification?

  • The programmer who built it is retiring. None of what he knows is written down.

  • There are three versions of the system documentation, and nobody knows which one’s current.

Tuesday, just after six. Bernd is at a customer in Wels, standing in front of the 2014 palletising system; the axis won’t return to its reference position. The programmer who built the control system is on a commissioning job in Romania and isn’t answering his phone. There are three parameter sets on the project drive: one from initial commissioning, two from the 2019 modification, all with near-identical names. Inside the control cabinet there’s a note with handwritten values, but nothing to say who wrote it. Bernd drives home that evening, because he doesn’t dare change settings on the off chance. He comes back on Thursday, after the programmer has read out the values over the phone – two trips for a number someone once wrote down. The customer asks whether we don’t document things like that.

Things people in this industry say every day.

Example questions

Questions from your day-to-day work

Three questions that come up day to day, and the document where you would expect to find the answer. In the demo you see this with sample documents; you test it with your own documents in the first weeks after go-live.

  • “How was the customer’s system parameterised during the last modification?”

    1 Commissioning report · Parameter set

  • “Which spare parts fit this series?”

    2 Parts list · Manufacturer documentation

  • “Which documentation version applies to this system?”

    3 System documentation · Revision status

Documents

The documents that matter to you

  • System documentation per customer
  • Parameter sets and configurations
  • Modification and commissioning reports
  • Manufacturer documentation for the components
  • Circuit diagrams and parts lists
  • Commissioning engineers’ voice notes

Pricing

What it costs

Basic package

from€500per month

Set-up fee €2,900 · excl. VAT

A flat fee per company. Everyone at your company can use it – technicians as much as office staff – with no per-user licence. One-click connections are included in the set-up. Before we start, we check whether your industry-specific software can be connected; that connection is charged on a time-and-materials basis, agreed in advance.

Drafts as Word, PDF or email are included in the Premium package.

At the kick-off we agree on twenty questions together – along with the documents each answer should come from. At sign-off we go through them together and look at what the system does with them. What follows from that is set out in the quotation.

Compare all packages

Getting started

Where to start

Start with a single series – the one the service team gets the most calls about. First the commissioning and modification reports with parameter sets from recent years, then the operating instructions you supplied and your suppliers’ declarations of incorporation. Questions asked at the machine are often about a set value – and that is in one of these reports, in a circuit diagram, or nowhere. In the first weeks after go-live, ask about a system whose status you know and check whether the right report comes up as the source. Load the folders as they are, including the commissioning engineer’s own files; nothing needs sorting or renaming beforehand. Before we start, we check whether the document directory in Kieselstein (an ERP system) can be connected; it is set up and charged on a time-and-materials basis, agreed in advance.

FAQ

Frequently asked questions

We have to keep technical documentation available for ten years. Does this help?

It doesn’t replace an archive in the legal sense. But you can ask what exists for a machine number – risk assessment, operating instructions, EU declaration of conformity, circuit diagrams, calculations and the declarations of incorporation for any partly completed machinery you bought in – and the answer gives the source for each. If the system finds nothing for an item, it tells you so; ahead of a market surveillance request, that is exactly what you need to know. In the first weeks after go-live, use a system you have delivered to test whether documents are cleanly matched to the machine number. The ten-year period stays the same when the EU Machinery Regulation 2023/1230 applies from 20 January 2027: under it, too, the technical documentation and the declaration of conformity must be kept available for ten years after the machine is placed on the market.

We’re modifying an existing system. How do we know what was actually running last?

You can ask about the versions that exist – parameter set, circuit diagram, program version – and the answer gives the date, revision note and document for each; if the version only appears in the file name, it says so. Which version applies is still your decision. It helps to add the last modification report and the acceptance record, because these usually show what was set after the last intervention and what was only planned. Whether several near-identically named versions are kept cleanly apart is worth checking in the first weeks after go-live. Whether a change counts as a substantial modification, and what follows from that, is not something the system assesses – it provides the documents that assessment is based on.

The customer complains months after acceptance. How do we find what was recorded at the time?

You ask by system and period; the answer lists the acceptance and commissioning records, photos, email correspondence and test records that are in the collection, each with date and source – including the email in which the customer himself asked for that setting at the time, if it was filed. Whether a notice of defects under § 377 UGB (the Austrian Commercial Code) was given in time in a transaction that is commercial for both sides is not something the system assesses; it shows who wrote what and when, and with this kind of question that is half the dispute. Your response can be produced as a draft that you read and send yourselves.

How do we get what only the commissioning engineer knows into the collection – without making him write reports?

Talking instead of writing: a voice note of a few minutes per system, plus his own folders and email threads in full. Then you go through system by system and ask where something exists and where nothing does. If the system finds nothing, it tells you so – and you can still fill the gaps with him while he’s here, instead of guessing two years later. How well voice notes from a noisy shop floor are transcribed is best tried right at the start, in the first weeks after go-live. A list of gaps is a more practical way into the conversation than asking him to write everything down before he retires.

Request a demo – with examples from Mechanical engineering & automation

In a 30-minute video call, we use sample documents from your industry to show you how questions are answered and what the source for each answer looks like. You don’t need any of your own documents for this.