purpose_and_application
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
purpose_and_application [2022/01/13 16:39] – [Disclaimer (What is the WebHMI not for?)] emozolyak | purpose_and_application [2022/01/13 17:25] – [Application target size] emozolyak | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Purpose ====== | ====== Purpose ====== | ||
- | The WebHMI' | + | The WebHMI' |
+ | |||
+ | <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 | ||
- | {{ : | + | {{ : |
- | ===== 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. | ||
- | {{ : | ||
- | ===== Disclaimer (What is the WebHMI not for?)===== | + | {{ :: |
- | <wrap em> Though WEBHMI has a fairly good means of ensuring its own reliability, | + | ===== Application target size ===== |
+ | |||
+ | 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 (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' | ||
+ | * Large disributed applicatoin - Level2 together with WebHMI (of any kind) | ||
+ | * Small size applications, | ||
+ | * Educational and trial applications - any of virtual images with the respective license. | ||
+ | |||
+ | |||
+ | |||
+ | ====== Disclaimer (What is the WebHMI not for? | ||
+ | |||
+ | <wrap em> Though WEBHMI has a fairly good means of ensuring its own reliability, | ||
</ | </ | ||
The examples of these are: | The examples of these are: | ||
- | *military | + | *military |
- | *hazardous production process control | + | *hazardous production process control |
+ | *process control with high failure costly consequences | ||
+ | *fast real-time control, machine automation etc. | ||
+ | |||
+ | However, still it maybe used in these fieldds for monintoring ONLY purposes. | ||
- | but is focused primarily on managing small (dozens of signals) isolated or geographically distributed systems, rather than solving mission-critical management tasks at critical industrial facilities. | ||
purpose_and_application.txt · Last modified: 2022/01/14 14:20 by 127.0.0.1