2. Designing and Deploying a Scalable EPM Solution Ken Toole Platform Test Manager MS Project Microsoft

3. Agenda Top 5 reasons a deployment doesn’t scale Understanding the EPM Design process Build the implementation team Logical Design of Project Server Key architecture factors for Scalability

4. Top 5 Scalability Killers 1.Inadequate network infrastructure 2.Inadequate database hardware 3.No Pilot 4.Undefined project management practices 5.Unrestricted access to data

5. EPM Initiative Development Develop vision for EPM Stake-holder identification and buy-in Collect Business Requirements EPM strategy development THEN … EPM solution design

6. EPM Design and Planning

7. Implementation Team Large scale Project Server deployments are complex and require varied expertise System Administrator Server Install, Clustering, Network Configuration, Shared Storage, Active Directory, Domain Name Resolution, Security Database Administrator DBMS installation, Drive Configuration, Tuning, Backup and Recovery, Security

8. Implementation Team Network Engineer Router and LAN configuration, load- balancing hardware, Firewall configuration, security Project Server Deployment Specialist? New training and certification exam

9. Logical Architecture Project Server IIS, ASP Pages Project Data Service XML Web Service View Processing Svc NT Service Session Mgmt Svc NT Service Scheduled Action Svc NT Service Trace Service NT Service Sharepoint “Front-End” IIS WSS DBPS Core DBPS Views DB PS Projects DB

10. Logical Architecture Project Server IIS, ASP Pages Project Data Service XML Web Service Sharepoint “Front-End” IIS WSS DBPS Core DBPS Views DB PS Projects DB

11. Capacity Planning Metrics Scalability Factors Configuration Options

12. Scalability Metrics Users per hour Max number of times a specified set of user operations (workflow) can be completed per hour. Focus on peak times like weekly time reporting. Size and complexity of data will effect this metric. Not a generalized or generic metric Cube Build Time Views Publishing throughput

13. Key Scalability Factors Network performance Database server performance Project Server security usage Project Server data usage

14. Network Performance Most frequent bottleneck for most installations Indicated by poor performance or throughput with low cpu utilization on all tiers of the application Primarily the result of latency rather than bandwidth, and the overhead associated with each network “round- trip”

15. Network Performance corrective actions Network infrastructure 100mb minimum between servers 1Gb Ethernet or fiber between server components option. Network Interface Card settings Avoid ‘hardware default’ On some systems consider 100mb/full setting instead of ‘auto-detect’ Test and consult your hardware vendor Hardware Options ‘NIC Teaming’ configurations Unisys style ‘virtual machine’ configuration (only suitable on very large hardware platforms)

16. DB Server Performance Typical DB server performance analysis and tuning. Often will present as a bottleneck after resolving any network issues Solutions are simple but can be costly in terms of hardware.

17. DB Server Performance corrective actions Data file configuration Separate transaction log and data files on separate logical drives Use db optimization scripts to separate Project Server data and indexes into multiple file groups Place index and views file groups on separate logical drives than other Project Server file groups Disk I/O hardware Use a larger number of physical disks per logical drive to ensure disk read/write activity is not bottlenecked on few physical drives Use hardware RAID controllers instead of Software RAID controllers Consult you hardware vendor

18. DB Server Performance corrective actions Server hardware Carefully test hyper-threading configurations and SQL Server settings related to threading and fibers Consider faster processors and increased number of processors Partition Project Server data onto multiple DB Servers

19. Project Server Security What data a given user has access to impacts the amount of data retrieved and transported throughout the system Use of restrictive permissions to limit the amount of data available to Project Professional users is recommended. RBS based security is optimal

20. Project Server Data Usage Project Management process and standards impact the way data is grouped in the system. Find a balance between the number and size of projects. When project sizes exceed ~ 2000 tasks consider phasing these into separate projects. Use ‘View in MS Project Professional’ feature from Project Center and enterprise outline codes to work with ‘partitioned’ projects efficiently. Avoid PM Practices that require a large number of project baseline saves. Consolidate non-project or Administrative tasks into a small number of projects

21. Front-End Configuration

22. Clustering Options Project Server WSS No Cluster Project Server WSS WSS Single Cluster WSS Project Server Dual Clusters WSS Project Server WSS PS

23. Clustering Factors WSS and Project usage balance Availability requirements Future Growth

24. Front-End Hardware RAM and Network 1 GB of RAM recommended 2 GB if using Portfolio Modeling features 2 to 4 processor commodity web servers Hyper-threading is ok HW accelerator cards can help in SSL implementations

25. Middle-Tier Configuration

26. View Processing Options Project Server Views Processor All on One Project Server Views Processor Dedicated Project Server DB Server Views Processor DB-Based

27. View Processing Factors Size of typical projects Number of Project Managers Frequency of Publish Frequency of OLAP Cube Build

28. View Processing Hardware CPU and Network Fast single processor speed Disable Hyper-threading High-speed link to DB server

29. Session Manager Options Project Server Session Mgr All on One Project Server Session Mgr Dedicated Project Server Session Mgr Multiple

30. Session Manager Factors Number of concurrent users Front-end clustering Availability

31. Session Manager Hardware RAM 1 GB + recommended Minor impact on processor utilization

32. Database Configuration

33. Database Options (Split) PS Database All on One PS Core Database PS Views Database Two-Way Split PS Web Database PS Views Database Three-Way Split PS Projects Database

34. Database - Factors Size of typical project Number of project managers Frequency of publish and cube build LOB or Custom Integration

35. Database Hardware Typical SQL Server behavior CPU, RAM, Disk I/O speed 1 GB RAM per CPU for rule of thumb Hyper-threading is ok Memory configuration Maximize memory available to SQL Avoid large amount of memory configured for fail-over

36. Find out more about Microsoft Office Project http://www.microsoft.com/office/project http://www.microsoft.com/technet/prodtechno/project http://msdn.microsoft.com/project List of newsgroups news://microsoft.public.project.pro_and_server news://microsoft.public.project Find out more about Project Management http://www.pmi.org Locate Local Microsoft Project User Groups http://www.mpug.org

37. Attend a free chat or web cast http://www.microsoft.com/communities/chats/default.mspx http://www.microsoft.com/usa/webcasts/default.asp List of newsgroups http://communities2.microsoft.com/ communities/newsgroups/en-us/default.aspx MS Community Sites http://www.microsoft.com/communities/default.mspx Locate Local User Groups http://www.microsoft.com/communities/usergroups/default.mspx Community sites http://www.microsoft.com/communities/related/default.mspx

38. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.