Using Rows and Swimlanes for OnePager Version 6.1

From OnePager Documentation
Jump to: navigation, search

About Rows and Swimlanes

This article introduces you to OnePager’s rows and swimlane management features. To help illustrate this approach we will repeat the Rows & Swimlanes tab from the Project-View Properties (PVP) form below:

P60-4 5-60-(1BB)-03082017.png

As the Rows/Swimlanes tab above illustrates, there is a step wise approach to constructing an informative and useful Gantt chart.

The general philosophy is for you to create or modify the project view by making the following determinations:

(1) Determine how tasks will be collected into rows.
(2) Determine how rows will be grouped into swimlanes keeping in mind that steps (1) and (2) are related.
(3) Determine how row will be ordered in swimlanes and how swimlane will be ordered.
(4) Determine how many additional text columns are needed.
(5) Determine how row and swimlane gridlines will be labeled.
(6) Determine how row and swimlane borders will be formatted.

The discussion that follows is divided into six sub-sections, one each for the decision steps listed above.

Step 1 – Collect Tasks into Rows

Collecting tasks into rows is the first step, although the most common situation is to make one task per row. Once completed, you have additional controls over row and swimlane manipulation with respect to grouping, ordering, labeling, and border formatting. Tasks may be collected into rows by various techniques under your control:

1) Make one task per row As the button name suggests, OnePager will place each task in an individual row. Note that no collection occurs in this case. When this command is selected, you have the following optional choice to make:

(1) Checking the Keep row count between X and Y checkbox. When this checkbox is checked, OnePager will take the total task count and assign them to rows such that the resulting row count is between your stated minimum (X) and maximum (Y).
(2) Unchecking the Keep row count between X and Y checkbox. When this checkbox is unchecked, OnePager will create as many rows as there are tasks/milestones imported from the Microsoft Project or Microsoft Excel source plan.

2) Collect task into rows by source column name. OnePager will examine the selected Microsoft Project or Microsoft Excel source plan fields for each encountered task and collect them into as many unique rows as there are unique terms. When this command is selected, you have the following choices to select from:

(1) Collect tasks automatically. OnePager will put tasks into rows such that there is no overlapping of task in the row with respect to start and finish dates.
(2) Collect up to ____designated number of tasks per row. OnePager will collect the imported task from your Microsoft Project or Microsoft Excel source plan into rows such that the number of task per row is less than or equal to the designated number of tasks per row. Collected tasks may overlap within the created rows.
(3) Make user designated number or rows. OnePager will create your designated number of rows and collect the imported tasks into that number of rows only. Collected tasks may overlap within the created rows and are not collected by means of a Microsoft Project or Microsoft Excel source plan field.

3) After task collection into rows is determined, you can determine how rows should be grouped into swimlanes. If the control is not checked, OnePager will ignore the grouping step and will make one swimlane containing all rows.

Step 2 – Group Rows into Swimlanes

1) If you check the checkbox specifying that rows are to be grouped into swimlanes, OnePager will use the designated Microsoft Project or Microsoft Excel source plan field to control row grouping.

2) Since rows may contain multiple tasks, each with unique data from the Microsoft Project or Microsoft Excel source plan field' controlling grouping, OnePager must first determine the number of swimlanes and then place the rows in their proper swimlane.

3) Please consider the following example.

4) OnePager first looks at all the data from the Microsoft Project or Microsoft Excel source plan and determines the number of unique values present which determine the number of swimlanes to be generated. You do not have control explicitly over the number of swimlanes that can be generated.

a) If there is more than one task in a row and the tasks have different data, OnePager will use the majority rule to compute the value for each row.
b) For example, suppose your designated Microsoft Project or Microsoft Excel source plan field contains the values Red and Green. Suppose further that:
  • Row1 contains two Red tasks and one Green task,
  • Row2 contains one Red task and two Green tasks,
  • Row3 contains one Red task
  • Row4 contains two Red tasks.
c) In this situation, two swimlanes will be generated. One of these is the Red swimlane and the other is the Green swimlane. Row2 belongs to the Green swimlane and the other three rows belongs to the Red swimlane.

5) At the completion of this step, OnePager will perform the ordering of rows within swimlanes and ordering swimlanes as described in the next sub-section.

Step 3 – Order Swimlanes and/or Order Rows in Swimlanes

1) Order Rows in Swimlanes. You have two options when controlling how rows will be ordered within swimlanes:

(1) Order rows like Microsoft Project. Selecting this ordering technique uses the sequence from top to bottom provided by the Microsoft Project or Microsoft Excel source plan. If several tasks are collected into the same row, OnePager will first sort them into their natural Microsoft Project or Microsoft Excel order and then will choose the first task in the list to represent the entire row if ascending order is your choice. If you choose descending order, OnePager will use the last task in the list.
(2) Order rows by user selected Microsoft Project source plan field. You may choose to order rows under the control of data in a designated Microsoft Project or Microsoft Excel source plan field and further choose either ascending or descending order. It should be pointed out that your Microsoft Project or Microsoft Excel source plan field used to order rows may be the same as your Microsoft Project or Microsoft Excel source plan field used to collect tasks into rows or a different Microsoft Project or Microsoft Excel source plan field. As discussed just above, OnePager chooses the first (last) value from list of values within each row when rows consist of tasks with differing data.

2) Order Swimlanes. At this point, tasks are assigned to rows and rows to swimlanes. OnePager now uses the data from your Microsoft Project or Microsoft Excel source plan field to order the swimlane within the project view. You have two options when controlling how swimlanes will be ordered:

(1) Order swimlanes like Microsoft Project. Selecting this ordering technique establishes the sequence from top to bottom provided by your Microsoft Project or Microsoft Excel source plan. Since the various tasks comprising a swimlane will have different natural occurrence orders, OnePager first will perform the analysis at the task level within each swimlane to determine the swimlane ordering value to assign to the swimlane. In other words, OnePager will first sort the set of tasks comprising all the rows in the swimlane into their natural order and then will choose the first task in the list to represent the entire swimlane. (If you specified descending order, OnePager will choose the last task in the list to represent the entire swimlane.)
(2) Order swimlanes by Microsoft Project source plan field. You may choose to order swimlanes under the control of data in a specified Microsoft Project or Microsoft Excel source plan field. As discussed in the item above, OnePager chooses the first (last) value from the list of values with each swimlane when swimlanes consist of rows that consist of tasks with differing data in the designated Sort swimlanes by field.

3) At the completion of the ordering rows and swimlanes steps, you may choose to show text columns and swimlane labels as described below.

Step 4 – Label Rows and Swimlanes

1) Labeling Rows - General Considerations If you check the Show text columns checkbox, you must designate a Microsoft Project or Microsoft Excel source plan field to be used for OnePager to select the appropriate additional text columns.

a) Since tasks may be collected into rows using your designated Microsoft Project or Microsoft Excel source plan field, there is a need to resolve conflicts when rows consist of tasks with differing data in the designated Collect tasks into rows by field.
b) If there is more than one task in a row and these tasks have different values from your designated Microsoft Project or Microsoft Excel source plan field, OnePager will display the label that occurs most frequently or the label that comes from the first task in the natural order of your Microsoft Project or Microsoft Excel source plan for tasks with the same frequency of occurrence of label data.

2) Labeling Multiple Rows with the Custom Text Columns Form. OnePager Pro and Express version 6.0 allows the definition of up to five additional text columns. These are defined by clicking the Text Column Properties... button shown above when the Show text columns checkbox is checked. When you do this, the Custom Text Columns form appears as shown below:

P60-4 5-60-(2)-11092016.png
a) This new form allows you to define up to five additional text columns which will be displayed to the right of the project view's outer left border if Swimlanes are not displayed or to the immediate right of the Swimlanes label showing. The additional text columns are defined from left to right.
b) How to use the Custom Text Columns form is described in the article at: Creating and Editing Rows and Swimlanes (Portal) 12.0.1-61.
c) The project view example below shows a project view with a swimlane and three text columns displayed as an example:
P61-4 0 1 5-61-(3)-10252017.png

3) Labeling Swimlanes. If you check the Show swimlane labels checkbox, you must designate a Microsoft Project or Microsoft Excel source plan field to be used for OnePager to select the appropriate swimlane label.

a) Since tasks may be collected into rows using your Microsoft Project or Microsoft Excel source plan field and the rows grouped into swimlanes using another source plan field, there is a need to resolve conflicts when swimlanes consist of tasks with differing data in the designated Label swimlanes by Microsoft Project or Microsoft Excel source plan field.
b) If there is more than one task in a swimlane and these tasks have different values from your designated source plan field, OnePager will display the swimlane label that occurs most frequently or the label that comes from the first task in the natural order of your Microsoft Project or Microsoft Excel source plan for tasks with the same frequency of occurrence of label data.

4) Finally, you may cause row and swimlane labels to be repeated on all output pages if the multi-page feature is being used.

5) After completing the selection of optional labels for rows and swimlanes, you have the further option to control format of gridlines that OnePager will place between rows and swimlanes as detailed in the discussion of Step 5 below.

Step 5 – Format Borders and Backgrounds

1) As the final step in preparing your rows and swimlanes presentation, you may choose to turn on the row and swimlane borders feature.

2) This feature allows you to exercise control of borders around rows, around swimlanes, the inner frame of the project view, and the outer frame of the project view as detailed in the next sub-section.

Format Borders

1) When the Format Borders button is clicked, a form consisting of five tabs is presented that allows you to control gridline color, width, and dash type.

2) The tabs are shown below and apply to:

(1) Swimlane borders
(2) Row borders
(3) Time cursor borders
(4) Inter frame borders
(5) Outer frame borders

3) Border commands for color, width, and dash type are as consistent as possible with those found in Microsoft Excel.

4) Swimlane borders, Row borders, Time cursors, Inner Frame and Outer Frame Common Controls. By clicking the Format borders… button in the Project-View Properties (PVP) form's Rows and Swimlanes tab you can configure borders for rows, swimlanes, and the other elements as shown below.

a) Line color This dropdown list provides a color palette from which the line color for the border can be selected.
b) Line width The line width for all borders is in units of font points.
c) Dash type There are five (5) line or dash types available for borders.
(1) Solid
(2) Dot
(3) Dash
(4) Dash dot
(5) Dash dot dot
d) Border type: There are three border types available:
(1) Above
(2) Below
(3) Both
e) The four controls mentioned above are consistently used for three (3) of the five borders tabs.
Swimlane Borders Tab
P61-4 0 1 5-61-(4)-10252017.png
Row Borders Tab
P61-4 0 1 5-61-(5)-10252017.png
Time Cursor Tab
P61-4 0 1 5-61-(6)-10252017.png
Inner Frame Tab
P61-4 0 1 5-61-(7)-10252017.png
Outer Frame Tab
P61-4 0 1 5-61-(8)-10252017.png

5) Vertical Gridlines Color. The Inner frame tab has an additional control for the color of the vertical gridlines. Vertical gridlines are shown to place time separations on the graph. Typically vertical gridlines are used to place separation between years or other major time boundaries.

6) The Inner frame tab below shows this control.

P61-4 0 1 5-61-(9)-10252017.png

7) Example of Vertical Gridlines: The following segment of a project view illustrates the use of vertical gridlines:

P61-4 0 1 5-61-(10)-10252017.png

(4.0.1.5-61)