Systems and Methods for Upgrading Controllers of a Building Management System

This application claims the benefit of Indian Provisional Application No. 202411064938, filed Aug. 28, 2024, which application is incorporated by reference herein.

The present disclosure relates generally to building management systems and more particularly to migrating a source controller to a target controller in a building management system.

Building Management Systems are systems that control and/or monitor one or more functions of a building or other facility. Building Management Systems may include, for example, an HVAC system, a security system, a video management system, an access control system, a fire system, and/or any other suitable Building Control System. Building Management Systems can include a large number of controllers. For example, an HVAC system may include a number of different controllers that operate various components within the HVAC system of various different zones. As another example, an access control system may include a number of different controllers. Over time, it may be desirable to upgrade existing controllers. Upgrading controllers can be a time consuming, tedious and error prone process. While controller upgrade tools exist, they are typically purpose-built, i.e., used to upgrade a particular component (e.g. particular component of a control application) of a particular type and particular model of a controller. What would be desirable are methods and systems for providing an upgrade tool framework for upgrading any of a variety of different types and models of controllers.

The present disclosure relates generally to building management systems and more particularly to upgrading controllers of a building management system. An example may be found in a method for migrating a source controller to a target controller of a BMS system, wherein the source controller runs a control application that includes a plurality of control application components. The illustrative method includes receiving a selection of the source controller and automatically detecting the plurality of control application components running on the source controller. A selection of the target controller is received. In some cases, the target controller may be the source controller. In other cases, the target controller may be a replacement controller. A selection of one or more of the control application components running on the source controller to migrate to the selected target controller is received. An application component migration strategy is automatically assembled for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration plugin from a plurality of predefined migration plugins of a migration plugin library for migrating the respective control application component from the selected source controller to the selected target controller. Each of the selected control application components running on the selected source controller are migrated from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy.

Another example may be found in a migration tool for migrating a source controller to a target controller of a Building Management System (BMS), wherein the source controller runs a control application that includes a plurality of control application components. The migration tool includes an input/output for communicating with the source controller and the target controller, a user interface, and a controller that is operatively coupled to the input/output and the user interface. The controller of the migration tool is configured to receive a selection via the user interface of the source controller and to receive via the input/output an identification of the plurality of control application components running on the source controller. The controller of the migration tool is configured to receive via the user interface a selection of the target controller and a selection of one or more of the control application components running on the source controller to migrate to the selected target controller. In some cases, the selected target controller may be the source controller. In other cases, the selected target controller may be a replacement controller. The controller of the migration tool is configured to assemble an application component migration strategy for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration plugin from a plurality of predefined migration plugins of a migration plugin library for migrating the respective control application component from the selected source controller to the selected target controller. The controller of the migration tool is configured to migrate each of the selected control application components running on the selected source controller from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy.

Another example may be found in a non-transitory computer readable medium storing instructions. When the instructions are executed by one or more processors, the one or more processors are caused to receive a selection via a user interface of a source controller of a Building Management System (BMS). The one or more processors are caused to receive an identification of one or more control application components running on the source controller. The one or more processors are caused to receive a selection of a target controller and to receive a selection of one or more of the control application components running on the source controller to migrate to the selected target controller. The one or more processors are caused to assemble an application component migration strategy for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration process for migrating the respective control application component from the selected source controller to the selected target controller. The one or more processors are caused to migrate each of the selected control application components running on the selected source controller from the selected source controller to the selected target controller in compliance with the respective application component migration strategy.

The preceding summary is provided to facilitate an understanding of some of the innovative features unique to the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, figures, and abstract as a whole.

While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the disclosure to the particular examples described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.

The following description should be read with reference to the drawings, in which like elements in different drawings are numbered in like fashion. The drawings, which are not necessarily to scale, depict examples that are not intended to limit the scope of the disclosure. Although examples are illustrated for the various elements, those skilled in the art will recognize that many of the examples provided have suitable alternatives that may be utilized.

1 5 All numbers are herein assumed to be modified by the term “about”, unless the content clearly dictates otherwise. The recitation of numerical ranges by endpoints includes all numbers subsumed within that range (e.g.,toincludes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).

