Docstoc

2012 Final SIR list - approved - pre-voting format r3

Document Sample
2012 Final SIR list - approved - pre-voting format r3 Powered By Docstoc
					2012 SIR List - May 10, 2012
   Product      SIR #    Subsystem         Component   Date Created Customer
ARCHIVE      ETA36891   ARCHIVE      UI                      1/5/11 Manitoba Hydro




ARCHIVE      PD23086    ARCHIVE      DATAMAN                10/9/06 Southwest Power
                                                                    Pool




ARCHIVE      PD34021    ARCHIVE      DATAMAN                3/26/09 Progress Energy




EMP          ETPA37369 DTS           DTS                     6/9/10 Alstom Grid




EMP          ETPA38217 DTS           DTS                    2/16/11 American Electric
                                                                    Power - Dallas
                                                                    (CAMS)
EMP   ETPA38393 DTS   DTS   3/29/11 ISO New England




EMP   ETPA38394 DTS   DTS   3/29/11 ISO New England

EMP   ETPA38395 DTS   DTS   3/29/11 ISO New England




EMP   ETPA38396 DTS   DTS   3/29/11 ISO New England


EMP   PD12435   DTS   DTS   1/21/04




EMP   PD12436   DTS   DTS   1/21/04



EMP   PD15718   DTS   DTS   8/26/04 ISO New England


EMP   PD16044   DTS   DTS   9/29/04 Alstom Grid
EMP   PD23491   DTS   DTS   11/22/06 FirstEnergy
                                     Corporation




EMP   PD24118   DTS   DTS     3/1/07 Transpower New
                                     Zealand




EMP   PD25574   DTS   DTS    7/11/07 Progress Energy -
                                     CP&L




EMP   PD26519   DTS   DTS     9/6/07 AMEREN
EMP   ETPA38405 GENERATION RTGEN   3/29/11 ISO New England

EMP   ETPA38406 GENERATION RTGEN   3/29/11 ISO New England

EMP   ETPA38407 GENERATION RTGEN   3/29/11 ISO New England




EMP   ETPA38408 GENERATION RTGEN   3/29/11 ISO New England




EMP   ETPA38410 GENERATION RTGEN   3/29/11 ISO New England



EMP   ETPA38416 GENERATION RTGEN   3/30/11 Alberta Electric
                                           System Operator
                                           (AESO)
EMP   ETPA38519 GENERATION RTGEN    5/19/11 EAA - EGAT
                                            Thailand




EMP   ETPA39110 GENERATION RTGEN   11/29/11 ISO New England
EMP   ETPA39599 GENERATION RTGEN   40995.69414 *Customer Support




EMP   PD13525   GENERATION RTGEN       3/18/04 Alstom Grid




EMP   PD18119   GENERATION RTGEN       4/26/05 Alstom Grid


EMP   PD18247   GENERATION RTGEN       5/10/05 Alstom Grid
EMP   PD18252   GENERATION RTGEN   5/10/05 Alstom Grid




EMP   PD24062   GENERATION RTGEN   2/21/07 Alstom Grid




EMP   PD24063   GENERATION RTGEN   2/21/07 Alstom Grid
EMP   PD32190   GENERATION RTGEN   10/2/08 Alstom Grid




EMP   PD36541   GENERATION RTGEN    1/5/10 Alstom Grid




EMP   ETPA36812 NETWORK   VVD      3/19/10 Alstom Grid
EMP   ETPA36823 NETWORK   NETWORK   3/22/10 Duke Energy South-
                                            East




EMP   ETPA37226 NETWORK   NETCOM    5/12/10 Alstom Grid




EMP   ETPA37388 NETWORK   NETWORK   6/14/10 Alstom Grid
EMP   ETPA37441 NETWORK   RTNET      6/29/10 Alstom Grid




EMP   ETPA38186 NETWORK   RTNET       2/8/11 NIPSCO (NiSource)




EMP   ETPA38215 NETWORK   STNET      2/16/11 American Electric
                                             Power - Dallas
                                             (CAMS)
EMP   ETPA38218 NETWORK   QKNET      2/16/11 American Electric
                                             Power - Dallas
                                             (CAMS)
EMP   ETPA38232 NETWORK   QKNET      2/18/11 American Electric
                                             Power - Dallas
                                             (CAMS)

EMP   ETPA38385 NETWORK   RTNET      3/29/11 ISO New England




EMP   ETPA38386 NETWORK   RTNET      3/29/11 Alberta Electric
                                             System Operator
                                             (AESO)




EMP   ETPA38388 NETWORK   NETMODEL   3/29/11 Alberta Electric
                                             System Operator
                                             (AESO)



EMP   ETPA38389 NETWORK   DCP        3/29/11 Alberta Electric
                                             System Operator
                                             (AESO)
EMP   ETPA38390 NETWORK   DCP     3/29/11 Alberta Electric
                                          System Operator
                                          (AESO)



EMP   ETPA38391 NETWORK   RTNET   3/29/11 Alberta Electric
                                          System Operator
                                          (AESO)




EMP   ETPA38392 NETWORK   CA      3/29/11 Alberta Electric
                                          System Operator
                                          (AESO)


EMP   ETPA38397 NETWORK   STNET   3/29/11 Alberta Electric
                                          System Operator
                                          (AESO)




EMP   ETPA38400 NETWORK   RTNET   3/29/11 Alberta Electric
                                          System Operator
                                          (AESO)
EMP   ETPA38467 NETWORK   RTNET       4/1/11 Hydro One




EMP   ETPA38538 NETWORK   RTNET      5/27/11 *Development
                                             Review


EMP   ETPA38687 NETWORK   NETWORK    7/27/11 Western Electricity
                                             Coordinating Council
                                             (WECC)


EMP   ETPA39304 NETWORK   NETMODEL   1/13/12 Duke Energy South-
                                             East


EMP   ETPA39554 NETWORK   CA         3/16/12 American Electric
                                             Power - Dallas
                                             (CAMS)


EMP   ETPA39555 NETWORK   CA         3/16/12 American Electric
                                             Power - Dallas
                                             (CAMS)




EMP   ETPA39581 NETWORK   RAS        3/21/12 ISO New England
EMP   ETPA39582 NETWORK   RAS       3/21/12 ISO New England




EMP   ETPA39583 NETWORK   RAS       3/21/12 ISO New England




EMP   PD16544   NETWORK   NETCOM   11/23/04


EMP   PD20397   NETWORK   RTNET    12/19/05




EMP   PD21255   NETWORK   CA        3/27/06 Dominion Virginia
                                            Power
EMP   PD23525   NETWORK   RTNET     11/27/06 FirstEnergy
                                             Corporation




EMP   PD31678   NETWORK   NETWORK    8/26/08 FirstEnergy
                                             Corporation




EMP   PD32209   NETWORK   RTNET      10/3/08 Alstom Grid
EMP   PD33153   NETWORK   CA   12/19/08 American Electric
                                        Power - Dallas
                                        (CAMS)
EMP   PD35935    NETWORK   NETMODEL   10/1/09 FirstEnergy
                                              Corporation




EMP   PD36453    NETWORK   NETCOM     12/4/09 FirstEnergy
                                              Corporation




EMP   ETP36857   SYSTEM    DBRESIZE   3/29/11 ISO New England
e-terrabrowser   ETB36475   e-terrabrowser WEBFG     1/13/10 ISO New England




e-terrabrowser   ETB36575   e-terrabrowser BUILDER   3/22/10 Manitoba Hydro




e-terrabrowser   ETB36818   e-terrabrowser WEBFG     7/26/10 FirstEnergy
                                                             Corporation




e-terrabrowser   ETB36833   e-terrabrowser WEBFG      8/5/10
e-terrabrowser   ETB36879   e-terrabrowser BUILDER       9/20/10 ISO New England




e-terrabrowser   ETB36966   e-terrabrowser BUILDER      11/22/10 ISO New England




e-terrabrowser   ETB37094   e-terrabrowser WEBFG         2/10/11 Bonneville Power
                                                                 Administration




e-terrabrowser   ETB37099   e-terrabrowser CLIENT        2/14/11 Manitoba Hydro



e-terrabrowser   ETB37175   e-terrabrowser WEBFG          3/4/11 Bonneville Power
                                                                 Administration




e-terrabrowser   ETB37259   e-terrabrowser WEBFGUTILS    3/29/11 Western Electricity
                                                                 Coordinating Council
                                                                 (WECC)
e-terrabrowser   ETB37270   e-terrabrowser WEBFG     3/30/11 Bonneville Power
                                                             Administration




e-terrabrowser   ETB37271   e-terrabrowser WEBFG     3/30/11 ISO New England




e-terrabrowser   ETB37273   e-terrabrowser WEBFG     3/31/11 Manitoba Hydro




e-terrabrowser   ETB37280   e-terrabrowser WEBFG      4/5/11 Alberta Electric
                                                             System Operator
                                                             (AESO)

e-terrabrowser   ETB37314   e-terrabrowser BUILDER   4/18/11 Manitoba Hydro

e-terrabrowser   ETB37350   e-terrabrowser BUILDER    5/5/11 Progress Energy



e-terrabrowser   ETB37670   e-terrabrowser CLIENT     9/2/11 American Electric
                                                             Power - Dallas
                                                             (CAMS)




e-terrabrowser   ETB37708   e-terrabrowser CLIENT    9/16/11 Hydro One
e-terrabrowser   ETB37988   e-terrabrowser BUILDER   12/13/11 ISO New England




e-terrabrowser   ETB38154   e-terrabrowser WEBFG      1/27/12 Madison Gas &
                                                              Electric


e-terrabrowser   ETB38262   e-terrabrowser WEBFG      2/22/12 ISO New England




e-terrabrowser   ETB38263   e-terrabrowser WEBFG      2/22/12 ISO New England



e-terrabrowser   ETB38283   e-terrabrowser CLIENT     2/29/12 ISO New England




e-terrabrowser   ETB38362   e-terrabrowser CLIENT     3/21/12 ISO New England
e-terrabrowser   ETB38363   e-terrabrowser BUILDER   3/21/12 ISO New England




e-terrabrowser   PD11585    e-terrabrowser BUILDER   3/31/99 Manitoba Hydro




e-terrabrowser   PD13796    e-terrabrowser BUILDER   3/31/04




e-terrabrowser   PD14380    e-terrabrowser BUILDER   5/18/04 Manitoba Hydro



e-terrabrowser   PD24799    e-terrabrowser WEBFG     5/11/07 Puget Sound Energy
                                                             EMS-DMS System


e-terrabrowser   PD30026    e-terrabrowser WEBFG      4/1/08
e-terrabrowser   PD30041   e-terrabrowser WEBFG    4/1/08 Hydro One




e-terrabrowser   PD30094   e-terrabrowser CLIENT   4/4/08 Alstom Grid
e-terrabrowser   PD31210   e-terrabrowser WEBFG    7/7/08 American Electric
                                                          Power - Dallas
                                                          (CAMS)




e-terrabrowser   PD32153   e-terrabrowser WEBFG   9/30/08 American Electric
                                                          Power




e-terrabrowser   PD32158   e-terrabrowser WEBFG   9/30/08 American Electric
                                                          Power
e-terrabrowser   PD32516     e-terrabrowser WEBFG           10/28/08 American Electric
                                                                     Power




e-terrabrowser   PD33646     e-terrabrowser CLIENT           2/10/09 ISO New England




e-terrabrowser   PD34056     e-terrabrowser WEBFG            3/27/09 Manitoba Hydro




e-terrabrowser   PD35030     e-terrabrowser WEBFG            7/13/09 ISO New England


e-                ETD38884   Client        User Interface    3/29/11
terradistribution


e-                ETD42721   Client        Displays          2/10/12 Madison Gas &
terradistribution                                                    Electric
e-                ETD42776   Client     User Interface   2/15/12 Madison Gas &
terradistribution                                                Electric




e-                ETD38887   Modeling   Model            3/29/11 Snohomish County
terradistribution                                                PUD

e-                ETD38981   Modeling   Model             4/1/11 Snohomish County
terradistribution                                                PUD




e-                ETD38982   Modeling   Model             4/1/11 Snohomish County
terradistribution                                                PUD




e-                ETD38983   Modeling   Model             4/1/11 Snohomish County
terradistribution                                                PUD
e-                ETD38984   Modeling    Model         4/1/11 Snohomish County
terradistribution                                             PUD




e-                ETD38986   Modeling    Model         4/1/11 Snohomish County
terradistribution                                             PUD



e-                ETD41526   Modeling    Converter    11/4/11
terradistribution


e-                ETD41526   Modeling    Converter    11/4/11 Madison Gas &
terradistribution                                             Electric


e-                ETD42720   Modeling    Converter    2/10/12 Madison Gas &
terradistribution                                             Electric


e-                ETD38987   Switching   SWO Server    4/1/11 Snohomish County
terradistribution            Orders                           PUD




e-                ETD38988   Tagging     Client        4/1/11 Snohomish County
terradistribution                                             PUD
e-                ETD38989   Tagging   Client                  4/1/11 Snohomish County
terradistribution                                                     PUD




e-                ETD38990   Tagging   Client                  4/1/11 Snohomish County
terradistribution                                                     PUD

e-                ETD38922   Tools     Viewer Config Editor   3/30/11 Snohomish County
terradistribution                                                     PUD




e-                ETD38886   Unknown   Unknown                3/29/11 Snohomish County
terradistribution                                                     PUD




e-                ETD38897   Unknown   Unknown                3/30/11 Snohomish County
terradistribution                                                     PUD


e-                ETD38898   Unknown   Unknown                3/30/11 Snohomish County
terradistribution                                                     PUD



e-                ETD38900   Unknown   Unknown                3/30/11 Snohomish County
terradistribution                                                     PUD
e-                ETD38901   Unknown   Unknown   3/30/11 Snohomish County
terradistribution                                        PUD




e-terrahabitat   ETH34300    HABITAT   HABITAT    8/6/09 Dominion Virginia
                                                         Power




e-terrahabitat   ETH36695    HABITAT   HABITAT   3/19/10 Transpower New
                                                         Zealand




e-terrahabitat   ETH36855    HABITAT   PERMIT    4/30/10 FirstEnergy
                                                         Corporation
e-terrahabitat   ETH37618   HABITAT   PERMIT    2/10/11 Reedy Creek Energy
                                                        Services (Disney
                                                        World)




e-terrahabitat   ETH37620   HABITAT   AEM       2/11/11 Bonneville Power
                                                        Administration


e-terrahabitat   ETH37628   HABITAT   ALARM     2/16/11 American Electric
                                                        Power - Dallas
                                                        (CAMS)


e-terrahabitat   ETH37665   HABITAT   CFGTEAM   3/10/11 Bonneville Power
                                                        Administration




e-terrahabitat   ETH37711   HABITAT   ALARM     3/29/11 Alberta Electric
                                                        System Operator
                                                        (AESO)




e-terrahabitat   ETH37713   HABITAT   ALARM     3/29/11 ISO New England
e-terrahabitat   ETH37714   HABITAT   PROCMAN   3/29/11 ISO New England



e-terrahabitat   ETH37795   HABITAT   ALARM     4/15/11 Connecticut Valley
                                                        Electric Exchange




e-terrahabitat   ETH37887   HABITAT   HABITAT   5/13/11 Bonneville Power
                                                        Administration



e-terrahabitat   ETH38217   HABITAT   PROCMAN   9/12/11 ISO New England

e-terrahabitat   ETH38660   HABITAT   HDB        3/9/12 ISO New England
e-terrahabitat   ETH38682   HABITAT   RAPUSER   3/20/12 ISO New England




e-terrahabitat   ETH38750   HABITAT   ALARM     4/27/12 Alabama Power
                                                        Company




e-terrahabitat   ETH38763   HABITAT   ALARM      5/7/12 Alabama Power
                                                        Company
e-terrahabitat   PD13985   HABITAT   SAMPLER    4/14/04 Manitoba Hydro




e-terrahabitat   PD18516   HABITAT   CFGTSTAT   6/13/05 PPL Corporation
e-terrahabitat   PD22016   HABITAT   ALARM     6/14/06 FirstEnergy
                                                       Corporation




e-terrahabitat   PD24138   HABITAT   SAMPLER    3/2/07 Hydro One
e-terrahabitat   PD30103   HABITAT   PERMIT     4/4/08 FirstEnergy
                                                       Corporation




e-terrahabitat   PD31569   HABITAT   PROCMAN   8/14/08 FirstEnergy
                                                       Corporation
e-terrahabitat   PD32433   HABITAT   RAPUSER   10/20/08 ISO New England




e-terrahabitat   PD32435   HABITAT   RAPUSER   10/20/08 ISO New England




e-terrahabitat   PD33041   HABITAT   ALARM     12/11/08 Hydro One
e-terrahabitat   ETH37712   WEBFG         ALARM VIEWER   3/29/11 Snohomish County
                                                                 PUD




e-terrascada     ETSC36715 e-terrascada   SCADA           4/7/10 Manitoba Hydro




e-terrascada     ETSC37053 e-terrascada   SCADA          9/14/10 American Electric
                                                                 Power - GENCO




e-terrascada     ETSC37294 e-terrascada   SCADA          2/18/11 Manitoba Hydro




e-terrascada     ETSC37746 e-terrascada   SCADA          3/29/11 ISO New England


e-terrascada     ETSC37747 e-terrascada   SCADA          3/29/11 ISO New England
e-terrascada   ETSC37754 e-terrascada    SCADA     3/31/11 BC Hydro




e-terrascada   PD16323    e-terrascada   SCADA     11/2/04 Alstom Grid




e-terrascada   PD30040    e-terrascada   SCADA      4/1/08 Hydro One




e-terrascada   PD33347    e-terrascada   TAGGING    1/8/09 AltaLink
                                                           Management, Ltd.

e-terrascada   PD34034    e-terrascada   SCADA     3/26/09 Progress Energy
e-terrascada    PD34309    e-terrascada   SCADA                4/27/09 We Energies




e-terrascada    ETSC37025 SYSTEM          SCADAFREQ            8/25/10 AMEREN




e-terrascada    ETSC38752 SYSTEM          SCADAFREQ        40997.62029




e-terrasource   ETSO39108 Client          DISPLAYS             2/23/12 ISO New England



e-terrasource   ETSO39278 Client          USER INTERFACE       3/22/12 Duke Energy South-
                                                                       East

e-terrasource   ETSO39279 Client          USER INTERFACE   40990.46998 Duke Energy South-East
e-terrasource   ETSO39350 Client           USER INTERFACE   40997.49174 Duke Energy South-East




e-terrasource   ETSO39087 Database         SERVER               2/22/12 ISO New England




e-terravision   ETV36845   e-terravision   VIEWER               3/30/11 Alberta Electric
                                                                        System Operator
                                                                        (AESO)
e-terravision   ETV36846   e-terravision   VIEWER                4/1/11 Alberta Electric
                                                                        System Operator
                                                                        (AESO)

e-terravision   ETV36943   e-terravision   VIEWER               8/25/11 American Electric
                                                                        Power - Dallas
                                                                        (CAMS)
e-terravision   ETV37101   e-terravision   VIEWER            1/13/12 American
                                                                     Transmission
                                                                     Company, LLC




e-terravision   ETV37116   e-terravision   DATA SERVER       1/26/12 American
                                                                     Transmission
                                                                     Company, LLC



e-terravision   ETV37170   e-terravision   VIEWER            3/21/12 American Electric
                                                                     Power - Dallas
                                                                     (CAMS)
iGRID           PD23467    iGRID           GRID             11/16/06 Australian Energy
                                                                     Market Operator




IMAGE           PD33656    IMAGE           AUTOGENERATION    2/11/09 American Electric
                                                                     Power
Nhood   PD36295   Nhood   CLIENT   11/8/09 Australian Energy
                                           Market Operator




Nhood   PD36295   Nhood   CLIENT   11/8/09 American Electric
                                           Power - Dallas
                                           (CAMS)
Nhood   PD36295   Nhood   CLIENT   11/8/09 Alstom Grid




Nhood   PD36295   Nhood   CLIENT   11/8/09 FirstEnergy
                                           Corporation
SMP   ETC36680   SCADA-SMP   Process Starter    4/2/10 Manitoba Hydro



SMP   ETC36829   SCADA-SMP   MISC               8/2/10 Bonneville Power
                                                       Administration




SMP   ETC36863   SCADA-SMP   SCADA             8/30/10 Connecticut Valley
                                                       Electric Exchange




SMP   ETC37141   SCADA-SMP   SPACESAVER        3/18/11 Manitoba Hydro




SMP   ETC37152   SCADA-SMP   CFE_READER        3/30/11 Western Area Power
                                                       Administration - CA
SMP   ETC37153   SCADA-SMP   ALARM        3/30/11 Western Area Power
                                                  Administration - CA




SMP   ETC37290   SCADA-SMP   ALARM        8/31/11 Deseret Power




SMP   ETC37293   SCADA-SMP   CFE_READER    9/6/11 Dominion Virginia
                                                  Power




SMP   ETC37301   SCADA-SMP   CFE_READER   9/22/11 Connecticut Valley
                                                  Electric Exchange
SMP   PD15885   SCADA-SMP   MISC          9/9/04 PPL Corporation




SMP   PD20747   SCADA-SMP   CFE_READER   1/27/06 Hydro One




SMP   PD21031   SCADA-SMP   SCADA        2/24/06 Hydro One
SMP   PD25682   SCADA-SMP   ISD      7/17/07 Manitoba Hydro




SMP   PD28054   SCADA-SMP   ALARM   11/26/07 Deseret Power
SMP   PD33700   SCADA-SMP   CFE_READER   2/18/09 FirstEnergy
                                                 Corporation




SMP   PD33964   SCADA-SMP   SCADA        3/19/09 Alstom Grid




SMP   PD35339   SCADA-SMP   SCADA        8/11/09 FirstEnergy
                                                 Corporation
Title
The definition of "how many" decimal places to
display is not clear




Dataman Logging HI519 msg - Sampler to RDB
transfer is slow. Can offending recording
definition be logged?




Auto Recreate index to resolve Msg Indx across
all key columns on table schema.key_tble not
detect"




DTS Simulation Control Parameters display is
confusing




DTS should support the phase shiftor MW
reference control
Retain status of unit frequency response flags
through DTS initialization



Allow breaker status to be toggled on the
BREAKER_STATUS_DYN display
Option to leave units being onlined in Local
Control




Ensure that synchronous condensers do not
produce MWs

SIR - We would like to have the capability of
adding events that allow the change of non-
simulated data across the system.


SIR - Display the Scenario Event Savecase
filename on the Scenario Event displays.


DTS Generic Underfrequency Load Shed
enhancements

Un-limited Simulation Session Snapshots
The “Create DTS Schedules” feature in RTGEN
(new in EMP2.3), which can be executed via the
TRANS_SCHEDULES_PARAMS display, needs
to be enhanced.




Quick Scenario Builder Insert at Last




DTS SIR - Add the capability to change the
Automatic Reclosure Status in a Circuit Breaker
Event




DTS SIR - When an Island collapses, do not set
the Remove flag on the
DTSEQUIP_UNIT_DATA, DTSPSM display.
Option to never use CPS unidirectional tight
control
Time error correction start and stop events in
SYSACT
Provide separate frequency bias for flat
frequency operation



ACE Diversity Interchange




Make popup displays go back to previous
display when done


Add a flag to indicate to AGC that DC tie lines
are not to be included in the ACE calculation and
in the Pause/Suspend Matrix
For Combined Cycle ST units, on Unit Details
popup show the CCYC derived LFC limits
separately.




Production Costing skips all unit calculations if
heat rate curves are not defined
improve navigation from generation telem
display to scada substation tabulars




Add 'Fuel in Use' indication on the Unit Details
popup




Add the ability to have a multiplier scalar on the
ZIN records

Control Signal column on Generation Unit Status
display and Unit Details popup should be
improved to always show something.
Add "spike" filtering capability to AGC-SCADA
interface processing.




Add Pause/Suspend threshold on the
Pause/Suspend matrix display




Create chart for ACE vs Frequency Deviation
including NERC BAAL limits
log analyst entries in addition to operator entries




RTGEN should provided alarm when
telemetered tie MWH does not match the
integrated tie MWH by more than allowed
amount




VVD should not recommend a control if the
device is tagged
Bundled SIRs 31238, 32706, 33580 related to
adding company names in all network apps
displays




Network case comparison - bus logic could be
more robust




A 'WMX' option for setting unit participation
factors would be very useful
RTNET should classify unit, load measurement
errors independently from their bus KCL
equation




Change Network Line/Transformer Summary to
allow data input
display


Combined STNETOPT savecase type for
PWRFLOW and CA solution options

QKNET should only monitor those elements
eligible for monitoring and be consistent with
RTNET.
If the branches of the interface have
measurements, the interface flow MW/MVAR
should be calcuated using measurement values

RTNET displays showing deltas between
RTNET solved values and SCADA data



Breaker Status Estimation in RTNET




 The Interface in NETMOM Shall have SCADA
analog mapped




Enable RTDCP to switch automatically to a user-
configurable standby VSAT server
RTDCP shall be enhanced with DXAPI interface




Modeling of Auxload in NETWORK APPs




Allow CA base case network quantities as
RAS/RAP trigger conditions



Add user-selectable options to the “Get Real-
Time Data” function in STNET




User-configurable savecase creation triggered
by network alarm state changes
Model data calculated from measurements for
load and generator unit




A button to "restore default settings" would be
useful


Network Apps - RTNET, RTCA .. option to
monitor based BOTH on MVA & AMPS



Create a model for a variable shunt reactor (as
opposed to just using an SVC or Synchronous
reactor)

SE/CA violations differentiated by company




Monitoring group activation functions for SE and
CA




RAS triggering conditions to be improved
New RAS actions to be supported




Improvements to RAS Validation message log




Case comparison utility should compare
OFFAVR flags

RTNET's Solution Record Display Should be
Revised to reflect the new Convergence Criteria




CA needs branch flow change alarms
New Tie Line Measurement Display in RTNET




Various buttons and displays need a more
contrasting color - EMP




Support SE robust external solution options
PS Tap Control For Individual Ctgc
Running NETVALID in EMP2.5 Against STNET
Savecases from EMP2.3 Nullifies Voltage
Solution in NETMOM.




Adding an option to globally enable/or disable a
default bus voltage monitoring




Enhance the DBResize Tool
Request for a mechanism to tab vertically
through a display with multiple entry boxes as
well as horizontally




Tab order within a picture




/ton_e-terrabrowser allows user to navigate from
test to production systems using back-arrow




create new viewport
Add delete display(s) function to DDLANA tool.




Add comment field to be added for every
element and display




Add a command to clear the command line




Improve WebFG filter



e-terraBrowser 3.6.0 and Sizeable -- still allow
minimize and maximize




WebFGUtils.exe requires admin privileges
WebFG Room definitions contain explicit layer
information




Allow the date/time format of the calendar
control to be configured




Add multiple keymaps




Enhance the F11 context shown in WebFG
Viewer to indicate whether a database field is
SELCOP or not

Condense all property tabs down to one on CAM
and CT dialog boxes.
Change FGBuilder to add Alias for display name
and enhance WebFGUtils to extract the alias
into the webfgdisplayinfo.xml file

Can not print the nhood displays via webfg
toolbar




ETB 3.6.1 file location change request
Display Menu conditions




DMS Toolbar ICONs are too hard to see (too
small) on large high resolution monitors


Provide an option to not include history in
webFG Rooms




Update the WebFG User Guide to make it
clearer just what is included in a room and its
impacts

When you create a room with the display
directory as part of the room it puts a file in the
user temp directory




Add "Always on Top" option to the Viewports
Tab
5.7 Display Builder and ActiveX conversion




Would it be possible to get an overview style
window for the display builder program? I (Dave
Collins at MH) have some large complex
overviews and having a small window that I
could use for panning and zooming around th

CAM compare time field with current time




Having CAMs react the same as conditional text
in display builder


AlarmViewer needs feature to print formated
output to file


Improve Toolbar Button UI
SIR: Improve search capability on displays and
from DB




Menus improvement in order to reduce mouse
mouvement
Changes to WebFG datapool host and addr
elements in webfg_config.xml.




FGScript grouping of conditions




Additional information to WebFG Programmers
Guide
Embedding a 3rd party script directly in the .DDL
eset




Add sort and filter application indicator to
webfgviewer client UI.



WebFG/Display builder should have a "keep
together" option for child records in a display




Add the ability to include the application and
family to display alias for e-terrabrowser

Online Help



MGE34: Background Layer Labels do not use
rotation value
Need indication of direction of power flow




Cold-Load pickup using ambient temperature in
Switch Order Management.

Create Logs of DMS Optimizations being run.




Tie operations in DMS back to switch plan being
executed in log.




Report of Temporary Network Changes
Operational Planner Reporting




Switch Order Status Improvements




Modeling Network Protectors



Modeling Network Protectors



MGE51: Process Normally Deenergized
facilities flag in the externals


Switch Order Archive Management




Tagging attributes
Easier tagging in DMS




Group Tagging for DMS


OLPF enhancements




Saving of sorting and filtering




Peer-to-Peer DA integration



Optimal Network Reconfiguration Enhancements




Dynamic Protective Device Group Settings
Improvements
Add to Emergency Load Shed Options




Make dbdef object description visible in hdbrio
and hdbexport, etc.




Inclusion of Indication on NISSED MRS
Datasets in SITEOVER, CFGMONI Display




Permit TLOGIN should be a SELCOP field
SIR - WebFG Version and Build Date on
PERMIT Workstation Modeling Display




MLF Message File Enhancement - Add support
for specifying a Windows event number within
message definition (for use with
AemlogEventCB).
Support remote alarm server with different
habitat group number



Add CFGTEAM_CLIENT to APPDEF




User-configurable savecase creation triggered
by network alarm state changes




Add option that will automatically silence alarm
when ACK or PageAck
Enhance PROCMAN to be able to test
environment variables


Create a way for the OBJDEF OVERLAY
options to work for a related (non-alarm list)
event




Add database fields to record MX, LV and RT
values



Add the ability to pass DSN via Procman
environment file
Allow -h switch in HDBRIO to work on character
and I*8 fields
Change RUSER API so that API calls made
outside the scope of a MAIL or EDEC callback
return a bad status and not cause an abort.




Critical alarm recognition; Improve standard
alarm interface




Navigation Improvments in Alarm Summary
displaysNavigation improvement in summary
displays
adding two additional displays to sampler sets




CFGTIMESTAT should be able to monitor
multiple Truetime devices from the Enabled
system
Use of CUSTOM1_ALMQ in FLAGS_ALMQ
records for custom functionality at FirstEnergy




Option to disable Sampler logging of every write
to the database should be provided
SIR: New PERMIT WebFG Display Needed
Showing USERs and USER called clones




Can a confirmation popup be implemented for
the STOPTASK button on the
PROCMAN_MASTER display?
Provide a way to have variable information in the
popup resulting from an EDEC data entry
rejection




Have EDEC popup indicate "Warning" instead of
"Entry Rejected" when predicate returns an SCF
warning code




Position of alarm list when selecting alarm
priority buttons
rovide a user enterable alarm information note
for each alarm




The alarm priorities at the substation level would
be useful if they were passed to SCADA




Rate of Change Limit processing should have
third, simpler calculation method




Multi-site front end RTU control




Change Site restore and remove keysets to not
mail messages to Tagnotes

Create Paged Tabular displays
Baud Rate is defined in scadamom as 16bit
signed int, which restricts the max speed.




WebFG Inconsistencies




SIR: Improve alarm indication to the operators
on station display.




Site Communications Status should also reflect
Tagnotes communications status

Faster and easier way to read HDR files from
non-secured lan
Request to update the CMDCONSL field for non-
telemetered points




ScadFreq should clearly alarm if frequency
deviation hits the maximum.




Create Paged Tabular displays




Request for "Range Value" functionality for
Projects


Search based on "Created from" template


Versioning on templates
Appropriate Field Width for ETS property Sheets




User parameter for "EMS Modeling Family"




Clear distinct visual difference between AC lines
DC lines

 Active Host for all DataSources WebServer
should be shown in Viewer Manager


Add support for KML hotSpot in Placemark to
anchor icon as needed
Tie Line Data in E-terravision




Show SCADA Data in E-terravision




Voltage PUV pod should show BS name


Simplify steps required to enter/toggle an
enterable mask check box on an iGrid display.




A polyline should be able to have a "halo"
NHOOD client does not allow to configure
different system (EMS and DTS)




NHOOD client does not allow to configure
different system (EMS and DTS)
NHOOD client does not allow to configure
different system (EMS and DTS)




NHOOD client does not allow to configure
different system (EMS and DTS)
Add functionality to disable serial watchdog while
ping addresses are defined.


DbUpdateCfg utility should require password
validation




Enhancements to SMP DataSet State Values
and Controls




Addition of synching the timers in SpaceSaver
(The Cleaner) to the server time.




Add support to Alstom's DNP3 implementation
for analog deadband download to RTU
Add support to e-terracontrol to allow users to
specify alarm behavior for scan group, rtu and
paths




SIR for SNMP trap functionality in e-terracontrol




Dual-ported serial RTU logic needs improvement




Add analog deadbands in DNP
Manual Actions in SMP GUIs should be logged




Set Point Error not returned to EMP




A simple solution is needed to the problem of
relays of mixed types within a single card.
Quality is not used correctly when a
measurement is assigned to two ISD data
sources.




Alarm pager should include alarm timestamp
within email text.
Request to improve the polling sequence used
for the DNP protocol




Request to support Active Directory groups for
viewing Area of Responsibility data.



