Bid Invitation - Addendum 1Issue Type Priority LoE NotesDocument DME Front Office processes that involve HorizonDocumentation Low Medium Will require discovery meetings with the responsible DME personnelDocument DME Middle Office processes that involve HorizonDocumentation Low Medium Will require discovery meetings with the respnsible DME personnelDocument DME Back Office processes that involve HorizonDocumentation Low Medium Will require discovery meetings with the responsible DME personnelCreate a trade type Exposure Report by position type (fin vs phys )Report Medium Medium Not sure about a trade type exposure ‐ could just be a straight position report grouped by position type (PHYSICAL, FINANCIAL) and possibly by Product or by tradebook (instead of by trade type).Explore ways to improve Cash Curve upload processExtension Medium Needs further definition discussion with StephenAdd Options entry and reporting Training Low Needs further definition discussion with StephenReview trade quantity status lifecycle (TRADE, FORECAST, PLAN, ACTUAL)Configuration Low Low Currently modeling two trades per single deal, one models the FORECAST profile and the second models the ACTUAL profile which is not Best Practice but probably done this way due to the different time units (hourly awards/forecasts with quarter‐hour actuals)Database view to streamline creating the daily Cash Month Position report‐ Needs BALMO pricing for use by the Cash Month Valuation mode thereby including the BALMO positions needed by Phil's report‐ Related to DME‐050Extension High Medium The Production prototype calculates the Current MTD Position report. Phill will validate the results.The next step is to add the Current MTD PnL calculation logic.The third step is to then replicate the Current MTD Position and PnL logic for the BALMO Valuation results to populate the third pan in the report view.
Create an "Unusual Trades" view in Horizon that would perform quality checks on trades with status = "New". Checks would be beyond what could be performed by the trade templates.Extension Medium Low Currently, this task is being managed via Event Messages to alert staff about trade captures issues. Some ideas: 1) check for trade prices that are outside the average trade price by some amount; 2) check swap trade sto verify that one of either the pay or the rec price indexes are not null; 3) check for any other strange trade capture behaviors that weren't caught by the templates.ICE Balmo Pricing is not interfaced into Horizon. Currently the pricing is manually added by Phil.Extension Medium MediumSecurity Matrix to automatically change credit limit if credit rating is changed. Credit rating and limit will be maintained in an existing Extension Medium MediumUploading Volatilities and Correlations were marked out of scope for the 2020 implementation. Phil has requested that we automate this upload process, because this data Extension High MediumNG Volatilities are currently not available. Smith is working on this, but I wanted to make sure it was being tracked. This will be needed Other Medium LowCreate report to support backtesting of at risk Low pdd ‐ Deloitte Recommendation 3.5.2.R1]Automate Back Office daily "DEC Yesterday" (and possibly daily "Estimated DEC Gross Margin" and "Congestion" reports) Low [pdd ‐ an alternative to asking BO to modify their existing spreadsheet to rerport daily performance of newer renewable resources like Bluebell 2 and Longdraw. Should be possible to also automate/consolidate daily DEC reporting and Congestion reports.]
Capture Bid/Ask forward prices in Allegro Medium [pdd ‐ EMDS currently sends just midpoint Forward Price to Allegro, despite Allegro having the capability to store and display multiple variations of forward prices. Allegro screens currently display Price, Open Price, High Price and Low price, but all four values are same (the midpoint price). We should take adavantage of ability to display the additional information we are getting but not using from OTC Global]Create report to support rolling 12‐month "Rates at Risk" metric along with excedance High [pdd ‐ Risk Policy section B.3]DEC Optionality High DEC output for forward months in LT Position view does not vary with day‐to‐day changes in forward prices. Revise methodology to reflect DEC optionality (or is this what we would get from Denton Options view?) Training Training High Continue to learn how Allegro works (e.g., creating and updating valuation modes and views, data modeling, database investigative work, trouble shooting, System Admin duties, and understanding how hedging terminology and accounting is applied on Allegro). Does not inlcude training on Hedging and Risk.
Generate trade Confirmations for hedge sales Configuration Low Medium Can Allegro generate a file like the email attachment (we call this a Confirmation Agreement or “Confirm”) that we can send to our counterparties within 2 days of when we are on the selling side of a hedge transaction? I’m sure it can; I’m just not sure how big an effort it would be to set up the template to do this. Technically the seller is responsible for doing this. However, our counterparties have historically all agreed to do this for us.Along this same lines, when we are a net seller with a counterparty during a month (see second attachment), we also are need to issue an invoice to them. Currently Mike has to do this manually. Can you also see what would be involved in having Allegro generate this type of document? Task owners needs training on this. MO also ran out of funds to pay for any licenses and or training. Is there any one at MRE that knows how to do this?
The existing CRR & PTP Position database views only query data from the CRR tradebook and thus there is no PTP trade data shown in these views as the view names would imply.Configuration Low There are two possible solutions: leave the Position views named as is currently and modify the database view SQL to include the PTP tradebook along with the CRR tradebook. The view SQL will then select results for both CRR and PTP trades and it would be up to the user to open the sidebar Index and select which tradebook they want to see, else they'll get both. An alternative solution would be to leave the database view SQL as is, rename the existing Position views to indicate they are CRR Position views and create duplicate/equivalent Position views for the PTP trades. This solution relieves the user from having to select the tradebook from the sidebar view Index.The CRR trade model requires 3 loadshapes to convert the award in terms of MW to a trade quantity in terms of MWh. Restructure the trade model to use only a single loadshape.Configuration Medium There are a lot of CRR trades that would have to be re‐modeled and a lot of loadshapes to be deleted. The current monthly MW rate loadshapes for each CRR path would have to be converted from a monthly MW rate to an hourly MW rate because Horizon can't model CRR trades with a time unit of MONTH. And we'd probably want to run an end‐to‐end Unit Test to verify the results are as expected.There are a lot of trades that have their market area set to ERCOT. The ERCOT market area is marked to the same forward curve as the HB_North market area. There really isn't any value, other than to be used to filter in a view, Configuration Low Waiting for input/clarification from EMOInvestigate adding ICE Forward curve prices to Horizon and use for the NextEra trade valuationConfiguration Low
The extra hour price and quantity data on the DST Autumn clock change date does not appear to be uploaded correctly from EMDSData Medium Examining the HB_NORTH RT quarter‐hour price index for a clock change date showed none of the expected four extra quarter‐hour prices for the extra hour. And the 01:45AM price had its DST Boolean checked TRUE which isn't right. This will affect the valuation of any physical power trade that spans the Autumn clock change date in any year.Terry ‐ EMO marking prices. What do you intend to do. Internal compare with external. Two way to do. Using second column in the prices but messy. Or, create a new price index. Configuration I can't remember if this was just a question that Phil asked or just something that needed to be in this list per se. Not too sure about the data though.