Manage trusted operational data from one controlled source of truth.
Govern contractor companies, physical locations, work unit groups and work units through a structured hierarchy.
Master Data Management provides the controlled data foundation for AssuriCore. It manages the trusted hierarchy of contractor companies, physical locations, work unit groups and work units, while respecting which data comes from external source systems and which data can be managed inside the portal. Contractor companies and work units are imported through the Enterprise Data Warehouse and cannot be manually created or deactivated in the portal, while physical locations and work unit groups can be managed by authorized portal administrators.
Assurance depends on trusted data, not spreadsheet folklore.
Every assurance workflow depends on the quality of its reference data. If contractor companies, work units, locations and groups are unclear, the rest of the platform inherits that confusion. Master Data Management gives organizations a controlled way to structure operational data, separate source-owned data from portal-managed data and keep responsibility aligned with the correct teams and assets.
-
One controlled contractor and work unit hierarchy.
-
Clear distinction between imported and portal-managed data.
-
Contractor companies imported from trusted source systems.
-
Work units imported through the Enterprise Data Warehouse.
-
Physical locations managed inside the portal.
-
Work unit groups managed inside the portal.
-
Group-level responsibility for units managed together.
-
Read-only protection for source-system fields.
-
Clear ownership of responsible teams and people.
Operational data becomes unreliable when ownership is unclear.
Contractor companies and work units may come from external master systems, while operational grouping, locations and responsibility structures often need to be managed inside the assurance platform. Without a clear authority model, users can end up with inconsistent company names, unclear unit ownership, duplicate structures and responsibilities assigned at the wrong level. A classic human achievement: multiple truths, all wrong in slightly different ways.
-
Contractor company data may be incomplete if the source only covers companies providing work units.
-
Company names are not reliable keys between systems.
-
Work units must stay aligned with their source-system details.
-
Physical locations are not available from the Enterprise Data Warehouse.
-
Work unit groups are not available from external source systems.
-
Some units are managed individually, while others are managed as a group.
-
Group-level responsibility must not be overridden at individual unit level.
-
Responsible teams and people need to stay aligned with the hierarchy.
A governed hierarchy for contractor assets, locations and work units.
Master Data Management structures operational reference data into a clear hierarchy: contractor companies, physical locations, work unit groups and work units. Imported data remains protected, while portal-managed structures allow authorized administrators to organize assets, create locations, define work unit groups and assign responsibility at the correct level. The document describes this hierarchy as the foundation for managing contractor assets and work units across the AssuriCore Portal.
From imported master data to governed operational structure.
Master Data Management follows a structured workflow that separates source-controlled data from portal-managed data. Users can view imported contractor companies and work units, then organize them into physical locations or work unit groups where relevant.
1.
Import trusted source data.
Contractor companies and work units are imported through the Enterprise Data Warehouse. Work unit names and types come from source systems and remain read-only in the portal.
2.
Build the hierarchy.
Imported work units are initially placed under the contractor company that owns them. The hierarchy can then be organized into contractor companies, physical locations, work unit groups and work units.
3.
Create physical locations.
Authorized administrators can create, edit and soft-delete physical locations such as bases or workshops when those locations are not available from external source systems.
4.
Group units that are managed together.
Work units of the same type can be grouped when they share the same responsible team and responsible people, such as Contract Holder, Senior Well Engineer or Site Supervisor.
5.
Protect group-level authority.
When a work unit belongs to a group, group-managed values are shown read-only at individual unit level. No sneaky overrides. The software is not here for your little exceptions.
1.
Import trusted source data.
Contractor companies and work units are imported through the Enterprise Data Warehouse. Work unit names and types come from source systems and remain read-only in the portal.
2.
Build the hierarchy.
Imported work units are initially placed under the contractor company that owns them. The hierarchy can then be organized into contractor companies, physical locations, work unit groups and work units.
3.
Create physical locations.
Authorized administrators can create, edit and soft-delete physical locations such as bases or workshops when those locations are not available from external source systems.
4.
Group units that are managed together.
Work units of the same type can be grouped when they share the same responsible team and responsible people, such as Contract Holder, Senior Well Engineer or Site Supervisor.
5.
Protect group-level authority.
When a work unit belongs to a group, group-managed values are shown read-only at individual unit level. No sneaky overrides. The software is not here for your little exceptions.
Designed around source clarity and hierarchy control.
The interface should make it obvious which data is imported, which data is editable and where responsibility is managed. Users should not have to guess whether a field can be changed or whether it belongs to the source system, the portal hierarchy or the group level.
Everything needed to govern operational reference data.
Master Data Management combines source-system alignment, hierarchy management, grouping logic and responsibility assignment into one controlled data-management experience.
Organization & work unit hierarchy.
Physical location management.
Work unit management.
Responsibility assignment.
Operational role assignment.
Data warehouse import.
Source-owned read-only fields
Validation & access control
Compliance management mode.
Unique naming rules.
Soft-delete support.
Data integrity & governance.
What this means in practice.
Master Data Management helps teams trust the structure behind their assurance workflows. It reduces ambiguity around source data, protects imported values and gives administrators a controlled way to organize assets for real operational use.
Clearer data ownership.
Users can immediately see what comes from source systems and what is managed inside the portal.
Better operational structure.
Work units can be organized by contractor, location or group, depending on how they are actually managed.
Stronger responsibility alignment.
Teams and responsible people are assigned at the correct level, reducing confusion and duplicate effort.
Fewer unsafe overrides.
Group-managed values cannot be changed at individual work unit level, keeping shared responsibility consistent.
Clearer data ownership.
Users can immediately see what comes from source systems and what is managed inside the portal.
Better operational structure.
Work units can be organized by contractor, location or group, depending on how they are actually managed.
Stronger responsibility alignment.
Teams and responsible people are assigned at the correct level, reducing confusion and duplicate effort.
Fewer unsafe overrides.
Group-managed values cannot be changed at individual work unit level, keeping shared responsibility consistent.
Built for teams that depend on trusted operational structures.
Master Data Management is designed for users who need reliable contractor, location and work unit data before assurance, audit, compliance or operational workflows can work properly.
Portal administrators.
Data governance teams.
Wells teams.
Contractor management teams.
Well engineering teams.
Audit and assurance teams.
HSE teams.
Application owners.
Support teams.
Organizations managing contractor assets and work units.
Source-owned data stays protected. Portal-managed data stays governed.
The architecture separates external master data from portal-managed operational structure. Contractor companies and work units are imported through the Enterprise Data Warehouse, while physical locations and work unit groups are managed in the portal. The hierarchy then determines where responsibility is assigned and whether data is managed individually or at group level.
External source systems
-
Your Data Warehouse
-
Import contractor companies and work units
-
Build portal hierarchy
-
Add locations and groups
-
Assign responsible team and people
-
Validate structure
-
Publish trusted operational data across modules
See how Master Data Management helps teams manage contractor assets, locations, work unit groups and responsibilities through one controlled data foundation.
Make operational data easier to structure, govern and trust.