View Categories

Editing & Managing SLM Projects

Editing & Managing SLM Projects enables engineering teams to make controlled modifications to Safety Instrumented System (SIS) data within dedicated Enterprise Project workspaces. Rather than editing live production data, users work inside isolated project environments where proposed changes can be reviewed, approved and validated before being merged back into production.

This project-based approach supports collaborative engineering, protects production data and provides a structured workflow for managing functional safety changes. Administrators can configure project settings, assign users and approvers, control permissions and monitor project progress throughout the engineering lifecycle.

This guide explains how Editing & Managing SLM Projects works, how Enterprise Projects are configured, and how project administration helps maintain secure and auditable engineering workflows.

What Is Editing & Managing SLM Projects?

Editing & Managing SLM Projects provides a controlled environment where engineers can develop, review and validate changes before those modifications are committed to the production database. Each Enterprise Project acts as a secure workspace that isolates engineering activities from live operational data.

Instead of modifying production objects directly, engineers check objects into a project where they can safely update Safety Instrumented Functions (SIFs), Inputs, Input Voting Groups and other engineering information. Once the proposed changes have been reviewed and approved, they are checked back into production through a controlled workflow.

Typical uses include:

  • Managing SIS engineering projects.
  • Developing engineering changes without affecting production.
  • Supporting collaborative engineering teams.
  • Reviewing proposed modifications before implementation.
  • Maintaining complete project audit trails.
  • Supporting Management of Change activities.

Where engineering data is imported or exported during a project, the workflow complements the Data Management Processing Adapters and Data Management Export Adapters for efficient engineering data management.

Creating Enterprise Projects for Editing & Managing SLM Projects

Creating a new Enterprise Project begins within the Enterprise Projects module. Administrators define the project configuration before assigning users, administrators, approvers and optional approval requirements.

When configuring a project, administrators can define:

  • Project name and description.
  • Optional start and end dates.
  • Project users.
  • User roles.
  • Project administrators.
  • Approval users and approval roles.
  • Foreground and background project colours.

Optional approval settings can also be enabled for:

  • Object check-out.
  • Object check-in.
  • Object deletion.

These settings allow organisations to tailor project governance according to their own engineering procedures while ensuring that Editing & Managing SLM Projects remains secure, controlled and fully auditable.

Configuring Project Users and Roles

Successful Editing & Managing SLM Projects depends on assigning the correct users and permissions before engineering work begins. Safety Lifecycle Manager allows administrators to add individual users or assign access using predefined security roles, simplifying administration for larger engineering teams.

Project administrators are responsible for maintaining project settings, managing project membership and updating configuration as engineering activities progress. Separate approval users or approval roles can also be configured to review object check-outs, check-ins and deletion requests where approval workflows are enabled.

Project colours provide an additional usability feature by making Enterprise Projects easy to identify from the project selection menu. This simplifies navigation when multiple projects are active and helps users quickly switch between engineering workspaces.

Projects involving Safety Instrumented Systems can also benefit from the guidance provided in the Safety Integrity Levels (SIL) Explained guide when planning engineering modifications.

Checking Objects Out into an SLM Project

Editing & Managing SLM Projects begins by checking production objects into an Enterprise Project. This process creates a working copy of the selected object inside the project workspace, allowing engineers to make changes without affecting live production data.

Users first ensure they are connected to the production database before selecting the required object and choosing Check Out Object from the toolbar. They then select the destination Enterprise Project and submit the request.

If project approvals are disabled, the object is checked out immediately as a background task. Where approval workflows are enabled, the request remains pending until it has been reviewed and approved by an authorised project approver.

Checking objects into a project allows engineering teams to:

  • Protect production data during engineering activities.
  • Develop and test proposed SIS modifications.
  • Collaborate safely within dedicated project workspaces.
  • Review changes before implementation.
  • Maintain a controlled engineering workflow.

Users may occasionally encounter situations where SLM prevents an object from being deleted.

This typically occurs when the object has child objects associated with it.

For example, an input may have a device associated with it within the Operate and Maintain module. In this scenario, the parent object cannot be deleted until the child object has first been removed.

The correct process is to:

  1. Locate and delete the child object.
  2. Return to the parent object.
  3. Perform the deletion operation again.

These dependency controls ensure that deleting objects in SLM does not create broken relationships or incomplete lifecycle records.

Editing Objects Within an SLM Project

