Planned, Expected and Actual

This is a subpage of a larger section.

Return to: DFR Planner

Planned, Feasible and Actual

• Planned dates and data hold the original dates and data (start end, duration, cost etc.) put in the planner.
• Actual dates and data hold the final actual dates and data as recorded by the team on task/action/gate start/completion.
• Feasible dates and data are automatically and continuously updated based on how the project progresses.
  • Feasible Start Date is the earliest possible date the gate or action can start (based on prior dependencies). If there is no precedence or dependencies this is equal to the planned start date.
  • Feasible End Date is the expected completion date.
  • Feasible Duration is the length (in days) of the available time window to complete the action/gate.

In the ideal scenario, where each item is completed on-time and exactly as planned, all three are the same. In the real world however this is rarely the case.

Example

Consider the project shown in the table below comprised of three top level gates, six sub-gates and 12 actions.

P1: Project 1
	G1: Gate 1
		SG11: SubGate 11
			A01: Action 1
			A02: Action 2
		SG12: SubGate 12
			A03: Action 3
			A04: Action 4
	G2: Gate 2
		SG21: SubGate 21
			A05: Action 5
			A06: Action 6
		SG22: SubGate 22
			A07: Action 7
			A08: Action 8
	G3: Gate 3
		SG31: SubGate 31
			A09: Action 9
			A10: Action 10
		SG32: SubGate 32
			A11: Action 11
			A12: Action 12

Planning Stage

Settings and Assumptions

• There is a same level precedence for each Gate and Sub-gate. No precedence is set for the actions within a gate, however the plans calls for them to run sequentially.
• Each day is a workday (no weekends and holidays). This is set through the Work Days Scheduler interface, which can be found in Manage Repository under the Repository Settings.
• Each Action has a duration of three days.
• Actions start at the beginning of the workday assigned (i.e. first thing in the morning)  and end at the end of the workday assigned.  For example a two day action starting on January 1 would be completed on January 2 (e.g. all day on day 1 and all day on day 2).
• Action 1 starts in January 1, when completed Action 2 starts and so forth.
• No lag time between gates and actions.

Planned Dates

Based on the above settings and assumptions, the planned dates would be as follows:

DFR Plan

				Planned Dates
				Start Date	Duration	End Date
P1: Project 1				Jan-01	36	Feb-05
	G1: Gate 1			Jan-01	12	Jan-12
		SG11: SubGate 11		Jan-01	6	Jan-06
			A01: Action 1	Jan-01	3	Jan-03
			A02: Action 2	Jan-04	3	Jan-06
		SG12: SubGate 12		Jan-07	6	Jan-12
			A03: Action 3	Jan-07	3	Jan-09
			A04: Action 4	Jan-10	3	Jan-12
	G2: Gate 2			Jan-13	12	Jan-24
		SG21: SubGate 21		Jan-13	6	Jan-18
			A05: Action 5	Jan-13	3	Jan-15
			A06: Action 6	Jan-16	3	Jan-18
		SG22: SubGate 22		Jan-19	6	Jan-24
			A07: Action 7	Jan-19	3	Jan-21
			A08: Action 8	Jan-22	3	Jan-24
	G3: Gate 3			Jan-25	12	Feb-05
		SG31: SubGate 31		Jan-25	6	Jan-30
			A09: Action 9	Jan-25	3	Jan-27
			A10: Action 10	Jan-28	3	Jan-30
		SG32: SubGate 32		Jan-31	6	Feb-05
			A11: Action 11	Jan-31	3	Feb-02
			A12: Action 12	Feb-03	3	Feb-05

Planned Costs

Planned costs can be automatically included/calculated based on the resources assigned to each action. See also DFR Resources, which can be found in Manage Repository under the Repository Settings.

For this example will only consider labor costs and ignore other cost variables.  From a labor prespective assume the following resources are assigned to the project.

Team Members & Resources For Project
Name	Hrs/Day	Cost Per Hour
Manager 1	8	100
Manager 2	8	100
Employee 1	8	50
Employee 2	8	50
Employee 3	8	50
Employee 4	8	50

These are defined in team resources as follows:

