Planned, Expected and Actual - Revision history

Richard House: Replaced content with 'Category: For Deletion'

2015-04-30T15:33:07Z

Replaced content with 'Category: For Deletion'

John Leavitt at 20:56, 28 January 2015

2015-01-28T20:56:33Z

← Older revision		Revision as of 20:56, 28 January 2015
Line 4:		Line 4:

	<br>		<br>
			====Summary====
			Unlike traditional project planning tools used for the creation of the plan, the DFR planner in Synthesis is not only used to create the plan, but also automatically tracks, monitors and updates the entire plan as time progresses and as actions are completed. This is done through the simultaneous use of three different types of dates and data, namely, ''planned'', ''Expected'' and ''actual''.

	==== Planned, Expected and Actual ====		==== Planned, Expected and Actual ====

John Leavitt: /* Planned, Expected and Actual */

2014-09-30T18:48:42Z

Planned, Expected and Actual

← Older revision		Revision as of 18:48, 30 September 2014
Line 13:		Line 13:
	***If there is no precedence or dependencies this is equal to the planned start date.		***If there is no precedence or dependencies this is equal to the planned start date.
	***If there is a precedence then this is the earliest start date possible, after the completion of the precedence.		***If there is a precedence then this is the earliest start date possible, after the completion of the precedence.
	**''Expected Completion ~~End~~ Date'' is the date that completion of the action is feasible.		**''Expected Completion Date'' is the date that completion of the action is feasible.
	***This is the "Expected Start Date + Planned Duration".		***This is the "Expected Start Date + Planned Duration".
	**''Expected Window'' is the length (in days) of the available time window to complete the action/gate.		**''Expected Window'' is the length (in days) of the available time window to complete the action/gate.
Line 20:		Line 20:

	<br>		<br>


	=== Example ===		=== Example ===

John Leavitt at 18:32, 30 September 2014

2014-09-30T18:32:59Z

← Older revision		Revision as of 18:32, 30 September 2014
Line 5:		Line 5:
	<br>		<br>

	==== Planned, ~~Feasible~~ and Actual ====		==== Planned, Expected and Actual ====

	*Planned dates and data hold the original dates and data (start end, duration, cost etc.) put in the planner.		*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.		*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.		*Expected 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).		**''Earliest Expected 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.		***If there is no precedence or dependencies this is equal to the planned start date.
	***If there is a precedence then this is the earliest start date possible, after the completion of the precedence.		***If there is a precedence then this is the earliest start date possible, after the completion of the precedence.
	**''~~Feasible~~ End Date'' is the ~~expected~~ completion ~~date~~.		**''Expected Completion End Date'' is the date that completion of the action is feasible.
	***This is the "~~Feasible~~ Start Date + Planned Duration".		***This is the "Expected Start Date + Planned Duration".
	**''~~Feasible~~ Window'' is the length (in days) of the available time window to complete the action/gate.		**''Expected Window'' 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.		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.
Line 984:		Line 984:
	'''Resource Conflicts'''		'''Resource Conflicts'''

	The late start of Action 1000 causes a resource conflict as shown next. Planned and ~~Feasible~~ dates are shown in this display. John Reliable, Eugene Doubter, and Maria General must allocate more resources to complete the project on time.		The late start of Action 1000 causes a resource conflict as shown next. Planned and Expected dates are shown in this display. John Reliable, Eugene Doubter, and Maria General must allocate more resources to complete the project on time.

	[[Image:Dfrex1 1.png\|center\|900px]]<br>		[[Image:Dfrex1 1.png\|center\|900px]]<br>

John Leavitt: moved Planned, Feasible and Actual to Planned, Expected and Actual

2014-09-30T18:25:15Z

moved Planned, Feasible and Actual to Planned, Expected and Actual

← Older revision	Revision as of 18:25, 30 September 2014
(No difference)

John Leavitt: /* End Section */

2014-09-30T18:01:22Z

End Section

← Older revision		Revision as of 18:01, 30 September 2014
Line 994:		Line 994:

	[[File:OnRevisedPlan.png]]		[[File:OnRevisedPlan.png]]

			A completed project may look like the following:
			[[File:CompletedDFR.png]]






	==== End Section ====		==== End Section ====

