KR100221101B1 - Cutting database system for flexible manufacturing system - Google Patents

Abstract

The present invention relates to a flexible production system, comprising: a machine tool entity for representing data of a machine tool; A robot entity for representing data of the robot; Machine tool entities representing machine-specific data of the machine tool; A part family entity representing data of a workpiece to be machined using the machine tool; An NC program entity that represents data of a machining program according to a workpiece and a process when a machining operation is performed with a machine tool; A Go entity for representing relative positional data of a workpiece when machining with a machine tool; A pallet entity representing data of a pallet for conveying a workpiece; A fixture entity for representing data of a fixation fixture of a workpiece; A fixture plan entity representing data relating to the operation plan of the fixture; A machine tool operation entity for representing data related to the operation of the machine tool; A machine tool plan entity for representing data relating to the operation plan of the machine tool; An operation entity representing data related to the process plan; A routing entity E13 representing data relating to the process sequence; A day routing entity E14 representing a daily process sequence; A plan entity representing data relating to daily workload; Job entities representing data related to the tasks assigned at the present time, and Calendar entities representing daily working hours: schedule entities and plan entities, schedule entities and machine tool plan entities), schedules Entity (E17) and daily routing entity, routing entity and daily routing entity, workpiece logistics and process entity, process entity and routing entity, machine tool entity and machine tool plan entity, process entity and machine tool operating entity, machine tool operating entity And a confirmation relationship between the machine tool plan entity, the NC program entity and the solid entity, the fixture entity and the fixture plan entity; Workpiece entities and fixture entities, fixture entities and process entities, machine tool entities and machine tool entities, machine tool entities and machine tool operating entities, machine tool operating entities and NC program entities, process entities and work entities), pallet entities and work Between entities form the necessary unidentified relationship; The fastener entity and the pallet entity, the robot entity and the machine tool entity, and the machine tool entity and the work entity have a database in which a null tolerant non-identifying relationship is formed.

Therefore, the cutting machine according to the present invention does not need to have multiple machining programs all by receiving an NC code, which is a machining program suitable for a process, and can reduce the memory of the cutting machine. It has the effect of being able to adapt well to small quantity batch production method.

Description

Cutting database system for flexible production systems

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a flexible manufacturing system (hereinafter referred to as FMS), and more particularly, to a cutting processing database system for FMS that integrates and manages general information related to cutting of a flexible manufacturing system.

FMS is a concept generated by the conversion from the small-volume mass production system to the small-volume small-scale system, which makes it possible to easily convert the production process according to the product by using a computer for various device cells involved in the production.

In other words, the FMS is composed of one integrated operating system and multiple cell management systems in terms of information flow. In order for the FMS to operate efficiently, the information flow between the integrated operating system and each cell or between cells should be smooth.

However, in the conventional FMS, necessary data are manually managed or managed on a file basis for a computer. In addition, the managed data is integrated around the production items, which is not organically managed, and the data required for each equipment is often managed individually.

However, when managing data as described above, the following problem occurs.

1. Data managed by hand cannot be accessed from the integrated operating computer or other cell control computer in the case of data stored in the file, making data sharing difficult.

2. Integrity of data or consistency of data cannot be guaranteed, and redundant data management may occur.

3. The input, deletion, modification, and retrieval of data was complicated and inefficient.

4. It is difficult to recover damaged data.

5. Since data is not integrated, it is almost impossible to automate and optimize production systems.

The present invention has been made to solve the problems of the conventional flexible production system described above, an object of the present invention is to provide a cutting database system for FMS for efficiently managing a series of information related to the cutting process of the flexible production system To provide.

1 is a diagram illustrating an IDEFIX model method for representing the substance of data.

FIG. 2 is a diagram showing an IDEFIX scheme showing the attributes of each entity shown in FIG.

FIG. 3 shows an IDEFIX scheme showing the relationship between the data entities of FIG.

4 is a schematic block diagram of a flexible production system for carrying out the present invention.

5 is a structural diagram of a cutting database according to the present invention.

* Explanation of symbols for main parts of the drawings

1: integrated operating computer 2: cell control computer

D: Cutting Database M: Machine Tool

R: Robot

