Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B2219/00—Program-control systems
  • G05B2219/20—Pc systems
  • G05B2219/23—Pc programming
  • G05B2219/23261—Use control template library
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B2219/00—Program-control systems
  • G05B2219/30—Nc systems
  • G05B2219/33—Director till display
  • G05B2219/33055—Holon, agent executes task and cooperates with other, distributed control
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B2219/00—Program-control systems
  • G05B2219/30—Nc systems
  • G05B2219/33—Director till display
  • G05B2219/33063—Generic coordination, master agent to data manager agent to tasks to active agent

Definitions

• the invention relates to a control system with service-oriented architecture for a flexible production plant, comprising a data communication system for the exchange of data coupled, decentralized, distributed devices with at least one software component and electrical and / or mechanical components as well as a A method of configuring a control system by developing and implementing service oriented software components as part of a service oriented architecture for distributed distributed devices in flexible manufacturing facilities.
• the European Integrated Project SOCRADES will develop methods, technologies and tools to model, design and implement networked systems provided by intelligent, embedded devices.
• SOCRADES The aim of this project (SOCRADES) is the development of so-called “middleware” technologies, ie application-independent technologies that offer services to mediate between applications.
• based architectures SOA
• wired and wireless network technologies as well as having an open interface.
• software components should contain device-specific functionalities.
• the object of the present invention is to refine a control system and a method for configuring a control system in such a way that it can be configured with little effort in the event of changes in the production plant or different production scenarios
• the software component is derived from a process or sub-process of a PPR model of the flexible production system, each software component derived from the process or sub-process control logic, a flexible interface for the Having access to resources represented in the PPR model as well as a communication interface for integration into the service-oriented architecture.
• each of the software components having control logic derived from the sub-process, a flexible interface for accessing resources represented in the PPR model, and a communications interface for integration into the service-oriented architecture , Presentation and analysis of different production scenarios as Client-server architecture,
• the method steps are carried out in a virtual development environment.
• control logic of a standardized software component is used for one production process, such.
• B. developed a clamping sequence for fixing sheets to be welded.
• a component-based engineering approach is therefore expediently geared to the manufacturing process. This engineering process provides the functional elements to professionally use the service-oriented architecture.
• resources such. As actuators, sensors, controls and electrical and / or mechanical components but also information and people necessary.
• the resources themselves are represented as a virtual model in such a way that their physical behavior is reproduced as expediently as possible.
• the reference to the resources is determined by the PPR model.
• the services as part of a combination of mechatronics, communication and intelligence are integrated into an overall concept, which assumes all control tasks.
• a service-oriented architecture they are preferably implemented as a web service.
• a model of a life cycle for the production plant is developed based on the standardized software components. It should be noted that it is not only for a specific target scenario that a draft is but that changing framework conditions are integrated into the planning approach.
• Another method step is characterized by the fact that different production scenarios are displayed as a client-server architecture and analyzed virtually.
• the aim here is that in practice no reprogramming of the production plant must be carried out if the general conditions change.
• different variants can simply be generated by a new client-server architecture.
• Another preferred method step provides that the developed software components and the associated client-server architecture are implemented at different aggregation levels.
• the web services can in turn call up further web services.
• a library of generic web services is to be generated.
• FIG. 1 shows a service-oriented architecture of a control system for a flexible production plant
• 2 shows a process graph of a virtual model of the production plant and web services derived therefrom; 3 is a flowchart for creating a model of a life cycle for the production plant and
• Fig. 4 schematic representation of a client-server architecture at different aggregation levels.
• FIG. 1 shows a schematic illustration of a control system 10 in service-oriented architecture for decentralized, distributed devices such as control units 12, 14, 16 in the form of programmable logic controllers (PLC, mini-PLC) or intelligent modules, as well as electrical and / or mechanical components 18 , 20, 22 in the form of transport systems, motors or sensors of a production plant 24.
• PLC programmable logic controller
• mini-PLC mini-PLC
• electrical and / or mechanical components 18 , 20, 22 in the form of transport systems, motors or sensors of a production plant 24.
• the devices 12, 14, 16, which are referred to as “devices” in FIG. 1, can be designed as a programmable logic controller (PLC), mini-PLCs distributed in the production plant 24, or intelligent control modules in the form of intelligent actuators or sensors Devices 12, 14, 16 are coupled to each other via a data communication system 26 for exchanging data, wherein the data communication system 26 may be formed as a wired bus system or wireless radio system.
• PLC programmable logic controller
• mini-PLCs distributed in the production plant 24 or intelligent control modules in the form of intelligent actuators or sensors
• Devices 12, 14, 16 are coupled to each other via a data communication system 26 for exchanging data, wherein the data communication system 26 may be formed as a wired bus system or wireless radio system.
• the devices 12, 14, 16 each have physical inputs or outputs 28, 30, 32 for controlling actuators or for acquiring sensor data.
• One or more software components 34 - 44 are implemented in the devices 12, 14, 16, via which different services (services) such as, for example, diagnosis, data access or also control processes are provided and called up.
• services such as, for example, diagnosis, data access or also control processes are provided and called up.
• each of the devices (devices) 12, 14, 16 forms a service as a combination of mechatronics, communication and intelligence, which are integrated into an overall concept, which takes over all control tasks.
• at least one software component is designed as a web service.
• the service-oriented architecture enables equal communication between the devices 12, 14, 16 without the need for a hierarchy concept.
• FIG. 2 outlines the engineering process for flexible production facilities based on a service-oriented architecture.
• the production plant 24 is represented by a PPR model containing product, process and resource information.
• the production process may be represented by a process graph 48 in which sub-processes 50, 52, 54 are included.
• Each sub-process 50, 52, 54 contains logic information, i. H. the timing of actions, including information about what resources are needed to perform each sub-process.
• the decisive design step is the adoption of this information for the development of services.
• the software components 34, 40, 42 of the devices 12, 14, 16 numbered in FIG. 1, which assume control processes, are each derived from one of the sub-processes 50, 52, 54.
• Each software component of a sub-process includes a control logic 56 that is developed for each one manufacturing process, such as sub-process 52, and derived from process graph 48. Since the processing of the sub-process 52 requires resources in the form of the electrical or mechanical components 18, 20, 22 such as sensors, motors and transport systems, a flexible interface 54 is implemented in which resource-specific data is allocated.
• the resources 18, 20, 22 themselves are represented in the virtual engineering environment (PPR model) in such a way that their physical behavior is reproduced as expediently as possible, for example the time consumption for a movement process.
• PPR model virtual engineering environment
• the standardized software components 34, 40, 42 are equipped with communication interfaces 60, 62.
• the communication interface 60 is implemented as a web service-based technology. mented and enables communication with other services and thus integration into an overall concept. Via the interface 62, resources 18, 20, 22 can be activated or their states can be queried.
• a model of a life cycle for the production plant is developed based on the software components.
• a time sequence of a plant life cycle is shown in FIG.
• a demand definition of the production plant such as its production capacity, is carried out.
• various variants are planned for the flexible operation of the production plant.
• the PPR model of the production plant accompanies the plant throughout its entire life cycle.
• the PPR model contains virtual mappings of equipment and components of the production plant that contain the software components as a module.
• the advantage of the invention in the planning phase is that a production system can be represented virtually with “intelligent” models of devices and components, the "intelligence" of the modules used being adapted by planning different variants for the flexible operation due to different framework conditions can. From such a PPR model, taking into account the plant life cycle in changing conditions can Then a control program for the actual plant control can be derived.
• the invention offers the advantage that devices in the form of programmable logic controllers, robot controllers or the like can be flexibly adapted to changing production conditions, without the need for time-consuming reprogramming.
• FIG. 4 shows that different production scenarios can be represented in the form of a client-server architecture and analyzed virtually.
• a product 64 is transported on a pallet.
• the unit of product and pallets is hereinafter referred to as "client.”
• a service 66 such as "transport demand” is requested via the data transmission medium 20.
• the request is forwarded to the device 12 as motor control of a transport structure, which in turn reports a service request 68 to the device 14 such as control of a transfer station.
• the device 14 calls the general service 70 "transport system", which ultimately provides the required transport capacity for transporting the product.
• the architecture shown in FIG. 4 also shows that a stepless transition from a central control to decentralized control components 12, 14, 16 can be performed.
• the web services used can in turn call other web services 72. These requests can be made over a global network 74 such as the Internet.
• Web services can be integrated into the IT landscape of a company. For example, a connection to an MES 76 (Manufacturing Execution System) can be established to retrieve specific routing information.
• MES 76 Manufacturing Execution System

Applications Claiming Priority (2)

Publications (1)

Family

ID=39106085

Family Applications (1)

Country Status (5)

Families Citing this family (15)

Family Cites Families (4)

• 2006
  • 2006-12-08 DE DE102006058282A patent/DE102006058282A1/de not_active Withdrawn
• 2007
  • 2007-12-07 WO PCT/EP2007/063526 patent/WO2008068333A1/de active Application Filing
  • 2007-12-07 JP JP2009539769A patent/JP2010511949A/ja not_active Withdrawn
  • 2007-12-07 US US12/517,860 patent/US20100131076A1/en not_active Abandoned
  • 2007-12-07 EP EP07847979A patent/EP2100198A1/de not_active Withdrawn

Non-Patent Citations (3)

Also Published As

Similar Documents

Legal Events