Browse Prior Art Database

Energymanagement - Taskplanung

IP.com Disclosure Number: IPCOM000210699D
Original Publication Date: 2011-Sep-09
Included in the Prior Art Database: 2011-Sep-09
Document File: 2 page(s) / 144K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

In industrial environments it is useful to switch off not used equipment or devices according to the phase of the work or the state of the staff. So energy can be saved by switching off the lights or the air-conditioning for example. State of the art is to do this manually.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

(This page contains 01 pictures or other non-text object)

(This page contains 00 pictures or other non-text object)

Energymanagement - Taskplanung

Idea: Boris Grassmann, DE-Nuremberg; Norbert Brousek, DE-Nuremberg; Florian Spannbauer, DE- Nuremberg; Josef Schindler, DE-Nuremberg; Rainer Unterhaslberger, DE-Munich; Dieter Tobisch, DE-Nuremberg; Ralf Koerner, DE-Nuremberg

In industrial environments it is useful to switch off not used equipment or devices according to the phase of the work or the state of the staff. So energy can be saved by switching off the lights or the air-conditioning for example. State of the art is to do this manually.

In the following a novel solution is proposed, to arrange primary plants, sub-processes and supporting plants in a hierarchy and control their energy consumption in interdependency. Primary plants are production lines for example. The air conditioning, fans, lighting etc. are supporting plants. The supporting plants can be assigned to multiple primary plants. A defined factor for the primary equipment and each production state describes how much capacity of the supporting equipment is necessary. The general dependencies getting assigned to a technology structure in a graphical user interface of an energy-management software (Figure 1, Red Box). The software is basically operated by drag & drop. The equipment is defined by a name, description and if necessary an extern label which represent the equipment in a source system. The equipment objects interact by equipment variables like "switch on" or "shift model". Furthermore the equipment can have additional attributes. Such an attribute is the nominal power consumption for example which can be used for a prediction model.

The equipment can be controlled according to the shift planning. So it is possible to define shift models (Figure 1, Blue Box) for individual equipments and production states like producing, break or standby. These shift models assign the shifts to parts of the day and the days to a profile. The profiles can be freely defined or in a certain interval, for example a week with 7 different days. For a clear arrangement colors can be assigned to the shifts. The shift model can be used for different plants as well. It is possible to rollout the shift model to a calendar. In the calendar view (Figure 1, Green Box) the whole shift model or single production states can be adjusted. Triggered by a change to a production state, the software adjusts the following production states.

In some cases it is necessary to start a sub-process a while before the main process. Therefore state transitions can be defined. By the state transitions the duration of the past or the following produ...