John Leavitt: /* Planning Stage */

2014-09-30T17:28:04Z

Planning Stage

← Older revision		Revision as of 17:28, 30 September 2014
Line 151:		Line 151:
	*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.		*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.
	*Monday, Tuesday, Wednesday, Thursday and Friday are workdays. Weekends include Saturday and Sunday. Holidays include December 25th, July 4th, January 1st, the fourth Thursday of November, the first Monday of September, and the last Monday of May. ''This is set through the [[Work Days Scheduler]] interface, which can be found in Manage Repository under the Repository Settings.''		*Monday, Tuesday, Wednesday, Thursday and Friday are workdays. Weekends include Saturday and Sunday. Holidays include December 25th, July 4th, January 1st, the fourth Thursday of November, the first Monday of September, and the last Monday of May. ''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.		*Each Action has a duration of three work 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).		*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 2, when completed Action 2 starts and so forth.		*Action 1 starts in January 2, when completed Action 2 starts and so forth.

John Leavitt: /* Action 1 */

2014-09-30T17:26:29Z

Action 1

← Older revision		Revision as of 17:26, 30 September 2014
Line 971:		Line 971:
	==== Action 1 ====		==== Action 1 ====

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

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

John Leavitt: /* Planned Costs */

2014-09-30T17:14:32Z

Planned Costs

← Older revision		Revision as of 17:14, 30 September 2014
Line 396:		Line 396:
	\|- style="background-color:#FDE9D9" align="center" valign="bottom"		\|- style="background-color:#FDE9D9" align="center" valign="bottom"
	\| height="15" \| Employee 4		\| height="15" \| Employee 4
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 5
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 6
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 7
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 8
	\| height="15" \| Employee		\| height="15" \| Employee
	\| align="right" \| 8		\| align="right" \| 8
Line 413:		Line 433:
	\|- style="background-color:#DCE6F1" align="center" valign="bottom"		\|- style="background-color:#DCE6F1" align="center" valign="bottom"
	\| height="15" \| CUS Team 1		\| height="15" \| CUS Team 1
	\| ~~E1 & E2~~		\| Various Assigned Employees
	\|- style="background-color:#DCE6F1" align="center" valign="bottom"		\|- style="background-color:#DCE6F1" align="center" valign="bottom"
	\| height="15" \| CUS Team 2		\| height="15" \| CUS Team 2
	\| ~~E3 & E4~~		\| Various Assigned Employees
	\|- style="background-color:#DCE6F1" align="center" valign="bottom"		\|- style="background-color:#DCE6F1" align="center" valign="bottom"
	\| height="15" \| CUS All		\| height="15" \| CUS All

John Leavitt: /* Action 2 */

2014-09-30T17:10:03Z

Action 2

Show changes

← Older revision		Revision as of 17:14, 30 September 2014
Line 396:		Line 396:
	\|- style="background-color:#FDE9D9" align="center" valign="bottom"		\|- style="background-color:#FDE9D9" align="center" valign="bottom"
	\| height="15" \| Employee 4		\| height="15" \| Employee 4
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 5
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 6
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 7
			\| height="15" \| Employee
			\| align="right" \| 8
			\| align="right" \| 50
			\|- style="background-color:#FDE9D9" align="center" valign="bottom"
			\| height="15" \| Employee 8
	\| height="15" \| Employee		\| height="15" \| Employee
	\| align="right" \| 8		\| align="right" \| 8
Line 413:		Line 433:
	\|- style="background-color:#DCE6F1" align="center" valign="bottom"		\|- style="background-color:#DCE6F1" align="center" valign="bottom"
	\| height="15" \| CUS Team 1		\| height="15" \| CUS Team 1
	\| ~~E1 & E2~~		\| Various Assigned Employees
	\|- style="background-color:#DCE6F1" align="center" valign="bottom"		\|- style="background-color:#DCE6F1" align="center" valign="bottom"
	\| height="15" \| CUS Team 2		\| height="15" \| CUS Team 2
	\| ~~E3 & E4~~		\| Various Assigned Employees
	\|- style="background-color:#DCE6F1" align="center" valign="bottom"		\|- style="background-color:#DCE6F1" align="center" valign="bottom"
	\| height="15" \| CUS All		\| height="15" \| CUS All