Design drawing review bijoy

Bijoy Kumar Roy – Malda West Bengal India

Design Drawing - Reviews

Presentation No- PDR -01

1

Prepared by : Bijoy Kumar Roy


Fix the Rules please Mobile phone in silence

No smoking

Respect time schedule

Open, frank and fruitful discussions in a polite manner

No peer-to-peer discussions while one is talking

Differences in opinions will not be taken personally

2


Fix the Rules please

Introduction

Review Process

Review objectives

Formal design reviews

(FDRs) Involved

Formal Design Reviews

Preparations for the Design Review

Drawing Initiation & Preparation

Agenda

Participation in the Review

The Design Review Session

The Design Review Report

Follow up Process

Oftentimes Problems

Problems in Construction Drawings

Drawing Quality reviewed

Guidelines for Design review

Question?


Introduction The design document is the key of a project.

Important to check repeatedly in the process.

To get IFC stamp approval on the drawing typically, reviewed many times

Appoint other reviewers. Unfortunately, we often don’t find our own errors.

Different stakeholders with different viewpoints are used in the review process.


Review Process Review / verification level process should be mentioned in the approved Project

Management Plan.

A review process is : “a process or meeting during which a work product or set of work

products is presented to project stockholder, personnel, managers, users, customers, or

other interested parties for comment or approval.” (IEEE)

Essential to detect / correct errors in these earlier work products because the cost of errors

downstream is very expensive!!

Review Process Summary

Notification

Schedule Time Review Documents

Comments Letter

Review Meeting

Comments Response


Review Process (2)

Review Choices:

- Formal Design Reviews (FDR)

- Peer reviews (inspections and walkthroughs)

Used especially in design and coding phase


A. Direct objectives – Deal with the current project

Detect analysis and design errors as well as subjects where corrections, changes and completions are required

Identify new risks likely to affect the project.

Find deviations from templates, style procedures and conventions.

Approve analysis or design product. Approval allows the team (Together, Everyone, Achieves, More) to continue on to the next improvement phase.

Review complete within the stipulated 05 working days duration

B. Indirect objectives – are more general in nature.To provide an informal meeting place for exchange of professional knowledge about methods, tools and techniques.

To record analysis and design errors that will serve as a basis for future corrective actions. (very important)

Review Objectives


B. Indirect objectives – are more general in nature. Many different kinds of reviews that apply to different objectives.

Reviews are not randomly thrown together.

Well-planned and orchestrated.

Objectives, roles, actions, participation, …. Very involved tasks.

Participants are expected to contribute in their area of expertise.

Idea behind reviews is to discover problems NOT to fix them/

Typically fixed after review and ‘offline’ so to speak.

Very common to review design documents.

Thus they are usually well-prepared initially prior to review.

Review Objectives (2)


Software Requirement Specification Review(SRSR) Detailed Design Review (DDR) Data Base Design Review (DDR) Test Plan Review (TPR) Software Test Procedure Review (STPR) Version Description Review (VDR) Operator Manual Review (OMR) Support Manual Review (SMR) Test Readiness Review (TRR) Product Release Review (PRR) Installation Plan Review (IPR) Development Plan Review (DPR) Preliminary Design Review (PDR)

Important to note that a design review can take place any time an analysis or design document is produced, regardless whether that document is a requirement specification or an installation document.

Formal Design Reviews Involved


Formal Design ReviewsPersonal experience in:

Operators’ Manual Users’ Manual

Program Maintenance Manual Staff Users Manual

Installation / Conversion Plan Test Plan(s)

Depend on size of project!


Preparations for the Design Review Participants in the review include the

– Review leader, – Review team, and – Development team.

Review Leader: – appoint team members; – establishes schedule, – distribute design documents, and more

Review Team preparation: – review document; list comments PRIOR to review session. – For large design docs, leader may assign parts to individuals; – Complete a checklist

Development Team preparations: – Prepare a short presentation of the document. – Focus on main issues rather than describing the process. – This assumes review team has read document and is familiar with project’s outlines.


Drawing Initiation & PreparationDrawing Initiation and Preparation

Designer (Drawing Originator)

Draughter (person producing the drawing and well known of the CAD

Standards and Manuals)

If appropriate produce a approved Project CAD Plan Table

Use Drawing Issue Register or similar

Follow designer’s instructions and refer standards , regulations or

similar legislation as require.

Self check against a Drawing Checklist or similar and discuss with

Designer during preparation before handover to others.


Participation in the ReviewDrawing / Report Checking (Use Drawing/Report Checklist) levels based on Drawing / Report

complexity

– Carry out and record checking with Management/Verification Plan

– Verified relevant calculations, standards, risks & equivalent legislation information

– Review Committee Decided Final Approver

Checking Level 1 – Design

– If satisfied add initials Checker and Approved by Approver (Designer)

Checking Level 2 – Drawing Review

If satisfied add initials of Checker and Checked,

Arrange for any amendments to the Drawing by Designer

If satisfied the amendment add initials by Checker

Pass it to the approver


