Intercax
IntercaxOne of the principal benefits of a digital thread platform such as Syndeia is that it gives project leaders a holistic real-time view of the entire modeling effort. By combining Syndeia data requests with data science analytics, users can monitor and document progress quantitatively. In Part 4 of this series, we review a new Jupyter
A key benefit of the Syndeia digital thread platform is that it enables the user to retrieve data from all the federated repositories through a single interface, the Syndeia Cloud REST API. Several of the Jupyter notebooks released in the API Cookbook with Syndeia 3.5 will each focus on a specific repository type. This post
Syndeia is a digital thread platform, part of the infrastructure of an integrated system development environment. While its capabilities are available through user interfaces we provide, such as the SysML plugins and the Syndeia Web Dashboard, the full power is realized as a set of “ready-to-integrate” services for building custom interfaces and dashboards. This involves
As Intercax prepares to roll out Syndeia release 3.5, we’re giving our blog followers an advance look at new features. First is the Generic RESTful API integration applied to Vitech GENESYS in the accompanying video. One important aspect of the Digital Thread is the ability to access all the system data, distributed over many models
In the first post in this series, we considered the relationship between Data Science and the Digital Thread. In this post, we will discuss what need to put these ideas into practice. First, obviously, is data. We want all the data about the system and a way to get to it. For that, I’m going
Intercax has released Syndeia 3.2, a major advance in “breaking the silos”, that is, breaking down the barriers between domain engineering tools and their users to make complex systems development faster and more efficient. We talk about MBE (Model-Based Engineering) rather than MBSE (Model-Based Systems Engineering) which can too easily become one more silo in
Part 1 and Part 2 of this blog series have focused on the SysML models of energy systems (and system-of-systems). In this part (Part 3), we will describe the MBE graphs created when the SysML-based architecture model is connected with discipline-specific models such as CAD models, simulation models, PLM models, requirements model of energy system
In Part 1 and Part 2 of this series, we focused entirely on possible visualizations of inter-model connections, i.e. connections created by Syndeia between elements in different tools. But many use-cases require us to trace connections across the system model where the sequences include both inter-model and intra-model connections. Syndeia 3.0 can show many of these,
Consider a healthcare facility with independent software systems for each department. A system engineer is tasked with developing a message exchange system between the departments based on the HL7 Version 2 standards. She begins by describing the interfaces and content exchanged between departments based on SysML interface blocks. The flow properties of these interface blocks are typed
In Part 1 of the blog series on Syndeia-JIRA interface, we described how Syndeia can connect to and browse JIRA repositories, and generate and connect SysML blocks from JIRA issues so that the block’s value properties mirror the issue characteristics like status, last update, etc. In Part 2, we showed how a multi-level SysML structure (e.g.