The following features have not been there before...
Double Left click between ValueElements in order to move the elements further apart. In order to move elements closer together keep your Shift Key pressed down and double (left ) click as well.
Bitrix24 is a complete suit of social collaboration, communication and management tools for organizations and now integrated in ValueMiner. The so called Social Enterprise Network (SEN) will transform your sidesteps into workgroups and your Deliverables will be tracked as tasks in Bitrix24. Changes will be synchronized from ValueMiner to Bitrix and vice versa. Combining ValueMiner and Bitrix24 results in an increasing efficiency in your teams as the context is given by ValueMiner and the technical requirements for effectively execute, report and document tasks.
The new Bitrix24 integration will be the first of SEN integrations. Integrations with Atlasssian JIRA and Atlasssian Confluence will follow.
The full integration of SEN Software combines ValueMiner’s strength in strategic and planning and SENs operational excellence. Check out our user guide for the Bitrix24 Integration to find further information for your specific UseCase such as Management Facilitation or Agile Management. Please click here
The aggregation will now be available as pulse: If any value is changed in the value tree the changes will be pulsing upwards the whole tree. This functionality is also available when models are connected via sidestep. To activate the pulsing aggregation: Right click on your BA and choose „edit“. Active the tick box for „Aggregation enabled“ and save your changes in the „Main“-Menu.
Any absolute value which has been entered in the Cost/Benefit View (excluding the field „Aggregation/Distribution KPI“) and the „Actual Target Date“ will be pulsed upwards accordingly to the weights entered as long as the element is a leaf (which means that it shall not have any child or related elements).
NOTE: If values are entered in a ValueElement which has children or related elements the value entered will be overwritten by the values from the leaves.
In the editor window for the business area the normalization of weights can also be enabled via a tick box and will work for all models within the business area.
Pulsing Aggregation is the perfect add on for our Program Management Office UseCase, Business Planning, Budget Planning or else. It will generate even more Value to you and your company. Check out our user guide for the Pulsing Aggregation to find further information on the case and new functionalities. Please click here
New field: Target date Actual
Additionally to the planned target date (in the ValueView) now the actual target date can be entered. Only the field Target date Actual will also be pulsed upwards via the new aggregation.
Color Provider for Target Date
Color Provider for Target date will show whether an element is in time or delayed. The basis for this calculation builds the comparison of the two target date fields: Actual and Planned. If there are both values entered the color will be displayed. Is one value missing (e.g. Target Date Planned) the element will remain grey.
Calculation of Weights
Weight can be calculated based on the values which have been entered int he „KPI“ field. Right click in the white area and choose the last from below „calculate weights“.
A short example to show that:
There are three elements, one parent and two children.
Child #1’s KPI: 400
Child #2’s KPI: 800
When the weights are calculated, the system sums up all KPI fields from children of the same parent and calculates the weight as follows:
Weight of Child #1 = 100/Number of children * (400 / ( 400+800) ) Weight of Child #2 = 100/2 * (800 / ( 400+800) )
Side by Side Positioning of SubModels
Elements assigned to Submodels can now be displayed in two different options in their parent model. Elements from Submodels can be shown next to each other arranged accordingly to their submodels or as usual with the same x - position:
Option: Side by Side not activated
Elements have the same x - position in their parent model as in their submodel. This means if you are modeling in the submodel, in the parent model elements might overlap.
Option: Side by Side activated
Elements from the submodels are located next to each other according to the submodel which they have been assigned to.
To activate the side by side mode, right click in the white space and enable the tick box from the menu.
Feel free to download our release notes: