WEBVTT
00:00:00.501 --> 00:00:02.322
Hello everybody, welcome to the Fire Science Show.
00:00:02.322 --> 00:00:11.035
Today we're talking fire engineering, and fire engineering is a very specific set of projects, very interesting set of projects.
00:00:11.035 --> 00:00:21.675
Today we are talking broadly infrastructure, energy, really big projects which cannot be qualified as your everyday real estate.
00:00:21.675 --> 00:00:31.568
I thought that a lot of engineers listening to this podcast are obviously in the space for building stuff like residential buildings, office buildings, car parks, malls, etc.
00:00:31.568 --> 00:00:34.868
That's our everyday jobs and that pays the bills.
00:00:34.868 --> 00:00:46.902
But for safety, engineering is so much broader, so much broader, and there is a lot of interesting things happening in different sectors of built environment which I would love to bring to you as well.
00:00:47.323 --> 00:00:50.491
I'm personally a bit involved in non-real estate projects.
00:00:50.491 --> 00:00:56.264
We're doing a lot of tunnels, as you know, listening to this podcast, but the scope and the world is much bigger than that.
00:00:56.264 --> 00:01:35.030
Therefore, I've invited a guest, dr Mukesh Tomar, from Jacobs, and he actually has a pretty big experience working on different types of very large infrastructural and non-real estate projects across the world, many of them in Middle East, which brings a very interesting perspective into how fire safety engineering looks of interesting aspects, from being able to define the objectives of the engineering, working with the local governments or authorities, building up the knowledge base to start even with the project and figuring out a project specific considerations.
00:01:35.030 --> 00:01:39.001
We talk about very long cable tunnels in remote locations.
00:01:39.001 --> 00:01:41.125
We talk a bit on nuclear.
00:01:41.125 --> 00:01:42.927
We talk a bit airports.
00:01:42.927 --> 00:01:57.355
I think it will bring you a very interesting perspective and if you actually work on non-real estate infrastructural projects, this will bring you a lot of things that you can relate to in your everyday engineering job.
00:01:57.355 --> 00:02:04.319
So I hope we captured the spirit of a little bit different fire safety engineering in the non-real estate projects.
00:02:04.319 --> 00:02:07.329
So please join me and Lukasz in this episode.
00:02:07.439 --> 00:02:09.729
Let's spin the intro and jump into the episode.
00:02:09.729 --> 00:02:15.467
Welcome to the Fire Science Show.
00:02:15.467 --> 00:02:19.002
My name is Wojciech Wegrzyński and I will be your host.
00:02:19.002 --> 00:02:48.512
The FireSense Show is into its third year of continued support from its sponsor, ofar Consultants, who are an independent, multi-award-winning fire engineering consultancy with a reputation for delivering innovative, safety-driven solutions.
00:02:48.512 --> 00:03:02.262
As the UK leading independent fire risk consultancy, ofr's globally established team have developed a reputation for preeminent fire engineering expertise, with colleagues working across the world to help protect people, property and the planet.
00:03:02.262 --> 00:03:18.350
Established in the UK in 2016 as a startup business by two highly experienced fire engineering consultants, the business continues to grow at a phenomenal rate, with offices across the country in eight locations, from Edinburgh to Bath, and plans for future expansions.
00:03:18.350 --> 00:03:26.870
If you're keen to find out more or join OFR Consultants during this exciting period of growth, visit their website at ofrconsultantscom.
00:03:26.870 --> 00:03:29.025
And now back to the episode.
00:03:29.025 --> 00:03:37.133
Hello everybody, I am joined today by Dr Mukesh Tomar, the head of fire engineering at Jacobs in London.
00:03:37.133 --> 00:03:39.167
Hey, mukesh, good to have you in the podcast.
00:03:39.860 --> 00:03:41.546
Lik ewise, Wojciech .
00:03:41.546 --> 00:03:49.675
I was thinking of making a session with you on this special podcast, so it's an opportunity for me, actually, and it's a pleasure to be here.
00:03:49.960 --> 00:03:51.143
Yeah, it's a pleasure for me.
00:03:51.143 --> 00:04:00.269
It's always fun to talk with fellow fire engineers about fire engineering, and today we're going to talk about fire.
00:04:00.269 --> 00:04:03.782
You called it non-real estate type of build environment.
00:04:03.782 --> 00:04:12.790
I usually call it infrastructure fire engineering, but that's the thing we're going to talk, so maybe can you define the scope where we will be in today's episode.
00:04:13.110 --> 00:04:13.673
Yeah, I'll tell you.
00:04:13.673 --> 00:04:20.730
That's why I say non-real estate fire engineering, because I see someone who is also a fire engineer, by the way.
00:04:20.730 --> 00:04:22.839
I can meet him in a pub or somewhere.
00:04:22.839 --> 00:04:24.908
And when he asks, can you fire engineer?
00:04:24.908 --> 00:04:29.807
I say yeah, I'm a engineer, by the way, like and meet him like in pub or somewhere.
00:04:29.807 --> 00:04:32.612
And when he asked me, like you fire engineers, yeah, I'm fine, like what you do, that's like I do the same stuff as you do.
00:04:32.612 --> 00:04:34.233
And then it's hard for me to explain them like why is so different like what I do from what they do?
00:04:34.233 --> 00:04:34.774
Like you know which?
00:04:34.774 --> 00:04:41.165
What the most of the fire engineers do is like a real estate project, which is office walls or the commercial, the buildings.
00:04:41.165 --> 00:04:43.588
But very few have, like what?
00:04:43.588 --> 00:04:46.192
Experience on the infrastructure wide.
00:04:46.192 --> 00:04:53.086
So when you say infrastructure is quite hard, some people only think like it could be, like you know, industrial projects, like factories and warehouses, those kind of things.
00:04:53.086 --> 00:04:55.072
So it's not really on infrastructure.
00:04:55.072 --> 00:04:57.925
So for me it's like real estate and non-real estate.
00:04:57.966 --> 00:05:13.560
It's the easy version of saying like what we generally count in infrastructure if I had to qualify myself into a group, I would say I am in that case 70% infrastructure fire engineer and 30% real estate fire engineer.
00:05:13.560 --> 00:05:22.002
So I also touched a bit of both worlds and I can relate to the, in one hand, this engineering looking the same.
00:05:22.002 --> 00:05:23.908
In one hand it's been completely back.
00:05:23.908 --> 00:05:27.269
First question to ask what's your background?
00:05:27.269 --> 00:05:35.793
How did you come to fire engineering and when did your career take a twist into the infrastructure projects?
00:05:35.793 --> 00:05:37.425
Did you work on real estate before?
00:05:38.208 --> 00:05:41.249
Oh yeah, my career is full of turns and twists, you know.
00:05:41.249 --> 00:05:50.891
So if I have to start back like, in 2007, I graduated with mechanical engineering and I went it for a master's in aerospace engineering quite interesting.
00:05:51.173 --> 00:06:06.014
and then I worked in winter as well for testing of like some buildings, aircraft, aerofoils, whatever you call it and after that I ended up in working for a medical firm which was to design for the medical equipment.
00:06:06.014 --> 00:06:18.779
Quite interesting, from mechanical to aerospace, to designing medical equipment but I had a passion of doing something in the field of either thermal or aerodynamics or those sort of things.
00:06:18.779 --> 00:06:36.670
So I was not really planning a career in the construction sector or the consulting sector, where I'm currently, but it just happened that I got an opportunity in 2011 and I joined the company in India back in those days and then we started with fire.
00:06:36.670 --> 00:06:45.781
So I was starting as a fire fighting engineer, fire protection engineer, generally make design for sprinklers and those active systems, generally speaking.
00:06:45.781 --> 00:06:50.298
So I worked on lots of these triples, by the way, and I've done lots of these triples.
00:06:50.298 --> 00:06:58.968
The problem I found and it's not a problem it just get boring after a certain point when you know there are standard that you can use and you can make your design.
00:06:58.968 --> 00:07:03.124
So the challenging part is like I would say like 10 20 person in those work.
00:07:03.124 --> 00:07:05.127
But but what I was always like?
00:07:05.127 --> 00:07:09.415
You know that I need to make a strategy so I can change the whole dynamics of the things.
00:07:09.415 --> 00:07:12.831
I can make things more you know, valuable or useful.
00:07:12.831 --> 00:07:21.870
Hence I was trying to shift it into the fire engineering, the actual fire engineering where we make fire strategies, and it took me like quite five, six, seven years.
00:07:21.870 --> 00:07:30.557
And then when I shifted to Dubai in 2015, and then I started slowly, slowly shifting into the fire engineering and since then it's been fun.
00:07:30.576 --> 00:07:49.833
So my first entry to the infrastructure project was in 2017, when I was working on Al Maktoum Airport in Dubai and I have to deal with a project where we had a number of road tunnels, tunnels, and I got surprised that how come, in 2016 and 17, we have such a limited data for road tunnel fire.
00:07:49.833 --> 00:07:55.317
And then I got excited as well, because when you don't have something, it's a possibility, right.
00:07:55.317 --> 00:07:57.848
I see it as a possibility that I can pursue it.
00:07:57.848 --> 00:08:19.399
I thought of doing a PhD in that topic, and then I also, like you know, started reading the codes and practices by different people, like what AECOM does, what Atkinson, what Tha does, what everyone else does, just to compare, and to my surprise, they all were slightly different than each other, and so does the codes of the various countries.
00:08:19.519 --> 00:08:32.056
So it is like I'm not able to understand how can a code or standard in UK, europe, asia or USA can be completely different than each other while they're solving the same problem.
00:08:32.056 --> 00:08:34.307
I mean, you know, I'm still not 100% sure.
00:08:34.307 --> 00:08:35.289
How does it work?
00:08:35.289 --> 00:08:48.346
So when I work on this project like one is in India, one is in Dubai or in Saudi and one is in UK, one is in Europe and they all follow a different code and the approach is completely different the objectives are completely different.
00:08:48.346 --> 00:08:52.791
Sometime, or most of the time, half the time, the objectives are not very clear.
00:08:53.399 --> 00:09:06.789
I have this from the opposite side, so I'm mostly dealing with projects in Poland, but we have engineering offices from all around the world trying to do projects in here and I am the one explaining that it's different in here.
00:09:06.789 --> 00:09:11.850
Like we do it differently and people are always surprised like why is it different?
00:09:11.850 --> 00:09:19.350
Would you say that those infrastructure larger projects allowed you to do more fire engineering?
00:09:19.350 --> 00:09:27.567
Because in the world of residential commercial buildings I feel everything's prescribed In Poland you would only engineer smoke control.
00:09:27.567 --> 00:09:29.304
Really, you absolutely don't.
00:09:29.500 --> 00:09:41.462
I mean, if you look at the very old standard, like you know, if you talk about, for example, nfpas are like NFPA 101 or 5000, which are mainly for life safety code, the similar codes of UK or Europe or the Middle East.
00:09:41.462 --> 00:09:42.144
They are very similar.
00:09:42.144 --> 00:09:43.846
Similar codes of UK or Europe or the Middle East.
00:09:43.846 --> 00:09:44.967
They are very similar.
00:09:44.967 --> 00:09:56.707
They're written in a way that you can adopt them in a building and you can make your design according to them and most cases they are purely prescriptive work, exceptionally in few projects where you have challenge.
00:09:56.727 --> 00:10:09.793
You do a little bit of performance-based and which is most limited to work you on a few of the CFD cases and then you dissolve it and then you show asset-to-asset and some smoke layer and that's it, that's all.
00:10:09.793 --> 00:10:22.308
But here in infrastructure it's quite opposite to the real estate projects or those projects it can be as hard as 80%, 90% performance-based and only factor-in-person prescriptive-based.
00:10:22.308 --> 00:10:27.065
There are a few examples that they are fully performance based, 100% performance based.
00:10:27.065 --> 00:10:46.202
So when you start you really don't know what you need to achieve and so you know it gets very, very interesting when you work on those projects that there are no clear objective what you want to achieve, and then you get challenged under like whatever you say, because you don't have a benchmark to set like you know that we need to start here.
00:10:46.222 --> 00:10:51.269
Why would you say you don't have an objective to achieve, so there's no authority that has an objective.
00:10:51.269 --> 00:10:56.471
The authority doesn't know what the objective should be, or they choose inappropriate objectives.
00:10:56.893 --> 00:11:02.966
Okay, so since you touched on the authority, I'll call myself lucky on a project where I can interact with authority.
00:11:02.966 --> 00:11:05.808
So it varies from region to region.
00:11:05.808 --> 00:11:09.230
It is usually in certain region, I'll not name which reasons.
00:11:09.230 --> 00:11:11.740
You can only contact authority.
00:11:11.740 --> 00:11:13.427
Once you finish your project.
00:11:13.427 --> 00:11:17.461
You submit it for the final or, like issue, for construction level of design.
00:11:17.461 --> 00:11:24.866
So when it goes to construction then you have the first opportunity to interact with the authorities, and that's too late for such projects.
00:11:25.368 --> 00:11:26.169
But there is a client.
00:11:26.169 --> 00:11:27.533
The client must know an objective.
00:11:27.533 --> 00:11:28.033
Okay.
00:11:33.379 --> 00:11:40.788
That's really a very high ambition to have a client which knows the real object I mean with no respect to any client so they do know some of the objective, but when it comes to fire, things become critical.
00:11:40.788 --> 00:11:53.982
So if I have to take an example, let's consider an example of 60 or 50 kilometer long of cable tunnels in a place like there's no city or nothing in there, like there's no fire service at all.
00:11:53.982 --> 00:11:59.241
So what do you expect the client to have as a requirement of object from the fire engineering?
00:11:59.241 --> 00:12:01.749
They don't really sometimes know, like, what it means to them.
00:12:01.749 --> 00:12:05.293
So we have to tell them and the things become challenging in such a long and complex project what it means to them.
00:12:05.293 --> 00:12:09.206
So we have to tell them and the and the things become challenging in such a long and complex project when you need to work.
00:12:09.206 --> 00:12:12.660
So as a fire engineer, we work against few objects.
00:12:12.660 --> 00:12:21.205
Like we need to make sure that the people who are there either occupying the building or the facility or working for maintenance, are safer.
00:12:21.205 --> 00:12:25.231
They can they can go out safely if there's any incident.
00:12:25.231 --> 00:12:39.884
Second, there should be an inherent and if not exclusively, provision to have the continuity of that business, so someone should not lose all of the investment or the or the work that they have done, and then there should be a resilience as well.
00:12:39.884 --> 00:12:43.740
So property protection, business continuity, life safety, all of them right.
00:12:44.263 --> 00:12:51.379
So if you look at the code for the standards of any country, they are mainly code for the standard for the building.
00:12:51.379 --> 00:12:53.566
So we have a building regulation in uk.
00:12:53.566 --> 00:13:03.582
There is similar building course or building fire course in in various countries in middle east, but they cover building, interestingly, right, and we're talking about infrastructure.
00:13:03.582 --> 00:13:05.768
So sometimes they have one liner.
00:13:05.768 --> 00:13:06.548
There is.
00:13:06.548 --> 00:13:20.528
There are few countries they have tried to put a table in their standard or their building aggregation codes, one table to cover the all the infrastructure project, saying like, okay, if you have a cable tunnel, do this, just one line.
00:13:20.948 --> 00:13:27.062
That's just not the way to to deal with making your objective for such a infrastructure heavy project.
00:13:27.062 --> 00:13:37.921
So when I'm saying like there's no objective or there's no clear objective, what I mean is like, because I don't have a building code saying to me, how do I make sure the people are safe?
00:13:37.921 --> 00:13:43.559
Everything I propose is just going to be my own interpretation of how do I do for engineering.
00:13:43.559 --> 00:13:45.908
Right, so I could do, you could do differently.
00:13:45.908 --> 00:13:49.450
And even in my team some people can do it totally differently than me.
00:13:49.450 --> 00:13:53.311
Then it becomes a hard sell to the authorities, to the client.
00:13:53.311 --> 00:13:55.548
Whatever we are saying makes sense.
00:13:55.548 --> 00:13:59.470
So that's why I say there is no clear, defined objective.
00:13:59.470 --> 00:14:03.071
It varies quite significantly in this project sometimes.
00:14:03.700 --> 00:14:08.308
I like the example that you brought, the 60 kilometer long cable tunnel.
00:14:08.308 --> 00:14:16.529
That's such an abstract concept to me that I would love to put it forward if you're willing to talk about examples like that.
00:14:16.529 --> 00:14:19.971
So okay, obviously let's agree.
00:14:19.971 --> 00:14:24.913
Life safety, continuity, property resilience that's, let's say, groups of objectives that we can narrow.
00:14:24.913 --> 00:14:27.011
Life safety continuity, property resilience that's, let's say, groups of objectives that we can narrow.
00:14:27.011 --> 00:14:33.283
Life safety I probably limited, because it's going to be manned only where the cable connects.
00:14:33.283 --> 00:14:35.460
There's not going to be people in the cable.
00:14:36.168 --> 00:14:39.881
So let's say, life safety is like default, probably okay.
00:14:39.881 --> 00:14:43.659
Now how do you care for other?
00:14:43.659 --> 00:14:56.409
Because like it feels like kind of binary, like Another objective you could put in is I do not have a fire in the tunnel, which is realistically very difficult to achieve with 100%.
00:14:56.409 --> 00:14:58.611
So where do you put those boundaries?
00:14:58.611 --> 00:15:06.258
How much safety for continuity, for productivity protection would you like to put in and how the hell you quantify that?
00:15:06.258 --> 00:15:07.765
That's a very interesting question.
00:15:08.259 --> 00:15:17.130
So there are a few clans that try to go to that level of resilience that what if we just don't allow fire to happen or not to grow?
00:15:17.130 --> 00:15:23.779
So we're talking about like an environment where the either oxygen is too low or something similar, something similar.
00:15:23.779 --> 00:15:37.890
We have not explored those for the cable tunnels for various reasons, but we did explore them for some warehouses and data center and some nuclear plants, and the outcome was that is a very complex solution.
00:15:37.890 --> 00:15:44.910
It looks very simple on paper, very simple, that you can reduce the oxygen and you can do some other methods and then the fire will never happen.
00:15:44.910 --> 00:15:53.888
But it's like your insurance policy you have one page of the cover and you have 100 pages of your terms and conditions.
00:15:53.888 --> 00:15:54.408
You know what I mean.
00:15:54.408 --> 00:15:56.234
Yeah, it's in some way it's like that.
00:15:56.234 --> 00:15:59.745
So when you read the fine prints you will know what I mean.
00:15:59.745 --> 00:16:06.850
So when you, when you're trying to go with that approach that, can we do it completely foolproof that fire will never happen?
00:16:06.850 --> 00:16:07.652
The answer is no.
00:16:07.652 --> 00:16:15.105
That's not going to be achievable, unless someone just makes it on paper, which is of course you have to accept, but then it won't happen.
00:16:15.105 --> 00:16:18.429
So now let's go down to the objectives Life safety.
00:16:18.429 --> 00:16:27.428
It looks very simple that life safety shouldn't be an issue but believe me, there are people when they go in work there, because of their arrangement it depends.
00:16:27.509 --> 00:16:37.344
If there's a partition between the large utility, tunnels could be like you know, someone can separate the dry utility from wet, or it can be some of the separations.
00:16:37.344 --> 00:16:45.350
When you have separation and it's a far separation, it's slightly easier so you can transfer people to other side and then they can slowly, slowly go outside.
00:16:45.350 --> 00:17:03.705
But when it's just a unique direction, just one way traffic tunnel or like one way, simply one tube, it becomes so hard because you don't have a huge clear height or the area to contain the smoke, so any fire, you are just chasing your life as a staff or whoever you are.
00:17:03.705 --> 00:17:14.416
And with such a long tunnel you aren't expecting exits or the cat ladders or the access hatches at a few meters.
00:17:14.416 --> 00:17:18.991
We're talking at least a few hundred meters, if not a few kilometers.
00:17:18.991 --> 00:17:25.661
So in one of the examples we had a two kilometer example.
00:17:25.661 --> 00:17:26.182
We had a two kilometer.
00:17:26.182 --> 00:17:32.910
So you can imagine like if you, if you are very good runner and when you are very good senses of sensing there's something wrong and you make it right point you make your exit and then you may be able to reach there.
00:17:33.352 --> 00:17:43.922
All you justify by a cfd simulation, by your fire hazard analysis, that what could burn, how it can burn and what level of smoke and soot and everything else can give.
00:17:43.922 --> 00:17:46.847
So you're running basically against a cfd scenario.
00:17:46.847 --> 00:17:51.642
I just hope like it's going to be that scenario in the real life if it has to happen.
00:17:51.642 --> 00:17:54.669
So those are the challenges for life safety as well.
00:17:55.431 --> 00:18:10.134
And now if you talk about property protection, unfortunately unless you provide an active fire suppression and that's also some people will debate or is concerned because of having active separation in such facilities, it's not a good idea.
00:18:10.134 --> 00:18:13.688
But I'm pretty open, I do accept those solutions.
00:18:13.688 --> 00:18:18.365
So if you have to put one, you increase your chance of property protection and business continuity.
00:18:18.365 --> 00:18:24.480
I'm not saying that you will just eliminate, that will never happen but you reduce your, your loss in a way.
00:18:24.480 --> 00:18:33.144
So those are the general things, but there are a number of five engineering options by which you can enhance your property production and business content.
00:18:33.144 --> 00:18:39.928
You can provide or propose some horizontal compartmentation, which we are doing currently in one of the utility tunnels.
00:18:39.928 --> 00:18:43.309
We are putting compartmentation at an interval.
00:18:44.250 --> 00:18:50.113
I'm asking that because some decision can be taken in an abstract space, Like you can say.
00:18:50.113 --> 00:18:52.314
It's better to compartmentalize this.
00:18:52.314 --> 00:18:57.296
And then the question is like okay, so every 100 meters, every 200 meters.
00:18:57.375 --> 00:18:58.176
Exactly.
00:18:59.477 --> 00:19:02.618
In a general, broad sense, it's easy to come with a solution.
00:19:02.618 --> 00:19:11.362
It's just very hard to narrow it in the technical details that you know that it's feasible, that it's economically viable and it's going to like provide you.
00:19:11.362 --> 00:19:13.428
So I'll give you an example from my world.
00:19:13.428 --> 00:19:16.343
So we were designing a road tunnel it's not a fire example.
00:19:16.343 --> 00:19:36.113
So we were designing a road tunnel and the road tunnel had a massive ventilation station which is quite near a residential district, and the occupants of the district were very annoyed with the fact that there's a big ventilation building nearby, as they envisioned that they're going to be dying out of smoke very soon.
00:19:36.759 --> 00:19:39.028
As if the road was not in tunnel, they would not.
00:19:39.028 --> 00:19:43.104
Of course, the cars would then magically not emit any smoke.
00:19:43.104 --> 00:19:45.165
Cars would then magically not emit any smoke.
00:19:45.165 --> 00:19:50.590
But anyway, the public was very hard on the investor.
00:19:50.590 --> 00:19:53.513
You need to install filters.
00:19:53.513 --> 00:19:58.922
That was the message of the public, and we get that message Like what do we do with it?
00:19:58.942 --> 00:20:00.746
And I'm like to design filters.
00:20:00.746 --> 00:20:02.912
I need to know two things.
00:20:02.912 --> 00:20:16.781
One is what's my initial concentration, so how much the cars can emit, which I can calculate which, by the way, I did, and it's not very much, but still and two, what is my target?
00:20:16.781 --> 00:20:22.861
Like they want filters, tell me what level of air filtration do you expect me to have?
00:20:22.861 --> 00:20:30.611
Only then I can narrow down a technical outline of a solution that will take the concentration from point A to point B.
00:20:30.611 --> 00:20:38.509
And at this moment the discussions pretty much never followed because it was impossible to one narrow down the initial conditions.
00:20:38.509 --> 00:20:43.646
It was already hard, and the more we narrowed them down, the more it looked like we don't need filters.
00:20:43.646 --> 00:20:49.250
And the second thing was they were just unable to provide me the target.
00:20:49.509 --> 00:20:52.843
Exactly that's the problem In the large infrastructure project.
00:20:52.843 --> 00:20:59.934
If you have your objectives clearly defined, what you need to achieve, you have already finished half of the job, believe me.
00:20:59.934 --> 00:21:04.868
Because they are not clearly defined, they are sometimes just not available.
00:21:04.868 --> 00:21:05.483
Sometimes it's worse.
00:21:05.483 --> 00:21:06.270
They are sometimes just not available.
00:21:06.270 --> 00:21:07.259
Sometimes it's worse, they are contradictory.
00:21:07.259 --> 00:21:12.807
They've been recommended in multiple sorts of documents and they're contradicting with each other.
00:21:12.807 --> 00:21:14.385
So that's another thing.
00:21:15.279 --> 00:21:18.029
And for resilience or property.
00:21:18.029 --> 00:21:20.868
How do you quantify the targets?
00:21:21.321 --> 00:21:23.730
At the end of the day, we are a human being.
00:21:23.730 --> 00:21:34.500
We try to do as much as possible to keep the risk as low as as possible and but at the same time, we are also consultant, we have a contractual obligation.
00:21:34.500 --> 00:21:41.982
I mean, we should not be, we should not driving our thoughts by how we feel, but what is the right way of doing?
00:21:41.982 --> 00:21:45.711
If there's a way exist, so also in this project.
00:21:45.711 --> 00:21:49.165
I'll give you a nice example, without quoting the trend and the project.
00:21:49.165 --> 00:22:05.573
So we did a projects in middle east and we made the life safety requirement and if there are any property protection or resilience requirement, the client should tell us right, because you are, you are the operator, owner of the facility.
00:22:05.573 --> 00:22:09.570
You must know what you need to protect and what is your resilience.
00:22:09.570 --> 00:22:19.607
If you tell me that I'm supplying from this cable tunnel to a facility which should never shut down and this is the only source of supply, then I know that what you're talking about.
00:22:19.607 --> 00:22:22.067
But these details are never available.
00:22:22.560 --> 00:22:23.665
How would you define resilience?
00:22:23.665 --> 00:22:26.068
Perhaps we should define the term for the general audience.
00:22:26.700 --> 00:22:26.980
Okay.
00:22:26.980 --> 00:22:33.406
So resilience is like, in a very simple layman's language, not having a single point of failure.
00:22:33.406 --> 00:22:49.667
Resilience to me I mean you can grow in a more complex manner, but in simple words, like if you take an example of that heat throw shutdown for 24 hours from a substation fire probably it was a case of resilience was not afforded to the project In some way.
00:22:49.667 --> 00:22:55.454
I'm not saying that it was not there, but it was not completely afforded to the project in that case.
00:22:55.454 --> 00:23:16.070
So if you have a single point of failure to a facility or to a function which is absolutely critical for an important reason, like it could be a connectivity to a country, it could be a strategical project or location or tunnel, or it could be a power plant which you cannot afford to shut down for even for a few hours.
00:23:16.070 --> 00:23:23.988
So in that sense, you need to tell us that, guys, we have this tunnel supplying to this critical facility and this northern end sea.
00:23:23.988 --> 00:23:29.512
If that's the case, we have a number of other ways to incorporate that resilience in the same project.
00:23:29.512 --> 00:23:35.112
But of course it will everything, every request will add up some sort of cost, right?
00:23:35.112 --> 00:23:42.134
So while every client is pushing towards a cost-effective solution which is fair and fine in all respect.
00:23:42.134 --> 00:23:46.826
But then if there's no clearly defined objective, we just can go a little far.
00:23:46.826 --> 00:23:56.067
So we ask them a number of times to the particular client that if you have any requirement for resilience of business, sometimes it comes from insurance.
00:23:56.067 --> 00:23:59.369
So if there's an insurance requirement, do let us know.
00:23:59.369 --> 00:24:00.625
But we just navigate it.
00:24:01.200 --> 00:24:20.704
And then, interestingly enough, we had a third representative who raised this question at the very last hour of the project, that we are fully okay with this project, that you meet the life safety, but have you made your client aware that there is a limited property protection or the business continuity or resilience offered by this design?
00:24:20.704 --> 00:24:25.452
I wow, someone is talking my language, so I got happy.
00:24:25.452 --> 00:24:31.951
But the problem is we welcome all sorts of inputs to the project, but it has to be the right time.
00:24:31.951 --> 00:24:33.622
And how would the client see that?
00:24:33.622 --> 00:24:42.872
So, while it was a very good point to be made as an authority representative, but as a client, it just became like it seems like someone has missed the spot completely.
00:24:43.401 --> 00:24:47.571
And then we have to go in depth and telling them that how it works.
00:24:47.571 --> 00:24:58.769
And then we explain no, we said this, we asked this, we never get the feedback and we assume this, this, this, this, and therefore we end up in this design.
00:24:58.769 --> 00:25:02.202
Even now, if you tell us, like what is the objective, we're happy to incorporate.
00:25:02.202 --> 00:25:08.873
But the answer was okay, we'll come back to you and like incorporate, but the answer was okay, we'll come back to you and like, as you said, they will never end up in.
00:25:08.873 --> 00:25:15.049
Like you're not coming up with a clearly, uh defined object at what they need to achieve, because there isn't one.
00:25:15.049 --> 00:25:17.964
They have to work with different stakeholder of that project.