DATA PIPELINES
From the signal to a table someone trusts
AI and reports rarely fail on the model. They fail on the path before it: the signal is there, the table is not, or nobody owns the number. I build that path — from the sensor or system to a state operations and IT can actually use.
Who this is for
IT and operations in mid-sized firms who notice: the numbers sit in five systems, the shift needs one, and nobody can deliver it without hand work.
Not for a platform you are meant to buy and fill yourselves. Not for a team that wants to hand over all of IT.
What a pipeline means here
A source, a target, someone who needs the number. In between, quality and freshness: does the value arrive complete, and on time? At the end, a table or an interface someone opens — not a graveyard of jobs.
The source can be the hall, a line-of-business system, or both. Where the data may go — on site, EU, a chosen cloud — we settle first. The pipeline follows the rule, not the other way around.
- Which source, which target, who needs the number.
- Keep the first path small enough to check.
- Make completeness and freshness visible — not only 'the job is green'.
- Hand over so your team knows the path. Operations only if agreed.
What I do not do
No 24/7 platform as a subscription. No replacement for your IT. No promise that every legacy system is 'connected' in one sprint.
No invented metrics and no tool list sold as the work. If the source is the machine, the first look often belongs on the machine-data page — not a slide about orchestrators.
Bremen and remote
Based in Bremen. The work is remote for companies across Germany. The pipeline can run on-prem or in the EU; residency decides that, not a cloud default.
Project-based, clearly bounded. A first call, a first limited path, then you decide how to continue.
How we start
A few sentences: which source, who needs the number, may the data leave the building. Then a proposal for a bounded first path — often visible in a few weeks.
If BAFA is in the room, the funding question stays with your advisor. I build the IT side. If the data must not leave, on-prem belongs with it.
Questions
- Is this the same as machine data?
- Machine data is often the source. The pipeline is the path to the table someone uses. They hang together; the start sits where your gap is.
- Which tools do you use?
- The ones that fit the source and the target — not a fixed platform you have to buy. The tools are a means. The delivery is a path someone trusts.
- Do you run the pipeline afterwards?
- Only if we agree. The default is handover and documentation so your team can keep going. No quiet wrapping of operations.
- Does this work remotely?
- Yes. The office is in Bremen; the projects are remote in Germany. On site when the hall or the server room decides it.