This case study walks through an actual NKMPV-conducted Network Survey Vehicle assessment on a 200 km state highway network in Punjab. Project specifics anonymised. The MoRTH RW/NH-33044/32/2019-compliant NSV deliverable was the basis on which the state PWD's next-year maintenance budget was approved by the finance department. What follows is the methodology, IRC SP 16 thresholds applied, and the lessons for state PWD / NHAI / concessionaire procurement.

Project Context

The network was a 200 km cluster of state highways in central Punjab — five disconnected SH stretches under the same PWD division responsible for routine maintenance, minor improvement, and periodic rehabilitation programming. The state PWD’s maintenance budget request for the upcoming financial year had been queried by the finance department for lacking objective condition data. The Engineer-in-Chief authorised an NSV-based pavement condition assessment to produce the data on which the budget allocation would be defended.

MoRTH circular RW/NH-33044/32/2019 had already established NSV as the mandatory methodology for NH-network monitoring. State PWDs are increasingly adopting the same methodology for their SH networks because (a) it produces a defensible objective dataset, (b) it generates a GIS-ready output that integrates directly into Pavement Management Systems (PMS), and (c) NABL-accredited NSV reports stand up to finance-department scrutiny in a way that visual-survey-based budgets do not. NKMPV was engaged with a 28-day timeline from contract sign-off to final report submission, including 18 days of field operation and 10 days of office processing.

The Required Deliverables

Per MoRTH RW/NH-33044/32/2019 read with IRC SP 16, the NSV deliverable for a 200 km state highway network includes nine mandatory items:

  • IRI per 100-metre segment — chainage start, chainage end, IRI mean (m/km), IRI 85th percentile, standard deviation
  • Rut depth — left and right wheel path separately, plus mean of both, severity-tiered per IRC SP 16
  • Cracking maps with type / severity / extent classification per IRC SP 16
  • Mean Texture Depth (MTD) with acceptance flag against IRC SP 16 threshold (≥ 0.7 mm for new BC)
  • Road geometry — gradient, crossfall, curvature per 100-metre segment from inertial measurement unit
  • Chainage-synchronised forward + 360-degree video with continuous GPS and chainage overlay
  • Raw data files in vendor-neutral formats (CSV, GeoJSON, plus original instrument-output formats)
  • Compiled report with maintenance recommendations per IRC SP 16 severity bands
  • NABL accreditation certificate (TC-14144) appendix for the surveying laboratory

Plus the state-PWD-specific addition: GIS shapefile (.shp + .dbf + .shx) compatible with their existing Pavement Management System for direct ingestion into the maintenance-prioritisation database.

Field Execution

NSV deployment ran across 14 working days plus 4 days of buffer for weather and re-survey. The NSV vehicle (Mahindra-class chassis with laser profiler, downward-facing texture camera, forward-facing HD video camera, 360-degree panoramic camera, IMU, and DGPS-connected positioning) was calibrated against control bumps and reference texture plates the morning of mobilisation. Calibration certificates were appended to the report.

Field productivity ran at approximately 18-22 lane-km per day, well within the 200-250 lane-km/day theoretical productivity for plain-terrain NSV work. The slower-than-theoretical pace was driven by traffic density on the busier SH stretches (forcing speed reduction below the 60-80 km/h optimal NSV speed) and by re-survey passes at locations where laser-profiler data showed transient signal degradation due to surface contamination.

  • Days 1-3: SH-stretch 1 (45 km, plain agricultural belt) — full coverage, no incidents
  • Days 4-7: SH-stretch 2 (50 km, urban-fringe with junction density) — required re-survey on 3 km section due to morning fog affecting laser profiler
  • Days 8-10: SH-stretch 3 (35 km, mixed plain / hill-foothill terrain) — IMU geometry capture critical, recurring brief stops to clean texture-camera lens of road dust
  • Days 11-13: SH-stretch 4 (40 km, rural/agricultural belt) — fastest progress, 22 lane-km/day average
  • Day 14: SH-stretch 5 (30 km, semi-urban industrial belt) — completed in single day

Total raw data: ~2 million IRI / rutting / cracking / texture data points, plus ~70 hours of forward-facing HD video, plus equivalent 360-degree panoramic video. Disk: ~1.8 TB of raw video plus ~80 GB of instrument-data files, post-processed in office over Days 15-22.

Network Condition Results

The IRC SP 16 thresholds applied as acceptance / severity criteria:

ParameterIRC SP 16 ThresholdNetwork Result (200 km)Status
IRI mean (NH/SH)Good < 2.5 m/km, Poor > 3.5 m/km42% Good, 39% Fair, 19% PoorNetwork mostly serviceable
Rut depth meanGood < 5 mm, Poor > 12 mm61% Good, 28% Fair, 11% PoorAcceptable
Cracking extentGood < 5%, Poor > 15%55% Good, 31% Fair, 14% PoorAcceptable network-wide
MTDGood ≥ 0.7 mm new BC, fair 0.5-0.7 mm47% Good, 38% Fair, 15% PoorTexture worn in older sections
Geometric anomaly (rolling)Curvature within design limits98% within IRC SP 84 design limitsNo major realignment required

