Enlogy product architecture
Clear product responsibilities from field equipment to enterprise operations.
Enlogy separates local execution, plant-level control, consumption optimization and central operations into products with defined responsibilities. This makes systems easier to integrate, operate, secure and evolve.
Architecture principles
Build around operational responsibility, not software labels.
Local-first operation
Product boundaries, data quality, permissions and operational evidence are defined before an integration is treated as production-ready.
Dedicated plant control
Product boundaries, data quality, permissions and operational evidence are defined before an integration is treated as production-ready.
Governed optimization
Product boundaries, data quality, permissions and operational evidence are defined before an integration is treated as production-ready.
Centralized visibility, not centralized fragility
Product boundaries, data quality, permissions and operational evidence are defined before an integration is treated as production-ready.
Open integration boundaries
Product boundaries, data quality, permissions and operational evidence are defined before an integration is treated as production-ready.
Evidence and controlled change
Product boundaries, data quality, permissions and operational evidence are defined before an integration is treated as production-ready.
Responsibility matrix
Know which product owns each function.
| Capability | EnergyPortal | enPowerManager | enCoreEnergy | Scadify |
|---|---|---|---|---|
| Enterprise portfolio hierarchy | Primary | Context | Context | Device identity |
| Central SCADA and dashboards | Primary | Status integration | Portfolio views | Local HMI |
| Plant-level PPC | Supervises | Primary | No | Qualified integration |
| Consumption optimization | Oversight | No | Primary | Measurement/control |
| Protocol acquisition | Ingestion | Project interface | Integrated data | Primary field layer |
| Offline local operation | No | Controller-specific | Central logic | Primary |
Data plane and control plane
Separate observation from action.
Not every data path is a control path. The architecture distinguishes read-only telemetry, advisory recommendations, human-approved commands and automatic closed-loop control.
Deployment patterns
Combine products according to the operating problem.
Renewable plant operations
EnergyPortal + enPowerManager + Scadify
Central SCADA, plant-level PPC, field data and operational reporting.
Hybrid power plant
enPowerManager + EnergyPortal + Scadify
Wind + solar, solar + storage and other engineered source combinations.
Multi-site optimization
enCoreEnergy + Scadify
Distributed facilities, branches, retail and commercial operations.
Brownfield modernization
Scadify + selected Enlogy products
Legacy devices, protocol conversion and staged integration.
Enlogy access and integrations
Your operations, across the screens you use
From the web portal to ChatGPT and Claude, mobile, TV and API connections: explore how each access option fits your team.
Explore access and integrations