A project goes through a number of stages, from the point where it is created, to a point where it ends. At each stage the status of the project changes. Capabilities available to the user change based on this status.
-
Project Creation
Project personnel are assigned and the scope of the project is defined. -
Project Activation
Project personnel can now create new items and modify existing as-built items within this project. -
Project Completion
Project personnel can no longer perform any work in his project. The project manager can still set the project back to the Active state if further work is required. -
Project Merge
Project items and changes are now merged up to, and are now available at, the as-built level. -
Project Finished
No further work can be done in the project, and it cannot be set back to the Active state. Items can still be merged or discarded. -
Project Canceled
The project can be canceled from either the active or completed state as long as no data has been merged. The project data is still available for review. -
Project Terminated
This is the second part of project cancelation and removes all project contents from the system.
Created project state
A newly created project is given a state of Created. When in this state, the project exists only within SmartPlant Foundation and is not available for use. Certain set-up activities can be performed during this state, for example, building the project team.
Active project state
When a project is ready for design work to proceed, it is activated. The project remains in this state until it is either completed or canceled. When a project is in the Active state, all of the various project design activities can be performed.
The transition from Created to Active project state can be the result of a workflow or can be changed using the shortcut menu command, Activate Project. For the workflow transition, a SmartPlant Foundation-defined workflow is involved in transitioning a project from the Created state to the Active state. The project is now available to users.
The benefit of using the workflow is that notifications can be sent to all interested
parties.
Before a project is transitioned to the Completed project state, all design work for that project must be completed. When the project is transitioned to the Completed state, design changes can no longer be made. Therefore, steps must be taken to guarantee that there are no design changes to be made after the project is transitioned to the Completed state.
-
Items can be merged both in the Active state and the Completed state. This is because it may be necessary to merge part of a project before completion in order to release items for modification in other projects. The system can be configured to allow or disallow partial merging of items when the project is in the Active state.
-
Items cannot be merged if they have conflict with their design basis; it is possible to supersede an item claimed in one project by a merge from another project. Some users are not able to merge an item that has been superseded, but others, with sufficient privileges, can review the conflicts, make changes to their project version, and then mark their project item as having its conflicts resolved, in which case the merge can then proceed.
-
It is not possible to merge a drawing without merging its reference drawing; doing so would result in a document at the plant level that references a drawing in the project that cannot be seen from the plant.
-
It is possible to impose the practice of signing off the drawing at the project level before it can be merged.
-
Project reports can be used to identify the status of all items in the project to assist with conflict resolution.
Completed project state
The project manager can promote the project to the Completed state using a SmartPlant Foundation-based workflow or shortcut menu option.
Once a project reaches the Completed state, it can only move forward to the Finished state.
No further design changes are allowed on the project when it reaches the Completed state.
-
No additional processing is required if all items have already been merged.
-
If the system is configured to prevent merge from the Active state, then all data must now be merged. This control may be necessary where it is difficult to merge part of a project when users are still working on other parts of the project.
-
Merging a project in a single step can only be performed from the Completed state. If successful, this automatically transitions the project to the Finished state. This can be automated by a workflow employed to manage the projects.
Merge
The project is only in the Completed state long enough for the data in the SmartPlant Foundation to be fully merged into the As-Built. When the merge process is completed, the project transitions to the Finished state.
Finished project state
The final state for a successfully completed project is the Finished state. Once a project reaches this state, no more work of any type can be performed on that project.
Canceled project state
If the decision is made to cancel a project, then the project is transitioned to a Canceled state, and no further edits can be performed on the project.
Terminated project state
The final state for a canceled project is the Terminated state. Once a project reaches this state, no work of any type can be performed against that project. During this state, SmartPlant Foundation performs the activities necessary to discard the changes made as part of the project.