What do we mean by 'proof'?
The purpose of our Proof of Concept Service is to demonstrate that Cognos Business Intelligence tools will deliver measurable business benefit on your specific project. Such proof may be achieved by:
  -Prototyping one or more of the 24 Ways, using some of your existing data.
  -Showing how Decision Flow techniques can empower your decision-makers.
  -Easing concerns about technical complexity or challenging data volumes.
Speed is of the essence with POCS. The point is not to end up with the first phase of an implementation, but to prove the worth and practicality of a selected application. The knowledge gained will be invaluable in developing your full BI solution.

How evidence breeds confidence
As well as generating confidence in the value and workability of a particular BI application, the POCS 'Quick Win' prototype provides many other benefits, including:
  -Project risk reduction, by identifying issues early.
  -Analysis of user requirements at the right level.
  -Appropriate, cost effective use of Cognos tools.
  -Opportunity to build quality metrics into project.
  -A valuable means of presenting BI to senior management for approval. A way of involving users,
   establishing realistic expectations and gathering their 'buy-in'.
  -A clear understanding of data staging requirements.

Gathering the proof
However large or small your project, every Proof of Concept Service follows the same basic pattern. This starts with a scoping exercise, followed by a number of days developing your agreed prototype and reviewing the lessons learned.

The Scoping Day is taken up with a BI consultant working with potential users of the application to establish the "sweet spot" and agree the scope of information to be delivered. The consultant will also work with your IT team to identify any potential risk.

Prototyping Days are developed to the Rapid Application Development of your prototype. There may be a pause after the Scoping Day to allow any identified requirements (developer training, hardware acquisition etc) to be addressed. Thanks to the speed with which BI applications can be built, there will be time for a number of iterations and refinements. To benefit from accelerated skills transfer, at least one of your nominated developers should be allocated to work alongside the BI consultant throughout. Also, users who take part in the scoping should be on hand to verify the application as it evolves, and to discuss opportunities or unforeseen issues that may arise. Ideally, Prototyping Days should occupy a single timeslot.

The Presentation/Review Day begins with a demonstration to show your decision-makers how the prototype will enable them to achieve their objectives, as agreed during the Scoping Day. The Review highlights both the opportunities presented and issues, which need to be addressed to deliver the eventual solution. Every POCS ends with an agreed set of next steps.


What the Proof on Concept Service delivers
  -A demonstrable application. It belongs to you and should be made available to users,
   though it must be impressed on them that it is only a prototype.
  -Excerpts from the Reports and Views compiled during the Rapid Application Development.
  -Accelerated skills transfer. Your developers will have gained valuable, hands-on rapid development experience in their own environment.
  -A Proof of Concept Service Call Report, itemising issues opportunities and the way forward.
  -Confidence that the tools are appropriate for the solution and that BI Inform is the right partner for you and your company.
You need to remember that the Proof of Concept Service is not a substitute for product training.