Managing Revisions in an As-Built and Project Environment - Intergraph Smart P&ID - 11.0 - Administration & Configuration - Intergraph

Intergraph Engineering and Schematics Projects Configuration and Reference

Language
English
Product
Intergraph Smart P&ID
Search by Category
Administration & Configuration
Smart Electrical Version
10
Smart P&ID Version
11
Smart Engineering Manager Version
12

In an As-Built environment the revision uniqueness must be maintained between the Projects and the As-Built across the whole Plant. You can maintain uniqueness in either of the following ways:

  • Using a SmartPlant Foundation revision scheme, where the software tracks incremental changes.

  • Using a tool revision scheme.

SmartPlant Foundation also uses the reserved revision method. The software generates a number following the highest existing minor revision when there is a gap in the minor revision sequence.

Example:

Drawing_Proj was claimed to Project 1. It was modified in the project and saved in Project 1 with revision C01. Drawing_Proj was claimed to Project 2, was modified in the project and saved later in Project 2 with revision C02.

* SmartPlant Foundation maintains the next revision number to the item (in this case: document) that gets published first, and a subsequent number to the item that gets published second. In the table below, the Drawing_Proj from Project 1 was published first, and Drawing_Proj from Project 2 was published second.

Plant Entity

Document name

Start of available major and minor revision

Changes to major and minor revision when in Projects

Published Major and minor revision numbers generated by SPF*

As-Built

Drawing

C00

Project 1

Drawing_Proj

C00

C01

C03

Project 2

Drawing_Proj

C00

C02

C04