Underground Digital Twins

We all have used 3D maps. From Google Earth, to Google and Apple Maps, to Esri, Mapbox and others, we are very used to seeing 3D buildings rendered on our devices. But think of the iceberg analogy…

Below is a bigger deal than above…

Icebergs are so much bigger than they appear. This is the case with the built environment. Look out your window and you see a complex city. But what you don’t see is what is below. We know that these underground assets are hit on average every 60 seconds in the United States which costs over $1B dollars in losses. What we can’t see is costing cities and developers money that could be better spent on making these cities sustainable.

But getting a hold on this issue is not easy. The ownership of these assets is many times private and those companies do not wish to share anything about what is underground for business or security reasons. Plus even if sharing was something that interested people, there isn’t a good unified underground model to place them in (we have many of these available for above ground assets). But there seems to be some progress in this area. Writes Geoff Zeiss:

At the December Open Geospatial Consortium (OGC) Energy Summit at EPRI in Charlotte, Josh Lieberman of the OGC presented an overview of the progress of OGC’s underground information initiative, with the appropriate acronym MUDDI, which is intended to provide an open standards-based way to share information about the below ground.

The part that gets my attention is that MUDDI model is intended to build on and be compatible with many existing reference models. This is a big deal because many of the stakeholders in underground assets have already invested time and money into supporting these. As Geoff writes:

MUDDI is not an attempt to replace existing standards, but to build on and augment existing standards to create a unified model supporting multiple perspectives.

I’m totally on board with this. Creating a new model that handles all these edge-cases only will result in a model nobody wants. As we work toward integrating underground models into Digital Twin platforms, MUDDI will be a huge deal. It’s not ready by any means yet but because it support existing standards everyone can get involved immediately and start working at creating underground digital twins.

January 10, 2019 bim Thoughts underground

BIM vs. Digital Twin

The thing with BIM is that BIM models are VERY complicated. That’s just the nature of BIM. People talk about digital twins all the time, and BIM (as an extension of CAD) is probably one of the first representations of a digital twin. BIM though by its nature isn’t an “as-built.” It is just a picture of what the real world object should be, where-as a digital twin is a digital copy of an existing asset. Now the best way to start a digital twin is to import a BIM model, but there are some areas you need to be aware of before doing so.

A BIM model might not be an as-built. As I said above, BIM is what something should be, not what it ends up being. During construction, changes are always made to the building, and in doing so, the BIM model ceases to be a digital twin. Just importing a BIM model without field verification can result in your digital twin not genuinely being a digital twin.
What detail do you need in hour digital twin? A BIM model might have millions of entities making up even a simple asset, such as a window frame that is unique and requires high accuracy. This is very important in the construction phase where even a millimeter off can cause problems, but for a digital twin, that detail is not needed. This is where BIM and digital twins diverge; the BIM model is the engineering representation of something vs. a digital twin is just the digital replica. There is no reason why you couldn’t import in such an elaborate window frame of course, but throughout a whole building or even a city, these extra details get lost in the LOD. The key here is knowing what your LOD is and how you want to view it. There is much going on in the 3D space where you can use LOD to display the elaborate window frame above, yet still be performant where needed.
Aftermarket features are generally part of a digital twin. BIM models are idealized in that they only show what was spec’d out. Digital twins need to show all those modifications that were made after the building was turned over to the owner. Doors removed, walls put up, windows boarded over. These things all need to be reflected in your digital twin. Just importing a BIM model that doesn’t address these changes means that when you go to link up your digital twin to IoT or other services, there is no one-to-one relationship. Preparation work of that BIM model before ingestion into a digital twin helps immeasurably.

It is easy to want to jump into creating digital twins of your buildings but it is critical to make sure that before you do so you’ve review your files to ensure that they are as-built and a twin of the real world asset.

January 8, 2019 bim Thoughts

BIM vs. Digital Twin

The thing with BIM is that BIM models are VERY complicated. That’s just the nature of BIM. People talk about digital twins all the time, and BIM (as an extension of CAD) is probably one of the first representations of a digital twin. BIM though by its nature isn’t an “as-built.” It is just a picture of what the real world object should be, where-as a digital twin is a digital copy of an existing asset. Now the best way to start a digital twin is to import a BIM model, but there are some areas you need to be aware of before doing so.

A BIM model might not be an as-built. As I said above, BIM is what something should be, not what it ends up being. During construction, changes are always made to the building, and in doing so, the BIM model ceases to be a digital twin. Just importing a BIM model without field verification can result in your digital twin not genuinely being a digital twin.
What detail do you need in hour digital twin? A BIM model might have millions of entities making up even a simple asset, such as a window frame that is unique and requires high accuracy. This is very important in the construction phase where even a millimeter off can cause problems, but for a digital twin, that detail is not needed. This is where BIM and digital twins diverge; the BIM model is the engineering representation of something vs. a digital twin is just the digital replica. There is no reason why you couldn’t import in such an elaborate window frame of course, but throughout a whole building or even a city, these extra details get lost in the LOD. The key here is knowing what your LOD is and how you want to view it. There is much going on in the 3D space where you can use LOD to display the elaborate window frame above, yet still be performant where needed.
Aftermarket features are generally part of a digital twin. BIM models are idealized in that they only show what was spec’d out. Digital twins need to show all those modifications that were made after the building was turned over to the owner. Doors removed, walls put up, windows boarded over. These things all need to be reflected in your digital twin. Just importing a BIM model that doesn’t address these changes means that when you go to link up your digital twin to IoT or other services, there is no one-to-one relationship. Preparation work of that BIM model before ingestion into a digital twin helps immeasurably.

