1. Common ISO/RTO Architecture ISO/RTO Information Technology Committee Walter A. Pfuntner, Jr, PhD, PE Chairman, ITC Architecture Working Group {wpfuntner@nyiso.com}

2. Common ISO/RTO Architecture Common Architecture Assumes similar business drivers Use of identical components and sub-systems Could not develop consensus on a component level Consensus on a technology level was possible Developed a Reference Architecture Information Technology Committee

3. The Reference Architecture What is it? A high-level pictorial representation of an ideal technology state A representation of the components and their inter- relations making up an ISO/RTO IT system Covers 6 areas of interest (domains) Security, Application, Data, Infrastructure, Platform, Redundancy Input from several ISOs AESO, CAISO, ERCOT, IMO, ISONE, MISO, NYISO, PJM, SPP Information Technology Committee

4. Benefits of a Reference Architecture Unified voice of ISO/RTO for vendors, customers and regulators re: A peer reviewed architecture Best practices based on experience Clarify expectations for vendors Provide a jumpstart for ISO/RTOs without an Enterprise Architecture Plan Information Technology Committee Reference Architecture Benefits

5. Reference Architecture Domains 6 domains Platform Infrastructure Application / Integration Data Security Redundancy Information Technology Committee

7. Reference Architecture Domains Security The Security Domain identifies the hardware, software and protocols that facilitate appropriate access to information while ensuring integrity and availability. Firewall Cisco, Nortel, Nokia Anti-virus Trend Micro Officescan, Sophos, McAfee Federated Identity RSA Directory Services iPlanet LDAP, Microsoft Active Directory Information Technology Committee

8. Reference Architecture Domains Application The Application / Integration Domain identifies key Commercial Off-the-Shelf software, infrastructure software, and custom designed software. It also highlights key intra- and inter-ISO integration software and protocols. Application Servers Microsoft IIS, BEA Weblogic Web Servers Microsoft IIS, Apache EAI Busses TIBCO, Vitria Information Technology Committee

9. Reference Architecture Domains Data The Data Domain identifies key data related technologies to be used by an ISO/RTO. Database, Data Warehousing and data manipulation products and protocols are featured. The information lifecycle is highlighted as well. Transactional Data Stores Oracle, Microsoft SQL Server Historical Data Stores Oracle, PI Query Interfaces Crystal Reports, Oracle Discoverer, Business Objects Information Technology Committee

10. Reference Architecture Domains Infrastructure The Infrastructure Domain provides for all aspects of the communications infrastructure for a distributed computing environment. This includes logical elements, physical hardware components, carrier services and protocols. The scope of the architecture includes voice, data, and video services. Routers/Switches CISCO PBX Nortel, Siemens SAN Switches Brocade, McData Information Technology Committee

11. Reference Architecture Domains Platform The Platform Domain defines the technical computing components of the infrastructure including client and server hardware platforms, operating systems, local and networked storage systems, and physical interfaces. System Management HP OpenView, IBM Netview, BMC Patrol Enterprise Backup IBM Magstar, StorageTek Blade Servers IBM, Sun, HP Information Technology Committee

12. Reference Architecture Domains Redundancy and Failover The Redundancy domain identifies the level of redundancy for various types of systems and data. Level of Redundancy Standard, High, Ultra, Continuous Environments Supported Production, Staging, QA, Development, Training Systems EMS, Market, Back Office Information Technology Committee

13. ISO/RTO Inventories Cross-referenced with the ISO/RTO IT Inventory Purpose / Benefits The RA acts as a visual portal to the IT Inventory Quickly identify common technologies across the ISO/RTOs Document target environment for vendors On a need-to-know basis, identify specific products/technologies/versions in use Provide a sanity check for architecture activities at each ISO/RTO Information Technology Committee

14. Next Steps Develop material for a variety of audiences Regulators & Public Utility Commissions Software/Hardware vendors & consultants Market Participants and Business Partners Provide an easy way for ISO/RTOs to maintain the inventory online (web based) Provide the ability to query the Reference Architecture / Inventory to provide varying levels of detail Information Technology Committee