VEDAM v1.1 · Railway Project Intelligence Platform

Project Start

—

Contract mobilisation

Baseline Finish

—

Original contract

Forecast Finish

—

● As of Data Date

Not set

—

Project Cost

Not set

Sanctioned budget

Actual Cost

—

Pending

Project Status

—

Overall Progress

0%

actual

Health: —

Scheduled %—

SPI—

Phase Progress

S-Curve — Planned vs Actual & ETC

Planned Actual ETC1 ETC2

Scenario 1 — Current rate

—

Scenario 2 — Required rate to finish on time

—

Both scenarios — gap = recovery effort

Red = delay · Purple = recovery

TCPI override: affects ETC2

Driving Activities

EVM Metrics

Budgeted Cost (BAC) ₹ Cr

Actual Cost (AC) ₹ Cr

PV

—

Planned Value

BAC×%sched

Planned Value

Budgeted cost of work scheduled to be done by data date.

PV = BAC × %sched

EV

—

Earned Value

BAC×%actual

Earned Value

Budgeted cost of work actually completed to date.

EV = BAC × Physical %

AC

—

Actual Cost

User input

Actual Cost

Real cost incurred for work performed to date.

AC = User input

CPI

—

Cost Perf. Index

EV÷AC

Cost Perf. Index

>1 under budget · =1 on budget · <1 over budget.

CPI = EV ÷ AC

SPI

—

Sched. Perf.

EV÷PV

Schedule Perf.

>1 ahead of schedule · =1 on schedule · <1 behind.

SPI = EV ÷ PV

CV

—

Cost Variance

EV−AC

Cost Variance

Positive = under budget. Negative = over budget.

CV = EV − AC

SV

—

Sched. Variance

EV−PV

Schedule Variance

Positive = ahead of plan. Negative = behind plan.

SV = EV − PV

EAC

—

Est. at Completion

BAC÷CPI

Est. at Completion

Forecast of total project cost at current cost performance rate.

EAC = BAC ÷ CPI

Enter BAC and AC above to activate cost performance metrics.

Contract Milestones

Activity Status

SPI & delay trajectory over data dates

SPI — Latest

—

Set a data date

Delay — Latest

—

vs baseline

Progress — Latest

—

Physical % complete

Trend

—

⚡ Trend Analysis

Click ↺ Refresh to load analytics.

SPI Over Time — Schedule Performance Index

Delay Accumulation — Days Behind Baseline

Planned vs Actual Progress — % Complete

Critical Activity Count — Over Time

Click ↺ Refresh to build heatmap.

Add Activity Slip

Global Assumptions

Resource efficiency (%) 100%

Below 100% = reduced productivity (monsoon, site access). Above 100% = acceleration (overtime, extra crews).

Impact on Project Finish

Baseline Finish

Saved baseline

—

Forecast Finish

Current schedule

—

What-If Finish

With your changes

—

Required SPI

To finish on baseline

—

Forecast S-Curve — Baseline vs What-If

Cascading Impact — Activities affected by your changes

Add an activity slip to see cascading impact on downstream activities.

Schedule Intelligence

Last computed: —

Schedule Narrative

Auto-generated from CPM data · Run Reschedule to refresh

Run Reschedule to generate narrative

VEDAM · Estimator

0 hrs

—

Total Design Hours

—

Hours / km

—

Total Project Cost

—

Cost / km

Confidence

Core Inputs

Project Name

Railway Type

Design Stage

Route Length km

Number of Stations

Structures / Bridges

Country / Region

Estimate Confidence

Fill Additional Input tab to refine. Save icon captures snapshot.

—

Total Design Hours

—

Hours per km

Normalised intensity

Effort by Discipline

Grade Split

Propagates km & stations → CPM durations → reruns schedule

Additional Inputs Each section refines the estimate

Disciplines in Scope

Toggle on/off. Deactivating removes discipline from estimate entirely.

Route & Configuration

Line type, % elevated/underground, depot

▼

Line Configuration

Line Type

% Elevated %

% Underground %

Depot / Stabling Yard

Project Nature

Site & Physical Conditions

Terrain, geotechnical, bridges, tunnels

▼

Terrain

Geotechnical Complexity

No. of Bridges / Viaducts

No. of Tunnels

Design Standard

Technical Complexity

Signalling, BIM level, electrification

▼

Signalling System

Electrification

BIM Requirement

Project Context & Schedule

Review cycles, survey data, dates

▼

Design Review Cycles

Survey Data Availability

Client Involvement

Design Start Date

Design End Date

—

Total Design Hours

—

Hours per km

Normalised intensity

—

Heaviest Discipline

—

Estimate Confidence

Effort Pyramid — Grade Split

Top Cost Drivers

Grade Mix

Discipline Intensity Heatmap

Full Hours Breakdown

Discipline	Director	Senior	Mid-Senior	Junior	Total	hrs/km	Share

₹ Construction Cost Estimate

Unit Rates — per km (₹ Cr)

Civil Works

Structures (Viaduct/Piling)

Track (Supply + Laying)

OHE & Traction

Signalling & Telecom

Land Acquisition

Per-Unit Costs (₹ Cr)

Station Cost (per station)

Depot Cost (per depot)

No. of Depots

Contingency %

Reference Anchor

30 km · 20 stn · 1 depot · Elevated · ₹14,820 Cr · ~104w

Cost Breakdown

Phase Cost Profile

Factor Analysis

Discipline Multipliers

Active Weight Factors

Effective Multiplier per Discipline

Iteration Log

Estimate Evolution

No snapshots yet.

Grade Mix Evolution

No snapshots yet.

All Snapshots

Save your first snapshot using the save icon on Core Input tab.

Contract Protocol Compensation Event — Clause 60.1 · PM assessment

Add Delay Event

Event Reference

Event Description

Responsible Party

Compensation Event Type

Impacted Activity

Delay Duration (working days)

Event Start Date

Notified?

Delay Event Register 0 events

📋

No delay events recorded

Add delay events using the form above. Each event will be analysed for CPM impact and EOT entitlement.

⚡

Add a delay event to begin analysis

Each event is analysed against the CPM schedule. Impacted activities, float consumption, and critical path effect are calculated automatically.

Window Analysis — Delay Apportionment by Period

Window analysis divides the project into time windows and identifies which delay events were operative in each window, the dominant delay cause, and the party responsible. This forms the basis for concurrent delay analysis under NEC4 — Clause 60.1.

Window	Period	Planned Finish	Actual/Forecast	Delay (d)	Dominant Cause	Responsible	Concurrent?

📊

Add delay events to generate window analysis

Windows are automatically created around each delay event, showing which delays were concurrent and the dominant responsible party per period.

Retrospective Analysis — Longest Path & Collapsed As-Built

Uses the Actual Start / Actual Finish dates already recorded per activity (Activity Details panel) — no separate as-built entry required. Retrospective methods per SCL Delay & Disruption Protocol (2nd Ed.) and AACE RP 29R-03. These are typically used in dispute/adjudication review, not routine prospective compensation-event assessment — see the note on each panel for contract-specific fit.

Retrospective Longest Path

"What was the as-built critical path to completion, viewed retrospectively?" — traced backward from whichever completed activity finished last, through whichever predecessor left zero gap before its successor's actual start.

Collapsed As-Built ("But-For")

Removes recorded delay events one at a time from as-built durations to see the completion date collapse toward what it would have been but for those events.

Order-sensitive. Removing the same events in a different sequence can change how delay is apportioned between parties, even though total delay recovered is identical — a documented limitation of this method (AACE RP 29R-03), not a tool defect. The comparison below shows both orders side by side; don't quote one order's split without disclosing which was used.

Removal order:

Order Sensitivity Check

⏮

No completed activities or delay events yet

Retrospective Longest Path needs at least one activity with both Actual Start and Actual Finish set. Collapsed As-Built needs delay events tied to activities with recorded durations.

