InputsWhat we need to model a depot
The method starts with the operational reality of the depot rather than a generic charger count.
Operations
Blocks, departures, return windows, reserve requirements, and dispatch exceptions.
Assets
Battery capacities, consumption assumptions, charger power, connector topology, and parking constraints.
Energy
Grid connection, meters, load limits, tariff structures, PV, battery storage, and local EMS signals.
Optimization
What Fenexity optimizes
Readiness first
Vehicles are prioritized by next duty, required energy, operational risk, and charger availability.
Cost under constraints
Charging is shifted around price, peak, and grid limits where the operating schedule allows it.
Robust operations
Plans remain explainable when chargers fail, schedules shift, or local limits change.
Outputs
What teams receive
How Fenexity labels evidence
How Fenexity labels evidence| Evidence type | How to read it | Required support |
|---|
| Capability | Describe what Fenexity does | Product capability and feature status |
|---|
| Modelled | Show scenario ranges | Assumptions, sensitivity factors, review date |
|---|
| Measured | Use in project studies | Project data and publication permission |
|---|
Evidence boundary
Where public customer references are not available, Fenexity uses capability language and modelled scenarios. Numeric customer outcomes are shown only when validated project data can be published.