Case

Case 1: Naming Conventions

A naming convention is a very useful tool to ensure that every object has a unique name and that everyone is referring to the same object. However, it can be quite difficult to manage a naming convention across tens of thousands of objects. When different aspects of the same object are managed in separate databases, a simple typo can cause confusion about whether the same object is being discussed. Inconsistencies in the naming convention can cause significant delays and confusion. EDM can help manage naming conventions by highlighting objects that do not comply with the convention, objects that have not yet been renamed, objects with inconsistent names across databases, and objects named in compliance with the naming convention but with names that do not match their object type. These issues will be listed to be systematically addressed, ensuring that everyone is referring to the same object and saving time in the process.

Case 2: Data Inconsistencies

A plant has thousands of items for which data is currently being maintained manually in several separate databases. Ideally, updating one database should also update the same property for the same item in another database. However, due to manual updates, inconsistencies in data frequently occur. Examples of data maintained in separate databases that must remain consistent include operational status, location, description, and safety classification. Without a single source of truth, inconsistencies can arise and cause significant delays during engineering projects and unsafe situations. By setting up comparisons and rules, EDM can detect inconsistencies and highlight them by creating issues. By systematically addressing these issues, data will be kept consistent and up-to-date across all data sources connected through EDM. This saves time by eliminating the need to manually check every property of each item in all separate databases.

Case 3: HAZOP

HAZOP studies are recurring activities in every plant that ultimately define the actions necessary to ensure the safety of the plant, its processes, and its people. However, activities based on HAZOP studies can sometimes interfere with other projects in the plant, causing delays, confusion, and frustration for both the HAZOP team and the engineering project team.EDM can help by keeping track of all activities required for any object within the framework of any project in the plant. When an object is scoped for a project, EDM will highlight whether this object is involved in another project or HAZOP activity and show its scope within the other project. This enables both project teams to be aware of each other’s activities and take appropriate action. Conflicts of actions scheduled to be done on the same object can be detected early, saving time and money.

Case 4: Migrations

DCS migration

• Engineering phase
• Design phase
• Construction phase

Data migration

• Engineering Software migration (for example CAD to SPI)
• Data validation against list of requirements