Global Infrastructure Sherpa - 커스텀 엔터프라이즈 데이터

The infrastructure market, mapped and tracked

Global Infrastructure Sherpa brings infrastructure transactions and the companies involved into a structured dataset for analysis.

Who is doing what, with whom and where

GIS connects recorded infrastructure activity with named participants and their roles. Transaction records bring together the announcement, location, technology, parties and source reference, so users can examine company activity across events.

• 01:Infrastructure activity
  • Follow recorded partnerships and other transaction activity across technologies and markets, with announcement dates and source references.
• 02:Companies in context
  • See which parties are named in an event and the role GIS assigns to each. Repeated appearances provide a basis for examining a company’s activity over time.
• 03:Data for analysis
  • Structured records and CSV export support analysis in other workflows.

The data is the product.

Evaluate GIS records for use within your organization’s own systems and workflows.

• 01:Infrastructure transactions
  • The supplied GIS records identify infrastructure events with a headline, deal type, recorded status, country and technology classification.
• 02:Companies and recorded roles
  • The sample links named counterparties to transaction roles. This provides a starting point for examining participation and relationships across records.
• 03:Source traceability
  • The sample includes a source_url for each transaction. Source links allow recipients to inspect the underlying reporting and its context.
• 04:Existing record structure
  • The sample uses existing GIS fields and identifiers. Its field dictionary defines the delivered columns without introducing a new schema.
• 05:API or recurring CSV
  • API and programmatic delivery are separately agreed and priced in the supplied product materials. Recurring CSV is a delivery option to scope with the buyer.
• 06:A defined commercial scope
  • Agree the coverage, delivery frequency, permitted uses and commercial terms before recurring supply. The sample illustrates data for evaluation

Put infrastructure intelligence to work.

Potential uses of licensed GIS data within a buyer’s own environment.

• 01:Internal research
  • Bring transaction records and their source links into an existing research workflow, with company names and recorded roles available for investigation.
• 02:Company monitoring
  • Use recurring records to support monitoring of named companies and infrastructure themes. Delivery frequency and change handling must be agreed.
• 03:Market analysis
  • Group supplied records by existing country, technology and deal-type fields. Results describe the supplied coverage, not a complete census of the market.
• 04:Relationship analysis
  • Use recorded participation to examine which companies appear together and in what roles. Participation alone does not establish ownership or control.
• 05:Client-facing intelligence
  • Evaluate how GIS data could support a buyer’s client work. Client display, onward distribution and derived outputs require an agreed license scope.
• 06:Integration evaluation
  • Test the sample in the intended workflow before defining production requirements. Identifiers, formats and update handling should be reviewed together.

A concrete data product to evaluate.

Existing sample fields show what a recipient can inspect and test.

• 01:id · headline
  • An existing GIS record identifier and transaction headline provide the starting point for each supplied row.
• 02:deal_type · status
  • Recorded classifications describe the transaction. Interpret status using the dictionary and source context; it is not evidence of project completion.
• 03:country · technology
  • Existing geographic and technology classifications support selection and grouping of the supplied records.
• 04:announcement_date · created_at
  • The record contains both fields. Their definitions remain those in the supplied dictionary; they should not be treated as interchangeable dates.
• 05:counterpart_count · counterparts
  • The sample carries a counterpart count and named participants with recorded roles. Review the supplied representation when planning ingestion.
• 06:source_url
  • The source link remains part of the record, providing a route back to the reporting behind the transaction.

Start with the sample. Define the supply.

A proposed evaluation path for an enterprise data engagement.

• 01:Select coverage
  • Define the countries, infrastructure technologies and transaction coverage relevant to the buyer’s use case.
• 02:Test existing records
  • Review a focused sample and its dictionary. Test the data in the intended internal workflow and identify the information required for evaluation.
• 03:Agree delivery
  • Scope API or recurring CSV delivery, including cadence, format and operational requirements. Daily supply is a requirement to agree, not an established service commitment.
• 04:Define update handling
  • Agree how new records, corrections and identifiers will be handled. The sample does not establish a production update protocol.
• 05:License the intended use
  • Define internal use, client display, onward distribution and any derived outputs. Commercial terms should reflect the agreed scope.
• 06:Confirm the arrangement
  • Confirm delivery responsibilities, support and commercial terms before recurring supply begins. No production service level is established by this brochure.

Recorded activity, illustrated

Follow recorded partnerships and other transaction activity across technologies and markets, with announcement dates and source references.

Understand each transaction

From headline to detail

The screens show the transaction narrative, structured details, Deal Intelligence, Sherpa Notes and the source-article link.

Source: supplied GIS platform collage, September 2026. Transaction visual enhanced for presentation; source wording and figures retained. Sherpa Notes shown as captured. These values are separate from the Malaysian sample

Read the Sherpa Signal

Research and reports

The captured article brings a transaction headline, named parties, key facts and Sherpa Analysis into a published reading view.

Relationship network

See which parties are named in an event and the role GIS assigns to each. Repeated appearances provide a basis for examining a company’s activity over time.

DayOne

Actual GIS app screenshot. The visible network is filtered to the partner role; screen contents are unchanged.

Companies in context

See which parties are named in an event and the role GIS assigns to each. Repeated appearances provide a basis for examining a company’s activity over time.

Compare sector activity

Companies across technologies

The heatmap makes the recorded sector activity of multiple companies visible in one comparison view.

SECTOR ACTIVITY

• Company
  • RWE
  • Google
  • TotalEnergies
  • Ørsted
  • Shell
  • Vestas
  • NVIDIA
  • Copenhagen Infrastructure Partners
  • Iberdrola
  • OX2
  • ENGIE
  • Amazon
  • Nordex Group
  • Microsoft
  • Santander

Explore geographic activity

GEOGRAPHY ACTIVITY

• Company
  • Google
  • RWE
  • Nordex Group
  • TotalEnergies
  • Meta
  • Petrobras
  • GE Vernova
  • Shell
  • Copenhagen Infrastructure Partners
  • Amazon
  • BNP Paribas
  • Iberdrola
  • ENGIE
  • EDF
  • Equinor

Find organisations. Trace their relationships.

• FIND ORGANISATIONS
• TRACE COUNTERPARTY RELATIONSHIPS

Compare companies

Side-by-side company comparison

The captured Matchup view shows an overview of recorded activity and a role breakdown, distinguishing shared participants from those shown for each company.

Overview

• Metric
• ExxonMobil
• Aramco
• Total Deals: 5 / 1
• Network Size: 10 / 1
• Technologies: Gas / Industrial / Oil Gas / Oil Gas
• Markets: Gabon / Greece / Guyana / United States / Saudi Arabia

Role Breakdown

• Developer - 5 partners
  • Shared: None
  • Only ExxonMobil
    • Golden Pass LNG
    • Energean
    • HELLENiQ ENERGY
    • Global Infrastructure Partners
  • Only Aramco
    • Saipem
• Partner - 3 partners
  • Shared: None
  • Only ExxonMobil
    • bp
    • CF Industries
    • EnLink Midstream
  • Only Aramco
    • None
• Supplier - 2 partners
  • Shared: None
  • Only ExxonMobil
  • Only Aramco

Global infrastructure coverage

Recorded markets include the United States, United Kingdom, India, Australia, Brazil and Germany, as well as Malaysia. Scope can be selected for evaluation by market and technology.