Skip to main content
Version: 2026.10

What Is a System?

A System is a named group of Resources and optional Subsystems you treat as one engineering unit, such as a product, project, or program.

A System groups:

  • Resources: files registered with the platform, each with its own revision history
  • Subsystems: other Systems linked into this one

What Can You Do with a System?​

  • Share it all at once. The role you give someone on a System carries over to every Resource the System tracks, as view or edit access. Control tags and InfoSec levels on each Resource still apply.
  • Version it as a whole. Branches and commits record which Resources belonged together at each point, so several people can work on one System and keep track of changes. You'll learn more in Revisions and Version Control.
  • Keep a record of outside work. The workflow log stores runs such as verification or simulation scripts, linked to the branch and commit that were active when they ran. You'll learn more in Workflow Logs.
  • Classify it. When InfoSec levels are on, the System has a classification level, and its Resources can't be set higher than that level. You'll learn more in Control Tags and InfoSec Levels.

Branches​

Use branches to version a System and to work on different versions of it side by side. Every System starts with a baseline branch. A commit is a saved point on a branch. It records which Resources and Subsystems belonged together at that moment.

A System is NOT a folder!​

One Resource can be in many Systems, and a System does not copy the Resources it groups. Inside a System, you can arrange Resources into folders to make them easier to browse.

Put it All Together​

An example of how you would use a System: the Asteria System, which you'll see in the next lessons, represents an orbital spacecraft. It groups the spacecraft's requirements, CAD models, analysis results, and verification reports, and links in the Systems that make up the spacecraft as Subsystems.