DE10002305A1 - Band saw cutting machine management system, has user interface which provides process information from database to dynamic user interface as required by user - Google Patents

Abstract

The database provider (13) receives information such as monitor data, description data and usage data of cutting machines via machine monitor (7). Interface provider (11) receives process information from database and sends to dynamic user interface. The content such as monitor data, usage data and identification data of the user interface varies based on content of process information required by user. Each cutting machine (1) is connected to corresponding monitor input device (3). The virtual machine (5) accumulates monitor data received from each monitor input device (3) and sends to machine monitor. The database provider (13) receives monitor data from machine monitor and stores monitor data along with description data. The description data has information regarding description of each cutting machine and monitor data has information regarding status of cutting machine. The usage data is derived from monitor data and description data.

Description

The present invention is intended to disclose the pending US provisional Patent Application No. 60 / 116,947 in the name of Masahiko Tadokoro et al, entitled "Management system for cutting machines" and submitted on January 21, 1999 expressly include in their entirety for reference.

The present invention relates to a management system for cutting machines.

The management of cutting machines (e.g. tape saws or the like) usually performed relatively inflexible. Management in in this connection concerns the monitoring of the cutting machines, the Cutting elements, the work or orders to be carried out, the user collecting and analyzing data and intervening to fix prob lemen or inquiries.

Typically, a device with multiple cutting machines uses lead pen or paper or at best calculation tools to equip them, Manage tool inventory and workflow. Older and current status data are not collected and saved in an easily accessible way, yet such data can be easily organized or centralized.

Programmable band saw systems in which work programs from one site computer of a supervisor (supervisor) can be downloaded NEN, are known (e.g., from U.S. Patent No. 5,418,729, "Communicati connection system for programmable band saw ", issued on May 23, 1995). These band saw systems also allow finding limited sawing and opening Support program information from the band saw for the supervisor's computer as well as simultaneous programming of orders by the supervisor computer and / or the band saw itself while an order is being executed. The Systems also allow easy conflict detection of an order number assignment and limited access to saw function values. However, be  system knew a number of shortcomings in overall mana gements of a facility or a variety of facilities.

The known systems connect the programmable logic controls (PLC) a variety of band saws with a single general computer, the typi is usually operated by a supervisor. The programmable Controls have specific programs that operate at the operating level of the saw manufacturer as well as a limited interface device with only a numeric and function keyboard and an LCD display device with one or two rows of characters. The user interface is therefore static and inflexible and cannot go without a major system overhaul be changed, like replacing the PLC's on each saw. Besides, only Saws are used that are specifically designed to interact with the system are thrown. Connections to the supervisor's computer are made through special ones serial connections that cannot share their bandwidth with other signals. Only a rudimentary PLC microprocessor and a central computer come into Fra ge and the operating software that interacts with each microprocessor is only working on the processor in question.

No external connections are provided, so consultation of the Her or an exchange with sales and service providers is possible. At the same time is a management of the machines, orders and one Cutting inventory at different facilities not possible with the be knew systems. No archiving of data for management purposes, neither Local privileged users are also planned. Best if so, Abar will query existing machines or orders prepare a list of assigned order numbers.

Monitoring functions are similarly restricted. The distribution of the workpiece Flows and inventory checks can only be done from a central computer be performed. A supervisor directly at the processing point has no access to the system at a supervisor access level nor would the supervisor be the same Find monitoring and editing options as with a control station.  

Even if such systems claim the workflow, effectiveness and in There is no control or mana to improve valve control gement of the cutting elements in question. No data of the cutting elements will be saved or can be called up. Because any saw or cutting machine is interchangeable Cutting or using cutting elements leads to their incorrect management Bottlenecks in the workflow, interruptions to work and possible problems Damage to the cutting machine and workpieces if any control of the Cutting elements are missing and a variety of chronic workflow interruptions conditions are possible.

The following is a list of those acronyms that are used in the disclosure of the following invention.
ASP - active server page
CGI - Common Interface for the Transition (Common Gateway Interface)
COM - Common Object Model
CORBA - Common Architecture for Object Request Broker Architecture
DCE - Distributed Computing Envi ronment Environment
DCOM - distributed object model for components (Distributed COM)
DHTML - dynamic HTML (Dynamic HTML)
HTML - Language for marking hypertext (Hypertext Markup Langua ge)
HTTP - Hypertext Transport Protocol
IIOP - Internet Between - ORB (Internet Inter-ORB Protocol)
IIS - Internet Information Server
ISA - Industry Standard Architecture
ISDN - Integrated Services Digital Network
JDBC - database connection via Java (Java Database Connectivity)
ODBC - Open Database Connectivity
ORB - Object Request Broker
Perl - practical language for summarizing data and creating reports (Praktical Extraction and Reporting Language)
POS - Persistent Object Service
PPP - Point-to-Point Protocol protocol
RMI - Remote Method Invocation
RPC - Remote Procedure Call
SGML - General, standardized language for marking text (Standard Generalized Markup Language)
SQL - Structured Query Language
TCP / IP - Transport Control Protocol / Internet Protocol
URL - standardized method for finding resources (Uniform Resource Locator)
VPN - Virtual Private Network
XML - extensible markup language

The management system according to the invention enables unexpected advantages for ver different interested participants - each facility with cutting machines, one Company with various such devices and manufacturers of such cutting machines seem.

According to a first aspect of the invention, a management system for Cutting machines and for assigning orders to the cutting machines on: a variety of cutting machines, each of which is a monitoring or Has test input device, through the test data to display the status of Cutting machine can be entered, and a variety of virtual machine parts for collecting the test data, of which each virtual machine part is one Cutting machine corresponds. A database server component communicates with Ma machine monitoring or testing component, records descriptive data and reads them out, including a machine table to describe the Cutting machines and an order table for describing the orders placed on the cutting machines are to be carried out, arranges the order table and dimensions  rail table to each other and records and reads usage data derived from the test data and descriptive data. A machine test component gets the test data from all of the multitude of virtual mechanical engineering share back and generate usage data and transmit the test data and Usage data to the database server part. A user interface server part kommuni adorns the database server part and the machine test part and provides dynamic, interactive user interface elements available, the areas of usage data, Test data and identification data included. The content of the dynamic, interactive User interface elements differ depending on the content of the Use data, test data and description data. At least one userinter faceübersetzteil shows the dynamic, interactive user interface elements.

In this way the system is distributed and the active components can be used by everyone Processor can be arranged in the device, that is, all components can run and interact on a single processor or can be separate, but components connected by a network by individual processors for each cutting machine, for a machine monitoring device, for a Da tenbank server, for a web server and for client browsers are provided. Two or more of the components can be provided on the same processor if such a configuration is advantageous over existing facility designs is. Because the monitoring components (especially the virtual machine components and the machine monitoring components) are platform independent, that can happen horizontal system in a system of cutting machines of different manufacturers be used as a data interface is not required for a special purpose is such.

Another feature of the invention is that each of the plurality of virtual measures machine components, the machine monitoring part, the database server part, the User interface server part and at least one user interface translation component Has identity and communication in the system according to the identities depending on the physical arrangement. In this case, optionally in Be response to a request from the user interface translation component Get user interface server component test data from the machine test component  and a test user interface including the test data to the user interface Send the setting part. Alternatively or additionally in response to a conditional Ab ask the user interface translation component, communicates the user interface server component with the database server component what records sends according to the conditional query of the user interface server component, and the user interface server component transmits a result user interface finally translated the corresponding user interface records component.

In a preferred embodiment, the user interface server compo nente when a job record in the job table and a machine record in the machine table correspond to an order use drawing in an order usage table with machine and record in Pairs.

In a further advantageous exemplary embodiment, the database also contains an alarm table for specifying alarm conditions in the job table and in the machine table. Whenever the user interface server component of a User interface to the at least one user interface translation component transmitted, the user interface server component checks the alarm table and hangs an alarm indicator to certain records in the job table and in the Machine table that correspond to the alarm conditions, the user inter face translation components evaluates the alarm indicator. That way an alarm possible and accessible and configurable on a distributed basis, whereby there is a quick response to any problems.

The test data preferably contain operating data corresponding to the setting every machine. Alternatively or additionally, the test data contain load detection data that shows the operating load of the machine. Finally, the test data Blockage detection data included that indicates whether the machine can operate or blocked and prevented from working.  

The system preferably has a multiplicity of microprocessors which via a network for operating the components are connected. Each of the components with a microprocessor as the host and the components communicate with each other over a network transport layer of the network.

The machine test component can measure the virtual machines accordingly Generate machine table for the description of the cutting machines. In this way the test components, especially the virtual machine components, transmitted over the network to work on the target processor, and therefore can updated, reset or configured as desired without the host process sor to visit physically.

In an implementation, each virtual machine component runs on one se separate processor on the corresponding machine. In this case, the ge separated processor on the corresponding machine preferably still one of the at least one user interface translation component. Alternatively or additionally Lich, the test input device can collect data of data with a variety of detectors on the cutting machine connected is. Each data collection device can by the corresponding ge separate processor can be controlled.

In a further implementation, the database server component and the User interface server component operated on the same processor. In this In this case, the same processor can continue to operate the machine test component.

In a further aspect of the invention, a cutting machine management system network system on: a variable number of instrumented cutting machines, each of which has a processor with a virtual machine component points, which scans the instrumentation on the cutting machine and status information preserved according to the status of the instrumentation. A database server maintains a database of descriptive information that the instruments described cutting machines and can be queried. A machine monitor is connected to every instrumented cutting machine via the network. The machine  nenmonitor comprises a processor with a machine test component that the scans virtual machine components and a status table with status information preservation of every virtual machine component. Bear a web server processes requests from distributed clients and provides hypertext documents. On dynamic content server interprets markup documents with dynamic ones Content including code segments asks the database server to retrieve the descriptive information, whereby the status table from the machine monitor is retrieved and hypertext documents depending on requests from the distributed clients and the internal interpretation of the code segments the. The hypertext documents contain different user interaction elements and information presented depending on the content of the descriptive informa tion and the status table.

In this way, the user interface provided at each browser station is flexible and changes according to the access level and the supplied data. For every Device using at least one (usually several) cutting machine det, the system allows monitoring and process management of the Ar work status and workflow from anywhere within the facility, however also prevents inappropriate access. Since the same protocol for that Furnishing system and the Internet used as a whole are communicati on and access possible at all levels (facility-wide communication as well Communication from outside the facility from any client browser on which a privileged user logs in).

The descriptive or description data can advantageously be a slice element table contain the usable cutting elements of the cutting machine describes and in which every order record and every machine record voltage is selectively associated with a cutting element record. The machines monitor component generates a cumulative work value for each cutting element ment recording according to the strength of the use of a corresponding Cutting elements of the cutting machine. Furthermore, the description data contain a user table in which the users of the system and the operator (Operator) of the machine are described, with each order record and  each machine record is selectively associated with an operator record. In this way the machine usage is also monitored and controlled, where for example order, cutting edge and personnel planning conflicts over the System can be checked.

In yet another aspect of the invention, the cutting machine mana gementnetzsystem a variety of interchangeable cutting elements for Shaping of workpieces and a variable number of cutting machines, in which a cutting element for forming workpieces can be installed. Each cutting machine is assigned a processor that is a virtual machine component that has at least the cutting element status on the cutting machine and the status information corresponding to the status of the cutting elements stores. A database server assigns a database of information to describe the instrumented cutting machines, stores Instructions for use for each cutting element and can be queried. A machine nenmonitor is connected to each cutting machine via a network and has one Processor with a machine monitoring component that the virtual Ma machine components and a status table including the cutting maintains element status of each virtual machine component and the Instructions for use generated depending on the status table. A user The interface server component communicates with the database server and the machine nenmonitor and provides interactive user interface elements that the cutting Use information included. At least one user interface is translated The development component represents the user interface elements.

Accordingly, the cutting element can use and therefore inventory and costs watches and be controlled. In particular, current orders are monitored, assigned to the cutting element used and the cumulative use Each cutting element in the inventory is calculated and recorded.

The present invention is based on the figures enclosed in the drawing explained in more detail without this being intended to be restrictive. Different versions  tion examples of the invention are in the various figures accordingly marked with the same reference numerals.

Show it:

Fig. 1 is a schematic overview of a management system of the cutting machine;

Figure 2A is a first embodiment of a management system for cutting machines.

Fig. 2B shows a second embodiment of a management system for cutting machines;

Fig. 3 is a schematic view of a first embodiment of an instrumented cutting machine;

FIG. 4 shows a flowchart to illustrate a process sequence of a virtual machine (VM) component on a processor assigned to the instrumented cutting machine according to FIG. 3;

Figure 5A assigned a flowchart for a process flow Därstellurig ei nes status table object a machine monitoring (MM) component on a server, the one or more VM components of FIG. 4.

5B is a flowchart illustrating a process flow ei nes Maschinenfabrik object of MM component.

Fig. 6 is an exemplary table of a database;

Fig. 7 is a flowchart showing a process flow of a routine for dynamically generating a user corresponding dynamic recording document in the system;

FIG. 8A is a flow diagram illustrating a process sequence ei ner Einlogin- and Menühauptproutine of the system;

8B is an exemplary user interface generated by the log-in and menu routine of Fig. 8A.

9A is a flowchart illustrating a process flow ei ner order command routine of the system.

FIG. 9B shows a first page of an exemplary user interface generated by the job command routine of FIG. 9A;

FIG. 9C is a second page of an exemplary user interface generated by the job command routine of FIG. 9A;

Fig. 9D illustrates an exemplary user interface generated by a Editierform routine of FIG. 9A;

Fig. 9E shows an example of a user interface generated by an edit material type routine of Fig. 9A;

10A is a flowchart illustrating a process flow ei ner scheduling routine of the system.

FIG. 10B shows a first page of an exemplary user interface generated by the planning routine according to FIG. 10A;

FIG. 10C illustrates an exemplary user interface generated by a Auftragsde tailroutine of FIG. 10A;

Figure 11A is a flowchart illustrating the procedure of a Alarmeinstellroutine of the system.

FIG. 11B is a first side of an exemplary user interface generated by the Alarmeinstellroutine of FIG. 11A;

Figure 11C is a second side of an exemplary user interface generated by the Alarmeinstellroutine according to Fig. 11A.

FIG. 11D modifications of an exemplary user interface design it demonstrates according to the set alarms in the Alarmeinstellroutine of FIG. 10A;

Figure 12A is a flowchart illustrating a process flow ei nes machine monitor of the system.

FIG. 12B is an exemplary user interface generated by the machine monitor routine of FIG. 12A;

FIG. 12C illustrates an exemplary user interface generated by a machinery detailed routine of FIG. 12A;

13A is a flowchart illustrating a process flow ei ner job start routine of the system.

FIG. 13B is an exemplary user interface generated by the job start routine of FIG. 13A;

13C is a flow diagram illustrating a process sequence ei ner cutting change routine of the system.

Fig. 13D illustrates an exemplary user interface generated by a cutting change routine of Figure 13C.

FIG. 13E illustrates an exemplary user interface generated by a Neuschnei denroutine of Figure 13C.

FIG. 13F illustrates an exemplary user interface generated by a Neuschnei denmarkenroutine of Figure 13C.

14A is a flow chart representation of a process flow of a machine table routine of the system.

FIG. 14B is an exemplary user interface generated by the Maschinenta bell routine of FIG. 14A;

FIG. 14C illustrates an exemplary user interface generated by a Editierma schin routine of FIG. 14A;

Fig. 14D illustrates an exemplary user interface generated by a Neumaschi nenroutine of FIG. 14A;

FIG. 15A is a flow diagram illustrating a process sequence ei ner user table routine of the system;

FIG. 15B is an exemplary user interface generated by the Benutzerta bell routine of FIG. 15A;

FIG. 15C illustrates an exemplary user interface generated by a user Zusatzbe routine of FIG 15A (or user detail routine).

FIG. 16A is a flowchart illustrating a process flow ei ner general poll routine of the system;

FIG. 16B is an exemplary user interface input generated by the All common interrogation routine of FIG. 16A;

Figure 16C illustrates an exemplary user interface input generated by a sum interrogation routine as an application of the routine of Fig. 16A.

16D illustrates an exemplary result user interface generated by the sum query of Figure 16C..;

FIG. 16E generates an exemplary order detail user interface as part of the interface of Figure 16D.

FIG. 16F illustrates an exemplary user interface input generated by a cutting (cutting element) interrogation routine as an application of the routine of Fig. 16A;

FIG. 16G illustrates an exemplary result user interface generated by the cutting query of Figure 16F.

Fig. 16H generates an exemplary cutting detail user interface as part of the interface of Figure 16G.

17A is a flow diagram illustrating a process sequence ei ner cutting table routine of the system.

FIG. 17B shows an exemplary user interface generated by the cutting table routine of FIG. 17;

Fig. 17C illustrates an exemplary user interface generated by the cutting detail routines of FIG. 17A, and

Fig. 18 is a flowchart showing a process flow of an update or refresh routine of the system, which runs in an invisible frame at the client browser for certain supplied user interfaces.

Fig. 1 shows in schematic form an overview of elements and connections by which the management system of the cutting machines according to the present invention is implemented. One or more cutting machines 1 are arranged, for example, on the operating floor of a device. Each cutting machine 1 is equipped with different outputs and sensors (an example is described in FIG. 2). The outputs and sensors are connected to a data collection device 3 via the input means. 3 Typically, the data collection device 3 has several analog or digital inputs and can be connected to other devices via a bus or an interface. This can provide a signal that contains values for all or some of the inputs. The data collection device 3 can also have analog or digital outputs.

Each data collection device 3 sends its signals to a “virtual machine” (VM) object or component 5 .

In the context of the present description, the terms "component" and "object" have their normal meaning in the field of object-oriented programming and distributed object technology, and in particular distributed calculation. A component can have a single function or a multiple function, and simple and complex examples are described below. A system can contain one or more components. Components can contain one or more objects. Objects usually have one or more procedures (routines) and one or more properties (variables). In the description herein, when "component" is used, more than one object may be present, or the component may be sufficiently complex to be understood as a system. Components can generally query one another to find out characteristics and the type of communication, can make their properties visible to the other components, can handle their own activities or those of other components and can maintain their own state for later use. The VM object or component 5 is preferably an individual software component which contains at least one object which has at least one of the following three functions: interrogating the data collection device by means of a timer or on request, maintaining the queried values and reporting the retained values by the timer or on request. When the VM component 5 reports the retained values, identification information corresponding to the VM component and suitable for the cutting machine 1 is contained. The VM component 5 can be provided on any suitable processor that is connected to the data collection device 3 and capable of communicating with this device.

Each VM component 5 is connected to a "machine monitor" object or component 7 . The machine monitor component 7 may be realized by a search server 9, the processor is connected to all VM component 5 via a report channel 25th The machine monitor 7 is also preferably an individual software component that contains at least one object that has one of the following three functions: Querying the VM components 5 with respect to their status by timer or when querying, sending back a field or a table that shows the machine status contains, according to the timer or query, and writing all queried values and secondary values together with corresponding time (date, time) and identification information into a database which is arranged in a database (DB) server 13 which is connected to the machine monitor 7 is. That is, the machine monitor 7 handles the periodic writing of status information in the DB server 13 and responds to requests for status information. Information previously written is not necessarily overwritten, so the database can also record previous status information.

As a result, a database with current status and / or older status information corresponding to one or more cutting machines 1 is maintained on the DB server 13 . In order to provide the information, a web server 11 is connected to the DB server as well as to the machine monitor 7 . In this context, a web server 11 is an application that has several functions, including answering access via an intranet or Internet connection, providing access and security levels, and translating and executing server-side scripts and requests. The web server serves connected browsers or other clients with web protocol hypertext or multimedia markup documents, which are generally translated in the client browser. However, in the present application, the markup or markup documents are generated dynamically and typically contain display elements, text and inserted hyperlinks that cause the web server to take action, such as supplying a subsequent markup document, querying the database or Processing a server-side script. The markup documents can be generated statically or, in the case of the present invention, dynamically by the web server.

Accordingly, client browsers 17 (operator) and 19 (manager) arranged in the device can access the web server 11 via a monitoring intranet, network or channel 27 . Since each operator browser 17 is connected to the web server 11 , which can read the status information from the DB server 13 and / or from the machine monitor 7 , each operator browser 17 is permitted to provide information regarding an assigned cutting machine 1 via the Surveillance network 27 to consider. That is, even if the operator browser 17 is closely adjacent to the assigned cutting machine 1 , the status information is first transmitted via the data collection device 3 , VM component 5 and machine monitor 7 to the database of the DB server 13 or web server 11 and comes back to the operator browser 17 via the web server 11 and the monitoring network 27 . At the same time, the manager browser 19 may be able to view information regarding any cutting machine 1 of the device via the monitoring network 27 .

The web server 11 is preferably also connected to the internet 15 as a whole via an internet connection 29 . In this way, the manufacturer 21 can query status and historical data from the database on the DB server 13 via the web server 11 . In addition, the operator browser 17 and manager browser 19 can be connected to the server 21 of the manufacturer, which stores, for example, collected and translated cutting machine data and online documentation for cutting machines at different operating devices.

Fig. 2A shows a first exemplary embodiment or the preferred structure for imple mentation of the management system for the cutting machine according to the present invention. Instrumented cutting machines 1 , which are described in detail in connection with FIG. 3, are queried by the data collection device 3 . The data collection device 3 is an area of a monitoring input device which also has sensors or manual inputs by means of which current data can be input. An example of a suitable data collection device 3 is the PC-OPDIO-16I / O-Card from National Instruments Corporation of Austin in Texas, which is an expansion card that fits into a plug-in card slot that connects to the bus (in this case ISA). a personal computer 5.1 is connected. The PC-OPDIO-16 plug-in card has eight optically isolated inputs (for example eight channels of on / off data) that measure digital levels up to 24 V. The optical isolation isolates the computer case from voltage surges, earth loops and other problems. Even if only eight bit information (for example eight on / off states or four on / off states and a sixteen valued (4 bit) variable and combinations thereof) are possible via the PC-OPDIO-16 plug-in card, one can suitable device or plug-in card can be substituted with any number of analog or digital inputs. The data collection device 3 is addressed by the operating system (for example, by programs and objects) of the host computer via the bus using a known device driver.

In the exemplary embodiment according to FIG. 2A, the data collection device 3 is installed in an ISA bus plug-in card slot of the personal computer 5.1 , which can have a known x86 architecture with a suitable display, input devices and network connections. The VM component 5 and the operator browser 17.1 are implemented by the same personal computer 5.1 . In this way, the number of processors required at the operator station is reduced. The VM components run as a single process under a (multitasking) operating system on the personal computer 5.1 and can have a uniform IP address or can have different ports which can be accessed by means of a common IP address. As described here, an IP address, a port under an IP address (or URL, for example) is considered an "identification" to which communication is directed regardless of the physical arrangement. Since every URL corresponds to an IP address, these are considered equivalent. In the preferred exemplary embodiment according to FIG. 2, the VM component is a COM object, encoded according to the Microsoft COM specification (Microsoft Corporation, Redmond, Washington) or preferably a distributed DCOM object according to the Microsoft DCOM specification. COM and DCOM objects run under a variety of operating systems, such as a variant of Microsoft Windows in this case (for example 3.x, 95, 98, NT, 2000, CE or successors). In general, COM objects are used for various component functions on a single computer and DCOM objects are used in a distributed architecture with a multiplicity of network-connected processors or computers which communicate with one another via at least TCP / IP and HTTP addressing. The COM and DCOM specifications and protocols are described in detail on the Microsoft Corporation website (http://www.microsoft.com).

All of the distributed components described herein are preferably network capable at a fundamental level. That is, for every distributed component no need to recognize routines and interact with a network provide transport layer. Each distributed object can be different from other objects Query services without "knowing" where the other object is or which interface is available for the other object. Distributed objects or Components inherently contain (as part of the underlying functionality and the concept of "being distributed") routines for interacting with network trans port layers (e.g. TCP / IP) and each has an (e.g. IP) address or a specific port on a shared IP address over which it is in one Network (e.g. LAN, WAN, intranet and / or internet or the like) can be found. If a component with no distribution functionality is available uses this, for example, via another component with a network transport layer access can be addressed. For example, in place  of a single DCOM (or equivalent) object a first COM (or equivalent) lentes) object with the desired function and a second COM (or equivalent tes) Object used with network transport layer functionality, of which each a unique IP address or specific assigned ports or to with a common IP address.

The VM components 5 will be described in detail later with reference to FIG. 4. It should be noted that in any case the special architecture and software of the exemplary embodiments are only exemplary. Where alternatives are known, they may be given here. However, it is intended that hardware and software with essentially the same functions and the same interaction or comparable interaction be regarded as equivalents. Alternative architectures to x86 (including the Pentium x86) currently available are, without limitation, Intel StrongARM, DEC Alpha, HP Ultra, Silicon Graphics, MIPS, PowerPC, IBM mainframe and emulators or the like, i.e. general-purpose microprocessors and - processors. Alternative operating systems to Windows are without limitation Unix and variants (Linux or the like), Solaris, OpenVMS, Java, Mac OS or the like, i.e. all-purpose operating systems. Alternative methods of ASP for providing application server functionality such as server-side action or dynamic content are also CGI scripts (implemented via C, Perl, Delphi or the like), ChiliASP, Cold Fusion (Allaire, Inc., Cambridge, MA), without restriction. WebObjects (Apple Computer Co., Cupertino, CA), proprietary or purpose-built solutions, or the like. Alternative methods to COM and DCOM for the provision of components, distributed components or object possibilities are CORBA without restriction, for example with IIOP (object management group), Java or JavaBeans, for example with RMI (Sun Microsystems, Inc., Palo Alto, CA), proprietary or purpose-built solutions or the like. In general, DCOM, CORBA / IIOP and Java / RMI show gateway possibilities for mutual cooperation. Alternative markup languages to HTML that can be displayed by a browser include, without restriction, variants of HTML, such as DHTML or XML, subgroups or supergroups of SGML, as well as proprietary presentation languages (e.g. Display Postscript, Envoy), as long as this presentation or markup - Allow languages to have the same or similar level of interaction between user and server. Those who are familiar with this area can use software and hardware tools that are already available to implement the invention described here without major experimentation.

In FIG. 2A, the operator browser 17.1 with the same functions as described above is preferably a “web browser” such as Netscape Navigator or Communicator (Netscape Communications, Inc., Mountain View, CA), Microsoft Internet Explorer or the like, that are capable of querying, receiving, translating and / or executing web protocol files HTML and variants (for example DHTML, XML, SGML), Java or Visual Basic applications, applets, scripts and variants, active X control, specifically plug -in protocols (quick time, shock wave or the like) etc. It should be noted that these standard file types are periodically replaced by new generations of the same specification or replaced by faster and more efficient types with essentially the same functions. Such replacing standards, file types, protocols, language variations and / or new generations of these are expressly to be regarded as equivalent.

The operator browser 17.1 are implemented as a second (multitasked) method on the personal computers 5.1 and have no interaction with the VM components 5 , except preemtives or time-slice multitasking. Each browser has a unique IP address or can have specific connections or ports that are assigned under a common IP address. Even if the VM components 5 and the operator browser 5.1 corresponding to the same cutting machine 1 are both implemented on the same processor as described above, all interactions of the operator browser 17.1 with a cutting machine 1 are carried out over the network, for example via a web server 11 and a machine monitor component 7 .

Each personal computer 5.1 is connected to a network 27.1 . In a geous embodiment before this is a known local Ethernet network. However, it may be another type of local area network, or it may be connected to a wide area network via leased lines, a frame relay, virtual private network (VPN) structures, internet protocol tunnels, or the like. More specifically, the network 27.1 is defined by connecting a set of computing devices arranged within the device in question, that is, a device with a number of cutting machines 1 to be operated and managed together. Even if different connections are shown in FIG. 2 for each VM component 5 and operator browser 17.1 , the personal computer 5.1 can use a single network card in its physical execution and each process interacts with the network protocols via the individual network card. Such network cards, if many components run on the same processor, can handle more than one network (for example IP) address, for example one for each component. Alternatively, if more than one component is active or is implemented by the same processor, the components can interact via different connections at the same IP address. In an advantageous embodiment, the network runs under a TCP / IP protocol, the current standard for Internet connections as well as for some intranets. An "intranet" is usually regarded as a local network that runs under Internet protocols. In this way, both the VM component 5 and the operator browser 17.1 can access the network with a single protocol. Again, subsequent protocols or network standards and / or new generations of them are expressly to be regarded as equivalent.

The network 27.1 also has connections to the machine monitor component 7 , the web server 11 , the database server 13 and the manager browser 19 . The machine monitor component 7 is a further individual process in a "multitasking" operating system, which is realized on a server computer 9.1 , which can be a known server computer with x86 architecture with corresponding display, input devices and network connections. The machine monitor component can have a unique IP address or specific, assigned connections under a common IP address. In a front part exemplary embodiment according to Fig. 2A of the machine monitor 7 is a broad res COM or DCOM object, as will be described with reference to Fig. 5 below.

