The claimed subject matter relates generally to industrial control systems and more particularly to control of power and energy that enables efficient and automated management of the same across various communications networks.
Various industrial protocols are employed to support automated manufacturing operations and communications. These can include device protocols, mid-level protocols between the device level and the control level, and upper-level protocols such as Ethernet that has been adapted to communicate via industrial control objects among factories and on to high-level networks such as the Internet. In one specific example of such an industrial protocol, the Common Industrial Protocol (CIP™) encompasses a comprehensive suite of attributes, messages and services, organized as objects, for the enablement of manufacturing automation application objectives—control, safety, synchronization, motion, configuration and information collection. Further, it enables users to integrate these manufacturing applications with enterprise-level Ethernet networks and the Internet. Supported by hundreds of vendors around the world, CIP provides users with a unified communication architecture throughout the manufacturing enterprise. The CIP protocol allows users to benefit today from the many advantages of open networks while protecting their existing automation investments when upgrading in the future.
Through the addition of functionally specialized objects, the CIP protocol provides a coherent integration of control, motion and synchronization, configuration and diagnostics, and safety information. This protocol includes seamless bridging and routing without the added cost and complexity of bridges and proxies. Further, the protocol provides freedom to deploy interoperable, multivendor systems, allowing users to choose best-of-breed products, with the assurance of competitive prices and low integration cost. This includes single, media independent protocol for all network adaptations of CIP—EtherNet/IP™, DeviceNet™, CompoNet™, and ControlNet™—that allows users to select the best network or networks for their application while still minimizing their overall investment in system engineering, installation, integration and commissioning. The CIP protocol also integrates support of Modbus® server devices into the CIP architectures with Modbus translation services for originator devices on CIP; allows devices supporting Modbus TCP and EtherNet/IP to reside on the same TCP/IP network—or even in the same device. Modbus integration is accomplished by the usage of objects to create an abstraction. Modbus is then accessed as if the Modbus devices were native CIP devices. It should be recognized that the functionality provided by a CIP object can be extended into other non-CIP networks in a similar manner.
A key topic that has gained prominence in modern industrial manufacturing is the ability to efficiently manage power and energy within a plant or across a set of plants and an associated supply chain, where such management spans a wide geography and communicates over networks. This includes the ability to understand and track in real time, where energy is being generated, transmitted, distributed and utilized. For instance, Cap and Trade policies may have to be considered in the management of a particular plant or even across broader energy domains that may be associated with a grid. Some of the energy management must be coordinated with the grid such as the ability to receive energy from the grid or conversely return unused energy back to the grid for appropriate credit. Unfortunately, existing industrial protocols do not support a standardized ability to aggregate energy data or manage energy resources let alone communicate or facilitate control in even the most basic energy demand applications. Presently, the difficulty in automation due to the lack of uniform methods of energy management information exchange leads most often to a manual exercise that is far from an efficient and responsive method for controlling and managing complex energy flows that dynamically change over time.
The following summary presents a simplified overview to provide a basic understanding of certain aspects described herein. This summary is not an extensive overview nor is it intended to identify critical elements or delineate the scope of the aspects described herein. The sole purpose of this summary is to present some features in a simplified form as a prelude to a more detailed description presented later.
An energy object is provided that enables energy in all its forms to be managed automatically across industrial communication networks. The energy object includes the ability to aggregate energy data from various point sources that may originate within a plant or more broadly across networks external to the plant that define an energy domain. This can include control devices that report energy that has been discretely taken from or added to a grid such as a smart grid that credits users for efficient energy use and transfer with the respective grid. By automatically collating energy data within an industrial protocol via the energy object and discrete energy monitoring sources, energy can be efficiently managed by associating its use to the actual production of products or services that consume the energy or conversely produce it. By having discrete control and understanding of energy in its smallest or discrete form from numerous network locations, energy can be controlled dynamically as a commodity to best serve various applications. Obvious applications include energy conservation where non-necessary components are idled or previously used processes are employed to return unused energy to an external or internal grid. More complex applications such as Cap & Trade and automated demand response (ADR) can easily employ energy objects as a control mechanism (e.g., turn off or on an energy source) or as a collection mechanism to determine and demonstrate that the energy users are in compliance.
In one aspect, the energy object can include an identifier having a device name, a qualified hierarchy, and an object class for associating a process with an energy source. The object can specify the type of energy consumed such as water, air, gas, electricity and steam (WAGES), for example. This can include measurements, some type of aggregation, and some type of time reference among other parameters. Water, for example, can be used to move materials and provide heating and cooling. Also, considering provision by utilities and climate and geography related usage limitations, it should be apparent that it is reasonable to manage water in an analogous manner as electricity. In another aspect, an energy object extension to an industrial protocol having a comprehensive suite of attributes, messages and services utilized for the monitoring and control of energy consuming or producing resources by a manufacturing automation application is provided. The energy object includes an identifier associated with an energy resource that is associated with a manufacturing automation application and an energy type associated with the energy resource. This includes a measurement characteristic associated with the energy resource to facilitate energy management by the manufacturing automation application.
To the accomplishment of the foregoing and related ends, the following description and annexed drawings set forth in detail certain illustrative aspects. These aspects are indicative of but a few of the various ways in which the principles described herein may be employed. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings.
An energy object extension to an industrial protocol having a comprehensive suite of attributes, messages and services utilized for the monitoring and control of energy consuming or producing resources by a manufacturing automation application is provided. The energy object includes an identifier associated with an energy resource that is associated with a manufacturing automation application and an energy type associated with the energy resource. This includes a measurement characteristic associated with the energy resource to facilitate energy management by the manufacturing automation application.
Referring initially to
A basic communication protocol may be extended by layering an industrial communication protocol on top of the basic communication protocol. For example, Ethernet is extended for industrial control purposes by layering the Common Industrial Protocol (CIP) on top of the Internet Protocol (IP) and this on top of Ethernet. Thus, CIP provides a method to interact with the energy object that is independent of the underlying communication protocols. As shown, higher level energy management systems and software 140 can employ the CIP protocol to interact with the energy objects 130 in order to facilitate overall energy control/management of a factory or participate across a network and associated grid with a collection of factories or processes. It should be appreciated that energy objects 130 may reside in controller 120 or more commonly in separate intelligent field devices 122 linked to the controller. The CIP protocol provides transparent access in either case.
In general, the energy objects 130 enable energy in all its forms to be managed automatically across industrial communication networks. The energy object 130 includes the ability to aggregate energy data from various point sources 110 that may originate within a plant or more broadly across networks external to the plant that define an energy domain. This can include control devices 120 that report energy that has been discretely taken from or added to a grid such as a smart grid (not shown) that credits users for efficient energy use and transfer with the respective grid. By automatically collating energy data within an industrial protocol via the energy object 130 and discrete energy monitoring sources 120, energy can be efficiently managed by associating its use to the actual production products or services that consume the energy or conversely produce it. By having discrete control and understanding of energy in its smallest or discrete form from numerous distributed network locations, energy can be controlled dynamically as a commodity to best serve various applications. Obvious applications include energy conservation where non-necessary components are idled or previously used processes are employed to return unused energy to the grid. More complex applications such as Cap & Trade can easily be controlled and monitored via the energy objects 130 that can also be employed as a control mechanism (e.g., turn off or on an energy source) or employed as a reporting device to show companies are in compliance.
In one aspect, the energy object 130 can include an identifier having a device name, a qualified hierarchy, and an object class for associating a process with an energy source. The energy object 130 can specify the type of energy consumed such as water, air, gas, electricity and steam, for example. This can include measurements, some type of aggregation, and some type of time reference among other parameters. In one aspect, an energy object extension to an industrial protocol is provided having a comprehensive suite of attributes, messages and services for the collection of manufacturing automation applications. The energy object 130 includes an identifier associated with an energy consuming or producing resource in a manufacturing automation application and an energy type associated with the energy resource. This energy object also includes a measurement characteristic associated with the energy type among other parameters described below with respect to
The energy objects 130 enable various aspects of control and monitoring. In one aspect, automated demand response (ADR) programs can be enabled. This allows consumers to automatically reduce usage to reduce peak grid load at utility request or at specific times while addressing energy generation limits, transmission limits, and failures. Demand/response can include reducing the base load, sequencing start-up, and shedding non-critical loads. This also includes generating power, storing energy for later usage, staggering power peaks, and operating at a reduced rate/capacity, for example.
The energy objects can be employed in conjunction with a Smart Grid to request/demand to reduce or produce energy, bid exchange for reducing or producing energy, control immediate needs or future consumption (e.g., day ahead event scheduling), or utility measurement enforcement and settlement. Within the confines of the plant, automated measurements determine usage which can be employed to reduce lower production rates, re-schedule production, or shed loads, for example. Energy production can include re-use for the factory, supplying energy to the grid, and receiving credits for excess power supplied to the grid.
Energy can be controlled via the energy objects 130 within the constraints of existing safety control systems. Events should be a request at the machine/cell, not a direct load control. Immediate shutdown of a load, without the proper prerequisite steps, may not be safe. Current event triggered load shedding may be able to occur with a delay to allow safe state controls. Future event load shedding can be scheduled to accommodate safety time. It is also noted that energy can be managed, controlled, and computed in substantially any form. This includes measurements that relate to energy (e.g., joules), voltage, current (real and reactive), power (e.g., joules/sec, volt*amps), fluid flows, pressure, temperature, and substantially any parameter or measurement that has some relationship to energy or power.
The energy objects 130 can also be employed to manage billing for usage including charging for the total kWh over a billing period. This may be tiered in rate, changed by season, changed by time of day (on/off peak), and so forth. Electrical peak demand charges can include automated charging/billing for the highest average kW usage during any single demand interval in the billing cycle. Demand intervals can include subdivision of the billing cycle during which peak demand is measured. Intervals are typically a 15 or 30 minute period but other periods can be employed. Intervals may be “rolling” or fixed to a time reference. Ratchet clauses can be supported that include increased peak demand charges in subsequent billing cycles due to a high peak demand in a prior billing cycle. Reactive demand charges include usage at non-unity power factor. The energy objects can also be employed with a safety component (e.g., safety PLC to control switching to different energy states) that limits activation, deactivation or modulation of an energy consuming or producing resource.
In one example application of the system 100, a manufacturing automation system for monitoring Cap and Trade emissions across multiple devices communicating within an industrial process can be provided. This includes a set of objects having identifiers associated with a number of emitting resources, an emission type, and a monitoring component to facilitate measurement and recording of emissions from the resources within the industrial process. This also includes a controller having an emission cap parameter set within a memory of the controller, where the controller processes the energy object. The system includes an accumulation function operating with the controller and operatively communicating with the object to accumulate the emissions from the resources and calculate a total emission, compare with the cap parameter, and provide notification for a trade if the cap is determined to be increased. The manufacturing automation system can also include a component to increase the cap parameter by communication from the controller to an external source that facilitates the trade.
In another aspect various forecasting applications can be supported. A historian type application can estimate a forward-looking forecast of energy use and demand based on a combination of energy data collected through the energy object, historical production, environmental and other related data, production schedules, weather forecasts, and so forth. The forecast could be set up as one hour, one day, one week, one month ahead (with higher confidence factors the shorter the forecast period), and could be communicated through a “Smart Grid” portal to energy providers to assist them in planning and controlling supply and hopefully passing along resulting efficiencies in the form of lower energy costs.
It is noted that components associated with the system 100 and controllers 120 can include various computer or network components such as servers, clients, controllers, industrial controllers, programmable logic controllers (PLCs), electric drives, energy monitors, batch controllers or servers, distributed control systems (DCS), communications modules, mobile computers, wireless components, control components and so forth that are capable of interacting across a network. Similarly, the term controller or PLC as used herein can include functionality that can be shared across multiple components, systems, or networks. For example, one or more controllers can communicate and cooperate with various network devices across the network. This can include substantially any type of control, communications module, computer, I/O device, sensors, Human Machine Interface (HMI) that communicate via the network that includes control, automation, or public networks. The controller can also communicate to and control various other devices such as Input/Output modules including Analog, Digital, Programmed/Intelligent I/O modules, other programmable controllers, communications modules, sensors, output devices, and the like. It is further noted that the industrial automation as described here in can include substantially any type of manufacturing automation that further includes all process and discrete manufacturing, as well as building maintenance, for example.
The network can include public networks such as the Internet, Intranets, and automation networks such as Control and Information Protocol (CIP) networks including DeviceNet and ControlNet. Other networks include Ethernet, DH/DH+, Remote I/O, Fieldbus, Modbus, Profibus, wireless networks, serial protocols, and so forth. In addition, the network devices can include various possibilities (hardware or software components). These include components such as switches with virtual local area network (VLAN) capability, LANs, WANs, proxies, gateways, routers, firewalls, virtual private network (VPN) devices, servers, clients, computers, configuration tools, monitoring tools, or other devices.
Turning now to
The energy objects 230 provide power and energy management extensions for devices in the system 200 and for processes controlled by respective devices. This enables manipulating discrete power modes, measuring total energy, and measuring demand (real and reactive), and provide alarm and event messages on energy or power conditions. This also includes optional generation control and optional diagnostic measurements that includes per phase and phase to phase currents and voltages in addition to trending, for example.
At 354, a Time reference parameter includes a time and date of the object (r/w attribute). At 360 a Data log parameter can be provided to store a set of measurements over a time period. At 364 a Priority parameter includes Opt-out, critical, non-critical (Grid categories) and Load shedding (Load-related) to assist in decision making in control of the energy resource. At 370, a Shed and Produce Services set includes a request operation state change estimation, a response indicates time to change operational state, and an actual request to change state. At 374, a CIP A&E (alarms & events) message set includes alarm on energy production below measured level (average or instantaneous) and alarm on energy consumption above a measured level. As can be appreciated more or less parameters, services, or alarm and event messages than shown in
Referring to
Referring to
It is noted that power quality load (phase) balancing applications can utilize an energy object in communicating power quality information and sending out alerts of fault conditions so that an energy consumer (e.g., drives and rectifiers) can change their operating point to control power factor, or phase imbalance at the point of common coupling. For instance, a non-electrical example, in an air system, a second compressor could be signaled to turn on in the event of a leak, or primary compressor failure. Thus, metering devices can be employed that can collect and trigger events. The events can be used by the energy object to change the operating point of the device (e.g., drive) in other ways than to reduce energy consumption (power factor, phase imbalance). This communication can be direct from device to device to facilitate fastest action. In some applications, communication is performed from the device monitoring energy, reporting to a controller. In other applications however, messages can be sent from device to device (rather than through a controller) when it is advantageous to do so. It is also noted that when consumable resources are measured, they can be included in the scope of the CIP energy object to provide enhanced forecasting. For example, measuring the solar intensity water temperature, fuel oil levels or wind speed in addition to the electrical power can be helpful in forecasting energy usage.
Proceeding to 1110, one or more discrete energy sources are monitored across a network. These can include conventional sources such as gas or electric or include more nuanced sources such as are described in more detail below with respect to sustainability factors. At 1120, energy data is aggregated and subsequently communicated via one or more energy objects as were previously described. Such objects can be employed to extend substantially any industrial protocol with energy monitoring and control capability. At 1130, energy demands are determined from across the network (or networks) from where the discrete energy sources were collected. This can include determining whether systems or process should be activated or deactivated to conserve and manage energy resources. As noted previously, a safety controller can be employed to facilitate such activation and/or deactivation where some components on the network may be activated while others are concurrently deactivated. At 1140, a determination is made as to whether or not energy should be automatically adjusted up or down. This can include idling or reducing energy in some processes and while activating or increasing energy in some others. If such adjustment is warranted, the process automatically adjusts energy supply or demand at 1160 before proceeding back to 1110 and monitoring energy. If no such adjustment is required, the process proceeds back to 1110 from the decision at 1140.
In general, energy packets or objects can be utilized for various applications. These include methods for aggregating energy data, measuring each machine for analysis and comparison, and determining energy cost per product (e.g., by tagging a bill of material with object data). The objects enable bridging the gap between 1st and 2nd shifts for example and minimize energy costs. These include providing energy information for use with other factors, such as order backlog, labor costs, and so forth. Line of sight controls include Level 1—basic metering, Level 2—sub metering, and Level 3—integrated data/decision forecasting.
The energy objects facilitate a proactive system that considers raw materials, physical assets/equipment, and production schedule for the user including use by automated agents. The energy object can be combined with CIP protocol for real-time monitoring and control. This includes determining regeneration opportunities within industrial drive and motion controllers. For example this includes control algorithms for mechanical shift to allow powered drives/controllers to affect idle drives/controllers.
The energy object includes a framework and proxy for certain applications including synchronized use of CIP objects across multiple facilities to effectuate produce/consume energy decisions. This helps users identify opportunities to harness energy existing in the facility which can include the use of gravity, motion on rollers, or transfer to flywheel or alternative fuel source (e.g., hybrid energy). The CIP energy objects can be employed to intelligently communicate with active and idled equipment to save costs. For example considering where robots are idle so many hours per year or what conveyors and other applications are employed including “Just-in-time” power concepts. The object can be employed as an entry point into the application and employed with suppliers to compare products and improve products/equipment used in facility. As noted previously CIP energy objects can place devices into “safe” mode/state based on safety modes.
The CIP energy objects can also be used in facility optimization where attributes of CIP energy objects include maximum and minimum values for each device. Some example attributes include an identifier, a device name, a hierarchy/fully qualified parameter, an object class, a role, a type of energy including water, gas, air steams, a measurement parameter, some type of aggregation, and some type of time reference. The energy objects can reside in various industrial automation hardware or software configurations.
It is noted that the term energy as used herein can be broadly defined to include one or more sustainability factors that can also be employed with the energy objects described herein. Sustainability factors can be associated with the product, the process, or a combination. The Sustainability factors can be used to extend a) the specification of materials and products b) the work instructions used to transform the products into finished material c) descriptors and other factors associated with the human resources performing production d) factors associated with the machines performing production e) factors associated with the facility and utilities supply chain involved in production, such as type of electricity used (solar vs. wind vs. coal, for example) and f) scheduling information. Sustainability factors can be created using known industry standards, or, individuals can develop their own factors in order to track and measure those characteristics that are of particular importance to them. However, as a sustainability factor could be self-created to account for factors unique in importance to an individual, company, retailer, region, and so forth, thus, it is to be appreciated that is not an all-inclusive list. Thus, energy objects as described herein can include monitoring and/or control of one or more sustainability factors. The following description provides some example processes where energy objects can be employed to monitor or control sustainability factors.
In one aspect, energy objects can be employed for optimizing production in view of detected carbon footprint ranges. In this aspect, sustainability factors are monitored and a decision is made as to whether or not current production methods are within an acceptable range to meet the desired carbon footprint. If the current range is acceptable, the process employs current production methods that satisfy the respective ranges. If the current production is not within acceptable ranges, the process proceeds where ingredients may be altered, shipping methods may be altered, and/or manufacturing methods may be altered to achieve desired carbon footprint levels. As noted previously, factors outside of the production process itself can impact the ultimate cost and profitability of the end product. Production using resources from various regions, or targeted for shipment to various regions, can be automatically modified depending upon the acceptable range of detected values for the carbon footprint of the end product which can be communicated and controlled via the energy objects. Thus, modeling can determine: which batch of raw ingredients or; which manufacturing method and/or; which shipping method provides the lowest (or suitable) overall carbon footprint for a particular product and/or destination.
In another aspect, energy objects can be employed for optimizing procurement and shipping systems in view of detected environmental or other energy/sustainability factors. Environmental factors are considered such as weather or other climate goals that may be desired for a particular product or process. Thus, it may be determined that a particular location is cooler than projected thus a different type of shipping or packaging could be employed. Procurement of supplies and/or production methods can be automatically adjusted in view of current environmental data. Material or products can be purchased or transported to support the environmental goals. As noted previously, shipments and additional factors could be aligned with environmental factors such as weather, to minimize environmental impact. For example, by coordinating with weather systems, truck shipments in affected regions could be delayed during ‘ozone alert’ times, or shifted to rail transport. The overall objective could be to optimize production while minimizing environmental impact. Advanced modeling could ascertain that under certain conditions, high ozone days are likely to occur in an upcoming week, and thus the manufacturer should pre-order those materials that require truck shipments to avoid increasing the ozone impact. Similarly, by coordinating with weather systems, production and shipping could be optimized to take advantage of ‘hotter’ or ‘colder’ routes for products requiring controlled storage, for example. The energy objects described herein can be employed to provide such coordination and control.
In yet another aspect, energy objects can be employed for optimizing regulatory compliance in view of various sustainability factors. Regulatory rules can be determined for a destination location, for example. These can include safety compliance, emissions, carbon taxes, in addition to other sustainability factors. Production requirements can be determined in view of the rules and related sustainability factors and optimized in view of the regulations. This can include manufacturing with alternative energy sources in order to meet some incentive offered by a regulating body. Labels can be automatically updated to reflect compliance with regulations and sustainability factors. Data and processes from a sustainability optimization system could include interconnectivity with a database containing regulatory rules to simplify regulatory decision making and oversight. For example, a particular government authority may desire to encourage the use of solar power. Merely having energy usage information on a label would be insufficient to administer a tax on a product, as that would not indicate what type of energy was used. By associating a sustainability factor indicating the type of energy used for production, in addition to other relevant sustainability factors, manufacturers could optimize production to take maximum advantage of government rebates and other incentives while minimizing the risk of adverse judgments. Similarly, regulatory bodies could optimize tax administration and administration of other regulations to drive the desired behavior to keep their economies and environments responsible and sustainable.
As noted previously, discrete energy monitors can be stationed throughout an industrial system or process and are employed to collect data from various sustainable sources including produced or consumed energy. The sustainable sources can be from various portions of a process and related to such factors as energy or waste for example. A tagging component such as a data historian (e.g., I/O module that identifies where/when energy is consumed) is provided to label or mark the collected source data as to which portion of an industrial process the data is associated with. For example, in a batch process, the source data may be tagged to indicate which pipe or valve a recipe component was transported across and how much energy such pipe or valve consumed as part of the process. From another point of view, the pipe or valve may be attributed to the amount of waste associated with a portion of the batch process and in its own manner, reflect a type of energy or sustainability factor that is attributable to the respective process. In a discrete process, where items may be assembled in a parallel or serial manner, the sources may be tagged to indicate a sustainability factor for the various components of the discrete process (e.g., discrete process A building an engine lists various components of the engine where the tagged data from the sources is associated with the engine components). A processor or controller collects the tagged data and links the tagged data with a manufacturing model to produce a model or specification that includes the discrete or batch process components that have been associated with the respective sustainability factors or energy source data. By associating energy or other sustainability factors with the manufacturing model or specification, various efficiencies can be provided for and managed within the factory since each item's energy/sustainability component can now be accounted for and traced as a component of the respective discrete or batch process.
In general, sustainable factors such as energy are monitored throughout a plant or process and associated with the model and energy object in order to increase plant efficiencies. Automated monitors can receive data from a plurality of sustainable sources that are distributed across an industrial process. Such processes can include discrete processes where automated assemblies occur (e.g., packaged assemblies) or can include batch processes where mixtures of various ingredients are combined to form a recipe or other combination of elements (e.g., chemical process, food process, beverage process, and so forth). As the respective processes are monitored, sustainable sources such as energy that is collected is tagged to indicate which portion of the discrete or batch process that the source contributed to. After tagging, the data is associated with the manufacturing model, where industrial managers or automated processes can then analyze the process for the components of energy that were attributed to the various portions of the respective process.
In contrast to prior systems that could only view energy from the overall sense of plant-wide consumptions, the source data that is associated with the energy object can now be analyzed in real-time or via offline modeling to optimize and mitigate energy usage. For example, portions of a process may be rearranged to minimize overall energy usage (e.g., perform step C before step A in order to conserve energy from the reverse order of A and C). It is noted that various models can have associated sustainable factors. Such models include MRP models (material requirement planning), MES models (manufacturing execution system), ERP models (enterprise resource planning), programming models (e.g., ladder logic, SFC, batch program, function block), and so forth. In general, the energy objects aggregates energy or other consumption data from the plant floor and correlates it to production output. This enables applying standard production modeling tools for production energy and emission forecasting and optimization, while extending the existing facility demand management system to include production, and lastly, link that system to the Demand Response and Smart Grid (DRSG), as well as, Cap and Trade systems, for example.
In another aspect, an energy object extension to an industrial protocol having a comprehensive suite of attributes, messages and services utilized for the monitoring and control of energy consuming or producing resources by a manufacturing automation application is provided. The energy object includes an identifier associated with an energy resource that is associated with a manufacturing automation application and an energy type associated with the energy resource. This includes a measurement characteristic associated with the energy resource to facilitate energy management by the manufacturing automation application. The industrial protocol is associated with a Common Industrial Protocol (CIP) that further comprises an Ethernet protocol, a device protocol, a control protocol, or a Modbus protocol, for example. The energy object extension includes a demand and response application to activate or deactivate components to facilitate energy management. This can also include a safety component to activate or deactivate components. The demand and response application is associated with reducing a base load, sequencing a start up, shedding non-critical loads, generating power, storing energy for later use, staggering power peaks, or operating at a reduced rate or capacity and can also be associated with a smart grid. This includes a manufacturing execution system (MES) or an energy management control system (EMCS) to facilitate energy management.
In anther aspect, a historian component is employed to generate the identifier, energy type, or measurement characteristic. The energy object extension includes an aggregation parameter, a role parameter, or an operational state parameter. This includes a units/scaling parameter, a roll over parameter, production capacity parameter, or a type parameter. This also includes a time parameter, a data log parameter, a shed and produce service, or an alarm and event message. The energy object extension also includes a parameter object to facilitate configuration, an energy object instance for a device, or an input/output assembly object to facilitate control. This includes an energy structured tag to facilitate energy control and an energy-enabled application that includes a device name, an energy state, a power graph, a demand charge, or an alarm. This can also include energy-enabled phase logic to facilitate energy control in a process or a controller to set increased energy modes of a system. The energy object extension includes a regulation service that exchanges energy to facilitate performance of other components associated with a grid. This includes one or more sustainability sources that are employed to control energy resources, where the sustainability sources are associated with cap and trade policies, waste management activities, or maintenance activities.
In another aspect, a manufacturing automation system for monitoring energy across multiple devices connected by one or more networks is provided. This includes a control and information platform for automatically increasing or decreasing energy resources of an automated system; and an energy object having an identifier, an energy type, and a measurement component to facilitate increasing or decreasing energy resources of the automation system.
In another aspect, a method to extend an industrial protocol having a comprehensive suite of attributes, messages and services for manufacturing automation applications related to energy production and consumption is provided. This includes monitoring a plurality of energy sources; associating the energy sources with a plurality of energy objects; associating the energy sources with an industrial automation protocol; and employing the industrial automation protocol to dynamically increase or decrease energy demands across an automated factory environment. The energy object includes an identifier, a measurement characteristic, an aggregation parameter, a role parameter, an operational state parameter, a units/scaling parameter, a roll over parameter, production capacity parameter, or a type parameter, a time parameter, a data log parameter, a shed and produce service, or an alarm and event message.
It is noted that as used in this application, terms such as “component,” “module,” “system,” and the like are intended to refer to a computer-related, electro-mechanical entity or both, either hardware, a combination of hardware and software, software, or software in execution as applied to an automation system for industrial control. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program and a computer. By way of illustration, both an application running on a server and the server can be components. One or more components may reside within a process or thread of execution and a component may be localized on one computer or distributed between two or more computers, industrial controllers, or modules communicating therewith.
The subject matter as described above includes various exemplary aspects. However, it should be appreciated that it is not possible to describe every conceivable component or methodology for purposes of describing these aspects. One of ordinary skill in the art may recognize that further combinations or permutations may be possible. Various methodologies or architectures may be employed to implement the subject invention, modifications, variations, or equivalents thereof. Accordingly, all such implementations of the aspects described herein are intended to embrace the scope and spirit of subject claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
This application is a continuation of U.S. patent application Ser. No. 12/684,469, entitled “Industrial Control Energy Object”, filed Jan. 8, 2010, which is herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3878401 | Ronnen | Apr 1975 | A |
4039392 | Singh | Aug 1977 | A |
4300125 | Loshing et al. | Nov 1981 | A |
4341345 | Hammer et al. | Jul 1982 | A |
4383298 | Huff et al. | May 1983 | A |
4624685 | Lueckenotte et al. | Nov 1986 | A |
4827395 | Anders et al. | May 1989 | A |
5043929 | Kramer et al. | Aug 1991 | A |
5202996 | Sugino et al. | Apr 1993 | A |
5251205 | Callon et al. | Oct 1993 | A |
5297057 | Kramer et al. | Mar 1994 | A |
5646862 | Jolliffe et al. | Jul 1997 | A |
5736983 | Nakajima et al. | Apr 1998 | A |
5761083 | Brown, Jr. | Jun 1998 | A |
5822207 | Hazama et al. | Oct 1998 | A |
5924486 | Ehlers et al. | Jul 1999 | A |
5983622 | Newburry et al. | Nov 1999 | A |
6012053 | Pant et al. | Jan 2000 | A |
6015783 | Von der Osten et al. | Jan 2000 | A |
6076108 | Courts et al. | Jun 2000 | A |
6263255 | Tan et al. | Jul 2001 | B1 |
6281784 | Redgate et al. | Aug 2001 | B1 |
6289252 | Wilson et al. | Sep 2001 | B1 |
6321983 | Katayanagi et al. | Nov 2001 | B1 |
6437692 | Petite | Aug 2002 | B1 |
6473893 | Kay et al. | Oct 2002 | B1 |
6507774 | Reifman et al. | Jan 2003 | B1 |
6633823 | Bartone et al. | Oct 2003 | B2 |
6701298 | Jutsen | Mar 2004 | B1 |
6747368 | Jarrett, Jr. | Jun 2004 | B2 |
6785592 | Smith et al. | Aug 2004 | B1 |
6857020 | Chaar et al. | Feb 2005 | B1 |
7043316 | Farchmin et al. | May 2006 | B2 |
7136725 | Paciorek | Nov 2006 | B1 |
7277864 | Ohnemus et al. | Oct 2007 | B2 |
7409303 | Yeo et al. | Aug 2008 | B2 |
7451019 | Rodgers | Nov 2008 | B2 |
7477956 | Huang et al. | Jan 2009 | B2 |
7565351 | Callaghan | Jul 2009 | B1 |
7587251 | Hopsecger | Sep 2009 | B2 |
7788189 | Budike, Jr. | Aug 2010 | B2 |
8029288 | Beekhuis | Oct 2011 | B2 |
8271363 | Branscomb | Sep 2012 | B2 |
20010011368 | Graser et al. | Aug 2001 | A1 |
20020013744 | Tsunenari et al. | Jan 2002 | A1 |
20020026343 | Duenke | Feb 2002 | A1 |
20020035495 | Spira | Mar 2002 | A1 |
20020066072 | Crevatin | May 2002 | A1 |
20020099464 | O'Connor et al. | Jul 2002 | A1 |
20020099804 | O'Connor et al. | Jul 2002 | A1 |
20020116239 | Reinsma et al. | Aug 2002 | A1 |
20020128933 | Day et al. | Sep 2002 | A1 |
20020168621 | Cook et al. | Nov 2002 | A1 |
20020169582 | Eryurek et al. | Nov 2002 | A1 |
20020178047 | Or et al. | Nov 2002 | A1 |
20020198755 | Birkner et al. | Dec 2002 | A1 |
20030014500 | Schleiss et al. | Jan 2003 | A1 |
20030028527 | Crosby et al. | Feb 2003 | A1 |
20030042794 | Jarrett, Jr. | Mar 2003 | A1 |
20030061091 | Amaratunga et al. | Mar 2003 | A1 |
20030088370 | Bagepalli et al. | May 2003 | A1 |
20030110065 | Twigge-Molecey | Jun 2003 | A1 |
20030110369 | Fish et al. | Jun 2003 | A1 |
20030171851 | Brickfield et al. | Sep 2003 | A1 |
20030221119 | Geiger et al. | Nov 2003 | A1 |
20040028966 | Hibbs et al. | Feb 2004 | A1 |
20040088119 | Landgraf | May 2004 | A1 |
20040107345 | Brandt et al. | Jun 2004 | A1 |
20040117240 | Ness et al. | Jun 2004 | A1 |
20040143467 | McAllister et al. | Jul 2004 | A1 |
20040158506 | Wille | Aug 2004 | A1 |
20040167677 | Weiss | Aug 2004 | A1 |
20040199294 | Fairlie et al. | Oct 2004 | A1 |
20040205412 | Staron et al. | Oct 2004 | A1 |
20040225649 | Yeo et al. | Nov 2004 | A1 |
20040249697 | Ohnemus et al. | Dec 2004 | A1 |
20040260489 | Mansingh et al. | Dec 2004 | A1 |
20040261673 | Allen et al. | Dec 2004 | A1 |
20050015287 | Beaver | Jan 2005 | A1 |
20050034023 | Maturana et al. | Feb 2005 | A1 |
20050065971 | Honda | Mar 2005 | A1 |
20050143865 | Gardner | Jun 2005 | A1 |
20050144154 | DeMesa et al. | Jun 2005 | A1 |
20050171910 | Wu et al. | Aug 2005 | A1 |
20050198241 | Pavlik et al. | Sep 2005 | A1 |
20050198333 | Dinges et al. | Sep 2005 | A1 |
20050278296 | Bostwick | Dec 2005 | A1 |
20060026145 | Beringer et al. | Feb 2006 | A1 |
20060248002 | Summer et al. | Nov 2006 | A1 |
20060248032 | Jellum | Nov 2006 | A1 |
20060259154 | Hood | Nov 2006 | A1 |
20060259160 | Hood | Nov 2006 | A1 |
20060276938 | Miller | Dec 2006 | A1 |
20070038646 | Thota | Feb 2007 | A1 |
20070073750 | Chand et al. | Mar 2007 | A1 |
20070078736 | Chand et al. | Apr 2007 | A1 |
20070088518 | Braun | Apr 2007 | A1 |
20070168213 | Comrie | Jul 2007 | A1 |
20070226068 | Keil et al. | Sep 2007 | A1 |
20070233288 | Hamidpour | Oct 2007 | A1 |
20070283030 | Deininger et al. | Dec 2007 | A1 |
20080015975 | Ivchenko et al. | Jan 2008 | A1 |
20080040296 | Bridges | Feb 2008 | A1 |
20080046387 | Gopal et al. | Feb 2008 | A1 |
20080046407 | Shah et al. | Feb 2008 | A1 |
20080059457 | Ohnemus et al. | Mar 2008 | A1 |
20080079560 | Hall et al. | Apr 2008 | A1 |
20080127779 | Morales Cerda et al. | Jun 2008 | A1 |
20080154749 | D'hooghe et al. | Jun 2008 | A1 |
20080255899 | McConnell et al. | Oct 2008 | A1 |
20080270272 | Branscomb | Oct 2008 | A1 |
20080272934 | Wang et al. | Nov 2008 | A1 |
20080319812 | Sousa et al. | Dec 2008 | A1 |
20090076661 | Pearson | Mar 2009 | A1 |
20090083843 | Wilkinson, Jr. et al. | Mar 2009 | A1 |
20090093916 | Parsonnet | Apr 2009 | A1 |
20090099887 | Sklar et al. | Apr 2009 | A1 |
20090100159 | Extra | Apr 2009 | A1 |
20090132176 | McConnell et al. | May 2009 | A1 |
20090138415 | Lancaster | May 2009 | A1 |
20090177505 | Dietrich et al. | Jul 2009 | A1 |
20090216387 | Klein | Aug 2009 | A1 |
20090222307 | Beaver | Sep 2009 | A1 |
20090281674 | Taft | Nov 2009 | A1 |
20090281677 | Botich et al. | Nov 2009 | A1 |
20090313164 | Hoglund | Dec 2009 | A1 |
20090319315 | Branscomb | Dec 2009 | A1 |
20090326726 | Ippolito | Dec 2009 | A1 |
20100023360 | Nadhan | Jan 2010 | A1 |
20100030601 | Warther et al. | Feb 2010 | A1 |
20100042455 | Liu et al. | Feb 2010 | A1 |
20100057480 | Arfin et al. | Mar 2010 | A1 |
20100070091 | Watson | Mar 2010 | A1 |
20100088136 | Cheng et al. | Apr 2010 | A1 |
20100100405 | Lepore et al. | Apr 2010 | A1 |
20100131343 | Hamilton et al. | May 2010 | A1 |
20100138003 | August et al. | Jun 2010 | A1 |
20100138066 | Kong | Jun 2010 | A1 |
20100185622 | Deninger | Jul 2010 | A1 |
20100217642 | Crabtree et al. | Aug 2010 | A1 |
20100217651 | Crabtree et al. | Aug 2010 | A1 |
20100218108 | Crabtree et al. | Aug 2010 | A1 |
20100249975 | Rezayat | Sep 2010 | A1 |
20100262445 | DeSorbo | Oct 2010 | A1 |
20100274367 | Kaufman et al. | Oct 2010 | A1 |
20100274377 | Kaufman et al. | Oct 2010 | A1 |
20100274602 | Kaufman et al. | Oct 2010 | A1 |
20100274603 | Walker et al. | Oct 2010 | A1 |
20100274611 | Kaufman et al. | Oct 2010 | A1 |
20100274612 | Walker et al. | Oct 2010 | A1 |
20100274629 | Walker et al. | Oct 2010 | A1 |
20100274810 | Walker et al. | Oct 2010 | A1 |
20100275147 | Kaufman et al. | Oct 2010 | A1 |
20100292856 | Fujita | Nov 2010 | A1 |
20100306097 | Greiner et al. | Dec 2010 | A1 |
20100314940 | Palmer et al. | Dec 2010 | A1 |
20100318233 | Yunes et al. | Dec 2010 | A1 |
20100332373 | Crabtree et al. | Dec 2010 | A1 |
20110046800 | Imes et al. | Feb 2011 | A1 |
20110071721 | Glilfillan et al. | Mar 2011 | A1 |
20110106321 | Cherian | May 2011 | A1 |
20110131455 | Law | Jun 2011 | A1 |
20110172838 | Pai | Jul 2011 | A1 |
20110273022 | Dennis et al. | Nov 2011 | A1 |
20120174830 | Comrie | Jul 2012 | A1 |
20120284790 | Bhargava | Nov 2012 | A1 |
20130096727 | Brandt | Apr 2013 | A1 |
20130254838 | Ahuja | Sep 2013 | A1 |
20140351010 | Kong | Nov 2014 | A1 |
Number | Date | Country |
---|---|---|
0977137 | Feb 2000 | EP |
WO 2004074954 | Feb 2004 | WO |
WO 2008011427 | Jan 2008 | WO |
Entry |
---|
Springer Handbook of Automation, 2009, Springer, 1841 pages. |
ABB, “Energy Management and Optimization for the Process Industries—Advanced It Tools for Planning, Monitoring, Controlling, and Reporting Energy System Operations”, Aug. 11, 2006 Brochure, published online at [http://library.abb.com/global/scot/scot296.nsf/veritydisplay/bd2a898a24267c46c12571c70070a851/$File/3BFI402000R3001—en—Advanced—IT—Tools—for—Energy—Management.pdf], retrieved Apr. 13, 2009, 6 pages. |
ABB, “Energy Management Solution for the Process Industry—Energy Management and Optimization”, Apr. 6, 2007 Brochure, published online at [http://library.abb.com/global/scot/scot313.nsf/veritydisplay/5e48efb88a7e1cbac125734600737b02/$File/3BFI405000R4001—en—Energy—Management—and—Optimization—3.5.pdf], retrieved Apr. 13, 2009, 12 pages. |
Dietmair, A., et al., “Energy Consumption and Optimization for Production Machines”, Sustain-able Energy Technologies, 2008, ICSET 2008, IEEE International Conference on IEEE, Piscataway, NJ, USA, Nov. 24, 2008, pp. 574-579, XP031442235, ISBN:978-1-4244-1887-9. |
EPO: Notice from the European Patent Office dated Oct. 1, 2007 concerning Business Methods, Official Journal of the European Patent Office, vol. 30, No. 11, Nov. 1, 2007, pp. 592-593. |
European Search Report for European Patent Application No. 10160581.4-1238 dated Sep. 23, 2010, 8 pages. |
European Search Report for European Patent Application No. 10160585.5-1527/2254061 dated Dec. 20, 2010, 9 pages. |
European Search Report for European Patent Application No. 10160649.9-1238 dated Sep. 23, 2010, 8 pages. |
European Search Report for European Patent Application No. 10160673.9-1238 dated Sep. 23, 2010, 9 pages. |
European Search Report for European Patent Application No. 10160737.2-1238 dated Nov. 4, 2010, 9 pages. |
European Search Report for European Patent Application No. 10160810 dated Aug. 6, 2010, 2 pages. |
European Search Report for European Patent Application No. 10160811.5 dated Sep. 20, 2010, 9 pages. |
GE Energy, “Energy and Asset Performance—Fact Sheet”, Sep. 2005, General Electric Company, published online at [http://www.gepower.com/prod—serv/serv/industrial—service/en/downloads/gea14163—eap.pdf], retrieved Apr. 13, 2009, 2 pages. |
Kennedy, Pat, et al., “In Pursuit of the Perfect Plant—A Business and Technical Guide”, Apr. 2008, Chapter 9—Energy Management, pp. 251-283; published by Evolved Technologist Press, New York, New York, USA. |
Kiritsis D., et al., “Research Issues on Product Lifecycle Management Information Tracking Using Smart Embedded Systems”, Advanced Engineering Informatics, Elsevier Lnkd—DOI: 10.1016/J.AEI.2004.09.005, vol. 17, No. 3-4, Jul. 1, 2003, pp. 189-202, XP004595481 ISSN: 1474-0346. |
Kouloura, et al., “A Systems Approach to Corporate Sustainability in Energy Management of Industrial Units”, IEEE Systems Journal, vol. 2, No. 4, Dec. 2008, pp. 442-452. |
Seref Erkayhan Ed—Ding Zhen-Hua, et al., “The Use of RFID Enables a Holistic Information Management Within Product Lifcycle Management (PLM)”. RFID EURASIA, 2007 1st Annual, IEEE, PI Sep. 1, 2007, pp. 1-4 XP031153342. ISBN: 978-975-01-5660-1. |
Yang, et al., “Eco-Design for Product Lifecycle Sustainability”, IEEE International Conference on Industrial Informatics, 2006, pp. 548-553. |
Y-S Ma, et al., “Product Lifecycle Analysis and Optimization in an Eco-Value Based, Sustainable and Unified Approach”, Industrial Informatics, 2006 IEEE International Conference on, IEEE, PI, Aug. 1, 2006, pp. 537-541, XP031003409, ISBN:978-0-7803-9700-2. |
Jawahir, I. S., et al. “Total life-cycle considerations in product design for sustainability: A framework for coomprehensive evaluation.” Proc. 10th Int. Research/Expert Conf. (TMT 2006), Barcelona, Spain, 2006. |
Dillenburg, Stephen, Timothy Greene, and O. Homer Erekson. “Aproaching socially responsible investment with a comprehensive ratings scheme: total social impact.” Journal of Business Ethics 43.3. |
Number | Date | Country | |
---|---|---|---|
20140257586 A1 | Sep 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12684469 | Jan 2010 | US |
Child | 14285511 | US |