Electrical Systems & Energy
Microgrids, substations, grid twins, DER forecasting and carbon compliance.
A general-purpose chatbot will give you a plausible paragraph about pavement deterioration. It will not give you the decay curve for your climate, your axle loads and your structural number — with the treatment window, the deferral penalty and the cost per square metre attached.
These fifty tools do. Each one carries a named method, a stated standard and real backend logic. They run in your browser, on your data, for nothing.
Governmental authorities, mega-project developers and large industrial corporations do not fail at O&M for lack of general advice. They fail at the point where a decision needs a defensible number — and that number needs a domain framework, a regulatory model, and operational logic that a conversational answer cannot carry.
Every tool states the method it runs — Webster's optimum cycle, median-rank Weibull regression, the Joukowsky equation, Saaty's eigenvector weights — so the result can be checked line by line, and defended in a review where someone disagrees with it.
Results reference the standard that decides them: ASTM D6433, EN 1993-1-9, IEC 62443-3-3, ISO 55001, FEM 1.001, ISO 12944. Where a threshold is breached the tool names the clause, not a sentiment.
Single-file, client-side applications. No backend, no database, no upload. That is what makes them usable on a client's own survey data on day one, without a procurement conversation about where the data goes.
Forty tools sit across the conference's eight core tracks. Ten more address cross-regional mega-infrastructure problems that do not fit a single track — Gulf corrosion, African rural microgrids, European district heating, Asian flood drainage, cross-border rail, port cranes and national asset registers.
Microgrids, substations, grid twins, DER forecasting and carbon compliance.
Pavements, bridges, autonomous corridors, signals and rail corridors.
CMMS, CAFM and EAM — reliability maths, integration and spares.
Desalination, transients, aeration energy, resilience and whole-life cost.
HVAC, BMS semantics, certification, vertical transport and handover.
OT security, private 5G, smart contracts, AR procedures and telemetry integrity.
Competence frameworks, simulators, curricula, certification and knowledge bases.
SAMP, AHP capital allocation, ESG, PPP risk and portfolio optimisation.
Gulf corrosion, African microgrids, European heat, Asian flood, global rail and ports.
Each tool asks for what you already hold — a PCI score, a strain reading, an SDI figure, a point list, a failure-time series. Defaults are realistic, so you can see the logic working before you touch anything.
A written verdict in plain language, six headline metrics with pass/fail colouring, a chart, a detail table, and a short list of what to do next. Export to CSV, print it, or copy a structured brief into your own document.
Where a result depends on an assumption that matters — alpha factor, detail category, discount rate, emission factor — the tool says so and tells you what it would take to measure it properly rather than estimate it.
These tools do the arithmetic, the index conversions, the option sweeps and the compliance checks. They do not take responsibility for the outcome. A qualified engineer reviews and signs; the tool never does.
The tools are free because they are the part that can be given away. What cannot be automated is knowing which authority is about to issue, what the evaluator actually scores, which credential gap will disqualify you at prequalification, and how to write the technical submission that survives the panel. That is the engagement.
We will tell you honestly whether it is winnable for you, what the gap is, and what it would take to close it — before anyone discusses a fee.
A deterioration curve built on one condition survey is a hypothesis. Two surveys make it a rate. The tools say which inputs carry the result so you know what to go and measure.
They size, screen, rank and check. They do not produce an issued design, and no output here should be construed as a certified calculation.
No live feeds, no integrations, no stored sessions. If a tool needs your SCADA history, you paste the series in — and it stays in the tab.