Planners withoutreading any Key Engineering drawings

Here we call them "keyboard jockeys", we go a step further meaning there is no mentality at all.

I do not know of a single contractor that delegate management and planning to the unqualified, on the other hand, my other hand is not enought to finish the count of the many A/E firms that provide cheap CM Services using the most unqualified personnel, perhaps because they play PM not at Risk, with PM at Risk you differentiate the kids from the grown ups.

Regards,

Rafael

As a new member of this forum I am wondering why it upsets you all so much that some "planners" cannot read single line electrical diagrams, P&IDs or Full Technical drawings with cherries on top! Surely this is a forum where "planners" of all experience and backgrounds can come to get guidance and help when it's needed! The sounds coming from some people on here are elitist at best. . . We are all out in the workplace to try and get on and make a mark. I am happy to share my expertise with anyone that needs it and have been helped, in turn, by many, many planners / colleagues in my time as a planner. Anyone who doesn't feel that they want to do that or who feel that just because some "planners" didn't take the time to do course after course after course should maybe leave this site and join www.Ifeelharddoneby.com :-) 

Hi Carmen,

Sorry for resurrecting this piece of discussion once again, I am kinda idle nowadays and just browsing over the discussions here and I find them all interesting. The forum is really a great way to share and learn at the same time.

Generally, i agree with all the comments here (this thread), however, there is one thing that is missing though and it is the most important thing, the philosphy and methodology behind the tender.

Basically, a project is awarded to a contractor based on their technical and commercial proposal and as a Planner who just got on board, the first thing you need to know is your winning philosphy and methodology. This includes your tender programme, resources and proposed production rates, methodologies, execution plan, etc. These documents should largely dictate on how you plan to build the project and how you will develop the programme. Of course you also need to double check the data behind the proposal (tender) against the awarded contract, most of the times there are changes.

Best regards,

Daniel

I dont know why we are calling P3 or P5 planners as planners if they dont know about specs, BOQ and contract drawings.

The first stage of project management is Scope Management and that has nothing to do with Primavera, its all about engineering skills and not computer skills.

Remember

"A Planner who cant read the drawings and BOQ in full detail is nothing but just a Primavera Software Operator"

Take Care

Muhammad Jawad

first of all, you should read and understand the Contract; study the Scope of Works (Baseline Programs must cover the full Scope of Works as per Contract); have a copy of the Bill of Quantities (BOQ); study the quantities and costs; review the drawings from time to time; create your time schedule as per your company standards based on your resources-productivity rates; make recommendations to upgrade available resources if practical and necessary; take a break and have coffee...

Carmen,



The MOM of the pre-bid meeting also needs to be added in the list...



J

HI...



In my opinion, planner should read all the docs related to the project...Wud be better, if he had completed this exercise before starting the detailed construction programme..without reading the things, how one can consider/think and add those things in the programm...This detailed exercise/homework during the start of project will make his life easy during the execution...



Further, the lack of information provided to the planning from the site may affect the planner during the time of updating/tracking only....



regards

J

To create an effective plan, a thorough comprehension of the objectives is necessary, this implies that the planner must take time out to study all documentation/communication pertinent to the task at hand.



Any other way results in a schedule fraught with risks

Carmen,



Of course it is very important to understand how is roughtly working the Unit, each scheduler has to made his own experiment and his own data base and thus must go through project documentation. Firthermore, I agree with James, I found so many PM that asked you "why do you need it", but I resign myself now to fight on each project to get information.



Well, Carmen what you propose are as you said basic document that shall be handled and understood by all schedulers. I would add equipment list, UG drawings (piping/CW) for engineering.



For Project, we must have a copy of the contract where are clearly written Scope of Work, milestones, progress measurement,......In addition to this contract, we should get manhours to be spent for Engineering, Procurement and Construction in order to look for productivty and any deviation that should come to Claim may be.



For Procurement we must know strategy that will be choosen with the number of requisitions to be placed.



For construction schedule, we should receive during the Engineering phase all MTO for piping, electrical, instrumentation, CW,...We apply ratio on these quantities and we can estimate manhours. These have to be compared to initial estimation from the begining of the project. At the begining of project, I personnaly made a table where I write main operation and quantities needed to estimate mhrs.

I prefer to fly blind. More exciting that way



Seriously though, imo you are on the money. I read everything about the job I can get my hands on, particularly interesting contractors and subcontractors’ special conditions of contract.



I have worked with several "bring me the info" type of planners. Give them a shovel and tell them to go dig.



Of course, equally frustrating are PM / day controllers who fail to provide the information when it’s requested (the "why do you need to know" type of managers and engineers). That’s another story though.