Application similar to HDBRIO for e-terracontrol
SCADA
Description
when requesting a data analysis of an analog point, the user couldn't see the levell of
detail (number of decimal places) he needed for the point (Frequency Deviation is
measured to 4/5 decimal places).
Number of decimal places is defined for display is on the Data Configuration/Column
definition/"Data Analysis" sub-section.
The user (one doing Data Analysis) should be able to specify what degree of detail he
wants returned in a query. Therefore it seems to me there should be a place to set (or
override the default setting) on the Data Analysis forms.
Additionally, there seems to be no documentation at all on "Decimal Places"
definition in "Data Analysis" on "Columns" form. I did a search through all my eTA
docs and could find none.
I have a request for dataman logging. Example of an HI519 message (Column
separation in the GUI denoted by commas):

10/08/2006 11:00:44 d, SPPDMA, "Processing time for Sampler to RDB transfer is
41 secs. Application may be slow to respond to requests and to other transfers.",
HI519, SPPMKT_DM2B, W

Is it possible to add the offending definition to this message? It is telling me that a
definition took too long but does not tell me which one. This makes it difficult to
troubleshoot.
Two Ideas for Resolution

1.The Data Manager could, based upon a configured flag, re-create any Database
Index when it detects this condition.
2.The eTerraArchive Transfer Record Details page could give users the ability to re-
create the Index (using the checkbox method with SAVE click to start the process).

The DTS Simulation Control Parameters display makes the distinction between
'Buffered' and 'Non-Buffered' parameter data.
The difference between the two types is that when the simulation is running, changes
to Non-Buffered parameters are picked up on the very next simulation cycle, whereas
the DTS has to be paused and then continued to pick up changed Buffered
parameters.

This is quite reasonable from a developer perspective, but there is no reason that the
user should be concerned with the difference between the two kinds of configuration
data, it only confuses them.

A customer made a good suggestion that we drop the distinction on the display, and
simply hide the input fields on the Buffered parameters when the simulation is moving
forward/continuing.
Currently DTS only supports the phase shiftor TAP control and it will be great that
DTS can support the phase shiftor MW reference control.
 In order to realistically simulate ISO-NE response to disturbances, the frequency
response on ISO-NE units is disabled in the DTS. For hydro units only, this disable
flag is reset during DTS initialization requiring the DTS operator to stop PSM,
change the flags back using hdbrio and restart PSM. Please provide an option to not
clear this flag.
Allow breaker status to be toggled on the BREAKER_STATUS_DYN display

 Currently the "online" button will put the unit in local, close the unit breaker, ramp the
unit to its ecomin and then flip the unit back to agc. What happens is that after the
unit is placed in local it may receive a UDS DDP that is less than its actual - because
UDS solved to the last RTNET solution. This will then ramp the unit down. Leaving
the unit in local will give the unit a chance to get a DDP that is within its limits and
then the instructor can flip the unit back to AGC.
Some synchronous condensers can get into a state where their wmech_un is non-
zero and it never gets set to 0. If a unit has dreac_un =true it is a synch and should
have its wmech_un set to 0 on initialization.
When creating an Event Scenario we would like to have the capability of adding
events that allow the change of non-simulated data across the system.

(From John Lyerly with Progress Energy Training.)

When a Scenario Event Savecase is in the work-area, display the Scenario Event
Savecase filename on the Scenario Event displays.

(From John Lyerly with Progress Energy Training.)
The DTS Generic Underfrequency Load Shed include some way to manually trigger
load shed.

Un-limited Simulation Session Snapshots, management directory.
Current Product

Currently, the logic for the automatic schedule creation feature does not look at the tie
line flows in NETMOM (in DTSPSM), but only at the total net interchange in
GENMOM (in RTGEN). The auto creation logic works by taking care of the biggest
mismatches first (scheduled vs current interchange). The logic works, but is not totally
comprehensive or intuitive with regards to the simulation in DTSPSM.

As can be seen from the following screenshot of the DTS_GEN_AREA_SUMMARY
display in RTGEN (captured after executing the auto scheduler builder), the auto
scheduler does not create schedules for all OPAs. The OPAs with scheduled
interchanges equal to zero are those who were not assigned a schedule, while the
OPAs with scheduled interchanges that are non-zero are those who were assigned at
least one schedule (if more than one schedule was created for a given OPA, the
value displayed is the total of the schedules).

One reason for an OPA not being assigned a schedule by the auto scheduler is that
the current logic cannot create schedules for OPAs who do not have any transacting
partners with current net interchanges in the needed direction. For example, if OPA1
has an ACE equal to (-1000), and its only possible transacting partner is OPA2
(defined by TSTRTY records in GENMOM) whose ACE is equal to (-900), then the
auto scheduler logic will not create a schedule for OPA1 because OPA1’s only
possible transaction partner also has a negative ACE.



Proposed Enhancement

The automatic schedule creation feature needs to be enhanced such that a user-
selectable option is introduced that would allow the auto creation feature to create
As of today, when selecting an supported equipment from SCADA, Network,
Generation or DTS display, the related event action is automatically inserted under
the currently QSB time record. However, the insertion is made at first. Since the
instructor defines the actions on paper chronologically, leveraging the QSB virtual
key, the instructor is required to defined her/his scenario in the reverse order ensuring
the final scenario is as defined chronologically on paper. This enhancement will
consist in modifying the QSB functionality to insert the selected/related event action at
last of the currently QSB time record.
please submit the following as an SIR to be eligible for voting during this year's DTS
User Group and next year's general User Group meetings. Thanks - let me know if
you need any other information.
For e-terraSimulator, (component = DTS):
Add the capability to change the Automatic Reclosure Status in a Circuit Breaker
Event.

Brady Williams
Progress Energy Carolinas
Energy Control Center
(919) 546-2401
When an Island collapses, do not set the Remove flag on the
DTSEQUIP_UNIT_DATA, DTSPSM display.
The CPS code automatically sets the flags for unidirectional and tight control when
there is a disturbance. There should be an option to not use this feature.
Provide an option to issue an event message to SYSACT whenever time error
correction begins and ends.
ISO-NE had a hunting control system while in the flat frequency mode. This is
because the 1% industry standard for normal operation had a value more than double
the pre-entered analyst-entered frequency bias setting would be selected over the
value normally in use as soon as the operator selects the flat frequency AGC control
mode.
NPCC CO1 CO10 working groups have proposed an ADI project in which ISO-NE,
PJM and NYPP pass their Area Control Error to a master site which then computes a
'regional' ACE and ADI term that is sent back to each site. Each site then controls
their respective systems to the non-native ACE if ADI Enabled or to Native ACE if ADI
not Enabled. We would like this incorporated into the product.

There are popup displays on the AREA_STATUS display with Done or OK buttons
that specifically call up AREA_STATUS, which we don't use.
If they were changed to call up the previous display, they would work with any display
they were called up from, not just AREA_STATUS.
The current (EMP 2.5) AGC implementation treats DC tie lines the same as AC lines.
This means that any error between scheduled and actual flow is treated as part of
ACE that should be controlled to. Likewise telemetry failure of a DC line will cause
AGC to pause/suspend.



A switch should be added to have AGC exclude DC lines from affecting ACE and the
pause/suspend matrix conditions.



Submitted via web portal:

Ray Wensley

AESO

403-705-5224

ray.wensley@aeso.ca
Confusion has occurred in the past for some EGAT users, when the PLC limits are
smaller than the sum of the unit limits.
For example, the Current Cycle LFCMAX for a steam-recovery unit may be higher
than the heat-recovery from the 2 gas turbines. The suggested changes on the
UNIT_DETAILs display are requested for enhancement:
(a) add another line for steam-recovery units, to show the limits derived from the heat-
recovery curve.
(b) Current Cycle for a unit should include the limit imposed by the curve, so that the
sum of the unit LFCs always matches the PLC LFCs.

[Peter Vickery -- 18/May/2011 20:29:06]
Manoj, please fix the description of this enhancement then return the ticket to me. I
will then copy it from this project ticket to an R&D ticket.

