THE SAPTARISHI SERIES — GAUTAMA LAYER

India has already crossed an important threshold in infrastructure planning. The country no longer has to imagine what a national geospatial planning environment might look like. PM GatiShakti has created one.

Five years after its launch, the National Master Plan integrates more than 1,800 data layers across 58 Central Ministries and Departments and all 36 States and Union Territories. In October 2026, the Government reported that the Network Planning Group had evaluated more than 400 infrastructure projects worth about ₹20.23 lakh crore using PM GatiShakti principles. The platform allows ministries and states to see proposed interventions in relation to other networks, constraints and economic activity.

That is a significant institutional achievement. It also creates the conditions for a more difficult question.

What happens when national and regional infrastructure planning becomes geospatially intelligent, but the detailed information used to design, coordinate, construct and eventually operate individual projects remains in a different information world?

Also Read – India Has Digitised Land Records. Now It Needs a Digital Cadastre Backbone

The map and the model answer different questions

Geographic Information Systems are powerful because they understand location, networks, territory and context. They can show where a proposed corridor intersects settlements, utilities, environmental features, logistics nodes or other infrastructure. At national and regional scale, that context is essential.

Building Information Modelling operates at another level of resolution. A coordinated project model can contain spatial and technical information about a station, terminal, hospital, bridge, building or infrastructure facility. It helps teams understand geometry, systems, interfaces and change within the project itself.

Neither environment replaces the other. A national GIS platform does not need to become the design model of every project. Equally, a detailed project model cannot explain the full territorial and network context in which the project sits.

The management opportunity lies between them.

A transport interchange, for example, is simultaneously a detailed physical project and a node in a much larger mobility system. An airport terminal has internal systems, structures and operational spaces, but it also depends on roads, rail, utilities, drainage, logistics and surrounding land uses. A hospital may be coordinated internally to a high digital standard while still depending on external water, power, transport, emergency access and district-level infrastructure.

When those two scales of information remain disconnected, decision-makers may have excellent detail and excellent context, but not necessarily a dependable relationship between them.

India has already demonstrated the value of geospatial coordination

PM GatiShakti was designed precisely to address the problems created when infrastructure agencies plan in isolation. Its whole-of-government approach uses a common GIS-based environment to improve visibility between ministries and states, support alignment decisions and identify infrastructure interactions earlier.

That makes Gautama a different proposition from simply calling for another digital platform.

Within the Saptarishi Framework, I describe Gautama as the layer concerned with transportation and infrastructure intelligence. In its public form, the proposition is straightforward: the information used to plan infrastructure at network scale and the information used to deliver projects at asset scale should not become strangers to one another.

This does not mean creating one enormous model of India. Nor does it require every project to use identical software. Those would be technology answers to what is fundamentally an information-governance question.

The more useful question is whether a major project can retain enough continuity between its detailed design information and its wider geospatial context for decisions made at one scale to remain intelligible at the other.

The cost of losing context

Infrastructure projects accumulate context during their development: land constraints, utility interfaces, environmental conditions, adjacent projects, access requirements, logistics assumptions, future network connections and dependencies on other agencies.

Some of that information is represented geospatially. Some sits in design models. Some is embedded in drawings, reports, schedules, correspondence or approval systems.

When the project advances, the temptation is to treat each stage as if it needs only the information produced specifically for that stage. Planning becomes one information environment. Design becomes another. Construction becomes another. Operations eventually inherit whatever survives.

The result can be a subtle form of digital fragmentation. Every system may be sophisticated within its own boundary while the relationship between systems weakens over time.

For large infrastructure, that matters because the most expensive problems often sit at interfaces rather than inside isolated disciplines. A utility conflict is partly a project-design issue and partly a territorial-information issue. A changed road alignment may affect both project geometry and network planning. A future expansion corridor may be invisible if the asset is considered only as a completed object rather than as part of a changing infrastructure system.

From digital projects to infrastructure intelligence

India’s infrastructure programme now has something that many countries are still trying to assemble: a national geospatial planning capability with institutional participation at scale.

The next opportunity is to ask how the detailed digital information being created on individual capital projects can contribute to that larger intelligence without requiring the national platform to become a repository for every piece of project data.

That distinction is important. The objective is not data accumulation. It is decision continuity.

Can an authority understand how a detailed project change affects the wider network? Can a project team access the authoritative spatial context it needs without repeatedly recreating it? Can information created during delivery remain useful when the asset becomes operational and its surroundings continue to change?

Those questions sit at the intersection of BIM, GIS, infrastructure governance and institutional responsibility. They cannot be solved by file formats alone.

Gautama therefore asks us to treat infrastructure information as something that must remain meaningful across scale: from object to asset, from asset to corridor, and from corridor to network — without confusing those scales or collapsing them into one technical system.

Why project maturity makes this urgent

This question will become more important as public agencies and major developers raise their expectations for digital delivery. Better coordinated models, richer geospatial data and more sophisticated project controls create value individually, but they also increase the cost of losing relationships between information environments. The more digitally capable a project becomes, the less acceptable it is for context to be reconstructed manually each time a decision crosses an organisational boundary.

That does not require a single national BIM mandate. It requires a governance expectation that important project information can be related to authoritative geography and infrastructure context at the moments when decisions genuinely depend on both.

The readiness question

The strongest test is not whether an organisation owns BIM software or has access to a GIS portal. It is whether the two information environments can support the same management decision when the decision requires both detailed project knowledge and wider infrastructure context.

India has already shown that geospatial integration can change how infrastructure is planned. The next step is to make sure the increasing sophistication of project-level digital delivery does not develop as a parallel universe.

The value will come from continuity: preserving enough relationship between the project and the network so that infrastructure remains understandable as both a physical asset and part of a larger system.

If project and geospatial systems had to support one major management decision tomorrow, would they produce one reliable answer — or several competing ones?

About The Author – (Apurva Pathak is a New Zealand-based architect, design manager, and built-environment governance
practitioner with more than three decades of experience across India, the Gulf, Africa, Papua New Guinea, and New Zealand. He is the author of the Saptarishi Framework, a proposed seven-layer Digital Public Infrastructure architecture for India’s built environment, integrating BIM, GIS, land governance, municipal automation, digital twins, environmental intelligence, and resilience planning.)

Disclaimer—(The views and opinions expressed in this article are solely those of the author and do not necessarily reflect the views of Indian Masterminds. For feedback or queries, please write to [email protected].)

Read Also: Why Does India Continue to Lose So Many Lives on Its Roads?