Home > Uncategorized > Roles and Responsibility?

Roles and Responsibility?

Below are a few observations of my time in the design office so far, a continued criticism from the Orator is that there’s not enough reflection in my work so I’m trying to plug that gap slightly, this started off slightly more formal then it ended up however with a little pruning it will end up in AER 5.  The final point is an observation on where geotechnics fit in to the grand picture, mainly at the bottom (pun intended).  Sorry no pictures today, my desk is mainly looking dull.

 

I have been designated a Graduate Geotechnical Engineer, the positions more senior to me are:

Design Engineer – a number of years design experience, 3 in section.

Senior Engineer – A chartered engineer or geologist with commensurate experience, 2 in section.

Principal Engineer – An experienced Senior Engineer coordinating larger projects incorporating a number of junior engineers. 2 in section.

Associate, Project Director, Technical Director – Individuals with significant experience and typically dealing with checking, budgeting and oversight rather than design.

My presence at Ramboll is for a very specific purpose, to learn the more technical aspects of the civil engineering profession.  My willingness to assume responsibility and ability to organise have been proven elsewhere in my career; by contrast for a junior engineer searching for competencies outside of their immediate day job opportunities would be very limited.  Comparing this environment to that of a site based graduate working for a contractor the points I would note are:

  • Responsibility.  Both roles lack responsibility however the day to day tasks of a contractor are mundane and frequently just involve box ticking type inspections, there is very little thought beyond the consideration of safety infractions of particular operations.  A contractor learns more through conversation with and observation of their line managers, from my time with Osborne there was not much of a mentoring type relationship.  A designer by contrast is responsible for their design and must recognise the limits of their own competence, a designer learns by doing whilst mentored by a more senior engineer. 

 

  • Understanding of CDM.  CDM is a fundamental aspect of construction in the UK, it shapes every stage of design and delivery.  Much of the work seems to be completed early in a design, certainly from my experience as a contractor CDM was something that was done to you and to hear it’s title in conversation was a rarity.  A contractor does get to understand buildability fairly quickly a benefit of being exposed to tradesmen from an early career stage.  If you accept that much of CDM is completed in the early stages then it must be the designer that is doing it.  This means a relatively junior engineer who has probably not been exposed to site work and is basing their work on university designs where things are wished in place.  I would pride myself on being able to think through a problem and how it fits together in time and space and have found myself picking up aspects of design too late.  An example has been designing the retained height of a wall to finished road level forgetting that a road needs to be dug out before it can be constructed therefore increasing the retained height of the wall in the temporary condition.  How are junior designers expected to pick things like this up?  The lesson I learn is that even though CDM felt like it was all complete by the time it hit site the truth is: Buildability needs looking at long before the on site operation begins.  Unfortunately the reality is this is next to impossible due to time constraints on site.

 

  • Application of knowledge.  On site application of knowledge is rare and extends more to techniques rather than principles, the techniques are normally learnt from a more experienced manager or perhaps even a tradesman on site.  The graduate contractor is quite possibly surrounded by managers of various backgrounds and depending on the company is probably in the minority as a civil engineering graduate.  As a result they see many of their colleagues and line managers avoiding true engineering.  It is quite natural for a graduate contractor to become relatively blind to technical issues or even shy away from them altogether.  I certainly felt a couple of times like I had a bit too much of the classroom about me however soon realised this was wrong as others were blindly skipping along telling people to put their glasses on whilst ignoring bigger issues.  Possibly this is natural due to the delineation of design responsibility and risk, why try and solve someone else’s problem?  Actually it’s not a in contracting company’s interest to get involved as is muddies the waters when it comes to claim time.

 

  • Management of people.  A design engineer gets no exposure to managing people, reading the ‘Successful Chartered Professional Reviews’ book combined with the ICE DOs management and coordination is a key attribute of a Chartered Engineer.  Whilst I acknowledge that the reviewers are asking the question ‘would this person make the right decisions if they were placed in the appropriate appointment?’ rather than ‘has this person made the decisions expected of a CEng?’ it must be hard for a designer to demonstrate that the answer to the former question is yes.  This lack of management could possibly extend for the first 10 – 20 years of their career depending on how quickly they rise however ultimately some of these people must eventually become team directors and perhaps even board members.  Times on site as residential engineers or secondments to contracting companies can close some of the gaps but possibly not fully.  This is perhaps where matrix structures fall down and a more project based organisation has the potential to develop better future managers and leaders as there would be a greater exposure to project managers (who should be good people managers) doing their jobs.  The opposite is of course true for a contractor, they are exposed to a huge variety of people from an early stage.  Early on at the lower end of the spectrum they have to manage, cajole, bribe and blackmail them into doing what is required on site.  As they become more senior they then have to ‘manage’ their own line managers by managing expectations and diplomatically telling them that some ideas are stupid.
  • Uniqueness of geotechnics.  I am coming to the conclusion that Geotechnics isn’t where the cool kids hang out.  We all know that work in the ground carries a huge amount of risk and that geotechnical engineers are often the key to reducing that risk to acceptable levels.  However the geotechnical section always seems subordinate to everyone, for example the Associate in my section regularly seems to be picked on by an Associate from highways; the Senior engineer who is borderline special gets picked on by his equal from Building Structures.  I don’t quite get it, I know our part of whatever is built is buried or hidden away and our work effectively becomes the enabling work but it’s always pretty important, and always on the critical path, it’s like we’re the RLC of the design world. For example highways need a large number of gantries designed for roads, the loads never changed, the kit that gets hung on them rarely changes the only different bit is the ground underneath and yet we are definitely working to them rather than the other way around.