The 200 km network produced a maintenance-prioritisation map: roughly 19% of the network (38 km) needed periodic-rehabilitation overlay or mill-and-overlay work in the upcoming year, a further 39% (78 km) needed routine maintenance (crack sealing, surface treatment), and 42% (84 km) was structurally and surface-functionally sound. The cost estimate, derived from the segment-prioritisation map cross-referenced against MoRTH Schedule of Rates, came to approximately ₹78 crore over a 3-year programme.

The Deliverable Package

Final NKMPV submission was multi-component:

  • Master report (PDF, 156 pages): Executive summary, methodology, equipment specs, IRC SP 16 threshold tables per parameter, network-level condition map, segment-by-segment data tables, maintenance recommendations against MoRTH SOR cost estimates, NABL TC-14144 certificate appendix, equipment calibration certificates
  • Raw data files: CSV per-100-metre tabulation of IRI / rutting / cracking / MTD / geometry across 2,000 segments × 5 parameters
  • GIS shapefile: .shp + .dbf + .shx with full attribute schema (SegmentID, ChainageStart, ChainageEnd, Lane, IRI_Mean, RutDepth_LH, RutDepth_RH, Cracking_Type, Cracking_Severity, MTD, Recommendation_Code, EstimatedCost). Direct ingestion into the state PWD's PMS
  • GeoJSON: Web-mapping-ready output for state PWD GIS portal integration
  • Forward HD video: ~70 hours, chainage-synchronised, with overlay showing chainage, GPS, and instrument readings
  • 360-degree panoramic video: Selected segments where IRC SP 16 mandates 360 capture (junctions, ROBs, structural reference points)
  • Calibration evidence pack: Laser profiler factory calibration cert + post-survey verification, IMU calibration cert, DGPS post-processing verification

Total delivery on Day 26 (within the 28-day contract window). The state PWD's PMS team completed shapefile ingestion within 5 working days. The maintenance-prioritisation map became the basis on which the next-year maintenance budget was defended at the finance department review — no further verification was demanded because the underlying data was NABL-traceable, MoRTH-procedure-compliant, and GIS-ready.

What Made This Submission Defensible

1. Vendor-neutral data formats

Many NSV vendors deliver data in proprietary binary formats that lock the client into the vendor’s viewer software. NHAI / state PWD requirements increasingly mandate vendor-neutral formats (CSV, GeoJSON, shapefile) precisely because finance / PMS / planning teams need data they can re-use across years and across vendors. NKMPV delivers in vendor-neutral formats by default.

2. Calibration evidence pack

An NSV report without calibration evidence is unverifiable and challengeable. Laser profiler calibration drifts with use; IMU calibration drifts with temperature; DGPS post-processing depends on base-station file integrity. NABL accreditation TC-14144 (ISO/IEC 17025:2017) means each instrument is on a documented calibration cycle, and post-survey verification at the end of every campaign closes the audit loop.

3. Direct PMS integration

The shapefile attribute schema designed to match the state PWD’s PMS field names eliminated a 2-3 week re-format step that would otherwise have delayed budget allocation. NKMPV worked with the PWD’s PMS analyst before mobilisation to align attribute schemas — a small front-end coordination effort that saved significant downstream lag.

Lessons for State PWD / NHAI Procurement

  • Specify NABL accreditation as a tender pre-qualification, not an optional preference. Without NABL, the report is challengeable at finance-department audit and budget allocation can be deferred.
  • Specify vendor-neutral data formats explicitly in the tender BoQ — CSV, GeoJSON, shapefile minimum. Avoid vendor-locked binary formats.
  • Coordinate shapefile attribute schema with your PMS team before tendering to avoid post-survey re-format delays.
  • Budget for re-survey contingency in the tender — weather, traffic, surface contamination — typically 10-15% of field-day count.
  • Plan for 360-degree video at junction / ROB / structural reference points per IRC SP 16, even if not explicitly demanded — saves a re-survey if Authority Engineer queries those sections later.
  • Insist on segment-by-segment maintenance-recommendation cost estimates against MoRTH SOR or state-specific SOR — this is what makes the data actionable for budget defense.

Engage NKMPV for Your NSV Survey

NKMPV is NABL-accredited (TC-14144 under ISO/IEC 17025:2017) for NSV surveys per IRC SP 16 and MoRTH RW/NH-33044/32/2019. Reports accepted by NHAI, BRO, state PWDs, BoT/HAM concessionaires across India without additional verification. We mobilise NSV crews from our Pinjore HQ within 24-72 hours of confirmed quote and deliver compiled reports within 25-30 days for typical 100-300 km network campaigns. View our NSV service →, see indicative NSV pricing, or call +91-82953-60108.

Note on this case study: project specifics — corridor identifiers, exact locations, contracting authority, contractor — are anonymised per the engagement agreement. The methodology, deliverables, IRC SP 16 threshold percentages, and budget-defense outcome reflect actual NKMPV NSV practice. For procurement enquiries with named project references, contact via our press kit.