Jump to: navigation, search

Difference between revisions of "Configure Comos for CUI"

(→‎Comos)
Line 26: Line 26:
 
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
 
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
 
<Give step-by-step instructions, use images, ...>
 
<Give step-by-step instructions, use images, ...>
 +
  
 
= UBIK =
 
= UBIK =

Revision as of 06:37, 13 August 2026

To run or extend the Comos – UBIK® – Interface => CUI you have to do some settings on Comos side or at least get some Data for Configuration from Comos. Because Comos is not a Product from Augmensys, please request all Comos changes or adaptions at your local Simens or Siemens Parter.


[edit]

Idea and Concept

The Interfaceing of Data is depending on 3 Parts

  • the possible representation of Data from Comos
  • the transfer media, like *.xml file or REST API Interface
  • the processing of the given Information in UBIK®

To hand over the primary needed Information from Comos to UBIK® there are only *.xml Files to use, cause the Comos side is writing a the Data to a fixed *.xml shema witch UBIK® is able to read in. This is called Metadata Transfer, and hands over Data about Cdevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes form Comos to a .xml file. When UBIK® Smar Studio is Importing this, it will generate ComosMetaProxy's with Traget MetaClasse's, ComosMetaProxyProperty's with Target MetaProperty's, Selective Lists and Items, SI Units and UnitItems, and some ComosDocumentTypeProxy's For detailed Informations about the UBIK® Classes please see

Comos

<Give step-by-step instructions, use images, ...>


UBIK

<Give step-by-step instructions, use images, ...>


See also

Retrieved from "https://wiki.augmensys.com/index.php?title=Configure_Comos_for_CUI&oldid=30427"