Creating Intelligent Digital Built Environments

PRESENTER 1: Today, we will be trying to talk about creating intelligent digital built environments. It's a very important day for me because it's the first time I will be presenting in AU and to be sharing our experience with you. But also, it is my wife's birthday today. So it is recording I want to say happy birthday, my darling. I love you. And I hope this will fulfill your expectation for a present from Las Vegas. It is all I can give.

AHMET CITIPITIOGLU: Probably not.

PRESENTER 1: That's right. OK, thank you again for all of you spending your valuable time with us. So these are the course description. Most probably, you have already seen this one, and it's widely was during the design and construction phase of our industry. It is adapted now.

Today, we will try to go a future user of the BIM through an entire BIM life cycle of the facilities. And we will try to achieve something like Google Maps, Google look-like searching engines for your facilities. So these are the learning objectives. We will go through our process details-- how we work. We will go through the challenges-- some of the challenges we have completed and sold.

Some of these challenges are still pending. We will share them with you. Also, we will share all the experience, successes, and stories with you. At that end, we will try to achieve a platform to platform that we achieve, which we call Google-Like browser of your facility.

For a quick introduction, we'll not just spend so much time there. So I am a mechanical engineer working for 20 years in this industry. I attended over 200 trainings, volunteers activities, and especially these are the ones that I enjoy most. Yes, I believe MAP is the most important part, especially BIM, but BIM-FM integration is the most important part. And who wants to talk about LOD? I will be very happy talk after the class but mark to understand what is LOD.

And my company for working for five years. We have around 8 million square meters. So it makes around 86 million square feet project reference asbout BIM. We are doing on the BIM-- BIM consultants and BIM service providing, and we are trying to implement BIM really in the project, not through the fancy pictures. These are the international-- some of the project areas that we are working, and I will just hand over to Ahmet to introduce himself.

AHMET CITIPITIOGLU: Good afternoon. I apologize for my voice. My name is Ahmet Citipitioglu.

I am the engineering and design director for TAV Construction, and I been in the consulting and construction industry for 20 years. My first BIM project was in the early 2000s in the Bay area, and things has changed since then. And primarily, right now, we're focused in airport construction, design, and operations.

And we're leading the push for digitization in our organization for all phases of these realizations for these projects that we're working on. A quick intro for TAV itself-- TAV Group is an airport company. So our primary business is public/private partnerships building, designing, and investing in airport operations.

Our flagship airport is the Instanbul Ataturk airport that we started working on in 2001. So it's a relatively new company. And we operate 19 airports, based on concessions on the build, operate, and transfer model. And we have every single functional company that you can imagine that's involved in serving airports-- security, duty-free food and beverage, and so forth. And I work for the company on the right, TAV Construction, which is the company that basically builds everything for the operations-- airports and related.

In general, as I mentioned, we design and build the airports and partner together with our parent company [NON-ENGLISH SPEECH] in Paris. We've serve more than a quarter million passengers a year around the world. And combining all these together, well, TAV Construction in itself, in the last three years, we're the number one airport contractor in the world, with all the projects we've been building around the region in the world. And we'll be talking about some of these projects in this presentation.

So we build large airports and tall high rise buildings and anything that's big or wide. And to combine the know how of all these, we basically put together a small group called within our company deemed integrate solutions, which basically tries to integrate all our know how with all this technology together. And this is kind of a short overview of all the applications that we've been gaining experience in the last four to five years.

So anything from construction onto or a phase which is where we prepare the airports for operations readiness. And obviously, the main focus for today's is the facilities management part. So anything we've touched on, and we're hoping to combine it all as a standard practice for all our airports in the near future. So not as much as Daniel, but we've been basically involved in more than 6 and 1/2 million square meters of built environment, which actually exceeds the amount of airports that we built in the last years.

So the structure of our talk today is going to basically be on why we're doing all this, how we do it, and then what exactly we're trying to achieve with implementing all these tools for the built environment. So this is just a small snapshot of some of the ongoing projects that have extensive BIM scopes and extensive FM scopes after hand over. The most prominent one being here is the Abu Dhabi Midfield Terminal Airport.

You see all the renders the actual models ongoing and the current or near the current site conditions. We're going to be opening this in 2019, I believe. We just completed this high rise in Istanbul, this multi mode, this office building for ADP in Paris. We just started the Bahrain Airport.

So all of these projects has some BIM FM scope but extensive BIM applications for projects. Just to give you an idea, this is nearly a million square meters. And from here to here, that's about three miles from one end to the other. So these are pretty large projects that we're working on in the region.

The base of the case study for us that will be basing most of our talk today is the Medina Airport, where we basically did the BIM-FM integration and this is now going to be a case study for the new addition of the BIM handbook coming out by the end of this year. And pretty much anything that was built on-site is in the model, and we integrated it into the CMMS database. So all the facility management workflows are now integrated with the model that we created.

Now going on to the why. I mean, the one obvious thing is contractual purposes. But for us as a company that is involved in designing and building and operating these, it makes sense to make use of this technology, obviously, for commercial purposes, especially when we build all this infrastructure.

We're going to be operating them for the next 20 to 30 years. And all this data-- there's a lot of value to actually put it together and use directly from construction. So this is something probably we're all familiar with.

And actually, this gives a good business motivation for it. And this is maybe for roughly a schematic view of the breakdown of the cost and time of a 30-year investment for a maybe 200,000 square meter airport, where you would have the time and effort gone into the design and construction, compared to the operations. And it just makes sense to actually invest in all these tools that we have for construction out into operations.

And this is roughly to scale so it gives you an idea of where the money is for all this stuff. And we'll now kind of shift on to the how part of what the process is. And then we'll follow on with the challenges and then with the what have we actually achieved and what we're trying to do. We're still working on making it better.

So this is one of my favorite slides. You may have seen it from before, and we're basically not just building physical buildings, but we're actually building digitally as well. And this is a pretty nice representation, I think, of it. And we've talked about the data.

We look of what we think of data on the site looks something like this. And so this is a snapshot I took when I was on site in Medina maybe five years ago, and it made me think of what the value of this drawing would be for operations, if it would be available at all. And I guess this is some common issue of having all these up to date and available. Usually, the problem is not only that they're aren't accurate after five years because airports are very dynamic buildings. They change a lot-- almost continuously.

It's just that you can't even find them most of the time, unfortunately. And talking about the data or information-- this is just to break it down to kind of give some context of what we're talking about. This is applies for not just BIM or anything but for pretty much anything in construction where we have some drawing or information from site that's captured and stored and shared and integrated to some system. But even if we do a good job on creating things and storing them, we have some ways to go with actually integrating them to make them even more useful and extensible for other systems.

And on the implementation side, again, this may be familiar. It's all about the people. The technology, I think, is there nowadays, especially with all these new tools 10 years ago is quite difficult to handle these big models-- maybe with on the hardware side. But the actual challenge is getting the process and the people, and we'll talk about that as well.

But at the end of day, even if you have all these together, it's a matter of execution. And having talked about execution, when we talk about putting BIM models for FM, actually the challenge starts right after you have the model.

As I mentioned, airports just don't stay static. Even by day one, they change continuously. And just to give you an idea-- since I started working at TAV in Istanbul, our headquarters, we've had our fourth extension for the airport in the last four years.

And so that's adding more and more to the building itself. And so you would need, not a BIM execution plan for just the modeling part but how to think about in the future, to future proof the existing models. Five years from now, what do you do with the models that are built in. Revit 2015? Who's responsible for that?

How are you going to get the new models that are created from the new projects or changes? These are continuous things that need to be assessed and documented. Otherwise, you'll have all these models that don't talk or work with each other. So the document is kind of an encompassing document that covers all the phase looking forward for operations, and the relationship would be something sitting at the very top of all these different projects that will happen throughout the lifecycle of the airport.

Again, I haven't seen an airport that hasn't changed in a long time. So you'll have all these projects, whether they're extensions or internal projects, that will have a whole new design team, a whole new different contractor, and a lot of different subcontractors sitting-- each having their own BIM execution plans. But the idea is making sure that whatever we get out of those models are easily consistent and compliant with basically what we're trying to integrate into our existing system. So Dan will talk about LOD 500 because that's usually where we end up talking about when we talk about FM.

DANIEL: Yeah. Actually contractual and academically is asking you I want the LOD 500 model for the fan. So, yes, there is a LOD 500 model in the documents of contract. But, sorry, there is not an LOD 500 model.

It's not I am saying that [INAUDIBLE] from the document, for example, to an 817 which is issued this month. In the item 112, if you look it is clearly stated that there is no such thing as an LOD 500 or 400 model. So you cannot say a model itself totally is a level of 500 or 400. You cannot say mechanical, electrical, structural models are LOD 500 or 400. You should go element wise.