Categories: Uncategorized
  1. Richard Farmer's avatar
    Richard Farmer
    13/02/2014 at 9:08 am

    Pretty fair summation of the profession.

    I would note that Graduate Engineer is the title applied to anyone not yet chartered in the structural side of the business. Civils are frequently more accepting of knowledge and experience. I was still a graduate engineer at the age of 40 although fortunately, having moved to a more civil oriented consultancy a year previous, I was not refrred to as such but still realised the need to pull my finger out and charter. It’s rather similar to the way that many civil engineers regard post nominal letters as pretentious because they don’t have them whereas structural engineers use them but think nothing of them; it’s similar to the way that soldiers salute the commision – because they do and it is a simple of measue of got it or not got it.

    On the CDM and buildability experience front I would note that most consultancies I worked for or had friends working for tended to send junior enginers to site for checkes and routine meetings so that they could walk around site and discuss buildability issues with the contractors team. They then designed the solutions and work arounds and learnt a) not to cock up themselves and b) how to get out of the mire.

    Mangement of people – remmber all work and no play makes Jack a dull boy – any graduate engineer not doing school careers fairs or STEM work or running a local football team or teaching tai chi or being heavily involved in some form of social group is a rarety. We all learn to manage and lead in different circukmstances, frequently where the lead are not obliged or driven to follow by contract or need. This should be presented at CPR and reviewers do look to see evidence of performance as evidence of further potential. Peculiarly many engineers use reserve service to show leadership (and might not stick long beyond chartering – too busy in work now – honest!).

    Geotechnical engieers are special. Many structural engineers don’t understand the geotechnical world, are a little bit scared of it and so ensure they keep it in it’s place. And then there are the other explanations…

  2. 13/02/2014 at 10:41 am

    Jeeeez Rich …where was all this thinking lurking?…I really must go back and look in the Appendices to the TMRs…I must have missed something!

    So in your scheme I was chartered at 28 and Principal at 32…where did it all go wrong? I got really interested in Geo around 30 …uugh ooh!

    …I’m pretty sure that I knew diddly squat about anything until I returned to teach it and am repeatedly surprised how little intellectual clarity exists in assessment and solution of engineering problems.

    I am pretty sure that I knew nothing of Project Management until after I’d near-on had a real road accident in a large project that I was leading ( about 40 by then) ….yeahh..yeah …I’d done all of the junior then senior manager management stuff….just didn’t register

    So , so much is bluff….and I’ve no way of knowing but I suspect that this is common

    So I found your piece really quite excellent

    My observations..
    1 Always be clear on the finance…how are things being paid for. Engineers, in my experience, remain ….er…engineers becuse they don’t do that

    2 For any project(design, contracting, whatever)…identify the risk and manage it…..trailing comment as above

    3. Find the courage to ask obvious questions…NEVER assume that ‘ this is how we always do it’…or worse ‘we’ve done this a million times.’… is good enough

    4. As you catapult out of the engineeringy towards managementy (which, sadly, I must commend) keep hold of fundamental engineering principles….you’d be amazed how powerful simple analysis can be and finding risk

    On the subject of the lowly GEO…here’s the tab…..
    When I was doing my p/grad work I was a principal in a structural section but with GEOs from FRUGRO through to ARUP and they’d gone into and remained in geo….often they were geologist by background…point is that they knew diddly about the engineering they were supporting…so it remains and they’ve no pants to query even the dullest civil/structural decisions….no wonder they’re whipping boys………..
    There is no doubt that geo is the most intellectually challenging technical area of civil engineering….they just don’t realise it!

    Well toodle pip….boy is the next AER goin’ ta be maaaaahty fine!

  3. painter789's avatar
    painter789
    13/02/2014 at 11:56 am

    Rich

    Excellent. Please just remember to tweak the tiller for CPR!!!! As it is a different course to sail.

    Kind regards

  1. No trackbacks yet.

Leave a reply to painter789 Cancel reply