Enabling the Digital Engineering Transformation

Experience GENESYS

Explore Vitech Products

Empowering Next-Generation Systems Engineering

GENESYS 2020 - New Features

The challenge of digital engineering is all about making the MBSE model relevant throughout the product lifecycle. Vitech makes it happen with the customer-driven enhancements in GENESYS 2020.

  Click HERE for more complete information on all the new features.

Enhanced Richness and Access in the Simulator

Executing your system design is a powerful way to confirm that your model is designed and executing as intended, and to gain insight into the interactions of your model. Seeing your model highlight as it executes allows better insight into potential issues that you might not have been able to see when viewing the results of a simulation run. Now, the nodes executing on an open diagram highlight, giving you information on when a function is enabled, what it is waiting on, and when it runs, by highlighting the function in different colors – colors that correspond to the timeline information already being displayed. Simply run or step through the simulation while the Realtime Rendering option is enabled, and you can watch your simulation run.
For those seeking to bring additional power and detail to the direct simulation of their system design, GENESYS provides access to the underlying execution model. Previously, users could complement their models with scripts to perform utility functions, access underlying data, etc. These scripts provided access to the behavioral context but not the actual model execution. With GENESYS 2020, you can now:
  • Access the specific function instances that are running in the simulation so you can make realtime decisions based on the state of your model;
  • Access the specific item instances that triggered your execution as well as items that are input and output; and
  • Natively set field values in item instances, pass them in the model, and make decisions on them.
If you are looking to take advantage of these advanced features, we recommend you review the Simulation User guide.

Expanded Diagram Capabilities

Having enough space to show all the information you want on a diagram is easier now that you can display multiple fields on a single line. So instead of making larger nodes, show the number and name on a single line and have an additional line for the other information you want to display.
Node templates can now be associated with connecting lines on diagrams where lines are more than just lines. For example, on a physical block diagram, you can specify to display not only the link connecting two components but also the items it carries. On a sequence diagram or an IDEF0, you can decide to show abbreviations rather than full item names. For each of these diagrams, the diagram options have been extended to include a connection node template in addition to the existing node templates. The following diagrams have this new capability:

  • Flow Internal Block
  • IDEF0 and IDEF A-0
  • Interface Block
  • Internal Block
  • Physical Block
  • Sequence
  • State Transition
We added the ability to customize the header frame block on a diagram. This is in addition to the frame block footer customization released with GENESYS 7.0. Now you can show more information at the top of your diagram, or you can keep the frame looking the same as it has been.


In response to customer requests, and as more customers are using the interface between GENESYS and DOORS, we have spent time increasing the performance and adding capability. For GENESYS 2020, we have added richness to the transferring of data between GENESYS and DOORS by giving the user the ability to specify additional attributes to be transferred between GENESYS and DOORS. When exporting or importing data, a dialog appears that allows you to specify additional attributes to be moved between the tools.

Users now have the ability to tailor the GENESYS user interface by adding custom commands to the ribbon. A custom command can open a file, launch an application, or execute a GENESYS script.

When executing a script, the folder and entity selections in the user interface are available to the script, allowing simple or advanced operations against this information. Scripts can specify when the command is enabled in the ribbon based on the selections or any other logic desired. Scripts leverage the full power of the .NET framework and provide direct access to, and manipulation of, GENESYS data via the GENESYS API. Users have a powerful means of interacting with external applications and services, automating complex logic, or performing macro-style operations directly from the GENESYS ribbon. When combined with customer commands, scripts open a world of opportunity to personalize GENESYS to your specific needs.

Additional Refinements

Adding an external reference to your entity in order to supplement the textual description adds richness to the model and to the reports created from the model. We made this easier by allowing you to drag-drop files directly onto an entity. This will create a new entity in the ExternalFile class, set the attributes including file location, and then set the augments/augmented by relationship.

If instead you want to set an image for an entity, you can drag-drop an image file onto an entity, either in an entity list or on a diagram, which will set the image. Dropping an image onto an entity on a diagram will toggle on the Use Image option.

When navigating through the different views available in GENESYS, once you find an entity, there are times when you would like to know the database folder in which the entity is located. In the property sheet view, under the properties tab, the folder path is displayed as a hyperlink. If you click on the hyperlink, a new Project Explorer pane opens with the folder and entity selected.

As we work with customers, we find that there are some model assistant rules that work well in specific cases, but are not necessary for all projects. In GENESYS 2020, we have set some of the rules that frequently cause confusion to inactive by default. The changes will not affect existing user settings, and they can be tailored easily by visiting the Model Assistant in the Project Explorer tree view. These rules are:

  • Auto-allocate on decomposition
  • Auto-relate on allocation
  • Auto-inclusion on decomposition of states
  • Auto-relate on inclusion

We have also added the ability to keep root functions and states synchronized when auto-maintain connector names is enabled. This means that when you change a Component name, the connected Root Function and Root States that are using the default name will be renamed as well.

GENESYS 2020 Schema Changes

  1. ExternalFile is now essential. With the capability to streamline external files, the ExternalFile class is assumed to be present in all schemas.
  2. The target classes for DefinedTerm used by has been expanded to include all classes.

The decomposability of Interfaces and Links creates overlap between a low-level logical Interface and a high-level physical Link. Given this overlap, rather than requiring two separate classes, the connection between components can be represented with a single class – Link. At more abstract levels, the Link can be treated as a logical statement of connection. At more detailed levels, the Link can be treated as the physical realization of the connection.

  1. The Essentials facility now includes Link in place of Interface.
  2. Added Link
    • assigned to Organization
    • reported by Document
    • c. A script has been created that will aid you in the transformation of Interfaces to Links if you decide that you want to transform them. You can find this report in the Schema Migration folder.

Based upon experience, industry dialog, and internal reflection, we identified the following:

  • The concepts of TestActivity and TestProcedure overlap.
  • VerificationRequirement verifies Requirement (in the problem space) and Function (in the behavior space). However, VerificationRequirement does not verify any part of the physical space – Component, Link, or Port.
  • The instantiation of the Needs-Behavior-Architecture (why-does-is) pattern present throughout the systems metamodel is not present in the verification dimension of the schema.
  • VerificationEvent – a programmatic concept – is interjected within the definition of the test architecture.

Given these observations, GENESYS 2020 versions of the baseline schemas include the following changes. Note, projects may continue to use prior versions of the schema with no changes to capability.

  1. Data migration
    • Transform TestProcedure entities to TestActivity entities
    • Transform VerificationRequirement executed by (executes) TestActivity to VerificationRequirement basis of (based on) TestActivity
  2. Deletions
    • Class TestProcedure
    • Relation executes / executed by
    • Relation fulfills / fulfilled by
  3. Class changes
    • Added to VerificationRequirement
      • attribute type (enumeration with possible values nil, Validation, Verification)
      • basis of (based on) TestActivity
      • specifies (specified by) TestActivity, TestConfiguration, TestItem
      • verifies (verified by) Component, FullPort, Item, Link
    • Removed VerificationRequirement executed by (executes) TestActivity
    • Removed from VerificationEvent
      • assigned to (responsible for) Organization
      • employs (employed by) TestConfiguration
      • fulfills (fulfilled by) VerificationRequirement
      • supplies (supplied by) Component, Document
    • Added TestConfiguration employed by (employs) TestActivity

Given the nature of the schema changes made in the 2020 base and Capability Architecture Definition schemas, project migration is required to transform specific classes and specific attributes. To best support this migration, GENESYS 2020 provides a schema migration utility on the Project tab. Also included is a report which details what relationships will be removed during the migration and a script which will transform Interface entities to Link entities.

This utility is targeted at the standard Vitech schemas. If your project uses a customized schema, additional migration support may be required. If you have made schema extensions and would like to understand what special steps – if any – are required to support your extensions, please contact Vitech Customer Support with a copy of your extensions. We are happy to review these and advise you in your migration accordingly.

Note: You do not have to migrate your schema in order to make use of GENESYS 2020. You should assess your project needs, your project lifecycle, and the changes present in the 2020 schemas to determine if, and when, to migrate your schemas. Project teams nearing a major milestone or approaching conclusion should strongly consider remaining with their current schema. We recommend that others move to the 2020 schemas to take advantage of the latest improvements in the systems engineering metamodel.

Follow Us: