View Categories

Object Tree Hierarchy

Object Tree Hierarchy provides the foundation for organising data within the SLM Global Module. Using a structured hierarchy of Enterprise, Site, Unit, Equipment, P&ID and Node objects, organisations can efficiently manage process safety information while supporting HAZOP, LOPA and other safety lifecycle activities.

Each object within the hierarchy has a specific purpose and relationship with other objects, allowing information to be reused throughout the system. This structure improves navigation, simplifies data management and ensures documents, equipment and hazard studies remain connected.

This guide explains how the Object Tree Hierarchy is organised, how each object is created and how these relationships support efficient process safety management within SLM.

What Is the Object Tree Hierarchy?

Object Tree Hierarchy is the structured framework used throughout the SLM Global Module to organise facilities, process units, equipment and supporting documentation. Each object has a defined relationship with its parent and child objects, making navigation intuitive while ensuring information is available throughout the safety lifecycle.

The hierarchy begins at the Enterprise level and expands down through Sites, Units, Equipment, P&IDs and Nodes. This object-oriented approach allows information to be entered once and reused by multiple modules without duplication.

  • Organise process safety information logically.
  • Provide consistent navigation throughout SLM.
  • Maintain relationships between related objects.
  • Reduce duplicate data entry.
  • Support HAZOP, LOPA and other safety studies.

Learn more about overall system configuration in the System Module Global Configuration guide. Organisations using the SLM Global Module can manage the complete hierarchy from a single location.

Creating Units within the Hierarchy

The Unit object is created beneath each Site and represents an operational area within the facility. Units form the parent object for Equipment, P&IDs and Nodes, making them a key part of the overall hierarchy.

When creating a Unit, administrators can define identifiers, names, process descriptions and other operational information. Once saved, the Unit becomes part of the Object Tree and provides the structure for all child objects.

  • Create Units beneath Site objects.
  • Assign Unit IDs and names.
  • Record process descriptions.
  • Provide the parent object for Equipment, P&IDs and Nodes.

Managing Equipment Objects in the Object Tree Hierarchy

Equipment objects represent the major process equipment protected by independent protection layers. Typical examples include pumps, vessels, tanks, furnaces and compressors.

Each Equipment object stores important information including equipment identifiers, categories, equipment types, related P&IDs, Nodes, HAZOP studies, LOPA worksheets and the protection layers associated with that equipment.

Equipment Categories and Types are selected from standard libraries created at the Site or Enterprise level, ensuring consistent classification throughout the organisation.

Learn how these libraries are configured in the Equipment Category & Type guide.

Working with P&IDs and Nodes in the Object Tree Hierarchy

P&ID and Node objects provide important relationships within the Object Tree Hierarchy. Rather than attaching drawings to every individual object, P&IDs are stored once and then linked wherever they are required.

This centralised approach ensures document revisions only need to be updated in one location while remaining available from Equipment, Nodes, Local Worksheets and HAZOP scenarios.

Nodes are primarily used during HAZOP studies and can be prepared before facilitation begins. Each Node can be related to Equipment and P&IDs, allowing facilitators to begin studies with the necessary information already organised.

Supporting HAZOP and LOPA Studies

The Object Tree Hierarchy is designed to support hazard studies by organising information before facilitation begins. Equipment, Nodes and P&IDs can all be prepared within the Global Module and then reused during HAZOP and LOPA studies.

This reduces workshop preparation time while ensuring facilitators have immediate access to equipment information, associated drawings and process nodes throughout the study.

  • Reduce HAZOP preparation time.
  • Reuse existing equipment information.
  • Maintain consistent document relationships.
  • Improve navigation during facilitation.

For more information on HAZOP preparation, see the HAZOP Facilitation Guide.

Benefits of an Object-Oriented Structure

Using an object-oriented hierarchy provides long-term benefits for both data management and process safety activities.

  • Maintain consistent relationships between objects.
  • Reduce duplicate document storage.
  • Improve navigation across the safety lifecycle.
  • Support multiple process safety modules.
  • Simplify document revision management.
  • Improve reporting and traceability.

Because objects are linked rather than duplicated, changes made to one object automatically benefit every related process safety activity.

Related Global Module Resources

Continue learning about configuring the Global Module with these related guides:

For additional guidance on process hazard analysis and process safety management, visit the AIChE Center for Chemical Process Safety (CCPS).

Please complete the form below

Please complete the form below.

You will automatically be forwarded to a demonstration video