Vision Document for Project Green Light Accurate, Complete and Efficient Risk Measurement and Reporting 10 September 2001 DRAFT FOR DISCUSSION ONLY.

Slides:



Advertisements
Similar presentations
SCO 3 Crewing Optimization As-Is Processes January 9, 2006
Advertisements

June 1, Current Status Technical Details Current Releases Issues Potential Use Cases Position Reporting Portfolio Reconciliation Cash Flow Matching.
A BPM Framework for KPI-Driven Performance Management
Ensuring Contract Compliance. Confidential 22 Office Depots strong executive level support and oversight Strong executive level support and oversight.
Roadmap for Sourcing Decision Review Board (DRB)
Vice President of Facilities
David Woo (dxw07u).  What is “White Box Testing”  Data Processing and Calculation Correctness Tests  Correctness Tests:  Path Coverage  Line Coverage.
OpalisRobot™ Demonstration Actual Run Book Procedure Actual Data center Run Book Procedure documenting for Level 1 staff how to both VERIFY.
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Pertemuan 16 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Troy Eversen | 19 May 2015 Data Integrity Workshop.
SAS 112: The New Auditing Standard Jim Corkill Controller Accounting Services & Controls.
Introductions Jim Enzinna, Chief, Licensing Division Mark DiNapoli, Assistant Chief, Licensing Division Tracie Coleman, Head, Information Section Vince.
Project Management What The Heck Is That?. Why Do We Need Project Management? Critical towards delivery of effective IT initiatives Ensures we align projects.
Release & Deployment ITIL Version 3
Ver Sep 09 Defense Medical Human Resources System internet for MHS Data Quality Course 16 Sep 2009.
System Testing There are several steps in testing the system: –Function testing –Performance testing –Acceptance testing –Installation testing.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Product Quality, Testing, Reviews and Standards
RUP Fundamentals - Instructor Notes
Why use RequisitePro RequisitePro is a comprehensive tool that supports any of today's requirements management processes. The predominant requirements.
© Grant Thornton | | | | | Guidance on Monitoring Internal Control Systems COSO Monitoring Project Update FEI - CFIT Meeting September 25, 2008.
Roles and Responsibilities
3.08 b Determine venture’s information technology.
Identify steps for understanding and solving the
Requirements Traceability: Planning, Tracking and Managing Requirements Presenter: Paula R. Maychruk, BV/TEd., CAPM, CBAP.
Financial Systems Needs Assessment Administrator Briefing Spring Quarter 2009.
1 Knowledge & Knowledge Management “Knowledge is power” to “Sharing K is power” Yaseen Hayajneh, PhD.
Current and Future Applications of the Generic Statistical Business Process Model at Statistics Canada Laurie Reedman and Claude Julien May 5, 2010.
Planning BOMS or Product Families: That is the Question? Jerry Edwards.
Margin Management. PAGE 2 Margin Management Plant Shutdowns 1.Late 1990’s – numerous “surprise” long-term plant shutdowns 2.Shutdowns resulted when a.
The Initiative For School Empowerment and Excellence (i.4.see) “Empowering teachers, administrators, policy makers, and parents to increase student achievement.”
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Best Practices FX Business. Pre-trade preparation and documentation.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
SSC SI Data Processing Pipeline Plans Tom Stephens USRA Information Systems Development Manager SSSC Meeting – Sept 29, 2009.
University of Minnesota Internal\External Sales “The Internal Sales Review Process” An Overview of What Happens During the Review.
(Project) RISK MANAGEMENT PROCESS SEPTEMBER 5, 2008.
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
4.5 Perform Integrated Change Control
<< DTC >> << Project Name >>
1 Purpose  To gain executive-level commitment from key market participants to take a leadership role in quickly improving retail transaction processing.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
PN UNC Workgroup Invoicing 10 th January Objectives of the Workgroups To determine business principles for future Invoicing processes –Consider/review.
Session 6: Data Flow, Data Management, and Data Quality.
Project Doorstep - London Preliminary Findings 17th April, 2000.
Software Maintenance1 Software Maintenance.
Standard Design Process Overview
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
Energy Operations Name, Title. 2 Overview of Services Daily trading P&L reporting Position reporting and limit monitoring Deal validation and confirmation.
SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.
An oil company in Canada
Service Management World Class Operations - Impact Workshop.
4.4 Monitor and Control Project Work
THE MIDDLE OFFICE A PERSONAL VIEW.
BA Continuum India Pvt Ltd
Oracle Subledger Accounting
PROJECT DOOR STEP LONDON
Overview – Processes Overview Purpose Roles & Responsibilities
Data Quality By Suparna Kansakar.
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
Sample Assessment & Governance Results
Presentation transcript:

Vision Document for Project Green Light Accurate, Complete and Efficient Risk Measurement and Reporting 10 September 2001 DRAFT FOR DISCUSSION ONLY

