Let's take it from a fundamental approach. A project can contain several contexts and each context is governed by a syntax.

The syntax defines the basic rules for the system structure and will decide how you can build a structure. This also applies in the structure below, which is an example of a shortened car wash design.

A systems breakdown structure can be created in many ways. This example represents a functional aspect and each letter code represents a different RDS 81346 classification table.

Normally, you will either look at your Piping & Instrumentation diagram (PI) or Electrical diagram when you start designing the structure.
This design has been created from a PI diagram and contains three high-level systems (one letter code) and each high-level system contains system elements (normally two and three letter codes).

The systems or system elements are either high-level systems, mid-level systems (two letter code) or component systems (three letter codes), depending on the rules defined in the syntax.

In the example above, system elements are organized across disciplines, i.e. mechanical and electrical elements are mixed into one functional system.

For instance, this PI diagram represents the structure above. Here you can see the resemblance between the PI diagram and the structure.

In the sidebar you can add or find information on the selected system.

Context (Functional breakdown) - Set the level of information (LOI) for the context

​Selected OOC - Set the LOI for the system

Heritage - Refers to the exact position of a system in a given structure

Color - Let you choose a color for the system

Description - Lets you describe the system(s) or add important information

Image - Upload a image related to the system

Owner - Assign owners to specific systems to gain an overview of ownership

Owner Groups - Assign owner groups to a system(s)