Construction time monitoring of an elevator system

Abstract

According to an aspect, there is provided a controller in an elevator system. The controller comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the controller to at least perform: determining remote identifier reading events at least in part based on data obtained from remote identifier readers configured to detect wirelessly readable remote identifiers in a building comprising the elevator system, wherein at least one of the remote identifier readers is arranged in each elevator car, and wherein each remote identifier reading event comprises timestamp data associated with the reading event, information identifying the associated remote identifier reader and a read remote identifier; and transmitting the remote identifier reading events to a backend system for further analysis.

Description

[0001] CONSTRUCTION TIME MONITORING OF AN ELEVATOR SYSTEM

[0002] BACKGROUND

[0003] Elevators may be used in a building construction phase , for example , for construction worker, construction material and equipment transport . In the construction time use ( CTU) , the elevators may be very heavily used and waiting times may increase . In the CTU, the amount of construction material and equipment transported with the elevators may be signi ficant , and loading and unloading of the transported construction material and equipment may take time . During the CTU, there may be long waiting queues for elevators of workers that are trying to access their assigned working floor .

[0004] Further, during the CTU, there are factors that impact negatively on the work ef ficiency of construction sites . For example , time may be wasted by construction workers waiting for elevators , and there may be delays in the transport of materials to corresponding floors . This in turn may cause chal lenges , for example , to the overal l schedule of a construction site .

[0005] SUMMARY

[0006] According to a first aspect , there is provided a controller in an elevator system . The controller comprises at least one proces sor ; and at least one memory storing instructions that , when executed by the at least one processor, cause the controller to at least perform : determining remote identifier reading events at least in part based on data obtained from remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising the elevator system, wherein at least one of the remote identi fier readers is arranged in each elevator car, and wherein each remote identi fier reading event comprises timestamp data associated with the reading event , information identi fying the associated remote identi fier reader and a read remote identi fier ; and transmitting the remote identifier reading events to a backend system for further analysis .

[0007] In an implementation form of the first aspect , a controller in an elevator system comprising at least one processor ; and at least one memory storing instructions that , when executed by the at least one processor, cause the controller to at least perform : determining remote identi fier reading events at least in part based on data obtained from remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising the elevator system, wherein at least one o f the remote identi fier readers is arranged in each elevator car, and wherein each remote identifier reading event comprises timestamp data associated with the reading event , information identi fying the associated remote identi fier reader and a read remote identi fier ; and transmitting the remote identifier reading events to a backend system for further analysis .

[0008] In an implementation form of the first aspect , the timestamp data associated with the reading event comprises an entering timestamp identi fying entering of the remote identi fier to a reading area of a remote identi fier reader and an exit timestamp identi fying an exit of the remote identi f ier from the reading area of the remote identi fier reader .

[0009] In an implementation form of the first aspect , the controller is configured to at least perform : obtaining elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; associating the elevator car event information with a remote identifier reading event ; and transmitting the elevator car event information to the backend system .

[0010] In an implementation form of the first aspect , the controller is configured to at least perform : obtaining elevator car event information comprising an elevator car event and timestamp data associated with an elevator car event ; and transmitting the elevator car event information to the backend system .

[0011] In an implementation form of the first aspect , the controller is configured to at least perform : controlling a remote identi fier reader to read remote identi fiers in response to obtaining the elevator car event information .

[0012] In an implementation form of the first aspect , the elevator car event is an elevator car door clos ing event .

[0013] According to a second aspect , there is provided an elevator system comprising at least one elevator car ; at least one remote identifier reader, wherein at least one of the remote identi fier readers is arranged in each elevator car ; and a controller according to the first aspect .

[0014] According to a third aspect , there is provided a backend system comprising at least one processor ; and at least one memory storing instructions that , when executed by the at least one processor, cause the backend system to at least perform : receiving, from a controller of an elevator system, remote identifier reading events associated with remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising an elevator system, at least one of the remote identi fier readers being arranged in each elevator car, wherein each remote identi fier reading event comprises timestamp data associated with the reading event , information identifying the associated remote identi fier reader and a read remote identi fier ; determining, for each read remote identi fier, a session at least in part based on the remote identi fier reading events , the session identi fying a j ourney of the read remote identi fier in the building comprising the elevator system; and determining at least one metric associated with the elevator system usage at least in part based on the sessions .

[0015] In an implementation form of the third aspect , the timestamp data associated with the reading event comprises an entering timestamp identi fying entering of the remote identi fier to a reading area of a remote identi fier reader and an exit timestamp identi fying an exit of the remote identi f ier from the reading area of the remote identi fier reader .

[0016] In an implementation form of the third aspect , the controller is configured to at least perform : receiving, from the controller of the elevator system, elevator car event information being associated with remote identi fier reading event , the elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; and determining the session for the remote identi fier at least in part based on the remote identi fier reading event and the elevator car event information .

