Designing reviews stages wuestion
Designing reviews stages wuestion
(OP)
Hello,
Some capital projects asks for design reviews in 30%, 60%, 90&, 100% while others asks for 50% and 100% only.
what is the difference and when we follow option 1 and when is 2?
thank you
Some capital projects asks for design reviews in 30%, 60%, 90&, 100% while others asks for 50% and 100% only.
what is the difference and when we follow option 1 and when is 2?
thank you





RE: Designing reviews stages wuestion
RE: Designing reviews stages wuestion
With each design progress submittal, it is a good idea to include a letter containing the following information: description of the anticipated construction scope of work (written in a simple way so all of the stakeholders can understand); list of drawings number and titles, list of specification sections, discussion of any critical issues, and notes and questions for specific reviewers. In other words, make it as easy as possible for stakeholders to weigh in, and make sure to document the review, comments and resolution in your files.
RE: Designing reviews stages wuestion
> System Requirements Review (SRR) to verify that the customer and contractor are on the same page w.r.t. interpretation of requirements and functionality
> Preliminary Design Review (PDR) to review the preliminary design -- presentation of a design that's compliant to all requirements, prior to detailed design
> Critical Design Review (CDR) to review to the completed design prior to fabrication
> Test Readiness Review (TRR) to review status of hardware prior to actual acceptance testing -- this would be most likely equivalent to something that done prior to building inspection
TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! https://www.youtube.com/watch?v=BKorP55Aqvg
FAQ731-376: Eng-Tips.com Forum Policies forum1529: Translation Assistance for Engineers Entire Forum list http://www.eng-tips.com/forumlist.cfm
RE: Designing reviews stages wuestion
Dave
Thaidavid
RE: Designing reviews stages wuestion
Have you actually SEEN a company successfully follow the Systems Engineering approach?
My current experience is that the customer's engineers write the SRR in isolation, and only managers go to the PDR.
When the CDR is presented, half the people in the room are totally gobsmacked, and the other half start re-writing the SRR to mean what they really wanted.
I was once on a project where the engineering kick-off happened with the SRR at revision "C". By the time testing began 3 years later, the SRR was at revision "K".
Griping aside,
I don't believe that Systems Engineering is inherently bad. It just relies on everyone paying very close attention to the details and communicating with each other before commitments are made. When people shrug because they don't know what they want, and write something vague, trouble is soon to come!
STF