SEC-Hub Glossary

Terms

Definition

Aspects are filters, which are used to view an object. An aspect is either a function, product, location, or type.

Generic description of letter codes, which are based on three different abstraction levels; see system levels.

Codes refer to letter codes defined in the RDS 81346 standard and realize the common language in a reference designation system.

A context contains a structure, which contains sets of different systems, component systems, etc.

A context contains either the functional, product, location or type aspect.

The Common Reference Editor is a module where you design your structure and classify your systems. Here's how you get started with your design!

DOMA

Refers to RDS relations across contexts.

The depth of a syntax element dictates a specific syntax element's nesting level. It governs whether a syntax element can be applied on the 1st, 2nd, 3rd, or infinite levels on the tree structure.

Makes a detailed comparison of the Discrepancy Analysis baseline and the Main Context, allowing users to merge or reject change proposals from the Discrepancy Analysis baseline.

This refers to the Trade Study Context's SIMO grid, which is used as the baseline for a discrepancy analysis between the Trade Study and the Main Context.

Shows the exact position of a selected system in a given structure.

An interface is a pragmatic relation between two systems. A system can give an output and receive input.

As a result of the collaboration between ISO and IEC, it is a part of the 80000 series.

RDS = Reference Designation System

The only cross-disciplinary standard applied within all professional disciplines is the presumption; everything is about systems.

The LOI indicates the stage at which either the project, context, system, or interface is.

An owner is an individual who has the main responsibility for a specific system or systems.

An owner group is a group of people who has the responsibility for a specific system or systems.

A project should be the prime overall subject of your design. Projects can contain one or more contexts.

The Systems Integration Monitor is a module that is used to define interfaces between systems within a context.

The SIMO classification table contains all the codes for the interfaces/relations between systems you create in the SIMO module.

The source is the system that initiates the interface.

A structure is within a context and is the general term for the design in a context. It consists of the breakdown of systems and component systems.

The syntax secures a uniform structure in a more detailed approach and governs how the system breakdown can be designed. See it as a set of rules you create, which are applied in the CORE design process.

The syntax elements represent the abstraction levels of TAG systems. See the syntax elements you build as either your high-(One letter code) & mid-level (Two letter code) systems or component systems (Three letter code).

A system is a combination of interacting organized elements. The term a system of systems refers to a set of systems for a task that none of the systems can accomplish independently. This is shown below:

When classifying a system, you may use ONE, TWO, or THREE letter codes to break a system down into system elements.

System ownership determines that someone owns a specific system.
It's possible to assign users or non-users as owners to gain an overview of system responsibility.

The target is the system that receives the interface (output from another system; see Interfaces).

A trade study is a copy of the Main Context from where you can create several baselines and run various analyses from the Trade Study back towards the Main Context.

When you have created a trade study then you have created a trade study baseline. This baseline can become a discrepancy analysis baseline etc., depending on the analysis you desire.

A true user refers to a person that are using the SEC-Hub.