1 / 16

Texas Nodal Market Implementation Program Infrastructure Update October 22, 2007

Texas Nodal Market Implementation Program Infrastructure Update October 22, 2007. INF: Project Summary - Initial Charter with Approved Changes. Project area: Infrastructure. Description: Provision of development, testing, EDS and production environments across the Program.

teneil
Télécharger la présentation

Texas Nodal Market Implementation Program Infrastructure Update October 22, 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Texas Nodal Market Implementation Program Infrastructure UpdateOctober 22, 2007 http://nodal.ercot.com 1

  2. INF: Project Summary - Initial Charter with Approved Changes Project area: Infrastructure Description: Provision of development, testing, EDS and production environments across the Program Project Manager: David Forfia Vendor(s): IBM, EMC, Oracle http://nodal.ercot.com 2TPTF Nodal Update 10/22/07

  3. EDS 4 MP SAT EDS 4 Capacity needs met? Prod #1 DevDR #2 Prod #2 Design to Min Requirements DevDisaster Site #1 Capacity Upgrade Capacity Planning Capacity Upgrade on Demand Enabled Capacity Upgrade Capacity Upgrade Capacity Upgrade Capacity Upgrade Capacity Upgrade Initial Storage Upgrade Capacity Planning INF: Project Summary - Initial Delivery Plan Q3 2006 Q4 2006 Q1 2007 Q2 2007 Q3 2007 Q4 2007 Q1 2008 Q2 2008 Q3 2008 Q4 2008 Q1 2009 Q2 2009 Q3 2009 Conceptual Design Build FAT ITEST Common model update process NMMS 6/30/08LMP Market Readiness Criteria MET 3/31/08Single Entry Model GO LIVE 12/01/08Real Time Operations GO LIVE Planning UI Operations UI EDS 3 Release Requirements, Conceptual Design Build FAT ITEST EDS 3 EDS 3 Data Validation 12/08/08Day Ahead Market/CRR GO LIVE Zonal Shutdown GO/NO GO Requirements, Conceptual Design Design, Build, Pre-FAT FAT ITEST EDS 4 Release Computing Infrastructure Design to Min Requirements Storage Software Database Licensing Strategy Portal/Integration Licensing Strategy Decommissioning plan Data Center Capacity Sufficient Power Recovered ? Data center virtualization Sufficient Power Recovered ? Colocation Existing Data Center Upgrade New Data Center Facility http://nodal.ercot.com 3TPTF Nodal Update 10/22/07

  4. EDS 4 MP SAT EDS 4 Capacity needs met? Capacity Upgrade DevDR #2 Prod #1 Prod #2 Design to Min Requirements DevDisaster Site #1 Capacity Planning Capacity Upgrade on Demand Enabled Capacity Upgrade Capacity Upgrade Capacity Upgrade Capacity Upgrade Capacity Upgrade Initial Storage Upgrade Capacity Planning INF: Project Summary – Actual Delivery Plan is slightly later than planned Q3 2006 Q4 2006 Q1 2007 Q2 2007 Q3 2007 Q4 2007 Q1 2008 Q2 2008 Q3 2008 Q4 2008 Q1 2009 Q2 2009 Q3 2009 Conceptual Design Build FAT ITEST Common model update process NMMS 6/30/08LMP Market Readiness Criteria MET 3/31/08Single Entry Model GO LIVE 12/01/08Real Time Operations GO LIVE Planning UI Operations UI EDS 3 Release Requirements, Conceptual Design Build FAT ITEST EDS 3 EDS 3 Data Validation 12/08/08Day Ahead Market/CRR GO LIVE Zonal Shutdown GO/NO GO Requirements, Conceptual Design Design, Build, Pre-FAT FAT ITEST EDS 4 Release Computing Infrastructure Design to Min Requirements Storage Software Database Licensing Strategy Portal/Integration Licensing Strategy Decommissioning plan Data Center Capacity Sufficient Power Recovered ? Data center virtualization Sufficient Power Recovered ? Colocation Existing Data Center Upgrade New Data Center Facility http://nodal.ercot.com 4TPTF Nodal Update 10/22/07

  5. Data Center virtualization was the only viable strategy to make the Nodal timeline • Move to a Collocation Site • RFP issued in October 2006 • Insufficient capacity available to support ERCOT specialized needs • Expand Existing Data Centers • Taylor • Lead times for core equipment longer than Nodal program • Austin • Existing facilities already expanded to maximum capacity • Long term viability of the facility not determined • Acquire a new Data Center Facility • Lead times for acquisition and relocation outside Nodal timelines • Currently being explored with the viability of the Austin facility http://nodal.ercot.com 5TPTF Nodal Update 10/22/07

  6. Expanding existing data center capacity is an integrated process • There are 3 components which are balanced to ensure a reliable data center • Standby Generator Capacity • Uninterruptible Power Supply (UPS) capacity • Data Center Air Conditioning (DCAC) capacity • The maximum capacity for equipment is determined by the minimum carrying capacity of any one of the components. • We have taken all steps possible to maximize the current capacity of the data centers to running at the available capacity of the UPS systems in each site. All possible near term facility upgrades have been completed. http://nodal.ercot.com 6

  7. The growth in Nodal server deployments and capacity was correctly forecast http://nodal.ercot.com 7TPTF Nodal Update 10/22/07

  8. Majority of the roadmap is completed, but not all assumptions were right http://nodal.ercot.com 8TPTF Nodal Update 10/22/07

  9. Server consolidation timeline was constrained to minimize risks • We will do this with the minimum disruption • We have a plan to: • Minimize the risk • Maximize the benefit • Lower overall costs • Safeguard Market Operations • Improve service levels • Not affect Texas Set 3.0 • However, there are always risks to be aware of in server migration • We are working with all the project managers and ERCOT committees to reduce risk and to optimize the timing. • In the process of server consolidation, one production migration was deferred and successfully rolled back two. • The net effect was a delay in final migrations and power recovery by 5 weeks. http://nodal.ercot.com 9TPTF Nodal Update 10/22/07

  10. Server consolidation will result in lower expenses during Nodal and after Nodal implementation Migration Metrics Servers Annual maintenance contracts will be cancelled on the retired database and application servers Servers will be made available on the secondary market to recoup their residual values Databases Unused or underused databases where eliminated resulting in additional licenses for use at Nodal vendor locations Database Storage Properly sizing the databases and compressing the data files for data which has been removed is resulting in a 36% reduction in used storage in production. http://nodal.ercot.com 10TPTF Nodal Update 10/22/07

  11. System requirements are driven by project detailed design documents Each project team has an assigned architect who is responsible for the architecture for the project’s deliverables that are consolidated into a deployment diagram by IDA that become individual work requests for operations to deploy the systems http://nodal.ercot.com 11

  12. Market trials and Integration testing will drive changes to the environments The assumption in the infrastructure plan is that the initial deployment specifications will have to be changed. The infrastructure technologies selected as the core for the Nodal system were picked because they adapt well to change. http://nodal.ercot.com 12

  13. Critical Path Mitigation Strategies Capacity issues – Scale Up Option Scale up options are implemented on the largest computing systems in the data center. Extra capacity is available to enable when necessary inside the system or can be added without system down time. • Provides the ability to scale up to the maximum capacity of the system to meet usage demands • System can recover from multiple component failures (CPU/Memory/Power Supply/ IO) with spare capacity within the system. • System availability above the 99.9% threshold. • Provides the ability to balance the load across all applications running on the system. • Minimum power usage configuration. http://nodal.ercot.com 13TPTF Nodal Update 10/22/07

  14. Critical Path Mitigation Strategies Capacity issues – Scale Out Option Scale out options are implemented on the smaller computing systems in the data center. Processing load is split across multiple systems to meet the business requirements. • Requires duplicate computing resources on two separate physical servers. • Provides the ability to scale up to the maximum capacity of all systems in the cluster to meet usage demands. • Classic Windows / Linux capacity expansion strategy typically with a load balancing appliance. • Provides the ability to do maintenance on a server without impacting the system. • System availability above 99.99% ERCOT will utilize both a scale up and scale out strategy to meet the business requirements of Nodal http://nodal.ercot.com 14TPTF Nodal Update 10/22/07

  15. Critical Path Mitigation Strategies Procurement and Architectural Delays http://nodal.ercot.com 15TPTF Nodal Update 10/22/07

  16. Questions http://nodal.ercot.com TPTF Nodal Update 10/22/07 16

More Related