Introduction :
Earned value in Primavera P6 is built from system logic. It depends on how cost, time, and progress are stored and linked. The tool does not guess work done. It reads data from activities, resources, and baselines. If any link is weak, the earned value becomes wrong. This creates wrong cost status and wrong schedule status. Learning this logic through Primavera P6 Training helps teams avoid silent setup issues that break reports.
Earned value is affected by baseline setup, activity progress type, resource curves, and time-phased costs. Each part must match how work happens on site. When teams skip these checks, reports look fine but the values do not match real progress.
How does Primavera P6 calculate earned value?
Primavera P6 calculates earned value from stored data. It does not work on rough progress. It follows set rules. The base of earned value is the approved baseline budget. This budget is spread across planned dates. The spread depends on resource curves and expense curves. Planned value comes from this time spread.
Earned value is the budgeted cost of work done. The tool multiplies the activity budget with the progress value. The progress value comes from the percent complete type set on the activity.
Actual cost comes from resource actuals and expense actuals. These values come from timesheets or cost imports. All values are time-phased by date. Many site engineers join Primavera P6 Training in Noida to learn how to handle schedules, track progress, and control project delays better.
- If the baseline is wrong, the earned value is wrong.
- If progress type is wrong, earned value is wrong.
- If curves are wrong, earned value timing is wrong.
Main data used by Primavera P6 for earned value
| Data Item | What it controls | Impact on earned value |
| Baseline budget | Total planned cost | Sets total EV limit |
| Percent complete type | How progress is read | Controls EV calculation method |
| Resource curves | How budget is spread | Controls EV timing |
| Expense curves | How expenses are spread | Changes EV spikes |
| Actual cost | Real cost spent | Controls CPI |
Key points to remember
- Earned value is not typed by the user.
- It is calculated from system data.
- Wrong setup leads to wrong EV.
Therefore, Primavera P6 Training in Noida helps working professionals learn real project planning with live practice and clear steps that match site work.
Common setup issues that cause earned value errors
Many earned value problems come from simple setup mistakes. These mistakes stay hidden.
Mixed progress logic
- Some activities use Physical percent complete.
- Some use Duration percent complete.
- Some use Units percent complete.
When these are mixed under one work group, earned value totals become uneven. Physical work should use Physical percent complete. Resource work should use Units percent complete. Time-only work should use Duration percent complete. Primavera P6 Training helps learners understand project planning, progress tracking, and cost control in a clear and practical way.
Wrong expense setup
- Expenses can be set at start, finish, or spread.
- Start-based expenses push earned value early.
- Finish-based expenses delay earned value.
- Spread expenses follow work flow.
- Wrong expense setup creates sudden EV jumps.
Late cost updates
- Actual cost often comes late from finance systems.
- Earned value moves forward with progress.
- CPI then looks good even when the cost is high.
- This hides real cost issues.
Baseline mismatch
Teams change the schedule but forget to change the EV baseline. Earned value is then compared with old budgets. Reports show false variances.
Common errors and how to fix them
| Problem seen in report | Root cause | Simple fix |
| EV jumps too fast | Expenses set at start | Spread expenses |
| CPI looks too good | Cost data late | Sync cost on time |
| SPI looks poor | Duration % used for scope | Use Physical % |
| EV does not match site | Wrong EV baseline | Set correct baseline |
Pointers
- Keep progress logic the same for similar work.
- Do not change curves without review.
- Lock baselines after approval.
- Sync cost data on fixed dates.
Key takeaways
- Earned value in Primavera P6 depends on baseline, progress type, curves, and cost timing.
- Mixed progress logic breaks EV totals.
- Wrong expense setup causes EV spikes.
- Late cost data creates false CPI values.
- Baseline control is critical for clean EV reports.
- Regular logic checks prevent silent errors.
Sum up,
Primavera P6 earned value follows strict system logic. It reads budget, progress, and cost from linked settings. If these settings do not match real work flow, earned value becomes misleading. This leads to wrong cost and schedule status. Primavera P6 Training Institute in Delhi supports learners with hands-on schedule work, real cost tracking tasks, and proper project control methods. When teams treat earned value as a technical control process, Primavera P6 becomes a strong planning and control system. Without this discipline, earned value turns into a weak number that hides real project issues.