Cognos scorecard overview


Published on

A quick overview of the Cognos Metrics Studio interface and basic user features.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Cognos scorecard overview

  1. 1. 15 July 2010<br />1<br />Cognos Metric Studio<br />National Scorecard<br />Prototype<br />
  2. 2. 2<br />15 July 2010<br />Metric Studio Overview<br />Scorecards<br />Groups (Strategies)<br />Projects<br />Tasks<br />Trends/History<br />Actions<br />Reports<br />Diagrams<br />Details<br />
  3. 3. 3<br />15 July 2010<br />What is a Scorecard?<br /> A scorecard is a collection of performance metrics and projects designed to reflect the strategic goals of a unit in an organization. The information on a scorecard tells you how well objectives are being met by comparing planned to actual results. By using status indicators such as traffic lights, scorecard users can quickly evaluate performance.<br />
  4. 4. 4<br />15 July 2010<br />Scorecards in Metric Studio<br />Scorecards can contain other scorecards to show the organizations in the business. <br /> To best manage your metrics application, create separate scorecards for each unit in your organization. You can then apply security to each scorecard so that metrics are accessible only to specific users, groups, or roles.<br />
  5. 5. 5<br />15 July 2010<br />Scorecard Interface<br />
  6. 6. 6<br />15 July 2010<br />Groups (Strategies)<br />You can use strategies to organize metrics in a way most meaningful to users. A metric can belong to more than one strategy. Strategies are often used to represent an objective which is a statement of intended outcome for a team or a balanced scorecard view of perspectives.<br />
  7. 7. 7<br />15 July 2010<br />Projects<br />You can use projects to track long-term goals using metrics. For example, you can create a project to track your goal to improve customer satisfaction. You can use metrics such as sales, number of returned goods, and product defects to track the project.<br />
  8. 8. 8<br />15 July 2010<br />Tasks<br /> You can use a task to track a specific portion of a longer term project. For example, a project may be to implement a Risk Management Plan and a task of that project is to do a series of Business Risk Reviews<br />
  9. 9. 9<br />15 July 2010<br />History<br />The history chart shows target values, actual values, target tolerance, and any specified user-defined columns. Tolerance is the acceptable range that a result can deviate from the target. In the history chart, a green diamond represents the target value, and yellow lines represent the tolerance.<br />
  10. 10. 10<br />15 July 2010<br />Actions<br />You use an action, which is a short-term activity associated with a metric, to correct or improve the performance of the metric. For example, You can create, monitor, and update an action to replace the supplier of the failing part.<br />
  11. 11. 11<br />15 July 2010<br />Reports<br />
  12. 12. 12<br />15 July 2010<br />Impact Diagrams<br />Impact diagrams show cause-and-effect relationships between metrics. You can choose to view an impact diagram by functional impact or summary impact. Functional impact shows you the metrics that affect the metric and the metrics that are affected by the metric. Summary impact shows you impact relationships based on the scorecard hierarchy. <br />
  13. 13. 13<br />15 July 2010<br />Diagrams<br />
  14. 14. 14<br />15 July 2010<br />Details<br />Each Metric and Scorecard has a Details Tab<br />