[0017] In an implementation form of the third aspect , the controller is configured to at least perform : receiving, from the controller of the elevator system, elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; determining a remote identi fier associated with the elevator car event at least in part based on the timestamp data ; and determining the session for the remote identi f ier at least in part based on the remote identi fier reading event and the elevator car event information .

[0018] In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises waiting times in a lobby .

[0019] In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises trips from a gate to a working floor .

[0020] In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises the number of floors traveled by the remote identi fiers .

[0021] In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises loading and unloading times for an elevator .

[0022] In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises information identifying entities who have been loading and / or unloading an elevator .

[0023] In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises information identifying entities keeping doors of an elevator open longer than a threshold value . In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises wrong way elevator trip detection .

[0024] In an implementation form of the third aspect , the at least one metric associated with the elevator system usage comprises the busiest times of the elevator system .

[0025] According to a fourth aspect , there is provided a method for construction time monitoring . The method comprises determining, by a controller of an elevator system, remote identi fier reading events at least in part based on data obtained from remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising the elevator system, wherein at least one of the remote identi fier readers is arranged in each elevator car, and wherein each remote identi fier reading event comprises timestamp data associated with the reading event , information identi fying the associated remote identi fier reader and a read remote identi fier ; and transmitting, by the controller, the remote identi fier reading events to a backend system for further analysis .

[0026] In an implementation form of the fourth aspect , the timestamp data associated with the reading event comprises an entering timestamp identi fying entering of the remote identi fier to a reading area of a remote identi fier reader and an exit timestamp identi fying an exit of the remote identi f ier from the reading area of the remote identi fier reader .

[0027] In an implementation form of the fourth aspect , the method further comprises obtaining elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; associating the elevator car event information with a remote identi fier reading event ; and transmitting the elevator car event information to the backend system .

[0028] In an implementation form of the fourth aspect , the method further comprises obtaining elevator car event information comprising an elevator car event and timestamp data associated with an elevator car event ; and transmitting the elevator car event information to the backend system .

[0029] In an implementation form of the fourth aspect , the method further comprises controlling a remote identi fier reader to read remote identi f iers in response to obtaining the elevator car event information .

[0030] In an implementation form of the fourth aspect , the elevator car event is an elevator car door clos ing event .

[0031] According to a fi fth aspect , there is provided a method for construction time monitoring . The method comprises receiving, by a backend system from a control ler of an elevator system, remote identifier reading events associated with remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising an elevator system, at least one of the remote identi fier readers being arranged in each elevator car, wherein each remote identi fier reading event comprises timestamp data associated with the reading event , information identifying the associated remote identi fier reader and a read remote identi fier ; determining, by the backend system for each read remote identi fier, a session at least in part based on the remote identi fier reading events , the session identi fying a j ourney o f the read remote identi f ier in the building comprising the elevator system; and determining, by the backend system, at least one metric associated with the elevator system usage at least in part based on the sessions .

[0032] In an implementation form of the fi fth aspect , the timestamp data associated with the reading event comprises an entering timestamp identi fying entering of the remote identi fier to a reading area of a remote identi fier reader and an exit timestamp identi fying an exit of the remote identi fier from the reading area o f the remote identi fier reader .

[0033] In an implementation form of the fi fth aspect , the method further comprises receiving, from the controller of the elevator system, elevator car event information being associated with remote identi fier reading event , the elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; and determining the session for the remote identi fier at least in part based on the remote identi fier reading event and the elevator car event information .

[0034] In an implementation form of the fi fth aspect , the method further comprises receiving, from the controller of the elevator system, elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; determining a remote identi fier associated with the elevator car event at least in part based on the timestamp data ; and determining the session for the remote identi fier at least in part based on the remote identi fier reading event and the elevator car event information .

[0035] In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises waiting times in a lobby . In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises trips from a gate to a working floor .

[0036] In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises the number of floors traveled by the remote identi fiers .

[0037] In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises loading and unloading times for an elevator .

[0038] In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises information identifying entities who have been loading and / or unloading an elevator .

[0039] In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises information identifying entities keeping doors of an elevator open longer than a threshold value .

[0040] In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises wrong way elevator trip detection .

[0041] In an implementation form of the fi fth aspect , the at least one metric associated with the elevator system usage comprises the busiest times of the elevator system .

[0042] According to a sixth aspect , there is provided a computer program comprising instructions which, when the program is executed by at least one proces sor , cause a system to perform the method of the fourth or fi fth aspect .

[0043] According to a seventh aspect , there is provided a computer-readable medium comprising a computer program comprising instructions which, when the program is executed by at least one proces sor, cause a system to perform the method of the fourth or fi fth aspect .

[0044] BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings , which are included to provide a further understanding of the invention and constitute a part of this speci fication, illustrate embodiments of the invention and together with the description help to explain the principles of the invention . In the drawings :

[0046] FIG . 1 illustrates a system according to an example embodiment .

