(19) United States
`(2) Patent Application Publication (10) Pub. No.: US 2003/0088534 A1
`(43) Pub. Date:
`May 8, 2003
`Kalantar et al.
`
`US 20030088534A1
`
`(54) METHOD AND APPARATUS FOR WORK
`MANAGEMENT FOR FACILITY
`MAINTENANCE
`(75) Inventors: Sayed Javad Kalantar, Racine, WI
`(US); Carey W. Zimmerman, Racine,
`WI (US); Cameron Adams, Waukegan,
`WI (US); Thomas E. Blenkhorn,
`Frankenmuth, MI (US)
`
`Correspondence Address:
`PATENT DOCKET DEPARTMENT
`GARDNER CARTON & DOUGLAS LLC
`191 N. WACKER DRIVE, SUITE 3700
`CHICAGO, IL 60606 (US)
`
`(73) Assignee: Vernon W. Francissen Gardner, Carton
`& Douglas, Suite 3400, Chicago, IL
`60610-4795 (US)
`
`(21) Appl. No.:
`(22) Filed:
`
`09/992,406
`Nov. 5, 2001
`
`FIRST
`FACILITY
`
`110
`
`SECOND
`FACILITY
`
`
`
`
`
`
`
`WIDE AREA
`NETWORK
`102
`
`120
`
`
`
`
`
`
`
`Publication Classification
`
`(51) Int. Cl." .............................. G06E 1/00; G06E 3/00;
`G06G 7/00; G06F 15/18; G06N 5/02;
`G06F 17/00
`(52) U.S. Cl. … 706/50
`
`(57)
`
`ABSTRACT
`
`A system and method are shown for work management for
`facility maintenance. The system includes a central man
`agement server configured to receive a first set of informa
`tion including tasks to be performed at a first facility and to
`generate a first work schedule for a first user selected to
`perform the first work schedule at the first facility. The
`system further includes a first client device at the first
`facility, where the first client device is configured to receive
`the first work schedule from the central management server
`and display the first work schedule to the first user via an
`electronic management interface. The electronic interface is
`further configured to receive task completion data from the
`first user and send the data to the central management server.
`When the central management server receives the task
`completion data, the central management server is config
`ured to update a status of the work schedule based upon the
`task completion data received from the first user.
`
`CENTRAL
`MANAGEMENT
`SERVER
`130
`
`DATABASE
`140
`
`
`
`FOR EACH Facility
`
`WORK QUALITY
`(-GRAPHS
`-TRENDS
`-RANKING)
`
`CiM Ex. 1044 Page 1
`
`

`
`Patent Application Publication
`
`US 2003/0088534 A1
`
`
`
`STILLVILS XMèJOWA
`
`SETTICIELHOS
`
`XMAJOWA
`
`SHdV89-) Å LITVTO
`
`SCINERAL
`
`(?NIXINWM
`
`
`
`
`
`
`
`CiM Ex. 1044 Page 2
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 2 of 33
`
`US 2003/0088534 A1
`
`
`
`
`
`V/ENW EICTINA
`
`XMRIONALEN
`
`Z?D
`
`ZI, I,
`
`>|EST)
`
`E!OVERHELNI
`
`ZGI
`
`
`
`
`
`ILNEHINEIÐ\/NWIN OINON LOETE
`
`
`
`
`
`(INE) LINn HOVHHELNI
`
`CiM Ex. 1044 Page 3
`
`

`
`Patent Application Publication
`
`e
`
`0W
`
`M4
`
`
`W\Vmm:<._n__>_m:Euu\Vomoomm>._._|=U<n_Mo_.~
`h<290»v_z_._m2Hcm__”,__A.u___+m__»_._,_“_m_n.._mn__.Fw_._«m_,_...==M__..m__a$
`0..._mzom5.0.5.
`33..zoFo:Emz_-Hzoo.xmi..M.n_xmfi
`
`m.mm:.6=EmmF<._n_s_m:.-cm...manan...mba009Qm:<._n_sm:9>.:.__o<n_
`
`
`
`a|J.'uIIn_mommxmfi
`
`
`
`
`
`mw<m_<h<nmm>mmm._<Ezmo
`
`
`
`
`
`mowomoommmmsopmnoomoommmum:
`\VQmmsopmnoQmum:
`n__>:.__o<"_....__xmfi.
`
`:2:Qzo_wmm.55m._:om_._owxmoa
`
`:2:mmm_oo<Sm\Vpznoomommm
`9mum:-mo<mmm_s_
`._m>m._..5352.
`
`
`
`mo<:oz<._
`
`
`
`
`
`0%mmm30.".
`m8~
`
`m.a.mum:Wmnbfim.
`
`._<s_.
`
`Sm\Vm.o<:wz<._
`
`CiM Ex. 1044 Page 4
`
`CiM Ex. 1044 Page 4
`
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 4 of 33
`
`US 2003/0088534 A1
`
`200
`
`TASK RECORD
`TASK ID = 12
`- TASK ICON
`- INSTRUCTION
`ENGLISH
`SPANISH
`POLISH
`- MAP
`- STATUS = SCHEDULED
`USER ID = SYSTEM
`TASK ID = 17
`- TASK ICON
`- INSTRUCTION
`ENGLISH
`SPANISH
`POLISH
`- MAP
`- STATUS = SCHEDULED
`USER ID = SYSTEM
`TASK ID = 29
`- TASK ICON
`- INSTRUCTION
`ENGLISH
`SPANISH
`POLISH
`- MAP
`- STATUS = SCHEDULED
`USER ID = SYSTEM
`TASK ID = 32
`
`TASK ID = 82
`
`TASK ID = 97
`
`204
`
`FACILITY RECORD
`FACILITY ID = 13.1
`DATE
`(20011007)
`WORKSCHEDULE
`TASKID = 32; USER ID = 34
`TASK ID = 29; USER ID = 34
`TASKID = 12; USER ID = 34
`TASK ID = 17; USER ID = 28
`TASKID = 97; USER ID = 28
`TASK ID = 82; USER ID = 28
`
`202
`USER RECORD
`USER ID = 28 ~T
`WORKSCHEDULE
`TASK ID = 17
`TASK ID = 82
`TASK ID = 92
`ERRORCOUNT = 0
`MESSAGE(file)
`INSTRUCT = N
`LANGUAGE
`USER ID = 34
`WORKSCHEDULE
`TASK ID = 12
`TASK ID = 29
`TASK ID = 32
`ERRORCOUNT = 3
`MESSAGE(file)
`INSTRUCT = Y
`LANGUAGE
`
`FIGURE 4
`
`CiM Ex. 1044 Page 5
`
`

