MPUGGTA 2005 EPM SCHEDULE Brendan Giles PMP President

MPUG-GTA: 2005 EPM SCHEDULE Brendan Giles, PMP President MPUG-GTA

MPUG-GTA: 2005 EPM Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2/5/2022 * Config 1 of 3: Planning EPM Config 2 of 3: Deploying EPM Config 3 of 3: Managing EPM Share. Point for EPM Client App Boot Camp / Tips & Tricks EPM Time Tracking SQL Reporting Services for EPM Customize Project (e. g. Project Guides) Microsoft Project Future Direction OLAP Cubes & Extensions Resource Mgt with Project Server Deployment Methodologies 2

MPUG-GTA: 2005 EPM o 2005 Q 1 n n n Jan – Planning a Scaleable EPM Solution Feb – Deploying an EPM Solution Mar – Managing an EPM Solution 2/5/2022 * 3

MPUG-GTA: 2005 EPM o Each Month: n n n Part 1: Review Microsoft Project Technical Briefing 2004 Part 2: Incorporates the appropriate Microsoft On -line Book Part 3: Discusses real client examples 2/5/2022 * 4

MPUG-GTA: 2005 EPM o And now for our feature presentation! 2/5/2022 * 5

Planning a Scaleable EPM Solution Dave D’Silva VP MPUG-GTA

Planning a Scaleable EPM Solution Part 1: DC 320 Designing a scalable EPM Solution -Theory / Gotchas -- 30 min o Part 2: Six Business/Technical EPM Scenarios -Project Server 2003 Configuration Planning Guide (Microsoft On-Line Book) -- 50 min o Part 3: Real life scenarios -- 10 min o 2/5/2022 * 7

Part 1 Overview: DC 320 Designing a Scalable EPM Solution o o o Top 5 reasons a deployment doesn’t scale Understanding the EPM design process Building the implementation team Logical design of Project Server Key architecture factors for scalability Configuration scenarios 2/5/2022 * 8

Top 5 Scalability Killers 1. 2. 3. 4. 5. Inadequate network infrastructure Inadequate database hardware No pilot Undefined project management practices Unrestricted access to data 2/5/2022 * 9

EPM Initiative Development Develop vision for EPM o Stake-holder identification and buy-in o Collect business requirements o EPM strategy development o THEN … o Pick the appropriate EPM solution 2/5/2022 * 10

EPM Design and Planning 2/5/2022 * 11

Implementation Team o Large scale Project Server deployments n o Complex and require varied and enterprise level expertise System Administrator n Server Install, Clustering, Network Configuration, Shared Storage, Active Directory, Domain Name Resolution, Security 2/5/2022 * 12

Implementation Team o Database Administrator n o DBMS installation, Drive Configuration, Tuning, Backup and Recovery, Security Network Engineer n Router and LAN configuration, load-balancing hardware, Firewall configuration, security 2/5/2022 * 13

Capacity Planning Performance Metrics o Scalability Factors o Six Business Driven Configurations o 2/5/2022 * 16

Scalability Metrics o Users per hour n n o OLAP Cube build time n n o Max number of times a specified set of user operations (workflow) can be completed per hour Focus on peak times such as weekly time reporting Dependant upon size and complexity of data Not a generalized or generic metric On Line Analytical Processing Building multi-dimensional DB for pivot tables Views publishing throughput n Converting project data to consumable data is time consuming 2/5/2022 * 17

Key Scalability Factors Network performance o Database server performance o Project Server security usage o Project Server data usage o 2/5/2022 * 18

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

Network Performance corrective actions o Network Infrastructure n n o Network Interface Card Settings n n n o 100 mb minimum between servers 1 Gb Ethernet or fiber between server components option. Avoid ‘hardware default’ On some systems consider 100 mb/full setting instead of ‘auto-detect’ Test and consult your hardware vendor Hardware Options n n 2/5/2022 * ‘NIC Teaming’ configurations Massively multi-processor box (e. g. 32 processors) 20

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

DB Server Performance Corrective Actions o Data File Configuration n o 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 n n n 2/5/2022 * 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 22

DB Server Performance Corrective Actions o Server Hardware n n n 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 2/5/2022 * 23

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

Project Server Data Usage o o o 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 Administrative projects 2/5/2022 * 25

Front-End Configuration 2/5/2022 * 26

Clustering Options No Cluster Single Cluster Project Server WSS Dual Clusters Project Server WSS WSS WSS 2/5/2022 * 27 PS Project Server

Clustering Factors WSS and Project usage balance o Availability requirements o Future growth o 2/5/2022 * 28

