We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAaliyah Fisher
Modified over 2 years ago
©2004 PJM 1 OASIS Phase II Approaching the Problem General Discussion on Strategy and Philosophy Andy Rodriquez - PJM Presented to the NAESB ESS and ITS February 16, 2004
©2004 PJM 2 How did we get here? OASIS 1A Fax Tagging Tagging Electronic Tagging XML Electronic Tagging OASIS Phase II/Electronic Scheduling ANOPR
©2004 PJM 3 Core Objectives Customer-driven Development Incremental Value Cost Effective Market Design Neutral Leverage Existing Tools… without being bound by those tools
©2004 PJM 4 How do we start? Begin with the ESC Use Cases Evaluate and Define OASIS functionality Identify Modular Components Determine Architecture Develop Approach
©2004 PJM 5 Architecture This should NOT necessarily be a discussion on technical issues Focus should be on deployment strategy that meets core objectives Identify modular groups where appropriate
©2004 PJM 6 Approach Should focus on incremental deliverables to provide ongoing value Phased approached to functionality will allow amortized cost burden to companies Can also be utilized to address regional diversity –If upgrades can be done on an incremental basis, we can work to ensure backward compatibility where possible
©2004 PJM 7 Ongoing Efforts IDC – Next Generation –No dependence on tags CIM Market Extensions –Coordination between RTOs PJM/MISO Congestion Management –Quantifying internal dispatch Information Technology Council –Facilitated Checkouts, Other Initiatives
©2004 PJM 8 Collaboration Should encourage participation to meet openness goals and ensure coordinated attack – minimal duplication of effort –NAESB Groups Seams Collaborative Information Technology Subcommittee –NERC Community Interchange Subcommittee Transaction Information Systems Working Group Operations Reliability Subcommittee Interchange Distribution Calculator Working Group –ISO/RTO Council Information Technology Committee
©2004 PJM 9 What is OASIS (my thoughts)? A market-oriented solution that optimizes the market interchange scheduling function –This would be developed by NAESB A reliability-oriented solution that meets the needs of the functional model with regard to operational interchange scheduling –This would be developed by NERC A set of interfaces to allow for market activity within a ISO/RTO/TP –This would be developed by the ISO/RTO/TP, but would align with the NAESB functions A market/reliability interface between the two, called the Interchange Authority, that would tie markets and reliability together –This would jointly be developed by NERC, NAESB, and the IRC
©2004 PJM 11 Suggested Timeline Spring/Summer 2004 – Develop Functional Design Documents –Detailed Scope –ESC Use Cases Summer/Fall 2004 – Develop Strategic Architecture Plan –Modules –Compatibility plans and requirements Winter 2004 – Identify Implementation Plan 2005 – Design Phase I Components 2006 – Implement Phase I Components, Design Phase II Components 2007 – Implement Phase II Components, Design Phase III Components 2008 – Implement Phase III Components
©2004 PJM 12 Initial Phases Phase I –OASIS Phase I Legacy Bridge –E-Tag Legacy Bridge (replace Authority with limited IA functionality) –IDC Architectural Split (Impact Calculator vs. TLR Process) Phase II –OASIS Phase II Functions –Legacy Bridge Upgrades –Operations Scheduling Tools (Functional Model) –Enhanced IA to Reliability Interface –IDC Next Generation Phase III –Electronic Scheduling –Market to IA Interface
©2004 PJM 13 Question Do we agree upon the core principles? –Customer-driven Development –Incremental Value –Cost Effective –Market Design Neutral –Leverage Existing Tools without being bound by those tools
©2004 PJM 14 Question Does everyone agree with these next steps? –Functional Design Work Begin with the ESC Use Cases Evaluate and Define OASIS functionality –Identify Modular Components Identify key components –Determine Architecture Group components logically based on dependencies –Develop Approach Build implementation plan for phased approach
©2004 PJM 15 Key Components Develop appropriate representation across the industry Establish governance issues –Identify leadership –Determine other key liaisons and roles –Set up meeting schedules –Agree to vision and scope –Establish milestones and deliverables
©2004 PJM 16 Questions?
©2004 PJM 1 OASIS Phase II Approaching the Problem General Discussion on Strategy and Philosophy Andy Rodriquez - PJM Presented to the NAESB ESS and ITS.
Future Of OASIS Conference March 29, 2005 Future of OASIS Conference Related Industry Initiatives NAESB - Robert Harshbarger OASIS IA Task Force and ESS.
Future of OASIS II Conference Presented by Karl Tammar – NYISO For the ISO/RTO Council March 29, 2005 ISO/RTO Activities and Initiatives.
©2005 PJM 1 Development of Wholesale Electricity Scheduling and OASIS Determining the Future Needs of the Open Access Same-time Information System Andy.
V. C. Summer Nuclear Stations Transition to a Data Centric Paradigm CMBG Atlanta June 2013.
How to commence the IT Modernization Process? 1 Tony Lester August 2011.
Systems Engineering for Systems of Systems Dr. Judith Dahmann The MITRE Corporation.
Query Health Pilots Sub-Work Group December 8, 2011.
Carnegie Mellon University CMUWorks - Staff Council Update March 15, 2012.
June 22, 2005 NAESB Board of Directors Meeting, San Antonio, Texas 1 North American Energy Standards Board Meeting of the Members NAESB Board of Directors.
Presentation Title | Date | Page 1 The Road to SOA.
Update on CAISO / PacifiCorp Energy Imbalance Market Presentation to WECC Seams Issues & Market Issues Subcommittees October 10, 2013 Jim Price, Senior.
July 14, 2009 Prepared by the North American Energy Standards Board 1 North American Energy Standards Board NAESB Review with the Demand Response Coordinating.
Efficient Dispatch Toolkit Proposal Stephen Beuning Xcel Energy, Director of Market Operations 3/11/10.
1/23/2014 9:52 AM SOA4HL7: Defining Services based on HL7 Messaging Artifacts Alan Honey, Kaiser Permanente Enterprise Architect (Based on material initially.
Standards & Interoperability Kickoff HHS – ONC September 20, 2010 Office of Standards and Interoperability 1.
SAR Overview Business Case Review Logical SARPhysical SAR Implementation Review 1.
Strategic Planning for Enterprise Application Services Joseph Percoco Rutgers, The State University of New Jersey Office of Information Technology January.
IPMA Executive Summary - October 31, 2002 IPMA Executive Summit The Enterprise Architecture of the HR/Payroll Systems October 31, 2002 FINAL NOTES AND.
1 Parallel Flow Visualization/Mitigation Proposal NERC OC Meeting June 9, 2009.
Compliance Technology Solutions NASACT Presentation Material Robert Garagiola – AERS National Technology Practice January 31 st, 2007.
FERCs OASIS II ANOPR Marvin Rosenberg Economist Division of Policy Analysis and Rulemaking Office of Markets, Tariffs and Rates Federal Energy Regulatory.
Supply Chain Management Workshop Buenos Aires, 13 de Agosto de 2004.
NERC Compliance Monitoring and Enforcement Program Update March 2008 Tim Kucey Manager - Enforcement & Mitigation.
The e-Framework Bill Olivier Director Development, Systems and Technology JISC.
1 RTO West Update & Stage 2 Filing Overview WECC Board of Directors June 5,2002 Portland,OR RTO WEST Frank Afranji.
Draft: 1/18/ NAESB Request R04016: Standard Energy Day A Problem Statement Discussion NAESB WEQ/WGQ Business Practices Subcommittee Jan
GEOSS Monitoring and Evaluation Charles S. Baker (USA) M&E WG Co-Chair Joint meeting of M&E WG and ET January 20, 2010 Geneva, Switzerland 1.
Systems Analysis and Design 8 th Edition Chapter 7 Development Strategies.
1 Implementation of Application Portfolio Management Overview July 2006.
© 2016 SlidePlayer.com Inc. All rights reserved.