Data Management - Delete Adapter
Data Management Delete Adapter provides a controlled method for removing objects from Safety Lifecycle Manager (SLM) using structured Excel input files. Rather than deleting objects individually, administrators can perform secure bulk deletions while maintaining data integrity and ensuring the correct objects are targeted.
The Delete Adapter is designed for engineering teams managing large datasets across multiple sites, units or projects. By requiring only a small number of object identifiers, the process reduces manual effort while providing a repeatable workflow for controlled data administration.
This guide explains how the Data Management Delete Adapter works, how to prepare the required Excel input file, and the best practices for safely deleting engineering data within SLM.
What Is the Data Management Delete Adapter?
The Data Management Delete Adapter is a component within the SLM Adapters module that manages the controlled deletion of engineering objects. Instead of removing records manually, administrators prepare an Excel input file containing the minimum information required to identify each object before submitting the deletion task.
According to the training, only three pieces of information are required for each object:
- Type ID
- Object ID
- Scope
These identifiers allow SLM to locate the correct object and process the deletion while maintaining database integrity. This structured approach helps minimise the risk of accidental deletions and provides a consistent process for managing engineering information.
For organisations performing wider administration activities, the Delete Adapter complements the Data Management Processing Adapters and Data Management Export Adapters, providing a complete toolkit for managing engineering data throughout its lifecycle.
Why Use the Data Management Delete Adapter?
Deleting engineering data directly from a complex functional safety database can be both time-consuming and prone to error. The Data Management Delete Adapter simplifies this process by allowing multiple objects to be removed in a single controlled operation using a predefined Excel file.
Rather than deleting records one at a time, administrators prepare a structured input file and submit it through the Adapters module. This approach supports repeatable engineering workflows while reducing manual administration effort.
Typical uses include:
- Removing obsolete engineering objects.
- Cleaning up imported test data.
- Deleting objects across multiple scopes.
- Supporting controlled database maintenance.
- Reducing manual administration time.
- Improving consistency during bulk deletion activities.
Where engineering information has first been reviewed or exported, administrators can combine this workflow with the Data Management Export Adapters to validate data before deletion.
Preparing a Delete Adapter Excel File
Before running the Data Management Delete Adapter, administrators create a structured Excel file containing the objects that are to be removed. Each row represents one object, while the columns contain the three identifiers required by the Delete Adapter.
The Excel input file contains:
- Type ID.
- Object ID.
- Scope.
The training demonstrates building an Excel file containing two objects from different scopes before uploading the completed spreadsheet into the Delete Adapter. This same structure can be expanded to include larger batches of objects, making it suitable for bulk engineering administration activities.
When preparing deletion files, it is good practice to verify the object identifiers before submitting the task, ensuring that only the intended engineering objects are removed from the selected scopes.
Understanding Type ID, Object ID and Scope
The Data Management Delete Adapter relies on three identifiers to locate and remove objects accurately. These values uniquely identify the object to be deleted and ensure that the correct record is targeted within the selected scope.
The three required fields are:
- Type ID – Identifies the object type within Safety Lifecycle Manager.
- Object ID – The unique identifier assigned to the object.
- Scope – The Object ID of the site or location where the object exists.
The training demonstrates retrieving this information by selecting the required object and opening the Views toolbar. The Light Bulb icon displays metadata including the Type ID, Object ID and Scope, allowing these values to be copied directly into the Delete Adapter Excel file.
Using the correct identifiers is essential because the Delete Adapter removes only the objects specified within the uploaded spreadsheet.
Using the Master Channel
After preparing the Excel file, administrators upload it through the Delete Adapter within the Adapters module. The correct processing channel depends on where the selected objects are located.
When deleting objects from multiple scopes, the training demonstrates selecting the Master Channel. This channel is designed to process deletion requests that span more than one site or scope, ensuring all specified objects are handled within a single task.
If all objects belong to a single scope, administrators can instead select the channel assigned specifically to that scope.
Selecting the appropriate channel helps ensure the deletion task is processed efficiently while maintaining the integrity of engineering data across the SLM environment.
Running a Data Management Delete Adapter Task
Once the correct processing channel has been selected, administrators attach the completed Excel file and queue the deletion task. Safety Lifecycle Manager validates the request before processing the selected objects in the background.
The standard workflow is:
- Select the appropriate Delete Adapter channel.
- Choose Select Files.
- Attach the completed Excel input file.
- Queue the deletion task.
- Allow the background process to complete.
Using the Editing and Managing SLM Projects showing a controlled check-in workflow from project review and approval to production deployment in this way provides a repeatable workflow for removing multiple engineering objects while reducing manual administration effort. Where large-scale database changes are planned, administrators may first use the Data Management Export Adapters to review engineering data before performing controlled deletions.
Monitoring Delete Adapter Tasks
After a deletion request has been queued, administrators can monitor its progress through the Adapter Tasks area of Safety Lifecycle Manager. This allows users to confirm whether the request is waiting to be processed, currently running or has completed successfully.
The training shows that completed deletion jobs are also visible within the dedicated Delete Adapter Tasks screen, providing confirmation that the requested objects have been processed.
Monitoring task status helps administrators:
- Confirm successful task completion.
- Identify processing issues quickly.
- Verify that uploaded files have been accepted.
- Track bulk deletion activities.
- Support controlled engineering administration.
Regularly reviewing Adapter Tasks is considered good practice, particularly when performing larger administration activities involving multiple engineering objects or scopes.
Verifying Successful Deletions
After the Delete Adapter task has completed, administrators should verify that the requested objects have been successfully removed from Safety Lifecycle Manager. This final validation step confirms that the correct objects have been deleted and that the task has completed without errors.
The training demonstrates verifying the deletion by returning to the original object locations and confirming that both the alarm object and the equipment object have been removed from their respective scopes. This provides assurance that the uploaded Excel file was processed correctly and that only the intended objects were affected.
Verification should always be performed after bulk deletion activities to ensure database accuracy and maintain confidence in the integrity of engineering information.
Data Management Delete Adapter Best Practices
The Data Management Delete Adapter is intended for controlled engineering administration rather than routine object removal. Following a structured workflow helps minimise the risk of accidental deletions while maintaining the quality of engineering data throughout the Safety Lifecycle Manager environment.
Recommended best practices include:
- Verify the Type ID, Object ID and Scope before creating the Excel input file.
- Confirm that every object listed is intended for deletion.
- Use the Master Channel when deleting objects from multiple scopes.
- Monitor Adapter Tasks until processing has completed successfully.
- Verify the deleted objects after the task has finished.
- Export important engineering information before performing large-scale deletion activities.
- Maintain copies of deletion spreadsheets as part of the engineering audit trail where required.
Following these practices helps ensure the Data Management Delete Adapter remains a safe and repeatable tool for managing engineering information while protecting the integrity of the production database.
Related Resources
Authoritative External Reference
For guidance on managing safety instrumented systems throughout their lifecycle, see the official IEC 61511-1 functional safety standard. It covers the specification, design, installation, operation and maintenance of safety instrumented systems in the process industry.
Data Management – Delete Adapter
0:06
Welcome to this Application Explainer video, part of our Data Adapters topic range.
0:10
In this video, we’ll cover the subject of Delete Adapters within SLM.
0:14
A delete adapter refers to a component or module responsible for managing deletion of data within the application.
0:21
It often encapsulates the necessary logic and operations required to safely and efficiently delete the targeted data whilst ensuring data integrity.
0:30
To utilise the Delete adapter for removing objects, only three data elements are required for the deletion of each object, type ID, object ID and the scope.
0:45
To efficiently delete multiple objects, we utilise the Delete adapter which is located within the Adapters module.
0:53
These adapters operate with an Excel input file structure as follows.
1:01
Type ID of the object, object ID of the object and scope.
1:07
The scope refers to the site’s object ID where the object is situated.
1:16
Let’s go ahead and build the Excel file with the information of the two objects from two different scopes.
1:34
In order to find the information for the type ID, object ID, and the scope for each object, we can click the light bulb icon in the Views toolbar.
1:47
In there, we’re going to find the object ID of the object, the scope and type ID of the object, and some other metadata and integration information.
1:56
For this scenario, we just need these three elements, so I’ll go ahead and copy and paste these into the Excel file.
2:15
We’ll also delete some equipment data which is located in a different scope, so again, I’ll copy and paste the required information into the Excel file.
2:40
Once we’ve built the Excel file, we can proceed to the Delete Adapters feature in the Adapters module.
2:50
Since we’re deleting 2 objects from two different scopes, when we come to the channel, we’ll select the master channel.
2:56
The other channels are designated for processing data related to those specific scopes.
3:01
Since in this scenario we’re deleting data from two different scopes, we’re going to use a master channel.
3:09
We then press Select Files button and attach our Excel file and queue the task.
3:23
We can check for the status of the task under Adapter Tasks and Delete Adapter tasks.
3:39
After the process is completed, we can verify that both objects have been deleted, the alarm under the first scope and the equipment under the second scope.