Discover our story, vision, and impact.

Get Started wIth 30 Days Free Trial

Blog

The Digital Thread Isn’t Broken. It Was Never Woven.

For fifteen years, the digital thread has been the named ambition of digital engineering. Connected requirements. Live traceability across system, software and physical design. A configuration record that resolves itself, in real time, across PLM, ALM, MBSE, simulation and manufacturing. Most large organizations have invested heavily and with serious intent. Vendors have iterated through several generations of architecture and standards. Yet the thread in most organizations, is still discontinuous.

How to Integrate Aras Innovator, Enterprise Architect, IBM DOORS and Jira

In today’s fast-paced Defence, Aerospace, and Automotive industries, teams are building highly complex, mission-critical systems, from missile guidance units to autonomous vehicles. These programs must meet the dual demands of safety certification and agile delivery. Yet many organizations still operate with disconnected tools:

When tools work in silos, even simple changes require manual updates across platforms, leading to delays, errors, and broken traceability.

In this demo, see how OpsHub Integration Manager (OIM) connects these tools into a unified digital thread, enabling end-to-end traceability across the entire development lifecycle. With low/no-code configuration, OIM allows teams to sync Aras Innovator, Sparx EA, IBM DOORS, and Atlassian Jira bidirectionally without plugins, without scripting, and without data loss.

Chapters:

00:06 – Pre-synced system element and requirement in Aras

00:20 – How to create an ECR in Aras

00:32 – How does OIM auto sync data to Enterprise Architect and IBM DOORS

00:46 – Verifying ECR in Enterprise Architect

00:57 – How to create software requirement and class element in EA?

01:14 – How to build diagram and link requirements and ECR

01:37 – Updating requirement status and preserving relationships

01:53 – Bidirectional sync to Aras and DOORS

02:00 – Updating ECR in EA and auto-sync to Aras

02:12 – Validating synced elements and requirements in Aras

02:34 – What preserving traceability between ECR and requirements looks like

02:50 – How to sync requirements from EA to DOORS

02:56 – Updating requirement status to approved in DOORS

03:01 – How status updates sync across EA and Aras live

03:21 – Approving ECR in Aras

03:34 – Syncing ECR and requirements to Jira

03:40 – How does the synced data look in Jira

03:56 – Updating requirement status in Jira

04:00 – Sync back to Aras and validation

04:12 – Completing ECR in Aras

04:19 – Final sync across DOORS, EA, and Jira

04:25 – Demo conclusion

Video Transcript

In Aras, we have pre-created a system element (0:06) and a requirement. (0:08) The system element and requirement have been (0:11) pre-synced to enterprise architect and (0:14) IBM doors. (0:16) Currently, Jira is empty in Aras. (0:20) Let’s (0:20) create an ECR. (0:20) Let’s add details like (0:24) the title and description. (0:24) Once the (0:27) details are added, we will mark it done (0:27) to save it. (0:29) The ECR is created (0:32) successfully. (0:32) OpsHub integration manager (0:35) OIM is working in the background. (0:35) We’ll (0:37) fetch the ECR and sync it to enterprise (0:37) architect and doors with all the (0:40) information intact. (0:43) Navigating to EA. (0:46) Let’s update the project to see if the (0:48) ECR is visible. (0:48) We can see the ECR is (0:52) successfully reflected after the (0:52) synchronization in EA. (0:54) The systems (0:57) architect creates a new software (0:59) requirement to be associated with the (1:01) ECR. (1:01) Now the systems architect creates (1:04) an element type. (1:04) Selects the type as (1:06) class. (1:06) The element as class has been created. (1:09) Now the systems architect goes on to (1:12) create a diagram. (1:14) adds the ECR, the system requirement, (1:17) the software requirement and both (1:20) elements to the diagram. (1:22) Links both the elements with the (1:27) requirement and both the requirements (1:28) with the ECR. (1:30) Now changes the status of the pre-synced (1:37) requirement from proposed to mandatory. (1:39) The newly created software requirement (1:42) and element will sync to ARASS and doors (1:45) bidirectionally preserving the (1:47) relationship established in EA. (1:49) So shall the revised requirement status (1:53) auto update in Aras and doors. (1:55) In EA the systems architect also makes (2:00) changes to the ECR. (2:03) The changes will (2:03) automatically be reflected in the Aras (2:06) ECR without any manual effort. (2:09) Navigating to Aras to validate the (2:12) synchronization. (2:14) In Aras, we can see (2:17) that the element block created in EA is (2:17) visible posts synchronization. (2:20) Similarly, the software requirement (2:22) created in EA is reflected in Aras as (2:24) well. (2:28) The updated status from EA is also (2:28) available. (2:31) Let’s move to the ECR in Aras (2:31) to check the synchronizations from EA. (2:34) We can see the linkage created in EA (2:37) between the requirements and ECR is (2:39) preserved in ARASS enabling complete (2:42) traceability between the tools. (2:44) The same (2:47) information is preserved in doors. (2:50) The (2:50) requirements are reflected from EA to (2:52) doors with the status intact. (2:52) Indoors (2:56) let’s change the status of both (2:56) requirements from pending to approved. (2:57) The status change will near realtime (3:01) sync to EA and ARAS. (3:03) In Aras we can see (3:07) the status update is successful. (3:07) In EA (3:11) under the properties for both (3:11) requirements we will see the status has (3:13) been updated as approved maintaining one (3:15) single source of truth across ARASS (3:18) doors and EA. (3:21) Going back to ECR in Aras (3:21) looking at the completed status of the (3:26) requirements let’s mark the ECR status (3:28) as approved. (3:31) The ECR with the updated (3:31) status will be reflected in Jira after (3:34) successful sync. (3:36) Now to Jira to see all (3:36) the synced data. (3:40) In Jira, the ECR has (3:40) synced as an epic and the software (3:43) requirement as a story. (3:45) In the software (3:48) requirement, we can see the linkage with (3:48) the ECR preserved providing full (3:50) traceability between the tools. (3:53) In the (3:56) software requirement, the developer now (3:56) changes the status to done as well. (3:58) Let’s move to Aras to check if the (4:00) synchronization from Jira is successful. (4:02) In (4:05) Aras, we can see the software (4:05) requirement is marked completed since (4:07) the developer closed the same story in (4:10) Jira. (4:12) Therefore, in Aras, let’s mark the (4:12) ECR status to completed. (4:16) This change (4:19) will sync to doors EA and Jira (4:21) respectively. (4:25) That completes the demo. (4:25) Thank you for (4:27) watching.