`
`Patent Application Publication May 8, 2003 Sheet 5 of 33
`
`US 2003/0088534 A1
`
`208
`
`CUSTOMER RECORD
`CUSTOMER ID = 355
`REGION ID = 110
`FACILITY ID = 13.1
`FACILITY ID = 133
`FACILITY iD = 134
`REGION ID = 111
`FACILITY ID = 135
`FACILITY ID = 136
`FACILITY ID = 137
`REGION ID = 1 12
`FACILITY ID = 138
`FACILITY ID = 139
`FACILITY ID = 140
`ACCESS
`USER ID = 56
`LEVEL = 110
`USER ID = 88
`LEVEL = 355
`USER D = 34
`LEVEL = 34
`USER ID = 28
`LEVEL = 28
`USER ID = 30
`LEVEL = 13.1
`
`CUSTOMER ID = 441
`REGION ID = 460
`FACILITY ID = 461
`FACILITY ID = 462
`FACILITY ID = 463
`REGION ID = 470
`FACILITY HD = 472
`FACILITY ID = 474
`FACILITY ID = 476
`ACCESS
`USER ID = 267
`LEVEL = 470
`USER ID = 332
`LEVEL = 441
`
`FIGURE 5
`
`CiM Ex. 1044 Page 6
`
`

`
`Patent Application Publication
`
`US 2003/0088534 A1
`
`
`
`CiM Ex. 1044 Page 7
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 7 of 33
`
`US 2003/0088534 A1
`
`
`
`??L = CTI ÅLITIOVH
`
`
`
`--/1. ER-105)|=|
`
`ERHOLS
`
`
`
`
`
`
`
`
`
`
`
`CiM Ex. 1044 Page 8
`
`

`
`mmaP
`
`.h..
`
`M
`
`te
`
`000N
`
`1A43500
`
`uanu9mmm:P.2u9>._._u=0<u___fl—._>_ann9mum:
`anE\WEmAawwmmD0.”.
`-m.2uE>:.__o<u_mu-n__mum:
`
`
`
`.m.m~un__m_m_mau~_>_s_s_oowz:<mm_n_o
`
`um.ISmo<Muw_m..«._.m_»z_Mam
`
`n.3zoo.xw<.cM3
`y8mmomaEosmmufine.M:3zoo.xofi8u9mmm:mmm:ms.
`
`
`
`
`
`.mm._:om_._ommo<"Em:.z_Melas_m:m>mmo.m_um__~%_.»z_v_m_o.s
`
` mmmoommnWs_s_oumm_>m_mmmu9mum:MN.SNEu«mm
`.~mzoo.xmfius..~.....m
`
`
`
`
`
`|2mm<m<»<n_EvWm_m<m<»<o
`m34...
`
`SN3.__<"_uwaneManna.mum:Em:
`
`8mmu
`
`CiM Ex. 1044 Page 9
`
`CiM Ex. 1044 Page 9
`
`
`

`
`Patent Application Publication May 8, 2003 Sheet 9 of 33
`
`US 2003/0088534 A1
`
`Sun__xms.
`
`2:m_m<m<55EN
`m.=..om_._om«E03m._:om.:uw.NRSn_z_
`
`
`
`2.un.t._.__o<”_5.02,5u9>:.__o<"_3u9mmmam.mm_m:3u9mum:
`
`
`
`
`m_>m__m.m_mHmmnammm_.5n_m:omxmoz,-2,.Ex:
`
`amaze:i/E
`
`
`
`
`xmé._aQ>:.__o<”_.2uo.mmmaan.Sn_z_ou#2300mommmm_>m_E.mmN...1E.<nn_:m:.:&.mxmfiums.wmmm:
`
`
`
`
`mF<nn_:annn__mmmammzomwmmm.Som_._om5.03n:2zumo<wmm_s_umo<:oz<._mnmoomm.3.S.2mv_w<._.mo”.mzoo_m:<an_:xmfi><._n_w_n_zuP0352.
`
`
`
`zoo.xwfiBmnommBE".8no.xmé.emu
`
`
`
`mzou_v_w<._.EN_wzoFo:E.wz_do.3.5$_m<».«%_n_mzoo_xm<:mmE.o
`
`2un__xmfim.5nm_._omxmoaIah><._n_m_a
`mzoo_v_m<»SNm._um_.m.mu_w1,_>om
`
`
`_._w_._wzm8“an8Nmum:0...
`
`
`
`
`
`
`
`
`
`MI_Dn_M_.._0.w!MO>>..INM.._.<Dn_D
`annmm_>o._n_sm_xmfi2P<ww%.om_.v%MwmEu22man
`
`
`m:<n_n5up8»mum:Eu9>:.__o<u_«SSn.3mxmfimo”.mzoo_xmfinzoomm
`>mom_>mmn5m
`onun__mum:m:.<n_n53:3m»<on5xmfiEu9>._._n__O<n_anIQmmmaummzbfim
`
`
`Sn_z_nn.9xmfim_>m_mEm5n9>:.__o<”_.8u9mama8Nmmum:<mo;ums._
`
`
`mm_>o.Es_mmun__xmfimaanmzowy3$2x<:m._:n_m:owxmoz.uE.><._n_m_n_
`zoo.xmi..op.9.:mo".mzoo_
`zoo.xmfi5.03<>mom_>mmn_:mgmEn
`
`
`
`m_mxn.___<»»movw%%.mmpmmsammm_.__..om_._omx8”ozoomm
`momoommwkmm:
`
`
`
`
`canZmnommm:.<n_n_:V55ums.xmfi
`
`EN
`
`
`
`.89Emaazoomm
`
`._.Dn_Z_
`
`CiM EX. 1044 Page 10
`
`CiM Ex. 1044 Page 10
`
`
`
`

`
`Patent Application Publication May 8, 2003 Sheet 10 of 33 US 2003/0088534 A1
`
`: `
`
`:* ,
`
`
`
`:
`
`CiM Ex. 1044 Page 11
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 11 of 33
`
`US 2003/0088534 A1
`
`
`
`~^?, ?, ERITISOIH
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`555
`
`NOOI NOI LOETES
`
`{755
`
`NOOI NOI LOETES
`
`1 ( 1 )
`Z55
`
`NOOI NOI LOETES
`
`CiM Ex. 1044 Page 12
`
`

