Friday, September 28, 2007

My commitment to the real world

The more I write in this blog, the more I realise what is important. I called it engineering for the real world, but now I realise the emphasis should be more on the real world and less on the engineering. I am an engineer and I think like an engineer but what I want to write about is the real world, the world that we all live in, for better or worse.

A few years ago I watched a documentary on how soilders are trained. The premise of the film was that most people do not have a natural instinct for killing, they have to be trained to do so. And the training that a soldier has to go through to create the natural killer instinct fundamentally changes the people that they are.

Of course, all this training must come at a price, and for soldiers it is a heavy one. The training does have an effect on who you are as a person and more importantly what your natural reaction to a situation is. This is by no means exclusive to the military, intense training affects us all as people. Many recruits probably don't realise this, but by agreeing to train as soldiers, they are making a huge sacrifise, not just potentially their lives, but they are allowing their nation to turn them into machines of war and in doing so change who they are as a person. It is of course not all negative, there are many benefits to becoming a soldier, but for those who have not been in the military I think it is important we remember all of the sacrifises that soldiers and their families make to protect our nations. Since watching the documentary I have always supported soldiers no matter what my view of the conflict they are engaged in, because of the sacrifise that they have made.

This morning I watched a TED talk by Deborah Scranton. She is a documentary film maker who has been creating a film covering the conflict in Iraq. This talk made me realise something, I have always said that I have supported soldiers, but to say something, and to make the commitment to do something are two different things. It is so easy to be a well meaning person saying that you believe strongly in this and that, but does this actually mean something unless you actually do something about it. It might not have to be something particularly special or important, but I think only by doing something can we demonstrate our commitment.

I feel now that I need to go out and do something for returning soldiers. It might not be much, but I have to demonstrate my commitment to myself, I have to find out if I am truly committed or if I need to reassess the way that I view the army and the people who work within it.

The talk by Deborah is really compelling. I'm not going to discuss the rights and wrongs of the wars going on around the world, but this is a film that is worth looking at for everyone. Whatever your point of view it does demonstrate what the soldiers are going through, and if demonstration is ever needed that soldiers in a conflict zone are not just doing their job, this film is it. It is a cliché, but this talk is so compelling that the silence is deafening.



Friday, September 21, 2007

Don't get caught in the incident pit

The incident pit is a concept I first read about in one of my mums diving magazines. At that time I realised how useful it is in describing incidents involving divers and how a lot of small things going wrong can result in a major incident.

In essence, the incident pit is something that you gradually fall into. One small thing might not initially go to plan or a relatively minor piece of equipment might break down or get left at home; when this happens you have put your first foot into the incident pit. Initially it is not a problem, but then something else goes wrong - that is another step into the pit. The challenge with the incident pit is that with each step, not only do you get closer and closer to the bottom of the pit and a serious incident, but with each step the sides of the pit get steeper and steeper. It gets more and more difficult to get out the further into the pit you go.

I think there is something to learn from this concept for engineers. I often see engineers taking steps into the incident pit with relatively minor problems, potentially causing much larger problems in the future. To define the incident pit I think that there needs to be two key elements. The first is that the incident pit is caused by a series of problems, any of which would not be a problem on their own, but each one exacerbates the next. The second is that you have to be in a situation where you are incrementally committing yourself. For divers this is relatively easy to understand, the deeper you are diving the more committed you are and the more difficult it will be to solve any problems. I think this is often the case for engineers; as we design and build something, we make more and more commitments and we have more and more invested in something, so just stepping away becomes difficult, if not impossible.

The trick is to know when to stop taking steps into the pit. Another key feature of the pit for divers is that you can always choose to stop taking steps into the pit, but this has a cost, because their dive may have to be cut short. It is the same in engineering, if you choose to stop taking steps into the pit there will probably be a cost.

I want to look at how the incident pits forms in engineering, so I'm going to consider a simple building being designed by a structural engineer. The design starts off well with no major problems and he makes his first submission to the client. They love the design, especially the huge front window that you have given them. At this point you haven't taken a step into the incident pit as nothing has gone wrong, but you have started to get committed.

The next day you get a call from the manufactures of the glass for the centrepiece window. They are no longer able to provide glass quite up to the specification you wanted. This is the first step into the pit. It might not be the designers fault but he does have the choice of whether to continue or not. At this point in time it is not a major problem, even if the glass is not quite up to the expected specification, it should still be strong enough so the engineer chooses to continue.

So the engineer goes and makes a few more submissions to district planners, the contractors who are pricing the project, and utility companies to check the sewers running under the house will be okay. As each one of the submissions goes in, the engineer gets more and more committed to the proposal; backing out gets more and more difficult.

And whilst the project is getting more and more committed, problems keep affecting the large glass window. The original calculations needed to be modified slightly imposing greater forces on the window, new codes of practise are issued which require a better performance of the window, the structural frame has to be modified slightly increasing the span of the window. The engineer is getting caught in the incident pit as he gets more and more committed. The small problems gradually mount up and if the engineer does not pull out soon enough he will be trapped - the design will not be adequate, but too many commitments have been made. All of a sudden the small problems escalate into one big problem.

There is no easy way to deal with the incident pit. You just have to recognise when things are not going as planned and know when it is time to pull out so you don't get trapped. By remembering how these small problems escalate and how easily you can get trapped, it is easier to deal with the problems.

Saturday, September 15, 2007

Pangea day

I've often been struck by the power of films. Very few other methods of communication seem to have the same ability to touch me. I think this might be because of the unique combination of story, images, music and words that a film can have. A well done film is a powerful thing and that power has to be used carefully.

I see Pangea Day as potentially one of the most important days in the history of humanity. The power of the films could profoundly change the way the world works and the way that we interact with our planet.

If you want to get involved I would encourage you to take a look at another film. This is the original wish by Jehane Noujaim, given to the TED conference.I hope that many more wishes like this have a chance to come true.



Friday, September 07, 2007

Sir Ken Robinson: Do schools kill creativity?

In an entertaining talk by a leading thinker, Sir Ken Robinson proposes that creativity is being killed by the education system.



Sunday, September 02, 2007

Creativity in engineering

Creativity is probably one of the less well recognised abilities that all engineers have. Solving practical problems is what engineering is all about and if you are trying to solve a problem that has never been solved before, you have to think creatively to come up with the solution.

The conventional view of creativity is that the fewer boundaries there are, the more creative the solution. This is however quite profoundly wrong in the case of engineering a solution to a problem, for engineers it is boundaries that allow us to use our creativity.

To demonstrate this I want to consider the case of somebody who asks an engineer to design a bridge from an island to the mainland. The engineer is only too happy to oblige and starts to scratch his head to come up with a design. So what design should he come up with? The engineer doesn't know much about his client or his problem, but does want to please him. So what is the best solution?

I'm going to simplify this problem somewhat to consider it in detail. I want to consider the bridge solution in terms of only two variables, the capital cost of the bridge and the capacity of the bridge, this is just to simplify the model we are going to consider, and more complex models will be developed later.

To model the solution I want to consider a two dimensional solution space. Each dimension represents one of the solution variables, so in this case we have a two dimensional space with one dimension representing the capital cost and the other dimension representing the capacity of the bridge.

Having generated this solution space, we need to consider the original request, a bridge to connect an island to the mainland. We don't know anything else so the best way to get as close as possible to the clients request is to go for something in the middle of the solution space, something average. In this case it probably represents a bridge with two lanes in each direction, something fairly standard and not very creative. If we go for a creative solution, something further from the middle of our solution space, we run the risk of being a long way from the clients requirements.

So how do we come up with something creative? What if we asked the client a few questions, one relating to each dimension of the solution space. What would you like the capital cost to be? What would you like the capacity of the bridge to be?

By asking these questions we can find the point on the solution space that represents our clients aspirations. But how does this relate to creativity, instead of having the whole solution space to use to come up with our bridge design, we only have a small part of the space to work with.

Consider what would have happened if our client had asked for a very low capital cost and a very low capacity because our client only needs to cross to the mainland on his own once a week. In this case, it seems like he doesn't actually want a bridge, because a rowing boat is a better solution. Just because we are tied to a small region within the solution space, it doesn't mean that our solution can not be creative; such as proposing a rowing boat instead of a bridge.

Exploring the different points within the solution space shows us the range of solutions that could be develop for this simple request for a bridge. Most of these solutions could not realistically be proposed without some initial input from the client to allow us to come up with the creative solutions for a point in the solution space.

Using this example it is clear that creativity in engineering and problem solving is not necessarily a result of starting with a blank sheet of paper and an open brief. It is the boundaries that are imposed on our solutions that both allow us and force us to generate a creative solution. I believe that many engineers do not like getting a full brief either because of the perceived difficulty in coming up with a solution with a very tightly defined solution space, or because they wish to have a broad solution space so they can look at many solutions.

This approach goes totally against what it means to be an engineer. We should be aiming to exceed our clients aspiration, and the only way to achieve this is through knowing where a clients desired solution is on the solution space. We should be embracing the challenges that we are set. Of course we must also have the tools to come up with the creative solutions that sit within a well defined solution space, and this is where engineers need to be taught design skills. It is these design skills that form our toolbox for coming up with creative and novel solutions.

Friday, August 31, 2007

Rotherwas Ribbon

It takes a lot to hold up a bulldozer, but near Hereford works on a new road project are being held up by a serpent. Or at least that is what it might be.

Nobody knew the Rotherwas Ribbon existed until earlier this year, but archaeologists working ahead of the bulldozers on a new road project have found a new archaeological site. The Ribbon seems to be nothing like existing UK sites and because only part of it is exposed, we don't know what future excavations will reveal. It must be an exciting time for archaeologists waiting to see what else might turn up at this site.


View Larger Map

For those involved in developing infrastructure it is more complex. I am excited by this discovery like archaeologists, but events like this always concern me. It is human nature to personalise events and infrastructure projects are no different; people associate infrastructure projects with the people who design them, build them and those who procure them. If a project is seen in a bad light, the people who build it are also often seen in a bad light. Even worse the people who build it can be seen as evil people intent on destruction.

This is not helped because of the negative image that infrastructure projects often have in countries where there is a good existing infrastructure. In these countries the effect of a project can often be small, with the public finding it difficult to engage with it. There is little passion for the project, but in contrast there might be a lot of passion about some of the perceived negative consequences. People fight to protect things that they feel might be damaged by a project; culture, the environment, tranquility, history. And that fight is often vocal, makes good stories for the media and draws in the public.

The negative perception of engineers is important, but it is not what concerns me when problems like the Rotherwas Ribbon occur is not how the public sees it, but how those involved in the project manage it. Often projects are well managed and come out with a good outcome, but things do go wrong. It is these projects that do go wrong which are the most damaging both for for the perception of the industry, and for the legacy that we leave behind. Good decisions have to made to avoid costing the taxpayer, the environment and our cultural heritage both now and in the future.

I wish those working on the project well. I have no doubt that hard decisions are being made by everyone on the project and that there will be a good outcome. I look forward to the day that I can go an visit the Rotherwas Ribbon in an environment that befits such an important piece of archaeology.

Wednesday, August 29, 2007

Engineering hints and tips

This blog did not seem like the right place to put some real hints and tips for engineering design so I've set up a separate blog to cover these (Engineering hints and tips)