So what we are doing for this purpose is we are preparing the LOD matrices. You can see [INAUDIBLE] LOD matrices in the left hand side. You will see an LOD matrices being prepared for the columns. And we can define all the visual and parametric requirements that we want in this document. We are attaching these documents to the BIM execution plus. So contractors, client knows what they will be getting and what they will be preparing. There is a mutual understanding.

In addition, for MEP specific we are preparing system tables. So the systems that you will use, how they will be modeled should be defined and attached to the BIM execution plans also. With these documents, again, everybody having mutual understanding. In that case, we will go the detail of the system definitions. But you should be careful what FM staff understands from the systems and what you are defining from the system. So the feedback will be very good from that.

Going forward if you Google the BIM, you will definitely see in the first 10 results of cycle like this, a similar view. It is always talking about the central model, and everything is working around this model. But it is really oversimplifying what we are really doing over-- for projects we chart bigger than midsize projects.

Because you are updating the models. Every discipline are preparing their own model. You are preparing models for level [INAUDIBLE]. You are prepaid model for client presentation, for coordination, for 4D. For 5D we are preparing different models sometimes. So it is not always the case that we are having a central role model in our hands, and it is continuously reviving.

So this sketch is coming from the [INAUDIBLE] from [INAUDIBLE] in 2012. It is more likely showing what's going on in our processes. We are updating, changing, collaborating and making coordination. Getting combined models, separating them. And this cycle goes on and on.

The problem here that we are facing is which model, which place, we will put the data. Which place we will put the FM data. Is it that model, that place that we have to put, or which revision? Because if you go to the-- document wise it is very clear. There is the one model. Everything is in the center, in the server. You can do it.

But it's not the case. So we have to find the right place that we will be putting the FM data. And if you are planning-- and you should-- make a BIM execution plan in the beginning. And it should be a paragraph. Just mention your goals, why you are using BIM processes in your project or your company. So you should start with that in mind, it is for sure.

This slide is showing two things. One, LOD is not a phasing issue. So its an LOD 400 is this, 500 is this, and 300 was this. So it's not a phasing issue. But more important, there's a misunderstanding. And it is rarely the case if you update your model based on the sight progress continuously, at the end of the day one click you will have a as-built model. It's quite not possible.

So there are many plug-ins, add-ins that you can do to update these things. But as a client, if you are looking at this perspective, you should start with the end of-- [INAUDIBLE] in the mind. Otherwise, you should face remodeling, and lots of problems in your hands. So how we applied this process, this organization?

AHMET: So the idea is obviously for these very large projects. It's not something that you can just take the as-built drawings and model. This is a schematic, a typical organization that we set up on our sites. Where you'd have your coordination team on site under the design manager with all the disciplines, and a layer of coordinators on site with the modeling team. Which basically are creating all the drawing models during the project.

And typically on these projects, we'd have mechanical and electrical subcontractors, or nominated subcontractors, that we keep at arm's length. Because contractually, it's their responsibility to take care of most of the coordination with our team together. And you have this big red box where you have these teams working together continuously on a weekly basis coordinating these models.

And that's some of the challenges, especially when you have a lot of information nowadays. We actually have a information manager to keep track of all these. Otherwise, you know, the coordinators and the BIM manager themselves are trying to put all this FM data together. Otherwise, at the end of the project it's not really feasible to actually think that you could sit down and put it together at the end of the project. You have to plan for it and organize it.

And this is a typical flow chart, a weekly flow chart almost. On most of our projects where nowadays we're required to have the coordinated model before we can actually even execute the shop drawings. So you would have new drawings issued for construction, specifications, instructions uploaded. Create your matrices or elements as you go through the modeling. Revise the modeling as necessary.

Do your coordination. Have your weekly coordination. And get your approvals for the areas that you can do your shop drawings. And it's an on and on cycle where you have this almost maybe three to four meetings with different groups, and then a general meeting weekly.

So LOD how this kind of fits-- contrary to what he says-- it's not a phasing that's correct. But at least to explain to our clients or to-- you know, when we have our projects to kind of give an idea. Because there's always that confusion or LOD is always used as a crutch, you know, just as a number out there.

