The renewal case, traced back to the asset.
Horizon is asset investment planning. It reads the register and the condition history, projects renewal need over a long horizon, and turns that into multi-year budget scenarios and submissions a board or a regulator can follow back to the asset data underneath.
This page describes what we are building, not something you can buy today. It is here because operators keep asking for it, and because the shape of it is still open enough that an operator's input changes it.
The capital plan and the asset register disagree.
Most operators keep two versions of the truth about their assets. One lives in the maintenance system: what is installed, how old it is, what has broken and what it cost. The other lives in a spreadsheet somebody builds in the autumn to support next year's capital submission, using round numbers and an engineer's judgement about which assets are near the end.
The second one is what gets funded. It is also the one nobody can reproduce a year later, because the reasoning behind each line lived in the head of whoever wrote it. When the regulator asks why a particular renewal is needed in year three rather than year six, the answer has to be reconstructed.
Horizon is meant to close that gap: one projection, built from the register, that can be re-run when the register changes and that carries its own working.
What we are building.
The scope below is the current design. It is not a commitment, and it will move as operators tell us what they actually have to defend.
Remaining Life at Asset Level
A remaining-life estimate for each asset, from its class, its age, its condition assessments and its own failure history, rather than one blanket design life applied to a whole category.
Multi-Year Budget Scenarios
Renewal need projected over a long horizon, and the ability to run the plan again under a different budget ceiling to see what gets deferred and what that deferment does to condition and risk.
Submissions That Trace Back
Renewal cases for boards and regulators where every figure can be followed down to the assets behind it, and the whole thing can be re-run next year against the register as it then stands.
Where it stands today.
Horizon is in development. There is no release you can use, no demo environment and no date we are prepared to put on this page. When there is something worth showing, it will be shown here the way the other two products are, with screenshots of the real thing.
What does exist is the ground it stands on. Keystone Asset already holds the register, the condition records and the maintenance cost history Horizon needs to read. RISKSYS already computes which assets carry the consequence. Horizon is the layer that turns those into a funded plan.
If you are preparing a renewal submission and would be willing to tell us what it has to survive, that conversation shapes the product more than anything else at this stage.
- Built on the Keystone Asset register, not a separate data set
- Reads criticality from Keystone RISKSYS where an operator runs it
- Aligned to ISO 55000 asset management planning practice
- Hosted alongside the rest of the line, with UAE data residency available
- No release date, and no early-access programme to sign up to yet
The two you can use today.
Keystone Asset
The hosted asset management system: asset register, work orders, maintenance planning, spare parts, fuel and cost reporting, aligned to ISO 55000. This is the record Horizon will plan against, and it is in daily operational use now.
About Keystone AssetKeystone RISKSYS
The network reliability studio. Build the network, describe how each asset fails, and simulate where supply is lost first and which asset to renew to change that. The studio runs in your browser today.
About Keystone RISKSYSTell us what your renewal case has to survive.
We are not selling Horizon yet. We are trying to build the right thing. Write to sales@praxisam.com or use the contact form.