[0047] FIG . 2 illustrates a block diagram of a construction time monitoring system according to an example embodiment .

[0048] FIG . 3 illustrates a block diagram of a backend system according to an example embodiment .

[0049] FIG . 4 illustrates an elevator system according to an example embodiment .

[0050] FIG . 5 illustrates a flow diagram of a method according to an example embodiment .

[0051] FIG . 6 illustrates a flow diagram of a method according to an example embodiment . FIG . 7 illustrates a block diagram of an apparatus according to an example embodiment .

[0052] DETAILED DESCRIPTION

[0053] FIG . 1 illustrates a system according to an example embodiment . The system illustrated in FIG . 1 may be applied, for example , during a construction time use ( CTU) .

[0054] The system comprises a site controller 100 ( or a site hub ) which may be connected to an elevator controller 104 via a site application programming interface (API ) 102 . This enables the site controller 100 to provide instructions to the elevator controller 104 , for example , to allocate elevator calls . In another example embodiment , the functions of the site controller 100 may be implemented by the elevator controller 104 , an elevator group controller or an elevator drive and thus no API 102 and separate site controller 100 are needed . The site controller 100 in general may refer to an entity that is configured to enable an access or a connection to a variety of di f ferent system elements . In an example embodiment , the site controller 100 and the elevator controller 104 may be arranged in an elevator shaft 106 .

[0055] The site controller 100 may comprise a first communication interface configured to provide a connection to at least one local construction site data source 108A, 108B, 108C associated with a construction site 110 , wherein the at least one local construction site data source is configured to track people and / or material flow during the construction time use . In an example embodiment , one or more construction site data sources may be configured to track people flow and one or more construction site data sources may be configured to track material flow . In an example embodiment , one or more construction site data sources may be configured to track both the people flow and the material flow. The connection to the at least one local construction site data source 108A, 108B, 108C may be implemented, for example, using at least one the following techniques: a Wi-Fi connection, a physical Ethernet connection or an loT mesh connection depending on the location. The WiFi connection may be used, for example, when high data throughput is needed. The loT mesh connection may be used, for example, for small, cheap and / or battery powered devices that do not send much data.

[0056] In general, the at least one local construction site data source 108A, 108B, 108C may refer to external sensors, automated systems and / or data sources that store and provide information about which tools, materials and people (i.e. transportable entities) are about to be, or are currently being transported in the elevator. Different site data may be arranged in a single data source, for example, a database, or in multiple data sources. Any appropriate tracking and / or identification system may be used to track and / or identify the tools, material and people, for example, Bluetooth, radio frequency identification (RFID) applying RFID tags, wireless positioning etc. The local construction site data source 108A, 108B, 108C and / or back-end systems 116 may comprise identification information associated with each transportable entity. The identification information may be stored, for example, in a remotely readable device or tag, for example, a radio frequency identification (RFID) tag, attached to or otherwise associated with a transportable entity. The construction site 110 may then comprise one or more readers that are able to remotely read the identification information, when the corresponding transportable entity is loaded / unloaded to / from an elevator. The readers may be arranged in the elevators or outside the elevators at appropriate locations. In an example embodiment, the at least one local construction site data source 108A, 108B, 108C may comprise one or more of the following:

[0057] - a material and waste tracking system

[0058] - a people location and identification system

[0059] - an asset location and usage rate management system

[0060] - a site condition monitoring system.

[0061] The material and waste tracking system may provide information, for example, where material and / or tools are being located, and how much waste is accumulated during the construction phase. The people location and identification system may provide information, for example, on personnel location and identity of the personnel at the location. The asset location and usage rate management system may provide information, for example, on one or more assets that can be used in the construction site 110 and their associated location. An asset may refer, for example, to a material, a tool, an employee etc. The asset location and usage rate management system may also track usage rate of the one or more assets, for example, when, where and / or how long an asset was used during the construction phase, where and / or how long a specific employee has worked in the constructions site during the construction phase etc. This may then provide management information, for example, to a back-end system 116. The site condition monitoring system may provide information, for example, on a status associated with the construction site 110. The status may refer, for example, to a degree of readiness of the construction site 110, safety and health issues (for example, the number of reported accidents, the number of accident-free days) , temperature, humidity, particulate matter levels etc. The site controller 100 may further comprise a second communication interface 112 , for example , an application programming interface (API ) , configured to provide a connection to at least one client application 114 configured to access data provided by the site controller and to at least one back-end system 116 configured to provide construction proj ect data associated with the construction site 110 . The second communication interface 112 enables the site controller 100 to connect to external systems and external systems or clients to connect to the site controller 100 . For example , elevator calls may be allocated from a mobile device of a person working at the site . Additionally or alternatively, an elevator call may be scheduled and allocated automatically, for example , by a cloud-based managing entity, for example , the back-end system 116 . In general , the back-end system or systems 116 may be an entity that processes data receives from the elevator system . The back-end system or systems 116 may store information associated with the construction site 110 , for example information on construction workers , tools , materials , construction proj ect schedule , costs of di f ferent materials and / or priority of di f ferent materials . In another embodiment , the back-end system or systems 116 may have an access to one or more systems that provides this information .

