Multiple galaxies

What are people views on multiple galaxies ?

How do we communicate data between different galaxies ?

Also, can we develop multiple galaxies in one project ? I have seen an option on System Platform but would need more clarity, like how SMS server works with multiple Galaxies, GR node etc

Parents
  • Multi-Galaxy Communication (MGC) in System Platform enables seamless interaction between multiple galaxies, allowing for distributed system architectures that extend beyond a single galaxy. Unlike traditional monolithic HMI/SCADA solutions that rely on a single server and point-to-point integration or external namespace brokers, System Platform is designed to support large-scale applications by distributing a single namespace and workloads across an unrestricted number of servers. MGC adds another layer of flexibility by interconnecting multiple galaxies' namespaces, enabling bidirectional or unidirectional data exchange while maintaining high performance. This enables enterprise-wide scalability for complex automation environments.

    Communication between galaxies is facilitated through Platform Common Services (PCS), the same communication framework used for OMI. PCS provides the underlying communication bus for secure and efficient data exchange between galaxies and supports encryption via the System Management Server (SMS). Encryption is highly recommended, and when enabled, all galaxies must use the same SMS server to ensure a unified certificate setup. Additionally, each Galaxy Repository (GR) node must be properly paired, ensuring that runtime data exchanges, namespace browsing, and security enforcement are consistently managed across all interconnected galaxies.

    MGC also allows customers to maintain complete development isolation between galaxies while still allowing them to exchange information in a controlled and secure manner. Each galaxy operates independently while still being able to access attributes from others. Graphics can directly reference attributes across galaxies and even use the 'owning object' feature to dynamically reference remote assets using relative paths (e.g., Me.Attribute), making cross-galaxy visualization seamless.

    For details on setting up and configuring multi-galaxy communication in System Platform, please refer to the AVEVA documentation portal.

     - Ernst

Reply
  • Multi-Galaxy Communication (MGC) in System Platform enables seamless interaction between multiple galaxies, allowing for distributed system architectures that extend beyond a single galaxy. Unlike traditional monolithic HMI/SCADA solutions that rely on a single server and point-to-point integration or external namespace brokers, System Platform is designed to support large-scale applications by distributing a single namespace and workloads across an unrestricted number of servers. MGC adds another layer of flexibility by interconnecting multiple galaxies' namespaces, enabling bidirectional or unidirectional data exchange while maintaining high performance. This enables enterprise-wide scalability for complex automation environments.

    Communication between galaxies is facilitated through Platform Common Services (PCS), the same communication framework used for OMI. PCS provides the underlying communication bus for secure and efficient data exchange between galaxies and supports encryption via the System Management Server (SMS). Encryption is highly recommended, and when enabled, all galaxies must use the same SMS server to ensure a unified certificate setup. Additionally, each Galaxy Repository (GR) node must be properly paired, ensuring that runtime data exchanges, namespace browsing, and security enforcement are consistently managed across all interconnected galaxies.

    MGC also allows customers to maintain complete development isolation between galaxies while still allowing them to exchange information in a controlled and secure manner. Each galaxy operates independently while still being able to access attributes from others. Graphics can directly reference attributes across galaxies and even use the 'owning object' feature to dynamically reference remote assets using relative paths (e.g., Me.Attribute), making cross-galaxy visualization seamless.

    For details on setting up and configuring multi-galaxy communication in System Platform, please refer to the AVEVA documentation portal.

     - Ernst

Children
No Data