Samruddhi Mahamarg is open and operatingThe Western Dedicated Freight Corridor is runningNagpur MMLP is commercially liveThe data practice in construction and infrastructure is catching upSamruddhi Mahamarg is open and operatingThe Western Dedicated Freight Corridor is runningNagpur MMLP is commercially liveThe data practice in construction and infrastructure is catching up
Data Stack GlobalRegister interest
16 February 2027 · Nagpur, Maharashtra

The day, in full.
Nothing gated.

Six sessions, each built around a question a delegate actually asked us. Every session closes with actions you can take on the first working day after the summit.

Opening session10:50 am – 11:30 amopens the day

From break-fix to predicted: what changes when the asset tells you first

Who is accountable for the sensors after the contractor has gone?

The instrumentation in year seven, and the data room the fund is about to open: the two moments when asset data is graded by somebody else.

From break-fix to sensor-driven: who pays for the instrumentation, who signs the business caseWhat the new toolkit actually detects, and at what false-positive rateStructural IoT on marine and elevated assetsSensor networks that survive the warranty: who owns them in year seven
A deck elevation with sensor ticks, one raised in Data Stream Blue above a hairline crack inside the deck.
Panel one11:30 am – 12:30 pmgovernance

Structure before software: getting your data ready before you buy anything

Who owns the schema when six contractors each brought their own?

The schema nobody agreed on, and what it costs to agree it late, treated as governance problems rather than software problems.

Buying software to fix a data problemSchema standardisation across a multi-contractor programmeTBM data nobody usesCultural change managementThe readiness checklist, and why it is the AI precondition rather than a governance exercise
Twelve differing naming conventions above a rule, resolved into one ordered column below it.
Walkthrough12:50 pm – 1:30 pmESG and the lender

Carbon data, from certificate to pour

Where does the carbon claim stop matching the pour?

An ESG commitment written at head office, batching logs kept at chainage, and a lender who needs the two to agree before the next drawdown. The session walks the trail from certificate to pour and stops wherever it thins out.

Where the trail starts: green steel certificates, low-carbon mix designs, and what each one actually certifiesWhere it thins out: untagged pours, substituted mixes, and the batch nobody recorded against a chainageWhat the lender asks for: the evidence a drawdown condition actually requires, and how much of it exists on a live project todayWho holds the record: whether embodied carbon sits with the EPC, the supplier or the concessionaire, and who gets asked when it is queriedWhat the premium is worth: what a green premium actually earns on an Indian project right now, and who in the room has captured one
A chain of five links, the first two solid and interlocked, the third broken open, the last two hollow and connected to nothing.
Panel two2:30 pm – 3:30 pmlinear assets

Running a line, not a plot: data on India's linear mega-assets

Why does the number I report to the board never match the number on site?

What a corridor-shaped data practice has to do differently from a building-shaped one, and what it costs when nobody makes the distinction.

The linear-asset problemGIS as the spine, not the sidecarDrone survey at production cadenceCatching schedule slip before the monthly reportThe overrun autopsy: where the time actually goes, measured on your own cycle
A dense grid of data over a building plot, and the same amount of data stretched thinly along a corridor.
Fireside3:50 pm – 4:40 pmCDO + CPO

The mandate the site ignores

How do you enforce digital compliance without stalling project momentum?

Bridging the gap between corporate digital mandates and site-level execution, where subcontractors resist new workflows, data logging and CDE tools.

The corporate mandate meets the site: where it diesEnforcement without stalling the programmeDesigning for hours, not weeks of trainingContracting for adoptionWhen the paper system works better
An orderly corporate data system above, a construction site below, and a connection that breaks in the gap between them.
Panel three4:50 pm – 5:50 pmthe contract question

Open or captive: the platform decision you live with for thirty years

Could we leave our platform, and could the operator open what we hand over?

The platform decision you cannot reverse, and the handover nobody can open, set against contracts that are being signed this year.

Open or captive, contractuallyOpen formats in practice, not in the standardThe AI preconditionCompressing handoverWhat operations actually receives: asset naming, test reports and as-builts structured to be queryable, not a folder of scans
Data rows moving between two containers, with three left behind against the wall of the first.

Timings, including breaks

9:30 am – 10:20 amRegistration, coffee and networking
10:20 am – 10:50 amOpening address
10:50 am – 11:30 amOpening session · From break-fix to predicted
11:30 am – 12:30 pmPanel one · Structure before software
12:30 pm – 12:50 pmNetworking break
12:50 pm – 1:30 pmPractitioner-led walkthrough · Carbon data, from certificate to pour
1:30 pm – 2:30 pmNetworking lunch
2:30 pm – 3:30 pmPanel two · Running a line, not a plot
3:30 pm – 3:50 pmAfternoon tea
3:50 pm – 4:40 pmFireside chat · The mandate the site ignores
4:40 pm – 4:50 pmChangeover
4:50 pm – 5:50 pmPanel three · Open or captive
5:50 pm – 6:00 pmClosing remarks
6:00 pm – 8:30 pmEvening reception

Not sure which sessions are yours? The readiness check will tell you in eight questions.

Take the readiness check