Teams
Name	Members
Team 1-2	E1 & E2
Team 2-3	E2 & E3
Team 3-4	E3 & E4
Team 1-2-3-4	E1, E2, E3 & E4

The allocation to tasks is as follows:

				Planned Dates			Manager		Team
				Start Date	Duration	End Date	Name	%Allocation	Name	%Allocation
P1: Project 1				Jan-01	36	Feb-05
	G1: Gate 1			Jan-01	12	Jan-12
		SG11: SubGate 11		Jan-01	6	Jan-06
			A01: Action 1	Jan-01	3	Jan-03	M1	25%	Team 1-2	100%
			A02: Action 2	Jan-04	3	Jan-06	M2	25%	Team 1-2-3-4	80%
		SG12: SubGate 12		Jan-07	6	Jan-12
			A03: Action 3	Jan-07	3	Jan-09	M1	50%	Team 3-4	100%
			A04: Action 4	Jan-10	3	Jan-12	M2	15%	Team 2-3	100%
	G2: Gate 2			Jan-13	12	Jan-24
		SG21: SubGate 21		Jan-13	6	Jan-18
			A05: Action 5	Jan-13	3	Jan-15	M1	50%	Team 2-3	100%
			A06: Action 6	Jan-16	3	Jan-18	M1	30%	Team 1-2	50%
		SG22: SubGate 22		Jan-19	6	Jan-24
			A07: Action 7	Jan-19	3	Jan-21	M2	20%	Team 1-2-3-4	50%
			A08: Action 8	Jan-22	3	Jan-24	M2	70%	Team 1-2-3-4	75%
	G3: Gate 3			Jan-25	12	Feb-05
		SG31: SubGate 31		Jan-25	6	Jan-30
			A09: Action 9	Jan-25	3	Jan-27	M1	30%	Team 3-4	60%
			A10: Action 10	Jan-28	3	Jan-30	M1	30%	Team 2-3	70%
		SG32: SubGate 32		Jan-31	6	Feb-05
			A11: Action 11	Jan-31	3	Feb-02	M2	50%	Team 2-3	80%
			A12: Action 12	Feb-03	3	Feb-05	M2	60%	Team 3-4	80%

From the inputs as defined above then the planned costs would be:

				Planned Dates			Planned
				Start Date	Duration	End Date	Cost
P1: Project 1				Jan-01	36	Feb-05	($38,520)
	G1: Gate 1			Jan-01	12	Jan-12	($13,800)
		SG11: SubGate 11		Jan-01	6	Jan-06	($7,440)
			A01: Action 1	Jan-01	3	Jan-03	($3,000)
			A02: Action 2	Jan-04	3	Jan-06	($4,440)
		SG12: SubGate 12		Jan-07	6	Jan-12	($6,360)
			A03: Action 3	Jan-07	3	Jan-09	($3,600)
			A04: Action 4	Jan-10	3	Jan-12	($2,760)
	G2: Gate 2			Jan-13	12	Jan-24	($13,680)
		SG21: SubGate 21		Jan-13	6	Jan-18	($5,520)
			A05: Action 5	Jan-13	3	Jan-15	($3,600)
			A06: Action 6	Jan-16	3	Jan-18	($1,920)
		SG22: SubGate 22		Jan-19	6	Jan-24	($8,160)
			A07: Action 7	Jan-19	3	Jan-21	($2,880)
			A08: Action 8	Jan-22	3	Jan-24	($5,280)
	G3: Gate 3			Jan-25	12	Feb-05	($11,040)
		SG31: SubGate 31		Jan-25	6	Jan-30	($4,560)
			A09: Action 9	Jan-25	3	Jan-27	($2,160)
			A10: Action 10	Jan-28	3	Jan-30	($2,400)
		SG32: SubGate 32		Jan-31	6	Feb-05	($6,480)
			A11: Action 11	Jan-31	3	Feb-02	($3,120)
			A12: Action 12	Feb-03	3	Feb-05	($3,360)

Planned Resource Loading

In this example the only resource used was personnel. Based on the prior entries each team member's utilization is as follows. Note that no overallocation are present.

	A01			A02			A03			A04			A05			A06			A07			A08			A09			A10			A11			A12
	1/1	1/2	1/3	1/4	1/5	1/6	1/7	1/8	1/9	1/10	1/11	1/12	1/13	1/14	1/15	1/16	1/17	1/18	1/19	1/20	1/21	1/22	1/23	1/24	1/25	1/26	1/27	1/28	1/29	1/30	1/31	2/1	2/2	2/3	2/4	2/5
Manager 1	25%	25%	25%	0%	0%	0%	50%	50%	50%	0%	0%	0%	50%	50%	50%	30%	30%	30%	0%	0%	0%	0%	0%	0%	30%	30%	30%	30%	30%	30%	50%	50%	50%	60%	60%	60%
Manager 2	0%	0%	0%	25%	25%	25%	0%	0%	0%	15%	15%	15%	0%	0%	0%	0%	0%	0%	20%	20%	20%	70%	70%	70%	0%	0%	0%	0%	0%	0%	0%	0%	0%	80%	80%	80%
Employee 1	100%	100%	100%	80%	80%	80%	0%	0%	0%	0%	0%	0%	0%	0%	0%	50%	50%	50%	50%	50%	50%	75%	75%	75%	0%	0%	0%	0%	0%	0%	0%	0%	0%	0%	0%	0%
Employee 2	100%	100%	100%	80%	80%	80%	0%	0%	0%	100%	100%	100%	100%	100%	100%	50%	50%	50%	50%	50%	50%	75%	75%	75%	0%	0%	0%	70%	70%	70%	80%	80%	80%	0%	0%	0%
Employee 3	0%	0%	0%	80%	80%	80%	100%	100%	100%	100%	100%	100%	100%	100%	100%	0%	0%	0%	50%	50%	50%	75%	75%	75%	60%	60%	60%	70%	70%	70%	80%	80%	80%	80%	80%	80%
Employee 4	0%	0%	0%	80%	80%	80%	100%	100%	100%	0%	0%	0%	0%	0%	0%	0%	0%	0%	50%	50%	50%	75%	75%	75%	60%	60%	60%	0%	0%	0%	0%	0%	0%	80%	80%	80%

Execution Stage

Action 1

Assume that the project got started a day late, i.e. the initiating action (A01) got started on Jan-2 instead of Jan 1.

Then on Jan-2 the DFR Plan would then transform as follows:

Planned Dates

Feasible Dates

Actual Dates

Planned

Estimated

Actual

Start Date

Duration

End Date

Start Date

End Date

Start Date

Duration

End Date

Budget

To-Date

To-Date

P1: Project 1

Jan-01

36

Feb-05

Jan-01

Feb-05

Jan-02

$38,520

$1,000

G1: Gate 1

Jan-01

12

Jan-12

Jan-01

Jan-12

Jan-02

$13,800

$1,000

SG11: SubGate 11

Jan-01

6

Jan-06

Jan-01

Jan-06

Jan-02

$7,440

$1,000

A01: Action 1

Jan-01

3

Jan-03

Jan-01

Jan-04

Jan-02

$3,000

$1,000*

A02: Action 2

Jan-04

3

Jan-06

Jan-04

Jan-06

$4,440

SG12: SubGate 12

Jan-07

6

Jan-12

Jan-07

Jan-12

$6,360

A03: Action 3

Jan-07

3

Jan-09

Jan-07

Jan-09

$3,600

A04: Action 4

Jan-10

3

Jan-12

Jan-10

Jan-12

$2,760

G2: Gate 2

Jan-13

12

Jan-24

Jan-13

Jan-24

$13,680

SG21: SubGate 21

Jan-13

6

Jan-18

Jan-13

Jan-18

$5,520

A05: Action 5

Jan-13

3

Jan-15

Jan-13

Jan-15

$3,600

A06: Action 6

Jan-16

3

Jan-18

Jan-16

Jan-18

$1,920

SG22: SubGate 22

Jan-19

6

Jan-24

Jan-19

Jan-24

$8,160

A07: Action 7

Jan-19

3

Jan-21

Jan-19

Jan-21

$2,880

A08: Action 8

Jan-22

3

Jan-24

Jan-22

Jan-24

$5,280

G3: Gate 3

Jan-25

12

Feb-05

Jan-25

Feb-05

$11,040

SG31: SubGate 31

Jan-25

6

Jan-30

Jan-25

