Branching and merging

[rssahai]

The concepts of branching and merging are absent from this glossary. Is their implementation for iModels hard or impossible?

---

⚠ Do not edit this section. It is required for imodeljs.github.io ➟ GitHub issue linking

• LINK: Glossary-of-terms-in-iTwin.js---iTwin.js-link-to-docs
• TAG: imodeljs-docs-question
• SOURCE: https://www.itwinjs.org/learning/glossary/

[rssahai]

Use case for branching and merging is a design-build-operate-maintain (DBOM) project that begins with existing survey and as-builts. The environmental permit package branches off during planning while concept design moves forward with new topographic surveys and plans toward a 30% review package. When the environmental permit package reaches its first review milestone, the environmental branch updates its existing and as-built plans with the concept design's 30% review package and continues to move along its branch. The branch-synch-merge cycle, if and when implemented for iModels, can simplify work on projects where environmental permit and concept design efforts need to move in parallel with related but different data sets.

[pmconne]

We are in fact currently working on an implementation of the workflow you describe. More details and documentation will emerge as the design solidifies.

[rssahai]

Looks like the Engineering Component Modeling initiative of the year 2000 (MicroStation/J, JMDL, ProjectBank) has finally found a commercially viable outlet in iTwin/iModel after 20-years!

[MichaelBelousov]

closing as this has been implemented a while ago. It is documented here: https://www.itwinjs.org/learning/transformer/branching-imodels/