Spreadsheet: chris_stokley__3968__Enron-PwrPrjctTaskList
Sheet: 10052001 (2)

Notes: | All rows are sorted first by Request Date, then by Due Date, then by Status.
 | Some numbers on [NAME], # Personnel, and # Man-Hrs a purely estimates, and subject to change.
Request Date | Due Date | Task Name | Status | Date Complete | Priority (1 Low-5 High) | Requested By | Description | # Power Team Personnel | # Power Team Man-Hrs |  | Personnel Selected | Power Team Task Lead | Notes
2001-08-21 00:00:00 | 2001-12-01 00:00:00 | Power Contract Baseline/Bandwidth Project | 0.1 | - | 5 | [NAME] [NAME] | Develop a db to capture power contract baseline and bandwidth information.  Round-up contracts to ensure population of active deals.  Develop a calc engine on top of the engine to determine the underage and overage of actual usage data with respect to an established bandwidth. | 5 | - |  | [NAME] | [NAME] | We are still in the process of defining requirements and re-working the database.  Within a few days, we will begin a full exercise of capturing data.  After sufficient progress there, we will code the calc engine pieces to identify consumption with respect to contractually established bandwidths.  There are 5 personnel dedicated to this effort at the current time; they are working to organize contracts and highlight information for more efficient processing as we begin in full on Monday, 10/08/2001.
2001-08-21 00:00:00 | 2001-12-01 00:00:00 | Power Contract Validation/Reconciliation Project | 0.25 | - | 5 | [NAME] [NAME] | Develop a db to capture power contract key fields.  Round-up contracts to ensure population of active deals.  Develop a db to house actual usage data from billing and deal mgmt data, and reconcile the existence of records within each. | 25 | - |  | [NAME] [NAME] [NAME] Others | [NAME] | We began this process in full on Monday, 10/01/2001.  We arrived at about 2300 deal numbers and about 600 contracts fully validated.  This work includes the rework required by the modification of the Validation db requested on 10/02/2001.  We will continue with full Validation in the coming week, with the expectation that our results on hit rate here will guide further Reconciliation and Contract Round-Up activities.
2001-09-04 00:00:00 | 2001-10-31 00:00:00 | Power Contract Round-Up | 0.5 | - | 4 | Power Team | Round-up all physical [NAME].  Make copies for GK group if necessary, coordinating their team members' time for such task.  Obtain inventory lists of the contracts delivered from each department (CSC, Legal, CAD, GK, Origination). | 5 | - |  | [NAME] [NAME] Others | [NAME] | Last week's statuses for Contract Round-Up remain the same:  Legal Dep't - Complete; GK (Paper) - Complete; GK (Documentum) - Status Pending; CSC (Pennzoil) - Complete; CSC (Dublin) - Not Started; Origination - Not Started.  The GK Dep't will continue to deliver the Power Team new business paper contracts on a daily basis.  The Power Team will deliver to GK Dep't a weekly list of fully validated contracts for appropriate upload to LiveLink.  Next week, we are planning visits to the CSC and CAD offices in Dublin, OH, as well as the origination offices (Long Beach, CA; [NAME], NJ; Chicago, IL, San Francisco, CA).  Our focus will the a full seek and copy of all contracts at each of these sites.
2001-09-19 00:00:00 | 2001-09-21 00:00:00 | Contract-to-RPS Check | 1 | 2001-09-26 00:00:00 | 3 | [NAME] | Make a quick review of the on-hand paper contracts to determine their existence in the RPS data extract.  Document the statistics and determine an appropriate stratification of the contracts for initial project activities. | 5 | 80 |  | [NAME] [NAME] | [NAME] | After completing this activity, we found an approximate 80% hit rate of paper contracts to RPS records.  This number has assisted in the estimation of expected paper contracts to be rounded up.
2001-09-24 00:00:00 | 2001-10-10 00:00:00 | RPS-to-CSC Database Development | 0.95 | - | 3 | Power Team | Determine the final requirements for the RPS-to-CSC Reconciliation Access db and implement these.  Requires finalizing the data requirements for billing/utility information, as well as the source of such. | 3 | 16 |  | [NAME] [NAME] [NAME] | [NAME] | We have identified the most appropriate data sources for this initiative, and are in the process of extracting such data from the parent CSC systems (LodeStar, STAT, and HP).  Our db is nearly fully developed, pending any changes in the initial two days of work here next Monday and Tuesday.  The process of reconciliing RPS data to CSC data will involve a dedicated team, whose count will be determined based on the throughput rate noted on Monday and Tuesday.
2001-09-25 00:00:00 | 2001-10-05 00:00:00 | Project Ranger Data Extracts | 0.75 | - | 4 | Power Team | Obtain a Project Ranger data extract containing the account profile and actual volume information for power deals. | 1 | 4 |  | Vivian Hart | [NAME] | Given our reliance on CSC parent system-specific data, we are not currently considering the use of Project Ranger data for our reconciliation efforts.  However, we continue to work with Project Ranger representatives to gather the appropriate information as it becomes available.  These personnel continue to serve in an influential capacity of defining our data requirements.
2001-09-26 00:00:00 | 2001-10-05 00:00:00 | [NAME] | 0.5 | - | 4 | [NAME] | Select a deal to trace through the batch module processing stages of deal capture and booking.  Determine the way in which Rates, [NAME], and 12x12s are captured in the batches or RPS; what information feeds the batches (e.g., Transaction Economics), what documentation stays with the paper contracts.  Determine the final process by which deals requiring batch re-run are executed and handed back off to the Power Team. | 2 | 8 |  | [NAME] [NAME] [NAME] [NAME] | [NAME] | [NAME] time has not been secured for this walkthrough.  Our walkthrough of the batches and transaction economics will help immensely in understanding the contents, type, and limitations on reliability of RPS data.
2001-09-26 00:00:00 | 2001-10-10 00:00:00 | Contract Type Profiling | 0.25 | - | 3 | [NAME] [NAME] | Determine the types of contracts in use for each year since the inception of the business at Enron.  Profile the pricing commentary. | 4 | 16 |  | [NAME] [NAME] | [NAME] | We have held several meetings with Enron personnel who have been involved with different stages of the Power contract evolution.  This has led to only a high-level understanding of the fact that contracts have changed a lot over the years, with only minimal standardization in a lot of cases.  Early next week, we anticipate taking a sampling of paper contracts to determine the standard form based on chronology.
2001-09-26 00:00:00 | 2001-10-12 00:00:00 | Contract Round-Up Matrix | 0 | - | 5 | [NAME] [NAME] | Develop a matrix detailing the number of contracts located in each target department (CSC, Legal, CAD, GK, Origination).  Firm up the expected estimate of paper contracts population. | 2 | 16 |  | [NAME][NAME] [NAME] | [NAME] | The delivery of this matrix will depend heavily on a more firm estimate of the expected population of paper contracts.  This determination will be made from the pools of CSC-, GK-, Legal-, and Originator-delivered paper contracts as compared to RPS and billing/utility data.
2001-09-26 00:00:00 | 2001-10-15 00:00:00 | Power Team & Team Everest Project Coordination | 0 | - | 3 | Power Team | Discuss the direction of Power Team and Team Everest to determine coordination of projects.  Obtain sign-off from Team Everest on Power Team's db design and data model for ease of data conversion. | 2 | 16 |  | [NAME][NAME] [NAME] [NAME] [NAME] | [NAME] | We have held several meetings with representatives from Project Everest this week.  Our progress continues in a positive direction, especially as it relates to definition surrounding the capture of data in the validation exercises.  We have covered nearly all of the fields in the current database version, and anticipate finishing this activity with Everest representatives by holding discussions surrounding pricing and pass through costs.  These changes continue to impact the database design, although not in a drastic manner.  Nonetheless, our time commitments to ongoing db changes continue.
2001-09-28 00:00:00 | 2001-10-05 00:00:00 | Final RPS Data Extract Format | 1 | 2001-10-10 00:00:00 | 5 | Power Team | Meet with IT to determine the final form of the RPS Data Extract, including the particular fields to capture and their formatting.  Determine the process whereby this extraction person and process are preserved for weekly exercises. | 2 | 4 |  | [NAME][NAME] [NAME][NAME] | [NAME] | We have finalized the format of the RPS extract data, in coordination with the needs of the Baseline/Bandwidth, Reconciliation, and Validation projects, as well as the needs of the other Enron initiatives.
2001-10-01 00:00:00 | 2001-10-31 00:00:00 | Unwind Process Definition | 0 | - | 3 | [NAME] | Define and test the process of unwinding deals discovered during the contract Validation/Reconciliation exercises.  Determine appropriate reporting and approval structures for tracking the information unwound in each deal. | 2 | 16 |  | [NAME] [NAME] [NAME] | [NAME] | Only preliminary discussions have been held surrounding this topic.  As an estimate, in about a month's time, we will begin the follow-up process for contracts or deals that were not handled during the activities involving the Access dbs.  This follow-up will involve researching the decisions and steps involved with structuring the deals in question, so as to flesh out a resolution process (e.g., book to RPS, remove from CSC, etc.).
2001-10-02 00:00:00 | 2001-10-05 00:00:00 | Baseline/Bandwidth Database Re-Development | 0.9 | - | 5 | [NAME] | Determine the final requirements for the Baseline/Bandwidth data capture and analysis db and implement these changes.  Hold appropriate discussions with SMEs and obtain sign-off before and after implementation from Project Leaders. | 2 | 32 |  | [NAME] | [NAME] | Database functionality is set and we have started capturing baseline/band information from the contracts.  However, there may be changes needed as we get more clarification on the contract langugage.  The Database is developed based on CA contracts.  We have tried to capture all possible contract language types.  Establishing a minimum set of requirements here is essential to completing  this task.
2001-10-03 00:00:00 | 2001-10-05 00:00:00 | Validation Database Re-Development | 1 | 2001-10-03 00:00:00 | 5 | [NAME] | Re-develop the Power Contract Validation db so that full site information can be captured, in order to facilitate the RPS-to-CSC visual reconciliation procedures. | 2 | 8 |  | [NAME][NAME] [NAME] | [NAME] | We have finished reworking the Validated contracts due to the changes in the db last week.  Minimal changes have evolved this week, and all have been implemented.  None have caused considerable rework of validated contracts.
2001-10-04 00:00:00 | 2001-10-08 00:00:00 | Baseline/Bandwidth Process Flow | 0.75 | - | 4 | [NAME] | Develop an illustrated and narrated process flow of the Baseline/Bandwidth project activities.  This should include a decision tree for differing scenarios, especially those related to the type of information encountered in the contracts and supporting documentation. | 1 | 8 |  | [NAME] [NAME] | [NAME] | Process Flow will be completed as we have the Baseline Contract language defined by Enron perrsonnel.  Once defined, we will know the process of how we should capture baseline information based on the contract language.
2001-10-04 00:00:00 | 2001-10-08 00:00:00 | RPS-to-Ranger Check | 1 | 2001-10-05 00:00:00 | 5 | [NAME] [NAME] | Select a set of Contract-to-RPS-validated contracts, and verify the existence of the deals in the initial Project Ranger data extract.  The results will frame any re-definition of the query that generates the Project Ranger data extract, as well as determine the expected success of the RPS-to-[NAME] or RPS-to-CSC reconciliation efforts. | 2 | 8 |  | [NAME] | [NAME] | A sample of 120 contracts (308 deal numbers) was chosen for this process.  We determined that about 55% (169) of the related counterparty names were matched between the data sets; 9% (27) of the counterparty names were not matched; and 36% (112) were indeterminate.  This suggests that the Project Ranger data is somewhat reliable and that we should focus on bettering the hit rate.  We held a meeting with Vivian Hart to discuss this, and a modification of the Project Ranger extract is in progress.  This extract will now include the Enron Account # and the Utility Account #, if available.