What is it?
The ITONICS Roadmap helps you to both master strategic planning as well as generate an overview across the innovation landscape over time.
This could include (a) future markets you identified to be attractive, (b) products and services you are working on to address that future (or existing) markets, (c) technologies you need to order to bring those products and services to market by developing them in-house or (d) working with start-ups, universities, and corporate partners.
Please note: This feature needs to be activated by ITONICS. Please contact your Customer Innovation Success Manager for further assistance.
Learn more about how:
- Create a roadmap and its layers
- Sync start and end dates (between different roadmaps)
- Creating own milestone types
- Deleting and editing roadmap scenarios
- Managing roadmap snapshots
How does it work?
While your users will later have the option to customize the roadmap to their needs, you need to provide them with a default configuration. Roadmaps can be built across different entities, i.e., separate entities can be displayed on one roadmap.
Create a roadmap and its layers
Once the roadmap feature has been activated for you, navigate to the Settings Wheel > Roadmap > All Roadmaps. You can also create single roadmaps from the 'Create button' in the main navigation bar.
A form opens from which you need to complete the fields.
A title, abstract, start, and end years are required information to enter. You can add an image and layers if you want to (optional).
To insert a high-level layer, hover over the Root field and click on the plus icon (1). You can type a new name for your layers and confirm by pressing ENTER or clicking Done. For any sub-layers, you may hover over the added (sub)layers and click on the plus icon again. To remove a layer hover over it again and click on the delete icon (2).
Following the above steps, you can go ahead and set up your layer structure for your roadmap. The below shows a best practice example connecting (innovation) projects with technologies and partners.
Press Save and Publish and let's start working with your first Roadmap.
Make sure to check the roadmap permissions within the system-level permissions.
You can access your new roadmap from the main navigation menu by hovering over the roadmap section.
Sync start and end dates (between different roadmaps)
The ITONICS Roadmap module allows you to add the same content element (e.g., projects, products, technologies) not only to one single roadmap but on multiple different roadmaps simultaneously.
ITONICS Roadmap provides you with a feature that synchronizes the start and end date of an element across different roadmaps. If not enabled, users have to add the start and end date from the Roadmap tab. If enabled, the start and end date will be kept continuous across all the different elements, and the start and end date can be also set as a normal data entry outside the roadmap tab.
This feature could be used to perform one of the following use cases:
- Your project affects multiple other activities on different roadmaps and is delayed by 2 weeks. Instead of maintaining and documenting this delay on every roadmap your project is listed on, you are simply adjusting the end date on your project and the project will update on every roadmap automatically.
- The collaboration with an important scientific partner is delayed and cannot start unless the last pending approvals on the legal side are cleared. This affects different project teams from kicking off their projects, which causes an overall delay in the planned initiative. Instead of updating all activities on the different roadmaps manually, the system will maintain the update automatically.
To enable the synced roadmap date feature, go to the Settings Wheel > Entity Configuration > Entity Configuration and navigate to the entity for which you want to enable the synced roadmap date feature by clicking the Edit pen icon:
Enable - if not already done - the Roadmap module for the element type of choice. Tick the checkbox Sync Roadmap Dates and click Save. In the field configuration, two new fields are added as roadmap sync dates. You can now adjust the field labels, tooltips, and help texts for both, the start date field and end date field, when you click on the pen icon. Note: The start and end date fields are mandatory by default.
You can also use the start and end date with the Excel import/export, but also within a workflow, for example using the date value change or convert entity trigger type. Note: When changing the start and end date via Excel import, it will change start and end date for the respective element(s) across all roadmaps as they are in sync.
Every time the start or end date is changed from the following locations, all other start and end dates are automatically updated and synchronized:
- Editing the above-generated start date field or end date field via the Edit Element functionality.
- Updating the start or end date on the roadmap visualization with drag and drop.
Note: The start and end dates cannot be edited on the Roadmap tab of an element if the sync roadmap date feature is enabled.
Note: When adding an element with synced roadmap dates, the start and end dates are updated for this element across all roadmaps. To avoid accidentally changing the dates on different roadmaps, the user has to select whether to overwrite the existing dates or apply the already set dates.
Creating own milestone types
There are default options provided in the Milestone Type dropdown, however, you can also create your own milestone types. Milestones are specific events at which you want to control the achievement of a particular task related to your content element put on the roadmap.
To do so, go to the Settings Wheel > Roadmap > Milestone Types. On the Manage Milestone Type page, click Add Milestone Type and enter your information: title, choose the entity type(s) (multi-select), and upload an icon if you prefer. When ready, click Save and Publish.
You will then find your new milestone type on the 'manage milestone type' page. Furthermore, you can delete, archive, or restore milestone types from this list. Users can then use the defined milestone types for their content elements and roadmaps.
Once you have defined the entities for which you want to provide the milestone types, a milestone configuration is added to the configuration pages of the respective entity/entities. You will find this when you navigate via the Settings Wheel > Entity Configuration > Entity Configuration to a specific entity. Click on the Pen icon to go to the edit section. Then select Milestone Configuration and the Manage Milestone Configuration interface will open.
Some fields are already listed, which you can configure by clicking the edit icon. You can not, however, delete any of these. To familiarize yourself with how to add new or existing fields, see the article Field Configuration.
Go to View Milestone Configuration to adjust the order of the fields that are displayed on the milestone preview. You can open the preview by pressing the title on the milestone bracket.
From the Form Milestone Configuration, you can drag and drop the fields according to your preferences. It affects the create/edit milestone popup.
Deleting and editing roadmap scenarios
Your users can create their own roadmap scenarios, i.e., different versions of a roadmap if you allow them to do so. You can globally manage all existing roadmap scenarios by navigating to the Scenario Manage Page via the Settings Wheel > Roadmap > Scenario Records. Here all roadmap scenarios are listed by showing the following information:
- Title - name of the scenario
- Roadmap - which roadmap is this scenario created for
- Status - different scenarios might be “Active” or already “Merged”
- Created - creation date of the scenario
- Created By - the user that created this scenario
- Visibility - who can access this scenario
- Actions - only delete is possible here
Managing roadmap snapshots
Roadmap snapshots allow you to save different states of your roadmap for later reference and backup purposes. Whenever there are major changes on your Roadmap you should take snapshots for proper documentation and later reference.
Note: When merging a Roadmap Scenario, a snapshot is taken automatically to document the previous state of the Roadmap before merging the roadmap changes from that scenario. The automatically created snapshot names follow the following convention: [yyyy-mm-dd hh:mm>] Snapshot before merging scenario <scenario name>.
The Application Owner is able to take snapshots of all existing Roadmaps with one click by navigating to the Settings Wheel > Roadmap > Roadmap Snapshots and clicking on the Create Roadmap Snapshots of all Roadmaps button. The system creates a snapshot for each existing roadmap with the following name: [yyyy-mm-dd hh:mm] Backup Snapshot.
All snapshots across all existing roadmaps can be found and managed via the Settings Wheel > Roadmap > Roadmap Snapshots. Here, all roadmap snapshots are listed showing the following information:
- Snapshot name - name of the snapshot
- Roadmap - which roadmap does this snapshot belong to
- Created At - creation date of the snapshot
- [Coming soon] Created By - the user that created this snapshot
Additionally, you can search for individual snapshots, change the sorting options and delete obsolete snapshots.
You can explore all taken snapshots of a specific roadmap by navigating to the Roadmap Settings (of the specific roadmap) > Snapshot > Show all snapshots. The system will present all taken snapshots on a timescale which can be used to explore all existing snapshots.
To access all your snapshots, click on show all snapshots. You will see that a second timeline now opens at the end of the roadmap with a list of the snapshots and a time indication.