Toolset Comparison Table
The table below outlines a key set of recommended good-practice elements for your toolset – and then compares a typical TCO or ROI Spreadsheet performance with that of the Lucidus Toolset.
| Recommended Good Practice | Typical TCO / ROI Spreadsheet |
Lucidus Toolset |
| Top-level value calculation results should be clearly outlined and supported with relevant graphics |  |
|
| Benefit logic strings from base customer data to projected value must be physically visible and easily understood | |
|
| Supporting graphics should be located in the correct place within their benefit logic chain | |
|
| Supporting evidence, documentation, slides, project plan, spreadsheets etc. should be available in the correct place within their benefit logic chain | |
|
| The tool should be able to demonstrate the means by which the customer will be able to track the calculated and agreed value through to actual delivery | |
|
| Both financial and non financial benefits should be evaluated and tracked to an equal degree using the same mechanisms | |
|
| Customer should be able to undertake single and multiple "What if" calculations on any base data and assumptions within – all within a protected environment |  |
|
| Customer should be able to inter-actively change data to simulate the performance of their enterprise | |
|
| Customer should be able to inter-actively change any assumptions to simulate the performance of their enterprise | |
|
| Value tracking should be predictive i.e. identify specific areas of potential value variance – whilst remedial action is still possible | |
|
| Value tracking should identify the financial effect of any variance from plans, the reason for this variance and the person (or people) responsible | |
|
| Business Case should be clearly articulated at the top level and then be capable of resolving questions by drilling down through specific benefit logic to the declared value assumptions and base data | |
|
| Risk and stakeholder management mechanisms should be available | |
|
| Business case and tracking dashboards should be made available and viewable over the web | |
|
| Automated (and flexible) Word & Excel output reporting should be available | |
|
| Automated and live process control support should be available to key individuals within a sales process and a procurement process | |
|
| This automated and live process control support should be capable of being used either within a sales process or a procurement process | |
|
| Data inputs should have secure audit facility | |
* Frequently will have single data item "What if" facility or even multiple "What if" calculations - but rarely will have the ability to undertake these fully within a safe environment.
