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
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 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.