Spreadsheet: kevin_presto__19892__OpportunitiesAndQuestions
Sheet: Integration Opps

Integration Opportunities (Interfaces and common solutions)
Opp. # | Business Area | Originator | Short Description | Detailed Description (if needed) | Benefit | Priority | Implementation Considerations
1 | Trading and Position Management | Various | Integrated wholesale and retail position management | Integrated reporting architecture for all retail and wholesale positions | 1) Allows for integration position reporting for retail and wholesale aspects of deals 2) Avoids redundant deal capture (e.g., structuring and trading in EWS, wholesale and retail) 3) Facilitates inter-book position taking
 | Valuation and Risk Analysis | Various | Integrated Curve management for retail and wholesale | Single database of valuation curves | 1) Consistent valuation across retail and wholesale positions 2) Reduction in reconciliation issues between wholesale and retail on same deal
 | Valuation and Risk Analysis | Various | Integrated P&L across retail and wholesale positions | Integrated reporting architecture for retail and wholesale valuation components to the deal level | 1) Provides single consistent P&L view to traders 2) Provides an integrated P&L for the deal
 | Origination and Structuring | Various | Use "Deal View" across EES and EWS | Utilize EES deal view architecture for shaped components of wholesale deals | 1) Reduces deal entry effort for EWS and associated entry errors (e.g., in EWS have to back the deal out if entered in error) 2) Reduces reconciliation between structuring and risk management (assuming structuring uses deal view)
 | Origination and Structuring | Various | Use the same valuation mechanism for structuring and risk analysis | Eliminate Excel based EWS structuring models and utilize risk management valuation (I.e. portcalc) | 1) Eliminate reconciliation effort between structuring and risk for EWS structured deals
 | Trading and Position Management | Various | Common front end deal entry (for retail and wholesale components) | Common deal entry windows for EWS and EES for shaped and block components of deals (may go to different systems behind the scenes - everest and enpower) | 1) Reduced shaped deal entry effort for EWS 2) Allows deals to be stored and processed in the most efficient manner transparent to the business user
 | Trading and Position Management | Various | Automated confirmations between EES and EWS | Integration of Everest and enpower to electronically confirm trades between EES and EWS (or EES and EOL) | 1) Reduces redundant deal entry and effort associated with reconciliation and error analysis
 | Valuation and Risk Analysis | [NAME] | Allow valuation to support various intervals (e.g., 15 minutes, 1 hour, daily) | PortCalc is hourly for TX (even though ERCOT is 15 min.). Need to enable more flexible valuation engine (I.e. Everest) | 1) able to correctly value deals where prices are cleared at different intervals 2) able to correctly allocate RTO services cleared at different intervals correctly (e.g., ERCOT balancing every 15 minutes)
 | Volume Management through Invoicing | [NAME] | Separate volumes from prices to allow for easier volume adjustment | Currently ENA must redo the deal / enter new deals to make volume adjustments. Allow volume adjustments to be associated with the original deal. | 1) Reduced effort for volume updates 2) Allows for linking of volume management adjustments to the original deal enabling more accurate P&L accounting
 | Trading and Position Management | Various | Improve deal entry speed for non-structured EES deals | EES needs Blotter for non-Full Requirements deals | 1) Faster entry of EES deals 2) Reduces backlog of EES deal entry and associated error potential
 | Volume Management through Invoicing | [NAME] | Develop common volume management engine for retail and wholesale transactions | EES and EWS have similar volume mgt functions. EWS does charge estimation, shadow settlement for RTOs. EES does charge estimation and shadow settlement for EWS. EWS does allocations to counterparties and books (like EES). EES does allocations to customers and books. Both EES and EWS provide detailed volume information to process disputes (internal and external). EES gathers and processes demand management notifications at the account/resource level (from ROC). EWS gathers notifications at the wholesale level from RTOs. | 1) Reduced reconciliation between wholesale and retail volumes and allocations. 2) Faster volume management and less dispute processing between EES and EWS
 | Volume Management through Invoicing | [NAME] | Develop common settlement engine for wholesale and retail transactions | EES and EWS have similar counterparty settlement and invoicing needs and flash to actual needs. Investigate utilizing a common solution for both areas (assuming the data architecture support this need) | 1) Easier to complete netting across EES and EWS counterparties 2) Single invoice being provided to each counterparties (for those which cross EES and EWS) 3) Automated checkout between EES and EWS 4) Easier allocation of P&L across wholesale and retail books
 | Volume Management through Invoicing | Various | Single Interface for RTO/ISO Information Flow | EWS completes all interaction with RTOs and passes relevant allocation data to EES. | 1) Reduced cost associated with interfacing with RTOs
 | Trading and Position Management | Various | Put contract validation into Trading and Position Management Capability | Operationalizing the contracts by incorporating contract terms into the trading parameters. Currently being completed after the fact by Settlement. | 1) Increased compliance with contract terms - reduced exposure to non-compliance damages
 | Volume Management through Invoicing | [NAME] | Automate trading interface with settlement | Eliminate current Unify/EnPower bridge and replace with automated interface. Currently Unify can't process some deal types included in enpower and exceptions are generated across the interface. | 1) Reduced reconciliation effort associated with Enpower to Unify interface
 | Volume Management through Invoicing | [NAME] | Common repository for meter data information | Lots of groups require meter information and currently this is stored in various places in different forms. | 1) Reduction in the effort associated with obtaining meter data 2) Improved analysis through more reliable meter information
 | Volume Management through Invoicing | Various | Automating flash to actual | Incorporate a solution where flash to actual exceptions are flagged and able to be corrected online with no technical workarounds required. For example a prior period adjustment needs to be put in the current period resulting in 2 discrepancies (old deal invalid, new deal invalid) - the system need to recognize that the adjustment is for a prior period deal. | 1) Reduced manual effort associated with reconciling and correction of flash to actual discrepancies 2) Reduced effort associated with explaining adjustments during checkout (??)
 | Valuation and Risk Analysis | [NAME] | Improve speed to value full requirements deals | ?? |  |  | Need to get more information from [NAME] and talk to IT personnel
 | Volume Management through Invoicing | [NAME] | Disaggregate gas and other positions that are currently aggregated | ?? |  |  | Need to get more information from [NAME]