August 2006 Note: Information contained in this deck is subject to change; estimates are for the...
-
date post
18-Dec-2015 -
Category
Documents
-
view
213 -
download
1
Transcript of August 2006 Note: Information contained in this deck is subject to change; estimates are for the...
August 2006
Note: Information contained in this deck is subject to change; estimates are for the purposes of budget planning, cost-comparison and analysis
TIO Business CaseRevised Architecture & Costs for Options 1, 2 & 3
based on changes in ACT scope
Option 1 Description:
Migration of Novell NetWare, eDirectory, GroupWise to Novell’s Linux-based platform, and migration of the City’s existing Microsoft environment to an updated Microsoft environment
Option 1 Mixed Novell & Microsoft Environment
04/18/23 - Confidential - for internal discussion purposes only - 3
Option 1 Key Assumptions1. City will continue to run a “mixed” platform that consists of Novell and Microsoft products and technologies2. City will begin migration from Novell Netware to Novell OES (Linux Kernel) beginning in 20093. City will upgrade their existing Microsoft environment to a “newer” Microsoft platform based on current Microsoft products and
technologies starting in January 20094. The “new” Novell and Microsoft products and technology will be phased in over a 4 year period of time, with basic upgrades and
maintenance completed every year thereafter, or until newer versions are deemed needed in the future5. TIO will have sponsorship from the Executive Office and Department heads. Executive Office is defined as Tim Ceis, Regina LaBelle,
and Dwight Dively (CFO)6. Depts. will be required to comply with prescribed architecture, standards and policies (Dept. exceptions may surface)7. Where feasible, server consolidation will be targeted for all new services, e.g., File/Print, Messaging, etc. (see Option 1 Architecture
slide)8. Administration responsibilities for services in the scope of TIO will for the most part remain the same9. Under Option 1, the labor costs for City Program Management and Enterprise Architecture are assumed to be the same as Option 310. Under Option 1, the labor costs for external Project Management and Technical Architecture are assumed to be the same as Option 311. Under Option 1, the labor costs for the Architecture, Design and Testing phases are assumed to be the same as Option 312. Where feasible and cost effective, Microsoft software licensing will be purchased through a 3 year Enterprise Agreement13. City will continue to pay for maintenance on Novell Open Enterprise Server (formerly Netware)14. City will continue maintenance on GroupWise15. No additional NetWare or Microsoft file servers will be installed after January 1, 2007 – assumed current environment will be sufficient
until major migration starts in 2009 (exception being annual server hardware replacement program and annual capacity expansion to existing servers)
16. Depts. have the option to load the Novell Client on client devices for access to the Novell environment17. Under Option 1, all City employees (qty. 10,000) will require a Windows Server CAL to access Corporate File shares, and for
authenticating to Active Directory (VPN, Citrix, other application access)18. Under Option 1, the native Microsoft migration tools will be leveraged for the Microsoft portion of the City’s environment19. Under Option 1, the cost estimates for Contact Management, Fax Integration and Mobile Messaging are assumed to be the same as
Option 2 and 320. Training cost estimates for Option 1 (Critical Enhancements & Additional Functionality) are assumed to be the same as Option 2 and 3
– not training for Novell base functionality required, estimated costs were allocated for limited training of Microsoft base functionality21. Microsoft Office SharePoint Server will be the information collaboration platform in Option 1, 2 or 322. Option 1 has an objective of attempting to reduce the server count while maintaining departmental administrator autonomy23. Software maintenance will be purchased with all software (Software Assurance with all Microsoft software, Software maintenance for
Novell and other 3rd parties)
04/18/23 - Confidential - for internal discussion purposes only - 4
Option 1 Key Assumptions (continued)
24. Microsoft Office Live Communications Server will be purchased and deployed for secured Instant Messaging and Live Meetings if this “Additional Functionality” item is pursued / funded
25. Microsoft Rights Management Server will be purchased and deployed for digital rights management if this “Critical Enhancement” item is pursued / funded
26. Microsoft Certificate Server will be purchased and deployed for securing server to server communication. An external provider will be used for digital certificates for the purposes of signing or encrypting electronic mail digital certificates if this “Critical Enhancement” item is pursued / funded
27. Microsoft MOM (renamed to System Center Operations Manager starting with 2007 release) will be purchased and deployed to monitor / manage all elements of the TIO infrastructure.; MOM agents will be installed on application servers at departmental option and expense. all Windows-based servers
28. Office will be funded and purchased by a separate business case and budget; a decision of which Office version deployed and when is still pending
29. Windows Vista will be funded and purchased by a separate business case and budget; a decision of when Vista will be deployed will be made after the product is released and internally tested / adopted by the City – note if City chooses not to purchase Windows licensing as part of the EA, they won’t be eligible for a Platform EA
30. City will continue to leverage their existing Desktop Management tools / platforms – upgrade cost estimates for upgrade to newest version of ZenWorks are factored in for approximately ¾ of the City devices; other Depts. device management costs will be responsibility of each Dept.
31. The City will not implement a virtual-server computing architecture for production use – only for lab and development environments where appropriate
32. Server hardware required for a City-wide “test lab” is calculated at 30% of total Server hardware cost estimate for Option 1 – it is assumed the City will also repurpose server hardware as required
33. O&M Labor estimates under Option 1 are assumed to be the same as current O&M labor up until the start of the migration in 2009 - O&M Labor will increase after migration is complete due to the need to administer, manage and maintain a larger and more complex environment that includes the addition of specific “Critical Enhancements” and / or “Additional Functionality” items that are selected by the City
34. O&M costs for Labor and Hardware/Software are calculated estimates for 1 year – the City will use this information to extrapolate O&M costs through 2016 and perform their own NPV analysis
35. In Option 1 (2009 through 2012), the assumption is that City departments' other IT work (i.e., projects and/or operational work) will be deferred in order to free up the internal labor required for TIO, and the City will not incur any backfill/augmentation costs for such internal staff
36. Labor calculations are based on 2080 man hours of work per year, using a blended hourly rate of $85 for City staff (provided by DoIT Finance), and a blended hourly rate of $175 for external staff
37. 9% Sales Tax was applied to total costs38. 50% contingency was applied to total costs
04/18/23 - Confidential - for internal discussion purposes only - 5
Option 1 - Program Timeline
Phase2
GroupWise Upgrade
NetWare & Windows
Note: "Each project has related migration tools, security and management components that are included as part of the timeline.
- Blue means "in scope" of TIO Budget and Cost Estimates
- Yellow means "out of scope" of TIO Budget and Cost Estimates
eDir & AD Upgrade
MOM & ZenWorks
File Svc. - Build, Test & Migration
AD - eDir Directory Synch
Server Mgmt Svc. - Build, Test & Implementation
PHASE IINetWare & Windows
2012
- DRAFT -
Print Svc. - Build, Test & Migration
PHASE IDirectory Svc - Build, Test & Migration
Messaging Svc - Build, Test & Migration
Office 2007 roll-out / upgrade
TIO - Planning, Architecture & Design
TIO Option 1 - Proposed Program Timeline (assumes 2009 start)
2009Project
PREPARATION / PLANNING
2010 2011
Arch - Phase 1
Data Center Facilities, Network, Storage, Power, etc. required to support TIO over Program Timeline
Migration Period
Future Microsoft Product Revision upgrades / deployment
Information Collaboration Svc - Build, Test & Migration
Desktop Mgmt Svc. - Build, Package & Test
FUTURE
ZenW Desktop
SharePoint 2007
TBD e.g. Vista & Line of Bus. Apps migration
Future Office upgradesOffice Roll-out (TIO Dependency)
Data Center Infra. (TIO Dependency)
04/18/23 - Confidential - for internal discussion purposes only - 6
Option 1 - Proposed ArchitectureNote: The Architecture illustrated is subject
to change based on the following criteria:
1. Novell and Microsoft product changes – this architecture is based on products available today; if the City adopts the newer products coming in future, the architecture will change slightly, and so will the specific server counts, placement and licensing
2. Dept. changes – certain Depts may choose to alter the proposed architecture to accommodate specific business / technical needs
3. City organizational changes – if the City adds, merges or changes Dept. structure, geographies, then the resultant underlying network and system infrastructure will need to change accordingly
4. Technical changes – if the underlying Data Center or City network infrastructure changes or is not able to accommodate the proposed architecture, modifications will be required
SMT DataCenter
(9) Dept. File Servers
SCL Remote Sites
(3) eDirectory, GroupWise, File, Print, ZenWorks(8) eDirectory
Replica Servers
Internal Firewall
Perimeter Firewall
Existing SMTP Relay Servers (SPAM)
Remote Firewalls
(8) Print Servers
(2) Clustered Dept. Print
Servers
(8) Management Servers
(4) Dept. Management
Servers
(2) BES Servers(2) FAX Servers
(2) Contact Mgmt.
Shared Novell Infrastructure
Shared Novell Infrastructure
SCL Novell
Shared City Infrastructure
62 Shared Novell / DoIT Managed Infrastructure
49 Dept. Managed Novell Infrastructure
Existing City-wide Infrastructure
SCL
(16) Novell File Servers
Shared Novell Infrastructure
SCL
SPU
SPD EOC
Shared Novell Infrastructure
Shared Novell Infrastructure
(16) GroupWise Servers (14) Dept. GroupWise Servers
Shared Novell Infrastructure
SCL
SPU
SPD(5) Dept eDirectory
Servers
SCL
SPUSPD
SCL
SPUSPD
(8) Active Directory Servers
Shared Microsoft Infrastructure
(4) Provisioning Auditing Servers
(2) DHCP/WINS
Servers(2) Password Mgmt Servers
(2) RSA Servers
Shared Microsoft
Infrastructure
Shared Microsoft
Infrastructure
Shared Microsoft
Infrastructure
Shared Microsoft
Infrastructure
(7) LCS Servers
Shared Microsoft
Infrastructure
(4) Clustered Print Servers
Shared Microsoft
Infrastructure
(4) Dept. Print Servers
SPU
SPD
(6) SharePoint Servers
Shared Microsoft
Infrastructure
(6) Clustered File Servers
Shared Microsoft Infrastructure
(4) Clustered
SQL Servers
Shared MS Infrastructure
(3) Certificate Servers
(2) MOM Servers
(2) RMS Servers
Shared City Infrastructure
(2) Active Directory, LCS Proxy
SCL MS
(3) eDirectory, GroupWise, File, Print, ZenWorks
SCL Novell
(2) Active Directory, LCS Proxy
SCL MS
(3) eDirectory, GroupWise, File, Print, ZenWorks
SCL Novell
(2) Active Directory, LCS Proxy
SCL MS
(3) eDirectory, GroupWise, File, Print, ZenWorks
SCL Novell
(2) Active Directory, LCS Proxy
SCL MS
(3) eDirectory, GroupWise, File, Print, ZenWorks
SCL Novell
(2) Active Directory, LCS Proxy
SCL MS
Boundary
North Service Center
Skagit
South Service Center
System Ctrl. Center
(2) ISA Reverse Proxy Servers (2) LCS Access Proxy Servers
Microsoft-wide Shared Infrastructure Microsoft-wide Shared Infrastructure
58 Shared Microsoft / DoIT Managed Infrastructure
26 Dept. Managed Microsoft Infrastructure
(9) Dept AD Domain Controllers
SCL SPU
SPD
(3) Dept. File
Servers
SPD
(2) Archiving Servers
Shared Microsoft
Infrastructure
04/18/23 - Confidential - for internal discussion purposes only - 7
Option 1 - Administration Model
Enterprise IT Architecture Governance
Shared City Infrastructure
Department Servers & Services
Dept. Users & Client Devices
Dept. Users & Client Devices
Dept. Users & Client Devices
Dept. Users & Client Devices
Dept Specific Infrastructure
Department Servers & Services
Department Infrastructure,
Servers & Services
DoIT provides Management & Administration
Depts. provide Management & Administration
IT Architecture Committee defines/governs Architecture & Standards
See file: TIO Mgmt & Administration Outline.doc for further details
04/18/23 - Confidential - for internal discussion purposes only - 8
Option 1 - Program DependenciesOffice Rollout• DoIT is responsible for Office Rollout to “DoIT Supported” Depts., all other Depts.
responsible for their own Office Rollout• If an EA is pursued, DoIT will be responsible for execution and procurement of Office
licenses for balance of City users (SPU and SCL have EA already)• City decision on timing for rollout of Office 2007 is still pending – recommendation is
to deploy Office 2007• Depts. will utilize current “push” deployment tools as vehicle to rollout Office package
to users• Depts. will fund external deployment assistance (contractors) as required
Data Center Infrastructure• Provides core Infrastructure for TIO, including:
– Data Center Facilities for new TIO Servers (power, HVAC, UPS/generator, racks, space, etc)
– Network Connectivity for new TIO Servers (within Data Center)– Storage (SAN) and SAN Connectivity for new TIO Servers (within Data Center)– Service Level Agreements to maintain High-Availability for TIO environment– Backup & Recovery System (hardware, software and media) for TIO environment
• SLA Metrics - monitored, managed and reporting for TIO environment• Budgeted every two years – ongoing activity• Supports growth through estimated capacity planning• Costs covered by other Dept budgets
04/18/23 - Confidential - for internal discussion purposes only - 9
Option 1 - PMO Resources
Assumption—the following resources are required for the entire duration of TIO, and will be provided from the City PMO:
• Full-time City Program Manager (48 months) – 8320hrs– Reports to City Executive Sponsors– Part of the City-wide PMO– Responsible for program schedule, milestones, budget, resource management– Loaded hourly rate of $85 = $707,200
• Full time City Enterprise Architect (48 months) – 8320hrs– Reports to City Program Manager– Responsible for technical solution, team direction / leadership and project
deliverables– Loaded hourly rate of $85 = $707,200
04/18/23 - Confidential - for internal discussion purposes only - 10
Option1 - Program Resources
Assumption—the following external resources are required for TIO Program Duration:
• External TIO Project Manager (75% for 48 months) – 6240hrs– Reports to City Program Manager– Responsible for project schedules, milestones, budget, resource management of
team members– Blended rate of $175 = $1,092,000
• External TIO Technical Architect (75% for 48 months) – 6240hrs– Reports to External PM– Responsible for technical solution, team direction / leadership and project
deliverables– Blended rate of $175 = $1,092,000
Option 2 Description:Migration of Novell NetWare, eDirectory, GroupWise, and migration of City’s existing Microsoft environment to a new standardized Microsoft platform over 4 years (starting in 2007)
Option 3 Description:Migration of Novell NetWare, eDirectory, GroupWise, and migration of City’s existing Microsoft environment to an new standardized Microsoft platform over 4 years (starting in 2009)
Option 2 & 3 Homogeneous Microsoft Environment
04/18/23 - Confidential - for internal discussion purposes only - 12
Option 2 & 3 - Key AssumptionsIf TIO is approved / funded, the following assumptions apply:1. TIO will be implemented over two budget biennia – Option 2 (2007/08 and 2009/10), or Option 3 (2009/10 and 2011/12)2. TIO will have sponsorship from the Executive Office and Department heads. Executive Office is defined as Tim Ceis, Regina LaBelle, and Dwight
Dively (CFO)3. Depts. will be required to comply with prescribed architecture, standards and policies (Dept. exceptions may surface)4. Microsoft technology (as defined in services ‘stack’) will be phased in based on two phases (see Program Timeline slide)5. Where feasible, server consolidation will be targeted for all TIO services, e.g., File/Print, Messaging, etc. (see Architecture slide)6. Administration responsibilities for services in the scope of TIO will for the most part remain the same (see Administration model slide)7. Architecture, Design and Testing for the TIO Program will begin January 2007 and continue through June 20078. Microsoft software licensing for TIO will be purchased through a 3-year Enterprise Agreement9. City will attempt to drop maintenance on GroupWise by June 30, 2009 depending on actual migration timeline10. No additional Netware file servers will be installed after January 1, 2007 - City will drop maintenance on NetWare on June 30, 200911. The Novell Client will remain on desktops during the coexistence period to support access to the Novell environment12. City will migrate print services environment that is currently hosted on Windows and Netware to Windows by the end of 200813. Office SharePoint Server will not be implemented in 2007-2008 - a strategy around the City’s use of the SharePoint environment will be developed
- Windows SharePoint Services can be deployed to support team based collaboration14. MOM will be purchased and deployed in support of all new servers implemented under TIO15. Office will be funded and purchased by a separate business case and budget; a decision of which Office version deployed and when is still
pending16. Windows Vista will be funded and purchased by a separate business case and budget; a decision of when Vista will be deployed will be made
after the product is released and internally tested / adopted by the City17. The City will not implement a virtual-server computing architecture for production use – only for lab and development environments where
appropriate18. Server hardware required for a City-wide “test lab” is calculated at 30% of total Server hardware cost estimate for Option 2/3 – it is assumed the
City will also repurpose server hardware as required19. O&M Labor estimates under Option 2 / 3 are assumed to be the same up until the start of the migration in 2007 / 2009 respectively - O&M Labor
will increase after migration is complete due to the need to administer, manage and maintain a larger and more complex environment that includes the “Critical Enhancements” and / or “Additional Functionality” selected by the City
20. O&M costs for Labor and Hardware/Software are calculated estimates for 1 year – the City will use this information to extrapolate O&M costs through 2016 and perform their own NPV analysis
21. In Option 2/3, the assumption is that City departments' other IT work (i.e., projects and/or operational work) will be deferred in order to free up the internal labor required for TIO, and the City will not incur any backfill/augmentation costs for such internal staff.
22. Labor calculations are based on 2080 man hours of work per year, using a blended hourly rate of $85 for City staff (provided by DoIT Finance), and a blended hourly rate of $175 for external staff
23. 9% Sales Tax was applied to total costs for Options 2 and 324. 30% contingency was applied to total costs for Option 2, and 40% for Option 3
04/18/23 - Confidential - for internal discussion purposes only - 13
Option 2 & 3 - Program TimelineNote: The Program Timeline below illustrates TIO projects that will deliver specific services in a specific sequence over a 4 year time period; Base
Functionality, Critical Enhancements and Additional Functionality (as defined by the ‘stack’) are components of each project. The City will choose which projects to undertake with “base functionality” and then whether they will fund/add “critical enhancements” and / or “additional functionality”. We pushed out Phase 2 to start in Jan 09 so that the budget could easily be split over the two budget biennia
Phase2
Note: "Each project has related migration tools, security and management components that are included as part of the timeline.
- Blue means "in scope" of TIO Budget and Cost Estimates
- Yellow means "out of scope" of TIO Budget and Cost Estimates
TBD e.g. Vista & Line of Bus. Apps migration
Future Office upgradesOffice Roll-out (TIO Dependency)
Data Center Infra. (TIO Dependency)
Win Srv "Longhorn" + related comp.
Deploy SMS Client / Decom. Zen
Future Microsoft Product Revision upgrades / deployment
Information Collaboration Svc - Build, Test & Migration
Desktop Mgmt Svc. - Build, Package & Test
FUTURE
SharePoint 2007 + related comp.
Proposed TIO Program Timeline (Option 2 assumes 2007 start, Option 3 assumes 2009 start)
2007Project
PREPARATION / PLANNING
2008 2009NOVELL & MICROSOFT COEXISTENCE PERIOD
2010
PHASE I
TIO - Planning, Architecture & Design
Office 200x
Arch - Phase 1
Data Center Facilities, Network, Storage, Power, etc. required to support TIO over Program Timeline
Messaging Svc - Build, Test & Migration
AD + related comp. AD - eDir Directory SynchDirectory Svc - Build, Test & Migration
- DRAFT -
Decommission Novell eDir
Decommission Novell Print
Decommission GWExchange 2007 + related comp.
Print Svc. - Build, Test & Migration
File Svc. - Build, Test & Migration
SMS v4 + related comp.
W2K3R2 + related comp.
Server Mgmt Svc. - Build, Test & Implementation
PHASE II
MOM2007+related comp.
04/18/23 - Confidential - for internal discussion purposes only - 14
Option 2 & 3 - Proposed ArchitectureNote: The Architecture illustrated is subject
to change based on the following criteria:
1. Microsoft product changes – this architecture is based on products available today; if the City adopts the newer products coming in 2007, the architecture will change slightly, and so will the specific server counts, placement and licensing
2. Dept. changes – certain Depts may choose to alter the proposed architecture to accommodate specific business / technical needs
3. City organizational changes – if the City adds, merges or changes Dept. structure, geographies, then the resultant underlying network and system infrastructure will need to change accordingly
4. Technical changes – if the underlying Data Center or City network infrastructure changes or is not able to accommodate the proposed architecture, modifications will be required
Note: original Assessment called for 114 servers, new count based on decision to not move forward with consolidation under ACT calls for 132 total new servers for TIO
SMT Data Center
(6) Clustered Dept. File Servers
SCL Remote Sites
Boundary
(2) ISA Reverse Proxy Servers
(9) AD Domain Controllers
(4) Provisioning /
Auditing Servers
Internal Firewall
Perimeter Firewall
Existing SMTP Relay Servers (SPAM)
Remote Firewalls
(2) LCS Access Proxy Servers
(7) LCS Servers
(6) SharePoint Servers
(4) Clustered Print Servers
(6) Clustered Dept. Print Servers
(3) Certificate Servers(8) SMS Servers
(2) MOM Servers
(4) Clustered
SQL Servers
(2) DHCP/WINSServers
(2) BES Servers(2) FAX Servers
(2) Password Mgmt Servers
(2) RMS Servers
(2) RSA Servers
(4) Servers hosting - AD, Exchange, File, Print, LCS Proxy, SMS
(2) ContactMgmt.
North Service Center
(4) Servers hosting - AD, Exchange, File, Print, LCS Proxy, SMS
Skagit
(4) Servers hosting - AD, Exchange, File, Print, LCS Proxy, SMS
South Service Center
(4) Servers hosting - AD, Exchange, File, Print, LCS Proxy, SMS
System Ctrl. Center
(4) Servers hosting - AD, Exchange, File, Print, LCS Proxy, SMS
City-wide Shared Infrastructure City-wide Shared Infrastructure
Shared City InfrastructureShared City
InfrastructureShared City
InfrastructureShared City
InfrastructureShared City
Infrastructure
Shared City InfrastructureShared City
Infrastructure
SCL Infrastructure
SCL Infrastructure
SCL Infrastructure
SCL Infrastructure
SCL Infrastructure
City-wide Shared Infrastructure
83 Shared City / DoIT Managed Infrastructure
49 Dept. Managed Infrastructure
Existing City-wide Infrastructure
Shared City Infrastructure
Shared City Infrastructure
SCL
SPUSPD
(6) Clustered File Servers
Shared City Infrastructure
SCL
SPU
SPD
Shared City Infrastructure
Shared City InfrastructureShared City Infrastructure Shared City
Infrastructure
(10) Exchange Clustered Servers
(8) Clustered Dept. Exchange Servers
Shared City InfrastructureSCL SPU
SPD
(9) Dept AD Domain Controllers
SCL SPUSPD
(4) Clustered
SQL Servers
Shared City Infrastructure
04/18/23 - Confidential - for internal discussion purposes only - 15
Option 2 & 3 - Administration Model
Enterprise IT Architecture Governance
Shared City Infrastructure
Department Servers & Services
Dept. Users & Client Devices
Dept. Users & Client Devices
Dept. Users & Client Devices
Dept. Users & Client Devices
Dept Specific Infrastructure
Department Servers & Services
Department Infrastructure,
Servers & Services
DoIT provides Management & Administration
Depts. provide Management & Administration
IT Architecture Committee defines/governs Architecture & Standards
See file: TIO Mgmt & Administration Outline.doc for further details
04/18/23 - Confidential - for internal discussion purposes only - 16
Option 2 & 3 - Program DependenciesOffice Rollout• Current Office version rollout is a “best practice” prerequisite for Messaging migration• DoIT is responsible for Office Rollout to “DoIT Supported” Depts., all other Depts.
responsible for their own Office Rollout• If an EA is pursued, DoIT will be responsible for execution and procurement of Office
licenses for balance of City users (SPU and SCL have EA already)• City decision on timing for rollout of Office 2007 is still pending – recommendation is
to deploy Office 2007 Depts. will utilize current “push” deployment tools as vehicle to rollout Office package to users
• Depts. will fund external deployment assistance (contractors) as required
Data Center Infrastructure• Provides core Infrastructure for TIO, including:
– Data Center Facilities for new TIO Servers (power, HVAC, UPS/generator, racks, space, etc)
– Network Connectivity for new TIO Servers (within Data Center)– Storage (SAN) and SAN Connectivity for new TIO Servers (within Data Center)– Service Level Agreements to maintain High-Availability for TIO environment– Backup & Recovery System (hardware, software and media) for TIO environment
• SLA Metrics - monitored, managed and reporting for TIO environment• Budgeted every two years – ongoing activity• Supports growth through estimated capacity planning• Costs covered by other Dept budgets
04/18/23 - Confidential - for internal discussion purposes only - 17
Option 2 & 3 - PMO Resources
Assumption—the following resources are required for the entire duration of TIO, and will be provided from the City PMO:
• Full-time City Program Manager (48 months) – 8320hrs– Reports to City Executive Sponsors– Part of the City-wide PMO– Responsible for program schedule, milestones, budget, resource management– Loaded hourly rate of $85 = $707,200
• Full time City Enterprise Architect (48 months) – 8320hrs– Reports to City Program Manager– Responsible for technical solution, team direction / leadership and project
deliverables– Loaded hourly rate of $85 = $707,200
Note: moved internal Program Mgmt and Enterprise Architect to “PMO” based on feedback from TIO Option 2/3 Review meeting on 7/20 – costs remained the same
04/18/23 - Confidential - for internal discussion purposes only - 18
Option 2 & 3 - Program Resources
Assumption—the following external resources are required for TIO Program Duration:
• External TIO Project Manager (75% for 48 months) – 6240hrs– Reports to City Program Manager– Responsible for project schedules, milestones, budget, resource management of
team members– Blended rate of $175 = $1,092,000
• External TIO Technical Architect (75% for 48 months) – 6240hrs– Reports to External PM– Responsible for technical solution, team direction / leadership and project
deliverables– Blended rate of $175 = $1,092,000
Note: increased external TIO Project Management and Technical architect from 50% over 18 months to 75% over 48 months based on feedback from TIO Option 2/3 Review meeting on 7/20 – external labor costs doubled
04/18/23 - Confidential - for internal discussion purposes only - 19
Option 2 & 3 - Architecture/DesignProject Assumptions
• Part of TIO Program – Preparation & Planning (see timeline)• 9 month effort, broken into parts phases :
– Phase 1 = 6 months, with start date of January 2007– Phase 2 = 3 months, with start date of January 2009
• Phase 1 scope - Architect, Design and conduct Design Validation Testing for:– Directory Services (AD + related components)– Messaging Services (Exchange + related components)– Print Services– Server Management Services (MOM)
• Phase 2 scope - Architect, Design and conduct Design Validation Testing for:– File Services (+ related components)– Desktop Management Services (SMS + related components)– Information Collaboration Services (SharePoint + related components)
• External Labor estimates for Phase 1:– Directory & Messaging SME (100% for 3 months) – 520hrs– Server & Management SME (100% for 3 months) – 520hrs– Test Engineer (100% for 3 months) – 520hrs– Blended labor rate of $175 = $273,000
• Internal Labor estimates for Phase 1:– SCL Architect (50% time for 3 months) – 260hrs– SCL Test Engineer (100% for 3 months) – 520hrs– SPU Architect (50% time for 3 months) – 260hrs– SPU Test Engineer (100% for 3 months) – 520hrs– SPD Architect (50% time for 3 months) – 260hrs– SPD Test Engineer (100% for 3 months) – 520hrs– SFD Architect (50% for 3 months) – 260hrs– SFD Test Engineer (100% for 3 months) – 520hrs– Parks Architect (50% for 3 months) – 260hrs– Parks Test Engineer (100% for 3 months) – 520hrs– (2) DoIT Test Engineer (100% for 3 months) – 1040hrs– Blended labor rate of $85 = $419,900
• External Labor estimates for Phase 2:– Desktop Management SME (100% 3 months) – 520hrs– Information Collaboration SME (100% 3 months) – 520hrs– Test Engineer (100% for 3 months) – 520hrs– Blended labor rate of $175 = $273,000
• Internal Labor estimates for Phase 2:– SCL Architect (25% time for 3 months) – 130hrs– SCL Test Engineer (100% for 3 months) – 520hrs– SPU Architect (25% time for 3 months) – 130hrs– SPU Test Engineer (100% for 3 months) – 520hrs– SPD Architect (25% time for 3 months) – 130hrs– SPD Test Engineer (100% for 3 months) – 520hrs– SFD Architect (25% for 3 months) – 130hrs– SFD Test Engineer (100% for 3 months) – 520hrs– Parks Architect (25% for 3 months) – 130hrs– Parks Test Engineer (100% for 3 months) – 520hrs– (2) DoIT Test Engineer (100% for 3 months) – 1040hrs– Blended labor rate of $85 = $364,650
Note: added Dept specific Test Engineers for Phase 1 and 2 based on feedback from TIO Option 2/3 Review meeting on 7/20 – internal Labor costs doubled
04/18/23 - Confidential - for internal discussion purposes only - 20
Option 2 & 3 - Directory ServicesBuild, Test & Migration Project Assumptions
• Part of TIO Program – Phase 1 (see timeline)• 12 month effort, with start date of June 2007, after Arch/Design Phase 1 is complete• Base Functionality includes production build, pre-production testing, pilot and migration of:
– AD - preparing existing City AD Domains– Add remaining (assumes 5000) users and desktops to Active Directory– Add remaining AD domain controllers– DirSynch - establishing synchronization between AD and eDirectory
• Critical Enhancements includes addition of:– AD Auditing (compliance)– Public Key Infrastructure (SSL certificates)
• Additional Functionality includes addition of:– AD Provisioning (automation of AD administration)– Password Management (client-side reduced sign-on)
• Directory Service implementation assumptions:– Starts after core AD infrastructure is in place– AD client roll-out will require “Desktop Touch” (new profile will be established)– 3rd Party Migration tools from Quest Software will be leveraged– Existing backup/restore system will have capability and capacity to support new Microsoft infrastructure
• External Labor estimates for Base Functionality Directory Services:– AD Build, Test, Migration SME (100% for 3 months) – 520hrs @ $175 = $91,000– AD Deployment Lead (100% for 12 months) – 2080hrs @ $125 = $260,000
• Internal Labor estimates for Base Functionality Directory Services:Note: assumes Build / Test completed by External Labor (above)
1. SCL AD Migration Lead (10% for 12months) – 208hrs2. SPU AD Migration Lead (10% for 12months) – 208hrs3. SPD AD Migration Lead (10% for 12months) – 208hrs4. DoIT AD Migration Lead (100% for 6 months) – 1040hrs5. (8 person) City Architecture Team (5% for 12 months) – 832hrs6. AD Client Rollout Team (4 persons - 100% for 6 months) – 4160hrs7. Blended labor rate of $85 = $565,760
• External Labor estimates for Critical Enhancements to Directory Services:– AD Auditing SME (100% for 3 months) – 520hrs @ $175 = $91,000– PKI SME (100% for 3 months) – 520hrs @ $175 = $91,000
• External Labor estimates for Additional Functionality to Directory Services:– AD Provisioning SME (100% for 3 months) – 520hrs @ $175 = $91,000– Dual Factor Authentication SME (100% for 3 months) – 520hrs @ $175 = $91,000– Password Management SME (100% for 3 months) – 520hrs @ $175 = $91,000
Note: reduced effort of internal AD Migration Lead based on reduced scope from change in Forest/Domain approach – internal Labor costs decreased by $240K
04/18/23 - Confidential - for internal discussion purposes only - 21
Option 2 & 3 - Messaging ServicesBuild, Test & Migration Project Assumptions
• Part of TIO Program – Phase 1 (see timeline)• 15 month effort, with start date of October 2007, after Arch/Design Phase 1 is complete• Base Functionality includes production build, pre-production testing, pilot and migration of:
– Exchange 2007 Server infrastructure and encryption (all Depts)– Remote access to Exchange via Web Access (OWA), Mobile Access (OMA)– Facsimile and CRM (establish new systems and integrate with Exchange for limited use)– Mobile Messaging integration (Blackberry)
• Critical Enhancements includes addition of: – Messaging Encryption
• Additional Functionality includes addition of: – Enterprise Archiving (messaging services)– Instant Messaging and Live Meetings
• Messaging Service implementation / migration:– Outlook will already be deployed to Desktops via prior Office roll-out– Exchange Server profile configuration will be automated for Outlook– GroupWise archives on file servers will be converted to Outlook PST files– 3rd Party Migration tools from Quest Software will be leveraged– Existing backup/restore system will have capability and capacity to support new Microsoft infrastructure
• External Labor estimates for Base Functionality Messaging Services:– Exchange Build, Test, Migration SME (100% for 3 months) – 520hrs @ $175 = $91,000– Exchange Deployment Lead (100% for 15 months) – 2595hrs @ $125 = $324,375
• Internal Labor estimates for Base Functionality Messaging Services:Note1: assumes Build / Test completed by External Labor (above)
– SCL Messaging Migration Lead (100% for 6 months) – 1040hrs– SPU Messaging Migration Lead (100% for 4 months) – 693hrs– SPD Messaging Migration Lead (100% for 4 months) – 693hrs– SFD Messaging Migration Lead (100% for 3 months) – 520hrs– Parks Messaging Migration Lead (100% for 3 months) – 520hrs– DoIT Messaging Migration Lead (100% for 6 months) – 1040hrs– (8 person) City Architecture Team (5% for 15 months) – 1040hrs– Blended labor rate of $85 = $471,410
• External Labor estimates for Critical Enhancements to Messaging Services:– Messaging Encryption SME (100% for 3 months) – 520hrs– Blended labor rate of $175 = $91,000
• External Labor estimates for Additional Functionality to Messaging Services:– Instant Messaging and Live Meetings SME (100% for 4 months) – 693hrs @ $175 = $121,275– Enterprise Archiving (messaging services) SME (100% for 3 months) – 520hrs @ $175 = $91,000
04/18/23 - Confidential - for internal discussion purposes only - 22
Option 2 & 3 - Print ServicesBuild, Test & Implementation Project Assumptions
• Part of TIO Program – Phase 1 (see timeline)• 12 month effort, with start date of October 2007• Includes production build, pre-production testing, pilot and implementation of:
– Print Server infrastructure (all Depts.)• External Labor estimates for Base Functionality Print Services:
– Print Service Build, Test, Migration SME (100% for 2 months) – 346hrs @ $175 = $60,550– Print Deployment Lead (100% for 4 months) – 693hrs @ $125 = $86,625
• Internal Labor estimates for Base Functionality Print Services:Note1: assumes Build / Test completed by External Labor (above)
– SCL Print Service Migration Lead (50% for 4 months) – 347hrs– SPU Print Service Migration Lead (50% for 3 months) – 260hrs– SPD Print Service Migration Lead (50% for 3 months) – 260hrs– DoIT Print Service Migration Lead (50% for 6 months) – 520hrs– (8 person) City Architecture Team (5% for 9 months) – 622hrs– Blended labor rate of $85 = $170,765
04/18/23 - Confidential - for internal discussion purposes only - 23
Option 2 & 3 – SysMgmt - ServerBuild, Test & Implementation Project Assumptions
• Part of TIO Program – Phase 1 (see timeline)• 9 months effort, with start date of October 2007• Includes production build, pre-production testing, pilot and implementation of:
– MOM 2007 Server infrastructure (all Depts.)– MOM Management Packs (as server components are deployed) including:
• IBM Server Hardware• Windows Base OS & Windows Server Cluster• Windows Active Directory• DNS, DHCP & WINS• Exchange, ISA & Live Communication Server• Windows DFS Service & DFS Replication• Print Service• Windows Rights Management Service• SharePoint• SMS
• External Labor estimates for Base Functionality Server Management Services:– MOM Build, Test, Migration SME (100% for 4 months) – 693hrs– Blended labor rate of $175 = $121,275
• Internal Labor estimates for Base Functionality Messaging Services:Note1: assumes Build / Test completed by External Labor (above)
– SCL Server Mgmt Lead (50% for 4 months) – 347hrs– SPU Server Mgmt Lead (50% for 3 months) – 260hrs– SPD Server Mgmt Lead (50% for 3 months) – 260hrs– DoIT Server Mgmt Lead (50% for 6 months) – 520hrs– (8 person) City Architecture Team (5% for 9 months) – 622hrs– Blended labor rate of $85 = $170,765
04/18/23 - Confidential - for internal discussion purposes only - 24
Option 2 & 3 - File ServicesBuild, Test & Migration Project Assumptions
• Part of TIO Program – Phase 2 (see timeline)• 18 month effort, with start date of April 2009, after Arch/Design Phase 2 is complete• Base Functionality includes production build, pre-production testing, pilot and migration of:
– File Server infrastructure (all Depts.)• Critical Enhancements includes addition of:
– Digital Rights Management platform• Additional Functionality includes addition of:
– Enterprise Archiving (file services)• File Service implementation / migration:
– Key decision for City: ‘clean-up’ data before migration, or after migration?– City Depts. will be required to add digital tags to specific files as required– Existing backup/restore system will have capability and capacity to support new Microsoft infrastructure
• External Labor estimates for Base Functionality File Services:
– File Service Build, Test, Migration SME (100% for 3 months) – 520hrs @ $175 = $91,000– File Service Deployment Lead (100% for 18 months) – 3114 @ $125 = $389,250
• Internal Labor estimates for Base Functionality File Services:Note: assumes Build / Test completed by External Labor (above)
– SCL File Migration Lead (100% for 6 months) – 1040hrs– SCL File Migration Test Engineer (100% for 3 months) – 520hrs– SPU File Migration Lead (100% for 4 months) – 693hrs– SPU File Migration Test Engineer (100% for 2 months) – 347hrs– SPD File Migration Lead (100% for 4 months) – 693hrs– SPD File Migration Test Engineer (100% for 2 months) – 347hrs– SFD File Migration Lead (100% for 3 months) – 520hrs– SFD File Migration Test Engineer (100% for 1 month) – 173hrs– Parks File Migration Lead (100% for 3 months) – 520hrs– Parks File Migration Test Engineer (100% for 1 month) – 173hrs– DoIT File Migration Lead (100% for 6 months) – 1040hrs– (2) DoIT File Migration Test Engineers (100% for 8 months) – 2768hrs– (8 person) City Architecture Team (5% for 12 months) – 832hrs– Blended labor rate of $85 = $821,610
• External Labor estimates for Critical Enhancements to File Services:– Digital Rights Management SME (100% for 3 months) – 520hrs– Blended labor rate of $175 = $91,000
• External Labor estimates for Additional Functionality to File Services:– Enterprise Archiving (File Services) SME (100% for 3 months) – 520hrs– Blended labor rate of $175 = $91,000
Note: added Dept specific Test Engineers for File Migration testing based on feedback from TIO Option 2/3 Review meeting on 7/20 – internal Labor costs increased $424K
04/18/23 - Confidential - for internal discussion purposes only - 25
Option 2 & 3 – SysMgmt - Desktop Build, Test & Implementation Project Assumptions
• Part of TIO Program – Phase 2 (see timeline)• 9 month effort, with start date of April 2009, after Arch/Design Phase 2 is complete• Includes production build, pre-production testing, pilot and implementation of:
– SMS v4 Server infrastructure (all Depts.)– SMS Functionality for Depts. to manage the following:
• Windows OS & Application Patching• Software Packaging & Distribution• Hardware & Software Inventory & Reporting• Remote Support• Software Metering & Usage Reporting
• Desktop Management implementation:– Dept File Servers will serve as SMS Distribution Points when necessary
• External Labor estimates for Base Functionality Desktop Mgmt Services:– SMS Build, Test, Migration SME (100% for 4 months) – 693hrs– Blended labor rate of $175 = $121,275
• Internal Labor estimates for Base Functionality Messaging Services:Note1: assumes Build / Test completed by External Labor (above)
– SCL Desktop Mgmt Lead (50% for 4 months) – 347hrs– SPU Desktop Mgmt Lead (50% for 3 months) – 260hrs– SPD Desktop Mgmt Lead (50% for 3 months) – 260hrs– SFD Desktop Mgmt Lead (50% for 3 months) – 260hrs– Parks Desktop Mgmt Lead (50% for 3 months) – 260hrs– DoIT Desktop Mgmt Lead (50% for 6 months) – 520hrs– (8 person) City Architecture Team (5% for 9 months) – 622hrs– Blended labor rate of $85 = $214,965
04/18/23 - Confidential - for internal discussion purposes only - 26
Option 2 & 3 – Info. CollaborationBuild, Test & Implementation Project Assumptions
• Part of TIO Program – Phase 2 (see timeline)• 12 month effort, with start date of April 2009, after Arch/Design Phase 2 is complete• Includes production build, pre-production testing, pilot and implementation of:
– Office SharePoint Server 2007 infrastructure (all Depts.)– SharePoint Functionality for the following:
• City-wide Collaboration Workspaces• Department Collaboration Workspaces• Individual Workspaces• Project & Portfolio Management (future – out of scope for TIO)
• Information Collaboration implementation:– Scope includes implementation of based SharePoint infrastructure, no data migration
• External Labor estimates for Base Functionality Info Collaboration Services:– InfoCollab/SPS Build, Test, Migration SME (100% for 4 months) – 693hrs– Blended labor rate of $175 = $121,275
• Internal Labor estimates for Base Functionality Info Collaboration Services:Note1: assumes Build / Test completed by External Labor (above)
– SCL Info Collab Lead (50% for 4 months) – 347hrs– SPU Info Collab Lead (50% for 3 months) – 260hrs– SPD Info Collab Lead (50% for 3 months) – 260hrs– DoIT Info Collab (50% for 6 months) – 520hrs– (8 person) City Architecture Team (5% for 9 months) – 622hrs– Blended labor rate of $85 = $170,765
City of Seattle
Department IT Profiles-information in the following slides is forthcoming from Depts. through John Jacobson-
04/18/23 - Confidential - for internal discussion purposes only - 28
City Light• Total number of users: 1,750• Total number of devices (desktops, laptops, tablets, mobile): 1,610• Total number of network attached printers: 315• Primary Dept (HQ) location: Seattle Municipal Tower• Location of primary server room / data center: SMT 26th floor• Number of remote sites: 5• Number of remote site server rooms: 5• IT Administration model: Decentralized• Number of IT staff: ??• Number of FTE’s can dedicate to TIO: ??
04/18/23 - Confidential - for internal discussion purposes only - 29
Public Utilities• Total number of users: 1,415• Total number of devices (desktops, laptops, tablets, mobile): 1,668• Total number of network attached printers: 298• Primary Dept (HQ) location: Seattle Municipal Tower• Location of primary server room / data center: SMT 26th floor• Number of remote sites: ??• Number of remote site server rooms: ??• IT Administration model: Decentralized• Number of IT staff: ??• Number of FTE’s can dedicate to TIO: ??
04/18/23 - Confidential - for internal discussion purposes only - 30
Police• Total number of users: 1,722• Total number of devices (desktops, laptops, tablets, mobile): 1,154• Total number of network attached printers: 191• Primary Dept (HQ) location: Seattle Justice Center• Location of primary server room / data center: SMT 26th floor• Number of remote sites: ??• Number of remote site server rooms: ??• IT Administration model: Decentralized• Number of IT staff: ??• Number of FTE’s can dedicate to TIO: ??
04/18/23 - Confidential - for internal discussion purposes only - 31
Fire• Total number of users: 1,065• Total number of devices (desktops, laptops, tablets, mobile): 470• Total number of network attached printers: 200• Primary Dept (HQ) location: Fire Station #10• Location of primary server room / data center: SMT 26th floor• Number of remote sites: ??• Number of remote site server rooms: ??• IT Administration model: Decentralized• Number of IT staff: ??• Number of FTE’s can dedicate to TIO: ??
04/18/23 - Confidential - for internal discussion purposes only - 32
Parks• Total number of users: 847• Total number of devices (desktops, laptops, tablets, mobile): 681• Total number of network attached printers: 92• Primary Dept (HQ) location: Parks and Recreation Admin Building• Location of primary server room / data center: SMT 26th floor• Number of remote sites: ??• Number of remote site server rooms: ??• IT Administration model: Decentralized• Number of IT staff: ??• Number of FTE’s can dedicate to TIO: ??
04/18/23 - Confidential - for internal discussion purposes only - 33
All other Depts. (DoIT Managed)
• Total number of users: ??• Total number of devices (desktops, laptops, tablets,
mobile): ??• Total number of network attached printers: ??• Primary Dept (HQ) location: ??• Location of primary server room / data center: ??• Number of remote sites: ??• Number of remote site server rooms: ??• IT Administration model: ??• Number of IT staff: ??• Number of FTE’s can dedicate to TIO: ??
04/18/23 - Confidential - for internal discussion purposes only - 34
City TotalsNote: TIO cost/budget derived from these totals
• Total number of users:• Total number of devices (desktops, laptops, tablets, mobile):• Total number of network attached printers: • Location of City primary data center:• Total number of remote sites:• Total number of remote site server rooms:• Total number of IT staff:• Total number of FTE’s can dedicate to TIO: