Handover Request workflow - HxGN SDx - Update 63 - Administration & Configuration

Administration and Configuration of HxGN SDx

Language
English
Product
HxGN SDx
Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version
10

The following information describes the Handover Request workflow. It explains what can and cannot be changed.

Remodel the work process

Work process remodeling, including creating new steps, requires changes to the underlying workflow template. For more information, see the rules for work process remodeling in Configure workflows and the detailed procedures in How to Configure the Workflow Model.

Details of internal process steps

What does the workflow look like?

Handover Request workflow (admin)

The steps that make up the workflow are described in the following table.

If you choose to edit the workflow, do not remove any steps marked as mandatory.

SHARED Tip For information on how to upgrade a workflow template, and the changes that have been made in various updates, see Upgrading workflow templates.

Step name

Description

Mandatory?

Comments

Set Handover Status to INPROGRESS

Sets the status of the handover object to IN PROGRESS.

The next step is Set Chapter Merge Status to INPROGRESS.

No

Set Chapter Merge Status to INPROGRESS

Sets the status of the chapter object to IN PROGRESS.

The next step is Initial Handover Review.

No

Initial Handover Review

Allows the user to review the handover request.

If the reviewer accepts the request, the next step is Validate Merge Items. Otherwise, the next step is Validate Handover Status.

Yes

This step is needed to review the handover information and approve or reject the request.

Validate Merge Items

Checks if the handover information can be merged from the project to the As-Built model.

The next step is Check Revision State of Doc.

Yes

This step is needed to stop the non-mergeable items from being merged.

Check Revision State of Doc

Checks the revision state of the document.

The next step is Merge documents and Tags.

Yes

This step is needed to validate if all the documents are signed off.

Merge documents and Tags

The handover information is merged with the As-Built model.

The next step is Set Handover Status to COMPLETE.

Yes

This step is needed to merge the changes to the plant or higher configuration for inclusion in the as-built data.

Set Handover Status to COMPLETE

Sets the status of the handover object to COMPLETE.

The next step is Set Chapter Merge Status to COMPLETE.

No

Set Chapter Merge Status to COMPLETE

Sets the status of the chapter object to COMPLETE.

The next step is Handover Completion Notice.

Yes

This step is needed as the data is already merged, and the chapter could be merged again if the status is not set to complete.

Handover Completion Notice

Allows the submitter to complete the handover request.

This is notification step, and is the last step of the workflow.

No

Validate Handover Status

Checks the status of the handover. Sends for rework, if not rejected.

If the information needs to be reworked, the next step is Reject the Handover Object. If the information cannot be handed over, the next step is Set Chapter Status to REJECTED.

Yes

This step is needed to determine if the request is to be rejected or reworked.

Set Chapter Status to REJECTED

Sets the status of the chapter object to REJECTED.

The next step is Handover Rejection Notice.

No

Handover Rejection Notice

Informs the submitter that the request has been rejected.

This is a notification step.

No

Reject the Handover Object

Rejects the handover object and sets the status of the handover object to REJECTED.

The next step is Revise Handover Object.

No

Revise Handover Object

Revises the handover object and saves the revision details.

The next step is Set New Handover Object Status to INPROGRESS.

No

Set New Handover Object Status to INPROGRESS

Sets the status of the new handover object to IN PROGRESS.

The next step is Set Chapter Status to INPROGRESS.

No

Set Chapter Status to INPROGRESS

Sets the status of the chapter object to IN PROGRESS.

The next step is Perform Handover Rework.

No

Perform Handover Rework

Allows the user to make the changes suggested by the reviewer.

The next step is Initial Handover Review.

Yes

This step is needed to make changes to the information.