Typical Request Cycle
The typical request cycle consists of:
1) The End User makes a request
2) Development of the request is scheduled
3) Developer completes the request
4) End User reviews results and is satisfied or the cycle restarts at step 1
In addition to the time actually spent in servicing the request, much time is spent in the communication and managing of the requests. In big companies, this time adds up to significant costs.
Self Serve Re-Engineers the Process
In addition to virtually eliminating development costs, InfoSilk enables the user to service there own requests. These self service features are described in the Self Serve Breeds Success and the Customization Ease & Power articles.
By enabling the business user to self-serve many of their reporting requests the savings in communication, management and development are significant. In addition the business user is happier because they get the data they need faster.
Real Cost Saving
The chart below shows the savings a customer realized by using InfoSilk. We used a conservative estimate of $150 per reporting request saved. Offloading the report customization process to the user saves real money for the organization. This is in addition to the major benefit that the user gets the data they need.