`
`Patent Application Publication May 8, 2003 Sheet 12 of 33 US 2003/0088534 A1
`
`
`
`3
`sh
`
`CN
`
`Lll
`
`m)
`92
`Ll
`
`|
`º
`C
`Nº.
`C
`| | ||
`T
`C
`
`| Role|al
`solº
`* -|-|S
`
`CiM Ex. 1044 Page 13
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 13 of 33
`
`US 2003/0088534 A1
`
`
`
`
`
`£), ERIT,5)||-||
`
`
`
`%,………… ~~~~(~~~~,~~~
`
`CiM Ex. 1044 Page 14
`
`

`
`Patent Application Publication May 8, 2003 Sheet 14 of 33 US 2003/0088534 A1
`
`
`
`É
`
`i
`
`CiM Ex. 1044 Page 15
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 15 of 33
`
`US 2003/0088534 A1
`
`001
`
`
`
`GEGEE
`
`§ 2.xxxxx xxº~~~~~~~
`
`CiM Ex. 1044 Page 16
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 16 of 33
`
`US 2003/0088534 A1
`
`
`
`CiM Ex. 1044 Page 17
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 17 of 33
`
`US 2003/0088534 A1
`
`
`
`CiM Ex. 1044 Page 18
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 18 of 33
`
`US 2003/0088534 A1
`
`
`
`
`
`~^8], ERIT,5)||-||
`
`* * * - - - - - - - - - - - - - - - - ºn tº º ºn tº º º ºs º- - - - -
`
`CiM Ex. 1044 Page 19
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 19 of 33
`
`US 2003/0088534 A1
`
`
`
`CiM Ex. 1044 Page 20
`
`

`
`Patent Application Publication May 8, 2003 Sheet 20 of 33
`
`US 2003/0088534 A1
`
`s_m.5>m
`
`s_mhu.>m
`
`
`
` _om_._um .§_..__2a=n_;__.£_a..£§_
`
`
`
`um...
`
`wmatmo2.m3.E
`
`._om_>._ao_:m
`
`mo:mm..o._.
`
`._ow_>._mn_=m
`
`._om_>._mn:w
`
`oo:mm_.._o._.
`
`oo:mm_.._o._.
`
`s_m_._.w>m
`
`s_mpm>m
`
`s_mFm>w
`
`s_m.5>m
`
`sm:m>w
`
`s_m:m>m
`
`_oo>o._oEw
`
`®
`
`ammo?UE2m>m>2
`9.5922%m=os_
`$592S%mcos.
`
`mcunnumo2nowcos.
`
`ooauumc2Damcos.
`
`mtwnmo2newcos.
`
`Ssmao2%mcos.
`
`CiM EX. 1044 Page 21
`
`onm_m=0_n_
`
`3.23m
`
`:oEmo
`
`CiM Ex. 1044 Page 21
`
`