Once objects have been checked out, engineers can begin modifying project data without impacting the production database. Enterprise Projects support changes to Safety Instrumented Functions, Inputs, Input Voting Groups and related engineering information while keeping every modification isolated inside the project.

Typical engineering activities include:

  • Updating Safety Instrumented Function properties.
  • Changing demand modes and process safety times.
  • Creating new Input Voting Groups.
  • Adding or modifying Inputs.
  • Removing obsolete engineering objects.

Because all modifications remain inside the project workspace, engineers can validate changes, collaborate with colleagues and complete reviews before committing updates to production. This makes Editing & Managing SLM Projects significantly safer than editing live engineering data directly.

Checking Changes Back into Production

After engineering work has been completed, users begin the check-in process to merge approved project changes into the production database. Before committing any updates, Safety Lifecycle Manager displays a detailed comparison between the project version and the existing production version.

The comparison identifies:

  • Modified object properties.
  • Newly created objects.
  • Deleted objects.
  • Relationship changes.
  • Original production values alongside proposed project values.

This review allows engineers to validate every proposed modification before the final check-in is performed. Once confirmed, the changes are processed as a background task and become part of the production database.

Where projects involve larger engineering updates, teams may first review exported engineering information using the Data Management Export Adapters before completing the final production check-in.

Managing Project Approvals for Editing & Managing SLM Projects

Approval workflows provide an additional level of control by requiring authorised users to approve critical project activities before they proceed. Administrators can independently enable approvals for object check-out, object check-in and object deletion.

When approvals are enabled:

  • Check-out requests remain pending until approved.
  • Delete requests require approval before objects are removed from the project.
  • Check-in requests require approval before project changes are merged into production.

Approvers review pending requests from within the Enterprise Projects module, where they can either approve or reject the submitted operation. For check-in requests, approvers also review the complete list of proposed engineering changes before authorising the merge into production.

Using structured approval workflows ensures that Editing & Managing SLM Projects supports secure engineering governance while reducing the risk of unintended changes reaching the production environment.

Importing Data into Editing & Managing SLM Projects

Editing & Managing SLM Projects also supports importing engineering data directly into an Enterprise Project using the Smart Import Adapter. Instead of importing data into the production database, administrators can load new engineering information into a project workspace where it can be reviewed before implementation.

To begin the import process, users select the appropriate Enterprise Project, open the Adapters module and launch the Smart Import Adapter. After selecting the correct site or processing channel, the import file is uploaded and queued for processing.

Where the import contains relational data, Safety Lifecycle Manager processes the import in multiple stages, allowing users to review the proposed changes before completing the final import.

Typical imported objects include:

  • Safety Instrumented Systems (SIS).
  • Safety Instrumented Functions (SIFs).
  • Input Groups.
  • Input Voting Groups.
  • Inputs and related engineering data.

Importing data into an Enterprise Project provides an additional layer of control by allowing engineering teams to validate imported information before it becomes part of the production environment.

Editing & Managing SLM Projects Best Practices

Following a structured approach to Editing & Managing SLM Projects helps engineering teams maintain data integrity while supporting collaborative development and controlled engineering changes.

Recommended best practices include:

  • Create separate Enterprise Projects for major engineering activities.
  • Assign project administrators and approvers before work begins.
  • Enable approval workflows for safety-critical engineering changes.
  • Review all proposed modifications before checking objects back into production.
  • Validate imported engineering data within the project workspace before final approval.
  • Monitor background tasks to confirm successful processing.
  • Maintain project records as part of the engineering audit trail.

Applying these practices helps organisations improve governance while reducing the risk of introducing incomplete or incorrect engineering information into production systems.

Improving Collaboration with Editing & Managing SLM Projects

One of the primary advantages of Editing & Managing SLM Projects is the ability for multiple engineers to collaborate within a controlled project environment. By separating project work from the live database, engineering teams can safely develop, review and refine changes without interrupting operational users.

Combined with configurable approvals, background task processing and structured project administration, Enterprise Projects provide a repeatable workflow that supports both everyday engineering activities and larger functional safety programmes.

For organisations managing multiple concurrent projects, this approach improves visibility, simplifies project administration and provides greater confidence that only approved engineering changes reach production.

Related Resources

Authoritative External Reference

For internationally recognised guidance on managing safety instrumented systems throughout their lifecycle, including engineering changes and governance, see the IEC 61511-1 Functional Safety standard.

Please complete the form below

Please complete the form below.

You will automatically be forwarded to a demonstration video