Data Foundation

Data shared between Saudi entities, with an owner, a contract and a purpose

Data products from Bilytica give Saudi enterprises and entities a way to share data with an owner, a contract and a purpose. We turn shared datasets into governed products with defined interfaces, quality commitments, discovery, an access workflow and a registered purpose per consumer, so teams stop rebuilding copies and every share stands up to PDPL questions.

1

Producer domain

  • Owns the source
  • Publishes a contract
2

Platform standards

  • Classification and access
  • Quality and freshness tests
3

Marketplace

  • Searchable catalogue
  • Documented definitions
4

Consumer

  • Analytics and reporting
  • Models and agents
Usage and issues reported by consumers become obligations on the producer
Last updated: Reviewed by Dr Sari Al Qahtani

Key facts

What it doesWe turn shared datasets into governed products with defined interfaces, service commitments and a registered purpose per consumer, so teams stop rebuilding copies and every share stands up to a PDPL question.
How the work runsProducer domain, Platform standards, Marketplace, Consumer.
Typical timelineAgreed after a scope review of your data and priorities.
Engagement modelA scoping conversation first, then a defined first release with acceptance gates.

The story in one minute

From a familiar problem to a clear result

How we build your trusted data platform

Delivery flow

  1. AssessSource map and data quality baseline
  2. DesignTarget architecture and data model
  3. BuildPipelines, cleansing and Bronze/Silver/Gold layers
  4. GovernOwners, rules, lineage and access
  5. RunMonitoring, support and handover

What cleansing looks like

  • Riyad / RIYADHRiyadh
  • Customer A ×2One customer record

A typical customerCDO, CIO and CTO · Reuse instead of rebuilding.

  1. Today

    Teams keep rebuilding the same datasets because nobody can find or trust existing ones.

    Data has no clear owner, description or quality promise.

  2. What we do

    We turn key datasets into owned data products with a clear description, quality checks and simple access through one catalogue.

  3. What you get
    • Owned data products
    • One searchable catalogue
    • Quality promises per product
    • Controlled sharing

How we work

Simple steps, one team

  1. 1

    Understand

    Agree the goal and the decisions it serves.

  2. 2

    Prepare data

    Connect, clean and check the data it needs.

  3. 3

    Build

    Package datasets as products with owners.

  4. 4

    Run and improve

    Track use and quality, add products.

Option 1

Quick review

Pick the first datasets to productise.

Option 2

First solution

A first set of products and catalogue.

Option 3

Scale up

Products across every domain.

New to a term? Data and AI glossary

Customer examples

How it worked for others

Client names are withheld. The stories are real.

A Saudi telecom operator

Customer data product

Before

Marketing, care and network teams each maintained their own customer extract, and none of them agreed on subscriber status.

What we built

A single subscriber data product with a published contract, quality commitments and a governed access route for every consuming team.

After

The private extracts were retired and campaign and care decisions ran on the same subscriber view.

A public-sector authority

Cross-entity sharing

Before

Data sharing between departments happened through email attachments and one-off exports, with no record of what had been shared.

What we built

A catalogue of classified data products with defined access tiers, an approval workflow and full logging of every grant.

After

Sharing moved onto a governed route and the authority could show exactly who held which data and why.

An industrial group

Asset data products

Before

Every reliability initiative began by re-deriving the same sensor and maintenance history from scratch.

What we built

Curated asset and maintenance products with tested definitions, published once and consumed by the analytics and modelling teams.

After

New reliability work started from a trusted baseline rather than repeating the same preparation.

Clients

Organisations we work with

Across banking, healthcare, government, retail, energy and telecom.

