Planning submittal - HxGN SDx - Update 63 - Help

HxGN SDx Help

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

You can load the planned revision of a document before any data is loaded into the company's system, and relate it to plant equipment that is to be loaded into a document revision later. You can use the planned revision to compare the data with the actual revision.

When you load the planned deliverables, the planned revision of the document has a status of RESERVED. When the actual deliverable is loaded into the system, the planned deliverables' status automatically changes to RESERVEDSUPERSEDED. However, if the actual revisions are deleted for any reason, the planned revision status is changed back to RESERVED.

Page-1 Is the submittal complete? Review deliverable submission  View more Correct validation/export stage errors  View more Review the submittal progress  View more Create the planning submittal  View more Populate the CSV file MDR planning submittal Create the MDR cover sheet

Steps

Description

MDR planning submittal

The MDR planning submittal templates are stored on Smart Community and available for download.

Create the MDR cover sheet

This file is stored on the MDR document and typically is a report from the contractor's system.

Populate the CSV file

Populate the CSV file with the deliverables and issue plan dates. The MDR document is usually listed as the first row of the file.

Create the planning submittal

The submittal is created, and the documents and plan milestones are loaded into the system.

Review submittal progress

A progress screen is used to view the upload, validation, and creation of the deliverables.

Correct validation/export stage errors

Any errors reported by the validation and export stages are addressed prior to re-submission.

Review deliverable submission

The MDR and the deliverable milestones of planned deliverables can be reviewed in the system.

What can be done on a planning submittal?

While processing the MDR planning submittal, if one or more issue purposes in the attached file are not related to the current plant or project, the validation rules stop the processing, and the user must relate the issue purpose to the current plant or project to process the submittal.

  • Create the first revision of the MDR with new attached planned revisions.

    • The first row usually contains the MDR document, though this is optional.

      • The MDR document name, title, revision, issue date (dd-mmm-yyyy), and area must be supplied.

      • The MDR document classification must be set to MDR.

      • The MDR filename is optional though the submittal create process will still request one.

    • The subsequent rows are repeated for each planned issue purpose of a planned document.

      • The planned revisions require a name, title, revision of ‘--', classification, area, and a document issue date though the issue date is ignored. The issue purpose and the planned date of issue at that purpose also need to be supplied.

    • All other information is optional.

  • Update the current revision of the MDR to update the issue plan of the reserved revisions or add new ones.

    • The first row usually contains the MDR document.

      • The MDR document name, revision, issue date (dd-mmm-yyyy), and area must be supplied.

        • The issue date of the MDR is ignored if the name and revision match the current revision as this must not be changed on an issued revision.

      • The MDR document classification must be set to MDR.

      • The MDR title can be updated.

      • The MDR filename must be left blank.

  • Create a new revision of the MDR document to update the issue plan of the reserved revisions or add new ones.

    • The MDR revision must be later in the revision sequence than the current revision and the issue date must be later than or equal to that of the current revision. A time stamp is automatically added to the issue date.

    • The MDR filename is optional though the submittal create process will still request one.

  • Update the planning information of planned revisions.

    • This can be done by updating the current MDR revision or creating a new one as above.

    • The subsequent rows can contain planned revisions.

      • The planned revisions require a name, classification and area that matches that of the existing planned revision, and an issue date though the issue date is ignored. The revision should still be ‘--‘. The issue purpose and planned date of issue at that purpose also need to be supplied.

      • The title can be updated.

      • All other information is optional.

  • Update the planning information of existing deliverables.

    • This can be done by updating the current MDR revision or creating a new one as above.

    • The subsequent rows can contain planned revisions as above or existing deliverables or a combination. The existing deliverables could be recently submitted documents in the Current state or documents that have been revised from the plant to the project as part of a change in the Working state.

      • The existing deliverable revisions require a name, revision, classification and area that matches that of the latest revision of that deliverable, and an issue date though the issue date is ignored. The issue purpose and the planned date of issue at that purpose also need to be supplied.

      • The title can be updated.

      • All other information is optional.

Learn more about the preconfigured mappings for a planning submittal

Planning submittals are used to create documents with a reserved status on the Master Document Register with the planned dates for the deliverables at each issue purpose.

Pre-requisites

All submittals require the following information created in advance. This information is used when processing the submittal. The submittal will create or update the MDR and all related documents.

  • All issue purposes, classifications, and disciplines referenced in the submittal must be related to the current project or its parent plant. If you relate an issue purpose, a classification, or a discipline at the plant level to a project, it disables its inheritance from the plant.

  • A contract must exist between the contracting organization submitting the deliverables and the organization hosting the SDx system.

  • The contract must have a related review matrix that defines the consolidator for the document review work process.

This mapping is used to submit the planned deliverables. One row must contain the MDR document which is usually the first row. Two examples of content are shown below, one for the MDR row and one for the planned deliverables.

All the columns listed below must be included in the CSV file.

Column name

Mapping

Type

Example (MDR)

Example (planned deliverables)

Required

Validation

Explanation

Action

Defines action Create or Delete or Update

C

C

Yes

Set to D to delete a document with a reserved status from the MDR.

Document Number

Document Name

String

C-INGR.HSV-AB-001-MDR-01

C-INGR.HSV-AB-001-PID-000

Yes

Revision

Document Revision

String

01A

--

Yes

The current time is appended on new revisions but the issue date is unchanged when updating existing revisions.

Issue Date

Issue date of this deliverable

dd-mmm-yyyy

10-Jan-2018

10-Jan-2018

Yes

Document Title

Drawing title

String

MASTER DOCUMENT REGISTER

PROCESS INSTRUMENT DIAGRAM 000

Yes

Classification

Relationship to document typing

Relation

MDR

XC

Yes

Must exist in the system

WBSCode

Relationship to work package of type WBS

Relation

6100

No

Must exist in the system

FEEDCode

Relationship to work package of type FEED

Relation

02.06

No

Must exist in the system

Discipline

Relationship to project discipline

Relation

MECH-PR

No

Must exist and be related to the project or plant

Must be related to the project or the plant.

Area

Relationship to plant area

Relation

20

20

Yes

Must exist in the system

Unit

Relationship to unit in the area

Relation

No

Must exist in the system

File Name

Name of file to be uploaded and attached

String

C-INGR.HSV-AB-001-MDR-01.doc

Yes

Planned IP

Planned milestone issue purpose

AB

Yes

Must exist and be related to the project or plant

Must be related to the project or the plant.

Planned Date

Planed milestone issue date

dd-mm-yyyy

10-May-2018

Yes

Can be set to blank to clear the date.