Service Status Change Event
A service status change event provides a controlled way to record when safety instrumented system functions and devices are commissioned, taken out of service, decommissioned or replaced. Within Safety Lifecycle Manager (SLM), these events create a dated, auditable history of important changes throughout the operational lifecycle.
Accurate service status is more than an equipment record. Commissioning establishes when functions and devices enter service, enabling SLM to begin tracking information such as service hours, prior use hours, failure rates and Tier 3 metrics where applicable.
This guide explains how the SLM Service Status Change Event works, the different statuses available for functions and devices, how commissioning affects lifecycle data, and how status changes are recorded against the affected objects.
What Is a Service Status Change Event?
A Service Status Change Event in SLM records a change in the operational status of functions and devices. It provides an auditable record showing the date on which equipment was commissioned, decommissioned, taken out of service or replaced.
Functions and devices have different available status options because their operational lifecycle requirements differ. Function status changes include Commissioned, Decommissioned and Out of Service. Device status options additionally include Replacing Kind, Replaced with Same Type and Demolished.
When a Service Status Change Event is processed, SLM creates a Service Status Change object beneath the affected function in the object tree. The change is also represented against the affected devices, providing traceability from the function level down to individual equipment.
This lifecycle history is particularly useful for safety instrumented systems, where teams need to understand not only the current configuration but when equipment entered or left service. The Safety Instrumented System guide provides broader context for the role of SIS equipment across the functional safety lifecycle.
Service Status Change Event Statuses and Their Effects
The status selected during a service status change determines how the affected function or device is treated within SLM. Commissioning places a device online and allows subsequent events to contribute to its operational information.
Decommissioning or demolishing a device places it offline. Once offline, subsequent events no longer affect the device data in the same way as they would for equipment actively in service.
The replacement options support equipment changes while retaining lifecycle traceability. Replacing Kind and Replaced with Same Type decommission the existing device and create and commission a new device using the applicable specifications.
This provides a clearer distinction between the history belonging to the original device and the operational history that should accumulate against its replacement. Rather than simply overwriting an equipment record, the change can be represented as part of the device lifecycle.
Commissioning SIS Functions and Devices
Commissioning is particularly important because it establishes the point from which operational information begins to accumulate. Commissioning a function provides the start date required for SLM to enable Tier 3 metrics for that function and begin tracking its service hours.
Commissioning an individual device starts its service-hour and prior-use-hour tracking. It also enables the accumulation of information used for device failure-rate tracking.
This makes the commissioning date an important lifecycle data point rather than simply an administrative status. Without an appropriate start point, operating-time information cannot accurately represent how long equipment has actually been in service.
The relationship between operational history and reliability information is explored further in the Failure Rate Library, where model-specific reliability information and accumulated operating experience can be managed through Prior Use Certificates.
How the Service Status Change Event Workflow Works
The service status change event workflow begins from the affected function. In the workflow demonstrated in SLM, the user opens Edit Tools and selects Service Status Change Event.
If the function has not yet been commissioned, the initial status selection applies to the function. The user selects Commissioned, enters the appropriate commissioning date and proceeds through the workflow.
SLM then displays the function and associated equipment, including inputs, outputs and logic solvers. The workflow shows the existing status, the proposed new status and the effective date for equipment affected by the change.
SLM can populate the status and date selected for the function across its associated devices. A device that already has the requested status does not undergo another status change. Once the user saves the event, SLM processes the change and creates the corresponding Service Status Change Event record.
The resulting event shows the new status and effective date for the function and for each device whose status was changed. This creates a persistent lifecycle record rather than leaving commissioning information as an undocumented configuration change.
Device Records, Event History and Prior Use Data
Devices can be created beneath Input, Output and Logic Solver objects in SLM. Each device record can contain information such as device type, manufacturer, Prior Use Certificate and certification status.
Where a Prior Use Certificate has been selected for the parent equipment, the corresponding specifications can pass to the device. This associates the device with the appropriate PUC and allows relevant device information to contribute to that Prior Use Certificate.
The device record also provides access to testing and performance information. According to the demonstrated workflow, this can include test scheduling, test-group membership, service status, commissioning dates, service hours, proven hours and other device statistics.
Event history provides another important layer of traceability. SLM can display events that have occurred against the device together with information such as event date and pass/fail status. Examples shown in the training include tests, demands, bypasses, fault or failure events and maintenance.
The Logging Events guide covers this operational event-recording workflow in more detail, while the How to Gather Prior Use Failure Rate Data guide explains how operational experience can contribute to prior-use reliability information.
Commissioning New Devices on an Existing Function
Not every device is commissioned at the same time as its parent function. Equipment may be introduced after the function is already operational, for example when a design change results in an additional transmitter being added.
In this situation, SLM allows the Service Status Change Event to be used for the devices without recommissioning the entire function. The user can select the Devices Only commissioning option and proceed to the equipment selection stage.
Devices that have already been commissioned can be distinguished from newly created equipment requiring a status change. The appropriate new device can then be set to Commissioned with an effective date. The date initially entered in the event is populated automatically but can be changed where necessary.
This workflow helps preserve the distinction between the original commissioning of the function and the later introduction of individual equipment. It is particularly relevant where equipment modifications are being managed during the operating phase of the lifecycle.
Connecting Commissioning with Testing and Performance Tracking
Commissioning affects several downstream operational workflows. Once a device has entered service, its operating history can begin to accumulate and the device can participate in the testing and performance-management processes associated with the function.
For example, the training workflow shows that commissioned devices can subsequently be added to test groups. The Configuring Test Groups guide covers how these groups are established for testing activities.
At the function level, commissioning also establishes the start date used for Tier 3 performance information. The Tier 3 Metrics guide provides additional information on this part of the Operate & Maintain workflow.
Together, these records help establish when equipment entered service, how long it has operated and what events have occurred during that period. This provides stronger context when reviewing testing, reliability and operational performance information.
Why Service Status Traceability Matters
Functional safety records need to represent the lifecycle of the installed equipment rather than only its present-day configuration. Knowing that a device exists does not establish when it was placed in service, whether it replaced another device, or which operational events belong to each period of service.
A service status change event helps preserve this chronology by associating equipment status with an effective date and retaining the resulting change within the SLM object and event history.
This is also consistent with the broader lifecycle approach used for safety instrumented systems. IEC 61511 addresses requirements across the SIS lifecycle, including operation and maintenance. Organisations should apply the standard according to their own functional safety management processes and engineering requirements.
Within SLM, status history provides supporting lifecycle traceability by connecting commissioning and equipment changes with the operational records that subsequently accumulate against functions and devices.
This is also consistent with the broader lifecycle approach used for safety instrumented systems. IEC 61511-1 addresses requirements across the SIS lifecycle, including operation and maintenance. Organisations should apply the standard according to their own functional safety management processes and engineering requirements.
Managing SIS Operational Records with Safety Lifecycle Manager
The Service Status Change Event provides the transition point between equipment configuration and its active operational history within SLM. Commissioning establishes when tracking begins, while later decommissioning, replacement and other status changes preserve the chronology of the equipment lifecycle.
These records then connect with other Operate & Maintain activities such as device-event logging, service-hour accumulation, prior-use data, failure-rate tracking, testing and performance metrics.
The MSS Safety Systems solution supports the management of safety-system information throughout these lifecycle activities. The Service Status Change Event specifically provides the SLM workflow demonstrated here for recording when functions and devices transition between operational states.
Maintaining this history gives engineers and functional safety teams a clearer record of what equipment was in service, when changes occurred and which operational information belongs to each stage of the equipment lifecycle.
