Difference between revisions of "Understanding Charts and Snapshots for OnePager for Version 7.1"

From OnePager Documentation
Jump to: navigation, search
(→‎Using Multiple Microsoft Excel Source Plans throughout a Project Period)
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
==Introduction==
+
==Overview==
  
−
This article has two major sections below.  The first major section is for [[Understanding Charts and Snapshots for OnePager for Version 7.1 #About Charts and Snapshots for OnePager Pro | About Charts and Snapshots for OnePager Pro]] <!--4.1.1.1-71--> and the second major section is for [[Understanding Charts and Snapshots for OnePager for Version 7.1 #About Charts and Snapshots for OnePager Express | About Charts and Snapshots for OnePager Express]] <!--4.0.1.2-71-->.  Please use these links to navigate to the appropriate section based on how you are using OnePager.
+
This article is meant to clarify how '''snapshots''' apply to OnePager charts.  Two cases are explained.  The first is where a single '''source plan''' is used to represent changes through the project which updated to the single '''source plan''' file. The second case is where multiple '''source plans''' are produced for each update of the project as it proceeds through time toward completion.
  
−
==About Charts and Snapshots for OnePager Pro==
+
The concepts described and used in this article apply equally to OnePager Pro, OnePager Express and OnePager Bundle.
  
−
OnePager charts and snapshots let you create schedule '''graphs''' for specific audiences and show them how the project is changing over time. Each chart is a subset of the tasks in a Microsoft Project '''source plan''' that you specified with a '''Flag''' field.  
+
==About Charts and Snapshots for OnePager==
 +
 
 +
OnePager charts and snapshots let you create schedule '''charts''' for specific audiences and show them how the project is changing over time. Each chart is a subset of the tasks in a '''source plan''' (e.g., Microsoft Project, Microsoft Excel, Smartsheet, or Oracle Primavera P6) that you specified with a '''Flag''' field.  
  
 
For each chart, you can import different versions of its schedule to keep track of how those tasks and milestones change over time. You can store each '''version''' of the schedule as a separate '''snapshot''' and give it a unique '''snapshot date''' in the past, present, or future. Each chart '''saves''' your presentation '''colors, row and swimlane assignments, font sizes, titles, and legends''' so that you don't need to '''re-edit''' the graphics every time the project changes.  
 
For each chart, you can import different versions of its schedule to keep track of how those tasks and milestones change over time. You can store each '''version''' of the schedule as a separate '''snapshot''' and give it a unique '''snapshot date''' in the past, present, or future. Each chart '''saves''' your presentation '''colors, row and swimlane assignments, font sizes, titles, and legends''' so that you don't need to '''re-edit''' the graphics every time the project changes.  
  
−
A simple relationship between a Microsoft Project '''source plan''' (Project A), charts created from that Microsoft Project '''source plan''' using different '''Flag''' settings, and '''snapshots''' is shown below:
+
A simple relationship between a '''source plan''' (Project A), charts created from that Microsoft Project '''source plan''', for example, using different '''Flag''' settings, and '''snapshots''' is shown below:
  
−
<center>[[File:P70-4_0_1_1-(1A)-04292020.png]]</center>
+
<!--<center>[[File:P70-4_0_1_1-(1A)-04292020.png]]</center>-->
 
<!--<center>P70-4_0_1_1-(1A)-04292020.png</center>-->
 
<!--<center>P70-4_0_1_1-(1A)-04292020.png</center>-->
 +
<center>[[File:P71-4_0_1_1-71-(1A-1)-11012021.png]]</center>
 +
<!--<center>P71-4_0_1_1-71-(1A-1)-11012021.png</center>-->
  
−
===Using a Single Microsoft Project Source Plan throughout a Project Period===
+
===Using a Single Source Plan throughout a Project Period===
  
−
The following discussion, based on the figure above, assumes that you have one Microsoft Project '''source plan''', with a single plan name (Project A), that is used to manage the project. This one Microsoft Project '''source plan''' is updated periodically, say, from week to week, and '''re-saved''' using the same Microsoft Project '''source plan''' name (Project A) from the beginning to the project's end. This being the first example scenario, the figure above shows the single Microsoft Project '''source plan''' from which three charts were created using different '''Flag''' fields, '''Flag20''' for executive views, '''Flag10''' for project team view, and '''Flag5''' for customer views.  
+
The following discussion, based on the figure above, assumes that you have one '''source plan''', with a single plan name (Project A), that is used to manage the project. This one '''source plan''' is updated periodically, say, from week to week, and '''re-saved''' using the same '''source plan''' name (Project A) from the beginning to the project's end. This being the first example scenario, the figure above shows the single '''source plan''' from which three charts were created using different '''Flag''' fields, '''Flag20''' for executive views, '''Flag10''' for project team view, and '''Flag5''' for customer views.  
  
−
Further, for the '''Flag20''' chart, there exist three '''snapshots''' taken from the Microsoft Project '''source plan''' on 6/1/2018, 7/1/2018, and 8/2/2018. Each '''snapshot''' represents the chart (under the control of '''Flag20''' in this case) at each of these three dates during the course of the project. The same dates or different dates are used to create '''snapshots''', in the example, for all three charts associated with Project A. This doesn’t need to be the case because '''snapshots''' can be taken at any time for any '''Flag''' field available and OnePager remembers them, makes them available for subsequent viewing, and allows updates as needed.
+
Further, for the '''Flag20''' chart, there exist three '''snapshots''' taken from the '''source plan''' on '''June 1st''', '''July 1st''', and '''August 1st'''. Each '''snapshot''' represents the chart (under the control of '''Flag20''' in this case) at each of these three dates during the course of the project. The same dates or different dates are used to create '''snapshots''', in the example, for all three charts associated with Project A. This doesn’t need to be the case because '''snapshots''' can be taken at any time for any '''Flag''' field available and OnePager remembers them, makes them available for subsequent viewing, and allows updates as needed.
  
−
A chart is a set of task bars and milestone symbols for an intended audience. Usually a chart is associated with a specific '''Flag''' or '''Number''' field in a specifically named Microsoft Project '''source plan'''. The chart also '''saves''' the '''task bar names, task bar label positions, and row and swimlane assignments, plus the title, legend, header/footer elements, and background colors'''.  This means you never have to re-enter this graphical information when dates change. Making and updating charts is the primary activity that OnePager users do!
+
A chart is a set of task bars and milestone symbols for an intended audience. Usually a chart is associated with a specific '''Flag''' or '''Number''' field in a specifically named '''source plan'''. The chart also '''saves''' the '''task bar names, task bar label positions, and row and swimlane assignments, plus the title, legend, header/footer elements, and background colors'''.  This means you never have to re-enter this graphical information when dates change. Making and updating charts is the primary activity that OnePager users do!
  
−
A '''snapshot''' is a how the tasks and milestones in a chart look as task bars and milestone symbols on a specific '''snapshot date''' (a.k.a. '''status date''' or '''version date'''). When you '''import''' updated schedules from a Microsoft Project '''source plan''', you must specify a unique '''snapshot date''' for the '''imported''' data unless you want to replace the data for an existing '''snapshot'''. What changes '''snapshot''' to '''snapshot''' depends on what changed in the Microsoft Project '''source plan'''.  Typically '''snapshots''' vary because of changes to '''start''' and '''finish dates''', '''baseline start''' and '''finish dates''', '''percent complete''' and '''milestone completions'''.
+
A '''snapshot''' is a how the task bars and milestone symbols in a chart look as task bars and milestone symbols on a specific '''snapshot date''' (a.k.a. '''status date''' or '''version date'''). When you '''import''' updated schedules from a '''source plan''', you must specify a unique '''snapshot date''' for the '''imported''' data unless you want to replace the data for an existing '''snapshot'''. What changes '''snapshot''' to '''snapshot''' depends on what changed in the '''source plan'''.  Typically '''snapshots''' vary because of changes to '''start''' and '''finish dates''', '''baseline start''' and '''finish dates''', '''percent complete''' and '''milestone completions'''.
  
−
===Using Multiple Microsoft Project Source Plans throughout a Project Period===
+
===Using Multiple Source Plans throughout a Project Period===
  
−
Another typical project schedule '''source plan''' management scenario with Microsoft Project is to create a Microsoft Project '''source plan''' at the beginning of a project and '''save''' the updated '''source plan''' with a unique '''source plan name''' after each update/status recording period. Under this scenario, charts and '''snapshots''' can still be created and maintained as with the first scenario above.
+
Another typical project schedule '''source plan''' management scenario is to create a '''source plan''' at the beginning of a project and '''save''' the updated '''source plan''' with a unique '''source plan name''' after each update/status recording period. Under this scenario, charts and '''snapshots''' can still be created and maintained as with the first scenario above.
  
 
The following steps correspond with the example in the figure below:
 
The following steps correspond with the example in the figure below:
  
−
:1) Create Microsoft Project '''source plan''' Project A-6/1/2018 with populated '''Flag''' fields '''Flag20''', '''Flag10''' and '''Flag5''' and '''save''' it.
+
:1) Create the '''source plan''' named '''Project A-June 1st''' with populated '''Flag''' fields '''Flag20''', '''Flag10''' and '''Flag5''' and '''save''' it.
  
−
:2) Launch OnePager using each of the '''Flag''' fields to control the task selection and ''''save''' the corresponding charts. In the first launch on 6/1/2018, the '''snapshot dates''' is set to 6/1/2018.
+
:2) Launch OnePager using each of the '''Flag''' fields to control the task selection and ''''save''' the corresponding charts. In the first launch on '''June 1st''', the '''snapshot dates''' is set to '''June 1st'''.
  
−
:3) On the next update of the Microsoft Project '''source plan''', save the update '''source plan''' as '''Project A-7/20/2018'''.
+
:3) On the next update of the '''source plan''', save the update '''source plan''' as '''Project A-July 20th'''.
  
−
:4) Launch OnePager in '''UPDATE existing Chart''' mode selecting the appropriate chart name. Set the '''snapshot date''' for the date of the snapshot (e.g., 7/20/2018) and create the '''snapshot'''.  
+
:4) Launch OnePager in '''UPDATE existing Chart''' mode selecting the appropriate chart name. Set the '''snapshot date''' for the date of the snapshot (e.g., '''July 20th''') and create the '''snapshot'''.  
  
−
:5) OnePager stores the '''snapshot''' for 7/1/2018 with the named chart.  
+
:5) OnePager stores the '''snapshot''' for '''July 20th''' with the named chart.  
  
 
:6) Repeat this process for each of the two remaining '''Flag''' field instances.
 
:6) Repeat this process for each of the two remaining '''Flag''' field instances.
  
−
After three iterations, there are three charts and nine synchronized '''snapshots''' available for use in presentations. There are three corresponding Microsoft Project '''source plans''' for the status dates, 6/1/2018 through 8/2/2018.
+
After three iterations, there are three charts and nine synchronized '''snapshots''' available for use in presentations. There are three corresponding '''source plans''' for the status dates, 6/1/2018 through 8/2/2018.
  
−
<center>[[File:P70-4_0_1_1-(2)-04292020.png]]</center>
+
<!--<center>[[File:P70-4_0_1_1-(2)-04292020.png]]</center>-->
 