[0062] In an example embodiment , the local construction site data sources 108A, 108B, 108B and / or the back-end systems 116 may store information associated with one or more transportable entities . A transportable entity may refer, for example , to at least one of a material , a tool , a batch of material , a person etc . Further, one or more properties may be associated with a transportable entity and may be known beforehand, for example , a weight , dimensions , a priority, a time window when the transportable entity is needed at a speci fic location, a destination floor, an identifier etc. Different transportable entities may have different priorities. In other words, the local construction site data sources 108A, 108B, 108B and / or the back-end systems 116 may include any information that somehow characterizes a transportable entity. Then, based on the information stored in the site data sources 108A, 108B, 108C and / or the back-end systems 116, the site controller 100 may be able to optimize the use of the elevators during the CTU.

[0063] In an example embodiment, the client application 114 may be executed in a device, for example, a mobile device of a user. The client application 114 may be used, for example, to place elevator calls, track material, tools and / or people.

[0064] In an example embodiment, the back-end system 116 may refer to one or more external project planning systems or construction management systems from which data indicating where items should be going may be obtained. The project planning system may comprise, for example, a cloud based construction project planning tool providing APIs to read data to other systems.

[0065] In an example embodiment, the back-end system 116 may refer to one or more logistics systems to obtain identification information of different materials, for example, to cloud based systems for tracking material deliveries and supply lines. The logistics systems may provide APIs to access logistics information that can be used by the site controller 100 for decision making.

[0066] In an example embodiment, the back-end system 116 may refer to one or more tool rental systems to obtain information of what kind of tools are being used, how they are used, and for what work tasks they are used during the CTU . The tool rental systems may refer to cloud based systems providing API s with tool rental information that can be used by the site controller 100 for decision making .

[0067] FIG . 2 illustrates a block diagram of an elevator system 200 according to an example embodiment . In an example embodiment , an elevator system may comprise the construction time monitoring system 200 .

[0068] The elevator system 200 may comprise a controller 202 and remote identi fier readers 204A, 204B, 204N communicatively connected to the controller 202 . The controller 202 may be, for example , an elevator controller or a separate controller arranged in the elevator system 200 . The remote identifier reader 204A, 204B, 204N is configured to detect wirelessly readable remote identi fiers . The remote identi fier reader 204A, 204B, 204N may refer, for example , to a reader configured to read radio frequency identi fication (RFID) identi fiers or tags or to a reader implementing any other remote reading technique . The remote identi fier readers 204A, 204B, 204N may be arranged in a bui lding in various locations . For example , one remote identi fier reader may be arranged in each elevator car of the elevator system, and one or more landing floors may have a separate remote identi fier reader, for example , close to an elevator waiting area of a landing floor .

[0069] FIG . 3 illustrates a block diagram of a backend system 300 according to an example embodiment . A backend system 300 comprises a controller 302 configured process data received from the elevator system 200 . The backend system 300 may be a cloud-based entity that is connected both to the elevator system 200 and at least one construction management system and / or a proj ect planning system . The backend system 300 may store information that links the remote identi fiers to actual construction workers , tools and materials . Alternatively, the backend system 300 may be able to retrieve this information from the construction management system or the proj ect planning system based on the remote identi fiers .

[0070] FIG . 4 illustrates an elevator system 400 according to an example embodiment . An elevator car 402 is configured to move vertically in an elevator shaft 404 . The elevator system 400 further comprises remote identi fier readers 204A, 204B, 204C, 204D, 204E , 204N arranged in selected locations in a building and connected to a controller 202 . The controller 202 may be an elevator controller or a separate controller arranged in the elevator system 400 . The remote identi fier readers 204A, 204B, 204C, 204D, 204E , 204N are configured to detect remote identi fier carried by construction workers and / or attached to tools and / or materials .

[0071] FIG . 5 illustrates a block diagram of a method according to an example embodiment . The steps discussed herein may be performed, for example , by the controller 202 of the elevator system 200 .

[0072] At 500 , the controller 202 may be configured to determine remote identi fier reading events at least in part based on data obtained from remote identifier readers configured to detect wirelessly readable remote identi fiers in a building comprising the elevator system 200 . The remote identi fiers , for example , RFID tags , may be carried by construction workers . Further, RFID tags may be attached to tools and / or construction materials . At least one of the remote identifier readers may be arranged in each elevator car of the elevator system or in each elevator car i f the elevator system 200 comprises multiple elevator cars . Remote identifier readers may additionally be arranged in desired locations of the building so that it is possible to monitor people, tool and material flow during the construction time in various parts of the building. Each remote identifier reading event may comprise timestamp data associated with the reading event, information identifying the associated remote identifier reader and a read remote identifier. In other words, each remote identifier reading event identifies what was read and when and where.

[0073] At 502, the controller 202 may be configured to transmit the remote identifier reading events to a backend system 300 for further analysis. The backend system 300 then may analyze and determine one or more characteristics relating to people, tool and material flow during the construction time based on the remote identifier reading events .

[0074] In an example embodiment, the timestamp data associated with the reading event comprises an entering timestamp identifying entering of the remote identifier to a reading area of a remote identifier reader and an exit timestamp identifying an exit of the remote identifier from the reading area of the remote identifier reader. This may enable to a solution in which it is possible to determine time spent in a reading area of a remote identifier reader.

[0075] In an example embodiment, the controller 202 may be configured to obtain elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event, associate the elevator car event information with a remote identifier reading event and transmit the elevator car event information to the backend system. For example, it is possible to link to the read remote identifier information that a travel from f loor 1 to f loor 22 was made by the read remote identi fier .

[0076] In an example embodiment , the controller 202 may be configured to obtain elevator car event information comprising an elevator car event and timestamp data as sociated with an elevator car event and transmit the elevator car event information to the backend system . In this embodiment , the elevator car event information and the elevator car event information are transmitted to the backend system as separate pieces of information . The backend system is then able to link the elevator car information to a speci fic remote identifier based on the timestamp data .

[0077] In an example embodiment , the controller 202 may be configured control a remote identifier reader to read remote identi fiers in response to obtaining the elevator car event information . Thus , the elevator car event may be , for example , an elevator car door closing event . For example , when a construction worker enters an elevator car, the controller 202 may control the remote identi fier reader arranged in the elevator car to read remote identi fiers in the elevator car only when the elevator door have been closed .

[0078] FIG . 6 illustrates a block diagram of a method according to an example embodiment . The steps discussed herein may be performed, for example , by the controller 302 of the backend system 300 .

[0079] At 600 , the controller 302 may be configured to receive , from a controller of an elevator system, remote identi fier reading events associated with remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising an elevator system, at least one of the remote identi fier readers being arranged in each elevator car. Each remote identifier reading event comprises timestamp data associated with the reading event, information identifying the associated remote identifier reader and a read remote identifier. In other words, the controller 302 may receive from the elevator system data relating to read identifiers that has been read using remote identifier readers arranged in the building. The data reveals what remote identifier was read and when and where .

[0080] At 602, the controller 302 may be configured to determine, for each read remote identifier, a session at least in part based on the remote identifier reading events. The session identifies a journey of the read remote identifier in the building comprising the elevator system. In other words, the movements of a remote identifier in the building can be tracked based on the remote identifier reading events.

[0081] At 604, the controller 302 may be configured to determine at least one metric associated with the elevator system usage at least in part based on the sessions. As the remote identifiers are carried by construction workers, and as remote identifiers can also be attached to tools and / or materials, the backend system is able to analyze how the elevator system is utilized during the construction time and what are the weaknesses and bottlenecks in the transportation.

[0082] In an example embodiment, the timestamp data associated with the reading event comprises an entering timestamp identifying entering of the remote identifier to a reading area of a remote identifier reader and an exit timestamp identifying an exit of the remote identifier from the reading area of the remote identifier reader. This may enable to a solution in which it is possible to determine a waiting time spent in a reading area of a remote identi fier reader . For example , i f a remote identi fier reader is placed in an elevator lobby, it is possible to determine waiting times associated with the remote identi fiers . For example , a construction worker travelling without special tools and / or materials may have a di f ferent waiting time in the elevator lobby than a construction worker carrying, for example , a space needing tool . As there may be a separate remote identi fier associated with the tool , it can be determined that the construction worker is transporting the tool as the sessions associated with the remote identi fiers of the construction worker and the tool are identical .

[0083] In an example embodiment , the controller 302 may be configured to receive , from the controller of the elevator system, elevator car event information being associated with remote identi fier reading event , the elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event , and determine the session for the remote identi f ier at least in part based on the remote identi fier reading event and the elevator car event information . For example , it is possible to link to the read remote identi fier information that a travel from floor 1 to floor 22 was made by the read remote identi fier . In other words , the elevator system may provide to the backend system additional information that has already been linked to the read remote identi fier .

[0084] In an example embodiment , the controller 302 may be configured to receive , from the controller of the elevator system, elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event , determining a remote identi fier associated with the elevator car event at least in part based on the timestamp data, and determining the session for the remote identi fier at least in part based on the remote identi fier reading event and the elevator car event information . When both the elevator car event and the remote identi fier reading event comprise timestamp data, the backend system is able to link the elevator car event to the remote identi fier reading event . For example , when a remote identi fier is read in an elevator car by a remote identi fier reader arranged in the elevator car, it is possible to link the remote identifier to a specific travel in the elevator car , for example , from floor 1 to floor 18 .

[0085] As discussed above , the backend system is able to determine one or more metrics associated with the elevator system usage based on the sessions associated with the read remote identi fiers . For example , i f a remote identi fier reader is arranged in a lobby area, it is possible to determine waiting times associated with construction workers , tools and materials in the lobby area . This may provide valuable information to the proj ect management of the construction site where time is spent during the construction time .

[0086] In another example embodiment , based on the sessions , it is possible to determine from a gate to a working floor . During the construction time di f ferent floors may be actively constructed in di fferent times . The backend system is now able to determine how and when the construction workers , tools and materials travel to the current working floor .

[0087] In another example embodiment , based on the sessions , it is possible to determine number of floors traveled by the remote identi fiers . For example , it is possible to determine whether a remote identifier travels short trips or long trips . For example , i f elevator are used excessively to short trips , thi s prohibits using the elevator to more important and longer trips .

[0088] In another example embodiment , based on the sessions , it is possible to determine loading and unloading times for an elevator . When an elevator is loaded and unloaded, one or more remote identi f iers stay longer within the reading area of a remote identi fier reader arranged in an elevator car . By analyzing the time when the remote identi fiers were in the reading area, it is possible to determine the loading and unloading times for the elevator and also who were loading and unloading the elevator and what tools and / or materials were involved in the loading and unloading .

[0089] In another example embodiment , based on the sessions , it is possible to determine loading and unloading times for an elevator . When an elevator is loaded and unloaded, one or more remote identifiers usually stay longer within the reading area of a remote identi fier reader arranged in an elevator car . However, sometimes during loading and unloading, it may be that no remote identi fiers are detected with the remote identi fier reader . This may mean that a worker or workers have gone further away, for example , to pick or deliver materials etc . In an example , elevator events relating to door status can be combined with the sessions . For example , based on the sessions and the elevator car events it can be detected that the elevator car doors are not closed while no remote identi f iers can be read over a certain time period . This information can then be used when determining at least one metric associated with the elevator system usage . The metric may indicate , for example , that too long loading and unloading time periods exist . The metric may also be used to provide instructions or feedback to workers that necessary materials should be brought into a lobby area before starting to load the elevator car or that unloading should be performed to the lobby area first , in order to free the elevator to serve other users .

[0090] In another example embodiment , based on the sessions , it is possible to determine information identi fying entities keeping doors of an elevator open longer than a threshold value . When the elevator doors are open, the remote identi fier reader arranged in the elevator car detects the same remote identi fiers continuously . This information can then be used for determining the identities of the construction workers involved .

[0091] In another example embodiment , based on the sessions , it is possible to determine wrong way elevator trip detection . For example , a construction worker may first travel to a speci fic floor and then continue to an intermediate floor . This may cause unnecessary congestion in the elevator system .

[0092] In another example embodiment , based on the sessions , it is possible to determine the busiest times of the elevator system . The collected sess ion data reveals the amounts of trips performed in the elevator system and when the trips were performed . Additionally, it is possible to determine waiting times in lobbies and the amount of construction workers / tools / material waiting in the lobbies . Based on al l thi s information, the backend system is able to determine the busiest times of the elevator system .

[0093] The metrics determined based on the sessions of the remote identi fiers allows to understand what causes problems during the construction time and identi fy what measures should be taken to improve the waiting times and / or transportation capacity of the elevator system.

[0094] In another example embodiment, the backend system may be configured to generate reports, alerts and / or notifications to relevant stakeholders based on the metrics. This may be performed, for example, when the metrics are not within predetermined thresholds or when the metrics deviate from recorded or analyzed normal trends and / or patterns enough, for example, by a threshold value. In an example, the backend system 116 may be configured to send the reports, alerts and / or notifications to the client application 114 via the API 112. In an example embodiment, the reports, alerts and / or notifications may be provided separately for individual tags or remote identifier groups. For example, it may be possible to analyze that remote identifiers belonging to the same session, material or tool type, subgroup ( subcontractor / company / worker type (for example, a plumber, an electrician, a carpenter etc.) ) are not within at least one preset threshold.

[0095] FIG. 7 illustrates a block diagram of an apparatus 700 or a system according to an example embodiment. The apparatus 700 may be, for example, a computer or a server computer, and it may be configured to implement the functions of the controller 202 or the controller 302. In an example embodiment, the apparatus 700 may be integrated to be part of an elevator controller or an elevator group controller.

[0096] The apparatus 700 comprises one or more processors 702, and one or more memories 704 that comprise computer program code. The apparatus 700 may also include a first communication interface 708 configured to enable communication with other entities or network elements. Although the apparatus 700 is depicted to include only one processor 702 , the apparatus 700 may include more than one processor . In an example embodiment , the memory 704 is capable of storing instructions , such as an operating system and / or various applications .

