Earned Value Management (EVM) for Aerospace Programmes

What EVM is and why aerospace programmes need it

Ask two managers how a programme is doing and you often get two different stories. One points at the budget and says spending is on track. Another points at the schedule and says the team is working flat out. Neither answer tells you whether the programme is actually going to deliver on cost and on time, because neither connects money to accomplishment. Earned value management exists to close that gap.

EVM is a technique that measures progress in the same units as the plan and the spend, so that cost, schedule and scope become one integrated picture. Instead of asking how much have we spent, it asks how much of the planned work have we actually completed and what did that completed work cost. On a job that lasts a few weeks this is a luxury. On a multi-year aerospace or defence programme, where a cost overrun discovered late can wipe out a margin that took years to build, it is a necessity.

For manufacturers supplying HAL, ISRO, DRDO and their primes, the customer often expects programme reporting that stands up to scrutiny. That is why serious aerospace programme management with EVM is treated as a core operational capability rather than a finance afterthought. Public standards bodies such as NIST have long promoted measurement discipline in complex acquisition, and the aerospace quality framework coordinated by the International Aerospace Quality Group assumes that programme performance is managed with evidence, not optimism.

Building the WBS: the foundation of every EVM number

Every earned value number begins with a work breakdown structure. The WBS decomposes the whole programme into progressively smaller, deliverable-oriented pieces, until you reach control accounts and work packages small enough to plan, budget and measure honestly. If the WBS is vague, every number built on top of it is vague too. If it is disciplined, EVM becomes almost mechanical.

A good aerospace WBS is product-oriented rather than department-oriented. It follows the deliverable: airframe structure, avionics integration, qualification testing, first article, delivery. Each element carries a budget, a schedule and a defined way of measuring completion. That measurement method matters enormously. A work package measured by percent complete invites wishful thinking, so aerospace programmes prefer objective methods: milestones with clear entry and exit criteria, units completed, or fixed formulas for work that starts and finishes within a period.

The WBS also has to reconcile with the physical product structure. The way a programme is broken down for management has to line up with the bill of materials and the released baseline, or reporting and execution drift apart. This is why the WBS is best defined alongside aerospace BOM and configuration software, so that the control accounts used for earned value map cleanly onto the assemblies the shop floor actually builds.

The three core measures: PV, EV and AC

Earned value rests on three quantities, each measured in currency so they can be compared directly. Planned value is the budgeted cost of the work scheduled to be done by a given date. Earned value is the budgeted cost of the work that has actually been completed by that date. Actual cost is what that completed work truly cost. Everything else in EVM is derived from these three.

The power of these three is in their differences. Earned value minus actual cost is the cost variance: positive means the work cost less than budgeted, negative means it cost more. Earned value minus planned value is the schedule variance, expressed in money: positive means more has been accomplished than planned, negative means less. Because both variances use the same baseline budget, they can be summed all the way up the WBS to give a single programme-level position that is internally consistent from the smallest work package to the top.

CPI and SPI: reading programme health

Variances tell you the size of a problem in currency. Indices tell you the efficiency behind it, which is what you need to forecast. The cost performance index is earned value divided by actual cost. A value of one means you are getting exactly a rupee of planned work for every rupee spent. Below one means you are spending more than the work is worth. The schedule performance index is earned value divided by planned value, and it tells you how fast work is being accomplished against the plan.

These two indices are powerful because they are ratios, so they are comparable across work packages of very different sizes and they trend meaningfully over time. A control account running a cost performance index of 0.9 for three consecutive reporting periods is not having a bad month. It has a structural problem, and the trend is a warning that the final cost will overrun unless something changes. Reading the two indices together is especially revealing. Strong schedule performance bought with poor cost performance often means the programme is throwing overtime and expedite costs at a slipping plan, which is rarely sustainable.

The discipline only works if earned value reflects genuine accomplishment. When progress is claimed from the shop floor in real time through an aerospace shop floor MES and confirmed against completed operations, the indices are trustworthy. When progress is a monthly guess typed into a spreadsheet, they are theatre.

Milestone billing and progress payments

On long programmes, cash cannot wait for final delivery. Customers pay against progress, and the mechanism is usually milestone billing or progress payments. The earned value baseline and the billing schedule should be two views of the same reality, so that what you invoice is anchored to what you have genuinely accomplished. When they diverge, a programme can look profitable on paper while starving for cash, or bill ahead of progress and face a painful reconciliation later.