As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include the plural referents unless the content clearly dictates otherwise. As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/of” unless the content clearly dictates otherwise.

It is noted that references in the specification to “an embodiment”, “some embodiments”, “other embodiments”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is contemplated that the feature, structure, or characteristic may be applied to other embodiments whether or not explicitly described unless clearly stated to the contrary.

1 FIG. 10 10 10 12 14 12 14 12 14 12 14 12 12 12 12 14 14 12 12 14 is a schematic block diagram of an illustrative system. The systemmay be considered as being part of a Building Management System (BMS), for example. The systemmay be considered as including a source controllerand a target controllerof a BMS. While a single source controlleris shown, it will be appreciated that a BMS may include a large number of source controllers. As shown, the target controlleris distinct from the source controller. In some cases, the target controllermay be a newer version of the source controller. In some cases, the target controllermay be the same model as the source controller, particularly if the source controlleris being replaced due to one or more flaws within the source controllerrather than replacing the source controllerwith the target controllerbecause the target controllerhas additional features or capabilities not included in the source controller. In some cases, a source controllerand the target controllermay be the same controller, particularly when only software components within the controller are being updated.

12 16 16 16 12 14 16 12 14 16 12 14 16 12 14 In the example shown, the source controllerincludes control application components. The control application componentsmay include various software programs, for example. In some cases, the control application componentsmay be configured by one or more configuration settings that can be updated or migrated from the source controllerto the target controller. The configuration settings may include, for example, equipment settings, setpoint settings, network settings, Bluetooth settings, connected device specifics, IO terminal details, device information, point data, and/or any other suitable configuration information. In some cases, the control application componentsmay collect and store respective support data and/or log information that can also be migrated from the source controllerto the target controller. As an example, the support data and/or log information may include current and/or historical data. As another example, the support data and/or log information may include current and/or historical alarm data and/or sensor data. In some cases, the control application componentson the source controllermay be a first version which will be updated to a second updated version on the target controller. The control application componentsmay include control points that are migrated from the source controllerto the target controller. These are just examples.

18 20 16 12 14 18 22 12 14 24 26 22 24 20 28 28 28 28 28 28 20 28 28 26 24 26 12 26 22 16 12 26 24 14 16 12 14 a b c d e a A migration toolmay be used, in conjunction with a plugin library, to migrate control application componentsof the source controllerto the target controller. The illustrative migration toolincludes an input/outputfor communicating with the source controllerand the target controllerand a user interface. A controlleris operatively coupled to the input/outputand to the user interface. The plugin libraryincludes a variety of migration plugins, individually labeled as,,,and. The plugin librarymay include any number of migration plugins, and may include considerably more than five migration plugins, for example. The controlleris configured to receive a selection via the user interfaceof the source controller. A user may tell the controllerwhich of the various source controllers they wish to upgrade and/or replace, thus selecting the particular source controller. The controllerreceives via the input/outputan identification of the control application componentsthat are running on the source controller. The controllerreceives via the user interfaceselection of the target controlleras well as a selection of which of the control application componentsthat are running on the source controllershould be updated and/or migrated to the target controller.

26 16 12 28 28 20 16 12 14 20 28 26 16 12 12 14 28 26 16 12 12 14 28 The controlleris configured to assemble an application component migration strategy for each of the selected control application componentsrunning on the selected source controller, wherein the respective application component migration strategy identifies a migration pluginfrom the plurality of predefined migration pluginsof the migration plugin libraryfor migrating the respective control application componentfrom the selected source controllerto the selected target controller. In some cases, the migration plugin librarymay include predefined migration pluginsthat are programmed for each combination of source controller, target controller and control application component. The controlleris configured to migrate each of the selected control application componentsrunning on the selected source controllerfrom the selected source controllerto the selected target controllerusing the respective migration pluginidentified in the respective application component migration strategy. In some cases, the controllermay be configured to migrate each of the selected control application componentsrunning on the selected source controllerfrom the selected source controllerto the selected target controllerusing the respective migration pluginidentified in the respective application component migration strategy without taking offline, stopping, rebooting or otherwise interrupting the operation of the Building Management System (BMS).

