New User Experience: Top-Down Planning with Roadmaps

ccppmop1561
As a portfolio manager, you can create roadmaps and can adjust roadmap items to plan for the future of your business. Start your portfolio planning from the top-down with minimal details. As you gather more details, use the following layouts to refine your roadmaps:
  • Timeline:
    Quickly understand the scope of work, capacity, and budget or other metrics for fiscal planning. You can tell when certain business events occur and where the dependencies exist. Create swim lanes to organize information in a way that speaks to different audiences.
  • Board:
    View initiatives that are categorized by status, type, or other criteria. For example, you can drag-and-drop roadmap items to advance their status from
    unapproved
    to
    pending
    and then to
    approved
    .
  • Grid:
    Fill in more granular details on roadmap items for planning and execution purposes. You can sort, filter, and can configure the view to suit your needs for better data entry.
You can configure the settings (in this release,
settings
are known as
view options
) for each layout to organize the information as it makes sense to you. The configured view options persist for you or for a saved view within a roadmap.
Example
: Sid is in charge of business development. He wants to create a roadmap for the new efforts that his research teams have underway. He begins by including the investments that the business unit plans to develop in the next fiscal year that is based on the quarterly business review. Sid realizes that he has two back-to-back meetings with two different stakeholder groups: an executive steering committee and his development directors. Both groups are interested in seeing the roadmap details, but they have slightly different expectations for viewing the information. For the steering committee, Sid groups the roadmap by
Business Outcome
because that matters most to them. For the directors, Sid switches the view to group by
Team
so that they have a clear picture of the items each team is planning to develop over the next year.
2
2
HID_newux_roadmaps
Video: Clarity PPM Strategic Roadmapping
The fastest way to innovate, Clarity PPM comes with strategic roadmaps that eliminate organizational fatigue, cutting annual planning from weeks to hours. Watch this video to learn how with drag-and-drop speed you craft new ideas with your team. Then add budgets, resources and tasks as you go. Roadmaps allows to combine top-down strategic planning with bottom-up agile execution.

To play the video in full screen, click the YouTube logo at the bottom.
Roadmapping Prerequisites
To use roadmaps, verify with your administrator that the following configuration is complete in Classic PPM:
  • Create a default entity
    . See
    Create an Entity
    in Configure an Organizational Breakdown Structure.
  • Configure monthly, quarterly, and annual fiscal time period types for the default entity
    . See Set Up a Financial Entity. If any fiscal period types are not defined on the default entity, those fiscal period types are blank in the column headings in the timeline.
  • Grant users the required access rights
    . See
    CA PPM Access Rights Reference
    in the English edition of the documentation.
  • Create custom global picklists
    . Include the grouping attributes or lookup values that your organization wants to use in all roadmaps. See Create a Custom Global Picklist.
  • Configure color display mappings
    . You can customize the color grouping options available for the default global picklists. You can also assign color grouping options for your custom global picklists. See
    CA PPM Studio Objects and Attributes
    in the English edition of the documentation.
Create a Roadmap
As a portfolio manager, begin with a new roadmap and fill it with roadmap items corresponding to your business goals.
Follow these steps:
  1. In the main menu, click
    Roadmaps
    .
  2. Click
    NEW ROADMAP
    .
  3. Complete the following fields:
    • START PERIOD
      Defines the roadmap start period that is based on what fiscal annual periods you have configured for your default entity. The field shows the next fiscal annual period by default. For example, if the current date is September 15, 2019, the default fiscal period shows 2020, the next annual fiscal period. 
    • DURATION
      Defines the roadmap duration and shows one year as the default. The duration that you can select depends on the corresponding annual fiscal periods that are set up on the default entity. For example, you select 2018 as the start period and there are three annual fiscal periods (2018, 2019, and 2020) set up on the default entity. The duration options that appear include 1 Year, 2 Years, and 3 Years.
      The
      Other
      option appears if you have more than five annual periods that are defined in the future. Consider a scenario where you select 2018 as the start period and the default entity has annual fiscal periods that are defined through 2025. In such a scenario the
      Other
      option appears. When you select this option, the system allows you to enter only a number from 6 through 8. You can change the duration after creating a roadmap by clicking
      Details
      and then updating the
      Duration
      attribute.
  4. Click
    CREATE
    .
    Your new roadmap appears in the default timeline layout with a unique system-defined ID. If auto-numbering is not set up in Classic
    Clarity PPM
    , enter a unique ID for your roadmap.
  5. Add items to your roadmap in the timeline, board, or grid layout.
To delete a roadmap, from the Roadmaps list page, click the
⋮ Actions
menu next to the roadmap and click
Delete
.
Edit Roadmap Details
You can add more details to your roadmap such as
description
or
type
. You can also edit the existing details. For example, change the author from you to somebody else who can take ownership of it.
Follow these steps:
  1. In the roadmap list, click a roadmap.
  2. Click 
    Details
    . The DETAILS pane appears.
  3. Edit the roadmap details. With auto-numbering,
    ROADMAP ID
    is read-only.
  4. To close the DETAILS pane, click
    X Close
    .
Plan Roadmap Items in a Timeline
The roadmap timeline layout displays planning items in monthly, quarterly, or annual periods. The column headers for the time periods match the fiscal time period labels that are defined for the default entity in Classic
Clarity PPM
. Only the roadmap items that fall within the roadmap start and finish dates appear on the timeline. The items are further filtered based on your period type view options.
When the roadmap duration is less than three years, time period columns are quarters (for example, 2019-Q1, 2019-Q2). Roadmaps with durations greater than three years show time periods as years.
Items on the timeline can be bars, circles, or diamonds. Bars result when you enter both start date and finish date for an item. Circles result when you enter only the start date for an item. Diamonds result when you enter only the finish date for an item.
Follow these steps:
  1. From the roadmaps list, open a roadmap.
  2. Click
    Timeline
    .
  3. To add an item, click the plus icon to start edit or drawing mode.
    If you have not yet assigned a picklist value to the roadmap item, it appears in the
    None
    swim lane. After you have assigned a picklist value to all the roadmap items, the
    None
    swim lane disappears.
  4. Click and drag to draw the item on the timeline to cover the appropriate duration. Or, click in a specific time period to create a roadmap item in that location. You can add multiple roadmap items within the same row.
  5. Complete the fields in the pop-up window. See Add Roadmap Items to a Roadmap for details.
  6. Click
    Done
    .
Create Roadmap Items With No Start or No Finish Date
To create a roadmap item with no start date, draw the roadmap item and clear the start date in the
START
field. The roadmap item appears with a diamond symbol, like a milestone.
To create a roadmap item with no finish date, draw the roadmap item and clear the finish date in the
FINISH
field. The roadmap item appears with an open circle symbol.
To convert the floating item to an item with firm start and finish dates, position the item on the timeline and hover over the circle. The pointer changes to an arrow to apply dates that align with your drag-and-drop placement. You can edit the exact dates.
Display Scope for Roadmap Items in the Timeline
The roadmap items that appear in the timeline depend on whether their start and finish dates fall within the roadmap duration. Note the following behavior for roadmap items:
  • A roadmap item with a start date before the roadmap starts and a finish date after the roadmap ends does not appear in the timeline.
  • A roadmap item with a start date before the roadmap starts and a finish date before the roadmap ends appears partially in the timeline. The roadmap item displays a "
    <
    " to indicate that it is straddling the roadmap start date.
  • A roadmap item with a start date after the roadmap starts and a finish date after the roadmap ends appears partially in the timeline. The ending of the roadmap items straddles the timeline. The roadmap item displays a "
    >
    " to indicate that it is straddling the roadmap end date.
A roadmap item that is not visible in the timeline appears in the roadmap board or grid layouts.
The following image displays how roadmap items appear in the timeline based on their start and finish dates:
The following image displays how roadmap items appear in the timeline based on their start and finish dates.
Arrange Items in the Timeline
  • Select a roadmap item and drag it anywhere to change the duration or the start or end dates. A roadmap item that you create on the Board shows up at the bottom of the Timeline and you can drag it anywhere.
  • Drag and overlap a roadmap item on to another item to push the target roadmap item down to the next available row. If you create an empty row, the roadmap items below that row move up to fill in the empty row.
  • The labels for the single-date roadmap items (that is, diamonds and circles) display outside the items. Hence, overlapping of the labels might occur when you drag one item over another to push the target item down. In this case, manually drag the target roadmap item down to a new row.
  • Select from available grouping attributes to organize the roadmap items into swim lanes as appropriate for different audiences. You can create roadmap items in the swim lanes and can drag the items between the lanes. See Configure Settings for the Timeline for details.
  • Save your grouping configurations as part of the roadmap view for easy retrieval. See Personalize Roadmaps Views. The grouping configurations for a roadmap persist across all your sessions.