But to give an idea of what we're talking about, you know, compared to the different phases is actually we kind of-- at least personally in our own organization-- consider an LOD 300 that comes out from the design team. And in most cases we don't even consider them as BIM models, because they don't have the content. And we may consider them as a DIM model, as. A dimension information model that's both contractually. And both for us-- most of the time we actually end up recreating the models anyway, because we need to embed all the naming and content the way that we want to put it for the FM people.

Because most of the time this isn't really considering what's happening in the end. And during construction really there's a lot of things that-- in the content-- that doesn't really come up here anyway. Because unless you procure something or get your approvals for the material, you really don't know what's going to be going into the model in that first place.

So during the construction phase we'd have our LOD 400's being updated, and then validated. Updated based on the as-built conditions. And we have integration. And it has kind of a crude number of people for the average project for an airport. Just to give you an idea of the size of the teams that are involved just in the BIM effort for integration and creating these models and putting them together.

And, of course, as I mentioned once you're done with the project, the models need to be updated continuously. Now, in this case you would have-- in this case for Medina the [INAUDIBLE] buys the operating company. And you would need to have a workflow to keep the models updated during operations. So there would need to be some workflow coming from the site.

When you have any changes-- new equipment or anything that need to be updated-- the models being updated, in this case in our organization, my organization [INAUDIBLE] would be doing the modeling together with the operator team as a continuous review. And this can happen maybe on a two month or six months basis, depending on how you set up the integration with the FM systems. So it's not critical that these are reflected directly into the models. But we'll see them in a few slides down how these are integrated. And you can either choose different paths to update your models and reflect them in your CMMS data base.

DANIEL: So how will we prepare this content? As I said, we shall start with the [INAUDIBLE] in the mind. These are various samples. For example, in the Revit you are trying to make a door. Where you start, you have the cutter for this predefined door. Now, you prepare your family, now you prepare your family type.

And these are generally based on what is coming from the design. The problem that comes here is the hire issue-- or the organization that you are making here-- is generally, or may not be, complying with the FM [INAUDIBLE] registry. So these doors may have a simple organization. But in a few slides I will talk about this organization, how it's affecting us.

And we are having additional attributes for the family stuff, which is mainly manufacturers, on the class numbers, type descriptions, things like that. After this family, we have the element itself. And in our model, we are putting several hundreds of the same element. And the modeling guides are spending too much time-- and are the companies spending most time-- to put that element to the right place.

So that's why-- as Ahmet mentioned-- we need someone to manage this information. I mean, most of you may know if you have one duct piece in a Revit model. If you put that duct you have 100 parameters directly in the duct itself. So 's information that parameters should be managed itself.

And these are the same parameters which are unique for the element, that you have to put. Can be room name, room number. We will talk about the systems which are critical when you go to the FM site. But going back the operation-- sorry-- going back to the organization that we are making for the door that we talked cannot be complying with the FM in something like that.

If you have a [INAUDIBLE] in it on the design stage or construction stage, you prepare different families for double stories. You prepare horizontal/ vertical different. When you can make a parametric modeling, it's not practical to make one model for each of them. So there are different types, different families for you.

But when you go to the FM and if you tell them, this is a unit which has [INAUDIBLE], which has filters. Then they say, if it is big it's [INAUDIBLE]. If it is small, it's [INAUDIBLE]. So if you don't start from the point of people thinking of it from a [INAUDIBLE] registry point of view or data requirement, you may require to put another layer, another perimeter, and another management system to your models.

Talk about content that we are preparing-- tagging. This is the most critical part going from the BIM to FM because the text, the unique text. Each element will have-- will be the link that you are taking from your model to the FM.

So there are many ways of making this tag links. So equipment serial numbers. There are classification numbers, which are internationally used. You can use GUID cards. But this tagging that client is requiring during the FM process should be defined in their BIM implementation process, other plan.

Otherwise, you should have to revise and update all your element texts, which you have several million of assets in a model. It's really challenging. And also a quality control is a must on this process.

So in the large airport project, the tagging of one element. For example, there is the 14 levels of information for each element tagging. This is a unique text.

AHMET: Right.

DANIEL: But it has so much information, it's not even readable. So what we advise is if you are trying to put so much information through an element in one parameter of tagging, it's not practical or ideal. You should be using other parameters to tag the elements. And should be human readable and understandable.

What we did for Medina is a sample for the starting of these four levels. We had the system code, subsystem code, room number, and a unique ID. With these four level of information that we are having in the tagging of the element, we were able to uniquely identify each and every element in the model.

