MétaCan
Menu
Back to cohort
Record W7164038547 · doi:10.5281/zenodo.20611808

Cost Management Challenges in Indian Infrastructure Projects: A Study of Quantity Surveying Practices

2015· article· en· W7164038547 on OpenAlexaff
Premalatha T G

Bibliographic record

VenueZenodo (CERN European Organization for Nuclear Research) · 2015
Typearticle
Languageen
FieldEngineering
TopicBIM and Construction Integration
Canadian institutionsImpact
Fundersnot available
KeywordsProcurementMandateTransparency (behavior)Government (linguistics)Integrated project deliveryProject managementAuditFunction (biology)Private sector

Abstract

fetched live from OpenAlex

significant majority of infrastructure projects failing to meet their original budgetary targets. This phenomenon is often rooted in a combination of socioeconomic factors, inadequate planning, and a lack of transparency in the procurement process. The mid-2010s represented a period of immense pressure for the Indian government and private stakeholders to deliver world-class infrastructure, yet the delivery mechanisms remained rooted in mid-20th-century methodologies. This study analyzes the specific limitations of the 2014–2015 period, where the friction between legacy practices and emerging digital requirements created a volatile environment for quantity surveyors. The failure to transition from reactive, post-hoc cost monitoring to proactive, predictive cost management during this era set the stage for subsequent industry-wide reforms and the eventual mandate for digital adoption. As the industry expanded, the inability to accurately forecast and control project expenditure became a major bottleneck, limiting the scalability of critical transport and energy projects. This research probes the "cost-estimation gap"—the chasm between initial project sanction and final delivery costs—which during 2015 was widening due to ineffective data management, fragmented project leadership, and a lack of unified digital standards across the public and private sectors. The implications are not merely financial; they touch upon the very stability of the construction ecosystem, affecting contractor viability, project safety standards, and public trust. By examining the QS function in isolation, we reveal how professional practices were frequently outpaced by the sheer scale and complexity of the projects they were meant to govern. The era was defined by a critical disconnect: the planning phase operated in a speculative, low-data environment, while the execution phase struggled under the weight of unmitigated risks, causing a feedback loop of financial inefficiency that stifled national competitiveness. 2. Quantity Surveying Practices (Circa 2014-2015) In the mid-2010s, quantity surveying in India was trapped in a difficult transitional phase. While developed global markets had begun the transition toward collaborative 5D BIM—integrating time and cost into 3D models—Indian professional practice remained largely tethered to conventional, paper-based methods that prioritized simple arithmetic over advanced data analytics. 2.1 Technological Adoption and Professional Constraints The professional tools and practices utilized by quantity surveyors during this period were primarily manual or limited to basic spreadsheet-based office software. The landscape was defined by three primary limitations that hampered efficiency and accuracy: Manual Measurement and Take-offs: The industry standard practice involved heavy reliance on physical, 2D CAD drawings or hard-copy blueprints. Quantity surveyors were required to perform manual take-offs—measuring quantities from these drawings by hand using physical scalers, planimeters, and complex grid overlays. This process was not only labor-intensive but also highly prone to human error, especially in complex, non-linear infrastructure geometries such as intricate flyover junctions, segmental bridges, or subway tunnel systems. The lack of automation often resulted in significant discrepancies between design intent and the final bill of quantities, leading to frequent contractual disputes during the execution phase when site conditions diverged from initial measurements. Furthermore, manual take-offs made it nearly impossible to rapidly adjust estimates in response to design modifications, which were frequent and often poorly documented. These manual errors cascaded into procurement delays, as the initial BoQ (Bill of Quantities) often required constant rectification, consuming valuable management time that should have been dedicated to strategic cost planning and value engineering. The reliance on manual methods also meant that auditing these quantities was a tedious process, often leading to "estimation drift" where quantities evolved based on subjective site interpretations rather than rigorous design specifications. The lack of a digital footprint for these calculations meant that institutional knowledge was tied to individual surveyors rather than embedded in organizational systems. Software Constraints and Interoperability: While project management tools like Microsoft Project (MSP) and Oracle Primavera were increasingly utilized for scheduling, there was a glaring interoperability gap between these platforms and the design software used by engineers. Data silos were the norm, making it difficult to link physical quantities directly to project costs in a dynamic, iterative environment. Because cost data was often managed in separate, offline spreadsheets, it could not be updated in real-time when design changes occurred, rendering estimates obsolete almost as soon as they were drafted. This lack of a "Single Source of Truth" meant that by the time a cost report reached a project manager, the data was already historical and rarely actionable for real-time risk mitigation. This fragmentation meant that data entry was redundant, increasing the administrative burden on QS professionals without providing a commensurate increase in project visibility or control. Furthermore, the reliance on disparate software meant that the QS function was often sidelined from the core design process, treated as an administrative cost-check rather than a strategic financial advisor. The lack of data integration forced QS teams into reactive roles, constantly "chasing" actual expenditure rather than forecasting future budgetary needs. This systemic lack of connectivity meant that even minor design alterations—such as a shift in foundation depth—could take days to propagate through the cost ledger, creating a persistent information lag that compromised project agility. BIM Reluctance: While Building Information Modelling (BIM) was emerging in global conversations, it was primarily utilized within India for high-end design visualization and basic clash detection rather than cost estimation. The lack of standardized protocols for "As-Built" data, combined with a cultural reluctance to shift from traditional documentation and a shortage of BIM-trained professionals, meant that QS professionals struggled to adopt these systems for precise, automated quantification. This reluctance was further fueled by the high cost of software licensing, the lack of a government mandate at the project level, and a general skepticism regarding the long-term ROI of digital tools in an industry accustomed to low-cost, high-manpower solutions that did not require specialized technical training. Consequently, BIM was treated as a "luxury" add-on for prestigious projects rather than an essential tool for baseline cost control. There was also a notable "digital divide" where small-to-medium enterprises (SMEs) were unable to afford the necessary hardware/software upgrades, creating a two-tier industry structure that stalled nationwide digital adoption. This divide inhibited the widespread creation of a shared industry knowledge base, preventing the benchmarking of cost and performance data that is essential for long-term improvement in infrastructure delivery. Furthermore, the absence of standardized BIM object libraries meant that each firm had to build its own data protocols from scratch, leading to an inconsistent and inefficient digital landscape where data could not be easily shared across project stakeholders or through the full asset lifecycle. 3. Cost Management Challenges The study identifies several key drivers that acted as catalysts for cost escalation during this period. These factors were often interconnected, creating a "domino effect" where one initial delay led to a chain of budgetary failures. Challenge Category Description of Impact Strategic Consequence Price Volatility Frequent, unpredictable fluctuations in raw material prices (steel, cement) and energy inflation significantly impacted procurement planning. Inability to fix long-term costs, leading to frequent contract renegotiations and protracted litigation between state agencies and contractors. Payment Delays Protracted approval cycles for payments to contractors disrupted vital project cash flow, leading to work stoppages and increased overhead costs. Increased interest burdens on contractor loans and significantly reduced subcontractor performance due to lack of liquidity. Inaccurate Estimation Poorly defined project scopes and reliance on manual estimation techniques led to consistent underestimation of project costs during the bidding phase. "Low-ball" bidding to secure contracts, followed by inevitable, costly change-order requests during the construction phase to remain profitable. Technical Inadequacy A clear lack of trained personnel in advanced digital estimation tools hindered the transition to efficient, data-driven project management systems. Persistence of high administrative overhead and excessive reliance on institutional memory rather than standardized, analytical data. Regulatory Hurdles Complex land acquisition laws and environmental clearance processes caused significant project delays, automatically increasing time-related costs. Substantial project life-cycle cost inflation well beyond original sanctioned estimations, as idle machinery and labor costs mounted. Scope Creep Unplanned changes in design requirements during the project lifecycle often occurred without formal, integrated cost-impact assessments. Fragmentation of the project budget, leading to massive financial losses, resource misallocation, and deep stakeholder distrust. Supply Chain Instability Limited coordination between logistics providers and site managers often caused b

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.006
metaresearch head score (Gemma)0.025
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.030
Threshold uncertainty score0.060

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.025
Meta-epidemiology (narrow)0.0000.001
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.006
Science and technology studies0.0040.003
Scholarly communication0.0050.003
Open science0.0020.004
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0020.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.149
GPT teacher head0.294
Teacher spread0.144 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2015
Admission routes1
Has abstractyes

Explore more

Same venueZenodo (CERN European Organization for Nuclear Research)Same topicBIM and Construction IntegrationFrench-language works237,207