Rotormaps Katana

What's New

• v1.6.22 — October 2026 capacity refresh: every operator that publishes forecast flow or available capacity was re-fetched, validated and matched again. 8,791 lines and substations now carry a 2026 capacity figure, up from 7,009, with Chubu included for the first time. Figures that are no longer published are withdrawn from view but kept on record, so any number previously quoted stays reconcilable. Most headroom is derived from forecast flow rather than published as available capacity, and each figure says which it is: a derived number is a screening estimate, not an operator commitment.
• v1.6.21 — Roadside 6.6 kV connections: small simulated sites and datacentre pins (up to about 2 MW) can now assume an unmapped 6.6 kV distribution line along the public road. Tick Assume roadside 6.6 kV line in the pin popup, open the Street View link at the exact coordinates, and record whether you can see the line. Each connection is labelled Assumed, Verified or Rejected, and that label follows it into the results, which show the fault level, SCR and voltage drop at the connection point. In the app, feeder length is estimated as the straight-line distance times a road-detour factor; formal studies route along real OpenStreetMap roads offline. Moving a pin clears its Street View check, so a check always belongs to the spot you are modelling.
• v1.6.20 — Two clear ways to read the grid: the analysis panel is now split into Current System View — what the grid is doing right now, via the Curtailment and Reverse Flow highlights — and Asset Analysis (formerly "Nodal Analysis") — the what-if simulation. The two open as a swipe-style pair: expanding one closes the other, so you always know which lens you are looking through. Curtailment and Reverse Flow are now buttons rather than tick boxes, because the two overlays contend for the same map styling and can no longer be shown at once — clicking the active one clears it. Keyboard users can open either view with Enter or Space.
• v1.6.19 — 2026 grid-capacity data, now live in the app: available-capacity figures published by all nine TSOs for 2026 are now used across the map, popups and analysis. 7,009 transmission lines and substations carry the new figures, of which 5,310 had no operator capacity data at all before and 1,517 were previously showing 2025 numbers. Provenance is now explicit: from 2026 the operators publish forecast flow (予想潮流) rather than available capacity, so most headroom is derived rather than published — every figure is labelled with which it is, because a derived number is a screening estimate and not an operator commitment. Data integrity: capacity records withdrawn after a matching review are retained and flagged rather than deleted, so any figure previously quoted stays reconcilable, and the app never displays a withdrawn value. Capacity matched to a circuit only by an ambiguous equipment number can fill a gap but can no longer overwrite a confidently-identified figure.
• v1.6.18 — Per-user logins & admin console: the shared access password is replaced by individual accounts — every user signs in with their own email and password. An in-app Admin page lets an administrator create users, enable/disable access instantly, reset passwords, and remove accounts. Disabling a user revokes their session on the very next request. Q-Headroom Pro: a new behind-the-login map adds a 50 MW datacentre hosting-feasibility layer alongside the BESS Q-headroom layer. Thermal accuracy fix: branches with no real rating in the dataset no longer report phantom overloads — the hosting verdict now counts only branches that carry a genuine rating.
• v1.6.17 — Engine generalisation: the convergence scoping is now device-agnostic, so a datacentre-only analysis (no BESS) is judged on its own electrical sub-network just like a BESS solve. Preparatory work for the Q-Headroom Pro datacentre layer.
• v1.6.16 — Datacentre large-demand what-if: drop a datacentre pin to model a large constant P/Q demand (up to 200 MW contracted) at a chosen utilisation. The datacentre connects like a generation pin — nearest/chosen substation, line tap, or a drawn dedicated line — and is solved as a steady-state PQ load bus. The engine also surfaces a heuristic in-rush & fault-duty screen at the connection point, derived from the solved network impedance. Limitation: Katana is a steady-state (fundamental-frequency) solver, not a transient/EMT model, so in-rush and fault duty are order-of-magnitude screening estimates only — always labelled as such, and never a substitute for a transient study. The CPAT export carries the datacentre load, and the results panel badges the demand scenario with the steady-state-only caveat.