`
`Patent Application Publication
`
`MM%
`
`
`
`53.0-3§._EmN2|..........I..|.|Iu|I
`,IE__£O_$mmmn_O2.832®ow_£§._ m_._on_“ozmacawuwnrmo
`
`
`
`
`
`
`3:._.._m_§_o-W §_om__mn_O_8mmmn_O0:0032®wo:m.=:m_.m_EEoU.__u¢__m...._O_u¢mmwn_0Son32®muaonommm8__>>.M_|!.,..§_3.5oaims.o28.23uoz®m_o._monommmoo__>>.w_|i3m _um__mu_O_uwwman_0Son82®.50.".no.25.5-...._=m_u._m_._._Oo_n_Emnm __oo__mn_O_uwwmmn_Ow:on_
`
`
`
`m>oEwm_-WGmacawEarwoo>oEom_->:__umu__Eo._._.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`°aK\wFmmmawz
`
`a_..e___§H5.23m
`
`coucmo
`
`.02®.32".no.2umso-WmEoEEoUuo__mu_OcommmmD«Eon.“oz®.80.".nos.#25.W._ _ow__mn_Ocomma;O2.832®.62".mos.B>>.WmEwEEoU__um__au_O_uomwmn_Om:on_
`
`
`
`
`
`CiM EX. 1044 Page 22
`
`CiM Ex. 1044 Page 22
`
`

`
`Patent Application Publication May 8, 2003 Sheet 22 of 33 US 2003/0088534 A1
`
`FIGURE 22
`
`START
`
`A 300
`
`1302
`
`RECEIVE A FIRST SET OF INFORMATION
`INCLUDING TASKS TO BE PERFORMED
`AND SCHEDULE AT A FIRST FACILITY
`
`GENERATE A FIRST WORKSCHEDULE
`FOR A FIRST EMPLOYEE SELECTED TO
`PERFORM THE FIRST WORKSCHEDULE
`
`RECEIVE A WORKSCHEDULE REQUEST
`FOR THE FIRST EMPLOYEE FROM A
`CLIENT DEVICE AT THE FIRST FACILITY
`
`1304
`
`1306
`
`1308
`
`AUTHENTICATE THE EMPLOYEE
`
`1310
`
`
`
`
`
`
`
`
`
`AUTHENTICATION
`SUCCESSFULP
`
`YES
`
`1312
`
`SEND THE FIRST WORKSCHEDULE TO THE
`CLIENT DEVICE AT THE FIRST FACILITY
`
`NO
`
`
`
`
`
`
`
`
`
`
`
`CiM Ex. 1044 Page 23
`
`

`
`Patent Application Publication
`
`May 8, 2003 Sheet 23 of 33 US 2003/0088534 A1
`
`FIGURE 23
`
`START
`
`A. 400
`
`1402
`
`ESTABLISH A COMMUNICATION LINK
`FROM A CLIENT DEVICE AT A FIRST FACILITY
`TO A CENTRAL MANAGEMENT SERVER
`
`RECEIVE AN AUTHENTICATION DATA
`FROM A FIRST EMPLOYEE VIA A USER
`INTERFACE ON THE CLIENT DEVICE
`
`1404
`
`1406
`
`SEND A WORKSCHEDULE REQUEST
`INCLUDING EMPLOYEE AUTHENTICATION
`DATA AND CLIENT DEVICE IDENTIFIER TO THE
`CENTRAL MANAGEMENT SERVER
`
`1408
`
`1410
`
`RECEIVE A FIRST WORKSCHEDULE
`FOR THE FIRST EMPLOYEE
`
`DISPLAY THE FIRST WORKSCHEDULE
`ON THE CLIENT DEVICE
`
`
`
`
`
`CiM Ex. 1044 Page 24
`
`