AHMET: One issue I guess here is the tagging with the room numbers was one that we faced, especially with equipment that would be recommissioned, de-commissioned, or removed. And that was one of the issues that you need to be considering with FM team, whether adding room numbers or not in the tags.

DANIEL: Yap, you are right. I mean, these rooms, rooms, rooms they are challenging. So generally it is very practical. You click in the area, the room is there. You have only one button sometimes. It puts automatically all the rooms in the model.

But if you are going to the FM with this room, it may not be the case. Because you should take the volume and the right volume. So when you look here, it's the gate that's going in the airport. The room volumes that you have to define may be different.

And you have to think in the ceiling voids. Because you want all the equipment in the ceiling voids. You have to think about risers. You have to think about the shelves, how you will make this area. Because you have to find room with every equipment and tagging based on these walls.

More important the numbering and the naming of these rooms. Because even if they change in the design and construction stage, most of the people that are working in construction knows it. I mean, entire construction cycle the mechanicals floor is 20th floor. And when they finish and you want to go to the hotel, the mechanical room goes to the 15th. So all the room names and numbers may vary. So a good quality control for the room naming and room numbering is a must.

Then systems. So what if some drive wants to see if they select a grid? In the model, they will be able to see all the routing going to their handling units. Or if they select a functional unit, they should be able to see all first wall, shut off wall. They should be able to see first [INAUDIBLE], where is it?

There is no automatic system definition that you can use in the softwares. But if you are going over a midsize project and you have many files it's not-- you cannot use that system definitions. So you have to have another layer of information to manage all the information in the complex facilities.

Why? Because, for example, in a true unit-- as you see here-- have minimal four air system and two pipe system. It will have additional electrical systems. So all these systems names that is coming in the second pavement, going to the third floor should be uniquely defined. And what we did is we defined different parameters for defining all the systems.

So with the [INAUDIBLE] that we develop, it was very practical in each model update the naming of their systems, and getting all the data visually available. And also when you are doing the name of the systems, the systems that you use in design and construction generally are not the same, the system and zoning understanding of the FM. So that feedback will be very good for that one.

But it's not only vision information. So if you see the sprinkler here and the sprinkler was shut off [INAUDIBLE], it's also very important and valuable information. You may have heard about the story. There was a fire and a sprinkler system run, and they couldn't find the shutoff valve for 30 minutes. Everybody everywhere as wet, even when the fire finished because the staff was on vacation.

AHMET: And that happens more than often, actually.

DANIEL: Yeah, it does. So that's why it is very important to find and to get the right information in the right place. And it's not maybe so much important and so much critical for some size of the project. But if you have over a million square meter, and if you have 200 walls for clothing and you have to find the right ones to close that sprinkler system it is really extremely important information.

And we should bring it to the user in one click. And it is our responsibility to press million right clicks before getting that one click working. So about the process that we are preparing and getting all this data available, I think you may five some information about the challenges that we have facing through this process.

AHMET: Sure. First and foremost we mentioned the motivation of actually having to do this work, aside from TAV, which serves its own purpose as we are designing and constructing airports for other clients. And one of the most critical thing is the specifications.

So the top two boxes are basically the BIM specification, or the only information of the BIM requirements in a multi-billion dollar project. And so they are basically saying, just give us a Revit model at LOD-- as built, I think, somewhere at the level of LOD 400. Where there is no definition of what LOD 400 was, or what they were actually intending to even do with the model.

And similar to all the buyer's remorse, its always a discussion at the end, well I want to use this for facilities management. How do you actually update and actually contractually come to a position where you can actually accommodate the extra cost or the work overhead to revise all these models? On the opposite end of the spectrum, as we have projects that have maybe multiple volumes of BIM specifications. But at the end of the day, you look at that there's really no use defined in them. So it tells you how they want to models put together, but there is really no end to it or integration or intent of what they would be doing with the integration side of the project. Which makes it also difficult.

Now, with whatever scope we arrive with, you know, we need to price it or arrange our organization to deliver these models. And the main issue is to budget it. And if we really don't know what the scope or the expectation of the client is, it's always a challenge for us. Unfortunately, in the market if you're trying to get your resources from external from the market companies, still you would see pricing based on some LOD delivery. Whereas, actually it's a process.

As I mentioned, we're updating the miles weekly. It's ongoing. You just can't say, I'm going to buy a model and then not update it. Especially if you're going to use it for FM purposes.