Jan-30

$4,560

A09: Action 9

Jan-25

3

Jan-27

Jan-25

Jan-27

$2,160

A10: Action 10

Jan-28

3

Jan-30

Jan-28

Jan-30

$2,400

SG32: SubGate 32

Jan-31

6

Feb-05

Jan-31

Feb-05

$6,480

A11: Action 11

Jan-31

3

Feb-02

Jan-31

Feb-02

$3,120

A12: Action 12

Feb-03

3

Feb-05

Feb-03

Feb-05

$3,360

(*) Since this is the first day in a task of a total duration of 3 days and total cost of $3000 the estimated cost to date is $3,000/3=$1,000

Resource Conflicts

The late start of A01 causes a resource conflict as shown next.

Action 2

Assume that action A01 was completed on Jan-05 and A02 started on Jan-07.  Then the entire plan would shift as follows:

Planned Dates

Feasible Dates

Actual Dates

Planned

Estimated

Actual

Start Date

Duration

End Date

Start Date

End Date

Start Date

Duration

End Date

Cost

Cost-to-Date

Cost

P1: Project 1

Jan-01

36

Feb-05

Jan-01

Feb-08

Jan-02

$38,520.00)

$5,480.00)

$4,000.00)

G1: Gate 1

Jan-01

12

Jan-12

Jan-01

Jan-15

Jan-02

$13,800.00)

$5,480.00)

$4,000.00)

SG11: SubGate 11

Jan-01

6

Jan-06

Jan-01

Jan-09

Jan-02

$7,440.00)

$5,480.00)

$4,000.00)

A01: Action 1

Jan-01

3

Jan-03

Jan-01

Jan-04

Jan-02

4

Jan-05

$3,000.00)

$4,000.00)

$4,000.00)

A02: Action 2

Jan-04

3

Jan-06

Jan-04

Jan-09

Jan-07

$4,440.00)

$1,480.00)

SG12: SubGate 12

Jan-07

6

Jan-12

Jan-10

Jan-15

$6,360.00)

A03: Action 3

Jan-07

3

Jan-09

Jan-10

Jan-12

$3,600.00)

A04: Action 4

Jan-10

3

Jan-12

Jan-13

Jan-15

$2,760.00)

G2: Gate 2

Jan-13

12

Jan-24

Jan-16

Jan-27

$13,680.00)

SG21: SubGate 21

Jan-13

6

Jan-18

Jan-16

Jan-21

$5,520.00)

A05: Action 5

Jan-13

3

Jan-15

Jan-16

Jan-18

$3,600.00)

A06: Action 6

Jan-16

3

Jan-18

Jan-19

Jan-21

$1,920.00)

SG22: SubGate 22

Jan-19

6

Jan-24

Jan-22

Jan-27

$8,160.00)

A07: Action 7

Jan-19

3

Jan-21

Jan-22

Jan-24

$2,880.00)

A08: Action 8

Jan-22

3

Jan-24

Jan-25

Jan-27

$5,280.00)

G3: Gate 3

Jan-25

12

Feb-05

Jan-28

Feb-08

$11,040.00)

SG31: SubGate 31

Jan-25

6

Jan-30

Jan-28

Feb-02

$4,560.00)

A09: Action 9

Jan-25

3

Jan-27

Jan-28

Jan-30

$2,160.00)

A10: Action 10

Jan-28

3

Jan-30

Jan-31

Feb-02

$2,400.00)

SG32: SubGate 32

Jan-31

6

Feb-05

Feb-03

Feb-08

$6,480.00)

A11: Action 11

Jan-31

3

Feb-02

Feb-03

Feb-05

$3,120.00)

A12: Action 12

Feb-03

3

Feb-05

Feb-06

Feb-08

$3,360.00)

End Section

Basis, Impact & Discussion

Basis for Modification	Basis Discuss
Impact on V8/V9 Users	Impact Discuss
Discussion	Comment on this feature, or discuss it in the Synthesis Discussion area of our Discussion Forums.
These pages are not intended to replace, or be used in-lieu of the official software documentation. They are working/developments notes intended to facilitate communication between the user community and the development team. Features and specifications listed here are for discussion purposes and their final implementation in may be different than the specifications presented here.