MongoDB Energy Italy

Eni

Document Processing · Enterprise Knowledge Search

Eni needed to make multilingual subsurface documents and extracted scientific data usable across geoscience teams, but its relational platform struggled with hundreds of thousands of documents, terabytes of unstructured content, and the complexity of creating comprehensive, searchable datasets for global research and drilling decisions.

hundreds of thousands of documents
more than 30,000 employees across 69 countries
terabytes of data

Reported impact

Business outcome

Eni improved platform performance and manageability, reduced development time and associated costs, gave scientists faster access to comprehensive subsurface datasets, and created a cloud-agnostic document platform that can support broader enterprise rollout and future generative-AI enhancements.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

Eni rebuilt its geoscience document platform on MongoDB Atlas with support from MongoDB Consulting. The new managed document data platform ingests processed text, tables, images, metadata, and AI-enriched outputs from subsurface documents, then exposes that information through search, dashboards, and custom applications used by geologists, engineers, and drilling teams. Atlas Search helps users filter relevant documents across years and geographies, while Atlas Charts gives non-developers a code-free way to visualize unstructured data in dashboards instead of exporting CSVs and spreadsheets. Atlas fits Eni's multi-cloud strategy and simplifies security, encryption, deduplication, scaling, and routine maintenance. The result is a shared knowledge environment that shortens development work, improves data completeness for research decisions, and provides the document foundation for NLP and generative-AI services that answer questions with grounded scientific context.

Data flow

Geoscience documents are extracted and enriched with AI, stored in Atlas as text, tables, images, and metadata, surfaced through Search and Charts for specialists and analysts, and fed into NLP and generative-AI services that retrieve relevant documents before answering questions.

Solution architecture

4 components · 3 layers
  1. Storage
    • MongoDB Atlas Acts as the managed document data platform for extracted geoscience content, metadata, and application data.
  2. Serving
    • MongoDB Atlas Search Lets scientists find relevant records across large multilingual document collections using a Google-like interface.
    • MongoDB Atlas Charts Provides code-free dashboards and visualizations over unstructured and extracted data.
  3. Uncategorized
    • MongoDB Consulting Supported Eni's migration, training, and architecture choices for the new platform.

Architecture clues

  • Atlas Charts is used alongside Power BI to visualize unstructured data with minimal coding.
  • Eni currently uses generative AI to retrieve relevant documents and uses LLMs to build answers.
  • The platform stores text, tables, images, and metadata extracted from documents.

Evidence from the source

Atlas Charts is really useful to visualize unstructured data.
Eni’s document management platform for geosciences offers an ecosystem of services and applications for creating and sharing content.
MongoDB Atlas is simple to integrate and makes it easy to ingest and deduplicate data from other systems.
The generative AI we’ve introduced currently creates vector embeddings from documents, so when a user asks a question, it retrieves the most relevant document and uses LLMs to build the answer.
Transparency Evidence & methodology 75/100 reference value · 77% 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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • 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 provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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. MongoDB

    Eni customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/eni
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Apr 24, 2024 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified May 28, 2026 · MongoDB · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.