Patent Grant
11095502
Non-limiting embodiments relate generally to component installation procedures, and more particularly, to passenger conveyor component installation and commissioning procedures.
Various control system such as passenger conveyor systems, for example, employ components or devices such as printed circuit boards (PCBs) that include hardware controllers which are typically configured to operate in a particular host system (e.g., an elevator system). The components are commissioned at the manufacturing facility before being deployed into the field or to a site operating the host passenger conveyor system. Deploying and commissioning these components can involve various setup tasks, along with a certain degree of steps and procedures to be executed inside the boundaries of the device manufacturer's production facility. The procedures include, but are not limited to, deploying certificates, and configuring software protocols, as well as employing contract specific data items pertaining to the passenger conveyor system.
Traditional control system components must typically be configured and setup in the production facility compounds before being deployed to a particular destination in the field, e.g., the site containing the passenger conveyor system. In addition, replacement components and deployment configuration changes are typically configured according to a specific target deployment setup. Thus, flexibility in deciding where to deploy a device is may be restricted.
According to a non-limiting embodiment, a device commissioning system includes a terminal device, a data communication network, and a network controller. The terminal devices selects a device type of a component configured to operate in a control system, and outputs a device activation signal that requests a configuration file for commissioning the component according to a selected device type. The communication network is remotely located from the component and stores configuration files for commissioning different types of components. The network controller receives the device activation signal indicating a request to commission the component according to the selected device type and establishes a secure data link to deliver the configuration file in response to the device activation signal. The component receives the configuration file corresponding to the selected device type, and installs the configuration file to commission operation as the selected device type
The device commissioning system further includes a feature wherein the component excludes at least one configuration file prior to the terminal device outputting the device activation signal.
The device commissioning system further includes a feature wherein the secure data link is established directly between the data communication network and the component.
The device commissioning system further includes a feature wherein the secure data link is established between the data exchange network and the terminal device.
The device commissioning system further includes a feature wherein the terminal device receives the at least one configuration file via the secure data link, and delivers the received at least one configuration file to the component.
The device commissioning system further includes a feature wherein the data communication network includes a contract data uploading system configured to receive contract data corresponding to the control system, the contract data indicating information of the control system corresponding to the component, a data server configured to store the contract data obtained by the contract data uploading system and the at least one configuration file, an application programming interface (API) configured to operate as an abstraction layer that allows the component to perform different functions according to device type selected at the terminal device, and an internet-of-things (IoT) inter-network configured to establish a signal communication between the component and the network controller following the commissioning.
The device commissioning system further includes a feature wherein at least one configuration file for commissioning the component is generated based on the contract data of the control system corresponding to the component.
The device commissioning system further includes a feature wherein the terminal device is installed with a service tool (SVT) software application (APP) that provides a service technician with an interface to invoke data communication with the data network and the component, and to select the device type of the components among a plurality of different device types.
The device commissioning system further includes a feature wherein the device activation signal includes a device identification (ID) information corresponding to the component.
The device commissioning system further includes a feature wherein the device ID information includes at least one of a unique ID code assigned to the component, a serial number, a model type, hardware specifications and public encryption key.
The device commissioning system further includes a feature wherein the terminal device obtains the device ID information from the component.
The device commissioning system further includes a feature wherein the terminal device is configured to exchange data with the component, and wherein the component transmits the device ID information to the terminal device in response to receiving a device ID request signal from the terminal device.
The device commissioning system further includes a feature wherein the terminal device obtains the device ID information in response to scanning a machine-readable optical label included with the component.
The device commissioning system further includes a feature wherein the component includes at least one of an electronic hardware controller configured to control the control system, and a graphical user interface (GUI) control panel configured to receive elevator call requests and display elevator assignment information, floor destination information.
The device commissioning system further includes a feature wherein the terminal device includes at least one of a smart phone, a tablet computer, and a laptop computer.
According to another non-limiting embodiment, an electronic data communication network comprises a data server, and a network controller. The data server is configured to store at least one configuration file for commissioning different types of components located remotely from the data communication network. The network controller is configured to receive a device activation signal from a terminal device indicating a request to commission a selected device type corresponding to a deployed component, and to establish a secure data link configured to deliver the at least one configuration file corresponding to the selected device. The deployed component receives at least one configuration file corresponding to the selected device type, and automatically installs the at least one configuration file to commission operation as the selected device type.
The electronic data communication network includes another feature wherein the secure data link is established directly between the data communication network and the deployed component.
The electronic data communication network includes another feature wherein the secure data link is established directly between the data exchange network and the terminal device such that the terminal device receives the at least one configuration file, and delivers the received at least one configuration file to the deployed component.
According to yet another not-limiting embodiment, a method for commissioning a component deployed onsite of a control system comprises storing, via a data server installed in the data communication network remotely located from the deployed component. The configuration files are configured to commission different types of components. The method further comprises selecting, via an electronic terminal device, a device type of the deployed component, and outputting, via the terminal device, a device activation signal that requests at least one configuration file for commissioning the deployed component according to the selected device type. The method further comprises receiving the device activation signal at a network controller installed in the data communication network, and establishing a secure data link to deliver the at least one configuration file from the data communication network in response to the device activation signal. The method further comprises delivering the at least one configuration file corresponding to the selected device to the deployed component, and installing the at least one configuration file on the deployed component to commission operation as the selected device type.
The method further comprises deploying the component without at least one configuration file prior to outputting the device activation signal.
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. In addition, descriptions of providing various procedures for configuring, setting up, and establishing operation of a passenger conveyor system device is referred to hereon as “device commissioning.”
Various embodiments of the disclosure provide a device commissioning system capable of being executed “ad-hoc” to commission a component deployed in the field or on-site of a host control system. such as, for example, a passenger conveyor system or elevator system With respect to elevator systems, for example, one or more non-limiting embodiments provides a device commissioning system that establishes various preconditions including, but not limited to, a unique and unalterable data exchange which is accessible to a service technician operating on a given conveyor system, which identifies passenger conveyor devices, an active connection between a passenger conveyor device and a trusted system of the manufacturer, and an active connection to the trusted system and the service technician using an authentication resource initiates a secure data link for exchange data.
The device commissioning system according to various non-limiting embodiments described herein allows non-configured passenger conveyor devices (e.g., devices that are not installed with one or more configuration files corresponding to a particular device type and/or passenger conveyor system) to be shipped generically with the possibility to be configured in the field for a range of applications or functions provided by a selected device type. Passenger conveyor devices can also be re-purposed or re-configured without being sent back to the producing entity's compounds or manufacturing facility.
Over time, passenger conveyor system devices implemented in a passenger conveyor system can become damaged or inoperable thereby requiring replacement. The device commissioning system allows a failed device to be replaced with a new device which may have already been deployed into the field without initially being configured. As a result, it is unnecessary to notify the manufacturing facility of a device's use case, or limit a device to an intended functionality before deploying the device into the field.
With reference now to
The non-configured passenger conveyor component 102 is deployed in the field, and is capable of operating onsite 104 with a corresponding or host passenger conveyor system 106 once installed with the appropriate configuration files. Although the passenger conveyor component 102 is deployed without having configuration files installed therein, the passenger conveyor component 102 may be initially deployed with various software files and data that allows for ad-hoc onsite commissioning. In at least one non-limiting embodiment, the passenger conveyor component 102 is deployed with hardware identification (ID) information, a unique private/public key pair, a public key/certificate, a model number, firmware version, and a commissioning API URL used to request signal communication with a remotely located data communications network 110 that stores one or more configuration files necessary for commissioning the component 102.
The passenger conveyor component 102 includes, but is not limited to, printed circuit board (PCB) 102 containing an electronic hardware controller configured to control the passenger conveyor system 106. The passenger conveyor component 102 can also include a graphical user interface (GUI) control panel configured to receive elevator call requests and display elevator assignment information, floor destination information, etc. The passenger conveyor system 106 includes, for example, an elevator system, an escalator system or a moving walk way.
The device commissioning system 100 includes a terminal device 108, an electronic data communication network 110, and a network controller 111. The terminal device 108 is configured to electrically communicate with the passenger conveyor component 102 configured to operate the conveyor system 106 (e.g., an elevator) and the data communication network 110 to facilitate commissioning of the passenger conveyor component 102. The terminal device 108 can be implemented as various electronic communication devices including, but not limited to, a smart phone, a tablet computer, and a laptop computer. The terminal device 108 is installed with a service tool (SVT) or other configuration software application (APP) that provides a service technician with an interface to invoke data communication with the data network 110 and the passenger conveyor component 102. The SVT APP interface also allows the service technician to select a device type of the passenger conveyor device among a plurality of different device types as discussed in greater detail below.
A service technician can utilize the terminal device 108 to initiate the process for commissioning the non-configured passenger conveyor component 102 used to operate with a host conveyor system (e.g., an elevator or elevator system). For instance, a service technician executes the SVT APP installed on the terminal device 108 and selects a desired device type of the passenger conveyor component 102. For example, the service technician can select “elevator controller” from the SVT APP in order to commission the non-configured component 102 as an elevator controller for a particular elevator system 106. Once commissioned, the component 102 can control various operations of the elevator system 106 including, but not limited to, elevator calls, floor assignments, etc. In another example, the service technician can select “elevator GUI control panel” to commission the non-configured component 102 as a GUI control panel included in a particular elevator system 106. Once commissioned, the component 102 can receive elevator call requests, display elevator assignment information, floor destination information, etc.
After selecting the device type, the service technician then obtains device identification (ID) information corresponding to the passenger conveyor component 102. The device ID information includes, but not limited to, a unique ID code assigned to the passenger conveyor component 102, a serial number of the physical component 102, model type of the physical component 102, and hardware specifications of the physical component 102. The terminal device 108 is configured to exchange data with the passenger conveyor component 102 wirelessly (e.g., via Bluetooth transmission) or by wire (e.g., using USB connections). In at least one embodiment, the passenger conveyor component 102 can wirelessly transmit the device ID information to the terminal device 108 in response to receiving a device ID request signal.
The device ID information can also be labeled on the passenger conveyor component 102. For example, the passenger conveyor device can be deployed with a label such as for example, a machine-readable optical label including, but not limited to a barcode and a quick response (QR) code. Accordingly, the terminal device 108 can obtain the device ID information in response to optically scanning the machine-readable optical label via an integrated camera system or other optical sensor. A label displaying specific device ID information can also be adhered to the physical component 102 so that a service technician can manually inputs the device ID information into the terminal device 108 to output a device activation signal to the passenger conveyor system 106 that requests configuration files or connection string for commissioning the passenger conveyor component 102 according to the selected device type.
The electronic data communication network 110 is remotely located from the passenger conveyor component 102 and the terminal device 108. In one example, the data communication network 110 can be operated by a manufacturer of the passenger conveyor component 102. In at least one non-limited embodiment, the data communication network 110 is implemented as a cloud-computing network, and can store configuration files for commissioning different types of passenger conveyor devices 102 configured to operate with the passenger conveyor system 106. The configuration files or connection string include, but are not limited to, connection secrets, protocol data, a shared access secrete token, public or private keys, authentication certificates, a password, etc. The electronic data communication network 110 is also configured to establish a secure data link 112 with the passenger conveyor component 102. In this manner, the passenger conveyor component 102 can receive the configuration files corresponding to a selected device type, and automatically initiate commissioning as discussed in greater detail below.
The data communication network 110 includes a contract data uploading system 114, a data server 116, an application programming interface (API) 118, and an internet-of-things (IoT) inter-network 120. The contract data uploading system 114, data server 116, application programming interface (API) 118, and internet-of-things (IoT) inter-network 120 can each be installed in the cloud-based data communication network 110, but the invention is not limited thereto.
The contract data uploading system 114 is configured to receive contract data corresponding to a given passenger conveyor system 106. The contract data is used to generate at least one configuration file or a connection string for commissioning a passenger conveyor device to operate with a given passenger conveyor system. The contract data includes, but not limited to, a conveyor system type (e.g., elevator system, escalator system, moving walkway), performance data, and index data that maps the passenger conveyor system to one or more passenger system devices commissioned to operate with a given passenger conveyor system. Accordingly, the data server 116 can store the contract data obtained by the contract data uploading system and the configuration files.
The application programming interface (API) 118 is configured to operate as an abstraction layer that allows the passenger conveyor component 102 to perform different functions according to device type selected by the terminal device 108. In at least one embodiment, the API 118 is serves as an interface used by other systems/services (e.g. terminal device 108) to interact (e.g. transfer configuration data) with a specific component 102 or a group of components 102.
The IoT inter-network 120 is configured to establish a data link with the passenger conveyor component 102 after completing commissioning. The IoT inter-network 120 serves to establish data communication between the network controller 111 and a plurality of different passenger conveyor devices located remotely from one another. The IoT inter-network 120 also can facilitate test message based communication and data exchange between a commissioned passenger conveyor device and the data communication network 110.
The network controller 111 can be installed in the data communication network 110, or can be located remotely therefrom. In at least one non-limiting embodiment, the network controller 111 is configured to receive a device activation signal from the terminal device 108 indicating a request to commission a selected device type. The activation request signal can include the device identification (ID) information corresponding to the passenger conveyor component 102, and the device type selected by the maintenance technician located in the field (e.g., onsite 104 and in possession of the passenger conveyor component 102). In response to receiving the device activation signal, the network controller 111 operates to establish a secure data link 112 between the data communication network 110 and the passenger conveyor component 102. In this manner, the passenger conveyor component 102 receives configuration files corresponding to the selected device type via the secured data link 112, and an installs the configuration files to invoke operation as the selected device type.
Turning now to
At operation 2, a service technician selects the type of device of which to commission the non-configured passenger conveyer component 102. The device can be selected using a SVT APP installed on a terminal device 108 operated by the service technician.
At operation 3, the service technician obtains device ID information and a public key associated with the passenger conveyor component 102. The public key can include a unique device ID that is obtained by scanning an optical machine-readable label (e.g., QR code) included with the component 102. In at least one embodiment, the component 102 includes a display unit, which automatically displays the device ID information (e.g., QR code) once powered on. The terminal device 108 can also communicate wireless with the passenger conveyor component 102 to obtain the device ID information and a public key.
At operation 4, the terminal device 108 transmits an activation request signal to the data communication network 110. The activation request signal can contain the selected device type, device ID information, and a public key obtained by the terminal device 108. In at least one embodiment, the activation request signal is received by an API 118, which then relays the activation request signal to a network controller 111 configured to operate the data communication network 110. Once the activation signal is verified and approved by the data communication network (e.g., the network controller 111), a Globally Unique Identifier (GUID) is dynamically generated. The Globally Unique Identifier is assigned to each single 102 device for identification purposes.
At operation 5, a new device entry corresponding to the passenger conveyor component 102 is generated and stored in the network server 116. In addition, the network controller 111 can communicate with the IoT inter-network 120 to register the passenger conveyor component 102. Once registered, the IoT inter-network 120 generates a new connection string for the passenger conveyor component 102 and delivers the connection string to the network controller 111. The connection string can include, but is not limited to, configuration files, protocols, a shared access secrete token, public or private keys, authentication certificates, a password etc. At operation 6, the network controller 111 maps the network string (including the configuration files) to the passenger conveyor component 102. The mapping and/or the network string is then stored in the network server 106 for future reference at operation 7. Accordingly, verification of the passenger conveyor component 102 is completed at operation 8, and the passenger conveyor component 102 can proceed to communicate with the data communication network 110 to download and install the configuration files corresponding to the selected device type.
When the passenger conveyor component 102 is equipped with WiFi communication capability or Internet connection, the component 102 proceeds to operation 9a and wirelessly transmits a commission request signal that is received by the network controller 111 via the API 118. In at least one embodiment, the commission request signal includes the device ID information (e.g., the public key). The device ID information can also be encrypted with a network key initially installed on the component 102. At operation 9b, the network controller maps the received device ID information to the device entry data stored in network server to verify the commission request output by the passenger conveyor component 102. When the device ID information matches the device entry data, the network controller verifies the passenger conveyor component 102 and establishes a secure data link 112 between the data communication network 110 and the component 102. Once verified, the configuration file corresponding to the selected device type is transmitted to the component 102 via the secure data link 112. Upon completing installation of the configuration files, the passenger conveyor component 102 outputs an acknowledgment (ACK) signal indicating installation of the configuration files is complete, and the data communication network marks the passenger conveyor component 102 as being commissioned at operation 9c. Accordingly, the passenger conveyor component 102 can operate in the passenger conveyor system 106 according to the selected device type.
When the passenger conveyor component 102 is not equipped with WiFi communication capability or Internet connection, downloading of the configuration files is initiated using the terminal device 108 at operation 10a. In at least one embodiment, once verification of the passenger conveyor component 102 is completed at operation 8, the network controller 111 facilitates delivery of the network signed connection string (e.g. the connection string signed with an authenticated network certificate) from the data communication network 110 to the terminal device 108. The connection string can also be encrypted with the public key obtained from the passenger conveyor component 102 and include the configuration files corresponding to the device type selected at operation 2.
At operation 10b, the terminal device 108 relays the connection string (including the configuration files) to the passenger conveyor component 102. The connection string can be communicated either wirelessly (e.g., by Bluetooth) or through a wired connection using, for example, a USB connection between the passenger component 102 and the terminal device 108. Once the configuration files are installed, the passenger conveyor component 102 outputs an acknowledgment (ACK) signal indicating installation of the configuration files is complete. The terminal device 108 relays the ACK signal to the network controller 111 via the API 118, and the passenger conveyor component 102 is marked as being commissioned at operation 10d. Accordingly, the passenger conveyor component 102 can operate in the passenger conveyor system 106 according to the selected device type.
In at least one embodiment, the device commissioning system 100 can perform a connection verification test as shown in
As described herein, a device commissioning system is provided, which is capable of being executed “ad-hoc” to commission a non-configured passenger conveyor device (e.g., devices that are not installed with configuration files corresponding to a particular device type and/or passenger conveyor system) deployed in the field. Accordingly, the device commissioning system allows a non-configured passenger conveyor devices to be shipped generically with the possibility to be configured in the field for a range of applications or functions corresponding to a subsequently selected device type. The device commissioning system also allows passenger conveyor devices to be re-purposed or re-configured without being sent back to the producing entity compounds. The device commissioning system also facilitates replacement of a failed device with a functioning non-configured device which may have already been deployed into the field.
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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5929400 | Colby et al. | Jul 1999 | A |
| 6003637 | Kim | Dec 1999 | A |
| 6349795 | Tatsumi | Feb 2002 | B1 |
| 6427807 | Henneau | Aug 2002 | B1 |
| 6471014 | Daniel | Oct 2002 | B1 |
| 6624750 | Marman et al. | Sep 2003 | B1 |
| 7069333 | Morris | Jun 2006 | B1 |
| 7073633 | Weinberger et al. | Jul 2006 | B2 |
| 7319967 | Meyer | Jan 2008 | B2 |
| 7395122 | Kreidler | Jul 2008 | B2 |
| 7561581 | Kim et al. | Jul 2009 | B2 |
| 7636343 | Mizukoshi | Dec 2009 | B2 |
| 7697893 | Kossi et al. | Apr 2010 | B2 |
| 7853210 | Meyers et al. | Dec 2010 | B2 |
| 7933594 | Nixon | Apr 2011 | B2 |
| 8422401 | Choong | Apr 2013 | B1 |
| 8560012 | Ohnishi et al. | Oct 2013 | B2 |
| 8634821 | Raleigh | Jan 2014 | B2 |
| 8676219 | Pratt, Jr. et al. | Mar 2014 | B2 |
| 9077611 | Cordray | Jul 2015 | B2 |
| 9246757 | Balog et al. | Jan 2016 | B2 |
| 9253860 | Wang | Feb 2016 | B2 |
| 9483035 | Buchdunger et al. | Nov 2016 | B2 |
| 9485790 | Mathews et al. | Nov 2016 | B2 |
| 9571472 | Pochuev | Feb 2017 | B2 |
| 9588506 | Clayton | Mar 2017 | B1 |
| 9588514 | Christensen et al. | Mar 2017 | B2 |
| 9615434 | Vangeel et al. | Apr 2017 | B2 |
| 9647726 | Schultz | May 2017 | B2 |
| 9699270 | Kande et al. | Jul 2017 | B2 |
| 9787853 | Balakrishnan | Oct 2017 | B1 |
| 9860677 | Agerstam | Jan 2018 | B1 |
| 9912733 | T | Mar 2018 | B2 |
| 9967149 | Fiennes | May 2018 | B1 |
| 9984348 | Skaaksrud | May 2018 | B2 |
| 10168676 | Patel | Jan 2019 | B2 |
| 10336573 | Hovi | Jul 2019 | B2 |
| 10361867 | Ahokas | Jul 2019 | B2 |
| 20020173970 | Hamada | Nov 2002 | A1 |
| 20030040924 | Spoke, III | Feb 2003 | A1 |
| 20030057029 | Fujino | Mar 2003 | A1 |
| 20040028023 | Mandhyan et al. | Feb 2004 | A1 |
| 20040094366 | Weinberger | May 2004 | A1 |
| 20040174904 | Kim et al. | Sep 2004 | A1 |
| 20050061586 | Engel | Mar 2005 | A1 |
| 20060144646 | Engel | Jul 2006 | A1 |
| 20060159007 | Frutiger | Jul 2006 | A1 |
| 20070078956 | VanGompel | Apr 2007 | A1 |
| 20070110010 | Kotola | May 2007 | A1 |
| 20080208369 | Grgic | Aug 2008 | A1 |
| 20080274766 | Pratt et al. | Nov 2008 | A1 |
| 20090314583 | Pustelniak | Dec 2009 | A1 |
| 20100185549 | York | Jul 2010 | A1 |
| 20100217657 | Gazdzinski | Aug 2010 | A1 |
| 20110132699 | Tokura | Jun 2011 | A1 |
| 20110315490 | Shi | Dec 2011 | A1 |
| 20120008529 | Averbuch | Jan 2012 | A1 |
| 20120116574 | Kangas | May 2012 | A1 |
| 20130007693 | Bliss | Jan 2013 | A1 |
| 20130056311 | Salmikuukka | Mar 2013 | A1 |
| 20130211559 | Lawson | Aug 2013 | A1 |
| 20130223279 | Tinnakornsrisuphap | Aug 2013 | A1 |
| 20130246928 | Hovi | Sep 2013 | A1 |
| 20130291085 | Chong | Oct 2013 | A1 |
| 20130294285 | Zhang | Nov 2013 | A1 |
| 20140305747 | Kumar | Oct 2014 | A1 |
| 20140336785 | Asenjo | Nov 2014 | A1 |
| 20140336786 | Asenjo | Nov 2014 | A1 |
| 20140337429 | Asenjo | Nov 2014 | A1 |
| 20150045956 | Joyce | Feb 2015 | A1 |
| 20150046710 | Clish | Feb 2015 | A1 |
| 20150113592 | Curtis | Apr 2015 | A1 |
| 20150113599 | Curtis | Apr 2015 | A1 |
| 20150113627 | Curtis | Apr 2015 | A1 |
| 20150127174 | Quam | May 2015 | A1 |
| 20150134733 | Maturana | May 2015 | A1 |
| 20150154324 | Reilio | Jun 2015 | A1 |
| 20150158699 | Haapaniemi | Jun 2015 | A1 |
| 20150233790 | Ratilla et al. | Aug 2015 | A1 |
| 20150274488 | Ramakrishnan | Oct 2015 | A1 |
| 20150281319 | Maturana | Oct 2015 | A1 |
| 20150284214 | Park | Oct 2015 | A1 |
| 20150310674 | Humphrey | Oct 2015 | A1 |
| 20150317645 | Kudrimoti | Nov 2015 | A1 |
| 20150319552 | Yang | Nov 2015 | A1 |
| 20150365512 | MacKenzie | Dec 2015 | A1 |
| 20150369014 | Gray et al. | Dec 2015 | A1 |
| 20150371160 | Weatherhead et al. | Dec 2015 | A1 |
| 20160072808 | David | Mar 2016 | A1 |
| 20160099970 | Grodzicki | Apr 2016 | A1 |
| 20160104126 | Eleid | Apr 2016 | A1 |
| 20160107861 | Thebeau | Apr 2016 | A1 |
| 20160134686 | Youker | May 2016 | A1 |
| 20160171455 | Eleid | Jun 2016 | A1 |
| 20160195864 | Kim | Jul 2016 | A1 |
| 20160203407 | Sasaki | Jul 2016 | A1 |
| 20160259315 | Alexander | Sep 2016 | A1 |
| 20160270021 | Wu | Sep 2016 | A1 |
| 20160277391 | Choyi | Sep 2016 | A1 |
| 20160289043 | Fang et al. | Oct 2016 | A1 |
| 20160294819 | Salmela | Oct 2016 | A1 |
| 20160295196 | Finn et al. | Oct 2016 | A1 |
| 20160355375 | Simcik | Dec 2016 | A1 |
| 20160357176 | Chand | Dec 2016 | A1 |
| 20160376124 | Bunter | Dec 2016 | A1 |
| 20170006135 | Siebel | Jan 2017 | A1 |
| 20170008162 | Tsubota | Jan 2017 | A1 |
| 20170010099 | Simcik | Jan 2017 | A1 |
| 20170046024 | Dascola | Feb 2017 | A1 |
| 20170073187 | Youker | Mar 2017 | A1 |
| 20170076408 | D'Souza | Mar 2017 | A1 |
| 20170093815 | Chen | Mar 2017 | A1 |
| 20170098447 | Fu | Apr 2017 | A1 |
| 20170105129 | Teplin et al. | Apr 2017 | A1 |
| 20170171306 | Lucas et al. | Jun 2017 | A1 |
| 20170171359 | Ando | Jun 2017 | A1 |
| 20170201504 | Funk | Jul 2017 | A1 |
| 20170234566 | Gerszewski | Aug 2017 | A1 |
| 20170237576 | Gerszewski | Aug 2017 | A1 |
| 20170243417 | Manikantan Shila | Aug 2017 | A1 |
| 20170272316 | Johnson et al. | Sep 2017 | A1 |
| 20170285623 | Figoli | Oct 2017 | A1 |
| 20170289824 | Figoli | Oct 2017 | A1 |
| 20170291800 | Scoville | Oct 2017 | A1 |
| 20170297864 | Koivisto | Oct 2017 | A1 |
| 20170346802 | Gruskin | Nov 2017 | A1 |
| 20170355554 | Eleid | Dec 2017 | A1 |
| 20170357253 | Kilpatrick | Dec 2017 | A1 |
| 20180014144 | Chen | Jan 2018 | A1 |
| 20180022574 | Pasini | Jan 2018 | A1 |
| 20180024847 | Campbell | Jan 2018 | A1 |
| 20180083982 | Asenjo | Mar 2018 | A1 |
| 20180109929 | Ly | Apr 2018 | A1 |
| 20180118512 | Baldi | May 2018 | A1 |
| 20180121072 | Baldi | May 2018 | A1 |
| 20180123784 | Gehrmann | May 2018 | A1 |
| 20180150806 | Eleid | May 2018 | A1 |
| 20180157482 | Kirchhoff | Jun 2018 | A1 |
| 20180183882 | Flynn | Jun 2018 | A1 |
| 20180208430 | Koivisto | Jul 2018 | A1 |
| 20180215578 | Kusserow | Aug 2018 | A1 |
| 20180284735 | Celia | Oct 2018 | A1 |
| 20180293587 | Oda | Oct 2018 | A1 |
| 20180314512 | Schonauer | Nov 2018 | A1 |
| 20180373304 | Davis | Dec 2018 | A1 |
| 20180375680 | Wright | Dec 2018 | A1 |
| 20180375720 | Yang | Dec 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2812806 | Oct 2012 | CA |
| 102301738 | Dec 2011 | CN |
| 101909345 | Mar 2013 | CN |
| 104731078 | Jun 2015 | CN |
| 105684482 | Jun 2016 | CN |
| 2599260 | Jun 2014 | EP |
| 2010278553 | Dec 2010 | JP |
| 2011104807 | Sep 2011 | WO |
| 11154212 | Dec 2011 | WO |
| 2015056009 | Apr 2015 | WO |
| 2017063884 | Apr 2017 | WO |
| Entry |
|---|
| Chemical Processing, “Cloud-Based Configuration Offers Down-to-Earth Savings, by Amol Chaubal, Honeywell Process Solutions”, www.chemicalprocessing.com, 3 pages. |
| Larry O'Brien, Leveraging New Automation Approaches Across the Plant Lifecycle, Jun. 22, 2017, 5 pages. |
| Search Report for European Application No. 18203734.1; Application Filing Date Oct. 31, 2018; dated Jan. 8, 2019 (8 pages). |
| Office Action issued in European Application No. 18203734.1; Application Filing Date Oct. 31, 2018; dated Dec. 1, 2020 (8 pages). |
| First Office Action for Chinese Application No. 201811306067; filed Nov. 2, 2018; dated May 27, 2021 (16 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20190140896 A1 | May 2019 | US |
