Overwiew of KBR cloud scenario

Overwiew of KBR cloud scenario

For energy management, visual energy 4 can also be used as a cloud solution. The visual energy 4 web server and the system centers or measuring devices also use the Internet to communicate across different locations. Depending on the scenario, different configuration settings are required..

Using secure HTTPS instead of the unenvrypted HTTP protocol is recommended ofr all cases with Internet communication!

Further information: Using HTTPS
 

The following two scenarios are possible:


Scenario A '>10 measuring devices': Decentralized system center (bus master)

 


Scenario B 'up to 10 measuring devices': Centralized system center (bus master)

 

 

The system center location needs to fulfill the following criteria:

  • If the location has only a few measuring devices (<5-10), installing the system centers (bus masters) centrally in the vicinity of the server is more economical.
  • For a higher number of devices per location, the benefits of a decentralized structure prevail. Some features such as SecureF or virtual devices are only possible in a decentralized setup.

The main challenge with both scenarios is that the decentralized location has to be accessible from the server. The connection is always established from the central server location. Since it cannot be assumed that a fixed IP address is available for energy capture at the decentralized location, you have to find another way to ensure that direct access is possible.

 

VPN

VPN

Configuration scenario A

Configuration scenario A

Different ports have to be forwarded to enable communication between the bus master and "visual energy 4 cloud". 
The following ports have to be accessible via Internet (visualenergy.de):

  • Port 9001 (TCP) for WCF communication
  • Port 80 for MSMQ communication
  • Port 443 for https communication (if required)

For this purpose, you may have to adapt the ports, as it is rather unlikely that port 80, for example, is assigned to the bus master throughout the entire customer system. Then, on the bus master, assign the ISS ("Message Queuing over http") binding to another port and forward it accordingly within the network. This way, you can install several multisys bus masters independently of the existing infrastructure. As the internal IP address is not visible from the outside, you need a public IP address or DynDNS name.

Configuration scenario B

Configuration scenario B