Add Dependencies for Roadmap Items
To define dependencies between roadmap items, add dependency lines between the roadmap items. You can add dependency lines from one roadmap item to another or to multiple roadmap items. For example, you can connect the CRM 2.0 roadmap item in the Grow the Business swim lane to the SaaS Migration roadmap item in the IT Operations swim lane.
Follow these steps:
  1. From the roadmap timeline, double-click the source roadmap item. Or, click the pencil icon that appears when you hover over the source roadmap item.
  2. In the pop-up window, select
    DEPENDENCIES
    to start dependency mode.
  3. Click the connector icon for the target roadmap items to create dependency lines from the source roadmap item.
  4. To delete a dependency line, click the X that appears next to each target roadmap item.
  5. To exit dependency mode, click the X in the blue
    EDIT DEPENDENCIES
    bar at the top of the page.
    Gray dependency lines with arrows show the relationships between roadmap items in the timeline.
  6. To hide the dependency lines, click
    View Options
    and clear the
    Show Dependencies
    check box.
In dependency mode, drag-and-drop is disabled for the roadmap items. To edit a roadmap item, double-click the item to open the Roadmap Item panel.
If there is a large distance between roadmap items, the dependency lines are truncated in the timeline. In the grid, add the Predecessors and Successors attributes from Column Panel to view all dependencies for a particular roadmap item. A maximum of 25 predecessor and 25 successor values appear for a roadmap item. Any changes you make to the dependencies in the timeline are reflected in the grid.
Configure Roadmap Timeline View Options
Configure the timeline layout to view roadmap items that are grouped in swim lanes by attribute. You can view the items by color and can map those colors back to meaningful values. You can also set the zoom level and select financial metrics that appear as badges on your roadmap items. By default, the timeline swimlane and color settings are set to
None
. Adjust the settings for your audience.
Follow these steps:
  1. Open a roadmap and click
    Timeline
    .
  2. Click
    View Options
    .
  3. In the
    View Options
    panel, configure the following settings:
    • ZOOM
      Zoom out to the left to show more time. Zoom in to the right to show fewer time periods and focus on a specific year, quarter, or month. The zoom scale varies based on the roadmap duration. If a roadmap item is out of view, use zoom to see the full roadmap.
    • PERIODS
      Select Months, Quarters, or Years. The timeline displays the roadmap items for the number of fiscal periods that are defined for the selected period type. For example, your default entity includes fiscal time periods for five years (60 months). When you select
      Months
      , the timeline displays roadmap items over 60 monthly columns. Zoom out to five years to view all 60 months.
    • SWIMLANES
      Select a picklist to group the roadmap items into horizontal swim lanes by the picklist values. For example, group roadmap items into swim lanes that are based on business outcomes for a steering committee. Group the same roadmap items by team for business development directors. Each audience can see where each roadmap item sits in their planning process. You can select from the list of default global picklists or can create a custom global picklist. You can also create a local picklist applicable only to this roadmap. See Create and Manage Local Picklists.
    • COLOR BY
      Select a picklist to add color to your roadmap items based on the display mapping of the picklist values. For example, select Status to display the roadmap items in different colors that indicate their approval status. All approved items appear in blue. The COLORS legend in the bottom right corner of the page shows the value associated with each color. If you collapse the legend, you can reopen it by clicking LEGEND. By default roadmap items appear in a blue color when you have not selected a value for SWIMLANES or COLOR BY.
    • METRICS
      Select up to three financial metrics to display as badges on the roadmap items to review them in the timeline. The METRICS legend in the bottom right corner shows the metrics in sequential order as you selected them. If you collapse the legend, you can reopen it by clicking LEGEND. The badges appear on each roadmap item in the same order as you select them. You can also edit the values for the selected metrics for each roadmap item in the timeline. See Define Metrics for Roadmap Items. Your selected metrics remain the same for you between sessions in an unsaved view. To keep your settings, save your view.
    • SHOW DEPENDENCIES
      Show or hide the dependency lines between roadmap items. This option is automatically selected when you start dependency mode to add dependency lines between roadmap items.
    • Clip Metrics to Roadmap Dates
      Clip the metric values for the number and money attributes to match the roadmap duration. If the roadmap includes items that fall either partially or completely outside the roadmap duration, their metric values are clipped to match the roadmap duration. When the option is unchecked, total values are visible for the metrics in the timeline and grid.
  4. Click
    X Close
    .
Roadmap Color Legend
The color legend appears when you select a value in the
COLOR BY
field in the board or timeline view options panel.
  • To collapse the legend, click
    X Collapse
    .
  • To expand it again, click
    LEGEND
    .
legend.png
Define Metrics for Roadmap Items
You can display up to three metrics that appear as badges on your roadmap items in the timeline. Use any stock or custom attributes on the Roadmap Item object of the following data types:
  • Number
  • Percent
  • Money
For the Calculated data type, only Stock attributes on the Roadmap Item object are supported.
Example
: For his FY18 Roadmap, Sid wants to review the planned capital and operating costs for his division by Business Outcome. He selects capital cost, operating cost, and ROI as shown metrics. The metrics display in the order selected. A little badge displays on each roadmap item in the timeline to provide the visibility into the metrics. Sid then groups the timeline into Business Outcome swim lanes. The swim lanes now display the subtotals for capital and operating costs for all the roadmap items in the lane. No subtotal appears for ROI because it is a number that is shown as percent.
As a default, the money attributes use the currency code that is defined on the Roadmap Item object in Classic PPM Studio. If a currency code is not defined for the Roadmap Item object, the product uses the home currency that is defined for the default entity. If necessary, you can add the Currency column to the grid layout and can change the currency codes for the roadmap items. The sub totals for the swim lanes use the single home currency.
Follow these steps:
  1. From the roadmap timeline layout, click
    View Options
    .
  2. Use the
    METRICS
    field to search and select up to three metrics to display on the roadmap items.
    The metrics appear in the order you select. If you do not see a specific number, percent, or money field under METRICS, verify that the field has an API Attribute ID defined on the Roadmap Item object in Classic
    Clarity PPM
    .
  3. Close the View Options panel.
    Metric badges appear on all roadmap items in the timeline displaying dashes (--) as no values are defined yet.
    For roadmap items that have either only a start date (circles) or a finish date (diamonds), the metric badges do not appear.  You can define or update the metric values for these roadmap items in the pop-overs.
  4. Define the values for the selected metrics for an item in the Roadmap Item pop-over.
    The metrics badges are updated to reflect the new values.
  5. Select swim lanes to display aggregates for the metrics for all data types except for number that is shown as percent. For percentages, dashes (--) display instead of aggregates.
  6. To edit the metrics for your roadmap items, complete one of the following steps:
  • In the timeline or board layout, double-click a roadmap item in a row or column. In the pop-over, edit the metric fields.
  • In the grid layout, edit the metric fields inline for a roadmap item row. If the metrics fields are not visible in the grid, click
    Column Panel
    to select and display them.
The updates are reflected in the timeline layout.
When you stack roadmap items at least three levels high, your metrics appear as rows inside each swimlane. Also, badges appear for the aggregates in the swim lanes. For a swim lane that contains less than three rows of items, the aggregates appear in a tool tip when you hover over the swim lane aggregation column.
Roadmap Metrics are Clipped by Default
By default, all metric values are clipped to match the roadmap duration (that is, roadmap start and finish periods) across all layouts.
For example, say that you change the roadmap duration as following after importing projects:
  • Before importing projects: Roadmap duration is March through October of 2018.
  • After importing projects: Roadmap duration is February through September of 2018.
Then, all the imported projects retain their original dates. However, if the project dates fall outside the new roadmap duration, the metrics (for example, Actual, Capacity, Cost, and so on) are clipped. When clipping is on, the project amounts from dates before and after the roadmap duration is not included. When clipping is off, the project amounts from dates before and after the roadmap duration is included.
If you clear the clipping option in View Options, the new setting persists for all the layouts.
Example: How Metrics are Clipped to Match Roadmap Duration
The following example shows a roadmap with a duration of four years spanning over 2016 to 2019. The roadmap includes roadmap items (RMI 1-6) that are linked to projects with varying start and finish dates. Based on how much of the project duration overlaps with the roadmap duration, the metrics are clipped accordingly.
The image shows how metrics for roadmap items are clipped to match the roadmap duration
  • Project 1 spans over 12 years (2012 through 2023) and shows a total cost of 1200 before clipping (that is, a cost of 100 for each year). After clipping, the clipped total shows as 400 to match the roadmap duration of only 4 years.
  • Project 2 shows a total cost of 400 before clipping. After clipping, the total shows as 0 (zero) because the project dates fall before the start of the roadmap duration. Similarly, the dates for project 6 also fall outside or after the end of roadmap duration. Hence, the clipped total for project 6 also shows as zero.
  • Project 3 overlaps partially (2 years) with the roadmap duration and displays a total cost of 200 after clipping. Project 4 dates fall completely within the roadmap duration. Both the clipped and unclipped total cost for this project show as 200. Project 5 is similar to project 3 and overlaps the roadmap duration partially (two years).
When you modify a financial metric (for example, Capital Cost), the value is distributed evenly across the number of days in the roadmap item duration. The total value is also updated accordingly. The metrics always reflect the updated values based on the roadmap item duration irrespective of whether the clipping option is selected.
Plan Roadmap Items On a Board
Use the board to group and visualize work as it progresses over its lifecycle. The board uses Status as the default picklist for columns and None as the default picklist for color. The roadmap items are arranged into columns by their approval status with no color. You can customize the values that appear for the Columns and Color By grouping attributes by configuring the corresponding lookups in Classic
Clarity PPM
. Alternately, you can create roadmap-specific local picklists.
Follow these steps:
  1. From the roadmaps list, click the roadmap for which you want to plan roadmap items.
  2. Click
    Board
    .
  3. Click
    NEW ITEM
    under a column to add the item to that column. The item appears at the top of the column.
    If you switch to another picklist where the new item does not have a value, the item appears in the NONE column at the bottom of the list.
  4. Click the plus icon to add a new roadmap item in the
    None
    column.
    If a default value is defined in Classic
    Clarity PPM
    , the item moves into the default value column after refresh.
  5. Complete the fields in the pop-up window. See Add Roadmap Items to a Roadmap for details on the field descriptions.
  6. Click
    Done
    .
Arrange Items On the Board
You can drag-and-drop roadmap items on the board across and within columns.
  • Move cards vertically within a column. You can also move cards horizontally across columns. The card position is saved for the selected picklist for the specific roadmap for all users.
  • Roadmap items that you create in another layout show up in the None column on the Board. Drag the items to their appropriate columns based on the picklist that you select. After you move all items from the None column, the column disappears.
  • If you add a roadmap item from the Grid and select a picklist value (for example, Approved for Status), then the item shows up at the top of the column by most recently created date. If you add multiple items, all the new ones show at the top, sorted by roadmap item name.
  • The columns are sorted based on the sorting that you define for the choices for a Columns picklist. To change the order of the columns, edit the picklist choices. See Manage Local Picklists for details. Within a column, cards are sorted by the most recently created date first until you re-order them.
    Note
    : For global picklists that apply to all roadmaps, the columns reflect the sorting which is configured for the corresponding lookup values in Classic
    Clarity PPM
    .
Show or Hide Columns on the Board
Show or hide columns on the board using the COLUMNS tab and save the configuration to a view. The capability allows you to display only the relevant columns when dragging cards across columns. You do not have to scroll to the far right to see all the columns.You cannot hide or show the None column.
The COLUMNS panel displays the name of the current picklist. When no picklist is selected, it displays the default picklist name, STATUS. With edit access to the roadmap, you can see an active EDIT link for managing local picklists. See
Manage Local Picklists
in this article for details. If you have view-only access to the roadmap, then you do not see the EDIT link at all.
The EDIT link appears disabled for global picklists. To edit the columns or values for a global picklist, update the corresponding lookup in classic PPM Studio. For example, to update the Type global picklist, update the Roadmap Item Type lookup in classic PPM.
Configure View Options for the Board
Configure the board layout for a roadmap to view the roadmap items that are grouped by specific attributes.
Follow these steps:
  1. From the roadmap Board layout, click
    View Options
    .
  2. In the View Options panel, configure the following settings:
    • COLUMNS
      Select an attribute or picklist by which to group the roadmap items into columns. For example, if you select Type, roadmap items are grouped under columns such as Projects, Ideas. You can select from the list of default or custom global picklists. See Create a Custom Global Picklist. You can also select a picklist that you created locally specifically for the roadmap. See Create a Local Picklist.
    • COLOR BY
      Select a picklist to group the roadmap items by color that is based on the display mapping of the picklist values. For example, if you select Status, the roadmap items in the columns are colored (red, blue, and so on) by their approval status. If you select a color grouping, a collapsible legend appears in the bottom right corner of the page to explain the color meanings. You can select from the list of default or custom global picklists or local picklists applicable to this roadmap.
    • Clip Metrics to Roadmap Dates
      Clip the metric values for the number and money attributes to match the roadmap duration. If the roadmap includes items that fall either partially or completely outside the roadmap duration, their metrics are clipped to match the roadmap duration. When the option is unchecked, total values are visible for the metrics in the timeline and grid.
  3. To close the View Options panel, click
    X Close
    .
Plan Roadmap Items In a Grid
Like a spreadsheet, the grid layout provides a detailed view of roadmap items in columns and rows. All the attributes of the roadmap items appear as column headings or fields with values.
You can configure the columns that you want to display on the grid using the Column Panel. The Column Panel lists all standard and custom attributes that are API enabled for the Roadmap Item object in Classic
Clarity PPM
.
Follow these steps:
  1. From the roadmaps list, click a roadmap.
  2. Click
    Grid
    .
  3. To view a list of columns, click 
    Column Panel
    .
  4. Select the columns that you want to display on the grid. You might have to scroll right to view all the items you select.
  5. To close the Column panel, click
    X Close
    .
  6. To add a new row at the top of the grid, click
    New Row
    .
    The new row is populated with any default values predefined for the Roadmap Item object attributes in Classic PPM.
  7. To add or delete a row anywhere on the grid, use the grid context menu. Select a cell in a row and right-click to display the grid context menu.
Edit Items on the Grid
To edit items on the grid, click in the rows inline to enter or edit values for the non read-only fields. Depending on the data type, you can also edit the fields as follows:
  • Select values from a drop-down list
  • Select a date from the date picker
  • Enter or clear check marks.
  • Use the
    ⋮ Actions
    menu for the In Plan column to either select or clear all roadmaps items appearing on the page as committed to be part of the roadmap.
The Grid updates with edits from the Timeline or Board layouts upon refresh. Use drag-and-drop to change the order in which the columns appear.
Set Targets for the Roadmap
You can set targets either as goals or constraints on the number and money attributes of the Roadmap Item object. By adding, moving, or removing roadmap items that you can effectively plan the roadmap while meeting the set targets. Number attributes that have the percent display option that is selected are not available as targets.
Example
: Typically Sid gets a funding amount that is approved for the year or mid-year. As he plans his roadmap items, Sid must keep in mind how much each roadmap item is reducing the overall planned funding amount (total cost). Sid has a fixed headcount and must track how much each roadmap item is consuming the capacity so he can add headcount. Sid is concerned that he only has a few architects and often they are needed for every investment. As Sid adds targets and sees how much the currently In Plan items apply toward the target, he has a better understanding of the impact. Sid decides to use Cap Ex, Op Ex, and Other FTE as his targets.
Follow these steps:
  1. From the roadmap grid, click
    View Options
    .
  2. Click inside the
    TARGETS
    field to search or select the attributes to use as targets for the roadmap items.
    A carousel appears above the grid displaying the targets as tiles in the order in which you selected them.
  3. Hover over a tile and click the pencil icon to specify the value for a specific target. For example, specify the total capital cost amount that you have received from your management. To track the target as a constraint, do not click the goal icon.
    The following aggregates are automatically updated on the tile:
    • In Plan. The aggregate of the respective attribute of the roadmap items that are in plan.  The value changes as you move roadmap items in or out of the plan.  
    • Variance. The difference between the target amount and the total amount that is consumed by the In Plan items.
  4. Refine the roadmap items in the grid as follows and reflect the updates to the targets on the tiles:
    • For each roadmap item, specify whether you want it in or out of the plan.
    • Enter the value for each In Plan roadmap item. You can update the costs for the roadmap items so that the targets are met.
If you have defined multiple scenarios for a roadmap, the target amounts and the type (goal or constraint) can vary for each scenario. However, the attributes that you select as targets and the order in which you select them remain the same across all scenarios. The target attributes that display and their order are based on the view that you have currently selected for the roadmap. See
Personalize Roadmap Views
in this article.
Set Targets as Goals
You can specify the following types of targets:
  • Goal: A target that you can either achieve or exceed. Benefit is an example of a target that is goal.
  • Constraint: A target that you try to stay under and not go over. Capital Cost is an example of a constraint.
By default, all targets that you specify are treated as constraints unless you specifically mark them as goals.
To flag a target as a goal, click the pencil icon next to it and select the upward facing arrow. The arrow turns blue. To undo the goal flag for a target, click the blue up arrow again. The arrow turns white and the target is no longer considered a goal.
As you move toward a goal, you see the blue up arrow on the tile and a gray progress bar until you meet the target. Once you exceed your goal, a green checkmark appears on the tile. The variance appears in green as it is good to either meet or exceed a goal.
As you use up a constraint amount, a green progress bar appears until you meet the target. Once you go over the constraint, the progress bar turns all red and a stop sign indicator appears on the tile. The variance appears in red as the planned items have exceeded the target and there is no remaining amount.
Display Time-Phased Data by Fiscal Periods
To manage the financials for your roadmap items, select and display per-period time-scaled-value (TSV) metrics in the grid. You can also display one or more Totals attributes in the grid.
The following metrics display as cost or monetary amounts:
  • Benefit
  • Capital Cost
  • Actual Capital Cost
  • Remaining Capital Cost
  • Operating Cost
  • Actual Operating Cost
  • Remaining Operating Cost
  • Total Actual Cost
  • Total Remaining Cost
  • Total Cost
The following metrics display in hours:
  • Capacity
  • Actual
  • Remaining Capacity
Follow these steps:
The following procedure describes how to display per-period TSV metrics and Totals attributes in the grid.
  1. From the roadmap grid, click
    View Options
    .
  2. Click the
    PER-PERIOD METRICS
    field and select the attributes to display their data as time-scaled values. The grid displays the metric data for the maximum number of defined fiscal periods.
  3. Click the
    PERIODS
    field and select the time period by which you want to view the per-period metrics. For example, if you select Benefit as a per-period metric and Monthly for periods, then you can view monthly benefit amounts for all your roadmap items for the roadmap duration.
  4. To close the Setting panel, click
    X Close
    .
  5. In
    Column Panel
    , expand the
    Totals
    attribute to view the group of attributes for which you can display total amounts in the grid. Select the attributes for which you want to display totals.
  • You can configure one set of Totals attributes and a different set of per-period metrics in the grid.
  • To
    not
    display the total amount for an attribute in the grid, clear the checkbox for that attribute in the
    Totals
    group in
    Column Panel
    .
  • Save the grid column positions for the the TSV metrics, non-TSV attributes, and Totals attributes to a view for later retrieval.
Updating the TSV Metric Totals in the Grid and Timeline
When you update the Totals fields, each TSV metric value is updated per period. Also, when you update the TSV metric value, the totals field for that per-period metric is updated. The Clip Metrics to Roadmap Dates setting impacts how each TSV metric value is spread per period.
  • When the Clip Metrics setting is checked (turned on), the TSV metric values are spread as per the following rules:
    • The total amount is spread across the roadmap dates.
    • If the roadmap item dates are within the roadmap duration, then the total amount is spread across the roadmap item dates.
    • If the start or finish date for a roadmap item is null (blank), the roadmap start or finish date is used for the null date.
    • If you update the Totals field, any existing TSV values are overwritten. The overwrite is limited to the TSV periods within the roadmap duration.
  • When the Clip Metrics setting is unchecked (turned off), the TSV metric values are spread as per the following rules:
    • The total amount is spread across the roadmap item dates.
    • If the start or finish date for a roadmap item is null (blank), the roadmap start or finish date is used for the null date.
    • If you update the Totals field, any existing TSV values are overwritten. The overwrite spans across all TSV periods for all roadmap items.
When you update the metrics in the timeline, the same rules apply as for updating the Totals fields for TSV metrics in the grid. The setting for the Clip Metrics to Roadmap Dates option is always the same for both the timeline and the grid.
Spreading of TSV Metric Values Using Calendars Days or Work Days
The spreading of the total value for the following TSV metrics is based on the number of calendar days in the month, quarter, or year. For example, in Q1 there are less days because February has only 28 days. Hence, the value is smaller in Q1 than in Q2.
  • Capital Cost
  • Operating Cost
  • Actual Capital Cost
  • Actual Operating Cost
  • Benefit
The spreading the the total value for the following TSV metrics is based on work days. Depending on the number of hours a specific work day constitutes, a metric might display a higher or lower amount per period.
  • Actuals
  • Capacity
You cannot edit the TSV metrics with either a "Remaining" or a "Total" prefix as they are calculated values.
Example: Displaying Per-Period Metrics
A roadmap with a duration of one year (Jan to Dec 2018) includes the following roadmap items and settings:
  • Roadmap Item 1 duration = three months, Jan - Mar 2018
  • Roadmap Item 2 duration = one year, Jan to Dec 2018
  • Period setting = Quarters
  • Per-Period Metrics setting = Benefit
  • Totals = Benefit
Based on the roadmap duration and settings, you see the relevant quarterly fiscal periods and corresponding benefits data on the grid. For example, if the roadmap includes only Roadmap Item 1, then only one quarter (2018-Q1) of benefit data appears. If you then add roadmap item 2, the grid updates to show benefits data for all four quarters (2108-Q1 through 2018-Q4).
Example: Clipping of Per-Period Metrics and Totals
Say you add Roadmap Item 3 with a duration of 2 years (Jan 2018 to Dec 2019) to the sample roadmap. You enter a total benefit of 2000 for the item. When clipping is disabled, this total amount gets distributed to all the quarters in the roadmap item duration using calendar days. If you now enable clipping, the total benefit amount for the roadmap item gets clipped to the roadmap duration of one year. So the distributed amount changes to 1,000 total for four quarters. If you again update the clipped total from 1,000 to say 1,500, the distributed benefit amount for each quarter is also clipped accordingly based on calendar days.
Bulk Actions for Totals Attributes
You can perform bulk actions on the totals group of attributes. For example, you can drag and drop the group anywhere on the grid of columns.
Configure View Options for the Grid Layout
  1. From the roadmap grid layout, click
    View Options
    .
  2. Configure the following settings for the grid layout:
    • MONEY DECIMAL DISPLAY
      Select whether you want to display one, two, or no decimal places for the money target values for the roadmap items.
    • NUMBER DECIMAL DISPLAY
      Select whether you want to display one, two, or no decimal places for the numeric target values for the roadmap items.
    • Show Targets
      Specify whether you want to display targets for your roadmap items as tiles in a carousel above the grid.
    • TARGETS
      Select attributes which represent the goals or constraints that you have received from the management team to plan your roadmap. Unchecking a selected attribute removes the attribute from the targets ribbon. You can save your selected targets in a view. See
      Set Targets for the Roadmap
      in this article for details
      .
    • PER-PERIOD METRICS
      Select attributes to view time-scaled financial values associated with the roadmap items to manage the roadmap over time. You can also view total amounts for the per-period metrics that you select and other per-period metrics in the grid.
    • PERIODS
      Select Months, Quarters, or Years. The grid displays the roadmap items for the number of fiscal periods that are defined for the selected period type. For example, your default entity includes fiscal time periods for five years (60 months). When you select
      Months
      , the timeline displays roadmap items over 60 monthly columns. Zoom out to five years to view all 60 months. The setting for the grid persists if you save it in a view.
      The PERIODS setting for the grid is separate from the PERIODS setting in the timeline layout. They are not kept in sync. Changing it in one layout does not impact the other layout.
    • Clip Metrics to Roadmap Dates
      Clip the metric values for the number and money attributes to match the roadmap duration. If the roadmap includes items that fall either partially or completely outside the roadmap duration, their metric values are clipped to match the roadmap duration. When the option is unchecked, total values are visible for the metrics in the timeline and grid.
Add Roadmap Items to a Roadmap
A roadmap consists of items that you want to plan during a given time such as an annual business event or a project that spans multiple quarters. Multiple roadmap items fill the roadmap duration.
Build a roadmap by adding items as you work through the planning details and funding constraints at your organization. You can use any layout to add roadmap items. When you revisit an existing roadmap, the application returns you to the most recent layout for that roadmap.
Note
: A roadmap item is only added to the currently selected scenario in which you are working, not to all existing scenarios.
Follow these steps:
  1. From the roadmaps list, click a roadmap.
  2. Click
    Timeline
    ,
    Board
    , or
    Grid
    .
  3. Enter the item name, start and finish dates, and other details:
    • In Plan
      Specifies whether the roadmap item is committed to be part of this roadmap. The values for this field are based on the Roadmap Item In Plan lookup attribute on the Roadmap Item object.
    • MUST HAVE
      Specifies the priority level of the roadmap item for the roadmap. For example, if you select Carryover, it means that you can move the roadmap item out of this roadmap and can carry over to the next one. You can select multiple values. The values for this field are based on the Roadmap Item Must Have lookup attribute on the Roadmap Item object. To display your custom values for the Must Have fields, configure the lookup values in Classic
      Clarity PPM
      .
    • SPONSOR
      Specified the person sponsoring the budget for the roadmap item. The list of sponsors that you can select from depends on the resources for which you have access rights in the system.
  4. Click
    DONE
    or click outside the pop-over to close the window. The new roadmap item is added to the layout.
  5. To edit the roadmap item in the Timeline or Board, double-click the item in a row or a column. The ROADMAP ITEM pop-over appears. To edit the item in the Grid, edit the fields inline. If you configure metrics for the Timeline under View Options, then you can define or edit the metrics in the pop-over.
When you delete a roadmap, all the roadmap items and any picklists that are associated specifically with the roadmap are also deleted. When you delete a roadmap item, any dependencies that exist for the roadmap item are also deleted.
Default Dates on the Board and Grid
When you add a roadmap item on the Board or the Grid, the Start date defaults to the first day of the roadmap Start Period. The Finish date defaults to the last day of the third month from the roadmap item Start date. For example, if the roadmap Start Period is Jan 2019, when you create a roadmap item on the Board or the Grid, the start and finish dates default as follows:
  • Roadmap item start: Jan 01, 2019
  • Roadmap item finish: March 31, 2019
The system administrator can change the default behavior by setting the Start and Finish attributes for the Roadmap Item object to be specific dates in Classic
Clarity PPM
.
Import Roadmap Items
You can import the following types of items into a roadmap scenario:
  • Internal projects that exist in the product
  • Internal custom investments that exist in the product
  • Investments that you maintain externally such as in an Excel spreadsheet.
  • Ideas that exist in the product
Import Roadmap Items From a CSV File
You can import a list of up to 250 roadmap items from a comma-separated values (CSV) file. Your imported roadmap items appear inside a single roadmap scenario. You cannot update existing roadmap items with this feature.
Importing roadmap items requires the
Roadmap - Edit
instance-level or OBS-level access right or the
Roadmap - Edit - All
global access right.
Refer to the following table for the supported types of roadmap item attributes that you can import and their correct formats.
Attribute Type
Format
Numbers
Do not use a thousands separator. Enter periods for the decimal places. Use a dash for negative numbers.
Percentages
Enter percentages as decimals. For example, to import 25percent, your raw import row should show 0.25.
Monetary values
Do not include a comma for the thousands separator, unless you enclose it in quotes. Decimal values are acceptable; however, do not include currency codes or symbols.
Strings
Use double quotes around any strings with commas. For example, "Roadmap Item 1 for regions A, B, and C".
Dates
Use YYYY-MM-DD format. For example, 2019-11-15 for November 15, 2019.
Static single value lookups
Specify one case-sensitive value from the set. For example, for type specify
Project
,
Program
,
Idea
, or
Feature
. For inPlan, specify
2
(In Plan) or
1
(Not In Plan).
Follow these steps:
  1. Log in to the
    Clarity PPM
    New User Experience
    .
  2. In the main menu, click
    Roadmaps
    .
  3. Open a roadmap and select a scenario.
  4. Click
    Item Actions
    ,
    Import from CSV
    .
  5. Download the PPM_ROADMAP_CSV_IMPORT_TEMPLATE.csv file.
  6. Prepare the CSV file:
    1. Open a spreadsheet, database, or other application where you can format your source CSV file. For example, a committee decides to explore 40 new portfolio items and sends you a list. You can configure that list in Microsoft Excel. Save a copy of the import template as my_new_items.csv, paste your list of 40 items, format the list as required, and import it into
      Clarity PPM
      .
    2. Review the first row of the template. The first row contains optional user-friendly names and instructions for each field. For example, Roadmap Item Name (Required field - Max = 80 characters), Start Date, NPV - Net Present Value (Money +/-0.00), or Operating Cost (Money +/-0.00).
    3. Verify that the second row contains the
      API Attribute ID
      for each attribute. The default values are already set. Your administrator can change these IDs in CA PPM Studio. For example, name, start, npv, or operatingCost. You can change the API Attribute IDs for any custom attributes only.
    4. Verify that the remaining rows (up to 250) contain values that are delimited by a comma with no spaces. Excel handles the commas inside cells and between cells for you when you save as CSV. You do not see the commas in Excel. You can build a raw import file in text using Notepad where you must include the commas.
    5. Verify that any date values you want to import follow the YYYY-MM-DD format. Be careful that Excel does not reformat your values.
    6. Save your CSV file. If working in Excel, use the Save As option to save your file as a CSV file with the .csv file extension.
  7. Verify that you have opened a roadmap and selected a scenario.
  8. Click
    Import CSV
    .
  9. Select the CSV file from your local PC or network server and click
    Import CSV
    .
    A confirmation message shows you how many rows were successfully imported and how many rows could not be imported.
  10. Locate your new imported roadmap items on the board, timeline, or grid. On the board, imported roadmap items might appear in the
    None
    column, ready for you to review. On the timeline, imported roadmap items appear in their specified swim lane (for example,
    None
    ,
    Project
    , or
    Idea
    ).
New items may not necessarily appear in the NONE column. Their placement depends on how the data is set up in the CSV. You could specify a lookup value for the status or type. The roadmap item would appear in the column or swimlane that corresponds with that value.
When working with the CSV import template in Microsoft Excel, observe the following requirements:
  • Format date column cells with the custom YYYY-MM-DD format.
  • Do not use commas as thousands separators.
  • Save the file as CSV and use UTF-8 encoding to preserve special characters that extend beyond the standard ASCII (ISO 8859 Latin I) codeset.
Use the following images for guidance:
csv.jpg
Import Projects, Custom Investments, and Ideas from PPM
You can create roadmap items by importing active projects or investments for which you have at least view access rights. When you import projects or investments as roadmap items, the application creates a link between the roadmap item and the project or investment. Each project or investment remains linked to the new roadmap item.
You cannot import a project, custom investment or idea that is already linked to a roadmap item in a scenario. Those projects, custom investment, and ideas are excluded from the IMPORT FROM PPM dropdown.
Before you can link a roadmap item with a project, custom investment or idea, the following conditions must be met:
  • they are
    active
  • the project is not a template or program
  • the
    Include in Roadmaps
    setting for the custom investment type is selected
  • the custom investment is not already linked to another roadmap item in the same roadmap scenario
When the start and finish dates of a project is different from that of the associated cost plan of record, the start and finish dates of the linked roadmap item reflect the project dates. However, the financial attributes such as Capital Cost or Operating Cost reflect the data from the cost plan.
Follow these steps:
  1. In the main menu, click
    Roadmaps
    .
  2. Open a roadmap in the timeline, board, or grid view.
  3. Click
    Scenarios
    , and select a scenario.
  4. Click
    Item Actions
    and select
    Import from PPM
    .
  5. To import projects, complete the following steps:
    You can import multiple projects by OBS, select one or many, or use both fields. When you import by OBS, you get a new roadmap item for each project. For example, you specify OBS-A and OBS-B, each with 10 projects, and you also select projects 1, 2, and 3 for the import. This example yields 23 roadmap items, one for each project.
    1. Select
      Projects
      from the drop-down menu.
      The
      IMPORT PROJECTS page appears.
    2. In the
      PROJECT OBS
      field, enter all or part of an OBS unit or select from the list. You can also search for projects in descendant levels and ancestor levels. Or, click
      Unit Only
      to constrain your import to projects in a specific OBS unit. Each OBS that you select appears in a list. Scroll up to view your OBS list. In this step, you are specifying the OBS units for multiple projects that you want to import. Press the
      Tab
      key or click outside the OBS filter to go to the next field.
    3. (Optional) In the
      PROJECTS
      field, enter as many characters of the project name to identify it in the list. Scroll down the list and select one or more projects to import as roadmap items. The projects that appear in this field are not limited by the OBS units you might have selected in the
      PROJECT OBS
      field. Typically, you import all projects by
      PROJECT OBS
      . However, the
      PROJECTS
      field allows you to select more projects to import into the same roadmap planning scenario.
    4. Click
      IMPORT ITEMS
      .
  6. To import investments, complete the following steps:
    1. Select a custom investment type (for example, Business Use Cases) from the drop-down menu.
      The
      IMPORT <investment type> page appears.
    2. Select your investment type instances and click
      IMPORT.
    The
    Item Actions
    button shows the
    Import in Progress
    icon and tooltip.
    You can directly include custom investment objects in roadmaps from Classic PPM. On the object creation page, select the Object Extension as
    Investment Extension
    and click
    Save
    . The page refreshes to show a new checkbox
    Include in Roadmaps
    , selected by default. Uncheck the checkbox if you do not want to include the custom investment object in roadmaps.
    Include in Roadmaps
    checkbox is not checked by default, in case you upgrade from 15.5.0 to 15.5.1.
    Each imported project or investment appears as a roadmap item in the timeline, board, or grid. Roadmap item data remains linked to the original projects and investments. The Linked To and Linked To ID columns on the grid layout show the original project or investment data. The financial data from the cost plans of the imported custom investments is also imported in the roadmap item.
  7. (Optional). Double-click the
    Linked To
    column and use the search drop-down to select a different custom investment or project instance.
  8. To continue to synchronize the shared data, select the
    Sync
    check box. For example, a change in the project start date also appears in the linked roadmap item start date.
  9. (Optional) Save any special changes that you make to the current scenario and view.
  10. Importing Ideas follows the same process of importing Projects. Follow steps 1-4.
  11. You can import ideas linked to an OBS unit or import multiple individual ideas.
The following financial attributes (planned and actual) can carry over and can remain synchronized with each imported project:
  • Currency Type
  • Payback Period
  • Benefit and NPV (Money)
  • Capital Cost, Operating Cost, and Total Cost (Money)
  • IRR and ROI (Percent)
Select an OBS Unit for a Roadmap
As a portfolio manager, you can restrict and limit OBS associations on roadmap objects. Only users having OBS-level access rights or global roadmap rights can view the roadmap objects associated with their OBS. To associate roadmaps with an OBS unit, see in the Classic PPM Administration documentation. After you associate a roadmap with an OBS, you can select an OBS unit for the roadmap in the
New User Experience
.
Follow these steps
:
  1. Navigate to a roadmap. You must have OBS unit or global roadmap access rights to view or edit the roadmap.
  2. Click the
    Details
    button.
    The associated OBS attribute for the roadmap appears.
  3. Select an OBS unit for the roadmap.
    The following example shows a roadmap with an associated OBS called Portfolio Roadmap OBS with two units.
