We’re continuing our blog series on using Syndeia digital pipelines to execute real world use cases in systems engineering. Digital pipeline automation is particularly valuable where models are large with many elements and where models must be routinely updated at regular intervals. In this post, we will see examples of both.

Our use case is to create a set of Jira issues (stories, in this example) based on a SysML model block structure managed in Teamwork Cloud (TWC) from CATIA Magic. In this scenario, the users intend to manage progress in design and testing of each component using Jira. In Part A, we start fresh and create the initial set of Jira stories starting with an autonomous vehicle model uploaded to TWC.

The pipeline has five outputs

1. A new set of Jira stories based on the blocks in in the TWC models
2. A new set of Jira blocked by relations between stories, corresponding to contains relations between the TWC blocks and parts
3. A new set of Syndeia tracks relations between TWC source elements and the corresponding Jira stories
4. A tabular report in Confluence listing the new artifacts (Note: this is available to authorized stakeholders without access to Cameo, Jira or Syndeia)
5. Slack notification of relevant stakeholders that a new run of the pipeline has been completed.

The following video, narrated by Manas Bajaj, illustrates these outputs as viewed in Syndeia, Jira, and Confluence and the easy navigation between them enabled by Syndeia.

 Part A - TWC Block structure to Jira generation

The second use case comes into play when the SysML model changes, i.e. a new version is checked into TWC. Whether the new pipeline run is triggered on a regular schedule, on the check-in event, or manually, the pipeline checks for new SysML blocks and changed SysML blocks and either creates new Jira stories or updates the existing ones. The same five outputs are generated in Part B.

Part B - TWC Block structure to Jira sync and update demo 

How the SysML blocks map into the Jira stories is determined by the transform and update code embedded inside the pipeline tasks. In this example, the text in the block Document field becomes the Description field in Jira. This can be coded as desired to the users’ purposes.

 A straightforward extension of the pipeline can be used to transform and update requirements in TWC to Jira issues, as shown in Part C below. 

Part C - TWC Requirements to Jira demo pipeline 

By building and updating the digital thread using pipeline automation, Syndeia enables the organization to manage the project more efficiently, reduce low-value engineering effort and provide the most current and consistent information to project managers.

In the next post in this series, we will demonstrate another common use case, using a pipeline to extract mass properties from a SolidWorks CAD file and post a daily report on Confluence.

This blog post is the 5th part in a series of posts and demonstrations that we will share, focusing on automating digital engineering workflows and use cases with Syndeia Pipelines.

• Pipelines Part 1 – Quick Introduction and Demo
• Pipelines Part 2 – Gap Analysis between Requirements and Tests
• Pipelines Part 3 – Matching Requirements to Parts using Syndeia Digital Pipelines
• Pipelines Part 4 - UAF Mission Architecture to Confluence Reports — Automatically 
• Pipelines Part 5 - TWC to Jira Transform and Update Pipelines (This post)