[Manoj Sinha -- 05/19/11 0:41:16]
The limit of ST in a combined cycle group is calculated based on the total CT limit and
corresponding MW on the ST curve (heat rate curve for ST in CC group).
In the unit detail pop up display, this calculated ST limit should also be visible to the
operator to avoid any confusion regarding the current limit being used by AGC.
This confusion gets more abetted if an additional telemetered source of (LFC) limit is
also available and the user has selected the option to use the telemetered limit.
The current limit being used for ST in the combined cycle group is telemetered or as
If none of the units in the area have heat rate curves defined (as sometimes happens
with market systems) PC doesn't do any of the unit calculations.
While most of the PC data is irrelevant if there are no curves (costs, fuel usage, and
emissions don't apply) the MWH calculations for the 'Actual' costing type could still be
done.
Currently the popups on the generation telemetered data display allow the operator to
go from the generation display to the appropriate substation tabular for the zin or zout
by selecting the substation name on the popup. It was pointed out that it would be
better if selecting the name brought up the tabular positioned to the appropriate
analog/point/etc. This can be done by using the "find" command in the keyset. For
example, changing
keyset DISPLAY_SUBSTN_TABULAR from

set KEY201=%fv%; display/app=SCADA substn_tabular

to

set KEY201=%fv%;
display/app=SCADA/find=(devtyp=%devtypid_zin%,device=%deviceid_zin%,analog=
%objectid_zin%) substn_tabular

works just fine for analogs. Since the same keyset is used for both analog and status
popups, and the analog popup is used for both analogs and counts, it means we need
different keysets for each type of data, and a way on the analog popups to
differentiate between analog and count. We should be able to do this by using the
indirect pointer from the zin/zout to the ztemp, and looking at objtype_ztamp.

For zout popups, you can't actually navigate to a setpnt or ctrl record since they aren't
shown on the tabular, but instead are accessed from a popup associated to the
parent . We don't have the information on the generation side to know what the
parent of the setpnt or ctrl record is, but we should be able to navigate to the first item
Currently the user needs to call up the Unit Fuel Mix Schedules display to see the fuel
or mix of fuels in use. It would be helpful if they could see that data on the Unit Details
popup. This will require a new field in GENMOM database to hold that data and
maybe changes in the PSASCHEDS API. When a fuel mix is in use, the field need to
show the names of both fuels being used. Perhaps there could be a way of tieing this
back to the 'Local fuel identifier' for each unit when the fuels are assigned to the units.

Currently, the AGC/SCADA interface processing as defined with the ZIN records
supports the ability to have an adder to the SCADA value using the Base Value field.
Please also consider supporting a multiplier Scalar to the SCADA value.
Currently the Control Signal column on the Generation Unit Status display and the
Unit Details popup only shows the control value for the cycle that was issued in the
just finished cycle. Otherwise it is blank when the PLC is on automatic control. When
it is not on automatic control it occasionally shows some other info. This should be
changed so that it always shows the last control sent (either pulse or setpoint) with the
value being shown in the normal black color when it is for the current cycle and in
white or some form of low intensity when it is not for the current cycle. In addition it
would be nice if a tool tip was attached to the value where the tool tip indicated the
timestamp at which the last control was issued. While we haven't implemented any
tool tips with variables defined in them the FG group has indicated it can be done.
See Sree Sundaram or Jim Nesbitt for questions about this tool tip functionality.
A recent spec requested that the AGC SCADA telemetry processing support "spike"
filtering which would "delay accepting significant step changes for one scan,
discarding the value if the change does not persist with significance limits adjustable
for each type of variable". The default spike threshold for a measurement type will be
specified on the ZTEMP record and the ZIN level threshold will be defaulted the first
time the ZIN is validated just as is currently done for the similar values. The ZTEMP
value will only be enterable in modeling but the ZIN value will be enterable in
modeling and online. The spike threshold will be an absolute limit, as opposed to a
percentage. If the spike threshold is zero then the feature is considered disabled.
Modeling validation and realtime entry processing should make sure that if the spike
threshold is greater than zero that it should also be greater than the existing value for
the "change threshold" at both the template and ZIN levels. In addition the existing
change threshold field processing should be changed so that it is an error if the
change threshold is greater than the spike threshold when the spike threshold is
EMP2.5 includes a new popup showing each Pause/Suspend condition for AGC and
the current state of that condition. Using this popup, the operator can quickly see the
reason the system is Paused. The implementation is such that it is easy to extend this
list to include other Pause/Suspend conditions.



Currently, this implementation did not change the source of the threshold for the
various Pause/Suspend checks. For example, the ACE to Trip check uses a field on
the OPA record. The various Pause/Suspend thresholds are scattered on various
RTGEN Analyst displays.



This SIR suggests putting the Pause/Suspend threshold on the record of the
Pause/Suspend matrix and removing them from the other analyst displays. In this
way, when the operator sees a Pause condition active, he can also see the threshold
associated with that condition. An analyst version of this popup will be used to enter
these thresholds.



At the same time, we should add another field on these Pause/Suspend matrix record
to support calling up a related display. It this way, when an operator sees a Pause
condition active, he can select the button for the related display and the stored text
EMP2.5 includes support for NERC BAAL limits. When this criteria is selected, it
takes the place of the L10 limits of the NERC CPS2 criteria.



EMP2.3 and later include a chart imbedded on the Area Status display showing a
scatter plot of ACE vs. Frequency Deviation. This chart includes straight lines for the
+/- L10 limits. When NERC BAAL criteria has been selected, there should be a
version of this chart that shows the NERC BAAL limit curves in place of the straight
line L10 values.
Currently in the generation code we issue logging alarms for most of the operator
entries, but almost none for the analyst entries. A request has come in to do this.



Initial investigation in the EMP2.5 product indicates that about 335 field entries are not
being alarmed in the edec.for routine, another 35 in the agcut codeset, 70 in the lf
codeset, and a few others in other codesets. In addition to logging field entries,
various actions that indirectly change the data should be logged (i.e., where a
command is issued to the edec processing code instead of a direct field entry).



Besides adding the alarm calls to the code (which requires in most cases setting up of
the data to be passed to the alarm) the new alarms (400+) need to be added to the
rgalm database. For record types that currently have no entry alarming the format of
the alarms needs to be determined, which may require additions to the rtgen.almmsg
file and new exception definitions. (Issuing alarms for long text fields can be tricky.)
For LF and perhaps some other generation codesets, displays will need to be
modified to issue edec commands on data entry. Also note that the sizing of the rgalm
database needs to be increased.



It is suggested that instead of trying to come up with 8 character names for the new
alarms that indicate the specific field being alarmed, OEnnnnnn be used instead, or
perhaps OEOPnnnn for OPA analyst entries, OPUNnnnn for UNIT analyst entries,
etc. There will be enough work coming up with the alarm text for each field without
trying to create unique names for the alarms themselves.



It is expected that detailed analysis of Tie MWH valued from SCADA. These values
Currently EMP supports import of the the changes to be made, including writing a
can be used to calculate Tie MW Error Adjustment parameters based on comparison
to the RTGEN integrated MWH value.



Please add a check and alarm for when the telemetered MWH is different from the
integrated MWH by more than a mismatch threshold.
When a device is tagged it should be considered unavailable.
VVD does not currently recognize the tags, and may recommend moving a tagged
device as a control.
VVD should recognize the tags, and avoid recommending a tagged device.

This SIR was written on behalf of BCTC. (Related project SIR: PJ28408)
SR# 2-22644:
Bundle SIRs 31238, 32706, and 33580. These are all related to adding the company
and division names on Network related displays and messages

31238 - Add Company/Division information on the RTNET MISMATCH_BUSROW
display
32706 - Add company ID information in Network Apps display violation messages
33580 - Add company ID information on RTNET's TELEMETERED_ANALOG and
TELEMETERED_ANERROR displays

This is a low resource SIR that involved making small modifications to network
common utilities code, a few displays, and a simple DBDEF change. (I estimate it
took us no more than 16 hours each to code and test and that is very conservative.)


The case comparison logic does the bus comparison by identifying each bus by it's
assigned node (I$ND_BS). This works fine most of the time, but will fail under some
circumstances.

Because each bus in the reference case is identified by its assigned node, if that node
becomes assigned to an open bus or to the null bus in the working case (as can
happen if the ND is associated with a branch or shunt device that is disconnected in
the working case), then the case comparison logic will use the node's primary bus in
the working case for the comparison. This may not be what the user would like it to
do, since the original bus (a non-primary bus) from the reference case may be largely
intact in the working case, except for the disconnected component, but the
comparison logic will compare it with its primary bus in the working case.

A more robust approach would save information for each node in the reference case,
instead of for each bus. During the comparison with the working case, some
consolidation could be done based on bus assignments to avoid comparing the same
buses twice in the comparison report. So the report could be based on nodes, but
avoid duplicate comparisons of the same bus.
Often when a power flow solution can't be achieved, it is because the unit MW
participation factors are not good. The iterations may try to draw too many MW from
small units, which can cause extreme voltage swings on small radial units, and non-
convergence can result. For those cases, a solution can usually be achieved by
setting participation factors to the unit MW capacities.

The use of WMX values as participation factors should be supported as a global
option in the study power flow, and possibly in RTNET and OPF as well. This option
would work like the existing normal/long/short global options. It would set only the
working participation factors, and would not overwrite the normal participation factors.
Currently RTNET lumps all shunt injection measurements in with their bus KCL
equations when it does 'error processing'. This means that all devices at a bus are
flagged the same (normal, suspect, anomalous), even if their measurements have
different accuracy class assignments with different breakpoints. (Breakpoints define
the 'number of sigmas' to be classified as suspect.)

The existing approach could be improved, such that shunt injection measurements
(or pseudo-measurements) could be independently classified as to their error status.

 The change I would like to see is to be able to enter updated Nominal KV
voltage levels for Transformers in the Network Line/Transformer Summary
display. In the screen shot below the current Nominal KV is From:138 and
To:342. These values are fixed and enterable only from eTerra Modeler and
then a database update. I would like to be able to change them on-line.
Currently, STNET has separate savecase type for PWRFLOW and CA solution
options. It will be great if a combined STNETOPT savecase type can be created to
store both of them.
Right now, QKNET monitors almost all the network elements, most of which are from
external in some cases. I suggest QKNET should only monitor those elements eligible
for monitoring and be consistent with RTNET.
In QKNET, if the branches of the interface have measurements, the interface flow
MW/MVAR should be calcuated using measurement values.


 These displays would be similar to the telemetered network data views. The desired
delta and number of differences to report will be user entered values. Separate the
displays by categories: Units, lines, zbrs, transformers, etc. Other information would
be availability and quality of the data and whether it has been auto-disabled.

For buses where there are obvious inconsistent flow measurements (such as net
injection exceeds a threshold) the system shall perform breaker status estimation on
the affected portion of the network and try to resolve the problem before state
estimation..

 The Operator will still see the SE give good results when there are manual switches
or telemetered breakers with wrong status.
 The interface defined in NETMOM shall have a SCADA analog measurement
mapped in RTNET and QKNET. The limit of the interface shall be able to be copied
from the limit of the SCADA analog.

 The operators will see consistant limits on interfaces beteween SCADA and all
network applications. The only place the need to change the limit is at SCADA
Add functionality to enable RTDCP to switch automatically to a user-configurable
standby VSAT server if the enabled VSAT server does not return results within a user-
configurable time period. Currently the RTDCP solution would just continue to fail
indefinitely (return ABNORMAL COMPLETION status) as long as something is wrong
with the enabled VSAT server. Same functionality for TSAT server is suggested.
Increased availability of VSA/TSA results
The RTDCP shall be enhanced with DXAPI interfaces so that the voltage limits and
interface limits calculated by VSAT and TSAT can be exported via DXAPI and
imported to SCADA and/or other network applications such as RTNET.

 The operator will see a dynamically updated limits on key buses and important
interfaces with reflectes the current status of the transmission network.
 The network application shall enhance the modeling of auxload. Auxload shall have
MW/MVAR analogs mapped to SCADA and a load curve associated with it. In
RTNET the Auxload will use the SCADA measurements to set up the basecase.
while in CA, Powerflow and DTS the auxload will adjust its MW/MVAR value based
on the load curve.

 The Operator will have more accurate study results in CA and DTS where there is
large auxload for generating units.
Currently only post-contingency network quantities are supported as trigger conditions
for a RAS or RAP. Missing ability to specify basecase (pre-contingency) network
conditions such as a line MW flow as a trigger condition in RAS and RAP definitions
in RTCA and STNET CA more remedial action schemes/plan (RAS) can be
modelled and evaluated in CA solutions.
It would be useful if the "Get Real-Time Data" button in STNET allows the user to
select which of the following data to copy from the real-time applications into
STNET:
	RTNET solution i.e. switching device statuses	us voltages etc. (currently always
•                                                 b
copied)
•
	Network Limits settings (currently always copied)	   	
	Network Monitored Element settings (currently always copied)	
•                                                                  	
•
	Contingency definitions (currently always copied)	   	
•
	RAS definitions (currently not copied)	 	
	VSAT case definitions (currently not copied):	
•                                                	
  Give operators more flexibility and more coverage over what real-time data is
copied into STNET from the real-time applications like RTNET, RTCA and
RTDCP. Sometimes operators and engineers make parameter changes
  in STNET for their studies that will get overwritten every time they run "get real-
time data".
This was originally submitted under habitat but was advised that it belongs under
power apps.


Add functionality that gives the user the option to specify independently for each
network alarm a user-configurable savecase (application type and savecase type)
that will be created when the alarm state changes to ALARM and a second savecase
that will be created when the alarm state returns to NORMAL	    with a “one-shot” vs
“retriggerrable” setting. The savecase name must be timestamped (i.e.
"yyyymmddhhmm" in the savecase name). A logical display to place these
configurable parameters may be on the Network Alarm Inhibit Control display
(ALARM_CATRTNET). This capability would facilitate the creation of savecases to
capture snapshots of abnormal system conditions for post-event analysis and
troubleshooting.
Model data can be calculated from available measurements for loads and generators.
However, there are several problems in the current version of this function:

1. When both load and generator are present, it fails to calculate
2. MVAr load is not calculated even whne there are immediate MVAr measurement to
determine to model data
3. EMP2.5 support group measuremets, ans so should be this function

It would be helpful if there was a button to restore the default values of RTNET's
parameters. This would be similar to using a savecase, but more convenient. The
default values of all parameters could be saved in a file. (Most likely, this approach
would support only one default parameter set.)
WECC receives branch limits (e.g. LNLIM, XFLIM) from our transmission owners as a
mixture of MVA limits, and AMPS limits - however, WECC is currently set up to only
monitor MVAs.

Enhancement to be made to monitor based BOTH on MVA & AMPS
Utilities are starting to use variable shunt reactors. Modelers can model these devices
as synchronous reactors or SVCs as a work around, however it is more desirable to
have a model that simulates the behavior of a true variable shunt reactors including
regulating taps, etc.
In the current SE/CA violation list, there is no company information associated with
each violation. We'd like to add the company (associated with monitored element) for
each violation and provide the capability to filter or differentiate the violations between
them. (color coding or something else). Also we'd like ETV to have a way to
differentiate those violations based on this company information.
Current EMP has the capability to activate/inactivate the monitoring group which can
be based on company. However there is no way of doing that for contingency. For
example, there is a line contingency (this line belongs to AEP) and it will cause the
violations outside the AEP company. If we setup the monitoring group so that we only
report the AEP violations, then this contingency violation will be filtered out since it is
outside AEP. However we'd like to see this violation gets reported since this
contingency definition belongs to AEP. It will be good EMP can separate the
monitoring group activation functions for SE and CA. In base case (SE/CA), we only
need to activate the AEP monitoring group but in post contingency we can monitor all
the companies.

User Group SIR request - Yuan Li, ISO-New England, yli@iso-ne.com

(1) the “status” in the pulldown menu is not straightforward for operator. By default it
means open. But it would make the definition clear with “open” or “close”. 	

(2) voltage drop criteria to be introduced

(3) “active” status to enable /disable the gate input individually
User Group SIR request - Yuan Li, ISO-New England, yli@iso-ne.com

New RAS actions to be supported:

(1) Set AGC flag. This will be helpful to solve contingency case with new island.

(2) MVar change for the load

(3) “active” status to enable/disable the actions individually

User Group SIR request - Yuan Li, ISO-New England, yli@iso-ne.com

RAS Validation message log is not that convenient for the user to troubleshoot the
RAS model errors. It would be more desirable for the users to locate the invalid RAS
gate input or action definition directly from the webFG display without navigating to
the log display.
The powerflow case comparison utility should compare OFFAVR flags of units and
SVS, to make it easier to determine differences in which devices are type-switched.

RTNET's solution record display in EMP 2.3
(RT_NETWORK_SOLUTION_RECORD) needs to be revised to reflect the new
voltage/angle convergence criteria. The new convergence criteria is based on the
voltage magnitude and angle differences across branches (see Brian Brewer from
Areva for more details). The solution record display will be much more helpful if it
includes the branch name (LN or XF name) along with the existing "from" station/bus
information. The "to" station/bus information would also be nice but it would require
additional columns and would not provide as much incremental benefit.

We would like to be able to identify contingencies that cause a significant change in
MW flow, even if they do not cause any normal contingency violation. This alarm
would be triggered either by a reversal in flow direction (which is why we need to look
at MW) or a large change in flow magnitude.
RTNET needs to have a new display added to the product that displays all tie line MW
and MVar measurements, as well as the corresponding solution values for each tie
line. This would allow analysts to quickly and easily identify residuals on tie lines.

One good example where this proposed display would be very beneficial is when
RTNET solves with an excess mismatch due to the "Total Tie Line MW Error" or
"Total Tie Line MVar Error" exceeding the user-defined thresholds (TTLNTOL1 or
TTLNTOL2 fields in the SEMATRX database) found on the SOLUTION_QUALITY
display. Currently, when this occurs, the analyst is sometimes forced to manually
search through the BUSES or TELEMETERED_ANALOG displays tie line by tie line
in order to find the measurement(s) causing the excess mismatch. This requires the
analyst to have an intimate familiarity with all the tie lines, their locations and their
measurements. This also can be time-consuming. As one can imagine, the proposed
display would allow analysts to quickly and easily identify residuals on tie lines.

The proposed display should be a hybrid of the layout and designs of the
TELEMETERED_ANALOG and LINE displays in RTNET, as shown in the screenshot
contained in the attachment. A new navigation tab needs to be added onto the
"Telemetered Network Data" family of displays.

Likewise, RTNET needs to have a new display added to the product that displays all
generation MW and MVar measurements, as well as the corresponding solution
Currently buttons are almost the same color as the background of a display. They
should be a somewhat contrasted color (maybe a grey). I have missed clicking a
done button in the process because it was easy to overlook.

Also text that blinks is not visible 50% of the time. The blinking text should blink
between 2 visible colors.

Sometimes RTNET solves with very low or high voltages in the external areas due to
lack of good modeling of external voltage/var support. Besides being an unrealistic
solution, it can cause solution problems in CA, which does not handle extreme
voltages very well. (Seen at BCTC to cause CA solution failure.)

Also, RTNET may not converge at all due to the same causes - poor modeling of
voltage/var support in the external.

I suggest that RTNET be enhanced to support two related options:

Option 1: model all external units as being on AVR, and ignore corresponding var
limits (no type-switching). For those external units without a voltage regulation target,
use a default per-unit value.

Option 2: same as option 1, except this approach is employed automatically if, and
only if, RTNET first solves with unreasonable voltages in the external using the
normal external modeling. Put all ext. units on AVR, turn off external var enforcement,
and re-solve.
There are a few Phase Shifters modeled in AEP EMS system. Current CA application
provides the capability to enable the PS tap movement in the post-contingency for all
defined contingencies. However, in some cases, the global flag is not good enough.
For some special contingencies, we’d like to see both post-contingency scenarios
with and without PS tap movement.

The proposed enhancement includes the following:
1)Add FRZPSTAP_CTG in QQQ_CTG field in ctgs.dbdef
2)In subroutine CA_SET_DPF_CONTROL_OPTIONS, change the input parameter
from ISCTG (Boolean) to CTG (int). And the content of this subroutine is modified
to:
      IF(CTG > 0) THEN
       ! prepare for the control options for the contingency dpf
       IF(IAND(QDPF,FRZCTRL_ITEMS_DPF) .NE. 0) QDPFW =
IOR(QDPFW,FRZCTRLW_ITEMS_DPF)
       IF(IAND(QDPF,FRZUNAVR_ITEMS_DPF) .NE. 0) QDPFW =
IOR(QDPFW,FRZUNAVRW_ITEMS_DPF)
       IF(IAND(QDPF,FRZXFTAP_ITEMS_DPF) .NE. 0) QDPFW =
IOR(QDPFW,FRZXFTAPW_ITEMS_DPF)
       IF(IAND(QDPF,FRZPSTAP_ITEMS_DPF) .NE. 0 .OR.
    &      IAND(QQQ_CTG(CTG),FRZPSTAP_CTG) .NE. 0 ) QDPFW =
IOR(QDPFW,FRZPSTAPW_ITEMS_DPF)
       IF(IAND(QDPF,FRZCPAVR_ITEMS_DPF) .NE. 0) QDPFW =
IOR(QDPFW,FRZCPAVRW_ITEMS_DPF)

    ELSE
     ! prepare for the control options for the basecase dpf
     IF(IAND(QDPFB,FRZCTRLB_ITEMS_DPF) .NE. 0) QDPFW =
IOR(QDPFW,FRZCTRLW_ITEMS_DPF)
     IF(IAND(QDPFB,FRZUNAVRB_ITEMS_DPF) .NE. 0) QDPFW =
IOR(QDPFW,FRZUNAVRW_ITEMS_DPF)
     IF(IAND(QDPFB,FRZXFTAPB_ITEMS_DPF) .NE. 0) QDPFW =
IOR(QDPFW,FRZXFTAPW_ITEMS_DPF)
Netvalid Nullifies Voltage Solution in NETMOM. This has been always the case. But
becomes a problem for FE when upgrading Solved Netmom savecase from EMP2.3
to EMP2.5.
FE is currently in the process of migrating from EMP2.3 to EMP2.5. One of the
conversion requirements of our operations is to maintain the numerous STNET
savecases that were created on EMP2.3 in the new EMP2.5 environment. Many of
these savecases are STNET.NETMOM type savecases that are automatically
created after each RTNET execution for historical data purposes (the NETMOM from
RTNET is saved into a STNET.NETMOM savecase). These savecases provide for
FE historical information on past RTNET solutions and performance, as well as
possible evidence in the case of regulatory audits, investigations, etc…	

Part of our process to migrate these EMP2.3 savecases into EMP2.5 is to run
NETVALID against the NETMOM in the EMP2.3 savecase. However, doing this
results in the voltage solution in NETMOM being completely wiped out. In other
words, the following fields are nulled out by NETVALID:
 K
•	V_BS	
 V
•	_BS	
 A
•	DEG_BS	

Because FE requires to maintain and archive previous RTNET solutions, running the
NETVAILD against the NETMOM database in these savecases during the migrating
process results in loss of the voltage solution. Hence, FE is not meeting our
conversion requirements.
Refer to the attached document for the rules of voltage monitoring and puzzle. The
existing voltage monitoring functionality (EMP2.3 and EMP2.5) skips the default
voltage monitoring if it performs NDLIM monitoring at the bus, or it performs non-
default voltage monitoring at the nodes of the bus.
The buses can be monitored more than once only if they have multiple nodes
that are individually non-default monitored, or if the bus is found to have
multiple NDLIMs with different limits. Otherwise, buses are each monitored
once at most.

The proposed user-configurable option would allow the default voltage monitoring for
the bus. Thus, it allows buses to be monitored more than once if that bus contains:
  NDs with NDLIM limits, or NDs with non-default VLIM monitoring, monitor and
report one violation for each ND.
  NDs without NDLIM limits, monitored these NDs using VLIM
  limits and reporting one violation per bus.

If the option is reset off, then the the existing voltage monitoring functionality should
be resumed. Some customers want this way.

07dec2009[bjb]: The proposed global option will cause a bus having default-
monitored nodes w/o NDLIMs to be monitored using their VLIM, even if the bus is
Provide the following enhancements:

1. Provide an option to export the records alphabetically in each mxdef file.
2. Allow user enter comment instead of just putting “ # File xxx.mxdef generated by
Database Resize Utility” in each mxdef file.	
3. When using “Show Final sizes too small” function, provide an option to also
include MAXLV record.
Example display: RTGEN GEN_UNIT_LIMITS display. It has several enterable
columns. If one wants to change all the data on one unit, one can go to the first
enterable field on that row, and tab along. But if one wants to change all the Cur Cap
data for a bunch of units, one has to do a bunch of tabs across to get to the same
column in the next row. It would be nice to have the following behavior:

tab -- move right horizontally   shift-tab move left horizontally -- have this now

now ctrl-tab -- move down vertically and ctrl-shift- tab -- move up vertically

SR# 2-22650:

Add the ability to specify a tab order within EACH picture. Options should include:
- Horizontal by placement (aka how it works now)
- Vertical by placement
- Tab order on each field format (much like designing a form in MS-Access or other
apps)

IE, some pictures might follow the default horizontal sequence, another vertical, and
another by individual specification of tab order.

Alternate: Use tab order specification always, but in builder add some buttons to “pre-
calculate” the tab sequence based on vertical or horizontal placement.

Open an eterrabrowser session on a production EMS. Navigate to several displays in
one or more viewports. Save the room and the navigation history for each viewport is
saved in the room.
Then start a eterrabrowser session on a qa/test EMS system, load the room then use
back-arrow, eterrabowser will use the history and navigate the viewport to the
production EMS system. Eterrabrowser does bring up a login popup, but the user may
not be aware that he is logging into a production EMS. That viewport is now on
production and all other viewports are on the qa/test EMS.
This could cause operational errors to occur. FE would like to either remove history
from the room or allow a configuration flag to not save history in the room.

Would like the ability to create a new viewport & callup a display into it - without
having to specify a name for the viewport.
Add a delete display function to the DDLANA tool. This option would allow the user to
specify one or more displays that should be deleted from the target DSET DDL files.

For example, the syntax for this command would be:

ddlana delete sourceDir -d displayName[s]

This would cause ddlana to remove the specified displays from the dset ddl files in
the specified source/target directory.

Additional functionality notes from customer:

"What I’d really like it to do is remove the display and all elements for that display that
are not used by any other display. However, I wouldn’t want it to do a full clean
because the EMP display files have some unused elements that I don’t want to get rid
of because that would just cause more differences between EMP and our files."



From the customer:

The display builder be enhanced to allow comments to be entered on every element
and display.


We have an issue where a button in a display a keyset with something like:

display/app=scada substn_list

If the operator has a string in the command line, then it is automatically appended to
the display name (substn_listtemp for example if temp is in the command line) and of
course there is no such display, so the commmand fails.

Please if I could prepend a "CLEAR" or some such command to clear the command
line, I could be sure that I avoid this problem.


In the WebFG filter, provide a mechanism to filter only certain records.

For example, I want to set all the stall checking values in the Procman Model display.
I’d like to see ONLY task records – no path, node, flag, etc.
from the customer:

 If I set the Sizeable of the Viewport to "No", the Minimize and Maximize buttons in the
taskbar will disappear. We really need the Minimize and Maximize buttons when the
Sizeable of the Viewport is set to "No".

So the expectation is that perhaps one can't resize the windows by dragging it
vertically or horizontally, but one can still either maximize and minimize.
When users do not have admin privileges they are unable to execute webFGUtils.exe
to validate the database links in displays.
 explicit layer information is always stored. If operators create individuall rooms and
the display developer adds layersthe Rooms will not call up the new layers and data
will not be visible. We would think that the majority of Room definitions would NOT
want to limit which layers are visible yet that is the only supported option. Critical data
can be hidden from the operator. Requiring the operator to recreate individual Room
definitions is cumbersome and problematic.
From the customer:

for the calendar control that is brought up when you double click on an enterable time
field on a webFG display, our operators have discovered it and want to use it.
However, it always tries to enter it as, for example, 31-Mar-2001 16:00:00. But that
isn’t our time format as defined in the timedate config file – our format is 03/31/01
1600:00. Because the format is wrong, the entry isn’t actually accepted.	
We would like to be able to configure the date/time format used by this control.

Provide a mechanism to provide different keymap settings for different users. For
example, the only a DTS intstructor or analyst should have the keyset for the Quick
Scenario Builder. Whether this is via different files, or by checking AREA and/or
Application permissions , or ??. Definition should be maintained on the web server,
not individual workstations.

This information is needed sometimes when an operator or support engineer need to
know whether a certain database or network model value will be overwritten by the
next database update.
See attached .ppt for an example.

Please allow the addition of an alias to Display Properties in FGBuilder and then have
WebFGUtils extract that information and place it into the webfgdisplayinfo.xml files so
that people don't have to manually add this information to these files.

The print button on the webfg toolbar does not print when on an nhood display. The
print function from the menus does print but instead of printing the nhood display you
are on, it prints the parent display that took you to the current nhood display. Please
add the functionality to the button so the nhood display you are on gets printed.



Customer would like to have a user defined parameter that tells the system where to
put the client logs and dump files instead of using the /Users/UserID/e-terraborwser
folder. They would like to keep all logs and dump files in a central location.
Customer would like a way to put permissions or CAMs on display menus, so that
either a different menu shows up on top of the display or some items in the menu
show up or not, depending on the permissions or CAM?

Here is the problem we’re trying to solve. Our onelines are compiled under various
applications, including DTSPSM. We have a menu called Application at the top of all
the onelines that lists these applications and bring up the same oneline in the chosen
application. The EMP60 onelines have the same menu, but it is labeled “Onelines…”.
We do not want DTSPSM to show up in this menu on the EMS, just the DTS.
Because we don’t know how to put conditionality on the menus, we end up needing
two sets of onelines, one to use in the EMS without DTSPSM in the menu, and with it
to use in the DTS. It would be nice to just keep one.

Another example would be not wanting to show the Analyst Displays menu for users
without analyst permission. On our pure EMP2.6 system with EMP60 displays, I took
away analyst permission, and the menu was still there with all the same entries; I just
couldn’t bring anything up. So if display menu conditions are possible, the EMP60
30" high-resolution monitors (something like 2500 x 1600) were purchased for the
DMS project. However the toolbar icons (both standard and DMS specific) are too
small for the operators to easily see. Can the size of the icons be increased?

From the customer:

The history in webFG rooms includes the name of the system where the room was
created, which is not necessarily the same system where the room is called up,
especially for support people who use webFG to access many systems. That means
that using the Back button could suddenly call up a display on a different system,
maybe even Production, and the user might not notice this. We consider this to be
dangerous, and would like a way to turn off the history in the rooms. We also aren't
convinced that it is intuitive to have the Back button take us to the display that was
previous when the room was created instead of the display that was up before we
called up the room.
a user should be aware that history is there, and that if they call up a room and then
use the Back button they will go to the display that was previous when the room was
created (and that might even be on a different system), not the display they had in
that viewport just before calling up the room
Customer would like the file name to be meaningful and not some random naming
convention so users do not accidently delete the file when cleaning up their PC. An
example is below:
CallupStr="%BASEURL%/webfgdirectory.htm?frame=left&appfilter=SCADA&are
as=C:\Users\lmclaughlin\AppData\Local\Temp\tmp7FBE.tmp" />

They would also like to have the document changed so that someone who does have
a private room and wants the display directory in it knows that this file is part of the
room and shouldn't be deleted.
User Group SIR request - Seth Fischer, ISO-New England, sfischer@iso-ne.com

This way, users can make sure a viewport stays on top. I believe this is possible if
defined in the display. I’m just saying it would be useful to have it be an option on the
Viewports Tab at runtime.
User Group SIR request - Lynn McLaughlin, ISO-New England, lmclaughlin@iso-
ne.com

If you bring a display from the 5.6 builder into the 5.7 builder without the -convert
switch, it tells you it will convert your FG colors, but it doesn't tell you that it won't
convert the activeX controls.

Several people have thought that it does all the converting that is necessary. Please
either change the popup to say in big, bold letters that if it won't do so, or change it so
that it will.
Would it be possible to get an overview style window for the display builder program?
I (Dave Collins at MH) have some large complex overviews and having a small
window that I could use for panning and zooming around the display would be very
helpful. I would refer you to AutoCAD and it''s Arial view option for an example of what
I am talking about.

Several EMP tasks, like SCANNER and RTGEN, update a habitat time field with the
time of the last "heartbeat" cycle. We plan to display these times as an indication of
the health of the applications.

We'd like for WebFG to provide a CAM to be able to compare the time in the habitat
field, with the current time and if the difference between the habitat time and the
current time is greater than a user defined value, we'd like to change the color or the
displayed time.
Customer reference: MH1238
Title: Having CAMs react the same as conditional text in display builder
Description: Show effect of CAM clauses within pictures as toggle through conditions,
same as CTs do
PSE customer asked "Please provide a feature in AlarmViewer to allow printing
selected or a range of pages to a file. File types could be txt, MS Word Doc, Excel,
text comma delimited, or PDF." And verified here at AREVA, the set page function
seems already here.
From Customer:

The present toolbar buttons are not keeping up with the expected graphical interface
standards. The buttons should be "toggle" buttons that show depressed when
selected and normal when unselected. We have to have a drop down menu to
unselect the action of pressing the button.

Improved UI and standard grahpical interface with other off the shelf products.
NOTE - This was submitted as WEBFG by customer, but after phone call to clarify, it
is apparent this SIR implementation may require multiple product updates. The main
goal by HydroOne was to get it in the UG SIR list for discussion. DevTrack only
allows one product, so submitting as WEBFG. See Notes.

Scott Vidler
Hydro One
705-792-3020

On displays that are very "busy" such as sub-transmission displays, operators have
can have a difficult time finding switches or DS (Distribution Station). A method to
enter the station name and have it retrieved from the DB and selecting it and having
the required display open and centre on the selected station would be a great asset.
Calling a DS from a menu should open the required sub-transmission display and
centre on the station.

What does this mean to the Operator?:
This would improve the capability to find stations that are in the dB but not necessarily
on a menu especially on large cluttered displays.

It would be helpful to have the capability to attach a default display to a menu so that
one would not always have to select one of the menu item,.

For example when selecting the "HABITAT Applications" menu, one gets a list of
items with "Alarm" as the first one. Then you have to mouse over "Alarm" and move
the mouse to "Alarm summary" and click. If we could attach a default display at the
level of the "Alarm" menu, one could click here and get to the default display (which in
this case wouild likely be the Alarm Summary display). This would help reducing the
mouse mouvements.

This feature would just mimic what MS Office provides in term of menu selection.
Changes to WebFG datapool host and addr elements in webfg_config.xml.



Currently under a datasource you can spec a max of two hosts and each host can
have a max of two addresses:



  <datasource id="default" provider="RdOleDB">

    <host>

       <addr id="HOSTA"/>

       <addr id="HOSTA-2"/>

    </host>

    <host>

       <addr id="HOSTB"/>

       <addr id="HOSTB-2"/>

    </host>

  </datasource>



I'd like to see the following changes:
Enhance FGScript to allow grouping of tests.
For example,
	 (
If          (“AREA1” read_permmited and unack1_area true)	
              OR (“AREA2” read_permmited and unack2_area true)	
              OR (“AREA3” read_permmited and unack3_area true)	
              OR (“AREA4” read_permmited and unack4_area true) 	
      )
gab
(
blink
)

Action: Enhance FGScript to allow grouping of conditions so complex test will work
properly.
Complete the WebFG Programmers Guide (webfg_pg.doc). Including a section on
using “Third Party Scripting”, documentation on the COM interfaces to WebFG and
the DOM available to 3rd party scripts (document, etc…). The Document! X product
from Innovasys provides a good starting point.
Allow embedding a “3rd party script”, JavaScript or VBScript, in a CAM directly in the
.DDL eset file like FGScript is. Currently the script code must be in a separate file on
the web server.

Action: Modify FG and the FGBuilder to also allow the script text in a CAM, JavaScript
or VBScript, to embedded directly in the .DDL. An external script file should still be
supported.
Add an icon/symbol to the webfgviewer viewport that indicates whether or not a filter
has been applied to the display that is currently in the viewport. Likewise, add an
icon/symbol to the webfgviewer viewport that indicates whether or not a sort has been
applied to the display that is currently in the viewport. Perhaps place this indicator in
the status bar/tray at the bottom of the viewport.
WebFG / Display builder should have a “keep together” option for child records in a
display. Currently, there is only a # of picgroups per display setting. But when the
number of children per parent is indeterminate, you can get records at the top of a
page without their reference parent. This should apply on hierarchical and driving list
tabulars. For example, the contingency analysis displays, with a parent contingency
and child violations.


Currently the feature to have an alias for a display is part of e-terrabrowser. The
customer requests that there be the ability to include the application and family for the
alias too.
We would like to see online help for DMS. EMS has Help on
Display/Function/Application - Not available yet in DMS Operator has to look in
manuals instead of using online help.

Background Layer Labels do not use rotation value. Shannon thinks that code change
is required to support this. MG&E has tagged as item for SAT.
MORE INFORMATION:::::::It does not appear that any layer other than roads is
respecting the label rotation values, and that the naming convention for the roads
layer might be hard-coded. The request is that rotation values be respected across
the board. This would include label-only layers, as well as layers that have the
drawing and labels all in one.
Need some sort of visual indication of the direction of power flow. This is needed in
the looped or meshed areas of the network (nominal and abnormal). Note, it is
understood that constant moving arrows is not realistic, but something more ad hoc
where the user selects a line section and clicks a button to request the direction of
power flow.


Here is some feedback from the MGE customer......
Ryan, I kind of like the way SynerGEE does it. They give you a display option
that can display arrows for various flows. They display the arrows right
on the lines. PSS/E displays both Watt and Var flow arrows (at the same
time, in two colors) offset from the lines. This is difficult to interpret
in dense areas.

Another thing to consider is how to relate the sign of the flows in the
attribute window to the map direction. I don't think we would be able to
maintain any kind of node1/node2 directionality logical in the GIS. I
don't want to have to do an network trace as part of my extract to
determine node order, and then do a bunch of swaps. Maybe if the
directional arrows were displayed automatically on the analyst window
callup. Maybe have two arrows of different colors and sizes displayed over
the line? One for watts, one for vars?
The DMS has a cold-load pickup model as part of the load allocation process but it
does not directly include ambient temperature. Running switching to take into Cold-
Load Pickup temperatures will make for easier restoration.
No Logging of DMS Power Flows. VVM or other optimiziations is kept. Operator
actions are logged. but a summary of results from each iDMS function is not logged.
If results are necessary to be kept, you can make a save case. But having a log of the
summary results is what we would like to have in the System Log. Operators are
running Power Flows to verify switching operations are within limits. They need a way
to log that they performed the necessary PF calculations before the switching
operation and be able to point a specific switch plan back to their running of the PF
calculations. Without logging that a PF was run, they have no way to prove they are
using the system.
Tie the System Log entries of switching being done in DMS back to the associated
Switch Plan being executed. While logging is done and can be sorted by AOR. The
actual steps cannot be tied back to a specific plan. Operators need a way to show
which actions were part of a approved plan and which where not. The System Log
does not tie actions back to an approved switch plan.

Provide a report of all Temporary Network Changes, including Cuts switching not in
normal state. The person responsible for the nightly update for us that is an operator
will need to look at all items that are temporary and then confirm they all made it to
the post update system. No Zombie changes left over.
"b) System performance Reporting: Historical archiving solution for DMS is part of
our roadmap. Support for time series data sampling to EDNA and e-terraarchive.

i. Total real and reactive load and percent loading by feeder.

ii. Min and max voltages by feeder

iii. Max % loading on any line section or transformer on each feederiv.

iv. Min and max power factor by feeder

v. Total system losses

vi. Customer count by substation and feeder when in normal or abnormal
configurations.

Operational planner would use these reports.

Prior to placing a switching order in the Scheduled status, it shall be possible for the
user to specify the probability (high/medium/low) that a job will be scheduled. In
addition a hold status on the Switching Order rather than moving the date out.
Operator currently changes date when orders are on hold. we would like a hold
status. Also a way to community likelyhood of switch.
MGE Model contains Network protectors none of which are SCADA modeled. Our
Model and topology processor don't have network protector functionality coded in.


MGE Model contains Network protectors none of which are SCADA modeled. Our
Model and topology processor don't have network protector functionality coded in.


In continuation with MGE 30 (ETD 41528 / ETD 41997), the server and client codes
need to be enhanced to respect the NORMDEENERGIZED flags added to the
devices Next actions: Sree to write up a document and review with Paul describing
the plan Generate a detailed implementation plan Implement the plan
Switching orders shall remain available in a library of switching orders until deleted by
the switching order's creator or the system administrator. Governance over who can
edit, maintain and delete specific switch orders allows for orders to be editted or
deleted by anyone who has access to the file. it is not managed at a by order basis
and thus ownership and governance over who is editted what is not known.

Add switch order number and the expected duration to the Tagging Attributes for a
Tag. Operator would like to know which tags are associated with a specific switch
order. Also the duration of the tags.
i) If a tag is associated to a switch order, the system shall automatically assign the
corresponding switch order number to the tag. Otherwise the DMS shall automatically
assign a unique tag number Tag numbers are typically unique. The user shall have
the option to enter a comment when placing a tag. Currently the switch order
number does not exist within the DMS system. A switch order name is given instead
of a switch order number. The tag number can be manually entered and comments
can be entered when placing a tag. Operator needs automation associated with all
the tagging that is done on the DMS system.

The system shall allow the user to place tags by group of devices. Tags added by
group may be removed individually or by group. This is critical as we have large
amount of tagging to be done in DMS.
No automatic restart is done when conditions change.
Color for Tab display Red for out of limits caused by OLPF but Pop up does NOT
have color validatation.
Voltage and current results for a feeder section are accessible by selecting the
section and invoking a results pop-up display but Pop up does NOT have color
validatation.
Need mouse over display with color for alarming.
When conditions change running the OLPF automatically should always run so that
operator is making decisions based on the current state. Getting to the results of the
OLPF should be transparent and easy for the operator to make the best possible
decisions.


All tabular-oriented views shall support user-defined sorting filtering and searching
based on any combination of user-selected fields without restarting the system or
logout/re-login. User changes shall be automatically saved for the next login as an
option. This is what is currently not happening. There is no option to choose to save
sorting at least. Filtering could be a safety issue. He has to manually re-setup
sorting and filtering with every logon. It is not saved in the room. With iDMS there is
more data to look at sort.

