View Categories

Instrumented Functions (IPL's)

Instrumented Functions are Independent Protection Layers (IPLs) identified during Layer of Protection Analysis (LOPA) that are implemented using instrumented systems. Within SLM, these functions provide the engineering framework for designing, documenting and managing protective functions throughout the functional safety lifecycle.

Each Instrumented Function combines inputs, logic solvers, outputs and configurable voting structures to represent how a protection layer operates in practice. By modelling these relationships, engineering teams can maintain complete traceability between hazard studies, detailed design and lifecycle documentation.

This guide explains the different Instrumented Function types available within SLM, how they are structured and how they support the development of reliable Safety Instrumented Systems.

What Are Instrumented Functions?

Instrumented Functions are engineering objects used to model protection layers that rely on instrumentation to detect hazardous conditions and bring a process to a safe state. They represent the instrumented Independent Protection Layers identified during LOPA and provide the foundation for detailed engineering design.

Within SLM, Instrumented Functions support multiple protection strategies while maintaining a consistent object structure that simplifies engineering, reporting and lifecycle management.

Each function combines:

  • Instrument inputs.
  • Input voting groups.
  • Logic solvers.
  • Output voting groups.
  • Final output devices.

This common architecture allows engineering teams to configure, review and maintain protective functions using a consistent workflow across every project.

For an overview of the complete engineering workflow, see the Instrumented Systems Overview.

Types of Instrumented Functions in SLM

SLM supports several Instrumented Function types, allowing organisations to model different forms of engineered protection while maintaining a consistent object structure. Each function type can be configured according to the protection strategy being implemented.

Supported Instrumented Functions include:

  • Safety Instrumented Functions (SIFs).
  • High Integrity Protective Systems (HIPS).
  • Interlocks.
  • Fire and Gas Functions.
  • Basic Process Control System (BPCS) functions.
  • Alarms.

Although each function type serves a different purpose, they all share common engineering principles, including configurable logic solvers, input and output structures, and voting arrangements where required.

For guidance on configuring complete Safety Instrumented Functions, see the Configuring a Safety Instrumented Function guide.

Creating Instrumented Functions

Instrumented Functions can be created directly within the Instrumented Systems module using the built-in engineering tools. Depending on the object level selected, engineers can create different function types that are appropriate for the site or unit being configured.

Once created, the function can be expanded by adding logic solvers, input structures, output structures and any required voting layers. Existing engineering objects can also be linked instead of recreated, helping maintain consistency across projects.

Using a structured approach to creating Instrumented Functions provides several benefits:

  • Standardises engineering workflows.
  • Supports consistent object relationships.
  • Reduces duplicate engineering effort.
  • Improves lifecycle traceability.
  • Simplifies future maintenance and modifications.

After creation, additional engineering information such as equipment associations, setpoints and auxiliary functions can be added as the design develops.

Building Function Structures

Every Instrumented Function within SLM follows a structured hierarchy that represents how the protection layer operates in the real world. This consistent architecture makes it easier to configure, review and maintain functions throughout the functional safety lifecycle.

The typical function structure includes:

  • Input Groups.
  • Input Voting Groups.
  • Instrument Inputs.
  • Logic Solver.
  • Output Groups.
  • Output Voting Groups.
  • Final Output Devices.

Functions such as Safety Instrumented Functions (SIFs) and High Integrity Protective Systems (HIPS) also support additional voting layers, allowing more complex architectures to be modelled while maintaining complete engineering traceability.

For organisations developing complete protective functions, the Configuring a Safety Instrumented Function guide explains the wider engineering workflow.

Applying Voting Logic

Voting logic determines how multiple inputs and outputs work together before a function initiates a protective action. SLM allows voting to be configured at several levels within the Instrumented Function structure, supporting a wide range of engineering designs.

Voting objects contain two key values:

  • N – the total number of participating devices.
  • M – the minimum number of devices required to initiate the protective action.

This allows engineers to configure common voting arrangements such as 1oo1, 1oo2, 2oo3 and other architectures used throughout the process industries.

Voting can be applied to both input and output voting layers, providing flexibility while maintaining clear documentation of how the protection layer operates.

Configured voting is automatically reflected throughout the engineering model, improving consistency between function diagrams and associated reports.

Linking Equipment and P&ID References

Instrumented Functions can be linked directly to the equipment they protect, creating clear relationships between process assets and their associated protection layers. These associations improve engineering traceability and simplify future maintenance activities.

Individual input and output devices can also be associated with P&ID references, allowing engineers to navigate directly between Instrumented Systems and engineering documentation.

Benefits of these associations include:

  • Improved equipment traceability.
  • Direct navigation to associated P&IDs.
  • Better visibility of protected assets.
  • More accurate Cause and Effect documentation.
  • Simplified engineering reviews.

For additional guidance on how engineering information is shared across modules, see Module Connections.

Managing Setpoints and Auxiliary Functions

Instrumented Functions can be configured with setpoints that define when a protective action should occur. These settings are managed through the Performance tab, allowing engineers to document the operating conditions that trigger each function.

Setpoints can include:

  • Sensor setpoint values.
  • Engineering units.
  • Setpoint type.
  • Trip settings.
  • Setpoint tolerances.
  • Time delays.
  • Engineering basis and notes.

For Safety Instrumented Functions (SIFs), configured time delays contribute to the overall response time calculation, while the associated setpoint information is also displayed within Cause and Effect Matrices for improved engineering visibility.

SLM also supports Auxiliary Functions, allowing secondary actions to be associated with a SIF without affecting its voting architecture or SIL calculations. These actions can be documented, managed and viewed alongside the primary protection function throughout the engineering lifecycle.

To learn more about Safety Instrumented Function configuration, visit the Configuring a Safety Instrumented Function guide.

Best Practices for Instrumented Functions

A consistent approach to configuring Instrumented Functions improves engineering quality, simplifies lifecycle management and supports compliance with functional safety standards. Establishing standard structures across all functions also makes future modifications significantly easier.

Recommended best practices include:

  • Use consistent naming conventions for all functions and objects.
  • Standardise voting architectures where appropriate.
  • Link equipment and P&ID references as early as possible.
  • Record engineering assumptions and setpoint basis.
  • Review function structures before completing detailed design.
  • Maintain complete traceability between LOPA studies and implemented protection layers.

Following these practices helps reduce engineering errors while ensuring Instrumented Functions remain aligned with the overall Safety Instrumented System design.

For additional guidance on documenting safety requirements, see the Safety Requirement Specification (SRS) guide.

Learn More About Instrumented Systems

Instrumented Functions form one part of a complete Safety Instrumented System. SLM connects these functions with hazard studies, engineering documentation, lifecycle management and performance reporting to provide a single source of truth for functional safety projects.

Related resources include:

For additional guidance on functional safety lifecycle requirements and best practices, refer to the International Electrotechnical Commission (IEC), which publishes the IEC 61511 standard for the process industry. 

Please complete the form below

Please complete the form below.

You will automatically be forwarded to a demonstration video