Front-End Hardware o RAM and Network n n o 2 to 4 processor commodity web servers n o SQL Standard can handle up to 4 processor Hyper-threading is ok for client app n o 1 GB of RAM recommended 2 GB if using Portfolio Modeling features Not OK in some situations (e. g. views server) HW accelerator cards can help in SSL implementations 2/5/2022 * 29

Middle-Tier Configuration 2/5/2022 * 30

View Processing Options All on One Dedicated Project Server Views Processor DB-Based Project Server Views Processor Project Server DB Server Views Processor 2/5/2022 * 31

View Processing Factors Size of typical projects o Number of Project Managers o Frequency of Publish o Frequency of OLAP Cube build o 2/5/2022 * 32

View Processing Hardware CPU and Network o Fast single processor speed o Disable Hyper-threading o High-speed link to DB server o 2/5/2022 * 33

Session Manager Options All on One Dedicated Project Server Session Mgr Multiple Project Server Session Mgr 2/5/2022 * 34

Session Manager Factors Number of concurrent users o Front-end clustering o Availability o 2/5/2022 * 35

Session Manager Hardware 1 GB RAM + recommended o Minor impact on processor utilization o 2/5/2022 * 36

Database Configuration 2/5/2022 * 37

Database Options (Split) All on One Two-Way Split PS Database Three-Way Split PS Core Database PS Views Database PS Web Database 2/5/2022 * 38 PS Views Database PS Projects Database

Database - Factors Size of typical project o Number of project managers o Frequency of publish and OLAP Cube build o LOB or Custom Integration o 2/5/2022 * 39

Database Hardware Typical SQL Server behavior o CPU, RAM, Disk I/O speed o n 1 GB RAM per CPU for rule of thumb Hyper-threading is ok (for some components) o Memory configuration o n n Maximize memory available to SQL Avoid large amount of memory configured for fail -over 2/5/2022 * 40

Database Highlights Scaling Upwards o Windows 2000 /2003 Server (SE or EE) Ø o WSS requires Windows 2003 Server Memory (1 Gb – 2 Gb) Network Adapter (2 x 100 Mps) o Processor ( 1 – 4) (900 Mhz – 1. 5 Ghz) o 2/5/2022 * 41

Planning a Scaleable EPM Solution o Wrap up n n Part 1: DC 320 Designing a scalable EPM Solution -Theory / Gotchas -- 30 min 5 minute break 2/5/2022 * 42

Planning a Scaleable EPM Solution Part 1: DC 320 Designing a scalable EPM Solution -Theory / Gotchas -- 30 min o Part 2: Six Business/Technical EPM Scenarios -Project Server 2003 Configuration Planning Guide (Microsoft On-Line Book) -- 50 min o Part 3: Real life scenarios -- 10 min o 2/5/2022 * 43

Planning EPM: Six Scenarios Configuration Supported Scenario* Users Business Value 1 (pdf goto 61 for p. 51) 2 (pdf goto 66 for p. 56) 835 3 (pdf goto 74 for p. 64) 20, 400 4 (pdf goto 79 for p. 69) 5 (pdf goto 83 for p. 73) 6 (pdf goto 87 for p. 77) 15, 000 Medium sized org (1 K-5 K) or dept needing portfolio mgt (e. g. Nortel) Medium sized professional services organization with small short term projects (e. g. small insurance firm) Large portfolio management organization geographically distributed across time zones (e. g. Microsoft) Large professional services (e. g. banks) 725 10, 800 Resource Management centric (e. g. public service) 100 per site Service Provider (e. g. Microsoft EPM 10 sites hosted Partner) *Project Server 2003 Configuration Planning Guide. pdf) 2/5/2022 * 44

Planning EPM Scenario 1 o Medium-sized organization or a department within a larger professional services organization that uses Project Server 2003 for portfolio management Ø o Resource Management Ø o Approximately 540 Projects/year Approximately 835 Users/year Uses most features Ø 2/5/2022 * Including timesheets, document libraries, risk and issue tracking and Portfolio Analyzer, but not modeling 45

Planning EPM Scenario 1 Types of Users 2/5/2022 * Project Managers Resource Managers 50 50 Time Sheet Users PWA Viewers 335 400 46

Planning EPM Scenario 1 Types of Projects Small (1 Week) Large (8 Weeks) 2/5/2022 * 10 Tasks 10 Assignments Manage 500 / Yr 100 Tasks 20 Assignments Manage 40 / Yr 47

Planning EPM Scenario 1 Highlights o Relatively large number of small projects completed quickly o Approximately 500 users o Two Configurations: n Standard: Single Server n Alternative: Multi-Server 2/5/2022 * 48

Planning EPM Scenario 1 Configuration -- Standard Middle Tier Database Server 1 - Project Server - WSS - SM - VW - SQL Std Ed - SQL AS 2/5/2022 * 49

Planning EPM Scenario 1 Configuration -- Alternative Server 1 - WSS Server 3 - SQL SE - DB - SQL AS Server 2 - Project Server - SM - VW DB Middle Tier 2/5/2022 * 50

Planning EPM Scenario 1 Performance a) STD b) ALT Views Processing Cube Build 463 / hr 3 min 600 / hr 3 min Team Members Project Managers 292 / hr 20 / hr 380 / hr 31 / hr 2/5/2022 * 51

Planning EPM Scenario 2 o Medium-sized professional services organization or a department within a larger professional services organization Ø o Large Scale Resource Management Ø o Approximately 1, 850 Projects/year Approximately 500 Users/year Uses a limited set of features Ø 2/5/2022 * Includes document libraries and risk and issue tracking 52

Planning EPM Scenario 2 Types of Users 2/5/2022 * Project Managers Resource Managers 25 125 Time Sheet Users PWA Viewers 375 200 53

Planning EPM Scenario 2 Types of Projects Small (2 Weeks) Large (1 Year) 2/5/2022 * 10 Tasks 10 Assignments Manage 1, 800 / Yr 3, 000 Tasks 20 Assignments Manage 50 / Yr 54

Planning EPM Scenario 2 Highlights o Relatively large number of small projects completed quickly o Approximately 500 users o Standard Config: n 2/5/2022 * Two Web front-end servers (WSS vs. PS) with a common SQL Server backend 55

Planning EPM Scenario 2 Configuration Server 1 Web front end Server 3 SQL SE Views DB SQL AS Server 2 Project Server WSS DB Middle Tier 2/5/2022 * 56

Planning EPM Scenerio 2 Performance 2/5/2022 * Views Processing Cube Build 707/hr 4 min Team Members Project Managers 202/hr 33. 3/hr 57

Planning EPM Scenario 3 o Medium-sized professional services organization or a department within a larger professional services organization Ø o Large Scale Resource Management Ø o Approximately 10, 000 Projects/year Approximately 12, 000 Users/year Uses all features Ø 2/5/2022 * Does not require modeling 58

Planning EPM Scenario 3 Types of Users 2/5/2022 * Project Managers Resource Managers 1, 200 Time Sheet Users PWA Viewers 8, 400 9, 600 59

Planning EPM Scenario 3 Types of Projects Small (2 Weeks) Medium (8 Weeks) Large (1 Year) 2/5/2022 * 20 Tasks 10 Assignments Manage 1, 200 / Yr 200 Tasks 15 Assignments 20 Assignments Manage 1, 440 / Yr 1, 500 Tasks 60 Manage 72 / Yr

Planning EPM Scenario 3 Highlights o Single domain with geographically distributed users across time zones o Uses load-balancing cluster n Offloading View Processing n Partitioning the SQL Server DB to isolate traffic 2/5/2022 * 61

Planning EPM Scenario 3 DB Server 1 & 2 - Project Server - WSS Server 4 Server 3 - SQL SE - Project DB - Views DB - SQL AS - Web DB Middle Tier (Web front-end) Server 5 - VM - SM 2/5/2022 * 62 Middle Tier (OLAP)

Planning EPM Scenario 3 Performance 2/5/2022 * Views Processing Cube Build 64. 5/hr 62 min Team Members Project Managers 160/hr Not avail 63

Planning EPM Scenario 4 o Large Scale Project Management Ø o Large Scale Resource Management Ø o Approximately 30, 000 Projects/year Approximately 12, 000 Users/year Uses a limited number of features 2/5/2022 * 64

Planning EPM Scenario 4 Types of Users 2/5/2022 * Project Managers Resource Managers 600 Time Sheet Users PWA Viewers 9, 000 4, 800 65

Planning EPM Scenerio 4 Types of Projects Small (2 Weeks) Medium (2 Months) Large (1 Year) 2/5/2022 * 10 Tasks 10 Assignments Manage 12, 000 / Yr 20 Tasks 20 Assignments Manage 2, 400 / Yr 3, 000 Tasks 10 Assignments Manage 36 / Yr 66

Planning EPM Scenario 4 Highlights o Project Server and Windows Sharepoint Services in a Load Balanced Cluster o Session Manager and Views Processing Load Balance Cluster o SQL Server Cluster (2 Nodes - Active 2 Nodes Passive) 2/5/2022 * 67

