MSC-PRO-ENG-440 - Hanford Site...2018/12/05 · Rev. 3 MSC -PRO ENG 440 Page 2 of 45 MSC...

Procedures

MSC-PRO-ENG-440Engineering Document Change

Revision 3, Change 0

Published: 09/24/2018Effective: 09/24/2018

Program: EngineeringTopic: Engineering

Subject Matter Expert: Dodd, EdwinFunctional Manager: Ryan, Grant

Use Type: MCP-Management ControlProcedure

*MSAPS.MSC-PRO-ENG-440*

Approved for Public Release; Further Dissemination Unlimited

Not Required : Excluded from USQExclusion Reason: MSA Facilities are non-nuclear and excluded from USQ

JHA: Administrative Periodic Review Due Date:09/24/2023Rev. 3, Chg. 0

Change Summary

Description of Change

This is a complete revision to implement the new electronic approval process.

NOTE: Employees may print off this document for reference purposes but are responsible to check MSA PS to ensure themost current version is used to prevent unintended use of obsolete versions. Use

Rev. , Chg. Page i of i

Published Date: Effective Date:

Rev. 3 MSC-PRO-ENG-440 Page 1 of 45

MSC Engineering Package Process Published Date: 9/24/2018 Effective Date: 9/24/2018

Table of Contents

1.0 PURPOSE ............................................................................................................................ 2

2.0 SCOPE ................................................................................................................................. 2

3.0 RESPONSIBLITIES............................................................................................................ 2

3.1 Engineering Package Originator .............................................................................. 2

3.2 Engineering Package Approver ............................................................................... 3

3.3 Document Control ................................................................................................... 3

4.0 INSTRUCTIONS ................................................................................................................ 3

4.1 Document Types ...................................................................................................... 3

4.2 Initiate EP – Create a New Workflow ..................................................................... 4

4.2.1 Approval Tasks ............................................................................................ 6

4.2.2 Document Control Review /Release Tasks ................................................. 7

4.2.3 Document Control Final Review ................................................................. 8

4.3 Revise an EP ............................................................................................................ 8

4.3.1 Approval Tasks .......................................................................................... 11

4.3.2 Document Control Review /Release Tasks ............................................... 12

4.3.3 Document Control Final Review ............................................................... 12

4.4 Cancel an EP .......................................................................................................... 13

4.4.1 Approval Tasks .......................................................................................... 13

4.4.2 Document Control Review /Release Tasks ............................................... 14

4.4.3 Document Control Final Review ............................................................... 15

4.5 Generating an EP for a Configured System with no Reference Drawings ............ 15

5.0 RECORD IDENTIFICATION .......................................................................................... 16

6.0 SOURCES ......................................................................................................................... 16

6.1 Requirements ......................................................................................................... 16

6.2 References .............................................................................................................. 16

APPENDIX A Engineering Package – User’s Guide ................................................................. 17

APPENDIX B Form Instructions ................................................................................................. 38

APPENDIX C Document Numbers ............................................................................................. 42

APPENDIX D Email Approval for EP ........................................................................................ 43



1.0 PURPOSE

This procedure describes the process for review, approval and release of Mission Support

Contract (MSC) engineering documents. The Engineering Package (EP) process is an electronic

work flow that is used by Mission Support Alliance (MSA) Engineering to release all types of

technical documents.

This document partially implements Integrated Safety Management System (ISMS) Core

Function #4, Perform Work within Controls.

2.0 SCOPE

This Level 2 Management Control Procedure applies to MSA and MSA contractors involved in

engineering activities in support of the MSC scope of work. The EP process is an electronic

work flow that is used by MSA engineering to release engineering documents into the site

document control system. Document types include: calculations, specifications, engineering

drawings and sketches, Facility Modification Packages (FMP), Functional Requirements and

Design Criteria documents, System Health and Status Reports, vendor information, test

procedures and engineering/technical text only documents such as reports and studies, and

Project/Program Execution Plans (PEP). These and other document types, such as work

packages, service delivery documents, etc., are governed by the procedures identified in

Appendix C of MSC-RD-RM-8310, Document Control Program.

NOTE: Software Verification and Validation documents are not released using the EP

process. Their development and release is addressed in MSC-PRO-IS-309, Controlled

Software Management.

3.0 RESPONSIBLITIES

3.1 Engineering Package Originator

The EP Originator has the responsibility to ensure that the EP is generated, approved and

released in accordance with this procedure. They are also responsible to ensure that the

appropriate approvers are assigned in the approval process in accordance with

MSC-PRO-QA-8635, Review and Approval of Technical Documents. Many of the documents

being released by the EP process will have specific procedures related to the generation of

those documents, follow those procedures for generating the required document and this

procedure for the release and approval of the documents.

Specific responsibilities include:

Generating the EP in accordance with the requirements of this procedure.

Identifying the approval personnel in accordance with the applicable procedure

(MSC-PRO-QA-8635)

Ensuring that the proper document classification is identified (e.g. OUO).



3.2 Engineering Package Approver

The EP Approver has the responsibility to ensure that their review is performed in accordance

with their governing procedures. Their signature is the indication that they have performed the

task appropriately.

3.3 Document Control

Document Control has the responsibility to ensure that the EP has been approved and released

in accordance with this procedure and their implementing procedures.

4.0 INSTRUCTIONS

4.1 Document Types

This section includes a listing of key MSA engineering documents, this list is not exhaustive.

Calculation. A document that assembles inputs, such as assumptions, bases requirements,

restraints, physical or chemical properties, and algorithms to analytically develop outputs based

on physical laws in accordance with MSC-PRO-ENG-8259, MSC Calculation Preparation and

Issue. Obtain a document number from the HDNS (HNF-CALC).

Engineering Drawing. Graphic technical documents that establish design and construction

requirements that represent the configuration baseline for a structure, system or component.

Engineering drawings shall be developed in accordance with MSC-PRO-ENG-709, CAD and

Drawing Development and Control Process for Engineering Drawings.

Engineering Sketch. A sketch is a drawing that does not change an H-series drawing and

provides information needed for the execution of field work.

Engineering/Project/Technical Text Only Documents. An engineering, project or technical

text only document developed in accordance with governing procedures, as applicable, such as

plans, reports, specifications, studies, description documents, etc. Obtain a document number

from the HDNS (HNF-RPT, HNF-PLAN, HNF-ENG, and HNF-SPEC).

Functional Requirements and Design Criteria (FRDC). The functional requirements and

design criteria shall be developed in accordance with MSC-PRO-ENG-8258, Functional

Requirements and Design Criteria.

Physical Modification. A physical modification EP, formerly known as Facility Modification

Package (FMP), is a compilation of standard forms and design elements (criteria, analysis,

drawings, etc.) in a single EP related to a specific modification task or project. The elements of

a physical modification EP shall be developed in accordance with MSC-PRO-ENG-2001,

Facility Modification Package Process.

Infrastructure Systems Health and Status Reports. Periodic reports developed in

accordance with MSC-PRO-ENG-61164, Infrastructure Systems Health and Status Reports.

The reports identify, collect, analyze, and document performance data for infrastructure



configuration-managed systems to improve their reliability and availability through early

detection of degradation.

Vendor Information (VI). Data necessary to install, operate and maintain the procured items

within a permanent structure or system. The VI process and requirements for managing the

requisition, receipt, distribution, review, approval, modification, and cancellation of

engineering VI data shall be performed in accordance with MSC-PRO-ENG-16406,

Engineering Vendor Information (VI) Process.

Program/Project Execution Plan (PEP). The PEP document shall be developed in

accordance with MSC-PRO-PM-25000, Project Execution Plans.

4.2 Initiate EP – Create a New Workflow

Once the document has been developed in accordance with their governing procedures and

process, the EP workflow shall be initiated.

NOTE 1: Some tasks are not used in the EP for approval and release of a text only document

(e.g. design verification). The EP tasks that are not used during the release of a text only

document will be greyed out during the process. Similarly, if the author has selected a

document action only, EP form sections associated with physical modifications will be greyed

out.

NOTE 2: While the EP workflow will ultimately allow for tracking and resolution of

comments within the work flow process, this version does not include that provision. This

combined with the fact that any comments received will invalidate the signatures received

previously (as part of the parallel review process) making the use of the current system for the

initial review a more time consuming process than using other means outside the workflow.

Actionee Step # Action

Document Originator 1. NAVIGATE to the DMCS workbench.

2. Using the DMCS EP Users Guide (Appendix A), SELECT “Create” a

new workflow.

3. IF the document needs cover sheets,

THEN USE the DMCS link to HDNS to create cover pages.

NOTE: See Appendix C for a list of the types and numbering schemes

for use by MSA engineering and select the appropriate document

type.

4. CONTINUE the EP process using the guide (Appendix A) and Form

Instructions (Appendix B) by filling in the requested information.




5. ENTER the required data as applicable (See Appendix A).

NOTE: Documents are uploaded by dragging the file to the File

Upload section (see Appendix A for more guidance and detailed

instructions).

6. ENSURE that a CACN is provided in the EP form by including it in a

note to Document Control.

NOTE 1: This note should also include permissions for Document

Control to add N/A to the applicable sections of the document that

were greyed out previously in the process.

NOTE 2: The form can be saved and restarted several times until the

document is complete and ready for the approval process.

DA 7. COMPLETE the USQ and Environmental Screening Sections

considering the following:

Whether USQ is necessary

Whether Environmental Activity Screening is complete.

NOTE 1: The facility point of contact may be used to identify a

qualified USQ evaluator for the facility. If multiple USQ evaluators

are needed because the change impacts multiple facilities, then attach

the USQ forms and the DA signs in the EP.

NOTE 2: A USQ is required if the changes could impact systems in a

nuclear facility. If the proposed change will impact a nuclear facility,

contact the facility point of contact to find a qualified USQ evaluator

and assign the task to them. The screening number or categorical

screening number will be listed.

NOTE 3: Originators that have the MSA basic engineering

qualification may make the determination of USQ and environmental

reviews needed.

8. IDENTIFY the required approver.

NOTE: Additional approvers may be added by emailing the DMCS

Administrator.

9. INDICATE if an Environmental Activity Screening has been

completed.




10. IF a screening has been completed,

THEN ATTACH the form to the EP.

11. IF a screening has not been completed,

THEN SELECT not required.

12. DETERMINE the necessary document approvers in accordance with

MSC-PRO-QA-8635, Review and Approval of Technical Documents

and/or MSC-PRO-PM-25000, Project Execution Plans

Document Originator 13. IF more than 8 people are required to sign the document,

THEN USE the email approval process to add approvers. See

Appendix D for details.

14. WHEN the Document is ready to be sent for approval,

THEN USE the EP to send the file to the reviewers in parallel. (The

process is automated from the perspective of the document originator

from here).

NOTE: EP process does not provide comment tracking and

resolution; you are encouraged to have all comments dispositioned

before you send the document out for approval in the EP process.

16. USE DMCS workflow process to track the status of the package

through the workflow.

17. IF a package is sent back for rework through the EP process,

THEN WORK with the reviewer to resolve the comment(s) and send

the document out for approval again.

18. REPEAT this process as necessary to get concurrence on the

document.

4.2.1 Approval Tasks


Approver 1. NAVIGATE to the assigned section in the DMCS workbench.




2. CLICK on the subject EP and review the FINAL.pdf in the EP

(see Appendix A for more guidance).

3. PERFORM the review as required by your governing

procedure(s).

4. DOCUMENT the review by your comments and/or approval.

NOTE: Reviewers are encouraged to resolve editorial comments

with the author without returning the document for rework –

otherwise all other approvals are voided.

5. IF the author needs to revise the EP based on your comments or

input,

THEN SELECT “yes” when prompted and the document will be

sent back to the author for rework.

4.2.2 Document Control Review /Release Tasks


Document Control 1. NAVIGATE to the assigned task section.

2. SELECT AND ACCEPT the task.

3. Using the link in the EP workflow, REVIEW the FINAL.pdf in

accordance with your governing procedure(s).

4. CHECK out the FINAL.PDF and add the page numbers to the

package index.

5. WHEN complete,

THEN CHECK the document back into DMCS.

6. ADD the revision number to the checked out .pdf using

Adobe®edit tools.

7. CLICK on the link to the Change Request to the Affected

Documents/Drawings listed in Block 2, Package Index, as well as

the applicable metadata.




8. SAVE and CLOSE.

9. CREATE the relationship on the Change Request to the Other

Affected Documents listed in Block 6.0 of the EP.

10. ENTER all applicable Work Package numbers, Project or Task

numbers, Area, Facility, Building, System IDs and

Responsibilities on the Change Request.

11. IF the author needs to revise the EP,

THEN SELECT the appropriate selection on the screen, enter a

note stating why and complete the task.

4.2.3 Document Control Final Review


Document Control 1. ACCEPT the task.

2. REVIEW the release stamp and correct as needed (yes to correct

and no to proceed).

4.3 Revise an EP

Actionee Step

#

Action


2. Using the DMCS EP Users Guide (Appendix A), SELECT “Revise a

workflow”.

3. INPUT the EP to revise and wait for the green checkmark to appear.

4. WHEN the green checkmark appears,

THEN COMPLETE the task.

5. IF the revision is a document action only,

THEN COMPLETE a Record of Revision (Site Form A-6001-489).



Actionee Step

#

Action

6. IF the document needs coversheets,

THEN USE the link and create coversheets.

7. WHEN coversheets are complete,

THEN CONTINUE the EP process using the guide (Appendix A) and

FORM INSTRUCTIONS (Appendix B) and filling in the requested

information.

8. ENTER the required data as available and through the EP process.

NOTE 1: Documents are uploaded by dragging the file to the File

Upload section (see Appendix A for more guidance and detailed

instructions).

9. ENSURE that a CACN is provided in the EP form by including it in a

note to Document Control.

NOTE 1: This note should also include permissions for Document

Control to add N/A to the applicable sections of the document that were

greyed out previously in the process.

NOTE 2: The form can be saved and restarted several times until the

document is complete and ready for the review and approval process.

10. COMPLETE the USQ and Environmental Screening Sections

considering the following:

Whether USQ is necessary

Whether Environmental Activity screening is complete.

NOTE: Originators that have the MSA basic engineering qualification

may make the determination of USQ and environmental reviews needed.

11. IF USQ Screening is required,

THEN CHECK the box and list the USQ number or Categorical

exclusion number.



Actionee Step

#

Action

12. WORK with the facility point of contact to identify a qualified USQ

evaluator for the facility.

NOTE: If multiple USQ evaluators are needed because the change

impacts multiple facilities, then attach the USQ forms and the DA signs

the EP.

13. IDENTIFY the required approver.

NOTE: Approvers’ that are not listed may be added by sending an

email to MSA Engineering DMCS Lead or DMCS Administrator to have

them added.

14. INDICATE if an Environmental Activity Screening has been completed.

15. IF a screening has been completed,

THEN ATTACH the form to the EP.

16. IF a screening has not been completed and is not required,

THEN SELECT Not Required.

17. ENTER the appropriate person as approver if an Environmental-

Activity Screening has been completed and attached.

NOTE 1: IF sections are greyed out, they are either not required at all

for the type of document that you are releasing or they will be completed

by the assigned individual when it arrives to them in the work flow.

Ensure that you include a note for Document Control to add any N/As

needed to the final form.

NOTE 2: Native AUTOCAD files cannot be uploaded at this time.

18. DETERMINE the necessary document approvers in accordance with


and/or MSC-PRO-PM-25000, Project Execution Plans

19 IF more than 8 people are required to sign the document,

THEN USE the email approval process to add approvers.

NOTE: See Appendix D for details.



Actionee Step

#

Action

20. WHEN the document is ready to be sent for approval in the EP process,

THEN USE the EP to send the file to the reviewers in parallel. (The

process is automated from the perspective of the document originator

from here).

NOTE: EP process does not provide comment tracking and resolution;

you are encouraged to have all comments dispositioned before you send

the document out for approval in the EP process.

21.. USE DMCS workflow process to track the status of the package through

the workflow

22.. IF a package is sent back through the EP process,

THEN WORK with the reviewer to resolve the comment and send the

document out for approval again.

23. REPEAT this process as necessary to get concurrence on the document.







procedure(s).


NOTE: Editorial comments should be resolved by working with

the author for resolution. If rework of the document is necessary,

all prior approvals are voided and it is returned to task T0040.

5. IF the author needs to rework the EP based on your comments or

input,

THEN SELECT yes when prompted and the document will be

sent back to the author.





Document Control 1. NAVIGATE to the DMCS workbench.

2. SELECT AND ACCEPT the task.


accordance with your procedure(s).


package index.

5. WHEN complete,



Adobe®edit tools.




8. SAVE and CLOSE.




numbers, Area, Facility, Building, System IDs and

Responsibilities on the Change Request.






Document Control 1. ACCEPT the task.




2. REVIEW the release stamp and correct as needed (yes to correct

and no to proceed).

3. COMPLETE the task and issue the document.

4.4 Cancel an EP



2. Using the DMCS EP Users Guide (Appendix A), SELECT

“Cancel” a workflow.

3. INPUT the EP to cancel and wait for the green checkmark to

appear. Then complete the task.

4. ASSIGN the approvers and send the work flow for approval.

5. WORK with approvers to resolve any comments and obtain

approvals.







procedure(s).


NOTE: Editorial comments should be resolved by working with

the author for resolution. If rework of the document is necessary,

all prior approvals are voided and it is returned to task T0040.




5. IF the author needs to rework the EP based on your comments or

input,

THEN SELECT “yes” when prompted and the document will be

sent back to the author.



Document Control 1. NAVIGATE to the assigned task section, select and accept the

task.


accordance with your procedures.


package index.

4. WHEN complete,



Adobe®edit tools.




7. SAVE and CLOSE.




number, Area, Facility, Building, System IDs and Responsibilities

on the Change Request.








Document Control 1. NAVIGATE to the assigned task section, select and accept

the task.

2. REVIEW the release stamp and correct as needed (yes to

correct and no to proceed).

3. COMPLETE the task and issue the document.

4.5 Generating an EP for a Configured System with no Reference Drawings

As MSA Engineering works to generate as-built drawings for systems that have recently been

designated as configured systems, there are cases where a system change is needed but it is not

appropriate to take the time and expense to complete the as-built process prior to the change.

In those cases, the proposed change is to be generated on an H-series drawing for release into

DMCS. The drawing will be tied to a “typical” or similar drawing generated by MSA

Engineering to capture the change. This “typical” drawing is to be developed to support the

release of the sketch and should be a relevant drawing that is related to the system and

proposed change. The sketch will have a unique number obtained from HDNS.

The number is to be entered in Section 2 for the release per the EP workflow. Once the

drawing is developed as an H drawing the proposed change can reference the H drawing for

usual release using the EP workflow above. This process will ensure that the change is

documented in DMCS and that when the system is configured later, the modifications made

previously are in the system and documented.



5.0 RECORD IDENTIFICATION

All records are generated, processed, and maintained in accordance with

MSC-PRO-RM-10588, Records Management Processes, or MSC-PRO-RM-32281, Electronic

Records Management, as applicable.

Records Capture Table

Name of Document Submittal Responsibility Retention Responsibility

None

6.0 SOURCES

6.1 Requirements

None

6.2 References

MSC-PRO-ENG-8259, MSC Calculation Preparation and Issue

MSC-PRO-ENG-709, CAD and Drawing Development and Control Processes for Engineering

Drawings

MSC-RD-ENG-1819, MSC Engineering Requirements

MSC-PRO-ENG-2001, Facility Modification Package Process

MSC-PRO-ENG-8258, Functional Requirements and Design Criteria

MSC-PRO-ENG-16406, Engineering Vendor Information (VI) Process

MSC-PRO-ENG-61164, Infrastructure Systems Health and Status Reports


MSC-PRO-RM-10588, Records Management Processes

MSC-PRO-RM-32281, Electronic Records Management

MSC-RD-RM-8310, Document Control Program.

DMCS User Support – EP Approval Workflow DMCS-HLP-0093



APPENDIX A Engineering Package – User’s Guide

The purpose of these workflows is to simplify current processes for Engineers, Design Authorities, and

Document Control staff and to automate when possible. This workflow will also provide tracking and

improve response time.

WORKFLOW TASK ASSIGNMENTS

All workflow tasks are identified below and include the task number, the person/skill the task is

assigned to, a description and detailed instructions for each task. Task numbers that begin with “T###”

are users assigned tasks, and task numbers that begin with “A###” are system automation tasks.

Creation Workflow:

T0010 – Engineering Package Author: Create New, Revise or Cancel latest approved revision of

the Engineering Package

1. Navigate to the DMCS Workbench and click on Appropriate Contractor Engineering Package

Workflow.

2. Once the Workflow is selected it will launch on the main screen. Click on T0010 and Select

Create New Engineering Package.

3. Once selection is made complete task.

T0020-01: Engineering Package Author: Choose ECR Template

1. Navigate to the Assigned Tasks section of the DMCS Workbench and click on the task T0020.

2. Accept the task and follow the instructions.



3. Choose the ECR template.

4. Add the Title of the Engineering Package and reason for the Change in the boxes provided.

5. Complete your task.

T0030: Engineering Package Author: Field Work


2. Accept task and follow the instructions.

3. If the Engineering Package is to release documents and coversheets need to be created. Please

go to HDNS via this link. Once HDNS step is complete, complete task.

4. If the Engineering Package does NOT require coversheets, complete task.

T0040: Engineering Package Author: Fill in Engineering Package

1. Navigate to the Assigned Tasks section of the DMCS Workbench and select task T0040 and

Accept Task.

2. Fill in the Engineering Package with all applicable information. This information will populate

onto the Final.PDF. If the Engineering Package is releasing a Document, select the Document

Action Only Radio Button, this will grey out fields not required for this action.

DO NOT use Drawing, Radiological Record, or Field Work Complete boxes (they are not active for

this version).

If the change will include drawing changes check the physical modification box. Even if it is just an as

built or paper exercise and NO field modifications are being made by the change.

Similarly, the release to work (yes or no) determination in section 2.0 is applicable only to physical

modifications and is to be checked yes if the document is to be included in a work document for field

work execution. Otherwise it is to be checked NO.



3. Boxes that are greyed out cannot be edited as this step. They will be filled out by the Design

Verifier or the USQ/ECO reviewers at their assigned tasks later in the workflow. EXAMPLE:

for Document Action only the Design Verifier will be greyed out.

4. Assign the Design Verifier at the bottom of box 6.0

5. Assign the USQ/ECO Reviewers in Box 7.0, if USQ or ECO are not necessary check the Not

Required box. IF the USQ is selected NOT REQUIRED the task will be assigned to the Design

Authority for sign off.

6. Assign Approvers in box 8.0. If necessary assign a Derivative Classifier at this task for

approval.



7. Assign Distribution, if necessary select add row to add multiple HIDs.

8. If you can’t see all of the data, you expect to see please try reloading your step.

9. Add any native or PDF files to the Add File icon at the bottom of the screen, under the File

Upload section. NO AutoCAD files can be added.

10. NOTE: You can save your progress on this step by clicking on the “SAVE” button at the

bottom of the page.

11. Complete task.

T0070-01: Engineering Package Author: Add Continuation Files

1. Navigate to the Assigned Tasks section of the DMCS Workbench and select task T0070-01 and

Accept Task.

2. Add any additional files to the Engineering package as needed to the add file icon. NOTE: NO

AutoCAD files can be added.

NOTE: You can only add up to 30 files. If you have more than 30 files, consider combining

some of the separate sheets into one PDF file.

3. If necessary to delete files that have been added, click on the ECR number provided under the

Subject Document to view existing continuation files. Users can hover over the file drawing

icon under Actions and select Delete to remove any unnecessary files.

Please do not click on the fmp.html & attempt to delete, this is a required file.



4. Complete task.

T0070-02: Engineering Package Author: Reorder files for Merge


Accept Task.

2. Reorder the files on the Engineering Package as necessary using the arrows.

3. The first file will be the fmp.html, this file is not moveable.

4. Complete task.

T0090-01: Lead Author QC/Walkdown


Accept Task.

2. Click on the link to the subject Engineering Package and review the FINAL.PDF in the subject

Engineering Package.

3. Leave a comment in the Notes section identifying the CACN for Document Control. This task

can also be used to send the merged PDF out to the Approvers for an initial review.

4. Complete task.

T0090-02: Derivative Classifier Review


Accept Task.



2. Click on the link to the subject Engineering Package and review the.FINAL.PDF in the subject


3. Leave a comment in the Notes section identifying approval of Engineering Package, task to add

the stamp is later in the workflow. If the Document/Drawing is not sensitive add a Note

identifying “No Sensitive Material”.

4. Complete task.

T0090-03: Design Verification


Accept Task.



3. Fill in the Design Verification boxes in section 6.0, users can click on the Save Review Data

tab to save progress at any time.

4. If necessary, leave a comment in the Notes section for the author to Engineering Package

author to review.

5. Answer the workflow control question if the Author needs to revise the Engineering Package

(Yes) or (No). Selecting yes will rework the workflow back to the Author for edits as

requested. DO NOT HIT THE REWORK BUTTON.

6. Complete task.

T0100-01: USQ Review (if necessary)


Accept Task.





3. Enter the USQ information in box 7.0 Reviews. If not required was selected this will be

assigned to the DA for acceptance and completion of the task. The DA’s name and date task

completed will be applied to the PDF.

4. If necessary, leave a comment in the Notes section for the author to review.


(Yes) or (No). If the answer is yes, this will rework the workflow back to the Author for edits

as requested. DO NOT HIT THE REWORK BUTTON.

T0100-02: ECO Review (if necessary)


Accept Task.



3. Enter the ECO information in box 7.0 Reviews and select save review data.





T0110-01: Design Authority Approval Task


Accept Task.









5. If the Engineering Package has been updated by the Author at task T0040 the Design Authority

will select all approvers to review the Package again as there are likely changes to the package

that requires approvers to review again. If the rework came from Document Control and only

minor changes were made the DA can assign just the approver whose review is necessary in the

drop down. Click on the approvers name and hit select item for each approver needing to

review the package again.

6. Complete task.

T0110-02 – T0110-08: Approval Tasks

1. Navigate to the Assigned Tasks section of the DMCS Workbench and select Accept Task.


Engineering Package. Note your approval responsibility role is noted with your workflow task.





T0120: Author Final QC

1. Navigate to the Assigned Task section of the DMCS Workbench and select task T0120 and

Accept Task.




Engineering Package, verify all information is correct.




T0130: Document Control Review Task


Accept Task.



3. Check out the FINAL.PDF in the subject engineering package and add the EP page numbers to

the Package Index. Once completed check the document back into DMCS.

4. Click on the link to Change Request to add the Affected Documents/Drawings listed in Block

2.0 Package Index on the ECR. Save and close.

5. Create the relationship on the Change Package to the Other Affected Documents listed in Block

5.0 on the Engineering Package.

6. Enter all applicable Work Package numbers, Project or Task number, Area, Facility, Building,

System IDs and Responsibilities on the Change Package. Document Control will not need to

enter the Release Dates on the Change Package. Once approved that information will be

automatically applied.

7. Leave a comment if all is approved as Document Control. Issues requiring the Authors

attention also need to be noted here. Choose whether the author needs to revise the engineering

package (Yes) or not (No).

8. Complete task.

T0140: Document Control Final Review


Accept Task.

2. Review the release stamp.



3. If the release stamp placement needs to be correct, delete the stamp and answer the workflow

control question “Yes”, if the stamp placement is correct then answer no.

4. Complete task.

T0150: Derivative Classifier Apply Stamp


Accept Task.



3. Check out the FINAL.PDF in the subject engineering package located under the FILES header

and add the Derivative Classifier stamp to the pdf. Check the file back in and return the

workflow.

4. Complete Task.

Revision Workflow

T0010 – Engineering Package Author: Revise latest approved revision of the Engineering

Package


Workflow.


Revise Engineering Package.




T0020-02 Engineering Package Author: Select Engineering Package


Accept Task

2. Input the Engineering Package to Revise and wait for the green check mark to appear.

3. Complete task.

T0030: Engineering Package Author: Field Work


2. Accept task and follow the instructions.

3. If the Engineering Package is to release documents and coversheets need to be created, please

go to HDNS via this link. Once HDNS step is complete, complete task.

4. If the Engineering Package does NOT require coversheets, complete task.

T0040: Engineering Package Author: Fill in Engineering Package


Accept Task.

2. Edit the Engineering Package (Note: Engineering Packages released using the workflows will

automatically populate the information from the previous revision at this task. Engineering

Packages not released using the workflow will have to have the information re-entered.)

3. Boxes that are greyed out cannot be edited as this step. They will be filled out by the Design

Verifier or the USQ/ECO reviewers at their assigned tasks later in the workflow.

4. Assign the USQ/ECO Reviewers in Box7.0, if USQ or ECO are not necessary check the Not

Required box. IF the USQ is selected NOT REQUIRED the task will be assigned to the Design

Authority for sign off.



5. Assign Approvers in box 8.0. Assign the Derivative Classifier at this task if necessary.

6. Assign Distribution, select add row to add multiple HIDs.

7. If you can’t see all of the data you expect to see, please try reloading your step.

8. Add any native or PDF files to the Add File icon at the bottom of the screen, under the File

Upload section. NO AutoCAD files can be added.

9. NOTE: You can save your progress on this step by clicking on the “SAVE” button at the

bottom of the page.

10. Complete task.

T0070-01: Engineering Package Author: Add Continuation Files


Accept Task.

2. Add any additional files to the Engineering package as needed to the add file icon.

NOTE: NO AutoCAD files can be added.



3. If necessary to delete files that have been added, click on the ECR number provided under the

Subject Document to view existing continuation files. Users can hover over the file drawing

icon under Actions and select Delete to remove any unnecessary files.

Please do not click on the fmp.html & attempt to delete, this is a required file.

4. Complete task.

T0070-02: Engineering Package Author: Reorder files for Merge


Accept Task.

2. Reorder the files on the Engineering Package as necessary using the arrows.



3. The first file will be the fmp.html, this file is not moveable.

4. Complete task.

T0090-01: Lead Author QC/Walkdown


Accept Task.



3. Leave a comment in the Notes section identifying the CACN for Document Control. This task

can also be used to send the merged PDF out to the Approvers for an initial review.

4. Complete task.

T0090-02: Derivative Classifier Review


Accept Task.



3. Leave a comment in the Notes section identifying approval of Engineering Package, task to add

the stamp is later in the workflow. If the Document/Drawing is not sensitive add a Note

identifying “No Sensitive Material”.

4. Complete task.

T0090-03: Design Verification


Accept Task.



3. Fill in the Design Verification boxes in section 6.0 users can click on the Save Review Data tab

to save progress at any time.

4. If necessary, leave a comment in the Notes section for the author to Engineering Package

author to review.






6. Complete task.

T0100-01: USQ Review (if necessary)


Accept Task.


Engineering Package. If Not required was selected this will be assigned to the DA for

acceptance and completion of the task. The DA’s name and date task completed will be applied

to the PDF.

3. Enter the USQ information in box7.0 Reviews.





T0100-02: ECO Review (if necessary)


Accept Task.





3. Enter the information in box 7.0 Reviews.





T0110-01: Design Authority Approval Task


Accept Task.







5. If the Engineering Package has been updated by the Author at task T0040 the Design Authority

will select all approvers to review the Package again as there are likely changes to the package

that requires approvers to review again. If the rework came from Document Control and only

minor changes were made the DA can assign just the approver whose review is necessary in the

drop down. Click on the approvers name and hit select item for each approver needing to

review the package again.

6. Complete task.

T0110-02 – T0110-08: Approver Tasks

1. Navigate to the Assigned Tasks section of the DMCS Workbench and select task T0110-02 –

T0110-08 and Accept Task.





3. When opening the Final.PDF package the approvers will take note of the assigned approver

responsibility.





T0120: Author Final QC


Accept Task.


Engineering Package, verify all information is correct.






Accept Task.





3. Check out the FINAL.PDF in the subject engineering package and add the EP page numbers to

the Package Index. Once completed check the document back into DMCS.

4. Click on the link to Change Request to add the Affected Documents/Drawings listed in Block

2.0 Package Index on the ECR. Save and close.

5. Click on the link to the Change Package to the Affected/Related ECR’s listed in Block 5.0 on

the Engineering Package.

6. Create the relationship on the Change Package to the Other Affected Documents listed in Block

6.0 on the Engineering Package.

7. Enter all applicable Work Package numbers, Project, Area, Facility, Building, System IDs and

Responsibilities on the Change Package. Document Control will not need to enter the Release

Dates on the Change Package. Once approved that information will be automatically applied.

8. Leave a comment if all is approved as Document Control. Issues requiring the Authors

attention also need to be noted here. Choose whether the author needs to revise the engineering

package (Yes) or not (No).

9. Complete task.



Accept Task.




4. Complete task.

T0150: Derivative Classifier Apply Stamp


Accept Task.





3. Check out the FINAL.PDF in the subject engineering package located under the FILES header

and add the Derivative Classifier stamp to the pdf. Check the file back in & return the

workflow.

4. Complete Task.

Cancel Workflow

T0010: Engineering Package Author: Cancel latest approved revision of the Engineering

Package


Workflow.


Cancel Engineering Package.


T0020-02: Engineering Package Author: Select Engineering Package


Accept Task

2. Input the Engineering Package to cancel & wait for the green check mark to appear.

3. Complete task.



T0070-03: Engineering Package Author – Assign Approvers

Navigate to the Assigned Task section of the DMCS Workbench and select task T0070-03 and

Accept Task

Assign Approvers in box 8.0

Complete task.

T0110-01 –T0110-08: Approver Tasks

1. Navigate to the Assigned Tasks section of the DMCS Workbench and select task

T0110-01- T0110-08 and Accept Task.



3. When opening the Final PDF package the approvers will take note of the assigned approver

responsibility.


5. The Engineering Package Author will need to assign himself as an approver and add a note

identifying why the Engineering Package is to be cancelled.

6. Complete Task.



Accept Task.



Complete task.





Accept Task.




4. Complete task.



APPENDIX B Form Instructions

Section 1.0 Package Description

Request and Justification: Provide a summary explanation of the reason for the document or change.

Work Package/Project Number: Enter the work package number if applicable. If one is not

available or it will involve multiple numbers list N/A. Otherwise enter the work package number. The

same guidance applies for the project or task number. Enter the project or task number if there is one

associated with the EP.

Area: Enter the area where the activity is taking place. List multiple areas or put “various” for

multiple area activities. Area choices include 200E, 200W, 1100, 300, etc.

Facility: Enter the applicable facility or N/A. The facility may be N/A if the building is not part of a

larger facility complex. Facilities include PUREX, PFP, REDOX, Tank Farms, etc.

Building: Enter the applicable building or N/A. This is simply the building number.

System ID: Enter the system ID. Ensure that correct name is entered for the system ID. This is a

searchable field.

Change Description and Scope: Provide a summary explanation of the reason for the document or

change and the scope. This should be related to the request and justification above.

2.0 Package Index

In this section enter all documents that are changed as part of the package. It should be just the

document being released (in most cases) for a document action only EP and may be a variety of files in

a physical modification EP. Enter the information requested on the form. The action codes and the

E/S/R meanings are provided below for clarification. The page number column asks the page number

of the document in the total final file. Currently the page numbers have to be entered by Document

Control personnel.

Action Code Description



NWC NWC (New Work Complete) is used for new drawings/documents released

into DMCS when the FMP is Work Complete and Field Verified. All new

drawings shall be identified as NWC. Standalone documents attached to an

FMP can be identified as NWC but are paginated as separate documents. All

NWC documents are identified within the package index section 2.0 of the

EP..

Identifying documents as NWC within the EP allows the document to be

released for work. The initial release of the EP into DMCS allows for

fabrication, construction, and installation of new SSCs as depicted on the

NWC document. The drawing or standalone document itself is not

designated as approved in DMCS until the EP is Work Complete and Field

Verified. Email the native file to Document Control for future retrieval.

New drawings created by a “Project” are issued using the DCN process. At

completion of the project the drawings are released to operations by the

FMP/EP processes.

RWC RWC (Revise Work Complete) documents are existing released documents

which have been altered to support the EP, but will not be revised until the

EP is Work Complete and Field Verified and accompanied by the

appropriate documentation. All existing essential and support drawings

altered to support the EP/Change, including “as-found” drawing

modifications, shall be identified as RWC. Standalone documents can be

identified as RWC but are paginated as separate documents. All RWC

documents are identified within the EP.

Identifying documents as RWC within the EP allows the document to be

released for work. If the document exists in digital format it may be provided

to the release station at the time of EP release for storage and later retrieval

(as with NWC documents). The initial release of the EP into DMCS allows

for fabrication, construction, and installation of new SSCs as depicted on the

RWC document. However, the drawing or standalone document itself is not

revised and released into DMCS until the EP is Work Complete and Field

Verified.

N N (New) documents can be released as part of an FMP as long as there is

drawing or another change that the document can be associated with. When

released, N documents are appended to the FMP as a section, but are

paginated separately from the FMP. All N documents are identified within

the FMP by FMP Section and Title.

N Document can be released as a document action only.



R R (Revised) documents are standalone documents released separately from

the FMP. When revised, R documents are attached to the FMP as a section,

but are paginated separately from the FMP. All R documents are identified

within the FMP.

R documents can be released as a document action only.

I I (Information) is information included to support an EP/Change.

Documentation not entered into DMCS is categorized as “I”. This is

information relevant to the overall modification which does not require

separate tracking (e.g., permits, USQ Screening forms, catalog data, excerpts

from reference materials). All I documents are identified within the EP.

C C (Cancellation) identifies a previously approved Change Document which

is to be cancelled.

S S (Supersede) provides for supersede of a previously released document.

Supersede EPs replace the previous FMP revision in its entirety but maintain

the relations to the related documents.

RTV Void – This code is used to void a drawing. The drawing will be revised and

stamped as “VOID”. It remains in the system for historical purposes. Any

drawing that is to be voided must be updated to incorporate any outstanding

changes as part of the voiding process. This code is used only for drawings

being revised by the drafters.

RTV-A Administrative Void – This code is used to void multiple drawings and has

the task performed by document control personnel. The drawing will be

revised and stamped as “VOID” by making changes to the record file. The

CAD file will not be updated. It remains in the system for historical

purposes. Any drawing that is to be voided must be updated to incorporate

any outstanding changes as part of the voiding process.

Drawing Designations:

E = essential

S = support

R = reference.

3.0 Design Requirements

This section will be greyed out and cannot be filled in if the EP is a document action only. Otherwise,

enter the relevant design information. For a simple design this document and the descriptions will

provide function(s) for the system/equipment, the applicable requirements to the design and the design

criteria. Please see MSC-PRO-ENG-8258 for more guidance on relevant functional requirements and



design criteria information to be included here. Use the graded approach, and if the relevant design

information needs more documentation that can be provided in this form generate a separate functional

requirements and design criteria document in accordance with that procedure.

4.0 Acceptance Criteria and Methods

Identify the techniques and relevant documents that are being applied to the acceptance of the

completed field work.

5.0 Other Affected Documents

In this section list all the other documents that may be affected by the proposed change. Enter the

document type, document revision number, the owning organization and the technical authority for the

documents listed.

6.0 Design Verification

If the document is a physical modification and requires a design verification, then determine if the

design verification will be done with a separate document (See MSC-PRO-ENG-8336). If it is, then

list the additional design verification documents in section 2.0 of the EP and check the box (after h).

Otherwise enter the information requested in each section and add any supporting information.

7.0 Reviews

In completing the EP flow, identify if there is a required USQ or ECO for the release of the document.

For documents that impact ONLY MSA facilities a USQ is rare. If these reviews are required, then

add the reviewers name and the document will be sent to them for their review and approval.

Otherwise select the not required box.

If a USQ review is left with No name selected it will be routed to the DA for final USQ determination.

8.0 Approvals and Distribution

Enter the information for approvers and for people to receive the document as part of the distribution

as requested in the EP process. People that are listed as approvers are not automatically added to the

distribution list and will need to be entered for distribution as well.



APPENDIX C Document Numbers

HNF-CALC-XXXXX: This document number is to be used for MSA Engineering Calculation

documents. These documents are developed in accordance with MSC-PRO-ENG-8259, MSC

Calculation Preparation and Issue.

HNF-SPEC-XXXXX: This document number is to be used for MSA Specifications.

HNF-PLAN-XXXXX: This document number is for any document that is a plan, such as

acquisition plans, assessment plans, maintenance plans or program/project execution plan, etc.

HNF-RPT-XXXXX: This document number is for non-engineering reports, HNF-ENG will be

used for MSA engineering.

HNF-FRDC-XXXXX: This document number is to be used for Functional Requirements and

Design Criteria. These documents are developed in accordance with MSC-PRO-ENG-8258.

HNF-ENG-XXXXX: This document number will be used for engineering reports/studies.



APPENDIX D Email Approval for EP

At this time, the EP software limits the signatures on an EP to 8 persons. This is being

addressed in the next revision. However, there is a process that allows for the approval of an

EP with more than 8 persons. This process is also the preferred process for the approval if

persons that are not comfortable with computer use are asked to approve the EP. This allows

people to review and approve the EPs with only use of site email. All approvers other than the

Author, the DA and the Engineering Manager can sign via the email process. The minimal

signatures in the EP process are used to release the document with the remaining email

approvals.

At Task T0040, Engineering Package Author: Fill in Engineering Package, ensure that the

Author, DA and Engineering Manager are identified in the EP process for electronic approval.

Then to obtain the other signatures using an email process, generate an email to send the

package. It is recommended that the author print the file and the ECR at Task T0090-01, Lead

Author QC/Field Walkdown. The easiest way to is print the file as a .pdf (save as a .pdf) then

the .pdf with the changes and the ECR data can be sent in the email for review and

concurrence.

With the file saved as a .pdf attach the file to the email and ensure that the email includes the

Document Number including the revision, the ECR number and that you have selected the

option for a “voting button” approval. Send the file and save the “sent file” in your email. The

sent file will allow you a single file to print showing all approvals.

When all approvals are received, then save the approval page as a .pdf and include it as the first

page after the ECR. The required signatures for release by the email approval process are the

originator/author, DA and the Engineering Manager. Identify these persons on the EP for

completion and attached the file and complete per the EP process as described in section 4.

MSC-PRO-ENG-440 - Hanford Site...2018/12/05 · Rev. 3 MSC -PRO ENG 440 Page 2 of 45 MSC...

Documents

Transcript of MSC-PRO-ENG-440 - Hanford Site...2018/12/05 · Rev. 3 MSC -PRO ENG 440 Page 2 of 45 MSC...