Coordinate the change request - HxGN SDx - Update 64 - Help

HxGN SDx Help
Language
English
Product
HxGN SDx
Search by Category
Help
SmartPlant Foundation / SDx Version
10

What does a coordinate change request imply?

You are now responsible to execute the change request. You can execute the change request using the document lifecycle workflow using the internal change action. If your change request involves external contractors, please contact your sales representative to purchase and configure HxGN SDx Projects.

You can now access the current and latest version of the documents that represent the engineering changes.

For HxGN SDx Projects users

Documents are assigned to relevant contractors to allow the communication with external contractors. For more information, see Communicate with stakeholders in your project.

Why do I need a project?

Assign a project to implement the requirements of the change request at the project scope.

Your scope must be set to a project to implement the change request at the project level.

How do I assign a project?

  1. Select Update on any of the workflow steps you have come across till now to set your change request to a particular project scope.

  2. Change your scope from plant level to the assigned project level.

  3. Select Project scope and select your project from the Query list.

  4. Select Save.

Who can associate a document to different contracts in different projects and what follows?

A document can be related to different contracts in different projects.

A project engineer can associate multiple documents to a contract through the relationship builder. The software then sets the contract's external organization by default as the collaborating organization for the documents according to the contract needs.

  • Set an action or contract to the documents related to your change request. A warning message is indicated if a document is not set to either an action or a contract.

  • Set to project scope if you require the change request to be implemented at project level.

  • You must have the MoC Owner role assigned to coordinate the change.

  1. Select Coordinate change implementation in your To Do List, and then select Coordinate Implementation on the Actions menu.

  2. For each document that needs changes, select > Create Internal Change Action and create the internal change action as described in Create an internal change action.

  3. Use Potential Impacts and Potential Conflicts to Analyze the impact of the requested change.

  4. Select Complete when the requested changes are implemented.

To review the proposed solutions, log on as a user with the MoC Approver role to Review and approve or reject the change to prepare it for the next workflow step.

Once a change request is claimed to the project level, all related documents, files, and tags from both the plant and project scopes are displayed in the project scope. A new revision of the document is created and attached to the change request in the project scope.

SHARED Tip You can view the documents and files attached to the change request from both plant and project scopes in the DOCUMENT VERSIONS and ALL FILES tabs. However, if the Query by selected configurations only option is selected in the Web Client Settings, only documents, files, and tags attached to the change request in the current scope will be displayed. For more information on the Query by selected configurations only option, see Query by selected configurations only.