Relatics 6.10 introduces a major new capability for organizations aiming to standardize and reuse information across projects: Libraries. In addition, this release includes several valuable other enhancements such as a new import mapping, workspace types and an improvement to the template functionality.
Explore all new features and improvements in the release notes below.
Libraries
Libraries help ensure consistency and quality, accelerate project setup, and leverage proven best practices and accumulated knowledge; ultimately improving efficiency and project outcomes.
Within Libraries, two types of standardized information are distinguished:
- Reference elements: information with a lifecycle or relevance that extends beyond a single project. These elements have a single occurrence and are referenced as needed.
- Stencils: information intended for repeated reuse accross projects, or “stencilling”. Stenciled information can still be tailored to the specifics of a project, but it prevents reinventing the wheel. Typical examples include standard inspections, risks, requirements and system breakdowns.
Reference elements
In addition to the regular elements used in Systems Engineering models, we’ve introduced a new kind of element: Reference elements. These elements differ in meaning from the existing type elements (now referred to as Project type elements), and the software also treats them differently. Their introduction provides a clearer distinction between core, project-specific engineering data and secondary contextual metadata.
Typical examples of Reference elements include persons, organizations, equipment (they are all unique and do not “cease to exist” when a project ends), as well as centrally agreed classifications such as object types, categories, or classes.
When creating new type elements, Power Users can now explicitly choose between Project type elements and Reference type elements. Existing elements can also be easily converted between the two types when needed. In the Type graphview, Reference type elements (and their properties and relations) are visually distinguished, and their visibility can be easily toggled through the view options.

By default, Reference elements are displayed in the property table on the detail view and appear as properties within table overviews.

If a Reference element has unique identifier that is determined outside of Relatics (e.g., a certain code or number), it can be assigned as the element’s natural key, replacing the default Relatics auto-generated ID.

Stencils
Where Reference elements enrich your project with secondary contextual metadata, stencils enable repeated reuse of standardized data across similar future projects. Stencils originate from Library workspaces, managed by domain experts. The following sections describe the workflow from managing and publishing libraries to using the standardized data in a project.
Managing and publishing a library
Libraries are created and maintained within dedicated library workspaces. Similar to regular project workspaces, these workspaces contain a type model, allowing library users to capture and manage knowledge derived from projects for reuse in similar future projects. Examples can include standard objects, risks, requirements, and inspections. Depending on the organization’s preferences, different categories of standard information can be maintained within a single library workspace or divided across multiple library workspaces.
Within a library workspace, the Power User can define Library definitions that specify exactly which information and fields should be made available to projects. This is done by copying a query script from an overview table, similar to how reports or exports are set up, and verifying the output using the preview feature. Once verified, the Power User publishes the library, generating an .RCSL file.

Including a library in the project workspace
As described above, publishing a library produces an .RCSL file that can be imported into any project workspace by the Power User. As a side note, an .RCSL file may also be created based on an open-standard XML file, enabling projects to use libraries that are managed in third-party applications as well.
When importing a library into a project workspace, the Power User maps the fields from the library file to the type elements, properties, and relations within the project’s type model. The library workspace and the project workspace do not need to share an identical type model, although doing so is recommended for convenience and consistency.
The chosen ‘Entry element’ defines the location in the workspace where project members can use the library.

Using the library as a project member
When creating new project data, users can now choose to either create a new element from scratch or to utilize the standard information from the library. This is done by dragging or copying/pasting items, called ‘Stencils’, from the ‘Libraries’ view below overview tables. A search box helps users quickly find the item(s) they’re looking for, and each item can be previewed before actually incorporating it in the project.

Note that:
- For each type element, multiple libraries can be offered to project members. These can be either different version of the same library, or libraries from different sources.
- Users can either create new elements from the library one-by-one or more at once, by selecting multiple stencils.
- Each stencil can be used multiple times. The ‘Usage count’ column indicates how many times the stencil is used. By clicking on that number, a pop-up opens displaying all elements based on the stencil.
- All information that users create with the use of a library, can be freely modified or deleted.
- Individual stencils can be disabled, to indicate they’re not relevant for the project and to prevent users from including them in the project.
Advanced library use cases
Besides the standard Library features, as mentioned above, multiple more advanced use cases are supported.
Besides the inclusion of single elements with their properties, more extensive ‘clouds’ of information can be offered to projects as well. For example, besides just requirements, a requirement library can also contain already certain standard risk with their control measures.

Similarly, libraries can also contain recursive elements. This allows, for example, to include complete standard system decompositions into your project with just a single drag action.

As a project member, Relatics can also provide recommendations for establishing specific relations. For example, if a system originates from a library, Relatics can propose relations to associated standard requirements defined within that library.

Import mapping
Similar to the mapping functionality used when including a library, the existing Relatics import feature now also supports field mapping.
This enhancement means that field names in the source file no longer need to exactly match the model of the workspace. During an import, Power Users can map file field names to the corresponding type elements, properties, and relations in the project.
Additionally, fields from the source file can now be ignored if they don’t have to be imported into the project.

Workspace types
When creating a new workspace, Administrators can now choose from three workspace types:
- Project workspace
- Template workspace
- Library workspace
The different workspace types are organised in separate tabs, so users can easily switch between these types in the workspace overview, making it simpler to distinguish and manage workspaces with different purposes.

Template improvements
With the introduction of workspace types, the management of templates has become slightly different. Previously, a single workspace could serve both as an active project and as a template. Now, each workspace is explicitly designated as either a project workspace or a template workspace. This distinction is clearly visible in the workspace overview (see above).
When creating a new template workspace, the Administrator selects the project workspace on which the template will be based. A selection box allows the Administrator to decide whether the selected project workspace should also subscribe to the new template workspace.
This approach enables templates to be based on a tested and proven project without giving that project a double function. It also ensures that future deviations within that project do not affect other projects connected to the template.

Deprecated model constructions
With this release, certain former model constructions and workspace settings are no longer supported. Both Administrators and Power Users of affected workspaces will be notified via a horizontal top banner. Selecting ‘View details’ opens a pop-up that lists the relevant issues and provides instructions on how to resolve them.
A transition period, running until 15 May 2026, allows Administrators and Power Users to manually resolve these items. After this date, any remaining issues will be migrated automatically, which may affect workspace behavior. We therefore recommend that Administrators and Power Users address all items before the end of the transition period.
The following items may require action:
- Deprecated model constructions
Certain former model constructions are no longer supported. Power Users can review the affected constructions via the notification banner and manually resolve them. After the transition period, any remaining deprecated constructions will be migrated automatically, which may impact workspace behavior. - Undefined workspace type
A workspace can no longer be both a project workspace and a template workspace. Based on the current settings, the software cannot determine the purpose of such workspaces, resulting in an undefined workspace type. Administrators must define the workspace type in Environment administration by specifying the intended type. If no action is taken, all workspaces that could not unambiguously be classified as project workspace will become a template workspace.
Release webinar
(Re)Watch our release webinar to see the new features in Relatics 6.10.