Personality=Job=Personality
Forum Sponsor
Top Posters
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts
I think weve missed the 3rd type of Planner, somewhere in the mix, neither Engineer or software monkey, youve got the lateral thinkers.
Dont necessarily have to have an Engineering Background (as long as they get up off their backsides, to ask the pertinent questions, and can pick up the principles of the job that they work on), and they dont neccessarily have to spend all of their time hiding behind copies of PC Weekly or Readers Motherboards (as long as they can run the software to a reasonably competent level).
What the lateral thinkers do is problem solve, they ask questions, and they offer (laymans) solutions. These solutions are occasionally wide of the make, but often the most pragmatic, if a little prosaic, way around the problems.
The Lateral thinker is a product of Nature and Early Years (youth) nurture. Numerate and literate, if a little prone to disappearing off on a tangent at first sight of an interesting problem ;o) .
Note: It is possible for either subset of Engineer or Software Jockey to be a Lateral thinker.
As for the definition of an Operator:
A person who, while claiming that a solution is neither their job nor problem, will quite happily tell you why something wont work, couldnt possibly be manned safely, and that they know a great way to solve the problem, but how nobody listens. All this is said through a Big Mac behind a copy of the Sun. (Theyre also quite probably scratching their @rse at the same time)
Mr Randall,
Thanks for the big laugh.
I look forward to your definition of an Operator.
seeems to have summed it up bad day or not
Clive,
Are you having a: "I-hate-the-world" moment?
Dave, my Dearest Little Peanut (For calling you that, will I get a roasting, or will I be as-salted [groan])?
Id have resigned by now, having to wait that long to download the stuff. Mind you, it gives you plenty of time to continue your on-line gambling career. Won any rubber-ducks lately?
Smooches galore.
Jamie.
James
By the way Im only here because Ive been waiting 2 hrs (no exageration) for P3e to download through Citrix to MSP.
More luv & kisses
Dave
ps its just crashed.
Hi James
We are nuts, as you know. I became a planner because nothing else would have me and I have to pay the mortgage.
Luv & kisses
Dave
Vishwas,
Beautiful words, most poetically scribed. Thank you for such inspiration. I now have new meaning to my life and work. I always thought that "the other side" were just envious of our profession. I shall now drive forward the Vision, the Mission: "WERE A BUNCH of KNOW-ALLs, nah, nah, nah-nah, nah!!"
Sleep well my Dear Planners, for we are custodians of "The Plan For All Eternity & Infinite Wisdom.
Hi James,
Sorry James and all guys (not gays),Its my mistake.
I was a civil engineer before I became a planner.
At that time I am working on a power plant project.
when we start MEP installation, we found that we need more planner to monitor/control the project.
So my boss asked me if I can try to be a planner.
Thats why i became a planner, and I like this job
Hi Nigel,
This is in response to your original post (I have overlooked the in-between posts for "All of Plannings sake"!)
Yes, we as Planners are UNIQUE!! The question now is - As PLANNERS do we become UNIQUE (or) do we become PLANNERS because we are UNIQUE??
Well, the answer is BOTH!
The Planning Profession is a class on its own. We stand apart from the rest of the CROWD, irrespective of our back-grounds - Engineering or Software-types. This is very similar to Doctors who stand apart in the professional society. (It is high time we start prefixing our names with "Pl." just like doctors prefix "Dr." against their names!!)
So, what makes us Planners, and, what makes us Unique?? Each one of us has an element of eccentricity that differentiates us from the rest. We have the Answers for any kind of Question; we have the Solutions for any kind of Problem. We understand the entire project even before it starts. We have the unique sense to imagine the entire course of the project (both time-wise and cost-wise) at the very beginning. We initiate, plan, execute, control things in an organization. We frame the back-bone of any organization or project. And, we are always in the lime-light – good or bad. Even though we DON’T do anything, we GET THINGS DONE, and, in our own, sweet way!
No doubt, ours is a coveted profession. Most of the others (who are not planners) are jealous of this role. They yearn to become “US” unsuccessfully most of the time. And, it is human tendency to conclude that “the grapes on the other side are sour”. :)
Definitely, it is eccentricity, our tolerant nature (the ability accept flak from all sides) and good political skills which makes us UNIQUE and PLANNERS (technical prowess and software skills makes us better planners, that’s all). In the language of the hoi polloi, we are PLANNERS because we have BALLS (that could be either Nature or Nurture)!!
Happy Planning!
Vishwas
Hi Zhang,
Good one! But why did you become a planner?
James.
PS. In your posting, you called us all "gays". This is men-who-like-men. I presume that that you meant "guys" (we forgive you, dearie, kiss, kiss!) :-)
hello gays,
nowadays project become more and more complex. The work for planner is also changing from technical based to management based.
Ive been work on a project with 400 MEP systems,also a lot of different kind of civil work (under water structure, rock blast/exvavation, piling,concrete/steel structur ...). these s no such kink of planner knows all these things. Do we need hundred of planners for the project?
So what can planner do?
A planner need to establish a system to organize all engineers to be involved in preparing / tracking of schedule.
A planner need to prepare work procedures, standard form, method of updating, coding structure... for the project
A planner need to even write code/programe to analize schedule/generate reports/update schedule...
A planner should have clear understanding of schedule method (CPM)and the process of time control(scheduling) , also good at using those softwares. (there are lots of planners do not know how to calculate LS,LF,TF,FF...)
Now a planner do not need to know a lot of technical knowledge if there is a good system. Now a planner is becoming a software jockey.
Well, Its just that, I mean we are exceptional! We are not just a termed "planner"...huh
James
Short answer is Yes, we are nuts!
I believe it takes a certain type of person to become a planner - which is why I post the topic in the first place.
From the comments so far, a large can of large worms has been opened.
Lets face it, there is a role for the software-jockey type of planner and the engineering background type of planner - and probably everything in between.
I reckon that the older planners probably have more of an engineering background and the younger planners more of a software background. BIG generalisations maybe.
Next time I will ask a less controversial question! (not!!!)
Cheers
Nige
Ronald,
I think you have opened a can of worms.
Why have we become planners? If you think we should have so much engineering experience, why then would we become a planner? Engineers tend to like engineering. Moreover, most "engineers", that I know, absolutely loathe any mention of the word "planning". What is it that resides in our character and draws us to such a bang-head-against-brick-wall occupation?
Are we all completely nuts?
James.
Dear Fellow:
Perhaps we need to distinguish this two terms. In my point of view:
Software jockey-probably is a guy who only has a software training, we called it a software user. He knows the software very well and can do the encoding, incorporating, editing wherein the data comes from his supervisor or whoever he report to.
Sometimes in the technical side a junior engineer with knowledge on how to use or operate the said software. He is still gathering or beginning to gather experiences in the actual world of engineering and construction. Surely he is well verse with the software application but still he depended on whats his boss instruction and input.
Now for the Planner...what do you think huh? A planner is not just a title or position per se....to become a planner you will undergo tedious training and must possess lots of experiences in different field of engineering. You need to have experiences in actual constructions, you need to have an experienced of being a field engineer, the project engineer, became a project superintendent and so on so forth. You need to experienced also of being a design engineer and lastly worked under the client representatives as member of his project or construction management team. Then you must have a technical knowledge in using the software.....a tool to minimize time so that you can still do some of your professional chores...
Meaning a planner is a seasoned professional engineer a diversified engineer, can work, can recommend solution, can plan, can forsee what lies ahead, can estimate, can evaluate, can analize, what else....it just a planner ...I am a planner...I reached this stage by time...by experiences and not by accident....I think you know what I mean....
Ronald Quilao
You lucky git. I just kept getting sacked for telling them what they dont want to know, then they blame me for not telling them!
Anyway, all said & done. I must take my medication: calm, calm.
James. :-)
James
Dont get me wrong, I agree with a lot of what you said. Especially the ideal mix of knowledge. There is, however, a fundamental difference between the software jockey and the engineer - and feel free to correct me.
The software jockey, generally, is au fait with the software but not necessarily, with the engineering (by that I mean the whole process, CDM/EPC etc). True, not all SJs are like that but the majority are, in my experience.
The engineer, on the other-hand, usually has a command of the process and the steps needed to implement that process. True, he knows doodly-squat about software and that is where the jockey comes in.
BIG generalisations I know. Who is "better"? Neither. Just different. In any event most companies now require a proper programme that has to be established between all parties - the "good old days", which I well remember, are long gone, where the engineer thought the programme was a few pretty coloured bars and to be done once and once only.
Apart from a very few older engineers/managers/etc, most people recognise the rationale behind a working, linked programme. Especially when one can demonstrate the savings that can be made, in time and or cost.
My first ever job was as a mechanical engineer at a steelworks in Sheffield - long gone and all but forgotten. I entered the planning world due to (good?) luck. I noticed that the guys in the rolling mills were changing the dies as per the production sheet, with no thought about the next but one size required. (4" then to 6" then back to 4" all taking time)
Having pointed this out, it was met with dis-interest. Until I mentioned that it would be quicker, therefore more productive and therfore a better bonus. That was it. Soon the director got involved and asked that I do a plan for the whole site. Then other directors (26 companies in the group) noticed our productivity and off I went.
That was back in the good old days - Elephant sized drawing board (Elephant used to be an imperial paper size, similar to A0), pencil and BIG rubber (eraser). No computers - think wages might have had an adding machine but that was it.
So some of us never were software jockeys, but knew the process. Yes, I now use software - as a tool. If my computer packs up - or there is no power available in a little Indian village, out in the wilds of no-where - then I can still do it the old fashioned way - forward pass, backward pass, float calcs, process maps, etc.
May be we should all throw away the computers and do it the "real" way. Would we be better planners/progammers/schedulers? Spect so. Would it be a better way of doing thing? Maybe not. But remember some of us Old G*ts never had a computer originally and still managed so where would the software jockeys be then? Probably not even born yet.
What does the industry now need? A mix of engineers with software knowledge, a willingness to learn, enthusiasm and the ability to ask questions, not feel foolish and to stick their hands up and say "I dont know..."
Rant and rave over.
Nigel,
Sorry to have to disagree with you but, in todays world, the "fag-packet" planning man will seriously stuff-up your project. Ive had many a situation where the fag-packet man has drawn it up by hand, and it looked appalling, had illogical logic etc. Being as nice as I could (which really is very nice)explained all the advantages blah blah, I input the data and asked him in which format he would like to see the programme. He just wasnt interested. He, but not only he, seems to think that a programme is a one-off, one-shot, never-to-be-seen-again single sheet of A4. There seems to be an abject failure, on the part of some PMs/Directors, to understand that "work", on a programme, is representative of physical objectives, and that theyd better take note of the fact that, if they want this work is to be accomplished, it is not matter of wishful thinking, but a hard reality that they need X number of people.
Mentioning Brunel, Edison etc. is a red herring, owing to the fact that all we see is the end-result, not the process or the data that comprised the project as a whole. I understand, however, that Brunel had a reputation for going seriously over-budget. He might have been a very good engineer and an extremely persuasive businessman, but was he ever able to forecast how long and how much with any level of accuracy? Itd be extremely interesting, though, to see whether he actually had any real planning process.
Ultimately, youre all correct in that there is an optimum combination of planning theory, software competence and practical experience that will make-up the ideal candidate. How often you get that in a person will be down to each individuals experience.
Feel free to discuss.
Cheers.
James.
Chris,
Please forgive me, I dont mean to deliberately set traps or cause anyone to feel offended. In my No.6 post, it was a back-door process to elicit your thoughts by which you would choose one candidate over another, when each candidate possesses only half of the ideal knowledge or experience.
Speaking from experience when attending interviews, as an interviewee, Ive had too many interviewers saying that they "dont want a software jockey". This really infuriates me, not because Im a software jockey, but because it takes equally as long, if not longer to become very competent with the software than it does to learn the principles of planning. This has manifest itself when PMs take on the role of planner, just to cut costs, yet they have absolutely minimal experience of driving the software. This results in a programme in which they rapidly lose confidence because it doesnt align with their expectations, or cannot discover why it doesnt; thus resulting in further erosion of planning as a role that is perceived as adding-value.
In addition to the above, I have to forecast the consequences of a PM who employs a Designer who actually cannot drive the CAD system, albeit the fact that he may be an engineer with many years experience. Its a fundamental fact that you will then need two people to achieve the same objective, thus probably incurring nigh-on twice the cost; yet they fail to see this until its too late.
Im sorry Chris, Im just having a right-ole whinge! Too many times Ive used the programme to raise some really serious issues....and they just dont believe me, even though Ive always been able to substantiate it via the programme data. Unfortunately PMs just dont want to listen....and when it all falls-down around their ears, who do they blame......the programmer. It doesnt exactly help when we have a Director whom expounds the virtues of using paper, yet always insists on knowing what the real situation is, yet doesnt want to spend any money on "planners".
Perhaps Im either in the wrong job or Im in the wrong company, but sometimes I think that Im all alone in the world. Is my situation common-place, or is almost everyone in this situation for most of the time etc?
Please inspire me.
James.
Blimey - what have I started?!
Software Jockeys - yes, met a few of those. Great at the software, cannot plan. Have also met, though, the guys that can plan a project, start to finish, on a fag packet but know nothing of the software used. Which would I rather have? Hmmm, tricky question?
Not at all. If someone has the knowledge to formulate a programme, even if on a few sheets of paper, by hand, then surely he is the better planner. After all he can sit with the software jockey and get things into the programme.
Remember, Brunel, Stevenson, Preece, Edison and others, did not have the use of computers and look what they did!
Most software jockeys I have come across - quite a few in all - would not know falsework from a tunnel boring machine but they will quite happily explain the ins and outs of the software, they rarely leave the computer screen and cannot reconcile a drawing with site come Hell, Hull or High Water.
What does this really mean? The man to do the job I suppose. Surely it is better to have a competent engineer that knows the job than someone that works a computer who has not got the faintest idea of what can be slipped/over-lapped or whatever but has to stick ridgedly to the rules.
Ideally get one candidate that can do both, but if not give me a "back of the fag packet" man any day.
James,
I wasnt aware that you were setting a trap, seems a bit pointless to me. However, the situation you originally outlined, which I did my best to address, seemed to be a choice between two individuals of relative inexperience. The type of people who might be considered for a junior planning position.
Suddenly you expect them to be senior planners capable of using the plan as a reference source for "costing, resourcing, EV analysis etc.". Yes of course it takes considerable time to gain the necessary expertise to fully exploit the potential of the software, but this is part of the development process of individuals within the organisation. You could not reasonably expect a junior planner to do this the instant he or she had been hired.
Perhaps you should have made a little clearer what it was you wanted in your original question. You dont have to play games or set traps on this forum, simply ask your questions, and people will, quite literally, queue up to supply you with the information you need.
Regards
Chris Oggham
Chris,
All in the best possible taste, but you fell into my trap!
Taking a course in operating the software provides the smallest of benefit. With projects often running into many thousands of lines, having complex interrelationships, combined with unique software "operating characteristics", it is absolutely essential that the "planner" be able to use the tools to a competent level, otherwise it can be impossible to determine whether the end-results are representative of the truth. Of course, a conventional bar-chart is comparatively straight-forward to compile and administer in most software packages. However, when you really want to use the project as a single reference source for costing, resourcing, EV analysis etc. then you really have be very comfortable with every facet....and that can take years.
Ultimately, its the same-old-story: We want the perfect candidate.....and unable to find one, they get so desperate that they end-up employing someone like me! Lethal!
James.
James,
That`s really quite tricky to answer, as it depends on a number of factors.
Take the person who has got a lot of experience with the work, knows how to plan, but can`t use the software. Usually a training course and a bit of time to build experience and confidence in using it is all that is required.
Then again take the person who knows how to use the software, very familiar with its functions, but little or no experience with the work or planning. If they are not afraid to ask questions and get out from behind the computer screen, again it`s just a question of time to build confidence and experience.
As you probably guessed the people I have had difficulty with are the ones who are interested only in driving the software. Whose knowledge of planning consists of looking to see what we did last time and who think that their work begins and ends at their computer screen.
Chris Oggham
Chris,
Evidently youve encountered people who call themselves planners but dont live up to your expectations. What criteria would you apply to enable someone to be called a planner? Moreover, how would you reconcile the situation whereby a person had an in-depth knowledge of the details but couldnt drive the software versus a person who had a basic understanding of the principles but was well-versed in the software. Which one would you employ?
James.
How about people who call themselves planners who think that all there is to it is to be a software jockey? Most of them couldnt plan a p*ss-up in a distillery, and the damage they do to the credibility of the rest of us mind-blowing!
How about Design Engineers??
Most of those I work with are like bunch of 5 year-old children: Incapable of doing anything on-time without extreme levels of supervision...except perhaps filling-in their timesheets. Give them a weeks notice to formulate their monthly milestones and they will do absolutely nothing about it until you sit there with them. They start to whinge about "...spending more time reporting than doing the job...." even though they spend less than 1% of their time doing it. Ive spent two years educating these people about how to describe a milestone...and they still cant do it. They cant seem to make the connection between time-spent, cost and the fact that there are people waiting for them to finish their pretty-little drawing so that they can build the bl**dy thing....and yet theyre totally paranoid about letting anyone know how things are progressing. Their estimates are so wildly optimistic (un-thought through) that its no-wonder projects are always overspent....and its mainly because they conveniently forget half of the processes involved.
What sort of personality do you have to have in order to be Design Engineer? Ambivalence, nonchalance, paranoia, zero-commercial skills, disconnect with the space-time continuum, illiteracy?
Experiences please??
James.
Hi Nigel,
Nature vs Nurture? A little of both maybe. After all you wouldnt make a graduate fresh from university into the Managing Director. No matter how good their degree or how intelligent they are, but you might in twenty years time once theyve gained experience, and "grown" into the company.
Would this be the same person as the fresh-faced university graduate? Damned if I know!
Chris Oggham
Planner = Virgo ;-)