Scheduling Engine

The scheduling engine behind fleet electrification that pays for itself

Celaxis runs a mixed-integer optimization solver that places charge windows in off-peak TOU slots, tracks 15-minute interval peaks to avoid demand billing spikes, and treats each vehicle's departure SOC floor as a hard constraint — not a preference.

Request Access
Abstract visualization of interconnected energy flow streams between charging stations and power grid nodes on dark background
OPTIMIZER_CYCLE 5 min
TARIFF_FEEDS 200+ utilities
CONSTRAINT_MODEL Multi-vehicle MILP

Four-stage pipeline from tariff data to charger command

1
Tariff Feed Ingestion

Live TOU rate calendars pulled from 200+ utility APIs. Demand period windows, ratchet clauses, and seasonal adjustments updated in real time. No manual rate entry.

2
Constraint Modeling

Per-vehicle departure windows, SOC floor requirements, charger capacity limits, and site-level peak thresholds are all encoded as hard constraints. Optimization runs within this feasibility space.

3
Multi-Vehicle Scheduling Solver

Mixed-integer linear program solves the joint scheduling problem across all vehicles simultaneously — not sequentially. Produces the globally optimal charging schedule for each 24-hour horizon.

4
EVSE Command Dispatch

Optimized schedule pushed to charging network management systems via OCPP or REST API. Real-time deviation monitoring catches unplanned events and re-optimizes within seconds.

TARIFF FEEDS 200+ utility APIs FLEET TELEMATICS SOC · route · departure CELAXIS OPTIMIZER Multi-vehicle MILP solver 5-min reoptimization cycle EVSE COMMANDS OCPP 1.6 / 2.0 · REST

The utility intelligence layer

For commercial fleet charging, demand charges and TOU peak windows are the two variables that determine whether electrification reduces or raises operating costs. The tariff engine models both with the granularity your utility bill actually uses — 15-minute demand intervals, season-specific TOU windows, and ratchet clauses that persist beyond the month they're triggered.

Utility Coverage
200+
US utility tariff feeds, continuously maintained
Update Frequency
Real-time
TOU calendars and demand period windows live
Demand Interval
15-min
Interval-level peak tracking for billing precision
Ratchet Handling
Full
Ratchet clause modeling per utility tariff schedule

Optimization never breaks operations

The hardest constraint in fleet charging optimization is the departure window. Celaxis encodes each vehicle's departure time and minimum SOC requirement as hard constraints before the solver runs — not as soft penalties it can trade off against cost savings. A schedule that saves $200 but puts a bus on the road at 60% SOC when dispatch requires 85% is not an acceptable schedule. It will not be produced.

Departure Window Encoding

Each vehicle's daily departure times are imported from your fleet management system or set manually. The optimizer treats these as hard deadlines, not soft preferences.

SOC Floor Enforcement

Minimum state-of-charge at departure is configured per vehicle or fleet-wide. If off-peak charging can't reach the floor, the system automatically authorizes on-peak charging to meet the constraint.

Missed-Window Alerting

If an unplanned event — charger fault, grid outage, extended dwell time — threatens a departure SOC, operations staff receive an alert with recharge options and cost impact estimates.

Real-time Reoptimization

Every 5 minutes, the optimizer re-runs with updated SOC telemetry, tariff period transitions, and any constraint changes. The schedule is always the best solution available right now.

REST API for enterprise integration

Embed Celaxis scheduling directly in your fleet management platform via our REST API. Submit fleet configurations, retrieve optimized schedules, and push commands to your EVSE network programmatically.

JSON request / response
Bearer token authentication
Webhook callbacks for schedule updates
Available in Fleet tier
POST /v1/schedule
POST https://api.celaxiq.com/v1/schedule
Authorization: Bearer <token>
Content-Type: application/json

{
  "fleet_id": "depot-pdx-001",
  "tariff_zone": "pacific-power-schedule-37",
  "horizon_hours": 24,
  "vehicles": [
    {
      "id": "bus-047",
      "soc_current_pct": 41,
      "soc_floor_pct": 85,
      "departure_time": "06:15",
      "charger_id": "bay-12",
      "max_charge_kw": 60
    }
  ]
}

Start with your utility bill, not a software demo

Send us three months of bills and your fleet's departure schedule. We'll model the demand charge reduction before you commit to anything.