Data transition for a BIM-to-FM process
stand what the source and the destination is for the information as well as the Extract Transform and Load (ETL) process for that data. It’s only by ensuring the process is consistent and reliable that you can ensure the data is also consistent and reliable. In a Federated Model for Information Management, the individual sys- tems that are responsible for the data to maintain their system keep data outside that system. It is sent through a trusted connection. The ETL process moves the information from one system to the Target system. At the Target system, processes are put in place to maintain and upkeep the data. Then the data can be returned to the store system based on information that’s updated from the Target. This bi-directional flow of information was appealing to DIA, which would not have to maintain a third database for storing information. Microdesk ModelStream was the product selected to help build the Federated Model for Information Management. ModelStream allows the information to be mapped between the source and the destination system. In DIA’s case, the source was a BIM model and the destina- tion was the IBM Maximo system. This mapping extracts information, transforms it, and loads it into the Maximo system. The Maximo system information is constantly being updated with new equipment and information. This information can then go back into the BIM model using ModelStream’s functions. This process allows each group to continue to update and maintain the data as needed based on their jobs. ModelStream handles the ETL process of moving informa- tion from one system to the other on an as-needed basis so the BIM process can be updated through the normal established workflow. The two systems are tied together through this mapping but they are not dependent on each other. As the BIM models evolve and standards are developed for data be- ing captured within those models, the mapping file is updated to show where the information needs to go into the Target system. There is a profile for each set of existing models using a different data standard. These don’t need to be updated to the new standard but can continue to
Denver International Airport fills the gap between collecting information and populating the asset management system. By George Broadbent and George Wright
Asset management — or facilities management (FM) — has both a strategic and tactical component to it, with both being vital to any long- term program success. The technical component boils down to two main areas. The first centers on where the information is coming from; the second evaluates how the system will be used to support asset/ work order management. However, there’s a fundamental component in between these two areas that’s often overlooked. This is the area of the region we call a data transition period. Denver International Airport’s (DIA) administration recognized that data transition was a critical component to its long-term success and began taking steps to fill the gap between the collection of information and population of the asset management system. The first look at this process became the need to develop a Single Source of Truth, which is where information would be centrally stored and used to feed all other systems. However, building and maintain- ing a Single Source of Truth system is a complex project and requires systems and controls in place that will constantly update the data from both the source and the destination system so all systems are in sync. About three years ago, DIA moved away from the central repository model for the information toward a shared communication between systems, known as a Federated Model for Information Management. Any information management plan that is developed needs to under-
28
csengineermag.com
january 2018
Made with FlippingBook Annual report