Another challenge is digital talent resourcing. That's actually quite common here. We're hiring positions that didn't exist a few years ago. And, yet, this is a nice graph showing the lifecycle of an engineer, so to speak, based on a book from a prominent Turkish engineer. And shows the knowledge curve and the experience curve for some-- a new graduate versus some experienced staff. And there's a clear gap between the BIM motivation.

So you have the decision makers on one end that want to build the project on time, on budget. And you have all these new requirements, and all these new stuff. But there's a certain gap between executing this. And so our biggest effort on these new projects are tying the two sides together to come on a common ground. But obviously this will-- as years pass by-- this cap is going to clearly close very soon.

On the design phase I'll just go through some of the challenges of actually authoring these models. The big yellow dots are the different disciplines. And typically we see in the market that you have all these different companies either outsourcing. Or in outsourcing their BIM resources, architects are a bit more ahead of the curve in that.

But this creates a gap between what the model updates are and how that's reflected into the models-- the design updates versus the updates in the models. And obviously the desire would be having everyone work on the same platform with the same understanding. And, again, this will be changing pretty soon.

When you look at the construction side, we have the same issue. This is kind of a schematic office plan between the most undesirable to the desirable configuration. Where you'd have the BIM team on one side and the design team on the other. And this happened a lot on early projects a few years ago.

And the same resourcing problems with the subcontractors having different appointed sub-BIM suppliers. But nowadays-- especially in [INAUDIBLE], for example, we have an integrated configuration, as we saw before. And basically we have people creating the BIM models and doing the design work sitting in the same area in same clusters. That's what makes it much more efficient to deliver all these and wrap all the information together, as the information is becoming available and these mounts are being created. It saves overhead and communication.

And then finally, of course, you want to keep these up-to-date or verify with the site conditions. And this is a typical project that it could be very costly if it's not integrated in the existing construction cycles. And there's many things.

Just because we're doing BIM doesn't mean that we're not doing all these construction cycles anyway. There's a lot of resources already where they're snagging handover checks, testing commissioning. Where you actually have use for all the models information. And just it's a matter of integrating mutually. Where you can have all this information pumped into the mobile devices, or at least on the checklists. And then when these checklists are being executed, you could feed back the existing conditions.

And same for operations. This is kind of the way we set up our validation for the as-built models verifications. So it's a matter of not trying to put new cycles, but exist-- use the existing construction cycles or workflows. Now, let's talk about putting everything together. We know we have all these challenges. But what are we trying to achieve, and how do we end up doing it?

And I guess the first discussion where do start and what's the roadmap to do it if we want it put all things together into integrating with FM systems? And we have the first phase of just regular putting together-- the execution plan-- as we mentioned. Not the modeling execution plan, but as an organization, how these models are going to be used. How they're going to be updated.

What are the requirements? What are the requirements in the BEPs or the BIM execution plans for all the people creating these models? If you have existing facilities, these are pretty typical for these new BOP airports. Where you have an existing airport. You take it over you build a new terminal. You operate the existing infrastructure as well.

So you need to integrate this. This is the case in [INAUDIBLE] as well. There's three terminals. We're building the fourth. So they want their existing terminals to be integrated with all the new BIM work being done. There's also a lot of work to actually create those models of those existing facilities as well.

Then the content integration, what platform is going to be used? And actually taking the data in from the models into the asset or CMMS database, if we're just populating for that. And then finally, we'll talk about the JS uses of both the BIM information on site, how you integrate would integrate that. What type of use cases you would have.

What type of interfaces you would need. How would you integrate them with existing systems? And, of course, you have trading. And the most important, keeping that cycle platform up-to-date. And-- oops, there you go.

So we don't want to integrate everything together. Interoperability is key. And in the early days, we'd always think that BIM would be the central hub of all the data, but that's not always the case. It's a strategic decision between where you keep the data. Do you sync them together? Do you have the systems talk to each other?

But the idea is there's different scenarios that you can fall through. And we'll talk in a bit more detail for what we did actually in Medina. But the idea is having all these systems talking to each other. But I think the key is when you talk about the asset or the information self, BIM is the ideal medium to actually create the data.

But how you consume that data is another issue that we'll be talking about as well. Because 3D models aren't always that practical to interact with all the time, especially when you're on the site. So this is the infrastructure for the site people accessing the BIM model and the CMMS models.

So you would have the BIM servers, the CMMS servers served over the [INAUDIBLE] of the airport. And we'd have the CMMS and integrate the integrator here. In this case, we're using Ecodomus and Medina to serve the data. Where the two systems are talking to each other having their own domains, and they're sharing the database on the tag information. So, Daniel will walk through the different platforms and kind of some of the outcomes of these different platforms that we're looking at.

DANIEL: Yap. Actually there are an increasing interest in the industry about BIM/FM integration softwares. So I'll talk about softwares, because there are viewers, there are integrators, there are data populators. There are many different softwares.

So we already used or reviewed almost-- nearly almost all of this software's available. And the technology and the tools are coming to market so fast that we have already two new softwares that are on the market that we didn't add here. So here we should mention that some of them have good advantages, and some of them have viewer advantages.

So there is no one right solution. You cannot have only one software and solve your case. If you are-- if you need to a right BIM? FM integration and make your FM working through this softwares. Make your-- build the environment intelligent and digital, you may need multiple of them for a viewer, for integrators different one.

So what we advise is to get someone of the capabilities of this software, who knows the capabilities of your company, what you want to do, and make the right solution. So what we did we use, for example, one of them, which is Ecodemus, for the data population and the viewer. So this one has also additional functionalities like quality control. So you can prepare work orders or mobile applications.

So in the Medina project, IFF was the CMMS software. So the data population was done through Ecodemus [INAUDIBLE]. And it was the gateway that is synchronizing all this data. So this is one of the alternative solutions that you may use in your process, for example.

Another that, again, will, we used was Aconex in the same project. The advantage here was Aconex was used in the entire construction period of the project. So all the documents was already there. It was very easy to link all the documents starting from day one of the projects.

So you already have the contract drawings, all the commissioning documents, catalogs, all the [INAUDIBLE] documents that you are looking for, commissioning, taggings. And we were able to link all documents to the model elements. Yap, it's a very effective model viewer. It is also improving. It takes it through the [INAUDIBLE] format.

They are also saying it's not a BIM/FM integration software for now. But in the long run, what they are looking to be the operation system of the construction. So we may see some future coming from there.

But after this all, we take them to the FM stuff, and they started to use this software. They have all this treated data in their hand. And what came up to us is user experience. So can you please raise your hands how many of you are often using, like, this navigation, Google map applications, for [INAUDIBLE] from some or to others? Does any of you use Google Earth for this purpose?

The problem here is if you have too much data in your hands, it doesn't mean it's the better user experience. Because the FM stuff was not able to find the mechanical/electrical room, which is very [INAUDIBLE] used to go there in a 3D model. But if you open a plant [INAUDIBLE], it was very easy for him to point out the place that he's looking for.

And you know these MEP guys who are making the FM always have that [INAUDIBLE] single [INAUDIBLE] hanging on their walls. And they find everything based on that one. So this experience that come from the FM stuff added value to our platform.

AHMET: So the first comment when we put together this and showed the stuff was this view. And the question was, well, where's my airport? I have my terminal, but I don't see my airport there. And that was kind of an eye opening for us. Because, yeah, an airport's actually-- we have more than maybe 30 different structures in the airport, with all the infrastructure.

So the model itself for one building-- which is a quite large model-- it's not that-- it doesn't really reflect the actual responsibility of the FM staff. And as we mentioned, that had a lot of challenges in navigation. And especially on the mobile devices when you have these big models, it's not that practical to push through these models through the web.

So we looked in integrating with the GIS platform, which actually has the advantages of actually combining the 2D information, or the interface. You will still have the 3D information. And the idea is actually creating the models in 3D with the BIM software. But actually creating different alternative interfaces or experiences through the GIS platform.

So this is a crude workflow of what we put together between BIM and GIS using the information on mobile devices. Where, again, the authoring tools would be within BIM. So all of this would be the proof-- the single source of truth, so to speak-- translating these 2D models or systems or layers into the GIS, and combining the two.

And you will see a lot of the visual examples at the end of this presentation. And making the data collected from the site synchronized between the two. But the work cycle is pretty much from BIM to GIS. This is quite challenging. There's not one simple way.

And there's a lot of things that we're investigating as workflows. Because I said, we're not doing this once. We're doing these continuous updates. Models are being [INAUDIBLE], even during life cycles for the-- during the operations of the airports.

So there are advantages between the two. And there's different mediums that we're able to now share with the models, whether they're 3D or just the 2D. We like to think of this as a digital 2D sheet for the end use for the technicians on this site.