Defect and Enhancement Severities Levels

Slides:



Advertisements
Similar presentations
By Saurabh Sardesai October 2014.
Advertisements

Performance Monitoring All All Contracts require basic monitoring once awarded. The Goal of contract monitoring is to ensure that the contract is satisfactorily.
SafeZone® patent pending 1 Detect. Inform. Prevent. NERC Physical Security Standards and Guidelines SafeZone® Detect. Inform. Prevent.
PROJECT RISK MANAGEMENT Presentation by: Jennifer Freeman & Carlee Rosenblatt
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
Project Management By: Dr Madhu Fernando Project Risk Management
Private & Confidential1 (SIA) 13 Enterprise Risk Management The Standard should be read in the conjunction with the "Preface to the Standards on Internal.
Real Time Settlement Timeline Workshop Debrief To TAC 11/29/2012 Evaluation and consideration of reducing the RT Settlement Timeline Jim Galvin- CSWG Chair.
ERCOT SCR745 Update ERCOT Outage Evaluation Phase 1 and Phase 2 TDTWG April 2, 2008.
OIRM Business Process Planning Overview for Business & Operations Advisory Committee May 27 – 28, 2015.
MIG TF Voting Items Market Participant Notification Period (Transmission outage) – =1 Year Interconnection Date for Protocol Considerations – First Interconnection.
Place your chosen image here. The four corners must just cover the arrow tips. For covers, the three pictures should be the same size and in a straight.
Inspection and Review The main objective of an Inspection or a Review is to detect defects. This activity and procedure was first formalized by Mike Fagan.
A JSJ Business Supplier Management Review.
Statement of Auditing Standard No. 94 The Effect of Information Technology on the Auditor’s Consideration of Internal Control in a Financial Statement.
Disaster Recovery Planning (DRP) DRP: The definition of business processes, their infrastructure supports and tolerances to interruptions, and formulation.
Day Ahead Market QSE’s Credit Requirements Concerns and Solutions August 14, 2008.
The Texas Nodal Market Trip Doggett ERCOT Interim President and Chief Executive Officer Mike Cleary ERCOT Chief Technology Officer Executive Briefing 28.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)
Renewables IPP frameworks for successful PPAs Dr Muriel Watt Head, Energy Policy & PV.
Principles for Recovery and Resolution of a Financial Market Infrastructure ACSDA Senior Leadership Summit – November 16 & 17, 2015.
NERC Lessons Learned Summary
Exceptional Fuel Costs in LMP
Managing Expectations and SLA
Risk Management DIA Working Group 22 May 2017.
Unit 1 What is Project Management
Phase Angle Limitations
Managing Expectations and SLA
2011 Prioritization Update to Market Subcommittees
The Continuum of Interventions in a 3 Tier Model
Reportable Events & Other IRB Updates February 2017
12.2 Conduct Procurements The process of obtaining seller responses, selecting a seller and awarding the contract The team applies selection criteria.
Software Project Management
Operational Risk.
Wholesale Market Reform
Briefing on 2017 CAISO Policy Initiatives Roadmap
ISO New England System R&D Needs
AgilizTech Support Desk Overview
Description of Revision
Auditing Application Controls
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Risk Criteria and Guidance_
Investing in Innovation (i3) Fund
SAI Jamaica’s SDG Audit Coverage
Software Project Management (SPM)
Amendment Invoice Task Force Progress Report
First Quarter Fiscal Year 2016
What a non-IT auditor needs to know about IT & IT controls
PRIDe in Gas Model workshop
Benefits of New England’s Proposed Capacity Market
Inspection and Review The main objective of an Inspection or a Review is to detect defects. (Not for Giving Alternative Solutions) This activity and procedure.
Recovery of Costs due to Invalid Ex-Ante Contracted Quantities in Imbalance Settlement 12th December 2017.
Amendment Invoice Task Force Progress Report
Statement of Auditing Standard No. 94
Amendment Invoice Task Force Progress Report
Risk management.
Project Name - Testing Iteration 1 UAT Kick-off
Amendment Invoice Task Force Progress Report
Third-party risk management (TPRM)
Amendment Invoice Task Force Progress Report
Risk management.
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
RISK RATING GUIDE APPENDIX C LIKELIHOOD RATING Rating Description
{Project Name} Organizational Chart, Roles and Responsibilities
Enabling Large Scale Utilisation of Class 3
Data Security and Protection Toolkit Assurance 2018/19
The opportunity of a lifetime must be seized within the lifetime of the opportunity.
IT Updates Maryland Health Benefit Exchange Board Meeting
Project Name Here Kick-off Date
Presentation transcript:

Defect and Enhancement Severities Levels Severity 1: Critical - Defects or Enhancements that cause or resolve the following: Environment or System Outage: one or more systems, or a function within a system, are rendered inaccessible or stop functioning all together (e.g. Markets UI, Outage) Environment or System Instability: one or more systems are experiencing uncontrolled data loss, memory leakage, component locking ,or similar error resulting in intermittent volatility of the system (e.g. Markets Settlements unexpectedly “dumps” all data older than seven operating days) Impacts to key Participant Milestones: a systems issue which impacts our ability to meet SPP milestone obligations to Participants (e.g. Conduct Annual TCR Auction Milestones, Onboarding dates for new Market Participants, Conduct Phase II Market Participant Testing Milestones). Business Owners, Project Managers, and/or Testing Leads should be prepared to escalate these issues to Program Leadership with the recommendation to potentially defer the external Milestone if the issue is not resolved prior to the target date Risk to meeting SAE16 or CIP Standards (e.g., logs not updating, lack of logging where expected, system monitoring failure, etc.) or Risk to meeting SPP Tariff and Protocols High Risk Vulnerabilities such as unauthorized access, revealing of data to improper Participant or external party, revealing of sensitive system information (e.g., passwords, authentication inoperable) In general, there are no options to manually mitigate (workaround) a Severity 1 Issue Severity 1 Issues are not eligible for deferral. In the event a Severity 1 Issue is deemed deferred, the severity level must be reduced.

Defect and Enhancement Severities Levels Severity 2: High - Defects or Enhancements that do not meet the Severity 1 definition that cause or resolve the following: Impair SPP’s ability to manage the reliability of the SPP footprint or perform daily operations functions Significantly impacts more than two-thirds (66%) of SPP’s participants as measured by the number of participants, or either 90% of SPP’s generational capacity or load served Result in an incorrect calculation of Participants’ financial position or the validity of an SPP Settlement Statement / Invoice (e.g., calculation of Market / Auction results, pre- Settlements Staging/POPS calculations, core Settlements calculations, data published via Statement/Invoice) Impact closing an internal SPP Test Stage: While a single Issue would likely not have such an impact, analysis of Severity 2 Defects is part of the Exit Criteria for each Stage. Business Owners, Project Managers, and Testing Leads should be prepared to escalate these Issues to Program Leadership if the probability of missing a Test Stage closure date due to one or more Severity 2 Issues becomes greater than 50%. There may be options to manually mitigate Severity 2 Issues, but generally these workarounds are likely only sustainable for a short term.

Defect and Enhancement Severities Levels Severity 3: Medium - Defects or Enhancements that do not meet the Severity 1 or Severity 2 definitions that cause or resolve the following: The impact to SPP reliability and/or markets capabilities is manageable The Issue generally impacts less than two-thirds of SPP’s Participants or less than 90% of SPP’s generational capacity or load served The Issue impacts a non-critical software component or business function The Issue is deemed to only impact rare or low priority business conditions / scenarios There should be options to manually mitigate Severity 3 Issues with the ability to sustain such workarounds with existing SPP or Participant resources The Issue should not impact closing an internal SPP Test Stage. Individual Severity 3 Issues do not require specific analysis; however, a combination of several related Severity 3 Issues may be evaluated in the Test Stage closure discussion if the overall impact of those Issues, specifically the manual mitigation options, is considered unsustainable. The benefits (improved reliability, market efficiency, reduced risk) are moderate to significant when compared to the implementation costs and time.

Defect and Enhancement Severities Levels Severity 4: Low - Defects or Enhancements that do not meet the Severity 1, Severity 2 or Severity 3 definitions that cause or resolve the following: Do not have any reliability or operations impact The item is considered cosmetic or “nice to have” and do not materially alter system functionality Impact documentation/training deliverables These Issues likely do not require a manual workaround The benefits (improved reliability, market efficiency, reduced risk) are minimal to low when compared to the implementation costs and time.