• Event-based milestones release payment when a defined deliverable is accepted, such as a completed first article or a passed qualification test.
• Progress payments reimburse a percentage of incurred cost as work proceeds, common on cost-reimbursable defence contracts.
• Retention holds back a portion until acceptance, protecting the customer against late defects.
• Provisional and final invoicing reconcile early estimates against audited actuals at defined points.

Tying billing milestones to the WBS matters because it removes argument. When a milestone is defined by objective earned value criteria and evidenced by inspection and delivery records, both parties see the same fact. This is where EVM and delivery evidence meet the traceability record: a milestone tied to an accepted first article is only as solid as the conformance evidence behind it, which is why programme control and aerospace traceability software belong in one connected system.

Multi-year cost control and estimate at completion

The single most valuable output of EVM is a forecast you can defend. The estimate at completion projects what the whole programme will finally cost, based on performance so far rather than the original hope. The most common approach assumes that the efficiency shown to date will continue: it takes the remaining work and adjusts it by the cost performance index, then adds it to what has already been spent. If a programme has been running at a cost performance index of 0.9, the remaining work will most likely cost more than its budget, and the estimate at completion says so in numbers, early.

This is what changes the conversation with management and customers. Instead of discovering an overrun when the budget line is crossed, a programme office can see the trajectory months ahead and choose to act: rebaseline, descope, add resource, or renegotiate. On a multi-year programme those months of warning are the difference between a managed correction and a crisis. The estimate to complete, the remaining spend forecast, feeds directly into cash planning and resource loading. When these forecasts live inside the aerospace and defence ERP software that also holds bookings and commitments, they update as reality changes instead of ageing in a static workbook.

How a configured ERP runs EVM

EVM asks a lot of an organisation. It needs a time-phased baseline, objective progress capture, actual costs collected against the right accounts, and a monthly cadence that reconciles all three without a heroic manual effort. Spreadsheets can demonstrate EVM on one programme. They cannot sustain it across a portfolio, because the data is copied by hand, the baseline drifts, and by the time the numbers are assembled they are already stale.

A configured ERP removes the copying. The WBS lives in the system as the spine that connects the plan to execution. Timesheets and supplier invoices post actual cost to control accounts automatically. Progress confirmed on the shop floor becomes earned value without re-keying. The indices, variances and estimate at completion are then computed from live data on demand. Elite Tech Corporation builds this on configured Zoho combined with custom AWS services rather than selling a packaged EVM product, so the control account structure, progress methods and reporting match how each programme actually runs. Manufacturers who want it delivered and validated locally choose aerospace and defence ERP in Bangalore as a configured implementation, not a shrink-wrapped licence.

Making EVM real on an aerospace programme in Bangalore

The gap between EVM in theory and EVM in practice is almost always data discipline. The method is not hard to understand. The hard part is capturing objective progress consistently, collecting actual costs against the right control account, and keeping the baseline honest when scope changes. A rollout that ignores these realities produces beautiful reports that nobody trusts, because everyone knows the underlying numbers are massaged.

A sound implementation starts small and objective. It defines a WBS that mirrors the product, chooses measurement methods that resist wishful thinking, and connects cost collection to the same accounts. It handles change through a controlled rebaseline so the plan stays meaningful, which ties EVM directly to aerospace configuration management and its change control discipline. Then it automates the monthly cycle so the numbers arrive on time and the same way every period. Elite Tech Corporation delivers this through aerospace ERP implementation services that configure Zoho and custom AWS to the programme, validate the earned value model against real reporting cycles, and train the programme office to run it. If you want to pressure-test EVM against one of your own programmes, speak to our aerospace team.

Conclusion

Earned value management is not about producing charts for a review meeting. It is about knowing, honestly and early, whether a programme is going to deliver on cost and on time while there is still room to steer. The three measures are simple, the two indices are easy to read, and the estimate at completion is the payoff: a forecast grounded in what has actually happened rather than what everyone hoped. What separates programmes that use EVM from programmes that merely report it is data discipline, and that discipline is far easier to hold when the work breakdown structure, cost collection and progress capture live in one connected system. For aerospace and defence manufacturers in Bengaluru and across India, a configured Zoho plus AWS platform makes EVM a running instrument rather than a monthly ordeal.