The Twin
Twenty entity types. Thirty-eight relationships. One graph.
What Is In The Model
The AI build-out is normally researched one domain at a time. Energy analysts model the grid. Semiconductor analysts model the supply chain. Cloud analysts model compute. Each is rigorous, and none of them can see past its own boundary.
Ridian holds eleven domains in a single graph:
- Land and environment: parcels, zoning, water stress, grid regions, market zones
- Energy and grid: generation, substations, connection queues, pools and headroom
- Supply chain: foundries, advanced packaging, chip SKUs, enabling equipment lead times
- Facilities: data centres, fabs, exchange points, with capacity, cooling and live load
- Compute: clusters, services and platforms, and what actually runs on them
- Data and models: training sets, foundation models, and where each is stored and trained
- Research: universities and national labs, benchmarks and published results, and the grant and incentive programmes funding them
- Applications and demand: the software consuming the compute, and the business segments driving it
- Commercial: contracts, offtakes, PPAs, funds and ownership
- Governance: legislation, export controls, planning permission, technical standards
- Evidence: the observations underpinning every claim above
Every entity carries a lifecycle stage, so the graph distinguishes what is announced from what is under construction from what is energised, and remembers when each of those changed.
Why The Joins Matter
A policy decision changes a grid connection. The grid connection delays a data centre. The data centre was going to house a GPU cluster. The cluster was going to serve a model. The model sits underneath an application with real customers and real revenue.
Five hops. Five domains. Five different specialist teams, none of whom holds the whole chain.
Ridian holds it as a single path, traversable in either direction. Ask it forwards to find the blast radius of a disruption. Ask it backwards to find what is really constraining a deployment. The answer is the same graph either way.
What It Deliberately Is Not
Within any single domain, Ridian captures enough to enable traversal and no more. It is not SCADA for the grid, not ERP for construction, not MLOps for models. Those systems go deeper than Ridian ever will.
Depth is a solved problem. The joins are not.