1 / 7

NMMS Update

NMMS Update. Raj Chudgar. Agenda. NMMS timeline NMMS Product Update NMMS Market Trials Update NMMS Model Verification Issues. NMMS High Level Timeline. Nov ’07: Release 1C Delivery Complete. Mar ’08: TSP Training on NMMS starts. June ’08: Go Live. April ’07:

mariasimmons
Download Presentation

NMMS Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NMMS Update Raj Chudgar TPTF

  2. Agenda • NMMS timeline • NMMS Product Update • NMMS Market Trials Update • NMMS Model Verification • Issues

  3. NMMS High Level Timeline Nov ’07: Release 1C Delivery Complete Mar ’08: TSP Training on NMMS starts June ’08: Go Live April ’07: Release 1A Delivery Complete 2007 2008 2009 Dec ’08: Nodal Go Live July ’07: Release 1B Delivery Complete April ’08: Start model validation Feb ’08: NMMS Sandbox started Mar ’08: Final Release for Go Live

  4. NMMS Progress • NMMS Core Product Modules • Information Model Manager (IMM) -- working • Project Tracker and Coordinator (PTC) -- working • Auto One-Line Generator -- working • Case/Model Builder -- working • Transmission Network Applications (TNA) – working • Topology Processor (to convert operations to planning models) -- working • Planning Model On Demand (MOD) -- working • Issues • Currently have ~12 open defects with the vendor • Additional non-Go Live functionality planned for summer 2008 • Working on Model issues with AREVA and ABB

  5. NMMS Market Trials • NMMS Sandbox was open to TSPs starting in Feb 2008 • ERCOT verified with TSPs that they were able to connect to the NMMS sandbox • Started NMMS Market trials March • Trials include 2 days of hands on work with ERCOT staff • Followed by 3 days of extended testing at TSP site, ERCOT staff on call • Completed testing with the following TSPs • AEP, STEC, Rayburn, and City of College Station • 9 additional TSPs scheduled in April • 8 additional TSPs scheduled for May • Issues: • A couple of scenarios have defects and TSPs will be provided addendums to test scenarios • Performance issue with multiple users. ERCOT to isolate and work with vendor Overall feedback thus far has been VERY positive

  6. Model Verification A. Powerflow (PF), SE, Shift Factors, Save cases B. Powerflow (PF), SE, Shift Factors, Save cases C. Powerflow (PF), SE, Shift Factors, Save cases 1. Current script to keep DB in sync EMS (zonal) EMS (Nodal) EMS (Nodal), backup site 2. Exported CIM from EMS 3. CIM importer from AREVA 1: Is currently being performed every ~ 2 weeks post DB load in zonal 2: AREVA has delivered multiple exports successfully, and ERCOT/ABB/AREVA have update the export multiple times, started Nov’2007 3: NMMS can export a CIM file today, but we are lacking the AREVA CIM importer • A, B, and C need to all be “explainable” before ERCOT states that the model conversion from zonal to Nodal is successful. John Adam’s team to assist NMMS team • Once A, B, C: are similar ERCOT should shut down 1 and 2 and NMMS then becomes source of changes and “dual entry” starts in Curtis’ team (highlighted in RED for manual process and dashed for CIM importer) • Red line indicates “Dual Entry once NMMS is source of model data NMMS (Nodal)

  7. Issues • Primary issue facing NMMS is without model verification Single Model Entry criteria can not be met • Requires EMS importer to validate current model to NMMS model • Secondary issues • Working with resource constraints with vendor • Working with vendor on remaining non-Go Live functionality delivery schedule • Working on negotiating change controls with vendor

More Related