implementation
play

Implementation Group (WRIG) Meeting #1 16 March 2020 Agenda - PowerPoint PPT Presentation

WEM Reform Implementation Group (WRIG) Meeting #1 16 March 2020 Agenda Introduction to WRIG (Terms of Reference & Key Roles) 9.00 am Aden Barker| ETIU AEMO Implementation Delivery Team 9.30 am Stuart Featham| AEMO AEMO


  1. WEM Reform Implementation Group (WRIG) Meeting #1 16 March 2020

  2. Agenda Introduction to WRIG (Terms of Reference & Key Roles) 9.00 am Aden Barker| ETIU AEMO Implementation – Delivery Team 9.30 am Stuart Featham| AEMO AEMO Implementation – Solution Design Overview 9.45 am Thomas Killin| AEMO Implementation Planning Workshop 10.15 am Stuart Featham| AEMO 11.55 Next Steps am WRIG Meeting #1 2

  3. WRIG Introduction Terms of Reference & Key Implementation Roles Session Purpose • Discuss and agree Terms of Reference • Discuss implementation roles of ETIU, AEMO and other stakeholders WRIG Meeting #1 3

  4. WRIG Introduction Terms of Reference The Foundation Regulatory Frameworks workstream of the ETS will require significant implementation effort from market participants and institutional bodies. ETIU has convened the WEM Reform Implementation Group (WRIG) to consult on this implementation effort and support successful delivery. Purpose of the WRIG The WRIG is an expert stakeholder forum requiring participation and input from relevant industry participants to assist the Taskforce to: • develop a joint industry program plan for the transition to new market arrangements, including ongoing status assessment and reporting; • identify and manage key program risks, assumptions, issues, and dependencies; and • resolve challenges to the implementation of the new WEM by, where necessary, developing amendments to Market Rules or regulation during the transition to new market arrangements (e.g. transitional approach to compliance and monitoring, market trial obligations). A key requirement of WRIG attendees is to represent their organisation and provide specific information that will assist planning and execution. WRIG Meeting #1 4

  5. WRIG Introduction Key Implementation Roles It is imperative that there is clarity over the roles and responsibilities of different parties to ensure implementation success. This will be developed over time, with initial high level views provided below: ETIU • Ultimately accountable for program success and benefits delivery • Determining and delivering any necessary regulatory changes • Arbiter of implementation challenges/issues (e.g. timeline vs scope) AEMO • Accountable for delivery of its internal program of change • Leading joint industry planning and execution (e.g. market trials) • Provision of information to WRIG on program status and RAID items Other participants/stakeholders • Accountable for delivery of internal change programs • Provision of information to WRIG on program status and RAID items WRIG Meeting #1 5

  6. AEMO Implementation Delivery Team Session Purpose • AEMO to introduce the key team members responsible for implementation Presentation Title 6

  7. AEMO Implementation Delivery Team Program Supporting Technology Business Management Technology Team Team Team Team: Senior Program Manager, WA PSO Business Manager: Solutions: Lead: Infrastructure Stuart Featham Thomas Killin Clayton James Solution Program Markets Delivery Lead : Coordinator: Business Lead : Cyber Security Arthur Kaye Anderson Mike Hales Panggabean Change Technical Lead Solutions Management Development Program Lead : Architect : Lead : Lead TBC David Devereux Paula Welke Principal Business Test Lead Analyst : Winston Cheng WRIG Meeting #1 7

  8. AEMO Implementation Solution Design Overview Session Purpose • AEMO to provide a summary of its approach to system design • AEMO to discuss the current state of its system Options and Recommendations (OAR) Presentation Title 8

  9. AEMO Solution Design An evolving environment has shaped the approach Market Design and Rules are still being developed and will not be finalised until late 2020 , leaving approximately 30 months – from now - to analyse, implement, test and trial business • Adoption of current AEMO application processes and solutions. Resulting in … and technology components (i.e. reuse and repurpose ) where appropriate. As market design evolves, the delivery program will need to be adjusted which will add • Ongoing analysis of proposed option complexity and risk – including the possibility of will be undertaken during the CAD and rework ing processes and solutions. SAD processes to align with the evolving WEM reform process. Compressed regulatory timeframes require the WEM Reform program and associated supporting solutions to be defined prior to finalisation of the amending rules. WRIG Meeting #1 9

  10. AEMO Solution Design An evolving environment has shaped the approach Implementation Plan Market Design / Rules WEM Reform Program WRIG Meeting #1 10

  11. AEMO Solution Design Technical Implementation: Three major streams Solution • Options Analysis & Recommendations • Conceptual Architecture Design Appropriate and timely Design and • Solution Architecture Design solutions Delivery • Program Implementation Plan • Development and test environments – focussing on the Supporting Strategic alignment cloud • Platform, tools and processes Platform Leveraging AEMO capabilities • Design and Build • WEM Reform Implementation Group (WRIG) Stakeholder Common understanding • Monthly Forums Engagement • AEMO, Government, Market Participants Common plan WRIG Meeting #1 11

  12. AEMO Solution Design OAR functional analysis approach Review current Assess business Gather/confirm Establish application Develop CAD application functional impact relevant applications impact stance approach capabilities Analysis of current/future Analysis of future Reuse functions based on applications based on Functional Capability Repurpose Functional dependencies Foundation Market Foundation Market Timeliness Buy Application stances Parameters, design Parameters, design Build decisions and assumptions decisions and assumptions Define a set of tranches to Assess the current and Gather and review the current Review current application Assess each application anticipated functional list of application support the functional capabilities and and/or gaps against the four develop related Conceptual requirements based on current functional state to assess against anticipated criteria above (refer to later Architecture Designs (CAD). Foundation Market ensure the application future market rules and slides for more details) Each CAD would consider the Parameters, design decisions, landscape is correct. flexibility for further Determine the stance on each - The broader context - Function/application assumptions and current Where possible, assess augmentation, taking into existing application WEM reform thinking similar existing application account tactical/timing Develop an overall stance for specifics Areas considered included capabilities. implications. the subfunction based on the to support the creating the - Process changes Determine what is not likely to application review. CAD - Information changes change. The CADs would progress through the normal review and approval processes. Target Functional Model Target Functional Model Application assessment Application/Functional stance CAD delivery plan WRIG Meeting #1 12

  13. AEMO Solution Design Implementation options considered The system can satisfy the requirements and can be reused with minimal to no functional business Assess impact software change. Changes if any, are expected to be mainly centred on REUSE configuration, parameters and/or input data Gather/confir applications m relevant The existing system can partially handle the requirements or has the potential to be augmented/enhanced/refactored/integrated to fully satisfy the RE- PURPOSE requirements. This may entail considerable software development effort, particularly for internal systems. capabilities application Review current A commercial-off-the-shelf system (COTS) that would satisfy the requirements (including cases where customisation is required). There is a high chance that the system procured will not be exactly aligned with AEMO’s digital strategy BUY application Establish and strategic pathway. However, this could still be preferable than building stance impact new systems, depending on assessment criteria such as total cost of ownership and supportability due to technology stack, etc. This option is to develop a system that delivers the required functionality. approach Develop BUILD CAD Building ensures that the system is fit for purpose, all requirements are satisfied, and that it is aligned to AEMO’s digital strategy and technology stack. WRIG Meeting #1 13

Recommend


More recommend