[tabs slidertype=”top tabs”] [tabcontainer] [tabtext]Transcript[/tabtext] [/tabcontainer] [tabcontent] [tab]
Service Status Change Event
0:06
Welcome to this Application Explainer video, part of our operate and maintain topic range.
0:12
In this video we will cover the subject of service status change events, commissioning functions and devices.
0:18
The Service Status Change Event is an event in SLM which tracks the change in status of functions and devices.
0:24
It provides an auditable trail with dates when these functions and devices have been commissioned, decommissioned, and replaced.
0:32
The following information will be covered in this training.
0:34
Chapter one will be an overview.
0:36
Chapter 2 will be device creation.
0:39
Chapter 3 will be service Status change event and commissioning functions and devices.
0:49
In Chapter 1, we’ll cover service statuses, effects of the SSC event on functions, effects of the SSC event on devices, and SSC object relationships with functions and devices.
1:03
As mentioned previously, the service status change event allows for the change in status for functions and devices.
1:12
The status changes for functions which can be found on the first step of the event are commissioned, decommissioned and out of service.
1:25
The status changes for devices are commissioned, decommissioned, out of service, replacing kind, replaced with same type and demolished.
1:36
Commissioned places the device online, which allows events to be recorded for that device.
1:41
Decommissioned and demolished places the device offline, making it so that events no longer have an impact on device data.
1:50
Replacing kind and replace with same type decommissions the old device and creates and commissions a new device with the same specifications.
2:00
Once a service status change event has been processed in SLM, a service status change object will appear in the object tree under the function showing the details of that change.
2:15
It will also create a device event under the affected devices detailing the change in status taking place for that device.
2:33
The status change also shows on the function object as well as the device object.
2:39
Commissioning the function provides a start date needed to enable Tier 3 metrics for that function and allows service hours to be tracked.
2:52
Commissioning devices starts the clock on tracking the device service hours and prior use hours.
2:58
It also allows for tracking failure rates for each device.
3:06
In Chapter 2, we will cover device connection to prior use certificate, viewing device information, device event history, and creating a device.
3:15
Devices can be added as a child to the Input, Output, and Logic Solver objects.
3:22
Clicking on the Device object shows several key sections of information for that device.
3:28
The Device Data section shows information like the device type, manufacturer, prior use certificate, and certification status.
3:37
If the prior use certificate has been selected for the parent of the device, those specifications will be passed on to the corresponding device, causing it to be associated with the prior use certificate, allowing the device data to be passed on to that prior use certificate.
3:55
For more information on prior use certificates, see the video on Prior Use Certificates.
4:02
The next two sections show testing data for the device, including test scheduling and which test groups it is tested in.
4:13
Next displays performance data, which shows device information like the service status, commissioning dates, number of service hours, proven hours, and other stats on the device.
4:25
Last, you’ll see history for the device, which displays a history of all of the events that have occurred, the date of the event, pass or fail status, and so on.
4:38
These events include tests, demands, bypasses, fault or failure events, and maintenance that’s been performed on the device.
4:55
To add a device, click on the Input Logic Solver output object, click on Edit Tools and Add Device.
5:05
Enter in the device ID and click on Save.
5:11
The device is now shown under the Input object.
5:19
In Chapter 3, we’ll cover service status change event workflow, commissioning functions and devices, and commissioning devices with commissioned functions.
5:30
When changing the service status of a functional device, navigate to the function, click on Edit Tools and Service Status Change Event.
5:41
If a function has not yet been commissioned, only the status for the functions will appear.
5:47
Select Commission and enter the Commission date.
5:51
Clicking Next will take you to Step 3, which displays a series of tables for the function type, inputs, outputs, and logic solvers.
6:02
Here you can see the current status before the change, what the status will change to, and the date of the change for any change in status.
6:12
SLM will also fill the status and date selected on step one for all devices.
6:18
No change in status will take place for a device that already has the desired status.
6:23
Click Save to conclude the workflow and process the event.
6:29
A Service status Change event is created, displaying the new status and date of change for the function and all of the devices that had a change in status.
6:40
If the function has been commissioned but the device has not yet been commissioned in SLM the process is very similar.
6:47
For example, a transmitter being added to the design of the function as a result of an MOC.
6:56
Once again, click on the function and use Edit Tools to add the Service status change event.
7:01
This time Scroll down to the Devices Only section and select Commissioned from among the choices and press Next.
7:09
Any devices that have already been commissioned will appear in here.
7:12
If the device has not yet been commissioned, you will see it on the next step.
7:20
Now with our input, you can see the devices that have been commissioned versus the one that has been created from the MOC.
7:27
To change the status, we select the status for commissioned.
7:36
The date that was entered in on the first step will automatically appear here.
7:39
The date, however, can be changed if desired.
7:44
Pressing Save will allow the event to process as a background task.
7:48
Once the event has finished processing, click on the tab to refresh and the results can be seen on the Service Status Change event, both in the object tree and for the device.
8:01
These commissioned devices can now be added to the test group.
8:05
For more information on building out test groups, see the video on Creating and configuring Test Groups.
[/tab] [/tabcontent] [/tabs]
