1. Field of the Invention
The invention relates to an automation tool to support the planning and implementation of automated technical processes.
2. Description of Related Art
Automation tools to support the planning and implementation of automated technical processes are generally known. Examples of automation tools of this type are CAD (Computer Aided Design) or CAE (Computer Aided Engineering) systems. Other examples of this automation tools are the so-called development environments, which are created e.g., to generate control programs for controlling and/or monitoring technical processes.
A drawback of these prior art automation tools is that every automation tool accesses its own database. This requires a time-consuming transfer of the data of the individual automation tools, particularly if a number of different automation tools are successively used to plan and implement automated technical processes. Even after this transfer of data from a first to a second automation tool, there is no content-based or functional connection between the data. Each user of an automation tool must deal with the full data volume and is responsible for the correct use and processing of the data within his or her scope of duties without always knowing the specific origin, context, or functionality of the individual data.
Before a product or a workpiece can be automatically produced, a significant amount of time and effort must be invested in setting up the automated production process for this product or workpiece. To set up this production process, specialists are required, i.e., production and automation specialists—hereinafter referred to as designers or automation specialists. These specialists receive specifications from other specialists—hereinafter referred to as technologists—who define the characteristics of the product.
The technologist is the planner of a product and generates, for example, the formula of a drug or the model of a motor vehicle in the form of individual body parts with welds or other connecting points. The technologist essentially thinks in terms of product characteristics, market factors, competition, economic efficiency, etc. Other important factors influencing the technologist are criteria such as production times, production costs, and product innovations.
The designer is the planner of the production installation. The designer specifies machines and equipment to mix and chemically or thermally influence the precursor materials of the drug or to transport, handle, and interconnect the body parts. The designer essentially thinks in terms of physical processes or physical quantities. The designer considers items such as plant parts, (pipe) lines and substances or their movements or mobility.
The automation specialist plans the automation of the resulting technical process. The automation specialist creates a control program to influence the machines or equipment, the transport and processing of the starting materials or products to ultimately produce the end product. The automation specialist essentially thinks in terms of digital quantities and final states or smaller, independent units.
In planning the automation of the resulting technical process, the automation specialist considers control functions, time sequences, drives and driving means, positions of moved or movable components in the process and states of the process. The automation specialist is familiar with the so-called state graphs and is used to dividing the technical process into separable partial processes, with which the automation specialist deals successively. The automation specialist's way of thinking is therefore less oriented towards the overall context of the technical process.
Extensive coordination is required among the individual specialists. This coordination takes place at least between the technologist and the designer on the one hand and the designer and the automation specialist on the other. Distributing the tasks among several specialists who have different ways of thinking and who until now have each used different automation tools for their scope of responsibilities results in substantial problems. Only a few of these problems will be identified below by way of example.
First and foremost, communication problems occur among the specialists involved. This is essentially due to the different language they use. Hence, communication primarily involves translated information, i.e., the designer, when trying to draw the automation specialist's attention to specific features of the mechanical system, attempts to think like the automation specialist and explain the problem in the automation specialist's language. If the designer fails to do this translation but uses his or her language to describe the problem to the automation specialist, the automation specialist translates what he or she has heard or read into his or her way of thinking. The example can of course be expanded to include every possible and meaningful communication among the specialists involved.
The consequence of this continuously required translation of information is a loss of information. For example, the designer may not, or only incompletely or incorrectly relay information to the automation specialist that he or she received from the technologist and that is not particularly important to him or her. This loss of information necessarily leads to inconsistencies in the data used.
One object of the present invention is thus to provide an automation tool that can be used to establish a content-based and functional connection among the data relating to the respective technical process, which remains linked to the data, such that a link established by a first specialist who is entrusted with the planning and implementation of the technical process will remain recognizable to other specialists as well.
Another object of the present invention is to prevent these losses of information.
Illustrative, non-limiting embodiments of the present invention may overcome the above disadvantages and other disadvantages not described above. The present invention is not necessarily required to overcome any of the disadvantages described above, and the illustrative, non-limiting embodiments of the present invention may not overcome any of the problems described above. The appended claims should be consulted to ascertain the true scope of the invention.
According to an illustrative, non-limiting formulation of the present invention, an automation tool for supporting the planning and implementation of an automated technical process is provided. The automation tool, on the one hand, includes access to a database containing a plurality of data relating to the technical process and, on the other hand, displays a user interface with a data window for displaying the data and at least one working window on a display unit. The specific data related to the technical process can be displayed in the working window and linked with data in the data window.
In according with the exemplary formulation, all the specialists use the same database in describing the technical process or their contribution to the solution of the automation problem. This database includes a plurality of data, and each datum relates to a component or an aspect of the technical process. Components of the technical process are, for example, containers, pipelines, etc., motors, valves, etc., control elements, limit switches, etc. and automation devices, e.g., programmable controllers and/or decentralized peripheral devices. Aspects of the technical process relate to, for example, the capacity of the individual components of the technical process to be influenced or controlled.
For the individual specialists, however, only a subset of these data is typically relevant. Each specialist is presented with precisely the data that are relevant for him or her in a working window provided for this individual specialist. Each specialist then links the data displayed in his or her working window with other data in the data window. This establishes a content-based and functional connection between individual data of the technical process.
By way of an example, if a certain surface finish is specified for a workpiece, the fact that this finish is required is encoded in a respective datum of the database. The type of finish is encoded in the same, or optionally in an additional datum. These data of the technical process are usually specified by the technologist, who largely decides on the type and the appearance or the functionality of the workpiece. The designer, based on the data displayed in the data window, recognizes the need for a device to polish the workpiece in the technical process. Thus, the designer creates a datum in the working window provided for him or her to represent such a polishing device. Once the datum has been created in the working window, it is part of the database and can therefore be displayed in the data window. If the designer or the technologist now links the datum representing the polishing device with the one or each datum encoding the polishing, a configuration of the polishing device is achieved. The data are thus no longer presented independently and in parallel, but are interlinked on the basis of the concrete technical process.
In an illustrative, non-limiting formulation of the present invention, a datum may consist of a simple data type, e.g., a byte, word, integer, etc., or a composite and/or user-defined data type. Composite data types are feasible in almost any combination. These data types are composed of simple data types and/or composite data types that have already been defined.
The above-described creation of a datum to represent a polishing device can also be generated automatically, i.e., if the data encoding the polishing can be used to automatically infer the requirement of the polishing. For example, if the data encoding the polishing are instances of a special data type, particularly a special object type.
The recognition of structures created by these data and the automatic derivation of information from these recognized structures, i.e., additional data, is preferably accomplished, for example, using the method described in the German patent application titled: “Automatisierungswerkzeug zur Unterstützung einer Planung und Realizierung eines Automatisierten Technischen Prozesses und Korrespondierendes Verfahren” (Automation tool for supporting the planning and implementation of an automated technical process and method therefor), filed on May 3, 2002 for Siemens AG (serial number: 102 19 912.4), incorporated herein by reference.
In an illustrative, non-limiting formulation of the present invention, the at least one working window is preferably provided to display data relevant for a technologist, a designer or an automation specialist. Each specialist can then use the working window provided for this particular specialist to link the data displayed in the working window with data displayed in the data window based on his expertise.
The data in the working window are linked with data in the data window by selecting the datum in the working window using a pointer device, e.g., a mouse or the like, and moving the selected datum onto the datum to be linked in the data window, or by selecting the datum in the data window using the pointer device and moving the selected datum onto the datum to be linked in the working window. This process of selecting an object, moving the object and releasing the selection of the object is usually referred to as “drag and drop” approach. Linking data by “dragging and dropping” the data in the automation tool results in an intuitive use for the specialists so that the automation tool can be used quickly, without a lengthy familiarization period.
According to an exemplary, non-limiting formulation of the present invention, it is preferable to adjust the suppression of the display of data irrelevant for a technologist, designer or automation specialist in the data window, so that the data volume displayed in the data window can be appropriately reduced. This makes the display clearer and thereby prevents, for example, incorrect or accidental linking.
A display of selected data in the data window or working window is also referred to as a view. According to an exemplary, non-limiting formulation of the present invention, it is preferable for the data window and the one or each working window, a plurality of views is feasible and meaningful, such that each specialist, in addition to the default views, can define his or her own views based on his or her requirements. For each specialist, a plurality of views can be defined to divide the technical process, e.g., spatially or functionally.
The views for presenting only the relevant data to the given specialist are preferably specified and selected, e.g., in the manner described in the German application titled: Automation tool, filed on May 3, 2002 for Siemens AG (serial number: 102 19 911.6), incorporated herein by reference.
Further advantageous embodiments of the present invention may thus also result from combining features thereof with aspects of the two abovementioned applications.
The present invention will now be described in detail by describing illustrative, non-limiting embodiments thereof with reference to the accompanying drawings. In the drawings, the same reference characters denote analogous elements:
The user interface 11 includes a data window 13 to display data 14 relating to a technical process. The technical process can be any automated process or any process that should be automated. The use of the automation tool 12 for an exemplary technical process will now be described with reference to
The user interface 11 further includes at least one working window. In the example depicted in
For example,
Based on the specialist's expertise and contribution to the automation of the technical process and of course based on the technical process itself, each of the specialists establishes links between data 14 in the respective working window 16, 17, and 18 and the data 14 in the data window 13. The data 14 in the data window 13 can be grouped for a clearer presentation. For example, a first group 19 combines data 14 regarding the technical process, which are more technology-related. Accordingly, the technologist may use only data 14 in the first group 19, where other data 14 are suppressed. Second and third groups 20 and 21, each contain data 14 which are more design-related or automation-related. This grouping of the data 14 provides a simple way to suppress the display of data 14 that are not relevant for a particular specialist, i.e., a technologist, a designer, or an automation specialist. A display of data 14 can also be suppressed using the attributes assigned to the data 14.
The data 14 are linked by selecting a datum 14, e.g., in a working window 16, 17, or 18 and using a pointer device, e.g., a mouse, to move the selected datum 14 in a working window 16, 17, or 18 onto a datum 14 in the data window 13 where it is released. This operation, which is referred to as “drag and drop,” is widely used in graphic user interfaces. The data 14 can also be linked starting from the data window 13 by dragging the selected datum 14 onto a datum 14 in a working window 16, 17, or 18. In addition, the data 14 can be linked by manual assignment, e.g., by selecting the datum 14 such that a contextual menu appears with an input field, in which the datum 14 can be linked, or by entering a reference to this datum 14 in the provided input field.
The alignment block 22 is described by the CAD system using different functionalities in a known manner. To make the boreholes 25 and 26 in a workpiece, such as the alignment block 22, the CAD system has a first functionality suitable for making the boreholes 25 and 26. To add cutouts and/or recesses to the workpiece, a second suitable functionality is provided.
The description of the alignment block 22 thus includes a series of data 14 (illustrated in
“borehole: PosX=12, PosY=20, Rad=5”
such that the information “borehole” is determined using the functionality of the CAD system with which the central borehole 25 was created in the CAD view.
The presence of each processing stations 28-31 is known from the prior planning of the technical process 27. Likewise, the need for the presence of each processing station 28-31 can be determined from the respective technological data 14 (illustrated in
Structures that the automation tool 12 cannot detect automatically are recognized by the respective specialist based on this specialist's experience and expertise. Thus, the specialist creates data 14, which the automation tool 12 cannot automatically generate. The specialist also creates links between the individual, manually or automatically generated data 14, which the automation tool 12 cannot automatically generate. The above also applies to data 14 encoding sawing, milling, and/or polishing of the alignment block 22 and automatically generated or generatable data to represent the respective processing stations 29, 30, and 31.
Each automation device 33-36 is represented in the database 15 by a respective datum 14. A competent specialist, e.g., the automation specialist, links the one or each datum 14 representing the respective automation device, e.g., one of the devices 33-36, with respective technology-related or design-related data 14. An example of such a linkage is the link between the datum 14 representing the second processing station 29 for drilling and the automation device 34 assigned to this processing station 29. The more detailed and comprehensive the data 14 is, e.g., the data 14 representing the respective automation device (one of the devices 33-36), the more specifically the respective data 14 can be linked.
For example, if the datum 14 representing one of the automation devices 33-36 includes data structures representing the so-called process image (process image of the inputs and/or process image of the outputs), then the datum 14 encoding the drilling tool for making the central borehole 25 (illustrated in
According to the exemplary, non-limiting embodiment of the present invention, an automation tool 12 is provided for supporting the planning and implementation of an automated technical process 27. The automation tool 12 has access to a database 15 containing a plurality of data 14 relating to the technical process 27. The automation tool displays a user interface 11 on a display unit, e.g., a screen 10 with a data window 13 to display the data 14 and at least one working window 16, 17, 18. Individual data 14 can be displayed in the working window 16, 17, 18 and linked with data 14 in the data window 13. This creates a content-based linkage of data that are currently isolated in the conventional automation tools. These content-based linkages of data provide the specialists involved in the planning and implementation of the technical process 27 with information regarding, for example, functional interrelations in the process. The automation tool 12 bridges the terminologies used by the specialists involved. As a result, communication problems and inconsistencies may be eliminated or at least substantially reduced.
The above description of illustrative, non-limiting embodiments has been given by way of an example. The above and other features of the invention including a device of the various novel components has been particularly described with reference to the accompanying drawings and pointed out in the claims. It will be understood that the particular construction of parts embodying the invention is shown by way of an illustration only and not as a limitation of the invention. The principles and features of this invention may be employed in varied and numerous embodiments without departing from the scope of the invention as defined by the appended claims and equivalents thereof.
Number | Date | Country | Kind |
---|---|---|---|
102 19 913.2 | May 2002 | DE | national |
This is a Continuation of International Application PCT/DE03/01405, with an international filing date of May 2, 2003, which was published under PCT Article 21(2) in German, and the disclosure of which is incorporated into this application by reference.
Number | Date | Country | |
---|---|---|---|
Parent | PCT/DE03/01405 | May 2003 | US |
Child | 10980926 | Nov 2004 | US |