Project Green Light: Vision Document 2 Contents Background Objectives Scope Approach Project Team Organization Project Schedule

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 3 Executive Summary

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 4 Background RiskTrac VaR Positions Officialized ID’s DPR reporting Source systems Other downstream systems (CAS, Infinity) VaR reporting Benchmarks 1321 BA failed to officialize book BA failed to mark book as Active Incompatible book attributes (ERMS) Spreadsheet / file load failure Long processing times (ERMS) 43 Incomplete book / curve set-up 2 Timing difference (VaR runs later than CAS, Infinity) Inconsistent rules on un- and re-officializations 4 Unmapped curve Curve = 0 Wrong correlations Incorrect portfolio aggregation Book was officialized after VaR runs at 6:15AM Potential Failures from Current Risk Systems and Processes 55 Lack of cross-checks and exception reporting across systems

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 5 Key Issues – Long RiskTrac loading times from ERMS and some spreadsheets (book admins waiting 2-3 hours to confirm RiskTrac loads) – Manual, tedious and error-prone processes of creating books and managing book attributes – Different cut-off times for VaR, credit (CAS) and Infinity – Inconsistent system rules on un- and re-officialization – Unreliable, Excel-based benchmark position reporting – Limited VaR diagnostic capabilities – “Over-centralized” maintenance of VaR inputs – Limited exception reporting and reconciliation mechanisms Background, continued 12345

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 6 Objectives The main objective of Project Green Light is to enhance current risk controls systems and processes to ensure that risks are measured and reported in an accurate, complete and efficient manner Work groups to address different components of this objective include: – Source feeds processing: Enhancing the timeliness and accuracy of information flow from source into risk systems – Data validation: Ensuring the correctness of current RiskTrac system configuration and developing processes to efficiently maintain system accuracy and reliability – Business process: Documenting current business processes, identifying opportunities for improvement, and putting new processes in place to implement solutions identified by the other work groups

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 7 Scope Project Green Light will focus on resolving issues involving ERMS, EnPower and spreadsheet feeds into RiskTrac, Credit and Infinity for gas, power, EGM and UK groups. For purposes of completeness, the project will also identify any issues with all other groups Project Green Light will focus on the flow of information from the source systems upon officialization. Issues on deal-entry, valuation and calculating of deals will be out of scope Some of the solutions that will be implemented will be short- to medium-term “fixes” to address some of the more immediate issues (like long processing times and time-consuming issues resolution). The project assumes, however, that a longer term system solution like Enlighten and Global Valuation will eventually be implemented

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 8 Project Team Organization Steering Committee Jeff GossettMike Jordan Debbie BrackettShona Wilson Program Mgt. Office Tom VictorioUK (James New?) Source Feeds Processing ERMS, EnPower, UK Data Validation Gas, Power, Global Products, UK Business Process Gas, Power, Global Products, UK Source Systems IT (ERMS, EnPower, UK) RiskTrac IT Commodity Risk Groups (Gas, Power, Glob. Products, UK Global Risk Ops Project Sponsor Sally BeckRick Buy

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 9 Approach Gather requirements from business and system groups Plan and initiate improvement projects Implement and manage systems and process changes Draft continuous and long term improvement plans Source feeds processing Data validation Business process ERMS EnPower UK RiskTrac CAS Infinity DPR

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 10 Approach, continued Source Feeds Processing Success measures Reduced waiting times to confirm information loads into RiskTrac Capability to measure percentage of daily positions loaded / not loaded into RiskTrac Identify positions not currently being captured in RiskTrac (and measure as a percentage of total Enron positions) Plan for measuring and reporting risk for non- RiskTrac positions Data Validation Success measures Achieve > 95% success rate of daily RiskTrac loads Reduced time and effort spent on issues resolution Efficient and reliable RiskTrac hierarchy structure that enables VaR reporting for all relevant portfolios Reduce number of unused books, portfolios, curves Business Process Success measures Definition of risk controls processes and responsibilities Transition plan to new processes and roles

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 11 Approach, continued Source Feeds Processing Initial list of projects Faster ERMS post-ID resolution Running parallel RiskTrac load processes ERMS function to prevent officialization of empty books Address inconsistent un- and re-officialization processes across risk systems Address inconsistent processes when the system finds no post-ids (eg. Infinity takes previous day’s data, RiskTrac does not) Determine impact of Enlighten Resources Project Manager – Greg Couch RiskTrac IT ERMS IT Data Validation Initial list of projects Determine correctness of current RiskTrac set- up Confirm accuracy of portfolio / book structure (no duplicates, all positions captured) Check curve mappings Develop efficient and reliable daily exception reporting and cross-checking Officialization loads VaR diagnostic report Business rules around exceptions (eg. materiality) Enhance RiskTrac reporting capabilities Benchmark position reporting and DPR loads VaR reporting and DPR loads Resources Project Manager – Gary Stadler (?) Global Risk Ops RiskTrac IT Business Process Initial list of projects Develop book archiving process Re-define RiskTrac user roles and responsibilities Re-define risk controls processes and and segregation of responsibilities Document current RiskTrac set-up procedures and develop checklists Improve RiskTrac user processes Moving sub-portfolios (drag-and-drop) Renaming books (for books with no trade history yet) Develop tool for assigning books to portfolios Online book request (online form with input validation, automatic table updates) Resources Project Manager (?) Global Risk Ops RiskTrac IT

DRAFT FOR DISCUSSION ONLY Project Green Light: Vision Document 12 Project Schedule Need to determine timeline for each project in each workgroup