Nine Velon-built Python modules under one canonical power-system model — built by Velon for transmission system operators, the major developers running large grid-connection studies, and the hyperscale data-centre operators siting GW-scale loads. Every deployment is bespoke and built around your approved environment. Start with a trial.
Year-round security-constrained dispatch with the grid as a first-class constraint. Reinforcement screening, stability headroom, hosting capacity — across every boundary in your network.
Hundreds of candidate POIs ranked on curtailment risk, capture rates, stability margin and reinforcement need — under your own market scenarios. The bedrock of every IC business case.
The same screen your TSO will run — before they run it. Curtailment exposure, voltage and stability headroom, redispatch risk and BESS sizing. Concrete inputs for site selection, ramp planning and connection negotiation.
Each engine surfaces a family of specialist applications. They share the same data ingestion, network reduction and scenario library — and write back to the same KPI ledger.
BESS arbitrage and value-stack co-optimisation across the scenario library — sizing, dispatch envelope, and the calendar-cost trade-off.
BESS state-of-charge · arbitrageHalf-hourly security-constrained dispatch across the year with the grid as a first-class constraint. The bedrock of every Pillar-2 KPI.
Branch loading · P10 / P50 / P90Localises the cause and cost of every constraint event — PTDF / LODF sensitivities mapping curtailment back to circuits, areas and connection points.
PTDF heatmap · circuit × hourMaximum megawatts you can push across each boundary — under every credible N-1. Asset-optimised dispatch of QBs and HVDCs.
Transfer · Boundary A → KWhere should the next block of generation, BESS or load actually sit? Per-zone headroom and locational signals on a single canonical model.
Hosting capacity · zonalThe foundation layer. Pulls market, weather and network data into a single canonical model — the same dataset every Velon engine inherits.
Sources → canonical → every engineRotor-angle / transient stability screening — TSI, small-signal damping, critical clearing time — across the scenario library at every candidate POI.
Rotor angle · damped swingSystem inertia, RoCoF and frequency-response containment headroom — surfaced as a stability margin per scenario and POI, hour by hour.
Frequency · RoCoF envelopePV/QV-based voltage stability margin, short-circuit ratio and reactive-support siting — automated across every candidate POI in the scenario library.
PV nose-curve · V-marginCollapses a full transmission model to a lean, boundary-aware study model — Python + DPL automation on commercial solvers. Feeds PSA, PFA & PVA.
Full model → reduced study modelThe Velon Suites are Velon-owned, modular software — not an off-the-shelf product. Power-system engineers and Python developers in the same studio — not a stitch of partner ware.
Every deployment is shaped to the operator's market design, grid code and boundary topology. The modules stay the same. The configuration is yours.
We work with TSOs and major developers to run a focused trial on their data — before any commitment. Six to eight weeks. Real numbers. Real engineers in the loop.
PSCAD, PowerFactory and PSS®E stay the trusted engines. The Velon Suites sit on top as a Python orchestration layer — stochastic sweeps, custom criteria and GIS visualisation the solvers alone don't deliver. The pattern is the same across every Velon engine.
Python apps — configurable, stochastic, standalone. Each engine is a Tier-1 app sitting over one canonical data layer. Adding a new study question = adding a new app, not rebuilding the stack.
Stochastic sweeps over 8,760 hours. Custom criteria (TSI, RoCoF, FRCR, V-margin, CCT). Tens of thousands of simulations aggregated to distributions, not tables. GIS heatmaps and interactive dashboards — not slideware. One canonical model behind all of it.
Velon engines drive the solvers the operator already validates, audits and trusts. Results are reproducible inside the operator's own toolchain — the suite never replaces them, never locks you in.
Click any module below to see what it does, what it ingests, and what each Velon Suite delivers from it. The architecture below is the runtime topology — the same shape across every jurisdiction the suites are deployed in.
3 engines · 9 applications · the runtime topology renders the same 8 architecture modules across every jurisdiction.
Every Velon Suite ships with an operator-facing workbench: maps, ranked POI tables, scenario controls, per-POI dossiers, and one-click export to the formats your IC review actually consumes.
Find the GW-scale site the grid will actually say yes to — curtailment exposure, voltage headroom and connection cost ranked before you commit to land or a queue position.
We work with TSOs and major developers to run a focused trial on their own data. Six to eight weeks. A few engineers, a defined question, a concrete deliverable. Then we decide together what a bespoke deployment looks like.
We pick one Pillar-2 or Pillar-3 question on a slice of your network. Boundary capability, curtailment exposure, stability screening — something you'd otherwise build by hand.
Your jurisdiction profile, your boundary topology, your grid code. The suite is configured against your canonical datasets and the commercial solvers you already license.
Joint review sessions with your engineering team — every result traced back to its scenario, its case, its solver run. No black-box outputs.
You see the suite running on your own data, and we scope the bespoke solution from there — scale into a deployment tailored to your operation, or close the trial with the artefact you have. No lock-in, no licence trap.
The same Velon team writes the engines, configures the deployment and runs the studies alongside your engineers. Four commitments we make to every operator we work with.
Per-operator profiles encode market design, grid code and boundary topology — the same code answers a North-American question, a European question and a Gulf question with the same engineering rigour.
The Velon Suites wrap PSCAD, PowerFactory and PSS®E — never replacing them. Every result is reproducible inside the operator's own toolchain.
Every assumption is timestamped to a named source. Every KPI in the dashboard traces back to the simulation case that produced it.
New scenarios, new modules and new criteria slot into the canonical data model without reworking the engines. Future-ready by construction.
Start with a trial on your own data. Six to eight weeks. A defined question. A concrete deliverable. Then decide.