Reviewing the Business Requirements

During your definition and planning phases, you developed a set of business requirements for your EPM solution. Before moving on to the physical design of the EPM solution technology components architecture, it is recommended that you review your business requirements again.

Perhaps there was a significant time delay between the planning and implementation phases, or maybe some assumptions related to the EPM solution usage and load characteristics you made previously might not be valid anymore, and you need to review and correct them.

A part of your business requirements collected for your EPM solution was also information about

  • Number of users and their roles in your organization

  • Your projects and their characteristics

  • Usage patterns

  • Feature usage across your organization

Based on the business requirements collected, you should be able to define some sort of fundamental user profile for your EPM solution that represents your fundamental assumptions about the EPM system usage and future load. This fundamental user profile can help you as guidance when you start designing your hardware architecture. Table 6.1 represents an example of such a fundamental user profile.

Table 6.1. Fundamental User Profile Example



Number of Microsoft Project Professional 2003 users:


Number of Microsoft Project Web Accessusers: (users in all roles)


How many projects do you expect to have ongoing at any one time?


What is the average duration of a project?




What is the average size of a project (in number of tasks)?




What is the largest project you expect to have? (tasks, duration, and number ofresources on the project team)


Total number of enterprise resources (size of Enterprise Resource Pool):


Average number of resources per project (size of the project teams):




Average number of resource assignments per task:


How will we track the projects?


Backup requirements:


OLAP cube generation schedule:


Does your organization need to minimize apotential downtime for EPM solution components?


Do you plan to use WSS-based featuresissues, risks, and document libraries?


If you plan to use WSS-based features, how many items per project would you need to createsand store?



Table 6.1 is just an example. You can add your own additional specific information and expand on what a fundamental user profile means for your organization. Examples of additional information you might want to collect can be information about whether you want to make your Project Server 2003 available via the Internet or whether you need to consider implementing SSL to make your EPM solution secure.

    QuantumPM - Microsoft Office Project Server 2003 Unleashed
    Microsoft Office Project Server 2003 Unleashed
    ISBN: 0672327430
    EAN: 2147483647
    Year: 2005
    Pages: 227
    Authors: QuantumPM LLC © 2008-2017.
    If you may any questions please contact us: