Accenture Telecommunications Nordics

Telia Company AB

Data Lake / Data Warehouse Modernization

Telia wanted to become a more data-led telecom operator, but one of its major data warehouses had metadata for only a tiny fraction of fields, making it hard for teams to find, understand, govern, and use information such as call records and customer interactions efficiently.

10,000 data engineer hours
87,000 data fields
only 1% of its data had corresponding metadata
€700,000 in data entry costs

Reported impact

Business outcome

Telia reduced the cost and time of metadata creation, made internal data easier to discover and use, improved governance and privacy management, and created a stronger data foundation for future sales, service, and marketing AI use cases.

  • Compliance
  • Cost Reduction
  • Productivity Improvement

Solution

Telia and Accenture built a generative AI metadata-enrichment workflow on Amazon Bedrock to make a large telecom data repository easier to use at scale. The implementation starts with prompts, examples, and warehouse context that Bedrock uses to generate tags and descriptions for missing metadata fields. Accenture applied the approach across 87,000 data fields, then stored the outputs in a centralized metadata repository so teams could search, interpret, and trust datasets more easily. The repository also strengthens governance by making assets easier to manage under privacy and regulatory controls. To keep quality high, the workflow includes a human-in-the-loop review model that flags AI-generated descriptions for Telia's data experts to verify and maintain. Accenture also provided training and change-management support so Telia could operate the solution independently and extend the same data foundation into later generative AI use cases for sales, service, and marketing.

Data flow

Data-field definitions from Telia's warehouse are passed to Amazon Bedrock with prompts and examples so the model can generate tags and descriptions for missing metadata. Those outputs are stored in a centralized metadata repository and flagged through a human-in-the-loop review system so Telia's experts can verify accuracy before teams across the company use the enriched repository for analysis, governance, and downstream AI use cases.

Solution architecture

4 components · 4 layers
  1. Compute
    • Amazon Bedrock Generates metadata tags and descriptions for warehouse fields based on prompts and examples.
  2. Storage
    • centralized metadata repository Stores standardized descriptions so teams can find, understand, govern, and reuse data consistently.
  3. Serving
    • AI-generated metadata descriptions Provide the detailed labels and summaries that make previously hard-to-understand data easier to use.
  4. Governance
    • human-in-the-loop review system Flags AI-generated descriptions for expert validation so the metadata layer stays accurate and maintainable.

Architecture clues

  • AI-generated descriptions are flagged for human review.
  • Outputs are stored in a centralized metadata repository.
  • The repository improves governance and privacy controls for confidential data.
  • The workflow uses prompts and examples to generate metadata descriptions.

Evidence from the source

"Accenture used Amazon Bedrock to analyze Telia’s data and automatically populate corresponding metadata descriptions."
"It relies on a 'human-in-the-loop' review system that flags AI-generated column descriptions"
"leverage Amazon Bedrock, building an intelligent solution that updated tags and descriptions for 87,000 data fields"
"only 1% of its data had corresponding metadata"
"saving Telia 10,000 data engineer hours and €700,000 in data entry costs."
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Accenture

    Telia Company AB customer story

    First-party
    https://www.accenture.com/en/case-studies/ai-data/telia-supercharges-its-data-with-gen-ai
    Source type
    Vendor-published customer story
    Published
    May 22, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page May 22, 2026 · Accenture · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.