TotalEnergies and OneTech already have a solid semantic foundation through TSF and SousLeSens (SLS). The strategic issue is adoption: leadership needs to see why governed meaning matters, where it creates measurable value, and how it fits the OneTech landscape across platforms, operations, data products, and AI.
The work builds on a first mission conducted from November 2025 to January 2026, the Cross-FPSO Semantic Preparation and Ontology Vetting Program, where Forvis Mazars assembled the team with NCOR, the National Center for Ontological Research. That mission validated TSF's alignment with BFO (Basic Formal Ontology, ISO/IEC 21838-2:2021) through a formal audit of the TE Business Objects ontology, and delivered a machine learning prototype that matched 23,000 Pazflor functional locations to Dalia equivalents to bootstrap cross-FPSO job card transfer for life extension planning. This second mission turns that validated technical foundation into a positioning narrative for TSF and SousLeSens within OneTech.
5 coordinated workstreams and 5 client-facing decks.
12 internal stakeholder interview profiles and 3 Voice of Peers interview profiles.
9 benchmarked tool profiles across semantic control, platform, graph, catalog, and AI layers.
25 strategic intelligence organization profiles backed by 26 evidence notes.
Management assets include the Executive Deck, one-pager, FAQ, use-case showcase, decision framework, RFI/RFP support, benchmark matrix, and evidence registers.
This deck is the strategic evidence layer. Use it to place the TotalEnergies question in a broader market context: control of meaning is becoming a strategic capability for AI-ready organizations, not a specialist modeling topic.
Executive summary
The most advanced organizations are converging toward the same pattern: models change, platforms change, but semantic assets become durable.
Fragmentation remains
Systems do not converge by themselves
Operational systems, documents, dashboards, copilots, and data platforms keep multiplying. The result is more access to data, not necessarily more shared understanding.
Stable asset
Meaning becomes reusable infrastructure
Healthcare, defense, finance, retail, cloud, and energy examples show the same move: controlled terms become ontologies, then knowledge graphs, then governed workflows.
Strategic hypothesis
Representation may beat model choice
The next advantage may not come from having a better AI model. It may come from having a better representation of operational reality.
Core message
Strategic semantic infrastructure lets an enterprise change AI models, platforms, and applications while preserving the governed meaning those systems depend on.
Why this matters now
AI makes knowledge easier to generate, but harder to organize.
The AI paradox
More output, less coherence
Organizations are accumulating documents, reports, dashboards, copilots, agents, vector indexes, and generated summaries without a shared model of the things those systems talk about.
Missing layer
Systems need shared entities
AI workflows need stable understanding of people, products, locations, processes, regulations, assets, events, evidence, and decisions.
What increases
Content volume.
Model experimentation.
Platform choices.
Agent workflows.
What does not automatically increase
Shared definitions.
Decision traceability.
Governed mappings.
Cross-platform meaning.
Result
More AI does not necessarily create more coherence. Semantic infrastructure is the control layer that keeps AI grounded in the same reality as operations.
Market interest signal
Search interest for ontology AI is moving from niche to visible demand.
Google Trends index, worldwide monthly interest
Ontology AIForward deployed engineer
Executive readout
Both terms stayed near zero through 2024, then accelerated sharply from mid-2025.
By May 2026, forward deployed engineer reaches the Trends maximum of 100, while ontology AI reaches 66.
The signal is not mature adoption. It is market attention moving toward ontology-backed AI delivery and embedded implementation roles.
Implication: semantic infrastructure is becoming part of the AI operating model, not a specialist data architecture topic.
Semantic infrastructure
The market uses similar words for different layers. The winners increasingly combine them.
Semantic layer
Analytics
Defines business metrics, reporting logic, dimensions, and reusable calculation meaning.
Knowledge catalog
Discovery
Documents data assets, ownership, lineage, quality, access, and governance responsibilities.
Knowledge graph
Relationships
Connects entities, events, documents, and facts so systems can traverse operational context.
Gives AI agents approved concepts, context, provenance, and action boundaries.
Observation
The strategic infrastructure is not one tool. It is the governed connection between meaning, evidence, systems, and AI execution.
Semantic authority
Semantic authority is not the same as platform capability.
Platform capability
What platforms can do
Integrate data.
Visualize workflows.
Query graphs.
Automate actions.
Support AI search and agents.
Semantic authority
What the enterprise must own
Authoritative identifiers.
Approved definitions.
Relations and constraints.
Mappings and provenance.
Validation and inference expectations.
Internal strategic assessment
A platform object model, property graph, schema, dashboard, or AI summary may support operations. It does not automatically prove that enterprise meaning is preserved, governed, exportable, or reusable outside the platform.
Decision rule
Operational acceptance should not be confused with semantic acceptance.
Evaluation rule
Evaluate semantic claims by evidence, not terminology.
The issue is not whether a platform says ontology, knowledge graph, semantic layer, or AI-ready data. The issue is whether governed meaning remains controlled, testable, and portable.
Authority
What model is authoritative?
There must be a designated model for enterprise meaning, with ownership, scope, and version control.
Portability
Can it leave the platform?
Definitions, identifiers, relations, constraints, mappings, and provenance must be inspectable, exportable, reconstructable, and reusable.
Traceability
What semantic loss is accepted?
Derived products may omit detail when needed. They should not contradict, redefine, or silently drift from approved meaning.
COMEX test
If the enterprise cannot inspect, govern, validate, export, and reuse its meaning outside a vendor system, it does not yet control its semantic infrastructure.
Strategic risk
Semantic lock-in is the next vendor lock-in.
Traditional lock-in
What leaders already recognize
Infrastructure dependency.
Data residency.
API coupling.
License and switching cost.
Emerging lock-in
What AI makes more dangerous
Meaning embedded in object models.
Relationships hidden in platform logic.
Rules buried in workflows.
Agent context controlled by vendors.
Why it matters
If enterprise meaning exists only inside a platform, future migration becomes semantic rework. AI increases the risk because agents act on hidden context, not only visible data.
Strategic position
Vendors should compete to operationalize meaning, not to own or redefine it.
Cross-sector evidence
The same lesson appears across sectors: durable meaning outlasts systems.
Healthcare
SNOMED
Clinical interoperability requires shared definitions. The ontology becomes infrastructure, not an application.
Life sciences
OBO Foundry
Federated ontologies let research organizations collaborate without redesigning meaning.
Defense
Mission models
Interoperability starts with common operational understanding, not APIs alone.
Internet platforms
Google
Entity-centric systems outperform document-centric systems for search, assistants, and recommendations.
Cloud and open source
AWS / Linux
Standard infrastructure layers become reusable foundations. Semantic assets may follow the same path.
Strategic lesson
Organizations that control their semantic infrastructure are better positioned to change models, adopt platforms, integrate acquisitions, comply with regulation, and preserve institutional knowledge.
Emerging stack
Semantic infrastructure connects systems, data, meaning, graph memory, and AI execution.
How to read it
Data products make evidence reusable, but the ontology defines what that evidence means.
The knowledge graph connects approved meaning to operational memory: entities, events, provenance, and context.
Agents consume governed context, execute workflows, and leave an audit trail back to operations.
Strategic point: platform choice matters less than control of the semantic contract.
Cross-sector evidence landscape
The organization evidence points to the same architecture pattern.
Department of War / DoD and ICDefense ontology standards
U.S. Customs and Border Protection / CBPBorder operations ontology
National Institutes of Health / NCBO BioPortalBiomedical infrastructure
NATO research communityDefense interoperability
GoogleSearch and AI infrastructure
MicrosoftEnterprise data and AI
Amazon Web ServicesCloud graph infrastructure
IKEAConsumer goods, retail, and digital experience
EDM Council FIBOFinance
Goldman Sachs / FINOS LegendFinance
JPMorgan ChaseFinance
Gene Ontology ConsortiumLife sciences
Open PHACTSLife sciences / pharma
AstraZenecaLife sciences / pharma
RocheLife sciences / pharma
NovartisLife sciences / pharma
PfizerLife sciences / pharma
DARPADefense research
BoeingAerospace
Airbus SkywiseAerospace
The Open Group OSDUEnergy
EquinorEnergy
Organization profile | Ontology-centric
Palantir Technologies
Probably the most visible commercial success story for ontology as operating architecture.
Signal
Palantir is the clearest commercial proof that ontology can become operating architecture, not a documentation layer.
Key points
Foundry, Gotham, and AIP center work around object types, properties, links, actions, functions, and security controls.
The ontology connects data, logic, decisions, and system write-back so users and agents operate on shared business objects.
Its market message turns semantic structure into an operating system for decisions, not a back-office data model.
Evidence
Palantir describes the Ontology as the system at the heart of its architecture and defines core concepts for objects, links, actions, functions, and operational workflows.
Decision systems need a governed model of the business before AI agents can act with confidence.
Organization profile | Ontology-centric
OBO Foundry
The gold standard for open, interoperable biomedical ontologies.
Signal
OBO shows that ontology value depends as much on governance and reuse discipline as on formal modeling.
Key points
The Foundry coordinates interoperable biomedical ontologies under shared design principles and community review.
Ontologies such as ECO encode evidence and conclusions so research claims can be connected and reused.
The model proves that federated domains can share meaning without collapsing into one central application.
Evidence
OBO publishes open ontology principles and reusable biomedical ontologies, including the Evidence and Conclusion Ontology for representing evidence-backed scientific assertions.
Mature semantic programs need operating rules: ownership, design principles, reuse, versioning, and review.
Organization profile | Defense ontology standards
United States Department of War / DoD and Intelligence Community
A public signal that formal ontology is becoming mission interoperability infrastructure.
Signal
Defense adoption signals that formal ontology is becoming mission interoperability infrastructure.
Key points
Public reporting states that BFO and CCO were selected as baseline standards for formal ontology work.
BFO provides top-level categories, while CCO adds reusable mid-level classes for mission-specific domains.
The target is data sharing, federated search, analytic efficiency, and interoperability across complex mission systems.
Evidence
Public sources describe Basic Formal Ontology and Common Core Ontologies as baseline standards for DoD and Intelligence Community ontology work and as a shared foundation for mission data integration.
Standards have to precede scale when many systems must coordinate under high operational risk.
Organization profile | Border operations ontology
U.S. Customs and Border Protection / CBP
CBP is building ontology-backed knowledge graphs for live border operations, not just exchange standards.
Signal
CBP proves that ontology can become mission infrastructure when response windows are measured in minutes and many sensor feeds must fuse into one operational picture.
Key points
Border Patrol leadership is leading an ontology development effort across CBP and DHS for enterprise-wide data integration and knowledge sharing.
A proof of concept used RDF triples linking sensors, acts of sensing, and unmanned aerial vehicles for real-time mapped airspace during drone interdiction.
A 30-day test collected 17,000 records meeting time and space criteria for qualified interdiction scenarios at the border.
Evidence
Public reporting from the Data Centric Architecture Forum describes CBP's ontology work and the sensor-to-drone RDF pattern used to give field agents precise, mapped airspace information under operational pressure.
Semantic models pay off when many feeds must fuse into one decision picture and the cost of ambiguity is measured in missed response windows.
Organization profile | Government and health infrastructure
National Institutes of Health / NCBO BioPortal
NIH-backed infrastructure has made biomedical ontologies searchable, reusable, and queryable at scale.
Signal
BioPortal shows how ontology becomes useful when it is searchable, mapped, queryable, and exposed as infrastructure.
Key points
BioPortal aggregates biomedical ontologies in a common repository for lookup, annotation, mapping, and reuse.
It exposes APIs, mappings, and SPARQL access so ontology assets can feed applications and analysis workflows.
The case proves that shared meaning needs service interfaces, not only files and stewardship documents.
Evidence
NCBO BioPortal describes itself as a comprehensive repository of biomedical ontologies, with services for search, annotation, mappings, APIs, and SPARQL access.
Semantic assets gain strategic value when they are consumable by platforms, products, analysts, and AI workflows.
Organization profile | Government and defense interoperability
NATO research community
NATO research shows ontology as an interoperability tool for coalition command and control.
Signal
NATO research makes the interoperability problem explicit: coalition systems need semantic mediation, not just connectivity.
Key points
IST-075 and IST-094 explored ontology-based semantic interoperability for heterogeneous command-and-control systems.
The work covers mediation, model harmonization, service discovery, and translation across tactical abstractions.
It proves that common meaning matters most when multiple actors must coordinate without one canonical system.
Evidence
NATO research papers document ontology-based approaches for semantic interoperability and tactical service discovery across military networks and command-and-control environments.
Federated operations need a shared semantic layer so local systems can remain different while decisions remain coherent.
Organization profile | Big tech and semantic infrastructure
Google
Google made knowledge graphs mainstream for entity-centric search.
Signal
Google made the strategic shift visible: understanding entities and relationships beats matching strings.
Key points
The Knowledge Graph models real-world things and relationships to improve search, panels, answers, and disambiguation.
It moves retrieval from document-centric matching toward entity-centric understanding.
The same logic applies inside enterprises where operational entities are scattered across documents and systems.
Evidence
Google introduced the Knowledge Graph as an intelligent model of real-world entities and relationships, commonly summarized as a move toward things, not strings.
Cloud graph services can host semantic assets, but they do not decide which meanings are authoritative.
Organization profile | Consumer goods and retail
IKEA
A rare public consumer-goods example where ontology and knowledge graph practice directly support product discovery, recommendations, and customer experience.
Signal
IKEA shows that ontology can support commercial experience, not only regulated or scientific domains.
Key points
Public material describes a three-layer knowledge graph: concepts, categories, and product data.
The graph supports product discovery, recommendations, search, navigation, APIs, and explainable customer experiences.
The case proves that semantic structure helps when product context and business rules must travel across channels.
Evidence
IKEA Knowledge Hub and public talks describe how concept, category, and data layers support recommendations and digital experience use cases.
A public example of enterprise knowledge graphs used for mission-critical financial applications.
Signal
JPMorgan Chase shows that entity resolution becomes core infrastructure when decisions depend on noisy text and internal identifiers.
Key points
Publications describe knowledge graphs used for risk assessment, fraud detection, investment advice, and financial news linking.
JEL links company mentions in text to entities in an enterprise company knowledge graph.
The case proves that graphs are valuable when they connect unstructured evidence to governed enterprise entities.
Evidence
JPMorgan Chase publications on JEL describe financial-news entity linking against a company knowledge graph and broader enterprise knowledge graph applications.
High-value decisions require entity resolution that connects documents, events, and enterprise-specific objects.
Organization profile | Pharma and healthcare
Gene Ontology Consortium
The early proof that scientific knowledge needs shared computable meaning.
Signal
Gene Ontology is the early proof that scientific knowledge needs shared computable meaning before large-scale analysis works.
Key points
GO provides controlled terms for gene functions, biological processes, and cellular components across organisms.
The knowledgebase combines evidence-supported annotations with GO-CAM models that connect annotations into pathways.
The case established the pattern of identifiers, evidence, relations, and curation before analytics.
Evidence
Gene Ontology public resources and the 2023 knowledgebase paper describe a computable structure for gene function, evidence-backed annotations, and biological models.
Reusable knowledge depends on stable identifiers, evidence codes, relationships, and sustained expert curation.
Organization profile | Pharma and healthcare
Open PHACTS
A landmark public-private semantic web initiative for drug discovery.
Signal
Open PHACTS showed that drug discovery needs answerable cross-domain questions, not isolated datasets.
Key points
The initiative integrated compounds, targets, diseases, tissues, pathways, and public drug-discovery databases.
It used semantic web technology, APIs, and query mechanisms to help researchers traverse related evidence.
The case demonstrates why domain questions should drive graph design.
Evidence
IHI project materials and the Open PHACTS triple store paper describe a semantic platform for integrating pharmacological data and answering complex drug discovery questions.
Semantic infrastructure should be judged by the cross-domain questions it makes answerable.
Organization profile | Pharma and healthcare
AstraZeneca
A strong public example of an internal pharma knowledge graph for drug development.
Signal
AstraZeneca shows how competitive knowledge graphs combine public science, internal evidence, and machine learning readiness.
Key points
BIKG integrates public, licensed, proprietary, and literature-extracted biological data for drug development.
The graph connects genes, proteins, diseases, compounds, NLP pipelines, and ontology alignment.
Kazu documentation shows the adjacent need for entity recognition and normalization in scientific text.
Evidence
AstraZeneca public materials describe BIKG as an internal Biological Insights Knowledge Graph and Kazu as tooling for biomedical entity recognition and normalization.
FAIR data becomes operational only when metadata, terms, models, applications, and governance are designed together.
Organization profile | Pharma and healthcare
Novartis
A visible drug-discovery knowledge graph case using biomedical entities and literature evidence.
Signal
Novartis is a clean public example of experts traversing evidence relationships instead of searching isolated repositories.
Key points
Public case studies describe a graph connecting genes, diseases, compounds, text-mined literature, historical data, and image-derived data.
Researchers use the graph to evaluate relationship strength and identify promising compounds or disease hypotheses.
OntoBrowser adds evidence of ontology tooling around open-source science and browsing.
Evidence
Neo4j and Novartis public sources describe drug discovery knowledge graph use cases and the OntoBrowser project for working with biomedical ontologies.
Experts need connected evidence paths that reveal why an answer is plausible, not only where a document is stored.
Organization profile | Pharma and healthcare
Pfizer
A visible pharma example of semantic integration, ontologies, and knowledge graph AI.
Signal
Pfizer reinforces the pattern: the higher the cost of scientific ambiguity, the more valuable governed semantic integration becomes.
Key points
Public sources describe data standards, vocabularies, ontologies, linked data, and an intelligent data framework.
Recent public material describes biomedical knowledge graphs with Data4Cure for continuously updated scientific insight.
The work connects literature, identifiers, compounds, disease areas, public data, and internal data for drug discovery.
Evidence
Bio-IT World and Drug Discovery Online sources describe Pfizer semantic integration work and knowledge graph collaboration for AI and data-driven discovery.
Complex assets need one governed model of reality across design, operations, maintenance, safety, and change impact.
Organization profile | Aerospace and operational platform
Airbus Skywise
The clearest public aviation platform example of ontology-backed operational data integration.
Signal
Skywise shows ontology becoming operational when it is embedded into fleet, maintenance, and equipment workflows.
Key points
Airbus launched Skywise with Palantir to integrate aviation data across airlines and operational use cases.
Developer documentation exposes ontology APIs for aircraft, parts, events, maintenance, and work packs.
The platform supports predictive maintenance, disruption reduction, fleet operations, and analytics over aviation data.
Evidence
Airbus public launch material and Skywise developer documentation describe an aviation data platform with ontology APIs for operational entities and workflows.
Industrial platforms can operationalize knowledge graphs, but enterprise meaning should remain governed above any single platform.
Implications for TotalEnergies
The external evidence supports TSF and SousLeSens as strategic control infrastructure.
Positioning
Own meaning once
TSF should define governed concepts that Cognite, Collibra, Fabric, search, and AI consume. Otherwise, each platform rebuilds meaning locally.
Adoption
Anchor in decisions
The message should start with operational questions: asset risk, maintenance evidence, production impact, CAPEX/OPEX, safety, and explainable AI.
Governance
Make evidence traceable
Every concept should carry ownership, source evidence, lifecycle status, mapping rules, and validation expectations.
Technology
Stay platform-neutral
The semantic layer should feed platforms without becoming captive to one vendor's object model, graph model, or AI interface.
Executive sentence
Ontologies and semantic knowledge graphs are the control system for enterprise meaning: they let operational, data, and AI platforms act on the same reality.
Conclusion
The pattern across 25 organisations is unambiguous: costly shared decisions require semantic infrastructure, and TotalEnergies already leads.
Twenty-five organization profiles across healthcare, defense, aerospace, energy platforms, internet infrastructure, open standards, and manufacturing have produced a consistent pattern. When decisions are expensive and interpretations must be shared across systems, people, and time, semantic infrastructure is built. Roche, Novartis, and Pfizer built it because drug discovery errors are fatal. Boeing and Airbus built it because lifecycle asset decisions cannot tolerate ambiguity at scale. Google, Amazon, and Microsoft embedded it because search, commerce, and AI cannot function without shared meaning. DARPA funded it because autonomous systems act on representations, not on ambiguous data. The convergence is cross-sector and the direction is clear.
The implication for TotalEnergies is specific. TotalEnergies operates at the same scale and with the same decision complexity as the organizations in this deck. FPSO equipment lifecycles, CAPEX/OPEX decisions, safety risk assessments, and multi-affiliate coordination all carry the same characteristics: fragmented evidence, high cost of interpretation errors, and decisions that must be traceable across time. TSF and SousLeSens already position TotalEnergies ahead of most oil and gas peers on semantic foundation. The question is not whether to invest further. It is how quickly to make that foundation operational.
Healthcare, defense, aerospace, and internet platforms have all converged on semantic infrastructure independently, validating the direction.
The pattern is consistent: when interpretations are shared, costly, and mission-critical, formal semantics pays.
Energy operators including Equinor are beginning the same move; TotalEnergies has a head start.
First-mover advantage is real: TSF and SousLeSens are more mature than most public peers in the sector.
Operational adoption, not technical design, is the remaining challenge and the next decision.
The next step is to connect this external evidence to the internal investment case: use the peer patterns as executive context for the LifeX production deployment decision, and make the cross-sector validation visible in the COMEX and OneTech leadership conversation.
Evidence pack
The deck is backed by one public-evidence note per organization.
Deck source
HTML and PPTX
The HTML source and editable PPTX sit in the Workstream 5 folder for reuse and refinement.
The evidence folder stores source notes for every organization profile in this deck.
Use in the communication kit
This workstream gives the external legitimacy layer: TotalEnergies is joining the operating pattern used by mature, knowledge-intensive organizations where semantic mistakes are expensive.