16 26 18 16 12 22 12 14 28 16 In some cases, one or more of the plurality of control application componentsmay be configured by one or more configuration settings, and wherein the controllerof the migration toolmay be configured to collect configuration settings associated with each of the control application componentsrunning on the source controllervia the input/output. Migrating each of the selected control application components from the selected source controllerto the selected target controllerusing the respective migration pluginidentified in the respective application component migration strategy may include migrating the configuration settings associated with the respective control application component.

16 26 18 16 12 16 12 14 28 16 In some cases, one or more of the plurality of control application componentsmay collect and store respective support data and/or log information, and the controllerof the migration toolmay be configured to collect support data and/or log information associated with each of the control application componentsrunning on the source controller. Migrating each of the selected control application componentsfrom the selected source controllerto the selected target controllerusing the respective migration pluginidentified in the respective application component migration strategy may include migrating the support data and/or log information associated with the respective control application component.

2 FIG. 1 FIG. 1 FIG. 30 30 10 30 10 30 32 34 36 34 36 32 16 34 36 34 36 34 36 32 34 36 34 36 34 36 38 18 38 40 42 a a b b a a b b is a schematic block diagram of an illustrative system. In some cases, the systemmay be considered as being an example of the system. In some cases, the systemmay be considered as being incorporated within the system. The systemincludes a source controllerthat has a control application componentand a control application component. Each of the control application componentand the control application componentof the source controllermay represent examples of the control application componentsof. As can be seen, each of the control application componentsandinclude a metadata provision interfaceand, respectively, and a config information provision interfaceand, respectively. These are preprogrammed interfaces that were previously installed on the source controller. The control application componentsandcommunicate via the metadata provision interfacesandand the config information provisional interfacesandwith a component migrate analysis blockof a migration tool, such as migration toolof. The component migrate analysis blockoutputs a component migrate strategyand a common migrate frameworkto support the migration.

44 44 44 44 42 46 46 46 46 46 46 42 48 50 48 50 50 50 50 50 48 52 54 56 a b c a b c d a b c d e The component migrate strategy may include a number of migrate strategy descriptions, individually labeled as,and. The common migrate frameworkmay include a number of elementsincluding, for example, a component migrate page loader, a common migrate page, a migrate logand a backup and recovery, some or all of which are tailored to the particular migration at hand. Other elementsmay also be included. The common migrate frameworkmay communicate with a migrate plugin libraryincluding a number of components. The migrate plugin librarymay include a component migrate page, a component migrate executor, a package migration plugin, a data migration pluginand a config migration plugin. In some cases, the migrate plugin librarymay include a parameter load interface, a parameter save interfaceand a migrate interface.

3 FIG. 58 30 38 32 38 34 36 32 38 34 36 32 38 38 42 42 60 a a b b provides a workflowshowing how the illustrative systemfunctions. At step zero (0), the component migrate analysis blocksolicits and receives a listing of all of the components within the source controller. At step one (1), the component migrate analysis blocksolicits and receives the metadata via the metadata provision interfacesandfor each of the listed components within the source controller. At step two (2), the component migrate analysis blocksolicits and receives the config data via the config information provision interfacesandfor each of the listed components within the controller. At step three (3), a master component strategy description file is parsed to extract component strategy elements that are relevant to the migration of the listed components within the source controller, and assembly and provide a migration strategy description to the component migrate analysis block. At step four (4), a migrate analysis page that is based on the migration strategy description is generated and provided by the component migrate analysis blockto a common migrate framework. At step five (5), the user selects which components are to be migrated. At step six (6), the user selects the source controller and the target controller. At step seven (7), a component migrate page is loaded and returned to the common migrate framework. At step eight (8), a migrate interface is called and migration occurs. At step nine (9), a migrate logis saved.

4 4 4 FIGS.A,B andC 62 12 14 16 62 64 66 68 70 28 20 72 are flow diagrams that together show an illustrative methodfor migrating a source controller (such as the source controller) to a target controller (such as the target controller) of a BMS system, wherein the source controller runs a control application that includes a plurality of control application components (such as the control application components). The methodincludes receiving a selection of the source controller, as indicated at block. The plurality of control application components running on the source controller are detected, as indicated at block. A selection of the target controller is received, as indicated at block. A selection of one or more of the control application components running on the source controller to migrate to the selected target controller is received, as indicated at block. An application component migration strategy is automatically assembled for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration plugin from a plurality of predefined migration plugins (such as the migration plugins) of a migration plugin library (such as the plugin library) for migrating the respective control application component from the selected source controller to the selected target controller, as indicated at block.

74 In some cases, assembling the application component migration strategy for each of the selected control application components running on the selected source controller may include extracting the application component migration strategy for each of the selected control application components from a master component migration strategy source or file. In some cases, extracting the application component migration strategy may include parsing the master component migration strategy source to identify and extract one or more parts of the master component migration strategy source based at least in part on one or more of the selected control application component, the selected source controller, and/or the selected target controller. In some cases, the selected control application component running on the selected source controller has a first version, and the selected control application component to be migrated to the selected target controller has a second version that is different from the first version. Parsing the master component migration strategy source to include one or more parts of the master component migration strategy source may be based at least in part on the first version of the selected control application component running on the selected source controller and the second version of the selected control application component to be migrated to the selected target controller. Each of the selected control application components running on the selected source controller are migrated from the selected source controller to the selected target controller using a respective migration plugin identified in the respective application component migration strategy, as indicated at block.

62 76 34 78 b In some cases, one or more of the plurality of control application components may be configured by one or more configuration settings and the methodmay include collecting configuration settings associated with each of the control application components running on the source controller, as indicated at block. The configuration settings may be collected via the configuration information provision interfaceassociated with the respective control application components. Migrating each of the selected control application components from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy may include migrating the configuration settings that is associated with the respective control application component, as indicated at block.

62 80 34 82 b 4 FIG.B In some cases, one or more of the plurality of control application components may collect and share respective support data and/or log information, and the methodmay include collecting support data and/or log information associated with each of the control application components running on the source controller, as indicated at block. In some cases, the support data and/or log information may include current and/or historical data. In some cases, the support data and/or log information may include alarm data and/or sensor data, for example. The support data and/or log information may be collected via the configuration information provision interfacethat is associated with the respective control application components. Migrating each of the selected control application components from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy may include migrating the support data and/or log information associated with the respective control application component, as indicated at blockon.

62 84 86 In some cases, each of the selected one or more of the control application components running on the source controller may include one or more control points, and the methodmay include receiving a selection of one or more additional points to add to a selected one of the control application components that are to be migrated to the selected target controller, as indicated at block. In some cases, the selected target controller or the upgraded control application component may allow use of additional control points. The selected one or more additional points may be added to the selected control application component during the migration of the selected control application component from the selected source controller to the selected target controller, as indicated at block.

62 88 In some cases, each of the selected one or more of the control application components running on the source controller may include one or more control points that are mapped to a corresponding terminal of the source controller, and the methodmay include receiving a mapping of one or more of the control points of a selected one of the control application components to a selected terminal of the target controller, as indicated at block. The mapping may be used during the migration of the selected control application component from the selected source controller to the selected target controller.

In some cases, the application component migration strategy for each of the selected control application components running on the selected source controller may include a human readable description of one or more steps of the migration strategy of the respective control application component from the selected source controller to the selected target controller. In some cases, the migration plugin identified by the respective application component migration strategy may automatically perform one or more of the steps of the migration of the respective control application component from the selected source controller to the selected target controller. In some cases, one or more of the steps of the migration of the respective control application component from the selected source controller to the selected target controller may need to be performed manually, such as rebooting the target controller during the migration.

