1 / 32

Once you log into the MOTE system you should see the screen on the next slide.

Once you log into the MOTE system you should see the screen on the next slide. Case Definitions.

aretha-knox
Download Presentation

Once you log into the MOTE system you should see the screen on the next slide.

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. Once you log into the MOTE system you should see the screen on the next slide.

  2. Case Definitions • Current_Mote - This case represents the data base topology as of the date it was transferred. The generation pattern is from a state estimator solution. The load is from the load forecast. The date for both of these will be shown in the “Time of Study” on the network study display. This case most likely is not the same as the production topology since it contains the updates since the last base case was move to production. The contingency files attached to this case will be the same as those running on the production system. The contingency files may not match the case topology.

  3. Case definitions REALTIME_MARKET_SESOLUTION – This is a snapshot of the state estimator solution. The last modified date indicates when the solution was completed and transferred to the MOTE server. The update should occur every 5 minutes. If the state estimator is not converging, a case will not be transferred to the MOTE. Most capacitor switches have been opened due to the settings in the SE. This case may not solve in STNET without turning some switches back to the closed position.

  4. Case definitions OC_TRANS1 to 34 - These save case files support the transfer of cases from ERCOT to the TOs. Example- Someone in ERCOT can save a case into one of the slots. Someone at the TO world can retrieve the case into their clone. The sender will provide information on what the case represents.

  5. Case definitions OPS_BASECASE- This is the base case that operations started with to run their studies. It has the same topology as the production system. The topology is older than the Current_Mote case.

  6. Note: • The OPS_BASECASE – Is an ENTIRE case. It brings in a case plus all the settings for your clone. This case should be loaded first to get these settings into your clone. This only needs to occur once unless you want to reset your settings. Some settings are retained by your case and some settings are brought in by the different case types. Generally a NETMOM case will change functions such as auto tap settings while an entire case will change items such as number of iterations.

  7. AREVA Training Contact • You may contact AREVA for detailed training on the STNET or other AREVA software. • Areva web site is: www.areva.com • Areva training site is: http://www.users.areva-td.com • Areva training email: TRAINING.na@areva-td.com

More Related