In This Article
1: Adding a VDT to the Library
Overview
Value Driver Trees (VDTs) can be imported into Ideas/Initiatives to save time and ensure consistency across your organization. Instead of manually creating complex VDT structures from scratch, you can reuse existing VDTs or import pre-configured VDT templates.
Why Import VDTs?
- Save Time: Reuse proven VDT structures instead of rebuilding them
- Ensure Consistency: Apply standardized calculation models across multiple initiatives
- Reduce Errors: Start with validated VDT structures
- Share Best Practices: Leverage VDTs created by other teams
When to Import vs. Create from Scratch:
- Import when you have a similar initiative or a standard template applies
- Create from scratch when your initiative requires a unique benefit calculation structure
Prerequisites
Before importing a VDT, ensure the following required permissions are enabled:
- The Role permission 'Contribute to VDT Library' is enabled (contact your system administrator for further assistance)
- Edit access to the Idea/Initiative or Value Hound VDT that you would like to import a VDT into
How to access a VDT Import
- Navigate to your Idea/Initiative or Value Hound
- Open the VDT tab using the burger menu on the left
- Locate the library icon in the VDT toolbar at the top of the page
- Click the library icon to reveal import options
1: Adding a VDT to the Library
Before you can import a VDT from the library, the VDT must first be added to the library. Follow these steps to make your VDT available for reuse:
Step-by-Step Instructions
Step 1: Access the VDT
- Navigate to the Idea/Initiative containing the VDT you want to add to the library
- Open the VDT tab using the burger menu
Step 2: Open the Library Options
- Locate the library icon in the VDT toolbar at the top of the page
- Click the library icon
- Select "Add to Library"
Step 3: Configure Library Settings
- Enter a descriptive name for the library VDT
- Add a description explaining what the VDT calculates and when to use it
Step 4: Save to Library
Click "Save" or "Add to Library"
The VDT is now available in the Import from Library dropdown
Note: You must have role VDT library management permissions to add VDTs to the library.
2: Importing from Library
The Import from Library option allows you to import VDT structures from other Ideas/Initiatives or Value Hound VDTs within your organization.
Step-by-Step Instructions
Step 1: Open the Import Dialog
- Click the library icon in the VDT toolbar
- Select Import from Library
- A pop-up dialog will appear
Step 2: Configure Import Settings
The import dialog displays the following options:
1. Replace Existing VDT Tree Checkbox
- Check this box if you want to completely replace your current VDT structure
- Leave unchecked to import into a specific parent node only
Note: Replacing the entire VDT tree will delete all existing VDT data
2. Select Import to Node
- Choose the parent node where the VDT will be imported
3. Select Source VDT from the Import from VDT dropdown
- Choose from the dropdown list of available VDTs
- Each VDT is labeled as either:
- Initiative VDT: From another Idea/Initiative
- Value Hound VDT: From the Value Hound module
Step 3: Select Parent Node to Import
- After selecting the source VDT, choose which parent node from that VDT you want to import
- You can import the entire VDT or just a specific branch
Step 4: Complete the Import
- Click Import to finalize
- The system will copy the selected VDT structure into your target node
- All node types, formulas, and KPI connections are preserved
What Happens After Import
- The imported nodes appear under your selected parent node
- KPI nodes remain connected to their original KPIs
- Constant nodes retain their values
- Variable nodes maintain their configuration
- You can immediately edit the imported structure as needed
Note: to delete an imported VDT, you will have to manually remove the imported nodes from the VDT
Next Steps
For further information on importing a VDT to an Idea/Initiative, please proceed with VDT Library and Template Management: Importing from Templates and Linked VDTs (Part 2)