ENGINEERING SOFTWARE · DOMAIN METHODS
INSPOSOFT develops domain-specific software and computational tools for energy storage, hydrology, water systems, and flood engineering.
We make data, assumptions, methods, and limits visible. Technical teams can inspect the result before they act on it.
Instead of a generic “AI” story, we keep source data, engineering methods, assumptions, and outputs in one reviewable frame.
The shared visual language covers three working contexts: energy operation, site inflow, and flood computation. Each keeps its own data, methods, and outputs in view.
ENERGY · BOBO
We use EPİAŞ price and generation data to examine BESS scenarios. Hourly dispatch, capacity sizing, and economic assumptions stay in one analysis.
Output: dispatch · sizing · economic sensitivity
Decision: storage size · operating scenarioReview: operation · assumptions · economics
FIG. 01 — SYNTHETIC DISPATCH · MODELLED
HYDROLOGY · AĞKOLU · KEMERÇAYIR · ALMUS
These applications combine observed flow, weather, and snow signals. Each one provides a site-configured 16-day inflow forecast.
Output: daily forecast · charts · validation
Decision: 16-day inflow viewReview: Q₀ · observed · forecast band
FIG. 02 — 16-DAY INFLOW · Q₀ → D₁₆
FLOOD ENGINEERING · TAŞKIN HESAP
We combine basin and soil data with Thiessen rainfall, synthetic methods, frequency analysis, and routing. The result is a report-ready computational workflow.
Output: hydrograph · comparison · report · export
Decision: design flood · method choiceReview: basin · rainfall · method · hydrograph
FIG. 03 — BASIN → HYDROGRAPH · Q₂–Q₁₀₀
Trust grows when the data source, important assumptions, and result limits are visible.
Dynamic programming; weather and snow features; synthetic flood methods; frequency analysis; reservoir routing.
Scenarios, forecast tables, hydrographs, report sections, and exportable data.
Model outputs support engineering review; they do not claim universal accuracy or regulatory approval.
VERIFICATION LEDGER · 2026-08
Every engagement follows three steps: frame the problem, choose a proportionate method, and review the output with engineering judgment in the loop.
Clarify the decision, data sources, time horizon, and boundaries that the work must respect.
Make the computation visible through assumptions, scenarios, and intermediate outputs that can be compared.
Deliver a report, table, chart, or export while keeping the boundary between automation and engineering judgment explicit.
These synthetic graphics show the inputs and outputs an engineer would inspect.
05 · RESEARCH LINEAGE
Earlier work in reservoir rationing, water balance, hydro-unit allocation, and optimization remains available as a methodology archive.
ARCHIVED RESEARCH · NOT A CURRENT PRODUCTTell us what you are trying to understand. We will route the conversation to the relevant energy, hydrology, flood, or methods area.
The first conversation scopes the use case, available data, and useful technical output.