Abstract:
A method for data retrieval and uniformalization of code events data for an elevator, comprising the steps of transmitting code events from an elevator controller to a business partner by means of a web services application, the business partner retrieving the data, storing the data in a business partner&#39;s data storage, and uniformalizing the data, and the business partner presenting the data by means of web and mobile applications. Another method for data retrieval and uniformalization comprising the steps of a service provider storing elevator data, the service provider transmitting said data to a web services application, a business partner retrieving said data by means of the web services application, the business partner storing the data in a business partner&#39;s data storage, the business partner uniformalizing the data, and the business partner presenting the data by means of a web and mobile device application.

Description:
FIELD 
       [0001]    The invention relates to the field of elevator/escalator maintenance data, and in particular, retrieving, uniformalizing and storing maintenance and callback data from service providers and elevating device controllers. 
       BACKGROUND 
       [0002]    Often, facility owners have multiple elevator/escalator service providers that maintain and repair their equipment, which is generally manufactured by various manufacturers. The service provider provides regular maintenance visits on a monthly, quarterly, or annual basis, as well as support in case of emergency (“callback”). 
         [0003]    Callback is generally initiated by facility owners via calling the service provider. Once initiated, the service provider enters the information into its internal system and dispatches a technician. The information generated from the call and the dispatch becomes a part of the callback history. Facility owners are able to monitor and access the callback history from the service provider&#39;s website. 
         [0004]    Whether facility owners have a single building or multiple buildings, they generally have multiple service providers. With the use of multiple service providers, facility owners are forced to manage multiple accounts in order to access the different web applications from each service provider. Additionally, the various service providers utilize different codes, formats and presentations with respect to their data files. As such, it is a mammoth task to collect and interpret the information from the various service providers, as there is no uniformalization of information storage among the various service providers. To further complicate this situation, service providers&#39; files are not always available, and are typically accessible only on an on-demand basis. 
         [0005]    At the conclusion of a contract for services, facility owners may decide not to extend the contract with the service providers depending on multiple factors (e.g., quality of service, new service provider offers, etc.). When the contract between the facility owner and the service provider is terminated, the facility owner no longer has access to data that was stored by the service provider during the contract tenure. As a result, the callback and maintenance history is no longer available to the facility owner. 
         [0006]    Since elevators and escalators have become computer controlled, they store elevator codes or events (e.g., information on the heat detectors or landing sensors) in the controller. Unfortunately, elevator/escalator code/event information is stored in a form that is proprietary to each manufacturer, and usage and maintenance data from different manufacturers cannot be compared. 
         [0007]    Technicians who service elevators and escalators access the data from the controller and are able to access various statistical data, events of use and the last service intervals from each elevator. From this data, technicians are able to facilitate servicing of the equipment and anticipate problems before they arise. 
         [0008]    Currently, the facility owner is able to access the controller&#39;s event and code remotely. Generally, the facility owner would install an application to gain remote access to the controller via a remote computer. Due to the direct connection between the controller and the facility owner&#39;s computer, the facility owner must be at the computer in order to open and view the event and code from the controller. As a result of the direct connection between the controller and the computer, the facility owner has to manage multiple accounts and computers. Additionally, the facility owner has no backup in case of data failure/disaster recovery. Further, the facility owner has to rely on a technician to analyze the event and code to identify or anticipate problems. 
         [0009]    Comparison of maintenance and usage data from various manufacturers is beneficial as it enables streamlining of maintenance procedures and comparison of elevators under different usage circumstances. However, a method of uniformalizing has not been heretofore disclosed in the prior art. Therefore, there is a need to retrieve and uniformalize elevator usage and maintenance data. 
       SUMMARY 
       [0010]    The invention relates to a method for data retrieval and uniformalization of code events data for an elevator, where any number of various service providers transmit code events from an elevator controller to a business partner through a web services application. The business partner retrieves and uniformalizes the data, and then presents the data through a web application. The data is uniformalized by mapping it into the database of the web server with data restrictions, and then converting the data to match those data restrictions. In one embodiment, the business partner can back up the data on a web server. In another embodiment, the data can be XML webservices data and can be retrieved, uniformalized and stored on a datastore. 
         [0011]    The invention also discloses another method for data retrieval and uniformalization. In such an embodiment, a service provider stores elevator data and transmits that data to a web services application. A business partner then retrieves that data through the web services application, uniformalizes the data, and then stores the data in a business partner web server. In another embodiment, the data can be data concerning elevator maintenance and service calls. The data is uniformalized by determining a mapping for the data into the database of the web server with data restrictions, and then converting that data to match its restrictions. In a separate embodiment, the data can be XML webservices data and the data can be retrieved, uniformalized and stored on a datastore. In another embodiment, a manufacturer application and API can be installed, where the manufacturer application and API transmit data to the web services application, allowing remote access by the end user. In yet another embodiment, the business partner can back up the stored data on a web server. In another embodiment of the present invention, the business partner may present the uniformalized data through an intuitive web application. The data from more than one elevator can be shown simultaneously in the web application. In yet another embodiment, the user can initiate and control callback by using a web services application, as well as communicate with the service provider through web services to make a call for service. In another embodiment, the business partner can set up web services for mobile applications, which allows mobile communication for the service provider with the business partner&#39;s datastore. The end user can then initiate a call using the business partner mobile application, communicating with the service provider through web services that makes a call for service of an elevator. In another embodiment, the end user can control callback by accessing the business partner&#39;s web server and initiating a call using a web services application. The web server can have a single sign on. In another embodiment, a standard presentation may display information from one or more service providers. In another embodiment, the web application can analyze datasets, display performance and deficiency information, and send out notifications to a single individual or multiple concerned parties. 
     
    
     
       DESCRIPTION OF FIGURES 
         [0012]      FIG. 1  shows a flowchart of the data retrieval process of the current art in which the end user requests callback by calling individual service providers, according to an embodiment of the present invention; 
           [0013]      FIG. 2  shows a flowchart of the data retrieval process of the current art as in  FIG. 1 , further elaborating that the information from service providers are generally in various file types, according to an embodiment of the present invention; 
           [0014]      FIG. 3  shows a flowchart of the data retrieval process of the current art directly from the elevator manufacturer controller, according to an embodiment of the present invention; 
           [0015]      FIG. 4  shows a flowchart of the data retrieval and uniformalization process from the service provider, according to an embodiment of the present invention; and 
           [0016]      FIG. 5  shows a flowchart of the data retrieval and uniformalization process from the controller, according to an embodiment of the present invention; 
           [0017]      FIG. 6 a    shows a sample dataset, according to an embodiment of the present invention; 
           [0018]      FIG. 6 b    shows a sample dataset, according to an embodiment of the present invention; 
           [0019]      FIG. 6 c    shows a sample dataset, according to an embodiment of the present invention; 
           [0020]      FIG. 7 a    shows a sample dataset, according to an embodiment of the present invention; 
           [0021]      FIG. 7 b    shows a sample dataset, according to an embodiment of the present invention; 
           [0022]      FIG. 7 c    shows a sample dataset, according to an embodiment of the present invention; 
           [0023]      FIG. 8 a    shows a sample of an XML string being transmitted between steps  60  and  65 , according to an embodiment of the present invention; 
           [0024]      FIG. 8 b    shows the data conversion from step  65  to step  70 , according to an embodiment of the present invention; 
           [0025]      FIG. 8 c    shows the data types of the Building Events Table, according to an embodiment of the present invention; 
           [0026]      FIG. 9 a    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0027]      FIG. 9 b    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0028]      FIG. 9 c    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0029]      FIG. 10 a    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0030]      FIG. 10 b    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0031]      FIG. 11 a    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0032]      FIG. 11 b    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0033]      FIG. 12 a    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; 
           [0034]      FIG. 12 b    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention; and 
           [0035]      FIG. 12 c    shows an example of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device, according to an embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0036]    With reference to  FIG. 4 , an embodiment of the data retrieval and uniformalization process for elevator/escalator (referred to generally as “elevator”) maintenance and callback data is described.  FIG. 4  relates to service providers that provide maintenance and standby on call service. The service providers perform standard maintenance, and store the maintenance information on the service provider&#39;s data storage. Furthermore, the service provider may be called (“service call”) by the user to rectify an issue with an elevating device, in which case the service provider will repair the elevator, and again store the service call information on the service provider&#39;s data storage. There is therefore information on both i) maintenance and ii) service calls on the service provider&#39;s data storage. The service provider has a web application that allows a user to log in and track the information and status of the maintenance and service call completed by the service provider. In step  5  any number of various service providers provide access to the respective service provider&#39;s data storage, and transmit that data to the business partner via a web services application, through a network such as the Internet. In step  10  the business partner retrieves the data from the network via a web services application. In step  15  the data is uniformalized and stored in the business partner facility. In the data retrieval and uniformalization process, the information using XML webservices is retrieved, uniformalized and stored on the Datastore. In step  20  the stored data is backed up by the business partner on a web server, and made available to the end user through a web application usable on fixed devices such as computers or mobile devices (e.g., smartphones, tablets and laptop computers). In step  25  the end user gains access to the business partner&#39;s web server via the Internet, allowing the end user to initiate and control callback by initiating a call or contact such as email or SMS using a web services application, which then communicates with the service provider system through web services to make a call for service of the elevator. In step  25  the end user may initiate and control callback by initiating a call using a web services application, which then communicates with the correct service provider system through web services to make a call for service of the elevator. The information from all service providers is uniformalized into the Datastore and may be presented intuitively on a web application at step  20 . In step  30  a web services for mobile application is set up by the business partner to allow mobile communication for the mobile application with the business partner&#39;s Datastore, so that the user may receive operating data at the elevator site or on the road. In step  35  the end user can control callback by initiating a call using business partner mobile application, which then communicates with the service provider system through web services for mobile application. 
         [0037]    With reference to  FIG. 5 , another embodiment of the data retrieval and uniformalization process is described.  FIG. 5  references controllers, which are devices built by disparate manufacturers, are installed on the machine room and control the operation of the elevator. The controllers collect and store data regarding the performance and service of each of the elevating devices, such as storing code events. Examples of code events are Heat Detectors, Recall Activated, Landing System Sensor Fault and Emergency Power Activated. A user can see events or codes for an elevator from a computer which has a direct connection to the controller. The present embodiment receives code events using XML webservices and stores them in the Datastore and uniformalizes them. In step  40  any number of various elevator controllers store code events through its connection with the elevator sensors. In step  45  the code events stored in the manufacturer controller is transmitted to a remote computer via a manufacturer network card. In step  55 , a manufacturer application and API would generally be installed to allow remote access by the user. In step  60  the manufacturer application and API transmit data to web services application. In step  65  the business partner retrieves the data from the network via the web services application. In step  70  the data is uniformalized and stored in the business partner facility. In step  75 , optionally, the stored data is backed up by the business partner on a web server. The uniformalized data may be presented through an intuitive web application. In step  80  the end user gains access to the business partner&#39;s web server via the Internet, allowing the end user to see data regarding the code events that have been created by an elevator. In step  85  a web services for mobile application is set up by the business partner to allow mobile communication with the business partner&#39;s datastore. In step  90  the business partner mobile application can access the controller code events data through web services. 
         [0038]    With reference to  FIGS. 6 a - c  and 7 a - c   , sample datasets are shown. In  FIG. 6 a   , table Activities contains activities having a unique activity id  102 , a company id  104 , a location id  106  which is tagged to the location of the elevating device, and a device id  108 , to identify a unique elevating device. The maintenance information is stored in the form of work description  110 , repair description  112 , the entered and completion dates  114 ,  116  and the work order number  118 . The invoicing information may be contained as invoice number  120 , estimated cost  122  and actual cost  124 . The callback information includes a callback id  123 , directive code  125 , deficiency number  126 , government-mandated code  127 , counter  128  for the number of occurrences, and billable  129  that determines whether the hours are billable or not. 
         [0039]    In  FIG. 6 b   , table Activity Labour contains a unique labour id  130 , the name of the mechanic  132 , the ticket number  134 , the hours spent at various rates per hour (regular hour, half hour, overtime and travel hours)  136 , as well as time spent at nonbillable activities  138 . 
         [0040]    In  FIG. 6 c   , table Activity Parts provides information on the parts used for the elevator repair. The part id  140  is a unique identifier, and also includes a SKU number  142 , OEM field  144 , and the name and manufacturer of the part  146 ,  148 , along with quantity of parts  150 , description  152  and price  154 . 
         [0041]    In  FIG. 7 a   , table Callbacks includes callback ID  156  for a unique record ID, device ID  158  to uniquely identify a device, a unique call code  160 , call code  162 , company callback ID  164 , company ID  166 , information regarding about the problem that occurred such as who entered the problem  168 , the date, time and description of the problem  169 , dispatch time  170 , the call status  171  (including call status and call close time and date), mechanic arrive time  172 , information regarding billable hours  174 , as well as other information regarding updates of the system  176  such as who updated it or when the update occurred. 
         [0042]    In  FIG. 7 b   , table Callback Time contains time  178 , callback ID  156 , dispatch time  170 , and mechanic arrive time  172  to determine the responsiveness of the mechanic&#39;s call. 
         [0043]    In  FIG. 7 c   , table Call Codes contains call code  162 , a further call code  160  to map the service provider code with business partner code and uniformalize the data, company ID  166 , and part name  182  to produce the call codes. 
         [0044]    With reference to  FIG. 8 a   , a sample of an XML string being transmitted between steps  60  and  65  is shown. In this example, the XML string transmits data on the building ID  185 , which is a unique identifier of the building, row ID  186  of the table, the manufacturer ID  187  of the elevating device, the dispatcher ID  188 , the car ID  189 , a car name  190  for the elevating device, a date stamp  192 , an event ID  193  which uniquely identifies the occurrence, along with the floor  195  where the incident occurred, and whether the event was confirmed  196 . 
         [0045]    In  FIG. 8 b   , data conversion from step  65  to step  70  is depicted, wherein the data from the XML string is uniformalized into tables of the Datastore  70 , in this example of the Building Events Table. The buildingid field is placed into the BuildingId field, the manufactureid into the ManufactureId field, and so on. 
         [0046]    In  FIG. 8 c   , the data types of the Building Events Table is shown. These fields in the table have data restrictions. For example, BuildingId is an integer, while RowId is a big integer, and CarId is a small integer and comment is a 255-character field that can hold various characters. In the data conversion process the data from the XML file is received and entered into the fields within the Datastore&#39;s 70 tables, under the restrictions of the various fields of the tables. Fields may be limited in different ways (such as varchar [127] or int [3]), and where the data does not fit, it is truncated or converted before being inserted into the database. For example, varchar [255] will be truncated to fit varchar [127], and a decimal number will be rounded to fit an integer data slot. In this way, the data is uniformalized into a single database. In an embodiment, inconsistencies of the field naming convention between the XML (representing the manufacturer&#39;s specification) and the tables of the Datastore  70  are resolved by means of a mapping table, wherein the names used by the XML incoming data are matched to the correct fields of the Datastore  70 . 
         [0047]      FIGS. 9 a - c , 10 a - b , 11 a - b  and 12 a - c    show further examples of XML data from Vendors that is used to encapsulate the maintenance history of an elevating device. 
         [0048]    With uniformalization of maintenance and usage data, there is a single sign on. The end user can control callback, allowing the end user to notify different concerned parties, such as owners, service providers, consultants and building tenants, to avoid any unwanted events, as well as send reminders of any kind. Further, uniformalization allows the end user to view information from multiple service providers in one standard presentation, instead of multiple reports in multiple formats. The end user can access information at anytime, providing access to the most recent information on their equipment. Further, information is backed up in the business partner facility. Therefore, the end user can access historical data even after switching service providers. Additionally, backup of data within the business partner&#39;s facility provides protection to the end user in the event of a data failure. Having the multiple datasets uniformalized enables the business partner application to analyze datasets, show performance and deficiencies, and send out notifications to the concerned parties.