Skip to main content

Our objective at this stage is to complete the interconnection of urban system blocks in SysML and then to transform that SysML model to an equivalent model in a simulation tool, here Simulink (The MathWorks). The initial step in SysML is to create internal block diagrams (IBDs) showing the parts and their ports and to draw connectors between them.  When the SysML model is complex, multiple diagrams are created to limit the number of parts and connectors per diagram to improve interpretability. Since each diagram is a selective view of the same SysML model, models of any complexity can be built by adding additional diagrams. Our complete SysML model, available for download with the final installment of this series, includes sixteen separate IBDs.


Figure 1 Internal Block Diagram, Water/Power/Gas distribution between major subsystems (Cameo)

Figure 1 is an example of an IBD from the top-level Urban_System_02 block. It is intended to show the flows of power, water, sewage and natural gas from the Utility Subsystem to the other major subsystems (flows to DataComm and SmartCity subsystems are shown on additional diagrams). Figure 2 shows another IBD from the same level with the flows of labor from the Residential Subsystem to the other subsystems. Additional diagrams show flows of transportation, goods, trash and communications.


Figure 2 Internal Block Diagram, Labor distribution between major subsystems (Cameo)

One feature of this model is highlighted by the color coding in these IBDs. The tan parts represent the subsystems/services; the green parts are “distribution blocks” representing the allocation of flows between multiple services or the aggregation of flows from multiple services. The use of these distribution blocks is pragmatic. Although SysML allows multiple connectors from one port, this can be a problem during model transform to other tools such as Simulink, which may not permit it.


Figure 3 Internal Block Diagram, Labor/Trucking/Goods distribution between industrial subsystems (Cameo)

Other IBDs are used to model flows inside the major subsystems. Figure 3 shows the flows of labor/goods/trucks within the Industrial Subsystem. The ports on the diagram boundary represent inputs/outputs of the Industrial Subsystem itself and correspond to ports on parts of that type in higher level diagrams.

Generally, architecture modeling and simulation will be done in different tools, each specialized for the purpose. The challenge arises that these models may be inconsistent, especially as time passes and the models evolve independently. One solution uses Syndeia to transform all or part of the SysML model into a model of similar structure in another tool. Figure 4 shows how the model for the Industrial Subsystem has been transformed into Simulink.


Figure 4 Simulink model transform of Industrial Subsystem connections

Each Simulink block in Figure 4 is connected to the original SysML block and duplicates its ports and connectors. Syndeia can compare and update the models in either direction as one or both change. Note that the Simulink model created is only the first step in building an executable simulation; typically, a Simulink analyst will add the simulation code to the blocks for the desired analysis. Syndeia maintains traceability between the models as part of the Total System Model.

In the next post, we add connections from our federated models to a JIRA (Atlassian) issue tracking repository for project management purposes. In this and the following posts in the series, we will provide alternative versions for SysML modeling in Rhapsody. Both SysML models will be made available for download with the final installment of the series.

Related Posts:

Tags:
Blog

Related Posts

Model-Based Systems Engineering for Autonomous Vehicles, Part 13 – Digital Reports

A key function of Digital Threads is to be able to answer questions about project status in real-time without the overhead of data collection, status reports and meetings. In this ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 12 – Digital Projects

In this post, we continue our updating of MBSE for autonomous vehicles in light of the current and upcoming capabilities of Syndeia, the digital thread platform from Intercax. As ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 11 – Digital Threads

In 2018, I published a ten-part blog series applying MBSE to an autonomous vehicle. That series continues to garner views on our website, but the state-of-the-art has advanced ...
Dirk Zwemer

Syndeia AI Multiple Agents, Part 4

Hello and welcome to a new demonstration of Syndeia AI that shows multiple AI agents in action – SysML v2, Teamcenter, Windchill, Jira, Jama Connect, Teamwork Cloud, and a Digital ...
Manas Bajaj

Fast-Track Digital Thread Training

Intercax is excited to launch a new self-paced training series designed to accelerate your journey into Digital Engineering: Building Digital Threads with Syndeia™. The new ...
Dirk Zwemer

Syndeia AI - Jira Agent, Part 3

We have all been there, trying to write complex query expressions or fill out a form with filters and drop downs to find issues in Jira. But now, you can finally talk with your ...
Manas Bajaj

Syndeia AI - SysML 2.0 Agent, Part 2

Greetings and welcome to an overview of the Syndeia AI - SysML 2.0 Agent. Syndeia AI is a collection of AI agents built on Syndeia Cloud. These AI agents are capable of processing ...
Manas Bajaj

Syndeia AI Agents, Part 1

Hello and welcome to a preview of Syndeia AI, a collection of AI agents that are powered by Syndeia Cloud. These AI agents can take natural language inputs, fetch latest data from ...
Manas Bajaj

Santa’s Mission 2024 with 8.2 billion landings made possible by Digital Threads (Day 5)

Santa has just returned from his whirlwind journey, and the workshop erupts in cheers. Elves spill into the command center, their faces glowing with joy and pride as they take in ...
Manas Bajaj