Participants in the Review (2) Checking Level 3- Detailed Check

If satisfied add initials Checked,



Pass it to the approver

Checking Level 4 - External Check

If satisfied add initials Checked,



Pass it to the approver for internal organization

When complete send to the external Checker. Consider discuss and resolve queries. If

revision is necessary.


Participants in the Review (3)

Checking Level 5 – As defined in the Management Plan

Carry out the required verification process if define extra checking

Approval

- Final review is complete when satisfied of each drawing.

Note: Record and check prints and/or CAD record versions in project records.

Remove obsolete drawings from use and clearly mark "SUPERSEDED", or

otherwise


Participants in the Review (4) Review Leader – Design Engineering Consultant

Needs to be external to the project team.

Must have knowledge and experience in development of the

review type

Seniority at least as high as the project leader.

Good relationship with project leader and team

Generally, this person really needs to know the project’s material

and should NOT be the project leader –Would impact objectivity!

Would miss things entirely!


Participants in the Review (5)Review Team

Needs to be from senior members of the team with other senior

members from other departments (Architectural, Civil,

Electrical, Mechanical, IT Security etc.).

Why?

Escalation?

Team size should be 3-5 members.

Too large, and we have too much coordination.

This is a time for serious business – not lollygagging!


The Design Review Session Review Leader is key person for sure!

Start with short presentation (development team)

Comments by members (review team)

Comments discussed to determine required actions team must perform(review and development teams)

Decisions regarding design product – tells project’s progress. Full approval Code “A” - Continue on to next phase (may have minor corrections)

Partial approval Code “B”- Revised and Resubmit)

• Continue to next phase for some parts of project; major action items needed for remainder of project.

• Continuation of these parts granted only after satisfactory completion of action items

– Granted by review team member assigned to review completed actions or by the full review team or special

review team or by some other forum

Rejection of Approval Code “C” – demands a repeat of Design Review

• Project has major defects, critical defects

Rejection Code “D”


The Design Review Report Review Leader’s primary responsibility following the review.

Important to perform corrections early and minimize delays to

project schedule.

Report contains:

Summary of review discussions

Decision about project continuation

Full list of action items – corrections, changes, additions the project team

must perform. For each item, anticipated completion date and responsible

person is listed.

Name of review team member assigned for follow up.


Follow up Process

The ‘follow-up person’ may be the review team leader him/herself

Required to verify each action item fixed as condition for allowing project to continue to next phase.

Follow up must be fully documented to enable clarification of the corrections in the future, if any.


Oftentimes ProblemsSometimes entire parts of DR are often worthless due to – Inadequately prepared review team, or – Intentional evasion of a thorough review.

Tipoff:– Very short report – limited to documented approval of the

design and listing few, if any, defects

– Short report approving continuation to next project phase in full - listing several minor defects but no action items.

– A report listing several action items of varied severity but no indication of follow-up (no correction schedule, no documented activities, …)


Problems in Construction Drawings

Drg. Rev.

number on Drg.

Request For Inspection (RFI) submittal are not mention Rev. #

Bijoy’s review was noted that the drawing should be IFC stamps, but not happen before start of construction.

No drawing revision

number


Problems in Construction Drawings (2)

Code “B” –Revised & Resubmit comments was not incorporated in the final Drg. before the commencement of work at site.

Drawings are with yellow text which are not readable properly

All Drawings in a folder are same numbers and same drawing title.


Drawing Quality reviewed

Drawing index and Drawing title are not same

Drawings are not available according to the drawing index

Standard project approved template are not used

Notes are copy paste from others drawing and are related

with the specific drawings


Varies in Drawing Template

Varies in drawing numbering system

Some drawing have physical signature some are not.

Examples; ERP 93103 and 45899, 102172

Drawing Quality reviewed (2)


1. Design Review Infrastructure Develop checklists for common types of design documents.

Train senior professionals to serve as a reservoir for Design Review Teams (Together, Everyone, Achieves, More).

Periodically analyze past Design Review effectiveness.

Schedule the Design Reviews as part of the project plan.

Guidelines for Design review

2. The Design Review TeamReview teams size should be limited, with 3–5 members being the optimum.


3. The Design Review Session

Discuss professional issues in a constructive way refraining from personalizing

the issues. Keep to the review agenda. Focus on detection of defects by verifying and validating the participants'

comments. Refrain from discussing possible solutions.

If disagreement about an error - end the debate by noting the issue and shifting

its discussion to another forum. Properly document discussed comments, and the results of their verification

and validation. Review session should not exceed two hours.

Guidelines for Design review (2)


4. Post-Review ActivitiesSome example Prepare the review report, including the action items Establish follow-up to ensure the satisfactory performance of all

the list of action items Test font size and font are different in the same drawing Drawing dimensions are not very clear Etc.

Guidelines for Design review (3)

Bijoy Kumar Roy – Malda West Bengal India 29

THANK YOU

For any Query, contract QA/QC Department – For any Query, contract QA/QC Department – QA/QC Manager QA/QC Manager


Feedback Please