User Tools

Site Tools


purpose_and_application

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
purpose_and_application [2022/01/13 16:57] – [Application target size] emozolyakpurpose_and_application [2022/01/13 17:25] – [Application target size] emozolyak
Line 1: Line 1:
 ====== Purpose ====== ====== Purpose ======
  
-The WebHMI's mission in brief is the <wrap em> "Rapid deployment of WEB-monitoring projects of various facilities, without special knowledge in the field of network technologies and extensive programming skills."</wrap>+The WebHMI's mission in brief is the  
 + 
 +<WRAP center round box 60%> 
 +**"Rapid deployment of WEB-monitoring projects of various facilities, without special knowledge in the field of network technologies and extensive programming skills."** 
 +</WRAP>
  
 WEBHMI is a solution that allows the user to effectively solve the task of monitoring the status of various engineering systems and facilities, as well as their remote management.  WEBHMI is a solution that allows the user to effectively solve the task of monitoring the status of various engineering systems and facilities, as well as their remote management. 
Line 26: Line 30:
 The next option involves the possibility of transferring data from the process directly to the target business application via the API The next option involves the possibility of transferring data from the process directly to the target business application via the API
  
-{{ :api_eng.png?direct&600 |}}+{{ :api_eng.png?direct&400 |}}
  
-===== Cloud Solutions =====+===== Cloud - based and large distributed solutions =====
  
 Finally, the variant of constructing a dispatching system for distributed objects, assuming a two-level topology in which WEBHMI acts as data gateways of the lower level, transferring information to a dedicated server that ensures its further processing and storage. For more information about this feature, contact your device vendor. Finally, the variant of constructing a dispatching system for distributed objects, assuming a two-level topology in which WEBHMI acts as data gateways of the lower level, transferring information to a dedicated server that ensures its further processing and storage. For more information about this feature, contact your device vendor.
  
-{{ :level2_eng.png?direct&600 |}}+ 
 +{{ ::cloud_conttrol_structure.png?direct&600 |}}
  
 ===== Application target size ===== ===== Application target size =====
  
-Size means number of registes (tags or variables) in the process. +Size means number of registes (tags or variables) in the process - usually the more tags the more screens, reports, control and other features demanding higher performance. Folloing are not strict rules but rather a "rule of thumb"
  
-  * Up to 2-3K - Hardware WebHMI version+  * Up to 2-3K (for single facility) - Hardware WebHMI version
   * High demanging in terms of performance with 5-10K and more tags - Virtual box image. This image can be installed on a dedicated industrial single - board computer or box PC or on a customer's virtualization server.    * High demanging in terms of performance with 5-10K and more tags - Virtual box image. This image can be installed on a dedicated industrial single - board computer or box PC or on a customer's virtualization server. 
-  * Small size applications, distributed IoT applications - Level2 virtual image.+  * Large disributed applicatoin - Level2 together with WebHMI (of any kind) 
 +  * Small size applications, distributed IoT applications - Level2 cloud running virtual image.
   * Educational and trial applications - any of virtual images with the respective license.   * Educational and trial applications - any of virtual images with the respective license.
  
purpose_and_application.txt · Last modified: 2022/01/14 14:20 by 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki