Me at my favourite coffee shop
Most mornings I have coffee in my favourite coffee shop and have a chat with George, the barrista. I like George and I want his coffee shop to remain viable – difficult in these times of rising prices – so, in addition to the pleasure of the coffee itself, I get satisfaction from knowing that I am contributing in a small way to his continuing income. I could have spent my $6 in another coffee shop or not on coffee at all and then those dollars would contribute to someone else’s income and job sustainability so I know that my expenditure is not increasing the number of jobs in total, I am simply impacting (admittedly in a very small way) where the jobs are being created or preserved.
But let us consider this same type of transaction – purchasing something for money – on a far larger scale. The government decides to build more infrastructure, say for a billion dollars, and it justifies that expenditure on the grounds that it is ‘creating thousands of jobs’. Let us set aside for a moment that the number of jobs is usually greatly exaggerated, never validated, and many of them may last only a few weeks or months. The real question is: are these jobs ‘additional jobs’, which is the way we are expected to view it and generally do, or have we simply changed the type and location of the jobs?
The government could have spent that one billion on community services (doctors, nurses, teachers, police etc or, indeed – if infrastructure is so important – on the maintenance of existing infrastructure ), or it could have left it in your pay packet instead of raising taxes to fund its infrastructure spend, but it chose to spend it on bricks and mortar. We like the idea of ‘more’ jobs being provided. We are less thrilled about the idea of jobs being lost. Fortunately for our peace of mind we do not see the jobs that are lost and although we do experience the lack of services that results we do not necessarily associate the two. So let us look at a typical project.
In December 1985 when the Adelaide Casino was established by the state owned Lotteries Commission, there was much hype about how many jobs would be ‘created’ by the Casino. And indeed, for the first six months, there was great excitement about this novelty. People flocked to it, abandoning their usual venues. It was the first Casino in the state and many went there to drink or eat, and some to gamble and the Casino employed many. After a while, however, the novelty wore off, fewer people went and the number of service people employed by the Casino declined. Customers sought to return to their previous venues but some of these, having to cope with reduced incomes in the interim but still pay high city rental prices had gone broke and moved out. Trouble was, in calculating the increase in jobs, no attention had been paid to where the new Casino customers were coming from or how long they would remain customers. The lovely little coffee shop I frequented in the city, which provided chess sets and boards for its customers, was sadly one of those that went out of business.
The moral of this story is when thousands of new job are vaunted, stop, look closer.
My team makes use of premortem thinking: as part of planning action, immediate or long term, consider how it might go wrong. We think ourselves into the future looking back at a project (or a meeting). Humans are surprisingly good at this time-travelling.
For me, this is part of a principle Asset Managers should embrace: the principle of reversibility. It’s not just about understanding the consequences of our decisions, but also about planning for the ability to undo or reverse their effects if needed. Sure, you can’t un-ring a bell, but we can find ways to get as close as possible to the pre-action state and minimize the impact if we think about it right from the start.
Do our plans have exit strategies or an undo button? None that I have seen, why not?
This is especially crucial in infrastructure projects, where large investments and long lifespans magnify the potential impacts. How would they be delivered differently if that was required? Would that requirement cause us to better maintain the infrastructure we currently have? I think so.
Let’s face the hard questions: Can we put rare earth metals back in the ground? Can we undo the energy consumed in building something new?
By embracing the principle in Asset Management and infrastructure decision-making, we can strive for resilient and adaptive systems that serve the present while safeguarding the future of generations to come. We navigate challenges with eyes wide open.
We ask tough questions, anticipate consequences, and face the answers with truth – and then we create our plans and strategies.
Penny and Ruth at AM Peak gala dinner, April 16 2024
Since I last posted I have spent a month celebrating 40 years of Asset Management in Australia with Penny, Jeff and Gregory; gone to one of my favourite conferences in Minneapolis; taught an advanced AM course to some sophisticated AM practitioners in Calgary, as well delivering to as a post ISO 55000 certification client in California.
I have been thinking about where AM needs to go next, at the same time as worrying that things have not moved far enough.
And it just keeps coming back to: We Need to Raise our Game. And not because what Penny kicked off four decades ago hasn’t made a huge difference already.
But I want us to do more.
First, to effect what Penny set out to do through Talking Infrastructure: to look up and out, to make a difference to key decisions on what infrastructure we really need.
Secondly, as I start to unwind from delivering basic AM training – something I have loved doing for nearly 14 years now – I reflect on our competencies.
This kicks off a series of questions and reflections on what we want to change, and how to do it.
How to interest existing AM practitioners in upskilling on risk, data analysis, culture/ system change, persuasion, strategic thinking?
How to find people who want to challenge the status quo on infrastructure projects?
What can we best offer from our collective experiences to support better decision-making?
I am looking forward to this!
Come and meet Penny and Talking Infrastructure in person! Watch this space for additional details, but here’s the programme so far:
April 15 & 16 AMPeak, Adelaide. Penny and Ruth will be at AMPeak.
April 18, Stantec, Brisbane
April 19, PACoG, Brisbane. Asset Institute, QUT, 11am- 12.30, followed by lunch. Join Joe Mathew and Kerry McGivern along with Penny and Ruth to discuss what we’ve learnt in 40 years – and look forward to the next 40. Includes a look of what is happening with asset management internationally, in this big year for AM.
April 23, Blue Mountains City Council, Katoomba, 10am to noon. Seminar with Jeff Roorda on Blue Mountains City Council planetary health and disaster recovery experience, plus update on the new advocacy project underway by IPWEA Roads and Transport Directorate (IPWEA RTD – NSW/ACT), on Lessons Learned from Disaster Recovery, to assist NSW Councils work with Local, Strate and Federal Government Agencies.
April 24, Sydney event, Dawes Point. 6-10pm Harbour View Hotel, 18 Lower Fort Street, Dawes Point, NSW 2000. Using the recent experiences of the Blue Mountains City Council, Talking Infrastructure is holding an event in central Sydney to call for urgent changes in all of our asset mindsets and tools to ensure planetary health, biodiversity and climate change resilience. Meet with Penny, Jeff, Gregory and Ruth, plus local IPWEA. Food provided thanks to AMCL.
April 30, IPWE, Melbourne. Presentation by Penny. Penny and Ruth will be at IPWE until May 3. There will also be a dinner out in Melbourne for TI friends and colleagues – please let us know if you would like to join us. And bring along your copy of Penny’s book to get signed!
If you are planning to attend our Sydney celebration, please RSVP to: amis40@talkinginfrastructure.com so we can keep an eye on numbers – limited to the first 60! Event is free, includes food and discussion with Penny Burns and Jeff Roorda and a whole heap of old friends and colleagues.
Full update of the 40th year celebration events shortly!
Join us at the Harbour View Hotel in the Rocks and help celebrate with finger food and drinks – plus Penny and Jeff on what we have learnt from the last 40 years to help us meet the challenges of the next 40.
Many thanks to Richard Edwards, Lynn Furniss and Matt Miles of AMCL
Penny Burns and Talking Infrastructure will be on the move in April to celebrate 40 years of Asset Management, and look forward to the next 40.
Adelaide April 15 & 16, Penny and Ruth will be celebrating at AM Peak.
Brisbane events April 17-19
Sydney April 24, venue TBC: Asset Valuation in a time of Climate Crisis. Including Jeff Roorda on how Blue Mountains City Council is taking a radically new approach, as well as Penny on how we must rethink our AMP modelling.
Melbourne April 30, IPWC. Penny speaking on the opening morning of IPWEA conference
Wellington May 4-6, events to be announced
Let us know if you are interested in meeting up in any of these cities.
See you in April! #AMis40
Someone I work with in the UK nuclear industry asks in despair, how come project engineers don’t feel that the whole point of building something is for it to operate? In other words, that construction projects only exist to create something that will be used to deliver products and services.
Why aren’t they interested in the long-term use that comes after construction?
If it really is all about use, they really need to consider what is required to use the asset. They should be interested!
This isn’t just to focus on what service we need to deliver. The asset has no point unless it delivers a service that is needed. Even project engineers can get that.
What we continue to struggle with is getting asset construction engineers and project managers to consider what is needed in order to use it successfully. And this includes providing as-built data – what assets are there to operate – and thinking ahead on operating strategy, and maintenance schedules. It’s designing and building with the operations and maintenance in mind. Designing for operability and maintainability.
In infrastructure, the asset ‘users’ are often not the customers, who may never touch or even see the assets. The people who use the assets are the operators; the people who touch the assets, maintenance.
An engineering design goes through many hands before it impacts on the customer – and if those hands in between are hamstrung by designs that are poor to operate, hard to maintain, and by the incomplete thinking that ‘throws the assets over the wall’ at operations (as we used to say in the UK) without adequate information – what is the point, really?
I believe there may be something called project time, where there is no ‘after’. No ‘and then what?’ – just onto the next shiny thing to build.
Thanks again to Bill Wallsgrove
Human beings may not naturally be good at thinking about the future.
One thought is that, just like with charity appeals for current disasters, we should focus on an individual. Think ourselves into the shoes of some one as they experience the future.
It could be ourselves, a grandchild (if we have one), a ‘descendant’ – or anyone we can picture.
A startling powerful example of this appears in the first chapter of Kim Stanley Robinson’s The Ministry for the Future, published in 2020. The author specialises in thoughtful, ‘realistic’ depictions of the future, for example in colonising Mars.
The Ministry for the Future starts by describing the experience of one Western man in a climate catastrophe, when twenty million people in northern India die in a heat wave. Many millions in a faraway country in the future: a newspaper headline. And ‘Frank May’, who works in a clinic near Lucknow, who nearly poaches to death in a lake full of people, where the water is above the temperature of blood.
I could not get the image of him out of my head for a lot longer than a headline.
I realised when watching the final episode of Planet Earth 3 last month that the image of Frank May was so vivid that it felt it was happening right now. It was not hypothetical, despite being fiction.
We may overdo the image of threats to a panda or polar bear or orangutan, to be invited to imagine a world without them. Just like we stop reacting to doe-eyed young children in charity ads. But I suspect we simply need this emotional connection.
Maybe like the Japanese traditionally put on the garment of a descendant, to feel how they will perceive the results of what we are doing now. We too could do this, to really feel it when we make a decision now about their infrastructure in fifty years’ time.
A technique to consider next time we are involved in long term asset decisions?
My colleague Todd Shepherd and I had a brainwave* last year to restructure how we teach Asset Management – not as a line that starts with investigating capital needs, the conventional beginning of the asset life cycle, but from where we are now. That is, right in the middle of maintenance. We are always deep in maintenance needs.
It makes more sense of the history of AM, straight off. It was not people writing business cases, or design engineers, who realised the urgent need for something different. It was maintenance, post World War 2, and then Penny Burns and the problem of unfunded replacements and renewals in the 1980s.
If Asset Management has waves, we might suggest what Wave Minus 1 was. Wave Minus 1 was hero engineers, from the Industrial Revolution on, building heroic infrastructure – Bazalgette and London sewers, Brooklyn Bridge. Sewers and bridges are both good things. But they are not quite such good things if they leak or fall down because they are not maintained or renewed.
With infrastructure, it is not enough to start; you have to see it through.
Penny used life cycle models to understand the extent of renewals, and increasingly I don’t feel anyone is really doing Asset Management if they do not use such models. Of course it is called life cycle for a reason. There isn’t an end, only another cycle.
But now I fear that starting at the beginning of one lifecycle in our teaching still makes it sound as though it is the creation of infrastructure that’s the important thing. We have not really got the cycle bit across enough, at least to the average engineer we teach. What comes after construction is still a vague future state, that is someone else’s problem.
And, not at all coincidentally, that’s also the point of the circular economy concept. There is no meaningful product end, and we are right in the middle of the mess we already built.
It is not a straight line into the future, where we set assets in motion and let them go. Longer term thinking, long-termism, has to think in cycles.
*Almost certainly it was Todd’s brainwave, which I managed to catch up with.
Recent Comments