Thurn-und-Taxis-Platz 6 Frankfurt am Main 18 jobs open at present
Discuss a programme

Projects

Three project types, specified without client names. Each runs through the same four stages and ends in an output the operator keeps.

Light travelling through fibre

Stages

We start with the physical system and the obligations around it, then design the IT. Every phase ends with a document or a running component that the client owns.

  1. 01

    Establish the facts

    We map the assets, systems, data flows, contracts and regulatory duties as they are today. Interviews are backed by system exports and site visits where needed. The output is a baseline that client teams and funders can both rely on.

  2. 02

    Design the target

    We set out the target architecture, the decisions it depends on and the options we rejected, with reasons. Security, data protection and funding conditions are design inputs from the first draft.

  3. 03

    Deliver in increments

    We split delivery into packages that can be tendered, built and accepted separately. Each increment has acceptance criteria agreed in advance, and we work alongside client teams and suppliers rather than around them.

  4. 04

    Hand over and evidence

    We close with operating documentation, test records and the evidence pack that auditors or funding bodies require. The client's team should be able to run and extend the system without us.

Illustrative. Each entry specifies a type of project we take on. None describes a named client.

Technical annex for a cross-border CEF Energy application

Initial state
A regional distribution system operator joins a cross-border consortium preparing a Connecting Europe Facility Energy application. The project concept is sound, but the IT and data sections are thin and the work packages do not match what the partners' systems can deliver.
Scope of work
We review each partner's documentation for metering, SCADA and data platforms, draft the target architecture for shared grid data, and restructure the technical work packages with deliverables and milestones that can be verified. We also outline the security and data-sharing arrangements between partners.
Output
An application whose technical sections hold together, a shared architecture the partners have agreed on, and a delivery plan that can be used from day one if the grant is awarded.

Smart meter data platform for a municipal utility

Initial state
A Stadtwerk is installing smart meter gateways and must offer dynamic tariffs, but meter data still reaches billing and grid planning through separate, partly manual routes.
Scope of work
We document the current data flows, design a meter data platform that serves billing, customer portals and grid planning from one source, and prepare the tender for the gateway administration and platform components. We define interfaces, data quality rules and the operating model.
Output
A target architecture and procurement package the utility can tender, a phased migration plan, and a clear split of responsibilities between the utility's IT, its grid department and external service providers.

CSRD and taxonomy data pipeline for an industrial group

Initial state
An industrial group that remains in CSRD scope after the Omnibus changes produced its first sustainability statement with heavy manual effort. Its auditor has asked for better traceability of energy, emissions and taxonomy figures.
Scope of work
We map ESRS datapoints and taxonomy KPIs to the group's ERP, energy management and site systems, design automated pipelines with documented lineage, and define the controls each data owner performs before figures reach the report.
Output
A reporting data model the finance and sustainability teams share, documented lineage for each material figure, and a control framework prepared for assurance.

Talk to us about your programme

Tell us about the system, the funding context and the timeline, and we will come back to you to arrange a first call. Email contact@feldwerkdigital.com.

contact@feldwerkdigital.com