Merging

1 Introduction
- 1.1 How merges are performed
- 1.2 Automated merges
- 1.3 Manual merges
2 Merge types
- 2.1 Merge weighting
- 2.2 Update domain normalized values

Introduction

This will walk you through the complete process of merging document nodes in Orthogramic, from understanding different merge types and their appropriate applications. Whether you're consolidating complementary information, updating outdated content, or replacing redundant data, Orthogramic's intelligent merge functionality provides a structured approach to maintaining the integrity of your business domain data.

By following the straightforward merge process outlined in this guide, you'll be able to make informed decisions about how different pieces of information should interact, ensuring your organization maintains a cohesive and accurate knowledge base that evolves alongside your business needs.

How merges are performed

Merges occur in two ways.

Automated Merges: When a user uploads a document and the automated merge is approved.
Manual Merges: When a user performs a manual node-on-node drag-to-merge.

Automated merges

When a user uploads a document, Orthogramic checks to see how the new information may improve if the holistic perspective of the organization. Sometimes this leads to suggestions to merge nodes. This is based on the merge type and merge weighting. See Merge Types and Merge Weighting below for more details.

Merge suggestions will be listed in the Approvals page.

New Approvals page required

Reviewing a merge suggestion: Clicking on a merge suggestion will display:

Source and Target nodes
Merge type and
Data in the merge node

Changing Merge types: Click the Change button to change Merge type. For more information on Merge types, see: Merge Types below.

Warning: Automated Organization Unit merges are not restricted to single level hierarchy differences as is the case for Manual Organization Unit merges. In the case of merging Organization Unit nodes, all the child nodes will also be required to be merged (or moved into the new Organization Unit where no merge is required). At the higher levels of an organization, this can lead to hundreds or thousands of child node merge and move actions. The existing child organization hierarchy is preserved in automated merges.

Before performing this action, please consider the effects very carefully.

Confirming the merge: After you select Merge at the top of the Insights Panel, you will be required to confirm the merge.

After the merge: Weighted scores—such as relevance, quality, and quantity are recalculated for the relevant organization unit and its business domains based on the newly merged data. See : Merging | Update domain normalized values below.

Manual merges

These are the steps in the merge process.

1. Defining merge source and target:

The Source is the node being dragged.
The Target node is the node being dragged onto.
Source and Target must be of the same type, i.e. Organization or Stakeholder.

Please note: Manual Organization Unit merges are restricted to single level hierarchy differences. In the case of merging Organization Unit nodes, all the child nodes will also be required to be merged (or moved into the new Organization Unit where no merge is required). At the higher levels of an organization, this can lead to hundreds or thousands of child node merge and move actions.

Nodes to be merged

After becoming the Source and Target nodes, the nodes to be merged are coloured as below.

2. Review merge suggestions: Orthogramic will highlight suggested changes to add or remove content. These are based on the merge type and merge weighting. See Merge Types and Merge Weighting below for more details.

3. Manual edits: Any manual edits you make are highlighted as you make them.

Changing Merge types: Click the Change button to change Merge type. For more information on Merge types, see: Merge Types below.

5. Confirming the merge: After you select Merge at the bottom of the Insights Panel, you will be required to confirm the merge.

After the merge: Weighted scores—such as relevance, quality, and quantity are recalculated for the relevant organization unit and its business domains based on the newly merged data.

Merge types

When merging a document in Orthogramic, a merge type is automatically selected from three types of merges below based on how the new information should best integrate with existing business architecture domain data. Each merge type ensures that your organization maintains a structured and strategic approach to managing its domain data.

Merge type and description	Use case	Outcome

Merge type and description	Use case	Outcome
Additive: This integrates the new document’s data alongside existing domain data without removing or replacing any content. This approach is ideal when the new information provides additional insights or expands on existing knowledge without creating conflicts.	When the document contains complementary information that enhances an existing domain without requiring changes to previous data. When multiple perspectives or data sources should be retained for future reference.	The merged document contributes to the domain while keeping all prior data intact.
Overwrite: This merge replaces outdated or redundant domain data with higher-priority content from the new document. This approach is useful when the new document provides more accurate, updated, or authoritative information than what currently exists.	When the document contains the latest policy, strategy, or regulatory update that must replace outdated versions. When previous data is no longer relevant or has been superseded by new business decisions.	Older data is removed and replaced by the new document’s content.
Update: This merge selectively integrates new data while preserving historical context where relevant. This approach balances maintaining past records while incorporating necessary updates.	When parts of the document contain updates that should be merged with existing data without completely removing prior versions. When historical context is important for tracking changes over time, but certain aspects of the domain require modification.	The merged content reflects updated information while keeping historical dependencies intact.

Merge weighting

The weighting of the source documents the domain data in each node determines the relative importance of attributes and elements when the merge occurs. The history of previous merges is also tracked at the attribute and element level. For example, an overwrite is more likely when merging a highly weighted Source with a lower weighted Target. See Document weighting

Update domain normalized values

The process of updating domain normalized values ensures that, following the merging of new business architecture data, the affected organisational units reflect a consistent and accurate representation of their domain metrics. This process involves recalculating weighted scores—such as relevance, quality, and quantity—for the relevant domains and units based on the existing and newly merged data. Only organization units and their impacted business domains in the merge are included. Each update is recorded with an audit reference to ensure traceability and consistency across the organisation's business architecture data.

Please note: Merge metadata auditing is available as part of a Professional Plan and above.