Oğuz Cem Demirci

Civil Engineer · M.Sc. Student, Transportation Engineering, METU

Case Studies / Daily Progress Reporting

Case study · Metro line construction · PMIS

50 sites. One truth. Zero Excel.

How we transformed a fragmented daily reporting process into a real-time, data-driven system across a large-scale metro line construction project.

My role
PMIS Implementation Consultant, ISETIA
Sector
Rail · metro line construction
Scope
Daily progress reporting (DPR)
Scale
50+ construction sites

Background

On a large metro line, the daily progress report (DPR) is the heartbeat of project control. Every day, each site records its workforce, equipment, and progress, and that data feeds schedule updates, management decisions, and later contractor claims.

  • 50+active sites reporting daily
  • Multiplecontractors and site teams
  • Every dayworkforce, equipment and progress data

Challenge: when scale breaks the process

BEFORE Site A Site B Site C … 50+ sites WhatsApp Email Phone calls DPR_v1.xlsx DPR_final.xlsx DPR_FINAL2.xlsx ? Management
  • Data scattered across WhatsApp, email and phone calls, with no single source of truth
  • Manual Excel consolidation produced multiple, conflicting report versions
  • No visibility on which of the 50+ sites had submitted, so daily data gaps went undetected
  • Management decisions were made on incomplete or outdated information
  • No standard format, so planned vs actual progress was impossible to track

Approach: standardize first, then digitize

We implemented PMIS ISETIA as a centralized common data environment (CDE), but the platform was the last step, not the first. A digital system built on an unclear process only automates the chaos.

  1. Standardize the processOne DPR format for every site, with clearly defined fields for workforce, equipment and progress.
  2. Define roles & approvalsWho submits, who reviews and who approves, so data is verified at the source.
  3. Configure the platformWorkflows built in PMIS ISETIA as the single CDE, connecting field to management in real time.
  4. Train & drive adoptionTraining, feedback loops and patience, because adoption is the real deliverable.

Deliverables: one platform, every signal

AFTER Site A Site B Site C … 50+ sites PMIS ISETIA Common data environment Standard DPR workflow Roles · approvals · alerts Real-time dashboards

Workforce tracking

Daily headcount per location and contractor

Equipment tracking

Real-time utilization across all sites

Progress tracking

Planned vs actual, with photo evidence

Missing data alerts

Automatic flags for sites that have not reported

Result

  • Real-time reporting: delays eliminated across all 50+ sites
  • Email-based data collection and manual Excel work removed from the workflow
  • Location-level visibility for management, enabling faster and better decisions
  • Contractor performance data became a reliable foundation for claim management
  • Full user adoption of the system
“Can’t imagine going back.”Site users after roll-out
BeforeAfter
Data collectionWhatsApp, email, phoneOne platform (CDE)
ConsolidationManual Excel, conflicting versionsAutomatic, single version
Missing reportsUndetectedFlagged automatically
ProgressNo standard formatPlanned vs actual, with photos
DecisionsIncomplete, outdated dataReal-time, location level

Key learnings

  1. Standardization before digitizationDefine the workflow first; a digital system on an unclear process only automates the chaos.
  2. Data quality drives decisionsBad data is worse than no data. Every field, role and submission is verified at the source.
  3. Adoption is the real deliverableThe best system fails if people do not use it. Training and feedback loops are non-negotiable.

Visual summary

The case study as a six-slide carousel. Swipe or scroll sideways.

Case study slide 1 of 6Case study slide 2 of 6Case study slide 3 of 6Case study slide 4 of 6Case study slide 5 of 6Case study slide 6 of 6

← All case studies