Hey,
At Statnett we’re thinking about our progress towards a world of more flexible data models. Although your introductions have been great, we’re still confused about the particulars surrounding the transition between types of models.
In particular, we consider the lineage of and managability of transformations of data. In the language of your data-modelling: we want the arrows between Source, Domain and Solution models to be versioned and configured as code. Is this a planned feature? If so, do you have any sketches of how this will look?
Transformations might be what we call “Interfaces” in the Domain and Solution models. I.e. the physical transformer from (e.g.) Siemens is implemented by a functional 300kv to 132kv transformer at the Substation “Foo”. Currently, we model this as two assets (phys. trafo and func.trafo) with a Relationship with label “Implements”. These relationships are more or less hand-crafted. But, we would like to have these mappings, and links, as code. Preferrably so that when a new trafo is loaded in the source, a new instance would appear in each Domain and Solution model. Updates would also likewise preferrably be bubbled up through the models.
Thanks for your response :)