X Enerji Product concept

Managing energy use across 85 factories with minute-by-minute data.

Meter data, a 48-hour forecast and waste alerts in one platform; the energy team sees waste before the bill arrives.

X Enerji product concept with sample data: a dark overview screen showing the total live load of 85 facilities, today's cost, peak-period share and a 48-hour consumption forecast. In front, a pale green phone screen shows Gebze Facility's live power and an alert that compressor K-3 is idling on the night shift.
Investigating consumption deviationsFull screen ↗
Product concept: a solution study presented through screen designs, not an interactive demo. X Enerji is fictional; screen data is illustrative.
Industry
Energy & Industry
Capabilities
Data & AI, Software Engineering, Cloud & DevOps
Platform
Web, mobile, IoT

Problem and approach

Problem

In a company with multiple facilities, energy consumption often becomes visible only when the bill arrives.

Meters from different manufacturers use their own protocols, leaving facility comparisons to manually assembled spreadsheets. A compressor idling overnight or a load running during peak hours disappears into the month-end total.

Approach

We connect the 85 facilities in stages, starting with pilot sites rather than all at once.

In a two-week discovery sprint, we map pilot-site meters to machines and test a prototype with actual users in week three. The jointly scoped first phase, such as monitoring and waste alerts at pilot facilities, targets a launch in 6–12 weeks; forecasting and other facilities are added in later phases.

Solution

Manage energy every minute, not just at month-end.

The X Enerji concept's Gebze Facility screen, with sample data: live power, today's consumption, end-of-day cost and power factor cards; a minute-by-minute consumption chart with a forecast band; three open anomalies, including compressor K-3 idling overnight; a facility heat map by area and consumption by production line.
Tracking open alertsFull screen ↗
A forecast is useful when it explains what to do next: forecasts, open anomalies and line loads appear side by side on the facility screen.
Two screens from the X Enerji concept's mobile app, with sample data. Left, Live Monitoring: Gebze Facility's current power, its share of contracted power and loads by line. Right, an alert: a chart showing compressor K-3 idling on the night shift, 1.8 MWh of excess consumption, its cost, a recommended action and an Assign to Maintenance button.
Live facility loadFull screen ↗
Mobile app: live load and an alert assigned to maintenance with one tap.
  1. Minute-by-minute consumption monitoring

    Each meter sends a reading every minute; consumption is traced from facility to line to individual machine.

  2. Anomaly and waste alerts

    The platform learns each machine's expected consumption by shift. Deviations and their costs are routed to the relevant team.

  3. 48-hour consumption and cost forecast

    Consumption and cost are forecast two days ahead with a confidence interval. Tomorrow's peak load is visible today.

  4. Peak-period load-shifting recommendations

    Identify loads that can be deferred from peak hours: which machine, at what time and with what monthly saving.

Scenario and scope

Example users

Energy manager, facility manager and maintenance team.

Example workflow

Meter data is collected, missing readings are flagged and measurements are compared with shift information. Deviations are assigned to the relevant team; the facility manager decides whether to apply load-shifting recommendations.

Decisions for a real project

Choose meter protocols, measurement frequency, historical data requirements, facility and machine mappings, alert thresholds and human approvals. Forecasting or recommendation models are enabled only if pilot evaluation is sufficient; the first phase may cover monitoring only.

Related service: Custom software development; for forecasting and anomaly scope, see AI integration. You can list your own users and systems in the project brief tool.

Timelines, teams and technologies in this scenario are illustrative planning choices; actual scope, schedule and team are defined during discovery. Product names do not imply partnerships.

What we measure

%10Target: reduction in energy cost
%90Target: accuracy of the 48-hour forecast
30 minTarget: maximum time for a deviation to reach the relevant team
%99,5Target: proportion of meter data reaching the dashboard completely

These targets are example measures defined for this scenario; actual results vary by project.

Technology and team

Technology

  • Python
  • Kafka
  • MQTT
  • TimescaleDB
  • PyTorch
  • React
  • Kubernetes
  • AWS

We explain data preparation, human approval and pilot planning for forecasts and anomaly alerts on the AI integration page, and other scenarios in our AI in business processes guide.

Suggested team 7 people

  • 1 data scientist
  • 1 product designer
  • 4 software engineer (web, mobile, backend)
  • 1 data engineer

Your process

Do you manage a similar operation? Let's schedule a 30-minute conversation about turning your factories' energy data into decisions.

Let's discuss this concept

This is an example, not a limit; we apply the same approach to similar processes in other industries.