In the advantageous embodiment according to FIG. 2A, the server computer 9.1 is preferably a computer with x86 architecture, which runs under Windows NT and Windows NT server with Internet Information Server (IIS), all of which are available from Microsoft. Windows NT Server and IIS run as consecutive, sole processes and IIS can translate scripted HTML pages under the microsoft standard known as Active Server Pages (ASP). The IIS and ASP specification and protocols are described in detail on the Microsoft Corporation website (http://www.microsoft.com). In this context, the "web server" is an NT server and the "application server" is IIS. In the description, a web server 11 is considered to have both web serving and application serving functions. However, a subdivision of the functionality between a web server implemented on one processor and an application server implemented on another processor can be regarded as equivalent. For example, the interpretation of script-containing pages on an application server can be carried out on an additional processor which lies between the web server 11 and the database server 13 . In this case, the web server only transmits pages that have been assembled by the application server without translating their content, all HTTP requests for page assembly being passed on to the application server.

In the exemplary embodiments, NT server and IIS together form an example of a web server application server configuration which has the dual functionality of web server 11 as described and the combination can have one or more unique IP addresses corresponding to Combined server and user interface (application) server component or can have several connections under the same IP address. Active server pages are platform-independent in their current implementation and can contain Jscript / JavaScript, VBScript, Perl or other scripts that are interpreted by IIS on the server computer 9.1 . The server computer 9.1 then performs queries, calculations or HTML page assembly as required and offers an HTML page to the connected browser. In the first embodiment, machine monitor 7 and web server 11 run on the same server computer 9.1 . In this way, the number of processors required to collect and store data and to answer queries is reduced. However, each component can be addressed separately via the network.

The DB server 13 in the advantageous exemplary embodiment according to FIG. 2A is an additional computer with x86 architecture on which an ODBC-compatible database is implemented, in this case Windows NT, Microsoft SQL server and / or Windows NT server (all available from Microsoft). The DB server can also be provided with a unique IP address or can have specific connections assigned to it under a shared IP address. ODBC-compatible or differently structured query database servers (for example JDBC-compatible, POS under CORBA) can have various forms and those with essentially the same or similar functions or interactions are to be regarded as equivalent (for example Oracle, Sybase or the like). The DB server 13 responds to queries and the use of standard SQL syntax under ODBC protocols. The database implemented on the DB server 13 is a relational database with various tables and is described in detail with reference to FIG. 7.

The manager browser 19 with the same functions as described above is essentially identical to the operator browser 17.1 in its physical architecture and its connections, except that there is no need to operate a VM component 5 on the same PC. Each browser, operator, manager or the like can have a unique IP address or can have specific connections assigned to it under a shared IP address. One difference between the manager browser and the operator browser 17.1 is the identification and access information which is stored and exchanged between the browsers 17.9 and 19 and the web server 11 , the web server 11 being different from each browser 17.1 , 19 depending on the access and identification information of the browser 17.1 , 19 answers. The manager browser 19 , as described below, has a higher level of access to the database and more and different HTML pages are offered to the manager browser 19 .

The web server 11 , which runs on the server 9.1 , is provided with an internet connection 29.2 for connection to the internet 15 as a whole. Every Internet connec tion is sufficient, for example modem via PPP, ISDN, TI, ATM, Kabelmo or the like. A "firewall" can be provided for additional security at the operating facility without influencing the basic functionality of the system. The Internet connection 29.2 has sufficient bandwidth and speed to carry out a sufficient number of transactions, the web server 11 responding to HTTP connections via the Internet connection 29.1 as well as via network 27.1 .

As noted above, remote users have HTTP access to the web server 11 at an "order desk" browser 23.2 and manufacturer browser 21.2 via the Internet 15 . The browsers 23.2 and 21.2 are essentially identical to the manager browser 19 in their physical structure, except that each is also equipped with an Internet connection and an IP address through which the browsers 23.2 , 21.2 access the Internet and consequently the Have web server 11 . A difference between the manager and operator browser 17.1 , 19 and the instruction table and manufacturer browsers 23.2 , 21.2 is the identification and access information which is stored and exchanged between the different browsers and the web server 11 , the web server 11 differs Lich each browser responds 17.1 , 19 , 23.2 , 21.2 depending on the access and identification information of the respective browser. The instruction table and manufacturer browser 23.2 , 21.2 have a tailored or limited access level to the database and different HTML pages can be supplied to the instruction table and manufacturer browsers 23.2 , 21.2 .

Fig. 2B shows a second embodiment of the management system for the cutting machine according to the invention. In the case of FIG. 2B, the functionality of each component is the same as that of FIG. 2A. However, 2B each VM object or component 5 runs of FIG. On a particular processor 5.2 and has a specific IP address. In this case, the processor 5.2 only needs sufficient capacities to handle a driver for the data collection device 3 , the VM object 5 and the network connection. Such a processor can be an embedded system or a single chip microcomputer. Accordingly, the operator browsers 17.2 run on their own computers or stations, wherein an operator tor browser 17.2 can be used to monitor two cutting machines, the lower two cutting machines 1 being assigned to the lower operator browser 17.2 according to FIG. 2B. The machine monitor component 7 is operated on a specific computer (query server) 9.2 with a unique IP address, such as the web server 11 (which also has its own IP address). The network connection to the DB server 13 is separated from a general network 27.2 . In this way, requests to the web server 11 via the Internet 29.2 , 15 do not require the retrieval of data from the DB server 13 via the facilities of the general network 27.2 . Accordingly, FIG. 2B shows components of the system in a distributed and portable form, which can be arranged differently from FIG. 2, so that requirements for internal resources and processors are handled as required. Other variations are possible.

Fig. 3 is a schematic view showing an instrumented cutting machine 1 and examples of their instrumentation. A candidate for such a machine is the horizontal band saw AMADA HA-700. The instrumented cutting machine is equipped with sensors, detectors, relays and limit switches, all of which are described below as detection channels.

It should be noted that the present system is applicable to any type of cutting or ver working machines is applicable, the cutting or processing elements ver uses that require wear and / or periodic replacement and that require a raw or pre-machined workpiece (in layers or parts) to form workpieces desired size or shape. In the context of this description Exercise includes such a "cutting element" processing tools such as band saw blades, circular blades, blades that can move back and forth, jet heads or nozzles sen, laser heads or other high energy heads, milling tools, grinding tools, Drilling tools or the like. The band saw described here as an advantage  Embodiment is just one example of one type of cutting machine in which the present invention is applicable. However, the present description shows exercise features that particularly show an advantage for band saw machines, and the peculiarity of the band saw-specific features, for example with regard to the other cutting machines are not claimed as part of the invention.

The instruments (channels) of the instrumented cutting machine 1 generate control data. Control data or "status" describes data that corresponds to physical conditions, signal level conditions or other conditions and is current or essentially in real time.

Channel D1 transmits an on / off signal for power and can be taken directly from the on / off switch as an alternating current and reduced as a 1 bit digital voltage. That is, if necessary, a step-down transformer and / or capacitor can be used to convert the AC power, for example, into a 1 bit 24 V digital signal. Accordingly, this channel provides as a binary indication whether the cutting machine 1 is switched on or off.

Channel D2 supplies a work or idle signal and can be taken as a 1-bit digital voltage directly from the work / idle light on the control panel of the cutting machine 1 or as a reduced AC current. This means that this channel provides a binary display of whether the cutting element or the saw blade is working or is idle, i.e. whether the saw blade is moving or stationary.

Channel D3 supplies an AUTO or MANUAL signal and can be taken as a 1-bit digital voltage from an AUTO / MANUAL switch on the control panel of cutting machine 1 . If the saw is in a manual mode, the machine stops as soon as the saw head reaches a lower limit position after cutting the workpiece. In the auto mode, feeding and cutting takes place automatically, so that the saw feeds the workpiece and cuts it with a preset length. This channel provides a binary display of the mode set on the cutting machine.

Channel D4 records the cutting edge speed and can either be taken from a cutting speed setting potentiometer or a cutting speed meter on the control panel of the cutting machine 1 either as an analog voltage level (subsequently converted A / D) or as a multibit digital value. The output is therefore a variable value corresponding to the cutting speed.

Channel D5 supplies a cutting voltage signal, which is taken from a cutting voltage adjustment potentiometer or a cutting voltage measuring device on the cutting machine 1 either as an analog voltage level (subsequently A / D converted) or as a multibit digital value. The output is therefore a variable value corresponding to the cutting tension, which is set mechanically on the cutting machine.

Channel D6 outputs a contour status signal ("round" or "square") and can be removed as a 1-bit digital voltage from a "round / square" switch on the control panel of the cutting machine 1 . The contour status reflects the shape of the workpiece (round or rectangular) and changes the cutting machine actuation parameters depending on the status. The output is therefore a binary value corresponding to the contour status that is set on the cutting machine.

Channel D7 outputs a sinking speed signal and can be entered manually as a valve position on the operator browser 17 or can be taken from a valve position / sinking speed setting potentiometer on the cutting machine 1 . The sampling takes place as an analog voltage level (then A / D converted) or as a multi-bit digital value. In a preferred exemplary embodiment, the positions of a flow control valve (FCV) and / or a pressure control valve (PCV) on the head sink hydraulics determine the head sink speed of the saw and these values can be entered manually into the database, for example by the operator.

Channel D8 outputs a cutting rate signal (for example cm ² / min.) And can be taken from a cutting rate measuring device on the cutting machine 1 either as an analog voltage level (subsequently A / D converted) or as a multi-bit digital value. The output is a variable value corresponding to the detected cutting rate.

Channel D9 outputs a cutting pressure signal and can be taken from a cutting pressure regulating potentiometer on the cutting machine 1 either as an analog voltage level (subsequently A / D converted) or as a multi-bit digital value. The output is therefore a variable value according to the cutting pressure set by the operator.

Channel D10 outputs a cutting depth signal (cm) and can be taken from a cutting depth setting potentiometer on cutting machine 1 either as an analog voltage level (then A / D converted) or as a multi-bit digital value. The output is therefore a variable value corresponding to the cutting depth set by the operator.

Channels D11 and D12 correspondingly transmit hydraulic fluid level and cutting fluid level signals, each of which is derived as a one-bit digital voltage from a high / low flow limit switch in fluid tanks of the cutting machine 1 . Each output is therefore a binary value or a variable value corresponding to the detected fluid level.

Channels D13 and D14 output a lower (L) and upper (H) from the limit switch signal and can be taken directly as one-bit digital voltages from the L / H limit switch or indicator lights on the control panel of the cutting machine 1 . Each output is therefore a binary or alarm value corresponding to excessive leak levels being detected.

Channel D15 provides a leak detection ON / OFF signal and can be taken as a one-bit digital voltage directly from the leak detection ON / OFF switch or indicator lamp on the control panel of the cutting machine 1 . The output is therefore a binary value or alarm value corresponding to the status of the leak detector as detected.

Channel D16 outputs a runout alarm ON / OFF signal and can be derived as a one-bit digital voltage directly from the runout alarm indicator lamp on the control panel of the cutting machine 1 . Generally, the cutting machine is controlled so that all machine operations are stopped for approximately 90 seconds after a runout alarm (when the H or L runout limit switch is actuated). The output is therefore a binary value corresponding to the phasing out alarm status set by the operator.

Channel D17 outputs an EMERGENCY STOP status signal and can be derived as a one-bit digital voltage directly from the EMERGENCY STOP on the control panel of cutting machine 1 . The EMERGENCY STOP button is a blocking switch which overrides many activities of the cutting machine 1 . The output is therefore a binary or alarm value corresponding to the detected EMERGENCY STOP status, which is set, for example, by the operator.

Channels D18, D19 and D20 output status signals for a limit switch of the control panel door, a limit switch of the front cutter blade wheel and a limit switch of the rear cutter blade wheel, and can be derived as 1-bit digital voltages directly from the limit switches of the cutting machine. Each of these limit switches is a lock that overrides certain functions of the cutting machine 1 . This output is therefore a binary or alarm value corresponding to the limit switch status as detected.

Channel D21 outputs a material position signal and can be derived from a material position potentiometer in the cutting machine 1 either as an analog voltage level (subsequently A / D converted) or as a multi-bit digital value. The output is therefore a variable value according to the material position entered.

Channel D22 outputs a vibration level signal or a vibration alarm signal and is attached to the workpiece clamp and hold by a vibration sensor direction either as an analog voltage level (then A / D converted)  or as a multi-bit digital value or as a one-bit digital voltage for the alarm headed. The output is therefore a variable value or a binary or alarm value corresponding to the vibration level or an excessively detected vibration level.

Accordingly, the monitoring data are representative of the machine status. The monitor data, as expressed in the above channels, contains On positions for machine functions (run-out limits), operating parameters of the machines to display how the cutting elements and the machine the Ma Process material (e.g. sinking speed, cutting pressure, cutting depth, contour status, cutting speed, cutting tension). Include further the monitoring data a load of the machine, control recordings, whether functio machine are active (e.g. ON / OFF; working / idling, coasting detection ON / OFF), alarm and security detection, which generally the machine stop ne (e.g. leak alarm, EMERGENCY STOP, door limit switch, wheel limit switch, vibration alarm), status recordings for feedback via Cutting or work activity (e.g. cutting rate, vibration), secondary Consumable levels that indicate the remaining supply (e.g. Hydraulic fluid level, cutting fluid level), and material processing parameters display the condition of the material in the machine (e.g. material position). From the monitoring data and identification data can Use data are generated, for example cutting edge use (at least both working hours and working area).

Fig. 4 is a flow chart corresponding to a distributed and portable (for example DCOM) object suitable for use as a VM object or Component 5. It should be noted that the VM components 5 are generated, modified or initiated by the machine monitor 7 in accordance with the exemplary embodiment present, in each case as necessary, for example shortly after adding a new cutting machine 1 , identifications for this purpose are stored in the database on the DB Server 13 added.

The VM component 5 or "collection object" is an individual component that reads the data from sensors and raw voltages via the monitor input device (for example data collection card 3 and sensors / channels of machine 1 ) and stores them until requested. The VM component 5 is consequently connected to the machine 1 and the MM component 7 and operates under the self-control and control of the MM component 7 . One VM component 5 per machine 1 is preferred. However, a single VM component 5 can alternatively collect data from a subset of the machines 1 (for example, when a group of machines 1 is considered a work unit).

The method of Fig. 4 is repeated at a predetermined cycle, with play, once every second. In step VM2, the VM component 5 reads the status of the I / O device (input / output device). In this case, a usage table is filled with the raw data of the data collection device 3 .

In step VM4, the VM component 5 generates a status table that matches the parameters of the table on the DB server 13 and fills the status field with the corresponding values.

In step VM6, the VM component 5 transmits the filled status field with status information to a calling component (if there was a request regarding the status table), in this case to the machine monitor 7 . Then the cycle is repeated.

Consequently, the VM component 5 performs at least two functions: reading the status table of the cutting machine 1 and responding to inquiries about a new status table with status information.

Fig. 5A and 5B are flowcharts representative of a quantity of distributed and portable (for example DCOM) object or a component suitable for use as Maschinenmonitor- (MM) Component 7. The MM component 7 performs several functions: reading the status of all cutting machines 1 (via the VM components 5 ), arranging the status information in a transfer table of an appropriate format, minor conversions into secondary data for fields in the transfer table, writing the Transfer table to the database, and responses to requests for a new transfer table with current status information.

The MM component 7 is a single component that queries the VM components 5 and transmits the data. The MM component 7 is consequently connected to the VM components 5 , a user interface server component (web server 11 ) and a database server component (DB server 13 ). The MM component 7 works under its own control and controls the user interface server component. A single MM component 7 is preferred. However, more than one can be used, for example an MM component 7 for each different group of VM components 7 (for example if the capacity of a single standardized MM component 7 is not sufficient).

The method of FIG. 5A (regular and principal update) is repeated according to two predetermined cycles, for example, a first cycle for updating the database (for example, every second), and a second cycle for the production of VM components 5 at all Schneidmaschi NEN 1 ( for example, every hundred cycles of the first cycle). The method according to FIG. 5B (response to status query) is carried out when queried.

In step MA2 of FIG. 5A, the MM component 7 checks a counting device to determine whether VM components 5 should be created or regenerated on the processor of each cutting machine 1 . The MM component 7 will, for example, carry out this activity at any point in time at which the count can be divided by 100.

If the count has reached a threshold value, a branch is made to step MM4, where the MM component 7 reads the table of the machines (for example see FIG. 6), including the values (as described in detail later) of the machine ID, machine name and Machine IP (e.g. identification, name and network address). Regardless of whether new machines have been included in the table, the MM components are destroyed or the existing VM components 5 are overwritten by each candidate processor on each cutting machine 1 and written and executed from a new VM component 5 on each machine 1 (each VM Component has a unique identification and address). The MM component then returns to the main MM routine in step MA6 and updates the tables.

In step MA6, the MM component 7 sends a request to each VM component 5 for a new status table of the machine status. After receiving each status table, the MM component 7 stores the received status table and, for each VM component 5 (each cutting machine 1 ), increases a transfer table with data corresponding to fields in the database. Minor status conversions and generation of secondary data values are performed at this point, ie, for example, whether the status of the cutting machine 1 has changed from operating to idling during the last cycle, the MM component 7 generates and records an end time in the transmission field -Database table input for displaying the time and date on which the cutting machine 1 was stopped. Other secondary data are generated as required.

Depending on the characteristics of the records in the database, you can such records are overwritten (since they contain current status), where "historical" records (e.g. the time of a change in a status record or the time of a status record, if this remained unchanged) can be written as a new recording.

In step MA8, the MM component 7 increments the count and the process is repeated.

In step MB2 of FIG. 5B, the MM component 7 creates a new table that is suitable for the status of all machines 1 .

In step MB4, the MM component fills the table with the latest results of the regular update (for example step MA6). In step MB6, the MM component transmits the table to the requester, in most cases the web server 7 .

In Fig. 6 is an exemplary table structure is made of a relational database for storing, Association and retrieval of data for the identification of the cutting machine, the contract, and other relevant status information represents. As usual, underlined spaces are used in the variable names to indicate a sub-variable, record, or field name, as is apparent from a description thereof.

The database server component (e.g. DB server 13 , Fig. 2A or 2B) is a stand-alone program that keeps the database. The database server component reads and writes to the database, maintains relations between recording fields, copies and mirrors values between associated fields, generates data in some fields based on functions and contents of other fields, responds to queries by searching according to the specified condition and organizes or sorts results before submitting them. The database server component generally does not take any action on its own, but could be set to archive, collect and ratio data under preset conditions or at certain times. The database server component is connected to the MM component 7 and the user interface server component (for example web server 11 ). The database server component generates data based on inputs and is therefore used to combine and connect monitor data and identification data to generate usage data.

Identification data is data that describes the characteristics of the machines, orders, Describe users and cutting elements or tools. Identification data ten include name, date, descriptive information, characteristics and Instructions. The identification data also capture a connection between the machines, orders, etc. Identification data is typically through  to enter a user manually, but can also be created or created as Stan default value can be assigned. Identification data usually do not include that current status data or monitor data (monitoring data).

Core tables contain order, machine, cutting edge, user name and order Machine usage tables. "Core Tables" does not mean that this Ta belle is necessary, but only that it is preferred.

The order table contains information related to specific orders. An order is a work instruction for a specific product configuration for its manufacture. The records in the order table are preferably first indexed by an order ID field, to which a specific code is assigned when the record is generated. Fields in the order table contain:
Login: records of the user who created the order and which were taken from the login field of the user name table at the time the order was created;
Shape type (Shape_Type): Records of the shape of the material to be processed are limited to entry in an editable secondary look-up table (shape);
Material type (Material_Type): records of the material to be processed and limited to entries in an editable secondary look-up table (material);
Job number (Job_Number): records of a job number to identify the job in the work schedule and in other records;
Order extension (Job_Extension): Records of order extension, modification or type / class information to identify the order;
Order date (Order_Date): records of the date on which the order was entered in the system;
Transmission to (Shipe_to): records of a target of the processing product for delivery;
Size X, Y, W, H (Size_X, Y, W, H): records of the physical dimensions of the material to be processed;
Due Date (Due_Date): records of the date on which the order is to be completed for delivery;
Special Instruction: records of any comments that a person looking at the order record should be made aware of;
Status: records of the current status of the job, limited to waiting (ie, entered into the system but not yet started or interrupted); Processing (ie, currently processed on a cutting machine); and completed (ie, completed and ready for delivery);
Cut length (Cut_Length): records of the length to which the workpiece is to be processed;
Quantity: records of the number of pieces to be produced;
Cutting area (Cutting_Area): records of the cross-sectional area of the material, which vary in size with the corresponding dimensions, see above, calculated or can be entered directly;
Number of bundles (Bundle_Number): Records of the number of material parts in a bundle for simultaneous cutting;
Lock: records of whether the record (or alternatively the locked or unlocked status) can be changed by a lower level of access privilege (ie whether an operator can change the record or only a manager);
Instructions (Other_Instruction): records of written processing instructions to be seen by an operator; and
Runs on machine (Run_On_Maschine): records of the machine ID of the machine on which the job is to be processed and limited to the machine IDs in the machine table.

The machine table contains information related to the cutting machines of the factory equipment. The records of the machine table are preferably primarily indexed in a machine ID field to which a specific code is assigned when the record is generated. Fields in the machine table are:
Machine name (Machine_Name): records of the name or number of the cutting machine according to general knowledge in the facility;
Model name (Model_Name): records of the type or model of the machine by, for example, model name or manufacturer or product code;
Machine IP (Machine_IP): Recording of a unique (static) IP address on the network to address the machine. That is, the VM component 5 of the corresponding machine 1 can be addressed via the IP address for this machine and communicated with it.
Cutting edge ID (Blade_ID): Recording of the cutting edge currently installed on the machine limited to cutting edge ID entries in the cutting table; and
Current job ID (Running_Job_ID): records of the cutting machine's job currently being processed and limited to the job ID entries in the job table. It should be noted that in this embodiment only one job is assigned to each machine. However, the use of a multi-valued field, for example in the work machine field of the job table and the current job ID in the machine table, will allow jobs to be split between the machines or the machines to process more than one job.

In connection with cutting machines are cutting blades or others Cutting elements a consumable element. They are subject to wear, ver deterioration and failures due to heat, tension, fatigue, over load or accumulation of cutting products or other by-products. Different types, brands and a variety of cutting elements work different. Furthermore, the same cutting element will be different on correctly configured machines and not correspondingly configured dimensions seem to behave.

Accordingly, there are reasons for a cutting element to fail or to be replaced the lifespan of each cutting element and the time between Failures important, as useful data regarding machine and cutting Work performance as well as regarding a selected cutting program. Furthermore, the cutting elements can be returned to the inventory and also at reused on another job or on another machine be used if they are still of sufficient quality.

Such a "cutting element" can of course be a band saw blade, a circular blade, a reciprocating blade, a milling or drilling bit, a nozzle or print head, a laser or another high-energy cutting head. The cutting table contains information depending on cutting in the inventory, in use and after use in the factory facility. The records in the cutting table are preferably primarily indexed in a cutting ID field, to which a clear code is assigned when a record is generated. Fields in the cutting table contain:
Type name (Type_Name): Recording of the cutting type (e.g. model name) limited to entries in an editable, secondary look-up table
(Blade_Type: Type_Name)
Total working time (Total_RunTime): Record of the accumulated hours of activity of each cutting edge;
Total cutting area: (Total_CutArea): Record over the total cutting areas (cross-section) of each cutting edge;
In use (In_Use): Record whether the cutting edge is currently in use;
Use by (In_UseBy): recording of the machine in which the cutting edge in use is installed limited to machine ID entries in the machine table;
Add date (Add_Date): records of the date on which the cutting records were added to the cutting table;
Date of the remover (Remove_Date): records of the date on which the cutting edge was removed from the company;
Keep: Record whether the cutting edge is still good for working after real distance;
Serial number (Serial_Number): Record of the serial number of the cutting edge;
Cutting edge brand (Blade_Brand): Recording of the cutting edge manufacturer limited to entries in an editable, secondary look-up table (Blade_Type: Type_Name: Brand);
Comment: Record of, for example, reasons for removing the cutting edge;
Size: Record of the size of the cutting edge; and
Pitch: Recording of the number division of the cutting edge.

The user name table contains information related to the users of the system. The records in the user (user) name table are preferably indexed first in a login field, to which a unique code is assigned when a record is created. Fields in the username table are:
User ID (User_ID): Recording via a unique user name for login to the system;
Password (Password): Recording of a password corresponding to the user ID for login of the system;
Name (Fullname): Record of the full name of the user for display and for reporting purposes; and
Task (duty): Recording of the access level or the user privileges of the user according to the job responsibilities of the user.

Usage data, as described below, are generated or entered directly give and show the use of resources (machines, cutting, users in Connection with orders). Consequently, the usage data, status or Monitoring data included when the specific monitoring data is displayed how the resource was or will be used. The usage data contain if accumulated or historical data that is between different times periods (including the present), or show a sta tus at a certain time.

The job machine table (Job_Machine_Usertable) contains information related to the current job that is currently running on a cutting machine in the factory. The records in the order machine usage table are preferably primarily indexed in both an order ID and machine ID field, which correspond to those in the order and machine tables. Since processing orders are processed on one machine, each current processing order has both a corresponding order ID and a machine ID. Fields in the order machine usage table, even if not shown in FIG. 6, can have fields corresponding to all acquisition channels D1 to D22 (see FIG. 3) that are updated with the status of such channels, as in the following b 70790 00070 552 001000280000000200012000285917067900040 0002010002305 00004 70671. In the table, those fields that have the same name as the channels D1 to D22 described above contain updated values for detection on the channel. If the channels capture binary, on / off, or true / false values, the fields are Boolean fields. If the channels record variable values, these can be integer or floating point fields. In addition to the channel fields, the order machine utilization table has the following fields:
Start time (Start_Time): Record the last time at which a specific machine and cutting edge was started;
End time (End_Time): Record the time at which a specific machine and cutting edge was stopped. This information can be empty if the machine is still working.
Runtime (Run_Time): Record of the accumulated runtime of a machine in the current work section, which is reset for a new start time, the runtime no longer increasing when the machine is stopped.
Cutting edge ID (Blade_ID): Recording of the cutting edges used for the current job / machine combination is limited to cutting edge ID entries in the cutting edge table.

The alarm table contains information related to alarms (alarms or highlighting) set by a user. The records in the machine table are preferably primarily indexed in an alarm ID field, to which a unique code is assigned when a record is generated. Fields in the alarm table are:
Alarm field (Alarm_Field): Recording of the field in which the system indicates an alarm or a highlight when the field appears on a user interface or a page;
Alarm type (Alarm_type): Record whether the alarm is a highlight or an alarm;
Icon Position (Icon_Location): records the position of the alarm attached to the page (for example, top, bottom, a wide picture);
Highlighting type for a highlighting (Highlight_Type): recording which manipulation of the existing recording information is carried out (for example style, color, flashing, colored background text or colored icon);
Threshold field (Threshold_field): records of the field that is checked for specified conditions for triggering an alarm;
Conditions: records the conditions under which the threshold field triggers an alarm (contains <, <, =, or the like); and
Threshold value (Threshold_Value): Record of the value against which the threshold value field is compared to generate an alarm (numerical or text value or "conflict" with job assignment or other conflict rules, as briefly discussed below).

Furthermore, several look-up tables are used to make lists of possible ones Save field entries. This includes material, shape, cutting type and cutting denmark in the corresponding look-up tables. These tables are editable and are used to use fillable list entries, for example from a list. Accordingly, the database stores records conditions of the order, the machine, the cutting edge, the user and the current status properties. As described in detail below, the Database partially represented, queried or events caused by the content of the database.

FIG. 7 shows the activity of a user interface server component - web server 11 according to FIGS . 2A and 2B - during the construction and provision of a page with dynamic content. As noted above, the web server 11 is a Windows NT server with an Internet information server, but can be any alternative web server 11 that is capable of translating dynamic markup documents on the server side and can be operated on any suitable platform. The server 11 with its software enables dynamic content and database connections. In an advantageous embodiment, a "web server" is used. But any device for supplying a responding client with flexible and dynamically changing user interface elements and for translating instructions contained therein can be regarded as equivalent.

The user interface server component (for example application or web server 11 ) is a single program which controls how a user interface is presented to a client. It also does most of the analysis work known as the "application server". The user interface server component is connected to the MM component 7 and the database server component (for example DB server 13 ) and to clients (for example browsers 17 , 19 , 21 , 23 ) and can receive status data from the MM component 7 , identification data from the database server component and usage data of query the database server component or generate usage data. The user interface server component is self-controlled and can also be addressed by instructions from the client. Depending on the instructions of the client and modifying conditions including the queried data itself, the user interface server component can generate dynamic content. The dynamic content can provide further choices for the client.

The dynamic content or dynamic, interactive user interface element present data to the client, which depend differently on conditions. The present tated data contain further options for generating dynamic Content. One condition (not exhaustive) is user or user access level vel, query conditions, alarm and functions actuated by queried data, the amount of data queried or whether dependent data exists. The dynami The content operates on the basis of fundamental rules, for example the requested offered content may not be fully variable. Basic rules and conditions included Titles displayed on the page and the output format of those to be displayed Data. The appearance of the output is not critical. For example, with an In structure with or without conditions, the dynamic content output depends on Inputs and rules from and the output will be acceptable in everyone formatted its appearance format.  

This routine summarizes the steps for the dynamic creation of a hypertext page for offering to a client browser and steps that take place when a user interacts with this page on the client browser. In this sense, the build UI routine represents distributed activities, both from the server and the client. The routine generally reflects the "build UI" and subroutines of Figures 8A, 9A, 10A, 11A, 12A, 13A, 14A, 15A and 16A, although some functions are specifically shown in each figure.

In step S25 ( FIG. 7), the web server 11 checks the work field of the user called: work record entry corresponding to the logged-in browser. Each de group of user interfaces described here is set to an appropriate working level. For example, a "add user page", as described with reference to FIGS . 15A to 15C, may only be permitted to those users with administrator work. As another example, a set of "order order pages" as described with reference to FIGS. 9A through 9E may be edited by both the administrator and supervisor, but may not be allowed to the operator. If the user (client browser) access level (work) is suitable, proceed to step S26. If the access level is prohibited, the process continues to step S25A, where a simple page or login is requested and offered to the client.

In steps S26 and S27, the web server 11 looks at the file extension of the file offered to the requesting browser. For ASP, if the file extension is for example .html or .htm (which indicates that the file is a static html page), the web server 11 transmits the file to the requesting browser (S31) and returns to the waiting state with regard to one next request (not shown).

However, if the file contains code segments that must be interpreted by the web server 11 (for ASP, these are identified by file endings such as .asp or .asa), the web server 11 opens the file and searches for brands that contain the code or scripts on the server side mark (S28). For ASP, each area of an ASP code or included script is enclosed by "<%" and "% <". If no code or script is found, even if the extension shows dynamic content, the file is offered as a standard HTML page (step S29, transfer of control to step S31).

If brands are included, the web server 11 evaluates the code (S30) and takes any necessary measure, for example replacing the code with HTML code and enclosed dynamic content. It should be noted that the fields and records that are to be offered, similar to the pages themselves, are filtered according to the access level (for example, the task field of the user name table assigned to the currently logged in user / browser). In this way, for example, pages used for editing can only be used for display by deactivating links for "save" or "confirm", as described below. In general, sensitive information is filtered out and editing options for lower access levels (for example operator) are deactivated, while higher access levels (for example supervisor, administrator) are given more editing capability.

In the context of the present description, a page formation area of a "Build UI" routine (e.g., FIGS . 8A, 9A, 10A, 11A, 12A, 13A, 14A, 15A and 16A and corresponding routines, even if not shown, for the remaining, described "detail" pages) according to the dynamic content code (for example ASP) carried out in the relevant "page". Since the information content and not the "page" layout or its aesthetic design is significant, the discussion in the present description of the user interface is limited to inputs, outputs and actions performed, even if examples are given for some "page" layouts. In the "Structure UI" routine, which will be described below, at least six types of information are used as inputs and outputs (text, highlighting, alarm, editing, link, script).

In each drawing, representative of a "build UI" operation is that shown Information in rounded boxes in connection with the "Structure UI" operation shown. "Text" information contains non-editable text or graphics output information mations (S30.F4, S30.F1). For example, a word, a number, or a gra  phical representation (icon or the like) of data offered to the user. "Highlighting" and "Alarms" refer to additional indicators, according to de another piece of information is important. Examples are flashing, changing colors, attached banners, sounds or the like. In the present description Use "highlighting" to indicate modifications to other information det while "alarm" is used to display additional information added det. For example, "highlighting" includes a change in the color of "Text" or "Link" or an emphasis on an "Edit" box (to indicate missing Information), while "Alarm" contains heading banners or additional text (S30.F5).

"Edit" information refers to empty fields that are to be filled with text information by the user, or to lists of information from which one or more elements are to be selected. The lists can be presented in many ways. Standard procedures include dropdown menus, "radio" buttons, check boxes or text list boxes (S30.F2). "Link" information relates to underlined text, buttons or icons which, when selected by the user, carry out an additional action (S30.F3). "Script" information relates to contained scripts (code segments) of the supplied pages (S30.F6), which are, for example, on the browser in an event-driven manner (for example when a link is clicked, when a time expires, when a certain condition is reached ) or run continuously invisible (not shown). An invisible image or invisible frame can be used to continuously update or refresh a user interface (as described below with reference to FIG. 17).

The resulting file, dynamically assembled, is transmitted to the requesting browser, which is viewed as a user interface interpreting component. This user interface interpreting component only shows the dynamic content to the user and responds to the user interface server component activity, interprets the action that is being taken with respect to the user interface shown, and transmits the instructions to the user interface server component (web server 11 ). The user interface interpreting component (client browser) accepts the link activation and the data entry. The data input is fed to the user interface server component (web server 11 ) in the format specified by the supplied user interface. Links indicate an action that should be performed by the user interface server component (web server ver 11 ). If the action is performed locally, the user interface server component (web server 11 ) can be viewed as if an area of its functionality is distributed over the user interface interpretation position, for example the user interface interpreter (client browser) contains a user interface server component with limited function (suitable for processing local scripts or routines).

In step S31, the browser arranges the page as in the specified markup Code specified. In step S32 the page is displayed and any necessary Script, which is specified when the page is offered for processing, is on the browser operated on the side. It should be noted that "page" is not necessarily a full picture side is. Structured markup language such as HTML allow simultaneous Dar position from several sides (for example as a frame) or, as already mentioned notices, in invisible representation (a hidden frame that specifies a Function).

Fig. 8A shows an exemplary flow diagram for the process (preferably framed) in which a log-in and menu page assembled and a requesting browser is available. The web server 11 generates links for further actions.

In step S2, a "homepage" user interface is presented to the client browser for login purposes. An exemplary page is shown in FIG. 8B. It should be noted that a client browser within a facility has the IP address or URL of this page as the "homepage" of the browser software, and a client browser outside the factory facility has access to this page via a corresponding HTTP address, this access theoretically can be done from anywhere in the world (under the restrictions of the respective security and firewall measures in the factory facility). The login interface has fields for user SD and password.

In step S4, a user ID and password with valid entries in the User name table compared. If the user is given access, the Continue to step S6. If a suitable user record does not exist, the login screen is presented again. Of course, after a request measured number of new attempts the system should be set so that it rejects further access attempts.

If the user is granted access, the browser receives the corresponding IP Address an access level corresponding to the corresponding task field in the Username table. This access level is used to restrict the offered pages and to limit the fields offered on the page. For example, users, supervisors and external participants have different ones Tasks or work and access level. Administrative work allows access to essentially all parts of the system.

In step S6, a user interface with corresponding menu links is offered. The menu links are preferably displayed in a secondary frame that remains active with the client browser, even if other pages are requested. Fig. 9B shows a job order user interface and also corresponding menu links along the left side. When a link is activated, the corresponding routine is called up, for example the corresponding user interface is queried by the web server 11 . Steps S6 to S24 are therefore to be viewed in such a way that they are continuously offered to the user via the frame and any other routine can be interrupted by activating one of these links, as described here (when the browser sends a new http request to the web server 11 , most of the work in progress is interrupted). Step S8 requests a job request routine as described with respect to FIG. 9A. Step S10 requests a scheduling routine as described below with reference to FIG. 11A. Step S12 requests a monitoring routine as described below with reference to FIG. 12A. Step S14 requests a machine table routine as described below with reference to FIG. 14A. Step S16 requests a user table routine as described below with reference to FIG. 15A. Step S18 requests a query routine as described below with reference to FIG. 16A. Step S24 requests a set alarm routine as described below with reference to FIG. 11A. In any case, the program returns to the menu link step S6.

FIG. 9A shows an exemplary method sequence in which an order request page is assembled and offered to a requesting browser and the web server 11 generates links for further actions.

Note that the embodiment is a distributed system and the Processing takes place at different points in the system. Even if a Flowchart shows a continuous flow of logic and process flows shows, the flowcharts are still marked with indicators after which one Processing is passed from one processor to another, for example from Web server to a browser, from the browser to a database, etc.

In step S8.2, a UI routine for setting up an order request is carried out, in particular for setting up a first page of the user interface for the order request. The "build UI" routine generally corresponds to the routines described earlier in the description with reference to FIG. 4. After completion of the "construction UI" routine, the complete file is fed to a browser, which interprets its content as a form that contains the designated information. An example of an appearance of a corresponding form is shown in FIG. 9B. "Edit" fields are provided for, corresponding to fields in the order table (database tables according to Fig. 6), order number (Job_Number), order tag (Job_Extension), order date (Order_Date), due date (Due_Date), send to (address or Customer - Ship_To), Form (via Sha pe: Shape_Type), Material (via Material: Material_Type), and Machine (Run_On_Machine). Both form, material and machine are provided with a list (generated from form, material and machine tables) from which valid entries can be selected.

If the form is displayed on the received browser, at least three hyperlinks are provided: "Next step", "Form", and "Material" (S8.4). The page offered contains a routine that rejects the form if an order number is not entered (S8.6). The shape and material links are intended to add new shapes and materials to the source database. If the form link is activated (S8.8), a user interface is offered to enable the entry of a new form. The database will be updated (Shape: Sha pe_Type) if appropriate information is entered. Fig. 9D shows a suitable form for entering a new form. If the material link is activated (S8.10), a user interface allows the entry of a new material and the database is updated (Material: Material_Type) if appropriate information is entered. Fig. 9E shows a suitable form for entering a new material. If "Next step" is activated, a second page is offered to the requesting browser (S8.12).

An example of the appearance of a second page of a suitable form is shown in FIG. 9C. As noted, "edit" fields corresponding to fields in the order table for the sizes (Size_X, Y, W, H), the cutting surface (Cutting_Area), the cutting length (Cutting_Length), quantity (Quantity), number of bundles (Bundle_Num) and special instructions (Special_Instruction) are provided. The cutting area can be calculated from size measurements. In such a case, a graphic for displaying the size measurements depends on the previously selected shape (from UI page P1, S8.2) and is selected from a catalog of corresponding graphics. Corresponding size entry fields appear for shapes in the catalog, for example a tube shape allows the entry of inner and outer diameter or an I-beam shape allows entry of height and width. The cut area is then calculated according to a corresponding formula. At the same time, standards of X, Y, W or H sizes appear for shapes that do not have a specific surface formula, and the cut surface can be entered directly.

When the second page is displayed on the receiving browser, at least two hyperlinks are provided: "Save" and "Back" (S8.14). If activated, the return link is used to display the first page of the order form with the previously entered values in each field. In this way, the user can edit both sides. If the memory link is activated (S8.16), all data stored in each field is transmitted to the web server, which stores this data as a new record under an order ID in the order table (database tables in FIG. 6). It should be noted that when a new job record is entered, a unique job ID is generated and written and the fields for status and lock are given default values (for example "wait", "wrong").

FIG. 10A shows an exemplary process flow according to which a Planungszu sammenfassungsseite assembled and a requesting browser is offered as well as links are generated for further actions.

In step S10.2, the web server checks for input filters and sorting status tus. The filters or sort status are the default values when first offered of the pages are specified and are described below.

In step S10.4, a setup user interface (UI) routine is carried out, in particular for the setup of a user interface for the planning summary page. The "build UI" routine generally corresponds to the routines described earlier in the description with reference to FIG. 7. After the "Auf bau-UI" routine has ended, the complete file is sent to a browser, which interprets its content as a form with the information displayed. An example of the appearance of a suitable form is shown in FIG. 10B.

As noted, "text" fields are provided corresponding to fields from order and user name tables (database tables according to FIG. 6) for order (Job_ID), material (material), shape (shape), size (Size_X, Y, W, H) ), Quantity (Cut_Length), due date (Due_Date), made on (Run_On_Machine), operator (via username: login: fullname) and status (status). Each occurrence of a status value is highlighted according to the parameters specified in the status. In particular, an icon corresponding to a status light is changed in color depending on the status (for example green, white). Initially, all field values for all order records are arranged on the page, even if a second or subsequent iteration of the page offered can only show selected records modified by sorting and filtering conditions.