Carrefour
STC
Fortum
Marriott International
United Utilities
Mobily
PepsiCo
H&M
Ericsson
Nordisk Film
Posten Bring AS
Norgesgruppen
Central Bank — Gulf Region
Public Investment Fund
Integrys Energy Group
Getinge
Entra
Australia Post
Roche
Ministry of Health
Swedbank
SpareBank 1
Telia Company AB
Danfoss
Kahoot!
Nesma Partners
Gentian Diagnostics
Lufthansa
Sokos Hotels
BHP Group
Emdad Al Khebrat (إمداد الخبرات)
ICA Gruppen
Qt Group
Vodafone
Ministry of Interior
Skatteverket — Swedish Tax Agency
Labster
Türk Telekom
State Bank of Pakistan
Arla Foods
SchoolSoft
Deloitte
Statkraft
DHL
Saudi Cement
Sinch
Zalora
Claned Group
Hurtigruten AS
Ameeri Dewan
MT Højgaard
SEB
Salling Group
Kela — Finnish Social Insurance Institution
YIT
TDC Net (Nuuday)
Bayer
NAV — Norwegian Labour & Welfare Administration
Visma
Novo Nordisk
Ministry of Hajj and Umrah
NEOM
SimCorp (Deutsche Börse)
Najm Insurance Services
Ooredoo
Audi
Novartis
LEGO Group
Skanska
Vero — Finnish Tax Administration
Jeudan
Nykredit
Tivoli A/S
Planmeca
Mölnlycke
Jacobs Engineering
Kesko
Konecranes Plc
NetCompany Group
Albert
Försäkringskassan — Swedish Social Insurance Agency
Kojamo
DSV A/S
Equinor
Volvo Group
Ørsted
VR-Yhtymä Oyj — Finnish State Railways
Sanoma Pro
Viaplay Group AB
Orion Pharma
Standard Chartered Bank
Vattenfall
Nordea Bank
Arp-Hansen Hotel Group
Kongsberg
Itslearning
DNB Bank
S Group
Nokia
E.ON
SkiStar AB
Schibsted Media Group
Danske Bank
Coca-Cola
Photocure
Credito Emiliano (Credem)
AT&T
Veidekke
Tietoevry
Walmart
Alinea Education
OP Financial Group
KONE
People — people-ksa.com
Deutsche Telekom
Elisa Oyj
Imam Abdulrahman Bin Faisal University
Castellum
Elm Company (إلم)
Warner Bros. Discovery
Unilever
SKF
Neste Corporation
Saudi Water Partnership Company (SWPC)
Scania
Finnair Plc
Intercity Istanbul Park
Coloplast
DirecTV
Ministry of Municipal & Rural Affairs
National Oil Company
Wärtsilä
Orkla
Andel
Yara International
Scandic Hotels Group
Sanoma Group
Telenor ASA
A.P. Møller-Mærsk
Shell
FAQ

Frequently asked questions

Is this data mesh? Our last attempt at that failed.

It borrows the ownership idea and drops the ideology. Most failures come from federating responsibility without providing a platform that makes doing it properly the easy path.

Our domain teams do not have data engineers.

Then start narrow. A small number of products owned by the central team, with domain owners accountable for definitions, is a workable first shape, and it is often where organisations should stay.

How do we stop this becoming another unused catalogue?

By making the catalogue the only route to access. A catalogue that only describes data gets abandoned; one that grants it stays current.

Do we need a new tool for this?

Rarely. Most estates already own a catalogue and an access mechanism that are underused. We would rather make those work than add another product.

How does this relate to the central platform?

Data products sit on top of it. The platform provides storage, standards and enforcement; the products provide the interface teams actually consume.

Who pays for a shared product?

We usually recommend central funding for the platform and domain funding for the products, with consumption visible to both so the conversation stays factual.

What are the stages of Data Foundation work?

The work runs in these stages: Producer domain, Platform standards, Marketplace, Consumer.

What does "We start with the products people already fight over" mean for Data Foundation?

Customer, product, asset and transaction views deliver the visible relief that earns support for the operating model behind them.

Cookie & Privacy Notice

We use cookies to improve your experience and analyse site traffic, in line with our Privacy Policy and the Personal Data Protection Law (PDPL). You can keep essential cookies only.