Following the publication of DEXPI 2.0 last October, DEXPI 2.0 information model is now available for Sparx Enterprise Architect users.
The full UML model is available to browse its classes, attributes and relations from a custom package structure, and access a set of diagrams covering DEXPI 2.0 Auxiliaries, Builtin, Core, Plant and Process models.
These deliverables will save time for Sparx EA users in comparison with starting off from an XMI file.
The QEA file of the EA Project can be downloaded from DEXPI 2.0 supporting materials and opened directly in Enterprise Architect 16 or later.
Class definitions from DEXPI 2.0 standard can then be reviewed and/or linked with local data models.
The EA project content is also available directly from a web browser via the HTML export.
The availability of these additional modelling assets is also an opportunity to underline the contributions of TotalEnergies, which has been funding and promoting several shared reference models used across standardization activities — including the collaborative work carried out within DEXPI. Highlighting these contributions helps foster broader adoption and understanding of the DEXPI standard.
The availability of the full UML content in Enterprise Architect also supports the wider promotion and democratization of DEXPI by making it easier to explore the structure, constraints, and modelling principles of the standard. In the same spirit of developing open industry “commons”, TotalEnergies is currently building a semantic version of the DEXPI models, aligned independently with both
• ISO 21838‑2 (BFO: Basic Formal Ontology), and
• the upcoming ISO 23726‑3 (IDO: Industry Data Ontology), still under development.
These semantic assets will be shared with DEXPI members for review and alignment, ensuring that their contents are validated collectively before broader dissemination.
These initiatives reflect a critical need shared across the industry: to be able to exchange data, we must first share common, high‑quality reference models.
A shared authoritative source prevents each organization from creating its own independent interpretation of the model, which would inevitably lead to incompatibilities, divergences, and unnecessary complexity.