90 90 90 90 90 a b c d In some cases, one or more steps of the migration of the respective control application component may be automatically carried out by the migration plugin, as indicated at block. The one or more steps may include migrating one or more configuration settings from the selected source controller to the selected target controller, as indicated at block. The one or more steps may include migrating support data and/or log information from the selected source controller to the selected target controller, as indicated at block. The one or more steps may include migrating schedule information from the selected source controller to the selected target controller, as indicated at block. The one or more steps may include migrating one or more Fast Access List (FAL) entries from the selected source controller to the selected target controller, as indicated at block. These are just examples.

4 FIG.C 62 92 94 In some cases, and continuing on, the methodmay include determining that one or more components running on the source controller that have an upgrade available, as indicated at block. One or more component upgrade suggestions may be provided to a user via a user interface, as indicated at block. The one or more component upgrade suggestions may be provided to the user when the user is selecting the components to upgrade.

5 5 FIGS.A andB 96 26 98 100 102 104 106 108 are flow diagrams that together show an illustrative series of stepsthat may be carried out by one or more processors that are executing instructions that are stored on a non-transitory computer-readable storage medium. The one or more processors may be part of the controller, for example. The one or more processors may be caused to receive a selection via a user interface of a source controller of a Building Management System (BMS), as indicated at block. The one or more processors may be caused to receive an identification of one or more control application components running on the selected source controller, as indicated at block. The one or more processors may be caused to receive a selection of a target controller, as indicated at block. The one or more processors may be caused to receive a selection of one or more of the control application components running on the selected source controller to migrate to the selected target controller, as indicated at block. The one or more processors may be caused to assemble an application component migration strategy for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration process for migrating the respective control application component from the selected source controller to the selected target controller, as indicated at block. The one or more processors may be caused to migrate each of the selected control application components running on the selected source controller from the selected source controller to the selected target controller in compliance with the respective application component migration strategy, as indicated at block.

110 112 114 116 5 FIG.B In some cases, the one or more processors may be caused to automatically collect configuration settings associated with each of the control application components running on the source controller, as indicated at block. The one or more processors may be caused to migrate the configuration settings associated with the respective control application component from the selected source controller to the selected target controller, as indicated at blockon. The one or more processors may be caused to automatically collect support data and/or log information associated with each of the control application components running on the source controller, as indicated at block. The one or more processors may be caused to migrate the support data and/or log information associated with the respective control application component from the selected source controller to the selected target controller, as indicated at block.

6 13 FIGS.through 6 FIG. 118 118 24 18 120 122 124 120 126 128 130 118 provide an example of an Human Machine Interface (HMI) Network control application component migration from version 1.0 to version 2.0. In this example, the source controller and the target controller may correspond to the same physical device, but this is not required. In, a screenis shown that shows a listing of all of the control application components of a source controller that may be upgraded, and allows a user to select which of the control application components are to be upgraded. The screenmay be displayed on the user interfaceof the migration tool, for example. As shown, there is an HMI (Human Machine Interface) Network control application component, a PanelBus Network control application componentand an OnboardIO Network control application component. The HMI Network control application componenthas been selected, as indicated by a checkmark. A Next buttonand a Cancel buttonallow the user to navigate through multiple screens, as desired. In this example, the screen or pageis tailored to include the control application components running on the particular source controller.