OBS GIF.gif
Link Roadmaps Items to Projects, Custom Investments, and Ideas
In a roadmap scenario, you can associate a roadmap item to an existing project, a custom investment, or an idea. You will only see projects, custom investments, or ideas for which you have at least view access rights. If you are linking Roadmap Items to a project, then the project:
  • Should be active
  • Cannot be a template or a program
  • Should not be linked to another roadmap item in the same scenario
Similarly, once an idea or a custom investment is linked to a Roadmap item, they cannot be associated with other roadmap items.
Linking allows you to drill into the associated Clarity PPM object (project, custom investment, or idea) and view more details about it. Also, you can import the latest system data from the object into the roadmap item.
Link Ideas to Roadmaps1.jpg
Follow these steps
  1. Open a roadmap.
  2. Click
    Scenarios
    to select a scenario.
  3. If you are on the Grid layout, use the
    Linked To
    column to link the roadmap item to a project, an investment or an idea. 
    1. The
      Linked To ID
      column is automatically populated with the linked project or investment ID.
    2. The
      Linked to Type
      column is automatically populated based on the type of imported object (project or custom investment type).
    If you cannot see the Linked To or any other columns in the grid, use the Column Panel to add columns to the grid.
  4. In the Timeline or Board layout, double-click the roadmap item to open the roadmap item details.
    image2018-12-7_14-28-40.png
  5. Click Link and then select the project, custom investment, or idea you want to link to the roadmap item.
  6. Click
    Done
    to save your changes.
  7. Use the hyperlink to access the project, investment, or idea pages. Depending on the object type you linked and the type of access you have, you land on one of the following pages:
    • Project tiles page
      You land on the project tiles page when you have access only to the project but no access to any of the modules (tabs) configured in the project. Consider an example where a project is configured to include only the Risks, Issues, and Changes modules. If you have view access to this project but no access to any of the modules, you land on the project tiles page. You do not see a link to navigate back to the source roadmap.
    • Project page with error
      You land on a project module page and receive an unauthorized error. Consider an example where a project is configured to include only the following modules in the listed order: Tasks, Risks, Issues, and Changes. If you have view access to this project but no access to the first module (Tasks), you land on the Tasks page of the project. However, since you are not authorized to see tasks, you get an error on the page. You see a link to navigate back to the source roadmap. You do not see any other modules.
    • Project page with no error
      You land on a project module page and do not receive an error. For example, a project is configured to include only the following modules in the listed order: Tasks, Risks, Issues, and Changes. If you have view access to this project and also access to the first module (Tasks), you land on the Tasks page of the project. You are also able to see the tasks and a link to navigate back to the source roadmap. You do not see any other modules besides Tasks.
    • Investment Details page
    • Idea Details page
      You land on the linked idea's grid page.
  8. To navigate back to the roadmap, click the roadmap name link at the top of the page.
You can also delete the link between roadmap items and
Clarity PPM
objects.
Follow these steps
:
  1. Open a roadmap.
  2. Click
    Scenarios
    and select a scenario.
  3. If you are on the Grid layout, double-click the
    Linked To
    column and click
    REMOVE LINK
    .
  4. In the Board layout or Timeline layout, double-click the roadmap item to edit it.
  5. Click the
    Edit
    icon next to the linked
    Clarity PPM
    object.
  6. Click the down arrow and click
    REMOVE LINK
    .
  7. Click
    DONE
    to save your changes.
Synchronize Roadmap Items with Linked Project, Custom Investment, or Idea Attributes
Links are created between roadmap items and projects, custom investments or ideas when you perform the following actions:
  • Import projects, ideas, or custom investments into a roadmap.
  • Link a roadmap item to a project, idea, or custom investment in the grid.
As the roadmap or portfolio manager, you can synchronize your linked roadmap items to existing projects. Synchronizing ensures that the roadmap data reflects the latest system data from the linked projects. You can control which roadmap items, attributes, or attributes groups to synchronize.
  • You can only synchronize the system-defined roadmap item and project attributes (metrics and dates) that are available by default. You cannot synchronize custom roadmap item or project attributes.
  • Release 15.6.1 does support the synchronization of custom attributes for your custom investment types.
  • If the parent of a project contains custom attributes that match the API Attribute ID of a roadmap item, the value of the attribute is synced when the project is synced.
Example:
Sid is working in a roadmap grid that has several roadmap items that are linked to
Clarity PPM
projects. As the portfolio manager, Sid knows that there are several project managers still working on changing metrics in their projects. He wants to exclude these projects from the synchronization process. Sid wants to control which roadmap items are updated with the project data. He also wants to update only the actual attributes and not the planned ones. When the project managers are done updating their plans, Sid opens the roadmap, selects the remaining roadmap items, and synchronizes them with the latest project data.
Follow these steps:
  1. In the main menu, click
    Roadmaps
    .
  2. Open a roadmap in the grid.
  3. Click 
    Scenarios
    and select a scenario.
  4. Import projects, ideas or custom investments into a roadmap or link a roadmap item to a project, idea, or custom investment in the grid. Verify that the Linked To field shows the associated project, idea, or investment.
  5. Click
    Column Panel
    and select one or more custom attributes that you want to synchronize in the grid.
  6. Select the
    Sync
    attribute. You might have to scroll the grid to the right to view the new attribute in its own column. By default, syncing is selected for linked roadmap items.
  7. For the linked roadmap items that you do
    not
    want to synchronize, clear the check box in the
    Sync
    column.
  8. Click
    Item Actions
    and select
    Sync Linked Items
    .
    1. Select the roadmap item attributes to synchronize. You can select all attributes, attribute groups, or only specific attributes.
    2. To sync custom lookup attributes for projects, ideas, and custom investments, select
      Matching Custom Attributes
      .
    3. Click
      SYNC
      .
      Sync in progress
      appears. You can work on other scenarios or other application pages during the sync operation. Only the current scenario is temporarily locked for editing.
  9. After the sync process is complete, the custom attributes are populated in the roadmap item custom attributes.
Matching Custom Attributes
When synchronizing matching custom attributes, the match is based on the API Attribute ID and Data Type for the child attribute of the parent Project, Custom Investment, or Idea object:
  • The API Attribute ID and lookup data type for the attribute must match the API Attribute ID of the roadmap item object.
  • The type for the attribute must match the attribute type on the roadmap item object.
  • The lookup must also match.
The following conditions also apply:
  • API Attribute ID must be a single character followed by an underscore (example: c_attribute).
  • When you select the
    Matching Custom Attributes
    option and the application finds a match, the data from the investment populates the roadmap item.
  • If the application finds no matching attributes, nothing happens to your custom investment attributes. The application continues synchronizing the remaining linked items as usual.
Synchronization is supported for custom attributes with the following datatypes:
  • static single-value lookups
  • simple data types (number, string, Boolean, date)
    Dynamic Lookups, Parameterized Lookups, Formulas, and Calculated Attributes are not supported.
Sync Column and Checkbox
The following three conditions control the appearance of the
Sync
checkbox in the grid:
  • Visible and Not Selected
    : The roadmap item is linked to a project; however, you do not want to synchronize it.
  • Visible and Selected
    : The roadmap item is linked to a project and ready for synchronization.
  • Not Visible
    : The roadmap item is not linked. Without a linked project, the roadmap item cannot be synchronized.
The following image provides examples of all three conditions:
image2018-6-14 9:9:41.png
To identify the last time a roadmap item was synchronized, add the
Last Synced Date
field from the Column Panel to the grid.
Personalize Roadmap Views
You can personalize a roadmap layout to see the columns that are relevant to you and capture the required information quickly and efficiently. You can also save your personalizations as views that you can access later. The saved views are also available to all users with access to the roadmap. The saved views are roadmap specific and span across all scenarios. If you select a view for a roadmap, then the view applies to all the scenarios for the roadmap irrespective of the scenario you are in.
The following examples are some ways that you can personalize the grid:
  • Pin or unpin columns to the left or right
  • Apply filters
  • Add or remove columns
  • Reorder the columns themselves using drag-and-drop.
Example
: Sid has created an FY18 Strategic Plan roadmap for his business unit at Acme Corporation. He likes to see certain details about the items on his roadmap (such as Sponsor, Owner, Finish, and Rank) based on his experience. He configures his Roadmap Item grid layout to reflect his preferences, filters it to show items
In Plan
, then saves these settings as
Sid's View
.
To add or remove columns from the grid for a roadmap, click
Column Panel
. The local picklists that you create for a roadmap also appear in the column panel for adding to the grid. To add custom fields as columns to all roadmap grids, add the fields as attributes to the Roadmap Item object in classic PPM. Define an API attribute ID. The attributes are now available in the column panel.
Create a View
To avoid creating multiple copies of nearly identical views, do not save a new view unless its properties are different from an existing view. A simple strategy is to create a core set of 10 or 15 views that all users can share. Users can make small adjustments to these core views without necessarily saving new views. You can continue working in an unsaved view. However, to preserve your filters, settings (view options), and grid configurations, save your view.
When you save a view, it includes your configurations to the timeline, board, and grid layouts for a roadmap.
The following image shows an example of the Work in Progress view that saves the following configurations on the roadmap timeline:
  • Filtering of roadmap items by Approved status
  • Swim lanes by Team attribute
  • Color by Team Status attribute
Image showing an example of a view that saves the filtering and setting configurations on the Timeline.
Follow these steps:
  1. From the roadmap list, click a roadmap.
  2. Click
    Timeline, Board,
    or
    Grid
    .
  3. Set any filters and adjust any settings (view options). On the grid, select the field columns.
    UNSAVED appears for the current view.
  4. Click
    VIEW, SAVE AS
    .
  5. In the
    SAVE VIEW
    panel, enter a new name. To replace an existing view, leave the same name. Click
    SAVE
    and click
    CONFIRM
    .
  6. Click
    SAVE
    .
    The view is saved and remains active as your current view.
To change the current view, click the
VIEW
menu and select another view.
Manage Views
Over time, the views might need maintenance. For example, you want to rename a view or remove obsolete views. You can identify your own views from the views of other users.
Each roadmap supports up to 500 views.
Follow these steps:
  1. Click
    VIEW, MANAGE
    .
  2. On the
    MANAGE VIEWS
    panel, click one of the two tabs:
    • CREATED BY ME:
      This tab displays views that you created. To rename a view, select the view name and enter a new name. To delete a view, click
      X Delete
      .
    • CREATED BY OTHERS:
      This tab displays views that other users created. The tab displays the view name, owner, and options to hide or show the view in the views list.
  3. To search for a view, enter its name in the search field.
  4. Click
    X Close
    .
The view that you select persists across all your sessions for a specific roadmap unless you change it. When you revisit the roadmap grid layout, the last view that you selected applies. If you do not select a view, the standard view appears as a default. If the view that you select is later deleted by the owner, the standard view applies.
Manage Roadmap Picklists
Configure a Default Global Picklist
The default picklists for grouping roadmap items are based on the values that your administrator defines for the following lookup attributes. The lookups reside on the Roadmap Item object in Classic
Clarity PPM
:
  • Status
    : The lookup contains the values for the Status attribute that lets you group items into columns by status. For example, all unapproved roadmap items appear under the Unapproved column.
  • Type
    : The lookup contains the values for the Type attribute that lets you group items by roadmap item type. For example, all ideas appear under the Idea column.
The In Plan lookup attribute is system-restricted. You cannot customize the lookup to add more values. You can only change the labels and the display colors for the existing values.
The default picklists are global and are available to all roadmaps in the system for grouping roadmap items. They appear differently on the different layouts. On the timeline layout, they appear as swim lanes with optional colors. On the board layout, they appear as columns with optional colors. On the grid, they appear as columns.
If a default color is not defined for the picklist values, the application uses white as the default color. You can customize the default color for the default global picklists.
Work with your system administrator to configure the default global picklists in Classic
Clarity PPM
. See
CA PPM Studio Objects and Attributes
for details.
Follow these steps:
  1. Click
    Administration
    ,
    Studio
    ,
    Objects
    .
  2. Open the Roadmap Item object and click the
    Attributes
    tab.
  3. Select the attribute that you want to configure. For example,
    Status
    ,
    Type
    , or
    In Plan
    .
  4. Configure the following properties:
    • Set the order in which the values appear in the list.
    • Rename or add values to the list to align with your business needs.
    • Change the predefined color display mappings.
    • Activate a lookup picklist that was previously deactivated or deactivate a lookup so it no longer appears as a picklist.
      Users cannot add new picklist values to the columns for deactivated picklists. The column appears visually different compared to the active columns. When you move the last item out of the deactivated value column, the column disappears.
  5. To add a new global picklist, click
    New
    and define the roadmap item attribute and its values.
Do not be confused by the appearance of a field called
Type
with values such as Investment, Product, and Application on the Details panel, and another field also called
Type
with values such as Project, Program, Idea, or Feature as seen in the swimlanes and legend. You are seeing the subtle difference between
Roadmap Type
and
Roadmap Item Type
.
Create a Custom Global Picklist
You can create your own custom picklist containing custom grouping values that are governed by the company. The global picklists appear under the SWIMLANES or COLUMNS and COLOR BY list under
All Roadmaps
. They apply to all roadmaps.
For example, you can create a custom picklist that is named Business Outcomes to group your roadmap items using the following values:
  • Mobile
  • Technology Enhancement
  • Wow the Customers
The custom picklist becomes available in the Columns and Color By grouping attributes. You can then select Business Outcomes from the Columns attribute to view your roadmap items that are grouped into columns corresponding to their business outcome value. Also, you can select Business Outcomes from the Color By attribute to view your roadmap items that are grouped by colors that you associate with the business outcomes.
Follow these steps
:
Note
: Work with your system administrator to configure a global picklist in Classic
Clarity PPM
using the following high-level steps. See
Configure Lookups
under
Administration
for details.
  1. In the Administration tool, create a Static List lookup that is associated to the Roadmap Item object. Select the Manual sort order so you can define the order in which the lookup values appear on the UI.
  2. Add your custom values to the lookup. The values correspond to the grouping options that the picklist contains on a roadmap.
  3. Reorder the values manually.
  4. On the Roadmap Item object, create an attribute. The attribute name corresponds to the picklist name that displays on the roadmap.
  5. Associate the new attribute to the Static List lookup using the Data Type field.
  6. In Display Mappings, select a color to represent each lookup value.
  7. (Optional). Specify a default color for each lookup value. If you deactivate a lookup value, the assigned color disappears for the value from the roadmap and it displays in the default color.
When you create a global picklist, the existing roadmap items first appear in the None swim lane or column and are sorted by their start date. You can then move these items from None to the other lanes. If you deactivate or delete the picklist in Classic
Clarity PPM
, the items again appear in the None swim lane or column.
If you delete the roadmap Item attribute that is used as a custom global picklist, the picklist is removed from all roadmaps.
Create a Local Picklist
Create a local picklist to group roadmap items by columns or by color in a specific roadmap. You can then use the picklist across all the layouts. For example, if you create a Columns picklist in the Board layout, the picklist appears in the Timeline settings as an option under SWIMLANES. In the Grid layout, the picklist choices appear in the Column Panel.
Apply the picklist choices to the roadmap layout. For example, if you create a columns picklist, move any new roadmap items from the None column to the new columns.
Follow these steps:
  1. Open a roadmap and click
    Timeline
    ,
      Board
    ,
    or Grid
  2. Click
    View Options
    .
  3. Click
    MANAGE PICKLISTS
    .
    The MANAGE PICKLISTS window appears.
  4. Click
    NEW PICKLIST
    .
  5. Enter a picklist name (for example, Business Outcomes).
  6. Add choices to your picklist. Name the choices to correspond to your picklist values. For example, Mobile, Technology Enhancement, and so on.
  7. To select a color for a picklist choice, click the red box to the left of the choice. Pick a color from the palette that displays.
  8. Click
    Done
    to save the picklist and add it to the Columns or Color By list under
    THIS ROADMAP
    .
If you create a color picklist, a color legend appears at the bottom right corner of the page. The legend displays the colors and their corresponding values in the picklist.
Example:
Sid has already compiled a roadmap of the new efforts that his research teams have underway. Upon drilling into the roadmap, Sid realizes that he wants to group the roadmap items by team, which is not a currently defined grouping available. He creates a Team picklist for his five teams, then distributes the available roadmap items to those teams. He also wants to have a quick way to indicate the status of these items. Sid selects Status as the color by attribute, which also causes a legend to appear at the bottom of the page indicating which color reflects which status. He then saves these choices as part of his "Working View".
NOTE:
When you switch between different scenarios for a roadmap, the grouping that you have currently selected for the roadmap items remains the same across all the scenarios.
Manage Local Picklists
You can select an existing local picklist or search for a picklist by name. After selecting a picklist, you can edit or delete the values. If you delete a custom local pickilst that is applied to a roadmap view, the default picklist gets applied to the view. For example, say that you have selected a local picklist (MyPicklist01) for the Columns grouping on the board layout. You delete the picklist. The view then refreshes and applies the default global picklist of Status to the Columns grouping.
Follow these steps:
  1. Open a roadmap and click
    Timeline
    ,
    Board
    , or
    Grid
    .
  2. Click
    View Options
    .
  3. Click
    MANAGE PICKLISTS
    .
    The MANAGE PICKLISTS window appears.
  4. Select a picklist that you want to edit.
  5. Edit the picklist values as follows:
    • Rename, delete, or add choices.
    • Move the choices up or down in the list.
    • Change the color choices.
    • Delete the entire picklist.
  6. When done, click
    X Close
    .
