Hamburg Worked from Barcelona Supervised by the HmbBfDI Same hour as us

Hamburg.
Port-scale documents.

Hamburg runs on paperwork and on weather. Germany's largest port, a publishing industry with archives going back generations, aircraft manufacturing and an offshore wind sector all produce the same underlying problem in different clothing: far too many documents and readings, arriving continuously, mostly routine, occasionally very much not.

Last reviewed 5 September 2026 · Engineering guidance, not legal advice.

WHAT IS ACTUALLY DIFFERENT HERE

An authority with form on employee data

Hamburg is a city state, so it runs its own data protection authority, the Hamburgische Beauftragte für Datenschutz und Informationsfreiheit. It is known internationally for enforcement around the excessive recording of employees' personal circumstances, which is worth remembering in a city full of shift work, terminal operations and driver scheduling. Any system that can be read as monitoring staff performance needs its logging scope decided deliberately at design time, not inherited from whatever the framework writes by default.

Port documents are only difficult at the edges

Bills of lading, customs declarations, dangerous goods documentation, delivery orders and terminal handovers arrive as a mixture of structured messages, PDFs, scans and occasionally photographs of paper. Ninety-odd per cent of them are routine and can be handled without a person. The entire value of the system is in what it does with the rest: whether it recognises that it is unsure, routes the exception to someone who can resolve it, and records why. A pipeline that quietly guesses on the hard cases is worse than no pipeline, because it moves the errors somewhere nobody is looking.

Archives that are technically online and practically unreachable

Hamburg's publishing and media groups sit on decades of material that has been digitised without becoming findable — inconsistent metadata, rights information in a separate system, and a search box that matches words rather than meaning. Retrieval over an archive is the least glamorous AI project in the sector and reliably one of the most valuable, provided the rights position is resolved first, because being able to find something is not the same as being allowed to reuse it.

No local region, and for turbines it barely matters

German cloud workloads mostly land in Frankfurt; there is no Hamburg region, and for the systems described here that is close to irrelevant. Offshore wind and aviation data face a different constraint anyway: bandwidth off the asset, not distance to a datacentre. The sane pattern aggregates and filters at the edge and moves summaries rather than raw signal. Provider region availability changes over time, so confirm it against current documentation rather than against this page.

THE WORK THAT COMES OUT OF THIS CITY

Freight and port logistics is the largest single source of work here, and it is more interesting than it sounds. A shipment generates a chain of documents produced by different parties in different formats and different languages, each of which has to agree with the others before goods move. Most of the labour is reconciliation: reading a document, finding the corresponding entry somewhere else, and deciding whether a discrepancy is a typographical difference or a real problem. That is a good fit for a system precisely because a human doing it at three in the morning is not at their best, and it is a dangerous fit unless the system is honest about its own uncertainty. Our logistics document pipeline describes the shape we use, with the exception path as the main feature rather than an afterthought.

Publishing and media groups arrive from the opposite direction. Their problem is not throughput but recall — decades of articles, images and broadcast material where the person who knew how it was filed has retired. Retrieval systems here live or die on the metadata work nobody wants to fund, and on being able to show where an answer came from. The architecture is covered under retrieval systems.

Aviation manufacturing and the maintenance businesses around it bring configuration and compliance records with a long life and a hard traceability requirement, which is a document problem with an engineering accent.

Renewables, and offshore wind in particular, bring sensor histories, service reports and weather data that only become useful when joined. Failure prediction on rotating equipment is a genuinely well-suited application, and it is described under predictive maintenance — with the same caveat that reaches every asset-heavy project: the model is easy and the data plumbing is not.

HOW A HAMBURG PROJECT ACTUALLY RUNS

Discovery where the documents arrive

Barcelona to Hamburg is a direct flight of well under three hours, and for freight work the first workshop belongs next to the people handling exceptions rather than in a meeting room upstairs. Half an hour watching a clerk resolve a mismatch is worth a week of specification.

Then remote, with the whole day shared

Hamburg and Barcelona are on the same clock, so there is no offset to plan around. For operations that already run in shifts, having no additional handover delay in the project itself is a small mercy.

And back for handover

Your team takes ownership in person, including the part everyone skips: what to do when the pipeline stalls at two in the morning. Afterwards it runs in your systems and your accounts.

QUESTIONS

QUESTIONS — 5

No. We have one office and it is in Barcelona. We come to Hamburg for discovery and handover and for the site visits that make freight work comprehensible. There is no local team and we are not going to imply one.

Usually, and the honest answer starts with a question rather than a yes: what does it expose. Some of these systems have modern interfaces, some have a database you are allowed to read, and some have a nightly file drop that everyone pretends is an integration. All three are workable. Which one you have decides most of the timeline, which is why we look at it during discovery rather than after signing.

Less accurate than people assume, provided the system knows when it is unsure. A pipeline that handles the routine majority and escalates the rest with a clear reason removes most of the labour and adds no risk. A pipeline that is slightly better on average but guesses silently on the hard cases is the one that causes an incident. We build for the first and measure it against your own historical documents, not against a public benchmark.

That depends entirely on what gets logged, and it is a decision rather than an accident. We scope logging to what the system needs to work and to what an auditor would need to reconstruct a decision, and we write down what is not collected. Where a works agreement is needed, having that description in advance makes the conversation shorter. Your HR and legal functions own the agreement itself.

Our ranges are on the pricing page, in euros and exclusive of VAT, and they do not vary by city. Document pipelines are one of the few things we can scope tightly early, because the volume and the document types are usually known before anyone talks to us.

Keep reading

Architecture

Logistics Document Pipeline

→

Architecture

Retrieval Systems (RAG)

30-minute technical call · no deck