Plant Operating Cases in As-Built and Projects - Intergraph Smart P&ID - 11.0 - Administration & Configuration

Plant Operating Cases in As-Built and Projects - Intergraph Smart P&ID - 11.0 - Administration & Configuration - Intergraph

Intergraph Engineering and Schematics Projects Configuration and Reference

ft:locale

en-US

Product

Intergraph Smart P&ID

Search by Category

Administration & Configuration

Smart P&ID Version

Smart Engineering Manager Version

When scoping As-Built items for a project, all the operating case data is copied together with the scoped items.

When creating a project, all the plant operating cases that exist in As-Built are created automatically in the new project.

Note the following information regarding plant operating cases when working with As-Built and projects.

Action	As-Built	Projects
Plant operating case management	You can add, delete, and rename plant operating cases as needed (performed in Options Manager). If there are plant operating case inconsistencies between As-Built and an associated project, you have to make sure that the names of the operating cases in the projects are the same as in As-Built.	You can add and rename cases as needed. You can delete only those cases that exist in the selected project only and they do not exist in As-Built. If the governing or active case in a project is defined differently from As-Built, when merging data into As-Built, the software applies the governing or active case functionality to the operating case that is defined as governing or active in As-Built and not to the case defined as governing or active in the project. When scoping items for a project whose governing or active case is different from As-Built, the software applies the governing and active case functionality to the operating case that is defined as governing and active in As-Built and not to the case in the project. Adding or renaming cases can cause inconsistencies between the current project and As-Built. You will have to make sure that the names of the operating cases in the project are the same as in As-Built. Typically, you would add or rename an operating case to fix any existing inconsistency that can be caused by adding or renaming an operating case in As-Built.
Scoping	All plant operating case data of the scoped items is automatically copied to the appropriate plant operating case of the project after the scoping is completed. If the governing case defined in a project is different from the governing case in As-Built, the governing case in the project remains unchanged when scoping items for that project.
Merging		All plant operating case data of the merged items is automatically copied to the appropriate As-Built operating case after the merging is completed. If the governing case defined in a project is different from the governing case in As-Built, the governing case in the project remains unchanged when merging items for that project.

Action

As-Built

Projects

Plant operating case management

You can add, delete, and rename plant operating cases as needed (performed in Options Manager).

If there are plant operating case inconsistencies between As-Built and an associated project, you have to make sure that the names of the operating cases in the projects are the same as in As-Built.

You can add and rename cases as needed. You can delete only those cases that exist in the selected project only and they do not exist in As-Built.

If the governing or active case in a project is defined differently from As-Built, when merging data into As-Built, the software applies the governing or active case functionality to the operating case that is defined as governing or active in As-Built and not to the case defined as governing or active in the project.
When scoping items for a project whose governing or active case is different from As-Built, the software applies the governing and active case functionality to the operating case that is defined as governing and active in As-Built and not to the case in the project.
Adding or renaming cases can cause inconsistencies between the current project and As-Built. You will have to make sure that the names of the operating cases in the project are the same as in As-Built. Typically, you would add or rename an operating case to fix any existing inconsistency that can be caused by adding or renaming an operating case in As-Built.

Scoping

All plant operating case data of the scoped items is automatically copied to the appropriate plant operating case of the project after the scoping is completed.

If the governing case defined in a project is different from the governing case in As-Built, the governing case in the project remains unchanged when scoping items for that project.

Merging

All plant operating case data of the merged items is automatically copied to the appropriate As-Built operating case after the merging is completed.

If the governing case defined in a project is different from the governing case in As-Built, the governing case in the project remains unchanged when merging items for that project.

The software copies the item data to the appropriate operating case according to the ID of the relevant operating case. So, even if an operating case has been renamed at one stage or another, the software will still copy the item data to the appropriate operating case.
If you attempt to merge data in an operating case that was created in the project and this case, does not exist in As-Built, the software stops the merge process and prompts you to create an operating case in As-Built that has exactly the same name as in the project.

See Managing Plant Operating Cases and Synchronize Plant Operating Cases.