iSCADA · HMI & tags
Describe the process. Get the SCADA system.
iSCADA turns a plain-language description of a plant into a live flowsheet, a structured tag database, and scaffolding in the conventions your SCADA platform actually uses.
What it does
- It knows the platform
- Each supported SCADA platform carries its own profile: tag addressing scheme, permitted datatypes, quality codes and naming conventions. Ignition gets dotted paths with Float8 and BAD_CONNECTION_LOST, because that is what Ignition uses.
- It knows the hardware
- Pick a controller and iSCADA works to its genuine I/O count and address format. It will not allocate a point that does not physically exist on the part you selected.
- It knows the equipment
- Tanks, vessels, columns, pumps, valves, motors, compressors, mixers, filters, heat exchangers, conveyors and instruments are modelled as equipment types with the measurements each one implies — not anonymous boxes joined by lines.
- Supported platforms
- Ignition (Inductive Automation), FactoryTalk (Rockwell), WinCC (Siemens), and a generic profile. Controller profiles cover Allen-Bradley, Siemens and Beckhoff families.
Most generated automation content has to be rewritten before it can be used, because it is written in no particular dialect — generic tag names, invented addresses, datatypes that do not exist on the target. The import succeeds and the real work starts afterwards. Coverage here is deliberately deep rather than broad: every profile is maintained in the product, not a generic adapter.