Engineering Systems

How we engineer

A plant of this complexity does not emerge from individual drawings. We have developed our own engineering tools and workflows that connect requirements, design and manufacturing in a closed loop.

Requirements engineering

3-Layer Closed-Loop Engineering

Requirements, components, documents and boundary conditions form one shared graph. Every decision has an origin, evidence and a timestamp.

  1. Layer 1

    System

    Overall goals, boundary conditions and system requirements of the plant – e.g. output, site, permitting. This is where planning, assignment and release take place.

  2. Layer 2

    Plant integration

    Interfaces and balances between assemblies: heat, material flows, pressures, temperatures. This is where we make sure the parts fit together.

  3. Layer 3

    Assemblies

    Detailed development of the individual components – lens field, optics, heat storage, DAC, electrolyser, synthesis – in parallel and with their own internal rounds.

The closed loop

  1. 01Plan

    A planning round assigns tasks to the assemblies.

  2. 02Develop

    The assemblies work in parallel and propose results.

  3. 03Release

    The next planning round reviews and releases – with evidence for every node.

  4. 04Feedback

    If a file or requirement changes, everything that depends on it is flagged as “suspect” across all layers until it is confirmed or revised.

Viewer of the engineering system showing requirements, components and dependencies across several rounds
Our traceability viewer (test scenario): rounds, assemblies and dependencies at a glance.

Manufacturing data

All the way to the machine: AP 242 and AP 238 (STEP-NC)

We generate design and manufacturing data in open, standardised ISO 10303 (STEP) formats. This keeps information lossless and traceable from requirement to machine tool.

AP 242 – Model-based 3D engineering

Geometry with product and manufacturing information (PMI) such as tolerances and fits in a neutral format – independent of the CAD system, archivable and exchangeable with partners.

AP 238 – STEP-NC (.stepnc)

Instead of machine-specific G-code, the .stepnc file describes what is to be made: features, machining steps, tools and tolerances – linked to the geometry from AP 242.

One chain, one origin

Every manufacturing file is booked in the engineering graph and traceable to its requirements. If the design changes, the affected manufacturing file becomes visible automatically.

Would you like to learn more about our engineering approach?

Send an email