Data governance and GDPR for Ingolstadt organisations: controls that produce evidence

Data governance fails when it arrives as a policy document and a committee. It works when it is built into the tools people already use.

This page covers data governance and compliance for analytics estates in Ingolstadt: what the federal commissioner (BfDI) and the Land data protection authorities expects under the EU GDPR and the Bundesdatenschutzgesetz (BDSG), which sector rules bite hardest given the local economy of automotive and mobility, energy generation and supply, and industrial machinery and engineering, and how to implement controls in Microsoft Purview and Power BI that produce evidence rather than paperwork.

What the federal commissioner (BfDI) and the Land data protection authorities expects of an analytics estate

Under the EU GDPR and the Bundesdatenschutzgesetz (BDSG), the obligations that touch analytics most directly are data minimisation, storage limitation, access control, and the ability to answer access and erasure requests. Analytics estates fail these quietly: a warehouse accumulates every column from every source because it was easier than deciding, retention defaults to forever, and permissions are granted to individuals who then change role.

• Betriebsrat co-determination is the single most underestimated factor in German analytics projects: any reporting that could be used to assess individual employee performance generally needs a works agreement before launch.
• MaRisk and BAIT expectations mean financial-sector data lineage and documentation standards are explicit, not inferred.
• The Lieferkettensorgfaltspflichtengesetz requires supply-chain due-diligence data that most ERP estates do not hold in reportable form.
• GoBD rules on retention and immutability of accounting-relevant data affect how analytics copies of financial data are stored.

None of this requires a governance department. What it needs is a searchable catalogue, classification that is wired to retention and labelling rather than decorative, group-based access, and the ability to produce evidence without raising a ticket. All four are weeks of work, not years.

Sector rules that bite in Ingolstadt

Ingolstadt's economy means the governance conversation here is not generic. With major vehicle manufacturing and research and refining and energy activity shaping the local client base, these are the obligations that come up in practice.

Energy generation and supply

Market reporting obligations and NIS2 critical-infrastructure duties apply, and consumption data is personal data for domestic customers. Half-hourly or sub-hourly interval data at national scale, settlement runs that are revised months later, and metering that is partly estimated.

The practical consequence for an analytics estate is that access design cannot be retrofitted. Row-level and object-level security have to reflect how authority is actually delegated in the organisation, and the design needs testing from a non-privileged account rather than assumed from documentation.

Industrial machinery and engineering

Export control and dual-use classification data should be modelled explicitly where machinery is shipped outside the EU and UK. Typical systems in scope: ERP, PLM / CAD, project management, field service management and CRM.

Software and technology

Product telemetry on identifiable users needs a lawful basis and consent handling, and SOC 2 or ISO 27001 evidence often covers the analytics estate.

Who can see what, and how you prove it

This is the question that exposes an estate, and the fix is unglamorous. The difference is between an afternoon of investigation and a parameterised report. Individual grants accumulated over years require the first; groups that mirror your control model allow the second.

The sequence is always the same: extract the permissions that actually exist, design groups around how the organisation really delegates authority, migrate and remove the individual grants, then make the evidence self-service so your second line runs the report instead of raising a request. For a business in energy generation and supply, the groups normally need granularity by function and by entity or site.

Classification, labels and the export problem

Most estates lose control of data at the export button. The intent is almost always benign, which is precisely why policy alone does not stop it. Sensitivity labels applied in Power BI travel with the exported file, so encryption and access restrictions persist outside the platform, and export can be blocked entirely for specific labels or audiences.

The classification scheme has to align to the information security policy you already have rather than introduce a competing taxonomy, and retention has to be enforced against your actual obligation under the EU GDPR and the Bundesdatenschutzgesetz (BDSG) instead of kept forever by default. Every control is then verified from a non-privileged account, because the most common finding in a governance review is a restriction that was configured correctly and never actually tried.

Working with German organisations: the practical constraints

• Specification discipline is higher than in the UK: expect a written Fachkonzept and a documented acceptance process, and plan for it rather than resisting it.
• Works council consultation should be scheduled at the start of a project, not discovered during user acceptance testing.
• Many Mittelstand clients prefer German-language documentation and stakeholder sessions even where the project team works in English.

The most underestimated factor in German governance projects is works council co-determination. Any reporting that could be used to assess individual employee performance generally needs a works agreement before launch, and discovering that during user acceptance testing is expensive. We schedule that consultation at the start.

A 90-day plan that produces evidence

1. Days 1 to 15: assessAccess extract versus policy, data map, classification gaps, retention reality. Output is a risk-ranked remediation plan, ordered by exposure rather than by ease.
2. Days 15 to 35: defineOwnership assigned to named people, classification agreed, retention written against the real obligation, access standards set. None of it drafted in isolation from legal or the business.
3. Days 35 to 70: implementPurview scanning and catalogue populated, labels published and applied, access rebuilt onto groups, lineage switched on, suppression implemented in measures.
4. Days 70 to 90: evidenceAccess evidence reporting, audit pack generation, steward training, and the first governance review run with your team rather than for them.

That sequence works because each stage produces something usable on its own. If the programme stops after the assessment, you still hold a risk-ranked plan an auditor would accept. Book a technical review if you want that assessment for a Ingolstadt organisation.

We work across Germany and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Wolfsburg, Mannheim, Leipzig, Dortmund, Bochum and Karlsruhe.

Frequently asked questions