Planning EPM Scenario 4 Config Middle Tier (VW SM) Server 1 - Project Server - WSS Server 2 -Views -Session - WSS Middle Tier (Web) Server 3 - Views - Session Server 5 Server 6 Server 4 - SQL EE - Views DB - Project DB (Passive) - Web DB - SQL AS 2/5/2022 * 68 DB

Planning EPM Scenario 4 Performance 2/5/2022 * Views Processing Cube Build 394/hr 63 min Team Members Project Managers 2823/hr 42/hr 69

Planning EPM Scenario 5 o Large Scale Organization Ø o Large Scale Resource Management Ø o Used for Time Capturing and Reporting 1 Task Projects are published by Resource Managers Team Members assigned at summary level tasks 2/5/2022 * 70

Planning EPM Scenario 5 Types of Users 2/5/2022 * Project Managers Resource Managers 0 2, 000 Time Sheet Users PWA Viewers 8, 000 800 71

Planning EPM Scenerio 5 Types of Projects Small (1 Month) Large (1 Year) 2/5/2022 * 1 Task 50 Assignments Manage 1, 920 / Yr 400 Assignments Manage 320 / Yr 72

Planning EPM Scenerio 5 Highlights o Project Server and Windows Sharepoint Services in a Load Balanced Cluster o Session Manager and Views Processing on 1 server o SQL Server partitioned on 2 servers 2/5/2022 * 73

Planning EPM Scenerio 5 Middle Tier (VW SM) Server 2 - Project Server - WSS Server 1 - Project Server 3 - Views Processing - Session Manager - WSS Middle Tier (Web) Server 4 - SQL SE - Project DB - Web DB 2/5/2022 * 74 - SQL SE - Views DB - SQL AS DB

Planning EPM Scenerio 5 Performance Views Processing Cube Build 221/hr 53 min Team Members Project (Resource) Managers 4500/hr 48. 8/hr 2/5/2022 * 75

Planning EPM Scenerio 6 o Hosted Deployment Ø o Designed to accommodate multiple sites Ø o Hosts sites for departments / divisions Each site may have different needs May require all project server features 2/5/2022 * 76

Planning EPM Scenerio 6 Types of Users 2/5/2022 * Project Managers Resource Managers 30 10 Time Sheet Users PWA Viewers 50 100 77

Planning EPM Scenerio 6 Types of Projects Small (2 Weeks) Large (2 Months) 2/5/2022 * 10 Task 200 Tasks 30 Assignments Manage 30/ Yr 600 Assignments Manage 7/ Yr 78

Planning EPM Scenerio 6 Highlights o Project Server and Windows Sharepoint Services on separate Load Balanced Clusters o Session Manager and Views Processing on separate servers SQL Server partitioned across 3 servers o SQL Analysis Services on its own server o 2/5/2022 * 79

Planning EPM Scenerio 6 Middle Tier (VW, SM) WSS WSS Views Processing Project Server Session Manager Project Server Middle Tier (Web) DB SQL AS SQL SE Web DB Views DB Project DB 2/5/2022 * 80

Planning EPM Scenerio 6 Performance Views Processing Cube Build 350+/hr 30 min Team Members Project Managers 6000+/hr 80/hr 2/5/2022 * 81

Planning a Scaleable EPM Solution o Wrap up n Part 2: Six Business/Technical EPM Scenarios -- Project Server 2003 Configuration Planning Guide (Microsoft On-Line Book) -- 50 min 2/5/2022 * 82

Planning a Scaleable EPM Solution Part 1: DC 320 Designing a scalable EPM Solution -Theory / Gotchas -- 30 min o Part 2: Six Business/Technical EPM Scenarios -Project Server 2003 Configuration Planning Guide (Microsoft On-Line Book) -- 50 min o Part 3: Real life scenarios -- 10 min o 2/5/2022 * 83

Planning a Scaleable EPM Solution o Part 3: Real life scenarios -- 10 min n Discussion 2/5/2022 * 84

Planning a Scaleable EPM Solution o Wrap-Up n n Part 1: DC 320 Designing a scalable EPM Solution -Theory / Gotchas -- 30 min Part 2: Six Business/Technical EPM Scenarios -- Project Server 2003 Configuration Planning Guide (Microsoft On-Line Book) -- 50 min Part 3: Real life scenarios -- 10 min Where to go for more info 2/5/2022 * 85

Planning a Scaleable EPM Solution Thank you o Questions o n n o Dave D’Silva dave@imsg. ca Brendan Giles brendan. giles@sympatico. ca Next Steps n n Join MPUG February & March MPUG Presentations 2/5/2022 * © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes 88 no warranties, express or implied, in this summary.