Scadify · Industrial edge controller and local automation platform
Bring reliable measurement, automation and local operations to the field.
Scadify connects field equipment with protocol integration, local SCADA, alarms, historian and resilient offline automation.
What it solves
Remote sites need central visibility, but local acquisition, alarms, runtime and approved control should not depend entirely on a permanent central connection.
Local acquisition
Connect meters, sensors, analyzers, actuators and equipment through a canonical tag and device model.
Edge automation
Run approved cyclic logic, command routing, runtime health and local recovery close to the process.
Local SCADA/HMI
Expose live tags, equipment status, alarms, trends and authorized actions at the site.
Historian and evidence
Retain selected measurements, events, alarms, deployments and user actions locally.
Protocol boundaries
Keep drivers separate from business logic so project-qualified protocol roles remain controlled.
Governed deployment
Use versioned automation/configuration artifacts, activation history and rollback concepts.
How it works
A traceable path from signal to operational action.
Bind
Map physical signals and protocols to canonical tags, devices, units, permissions and quality.
Run
Execute the local runtime, evaluate alarms and apply approved non-safety automation.
Record
Store measurements, runtime status, commands, events and deployment evidence locally.
Synchronize
Exchange normalized telemetry and configuration with central Enlogy products when connectivity is available.
Govern
Control engineering changes through roles, approval, version history and rollback.
Use cases
Built around the operating context.
The right product configuration depends on equipment, data quality, control responsibility, operating policy and the evidence required by the project.
- Renewable plant telemetry and local SCADA
- PPC field infrastructure
- Factory energy and process integration
- Retail HVAC and lighting control
- Pumping and water infrastructure
- Brownfield protocol modernization
Integration model
Connect the systems you already operate.
Governance and boundaries
Scadify is intended for non-safety and project-qualified automation unless a separately validated safety architecture exists. Security level, protocol roles, hardware availability and certifications must follow the current engineering release matrix.
Architecture and evidence
Make the operating model visible.
Product relationship
Defined responsibilities, connected operations.
Scadify is the local execution and evidence layer for EnergyPortal, enPowerManager and enCoreEnergy. It can operate locally according to deployed release and configuration without permanent central connectivity.
Plan your deployment
Find a solar production loss before dispatching a team
Example operating scenario
One inverter produces less than its neighbours. Compare string currents, irradiance, equipment state and meter readings to distinguish a local fault from cloud cover or a communication gap.
Data to prepare
Inverter and string inventory, meter map, weather sensors, single-line diagram, alarm history and available communication interfaces.
What Enlogy provides
A shared equipment view, contextual alarms and time-series evidence help the operator identify the affected circuit and prepare a maintenance task.
Questions to ask before buying
- Can the demonstration distinguish missing data from zero production?
- Which inverter brands, signals and local operating functions are included?
- How are alarm delivery, historical retention and commissioning tested?
Illustrative workflow; project scope and acceptance criteria are agreed for your facility.
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 interoperabilityIndustrial control and functional safety
IEC 61131-3 · IEC 61511 · IEC TS 63074
Why you need it
Plants need maintainable control logic and clear separation between operational control and safety functions.
What Enlogy provides
Enlogy develops PLC integration and control workflows with safety-system interfaces, interlock context and security requirements for safety-related control systems.
IEC 62443 OT cybersecurity
IEC 62443 · IEC 62351 · ISO/IEC 27001 · ISO/IEC 27002 · ISO/IEC 27019 · NIST SP 800-82 · NIST CSF 2.0
Why you need it
Connected energy systems need controlled access, secure communication and a manageable cyber-risk lifecycle.
What Enlogy provides
Enlogy applies industrial and energy-sector security across development, identity, OT interfaces, communication, monitoring and incident workflows.
Explore this capability: IEC 62443 OT cybersecurityFAQ
Questions engineers and operators ask first.
Is Scadify a gateway or a PLC?
It combines gateway, local SCADA, historian and automation-runtime capabilities; its exact role depends on hardware, protocol and application configuration.
Can it operate without EnergyPortal?
The architecture is local-first. Essential local functions are intended to continue subject to the deployed release and configuration.
Is Scadify IEC 62443 certified?
No certification is claimed. The architecture includes a requirements-mapping and hardening path toward industrial component-security areas.
Next step