A cutting database system for FMS according to the present invention comprises: a machine tool entity representing data of a machine tool; A robot entity for representing data of the robot; Machine tool entities representing machine-specific data of the machine tool; A part family entity representing data of a workpiece to be machined using the machine tool; An NC program entity that represents data of a machining program according to a workpiece and a process when a machining operation is performed with a machine tool; A Go entity for representing relative positional data of a workpiece when machining with a machine tool; A pallet entity representing data of a pallet for conveying a workpiece; A fixture entity for representing data of a fixation fixture of a workpiece; A fixture plan entity representing data relating to the operation plan of the fixture; A machine tool operation entity for representing data related to the operation of the machine tool; A machine tool plan entity for representing data relating to the operation plan of the machine tool; An operation entity representing data related to the process plan; A routing entity E13 representing data relating to the process sequence; A day routing entity E14 representing a daily process sequence; A plan entity representing data relating to daily workload; Job entities representing data related to the tasks assigned at the present time, and Calendar entities representing daily working hours: schedule entities and plan entities, schedule entities and machine tool plan entities), schedules Entity (E17) and daily routing entity, routing entity and daily routing entity, workpiece logistics and process entity, process entity and routing entity, machine tool entity and machine tool plan entity, process entity and machine tool operating entity, machine tool operating entity And a confirmation relationship between the machine tool plan entity, the NC program entity and the solid entity, the fixture entity and the fixture plan entity; Workpiece entities and fixture entities, fixture entities and process entities, machine tool entities and machine tool entities, machine tool entities and machine tool operating entities, machine tool operating entities and NC program entities, process entities and work entities), pallet entities and work Between entities form the necessary unidentified relationship; The fastener entity and the pallet entity, the robot entity and the machine tool entity, and the machine tool entity and the work entity have a database in which a null tolerant non-identifying relationship is formed.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

First, before describing an embodiment of the present invention, IDEF1X used in the present invention will be described.

Recognizing the need for common analysis and communication techniques in production engineering, a series of modeling techniques developed by the US Air Force's Integrated Computer Aided Manufacturing (ICAM) program is called IDEF. IDEF modeling techniques include IDEF0 (IDEF Information Modeling), which models the functionality of the system, IDEF1X, which models information within the system, IDEF2 (IDEF Dynamics Modeling), which models changes in the characteristics of the system over time, and modeling the system operating processes. IDEF3 (IDEF Process Modeling).

Also, IDEF4 (IDEF Object-Oriented Design), an object-oriented design technique, and IDEF5 (IDEF Ontology Description), an ontology representation technique, are under development.

IDEF1 originates from Codd's Relation Theory, Chen's ER model, and Hughes Airlines' ELKA (Entity-Link-Key-Attribute), and IDEF1X is based on IDEF1's LDDT. (Logical Database Technique) was born.

IDEF1X is an information modeling technique used to standardize data and model it in a consistent, predictable way. Its main purpose is to:

1) Provide a means to fully understand and analyze the organization's data resources.

2) It provides a common means to express and convey the complexity of data.

3) Provide techniques for expressing the unified view of the data required to operate an organization.

4) It provides a means for defining independent data points that are valued by users of the data and can be converted into physical databases.

5) Provides a way to derive an integrated data definition from existing data resources.

The basic concept of IDEF1X is explained as follows.

First, in the IDEF1X model, the substance of data is represented as shown in FIG. Independent entities are represented by rectangles with rounded corners, dependent entities are represented by rectangles with rounded corners, and the name and number of the entity are displayed at the top of the rectangle.

Figure 2 represents the identifiers and attributes of each entity. An identifier is an attribute corresponding to a primary-key that uniquely distinguishes each entity and is displayed above the horizontal line inside the rectangle. Attributes represent the nature of each entity and are represented below the rectangular horizontal line.

The relationship between the data entities is represented by a line connecting the parent entity and the child entity as shown in FIG. The name of the relationship is shown above this line.

These relationship expressions are classified into Identifying Relationships and Non-Identifying Relationships, depending on whether the primary key of the parent entity is part of the primary key of the child entity. Is indicated by a dotted line.

A confirming relationship is a relationship in which an identifier of a parent entity is part of an identifier of a child entity, and an unchecking relationship is a relationship in which an identifier of a parent entity is an attribute of a child entity.

Non-confirmed relationships are further divided into Mandatory Non-Identifying Relationships and Optional Non-Identifying Relationships.

A mandatory unconfirmed relationship is one that does not allow nulls of the parent entity among unconfirmed relationships.

4 shows a schematic of a flexible production system for carrying out the invention.

In the drawings, the symbol M denotes a machine tool, and there may be more than one machine tool M of the same, similar or different type. The symbol R means a robot, which is used for loading a workpiece in a cutting FMS, and such a robot R may be deleted or installed in plurality.

Although not shown in the drawings, in addition to the above-described machine tool (M) and the robot (R), it is easy for those of ordinary skill in the art to add equipment or equipment related to logistics for setting up the workpiece. You will know.

The machine tool M, the robot R, and the like are connected to the cell control computer 2 via the network N, and the cell control computer 2 is operated by a cell control program.

The cell control computer 2 is connected to the integrated operating computer 1 via the network N, and the integrated operating computer 1 is driven by the integrated operating program.

Here, the symbol D means a cutting database, which is mounted on the integrated operating computer 1 or mounted on a separate computer and connected to the integrated operating computer 1 through the network N.

5 shows the structure of the logistics database D operated by the integrated operating computer 1 as IDEFIX.

As shown, the entities constituting the cutting database according to the present invention represent a machine tool entity E1 representing data of a machine tool, a robot entity E2 representing data of a robot, and data for each type of machine tool. Machine tool entity (E3).

In addition, the cutting database of the present invention includes a part family entity E4 representing data of a workpiece to be machined using a machine tool, and a machining program according to the workpiece and the process when the machining operation is performed with the machine tool. An NC program entity E5 for expressing the data of the data, and a Go entity E6 for representing the relative positional relationship data of the workpiece when the machining operation is performed by the machine tool.

Further, the cutting database of the present invention includes a pallet entity E7 representing data of a pallet for transporting a workpiece, and a fixture entity E8 representing data of a fixture for fixing the workpiece. A fixture plan entity (E9) representing data relating to the operation plan of the fixture, a machine operation entity (E10) representing data relating to the operation of the machine tool, and the operation of the machine tool. A machine tool plan entity E11 representing data relating to the plan; An operation entity E12 representing data associated with a process plan, and a routing entity E13 representing data associated with a process sequence.

In addition, the cutting database of the present invention includes a daily routing entity E14 representing the daily processing sequence, a plan entity E15 representing data related to the daily workload, and an assignment at the present time. Job entity E16 representing data associated with the completed job, and Calendar entity E17 representing daily work time.

The relationship between these entities (E1-) is: schedule entity (E17) and plan entity (E15), schedule entity (E17) and machine tool plan entity (E9), schedule entity (E17), and daily routing entity (E14), routing Entity (E13) and daily routing entity (E14), workpiece logistics entity (E4) and process entity (E12), process entity (E12) and routing entity (E13), machine tool entity (E1), and machine tool plan entity (E11). ), Process entity (E12) and machine tool operating entity (E10), machine tool operating entity (E10) and machine tool plan entity (E11), NC program entity (E5) and solid entity (E6), solid object entity (E8) ) And the fixture plan entity E9 form a confirming relationship.

Also, the workpiece logistics entity (E4) and fixture entities (E8), fixture entities (E8) and process entities (E12), machine tool entities (E3) and machine tool entities (E1), machine tool entities (E3), and machine tool operations The entity (E10), the machine tool operating entity (E10) and the NC program entity (E5), the process entity (E12) and the work entity (E16), the pallet entity (E7), and the work entity (E16) establish a mandatory unconfirmed relationship. Form.

In addition, the nullable non-confirmed relation between the fixture entity E8 and the pallet entity E7, the robot entity E2, the machine tool entity E1, the machine tool entity E1, and the work entity E16. Is formed.

The attributes in each entity (E1-E16) in which such a relationship is formed are as follows.

That is, the machine tool entity E1 includes an identifier (MC ID) for identifying a machine tool, an identifier (RB ID) of a robot dependent on the machine tool, a type of machine tool (Mc Type), and a state of the machine tool (mc_st). , Machine tool name (mc_nm), Machine tool CNC controller type (cnc_nm), Machine tool CNC memory amount (cnc_mem), Machine tool simultaneous control axis number (cnc_ax), Machine tool spindle torque (sp_trq), Machine tool Revolutions per minute (sp_rpm), power of the machine tool spindle (sp_pwr), table size of the machine tool (tb_sz), payload of the machine tool table (tb_load), size of the machine tool as a whole (dim_sz), machine tool weight ( dim_wgt) and the capacity mag_cap of the machine tool tool magazine as attributes.

In addition, the robot entity E2 has an identifier attribute (RB ID) for identifying the robot, and the machine tool entity E3 has an identifier (Mc Type) identifying the type of machine, a cutting type (cut_type), and a pallet. Is a time (u_tm) for loading into the machine and a time (u_ime) for unloading the pallet to the outside of the machine.

The workpiece logistics entity (E4) is an identifier (Part Type) that identifies the type of the part, the name of the part (part_nm), the material of the part (mtl), the weight of the part (sub), the possibility of subcontracting (sub), Attributes include a drawing, a pic of a part, and an order price of the part (ord_cost).

In addition, the NC program entity E5 includes an identifier (Pgm NO), a process number (Op NO), a part type (Part type), an NC program type (pgm_ty), and an NC program code (code) identifying the NC program. A code representing the part is provided as an attribute.

In addition, the solid entity E6 has, as attributes, an identifier Pgm NO identifying the NC program and a relative positional relationship loc on the fixture of the part.

In addition, the pallet entity (E7) has an identifier (Pal ID) identifying the pallet, the type of fixture (Fixt Type), the total number of parts (n_part) on the pallet, and the time (i_tm) when the pallet is injected for processing. Equipped.

In addition, the fastener entity E8 may include an identifier identifying the fastener, a part type, and a maximum number of parts (m_part) that can be mounted on the fastener; The number of fasteners by type (n_fix), the mounting time of the fixture on the pallet (u_tm), and the detachment time of the fixture on the pallet (d_tm) are provided as attributes.

The fastener plan entity E9 has identifiers (Fixt Type, Date) identifying the fastener usage plan, and the required amount qnt of the fastener as attributes.

The machine tool operating entity E10 includes, as attributes, an identifier (Part Type Op NO) for identifying a relationship between a machine and a process, and a machine type (Mc Type).

In addition, the machine tool plan entity E11 has identifiers (Part Type, Date, Op NO, MC ID) for identifying the machine operation plan, and the part machining quantity qnt as attributes.

In addition, the process entity E12 has an identifier (Op NO, Part Type), a fixture type (Fixt Type), and a process time (op_tm) identifying the process.

The routing entity E13 has an identifier (Part Type Op NO) identifying the process sequence as an attribute, and the daily routing entity E14 has an identifier (Part Type, Date, Op NO) identifying the work plan as an attribute. do.

In addition, the plan entity E15 includes an identifier (Part Type, Date) identifying the work plan, the order quantity (q_ord), the planned quantity (q_pln), the input quantity (q_in), the quantity of parts being processed (q_wip), and the quantity of semi-finished product (q_half). ); The quantity of defects (q_def), the number of finished products (q_fin), the order receipt quantity (q_gs), the order availability (q_rs), and the inventory quantity (q_stk) are provided as attributes.

In addition, the job entity E16 includes an identifier (Job NO) identifying a current job, a processing machine (MC ID), a process number (Op NO), a pallet number (Pal ID), a part type, and a job wait. Attributes include a time q_tm, a time o_tm at which the machining process starts, and a time f_tm at which the machining process ends.

In addition, the calendar entity E17 has an identifier (Date) for identifying a date, daily work start time day_st, and daily work end time day_fin as attributes.

The above-described database system stores data necessary for each entity, so that the integrated operating program in the integrated operating computer 1 of FIG. 4 is in the state of the machine tool M in the cell control program of the cell control computer 2. Command an initial check of

According to this command, the cell control program checks the state of each machine tool M and reports to the integrated operating computer 1 the state of each machine tool M and the preparation for machining start. The integrated operation program thus records the state of each machine M in the cutting database D.

At this time, the data is stored in the entity of FIG. The integrated operating program checks the workload today according to the plan entity E15 of FIG. 5, places work on each machine tool M using logistics equipment, and instructs the cell control program to start machining.

The cell control program thus accesses the cutting database D of FIG. 4 via the network N. FIG.

The pallet ID, part name and process number to be worked on now are checked in the working entity E16 in the cutting database D. With this part name and process number, the code is imported from the NC program entity E15 to the cell control computer 2. This code is necessary for driving the cutting machine M and depends on the workpiece and the process.

The cell control program checks the state of the machine tool M during machining, reports it to the integrated operation program, and writes it to the cutting database D.

After the end of processing, the cell control program reports to the integrated operating program that the end of the processing is completed, recorded in the cutting database (D), and transferred to the machine (M) for the next process using logistics equipment. It proceeds until the quantity as planned in plan entity E15 is processed. Each machine tool M is driven until the quantity as much as planned by the machine tool plan entity E11 is processed.

As described above, the present invention has the following effects by making a database of information related to cutting of a flexible production system.

1. Consistent data can be shared between FMS components.

2. The cutting machine (M) can automatically receive the NC code (code) that is suitable for the process.

3. The cutting machine (M) does not need to have all of the cutting programs (M) by receiving the NC code, which is the program for the process, when necessary, and the memory of the cutting machine (M). It can reduce the cost and adapt well to small quantity batch production methods.

4. Data can be managed stably, and it is easy to manage a series of data such as data input, output, modification and deletion.

5. The machine equipment (M) is easy to monitor and maintain by managing data on the condition, history, maintenance and repair of each machine equipment (M).

Claims (18)

The plurality of machine tools M and the robot R are controlled by a cell control computer 2 connected via a network N, the cell control computer 2 via an integrated operating computer (N). A flexible production system connected to 1) and having an integrated operating computer (1) having a cutting database (D), the cutting database comprising: a machine tool entity representing data of the machine tool; A robot entity representing data of the robot; Machine tool entities representing machine-specific data of the machine tool; A part family entity representing data of a workpiece to be machined using the machine tool; An NC program entity that represents data of a machining program according to a workpiece and a process when the machining operation is performed with the machine tool; A Go entity representing relative positional data of the workpiece when machining with the machine tool; A pallet entity representing data of a pallet for conveying a workpiece; A fixture entity for representing data of a fixture for fixing the workpiece; A fixture plan entity representing data related to the operation plan of the fixture; A machine operation entity for representing data related to the operation of the machine tool; A machine tool entity representing data relating to the operation plan of the machine tool; An operation entity representing data related to the process plan; A routing entity E13 representing data relating to the process sequence; A day routing entity E14 representing a daily process sequence; A plan entity representing data relating to daily workload; A job entity representing data associated with the job assigned at this time and a calendar entity representing daily work time: the calendar entity and the plan entity, the schedule entity and the machine tool plan Entity), the schedule entity E17 and the daily routing entity, the routing entity and the daily routing entity, the workpiece logistics entity and the process entity, the process entity and the routing entity, the machine tool entity and the machine tool plan An entity, the process entity and the machine tool operating entity, the machine tool operating entity and the machine tool plan entity, the NC program entity and the solid entity, the fixture entity and the fixture plan entity form a confirmation relationship; The workpiece logistics entity and the fixture entity, the fixture entity and the process entity, the machine tool entity and the machine tool entity, the machine tool entity and the machine tool operation entity, the machine tool operating entity and the NC program entity, the Process entity and the working entity), the pallet entity and the working entity form an essential unconfirmed relationship; And wherein said fixture entity and said pallet entity, said robot entity and said machine tool entity, and said machine tool entity and said work entity have a null permissible non-confirmed relationship. The machine tool entity of claim 1, wherein the machine tool entity includes an identifier (MC ID) for identifying a machine tool, an identifier (RB ID) of a robot dependent on the machine tool, a type of machine tool (Mc Type), and a state of the machine tool. (mc_st), machine tool name (mc_nm), machine tool CNC controller type (cnc_nm), machine tool CNC memory amount (cnc_mem), machine tool simultaneous control axis number (cnc_ax), machine tool spindle torque (sp_trq) , Revolutions per minute (sp_rpm) of the machine tool spindle, power of the machine tool spindle (sp_pwr), table size of the machine tool (tb_sz), payload of the machine tool table (tb_load), size of the machine tool as a whole (dim_sz), machine tool Cutting database system for flexible production systems with machine weight (dim_wgt) and machine tool tool magazine capacity (mag_cap) as attributes. The cutting database system of claim 1, wherein the robotic entity has an identifier attribute (RB ID) for identifying a robot. According to claim 1, The machine tool entity is an identifier (Mc Type), the type of cutting (cut_type), the time to load the pallet into the machine (ℓ_tm), unloading the pallet outside the machine ( Cutting database system for flexible production systems with an unloading time (u_tm) as an attribute. The method of claim 1, wherein the workpiece is an identifier (Part Type) for identifying the type of the part, the name of the part (part_nm), the material (mtl) of the part, the weight (weight) of the part (sub) ), A cutting database system for a flexible production system with attributes of the part's draw, the part's pic, and the part's order price (ord_cost). The NC program entity of claim 1, wherein the NC program entity comprises an identifier (Pgm NO), a process number (Op NO), a part type (Part type), an NC program type (pgm_ty), and an NC program code (ID) identifying an NC program. code A cutting database system for a flexible production system, with a code representing the part as an attribute. The cutting database system according to claim 1, wherein the solid entity (E6) has an identifier (Pgm NO) for identifying an NC program and a relative positional relationship (loc) on a fixture of the part as an attribute. . The pallet entity according to claim 1, wherein the pallet entity includes an identifier (Pal ID) for identifying the pallet, a fixture type (Fixt Type), the total number of parts (n_part) on the pallet, and a time (i_tm) in which the pallet is input for processing. Cutting database system for flexible production systems. The fastener entity (E8) according to claim 1, wherein the fixture entity (E8) comprises: an identifier for identifying the fixture, a part type, a maximum number of parts (m_part) mountable on the fixture; A cutting database system for a flexible production system having as attributes the number of fixtures (n_fix), the time at which the fixture is mounted on the pallet (u_tm) and the time at which the fixture is removed on the pallet (d_tm). The cutting processing database system according to claim 1, wherein the fastener plan entity has an identifier (Fixt Type, Date) for identifying a fastener usage plan and a required amount of fasteners (qnt). The cutting processing database of claim 1, wherein the machine tool operating entity has an attribute (Part Type Op NO) identifying a relationship between a machine and a process, and a machine type (Mc Type) as an attribute. system. The cutting machine according to claim 1, wherein the machine tool plan entity has an identifier (Part Type, Date, Op NO, MC ID) for identifying a machine operation plan, and a part machining quantity qnt as an attribute. Database system. The cutting database system of claim 1, wherein the process entity has an identifier (Op NO, Part Type), a fixture type (Fixt Type), and a process time (op_tm). . The cutting processing database system of claim 1, wherein the routing entity has, as an attribute, an identifier (Part Type Op NO) identifying a process sequence. The cutting database system of claim 1, wherein the daily routing entity has an attribute (Part Type, Date, Op NO) identifying a work plan as an attribute. The plan entity of claim 1, wherein the plan entity includes an identifier (Part Type, Date), an order quantity (q_ord), a planned quantity (q_pln), an input quantity (q_in), an amount of processing part (q_wip), and an amount of semi-finished product. (q_half); A cutting database system for a flexible production system having as a shortage quantity (q_def), number of finished products (q_fin), order receipt quantity (q_gs), order availability (q_rs), and inventory quantity (q_stk) as attributes. The method of claim 1, wherein the job entity comprises an identifier (Job NO), a processing machine (MC ID), a process number (Op NO), a pallet number (Pal ID), a part type (Part Type), A cutting database system for a flexible production system, with attributes as work wait time (q_tm), start time of the machining process (o_tm) and end time of machining process (f_tm). 2. The cutting database system of claim 1, wherein the calendar entity has an attribute (Date) identifying a date, a daily work start time (day_st), and a daily work finish time (day_fin) as attributes.