<!--<center>P70-4_0_1_1-(2)-04292020.png</center>-->
 
<!--<center>P70-4_0_1_1-(2)-04292020.png</center>-->
 +
<center>[[File:P71-4_0_1_1-71-(2-1)-11012021.png]]</center>
 +
<!--<center>P71-4_0_1_1-71-(2-1)-11012021.png</center>-->
  
−
The mechanics for establishing and performing either of these two status maintenance scenarios are included at [[Basic Workflows for Version 7.0 (Portal) | Basic Workflows (Portal)]] 7.0.1-70 and [[Creating Various Multi-Charts with OnePager Pro and Express for Version 7.0 (Portal) | Creating Various Multi-Charts with OnePager Pro and Express (Portal)]]. 8.0.1-70
+
==Related Links==
−
 
+
−
==About Charts and Snapshots for OnePager Express==
+
−
 
+
−
OnePager charts and '''snapshots''' let you create schedule '''graphs''' for specific audiences and show them how the project is changing over time. Each chart is a subset of the tasks in a Microsoft Excel '''source plan''' that you specified with a '''Flag''' field.  For each chart, you can import different versions of its schedule to keep track of how those tasks and milestones change over time. You can store each '''version''' of the schedule as a separate '''snapshot''' and give it a unique '''snapshot date''' in the past, present, or future.  Each chart '''saves''' your presentation '''colors, row and swimlane assignments, font sizes, titles, and legends''' so that you do not have to '''re-edit''' the graphics every time the project changes.
+
−
 
+
−
A simple relationship between a Microsoft Excel '''source plan''' (Project A), charts created from that Microsoft Excel '''source plan''' using different '''Flag''' settings, and snapshots is shown in the figure below:
+
−
 
+
−
<center>[[File:X70-4_0_1_2-(1)-70-09082020.png]]</center>
+
−
<!--<center>X70-4_0_1_2-(1)-70-09082020.png</center>-->
+
−
 
+
−
===Using a Single Microsoft Excel Plan throughout a Project Period===
+
−
 
+
−
The following discussion, based on the figure above, assumes that you have one Microsoft Excel '''source plan''', with a single plan name (Project A), that is used to manage the project. This one Microsoft Excel '''source plan''' is updated periodically, say, from week to week, but saved using the same Microsoft Excel '''source plan''' name (Project A) from the beginning of the project to the end. This being the first example scenario, the figure above shows the single Microsoft Excel '''source plan''' from which three charts were created using different '''Flag''' fields, '''ShowIT1''' for executive views, '''ShowIT2''' for project team view, and '''ShowIT3''' for customer views. 
+
−
 
+
−
Further, for the '''ShowIT1''' chart there exist three '''snapshots''' taken from the Microsoft Excel '''source plan''' on 6/1/18, 7/1/18, and 8/2/18, respectively.  Each '''snapshot''' represents the chart (under the control of '''ShowIT1''' in this case) at each of these three dates during the course of the project.  The same dates or different dates are used to create '''snapshots''', in the example, for all three charts associated with Project A.  This doesn’t need to be the case because '''snapshots''' can be taken at any time for any '''Flag''' field available and OnePager retains them, make them available for subsequent viewing, and allow updates as needed.
+
−
 
+
−
A chart is a set of tasks and milestones for an intended audience.  Usually a chart is associated with a specific '''Flag''' field in a specifically named Microsoft Excel '''source plan'''.  The chart also saves the '''colors, text positions, font sizes, and row and swimlane assignments of the tasks/milestones, plus the title, legend, header/footer elements, and background colors'''.  This means you never have to re-enter this graphical information when dates change in the project.  Making and updating charts is the primary activity that you want OnePager to do!
+
−
 
+
−
A '''snapshot''' is a how the tasks and milestones in a chart looked on a specific '''snapshot date''' (a.k.a. '''status date''' or '''version date''').  When you import updated schedules from a Microsoft Excel '''source plan''', you must specify a unique '''snapshot date''' for the imported data unless you want to replace the data for an existing '''snapshot'''.  What changes '''snapshot''' to '''snapshot''' depends on what changed in the Microsoft Excel '''source plan'''.  Typically '''snapshots''' vary because of changes to '''start''' and '''finish dates''', '''baseline start''' and '''finish dates''', '''percent complete''' and '''milestone completions'''.
+
−
 
+
−
===Using Multiple Microsoft Excel Source Plans throughout a Project Period===
+
−
 
+
−
Another typical project schedule '''source plan''' management scenario with Microsoft Excel is to create a Microsoft Excel '''source plan''' at the beginning of a project and save the updated '''source plan''' with a unique file name after each update/status recording period.  Under this scenario charts and '''snapshots''' can still be created and maintained as with the first scenario discussed earlier. The following steps correspond with the example in the figure below:
+
−
 
+
−
:1) Create Microsoft Excel '''source plan''' Project A-6/1/2018 with populated '''Flag''' fields '''ShowIT1''', '''ShowIT2''', '''ShowIT2''', and save it.
+
−
 
+
−
:2) Launch OnePager using each of the '''Flag''' fields to control the task selection and save the corresponding charts.  In the first launch on 6/1/2018 the '''snapshot dates''' is set to 6/1/2018.
+
−
 
+
−
:3) On the next update of the Microsoft Excel '''source plan''', save the updated plan as '''Project A-7/20/2018'''.
+
−
 
+
−
:4) Launch OnePager in '''UPDATE existing Chart''' mode selecting the appropriate chart name. 
+
−
 
+
−
:5) Set the '''snapshot date''' for the date of the snapshot (e.g., 7/20/2018) and create the '''snapshot'''. 
+
−
 
+
−
:6) OnePager stores the '''snapshot''' for 7/20/2018 with the named chart. 
+
−
 
+
−
:7) Repeat this process for each of the two remaining '''Flag''' field instances.
+
  
−
After three iterations, there are three charts and nine synchronized '''snapshots''' available for use in presentations. There are three corresponding Microsoft Excel '''source plans''' for the status dates, 6/1/2018 through 8/2/2018.
+
[[Basic Workflows for Version 7.1 (Portal) | Basic Workflows (Portal)]] <!--7.0.1-71-->
  
−
<center>[[File:X70-4_0_1_2-(2)-70-09082020.png]]</center>
+
[[Creating Various Multi-Project Charts with OnePager for Version 7.1 (Portal) | Creating Various Multi-Project Charts with OnePager (Portal)]] <!--8.0.1-71-->
−
<!--<center>X70-4_0_1_2-(2)-70-09082020.png</center>-->
+
  
−
Unlike Microsoft Project, Microsoft Excel does not create unique '''Task IDs'''. Rather it is up to you to create a '''Task ID''' column and populate it with unique '''Task ID’s''' so that OnePager Express ('''OPX''') can uniquely identify these rows in future updates. When creating a chart from multiple Microsoft Excel '''source plans OPX''' relies on these unique '''Task ID''' fields that you provide.  '''Task ID''' field contents must be '''unique''' across the multiple Microsoft Excel '''source plans''' you expect to incorporate into a single chart.  If the multiple Microsoft Excel '''source plans''' do not contain a '''Task ID''' field or the contents are '''not unique''', the update process in '''OPX''' can lead to unexpected results when you insert or remove rows from any of the Microsoft Excel '''source plans''' involved.  
+
[[Managing Chart Data for Version 7.1 | Managing Chart Data (Portal)]] <!--23.0.1-71-->
  
−
The mechanics for establishing and performing either of these two status maintenance scenarios are included at [[Basic Workflows for Version 7.0 (Portal) | Basic Workflows (Portal)]] 7.0.1-70 and [[Creating Various Multi-Charts with OnePager Pro and Express for Version 7.0 (Portal) | Creating Various Multi-Charts with OnePager Pro and Express (Portal)]]. 8.0.1-70
+
[[Snapshots (Versioning) for Version 7.1 | Snapshots (Versioning)]] <!--23.4.1-71-->
  
−
(4.0.1.1-71, 4.0.1.2-71)
+
(4.0.1.1-71)
  
 
[[Category:Version 7.1]]
 
[[Category:Version 7.1]]
−
[[Category:Getting Started with Version 7.1]]
 
−
[[Category:Core Concepts]]
 
−
[[Category:Charts]]
 
 
[[Category:Snapshots]]
 
[[Category:Snapshots]]
−
[[Category:Importing]]
 
 
[[Category:OnePager Pro]]
 
[[Category:OnePager Pro]]
 
[[Category:OnePager Express]]
 
[[Category:OnePager Express]]
 +
[[Category:OnePager Bundle]]

Latest revision as of 17:16, 26 April 2022

Overview

This article is meant to clarify how snapshots apply to OnePager charts. Two cases are explained. The first is where a single source plan is used to represent changes through the project which updated to the single source plan file. The second case is where multiple source plans are produced for each update of the project as it proceeds through time toward completion.

The concepts described and used in this article apply equally to OnePager Pro, OnePager Express and OnePager Bundle.

About Charts and Snapshots for OnePager

OnePager charts and snapshots let you create schedule charts for specific audiences and show them how the project is changing over time. Each chart is a subset of the tasks in a source plan (e.g., Microsoft Project, Microsoft Excel, Smartsheet, or Oracle Primavera P6) that you specified with a Flag field.

For each chart, you can import different versions of its schedule to keep track of how those tasks and milestones change over time. You can store each version of the schedule as a separate snapshot and give it a unique snapshot date in the past, present, or future. Each chart saves your presentation colors, row and swimlane assignments, font sizes, titles, and legends so that you don't need to re-edit the graphics every time the project changes.

A simple relationship between a source plan (Project A), charts created from that Microsoft Project source plan, for example, using different Flag settings, and snapshots is shown below:

P71-4 0 1 1-71-(1A-1)-11012021.png

Using a Single Source Plan throughout a Project Period

The following discussion, based on the figure above, assumes that you have one source plan, with a single plan name (Project A), that is used to manage the project. This one source plan is updated periodically, say, from week to week, and re-saved using the same source plan name (Project A) from the beginning to the project's end. This being the first example scenario, the figure above shows the single source plan from which three charts were created using different Flag fields, Flag20 for executive views, Flag10 for project team view, and Flag5 for customer views.

Further, for the Flag20 chart, there exist three snapshots taken from the source plan on June 1st, July 1st, and August 1st. Each snapshot represents the chart (under the control of Flag20 in this case) at each of these three dates during the course of the project. The same dates or different dates are used to create snapshots, in the example, for all three charts associated with Project A. This doesn’t need to be the case because snapshots can be taken at any time for any Flag field available and OnePager remembers them, makes them available for subsequent viewing, and allows updates as needed.

A chart is a set of task bars and milestone symbols for an intended audience. Usually a chart is associated with a specific Flag or Number field in a specifically named source plan. The chart also saves the task bar names, task bar label positions, and row and swimlane assignments, plus the title, legend, header/footer elements, and background colors. This means you never have to re-enter this graphical information when dates change. Making and updating charts is the primary activity that OnePager users do!

A snapshot is a how the task bars and milestone symbols in a chart look as task bars and milestone symbols on a specific snapshot date (a.k.a. status date or version date). When you import updated schedules from a source plan, you must specify a unique snapshot date for the imported data unless you want to replace the data for an existing snapshot. What changes snapshot to snapshot depends on what changed in the source plan. Typically snapshots vary because of changes to start and finish dates, baseline start and finish dates, percent complete and milestone completions.

Using Multiple Source Plans throughout a Project Period

Another typical project schedule source plan management scenario is to create a source plan at the beginning of a project and save the updated source plan with a unique source plan name after each update/status recording period. Under this scenario, charts and snapshots can still be created and maintained as with the first scenario above.

The following steps correspond with the example in the figure below:

1) Create the source plan named Project A-June 1st with populated Flag fields Flag20, Flag10 and Flag5 and save it.
2) Launch OnePager using each of the Flag fields to control the task selection and 'save the corresponding charts. In the first launch on June 1st, the snapshot dates is set to June 1st.
3) On the next update of the source plan, save the update source plan as Project A-July 20th.
4) Launch OnePager in UPDATE existing Chart mode selecting the appropriate chart name. Set the snapshot date for the date of the snapshot (e.g., July 20th) and create the snapshot.
5) OnePager stores the snapshot for July 20th with the named chart.
6) Repeat this process for each of the two remaining Flag field instances.

After three iterations, there are three charts and nine synchronized snapshots available for use in presentations. There are three corresponding source plans for the status dates, 6/1/2018 through 8/2/2018.

P71-4 0 1 1-71-(2-1)-11012021.png

Related Links

Basic Workflows (Portal)

Creating Various Multi-Project Charts with OnePager (Portal)

Managing Chart Data (Portal)

Snapshots (Versioning)

(4.0.1.1-71)

Retrieved from "https://wiki.onepager.com/wiki/index.php?title=Understanding_Charts_and_Snapshots_for_OnePager_for_Version_7.1&oldid=44918"