7 FIG. 132 134 136 138 34 36 134 140 34 36 a a b b. provides an illustrative block diagramshowing that an HMI Network control application component blockprovides metadatavia a metadata interface(similar to the metadata provision interfacesand). The HMI Network control application component blockprovides config data via a config data interface(similar to the config data provision interfacesand

8 FIG. 6 FIG. 144 128 144 24 18 144 146 144 148 150 152 146 150 provides a screen or pagethat may be displayed in response to the user selecting the Next buttonin. The screenmay be displayed on the user interfaceof the migration tool, for example. The screenincludes informationthat describes the HMI network control application component, including identifying current and target versions, upgrade features and upgrade notes. The screenalso includes a Previous button, a Next buttonand a Cancel buttonthat may be used by the user to navigate through multiple screens, as desired. After confirming the information, the user may select the Next button, and a migrate strategy is automatically generated.

9 FIG. 154 154 24 18 provides a screenthat includes a migrate strategy description that informs the user of the automatically generated migration strategy. The screenmay be displayed on the user interfaceof the migration tool, for example. In some cases, the automatically generated migration strategy may include one or more steps that to be performed manually by the user (e.g. restart the target controller when instructed).

10 FIG. 11 FIG.A 156 156 24 18 156 158 158 160 156 162 162 18 24 164 a provides a screenthat includes migration information. The screenmay be displayed on the user interfaceof the migration tool, for example. The screenincludes a listingof controllers. The user is able to select one controller or multiple controllers from the listingby clicking on the desired controllers to upgrade. A sectionincludes a listing of configuration items. Some of the configuration items may be enabled or disabled, depending on which controllers were selected. The screenincludes a Manage Additional Points button. Selecting the Manage Additional Points buttonallows for additional points to be managed, and will cause the migration toolto display on the user interfacescreen, such as shown in.

164 166 168 164 170 172 170 18 174 174 176 178 180 11 FIG.B The screenincludes a listing of controllersand a listingof available points for the selected controller. In some cases, the selected target controller or the upgraded control application component may allow use of additional control points. As shown, a controller named Demo1 has been selected. The screenincludes an Add buttonthat may be used to add additional points and a Remove buttonthat may be used to remove one or more points. Clicking the Add buttonwill cause the migration toolto display a screenas shown in. The screenincludes a listingof points that may be added. A Save buttonallows the user to save the added points, and a Close buttonallows the user to revert to a previous screen.

12 FIG. 12 FIG. 12 FIG. 12 FIG. 182 184 184 184 186 188 190 192 188 194 194 192 196 196 198 196 200 provides a screenon the left hand side ofthat provides a summaryfor the proposed migration. The user is able to confirm the details within the summarybefore initiating the actual migration (e.g. before the actual copying of files, settings and/or other information to the target controller). The screenincludes a Previous button, a Migrate button, a Close buttonand a Show Log button. Selecting the Migrate buttoncauses a screento be displayed, as shown in the middle of. The screenprovides a progress bar for the migration. Alternatively, selecting the Show Log buttoncauses a screento be displayed, as shown on the right hand side of. The screenincludes a migration messageinforming the user of the results of the attempted migration. In this particular case, the migration failed. The screenincludes a Close buttonthat allows the user to return to a previous screen.

13 FIG. 202 202 204 42 206 208 210 212 214 216 210 212 214 216 is a block diagram showing an illustrative summationof an HMI control application component migration. The summationincludes an HMI Network control application component migrate executor in pluginthat carries out and controls the migration. In some cases, the common migrate frameworkmay call the migrate interface provided by the HMI MigrateTool plugin. This includes copying packages, as indicated at block, migrating the device configuration as indicated at block, migrating point data as indicated at block, migrating schedule data as indicated at block, migrating FAL data as indicated at blockand migrating alarm data as indicated at block. In some cases, the blocks,,andmay be involved in migrating from an existing BACnet network to an HMI network.

14 FIG. 14 FIG. 14 FIG. 218 220 222 224 provides an example of IO terminal mapping screen or page for mapping terminals between a first device and a second replacement device.includes a listingof available devices to add. A sectionallows the user to select between displaying a device1 and a device2, with perhaps device1 representing the original device and device2 representing the replacement device. As shown, device1 is selected, soincludes a graphical representationof device1. The graphical representation includes a listingof available terminals. The user is able to change the control point that assigned to a particular terminal of the device via a drop down box. The drop down box displays a listing of control points that are compatible with the particular terminal. For example, for an analog input terminal, the corresponding drop down box may only allow selection of control points that are compatible with the analog input terminal type.

Having thus described several illustrative embodiments of the present disclosure, those of skill in the art will readily appreciate that yet other embodiments may be made and used within the scope of the claims hereto attached. It will be understood, however, that this disclosure is, in many respects, only illustrative. Changes may be made in details, particularly in matters of shape, size, arrangement of parts, and exclusion and order of steps, without exceeding the scope of the disclosure. The disclosure's scope is, of course, defined in the language in which the appended claims are expressed.