Understanding Project Views and Snapshots for OnePager Pro for Version 6.0

From OnePager Documentation
Jump to: navigation, search

About Project Views and Snapshots

OnePager project views and snapshots let you create schedule graphs for specific audiences and show them how the project is changing over time. Each project view is a subset of the tasks in a Microsoft Project source plan that you have specified with a Flag field. For each project view, 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 project view 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 Project source plan (Project A), project views created from that Microsoft Project source plan using different Flag settings, and snapshots is shown below:

P52-4 1-(1)-05292015.png

Using a Single Microsoft Project Source Plan throughout a Project Period

The discussion which follows, 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, but saved using the same Microsoft Project 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 Project source plan from which three project views were created using different flag fields, Flag20 for executive views, Flag10 for project team view, and Flag5 for customer views. Further, for the Flag20 project view, there exist three snapshots taken from the Microsoft Project source plan on 6/1/2015, 7/1/2015, and 8/2/2015. Each snapshot represents the project view (under the control of Flag20 in this case) at each of these three dates during the course of the project. The same dates were used to create snapshots, in the example, for all three project views 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 will retain them, make them available for subsequent viewing, and allow updates as needed.

The following statements summarize project views and snapshots to assist you in understanding how OnePager supports this project management scheduling, control, and reporting scenario:

1) A project view is a set of tasks and milestones for an intended audience.

2) Usually a project view is associated with a specific flag or number field in a specifically named Microsoft Project source plan.

3) The project view also saves the task names, text positions, 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.

4) Making and updating project views is the main thing that OnePager users usually do!

5) A snapshot is a how the tasks and milestones in a project view look on a specific snapshot date (a.k.a. status date or version date).

6) 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.

7) 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.

Using Multiple Microsoft Project 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, project views 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 Microsoft Project source plan Project A-6/1/2015 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 project views. In the first launch on 6/1/2015, the snapshot dates will be set to 6/1/2015.

3) On the next update of the Microsoft Project source plan, save the update source plan as Project A-7/1/2015.

4) Launch OnePager in UPDATE existing Project View mode selecting the appropriate project view name. Set the snapshot date for the date of the snapshot (e.g., 7/1/2015) and create the snapshot. OnePager will store the snapshot for 7/1/2015 with the named project view. Repeat this process for each of the two remaining Flag field instances.

5) After three iterations, there will be three project views and nine synchronized snapshots available for use in presentations. There will be three corresponding Microsoft Project source plans for the status dates, 6/1/2015 through 8/2/2015.

P52-4 1-(2)-05292015.png

The mechanics for establishing and performing either of these two status maintenance scenarios are included at Basic Workflows (Portal) and Creating Various Multi-Project Views with OnePager Pro and Express (Portal) .