HYDRA System Architecture & Deployment
HYDRA allows a high level of flexibility for system deployment. As most manufacturing companies already operate an ERP-system or various other IT-systems, HYDRA is usually technically integrated with these systems. On the other hand, quite a number of companies deploy HYDRA on a stand-alone basis - for reasons such as missing function capability of their existing external systems, or simply because the production shop floor environment shall be brought under control first, before an ERP-system will then subsequently be introduced. HYDRA provides the advantage of being able to operate stand-alone, where by the generation of a production order is the starting point of activity in HYDRA. Production order contain entire operation routes, along with input material components lists and other target data and related/linked documents & files. Production orders can be generated entirely manually, or on the basis of predefind routing master data ("Workplans") within HYDRA.
Note: The respective logos and company/product namesare property of the respective companies.
The typical HYDRA-8 system installation consists of three major elements:
- HYDRA host server, hosting the MES-Weaver 3.0 base application of HYDRA
- MOC ( = Manufacturing Operation Centre), the typical office PC for purposes of data management, supervision, control and reporting
- AIP ( = Acquisiton & Information Panel), the MS Windows based shop floor PC, often operates as industrial touchscreen panel PC, for manual data capturing along with connectivity to devices, gages and machines, whenever applicable