⚖️

No entitlement computed yet

Add employer-caused delay events to compute EOT entitlement. Contractor-caused and neutral events are shown but do not attract EOT.

📄

Claim narrative will appear here

Add delay events and compute EOT. The system will generate a structured claim narrative referencing the correct contract clauses for your chosen protocol.

§1Cover Page

▼

Report Title

Report Period

Project Name

Corridor / Location

Client

Consultant / Org

Contract No.

Package / Lot

Contract Value (₹ Cr)

Planned Completion

Document No.

Revision

Submission Date

Status

Signature Block

Prepared By

Designation

Checked By

Designation

Approved By

Designation

Distribution

§2Project Summary

▼

↺ Overall progress, start/finish dates and delay auto-fetched from schedule

Overall Progress (auto)

—

Forecast Finish (auto)

—

Project Brief

Executive Summary / Highlights This Period

Key Milestone (This Period)

Next Key Milestone

§3Physical Progress

▼

↺ Planned % and Actual % auto-calculated from schedule activities per WBS group

WBS / DisciplinePlanned%Actual%Last Period%

Progress Notes

§4Schedule Status

▼

↺ SPI, delay days, critical activities auto-fetched from CPM engine

SPI (auto)

—

Delay Days (auto)

—

Schedule Status

Revised Completion Date

Critical Path Activities This Period

Look-Ahead (Next 4 Weeks)

Recovery Plan (if delayed)

§5Cost Status & EVM

▼

Planned Value — PV (₹ Cr)

Earned Value — EV (₹ Cr)

Actual Cost — AC (₹ Cr)

Budget at Completion — BAC (₹ Cr)

Estimate to Complete — ETC (₹ Cr)

Forecast Final — EAC (₹ Cr)

Cost Commentary

§6Issues & Risks

▼

§7Next Period Plan

▼

Key Activities Planned

Client Decisions Required

Resources / Constraints

\n

VEDAM TLC 260629-07

New Project

Split:

Ch: Time:

Activities

No activities.
Use + Activity or load a sample.

Activity Detail

Click an activity line
to view and edit details.

0 activities Stations: 0 Infra: 0 ⚠ conflicts

Project Settings

Project

Project Name

Corridor

Total Length (km)

Y Axis

Chainage Start (km)

Chainage Interval (km)

View Window

TLC Start Date

TLC End Date

Project Start Date

Data Date

Time Axis Tiers

Number of tiers (1–3)

Tier 1 (outermost)

Tier 2

Tier 3 (innermost)

Season Band — only enabled seasons display

Monsoon –

Winter –

Summer –

Default Activity:

DATE	FROM CH (KM)	TO CH (KM)	ACTIVITY	STATUS

Copy rows from Excel or Google Sheets — columns: Date · From Ch (km) · To Ch (km) · Activity · Status.
One row per line, tab-separated. Header row is auto-detected and skipped.
Accepted date formats: YYYY-MM-DD · DD/MM/YYYY · DD-Mon-YYYY · DD-MM-YYYY.

Default Activity (if column missing):

ID	Category	Description	P	I	Score	Residual	Status	Owner	Mitigation

No risks recorded. Click + Add Risk to begin.

0

Total Risks

0

Open

0

High (≥15)

0

Closed

Risk Heatmap (P × I)

Low (1–4)

Medium (5–9)

High (10–24)

Very High (25)

P = Probability (1-5) · I = Impact (1-5)

📌 Delay Analysis Register — Log delay events, classify by responsibility, and record concurrent delay. This register feeds into §3 Schedule Status of the Progress Report. EOT quantum is auto-summed per classification.

0d

Employer Risk

0d

Contractor Risk

0d

Neutral / Force Majeure

0d

Net EOT Entitlement

ID	Activity	Event Description	Start Date	End Date	Delay (d)	Classification	Concurrent?	Concurrent Days	Net Days	Clause Ref	Status

No delay events recorded. Click + Add Delay Event to begin.