Add Model(s) to Digital Twin for one Litmus Edge

to add model(s) with litmus excel add ins, you should be familiar with how models work in digital twins docid\ xlj3gvozyg 52ue4pb5u7 on litmus edge before you begin you have installed the litmus excel add ins extension see install litmus excel add ins docid\ gzdhbj1xzznddthyocuuu for details you have prepared a prepare a new tool file to manage digital twin models docid\ ov8snxemrb3nvzjjk6duh initial preparation open a new dt model management tool file in excel if prompted, enable content to allow the code to run make sure the the tool is set connect to is set to one le add models(s) mandatory model settings the two m's provide the following two model settings to start the definition of a model model type select the type of the model model name provide the name for the model notes the tool will verify that the entries for the model name column are unique and notify the user in case the same model name was already used it is recommended to click the compare vs le button to check if a model with the provided model type and name may already be defined on litmus edge if no model with the selected model type and name combination is defined, the row will stay as a for the action if a model with the selected model type and name combination is already defined, the row will change to m for the action and the settings of the model will be pulled notes this doesn't need to be done for every model individually but can instead be done once all desired models have been added to the sheet model definition properties static attributes create and import models docid\ zpadx1lmme0f44v7r6v6q allow to m anage the metadata for the model this column combines all of these as a single json object it is recommended to use the static attributes wizard docid\ sgcuuahdbpogmkt6m6ck when setting your specific values for static attributes transformations create and import models docid\ zpadx1lmme0f44v7r6v6q allow to define how to transform the data collected in instances by converting raw json data to a desired format by defining the json based schema by the model this column combines all of these as a single json object it is recommended to use the transformations wizard docid\ szgnxuppussqogr75xu0n when setting your specific values for transformations dynamic attributes create and import models docid\ zpadx1lmme0f44v7r6v6q allow to m anage variable data in the model this column combines all of these as a single json object it is recommended to use the dynamic attributes wizard docid\ pm4mpwmlpyltf5lqro8g6 when setting your specific values for dynamic attributes model schema create and import models docid\ zpadx1lmme0f44v7r6v6q allows to create a custom data structure for the model this column combines all of these as a single json object it is recommended to use the model schema wizard docid\ swqiuan 1cmi7eg qofle when setting your specific model schema i f all add model(s) to digital twin for one litmus edge /#mandatory model settings ( ) model settings are provided, as well as all add model(s) to digital twin for one litmus edge /#not mandatory model settings settings are changed, the model is ready to be added to litmus edge notes to add more models to the sheet, repeat the process described under add model(s) to digital twin for one litmus edge /#add modelss for every model you want to add executing actions when all add model(s) to digital twin for one litmus edge /#mandatory model settings and add model(s) to digital twin for one litmus edge /#not mandatory model settings settings for all model(s) are set, they are ready to be added it is recommended but not mandatory to verify the configuration first without executing the action by pressing the verify only button this will check that all required model settings are provided and logically correct and provide any finding to the user example below the user not select a uns connector despite having enabled uns in column uns enabled important the tool can not verify if all provided model settings are factually correct for example it can not verify that the value of a static attribute is correct for what the user want to achieve the model(s) can be added to litmus edge by pressing the verify + execute button this will check that all required model settings are provided and logically correct and provide any finding to the user if no issues have been identified, the tool will verify that the user wants to execute all the actions from the action column a add model(s) m modify model (s) d delete model (s) i ignore model (s) > do nothing to perform all actions, press the yes button the tool will perform all actions row by row when finished, a result summary is shown close the result summary by pressing the x close button the tool will ask if the user wants to re compare the model(s) against litmus edge to re compare, press the yes button to not re compare, press the no button if the user selected to press the yes button from aboves messagebox, the tool will pull all the model settings from litmus edge again including the modelid and also change the action to m for each model with a modelid or a formodel with no modelid not mandatory model settings model description enter a short description of the model in the description field uns enabled select if you want to enable litmus uns for the model uns connector if litmus uns connector(s) are defined for the litmus edge, select which litmus uns connector to use to populate the static attributes with the litmus uns hierarchy notes selecting an uns connector will automatically add the respective static attributes associated with the uns connector as well as adding them to the model schema under the metadata folder by default before enabling uns after enabling uns troubleshooting the tool will perform several checks throughout the proces of defining the model settings if they do not pass successfully, the user will be notified the checks include model name uniqueness on a litmus edge level the tool checks if a model name already exist for a specific litmus edge in the tool allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for model names and descriptions the user is shown a message box as notification the character(s) are highlighted in red and also shown in a note see allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for a full list for both names and descriptions correct json formating for static attributes, trasnformations, dynamic attributes and model schema example for an invalid json formatting of the static attributes while it is possible to not define entries for the columns static attributes, trasnformations, dynamic attributes and model schema , the tool verifieds if any of these columns are empty as this will cause instances of this model to not return data or not return expected data while it is possible to leave some values for static attributes and dynamic attributes empty, the tool checks for such empty values as this will cause instances of this model to not return data or not return expected data example no schemaid defined for dynamic attribute