Intro Session QA (Jump Start)

[roopksaini]

Captured Q&A from the introduction to the iModel.js Jump Start event on July 14th 2020. In this session Keith Bentley introduced iModel.js. He talked about the key principles behind the technology, and what makes it a truly unique and open solution for your Infrastructure Digital Twin.

Please don't reply to this discussion. If you have follow-up questions or comments please start a new discussion.

[roopksaini]

Q: What is your definition of a large model?
A: When we talk about large iModels we mean entire road systems, industrial plants, multiple buildings and other large pieces of infrastructure. The iModel also encompasses the changes made to the asset over design, construction and maintenance of the asset. An iModel is part of the digital twin which includes data stored in other systems as well.

Q: Question to Keith: What is his view on data standardization and its role in success of Digital Twin?
A: As I said, persistence is the primary factor that determines the capabilities of a software architecture. When people refer to "standards" today, they're typically talking about interchange formats. We propose instead that "standards" for digital twins should focus on schemas that describe the structure, hierarchy, and relationships in the models. Then, the OPEN digital twin platform provides persistence, access, and interoperability.

Q: Large highway projects span large distances and DOTs typically let our segments go to different contractors and/or builder-operators. How would a DOT maintain the digital twin with iModel when each segment may be using a different technology stack?
A: We can synchronize data from many file formats into a single iModel, putting the data from multiple different files in multiple different file formats into a single iModel while tracking changes that happen in any of the source files.

Q: Thanks for the great sharing, Mr. Bentley. If there is an iModel 3.0, what would that be from your perspective?
A: We publish a public roadmap on the iModel.js website that describes the future plans for iModel.js. Here is the link Roadmap, https://www.imodeljs.org/changehistory/roadmap/#release-30.