Project Control & Monitoring: Systems, Tools & Real-World Applications

TAKEAWAYS:

• Control systems (planned vs. actual performance) are the backbone of project success—without them, even well-planned projects fail (e.g., Kathmandu Metro delays).
• Earned Value Management (EVM) combines scope, cost, and time into a single metric (CPI, SPI) to spot problems early—used by Daraz to track order fulfillment delays.
• Monitoring tools (Gantt charts, dashboards) turn raw data into actionable insights—NTC uses them to track fiber-optic cable installation progress across Nepal.
• Corrective actions (replanning, reallocating resources) are triggered by deviations—Khalti’s app updates use this to fix login failures during Diwali traffic spikes.
• Lessons learned from post-project reviews (e.g., Khimti-I’s BOOT model) prevent future failures—Nepal’s infrastructure projects often ignore this step.
• Stakeholder communication (reports, meetings) keeps everyone aligned—Pathao’s driver app updates rely on real-time monitoring to adjust surge pricing.

1. What Is Project Control?

Project control is the systematic process of tracking, measuring, and adjusting project performance to meet goals. It answers:

• Are we on schedule? (Time control)
• Are we within budget? (Cost control)
• Are we delivering the right quality? (Quality control)

How it works:

flowchart TD
    A["Project Plan"] --> B["Monitor Actual Performance"]
    B --> C["Compare vs. Plan"]
    C --> D["Identify Deviations"]
    D --> E["Take Corrective Action"]
    E --> F["Update Plan"]
    F -->|"Loop"| B

Key components:

• Baseline plan: Original scope, schedule, and budget.
• Performance metrics: Actual progress vs. planned (e.g., tasks completed, costs incurred).
• Variance analysis: Why are we behind/ahead? (e.g., labor strikes, material shortages).
• Corrective actions: Adjustments like reallocating resources or changing timelines.

2. Earned Value Management (EVM): The "Single Number" for Project Health

EVM combines scope, cost, and time into three critical metrics:

Derived metrics:

• Cost Performance Index (CPI) = EV / AC
  • CPI > 1: Under budget (good!)
  • CPI < 1: Over budget (red flag)
• Schedule Performance Index (SPI) = EV / PV
  • SPI > 1: Ahead of schedule
  • SPI < 1: Behind schedule

Worked Example: Daraz’s Order Fulfillment Daraz tracks order delivery using EVM:

• PV: 10,000 orders scheduled for December (budget: Rs. 500,000).
• EV: Only 7,000 orders completed (earned Rs. 350,000).
• AC: Rs. 400,000 spent. Calculations:
• CPI = 350,000 / 400,000 = 0.875 (over budget by 12.5%).
• SPI = 350,000 / 500,000 = 0.7 (30% behind schedule). Action: Daraz might hire temporary staff or outsource to Pathao for last-mile delivery.

3. Monitoring Tools: Turning Data into Decisions

4. Corrective Actions: Fixing What’s Wrong

When deviations are detected, managers take action:

1. Replanning: Adjust timelines or scope (e.g., NTC delays fiber-optic rollout due to land acquisition issues).
2. Resource Reallocation: Shift workers/materials (e.g., Daraz reroutes delivery personnel during strikes).
3. Quality Adjustments: Improve processes (e.g., Nabil Bank’s loan approval system after high rejection rates).
4. Vendor Management: Replace underperforming suppliers (e.g., NTC switches cable vendors mid-project).

Case Study: Kathmandu Metro Delays

• Problem: 3-year delay due to land acquisition and political interference.
• EVM Analysis:
  • PV: 100% completion by 2020 (budget: Rs. 50 billion).
  • EV: Only 60% completed by 2023 (earned Rs. 30 billion).
  • AC: Rs. 45 billion spent.
  • CPI = 0.67 (over budget), SPI = 0.6 (behind schedule).
• Corrective Actions:
  • Government injected additional funds.
  • Fast-tracked land acquisition via legal reforms.
  • Used Chinese expertise for construction.

5. Project Monitoring Systems

Monitoring ensures the project stays on track. Key systems:

• Progress Reports: Weekly/monthly updates (e.g., Khimti-I’s power generation reports).
• Meetings: Steering committee reviews (e.g., NTC’s monthly progress meetings).
• Audits: Independent checks (e.g., Nepal Rastra Bank audits bank loan projects).
• Lessons Learned: Post-project reviews (e.g., Melamchi Water Supply’s cost overruns).

mindmap
  root((Project Monitoring))
    Data Collection
      Progress Reports
      Financial Records
      Quality Checks
    Analysis
      Variance Analysis
      Trend Analysis
    Reporting
      Dashboards
      Meetings
    Action
      Corrective Measures
      Replanning

6. Challenges in Nepal: Why Projects Fail

Worked Example: Khimti-I Hydropower (BOOT Model)

• Problem: 2-year delay, 30% cost overrun.
• Root Cause:
  • Poor risk management (underestimated land acquisition time).
  • Lack of EVM (no real-time tracking).
• Lesson: Nepal’s BOOT projects must adopt strict monitoring and international standards.

In the Real World

1. Khalti’s App Updates

   • Idea: Real-time monitoring of system performance.
   • How: Khalti tracks login failures, transaction speeds, and server response times. During Diwali (high traffic), they use control charts to detect spikes and reallocate servers to high-demand regions (e.g., Kathmandu, Pokhara).

2. Daraz’s Order Fulfillment

   • Idea: Earned Value Management (EVM) for logistics.
   • How: Daraz uses EVM to track:
     • PV: Planned orders per day (e.g., 50,000).
     • EV: Actual orders fulfilled (e.g., 40,000).
     • AC: Cost of delivery (e.g., Rs. 20 million).
   • Action: If SPI < 0.9, Daraz partners with Pathao for surge pricing.

3. NTC’s Fiber-Optic Rollout

   • Idea: Gantt charts and dashboards for large-scale projects.
   • How: NTC’s project to connect all 77 districts uses:
     • Gantt charts to track district-wise progress.
     • Dashboards to show real-time data on cable laying, tower installations, and user sign-ups.
   • Challenge: Monsoon delays in rural areas → NTC pre-orders materials and trains local crews.

Exam Tip

1. Define clearly: Start answers with precise definitions (e.g., "Project control is the process of...").
2. Use EVM formulas: Always show calculations for CPI/SPI in numerical questions.
3. Link to Nepal: Relate answers to Khimti-I, Kathmandu Metro, or NTC for full marks.
4. Compare tools: Use tables to contrast Gantt charts vs. dashboards vs. S-curves.
5. Critique failures: For "Why do projects fail in Nepal?", use the 5 challenges table above.
6. Case studies: For scenario-based questions (e.g., Khimti-I), structure answers as:
   • Problem → EVM analysis → Corrective actions → Lessons learned.

Visual Summary: Project Control Cycle

flowchart LR
    A["Plan"] --> B["Monitor"]
    B --> C["Measure"]
    C --> D["Compare"]
    D --> E["Analyze"]
    E --> F["Act"]
    F -->|"Loop"| B