Skip to main content
Strukata

Data management

Data management: one source of truth for your core business data

In most organisations, customer, product and order data lives in several systems and a handful of spreadsheets, each copy slightly different. Reports disagree and nobody is sure which number is right. Strukata's data management work brings that core data together in one trustworthy, documented foundation, with data quality checked on the way in and ownership agreed in plain terms.

Discuss your data

What data management solves

Data rarely goes wrong in one dramatic moment. It drifts. A customer is added twice with a different spelling, a product code changes in one system but not in another, an export is pasted into a spreadsheet and lives on there. Each difference is harmless on its own; together they mean that finance, sales and operations work from different versions of the same facts.

Good data management makes one version authoritative. For your core entities, the master data such as customers, products, suppliers and locations, it is clear where the record lives, who maintains it and which rules it must meet. Other systems and reports then draw on that single source of truth instead of keeping their own copy.

Signs your data quality needs attention

You don't need a large data team to have a data problem. Common signs include:

  • Two reports on the same subject show different numbers
  • Duplicate or outdated customer and supplier records cause errors in invoices or deliveries
  • People keep private spreadsheets because they don't trust the system
  • Every report starts with manual cleaning and checking
  • Nobody can say with confidence what a field or KPI actually means
  • An automation, reporting or AI project is on hold because the data isn't ready

How we approach master data management

We start with the questions the data has to answer and the processes that create it, not with a tool. Together with the people who enter and use the data, we trace where each core entity comes from, where copies exist and where they diverge. We record the current data quality as a baseline: duplicates, missing fields, conflicting values.

Then we design the foundation: a clear data model, the source system for each entity, and quality rules that validate data on the way in. Depending on your situation, that may be a better-configured system you already own, integrations that keep systems in step, or a lightweight data warehouse for a mid-sized organisation. We build in short cycles and fix quality issues at the source, rather than cleaning the same errors every month.

Governance is part of the work, done sensibly rather than bureaucratically: each core entity gets an owner, definitions are documented, and access is arranged so people see what they need and nothing more. We finish with monitoring on critical records, training, and a measurement against the baseline.

What it delivers

A data foundation your organisation can rely on and build on.

  • A single source of truth for customers, products, orders and other core entities
  • Data quality issues surfaced and fixed at the source, with monitoring that flags new ones
  • Documented definitions, so everyone means the same thing by the same field
  • A foundation that reporting, automation and AI can safely build on

Frequently asked questions

Where do we start with data management?

With one area where inconsistent data visibly costs time or causes errors, often customer or product data. We map how that data is created and used, measure its quality, and fix it properly before moving on. Starting small keeps the effort proportionate and shows early whether the approach works for you.

Who owns our data?

Your data remains yours, during and after the engagement. Within your organisation we help you assign a business owner to each core entity, so it is clear who decides on definitions and corrections. That ownership is what keeps data quality from slipping once the project is finished.

How does data management relate to GDPR?

Bringing data together is a good moment to check that personal data is stored only where it is needed, kept no longer than necessary and visible only to the people who need it. Where our work involves processing personal data on your behalf, we act as a processor under a separate data processing agreement. Legal judgements remain with your privacy officer or legal adviser.

Which tools do you use?

That depends on what you already run. Often the right place for master data is a system you already own, configured properly, with integrations keeping other systems in step. Where a separate foundation is needed, we choose established tools that fit your environment and that your team can maintain.

Do we need a data warehouse?

Not always. A data warehouse makes sense when data from several systems has to be combined for reporting or analysis. If the problem is mainly duplicate or inconsistent records in your operational systems, fixing them at the source and connecting systems properly is often enough.

How is data management different from business intelligence?

Business intelligence turns data into reports and dashboards; data management makes sure the data underneath is correct and consistent. Without that foundation, dashboards simply show the inconsistencies faster. The two can be combined in one engagement, with the data foundation coming first.

Green infrastructure

Krinkels

Krinkels

Prediction model for tree condition

For Krinkels we built a prediction model that forecasts tree condition, so inspections and maintenance can be planned where they matter most instead of on fixed schedules.

AI integration · Data management

Motorsport

Bern Racing Team

Bern Racing Team

Data analysis dashboard for Formula E cars

Upcoming

For the Bern racing team we're building a data analysis dashboard to measure and compare the performance of their Formula E cars.

Business intelligence · Data management

Climate & environment

GlacierOS

GlacierOS

Measuring and protecting glaciers

Upcoming

GlacierOS is a system for measuring glaciers, and in a later stage protecting them: proprietary technology designed to protect the firn layer.

Custom software · Data management

Not sure which number is right?

Tell us where your data disagrees, and we will help you decide where to start.

Discuss your data