Power Consumption
Manage thousands of local decisions through one operating model
Benchmark, govern and optimise energy use across stores, branches, campuses and distributed facilities with common policies and local execution.
Operational problem
Utility totals rarely explain the operational reason for consumption. Weather, production, shifts, occupancy, comfort, safety and equipment constraints must be connected before a recommendation can become a safe action.
enCoreEnergy combines measurements with operational context, analytics, AI-supported recommendations, workflows and verification. Scadify or existing BMS/PLC systems provide qualified local acquisition and execution; EnergyPortal can consolidate enterprise portfolios.
Core capabilities
Site and asset hierarchy
Configured according to the project’s data, control, approval and operating boundaries.
Normalised benchmarking and archetypes
Configured according to the project’s data, control, approval and operating boundaries.
Central schedules and policies
Configured according to the project’s data, control, approval and operating boundaries.
Exception and alarm workflows
Configured according to the project’s data, control, approval and operating boundaries.
Portfolio reporting with local context
Configured according to the project’s data, control, approval and operating boundaries.
Products and delivery responsibilities
Assemble the operating stack around the action.
Consumption, multi-utility optimisation, workflows and verification.
View responsibility →ScadifyField acquisition, local automation, protocols and resilient execution.
View responsibility →EnergyPortalCentral visibility, analytics, reporting, workflows and governance.
View responsibility →Operational workflow
From operational context to measured action.
- 01Classify sites and equipment
- 02Collect meters and operational drivers
- 03Benchmark and identify exceptions
- 04Assign or approve local action
- 05Verify portfolio and site outcomes
Data sources and integrations
Connect the evidence that explains the decision.
- Utility meters and submeters
- HVAC, lighting, pumps and equipment state
- Production, shifts, schedules and occupancy
- Weather, temperature and humidity
- Tariffs, invoices and maintenance context
Governance and resilience
Direct control is constrained by installed systems, safety interlocks, operating policy and customer approval. Recommendations, workflows and closed-loop control are separate modes.
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.
Normalised energy-performance indicators
Use an agreed baseline, operational definition and evidence source before assigning a target.
Prioritised demand, schedule and equipment opportunities
Use an agreed baseline, operational definition and evidence source before assigning a target.
Human-approved actions with clear ownership
Use an agreed baseline, operational definition and evidence source before assigning a target.
Baseline and reporting-period evidence
Use an agreed baseline, operational definition and evidence source before assigning a target.
Solution architecture
Make responsibility visible from field to enterprise.
enCoreEnergy combines measurements with operational context, analytics, AI-supported recommendations, workflows and verification. Scadify or existing BMS/PLC systems provide qualified local acquisition and execution; EnergyPortal can consolidate enterprise portfolios. 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 meter inventory, baseline design, significant-use analysis, interlock review, pilot acceptance criteria, field integration, commissioning, operator training and M&V planning.
Publication boundary
Capabilities are described as supported or project-configured where appropriate. Customer identities, quantified results, certifications and regulatory acceptance are not inferred from the solution page.
Related solutions and products
Continue with the next operational question.
FAQ
Questions to resolve before implementation.
Can every branch use the same control schedule?
Common policies can be applied while local climate, equipment, occupancy and operating constraints remain visible.
Can branches operate during a network outage?
Local execution depends on Scadify or existing controls and the deployed configuration; central analytics can resume after synchronization.
How are sites compared fairly?
Benchmarks can be normalised using area, weather, operating hours, occupancy, production or other agreed drivers.
Next step