[0097] Furthermore , the processor 702 is capable of executing the stored instructions . In an example embodiment , the processor 702 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors . For example , the processor 702 may be embodied as one or more of various process ing devices , such as a coprocessor, a microprocessor, a controller, a digital signal processor ( DSP ) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as , for example , an application speci fic integrated circuit (AS IC ) , a field programmable gate array ( FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like . In an example embodiment, the processor 702 may be configured to execute hard-coded functionality . In an example embodiment , the processor 702 is embodied as an executor of software instructions , wherein the instructions may speci fically configure the processor 702 to perform the algorithms and / or operations described herein when the instructions are executed .

[0098] The memory 704 may be embodied as one or more volatile memory devices , one or more non-volatile memory devices , and / or a combination of one or more volatile memory devices and non-volatile memory devices . For example , the memory 704 may be embodied as semiconductor memories ( such as mask ROM, PROM (programmable ROM) , EPROM ( erasable PROM) , flash ROM, RAM ( random access memory) , etc . ) . In an embodiment , the at least one memory 704 may store program instructions 706 that , when executed by the at least one processor 702 , cause the apparatus 700 to perform the functionality of the various embodiments discussed herein, for example , one or more methods discussed relating to FIG . 5 and 6 . Further, in an embodiment , at least one of the processor 702 and the memory 704 may constitute means for implementing the discussed functionality .

[0099] One or more of the examples and example embodiments discussed above may allow to understand what causes problems during the construction time and identi fy what measures should be taken to improve the waiting times and / or transportation capacity of the elevator system . Further, one or more of the examples and example embodiments discussed above may enable a solution that enhances the utili zation of elevators during the construction time , thus enhancing the overall construction proj ect schedule . Further, one or more of the examples and example embodiments discussed above may enable a solution in which sessions associated with remote identi fiers can further be combined with elevator events ( for example , doors , positions , actions , call state ) to provide insights on the movement of individual tags . This allows calculating various values ( lobby waiting time , start / end floors , number of floors traveled, total session time ) that can be used to monitor and improve the waiting times .

[0100] Example embodiments may be implemented in software , hardware , application logic or a combination of software , hardware and application logic . The example embodiments can store information relating to various methods described herein . This information can be stored in one or more memories , such as a hard disk, optical disk, magneto-optical disk, RAM, and the like . One or more databases can store the information used to implement the example embodiments . The databases can be organi zed using data structures ( e . g . , records , tables , arrays , fields , graphs , trees , lists , and the like ) included in one or more memories or storage devices listed herein . The methods described with respect to the example embodiments can include appropriate data structures for storing data collected and / or generated by the methods of the devices and subsystems of the example embodiments in one or more databases .

[0101] The components of the example embodiments may include computer readable medium or memories for holding instructions programmed according to the teachings and for holding data structures , tables , records , and / or other data described herein . In an example embodiment , the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media . In the context of this document, a "computer-readable medium" may be any media or means that can contain, store , communicate , propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus , or device , such as a computer . A computer- readable medium may include a computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus , or device , such as a computer . A computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution . Such a medium can take many forms , including but not limited to , non-volatile media, volatile media, transmission media, and the like .

[0102] While there have been shown and described and pointed out fundamental novel features as applied to preferred embodiments thereof , it will be understood that various omissions and substitutions and changes in the form and details of the devices and methods described may be made by those skilled in the art without departing from the spirit o f the disclosure . For example , it is expres sly intended that all combinations of those elements and / or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the disclosure . Moreover, it should be recogni zed that structures and / or elements and / or method steps shown and / or described in connection with any disclosed form or embodiments may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice . Furthermore , means-plus- function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents , but also equivalent structures .

[0103] The applicant hereby discloses in isolation each individual feature described herein and any combination of two or more such features , to the extent that such features or combinations are capable of being carried out based on the present speci fication as a whole , in the light of the common general knowledge of a person skilled in the art , irrespective of whether such features or combinations of features solve any problems disclosed herein, and without limitation to the scope of the claims . The applicant indicates that the disclosed aspects / embodiments may consist of any such individual feature or combination of features . In view of the foregoing description it will be evident to a person skilled in the art that various modi fications may be made within the scope of the disclosure .

Claims

CLAIMS1. A controller in an elevator system comprising : at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the controller to at least perform: determining remote identifier reading events at least in part based on data obtained from remote identifier readers configured to detect wirelessly readable remote identifiers in a building comprising the elevator system, wherein at least one of the remote identifier readers is arranged in each elevator car, and wherein each remote identifier reading event comprises timestamp data associated with the reading event, information identifying the associated remote identifier reader and a read remote identifier; and transmitting the remote identifier reading events to a backend system for further analysis.

2. The controller according to claim 1, wherein the timestamp data associated with the reading event comprises an entering timestamp identifying entering of the remote identifier to a reading area of a remote identifier reader and an exit timestamp identifying an exit of the remote identifier from the reading area of the remote identifier reader.

3. The controller according to any one of claims 1 - 2, wherein the controller is configured to at least perform: obtaining elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event; associating the elevator car event information with a remote identifier reading event; andtransmitting the elevator car event information to the backend system.

4. The controller according to any one of claims 1 - 2, wherein the controller is configured to at least perform: obtaining elevator car event information comprising an elevator car event and timestamp data associated with an elevator car event; and transmitting the elevator car event information to the backend system.

5. The controller according to any one of claims 3 - 4, wherein the controller is configured to at least perform: controlling a remote identifier reader to read remote identifiers in response to obtaining the elevator car event information.

6. The controller according to any one of claims 5, wherein the elevator car event is an elevator car door closing event.

7. An elevator system comprising: at least one elevator car; at least one remote identifier reader, wherein at least one of the remote identifier readers is arranged in each elevator car; and a controller according to any one of claims 1 - 6.

8. A backend system comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the backend system to at least perform:receiving, from a controller of an elevator system, remote identi fier reading events associated with remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising an elevator system, at least one of the remote identi fier readers being arranged in each elevator car, wherein each remote identi fier reading event comprises timestamp data associated with the reading event , information identifying the associated remote identi fier reader and a read remote identi fier ; determining, for each read remote identi fier, a session at least in part based on the remote identi fier reading events , the session identifying a j ourney of the read remote identi fier in the building comprising the elevator system; and determining at least one metric associated with the elevator system usage at least in part based on the sessions .9 . The backend system according to claim 8 , wherein the timestamp data associated with the reading event comprises an entering timestamp identi fying entering of the remote identi fier to a reading area of a remote identi fier reader and an exit timestamp identi fying an exit of the remote identi fier from the reading area of the remote identi fier reader .10 . The backend system according to claim 8 or 9 , wherein the controller is configured to at least perform : receiving, from the controller of the elevator system, elevator car event information being associated with remote identi fier reading event , the elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; anddetermining the session for the remote identi fier at least in part based on the remote identi fier reading event and the elevator car event information .11 . The backend system according to claim 8 or 9 , wherein the controller is configured to at least perform : receiving, from the controller of the elevator system, elevator car event information comprising an elevator car event and timestamp data associated with the elevator car event ; determining a remote identi fier associated with the elevator car event at least in part based on the timestamp data ; and determining the session for the remote identi fier at least in part based on the remote identi fier reading event and the elevator car event information .12 . The backend system according to any one of claims 8 - 11 , wherein the at least one metric associated with the elevator system usage comprises waiting times in a lobby .13 . The backend system according to any one of claims 8 - 12 , wherein the at least one metric associated with the elevator system usage comprises trips from a gate to a working floor .14 . The backend system according to any one of claims 8 - 13 , wherein the at least one metric associated with the elevator system usage comprises the number of floors traveled by the remote identi fiers .15 . The backend system according to any one of claims 8 - 14 , wherein the at least one metric associated with the elevator system usage comprises loading and unloading times for an elevator .16 . The backend system according to any one of claims 8 - 15 , wherein the at least one metric associated with the elevator system usage comprises information identi fying entities who have been loading and / or unloading an elevator .17 . The backend system according to any one of claims 8 - 16 , wherein the at least one metric associated with the elevator system usage comprises information identi fying entities keeping doors of an elevator open longer than a threshold value .18 . The backend system according to any one of claims 8 - 17 , wherein the at least one metric associated with the elevator system usage comprises wrong way elevator trip detection .19 . The backend system according to any one of claims 8 - 18 , wherein the at least one metric associated with the elevator system usage comprises the busiest times of the elevator system .20 . A method for construction time monitoring, the method comprising : determining, by a controller of an elevator system, remote identi fier reading events at least in part based on data obtained from remote identifier readers configured to detect wirelessly readable remote identi fiers in a building comprising the elevatorsystem, wherein at least one of the remote identi fier readers is arranged in each elevator car, and wherein each remote identi fier reading event comprises timestamp data associated with the reading event , information identi fying the associated remote identi fier reader and a read remote identi fier ; and transmitting, by the controller, the remote identi fier reading events to a backend system for further analysis .21 . A method for construction time monitoring, the method comprising : receiving, by a backend system from a controller of an elevator system, remote identi fier reading events associated with remote identi fier readers configured to detect wirelessly readable remote identi fiers in a building comprising an elevator system, at least one of the remote identifier readers being arranged in each elevator car, wherein each remote identi fier reading event comprises timestamp data associated with the reading event , information identi fying the associated remote identi fier reader and a read remote identi fier ; determining, by the backend system for each read remote identi fier, a sess ion at least in part based on the remote identi fier reading events , the session identi fying a j ourney o f the read remote identi f ier in the building comprising the elevator system; and determining, by the backend system, at least one metric associated with the elevator system usage at least in part based on the sessions .22 . A computer program comprising instructions which, when the program is executed by at least one processor, cause an apparatus to perform the method o f any of claims 20 - 21 .23 . A computer-readable medium compri sing a computer program comprising instructions which, when the program is executed by at least one processor, cause an apparatus to perform the method of any of claims 20 - 21 .

Images