What is Hexagon SDx?
Hexagon SDx, sold as HxGN SDx, is an asset lifecycle information management solution for industrial assets. Today it is called Octave InConcert Core. Octave describes it as a solution that centralizes engineering, operations and maintenance data into one source of truth, available as SaaS or on-premises. The listed capabilities include a unified repository, digital twin integration, dashboards, role-based access control, secure file sharing, and compliance and audit tools.
The newer line, HxGN SDx2, is now called Octave InConcert. Octave presents it as cloud-native SaaS with document management and control that covers routing, tracking and redlining. It also offers engineering information management, asset handover support, change management, design review and an AI assistant. Octave calls InConcert “the heart” of Smart Digital Reality, its vision of a virtual representation of physical assets fed by engineering and operating data.
For anyone searching for “Hexagon SDx”, the short version is: the product continues, under a new name and a new owner.
What changed in 2026: from Hexagon to Octave
The change happened in steps, each recorded in official sources:
| Date | Event | Source |
|---|---|---|
| 17 Jun 2025 | Hexagon announces the name Octave for the company it planned to spin off, comprising its Asset Lifecycle Intelligence and Safety, Infrastructure & Geospatial divisions plus ETQ and Bricsys | Hexagon release via PR Newswire |
| 2 Mar 2026 | Octave launches its own brand | Octave release |
| 24 Apr 2026 | Hexagon AB’s Annual General Meeting resolves to distribute all Octave shares to shareholders | Hexagon investor relations |
| 28 May 2026 | The distribution completes. Octave Intelligence plc trades on Nasdaq Stockholm as SDRs and on Nasdaq New York under the ticker OCTV | Hexagon investor relations |
| 2026 | HxGN SDx becomes Octave InConcert Core; HxGN SDx2 becomes Octave InConcert | Octave product pages |
Octave says InConcert keeps the core functionality of SDx2 and that the change reflects its move to an independent brand, with refreshed naming, design and positioning. For existing contracts, version roadmaps and support, the reference is Octave. If contracts, invoices or support tickets still name Hexagon, it is worth confirming with Octave which entity now holds them.
This page uses “SDx” and “InConcert” side by side, because that is how engineering teams still talk about the product.
Where SDx fits next to an EDMS and an ECM
SDx is not just a document repository. Its central unit is the asset object, such as an equipment tag, linked to documents, 3D models and operating data. A classic EDMS controls the document and its revisions. That difference changes the kind of project, the kind of data and the kind of migration.
| Aspect | EDMS: Meridian, ProjectWise, Greendocs | SDx / Octave InConcert, asset information management | Corporate ECM / DMS |
|---|---|---|---|
| Central unit | Document and revision | Asset object, such as a tag, linked to documents and data | Business document |
| Question it answers | “What is the current revision of this drawing?” | “What do we know about this equipment, and where is it?” | “Where is this contract?” |
| Typical data | Files and metadata | Tags, attributes, relationships, documents, models | Files, forms |
| Strongest phase | Project and operations | Handover and operations | Company-wide |
| Critical dependency | Document numbering | Class library and tag standard | File plan |
The software categories are compared in EDMS vs ECM vs DMS. For tools side by side, with no brand recommendation, see the EDMS comparison. The two can coexist: the EDMS stays as the document vault and SDx provides the asset context.
What is SDx used for in engineering?
Octave’s product pages and the case study it publishes point to four main uses in asset-intensive industries:
- A single source of asset information. Technical drawings, equipment data and maintenance reports in one place, open to engineering, contractors and maintenance.
- Project-to-operations handover. The EPC delivers documents and tags; the platform organizes the delivery so operations receives the asset with its information linked.
- Engineering change management. Design review and change workflows over the same data set.
- A base for the digital twin. Engineering data linked to 3D models and operating data, within the Smart Digital Reality vision.
For this to work, the owner has to define what it will receive. Open specifications help. CFIHOS, managed by JIP36 under IOGP oversight, offers standardized information handover specifications for anyone who designs, operates, maintains or decommissions industrial facilities. Nothing requires a project to use CFIHOS with SDx: it is a reference the owner can adopt.
What to settle before an SDx project
Asset information platforms expose gaps that a document-only EDMS can hide. Before configuring SDx or receiving a handover into it, 29docs recommends settling five points:
- The tag standard, with one format for every contractor on the site.
- The class library: which equipment classes exist and which attributes each one requires.
- Document types and their link to tags: which document types must point to which classes.
- The status that counts as final, so only approved or as-built revisions go into operations.
- Who keeps the data current after handover, and in which system each change is made first.
What 29docs does around SDx
29docs is a Brazilian, platform-agnostic consultancy in engineering document management and asset information. It works with Hexagon SDx among other platforms, does not sell licenses and is not a Hexagon or Octave partner. Its work sits in processes and data:
- Process design: document numbering, document types, issue statuses and rules linking documents to tags, before the platform is configured.
- Handover requirements for EPCs: which documents, which attributes and in what format, so the delivery goes into SDx without rework.
- Data migration into or out of SDx, for example from an EDMS such as Meridian or ProjectWise into InConcert, or from SDx into another system. See EDMS migration.
- Independent consulting to settle the role of each system: what stays in the EDMS, what goes to the asset platform and how they talk to each other. See independent consulting.
- Traceability and compliance, to show where each document came from in an audit.
How 29docs handles migration and handover
The pipeline is the same one 29docs uses in other migrations, adjusted to the SDx data model:
- Extraction of metadata, files and, where they exist, the source tag list.
- Transformation and normalization to the destination’s numbering standard and class library.
- Validation of every document against quality rules, including the document-to-tag link. Only a batch that meets the agreed thresholds moves on to loading.
- Load into the destination with the agreed structure.
- Validation and comparison reports between source and destination.
It all starts with a free 30-minute assessment. Then organize, standardize and make available, with support after go-live. For the sector view, see engineering document management in chemicals and oil and gas.
Trademark note
HxGN, SDx and Hexagon are trademarks of Hexagon AB or its affiliates. Octave and InConcert are trademarks of Octave Intelligence plc or its affiliates. Other names belong to their owners. 29docs has no commercial relationship with Hexagon or Octave. Descriptions come from these vendors’ public pages, accessed on 14 October 2026.
Updated on .