A Move to Crystal Reports - Justification Doc

[qu1ncy]

Hello all you devoted CR users,

I've employed CR 8.5 as a reporting module for a single dept project within our organization, and am encouraging our senior managers to look at CR as our company wide reporting tool. I've been asked to create a doc justifying such a move. Our current reporting tools consists of Oracle Reports (in our development area) and MS Access (for our end-user produced rpts). Has anyone had to do this who can either fire a example my way of such a justification, or who knows of a white paper in existence which serves the same purpose?
Our CR area rep sent me a 'Crystal Decisions' real life 'Solution' (example) document which really doesn't meet my needs, and he's not aware of any available documentation.

Assistance with this would be valuable and appreciated.

qu1ncy

 

[cbrittain533]

I don't think you will find anything that will justify it for your company. All companies are different and therefore have different requirements. What you can do is lay out the current environment and project the impact that a Crystal implementation would have. Focus on the need for two reporting tools in your current environment and how Crystal can meet the needs of both user groups within a single tool. You can also look at the ease of distribution of the current reports and how that could be enhanced with Crystal. Two big factors for me were the ease of learning the tool for the business users and the capability of the tool to be integrated into a web environment with the Crystal Enterprise solution. I would start with why you choose Crystal for this department project instead of going with your current reporting solution.

Good luck.