The DMS shall integrate with switches and fault interrupters equipped with peer-to-
peer communication facilities for fully automated distribution control. If the DMS
executes planned it must provide the ability to easily update the configuration of the
distributed control system to a new normal state.
The specified future time period shall be adjustable from a minimum of one day to
seven days. The DMS shall produce a list of recommended switching actions to
perform over the user not look for the peak in the next window. Currently the
Operator would have to know the peak in the next seven days rather than having the
system suggest it.
How settings are communicated to remote DA devices is critical to their operation in a
changing distribution topology. DMS shall allow the definition of protection device
group settings (i) notify the ECC Dispatcher of the suggestion to change the
protection group settings or (ii) automatically send remote commands to change the
protection group settings. Protection operating correctly directly relates to safety for
Operators.
"b) When emergency load shedding is requiredthe user will activate the ELS function
and enter the amount of load to be shed. The ELS shall then determine which
switching devices to operate to accomplish the load shedding objective. ELS shall
allow the user to shed load using the following load shed facilities:i. Remote
connect/disconnect and direct load control features for AMI meters at specified
individual customers. The actual load shedding of these customers shall be
accomplished by the AMI system upon receipt of a command from DMS.ii. Remote-
controlled line reclosers load break switches and sectionalizers located in the field
(outside the substation fence). These remote-controlled switches shall enable the
DMS to shed the load served by a portion of the distribution iii. Feeder circuit breakers
and reclosers located in the substations. These devices shall be used to shed an
entire feeder.iv. Substation transformer switches located on the high-side (supply
side) of the substation transformers. These switches shall be used to shed the entire
load served by the affected Emergency Load Shed should be flexible for operator to
maintain as much reliabilty as possible.
It would be very helpful if you could see the description of data objects (from dbdef)
within hdbrio, hdbexport, or anything that's looking at the schema.

I understand that these descriptions today are in free comments format and would
probably be "attached" to an object in dbdeft to make it work.

I suppose the really tough part is to attach existing comments to proper objects, but
maybe it could be accomplished over time.
TRANSPOWER had recently had a significant incident with MRS on their system.

One of the key factors uncovered during the incident review was that the SITEOVER,
CFGMONI Display provided no visual indication to analysts that there were
Application Sets NISSED. Customer TRANSPOWER believes this is a significant
omission in the design of this display, given it’s key role in determining the
serviceability of the system.

Future versions of the Display (SITEOVER, CFGMONI Display) do provide a visual
indication that application sets are NISSED. A suggestion would be a number;
i.e. 0 = no application sets NISSED, 3 = 3 Application sets NISSED etc.


Suggest changing the TLOGIN field to selcop. The TLOGIN field in permitnv should
not be updated during a permit database load.

Glen Collins
The PERMIT ACTIVE_SESSIONS display shows the WebFG client workstation's
WebFG version and build date, but only while the workstation WebFG client is
actively connected. It would be very useful if the Workstation Modeling display
included the WebFG version and build date at last login for each workstation.

The reason I’m suggesting this is for a couple of reasons - First, when managing
upgrades, it would be a great place to see which workstations have been upgraded
and which have not without having to look through logs or wait until they are logged in.
We have some workstations that use the same user, so associating this with a login
would not be beneficial. Having a specific list would be easiest to use and the
Workstation Modeling display seemed like the most sensible place for it. Secondly, if
we have issues reported, one of the first things we want to knowf for troubleshooting
is what version and build of WebFG they have.

Notes:

- We realize the Workstation (WS) display is a modeling display that is not meant for
run-time information, but it is the most convenient existing display to show this
information. Similar to how the amplified USER Modeling display has a Last Login
indicator for each USER, which is field TLOGIN_USER in the PERMITNV database.
What I'm suggesting is something similar to this.

Add support for a new statement in a message definition to specify a Windows event
number to be used with AemlogEventCB.


The current alarm supports the remote alarm server with the same habitat group
number. It will be great if it can support remote alarm server with different habitat
group number.

We've made the change by our own and pls contact us if you need it.
SR# 2-53042:

For situations where customers may want to run CFGTEAM_CLIENT under
PROCMAN, it would be nice if the application was defined in the CFGTEAM.APPDEF
file. We can customize our own, but if worked into product file, will not have to redo it
if patched in the future.
Add functionality that gives the user the option to specify independently for each
network alarm a user-configurable savecase (application type and savecase type)
that will be created when the alarm state changes to ALARM and a second savecase
                                                                w
that will be created when the alarm state returns to NORMAL	ith a “one-shot” vs
“retriggerrable” setting. The savecase name must be timestamped (i.e.
"yyyymmddhhmm" in the savecase name). A logical display to place these
configurable parameters may be on the Network Alarm Inhibit Control
display(ALARM_CATRTNET). This capability would facilitate the creation of
savecases to capture snapshots of abnormal system conditions for post-event
analysis and troubleshooting.
When alarms are acknowledged, also silence the alarm if there are no remaining
unacked audible alarms
We have separate PROCMAN models for DTS and EMS and some differences
between production and development systems. It would be nice to have a single
model, and have PROCMAN be able to do tests on environment variables as well as
PROCMAN flags, or in order to set PROCMAN flags.
Create some kind of configuration or API option so that the OBJDEF OVERLAY
options for Ack or Delete can work when a new non-alarm list "event" is posted for an
OBJDEF which still has a "related alarm" in the list.

It seems like making it a model option (such as on the EXCDEF) would be cleaner, as
an API option would complicate matters since it would imply even more changes
needed in the client application. (Scada being the usual suspect.)

Here is information on the customer motivation, as it may have a bearing on the best
way to implement such an option:

SR# 2-62542:

I would like to submit an alarm subsystem functionality change request. We use
Overlay/Del on object definitions. One problem with this is that when a breaker is in
alarm that it is OPEN, then a user sends a control to close, the commanded breaker
operation is not posted as an alarm by the scada client. Therefore the OPEN alarm is
still in the alarm summary.

Customer further explained that they use the "Prevent Abnormal Alarm Deletion"
feature on some CATs, so once it goes OPEN, that point is considered Abnormal.
The CLOSE is not even alarmed, so the entry in the alarm list never changes from
Abnormal, and thus cannot be deleted. It becomes a sort of "orphaned" alarm. They
use the "force purge" feature to remove it, so it is not stuck forever. Just not ideal.
Customer would like to be able to display LV, MX, and RT values in a display
(especially OAG displays).


(SR 2-69622 - Contact Randy Suhrbier)
Customer would like the ability to pass DSN information via the Procman environment
file instead of having to model it into the Dataman model.
HDBRIO lets me use the -H switch to see an integer*4 value as hex, but nothing
else.

I'm having a problem with a character field and I would like to be able to tell if it has
blanks in it, or something non-printable, like 0s. Please enhance HDBRIO to show
character fields as hex, and while you're at it, consider other formats, like I*8. (I*4
and I*2 fields do currently indicate in hex when using that -h option for "read" or "/".)
As reported/requested by Lynn McLaughlin:

I’m making an RUSER API call in RTGEN, sometimes from the EDEC processing
and sometimes not. My code checked the status and aborted if scf_bad was true,
which was true when I wasn’t in the EDEC processing. The .err file says it has to be
called from within an RUSER transaction, which makes sense. So I took the
osal_abort out of my code and tried to do something different depending on whether
the status was good or not, and it aborted anyway. A closer look at the .err file tells
me it was actually in ruser.cpp. And a closer look at the documentation does say that
if “called outside the scope of the user mail or entry callback, the RUSER is aborted.”	

Please change the RUSER API to return a bad status instead of aborting when called
outside the MAIL or EDEC entry callback scope, or for any other reason.

The standard presentation of alarms is chronological order with the most recent alarm
at the top of the first page. The standard presentation can extend for many pages as
a function of the system activity. The “Critical Alarm Recognition” provides ready
identification of the user specified alarms that generally affect the integrity of the
electric distribution system without having to page down in the Unack Alarm list or in
the Abnormal Summary to identify these users’ specified alarms.

Navigation improvements in summary displays include:

1. Add “Go To Top” and “Go To Bottom” of the multiple page summary display, i.e.
Event Summary, Unack Summary, etc., that use the Page Down and Page Up
buttons
to navigate the display;

2. Make the summary a continuous display with the vertical scroll bar to navigate the
summary;

3. Provide for sorting the summary for specific Device Type and Point Name;

4. Reformat the Message column in Unack Summary to the filterable columns found
in the Abnormal Summary;

5. Provide filtering feature by date range

6. Provide a freeze frame feature for use during high activity periods to ensure
visibility of critical information until user can take necessary action, or minimize the
scrolling of the summary so that the critical information does not seem to disappear
from the current view.
There were a number of problems with the DDL sent. Most of these
problems related to using WebFG vs RapportFG. Since we are still in
RapportFG, I had to remove the WebFG display navigation, and did a quick
port of other issues (colours not supported, etc), but tried to keep
them as close to the WebFG standard as possible.

That said, there were STILL these problems, which may or may not be in
the product version:
- sampler debug display
 - toggle keyset for LOCKDBG flag was for PERMDBG flag
 - LOCKTMDBG was displayed as a toggle, but is an integer value
(keyset toggled PERMDBG flag)

- sampler performance stats display
 - user record: messages written & byte count fields way too
small -- only showed stars. # messages should be at least 6 chars & #
bytes at least 8 (I changed to 7 & 11 for all three rows, so they all
lined up, and enough room. We are in the 100,000's for # messages and
10,000,000's for # bytes).
 - items picture: same: increase # messages to 7 char (maybe not
enough still?) and # bytes to 11 char. Currently in 7 & 10 digits
already on our system!
 - the SAMPLER_DB_PERM display still needs the LOCATION field for
alarms to be added to the display (RDR_PDCR_116/117). (I did not change
this, yet)


Manitoba Hydro has added two other displays to SAMPLER sets: "permanent
requests summary" (set MH_SAMPLER) and "out of date definitions" (set
MH_SAMPLER2). We find these displays very useful. The first lets us
very quickly scan all requests to ensure that they are (a) recording
samples and (b) recording definitions in eterra-archive are catching up
(used primarily after a failover). The second its monitoring of two True Time devices.
Habitat 5.5's CFGTIMESTAT has improved display is similar, but
By default, CFGTIMESTAT monitors the True Time device only when it has the
Enabled role. However, you can configure it to monitor one True Time device from
the Enabled host and the other device from the Standby host, by defining the
environment variable CFGTIMESTAT_STANDBY_ACTIVE.

However, this is not total redundancy of the True Time devices, as there is no
automatic failover from one device to the other. And CFGTIMESTAT should be able
to monitor multiple (e.g. more than 2) Truetime devices from the Enabled system, to
make it a very good product. There is decent 3rd party software that can handle
multiple Truetime devices for time syncing (at least on Windows) and handling failing
over to alternate time sources if one fails.

*** On 2006 SIR Voting List ****
*** On 2007 SIR Voting List ***
*** On 2008 NA-UG SIR Voting List ***
FirstEnergy is looking for some custom functionality on the ALARM summary.
This applies both to WCC (HAB54p20041029 / emp22p20041029) and RCC
(HAB55p20050331 / EMP23p20050331).

I have searched the HABITAT_SRCDIR\RCSE\ALARM codeset for both
HAB54,HAB55.
On the ALMQ records, I can find NO reference to
CUSTOM1_ALMQ...CUSTOMx_ALMQ

I would then assume ...
I can link CUSTOM1_ALMQ on a ALMQ picture using FGBuilder...
I can set or clear the bit using data entry DICE...
I can tweak the ALARM source code to behave based on that field...

Can you confirm that CUSTOMx are intended for customer use?
Notice the lack of comments in the ALARMLST.DBDEF excerpt below...

//FIELD FLAGS_ALMQ B*4 FILL=00

//MASK NODEL
T = the alarm cannot be deleted

//MASK CUSTOM1
//MASK CUSTOM2
//MASK CUSTOM10
T = custom flag is set

(1)
The dispatchers want certain alarms to be exempt from ACK or DELETE actions.
Create a “DO NOT ACK or DELETE” icon that appears on each ALMQ record
(picture).
The icon is linked to CUSTOM1_ALMQ for that record.
If the button is depressed (active, TRUE)the alarm is ignored.
Customer reference number is: SR 1-13513894
Customer Contact is: Anita Lo

Sampler logs every write to the database with log entry is SA030. Our ultimate plan is
to model 40 writes every 60 seconds, which will make the log useless. Admittedly,
being able to log writes would be quite useful in a debugging situation, because
Sampler's update is made directly against the Hdb database, and there is the
potential for another application also updating the same database resulting in
Sampler's updates being overwritten . Therefore we propose that an option be
provided to disable Sampler logging of every write to the database, which could be set
after the configuration was thoroughly tested.

*** On 2007 SIR Voting List ***
*** On 2008 NA-UG SIR Voting List ***
There needs to be a new WebFG display created for the PERMIT application that lists
every USER who is currently logged into WebFG on the EMP, and lists every clone
that the USER currently has a WebFG display opened into. This is especially needed
for the STNET application where not enough clones exist for all USERs who need to
run studies, and they need to use an STNET clone without taking over a clone that
another USER is already utilizing. This display also needs to dynamically refresh itself
without having to be manually refreshed by the user.

This display needs to have two views:
1.The first view needs to list each USER who is currently logged into WebFG on the
EMP. Underneath each USER, every clone that the USER currently has a WebFG
display opened into should then be listed (and the time stamp that the last display
pointing to that clone was called up). This view should be filterable by USER.
2.The second view needs to list every clone on the EMP. Underneath every clone,
each USER who currently has a WebFG display pointing to that clone should then be
listed (and the time stamp that the last display for that clone was called up). This view
should be filterable by application.

*** On 2008 NA-UG SIR Voting List ***


From SR# 2-10841:

Can a confirmation popup be implemented for the STOPTASK button on the
PROCMAN_MASTER display? (Similar to what was done for the overall PROCMAN
EXIT "STOPAPP" button.)

FE reported -
"A support person accidentally aborted the WFGSERVER task from within Procman
on the enabled EMS system. WFGSERVER was restarted via the command line (and
outside the control of Procman). An emergency failover was later performed to allow
Procman to regain control of the process. We feel that a confirmation window would
have forced a re-evaluation of the abort command and could have saved us the
outage."

Perhaps a confirmation popup can be implemented in a way that is a configurable
option to avoid others complaining about needing to confirm a task stop.
SR# 2-13928:
Provide a way to have variable information in the popup resulting from an EDEC data
entry rejection, to avoid having to make a different SCF status code definition for each
desired unique message.

(ISONE's example - They can only update a field if another has not been updated
within the last hour, based on a "last updated" time stored away, so there are 1 to 59
minutes to wait until being able to update the value. So when the EDEC check fails
and does not update the data in the database, they want to return information that
includes how many minutes remaining. But that would require 59 SCF codes/text.)

(1) One way would be to make the SCF facility more like MLF, where parameters can
be passed to form the string. Since SCF is not a function call like MLF, and just a
code definition into a constant, this does not seem likely.

(2) Another would be to change RUSER_SEND_MESSAGE so it can work from
inside the RUSER entry predicate function. They tried using it, but it is inert. The
code does not seem to harm the program, but it does not work. This limitation is not
documented, but the RuserSendMessage source code header comments implies a
known limitation going back to CG:

"** For CG console dialogs, this function may be called to send a
** response back to Rapport-CG and to terminate the dialog at the same
** time, i.e. if this function is to be called, it must be called within
** the within the scope of the user defined callback functions and
** outside the scope of the entry predicate callback, and
** calling this function has the same effect as calling RAPUSER_END."

Or any other way to do allow what ISONE wants to do.
SR# 2-13928:
When the RUSER EDEC entry predicate function returns an SCF WARNING status,
have the resulting popup indicate "Warning" instead of "Entry Rejected."

The webfg_rm.pdf states, "The validation callback should examine the entry for
validity and return RUSER_S_ACCEPT if the entry is to be accepted. If the entry is to
be rejected, an SCF status code of severity ERROR should be returned. The text
string corresponding to this code will be logged."

ISONE has a special case where the EDEC predicate code will begrudgingly accept
the data and write it to the database, but they want to indicate a warning to the user,
so they return an SCF warning code. This results in a popup to the WebFG user
indicating the SCF code and text, but it is always preceded by "Entry value rejected."
(See attached BMP image.) Since the value is actually being kept, the words do not
match reality. Indicating "Warning" when the SCF code is not an ERROR would
resolve this.

If an alarm priority is selected and the list is scrolled down, selecting a different priority
button does not position the list to the top and it remains scrolled down. The operator
could miss the most recent alarms in this instance. The list should be repositioned to
the top.
Create a field to allow the user to enter an alarm note or information about an alarm.
This should be accessible from the alarm summary display.The user would be able to
enter information associated with the alarm such as what to do when this alarm
comes in or why the point is in alarm. This should note or information should be a
user enterable field that is is only removed or updated when the user removes the text
or modifies the field. The field should be at least 160 characters. The operator will
be able to see why a point is in alarm and/or a more description of what the alarm is
and what actions should be taken when the alarm comes in. The note will remain
with the point even after the point returns to normal so that the next time the point
goes into alarm the operator will have information about the alarm. The operator will
have the ability to enter, modify or remove the text in the alarm note.

I would like to see the alarm priorities at the substation level somehow passed to
SCADA so that I can make our Overview display more useful.

Currently the SCADA database has one flag that rolls up ALL unacknowledged
alarms and that provides too much information to our operators. I would like to be
able to pick individual priorities and color them through a CAM.

For example, if my main concern was equipment failures I might want to know if there
were priority 1 and priority 2 alarms. If I were concerned about communications
failures I might want only priority 3, or non critical might show up as priority 5 and the
Substation indicator colored appropriately.
Neither of the two methods of computing rate of change will generate an accurate
slope under normal circumstances. The "with timer" method uses an obsure least-
squares method resulting in a percentage rate of change. The "without timer" method
is calculated every value change, and so the "average" is over the last two changes,
not over the last period of time.

What is needed is a simple average calculated every minute (or other configurable
period of time), which will result in accurate units, such as "feet per minute".

With the ability of EMP to gather point data from multiple sites (SMP front ends), it
would be nice to have some control at the EMP level as to which site is allowed to
actively scan, rather than having to navigate to two (or more) front ends. For
example, we have two front end redundant pairs, but older RTUs are only single
ported. Only one of the pairs may scan. We have to navigate to two different SMP
Comstate displays, NIS the RTU/paths on one, and then enable them on the other.
Note that this ability must remain compatible with having both SMP front end pairs
polling other RTUs, where there are dual-ported RTUs.
The restore and remove commands for Sites include mail to Tagnotes, but not
everyone uses Tagnotes and therefore must customize this keyset. A different keyset
should be used for systems without Tagnotes.
If you use the combo box on the SCADA tabulars to go to an extremely large
substation, it takes a long time to go there. Much better performance results by
having a limited number of records per page instead of a whole substation. We
implemented this with a button on the tabulars for switching between the paged and
non-paged versions.
We would like to implement baud rates of 38400 but we are limited in the scadamom
database to 32767(16 bit signed integer). I can manually enter 38400 into
scadaserver in e-terracontrol so at least 16bit unsigned is supported here and we
would like to take advantage of this without having to manually set the speed
everytime we perform a failover. We are running EMP2.5/e-terracontrol 3.5.

Can this field be changed in scadamom to 16bit unsigned since it does not make
sense to have a signed baud rate anyways?

Scada Summary Displays/Remote and Manually Entered and subsidary displays
should be consistent with the upgrade to the Substation tabular directory displays.

Calculation Information directory and subsidary displays should be consistent with the
upgrade to the Substation tabular directory displays.


There are inconsistencies across scada. Some displays ask users to use the bar in
webfg to perform the find substation search (Scada Summary Displays/Remote and
Manually Entered) while other displays required that you type it into the display
(Calculation Information display)

Scada Analyst RCONST should have find substation button to allow users to move to
other substation without having to go back to the directory.

Scott Vidler
Hydro One
705-792-3020

Presently if an exception exists on a device (transformer, breaker etc) the operator
has to manually look for it on the exception list or in some cases companies have use
extensive CAMS to provide an indication on the display. I propose that the DB be
organized so that device alarms are defined in the hierarchy as children of the device
so that a simple CAM can be used to identify on the display that there is an exception
on the device (colour, shimmer, halo etc).

What does this mean to the Operator?:
If a device has been out of service for maintenance and the operator is switching it
into service an exception on the device that could indicate an outstanding problem is
not readily identifiable. Our operators have to search out any problems by looking at
the station exception list. Having an easy method to display this from the DB visually
would be much better.

The Site Communications Status display indicates only the state of the ISD data path,
and not the Intersite Tagging path. It should display both, as they are formed
separately.
Customer suggested AREVA to provide a utility without using dataman and Oracle
DB to read HDR files from non-secured lan and dump the desired requested data to
csv file.

Currently, it takes 18 hours or more to dump data to DB for one year data and slow
down relational DB performance.
It's been seen that the CMDCONSL_POINT field is not updated when a user changes
the state of a point where the "Normal Source" is Entered. The customer would like
to have the CMDCONSL_POINT field updated for these Entered points, so the user
information will show on the SCADA Exception_Indexed display in the "Commanded
by Client" column. At this time, only telemetered points get an update to the
CMDCONSL_POINT field, indicating which user last performed a successful
supervisory control. When a status change is flagged as commanded, the command
source (CMDCONSL_POINT) is updated.

The Symmetricom Truetime device is designed so that once the device hits the
maximum frequency deviation, it will stay there until the time deviation is manually
reset. Even a momentary outage of the frequency reference will cause the device to
hit the maximum frequency deviation and stay there, even if the frequency source has
been restored. This is "by design", and there is no change in this behaviour expected
from the supplier.

However, this means that devices which are at remote sites must be visited in person
to issue the reset. Very clear alarming is needed to draw Operations attention to this
problem, so that personnel can be scheduled. And it would be preferable to have
repeated alarming if the condition was not resolved within a period of time

The workaround is to issue an alarm when the Scada measurement which is mapped
to the frequency deviation violates either an operational or reasonabilty limit. But it
would be better if an alarm was re-issued periodically, which Scada does not do. We
suggest that an Alarm interface be added to SCADFREQ generate such an alarm
periodically.

Previously ETP36856 -If you use the combo box on the SCADA tabulars to go to an
extremely large substation
 it takes a long time to go there. Much better performance results by having a limited
number of records per page instead of a whole substation. We implemented this with
a button on the tabulars for switching between the paged and non-paged versions.

We request the ability to edit Projects from the table view, and use the "Range Value"
feature to change fields for multiple projects at once. Since there might be many,
possibly hundreds of projects in a deployment, we will need the ability to do a mass
change of States or Effective Date from the Projects View.
When you create an entity from a template, you get the “Created from” info on the
property sheet. It would be nice to be able to search for that template name, to get
you a list of every object created from it.
It would be nice to have some method of versioning on templates, so you can tell
which iteration of a template was used. This would particularly be useful while the
template was being developed, to determine which version was better. And
especially nice if the ability to search for objects created from a particular template,
requested in SIR ETSO39278, was implemented.
The data fields on property sheets would be much better if they were sized more
appropriately. The current version has extremely wide data entry fields, combo boxes,
etc that span the width of the display (200+ characters wide, depending on frame
sizing). It just looks wrong, not to mention confusing, when you have a numeric field
that is approximately 200 spaces wide for a 3 digit number. This makes the fields
more difficult to locate.


E-terramodeler, while not perfect, did a much better job displaying data fields with
appropriate lengths.


This is a purely cosmetic change and not as important as getting the major bugs out
of ETS. However it is important in terms of getting the product more "usable" from a
users’ perspective.
Since there may be multiple modeling clones, or teams that share clones, it would be
convenient for there to be a User parameter "EMS Modeling Family". For customers
that have one modeling clone per User, that might always be the User name. But for
those that have modeling teams, one clone per User might be excessive.

This is similar to ETSC38107 - "Parameterize Import/Export hdb default family
names", but is different in that it suggests including a parameter on the User record,
so that multiple users could be assigned the same family.


There should be a clear distinct visual difference between HVAC HVDC lines in the
ETV viewer for both types of displays (System Overview Schematic Regional).

In the etv3 viewer Viewer Manager window the active host for each data source
should be shown not just for the NetworkDataService data source as it now. In
addition the active host (and other pertinent information) for the IIS web server
should be shown.
User would like to anchor an icon to a specific point for the placemark. hotSpot
provides this anchor but ETV doesn't support it.
ATC's model is broken down into different companies. Since the performance of the
e-terravision client degrades as you add more data to the display I would like to make
separate displays for each company within ATC's model. However this presents a
problems because of tielines. I use the hdbcsv -t c -v ATC command to retrieve the
ATC company data. The display has been built. I then use the model difference tool
within the Authoring Tool, and it shows lines that are in the model, but not on the
display. This is because the other end of the line is outside of the ATC company and
therefore not in the Grownet file. These lines are important and need to be shown.
Also there stations in the ATC company that are tapped off of a different companies
line. I can show the station on the display, but with no line. E-terravision needs the
ability to retrieve and display the tie line information. I have attached a couple of
screen shots to illustrate the issues I have described.


I (Deborah Kirner) suggested that Brad create a GrowNet for the entire model and
use his Coordinates file as a means of filtering what he wanted. He said this was fine
for the initial creation of the display but not for dealing with changes, but he more
concerned about ongoing maintenance of the display. If his GrowNet file has the
entire model, but the display does not, the model difference tool in the Authoring Tool
I would like the ability to show SCADA data within the e-terravision. I would like to
see the same type of data as what the RTNET/STNET shows. Obviously there is less
of it since you don't have SCADA on everything like network does. I would like to be
able to see MW, MVARs and voltage where available. They we have it currently, is
that that the switch statuses still come from the network applications. RTNET still
retrieves the status when it is not solving.
Current PUV pod shows the voltage information based on ND. Our dispatchers like
to see if the BS number could be added as another column.

If you have an enterable mask, in order to enter it you have to click on the check box
which will tick or untick the box, then you have to hit the ENTER key, then you have to
right click and "Save Data Changes".

It would be easier if you didn't have to hit the ENTER key.

The original email along with example screen shots from the customer regarding this
SIR is in a Word document attached to the "Notes" tab of this SIR.

A polyline should be able to have a "halo". This allows for lines to cross each other
but not touch. The halo should be the same color as the background.
Author: C VAN-ASSEL

For KOSOVO project, operator workstation running webfgclient 3.5 should access at
least to two different system (EMS for normal operation running on redundant server
(KMEMS01/02) and DTS system (KMMDL01) ).
This configuration is not possible with NHOOD client since nhoodconfig.xml file is
unique for the webfgclient and following configuration does not allow to run NHOOD
on DTS server (KMMDL01) since it connect to EMS system (KMEMS01/02) if
NHOOD server is running on EMS.

"
<?xml version="1.0" encoding="utf-8"?>
<nhoodConfiguration>

  <initDisplay maxDepth="6" defDepth="4" frameRate="6" voltageGradients="off"
alarms="on" mw="off" mvar="off">
   <services>
     <serviceUrl>http://kmems01:30096</serviceUrl>
     <serviceUrl>http://kmems02:30096</serviceUrl>
     <serviceUrl>http://kmmdl01:30093</serviceUrl>
   </services>
  </initDisplay>
"

Regards,
Christian VAN-ASSEL
Author: C VAN-ASSEL

For KOSOVO project, operator workstation running webfgclient 3.5 should access at
least to two different system (EMS for normal operation running on redundant server
(KMEMS01/02) and DTS system (KMMDL01) ).
This configuration is not possible with NHOOD client since nhoodconfig.xml file is
unique for the webfgclient and following configuration does not allow to run NHOOD
on DTS server (KMMDL01) since it connect to EMS system (KMEMS01/02) if
NHOOD server is running on EMS.

"
<?xml version="1.0" encoding="utf-8"?>
<nhoodConfiguration>

  <initDisplay maxDepth="6" defDepth="4" frameRate="6" voltageGradients="off"
alarms="on" mw="off" mvar="off">
   <services>
     <serviceUrl>http://kmems01:30096</serviceUrl>
     <serviceUrl>http://kmems02:30096</serviceUrl>
     <serviceUrl>http://kmmdl01:30093</serviceUrl>
   </services>
  </initDisplay>
"

Regards,
Christian VAN-ASSEL
Author: C VAN-ASSEL

For KOSOVO project, operator workstation running webfgclient 3.5 should access at
least to two different system (EMS for normal operation running on redundant server
(KMEMS01/02) and DTS system (KMMDL01) ).
This configuration is not possible with NHOOD client since nhoodconfig.xml file is
unique for the webfgclient and following configuration does not allow to run NHOOD
on DTS server (KMMDL01) since it connect to EMS system (KMEMS01/02) if
NHOOD server is running on EMS.

"
<?xml version="1.0" encoding="utf-8"?>
<nhoodConfiguration>

  <initDisplay maxDepth="6" defDepth="4" frameRate="6" voltageGradients="off"
alarms="on" mw="off" mvar="off">
   <services>
     <serviceUrl>http://kmems01:30096</serviceUrl>
     <serviceUrl>http://kmems02:30096</serviceUrl>
     <serviceUrl>http://kmmdl01:30093</serviceUrl>
   </services>
  </initDisplay>
"

Regards,
Christian VAN-ASSEL
Author: C VAN-ASSEL

For KOSOVO project, operator workstation running webfgclient 3.5 should access at
least to two different system (EMS for normal operation running on redundant server
(KMEMS01/02) and DTS system (KMMDL01) ).
This configuration is not possible with NHOOD client since nhoodconfig.xml file is
unique for the webfgclient and following configuration does not allow to run NHOOD
on DTS server (KMMDL01) since it connect to EMS system (KMEMS01/02) if
NHOOD server is running on EMS.

"
<?xml version="1.0" encoding="utf-8"?>
<nhoodConfiguration>

  <initDisplay maxDepth="6" defDepth="4" frameRate="6" voltageGradients="off"
alarms="on" mw="off" mvar="off">
   <services>
     <serviceUrl>http://kmems01:30096</serviceUrl>
     <serviceUrl>http://kmems02:30096</serviceUrl>
     <serviceUrl>http://kmmdl01:30093</serviceUrl>
   </services>
  </initDisplay>
"

Regards,
Christian VAN-ASSEL
It should be possible to disable the Serial WDOG even with PING addresses defined
without having to remove the PING addresses. These are still useful in the situation
without a serial wdog in that if the network card failed, then the blind node would not
become master.
The DbUpdateCfg user interface on the SMP, when entering the passwords for the
service accounts each character appears as an " * " so there is no visibility of what is
actually entered. Also, there is no re-entry to verify the password. In addition there is
no feedback from the "Save Configuration" button so it is not clear if it saved normally
or not. As a result the wrong password was entered for the Service Account, which
caused a problem during the update.

It would be helpful if the user interface could be enhanced to allow verification and
tracking of password changes.
SMP DataSet State Values and Controls currently include the Data Set's status
(STAA, STAB and STAT values), and the ability to send controls to toggle that status
(ENABLE / DISABLE (eg, Status toggle) and REFRESH (eg, demand scan). These
controls can be mapped to EMS Scada points, enabling the operator to view and
control the Communications devices without having to call up the SMP Scada
COMSTATE display.

SMP Scada COMSTATE also shows an "Alarm Inhibit" value, and this can be set and
reset from the SMP COMSTATE display, but is not available for mapping to EMS
Scada.

So that the operator can have complete control of the DataSet values, the Inhibit
value should be added to those points available to the EMS Scada, along with a
control to toggle that value.
Currently the timers in SpaceSaver are not synched to anything, they start counting
when they are started.

Is it possible to have the ability to sync these timers to the server time? Eg. An hourly
schedule with an offset (time base) of 60 would be run 60 seconds after every hour
instead of it being relative to when the schedule timer was started.
According to the documentation, RTU Initialization is a CfeReader concept which
involves placing field devices into a known state, such that normal scanning and
control may commence. During RTU initialization field devices are notified as to a
restart, if supported by the protocol, followed by downloading database-modeled
parameters such as analog dead bands and synchronization of RTU time.

There is a note that downloading of analog dead bands is not currently supported in
this implementation of DNP3 (taken from the AREVA DNP3 Modeling Guide -
2008).

The customer states:

The current e-terracontrol DNP 3.0 implementation does not support downloading
analog deadbands from e-terracontrol to the RTU. This requires e-terracontrol users
to travel to each substation to update the RTU's configuration if they want to update
deadbands for analogs to tweak scan performance.
SR# 2-61382:

The current implementation of e-terracontrol does not allow users to specify the alarm
behavior for cards, scan groups, RTUs and PATHs. For example, when we have a
scan group failure, our EMS operators on e-terrascada see the alarm for the scan
group failure, but never get a return-to-normal alarm from Alarm Pager. It would be
nice to be able to decide whether you want alarms for data set objects of all types.
For example, maybe you would not want to generate alarms on cards, but on scan
groups, or not on these, but on the RTU only.

This is a request to add functionality for SNMP traps for standalone e-terracontrol
scada.

There is no current or planned SNMP support for any e-terra application. The goal is
to have a single alarm reporting system like what's available in e-terracontrol/e-
terrabrowser except to also accept other alarm sources. Some sites have a lot of
other products that broadcast alarm messages via SNMP and it would be beneficial to
trap these for display in the e-terra product.
I believe the explanation in the knowledge base article 1405, "Further explanation of
the PortAddress2 parameter" is incorrect, and the logic does not work as stated
there.

We gathered from the knowledge base that you could model two ports for a Port
Dataset: Primary Address/ADDRESS_PATH and Secondary
Address/ADDRESS2_PATH.

We have identical RTUs on our COM1 and COM2, behaving exactly like a dual
ported RTU. So we have a single PATH modeled, and defined Primary Address to be
COM1 and Secondary Address/ADDRESS2 to be COM2.

We found the logic behaves exactly like this:

COM1 is used on the A side of our redundant system when that side is online
COM2 is used on the B side of our redundant system when that side is online

We tried disconnecting cables to simulate failures.

We could not under any circumstance make the B side use COM1. We could not
make the A side use COM2.

We'd like an option for the logic to work as described in knowledge base article
1405:

If COM1 cannot be used on either side, COM2 can be used on either side, and this is
done automatically.
There have been several requests by customer to add analog deadbands in DNP.
Cfereader does support ANALOG deadbands for other protocols that support analog
deadbands (IEC, SES, ...)
If someone performs an action in the GUI for an application, it should be logged
SEPARATELY in that application's log. That would allow a determination as to
whether a "problem" is a spontaneous problem, or whether it is an "oops" by a
human.

Note that the incident that prompts this request involved the CFEReader, but the
suggestion applies to all SMP apps.
SUMMARY: Errors detected by e-terracontrol for digital controls and setpoints with
zero timeouts should be returned to the EMS Scada.

Original problem: The control error from a set point control does not get sent back to
the EMP. From the ISD log, there are two controls being sent out, a set point at
11:46:10 and a binary output at 11:46:19. Both ends in error as indicated in the
socket trace. The remote end is a simulated RTU. Both has the same error=5 in the
status field in the dnp responses. The binary output error was sent back to the EMP
and displayed in the dialog box. The set point error was not recognised as seen in the
ISD log, so it was considered as success. The set point error should be treated
similar to the binary output.

Later investigation showed that the set point had a zero timeout and the digital control
had a non-zero timeout.

The developers indicate that they would expect the setpoint responses to behave the
same as the digital control responses if the timeout is non-zero. For controls and
setpoints with zero timeouts, the control is not put on the pending list of the e-
terracontrol Scada server and a negative response from the RTU cannot be
propagated up to the EMP. For controls and setpoints with non-zero timeouts, if a
There needs to be a simple solution to the problem of relays of mixed types within a
single card. With CFE front ends, each RELAY record modeled the MDLPARMx
fields that defined the type of control for that relay. With SMP front ends, that
modeling was moved to the CARD, and within the SMP duplicate Card data sets were
required for each control data item type. SMPDUMP as delivered with EMP2.1.1 and
EMP2.2 automatically generates these cards when mixed relay types are detected,
but that is an imperfect solution, which may not work ideally for all protocols.
EMP2.3's SMPCFG does not create the duplicate cards - users are expected to
"correct" their modeling in SCADAMOM. This creates its own set of protocol-
dependant problems.
SMP 3.4 connecting to EMP 2.3 via ISD. Within the e-terracontrol server, a
measurement is assigned to two ISD Data Sources. The expected behavior is that
the value will be provided based on a combination of priority and data quality. After
testing, the observed behavior indicates that no "best quality" evaluation is done when
the data sources are of type ISD. It appears that the highest priority data source
value is used, regardless of quality. If the priorities are equal, the value from the first
data source listed in the measurement's Data Source dialog window is used.

This allows a suspect or replaced value to be in use, even though the other data
source has a good quality value.

The following tests were performed by the customer and then verified on systems
here at Areva as well:

Site PD, priority = 200
Site P2, priority = 100

PD has a good quality value
P2 has a replaced value

Only ISD link to PD is in service: value is from PD
Start ISD link to P2: value is now from P2 - even though it has a replaced quality on
the EMP side. Once the value is in SMP, the quality shows as Good.

Change the setup so that:

Site PD, priority = 100
Site P2, priority = 200

PD has good quality value
P2 has replaced value

P2 ISD link is up, PD ISD link is down: value is P2's replaced value (although is
We have e-terracontrol and use the alarm pager application to send out text
messages via email to our cell phones on certain critical alarms.

Because the messages do not include unique time stamp information, the text
messages are identical to each other for a given alarm - even though they are for
alarms that happen at different times. This causes difficulty because the cell phone
considers multiple text messages for a given alarm to be duplicate rather than unique
messages as there is no unique text (like a time stamp) that would differentiate
messages for alarms that occur at different times but for the same alarm point.

It would be beneficial to include time stamp information in the text of the message, so
we would know when the alarm actually happend if we are away from our cell phone
for a time or if the cell phone is out of range of a cell site. When out of range, the
message is held and they stack up and are then sent when the phone is back in
service. Without a timestamp included, this causes confusion as to when the alarm
actually occured.
This request is associated with SPR PD25323 and is detailed in the
Polling_sequence_detail.zip file attachment in the Notes section of this SPR.

There are multiple issues involved with the current DNP3 polling sequence, and the
behavior on multi-drop lines. In order to clarify what actions need to be taken, the
three different identified issues have been broken down into 3 issues as noted in the
attached file with the item (1) being the following:

1. DNP3 RTU initialization sequences require three discrete commands from
CfeControl to the protocol DLL: RTU initialization, time initialization, and the first
integrity poll for a scan group under the RTU. These are sub-optimally ordered, such
that a set of RTU initializations for all RTUs on a line are issued prior to a set of time
initialization requests, which are followed by integrity polls. Given that each RTU
initialization and time initialization can result in multiple messages to a single device,
response times can be quite high, particularly when using a cellular communications
medium.

Adjusting the current DNP3 initialization implementation would be a very worthwhile
enhancement. We have discussed possible alterations internally regarding the DNP3
RTU initialization sequence. There are two basic approaches - one would be to alter
Currently, each login must be defined in the Scada Server as a User object for each
specific login that's intended to view Area of Responsibility data. This is a request to
add support for Active Directory groups to allow sites to define a "group" object that
would allow all the members of the group to access the Area of Responsibility data.

We would like to have a RIO like program for the SCADA DB. At the very least it
should do an import and export with the ability to specify desired fields. The dynamic
data like the on-line - off-line status should be exportable too. The RIO like program
should run against the SDB also.
product_system    voting_category
ARCHIVE-ARCHIVE   e-terraarchive [Archive]
ARCHIVE-ARCHIVE   e-terraarchive [Archive]

ARCHIVE-ARCHIVE   e-terraarchive [Archive]

EMP-DTS           e-terrasimulator [EMP - DTS]

EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]

EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-DTS           e-terrasimulator [EMP - DTS]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-GENERATION    e-terrageneration [EMP - Generation]
EMP-NETWORK       e-terratransmission [EMP - Network]
EMP-NETWORK       e-terratransmission [EMP - Network]
EMP-NETWORK       e-terratransmission [EMP - Network]
EMP-NETWORK       e-terratransmission [EMP - Network]
EMP-NETWORK       e-terratransmission [EMP - Network]
EMP-NETWORK       e-terratransmission [EMP - Network]
EMP-NETWORK       e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-NETWORK                     e-terratransmission [EMP - Network]
EMP-SYSTEM                      e-terraplatform [EMP]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser   e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terrabrowser-e-terrabrowser          e-terrabrowser [WebFG]
e-terradistribution-Client             e-terradistribution
e-terradistribution-Client             e-terradistribution
e-terradistribution-Client             e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Modeling           e-terradistribution
e-terradistribution-Switching Orders   e-terradistribution
e-terradistribution-Tagging            e-terradistribution
e-terradistribution-Tagging            e-terradistribution
e-terradistribution-Tagging            e-terradistribution
e-terradistribution-Tools              e-terradistribution
e-terradistribution-Unknown            e-terradistribution
e-terradistribution-Unknown            e-terradistribution
e-terradistribution-Unknown   e-terradistribution
e-terradistribution-Unknown   e-terradistribution
e-terradistribution-Unknown   e-terradistribution
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-HABITAT        e-terrahabitat [HABITAT]
e-terrahabitat-WEBFG          e-terrabrowser [WebFG]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-e-terrascada     e-terrascada [SCADA]
e-terrascada-SYSTEM           e-terrascada [SCADA]
e-terrascada-SYSTEM           e-terrascada [SCADA]
e-terrasource-Client          e-terrasource
e-terrasource-Client          e-terrasource
e-terrasource-Client          e-terrasource
e-terrasource-Client          e-terrasource
e-terrasource-Database        e-terrasource
e-terravision-e-terravision   e-terravision
e-terravision-e-terravision   e-terravision
e-terravision-e-terravision   e-terravision
e-terravision-e-terravision   e-terravision
e-terravision-e-terravision   e-terravision
e-terravision-e-terravision   e-terravision
iGRID-iGRID                   e-terrabrowser [WebFG]
IMAGE-IMAGE                   [not-a-product]
Nhood-Nhood                   e-terrahabitat [HABITAT]
Nhood-Nhood                   e-terrahabitat [HABITAT]
Nhood-Nhood                   e-terrahabitat [HABITAT]
Nhood-Nhood                   e-terrahabitat [HABITAT]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
SMP-SCADA-SMP                 e-terracontrol [SMP]
voting_category_sir   product_subsystem_lookup
ARCHIVE ETA36891      ARCHIVE-ARCHIVE
ARCHIVE PD23086       EMP-DTS

ARCHIVE PD34021       EMP-GENERATION

EMP ETPA37369         EMP-NETWORK

EMP ETPA38217         EMP-SYSTEM
EMP ETPA38393         e-terrabrowser-e-terrabrowser
EMP ETPA38394         e-terradistribution-Client
EMP ETPA38395         e-terradistribution-Modeling
EMP ETPA38396         e-terradistribution-Switching
                      Orders
EMP PD12435           e-terradistribution-Tagging
EMP PD12436           e-terradistribution-Tools
EMP PD15718           e-terradistribution-Unknown
EMP PD16044           e-terrahabitat-HABITAT
EMP PD23491           e-terrahabitat-WEBFG
EMP PD24118           e-terrascada-e-terrascada
EMP PD25574           e-terrascada-SYSTEM
EMP PD26519           e-terrasource-Client
EMP ETPA38405         e-terrasource-Database
EMP ETPA38406         e-terravision-e-terravision
EMP ETPA38407         iGRID-iGRID
EMP ETPA38408         IMAGE-IMAGE
EMP ETPA38410         Nhood-Nhood
EMP ETPA38416         SMP-SCADA-SMP
EMP ETPA38519
EMP ETPA39110
EMP ETPA39599
EMP PD13525
EMP PD18119
EMP PD18247
EMP PD18252
EMP PD24062
EMP PD24063
EMP PD32190
EMP PD36541
EMP ETPA36812
EMP ETPA36823
EMP ETPA37226
EMP ETPA37388
EMP ETPA37441
EMP ETPA38186
EMP ETPA38215
EMP ETPA38218
EMP ETPA38232
EMP ETPA38385
EMP ETPA38386
EMP ETPA38388
EMP ETPA38389
EMP ETPA38390
EMP ETPA38391
EMP ETPA38392
EMP ETPA38397
EMP ETPA38400
EMP ETPA38467
EMP ETPA38538
EMP ETPA38687
EMP ETPA39304
EMP ETPA39554
EMP ETPA39555
EMP ETPA39581
EMP ETPA39582
EMP ETPA39583
EMP PD16544
EMP PD20397
EMP PD21255
EMP PD23525
EMP PD31678
EMP PD32209
EMP PD33153
EMP PD35935
EMP PD36453
EMP ETP36857
e-terrabrowser ETB36475
e-terrabrowser ETB36575
e-terrabrowser ETB36818
e-terrabrowser ETB36833
e-terrabrowser ETB36879
e-terrabrowser ETB36966
e-terrabrowser ETB37094
e-terrabrowser ETB37099
e-terrabrowser ETB37175
e-terrabrowser ETB37259
e-terrabrowser ETB37270
e-terrabrowser ETB37271
e-terrabrowser ETB37273
e-terrabrowser ETB37280
e-terrabrowser ETB37314
e-terrabrowser ETB37350
e-terrabrowser ETB37670
e-terrabrowser ETB37708
e-terrabrowser ETB37988
e-terrabrowser ETB38154
e-terrabrowser ETB38262
e-terrabrowser ETB38263
e-terrabrowser ETB38283
e-terrabrowser ETB38362
e-terrabrowser ETB38363
e-terrabrowser PD11585
e-terrabrowser PD13796
e-terrabrowser PD14380
e-terrabrowser PD24799
e-terrabrowser PD30026
e-terrabrowser PD30041
e-terrabrowser PD30094
e-terrabrowser PD31210
e-terrabrowser PD32153
e-terrabrowser PD32158
e-terrabrowser PD32516
e-terrabrowser PD33646
e-terrabrowser PD34056
e-terrabrowser PD35030
e-terradistribution ETD38884
e-terradistribution ETD42721
e-terradistribution ETD42776
e-terradistribution ETD38887
e-terradistribution ETD38981
e-terradistribution ETD38982
e-terradistribution ETD38983
e-terradistribution ETD38984
e-terradistribution ETD38986
e-terradistribution ETD41526
e-terradistribution ETD41526
e-terradistribution ETD42720
e-terradistribution ETD38987
e-terradistribution ETD38988
e-terradistribution ETD38989
e-terradistribution ETD38990
e-terradistribution ETD38922
e-terradistribution ETD38886
e-terradistribution ETD38897
e-terradistribution ETD38898
e-terradistribution ETD38900
e-terradistribution ETD38901
e-terrahabitat ETH34300
e-terrahabitat ETH36695
e-terrahabitat ETH36855
e-terrahabitat ETH37618
e-terrahabitat ETH37620
e-terrahabitat ETH37628
e-terrahabitat ETH37665
e-terrahabitat ETH37711
e-terrahabitat ETH37713
e-terrahabitat ETH37714
e-terrahabitat ETH37795
e-terrahabitat ETH37887
e-terrahabitat ETH38217
e-terrahabitat ETH38660
e-terrahabitat ETH38682
e-terrahabitat ETH38750
e-terrahabitat ETH38763
e-terrahabitat PD13985
e-terrahabitat PD18516
e-terrahabitat PD22016
e-terrahabitat PD24138
e-terrahabitat PD30103
e-terrahabitat PD31569
e-terrahabitat PD32433
e-terrahabitat PD32435
e-terrahabitat PD33041
e-terrahabitat ETH37712
e-terrascada ETSC36715
e-terrascada ETSC37053
e-terrascada ETSC37294
e-terrascada ETSC37746
e-terrascada ETSC37747
e-terrascada ETSC37754
e-terrascada PD16323
e-terrascada PD30040
e-terrascada PD33347
e-terrascada PD34034
e-terrascada PD34309
e-terrascada ETSC37025
e-terrascada ETSC38752
e-terrasource ETSO39108
e-terrasource ETSO39278
e-terrasource ETSO39279
e-terrasource ETSO39350
e-terrasource ETSO39087
e-terravision ETV36845
e-terravision ETV36846
e-terravision ETV36943
e-terravision ETV37101
e-terravision ETV37116
e-terravision ETV37170
iGRID PD23467
IMAGE PD33656
Nhood PD36295
Nhood PD36295
Nhood PD36295
Nhood PD36295
SMP ETC36680
SMP ETC36829
SMP ETC36863
SMP ETC37141
SMP ETC37152
SMP ETC37153
SMP ETC37290
SMP ETC37293
SMP ETC37301
SMP PD15885
SMP PD20747
SMP PD21031
SMP PD25682
SMP PD28054
SMP PD33700
SMP PD33964
SMP PD35339
voting_category_lookup
e-terraarchive [Archive]
e-terrasimulator [EMP -
DTS]                         Row Labels                             Count of voting_category
e-terrageneration [EMP -
Generation]                  [not-a-product]                                   1
e-terratransmission [EMP -
Network]                     e-terraarchive [Archive]                          3
e-terraplatform [EMP]        e-terrabrowser [WebFG]                           41
e-terrabrowser [WebFG]       e-terracontrol [SMP]                             17
e-terradistribution          e-terradistribution                              22
e-terradistribution          e-terrageneration [EMP - Generation]             17
e-terradistribution
                             e-terrahabitat [HABITAT]                          30
e-terradistribution          e-terraplatform [EMP]                              1
e-terradistribution          e-terrascada [SCADA]                              13
e-terradistribution          e-terrasimulator [EMP - DTS]                      14
e-terrahabitat [HABITAT]     e-terrasource                                      5
e-terrabrowser [WebFG]       e-terratransmission [EMP - Network]               36
e-terrascada [SCADA]         e-terravision                                      6
e-terrascada [SCADA]         Grand Total                                      206
e-terrasource
e-terrasource
e-terravision
e-terrabrowser [WebFG]
[not-a-product]
e-terrahabitat [HABITAT]
e-terracontrol [SMP]

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:25
posted:7/30/2012
language:English
pages:157