Performance Point Server

Microsoft has recently announced changes to its BI Roadmap, including shifting PerformancePoint Server into SharePoint Server.

PerformancePoint Server 2007 SP3 will be released during the summer, after which Microsoft will stop all further investments in the standalone versions of PPS. The decision comes after in-depth product roadmap reviews and customer feedback. This shift will make the scorecard, dashboard, and analytical capabilities of PerformancePoint available to all users in an organization.

A more detailed product roadmap will be revealed at Convergence 2009 New Orleans... just another reason to attend!

DIT uses customized .NET collections for retrieval of the dimension data from the source systems. Alongside already mentioned default dimensions, you can define any number of custom dimensions. In order to populate the required custom collection (dimension) with the corresponding source system data you first need to retrieve it from the source system. Often, source system stores the financial data in the database, and you can access it using the .NET data access classes and methods. Since memory is not an infinite resource, you should use SqlDataReader for data extraction. Once you obtain the data from the source system you can store it in the memory stored customized collection. All dimension data is stored in memory stored customized collections and overridden GPProvider methods are used for the dimension data retrieval.

Balance data is retrieved based on the carefully crafted balance request. Balance request contains a number of account and balance criteria. Your provider's task is to build (based on the submitted criteria) and execute the appropriate SQL query on the source system data. Unlike dimension data, balance data is retrieved via customized SqlDataReader object. For example, an ordinary company can store tens of thousands of transactions in its source system. Again, since memory is not an infinite resource, data is read directly from the source system database. DIW reads it using the returned customized data reader and populates it directly into the PPS database hence, no memory is used during the data extraction. By far, balance request functionality implementation is the most challenging part of the custom provider development. In order to successfully implement it, you need the thoroughly analyze the source system data. Also you should write unit tests for each of the overridden GPProvider methods, since balance request criteria testing can easily turn into a time consuming nightmare.

View Part 2 of this series.

The Microsoft Downloads Center has the following Microsoft Office PerformancePoint Server 2007 SP2 products available for download:

• PerformancePoint Server 2007 SP2 (64bit)
• PerformancePoint Server 2007 SP2 (32bit)
• PerformancePoint Server 2007 Management Reporter SP2

Note from the PerformancePoint Team Blog:
We are also releasing a script from MS Downloads, which PerformancePoint Server Planning customers who have installed builds 3.0.3999.1 or higher are required to run before installing PerformancePoint Server 2007 SP2. PerformancePoint Server customers who are deploying SP2 with Microsoft SQL Server 2008 must also install four SQL Server 2005 CU9 redistributables, which are available for download as hotfixes from the SQL Server 2005 CU9 site. For details, see the PerformancePoint Server Planning Readme.

Data Integration Toolkit (DIT) was introduced in the part 1 of this post. In part 2 we will focus on how it can be used to create a custom provider for your source system.

By now, it is assumed that you have downloaded and installed the DIT on your development system. If you look at the DIT assemblies, you will find a number of general ledger (GL) related data collections.

The main task of the provider you are going to create is going to be the retreival of GL data from your source system. This data will be stored in those GL related data collections. The main DIT class, which is called from the PerformancePoint Server (PPS) Data Import Wizard (DIW) and used for preparation of the source system data for the PPS, is the GLProvider class. You can find it in the Microsoft.Dynamics.GP.PerformancePointServer.GLDataProvider.dll DIT assembly.

To start building your custom data provider you will have to inherit the GLProvider class and override a number of its methods. The GLProvider class contains override methods for the extraction of the default dimensions. Some of those dimensions are calendars, entities, currencies account types, account segments etc. In addition to this, any number of custom dimensions can be specified. You will find more info about the implementing of the various dimension retrieval methods in the Part 3 of these posts.

Microsoft issued a Dynamics GP to PPS integration provider. This provider is created using the DIT and it is extracting data from Dynamics GP and importing it into PPS. You can look into it to find out what you're striving for and what a custom provider should look like.

If you want to read more about it, you can find a review here.

Direct or FDM 7.0 data warehouse? That is the question.

You may fall into one of the following Microsoft FRx partner profiles: an existing ERP partner of Microsoft FRx, a new prospective ERP partner, or a customer who (instead of FRx) desires to use PerformancePoint Server and Management Reporter for your enterprise reporting needs.

If you fit one of these profiles and are considering PerformancePoint Server / Management Reporter, you may be asking yourself the question, “Is it right for me to develop a data provider integration to PerformancePointserver and Management Reporter?”

At Merit Solutions, based on our findings and integration development experience with PerformancePoint Server and Management Reporter, there appear to be three different types of consumers pursuing answers to this question. 

1. Current FRx partners with an FDM 7.0 (Financial Data Mart) integration to FRx. 
2. Current FRx partners with a direct integration between their system and FRx. 
3. ERP software companies or their customers who were not FRx partners but need a management reporting solution.

I need to create a Time dimension that starts on 1/1/1970 to load historical data. However, when I create the PerformancePoint calendar, I can't go back more than 25 years from now. I also tried to sync the dimension to staging so that I could load it there, but then I can't load it back into production because the 'Load this dimension from Staging Area' is not available. Does anyone have a work around for this? It is a serious matter for me. Thanks, ceecee

Microsoft Office Performance Point Server is a BI software product from Microsoft. It is fully integrated with other Microsoft Office products including Excel, Visio, SQL Server, and SharePoint Server. The software itself allows customers to monitor, analyze, and plan their business as well as drive alignment, accountability, and actionable insight across the entire organization. Performance Point Server is using Data Integration Framework to retrieve the data from diferent source systems. This framework enables the development of data providers that target various source systems (like Dynamics AX, Dynamics GP, or other third party source system) and surface data to consumers in a standardized and meaningful way. In the following posts, I will try to illustrate PPS Data Integration Toolkit architecture and the way of using it for development of custom data providers. For more information you can read Tim Kent's blog or search through PPS related blogs.

Merit Solutions, Inc. -

The Top 10 Benefits of Microsoft Office PerformancePoint Server 2007 can help transform your business process and turn your data into a competitive advantage:

1. A complete and integrated performance management solution
2. Performance management for all business users
3. Monitoring, analyzing, and planning across the entire organization
4. Advanced analytic and visualization capabilities
5. Aligned and integrated corporate planning
6. Shorter budgeting cycles and broader contribution
7. Accountability from the individual to the enterprise
8. Cross-enterprise view
9. Enhanced partnership between IT and business analysts
10. Built on the Microsoft Business Intelligence platform

For more information on each of the benefits, read the full article: PerformancePoint Server 2007 Top 10 Benefits.