"Edit" fields are provided for sorting and filtering conditions. For example a "sort" field can have a list of fields to which a sort is based is reversible, in this case a list of three fields (material, date or open carrier number), selectable by a "radio" button. Of course, the plan can alternatively sorted by more than one button and on each Field. A "filter" field can have a list of field conditions or values, from which records are selected or excluded, in this case the status field can filter the records (to display only such records drawings that are waiting, processing, or finished) cash through a box. Of course, the plan summary can be by more than one Condition and be filtered on each field.

If the form is displayed on the received browser, many Hyperlinks offered: "Update", "Next page", / "Previous page", "Detail" for each recording and "Finished", "Waiting" or "Processing" for each Recording depending on the status (S10.6).

There are more records than can be displayed on a single page the first page only for example the first 20 records. If the "next Page "or" Previous Page "link is activated, recording will start from the last record shown on the first page and the planning together Version is built up and again using the same routines shows, except that the previous records are not shown.

The detail links, one for each record, are provided to view detailed information regarding the recordings. If a detail link is activated (S10.16), a user interface is offered for reviewing the details of the recording and further details can be obtained from the database. Fig. 10C shows a corresponding page for review of the details.

Each job record has a status: Completed, Waiting, or In Progress. If this is represented in FIG. 10A, the status as inline static text block is displayed together with other recording areas. Furthermore, each status text block is identified by hyperlink and / or highlighting and the user can activate the status text block to change the status.

In particular, if the "wait" text (for example, underlined) of one of the recordings with the displayed "wait" status is activated (S101), the browser activates a script that directs the server to send a "start order" page, as further below described with respect to FIG. 13A. The start job page shows the relevant job information and if the user identification (access level) is suitable, a last option for editing or changing the job parameters is offered before requesting confirmation that the job should be started. Generally, an operator would indicate the start of a job in this way. Once the confirmed order has started, the status of the recording in the database has changed to "in progress" and the planning page is again provided with the updated status.

If the "in progress" text (underlined if necessary) is one of the recordings is activated with a displayed "in progress" status (S10.14), ak the browser activates a script that represents a dialog (not shown), the one Confirmation requests that the job is finished. Once the order is finished confirmed, the status of the recording in the database is changed to "Been det "and the planning page is provided with the updated status.

If the "Finished" text (for example, underlined) is one of the records is activated with a "finished" status shown (S10.10), the brow is activated This is a script that represents a dialog (not shown) that provides confirmation demands that the order or the work piece be removed should. If the work piece is confirmed for removal, it will be from the order or Work list deleted (for example, order recording is activated with all the details and then eliminated).  

FIG. 11A shows an exemplary process sequence, assembled by the alarm side and a requesting browser can be transmitted wherein the web server 11 creates links for further actions.

In step S24.2, a setup user interface (UI) routine is carried out, in particular for setting up a first page of a user interface for an alarm setting routine. The "Build UI" routine generally corresponds to the routines previously described in the description with reference to Fig. 7. After completion of the "Build UI" routine, the complete file is fed to a browser which displays its contents as a form interpreted with the appropriate information. an example of the appearance of such a form is shown in FIG. 11B. As to pinned (S24.F1) are "edit" fields corresponding to the fields in the alarm table (database tables according to Fig. 6) for alarm type (Alarm_Type) and alarm field (Alarm_field) is provided. The alarm field is provided with a fixed list from which valid entries can be selected (for example order number, machine number, cutting total cutting surface, cutting total runtime). It should be noted that the alarm field This data field is by name, which can be modified when the user interface is displayed and not the field by which the alarm is conditioned.

If the form is displayed on the received browser, we at least two hyperlinks are provided: "next step" and "delete" (S24.4). On Delete leads back to the calling page. If "next step" is activated, a second page is supplied to the requesting browser (S24.6).

An example of the appearance of a second page with a suitable form is shown in FIG. 11C. As said, "Text" fields contain the previously entered alarm type and alarm fields. "Edited" fields correspond to fields in the alarm table and are intended for the highlight type (Highlight_type), limit value field (Thres hold_field), condition (Condition), limit value number (Threshold_value) and icon position (Icon_Location). If a "highlight" as opposed to an "alarm" was selected on the first page, the icon position is not used because it indicates where a message or icon should appear on an alarm page. The highlighting types measured are displayed in a fixed list. At least three types of highlighting / alarms are provided. For comparisons set by a user, the alarms have a first type of highlight / alarm where the alarm field is equal to the limit field and is highlighted or alerted if it exceeds an input value (in which case for example as Condition "<" or greater than and the input value would be saved as a limit value specification). The alarm comprises a second type, in which the alarm field is highlighted or alarmed if the (different) limit value field exceeds a limit value (for example, the machine number would be highlighted if the total cutting edge running time on the corresponding machine exceeds a limit value). A conflict alarm can also be set if conflicts are detected (for example, by highlighting the machine name fields with the same job number or cutting edge numbers under conflicting circumstances such as simultaneous processing). In such a conflict, "condition" would save = "and" limit amount "would save" conflict ". Even if only three types of alarm are shown here, storing the corresponding conditions for numbers or text in the condition field (<, <, =, including or the like) allows the detection of many conditions and their display.

When the second page form is displayed on the received browser, at least two hyperlinks are provided: "Execute", "Back" (S24.8). The back link, if activated, transmits the first page of the order form again with the previously entered values in each field. In this case, the user can edit both pages or return to the first page for deletion. If the execution link is activated (S24.9), all data stored in each field is sent to the web server 11 , which checks the alarm for validity and the data if correct, as a new record (S24.10) under an alarm ^- enrolls ID in the alarm table (Fig. 6). If the data does not specify an appropriate alarm, for example negative values for the limit value field), the user is led back to the first page (S24.11). It should be noted that if a new alarm recording is entered, a unique alarm ^- generated ID and ge written will and unused fields are provided with default values or null values.

FIG. 11D shows an example of an emphasis in the case of conflict, as it appears in a horse be placed Planning User Interface. In this case, two conflict alarms were set, highlighting the job number and the machine name if a conflict occurred. The rules for "conflict" are always the same - if each machine name carries out an order: status of "edit" more than once. With regard to the planning routines according to FIG. 10A, at the point in time when the web server 11 assembles the page and checks it for highlighting and alarm conditions (S10.4, S10.F1), each order number and each machine name is highlighted - in this case with a Alarm type of highlighting and a highlighting type with blinking text.

Fig. 12B (described later with reference to the machine monitoring routines) shows an example of highlighting with different alarm field and limit field as it occurs on a monitoring user interface. In this case, an alarm was set that occurs at the bottom of a page, for example if the machine name is on the page and if cutting edge: total runtime exceeds a limit value. The alarm provides, for example, an alarm icon and an identification of the alarm with fields limit value field, alarm field, condition and limit value amount, the text being assembled by analyzing the alarm conditions. With regard to the monitoring routine according to FIG. 12A, at the point in time at which the web server 11 assembles the page and is checked for highlighting and alarm conditions (S12.4, S12.F1), the alarm according to the icon position (below) and the alarm conditions appended when the alarm is triggered by the queried data (in this case, the web server 11 checks cutting edge: total runtime for each machine name).

As noted in the associated flowchart description, some highlights and alarms are standard and are always checked, e.g. performance, cutting edge, up, down, front and rear are always checked (via queried status by the MM component 7 instead of by reference to the Database) on the monitoring page.

FIG. 12A shows an exemplary process flow, assembles monitoring page after a machine and a requesting browser is offered, being produced for further action links.

In step S12.2, the web server contacts the MM component 7 in order to obtain the current status of each machine. That is, any current status information corresponding to signals D1 to D22 is queried. As an example, the current status can include: power, cutting in operation / out of service, up, down, front and rear signals. Up and down refers to the vertical position of the cutting edge ("Up" is before cutting and "Down" is total after cutting the material) via, for example, additional two "channels" to those from Fig. 3. "Before ne" and “Rear” refers to the material holding clamping position for inserting the material into the cutting machine, that is, channel D21 from FIG. 3.

In step S12.4, a setup user interface (UI) routine is processed, in particular for the setup of a user interface for a monitoring page. The "Setup UI" routine generally relates to routines as described in the description with reference to FIG. 7. After completion of the "Structure UI" routine, the complete file is fed to a browser, which interprets its content as a form with the corresponding information. It should be noted that the web server 11 uses the current status information from the MM component 7 as well as the latest corresponding records from the database for assembling the UI. An example of an appearance of a suitable form is shown in Fig. 12B.

As noted, "text" fields are provided for start time, Maschi ne, power, cutting edge, working mode, up, down, front, back, working time, quantity (QTY), cut area and status. Every occurrence of performance, cutting edge, up, down, Front and back are highlighted according to those specified in the record Parameters. In particular, an icon that represents a status light is in color  changed (e.g. green, white) depending on the status (e.g. on / off or true / false). Each field value for all machine records (get from different tables) is arranged on the page.

If the form is displayed on the received browser, some will Hyperlinks provided: "next page" / "previous page" and "detail" for each Recording.

There are more records than can be displayed on a single page the first page contains only the first 20 records, for example. Becomes the "next page" or "previous page" link will be activated marked on the first page starting with the last recording and the machine monitoring page is built and displayed using same routines, except that the previous records show be put.

The detail links, one for each machine, are provided to review the detailed information regarding the machine. If the detail link is activated, a user interface is offered which allows the details of the recording to be viewed, and further details are extracted from the database. FIG. 12C shows a right side to a review of the details Machine.

FIG. 13A shows an exemplary process flow, page assembled by starting a job, and an interrogating browser is supplied, being generated for further actions links.

In step S101.2, a setup user interface (UI) routine is carried out, in particular for setting up a user interface for the start order side. The "Setup UI" routine generally corresponds to the routines previously described in connection with FIG. 7. After completion of the "Structure UI" routine, the complete file is fed to a browser, which interprets its content as a form with the designated information. An example of the appearance of a suitable form is shown in FIG. 13B.

"Edit" field from the order, machine, cutting and order machines use tables (database tables according to Fig. 6) are for order number (Job_Number), order date (Order_Date), due date (Due_Date), translate the (address or customer - Ship_To ), Special instruction (Quantity), quantity (shape), material (material), cutting length (Cut_Length), sizes (Size_X, Y, W, H), sinking speed (via e.g. Job_Machine_Usage: machine ID: FCV_Position) Machine (Run_On_Machine) and cutting edge serial number (for example via Blade: Blade_ID: Serial_Number). Accordingly, the user can edit the order before it starts (with confirmation) in this way.

If the form is displayed on the received browser, several are Right hyperlinks provided: "Shape", "Material", "Change cutting edge" and "Confirm". The shape and material links (S101.8, S101.10) behave identically to those above steps described with respect to steps S8.4, S8.8 and S8.10.

The cutting edge change link is intended to select the available cutting edges or blades from the source database or to add a new cutting edge or blade to the database. If the cutting edge change link is activated (S101.12), a user interface for selecting an available cutting edge is provided in accordance with the recordings in Blade: Blade_ID as described with reference to FIG. 13C. When the confirmation link is activated (S101.14), the job recording (job: status) is confirmed to start. Once the job has been confirmed to start, the "Status" in the job table of the database is changed to "In progress" and the planning page is made available again with the updated status.

Fig. 13C shows an exemplary process flow for assembling and loading riding position of a cutting edge change page to a requesting browser, being generated for further actions links.

In step S112.2, a setup user interface (UI) routine is processed, in particular for setting up a user interface for a cutting edge side. The "On Build UI" routine generally corresponds to the routines previously described in connection with FIG. 7. After processing the "Structure UI" routine, the complete file is sent to a browser, which interprets its content as a form with the corresponding information. An example of an appearance of a suitable form is shown in FIG. 13D.

"Text" fields from the machine and cutting table are provided for the machine (Machine_Name), model name (Model_Name), serial number (Blade: Serial_Number) and brand (Blade: Blade_Brand). "Edit" fields from the cutting tables are provided for keep (keep), comment (comment), cutting type (Type_Name), cutting edge mark (Blade_Brand), pitch (pitch), size (size) and serial number (Serial_Number). In the example of FIG. 13D, an additional radio button selection is created to allow the user to choose between selecting a cutting edge from the inventory or adding a new cutting edge.

Changed fields are only saved if the "Save" link is activated, as described below. The user can directly change the status of the "Keep" field and the "Comment" field in the examples of Fig. 13D, each with a radio button according to a fixed standard list (even if a comment can be given directly as text) is produced. If the user chooses to add a new cutting edge, the cutting type, cutting edge mark, division and size are entered as new entries in the cutting table. It should be noted that when a new cutting edge record is entered, a unique cutting edge ID is generated and registered. The user can also select a new cutting edge from the inventory, in the example according to FIG. 13D from a list of cutting edges in the cutting table.

If the form is displayed on the received browser, ver various hyperlinks provided: "cutting type", "delete" and "save"  (S112.4). When the delete link is activated, the web server returns to the calling one Previous page (for example the order start page).

If "cutting type" is activated (S112.8), a user interface is operated which allows the entry of a new cutting type according to the lookup table with the cutting type. Fig. 13E shows a suitable form for adding or deleting a new cutting type. Fig. 13E further shows a link for adding a new cutting edge mark and Fig. 13F shows a suitable form for adding or deleting a new cutting edge mark.

If the "memory" link is activated (S112.8), various actions can be carried out by the web server 11 . Any changes in the status of the "Keep" or "Comment" fields are saved for the old cutting edge according to the cutting edge ID. A new record is added to the cutting table if the user selects to input a new cutting edge, and further the new cutting ID is recorded in the corresponding machine table as the cutting edge in use. Cutting edge related fields in other tables are updated and at least Cutting edge: In use: Cutting edge: In use by; Cutting edge: add date and cutting edge: remove date for both the old (removed) cutting edge and the new (installed) cutting edge is updated appropriately (the new cutting edge is added and recorded as in use and by which machine used, the old cutting edge becomes removed and recorded as no longer in use). The web server 11 then returns to the requesting page (for example, the order start page).

As a result, detailed records are kept for each cutting edge in the cutting inventory and in use and can be queried (for example by the in following described query routine) for the purpose of removal or Sta cutting edge. The logic of the system ensures that only one cutting edge is in Use on a machine and for an order. All cutting edges have one recorded reason for removal when they are no longer usable, and will be recorded as available for further orders if they have been removed  (for example, if a new job requires a different cutting edge, but the old cutting edge can still be used).

FIG. 14A shows an exemplary process flow according to the table on page assembled which an engine and a requesting browser is provided, wherein the web server 11 creates links for further actions.

In step S14.2, a setup user interface (UI) routine is carried out, in particular for setting up a first page of a user interface for the machine table. The "Build UI" routine generally corresponds to the routines previously described with reference to FIG. 7. After completing the "Structure UI" routine, the complete file is sent to a browser, which interprets its content as a form with the corresponding information. An example of the appearance of a suitable form is shown in FIG. 14B.

There are "text" fields for each machine ID record in the machine board for Machine name (Machine_Name), model name (Model_Name), IP address (Machi ne_IP), serial number (via Blade: Blade_ID: Serial_Number) and cutting edge mark (via Blade: Blade_ID: Blade_Brand).

If the form is displayed on the receiving browser, at least three hyperlinks are provided: "Detail", cutting edge "and" new machine "(S14.4). The Detail and blade links are used to view the machine and cutting details provided by the source database.

The cutting edge link is provided by the source database for changing the cutting edge used. If the cutting edge link is activated (S14.2), a user interface that enables the cutting edge in use to be exchanged is used according to the records in the cutting edge table (Blade: Blade_ID). FIG. 13C describes a routine used and FIG. 13D shows a suitable form for representing the cutting edge in use. If the detail link is activated (S14.10), a user interface is used to display the machine details that were taken from the machine table for this recording (Machine: Machine_ID). FIG. 14C shows a suitable form for display of the machine details.

If the new machine link is activated (S14.6), a user interface for entering a new machine record is operated according to the machine table fields (Machine: Machine_ID). FIG. 14E shows a suitable form for A reproducing a Neumaschinenaufzeichnung. It should be noted that when a new machine record is entered, a unique machine ID is generated and registered.

FIG. 15A shows an exemplary process flow according to which a user page tables assembled and a requesting browser is transmitted, the web server 11 creates links for further actions.

In step S16.2, a setup user interface (UI) routine is carried out, in particular for setting up a first page of a user interface for the user table. The "Structure UI" routine generally corresponds to the routines described in connection with FIG. 7. After completing the "Structure UI" routine, the complete file is fed to a browser, which interprets its content as a form with the corresponding information. An example of a suitable form is shown in FIG. 15B.

"Text" fields are provided for Username (Full_Name) Login ID (User_ID) and Access level or duty (duty), which differs from each login record in the Machine table result.

If the form is displayed on the receiving browser, at least five hyperlinks provided: "Detail", "Add User", "Update" and "Next." te / previous page "(S16.4).

If "Add user" is activated (S16.6), a user interface is provided which allows the entry of a new user record. Corresponding to the user name table fields (username: login). FIG. 15C shows a fitting For mular for entering the user details. It should be noted that when a new user record is entered, a unique login identity is generated and registered.

The detail link is provided for viewing the users from the source database. If this link is activated (S16.10), a user interface is provided which enables the user to look through according to the recordings in the user name table (user name: login). FIG. 15C is substantially the same form as the supplied except editable fields such as name field and login name with the user information are displayed according to the inline detail button.

There are more records than can be represented on a single page For example, the first page includes the first 20 records. Will that "Next Page" or "Previous Page" link activated, records will start the last record selected on the first page and the user table page is built up and displayed again using the same routines, only the following records are presented.

FIG. 16A shows an exemplary procedure, the assembles to a query page and a requesting browser is supplied, wherein links are created for further actions.

In step S18.2, a setup user interface (UI) routine is carried out, in particular for the setup of a user interface for a query page. The "Setup UI" routine generally corresponds to that described in connection with FIG. 7. After completion of the "Structure UI" routine, the complete file is fed to a browser, which interprets its content as a form with the corresponding information.

Queries can be performed on any set of records, filters, or conditions in the database. For example, instead of a general query according to which each field and filter can be selected, specific query pages for user, order, cutting edge or machine can be provided. Examples of such suitable forms are shown in Figures 16B, 16C and 16G. For example, FIG. 16B shows a suitable form for a general request (entered in each field), FIG. 16C shows a suitable form for an order summary request limited to machine name and material filter, and FIG. 16G shows a suitable form for a cutting request restricted to a cutting type filter.

"Edit" fields are for the query fields (for example, in the case of FIG. 16C for machine name and material) for sorting, for query filters (for example boo lesh or by condition), query time (in this case on a daily basis, weekly basis or any other way Time) and time fields as required (day, week, time, date, year, etc.). For example, a "sort" field can comprise a list of fields by which sorting can be carried out - in the case of FIG. 16B a list of three fields (material, date or order number) - selectable by "radio" button. Of course, the query page can be provided with a large number of filters on each field, for example diverse field conditions or values from which records can be selected or excluded.

At least one hyperlink is provided, in this case a submit button that the query is sent to the server (S18.4). If the results are transmitted, the web server sends the query in SQL syntax to the ODBC-compatible Da tenbankserver as described above.

If the query results are transmitted and displayed by the database server, an appropriate organization of the query results is provided. This is followed, for example, by a query of a machine field according to the order table, who shows the selected records of the order table (and other tables, as necessary). FIG. 16D shows a result page for a query of an order processing machine, which orders are planned for this machine, for example using an order-specific query page according to FIG. 16C.

For example, with reference to FIGS . 16C and 16D, when a query is carried out for the orders of a specific machine that can still be filtered for specific materials, the query results are organized into a result UI according to the order ID (S18.6). "Text" fields corresponding to fields of job and job / machine usage tables are provided for job number (Job_Number), job extension (Job_Extension), start time (Job_Machine_Usage: Job_ID: Start_Time), end time (Job_Machine_Usage: Job_ID: End_Time) runtime (Job_Machine Job_ID: Run_Time), Quantity (Cut_Area), Material (Material), Form (Shape) and Sizes (Size X, Y, W, H). Secondary values can be calculated from this, for example a cutting rate is calculated by dividing the cutting area by the running time. There are also sums and averages for certain fields as necessary. An exemplary addition for runtime, quantity and cut area as well as an average value for the cut rate are shown in the results according to FIG. 16D.

If the form is displayed on the receiving browser, several can Hyperlinks are provided: "next page" / "previous page" and "detail" for each record (S18.8).

There are more records than can be represented on a single page For example, the first page contains the first 20 records. Become the "next page" or "previous page" link is activated (S18.10), the Recordings marked from the last recording on the first page and the query results page is built up and again with the same routi NEN, except that the previous records are shown.

The detail links, one for each record, are provided to review the detailed information regarding the recordings. When a detail link is activated (S18.12), a user interface is provided which allows the details of the recording to be viewed, and further details are extracted from the database. FIG. 16E is a right side to a review of the details.

As noted, Fig. 16F shows an example of a cutting edge query page with a cutting type filter. This page is offered using the routine of FIG. 16A, even if all fields suitable for input and output are not shown specifically in FIG. 16A. FIG. 16G shows an example of a cut-oriented query result page corresponding to the search page shown in FIG. 16F and FIG. 16H shows an example of a cutting detail page that can be accessed via the cut-oriented query results page. The provision of the cutting-oriented query page, result page and detail page is essentially the same as the general and / or order summary query routines as described above and exemplary fields of interest are visible in the output pages.

FIG. 17A shows an exemplary process sequence, after a beauty Schneidenta (inventory) assembled pages and a requesting browser is supplied, wherein the web server 11 creates links for further actions.

In step S50.2, a setup user interface (UI) routine is carried out, in particular for the setup of a first page of a user interface for the cutting table. The "Setup UI" routine generally corresponds to the routines described in connection with FIG. 7. After processing the "Structure UI" routine, the complete file is fed to a browser, which interprets its content as a form with the corresponding information. An example of a suitable form is shown in FIG. 17B.

"Text" fields pulled out of each cutting ID record in the cutting The table is intended for cutting serial number (Serial_Number), cutting denmarke (Blade_Brand), add date (Add_Date), remove date (Remo ve_Date), runtime (Total_RunTime), cutting surface (Total_CutArea), division (pitch) and size.

If the form is displayed on the receiving browser, at least Four hyperlinks provided: "Detail", "Delete", "Update" and "Next" and / or "previous page" (S50.4). "Update" and "next / previous  Page "(S50.8) Links perform activities similar to those described above by.

The detail link is provided by the source database for reviewing the cutting edge details. If this link is activated (S50.10), a user interface is provided which enables the cutting details to be viewed in accordance with the recordings in the cutting table (Blade: Blade_ID). FIG. 17C shows a suitable For mular to represent the cutting details.

If "Delete" is activated (S50.6), the corresponding (inline) cutting edge record will be made deleted. The system can ask for confirmation (not shown).

FIG. 18 illustrates a routine for self refresh a user interface made available. This routine is provided as an invisible framework (for example with display dimensions of negligible size or off-screen) together with designated user interfaces as described above. In general, this is particularly useful with the planning and monitoring interfaces. Usually, browsers do not update HTML pages until a new action is taken by the user. By providing an invisible update frame together with the planning or monitor page, as long as these pages are displayed, the update frame will periodically request a refreshed page from the web server 11 . In step S202, a counter is incremented. In step S204, the counter is checked to see if a countdown level has been reached (for example, 1 second, 10 seconds, or the like). If the counting device reaches the assigned level, a query is sent from the browser to the web server 11 for a refreshed page (S206). The web server 7 follows the routines described above and requests current information from one or both machine monitoring components 7 or DB server 13 . The new page is provided (S208) and the counting device is restarted (S210).

Accordingly, according to the invention, the control software devices are components distributed in nature and on every known processor in a network  can be placed or executed at the factory. Each component is its own NEN network address or specific assigned connections under a ge provided common (IP) address. The functionality of each component is carried out without reference to their physical positioning in the network. On the In this way, each component on the same processor with each other Component can be arranged and such components are ko via multitasking existent. Since each component relates to the network, the com communicating via their network addresses or connections and not inside the host processor or via a bus. If necessary, the Distributing components to other processors is the component function exactly the same as before they were distributed. Because the components like each one whose intranet or internet facility is addressed, the connection can network cabling and bandwidth with existing office or other network share works. The virtual machine components handle the collection of Data from the cutting machines while the machine monitoring compo collects data from the virtual machine components. The machines Monitoring component now creates and creates the virtual machine compo elements as necessary, for example when adding a new virtual one Machine or remove an old virtual machine from the system what pa parallel to the actual addition of a new cutting machine.

User interface interpretation and server components are just as portable, and a control user interface can therefore be accessed, viewed and user input can take place where it is most convenient. Because the user interface for each individual cutting machine is generated in the same place (User interface server component or web server), such user interfaces managed centrally. If a new type of cutting machine is added o the one with more or less instrumentation can use the user interface centrally changed and made available according to the new requirements. Will new features and functions be added to the user interface on the server compo added, they appear instantly on the target or client browser. The flexible user interface allows machines, orders, materials and cutting elements  with central administration or with administration of distributed positions in the factory facility or over the Internet as a whole.

In particular, cutting elements can be made of green for their entire service life that of replacing or other commenting data are tracked. Since the Components on each cutting machine in cooperation with that from there accessible database the use (for example, after hours or cutting area) of each individual cutting element when a cutting element is on the same or different machine is being reused for some reason is no longer used, or who is reintroduced into the database inventory that such records are automatically kept for each sheet. An alarm depending on the cutting element usage (or other interests) and if a cutting element is used inappropriately (at such information about the proposed service life), such information made known to managers or operators via the flexible user interface. The user interface, which is generated dynamically and centrally, allows attachment of alarm information to almost every area of the user interface, for example on machine name, order identification etc. Accordingly, the alarm appears information if it is relevant.

It should be noted that not all of the components, data tables and / or functions ones described here in detail are necessary for a complete and are functionally described invention. For example, the system can only be used for Management of the cutting elements, machines, users, orders or everyone Permutation or combination thereof can be used. Furthermore, the Sys tem be used or configured for only a discrete function as described herein is described, for example monitoring, query, planning, order assignment tion, alarm setting, cutting element inventory control or the like or any combination or permutation thereof. For example, no database is necessary manoeuvrable for an embodiment only for monitoring and no virtual Ma Machines are necessary for an exemplary embodiment only for planning. Several out Leading examples of distribution in the system are possible, some or all components operated by some or all processors in the network  can, the distributed nature of the system being different and interacting components assigned different functions concerns, and not necessarily multiple processors at different Posi tions (even if this is in at least one embodiment of the invention is carried out). Not one or more of the above described Ele elements are critical to the operation of the invention unless expressly stated specified.

Although the above description describes certain embodiments of the present As regards the invention, modifications of the invention will be apparent to those skilled in the art these are intended to function as well as elements necessary for the invention be determined only by the appended claims. Changes can be made within of the appended claims as originally filed or revised without Leaving the scope of protection. Even if the invention un ter reference to certain devices, materials and embodiments has been described, the invention should not be limited to these special features become. Instead, the invention embraces all equivalents and / or insignificantly different structures, processes and uses within the Scope of protection.

Claims (20)

1. Management system for cutting machines and for assigning orders to the cutting machines with:
a plurality of cutting machines, each of which has a monitoring input device through which monitoring data can be input to indicate the status of the cutting machine;
a plurality of virtual machine components for collecting the monitoring data, each virtual machine component corresponding to a cutting machine;
a database server component for (i) communication with the machine monitoring component, for (ii) recording and reading of descriptive data comprising a machine table for describing the cutting machines and an order table for describing the orders to be carried out on the cutting machines, for (iii) association of the order table and Machine table, and for (iv) recording and reading usage data derived from the monitoring data and descriptive data;
a machine monitoring component for querying the monitoring data from all of the plurality of virtual machine components and for generating the usage data, the machine monitoring component providing the monitoring data and usage data of the database server component;
a user interface server component for (i) communication with the database server component and the machine monitoring component, for (ii) transmission of dynamic, interactive user interface elements that contain parts of the usage data, monitoring data and identification data, the content of the dynamic, interactive user interface elements depending on the content which is usage data, monitoring data and descriptive data, and
at least one user interface interpreting component for displaying the dynamic, interactive user interface elements. 2. System according to claim 1, characterized, that the system has a variety of over a network to operate the com Components connected microprocessors, each component ei the microprocessors as hosts and the components among themselves communicate through a network transport layer of the network. 3. System according to claim 1, characterized, that the descriptive data contain a cutting element table for loading writing wearable cutting elements for the cutting machines and that each order record and each machine record selectively with one Cutting element record is associated with the machine monitoring component a cumulative work value for each cutting element record generated that is representative of the size of the use of a corresponding Cutting elements of the cutting machine is. 4. System according to claim 1, characterized, that the descriptive data is a user table to describe the user or Users of the system and the operators of the machine include and that each order record and each machine record selectively with one Operator record is associated. 5. System according to claim 1, characterized,  that the monitoring data operation data according to settings of every machine included. 6. System according to claim 1, characterized, that the monitoring data load detection data to indicate the activity load of each machine included. 7. System according to claim 1, characterized, that the monitoring data includes lock detection data that is on show whether the machine is ready for operation or locked and in operation is hindered. 8. System according to claim 1, characterized, that each virtual machine component on a separate processor of the corresponding machine is running. 9. System according to claim 8, characterized, that the separate processor of the corresponding machine continues to work operates at least one of the user interface interpreting components. 10. System according to claim 8, characterized, that the monitoring input device is a data collection device for Has data accumulation using a variety of detectors at the Cutting machine is connected, each data collection device by ei a corresponding separate processor is controlled. 11. System according to claim 1, characterized,  that the database server component and the user interface server component run on the same processor. 12. System according to claim 11, characterized, that the same processor operates the machine monitoring component. 13. System according to claim 1, characterized, that the machine monitoring component corresponds to the virtual machines generated according to the machine table for the description of the cutting machines. 14. System according to claim 1, characterized, that each of the multitude of virtual machine components, the machines monitoring component, the database server component, the user interface face component and the at least one user interface interpreting component has an identification and the communication in the system accordingly Identification takes place regardless of the position. 15. System according to claim 14, characterized, that in response to a request from the user interface interpreting component the user interface server component monitoring data from the machine surveillance component queries and a surveillance user interface for Provides including the monitoring data for the user interface interpretation component. 16. System according to claim 14, characterized, that in response to a conditioned request from the user interfaceinter pretiercomponent the user interface server component with the database server component communicates, the database server component records  corresponding to the conditioned query to the user interface server compo nente transmitted, and the user interface server component a result user terface operates including the appropriate records for the user interface face interpreting component. 17. System according to claim 1, characterized, that if an order record in the order table corresponds and ei machine recording in the machine table the user interface server component of an order usage record in an order usage ta belle generated to display an assigned machine and record. 18. System according to claim 1, characterized, that the database still has an alarm table for specifying alarm conditions in the order table and the machine table and every time when a user interface is provided by the user interface server component to the at least one user interface interpreting component, the user interface server component checks the alarm table and sends an alarm indicator to spec fish records in the order table and machine table attached to the Alarm conditions correspond, with the user interface interpreting component interprets the alarm indicator. 19. A cutting machine management network system with:
a variable number of instrumented cutting machines, each having a processor with a virtual machine component that scans the instrumentation on the cutting machine and maintains status information corresponding to the status of the instrumentation;
a database server which holds a database with descriptive information about the instrumented cutting machines and which responds to requests;
a machine monitor connected via network to each instrumented cutting machine, which monitor contains a processor with a machine monitoring component that scans the virtual machine components and contains a status table with the status information of each virtual machine component;
a web server for processing requests from distributed clients and for providing hypertext documents;
a dynamic content server for interpreting markup documents with dynamic content with code segments, which dynamic content server queries the database server for receiving descriptive information, queries the status table from the machine monitor and generates hypertext document in response to requests from distributed clients and an internal interpretation of the code segments, wherein the hypertext documents contain various user interaction elements and displayed information, which depend on the content of the descriptive information and the status table. 20. Cutting machine management network system with:
a variety of interchangeable cutting elements for forming workpieces;
a variable number of cutting machines in which the cutting elements provided for forming the workpieces can be arranged, each cutting machine being assigned a processor with a virtual machine component which scans at least cutting element status on the cutting machines and which keeps the status information corresponding to the status of the cutting elements;
a database server that holds a database of information that describes the instrumented cutting machines, stores usage information for each cutting element, and responds to requests;
a machine monitor that is connected to each cutting machine via a network, the machine monitor having a processor with a machine monitoring component that queries the virtual machine component, contains a status table with the cutting element status of each virtual machine component and the usage information depending on the Statute table generated;
a user interface server component for communication with the database server and the machine monitor for providing interactive user interface elements which contain the cutting element useful information, and
at least one user interface interpreting component for displaying the user interface elements.