Interesting quote heard the other day…
“We didn’t have URS documents 10 years ago…what did we used to do?…”
Specifications and other documents were prepared based on meeting with users and discussing their requirments with them…most of this got documented, hopefully, somewhere, somehow…requirments not discussed got determined by engineering judgement, copied from the last job, or even just made up…
Eventually, specs got approved, stuff got purchased, installed, commissioned, and then came the validation effort…probably by another group
What to validate?
The search was on…check the specs, check the meeting minutes, check the drawings, check what you validated on the last project…who knows for sure?…forget it, validate everything…
Budget? what Budget?…Schedule? what Schedule?…this is validation, you can’t ask me to justify what I’m doing, just sit there and pay for everything, and we’ll let you know when we finish
Bright Idea…
We should gather all of the requirements we want to validate in one document instead of not documenting them at all, or having them scattered in multiple documents all over the place…
The birth of the URS…
Design Verification…
Validation focuses on what’s critical…
Quality gets designed in…
Now we just need to start working like we understand how this whole thing is supposed to work…