as United States
`a2) Patent Application Publication co) Pub. No.: US 2001/0009425 Al
`(43) Pub. Date: Jul. 26, 2001
`
`Thomasetal.
`
`US 20010009425A1
`
`MAN-MACHINE INTERFACE FOR A
`VIRTUAL ANNUNCIATOR PANEL DISPLAY
`
`(57)
`
`ABSTRACT
`
`(54)
`
`(76)
`
`Inventors: Robert P. Thomas, Ellington, CT (US);
`James VY. Petrizzi, Tariffville, CT (US)
`
`Correspondence Address:
`CANTOR COLBURN, LLP
`55 GRIFFIN ROAD SOUTH
`BLOOMFIELD, CT 06002
`
`(21)
`
`Appl. No.:
`
`09/803,586
`
`(22)
`
`Filed:
`
`Mar. 9, 2001
`
`Related U.S. Application Data
`
`(63)
`
`Continuation of application No. 09/156,203, filed on
`Sep. 17, 1998, now Pat. No. 6,219,046.
`
`Publication Classification
`
`(51)
`(52)
`
`Tint. C7 occ cececcceccccccscscssceseessessesssesreseeaneese GO06F 3/00
`US. C1.
`ccceccccccccecsssscssssssscteeesees 345/771; 345/772
`
`A power managementcontrol system provides control and
`graphical representation of a plurality of electrical devices
`and components of an electrical distribution system. The
`control system includes a virtual three-dimensional annun-
`ciator panel for displaying an indication of the status or
`condition of a pluralitya plurality of electrical devices of an
`electrical distribution system. The virtual annunciator panel
`includes an array (6x8)of indicator buttons that represent a
`particular device, event or group of events of the PMCS. ‘The
`buttons are displayed in different colors to indicate different
`alarm systems. The annunciator panel functionsto notify the
`user/operator of an alarm condition of a device, as well as
`permits the user to acknowledge alarms. The development of
`the virtual annunciator panel display is automated using
`software, namely an Annunciator Panel Wizard. The Panel
`Wizard provides the automated configuration of the annun-
`ciator panel graphic as well as a built-in event mapping to
`the annunciator buttons which is user configurable. The
`Panel Wizard allows the user to generate the virtual annun-
`ciator panel display without any programming skills or
`detailed device knowledge.
`
`16
`
`24
`
`(oN
`
`
`| =— | ==
`£PM3710
`EPM3720
`
`29
`
`. up to 247 devices
`per network
`~=multiple Modbus RTU networks
`20
`
`Modbus Concentrator
`
`32
`
`
`
` |
`
`
`MULTILIN 269
`MULTILIN 565
`$485 cards
`and adapters
`Direct connect
`18
`Modbus devices
`24
`
`
`
`
`
`
`
`=
`
`Google Exhibit 1011
`Google v. VirtaMove
`
`
`Bee
`
`
`
`
`
`
`_—
`MICRO VERSA
`oo
`ENHANCED. MICRO
`SPECTRA ECM
`PLEPM
`VERSA TRIP-D
`TRIP
`6—>
`be13
`
`5
`L_
`
`
`
`co}6(Lp C0 —_
`
`
`iO
`co
`gd
`POWERLEADER
`°
`MICRO VERSA
`ENHANCED MICRO
`METER
`RIP PM
`VERSA TRIP—C
`28
`——_—_,—_—___—"
`26
`
`
`
`
`
`
`
`1 z
`
`
`S| Lea
`
`
`
`
`
`MOP
`30
`
`Google Exhibit 1011
`Google v. VirtaMove
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 1 of 15
`
`US 2001/0009425 Al
`
`
`
`YSUGAOMDIN
`
`
`
`9¢
`
`
`
`O~dldlVSYIAAddida>aaIGNfJLaf
`
`97coFF>A.
`
`
`SaoIAap/pz0}dn“SyJOMJOUALYSNqpo~aidangz
`
`OMDIN=-YSYGAOMDINYadvITMAMOd
`
`YSuaA"=‘GONVHNGchtWoaVaLdadSAdd
`yIOMJOUJOdCi)
`QUL—]aTOeS|9“4Q-dlul
`
`
`
`(Co)ol__]SeolAepSNqpowSL
`=ael
`
`fO7ZEWNdgOLZENdg/(—][=3vlVe
`ce4
`jobve
`
`
`yauucdpaigsua}dppopup
`
`JojDy{Us9U0DSNqpo~EEE]
`gggNTILINN692NTILLINOS
`
`ve
`
`
`
`SP499_SBYSY
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 2 of 15
`
`US 2001/0009425 Al
`
`ve
`
`
`
`NIWA¢-SNg
`
`NIVA_1—SNg
`
`danvaea
`
`T1ENOal
`
`dayvaua
`
`STEnowl
`
`SOVIIOAM01
`
`sngod
`
`
`
`
`||JL
`AUVAWNSNavi||Ieee|
`NOLVedsdOeeee|eeeee||
`
`
`
`u3d3=4|-snaAN2899SNn_8799AV1SaAVTaudavAVISYAMVZ#MAWYOASNVELL#USAYOISNVYLAdVNIedAVIS.
`
`
`
`
`
`
`Z#YANYO-SNVeLLfMINYOISNWYLvSyNVAYddSvYayVANaGSyUaWWSYESoC
`
`
`
`
`TVENONLS1ENoulNOLVWY3d0JanoJVaNnOwL
`
`
`
`
`WAYANADWHANSSanoladenoFIGNOYL
`+9£9e7
`
`TWd9CTIMONNOV
`
`G6OIA
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 3 of 15
`
`US 2001/0009425 Al
`
`oS BIDMIODUOM
` 90DLa}U]
`
`vS
`
`jooiudnr9
`
`1asp
`
`suoljooddy
`
`3|NPOW
`
`&Old
`
`20D]19}u|
`
`pibg
`
`joo1bo7
`
`40d
`
`Seid]O}0q
`
`ZpJOaMIESFaqOv
`
`
`
`ge
`
`|Duo!\dQ
`
`AWAIONPOl
`
`sainpo~|
`
`
`
`sunydogOV0sWWJOJBADM\
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 4 of 15
`
`US 2001/0009425 Al
`
`UsLUdo[aAaq
`
`joioedS
`
`OS“SONd\Ze"HONOLNI\O
`JOMOIAMOPULM
`
`yono|u|
`
`
`
`
`
`
`
`
`
`
`
`21607 Sills
`
`
`
`BOA
`
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 5 of 15
`
`US 2001/0009425 Al
`
`
`
`STONVH4OO§|Do|DI]
`
`
`
`STGNVHAIGNVH
`
`SIONVH
`
`LANIGV98ONY
`
`seyojdaopyjjous45
`
`
`SUBBIOS
`
`IDINGD]39||sayojdeon4abn]49
`
`
`
`SOO,aul-8UQ39
`
`
`
`soyojdson4ious49
`
`
`
`UODE}aSPuDZIM
`
`
`
`YANALSV4
`HANZLSVS
`
`YANALSV3
`
`STONVH
`
`||
`
`DU0CQOOGLL
`coacoco
`QUD0Q0
`
`DEOUQUUUN
`aocIc
`caCaco
`DUQ0UC
`
`LANZA
`
`LNZA
`
`LN3A
`
`
`
`PIDZIMUO]DAS[Z39
`
`~SNOSUDI[SOSIW4D
`
`
`
`P4OZIMYOHDAA!Z39
`
`
`
`P4OZIMUR|doO|439
`
`
`
`plOZIWyyUDIdIOO]439
`
`
`
`sjoo{eluuny
`
`SOUITIMS
`
`S4BPIIS
`
`suo}ng
`
`sowDi4
`
`SHIOID
`
`sjeund
`
`
`S13}3\N
`s}y6r]
`
`
`
`sko|dsiq}xe1
`
`Spusdy
`
`
`
`UONCUdDsSaqPJOZIM
`
`
`
`
`
`aiydosgyeuiqoggayy
`
`
`
`puawluoyYOUS
`
`
`
`XOG|OO|WOL,SAOLUSY
`
`xog|jco]O}PPpy
`
`jgouD4poa|as
`
`
`
`g
`
`OLA
`
`
`
`
`
`
`
`supjdioo,4JojaiydnigyoulqnggQuy
`
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 6 of 15
`
`US 2001/0009425 Al
`
`
`
`EERSTE](0)SUS819SADINGOL39||sayojdac04
`
`
`
`
`YaMOd=ENEBEMOdseypidaa04||plus39
`XOG|OO|,WO}sAoWayXOG|Oo]0}ppy[jeoug|[yas|dtydDjig
`
`
`
`
`
`L3NIEVOaNdvuLoadsS9}O[C9004[JOWS39
`
`
`
`
`
`suonpagjasDeByopIMs40}aiydpdi9ajojdawoNseaspujyoeds
`
`
`
`000839OVA/NEMOdpaozimuojdioo|435
`
`
`
`xogBojpiguoijoejaspsozim
`9“Old
`five”o)Cire5)
`
`
`
`ayD\dawoNseespujeds
`2610449
`
`puozimUD|dIoo]439
`
`PABZIMUONDASTZ3D
`
`uonduoseqPJDZIM
`
`sjooleul]-eug49
`snoaup||sosi—39
`
`WUSWLUODYOUs
`
`
`
`sjoo,awiyuny
`
`SOYOUMS
`
`S49Pl/S
`
`
`
`skojdsiq.4x9},
`
`Spusl,
`
`suoyjng
`
`Sy901D
`
`SeuiDJ4
`
`S|BUD¢
`
`SIO}ON
`
`s}y5r]
`
`
`
`

`

`Patent Application Publication AOld
`YuaNVaNa-9YVaNeYaMOdYayTIVASHEVaNEeaMOdSajodsooy[ows35LHOINeaipidesDs
`
`
`
`
`
`
`
`
`
`
`
`MSHVANE-MYSNVaNG-y%ASNHVaYa-HYSEMVSYS-DYANVaUE-9P4IDZIMupjdioo449
`
`
`
`
`PADZIMWOLLHAAi331LHOIWOLLYSAL431pIDZiIMub|dool449|Eh]UONDAS[Z4DmEHePADZIM
`
`
`abun]49asCooS8}0|de004||DWS39IHE==susatoSUDINGD{49|||sayjdeony
`
`
`
`XOg|OO|WO,aAOWayXOG|OO|0}Ppy|lecuvo||pares|aypjdsop4|JOWS||yDsUg
`louie
`
`
`
`
`
`SUOIOAR|9JIDOHYOYUMSJOPAOZIMsyD[de0D4|JOLUS||YDOIGJaMog
`S|auddeSESOWDI4
`
`aouv1TWASsyy6!]
`SNOSUDI|9OSIW49UO!DAS|yAD[]
`
`
`
`Sx90[98]suo}ng
`
`
`
`
`
`XOgBolDIqUONDE/3aSPIDZIM
`
`
`
`SJoo]aulT-8Ug49
`
`
`
`sjoojsuuiyuNny
`
`S13}90\
`
`SOYOUMG
`
`S4AOptS
`
`
`
`Jul. 26, 2001
`
`Sheet 7 of 15
`
`US 2001/0009425 Al
`
`YAYDINOYMLODIIYHIINOYLOSTZ
`
`JaMod
`
`JUSLULUODWOUS
`
`
`
`udlydiu9seqP4DZIM
`
`
`
`sApidsiq3x9]
`
`SpuslL
`
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 8 of 15
`
`US 2001/0009425 Al
`
`roll}
`
`
`
`a
`
`YqaLW
`
`
`
`
`VSYBAOXOINVSUAAONDIN4aSnr
`OLZEWdS|—||—]
`O?SLEWdSa
`Wddidiea
`
`XOG|OO]WO1}BAOWUaY
`
`
`XOgBopiquols9}aSgP4DZIM
`
`
`
`O¥QINGSONVHNAOYOINTIONVHNA
`co(|
`
`
`
`Q-dislVSH3AO~dldt VSYSA
`
`S69¢NOLINA69%NIGLLINN
`xoq|oo,©}Ppy
`
`8OLL
`
`ySq0VS14seM0d
`
`cc
`on|
`—_o5
`off2Oo
`
`
`
`
`
`
`
`SUOIPDAS[SIDSHYSUMS10}PUPZIMa}Djds0D4||DLUSJNDWDIjEdS
`
`Wdaid
`
`
`
`
`
`sajojdson43610749
`
`
`
`SUusdIOSJIDINGD!FS
`
`
`
`S]OO]8UIT-BUD39
`
`
`
`soppideop4jJouis39
`
`SNOSUDIJSISIW39
`
`
`
`PIDZIMUCHDAS|Z3D
`
`
`
`PIDZIMUCHDASIZFO
`
`
`
`PIOZIMUD|duoO}439
`
`
`
`PIOZIMUD|ducol435
`
`
`
`sjoo,aujuny
`
`shojdsiqxa
`
`Spusl
`
`SOYSUMS
`
`SISPIIS
`
`
`
`UdI}dUOSEqP4IDZIM
`
`
`
`JUSWIUWIODYOUS
`
`9yo|deop4
`
`IDWSWJdJjIeds¢
`
`
`

`

`
`
`:éouanb-ouenbel413|095aboYOA
` *}U9lNO1ne=ta{NSNSrYOVY‘QWONdnoigaXWAOz/¢3
`
`
`1ajD9SJuang
`
`5sounjoquyshoo.
`‘BLUDNSdlAaqQ(%)4d[P30(a)zUYAM[P30
`
`
`
` Ww=So°a>‘Aaydeleg(%)‘ssippy‘naponsounjpquy)yus.ing
`
`
`“UM
`LING\TSHONOLNI\?O—JOMalAMOPUIM—YONO|U| Patent Application Publication
`
`
`sjuiodias\(Zdnjas)(|dnyes)(puwq"wuey))/Bu1]uxa|20M|196607US 2001/0009425 Al\(puuigbuipys
`
`
`
`
`
`
`
`Sen|[DABulsayeW[DUUONOZLENdS
`
`
`
`
`
`[pI9edS91Bo7ally
`
`
`
`
`
`
`
`SaNn[DAesDUqsalu]
`
`
`
`
`
`IN-1]abnyo,‘Bay
`
`
`
`1-7aboyo,‘Bay
`
`
`
`uauing‘Bay
`
`
`
`“NYE[P}OL
`
`VA10}0L
`
`Clo oc
`
`ao
`
`oO
`
`ac o]}o oO
`
`
`
`‘N~1]SHOA
`
`Uuadng
`
`“NY
`
`WAH
`
`6“OLA
`
`
`
`cow[puear]8s
`
`
`

`

`
`
`Patent Application Publication Jul. 26, 2001=Sheet 10 of 15 US 2001/0009425 Al
`
`Annunciator Panel Wizard menitors DDE Items at Event Logger
`
`60
`
`48
`
`Event Logger
`tracks events
`reported by
`PMCS DDE
`Server
`
`
`OFF
`DDE item Name Trip 1”
`Status
`
`
`
`Configured Events
`Received
`Relay Tripped?
`NO
`Error Condition?
`NO
`
`Overvoltage Condition? NO
`
`Annunciator Panel Wizard
`
`
`Event Logger
`
`DDE Server
`
`62
`
`
`
`
` PMCS
`
`FI¢. 10
`
`Annunciater Panel Wizard monitors
`DDE Items at Event Logger
`
`
`
`34a
`
`Jj4c
`
`60
`
`
`
`48
`
` 12
`
`
`
`
`
`Relay 3
`Relay 2
`Relay 1
`DDE Item Name Trip 17
`
`Status
`ON
`“) (red)|(gray)
`(gray)
`
`
`
`
`
`Annunciator Panel Wizard
`
`
` Error Condition?
`
`Overvoltage Condition? NO
`
`
`
`Event Logger
`tracks events
`reported by
`PMCS DDE
`Server
`
`62
`
`FIG.
`
`17
`
` PMCS
`
`
`
`
`
` Event Logger
`
`DDE Server
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 11 of 15 US 2001/0009425 Al
`
`
`
`eiDMispuom[_]
`
`
`
`
`ROSajpseyJO,JON—AdogjouoowWoig—YonoLU]
`
`
`
`
`SsWuUNydjeySMOpUImM|DIOedSour]4xs[ebunwiyupyally
` |MOHdV|
`WE
`
`ULE
`
`,eg<f
`LE
`PLPt
`PL|
`PE|PLL
`PF
`
`d1gHANVAANNSWavT¥|)TVSOGTIMONMOV]|L3S3Y
`
`Ww
`oO
`
`Z9
`
`GhOLA
`
`#-LOLY
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 12 of 15 US 2001/0009425 Al
`
`
`
`Panel!
`Security Access Level[0+-4
`Select each panel
`to configure the button text
`
`Annunciator Panel Name
`
`Annunciator Panel Dialog
`
`70
`
`
`
`
`
`68
`
`
`
`
`
`
`Annunciator Panel Diclog
`
`
`
`|SR/745
`1st Line
`78
`|H| CURRENT
`2nd Line
`3rd Line}TRIP
`
`Annunciator Panel Name |Panel|
`
`Security Level [oO|
`76
`
`68
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 13 of 15 US 2001/0009425 Al
`
`to configure the button text
`Select each panel
`
`[rici|Cric2ricsJLrice|rics Rt
`[-raci||racefd
`[_rsci_|[_a3c2_][_rsc3_JL_asca_|Lescs_]
`[ft
`
`
`
`
`
`68
`
`70
`
`
`Annunciator Panel Dialog
`
`Annunciator Panel Name
`
`
`
`
`Panel1
`Security Access Level 5000-72
`
`
`
`
`
`
`
`
`
`
`
`34
`
`34
`
`
`
`
`
`
`
`| 2 235 BREAKER 455 BREAKER|eee|FiTROUBLE 255 BREAKERTROUBLE TROUBLE TROUBLE aa GENERAL
`
`
`
`
`|“eee|FhMAIN|Saexce|MAIN|beer||Seeker
`
`34 [reeel||Neer pee|ee|
`
`6648 LINE BUS,aL|“eee|peo|a) pew|AZ6555 LINE 6682 LINE
`
`
`
`
`PRIMARY[wiitetay|[ieretar|oer [aeRe|RELAY
`
`
`
`
`pC BUS
`LOW VOLTACE
`
`
`
`OPERATION
`
`TROUBLE
`
`62
`
`63
`
`64
`
`FIG. 16
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`Sheet 14 of 15 US 2001/0009425 Al
`
`82
`
`Annunciator Panel Configuration
`
`
`
`
`
`
`
`FIG. 17
`
`
`
`Annunciator Panel ItemsJ,sss
`
`88
`
`
`
`86
`
`
`
`
`
`FIG. 18
`
`Annunciator Panel Items
`
`
`Item Name [
`Desc.
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jul. 26, 2001
`
`=Sheet 15 of 15 US 2001/0009425 Al
`
`104
`
`Annunciator Panel
`
`items |
`
`FIG. 20
`
`
`114
`
`Annunciater Panel Events Add
`
`ANN_P_1A
`Item Name
`Device Name
`
`116
`
`
`
`
`
`| @OFF OON
`
`
`Event [+ 418
`Action
`
`120
`
`FIG.
`
`217
`
`

`

`US 2001/0009425 Al
`
`Jul. 26, 2001
`
`MAN-MACHINE INTERFACE FOR A VIRTUAL
`ANNUNCIATOR PANEL DISPLAY
`
`BRIEF SUMMARY OF THE INVENTION
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`{0001] This application is a continuation of U.S. patent
`application Ser. No. 09/156,203, entitled MAN-MACHINE
`INTERFACE FOR A VIRTUAL ANNUNCIATOR PANEL
`
`DISPLAY,filed on Sep. 17, 1998 and now allowed, which
`is incorporated byreference in its entirety.
`
`BACKGROUND OF THE INVENTION
`
`[0002] The present invention relates generally to a power
`management control system and in particular, to software
`that implements and automates the developmentof a virtual
`3-D annunciator panel display including built-in event map-
`ping to the annunciatortiles.
`
`[0003] Power management control systems monitor and
`control a variety of intelligent electronic devices of an
`electrical distribution system. ‘These control systems, gen-
`erally, include an annunciator panel or board provided at a
`console of the operator or user. The annunciator panel
`includes an array of buttons that provide status information
`of selected devices of the distribution system. Each button is
`indicative of the status of a corresponding device of the
`distribution system. Each of the buttons iWuminates with
`different colors, wherein each color is representative of the
`status of the selected device. For example, a green button
`may represent that the corresponding device is operating
`properly, and a red light may indicate that a fault condition
`exists. The panel provides an easy method of visually
`monitoring the condition or status of the electrical system. If
`a fault occurs that requires acknowledgementby the opera-
`tor of the system before resetting the fault, the operator may
`attempt
`to reset the failure by depressing the button to
`acknowledge the fault.
`
`[0004] Some power management control systems include
`a computer connected to a common bus that allows com-
`munication between the
`intelligent monitoring/control
`devices and a server. The control system provides graphical
`representations of and linksto the devices of the distribution
`system to enable a user to monitor and operate the distri-
`bution system.
`
`[0005] For these computer control management systems,
`there is a need for an equivalent virtual annunciator panel
`display that provides the same function of the annunciator
`panel described hereinbefore. Some power management
`control systems do offer a virtual three-dimensional annun-
`ciator panel displays; however,
`the system is not easily
`configurable without having programming knowledge and
`capability as well as intimate knowledge of each of the
`devices of the distribution system.
`
`[0006] Current virtual annunciator panel displays also
`include an array of buttonsortiles that provide the status of
`selected intelligent devices of the distribution system. In
`order to functionally link buttons of the virtual annunciator
`panelto the selected devices, each virtual annunciator panel
`requires custom programming by a knowledgeable integra-
`tor.
`
`[0007] The above discussed and other drawbacks and
`deficicncics are overcomeoralleviated by a power manage-
`ment control system comprising a network, a first control
`device connected directly to said network and communi-
`cable with said network, a user configurable annunciator
`panel, said panel including an indicator for visually display-
`ing the of status or condition ofthe first control device, and
`software defining an annunciator panel wizard, wherein the
`annunciator panel wizard provides user configuration of the
`annunciator panel.
`
`[0008] The above discussed and other features and advan-
`tages of the present
`invention will be appreciated and
`understood by those skilled in the art from the following
`detailed description and drawings.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0009] Referring now to the drawings wherein like ele-
`ments are numbered alike in the several FIGURES:
`
`FIG.1 is a diagrammatic block diagram of a power
`[0010]
`management and control system in accordance with the
`present invention;
`
`(0011] FIG. 2 is a view of a virtual annunciator panel
`display windowgenerated by computer software embodying
`the present invention;
`
`(0012] FIG.3 isa block diagram of the computer software
`used in the power management and control system of the
`present invention;
`
`FIG.4 is view of an InTouch-windowviewer win-
`[0013]
`dow generated by the computer software of FIG.3;
`
`FIGS. 5-8 are views of wizard selection dialog box
`[0014]
`windows generated by the computer software of FIG. 3;
`
`[0015] FIG. 9 is a view of an InTouch-windowviewer
`window generated by the computer software of FIG. 3;
`
`[0016] FIGS. 10 and 11 are diagrammatic block diagrams
`of an annunciator panel display, Event Logger and power
`management and control system in accordance with the
`present invention;
`
`{0017] FIG. 12 is a view of an InTouch-windowviewer
`window generated by the computer software of FIG. 3
`showing a virtual annunciator panel display presented to an
`integrator for programming;
`
`[0018] FIG. 13 is a view of a dialog box window gener-
`ated by the computer software of FIG. 3 for configuring the
`buttons of the virtual annunciator panel display;
`
`[0019] FIG. 14 is a view of a dialog box window gener-
`ated by the computer software of FIG. 3 for providing a
`description of a button of the virtual annunciator panel
`display;
`
`[0020] FIG. 15 is a view of a dialog box window gener-
`ated by the computer software of FIG. 3 showing the
`configured virtual annunciator pancl Display of FIG. 12;
`
`

`

`US 2001/0009425 Al
`
`Jul. 26, 2001
`
`display 12 without any programming skills or detailed
`device knowledge. The invention closely couples the exist-
`ing event processing in the PMCS 10 with annunciator
`displays 12 in the user interface, as will be described in
`greater detail hereinafter.
`
`[0026] Referring now to FIG.3, a block diagram 36 of the
`software for monitoring and controlling selected aspects of
`power usage/consumption of the PMCS 10, discussed
`above, is generally shown. This software is loaded into the
`computer 16 and includes a dynamic data exchange (DDE)
`server 40. DDE server 40 allows external programs to access
`power managementdata in a Microsoft Windows environ-
`ment. Data interface to DDE server 40 is provided by the
`system through a Wonderware InTouch utility. A configu-
`ration and control interface for the DDEserveris provided
`through server application window menus. Associated with
`DDEserver 40 are logical data tables 42 and related mod-
`ules, 1.e., an Excel or other DDE aware applications module
`44, a waveform capture module 46, an event logger module
`48, productivity modules 50, and a Wonderware InTouch
`module 52. Module 52 includes a tool kit for building
`screens and interfaces, and a graphical user interface 54 for
`monitoring and control of the clectrical distribution system.
`The graphical user interface 54 for the server operates in 32
`bit Windows or Windows NT environment and InTouch
`library functions. Waveform capture module 46 provides for
`viewing and analysis of waveforms(e.g., Fourier, frequency
`and/or harmonic analysis) captured by sophisticated meter-
`ing devices. Event Logger module 48 provides for viewing,
`organizing and analyzing unusual behavior in a power
`system. Productivity modules 50 include, for example, a
`cost allocation module and a load management module. The
`cost allocation module provides for tracking power con-
`sumption to the sub-unit level, developing internal billing
`methods and reports, thereby reducing cost. The load man-
`agement module provides for tracking power demand and
`automatically shedding non-critical loads to prevent peak
`demand penalties, and provides for timer-based control to
`reduce power consumption. DDE server 40 communicates
`though the interface card 18 shown in FIGS. 1 and3.
`
`[0021] FIG. 16 is a view of an InTouch-windowviewer
`window generated by the computer software of FIG. 3
`showing the configured virtual annunciator panel display of
`FIG. 12; and
`
`FIGS. 17-21 are views of an InTouch dialog boxes
`[0022]
`for configuring the Event Logger to enable interface with the
`annunciator panel display of FIG.2.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`
`[0023] Referring now to FIG. 1, a power management
`control system (“PMCS”), generally designated 10, provides
`a three-dimensional (“3-D”) virtual annunciator panel 12
`(see FIG. 2) for displaying a visual indication of the status
`or condition of a plurality of electrical devices and compo-
`nents 13 of an clectrical distribution system 14. The PMCS
`10 comprises a computer 16, e.g., an IBM-PC AT compatible
`machine which is based on a Pentium processor, having
`standard RS485interface cards 18, or an RS232 to RS485
`convertor, and adapters installed in its I/O slots. The com-
`puter 16 contains software for monitoring and controlling
`selected aspects of power usage/consumption, as described
`in more detail hereinafter. Cards 18 provide I/O ports that
`define multiple industry standard Modbus RTU networks 20
`and 22. The Modbus RTU protocolis a well-known industry
`standard. Devices with a Modbus RTU interface can be
`
`the display of the virtual
`[0024] Referring to FIG. 2,
`three-dimensional annunciator panel 12 includes an array
`(6x8) of indicator buttons or tiles 34 that represent a
`particular device, event or group of events of the PMCS 10.
`‘The buttons 34 are displayed in ditterent colors to indicate
`different alarm systems. The annunciator panel 12 functions
`to notify the uscr/operator of an alarm condition of a device
`13, as well as permits the user to acknowledge alarms, as
`will be described in greater detail hereinafter.
`
`connected directly to the Modbus,e.g., control devices 24,
`such as, Multilin models 269 and 565 and power manage-
`ment EPM 3710 and EPM 3720. Other devices communi-
`cate on the Commnnet protocol and include trip units 26,
`e.g., Trip, Enhanced Trip-D, Trip PM and Enhanced Trip-C
`Units, which are commercially available from General Elec-
`tric Co., meters 28, e.g., Power Leader Meters commercially
`available from General Electric Co., and relays 30, e.g.,
`General Llectric Co.’s Spectra LCM and Power Leader
`MDP. A Modbus concentrator 32 provides an interface
`between the Modbus RTU protocol and the Commnet pro-
`tocol, whereby these devices can communicate through
`Modbus concentrator 32 over the Modbus.In this example,
`up to thirty-two devices (ie., direct connect devices or
`Modbusconcentrators) can be connected to each Modbus
`[0027] The event logger module 48 includesautility that
`RTU network.
`passes a received message as an un-acknowledgeable or
`acknowledgeable alarm or as an event based upon the
`contents of an initialization file. The DDE server 40 ensures
`that all events are cast in the same format so that the event
`
`logger module 48 can interpret each event. Electrical meters
`28 and control/protection devices 26 use various codes to
`describe occurrences to the circuits that are monitored or
`controlled. A file collates these codes into three categories
`for analysis. These three categories for any particular device
`are modifiable for the code received from a device. Thethree
`categories are ‘ACK/UNACK’for acknowledgeable alarms,
`‘-”
`for
`alarms
`requiring
`no
`acknowledgment,
`and
`“EVENTS”for merely reporting the device status.
`
`[0025] The development of a virtual 3-D annunciator
`panel display 12 is automated using software, namely an
`Annunciator Panel Wizard. The Panel Wizard provides the
`[0028] The waveform capture module 46 includesautility
`automated configuration of the annunciator panel graphic as
`well as a built-in cvent mapping to the annunciator buttons
`that provides an interface to configure and display data from
`a device that transmits waveform data. These devices trans-
`34 whichis user configurable. The Panel Wizard provides a
`mit waveform data with different formats. One uniform
`rapid and cost effective method by which to develop a virtual
`annunciator pancl display 12. Previous implementations of
`annunciator panel displays required custom programming
`by the integrator developing the system. The Panel Wizard
`allows the user to generate the virtual annunciator pancl
`
`display format is desired for these different types of meters.
`This utility applies header information transmitted by the
`meter to correctly scale and display the comma separated
`valuc data transmitted by the devices as applicable.
`
`

`

`US 2001/0009425 Al
`
`Jul. 26, 2001
`
`[0029] The Wonderware InTouch module 52 includes a
`software toolkit for rapid developmentof three-dimensional
`representations of electrical distribution switchgear 56, as
`shownin FIG.4. These switchgear elevations have logical
`connections to the switchgear devices 13. Referring to FIG.
`4, a typical switchgear elevation developed with the so-
`called Power Wizardsillustrated in FIGS. 5-8 is shown. This
`
`elevation can be modified to any dimensions with an infinite
`number of combinations and arrangements of meters and
`protection devices to quickly and accurately represent a
`customer’s switchgear. The Power Wizards eliminate the
`necessity to draw each individual component line by line.
`The user starts by selecting a cabinet wizard such as the
`AKD-8 or Power Break Cabinet to which handles, panels,
`and fasteners are added, FIGS. 5 and 6. Thereafter, circuit
`breakers 26 (FIG. 7), meters 28 and otherprotection devices
`(FIG.8) are located or dropped onto the appropriate panels
`in the same locations as the customer’s actual switchgear.
`These items have dialog boxes associated with themthat are
`opened by double clicking on one of the Power Wizards
`once they have been dropped. From this dialog box a
`navigational
`link is established to another window that
`contains another Power Wizard that displays detailed meter-
`ing, configuration, and control information.
`
`[0030] The Wonderware InTouch module 52 includes pre-
`defined tabular representations of metering and setup/set
`point information that is generated automatically, with the
`appropriate database server
`links established. A rapid
`method is provided to accurately generate a user interface
`for power distribution metering, protection, and control
`devices 13 with the capability to repeat this interface repeat-
`edly for many devices of the same type while maintaining
`the capability to uniquely identify a device. The Power
`Wizards allows the user to generate a power distribution
`device interface without programming skills or detailed
`knowledge of the device.
`
`[0031] Referring to FIG. 9, an example of a Power Wizard
`of a metering device 28. The Power Wizards instantly
`develop a standard looking interface for a particular device
`type. These Power Wizards also create from this standard
`interface, unique database links that the user defines by
`selecting a name and entering in this name from a Power
`Wizard dialog box. In this way the same wizard may be used
`over and over again but can be logically distinguished from
`another via the user-defined namefor a device entered in the
`Power Wizard dialog box. All marginfor error that may have
`occurred in manually entering in the data access links to a
`database server are removed by the Power Wizards capa-
`bility to set
`them up automatically using a unique user
`defined device name.
`
`[0032] Every windowsapplication is registered in a win-
`dows kernel with an application name. To uniquely identify
`a data item for communication between two cooperating
`(DDE aware) windowsapplications, the data item is iden-
`tified by tuple (Application, Topic, Item). Topic name pro-
`vides a grouping, and item name specifies the actual data
`point to be accessed under a topic. For the DDE server 40,
`the application nameis the server’s executable name. Topic
`name can be the device identification name and item name
`
`can be the register identification of a ficld data point. For
`example, with a General Electric Co. EPM meter, the tuple
`can be GE32MODB, EPM1, AMP_A where GE32MODRis
`the Application name for a DDE Server, EPM1 is the meter
`
`identification name, and AMP_Aisthe current for phase A.
`DDE messages mainly include requests to send data as
`identified by the Topic and Item name. They mayalso be for
`set point download to the data point as identified by the
`Topic and Item names. Input parameter values are reported
`by field devices on the communication interface in response
`to a poll by the server. This value may be a float value, an
`integer value, a string or discrete status bits.
`
`[0033] Set points registers are to be downloaded based on
`request from a DDEclient,i.e., a program, for example, such
`as Wonderware In'louch 5.0 or MS-Excel, which request
`data items from the DDEserver 40 and accepts data through
`DDE. The DDEserver acts as a link between a client
`
`requesting device data and a field device that can provide the
`data. The DDE server communicates to the field device
`
`through communication ports and to the clicnt via DDE
`message link. A client sends its requests to the server to
`read/write some device registers. The server maps each
`request to suitable device read/write request packets and
`carries out the necessary transaction with the device. Thenit
`relays the result back to the client after processing and, if
`necessary, casts the collected device data to the proper
`format. Apart from reporting contents of normal device
`registers, the server can also collect special data like wave-
`form capture/recording data from the device and passit to a
`client.
`
`‘The DDE server 40 maintains current status
`[0034]
`(DEAD/ACTIVE)ofall active topics (devices). This infor-
`mation does not have any direct register associated with the
`device topic name and hence a pseudoitem called ‘STATUS’
`is maintained by the DDEserver.If the DDEserver 40 does
`not get a response from any device during ‘n’ consecutive
`poll cycles then that particular device is declared DEAD.
`The value of‘n’ is read from an initialization file. The status
`
`of any device will be updatedto a clientonly if a pre-defined
`item called ‘STATUS’ is made active. DEAD devices would
`be polled with period equal to a dead device scan interval
`(available in initialization file) instead of the device scan
`interval. DEAD devices will become ACTIVE when they
`respond to a polling request.
`
`[0035] A device type register map must be configured for
`each of the device topics connected thereto. The system
`provides for configuration of a starting valid address, a last
`valid address, and a set of invalid register blocks using this
`utility. Valid registers, in the present example, are ROXXXX;
`RIXXXX; R3XXXX; or R4XXXX. Accordingly, DDE
`server 40 supports the following Modbusregister types;
`ROXXXX—Discrete coils, R1XXXX—NDiscrete status reg-
`isters, R3XXXX Input registers, and R4XXXX—Set point
`registers. With these generic types, a user can configure any
`numberof register types. Each of these types will have poll
`rate attributes (i.e., Fast Poll, Slow Poll, or Poll Once).
`Buffered events, read/write date/time registers for time syn-
`chronization, waveform capture data and waveform record-
`ing data are implemented differently in the devices which
`support them hence, no common configuration utility is
`provided for these functions. The DDE server handles each
`of these functions specifically. Again a mnemonic nameis
`associated with a register address.
`
`In general, the DDE server 40 uses the Modbus
`[0036]
`RTU protocol to communicate with a field device 13. The
`DDEserver provides appropriate return valucs as specified
`
`

`

`US 2001/0009425 Al
`
`Jul. 26, 2001
`
`for all clients, ie., periodic polling packets for active topics
`and items, periodic polling packets for events and status,
`periodic update of timeto all the devices, data value update
`to clients for acquired items, event/status report to InTouch
`so that it becomes part of normal alarm log, and status
`update for active topics (devices). Set point write requests
`are properly formatted set point download communication
`packets for the request. Execution and termination of the
`server are initiated on user request from the DDE server
`window menu.
`
`[0037] As described hereinbefore, the Annunciator Panel
`Wizard assists the integrator in the development of the
`virtual annunciator panel display 12 of the present invention,
`shownin FIG.2. Specifically, the Annunciator Panel Wizard
`interconnects specific device events/alarms received by the
`Event Logger Module 48 through the DDE server 40 to
`specific butions 14 of the annunciator panel 12, and thereby
`provides the ability to notify the user of Alarm On/Off states
`of the devices throughout the PMCS 10. The annunciator
`panel 12 also allows the user to acknowledge alarms which
`are either currently on, or have previously been on and have
`gone to an off state.
`
`[0038] The Annunciator Panel Wizard provides a screen
`full of indicator buttons 34, each relating to a particular
`device 13, event, or group of events. The Annunciator Panel
`Wizard monitors selected DDE itemsin the Event Logger 48
`and respondsto changesofstate in these items by changing
`the colors of individual indicator buttons 34. For example,
`the integrator might configure a relay trip event
`to be
`associated with a button in the Annunciator Panel Wizard.
`
`The Annunciator Panel Wizard monitors a DDEtag 60 at the
`Event Logger 48 corresponding to the trip status of the
`corresponding relay 13 and displays a gray indicator if the
`relay is operating properly, and a red indicator if the relay
`has tripped.
`
`{0039] The annunciator panel 12 includes an array of
`forty-eight (48) buttons 34 (six columns by eight rows).
`Each button 34 has an animation link, as well as 3 lines of
`text (definable at design time) that describe the function of
`each button. For example, referring to FIG. 2, the descrip-
`tion of the second button downin thefirst columnof buttons
`is “BUS-1 MAIN BREAKER TROUBLE”.
`
`[0040] As shownin FIG. 12, four (4) additional buttons
`62-65 are disposed below the array of buttons 34 labeled
`“RESET”, “ACKNOWLEDGE ALL”, “ALARM SUM-
`MARY”and “HELP”, respectively. The RESET button 62
`allows a privileged user the ability to reset all Alarm
`Indicators that are currently in an Alarm Acknowledged
`state. The ACKNOWLEDGEALLbutton 63 cycles through
`all of the panel buttons 34 and acknowledges all Alarm
`Indicators which are in an unacknowledged state. The
`ALARM SUMMARYbutton 64 brings the local $30 Event
`Logger program 48 to the foreground. The HELP button