Display Versioning
SF Visualizer supports display versioning in order to show a consistent graphical representation of your Sigmafine Model version when you are working with a Display.
Versioning is a feature of the PIAF that allows to create several versions of a Sigmafine Model in order to record the changes to the plant that the model represents.
When you need to make changes to a Sigmafine Model, such as adding assets, removing assets or changing the connections, you can continue to use the existing Sigmafine Model, or you might decide to create a new Sigmafine Model version. Every time you create a new model version, you also define the effective date from which the model version is valid. By doing this, you can manage models representing your plant along the time.
SFHub Visualizer supports both model and display versioning.
Model versioning happens when multiple versions of the same model are created. Each version is then characterized by:
- An effective date, meaning the date on which the version is set to be used. Each version has a different effective date.
- A different configuration. Every version consists of different elements, connections, etc.
Display versioning happens each time a new display, related to a model version, is converted and imported into SFHub Visualizer. A specific Display is created for each model version, with the Display representing the model content. Each display version is then characterized by:
- A specific model version, meaning the version of the model associated to the display. Each display version is associated to a different model version.
- A different configuration representing the associated model.
It's important to understand that every Display is synchronized with a specific model version.
SFHub Visualizer uses the case time range to identify the right display version to be open accordingly the effective date of the Sigmafine Model version.
Starting from SFHub Visualizer 3.0, display and model version can be created by the user as needed using the display administration features made available by the SFHub Authoring application.
How Versioning is Supported
Every time a display is converted and imported into SFHub Visualizer, the version of the model (the model version and revision that has been synchronized by SF Modeler) is detected. At that time, a data structure is created which allows the different display versions to be associated with the different versions and revisions of the model.
SFHub Visualizer does not support Element versioning.
All displays, related to different versions, must have the same name. Therefore, it is important to note the display name during the conversion and upload.
How a Display Version is Selected
SFHub Visualizer always opens the latest version of a display (if multiple versions have been imported). Following the selection of a case, Visualizer automatically identifies which display version should be used and automatically displays that version.
Similarly, access to the AF Server is performed by executing the QUERY DATE consistent with the selected case.
EXAMPLE: A Model with two versions
In our example, our model has two versions V1 and V2 therefore, it also has two displays. The first version (V1) is the original model with an effective date of 1/1/1970; the second version (V2) is a model revision with an effective date of 6/24/2019.
- If you open a Case having an EndTime that is prior to 6/24/2019 (\< 6/24/2019), the Display with model version V1 is opened in SFHub Visualizer.
- If you open a Case having an EndTime that is equal to of later than 6/24/2019 (> 6/24/2019), the Display with model version V2 is opened in SFHub Visualizer.