Looking for suggestions on how to incorporate goals into my data warehouse

I am building a new dimensional data warehouse for the financial institution I work for and I need to include goals for various metrics such as 'Percent of Accounts With a Checking Share',  'Average Services Per Member', etc.  The goals would be by branch location and time period.  In some cases the goal may be the same for every branch and in other cases it may be different for each branch.  I already have a dimension table for the branch information.  The design needs to be flexible so I can easily add new metrics and eventually include metrics for other business areas (lending, marketing, etc.).  I am looking for some suggestions on where the metrics and goals should be in my design.  Should I create a new dimension table which stores all of the possible metrics and then have another table with the actual goal for each branch?  How have you handled different types of goal values (percent, dollar amount, integer value)? 

Any suggestions would be greatly appreciated.

What you are describing seems to be simple MDX calculations that will be based off the information that you will have in your warehouse. For example MDX could simply divide the count of "Accounts that have a Checking Share" with the "Total number of Accounts" to get the "Percent of Accounts with a Checking Share."

As far as design considerations here's an exerpt from http://msdn.microsoft.com/en-us/library/aa902672(v=SQL.80).aspx
Calculated Measures

A calculated measure is a measure that results from applying a function to one or more measures, for example, the computed Extended Price value resulting from multiplying Quantity times Price. Other calculated measures may be more complex, such as profit, contribution to margin, allocation of sales tax, and so forth.

Calculated measures may be precomputed during the load process and stored in the fact table, or they may be computed on the fly as they are used. Determination of which measures should be precomputed is a design consideration. There are other considerations in addition to the usual tradeoff between storage space and computational time. The ability of SQL to state complex relationships and expressions is not as powerful as that of MDX, so complex calculated measures are more likely to be candidates for pre-computing if they are accessed using SQL than if they are accessed through Analysis Services using MDX.

Goals are nothing more than another set of measures.  Usually, measures show results of sales activity, but goal measures quantify the corporate goal setting activity.  Consider the following simple fact table:

-----dimensions----------------  ------facts------------------

Time       Geography   Product      ActualSales  GoalSales

DEC2011 FLORIDA      BICYCLES  1073            1200

etc.

Hope that helped!

John