mP Automation Server
Orchestration of batch processes: time-driven, event-driven and on external demand – using container swarm operation.
mP Automation Server orchestrates all batch-related forecasting processes in mP Xnergy. There are three
types of trigger: time-based according to a fixed schedule, event-driven as soon as new data becomes available, or
triggered by an external API. In cloud operation, mPAS launches as many container instances as necessary –
swarm operation for maximum throughput, even under peak load.
The challenge
- Sequential forecasting calculations take too long for large portfolios
- Gate closure deadlines must be met – even during peak loads
- Manual monitoring of batch processes is error-prone and labour-intensive
- Full automation requires event-driven processing – not just fixed
schedules
The solution
- Time-driven: Fixed schedules for daily forecasting jobs – e.g. daily at 06:00
- Event-driven: Jobs start automatically as soon as new measurement data or weather data becomes available
- External trigger: Third-party systems trigger forecasts via Web Service – on demand following
data delivery - Swarm operation: In cloud operation, as many container instances as required – no bottlenecks
during peak loads - Self-monitoring: Alerts in the event of irregularities, detailed logs for each process
Fully automated orchestration of forecasting jobs
See for yourself – we’ll show you mP Xnergy in action during a personalised demo.