Single file, no server
Every Aetherix console ships as one standalone HTML file. It opens in a browser, runs with the network cable unplugged, and holds no client data anywhere but the machine it is on.
Engineering intelligence
Aetherix builds standards-led consoles that turn field data into a defensible verdict — lightning risk, asset condition, flood exposure, line capacity, fault cause, storage economics and highway inundation. Each one ships as a single file that runs offline, under your own brand.
The problem we build against
Condition sits in one system, geography in another, the network model in a third and the regulation in a PDF. The decision gets argued from instinct, and the document that justifies it is assembled by hand the night before. Aetherix closes that gap with engines that compute the answer, prescribe the fix, and compile the report from the same live model.
Every Aetherix console ships as one standalone HTML file. It opens in a browser, runs with the network cable unplugged, and holds no client data anywhere but the machine it is on.
The engines are built on published standards and the report states its basis explicitly, so a reviewer can follow the method rather than trust the badge.
Reports compile from whatever state the model is in and flag themselves stale the moment an input changes. The number in the document always matches the model that produced it.
Wordings, branding and house style are yours to set. The client sees your firm, not ours.
Confidence levels, duration curves, sensitivity sweeps and abstention rules are built in, because a single point estimate is what makes engineering software untrustworthy.
No cloud dependency, no rate limit, no silent model update between the draft and the signature. The same inputs give the same answer next year.
Products
Each product owns a decision that utilities, consultants and infrastructure owners have to defend in writing.
From site data to a defensible IEC 62305-2 verdict.
A complete lightning-risk console. Every component R_A…R_Z across up to five zones, protection measures prescribed and the whole calculation re-run to prove the protected state — with an optional embedded ground-flash-density grid for Peninsular Malaysia.
Read the full write-upYour grid on a map, health-scored where it actually sits.
Substations and circuits mapped from your own KMZ and PSS/E RAW, scored on a CIGRE health index, then ranked into an intervention queue by risk reduction per ringgit.
Read the full write-upWhich substations drown first — and which ones matter when they do.
Scenario-aware pluvial, fluvial and coastal flood screening across your substation fleet, consequence-weighted by network criticality and priced in SAIDI minutes and expected annual loss.
Read the full write-upThe capacity is already in the ground. Prove it, then bank it.
A field-validated IEEE 738 dynamic line rating engine that quantifies the headroom your static rating hides, tests it against heatwave physics, and compares it honestly against reconductoring.
Read the full write-upSolutions
Most engagements start with a question rather than a product. These are the four we are asked most often.
Condition, criticality and consequence joined into one risk-ranked, budget-constrained programme you can take to a capital committee.
Prove the headroom already in the ground, and shorten the distance between a trip and a patrol plan.
Scenario-aware exposure screening for grid and highway assets, priced in customer-minutes and ringgit rather than in colours on a map.
Standards-led verdicts and tariff-accurate business cases, compiled into documents that survive review.
Engagement
Aetherix works both ways. Take the console and run it yourself, or have us operate it and deliver a signed report.
Licence any console for your firm, white-labelled, with the wordings and report identity set to your house style.
We operate the same engines on your behalf and deliver a signed, defensible report — risk assessments, capacity studies, resilience screening and business cases.
Independent review of proposed designs, existing installations and third-party studies against the relevant standard — useful for tenders, disputes and sign-off.
A new console built around your method, your data and your regulatory context, delivered on the same single-file, offline, standards-first basis.
Tell us the asset, the standard and the deadline. We will tell you which console answers it and what we need from you to start.
or write to aetherix.systems@gmail.com
Products & solutions
Seven standards-led engineering consoles. Every one of them takes data you already have, computes an answer you can defend, and compiles the document that defends it. Open any write-up for further details.
Grouped by the decision each console owns. Click through for the full page — problem, capability, outputs and delivery model.
From site data to a defensible IEC 62305-2 verdict.
A complete lightning-risk console. Every component R_A…R_Z across up to five zones, protection measures prescribed and the whole calculation re-run to prove the protected state — with an optional embedded ground-flash-density grid for Peninsular Malaysia.
Read the full write-upYour grid on a map, health-scored where it actually sits.
Substations and circuits mapped from your own KMZ and PSS/E RAW, scored on a CIGRE health index, then ranked into an intervention queue by risk reduction per ringgit.
Read the full write-upWhich substations drown first — and which ones matter when they do.
Scenario-aware pluvial, fluvial and coastal flood screening across your substation fleet, consequence-weighted by network criticality and priced in SAIDI minutes and expected annual loss.
Read the full write-upThe capacity is already in the ground. Prove it, then bank it.
A field-validated IEEE 738 dynamic line rating engine that quantifies the headroom your static rating hides, tests it against heatwave physics, and compares it honestly against reconductoring.
Read the full write-upClassify why the line tripped — in seconds, not days.
Drop a recorder capture and FaultSense identifies the faulted terminal, ranks the probable root cause with calibrated confidence, and estimates the distance to the fault.
Read the full write-upThe battery mandate, turned into the fastest-payback asset on site.
Sizes solar and storage against the full RP4 bill engine, sweeps the battery block for payback-optimal capacity, and clears the ST compliance gates in the same screen.
Read the full write-upKnow which stretch of expressway floods before the traffic does.
Segment-level inundation risk across an expressway network, tuned by climate horizon, rainfall sensitivity and consequence weight, with recommended actions and a report studio.
Read the full write-upBy decision
Condition, criticality and consequence joined into one risk-ranked, budget-constrained programme you can take to a capital committee.
Prove the headroom already in the ground, and shorten the distance between a trip and a patrol plan.
Scenario-aware exposure screening for grid and highway assets, priced in customer-minutes and ringgit rather than in colours on a map.
Standards-led verdicts and tariff-accurate business cases, compiled into documents that survive review.
Describe the asset and the decision. We will point you at the right console — or tell you honestly that we do not have one for it yet.
or write to aetherix.systems@gmail.com
Solutions
Aetherix consoles are built around the four questions we are asked most: what do we fix first, how much capacity do we really have, what does the climate do to this asset, and does the business case survive review.
Condition, criticality and consequence joined into one risk-ranked, budget-constrained programme you can take to a capital committee.
Prove the headroom already in the ground, and shorten the distance between a trip and a patrol plan.
Scenario-aware exposure screening for grid and highway assets, priced in customer-minutes and ringgit rather than in colours on a map.
Standards-led verdicts and tariff-accurate business cases, compiled into documents that survive review.
How we work
Licensing and consultancy are not separate businesses here — they are the same engines, operated by you or by us.
Licence any console for your firm, white-labelled, with the wordings and report identity set to your house style.
We operate the same engines on your behalf and deliver a signed, defensible report — risk assessments, capacity studies, resilience screening and business cases.
Independent review of proposed designs, existing installations and third-party studies against the relevant standard — useful for tenders, disputes and sign-off.
A new console built around your method, your data and your regulatory context, delivered on the same single-file, offline, standards-first basis.
At a glance
Aetherix product line
| Console | Domain | Standards basis | The decision it owns |
|---|---|---|---|
| StrikeGuard | Risk & Protection | IEC 62305-2 | From site data to a defensible IEC 62305-2 verdict. |
| AFMS Sentinel | Asset Intelligence | CIGRE TB 858 · ISO 55000 | Your grid on a map, health-scored where it actually sits. |
| SubMerged | Climate Resilience | ISO 55000 · CIGRE-aligned | Which substations drown first — and which ones matter when they do. |
| iDLR Insight | Network Capacity | IEEE 738 | The capacity is already in the ground. Prove it, then bank it. |
| FaultSense | Operations | COMTRADE · evidence fusion | Classify why the line tripped — in seconds, not days. |
| SURIA·BESS | Energy Economics | RP4 tariff · ST rules | The battery mandate, turned into the fastest-payback asset on site. |
| HIWAY | Infrastructure Resilience | Climate-horizon risk engine | Know which stretch of expressway floods before the traffic does. |
The engagements that work best start with the decision nobody wants to sign. Send it over.
or write to aetherix.systems@gmail.com
About Aetherix
Aetherix Systems is an engineering-intelligence practice working across power transmission and distribution, renewable energy and public infrastructure. We started where most of our clients still are — defending a capital decision with a spreadsheet — and built consoles that compute the answer properly and compile the document that justifies it. Malaysia-first in context, standards-based by construction, so the same engines deploy anywhere.
How we build
These are not values on a wall. Each one shows up as a feature you can point at.
Every Aetherix console ships as one standalone HTML file. It opens in a browser, runs with the network cable unplugged, and holds no client data anywhere but the machine it is on.
The engines are built on published standards and the report states its basis explicitly, so a reviewer can follow the method rather than trust the badge.
Reports compile from whatever state the model is in and flag themselves stale the moment an input changes. The number in the document always matches the model that produced it.
Wordings, branding and house style are yours to set. The client sees your firm, not ours.
Confidence levels, duration curves, sensitivity sweeps and abstention rules are built in, because a single point estimate is what makes engineering software untrustworthy.
No cloud dependency, no rate limit, no silent model update between the draft and the signature. The same inputs give the same answer next year.
Domains
Transmission and distribution asset management, network capacity and operations, climate resilience for grid and highway assets, lightning and electrical protection, and renewable-plus-storage economics. Regulatory context is Malaysian by default; the methods are drawn from IEC, IEEE, CIGRE and ISO publications and travel.
From site data to a defensible IEC 62305-2 verdict.
Your grid on a map, health-scored where it actually sits.
Which substations drown first — and which ones matter when they do.
The capacity is already in the ground. Prove it, then bank it.
Classify why the line tripped — in seconds, not days.
The battery mandate, turned into the fastest-payback asset on site.
Know which stretch of expressway floods before the traffic does.
Engagement
Licence any console for your firm, white-labelled, with the wordings and report identity set to your house style.
We operate the same engines on your behalf and deliver a signed, defensible report — risk assessments, capacity studies, resilience screening and business cases.
Independent review of proposed designs, existing installations and third-party studies against the relevant standard — useful for tenders, disputes and sign-off.
A new console built around your method, your data and your regulatory context, delivered on the same single-file, offline, standards-first basis.
Questions
Licensing, studies, second-opinion review or a custom engine — start with an email and we will scope it honestly.
or write to aetherix.systems@gmail.com
Contact
One email address, answered by the people who build the engines. Describe the asset, the standard and the deadline — we will tell you which console fits and what we need from you to start.
This form composes an email in your own mail client — nothing is submitted to a server, and no data leaves your device until you press send.
Intelligence Beyond Boundaries
Malaysia — working across Peninsular Malaysia and the wider ASEAN region, remotely and on site.
Enquiries are read by an engineer, not a queue. Expect a scoped reply rather than a sales sequence.
Client data stays on your machine. Where a study needs your data, we agree the handling terms before anything moves.
Clear standard, clear deadline — we can quote from that.
That is AFMS Sentinel, and we can show you the queue in a week.
That is iDLR Insight, and it is the cheapest study you will run this year.
No forms to chase, no gatekeeping. Write to us and we will answer with something useful.
IEC 62305-2 · Risk management console · two editions
StrikeGuard turns a day of spreadsheet drudgery into a defensible lightning risk assessment — computed live, verified before and after protection measures, and issued as a one-page PDF summary and a full Excel report. Choose the standard edition, or the Peninsular Malaysia edition that reads the flash density straight off an embedded six-year grid.
Why StrikeGuard
IEC 62305-2 is a web of collection areas, probability factors and loss values across four damage sources and up to five zones. Doing it by hand is slow. Defending it in front of a client, insurer or authority is worse.
One transcription slip in a loss factor and the whole verdict moves. Nobody can audit a spreadsheet built in a hurry.
Telling an owner the risk is too high without prescribing and proving the fix leaves the job half done.
N_G is the input the whole calculation scales on, and it is routinely read off an isokeraunic chart by eye — then never recorded in the report.
A verdict is only as good as the working behind it. A reviewer, insurer or authority wants to see every risk component, per zone — not just the headline figure.
The console
Structure, power line, telecom line and up to five zones. Collection areas, N_D/N_M events, and every probability and loss factor from Annexes A–C — recalculated live as you type.
The engine finds the dominant risk component per failing zone, prescribes IEC 62305-3/-4 measures, then re-runs the full calculation to verify the protected state.
One click generates the client deliverables: a one-page PDF verdict summary for the file, and a full Excel report carrying the summary, inputs, zone data and per-component risk detail across four sheets — built live from your inputs, not boilerplate.
No server, no cloud, no telemetry — the console runs with the network cable unplugged. Saved assessments are encrypted on device with AES-GCM under a key derived from your password with PBKDF2.
Choose your edition
The risk calculation is identical in both. What differs is where the lightning environment comes from — typed in by the assessor, or read out of an embedded grid.
You supply N_G.
The assessor enters ground flash density from the source they are required to cite — a national meteorological figure, a network operator's data set, or the value specified in the project brief. Every other part of the engine is unchanged.
Lock the coordinates. The grid supplies N_G.
A six-year ground-flash-density surface for Peninsular Malaysia is embedded in the file. Lock the site position and the console reads the flash density for that cell, derives the ground strike point density, and stamps the provenance into the report.
Peninsular Malaysia edition
N_G is the term the entire IEC 62305-2 calculation scales on. In most assessments it is read off a contour map by eye and never recorded. The GFD edition removes that step entirely.
You are viewing the standard edition. The embedded grid described below ships only in the Peninsular Malaysia edition — switch the edition selector above to see how it works.
Enter or pick the coordinates and lock them. The console resolves the grid cell containing that position.
The six-year mean ground flash density for that cell is returned in flashes per square kilometre per year, with the cell class shown on the map.
N_SG = k · N_G, with k = 2 — an average of two ground strike points per ground flash, the practice this console adopts under IEC 62305-2.
The locked coordinates, grid class, N_G, k, resulting N_SG and the source layer are written into the assessment record and carried into every report.
| Region | Peninsular Malaysia |
|---|---|
| Period | 2012–2017 · six-year mean |
| Grid | 547 × 607 cells at 1 km |
| Bounds | 1.247°N – 6.741°N, 99.626°E – 104.554°E |
| Projection | WGS84 geographic |
| Delivery | Embedded in the file — no tile server, no API key |
The surface is a measured flash rate conditional on detection-network availability over the recording period — not an estimate of the true climatological rate, and no coverage uplift is applied. Positions on no-data cells (sea, or outside the mask) resolve to the nearest classified cell and the console reports the offset distance rather than hiding it. Where a project or authority mandates a specific N_G source, enter that value instead — the standard edition exists for exactly that case. The console reads a continuous surface where one is available, and otherwise falls back to five-class behaviour — in which the five legend values are entered once from the source symbology before a position can be converted to N_G.
How it ships
One file, no server — the console runs with the network cable unplugged, and every deliverable is generated on your own machine.
Every risk component in the standard, per zone, not just the headline R.
Zones supported, each with its own tolerable-risk and frequency criteria.
Vault encryption, with the key derived from your password via PBKDF2.
Servers. The console runs with the network cable unplugged.
Licence StrikeGuard to run defensible IEC 62305-2 assessments in-house — or have Aetherix run the assessment for you.
or write to aetherix.systems@gmail.com
GIS asset fleet · ISO 55000 · CIGRE-aligned
AFMS Sentinel binds your substation coordinates, circuit geometry and network model into one health-scored fleet view — then turns it into a defensible, budget-constrained intervention plan.
Why AFMS Sentinel
Condition data lives in one system, coordinates in another, the network model in a third, and the flood map in a PDF. The investment case gets argued on instinct because nothing joins them up.
A health index of 3.8 means one thing on a radial spur and something else entirely on a backbone intake feeding a hospital.
Low-lying, coastal and steep-access sites carry real probability-of-failure and restoration-time penalties that never reach the ranking.
Without risk-reduction-per-ringgit, the queue is set by whoever escalated most recently.
The console
Substations from your PMU KMZ, circuits from your Lines & Cables KMZ, rendered on an embedded 20 m digital-elevation basemap with hillshade and hypsometric tint — no external tiles, so it works offline.
Five-band health index across the mapped fleet, recomputed live against a tuneable intervention threshold, with the band distribution and regional snapshot updating as you tune.
Ground elevation and local slope sampled per substation. Flood susceptibility, landslide exposure and access difficulty can be switched on to modify probability of failure and restoration time — off by default, so the core engine stays auditable.
Load your PSS/E RAW case to bind loads and voltage tiers to the mapped fleet, so criticality weighting reflects the real system, not a nameplate guess.
Annualised risk as probability of failure × monetised consequence, with value-of-lost-load, criticality weight, corrosion factor and annual budget as live strategy levers.
Ranked by risk reduction per ringgit inside your budget envelope — the shortlist you can actually take to a capital committee.
Outputs
Sentinel compiles a journal-style technical report from whatever state the model is in — every figure and table reflects the scenario you tuned.
Introduction, data sources, method, health-band results, sensitivity analysis and conclusion — the full condition record.
How the PSS/E case binds to the mapped fleet, voltage-class composition and criticality derivation.
Annualised risk exposure, the ranked intervention queue and the budget-constrained programme.
The CIGRE and ISO 55000 basis, stated explicitly so a reviewer can follow every step.
GIS asset fleet · risk & investment plan
Illustrative fleet · intervention band ≥ 3 · budget RM 150 M/yr
| Rank | Substation | kV | Health | Risk RM M/yr |
|---|---|---|---|---|
| 1 | Site A (coastal) | 275 | 4.4 | 18.2 |
| 2 | Site B (urban intake) | 132 | 4.1 | 14.7 |
| 3 | Site C (backbone) | 500 | 3.6 | 12.9 |
How it ships
One file, no server, your branding on the deliverable — the same delivery model behind every Aetherix console.
CIGRE health bands across the mapped fleet.
Elevation basemap embedded in the file — no tile server.
Terrain lenses: flood, slope/landslide and access.
File. Map, engine, report and exports all ship together.
Bring your own KMZ, CSV, GeoJSON and RAW. Sentinel maps them, scores them and hands back a funded programme you can defend.
or write to aetherix.systems@gmail.com
Flood risk · resilience · GIS
SubMerged screens pluvial, fluvial and coastal exposure across the whole substation fleet, weights it by what each node actually carries, and prices the result in customer-minutes and ringgit.
Why SubMerged
A severely exposed radial spur and a moderately exposed backbone intake are not the same risk. Screening hazard alone puts the wrong assets at the top of the list and the wrong number in the business case.
Without binding exposure to the network model, ranking rewards the wettest site rather than the costliest outage.
Boards approve capital against today's map, then discover the asset was sized for a horizon that has already passed.
Energised switchgear standing in water is an electrocution and arc-flash hazard. De-energisation candidates should be identified before the water arrives, not during.
The console
Drag-and-zoom geographic projection with colour lenses for flood band, network criticality, voltage class and existing-versus-future assets — recomputing live with horizon, climate scenario and ENSO phase.
A network criticality index derived from the bound PSS/E case promotes flood-moderate backbone nodes above severely exposed radial spurs, which is where the real money is.
Every station with its band, raw flood score, weighted score, customers affected, SAIDI contribution and expected annual loss — filterable to critical service only.
Both scenarios plotted across horizons so the capital decision is made against the asset's service life, not this year's rainfall.
SAIDI minutes and value-of-lost-load converted into expected annual loss in ringgit, with the VoLL envelope exposed as a live sidebar lever.
Candidate stations for pre-emptive de-energisation flagged against a drainage floor, so the safety case is prepared in advance and documented.
Outputs
Every figure in the report is generated from the live model state, with the public-record anchors and assumptions stated in the document itself.
Risk-band distribution, state and regional snapshot, hazard driver breakdown and the consequence-weighted queue.
Expected annual loss, avoided customer-minutes and the prioritised hardening programme.
Monsoon calendar, ENSO modulation and the wet-season paradox, with the statistical correlations set out.
Flagged stations, drainage assumptions and the OSH rationale for each candidate.
Flood risk · consequence-weighted register
Illustrative fleet · SSP5-8.5 · horizon 2046 · VoLL RM 15/kWh
| PMU | kV | Band | Flood | EAL RM M/yr |
|---|---|---|---|---|
| Intake A | 275 | Severe | 84 | 22.4 |
| Intake B | 132 | High | 71 | 15.1 |
| Intake C | 500 | Moderate | 58 | 13.8 |
How it ships
One file, no server, your branding on the deliverable — the same delivery model behind every Aetherix console.
Climate scenarios, SSP2-4.5 and SSP5-8.5, run side by side.
Risk trajectory from 2026 to 2056.
Hazard pathways: pluvial, fluvial and coastal.
External API calls. The screening is fully reproducible offline.
Bring your fleet and network case. SubMerged returns a ranked, priced, scenario-tested resilience programme.
or write to aetherix.systems@gmail.com
Dynamic line rating · field-validated
iDLR Insight calibrates a corrected IEEE 738 thermal model against real field records, shows how dependable the extra ampacity actually is, and turns deferred reinforcement into a number a planner can sign.
Why iDLR Insight
Conductors are rated for a stagnant, sun-drenched, worst-case hour. Most hours are not that hour. The gap is real capacity — but nobody will dispatch against it without evidence of how dependable it is.
An average uplift means nothing to a system operator. What matters is the ampacity available at the confidence level they are willing to run.
At many sites hot afternoons are also windy, so naive analysis shows higher capacity in heat. Hold wind fixed and the sign flips.
Reconductoring is costed while the cheaper option — running the existing conductor to its real thermal limit — is never quantified.
The console
A corrected IEEE 738 model calibrated to field data and driven live by ambient temperature, wind speed, wind angle, cloud cover and conductor limit.
A duration curve of measured rating across the full record, so headroom can be claimed at a stated confidence rather than as a mean.
Each driver swept while the others are held at your current settings — the local slope is what operators actually feel.
Mean measured rating across the ambient-temperature by wind-speed plane with your operating point ringed, so the gradient of the opportunity is visible.
Temperature and wind separated so the sea-breeze confound is removed. The compound risk case — heat arriving with stagnant air — is modelled explicitly.
The DLR case set against the reconductoring case on the same basis, so deferral value is quantified rather than asserted.
Outputs
Pick a focus and the technical report restructures itself around it. On Auto, the focus follows whichever page you are tuning.
Data, method, results, discussion and limitations — the full journal-style record for the corridor.
Influence ranking consolidated from correlation, permutation importance and practical ampacity swing.
The compound heat-plus-stagnant-air case and what it means for firm capacity.
Connection headroom framed for a large, time-critical load without waiting for reinforcement.
Dynamic line rating · corridor study
Illustrative corridor · 275 kV · conductor limit 75 °C
| Wind regime | Mean DLR | vs static | P95 available | Hours |
|---|---|---|---|---|
| Calm 0.5–1 m/s | 1,290 A | −9% | 1,140 A | 18% |
| Moderate 1.5–2.5 | 1,880 A | +23% | 1,610 A | 54% |
| Breezy 3–6 | 2,340 A | +53% | 2,020 A | 28% |
How it ships
One file, no server, your branding on the deliverable — the same delivery model behind every Aetherix console.
The thermal basis, corrected and calibrated rather than assumed.
Report focuses compiled from the same live model state.
Options compared on one basis: dynamic rating and reconductoring.
Cloud dependency. Tuning and reporting run locally.
Bring your conductor data and field records. iDLR Insight returns a defensible operating concept and a deferral case.
or write to aetherix.systems@gmail.com
Fault discrimination · evidence fusion
Drop a COMTRADE or recorder capture. FaultSense identifies the faulted terminal, ranks the probable cause against your own confirmed-fault history, and — given the line's reactance — estimates the distance to the fault.
Why FaultSense
Root-cause classification is done by whoever is free, from memory, days later. Patrols go to the wrong span, repeat faults get filed as one-offs, and the vegetation budget is argued without evidence.
Two engineers looking at the same oscillogram reach different conclusions, and neither writes down the reasoning.
A guess and a well-evidenced verdict look identical in the outage report, so both are trusted equally — or neither is.
Hundreds of captures sit unexamined because processing them one at a time is not worth anyone's week.
The console
Stage one applies tuneable thresholds — deep voltage dip, surge ratio, fault duration — so the first cut is deterministic and inspectable, not a black box.
Stage two runs a naive-Bayes posterior over cause priors that you set from your own confirmed-fault history, because a balanced prior is wrong for every real network.
A temperature parameter softens overconfidence, and the engine returns REVIEW rather than a verdict when the top posterior or the top-to-second ratio falls below your thresholds.
Given positive-sequence reactance and line length, distance is computed from the captured voltages and currents, with the zero-sequence ratio improving line-to-ground accuracy.
Drop hundreds of files or a whole folder at once. Flat CSVs containing many oscillograms are detected and split automatically. Batch size is limited by disk, not memory.
Rename every cause class and edit the recommended field action shown with each verdict, then export the configuration as JSON to share across the team.
Outputs
Every classification carries its terminal, confidence, distance band and the recommended field action — exportable as CSV for the outage record.
Faulted terminal, ranked cause, confidence, surge ratio, dip depth, duration and estimated distance.
The whole backlog classified in one table, ready for the outage management system.
Thresholds, priors, calibration temperature and class labels exported as JSON so the method is reproducible.
Records where the engine abstained, isolated for human adjudication rather than silently guessed.
Fault discrimination · batch summary
Two-stage engine · abstain threshold applied
| Record | Verdict | Conf. | Terminal | Dist. km |
|---|---|---|---|---|
| EV-0142 | Lightning | 0.87 | B | 24.6 |
| EV-0143 | Vegetation | 0.71 | A | 8.2 |
| EV-0144 | REVIEW | 0.44 | — | — |
How it ships
One file, no server, your branding on the deliverable — the same delivery model behind every Aetherix console.
Stages: deterministic physics, then calibrated evidence fusion.
Captures classified in a single batch run.
The engine says so when the evidence does not support a verdict.
Raw samples retained. Only summaries and a decimated plot are kept.
Point FaultSense at a folder of recorder files and get a classified, confidence-scored, distance-estimated table back.
or write to aetherix.systems@gmail.com
Solar + storage · RP4 economics · ST compliance
SURIA·BESS Strategy Lab sizes storage on the actual exceedance energy above your shave threshold — not a rule of thumb — sweeping the full tariff bill engine to find the payback-optimal block and proving compliance as it goes.
Why SURIA·BESS
Land caps the array long before the tariff caps it, solar peaks hours before the billed maximum demand, and the battery gets sized on a rule of thumb that has nothing to do with the bill.
Photovoltaic yield barely touches the maximum-demand line. The money left on the table sits in the capacity and network charge.
A battery required by regulation is budgeted as a cost of compliance instead of dispatched as the fastest-payback asset on the site.
A single payback figure with no degradation, no confidence level and no sensitivity does not survive the first question.
The console
Capacity charge, network charge, energy and peak-window structure modelled end to end, so every saving is attributed to a line on the invoice rather than to a blended rate.
The design day plotted as load, solar output, net import and the shaved profile against the peak window, with the shave threshold as a live control.
The battery block swept across the range against the full bill engine, marking the payback-optimal capacity and the firm-shave confidence you are willing to run at.
The regulatory and engineering constraints the configuration must clear — including the storage mandate above the array threshold and the ceiling on array size relative to maximum demand — checked live.
Point the model anywhere, pull hourly irradiance, temperature and cloud cover, and have peak sun hours and design temperature written straight into the yield and storage engines.
Net present value over the asset life with degradation applied year by year, project internal rate of return against a hurdle, and the cumulative cash position discounted and undiscounted.
Outputs
The technical report compiles from the live model, so the configuration in the document is the configuration you locked.
The decision in one section: recommended configuration, payback, annual saving, net present value and internal rate of return.
Where the annual saving comes from across the tariff stack — the breakdown the board will ask about.
Each sizing and regulatory gate with its pass condition and the configuration's margin against it.
How payback moves with tariff, degradation, load growth and shave confidence.
Solar + storage · business case
Land-limited array · commercial time-of-use tariff · peak window 14:00–22:00
| Metric | Solar only | Solar + BESS | Delta |
|---|---|---|---|
| Billed MD | 4,620 kW | 3,780 kW | −840 kW |
| Annual saving | base | improved | MD + energy |
| Simple payback | — | within horizon | on the block |
How it ships
One file, no server, your branding on the deliverable — the same delivery model behind every Aetherix console.
The commercial time-of-use structure modelled in full, not approximated.
Net present value horizon with degradation applied annually.
Storage sweep range against the live bill engine.
Hourly irradiance pulled for any coordinate you point at.
Bring your load profile and site coordinates. SURIA returns a sized, priced, compliance-cleared solar and storage configuration.
or write to aetherix.systems@gmail.com
Highway inundation · warning & alert
HIWAY scores every monitored segment of the expressway network for inundation risk, tunes it against climate horizon and monsoon phase, and turns the result into ranked, actionable interventions.
Why HIWAY
Expressway operators know which stretches have flooded before. What they lack is a scored, ranked, defensible picture that says which segment is exposed under this month's conditions and what to do about it.
Knowing that a segment flooded in 2021 is not the same as knowing its exposure under the current horizon and monsoon phase.
A short closure on a low-volume link and a closure on a strategic corridor are treated as the same event in most planning.
An alert that does not say what to do — raise signage, prepare pumps, stage a closure — gets acknowledged and then ignored.
The console
Every monitored segment with its length, exposure and current risk band, aggregated to a network-level picture of how many kilometres are at risk right now.
Climate horizon, consequence weight and rainfall sensitivity as live controls, so the risk picture can be stress-tested rather than accepted.
North-east monsoon and inter-monsoon modes shift the baseline, because the same segment carries a different exposure in December than in April.
Current conditions pulled into the model so the operational picture and the planning picture use the same engine.
Each elevated segment carries a specific action — drainage inspection, signage escalation, pump staging or closure threshold — rather than a bare score.
Define the report, generate it, adjust the sensitivity and regenerate. Print to PDF or download a standalone HTML copy for distribution.
Outputs
The report studio compiles a structured document from the tuned model — abstract, methodology, results and recommended actions.
The current picture: segments at risk, kilometres affected and the driving conditions.
Abstract, introduction, methodology and results in a structured, citable format.
Per-segment interventions with the threshold that triggers each one.
How the ranking moves as horizon, rainfall sensitivity and consequence weight change.
Highway inundation · network brief
North-east monsoon posture · consequence weight 0.60
| Segment | Length km | Band | Score | Action |
|---|---|---|---|---|
| K-12 | 6.4 | High | 81 | Stage pumps |
| K-07 | 4.1 | Moderate | 57 | Inspect drainage |
| K-21 | 9.8 | Low | 26 | Monitor |
How it ships
One file, no server, your branding on the deliverable — the same delivery model behind every Aetherix console.
The unit of analysis — not the whole network, not a single point.
Monsoon postures modelled, with an adjustable climate horizon.
Live levers: horizon, consequence weight and rainfall sensitivity.
Report formats generated straight from the tuned model.
Bring your segment inventory. HIWAY returns a scored network, ranked exposures and an action per segment.
or write to aetherix.systems@gmail.com