`
`Patent Application Publication May 8, 2003 Sheet 24 of 33 US 2003/0088534 A1
`
`FIGURE 24
`
`START
`
`A 500
`
`RECEIVE A FIRST TASK STATUS
`UPDATE MESSAGE CORRESPONDING
`TO A FIRST WORKSCHEDULE FROM A
`EMPLOYEE AT A CLIENT DEVICE
`
`UPDATE A STATUS OF EACH TASK SPECIFIED
`IN THE FIRST TASK UPDATE MESSAGE
`
`
`
`1506
`
`RECEIVE
`A WORK STATUS REPORT
`REQUEST FROM A SECOND
`MPLOYEE?
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`1502
`
`1504
`
`NO
`
`YES
`
`1508
`
`GENERATE A WORKSTATUS REPORT
`FOR THE SECOND EMPLOYEE
`
`SEND THE WORKSTATUS REPORT
`TO THE CLIENT DEVICE
`
`1512
`
`RECEIVE A SECOND
`UPDATE MESSAGE7
`
`UPDATE THE STATUS OF EACH TASK
`BASED ON TASK DATA IN THE
`SECOND UPDATE MESSAGE
`
`
`
`1510
`
`NO
`
`1514
`
`CiM Ex. 1044 Page 25
`
`

`
`Patent Application Publication May 8, 2003 Sheet 25 of 33 US 2003/0088534 A1
`
`FIGURE 25
`
`A 600
`
`QUERY A. FIRST EMPLOYEE TO
`UPDATE A STATUS FOR EACH TASK
`
`RECEIVE TASK COMPLETION DATA
`FROM THE FIRST EMPLOYEE VIA A
`CLIENT DEVICE AT A FIRST FACILITY
`
`SEND A FIRST STATUS UPDATE
`MESSAGE FROM THE CLIENT DEVICE TO
`A CENTRAL MANAGEMENT SERVER, THE
`FIRST STATUS UPDATE MESSAGE
`INCLUDING THE TASK COMPLETION DATA
`
`
`
`RECEIVE
`A WORKSTATUS REPORT
`REQUEST FOR A SECOND
`MPLOYEE?
`
`1602
`
`1604
`
`1606
`
`NO
`
`YES
`
`1610
`
`DISPLAY THE WORKSTATUS REPORT ON THE
`CLIENT DEVICE TO THE SECOND EMPLOYEE
`
`1612
`
`
`
`
`
`
`
`STATUS
`CHANGED FOR ANY TASK IN THE
`REPORT2
`
`SEND A SECOND UPDATE MESSAGE
`INCLUDING CHANGED STATUS TASK DATA TO
`THE CENTRAL MANAGEMENT SERVER
`
`
`
`NO
`
`1614
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`CiM Ex. 1044 Page 26
`
`

`
`May 8, 2003 Sheet 26 of 33 US 2003/0088534 A1
`Patent Application Publication
`FIGURE 26
`
`START
`
`A 700
`
`
`
`RETRIEVE A TASK RECORD INCLUDING
`A TASK MARKED WITH A TASK
`"SCHEDULED" IDENTIFIER
`
`1702
`
`1704
`
`YES
`
`1706
`
`UPDATE ATASK SCHEDULED IDENTIFIER TO A
`TASK DUE IDENTIFIER IN A TASK RECORD
`
`
`
`NO
`
`1708
`
`
`
`
`
`
`
`MORE
`THAN ONE TASK RECORD
`INCLUDING ASCHEDULED TASK
`IDENTIFIER2
`
`
`
`YES
`
`RETRIEVE A NEXT TASK RECORD
`
`NO
`
`1710
`
`CiM Ex. 1044 Page 27
`
`

`
`Patent Application Publication May 8, 2003 Sheet 27 of 33 US 2003/0088534 A1
`
`START
`
`A 800
`
`1802
`
`RETRIEVE A TASK RECORD INCLUDING A
`TASK MARKED WITH A TASK DUE IDENTIFIER
`
`1804
`
`YES
`
`1806
`
`UPDATE THE TASK DUE IDENTIFIER TO
`A TASK LATE IDENTIFIER
`
`
`
`
`
`NO
`
`SEND AN ALERT TO AN EMPLOYEE HAVING
`A PREDETERMINED HIERARCHY LEVEL
`
`
`
`
`
`
`
`
`
`MORE
`THAN ONE TASK RECORD
`INCLUDING ATASK DUE
`IDENTIFIER2
`
`YES
`
`RETRIEVE A NEXT TASK RECORD
`
`1808
`
`NO
`
`1812
`
`CiM Ex. 1044 Page 28
`
`

`
`Patent Application Publication May 8, 2003 Sheet 28 of 33 US 2003/0088534 A1
`
`FIGURE 28
`
`START
`
`A 900
`
`
`
`RETRIEVE A TASK RECORD INCLUDING
`A TASK MARKED WITH A TASK
`APPROVED IDENTIFIER
`
`1902
`
`
`
`
`
`
`
`
`
`
`
`
`
`NO
`
`CLOSE THE TASK RECORD?
`
`1904
`
`YES
`
`1906
`
`UPDATE THE TASKAPPROVED IDENTIFIER
`TO A TASK CLOSED IDENTIFIER
`
`1908
`
`MORE
`THAN ONE TASK RECORD
`INCLUDING ATASK APPROVED
`IDENTIFIER2
`
`
`
`YES
`
`RETRIEVE A NEXT TASK RECORD
`
`NO
`
`1910
`
`CiM Ex. 1044 Page 29
`
`

`
`Patent Application Publication May 8, 2003 Sheet 29 of 33 US 2003/0088534 A1
`FIGURE 29
`
`START
`
`/*
`
`
`
`
`
`NO
`
`
`
`
`
`
`
`
`
`RETRIEVE ATASK RECORD INCLUDING
`A TASK WMARKED WITH A TASK
`DONE HDENTIFIER
`
`2002
`
`
`
`2004
`
`APPROVE THE TASK BY
`A SYSTEM7
`
`YES
`
`2006
`
`UPDATE ATASK DONE IDENTIFIER TO
`AN AUTOMATICALLY APPROVED TASK
`IDENTIFIER AND CLOSED IDENTIFIER
`
`MORE
`THAN ONE TASK INCLUDING A
`TASK DONE IDENTIFIER">
`
`
`
`YES
`
`RETRIEVE A NEXT RECORD INCLUDING
`A TASK DONE IDENTIFIER
`
`NO
`
`2010
`
`CiM Ex. 1044 Page 30
`
`

`
`Patent Application Publication May 8, 2003 Sheet 30 of 33 US 2003/0088534A1
`
`FIGURE 30
`START
`
`
`
`RETRIEVE A FIRST TASK RECORD
`INCLUDING ATASK MARKED WITH
`A TASK NOT DONE IDNETIFIER
`
`2100
`
`A
`
`2102
`
`NO
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2104
`
`
`
`
`
`CANCEL OR RESCHEDULE
`THE TASK?
`
`YES
`
`2106
`
`A ROUTINE TASK TYPE2
`
`YES
`
`UPDATE ATASK NOT DONE IDENTIFIER
`TO A TASK CANCELLED IDNETIFIER
`
`UPDATE ATASK NOT DONE IDENTIFIER
`TO A TASK RESCHEDULE HDNETIFIER
`
`MORE THAN
`ONE TASK INCLUDING ATASK NOT
`DONE IDENTIFIER7
`
`
`
`YES
`
`RETRIEVE A NEXT TASK RECORD
`
`2108
`
`NO
`2110
`
`NO
`
`2114
`
`CiM Ex. 1044 Page 31
`
`

`
`Patent Application Publication May 8, 2003 Sheet 31 of 33 US 2003/0088534 A1
`
`FIGURE 31
`
`START
`
`A
`
`
`
`RETRIEVE ATASK RECORD INCLUDING
`A TASK MARKED WITH A TASK
`RESCHEDULE IDENTIFIER
`
`2202
`
`
`
`CANCEL / CLOSE THE TASK?
`
`RESCHEDULE
`THE TASK
`
`2204
`
`2208
`
`UPDATE THE TASK RESCHEDULED IDENTIFIER
`TO A CANCEL / CLOSE IDENTIFIER
`
`
`
`
`
`2210
`
`MORE
`THAN ONE TASK INCLUDING A
`TASK RESCHEDULE
`IDENTIFIER2
`
`
`
`YES
`
`RETRIEVE A NEXT TASK RECORD
`
`NO
`
`2212
`
`CiM Ex. 1044 Page 32
`
`

`
`Patent Application Publication May 8, 2003 Sheet 32 of 33 US 2003/0088534 A1
`
`FIGURE 32
`
`START
`
`A
`
`RECEIVE A WORKSCHEDULE REQUEST
`INCLUDING USER ID AND FACILITY ID, REGION
`ID OR CUSTOMER ID
`
`2232
`
`RETRIEVE CUSTOMER RECORD
`CORRESPONDING TO THE FACILITY ID,
`REGION ID OR CUSTOMER ID OF THE WORK
`SCHEDULE REQUEST
`
`2234
`
`SEARCH CUSTOMER RECORD FOR USER ID
`AND CORRESPONDING LEVEL VALUE
`
`2236
`
`
`
`2240
`
`
`
`DOES LEVEL VALUE
`MATCH FACILITY ID, REGION ID OR
`CUSTOMER ID
`REQUESTED7
`
`
`
`YES
`
`RETRIEVE REQUESTED WORKSCHEDULE
`DATA AND SEND TO USER
`
`NO
`
`2242
`
`
`
`
`
`CiM Ex. 1044 Page 33
`
`

`
`Patent Application Publication May 8, 2003 Sheet 33 of 33 US 2003/0088534 A1
`
`FIGURE 33
`
`START
`
`/*
`
`2252
`
`RECEIVE A BROADCAST MESSAGE REQUEST
`FROM A HIGH LEVEL USER
`
`RETRIEVE CUSTOMER RECORD
`CORRESPONDING TO THE USER ID OF HIGH
`LEVEL USER
`
`2254
`
`SEARCH CUSTOMER RECORD FOR EACH
`USER ID VALUE
`
`2256
`
`RETRIEVE EACH USER RECORD FOR EACH
`USER ID FOUND IN CUSTOMER RECORD
`
`2258
`
`
`
`
`
`
`
`INSERT BROADCAST MESSAGE TEXT FROM
`BROADCAST MESSAGE REQUEST INTO EACH
`USER RECORD
`
`2260
`
`CiM Ex. 1044 Page 34
`
`

`
`US 2003/0088534 A1
`
`May 8, 2003
`
`METHOD AND APPARATUS FOR WORK
`MANAGEMENT FOR FACILITY MAINTENANCE
`
`FIELD OF THE INVENTION
`[0001] This present invention relates to facility manage
`ment. More specifically, it relates to a system and method for
`managing facilities using client devices at each facility that
`communicate with a central management server through a
`network.
`
`BACKGROUND OF THE INVENTION
`[0002] Facility maintenance is no longer considered just
`an overhead expense, and it plays an important role in a
`company’s success. The more an enterprise can optimize
`and maintain its assets, the more it can compete in the areas
`of cost and quality.
`[0003] One of the important factors in maintaining a
`successfully operating facility is work scheduling. Prior to
`the introduction of computerized work scheduling systems,
`scheduling of work was performed manually. The manual
`scheduling process involved determining what work has to
`be performed and the time, materials and resources, such as
`workers and tools required to perform it, as well as infor
`mation which influenced the schedule, such as the priority
`associated with the work orders. The frequency with which
`the scheduling process had to be performed along many
`other factors contributed to the development of computer
`ized scheduling systems.
`[0004] One of such computerized schedule systems is
`described in U.S. Pat. No. 5,111,391, Fields et al. The
`Fields’ patent relates to a system and method for the creation
`of staff schedules at remote locations, and takes into account
`location specific values and historical data, while simulta
`neously conforming to corporate policy regarding schedul
`ing standards and labor regulations. Another computerized
`schedule system is described in U.S. Pat. No. 5,343,387,
`Honma et al. The Honma’s patent is directed to a building
`management system. Specifically, the Honma’s patent
`describes a cyclic building maintenance work schedule
`preparation system that is useful in preparing a schedule
`table of cyclic work in advance upon sending workers to
`periodically visit client buildings under a maintenance con
`tract to conduct inspections at the buildings.
`[0005] In addition to the work scheduling, a maintenance
`analysis and worker training are also important factors in
`maintaining a successfully operating facility. One such sys
`tem is described in the U.S. Pat. No. 5,867,823, to Richard
`son. The Richardson’s patent describes a hand-held system
`that provides work guidance and instruction for carrying out
`a given task and records maintenance duties without the
`need for written records and that is carried by a worker.
`[0006] While the existing systems describe electronic
`work scheduling and providing instructions to a worker, a
`need still remains for a dynamic work management system
`enabling a user interaction with the system.
`
`SUMMARY OF THE INVENTION
`[0007] The system and method of the present invention
`includes a system and method for work management.
`[0008] In accordance with one aspect of the present inven
`tion, a system for work management includes a central
`
`management server configured to receive a first set of
`information including tasks to be performed and scheduled
`at a first facility. When the central management server
`receives the first set of information, the central management
`server generates a first work schedule for a first user selected
`to perform the first work schedule at the first facility.
`According to an exemplary embodiment of the present
`invention, the central management server is further config
`ured to receive a first task status update message correspond
`ing to the first work schedule and, responsively, update a
`status of each task of the work schedule based upon task
`completion data received in the first task status update
`message. The exemplary system of the present invention
`further includes a first client device corresponding to the first
`facility. The first client device includes an electronic man
`agement interface configured to display the first work sched
`ule to the first user at the first facility and further receive task
`completion data from the first user for each task in the first
`work schedule. The client device is further configured to
`incorporate the task completion data from the first user into
`the first task update message and send the first task update
`message to the central management server. The central
`management server according to an exemplary embodiment
`of the present invention further includes a database config
`ured to store the first work schedule, and the database
`includes a plurality of task identifiers each of which is
`associated with a corresponding one of a plurality of tasks
`specified in the first work schedule. According to an exem
`plary embodiment of the present invention, the central
`management server is a web-based central management
`server, and the electronic management interface on the first
`client device is a web-based electronic management inter
`face.
`[0009] In accordance with a preferred embodiment, a
`method for managing work at a facility includes receiving
`on a central management server from a first facility a first
`message including a first set of information including tasks
`to be performed and scheduled at the first facility, and
`generating a first work schedule for a first user selected to
`perform the first work schedule at the first facility. The
`method further includes sending from the central manage
`ment server to the first facility a second message including
`the first work schedule responsive to receiving a work
`schedule request from the first user. The method further
`includes receiving on the central management server from
`the first facility a third message including task status update
`data corresponding to the first work schedule, and updating
`a status of each task in the first work schedule based upon
`the task completion data received in the third message. The
`method further includes sending to the first facility a fourth
`message including the status of each task in the first sched
`ule. The central management server sends the fourth mes
`sage responsive to receiving a first work status request
`message from the first facility. The method in accordance
`with the present invention further includes monitoring a
`status of each task specified in the first work schedule using
`the task status update data received from the first facility,
`detecting that the status for a task indicates that the task is
`uncompleted, and rescheduling the uncompleted task
`responsively to detecting the uncompleted task status. The
`method further includes sending an alert message to a
`manager of the first facility associated with the uncompleted
`task.
`
`CiM Ex. 1044 Page 35
`
`

`
`US 2003/0088534 A1
`
`May 8, 2003
`
`[0010] In accordance with a preferred embodiment of the
`present invention, another method for managing work at a
`facility includes sending from a client device at a first
`facility to a central management server a first message
`defining a first set of information including tasks to be
`performed and scheduled at the first facility, receiving at the
`first client device a second message including a first work
`schedule for a first user selected to perform the first work
`schedule at the first facility, and displaying the first work
`schedule to the first user on an electronic management
`interface associated with the first client device. The method
`in accordance with the present invention further includes
`receiving via the electronic management interface a first user
`input for a task specified in the first work schedule, where
`the first user input includes task completion data correspond
`ing to the first work schedule, and responsively, generating
`on the first client device and sending to the central manage
`ment server a third message including task completion data
`corresponding to the first work schedule. The method in
`accordance with the present invention further includes
`receiving from the central management server a fourth
`message including status of each task in the first work
`schedule.
`[0011] In accordance with another aspect of the present
`invention, a fixed location interface unit configured to per
`mit information transfer between an end user and a central
`management server includes a first application configured to
`establish a communication link between the fixed location
`interface unit and the central management server, an elec
`tronic interface configured to display a first workschedule to
`a first user and receive from the first user task completion
`status data for each task in the first work schedule. The fixed
`location interface unit in accordance with the present inven
`tion further includes a second application configured to
`generate and send to the central management server a first
`task status update message upon receiving the task comple
`tion status data from the first user. In accordance with
`embodiments of the present invention, the electronic inter
`face is a web-based interface, a graphical user interface, a
`touch screen interface, or the combination thereof. Further,
`in accordance with embodiments of the present invention,
`the first work schedule displayed to the first user is an
`icon-based work schedule in which each task in the work
`schedule is associated with a task icon. In one embodiment
`of the present invention, the icon-based work schedule may
`include a color-coded task icon for each task in the first work
`schedule. The fixed location interface unit, in accordance
`with the present invention, includes a fourth application
`configured to permit a supervisory user to request a first
`work schedule report, receive the first work schedule report
`from the central management server, and display the report
`to the supervisory user.
`[0012] In accordance with another aspect of the present
`invention, a central management server is configured to
`manage work on a plurality of facilities. The central man
`agement server according to the present invention includes
`a database configured to store work schedules for a plurality
`of facilities, a plurality of facility records, a plurality of task
`identifiers for each task specified in the plurality of work
`schedules, and a plurality of instruction information records
`for each task. The central management server further
`includes a first application configured to receive from a first
`facility a first set of information including tasks to be
`performed and scheduled for the first facility. The central
`
`management further includes a second application config
`ured to retrieve a first facility record from the database and
`generate a plurality of first facility work schedules for a
`plurality of first facility users selected to perform the tasks
`at the first facility. The central management server stores the
`work schedules in a database. The central management
`server further includes a third application to generate an
`icon-based schedule for each of the plurality of first facility
`work schedules. In accordance with the present invention,
`each task specified in the work schedules is associated with
`a predetermined task icon. The central management server
`further includes a fourth application configured to receive a
`first work schedule request from a first user at a first facility.
`In accordance with the present invention, the first user
`requests the first work schedule via a fixed location interface
`unit configured to permit information transfer between the
`plurality of first facility users and the central management
`server. The fourth application is further configured to
`retrieve a first work schedule for the first user and send the
`first work schedule to the first user. The central management
`server in accordance with the present invention further
`includes a fifth application configured to receive a first task
`status update message corresponding to the first work sched
`ule and, responsively, update a status of each task of the first
`work schedule based upon task completion data received in
`the first task status update message.
`[0013] The foregoing and other features and advantages of
`the system and method for work management will be
`apparent from the following more particular description of
`preferred embodiments of the system and method as illus
`trated in the accompanying drawings.
`BRIEF DESCRIPTION OF THE DRAWINGS
`[0014] Preferred embodiments of the present inventions
`are described with reference to the following drawings,
`wherein:
`[0015] FIG. 1 is a diagram illustrating a preferred embodi
`ment of the network architecture for providing facility work
`management in accordance with the present invention;
`[0016] FIG. 2 is a functional block diagram illustrating
`one example of an embodiment of an Electronic Manage
`ment Interface according to the present invention;
`[0017] FIG. 3 is a data diagram illustrating an example of
`some data structures that may be present in a central server
`database in accordance with the present invention;
`[0018] FIG. 4 is a data diagram illustrating an example of
`data contained in a facility record, a task record and a user
`record in accordance with the present invention;
`[0019] FIG. 5 is a data diagram illustrating an example of
`a customer record populated with data for two customers in
`accordance with the present invention;
`[0020 FIG. 6 is a simplified diagram illustrating an
`embodiment of a software architecture that may be
`employed on an Electronic Management Interface in accor
`dance with the present invention;
`[0021] FIG. 7 is a block diagram illustrating an exchange
`of messages for requesting a work schedule according to one
`embodiment in accordance with the present invention;
`[0022] FIG. 8 is a block diagram illustrating an exchange
`of messages for requesting on work schedule according to a
`second embodiment in accordance with the present inven
`tion;
`
`CiM Ex. 1044 Page 36
`
`

`
`US 2003/0088534 A1
`
`May 8, 2003
`
`[0023] FIG. 9 is a block diagram illustrating a message
`flow for Electronic Management Interface central manage
`ment server communication in accordance with the present
`invention;
`[0024] FIGS. 10A, 10B and 10C are block diagrams
`illustrating three exemplary embodiments of EMI units in
`accordance with a preferred embodiment of the present
`invention;
`[0025] FIG. 11 is an exemplary language selection dialog
`box in accordance with a preferred embodiment of the
`present invention;
`[0026] FIG. 12 is an exemplary login dialog box in
`accordance with a preferred embodiment of the present
`invention;
`[0027] FIG. 13 is an exemplary icon-based schedule dia
`log box in accordance with a preferred embodiment of the
`present invention;
`[0028] FIG. 14 is an exemplary task location dialog box
`in accordance with a preferred embodiment of the present
`invention;
`[0029] FIG. 15 is an exemplary task instructions dialog
`box in accordance with a preferred embodiment of the
`present invention;
`[0030] FIG. 16 is an exemplary task status update dialog
`box in accordance with a preferred embodiment of the
`present invention;
`[0031] FIG. 17 is an exemplary web site dialog box for a
`web site user in accordance with a preferred embodiment of
`the present invention;
`[0032] FIG. 18 is an exemplary web site dialog box that
`may be displayed to a user upon authenticating the user
`accordance with a preferred embodiment of the present
`invention;
`[0033] FIG. 19 is an exemplary web-site work calendar
`dialog box in accordance with a preferred embodiment of
`the present invention;
`[0034] FIG. 20 is an exemplary dialog box illustrating a
`work order record in accordance with a preferred embodi
`ment of the present invention;
`[0035] FIG. 21