Field Automation
Connect industrial protocols without losing engineering meaning
Normalise approved industrial protocols, device maps, quality, units and commands into a governed field-to-enterprise data model.
Operational problem
Remote sites must continue acquiring, alarming and executing approved local logic through protocol diversity, brownfield equipment and intermittent central connectivity.
Scadify separates canonical tags, protocol drivers, local HMI, historian, alarms and automation runtime from physical hardware. EnergyPortal, enPowerManager and enCoreEnergy consume governed field evidence and provide higher-level context.
Core capabilities
Device-model and canonical tag governance
Configured according to the project’s data, control, approval and operating boundaries.
Read/write separation
Configured according to the project’s data, control, approval and operating boundaries.
Quality, timestamp, unit and scaling preservation
Configured according to the project’s data, control, approval and operating boundaries.
Project compatibility and interoperability testing
Configured according to the project’s data, control, approval and operating boundaries.
Drivers separated from application logic
Configured according to the project’s data, control, approval and operating boundaries.
Products and delivery responsibilities
Assemble the operating stack around the action.
Operational workflow
From operational context to measured action.
- 01Register device and protocol scope
- 02Map signals to canonical tags
- 03Test read, write and quality behaviour
- 04Deploy controlled configuration
- 05Monitor health and evidence
Data sources and integrations
Connect the evidence that explains the decision.
- Meters, sensors, analyzers and actuators
- PLCs, RTUs, BMS and existing SCADA
- Modbus, MQTT and project-qualified telecontrol interfaces
- Local alarms, commands, deployments and audit logs
- Central configuration and operational policies
Governance and resilience
Scadify is intended for non-safety and project-qualified automation unless a separately validated safety architecture exists. Protocol maturity, hardware and certification status follow the release matrix.
Protocol roles, OEM compatibility, data retention, control limits and failure behaviour must be confirmed from the engineering-approved release and project documents.
Outcomes and KPI framework
Measure the operating result, not only the software activity.
Local-first operation and evidence
Use an agreed baseline, operational definition and evidence source before assigning a target.
Reusable device/tag model across field platforms
Use an agreed baseline, operational definition and evidence source before assigning a target.
Controlled protocol and command boundaries
Use an agreed baseline, operational definition and evidence source before assigning a target.
Staged integration and rollback visibility
Use an agreed baseline, operational definition and evidence source before assigning a target.
Solution architecture
Make responsibility visible from field to enterprise.
Scadify separates canonical tags, protocol drivers, local HMI, historian, alarms and automation runtime from physical hardware. EnergyPortal, enPowerManager and enCoreEnergy consume governed field evidence and provide higher-level context. The architecture separates observation, recommendation, human-approved action and local execution so that each team can see what it owns.
Engineering and implementation
Move from architecture to accepted operation.
Engineering scope can include I/O and protocol assessment, panel and network design, control logic, HMI, commissioning, migration, FAT/SAT, training and lifecycle support.
Customer applications
Discuss integration, commissioning and operational support for your equipment and sites.
Standards compliance for this capability
Standards compliance for this capability
Enlogy provides full compliance with the standards below across development, integration and system operation and management.
IEC 61850 and grid interoperability
IEC 60870-5-104 (IEC-104) · IEC 61850 · IEC 61850-7-420 · IEC 61850-7-410 · CIM (IEC 61970 / IEC 61968)
Why you need it
Utilities and plant operators need consistent equipment meaning across SCADA, substations and dispatch systems.
What Enlogy provides
Enlogy connects telecontrol and equipment data models with a common asset context, preserving measurement quality, timestamps and command responsibility.
Explore this capability: IEC 61850 and grid interoperabilityMetering, GIS and BIM integration
DLMS/COSEM · M-Bus / OMS · OGC API · GeoJSON · CRS/EPSG · IFC
Why you need it
Operators need meter data linked to the right site, building, network and physical asset.
What Enlogy provides
Enlogy connects metering and AMI data with spatial APIs, geographic coordinates and building information models for location-aware monitoring and reporting.
Related solutions and products
Continue with the next operational question.
FAQ
Questions to resolve before implementation.
Which protocols are supported?
Protocol roles and maturity are published from the current compatibility matrix. A protocol name alone does not prove client, server, read or write scope.
Can a proprietary OEM protocol be integrated?
It can be assessed as a project integration when documentation, interface ownership and test access are available.
Are timestamps and quality preserved?
The canonical model is designed to preserve them where the source and driver provide reliable values.
Next step