Delete a Local Picklist Choice
  • If you delete a picklist choice, the corresponding column or swim lane is deactivated and appears unavailable on the layouts. After you move all the roadmap items from the deleted column or swim lane, the column or swim lane disappears.
  • If you delete a picklist choice that is assigned a color, any existing roadmap items continue to display the color. After you move the roadmap items from the deleted column or swim lane, the column or swim lane with color disappears.
Create Roadmap Planning Scenarios
A scenario is a copy of the roadmap data with a unique name. Scenarios allow you to explore changes to the roadmap items in the context of a
what-if
scenario. For example,
how can we maximize ROI
?
What if we add 50 resources? What if we increase the contractual price to our client and delay shipping for six months?
You can create multiple scenarios for a roadmap and can indicate which is the plan of record and which is the baseline. When you report the portfolio performance, you can decide to use only one plan (for example, the plan of record).
Example:
Sid is preparing for a stakeholder meeting to review his Technology Work roadmap for the next six months. The stakeholders ask many questions. He wants to answer them visually so they can see the impact of making the suggested changes. For example, John wants to know if adding more resources for the roadmap items delivers faster time-to-market. Karen wants to know the impact if they reduce funding and allocate fewer resources. Sid selects the default scenario and clicks Save As to create a scenario with a new name. He edits the content to reflect these scenario questions. Sid creates the following scenarios from the default scenario:
  • Technology Work with More Resources
  • Technology Work with Fewer Resources
As you switch between scenarios, only the roadmap item data changes. Everything else remains the same including the view personalizations and the grouping.
Follow these steps:
You can create a scenario from any roadmap layout by copying either the default scenario or an existing scenario.
  1. Open a roadmap and click
    Scenarios
    .
    If you have not created any scenarios, the Default Scenario appears in the Scenario drop-down list. If you have created scenarios, the existing scenarios also appear in the menu.
  2. Select the default or an existing scenario and then select
    Save As
    to create a copy of that scenario.
  3. Enter a name for the new scenario and click
    Save
    .
  4. Edit the roadmap items specific to this scenario. The changes are not reflected in the other scenarios.
Default scenario
If you are not using scenarios, the system creates a default roadmap scenario using the base roadmap data and applies the Plan of Record (POR) tag. Until you create more scenarios, the default scenario and its POR tag are not visible.
Baseline
You can tag only one scenario per roadmap as a baseline. You are not required to mark a scenario as a baseline. If a scenario is already tagged as the POR, you cannot tag it as the baseline. You can delete a roadmap scenario that is the baseline.
Plan of Record (POR)
You can tag only one scenario per roadmap as the plan of record. If no scenarios exist for a roadmap, you cannot edit the default scenario plan of record tag to No. There must always be a plan of record scenario in the system. If you try to delete a roadmap scenario that is the plan of record, you are prompted to select another scenario as the plan of record.
Manage Scenarios for a Roadmap
You can edit a roadmap item and its attributes in all scenarios but each change is specific to each scenario.
  1. Open a roadmap and click
    Scenarios
    .
  2. Click the
    Scenario
    drop-down and click
    MANAGE
    .
  3. Click the
    ⋮ Actions
    menu next to a scenario to manage the scenario as follows:
    • Rename the scenario
    • Delete the scenario
    • Set the scenario as the POR and remove the POR tag from any previous POR scenario.
    • Make the scenario the baseline and remove the baseline tag from any previous baseline scenario.
    • Remove the baseline tag from a baseline.
  4. Click
    X Close
    .
Compare Scenarios in the Timeline
Compare two roadmap scenarios in the timeline so you can evaluate your different
what-if
scenarios and can decide the best course of action for a given roadmap. Roadmap scenario comparisons let you analyze the same roadmap items within two different scenarios.
Example
: Sid is working on the Technology Work roadmap and the following scenarios:
  • Technology Roadmap with More Resources
  • Technology Roadmap with Less Funding
Sid has a meeting that is scheduled with stakeholders to support and discuss his selected plan of record for the Technology Work roadmap. Before the meeting, Sid wants to compare each of his roadmap scenarios. Based on the comparison, he wants to take notes that support a specific scenario to be flagged as the plan of record.
The following image shows the scenario comparison toolbar.
scenario_comparison_toolbar_updated
scenario_comparison_toolbar_updated
Follow these steps:
To compare scenarios, verify that at least one more scenario exists besides the default scenario.
  1. Open a roadmap in the timeline layout.
  2. Click
    Compare Scenarios
    to start comparison mode.
    The Compare To menu appears.
  3. From the
    SCENARIO
    menu, select the first (compare from) scenario.
  4. From the
    COMPARE TO
    menu, select the second (compare to) scenario.
    The
    compare to
    scenario roadmap items appear as the lower timeline bars with the lighter shading. The
    compare to
    scenario roadmap items appear in the same swim lane as their corresponding
    compare from
    roadmap items.
  5. Use the following guidelines to compare the roadmap items in the two scenarios:
    • Dependency lines appear only for the
      compare from
      scenario roadmap items.
    • If differences exist with the
      compare to
      roadmap items, a delta icon appears on the
      compare from
      scenario roadmap items. The
      compare from
      scenario roadmap items are read-only.
    • Metrics badges on roadmap items appear only for the
      compare from
      scenario. Also, the totals per swim lane are derived from the
      compare from
      scenario only.
    • Grouping by swim lanes is driven by the
      compare from
      scenario.
    • Roadmap items in the
      compare to
      scenario are organized by date and not by their timeline position or grouping.
    • If a roadmap item has changed to another swim lane in the
      compare to
      scenario, it still appears in the same swim lane as the
      compare from
      scenario roadmap item. You can easily compare visually as the
      compare from
      and
      compare to
      roadmap items are close together.
  6. Click
    SHOW
    to display the roadmap items that reside in the
    compare to
    scenario but do not reside in the
    compare from
    scenario.
    The
    Not In
    <scenario>
    window appears. This window shows items that have been removed from a scenario or added to one scenario but not the other scenario.
    If the roadmap item is not part of the display scope, it does not appear in the
    Not In Scenario
    window.
  7. Click the delta icon for a
    compare from
    roadmap item to view the attributes that have changed for that roadmap item in the
    compare to
    scenario.
    A pop-over appears displaying the following attributes only if there are changes to these:
    • Start or Finish Date
    • Swim lane attribute
    • Color attribute
    • Metrics
    For the swim lane, color by, and metric attributes, the comparison is based on the values that are configured on the view. For number, money, and date attributes, the delta value between the two scenarios appears under the DELTA column.
  8. Click
    X
    on the Compare To banner to get out of scenario comparison mode.
Displaying Roadmap Items in Scenario Comparison Mode
  • A roadmap item with a delta icon and no
    compare to
    roadmap item indicates that the item does not exist in the
    compare to
    scenario. Hover over the delta icon to show all the details for the Compare From scenario and NULL entries for the Compare To scenario column.
  • For easier visual comparison, you can click the
    compare from
    roadmap item to highlight both the
    compare from
    and
    compare to
    items.
  • Overlapping rules do not apply to
    compare to
    roadmap items. See
    Overlap Positioning and Compare To Roadmap Items
    in this article.
  • The roadmap items are read-only and you cannot edit them.
Overlap Positioning and Compare To Roadmap Items
By viewing the
compare from
and
compare to
items together in the timeline, you are able to compare a roadmap item in different scenarios. To facilitate the comparison, the roadmap item overlapping logic does no apply on the
compare to
roadmap item as it could push the item down the page and out of view. Because overlapping logic applies on the
compare from
roadmap item, when you select the item, both the
compare from
and
compare to
roadmap items are highlighted. Highlighting both the items allows for better viewing and comparison. The following image shows how both the
compare from
and
compare to
roadmap items are highlighted when you select the
compare from
item.
visually_compare_roadmap_items
visually_compare_roadmap_items
Apply Search Filters for Roadmaps and Roadmap Items
You can search for specific roadmaps and roadmap items or can apply filters.
Follow these steps:
  1. On the roadmap list page, click the
    Search
    field.
  2. Enter a roadmap name or ID.
  3. To search for roadmap items, open a roadmap.
  4. Enter a roadmap item name or ID, or select filter criteria such as Status, Sponsor, or Owner.
When filtering for roadmap items using the free-form search, the search uses both the roadmap item name and ID. The roadmap item ID uses an autonumbering format of RI00001. Assuming that the system administrator has not changed this format, if you enter
R
,
I
, or
0
(zero), all roadmaps items are returned in the search results.
To view the roadmap ID, open the roadmap and click
Details
. To view the roadmap item ID, click Column Panel on the Grid layout and add Roadmap Item ID to the grid.
As you switch between the layouts in a roadmap, the filters that you select remain active.
In a roadmap scenario, you can associate a roadmap item to an existing project, a custom investment, or an idea. You will only see projects, custom investments, or ideas for which you have at least view access rights.