Data Management - Processing Adapters
Data Management Processing Adapters provide an efficient way to perform large-scale changes across an SLM database without manually editing individual records. Whether you need to rename hundreds of objects, reorganise an asset hierarchy or remove incorrect relationships, Processing Adapters automate repetitive administration tasks while helping maintain a consistent and accurate database.
Within Mangan Software Solutions’ Safety Lifecycle Manager (SLM), Processing Adapters use structured CSV input files to execute controlled bulk operations. Instead of modifying each object individually, administrators prepare a validated dataset, queue the processing task and monitor execution from within the application.
This guide explains how Processing Adapters work, when they should be used, how bulk processing jobs are executed and the best practices that help maintain high-quality functional safety data throughout the lifecycle.
Why Use Data Processing Adapters in SLM?
As Safety Lifecycle Manager databases continue to grow, manual administration becomes increasingly time consuming. Processing Adapters allow administrators to perform complex changes across multiple objects while maintaining consistency throughout the database.
Rather than opening each object individually, administrators prepare a single input file that defines every required modification. This approach provides a repeatable workflow that is easier to validate before execution.
Processing Adapters are commonly used when:
- Renaming large numbers of Safety Instrumented Functions (SIFs).
- Updating interlock identifiers after project changes.
- Removing obsolete object relationships.
- Reorganising plant hierarchies.
- Standardising naming conventions.
- Correcting imported engineering data.
- Supporting brownfield migration projects.
- Performing large-scale database clean-up activities.
Because every operation is processed as a managed task, administrators can monitor execution and confirm that requested changes have completed successfully before continuing with additional work.
For organisations managing extensive functional safety information, Processing Adapters provide a significantly faster and more reliable alternative to manual editing.
For more information about Data Management capabilities, see the Data Management Processing Adapters overview.
Available Data Management Processing Adapters
SLM includes Processing Adapters that automate common bulk administration activities. The training covered by this guide introduces two core Processing Adapters that simplify object maintenance using CSV-based input files.
These Processing Adapters include:
- Rename Objects Adapter — Changes object identifiers in bulk while preserving the underlying records.
- Unlink Objects Adapter — Removes parent-child relationships between selected objects without deleting the objects themselves.
Each adapter follows the same overall workflow:
- Prepare the required CSV input file.
- Populate the mandatory object information.
- Upload the file into the Processing Adapter.
- Queue the processing task.
- Monitor execution status.
- Review completion results.
- Verify that all requested changes have been successfully applied.
Although each adapter performs a different operation, they all use the same controlled processing approach, allowing administrators to safely manage bulk changes across an SLM database.
For administrators working with larger Safety Lifecycle Manager deployments, these Processing Adapters become essential tools for maintaining accurate and consistent engineering data throughout the lifecycle.
Renaming Objects with SLM Processing Adapters
One of the most common administrative tasks performed within Safety Lifecycle Manager is updating object identifiers. During plant modifications, naming convention changes or database standardisation projects, hundreds of objects may require new IDs. The Rename Objects Adapter provides a controlled method for performing these updates in bulk using a CSV input file.
Rather than editing each object individually, administrators prepare a structured CSV file containing the required object information before submitting it through the Processing Adapter. SLM then processes each record as a managed background task, allowing progress to be monitored throughout execution.
The training demonstrates that each record requires four pieces of information:
- Scope
- Type ID
- Current Object ID
- New Object ID
These values uniquely identify the object that will be renamed and specify the new identifier that should be applied. Once processing has completed successfully, the updated object IDs can be verified directly within the database.
The Rename Objects Adapter is particularly useful when:
- Implementing new company naming standards.
- Correcting imported object identifiers.
- Renaming Safety Instrumented Functions (SIFs).
- Updating Interlock identifiers.
- Supporting brownfield migration projects.
- Preparing databases for commissioning or handover.
Preparing the Rename Objects CSV
The quality of any Processing Adapter task depends on the quality of its input file. Before queuing a job, administrators should verify that every row contains complete and accurate information.
The training demonstrates a straightforward workflow for creating the CSV file:
- Identify the objects that require renaming.
- Collect the Scope for each object.
- Record the object Type ID.
- Enter the existing Object ID.
- Specify the replacement Object ID.
- Save the completed CSV file.
Before uploading the file, it is considered good practice to:
- Review all object IDs for typing errors.
- Confirm naming standards have been agreed.
- Remove duplicate entries.
- Test a small batch before processing a large dataset.
- Retain a backup copy of the original CSV file.
Careful preparation reduces processing errors and helps ensure that bulk updates are completed successfully on the first execution.
Preparing the Unlink Objects CSV
As with every Processing Adapter, successful execution begins with a well-prepared CSV file. Administrators should ensure that both the child object and the parent relationship are correctly identified before submitting the task.
The workflow shown in the training is:
- Identify the child object to be unlinked.
- Record the Child Type ID.
- Record the Child Object ID.
- Identify the parent object.
- Record the Parent Type ID.
- Record the Parent Object ID.
- Specify the appropriate Scope.
- Save the completed CSV file.
Before uploading the file, administrators should validate that every object exists within the specified scope and that the intended parent-child relationships have been correctly identified. Performing these checks helps avoid unintended changes and reduces the need for corrective work after processing.
Running and Monitoring Data Processing Tasks
After preparing the input file, administrators can upload the CSV file into the appropriate Processing Adapter and queue the task for execution. SLM processes the request as a managed background job, allowing users to continue working while the task runs.
The training shows that administrators can monitor progress through the Processing Adapter Tasks view, where queued, running and completed jobs are displayed.
Once processing has completed, administrators should verify the outcome by reviewing the affected objects within SLM to confirm that the requested changes have been successfully applied.
A recommended workflow is:
- Validate the CSV file.
- Upload the input file.
- Queue the Processing Adapter task.
- Monitor execution progress.
- Review any reported processing issues.
- Verify the resulting database changes.
- Archive the input file for future audit purposes.
Following a structured execution and verification process helps maintain confidence in bulk database administration while supporting accurate, consistent and auditable Safety Lifecycle Manager data.
Best Practices for Using Data Management Processing Adapters
Although Processing Adapters simplify large-scale administration, they should be used as part of a controlled data management process. Good preparation and validation significantly reduce the likelihood of errors while ensuring that changes remain traceable and repeatable.
Before executing any bulk processing task, administrators should consider the following recommendations:
- Back up the database or ensure an appropriate recovery strategy is available.
- Validate all CSV data before uploading.
- Confirm that object identifiers follow approved naming standards.
- Test new processing files on a small dataset before running large jobs.
- Carry out bulk updates during planned maintenance periods where appropriate.
- Review Processing Adapter results before beginning additional administration work.
- Retain CSV files as part of the project audit trail.
These simple practices help maintain database integrity while providing confidence that bulk updates have been completed successfully.
Common Administration Scenarios
Processing Adapters support many routine administration activities throughout the functional safety lifecycle. While the training demonstrates object renaming and unlinking, the same structured workflow can be applied whenever large numbers of controlled data changes are required.
Typical examples include:
- Implementing revised plant naming conventions.
- Updating Safety Instrumented Function (SIF) identifiers after project changes.
- Reorganising plant or unit structures.
- Removing obsolete parent-child relationships.
- Correcting engineering data following imports.
- Preparing databases for commissioning activities.
- Supporting migration from legacy systems.
- Standardising object information across multiple sites.
Using Processing Adapters instead of manual editing improves consistency, reduces administration time and helps maintain high-quality engineering data throughout the Safety Lifecycle.
Related Resources
If you are working with Data Management Processing Adapters, the following guides provide additional information on related administration tasks:
Additional Functional Safety guidance:
These related guides explain the wider functional safety concepts that Data Management activities support and help place bulk administration tasks within the overall Safety Lifecycle.
Authoritative External Reference
For further guidance on the functional safety lifecycle and the management of safety instrumented systems, see the official IEC 61511-1 functional safety standard. The standard covers the specification, design, installation, operation and maintenance of safety instrumented systems in the process industry.