It is easy to want to jump into creating digital twins of your buildings but it is critical to make sure that before you do so you’ve review your files to ensure that they are as-built and a twin of the real world asset.

January 8, 2019 bim Thoughts

The End of GIS

So yea, link bait title, sue me. But I felt like it needed to be there. But before I go into what that all means, I’m going to continue blogging over on Medium but with a new focus. The RSS feed, email blasts, and Twitter account will cease to produce original content.

So why is there an end to anything? I’ve been working toward this end for some time, the focus has been to move away from proprietary stacks and toward open source. But there is a more significant theme to this. Pivoting away from specialized software that is good at one thing, towards libraries to get things done. Regardless I’m now working at a company that specializes in aggregating, analyzing and visualizing 3D data. GIS has been useful at many things, but 3D was never one of it.

The start of Spatially Adjusted happened over the course of a family vacation to my wife at the time’s in-laws in rural Texas. I can’t recall exactly what made me start, but it was the intersection of Esri and Open Source. This was pre-OSGeo, things in my life were still ArcGIS and mostly ArcIMS. There was a ton about me being excited about EDN when that first arrived and unboxing ArcGIS 9.1. But I was getting into open source. In fact, the first time I blogged about PostGIS, Sean Gillies was quick to put me in my place. Because of course I was a big Esri supporter, and all he saw was someone complaining about the quality of the software.

My blog has a big story arc in it. I go from “Esri blogger” to “Esri hater.” Early on I used to get Esri passing me info to get the word out. The reality of this was there was no Twitter or Facebook yet, so the only place people could be open was my comments on my blog posts. But over the years I grew bitter about the software. I grew tired of competing against Esri on contracts. I became angry at software being half-baked and having to rewrite things every few years. Look, there was a ton to like about the Esri Web ADF… No wait, there wasn’t. I’m sure people worked very hard on it, and they probably take it personally when I call it a POS but it was. Engineers aren’t at fault for creating the Web ADF, Esri marketing is at fault for choosing to push it.

I honestly could write pages on why I dislike things about Esri but I won’t. I’m honestly over it. I look back at ArcObjects, MapObjects, Web ADF and the rest and I feel like it was a different person. I cannot picture myself doing that work anymore, and that’s OK, we all grow up and grow into what we enjoy. That’s the big picture through this journey, being open to change. The “threat” of Google Earth, the “threat” of open source, the “threat” of the ELA. All irrelevant in the end. The most prominent part of our professional lives is our ability to handle change. Don’t assume anything, just look for ways to improve your workflows, provide better service toward others and be proud of your career.

Throughout this journey, there have been a couple people who have affected great change in me. Early on I can only think of two people; Howard Butler and Sean Gillies. Both forced me to look at how I perceived open tools such as GDAL, UMN MapServer, and PostGIS. Sean more than anyone called out my proprietary bullshit and while I didn’t agree with everything he said, it did open my eyes. Later on, blogging brought me into contact with more developers. People such as Bill Dollins, Dave Bouwman, and Brian Flood. The work they were doing, even in the Esri ecosystem really helped me grow. Even inside Esri, the creation of EDN and the DevSummit introduced me to Brian Goldin, Steve Pousty and Rob Elkins who basically made the first DevSummit my Woodstock.

I also can’t stress enough how many people I’ve met over the years because of this blog. Not a conference goes by where someone introduces themselves to me and tells me they follow me. That means a ton as personal networks is what drives us all. It has been those who introduce me to the fantastic stuff they are working on that inspires my passion. But that is why I think my story arc went from “Esri blogger” to the intersection of 3D BIM and GIS.

I really can’t think of anyone I’ve met over these years I don’t have a ton of respect for. From Art Haddad pushing ArcGIS Server to be something more than a hacked together project to Jim Barry always making sure I could find the right documentation or developer help, I’ve always been lucky enough to find the right person to help out. I really could go, but everyone should know what a great asset you are and still will be.

So what now for me? At Cityzenith I’m focused on building the platform that the real estate and AEC industries can use to make a better world. This blog has been on so many different platforms over the years. Best I can recall the progress went; Blogger -> MovableType -> Wordpress -> Octopress -> Wordpress -> Github Pages -> Wordpress and rather than port it over to yet another platform I think it has earned the right to relax. Just like PlanetGS.com got to retire in dignity, so will Spatially Adjusted.

So follow me over at Medium where I’ll be talking about Elastic, Unity, Mapbox, Turf.js, Tippecanoe, Safe FME, 3D formats, AWS (including Lex, Lambda and Comprehend) and using Unity inside web browsers and mobile devices. Should be a blast!

So I think I’ll just leave this here because it is how I feel.

GIS has been won!

July 17, 2018 Thoughts