# SAP Migration Schedule Risk PERT Calculator

> Source: https://netray.co/tools/sap-migration-schedule-risk-pert-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Turn optimistic, likely and pessimistic durations into a commitment date at the confidence level you choose.

## Category

erp-migration

## Erp

SAP S/4HANA

## Audience

- SAP program manager
- PMO
- CIO

## Tool

**Kind:** calculator

**Inputs:**

#### Optimistic duration

**Key:** opt

**Type:** number

**Default:** 14

**Min:** 1

**Step:** 1

**Unit:** months

**Help:** Everything goes well; about a 5 percent chance of being this fast or faster.

#### Most likely duration

**Key:** likely

**Type:** number

**Default:** 18

**Min:** 1

**Step:** 1

**Unit:** months

**Help:** Your honest single-point plan.

#### Pessimistic duration

**Key:** pess

**Type:** number

**Default:** 28

**Min:** 1

**Step:** 1

**Unit:** months

**Help:** Serious but realistic setbacks such as failed rehearsals or late data cleansing.

#### Confidence level for commitment

**Key:** conf

**Type:** select

**Default:** 0.8

**Options:**

##### 50%

**Value:** 0.5

##### 70%

**Value:** 0.7

##### 80%

**Value:** 0.8

##### 90%

**Value:** 0.9

##### 95%

**Value:** 0.95

#### Program burn rate

**Key:** burn

**Type:** number

**Default:** 450000

**Min:** 0

**Step:** 10000

**Unit:** $ per month

**Help:** Total monthly team and vendor cost.

**Outputs:**

#### PERT expected duration

**Key:** mean

**Expr:** (opt + 4 * likely + pess) / 6

**Format:** months

**Description:** Weighted mean of the three points.

#### Standard deviation

**Key:** sd

**Expr:** (pess - opt) / 6

**Format:** decimal

**Description:** Spread of the estimate in months.

#### Z score for chosen confidence

**Key:** z

**Expr:** normsinv(conf)

**Format:** decimal

#### Duration to commit at chosen confidence

**Key:** commit

**Expr:** mean + z * sd

**Format:** months

**Primary:** true

**Description:** Duration you can promise with the selected probability.

#### Schedule reserve over expected

**Key:** reserve

**Expr:** commit - mean

**Format:** months

#### Cost of the schedule reserve

**Key:** reserve_cost

**Expr:** max(reserve, 0) * burn

**Format:** currency

**Primary:** true

**Description:** Budget needed if the reserve is fully used.

**Chart:**

#### Committed duration vs optimistic estimate

**Type:** line

**X:** opt

**From:** 6

**To:** 18

**Steps:** 13

**Series:**

- commit
- mean

**Disclaimer:** PERT assumes a roughly normal total duration and independent risks. Real programs have correlated risks; treat the output as a discussion aid.

## Content

**Intro:** A single go-live date hides how uncertain it is. A three-point estimate shows the spread, and the confidence level tells you how much reserve you need to promise a date you can keep.

**Sections:**

#### How to use it

**Body:** Ask the program team for three numbers for the full duration: optimistic, most likely and pessimistic. Do this independently, then compare. Pick the confidence level the sponsor wants for the committed date. The calculator returns the PERT expected duration, the standard deviation, and the duration to commit at that level, with the cost of the schedule reserve based on your monthly burn rate.

**Bullets:**

- Collect estimates from several leads separately
- Keep pessimistic realistic, not catastrophic
- Choose confidence with the sponsor, not alone
- Review monthly as rehearsals complete

#### The formula

**Body:** Expected duration is (optimistic + 4 x most likely + pessimistic) / 6. Standard deviation is (pessimistic - optimistic) / 6. The commitment duration is expected plus z times the standard deviation, where z comes from the inverse normal distribution for your confidence level; at 80 percent z is about 0.84 and at 90 percent about 1.28. The difference between commitment and expected duration is the reserve, which multiplied by the burn rate gives its cost.

#### Common mistakes

**Body:** Teams often set the pessimistic case too close to the likely one, which understates risk, or treat PERT as a prediction rather than a model. If critical-path risks are correlated, such as late data cleansing causing both test and cutover delays, true uncertainty is wider than shown. Use the reserve cost to start an honest conversation about contingency instead of hiding it inside task estimates.

**Cta:** Netray can build a private assistant over your plans, risk logs and status reports to help track schedule drift across workstreams.

**Faq:**

#### Why divide by six?

**Answer:** In the PERT approximation, the range between optimistic and pessimistic covers about six standard deviations of a roughly bell-shaped distribution, so one sixth of the range is the standard deviation.

#### Which confidence level should I commit to?

**Answer:** Many sponsors accept 80 percent for internal plans and 90 percent for external or contractual dates. Higher confidence costs more reserve, so make the trade-off explicit.

#### Does this replace critical path analysis?

**Answer:** No. It summarises uncertainty at the program level. Use a schedule with a critical path and, if needed, a Monte Carlo tool for detailed risk analysis.

#### Can I use weeks instead of months?

**Answer:** Yes, as long as all three estimates use the same unit. The labels say months, but the arithmetic is unit-free; adjust the burn rate to the same period.

## Search terms

pert calculator sap project, sap migration schedule risk, three point estimate calculator, s4hana timeline estimate, project confidence level duration, sap go-live date confidence, pert expected duration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json