Message-ID: <18999998.1075841553432.JavaMail.evans@thyme> Date: Sat, 23 Jun 2001 11:04:42 -0700 (PDT) From: will.smith@enron.com To: cara.semperger@enron.com, corry.bentley@enron.com Subject: Pre-Schedule Workspace Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-From: Smith, Will X-To: Semperger, Cara , Bentley, Corry X-cc: X-bcc: X-Folder: \ExMerge - Semperger, Cara\Deleted Items X-Origin: SEMPERGER-C X-FileName: cara semperger 6-26-02.PST Cara, Corry, Here is a consolidation of your input: Border2 is not required for creating confirmation records nor for creating route data. Include Transmission information in the path when creating confirmation records. The path should resemble: UPSTREAM-SUPPLY-E-TRAN1(OASIS ID)-E-TRAN2(OASIS ID)-E- ... -MARKET-DOWNSTREAM Make Build Route sheet read only to prevent removal of data. Build Routes is dependent on the data staying in the sheet to determine if deals have changed. Add an option to clear the sheet to start over. The transmission deal number is not required for path confirmation records. Add "Prepare Next Day" and "Copy Workspace" functionality. Allow change font properties (color, bold, etc) and cell properties (highlight color). Allow searching in the sheets. e.g. search for a deal number. A simple search for string or number will do. Daily Summary needs to be completed. Neither Upstream nor Downstream are required for path creation. Fix "General SQL error. ORA-02289: sequence does not exist" problem. "insert keys" etc to tool bar. (example: redo, insert row,...) Although the sheets in this app are similar to Excel, there are some limitations. Implementing things like "redo" can be complicated if not impossible. When you open "path confirmation" it defaults to your last user sort settings. I don't know if this is possible. Very Important: We need to determine what is the very least requirements for this application to replace your current processes. The goal of this application is to allow you to set your excel worksheets aside and work strictly within Pre-Schedule Workspace (PSW). If with the current approach we are not able to achieve this goal, we need to take a step back are reevaluate our situation. Also, I can provide some of the basic Excel functionality that is currently missing, but I don't want to get into a situation where I am rewriting Excel. We need to determine what Excel functionality is a must and what functionality we can do without. Let me know if you have any other concerns. Thanks, Will