Patent Application
20200031611
The present disclosure is related to passenger conveyor systems, and more particularly, to elevator management and control systems.
Elevators are key resources in current building schemes and structural designs. The ability to effectively move people through a building is related to the number of elevators available to service customers at any particular time. However, elevator cars can be scheduled to operate out of normal service, sometimes referred to as “out-of-group”. For example, an elevator car can be operating “in-group” and made available to service calls input by a customer, or can be scheduled out-of-group to allow for maintenance events, emergency events, freight service, and operation testing.
Conventional elevator systems also allow authorized personnel to manually invoke different operating modes of an elevator car. Thus, an elevator car may be manually taken out-of-group until the authorized personnel reinvokes the normal operating mode of the elevator, i.e., manually returns the elevator car into the servicing group.
Disclosed is an elevator management system that includes an elevator system and a service provider controller. The elevator system is configured to control at least one elevator car and to transmit a status message indicating status data of the at least one elevator car. The service provider controller is configured to determine a current operating mode of the at least one elevator car based on the status message and to assign the at least one elevator car to a current status group among a plurality of different status groups based on the current operating mode.
According to another non-limiting feature, the service provider controller is located remotely from the elevator system.
According to another non-limiting feature, the status message is continuously transmitted according to a transmit time.
According to another non-limiting feature, the elevator management system further comprises a user interface in signal communication with the service provider controller, the user interface configured to display the different status groups and to identify the at least one elevator car in the assigned current status group.
According to another non-limiting feature, the user interface is configured to the display the status information of the at least one elevator car.
According to another non-limiting feature, the service provider controller automatically updates the user interface in response to a change in the status data.
According to another non-limiting feature, the service provider controller updates the user interface by assigning the at least one elevator car to a different status group among the plurality of status groups in response to determining a change in the operating mode.
According to another non-limiting feature, the service provider controller determines whether at least one of a number of elevator cars operating in-group is above or below a threshold number assigned for passenger use.
According to another non-limiting feature, the service provider controller commands the user interface to display an alert when the number of elevator cars operating in-group falls below the threshold number.
According to another non-limiting feature, the service provider controller determines an optimal day and time to remove an elevator car from an in-group mode based on historical data and displays the optimal day and time on the user interface.
According to another non-limiting feature, the service provider controller automatically schedules removal of at least one elevator cars from operating in an in-group mode.
According to another non-limiting feature, the service provider controller automatically invokes an out-of-group mode of an out-of-group elevator car in response to removing the out-of-group elevator car from the in-group mode.
According to another non-limiting feature, the service provider controller calculates at least one of elevator car, group and building availability for a given time period, and commands the user interface to display the calculated availability.
Also disclosed is a method of managing an elevator system. The method comprises controlling, via an elevator system, at least one elevator car, transmitting, via the elevator system, a status message indicating status data of the at least one elevator car, determining, via a service provider controller, a current operating mode of the at least one elevator car based on the status message, and assigning the at least one elevator car to a current status group among a plurality of different status groups based on the current operating mode.
According to another non-limiting feature, the service provider controller is located remotely from the elevator system.
According to another non-limiting feature, the method further comprises continuously transmitting the status message according to transmit time.
According to another non-limiting feature, the method further comprises displaying, via a user interface in signal communication with the service provider controller, the different status groups to identify the at least one elevator car in the assigned current status group.
According to another non-limiting feature, the method further comprises displaying, via the user interface, the status information of the at least one elevator car based on the transmitted status message.
According to another non-limiting feature, the method further comprises detecting, via the service provider controller, a change in the status data, and automatically updating the user interface, via the service provider controller, in response to the change in the status data.
According to another non-limiting feature, updating the user interface further comprises determining, via the service provider controller, a change in the operating mode, and assigning the at least one elevator car to a different status group among the plurality of status groups in response to the change in the operating mode.
The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:
A detailed description of one or more embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures.
The term “about” is intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application.
Various non-limiting embodiments described herein provide an elevator management system that offers customers and maintenance providers the ability to efficiently schedule one or more elevators out-of-group. In addition, the elevator management system provides a service provider with real-time information on the operating status of one more elevator cars. In this manner, an out-of-group elevator car can be quickly identified and brought back into the service without requiring significant on-site maintenance servicing. In this manner, customer satisfaction is improved while providing a client the opportunity to reduce costs incurred from service provider on-site maintenance.
In one or more non-limiting embodiments, the elevator management system also provides the ability to view past history of elevator operations. If a customer has a complaint about elevator wait times, a historical view of the elevator cars in a group can be displayed to show the number of elevator cars available “in-group” for any time period. The system can automatically display whether the elevators “in-group” for a given time period is above or below a threshold for an acceptable service level. When the number of “in-group” elevator cars fall below the threshold, the customer can view whether the service level was affected by elevator malfunctions, or by the customer putting the elevator into an ‘out-of-group” mode. The historical in-group availability can also be used to have the system automatically recommend the best day and time to take a car “out-of-group” (e.g., for maintenance, special modes, etc.) to least effect the elevator service level.
With reference to
The tension member 107 engages the machine 111, which is part of an overhead structure of the elevator system 101. The machine 111 is configured to control movement between the elevator car 103 and the counterweight 105. The position reference system 113 may be mounted on a fixed part at the top of the elevator shaft 117, such as on a support or guide rail, and may be configured to provide position signals related to a position of the elevator car 103 within the elevator shaft 117. In other embodiments, the position reference system 113 may be directly mounted to a moving component of the machine 111, or may be located in other positions and/or configurations as known in the art. The position reference system 113 can be any device or mechanism for monitoring a position of an elevator car and/or counter weight, as known in the art. For example, without limitation, the position reference system 113 can be an encoder, sensor, or other system and can include velocity sensing, absolute position sensing, etc., as will be appreciated by those of skill in the art.
The system controller 115 is located, as shown, in a controller room 121 of the elevator shaft 117 and is configured to control the operation of the elevator system 101, and particularly the elevator car 103. For example, the system controller 115 may provide drive signals to the machine 111 to control the acceleration, deceleration, leveling, stopping, etc. of the elevator car 103. The system controller 115 may also be configured to receive position signals from the position reference system 113 or any other desired position reference device. When moving up or down within the elevator shaft 117 along guide rail 109, the elevator car 103 may stop at one or more landings 125 as controlled by the system controller 115. Although shown in a controller room 121, those of skill in the art will appreciate that the controller 115 can be located and/or configured in other locations or positions within the elevator system 101. In one embodiment, the system controller 115 may be located remotely or in the cloud.
The machine 111 may include a motor or similar driving mechanism. In accordance with embodiments of the disclosure, the machine 111 is configured to include an electrically driven motor. The power supply for the motor may be any power source, including a power grid, which, in combination with other components, is supplied to the motor. The machine 111 may include a traction sheave that imparts force to tension member 107 to move the elevator car 103 within elevator shaft 117.
Although shown and described with a roping system including tension member 107, elevator systems that employ other methods and mechanisms of moving an elevator car within an elevator shaft may employ embodiments of the present disclosure. For example, embodiments may be employed in ropeless elevator systems using a linear motor to impart motion to an elevator car. Embodiments may also be employed in ropeless elevator systems using a hydraulic lift to impart motion to an elevator car.
In other embodiments, the system comprises a conveyance system that moves passengers between floors and/or along a single floor. Such conveyance systems may include escalators, people movers, etc. Accordingly, embodiments described herein are not limited to elevator systems, such as that shown in
Turning now to
The elevator management system 150 further includes one or more terminal devices 158 and an elevator management user interface 300. In one or more non-limiting embodiments, the service provider controller 152, the terminal device 158 and/or the elevator management user interface 300 can be collectively referred to as an elevator management service provider system 155. The terminal device is capable of providing user data to the service provider controller 152. The terminal device 158 can include various types of computing devices such as, for example, a desktop computing workstation, laptop computer, a tablet computer, a smart phone, a smart watch, or other wearable smart computing devices. The user data includes a wide variety of data including, but not limited to, surrounding environmental data, location data, and elevator maintenance data.
The terminal device 158 is also configured to provide the service provider controller 152 with customer data. The customer data includes, for example, requests to schedule one or more elevator out-of-group. For instance, a customer may use a terminal device 158 to submit a request to schedule an elevator 103a for freight delivery on selected day and time. The service provider controller 152 can analyze the history of operating status of a given elevator system 101 to determine whether the day and time requested will conflict with the elevator system's capability based on the operation status history of the elevator system over time. If the history suggests that the day and time selected by the user typically involves a high-rate of out-of-group elevator cars (e.g., due to student move-in weekend for example), the service provider controller 152 can send a message to the customer denying the request and asking the user to submit an alternative day and/or time.
When the service provider controller 152 grants the customer's request, the service provider controller 152 can automatically send the customer a reminder message about the scheduled out-of-group event, add the scheduled out-of-group event to the customer's electronic calendar, etc. On the day of the scheduled out-of-group event, the service provider controller 152 is configured to automatically invoke the operating mode of an elevator car 103a, 103c, 103n. For example, the service provider controller 152 can automatically invoke the freight mode of elevator car 103a during the time frame requested by the user, and send a message to the customer indicating which elevator car is ready to perform the requested service and the current location of the elevator car. In another example, the service provider controller 152 can automatically override a manual attempt to place one or more elevator cars 103a, 103b, 103n out of group when the number of in-group elevator cars falls below a threshold number. In this manner, the service provider controller 152 can aim to keep a selected number of elevator cars in-group to ensure customers can be serviced at all times.
The service provider controller 152 is configured to receive status data from the elevator system 101. The status data includes, but is not limited to, elevator door state (i.e., are the door open or closed) door state time, elevator car travel direction, current operating modes of the elevator cars, current locations of the elevator cars (current floor or landing), passengers in car, etc.
The current operating modes can be grouped into categories. The categories may include, for example, serving passengers, avail for passenger use, out of service or powered down, maintenance, special customer modes, freight loading/delivery, and emergency modes. The status data can also include diagnostic data, which indicates reasons why an elevator car 103a, 103b, 103n is not servicing customer calls.
Each elevator car 103a, 103b, 103n can communicate its status data by transmitting a status message to the service provider controller 152 according to a set transmit time, e.g., every 10-20 seconds. It should be appreciated, however, that the transmit time is programmable and that other transmit times can be employed.
Accordingly, the frequent transmission of status data provides a time period snapshot of the usage of the elevator system 101, along with the current operating status of each elevator car 103a, 103b, 103n. This data can be presented across a group of elevator cars 103a, 103b, 103n of an entire building to ascertain times at which the elevator cars 103a, 103b, 103n are available for passenger use is below a critical point for acceptable building service. The frequently transmitted status data can also be utilized by the service provider to schedule maintenance at times that are least likely to inconvenience the customer. The service provider controller 152 can provide a visualization of the elevator system 101 based on the status data using the elevator management user interface 300 as described in greater detail below.
In one or more embodiments, the service provider controller 152 is configured to perform one or more elevator system management operations. The management operations include, but are not limited to, (1) determining whether the current or historical number of elevator cars 103a, 103b, 103n operating “in-group” is above or below a threshold number assigned for passenger use, (2) issuing a warning when the number of elevator cars 103a, 103b, 103n “in-group” falls below the threshold number, (3) recommending an optimal day and time to remove an elevator car 103a, 103b, 103n from an in-group mode (i.e., allow an elevator car to operate out-of-group) based on historical data, (4) automatically scheduling removal of elevator cars 103a, 103b, 103n from operating in-group and placing one or more elevator cars 103a, 103b, 103n in an out-of-group mode based on recommendation, and (5) calculating elevator car, group and/or building availability (not in shutdown mode) for any time period. In at least one embodiment, the time period can be manually input to the service provider controller 152 (e.g., by a customer or building operator).
In at least one non-limiting embodiment, an “in-group” threshold number can be selected by the customer or building operator. For instance, a building operator may desire to have a predetermined number of elevator cars 103a, 103b, 103n operating “in-group” during specified times to maintain acceptable customer service to its building riders. The building operator may allow for require a higher number of elevator cars 103a, 103b, 103n to operate “in-group” during weekday business hours, compared to weekend hours. Accordingly, a first “in-group” threshold can be set for weekday business hours (e.g., Monday through Friday, from 8:00 AM to 5:00 PM), while a different threshold number (e.g., a lower threshold) can be set for weekend hours (e.g., Saturday and Sunday).
The processing of the data 202 may reveal data including, but not limited to, a number of elevator door openings/closings, elevator door time, vibrations, a number of elevator rides, elevator ride performance, and elevator flight time, current elevator car location, and current elevator door status (i.e., open-door state or closed-door state). Although the sensor 210 is illustrated as being installed on the elevator car 103 itself, it should be appreciated that sensors can be included at different locations of the elevator system 101 (e.g., in the elevator shaft 117). In other embodiments, individual sensors are not required to get the data. For example, some systems map use information from sensors, others may use data from the elevator system controller 115.
The remote system 152 may be a computing device, such as, for example, a desktop computer, server, etc. The remote system 152 may also be a mobile computing device that is typically carried by a person, such as, for example a smartphone, PDA, smartwatch, tablet, laptop, etc. The remote system 152 may also be two separate devices that are synced together, such as, for example, a cellular phone and a desktop computer synced over an internet connection. In one or more embodiments, the remote system 152 can be implemented using a distributed computing platform (e.g., cloud computing). The remote system 152 may use data 202 from the sensor 210 to manage the elevator system 101. For example, a user operating a work station that implements the service provider controller 152 can utilized the data 202 to optimize in-group/out-of-group car scheduling, current elevator system operating state analysis, remote diagnostic analysis, determine historical elevator availability (uptime) rates, determine historical car in group rates, and/or remote elevator car operating mode control.
The sensor 210 is configured to transmit the data 202 to the remote system 152 via wired protocols (not shown), short-range wireless protocols 203 and/or long-range wireless protocols 204. Short-range wireless protocols 203 may include but are not limited to Bluetooth, Wi-Fi, HaLow (801.11ah), Wireless M-Bus, Zigbee, zWave. Using short-range wireless protocols 203, the sensor 210 is configured to transmit the data 202 to a local gateway device 240. The local gateway device 240 is configured to transmit the data 202 to the remote system 152 through a communications network 154. The communications network 154 may be a cellular network, satellite network, wired network, or any other communications network known to one of skill in the art. Using long-range wireless protocols 204, the sensor 210 is configured to transmit the data 202 to the remote system 152 through the communications network 154. Long-range wireless protocols 204 may include but are not limited to cellular, GSM, CDMA, LTE (NB-IoT, CAT M1), LoRa, or SigFox.
Turning now to
The elevator management user interface 300 displays an elevator car identifier (ID) 302a, 302b and 302c for each elevator car included in a given elevator system, and categorizes the elevator cars into status groups 304a, 304b and 304c based on the status messages received from each respective car. The status groups include, but are not limited to, an “in-group” status 304a, an “out-of-group mode” status 304b, and an “out-of-service” status 304c.
The in-group status group 304a includes the elevator cars which are currently operating in-group and available to service customer calls. The independent mode status group 304b includes elevator cars operating in various out-of-group status modes. The “out-of-group status” modes include, but are not limited to, freight status, independent service, VIP service, emergency status, maintenance status, etc. In this example, elevators included in the “out-of-group mode” status group differ from the elevator cars included in the out-of-service status group 304c in that cars operating in the “out-of-group mode” are powered on, but have been taken out-of-group to perform a particular service while ignoring general customer calls. These cars, however, can be returned to the “in-group” status 304a once its “out-of-group mode” service has been completed. The “out-of-service” cars, however, are powered down due to maintenance issues or are otherwise out of routine operation, for example, and cannot be placed back into the “in-group” status until elevator maintenance on the car has been completed.
The elevator management user interface 300 further displays status information 306a, 306b and 306c corresponding to each elevator car. The status information can actively change based on the status message received from each elevator car. In this manner, a service provider can analyze the elevator management user interface 300, and quickly determine the current status of a given elevator system during real time.
The elevator management user interface 300 may also include a mode change selector 308a, 308b and 308c, which allows the service provider to remotely change the operating mode of a given elevator car. For example, a service provider can remotely deactivate the freight mode of elevator car 302b after freight servicing has been completed and return elevator car 302b in-group. Accordingly, the elevator management user interface 300 is updated by removing elevator car 302b from the “out-of-group mode” 304b category and adding it to the “in-group” category 304a. In this manner, the elevator system is brought up-to-date in real time. In another example, the service provider can remotely power on an out-of-service elevator car (e.g., car 302c) and/or remotely perform a system reset using the mode change selector 308c.
Turning now to
At operation 508, the transmitted elevator car status is received at the service provider controller. The service provider controller can be located remotely from the elevator system and can be installed on a workstation operated by a service provider operator or can be running on a remote server or in the cloud. At operation 510, the service provider controller determines a status group of the elevator car based on the elevator car status. At operation 512, the determined status group of the elevator car is displayed on the elevator management user interface. At operation 514, current status information indicated by the transmitted status data is also displayed on the elevator management user interface.
At operation 516, a determination is made as to whether the status group and/or the status information of the elevator car has changed. In at least one embodiment, the service provider controller can automatically determine a change in the status group and/or the status information of the elevator car. When the status group and/or the status information has not changed, the method returns to operation 504 and continues monitoring the status of the elevator car. When, however, the status group and/or the status information has changed, the elevator management user interface is updated accordingly at operation 518, and the method returns to operation 504 to continue monitoring the status of the elevator car.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.
While the present disclosure has been described with reference to an exemplary embodiment or embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from the essential scope thereof. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this present disclosure, but that the present disclosure will include all embodiments falling within the scope of the claims.
