Capgemini Manufacturing global

TE Connectivity

Enterprise Knowledge Search

TE Connectivity needed to help product-development teams find and reuse engineering knowledge trapped in dozens of incompatible systems without spending hours searching documents or depending on subject matter experts.

2.5 million documents ingested in three months
75 million engineering documents spread across 66 different databases
Access granted to 8,000 engineers at launch
Productivity increased five to 10 times for product development

Reported impact

Business outcome

TE Connectivity gave engineers a secure way to search and summarize proprietary knowledge much faster, reduced time spent navigating siloed systems, and created an enterprise platform that can scale as more content is ingested.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

TE Connectivity, Capgemini, and AWS built TELme as a generative-AI research environment that turns scattered engineering knowledge into a searchable, conversational workspace. The program ingested 2.5 million documents in just over three months and was designed to scale toward 75 million documents held across 66 databases. AWS supplied the cloud infrastructure plus managed services including Amazon Bedrock and Amazon OpenSearch Service, while Capgemini used a retrieval-augmented generation architecture to combine those services with Claude 3.5 and TE's proprietary data. The result is a secure interface where engineers can search, summarize, and retrieve technical information without trawling through siloed systems or relying on subject-matter experts to answer basic questions. TELme is organized under a single API, continues to ingest more content, and is refined daily through joint feedback and governance so it can serve product-development teams at enterprise scale.

Data flow

Engineering and operational documents are ingested from dozens of databases, indexed for search and retrieval, combined with proprietary context through a RAG architecture, and surfaced through TELme so engineers can ask questions and receive summarized answers in a secure UI.

Solution architecture

4 components · 2 layers
  1. Compute
    • Amazon Bedrock Hosts the generative AI foundation-model services used in the enterprise research workflow.
    • Claude 3.5 Acts as the underlying model used by TELme against TE's proprietary data.
  2. Serving
    • TELme Provides the conversational research interface that lets engineers search and summarize internal knowledge.
    • Amazon OpenSearch Service Supports search, analytics, and retrieval across the ingested engineering corpus.

Architecture clues

  • The cross-company team continues to ingest more content and refine the system daily
  • The solution is organized under a single API
  • The target corpus was scheduled to expand to all 75 million engineering documents
  • The team used retrieval-augmented generation to combine TE data with foundation models

Evidence from the source

"2.5 million engineering documents"
"AWS supplied the cloud infrastructure and fully managed services, such as Amazon Bedrock ... and Amazon OpenSearch Service"
"Capgemini used retrieval-augmented generation (RAG) ... to integrate these services into an enterprise-scale solution."
"Product development teams needed to sift through countless documents scattered across dozens of incompatible systems to conduct background research."
Transparency Evidence & methodology 90/100 reference value · 91% 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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence91%
  • 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
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/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. Capgemini

    TE Connectivity boosts product development with a knowledge hub - Capgemini

    First-party
    https://www.capgemini.com/news/client-stories/te-connectivity-boosts-product-development-with-a-knowledge-hub/
    Source type
    Vendor-published customer story
    Published
    May 15, 2025
    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 15, 2025 · Capgemini · 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.