Unlock the Full Potential of Your MEP Data: The Case for a Unified Data Model

A big inefficiency in MEP design lies in communicating data between disparate design software. What if all of these applications could communicate seamlessly with a single data model? This class will showcase a solution in which disparate applications communicate via a common schema (GraphQL) and a cloud database (Neo4j). Introducing the design-as-a-service concept, we’ll consider the huge potential unlocked by moving the primary data model from Revit software to a connected cloud service. We’ll see how a common data model can store data beyond that which can be stored in the Revit model, and explore how you can easily integrate your own apps and services. Examples will include integrating an electrical calc service, and how the cloud data functions as a digital twin, where live sensor data is visualized within the Forge Viewer. Finally, we’ll consider how we can work together to further define and improve the data schema as something we can all own as innovators in MEP design.