JPH09201746A - Production system design support device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To utilize a data obtained from a simulation in the other design level simply, when the design of a production system is carried out passing through design levels along the multistage. SOLUTION: A simulation program is set corresponding three stages of deisgn levels 1 to 3, and memories 30a to 30c corresponding to the program, the data, and the data converting rule, respectively are provided in a memory device 30. When the data used in an abstract design level is advanced to a concrete design level, it is converted to the data utilized by the data converting rule there, and it is not necessary to convert the data into the form to be utilized, at every time by a user, and input by the manual work, and as a result, a rapid and accurate design work can be carried out.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a production system design support apparatus suitable for carrying out a plurality of stages of simulation when designing a production system and evaluating the results of the simulation performed at each stage.

[0002]

Conventionally, in the design of a production system that comprehensively handles a production line of a factory, a warehouse, or a transportation system, a design of a schematic concept is started, and then a budget and a production are produced. Since various constraints such as concrete restrictions such as scale or site area, flow of products and parts to be produced, processing processes, etc. are constructed in various ways, the premise and design method for designing them Are complex and diverse.

In this case, in the usual case, as a design stage, the design procedure is positioned so as to obtain a final production system specification through a plurality of steps from an abstract level to a concrete level. There is. Therefore, the developer starts with the outline design at the abstract concept level and, according to the development program for such design, defines the scope of application of the distribution system such as the production line, storage, and movement of the target product. Then, based on the various data obtained there, the program proceeds to the next step to execute the program for determining the rough specifications.

FIG. 41 shows an example of a life cycle model which is a reference when designing such a production system. As the cycle of the production system, there are various models such as concept study, basic plan, basic design, detailed design, and operation, and further, there is an actual model corresponding to the actual production line. Each cycle has a purpose to be performed within the level, a model suitable for the design is created and generated, and corresponding data is set. Then, an item for evaluating whether or not the result obtained when the simulation is performed with the model or data set in the cycle achieves the initial target is provided.

In designing a production system, the above-mentioned cycle of an abstract level is used as a starting point and gradually shifts to a specific design level, and the detailed conditions are satisfied while the general conditions are satisfied. By performing such a simulation process, the specifications of the actual production system can be obtained.

In this case, in general, in a cycle shown in FIG. 41, a part from a basic plan to a basic design to a detailed design is often executed by a simulation program in particular. The program is prepared. Therefore,
The contents of the simulation process at each design level will be briefly described.

For example, in the cycle of the basic plan, for the purpose of clarifying the method and means, block charts are generated as a model to create a flow chart of processes and functions. Use only rough values for data, and stop at about the average or summary values. Through such a rough simulation, the production capacity, the amount of investment, or the equipment operating state is estimated. Then, with respect to this result, the investment payback period, the system operating rate, the neck process, etc. are predicted and evaluated.

In the cycle of this basic plan, concretely, for example, as shown in FIG. 42, an image of the production system is prepared. First, as a schematic configuration of the production system,
Set rough production system elements. This roughly sets the configuration of a combination of the processing line 1, the automatic transfer 2, the automatic warehouse 3, the automatic transfer 4, the assembly line 5, etc., and executes the above-mentioned simulation under such conditions to evaluate the result. It is a thing.

Next, in the basic design cycle, for the purpose of defining software and facility functions, a planar model of the block layout is created and a flow chart of the facility processing procedure is created. At this time, the data is set as a value that includes the probability variation. By executing the simulation process based on the setting of such a model, detailed results of the production capacity, the investment amount, or the equipment operating state can be obtained. This result will be evaluated in terms of the investment return, as well as in terms of equipment availability or system elements.

In this basic design cycle, specifically, for example, as shown in FIG. 43, a rough production system is designed. In other words, the direction is set in accordance with the concept described above, and it is a level for designing the approximate investment amount, effect, system scale, and the like. In this case, the components of each production system are also expressed with rough accuracy. For example, in the processing line 1, it is represented by a buffer 7 that connects between the step 6 for processing an object and the step 6.
The process 6 is designed with reference to the average cycle time and the operating rate.

When this design level is completed, a detailed production system is subsequently designed. Here, for the purpose of clarifying software and equipment specifications, a detailed layout model including a spatial layout is created, and a model is also created for details of equipment features and processing procedures. At this time, the data is treated as data that takes into consideration the characteristics peculiar to software and equipment. By performing a simulation based on such detailed settings, equipment operation, operation control, or software specifications can be obtained as a result. As for this result, the system operation is evaluated, and also the interference between the devices is evaluated.

More specifically, as shown in FIG. 44, the constituent elements of each production system are expressed as fairly specific values. For example, in the processing line 1, the process 6 is the concrete equipment 10, and the transportation equipment 11 is connected between these equipments 10, and more detailed data is required to realize such a configuration. In addition, each equipment 10 and the transportation equipment 11 of the processing line 1 have a product number A, B, C, D.
The actual operating conditions of the production system such as cycle time, setup conditions or failure data are used as data.

Similarly, in the automatic transfer systems 2 and 4, each transfer path 12 or 13 is represented by a specific transfer layout (straight road, curve, intersection, etc.), or AGVs 14 and 15 (automatic transfer vehicle). Is calculated as a specification expressed by a specific speed level (shift level such as 1st speed or 2nd speed). In the automatic warehouse 3, the loading station 16a and the unloading station 15b
Each of the AGVs 14 and 15 arrives and departs to store and pay out the parts being manufactured, and the storage state is managed as part inventory information. In the assembly line 5, a facility 17 for carrying out the process 8 is similarly performed.
A transport facility 18 is provided to connect between these facilities 17 and a specific assembly process is assumed.

The actual design work is performed by performing a simulation using these detailed data. In such a detailed simulation, production management information (for example, a production instruction by Kanban or MRP) can be added, and a detailed simulation including these can be performed.
Also, in the simulation at this stage, it is necessary to determine the specific specifications of the system that is actually installed in the factory, so the equipment layout (size, number, etc.) of these equipment models (AGV, various equipment), etc. It has been decided.

Now, the simulation program used at each of the above-mentioned design levels of a plurality of stages is basically carried out according to the flow shown in FIG. That is, in a simulation process at a certain design level, in order to set the purpose and specifications and achieve this, the data of the result obtained by the simulation at the previous design level is used, and it is newly necessary in the simulation. The data will be input as a condition, and the simulation will be performed based on this. The simulator device 19 executes arithmetic processing based on the given data and the simulation program and outputs a predetermined result.

If the simulation result is evaluated under the conditions as described above and becomes "OK", the output data of the simulation result is obtained as a product. When the evaluation result is not suitable, the user selects whether to change and set the initially set input data or return to the simulation program at the design level in the previous stage and reexamine.

Therefore, in order to design one production system to a concrete level, it is not unidirectionally performed from an abstract level to a concrete level, but repeated simulation is performed within a certain design level. Or, it is necessary to return to the design level of the previous stage or the previous stage to change and set the data and execute the simulation (see FIG. 46).

In this case, in each simulation program, there is a case where the format of the data to be input cannot always be input as it is in the simulation result obtained in the previous stage, and those data are in the format of the simulation program. It is necessary to input the data after transforming or calculating to fit. If the simulation result obtained in this way is good, it is used as a new simulation result as input data for the simulation program at the next design level.

Further, when the simulation result does not meet the design specification or the purpose, it is necessary to change and set the input data and perform the simulation again as described above. In some cases, the correction is made only in the simulation program. In some cases, it becomes impossible to perform the simulation by returning to the simulation program at the previous stage and resetting the data.

By the way, in the design of the production system as described above, it is necessary to carry out a final design through a simulation program corresponding to a plurality of design levels. Since it is necessary to input the necessary input / output data between them for each simulation program when advancing to different design levels, when sharing data between design levels and using it,
It is necessary to transform or calculate the data each time to make the data compatible and then input and set.

In addition, a normal simulation program is not configured to perform a complex simulation with other design levels, and the following design is performed after performing an optimum design in one simulation program. It is assumed to advance to the design level. Therefore, it is impossible to use the data of the simulation programs of the design level mutually, to execute the simulation program of the design level of the previous stage again to make a correction, and then to return to the simulation program again.

That is, when trying to execute such a composite simulation, the fact that the format of the data between them is different is a bottleneck. There is a problem that it is not possible to use such a database, and data cannot be exchanged between simulation programs.

From the above circumstances, when designing and evaluating a production system, mutual exchange of data over the use of the simulation program cannot be easily performed, and a good production system is finally constructed. It takes a lot of time to get to the factory
There is a problem that if you include conversion work etc. at the time of data input, it is very troublesome work considering correction work when inputting incorrectly, which is a major factor that hinders quick design work. Is the reality.

Further, in addition to such a problem, even when the simulation program is changed or added, the use relationship of the data becomes troublesome in the same manner as described above, and there is a problem that the usability is deteriorated. For the production system in operation, when design changes or specifications are to be changed, operational improvements such as adding a new simulation program for new equipment or changing specifications of equipment in operation. Even when doing so, the problem is that the data cannot be used easily.

Further, regarding the production system designed in this way, even when the equipment is actually operated, the setting of conditions for driving each equipment is based on the data obtained by the design. It is necessary to read and set the conditions of the equipment, and even in this respect, there is a problem that the use of data becomes troublesome from the time of operation to the maintenance.

The present invention has been made in view of the above circumstances. An object of the present invention is to automatically design a production system without re-inputting design data at each design level when there are a plurality of design levels. Another object of the present invention is to provide a production system design support device which can be used as design data suitable for a design level and which enables quick and hassle-free design evaluation.

Further, according to the present invention, a program for easily changing or adding a simulation program at each design level and for maintaining the compatibility of the data to be used with other design levels even in that case is provided. It is to provide a production system design support device that can be easily created.

[0028]

According to the first aspect of the present invention, when designing a production system, it is necessary for simulation at a higher design level corresponding to an abstract level according to the basic concept. When the predetermined data is input, the simulation calculation means executes the simulation processing according to the program, and the result data obtained by this calculation is converted by the data conversion processing means.
According to the data conversion rule stored in the data conversion rule storage means, arithmetic processing is performed and converted into corresponding data of another design level, and the resulting data is stored in the data storage means.

As a result, for example, when executing the simulation process corresponding to the next design level, the input data already obtained at the design level of the previous stage is input without newly performing the input work. Since it is stored in the data storage means in a state of being converted into appropriate data as data, it can be read and used as it is. Therefore, it becomes possible to carry out the simulation simply by inputting the necessary data, and the data obtained at the design level in the previous stage can be promptly processed without performing complicated calculations such as conversion processing. The simulation process can be started, and by doing so, data input mistakes can be reduced as much as possible.

In this way, even when the simulation processing corresponding to the lower design level is carried out, similarly, the simulation can be carried out by sequentially utilizing the result data obtained at the design level of the preceding stage. become able to. Furthermore, when the result of the simulation is not good, even when returning to the design level of the previous stage and performing the simulation repeatedly, the data already used can be used as it is, and if necessary. It becomes possible to do it only by changing and setting the data.

Further, since it becomes possible to carry out such a thing quickly, it becomes possible to easily and quickly repeat the simulation between design levels, so that the design efficiency is greatly improved. Will be able to.

According to the second aspect of the present invention, when the simulation program is executed, when the simulation process is executed, the data obtained according to the data conversion rule described in the data model is obtained. By performing the simulation process, it is possible to automatically obtain data converted to a format suitable for the data used at other design levels by executing the simulation process. Like

As a result, for example, when a design change such as a change or addition of a model of data when executing a simulation process is made or a design change such as a specification change of a production system is made, it is used at another design level. Since the data conversion rules for the data to be written are integrally configured, it is not necessary to change and set the entire data conversion rule each time, and the design can be easily changed or added.

According to the present invention, the simulation program can be stored in the storage device as one of the data models without separately providing a program for displaying the result of the simulation processing. By incorporating the data model, the processing contents relating to the display processing can be easily handled. By handling it as one of the data models in this way, additions and changes can be easily edited.

According to the fourth aspect, the calculation required for performing the simulation processing is described and stored as one of the data models. By incorporating the data model in the simulation program, it becomes easy. Can be made to perform arithmetic processing, and additions and changes can be easily edited.

According to the fifth aspect, when the simulation processing is executed, the user can determine whether or not the data obtained as a result of the simulation of the design level is to be converted into the data of another design level. Since it is possible to make a selection, for example, in the case where a favorable result is not obtained in the simulation, or when it is desired to store the obtained data as a reference, it is possible to end without performing the data conversion process. As a result, unnecessary data conversion processing can be eliminated and rapid processing can be performed, and at the same time, it is possible to prevent problems such as erroneous use of data at other design levels.

[0037]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below.
Two basic examples will be given and one concrete example will be given. That is, a first basic embodiment will be described as a first embodiment with reference to FIGS. 1 to 6, and a second basic embodiment will be described as a second embodiment with reference to FIGS. FIG. 10 to FIG. 40 are used to explain various modes and applied to a production system design support apparatus using an AGV (automatic guided vehicle) system based on a second basic example as a third example with reference to FIGS. An example will be described.

(1) First Embodiment (First Basic Embodiment) This corresponds to the first basic embodiment of the present invention, and is a schematic diagram of a design support apparatus applicable to various production systems. FIG. 1 shows an exemplary embodiment of which FIG.
This will be described with reference to FIG.

FIG. 1 shows a schematic block configuration. The simulation device 21 is composed of an input / output unit 22, a simulation operation unit 23, a display processing operation unit 24, and a data conversion processing operation unit 25. The simulation device 21 includes a display device 26, an input device 27,
An external input device 28 and an external output device 29 are connected, and a storage device 30 as storage means is connected.
The storage device 30 includes a program storage unit 30a for storing a simulation program, a data storage unit 30b as a data storage unit, and a data conversion rule storage unit 30c as a data conversion rule storage unit.

The program storage unit 30a of the storage device 30 stores a simulation program configured corresponding to three design levels described later. The data used in this simulation program is stored in the data storage unit 30b in a state of being converted into a data format according to the design level. In addition, the data conversion rule for converting the data according to the design level is set in advance, and the data conversion rule is stored in the data conversion rule storage unit 30c.

The simulation device 21 includes the input device 2
The operation input such as various data and commands input by the user via 7 is received from the input / output unit 22 and processed by the simulation calculation unit 23, and the operation input data and command input state and the simulation processing execution state are received. Are displayed on the display device 26. Further, these operation inputs, display outputs, or data are transmitted / received to / from the external input device 28 or the external output device 29.

In this case, the external input device 28 and the external output device 29 correspond to, for example, a terminal separately provided outside or each component of the production system, and actually manufacture the product in the production process. It can also be applied to devices and the like.

The program that defines the behavior of the simulation data model stored in the program storage unit 30a, which is set according to a plurality of design levels,
As shown in FIG. 4, for example, the simulation can be executed corresponding to three design levels. In this case, it is constructed so as to shift from the abstract design level to the concrete design level as it goes from the design level 1 to the design level 3.

For example, in the design level 1, a program (L1-1), a program (L1-2), etc. that define a data model when executing a simulation for performing a rough design are set, At the design level 2, there are provided a program (L2-1), a program (L2-2), ... Which are designed to obtain data in a little detail based on the result obtained by the program (L1-1). .

Further, in the design level 3, as a program for defining the data model for performing the most specific simulation, for example, for the simulation to be executed upon receiving the result of the program (L2-1) of the design level 2 in the preceding stage. Data model program (L3-1), program (L3-2), etc., or a data model program (L3) for simulation when the program is executed by receiving the result of the previous level 2 program (L2-2). −
3), program (L3-4), ... Are set.

It should be noted that the program between these design levels is not limited to the relationship shown by the solid line in the figure, but other connections may occur as the simulation processing progresses, and such new connections may occur. Is also configured to support.

Then, in each of the design levels 1 to 3, the data actually handled in the simulation processing is, for example, in the design level 1, the data D1 (L1), D2 (L
1), D3 (L1), ..., and at the design level 2, data D1 (L2), D2 (L2), D3 (L2),
It is used as ..., and at the design level 3, data D1
(L3), D2 (L3), D3 (L3), ...

Further, the data used in each of the above design levels is commonly used within the same design level, but the data used in other design levels are related but cannot be directly used. There is something. In other words, the data obtained as a result of the simulation at a certain design level will be used as the input data newly used at the simulation at the next design level.
The data used between the design levels are defined by a predetermined relationship, and the relationship is set by the data conversion rule stored in the data conversion rule storage unit 30c.

In this case, the data conversion rule is created according to the concept shown in FIG. That is, for example, in the higher design level M, the data D1 (L
M), D2 (LM), D3 (LM), ... Are used, and the data D1 is obtained at the design level m which is one step lower than this design level.
If (Lm), D2 (Lm), D3 (Lm), ... Are used, since these data are related to each other, generally, as shown in the figure, When converting the data of the higher design level M based on the data of the design level m, a general formula like the formula (1) is obtained for the n-th data Dn, and in the opposite case, the formula (2). A general formula such as

Dn (LM) = Fn [D1 (Lm), D2 (Lm), D3 (Lm), ...] (1) Dn (Lm) = fn [D1 (LM), D2 (LM), D3 ( LM),…]… (2)

Then, when the data conversion rule is determined for the data at each design level shown in FIG. 4 according to the above equations (1) and (2), as shown in FIG.
A group of data conversion rules divided into four blocks is formed corresponding to the conversion from the upper level to the lower level and the conversion from the lower level to the upper level between the three design levels 1 to 3. In the figure, the function of the data conversion rule between the design level 1 and the design level 2 is represented as F or f, and the function of the data conversion rule between the design level 2 and the design level 3 is represented as G or g. It represents.

In this case, from design level 2 to design level 1
The data conversion rule used in the data conversion processing to is: D1 (L1) = F1 [D1 (L2), D2 (L2), D3 (L2), ...] D2 (L1) = F2 [D1 (L2), D2 ( L2), D3 (L2), ...] and the data conversion rule from the design level 1 to the design level 2 is D1 (L2) = f1 [D1 (L1), D2 (L1), D3 (L1), ...] D2 (L2) = f2 [D1 (L1), D2 (L1), D3 (L1), ...]

The data conversion rule from the design level 3 to the design level 2 is as follows: D1 (L2) = G1 [D1 (L3), D2 (L3), D3 (L3), ...] D2 (L2) = G2 [ D1 (L3), D2 (L3), D3 (L3), ...], and the data conversion rule from the design level 1 to the design level 2 is: D1 (L3) = g1 [D1 (L2), D2 (L2) ), D3 (L2), ...] D2 (L3) = g2 [D1 (L2), D2 (L2), D3 (L2), ...].

Next, the operation of this embodiment will be described with reference to the program flow charts shown in FIGS. FIG. 2 shows the main program of the simulation device 21. When the program is started,
An initial screen display for selecting the design level of the simulation program is displayed on the display device 26 (step S1), and in this state, a standby state is entered until the user inputs a level setting of the design level from the input device 27. (Step S2).

When the level setting is input, a display screen for inputting the setting conditions corresponding to the input design level is displayed on the display device 26 (step 3), and in this state, the display is used. Input device 2
The process waits until the simulation setting input to be executed from 7 is performed (step S4).

Next, when the simulation setting is input, the corresponding simulation program is read from the program storage section 30a of the storage device 30 (step S
5) Then, the simulation is executed according to the simulation program (step S6).

In this case, in the execution of the simulation program, the display device 26 and the input device 27 are used to display the necessary items and to input the corresponding data. Read data from the data storage unit 30b of the storage device 30,
The simulation will be executed based on those data. Then, after the predetermined simulation is executed, the obtained result data is displayed, and the evaluation is performed automatically or by the user's judgment. If the evaluation result is good, the simulation program is terminated, and if it is unsuitable, the simulation is performed again by changing the data, and the simulation is repeated.

Even when the simulation is repeated as described above, the result may be unsuitable and the input data itself may be unsuitable. Then, in such a case, a desired result that fits is not obtained as long as the simulation of the design level is executed, and therefore it is necessary to return to the design level of the previous stage and perform the re-simulation. In such a case, the simulation of the design level is once terminated, the design level simulation of the preceding stage is set, and the program is executed.

When the execution of the simulation process is completed in this way, whether or not to perform the data conversion process is input (step S7). In this case, the data conversion process is performed when the simulation result is good,
For example, as described above, when returning to another design level and executing the simulation again, it is not necessary to immediately convert the result data obtained by the simulation that has just been executed. If the data conversion process is to be executed, the process proceeds to step S8 to execute the data update program shown in FIG. 3, and if the data conversion process is not to be executed, the process directly returns to step S1.

Now, in FIG. 3, when the execution of the data update program is started, first, it is judged whether or not the data has been updated in the simulation processing just executed (step T1). The program is terminated as it is, and if data is updated, the process proceeds to step T2.

At step T2, all the data updated by the simulation process just executed is read from the data storage section 30b, and subsequently, the data conversion rules for other design levels set for those data are described. All other data necessary for the conversion operation are read (step T3), and the corresponding data conversion rule is read from the data conversion rule storage unit 30c (step T3).
4).

Next, based on the read data conversion rule, the data conversion processing operation unit 25 calculates data of another design level (step T5), and the operation result is stored as update data until now. Instead of the data, the data storage unit 30b stores and updates the data (step T6). As a result, the conversion process of the data changed by the simulation process executed at that time ends. When data that needs to be updated is generated by this data conversion processing (step T
7) By repeating steps T2 to T6 again,
The conversion processing of those data is also carried out.

According to this embodiment, when the simulation process of one design level is executed, the data updated by the simulation is treated as data to be used at other design levels as well. Since the data conversion processing is performed according to the data conversion rule so that the data can be used as the input data, the data is read as it is from the data storage unit 30b when the simulation processing of another design level is performed next time. You will be able to handle it.

Therefore, when the data obtained by the previous design level simulation is used as new input data every time the design level advances as in the conventional case, the data is transformed into the data required for the design level simulation process. However, since it is not necessary to perform the input work again, a quick simulation process can be executed, and the input data can be handled easily and quickly, which can prevent erroneous data input.

(2) Second Embodiment (Second Basic Embodiment) FIGS. 7 to 9 show a second embodiment of the present invention.
The difference from the first embodiment is the configuration of the simulation program and the simulation data model program stored in the storage device 31. Storage device 3
1 stores, in addition to simulation programs provided corresponding to various design levels, programs A, B, C, ... Of simulation data models used in the execution of the simulation programs. These programs A, B, C, ... Are configured as follows.

That is, the simulation program is set corresponding to the overall design level, and is set to execute the simulation processing corresponding to each design level. The simulation data model program at each design level used in the simulation program includes a program description section that defines the relationships of the data models and a data storage section that stores actual data used in the simulation. , The data conversion rule part that stores the data conversion rule for converting the data used in the simulation from the data obtained in other simulation processing to the usable state is configured in an integrated form. There is.

When the simulation program is executed by the simulation device 21, when the program of the required data model is read out, the program description section, the data storage section and the data conversion rule section are read out together. The data conversion process executed in the course of the simulation process is also processed in the simulation program using the data conversion rule, as described later.

In the above-described configuration, the simulation apparatus 21 starts the operation, waits for the user to execute the main program, and waits for the user to input the setting of the simulation from the input device 27. A simulation program, which will be described later, is executed according to the input operation.

FIG. 8 shows a main program. When the program is started in the same manner as in the first embodiment, the display device 26 is caused to display an initial screen for design level selection (step P1). The system waits for a design level setting input via the input device 27 (step P2). Then, when the design level is selected and set, a display screen for inputting the setting to be simulated is displayed on the display device 26 as a display screen corresponding to the design level (step P3).
When the content of the simulation is selected and set by the input device 27 in that state (step P4), the simulation program is read (loaded) from the storage device 31 (step P5), and then the read simulation program is executed. (Step P6).

In this simulation program, the contents of the simulation are described according to the set design level, but what is common to all the design levels is the data conversion processing part. Therefore, as shown in FIG. 9, the schematic contents of the data conversion processing when the simulation program is executed will be described with reference to the flowchart in which the data conversion processing portion of the simulation program is extracted and shown.

First, when the program is started, a data input screen is displayed (step Q1), and then it is judged whether or not a simulation process of another design level has been carried out before (step Q2). If the program is being executed, it is determined to be "YES" and the process proceeds to step Q3. Here, in the subsequent simulation, whether or not to use the data updated by the simulation processing of another design level is determined according to the input instruction, and in the case of “YES”, it is stored in the storage device 31. The program of the corresponding applicable data model is accessed to read out the necessary model and data (step Q4).

Next, with respect to the read data model, the data conversion rule contained in the program of the data model is applied so that the data used in the simulation at this design level is subjected to the data conversion processing (step). Q5). Then, the data obtained as a result is displayed on the data input screen of the display device 26 and displayed as the input data at a predetermined position on the screen (step Q6). In this state, the system waits for input of other necessary data (step Q7). In the above-mentioned step Q2 or Q3, "N
If it is determined to be "O", in any case, the process jumps to step Q7 and waits for input of necessary data.

Here, the user newly inputs the necessary data out of the data displayed on the data input screen and, if necessary, changes and sets the data already in the input state, When the data input is completed and an instruction is input to that effect, the simulation device 21
Determines "YES" in step Q7, accepts the input data displayed on the data input screen, uses it as data required for the simulation, and executes the simulation according to the program (step Q8).

When a series of simulation processing is completed, the result is displayed (step Q9), and the user waits for the user to input whether the result is OK or not (step Q10). . When the user inputs an instruction to that effect when the simulation result is not good, the simulation device 21 determines “NO” in step Q10, moves to step Q11, and determines whether to perform the simulation again. If the determination is "YES", the process returns to step Q6 and waits for data to be input again to repeat the simulation.

On the other hand, when it is determined that the simulation result is good and the user inputs an instruction to that effect, the simulation device 21 determines "YE" in step Q10.
S ”is determined and the process proceeds to step Q12. Even if it is determined to be "NO" in step A10, it is expected that a good result will not be obtained even if the simulation processing of this design level is repeatedly executed, and the instruction input by the user returns to the design level of the previous stage. If it is determined that the simulation is to be performed by "N" in step Q11.
When it is determined to be "O", the process proceeds to step Q12.

Then, in step Q12, the simulation device 21 determines whether to save the data obtained as a result of the simulation performed in step Q8. This is because when the user determines whether or not to store the data obtained as a result of the simulation as update data and receives an instruction input, the simulation device 21 stores the update data in the storage unit 31 as the previous data. Instead of this, the newly obtained data is stored (step Q13), after which the program is terminated and returns to the main program.

After that, when the simulation processing of another design level is executed, the necessary simulation setting input is carried out by the main program in the same manner as described above, and in this case, it is already obtained. If you want to use the data obtained in the previous stage after reading the specified data and input the rest of the required data, convert it to a data format that is suitable for the simulation process at the design level. Since the input is automatically set, the user does not need to newly perform the data input operation, and the data input process can be performed quickly and reliably.

The second embodiment as described above can obtain the same effect as that of the first embodiment, and has the following practical merit. In other words, even when changing or adding a data model program, by setting the relationship with other data models in the program and setting the data conversion rules for the data between them. Since it can be created easily, it becomes possible to easily make changes in program units, and it is also possible to realize system expansion and application to other systems at low cost.

(3) Third Embodiment (Applied Embodiment) The third embodiment of the present invention is based on the basic structure of the object-oriented program format, which is the method of the second embodiment, based on the AGV. FIG. 10 shows an embodiment in the case of being applied to a production system design support device that uses a (unmanned guided vehicle) for production, and will be described below with reference to FIGS. 10 to 40. The schematic configuration of this embodiment is the same as the configuration of FIG. 7 shown in the second embodiment, and therefore the configuration in FIG.

(A) Description of Design Procedure First, before explaining the present apparatus, what kind of process is normally followed in designing and evaluating such a production system? This point will be briefly explained. FIG. 10 and FIG. 11 abstract the flow of what process is normally performed when designing a general production system in which a product is manufactured on a factory production line or the like. It outlines the process of progress of the design level and its evaluation contents from the general level to the concrete level. A brief description will be given below with reference to these drawings.

As shown in FIG. 10, the main flow of the design procedure is in the direction indicated by the white arrow. That is, as the design level, including the 0th level corresponding to the concept study, the 1st level is the basic plan, the 2nd level is the basic design, and the 3rd level is the detailed design. The flow is such that E1 and a reuse level E2 that is intended for applications such as maintenance and reuse are added.

At each design level, when the purpose and specifications at the design level are determined, design and examination are executed, and the evaluation is performed. , It will be possible to obtain the products such as data and specifications obtained by the examination as a result of the design level. This result is used as data to be used in the next design level.

In the above-mentioned case, in the concept study stage, which is the 0th-order design level, there are rationalization issues, new factory plans, new product plans, etc. as objectives and specifications. There are management index calculations such as production capacity and allowable investment amount, and factory index calculations such as productivity and environment. There are items such as investment potential and factory environment improvement as the evaluation of the result of the design examination, and if the concept, image diagram, etc. are obtained as a result of conforming to these items, the project and system specifications or system goals are based on this. The value comes to be decided.

Next, according to the contents of the products in the concept study stage determined as described above, in the basic design stage, which is the primary design level, as shown in FIG. The aim is to clarify the basic specifications of the entire system. Correspondingly, in design study, system configuration study such as equipment type and range, system prerequisite study such as operating rate, system capacity scale rough calculation, Review the process flow chart and the expected investment amount and its effect. The evaluation of the results obtained by such examination includes items such as system target value, scale / realization level, investment amount and its effect, or neck points. It is possible to obtain a specific deployment plan, a system concept diagram, a system proposal diagram, a product improvement plan, a process improvement plan or a dynamic condition target value.

At the basic design stage, which is the secondary design level,
The purpose and specifications are to define and clarify the functions of each system element, whereas in the design study, the system overall configuration specifications / procedures, dynamic behavior condition studies, investment Examine system capacity / scale calculation or layout diagram for decision, and further calculate investment return. The evaluation of the results obtained by such examination includes dynamic target value level, dynamic behavior of each element,
If there are items such as interference between elements, return on investment or neck points, and these evaluation results are good, system specifications, layout drawings, process improvement plans, etc. will be obtained as deliverables.

At the detailed design stage, which is the third design level,
The purpose and specifications are to clarify the configuration and control method of each element, and aim for specific improvement studies. In design studies, the behavior of each element corresponding to the configuration / processing procedure or physical behavior, control of the entire system The method will be verified, and the equipment configuration specifications will be broken down or specific measures will be taken into consideration. The evaluation of the results obtained by such examination is the evaluation of the system operation including the interference in the element or the role of the person, and the final product is the final design document and drawing, the final layout drawing or It is an operation method specification, etc., and the procedure is to receive the result and start the system production and start preparation for factor education.

It should be noted that, based on the specifications of the production system determined in this way, in the operation stage, the goal is to take measures against unachieved or neck points with respect to the system target value. Research and analyze the data to narrow down those issues, consider measures from both aspects of the system and each element, and formulate an implementation plan. As an evaluation of the results obtained by such examination, the operating rate of each element with respect to the current situation and the improvement plan is evaluated, and the operating rate of the entire system is evaluated. A list of concrete implementation projects will be created, modification specifications and modification drawings will be obtained, and modification can be implemented based on these.

Further, in the reuse stage for a similar system, in consideration of the purpose such as a mass production product or a request for changing the specification configuration, in design examination, the components of the required system and the current system are selected. The functions and specifications are compared, and the possibility of reuse, including actual data, is examined and evaluated both statically and dynamically, and a reuse plan is drafted based on these. As the evaluation of the results obtained by such examination, reusability, cost comparison between reuse and new, and possibility of countermeasure schedule are evaluated comprehensively, and these results are good. , The reuse plan is obtained, and the start of reuse can be implemented.

(B) Description of Program System Next, the system of the simulation program and its data model corresponding to each level of the production system design support apparatus in this embodiment will be described. FIG. 12 conceptually shows the configuration of the system. For the entire target production system to be designed, the primary design level (hereinafter,
At the stage of design level 1), the (L1-1) line,
(L1-2) Transport system, (L1-3) Storage, (L1-4)
It is divided into data model programs that show each component such as the product or (L1-5) production control as a model, and is configured to roughly design each of these items.

Then, a program (L1-- that shows the behavior of each data model set at the design level 1 stage described above).
For 1) to (L1-5), there are a plurality of data model programs set corresponding to the design level 2 stages. For example, in the (L1-1) line, (L2-
1) Processing line, (L2-2) assembly line, (L2-3) loading / unloading conveyor etc.
2) In the transfer system, (L2-4) AGV system,
(L2-5) forklift, (L2-6) hand truck,
(L2-7) Home stations and other programs are prepared. In addition, in (L1-3) storage, (L2-8)
Each program such as automatic warehouse, (L2-9) flow rack, (L2-10) pallet storage, etc. is prepared. For (L1-4) product, (L2-11) transport box, (L2-12) work etc. Each program is prepared.

Further, a data model program of the design level 3 stage is prepared corresponding to each data model program of the design level 2 stage. For example, the data model of the (L2-4) AGV system is prepared. Each program such as (L3-1) AGV, (L3-2) route details, (L3-3) loading / unloading station, (L3-4) curve, (L3-5) intersection, etc. Being prepared. Although not shown in the drawing, programs for other data models are similarly prepared for each of the programs corresponding to the design level 3, and these programs are used for the design.

With regard to the programs of these data models, as shown in another example in FIG. 13, for example, the data format to be the model used in each program is set, and the simulation device 21 executes the simulation program. When reading and executing each program, each data is directly dealt with about the contents of those programs, but between each design level,
The data are closely related and the relationships between them need to be clarified.

Therefore, in the data model program, the format of the model data is defined in advance, and is configured as shown in FIG. 14, for example.
In FIG. 14, the transfer system (L1
-2) is shown as an example, and this transfer system (L1
-2), "operating time", "lead time",
Data such as "inventory quantity", "transportation source model", or "transportation destination model" is used, and those data are used at the design level 2 which is another design level.
The data conversion rules showing the correlation with various data used for are set and stored integrally (the contents will be described later).

At the design level 2 in the next stage of the transfer system, simulation programs for the above-mentioned AGV system (L2-4) and home station (simplified) (L2-7) are prepared. L2-
In 4), as the model data format, "all route length", "each route length", "all section AGV average speed",
“Average route speed for each route”, “Total lead time”, “Each lead time”, etc. are provided. For the home station (simple) (L2-7), the model data format is “AGV number”, “ "AGV operation rate", "AGV transport capacity", "AGV system cost",
"AGV system total cost" or "operating time" is provided, and data conversion rules corresponding to each are set and stored in advance.

At the design level 3, AGV
In correspondence with the system (L2-4), AGV (L3-1), route details (L3-2), loading / unloading station (L3-3),
Each program of curve (L3-4) and intersection (L3-5) is prepared, and home station (simplified) (L2
-7) Home station (details) (L3-
6) is prepared.

As the data model in each program described above, in AGV (L3-1), "AGV speed low speed", "AGV speed high speed", "acceleration time (low → high)",
"Visibility (far)", "Visibility (near)", "Transfer instruction time", etc., "Detailed travel route" in the route details (L3-2), and in the unloading station (L3-3),
"Operating time", "Average number of work stays", "Station cost", etc. For curves (L3-4), "Passage time", "AGV average transit time", "Curve unit price", etc. In L3-5), "Transit time", "AGV
These are "average transit time", "intersection unit price", etc. Further, in the home station (details) (L3-6), there are "AGV number", "AGV operating rate", "AGV carrying capacity", "operating time" and the like. Further, in each simulation program, a data conversion rule with respect to data of a higher design level is set and stored.

(C) Description of Data Conversion Rule Next, the data conversion rule showing the handling of each of these models and their data will be described. As for the program of each data model in each of design levels 1 to 3, for example, the portion corresponding to FIG.
The data relationship is set as shown in. In this case, the data set in the program of the data model of each design level is indicated by an arrow because the data connected by the solid line is calculated according to a predetermined function with respect to the data models of other design levels. It can be obtained as part of the data.

The data conversion rule is a property obtained as a result of conversion or conversion from various data that should be obtained by executing the simulation process of another design level with respect to the model and data used in the simulation process of the design level. Data is automatically calculated and obtained, and these are stored as, for example, the following functions.

In this case, these relationships are divided into upper conversion and lower conversion between each design level [A].
~ Shown in groups of [D], and in each group, [Number]
The data conversion rule indicated by is stored in the program of each data model. These are set in the same manner as the data conversion rule shown in FIG. 6 in the first embodiment described above. In addition,
The data conversion rule indicated by [E] indicates a data conversion rule within the same design level, which is a complementary data conversion rule for integrating or associating each data.

[A] (Design level 2) ← (Design level 1) [1] Travel route (AGV system (L2)) = f (source model, destination model (transport system (L1)) (f; transport Function set with source model and destination model as variables) [2] Operating time (home station (L2)) = operating time (transfer system (L1))

[B] (Design level 1) ← (Design level 2) [3] Lead time (transport system (L1)) = lead time (AGV system (L2)) (lead time (AGV system (L2)) , [C]) [4] Inventory quantity (transport system (L1)) = AGV average inventory quantity (AGV system (L2)) (AGV average inventory quantity (AGV system (L2)) is [d]
by)

[5] Calculation result Investment amount (Transport system (L
1)) = total cost of AGV system (home station (L
2)) [6] Transport distance (transport system (L1)) = total route length (A
GV system (L2)) (Total route length (AGV system (L2)) depends on [a])

[C] (Design Level 3) ← (Design Level 2) [7] Detailed Travel Route (AGV System (L3)) = Travel Route (AGV System (L2)) [8] Operating Time (Home Station (L3) )) = Working time (Home station (L2))

[9] Number of AGVs (home station (L
3)) = Number of AGVs (home station (L2)) [10] AGV availability (home station (L3)) = AG
V availability (home station (L2)) [11] AGV transfer capacity (home station (L3)) = A
GV transport capacity (home station (L2))

[D] (Design level 2) ← (Design level 3) [9] Number of AGVs (home station (L2)) = AGV
Number of units (home station (L3)) [10] AGV availability (home station (L2)) = AG
V availability (home station (L3)) [11] AGV transfer capacity (home station (L2)) = A
GV transport capacity (home station (L3))

[12] Route length [HS → SS] (AGV system (L2))
= G1 {AGV speed low speed (AGV (L3)), AGV speed high speed (AGV (L3)), detailed travel route (AGV system (L3)), distance (travel path (L3)), transit time (curve (L3)) ), Transit time (intersection (L3)), unloading station (unloading station (L3))}

[13] Route length [SS → SS] (AGV system (L2))
= G2 {AGV speed low speed (AGV (L3)), AGV speed high speed (AGV (L3)), detailed travel route (AGV system (L3)), distance (travel path (L3)), transit time (curve (L3)) ), Transit time (intersection (L3)), unloading station (unloading station (L3))}

[14] Route length [SS → HS] (AGV system (L2))
= G3 {AGV speed low speed (AGV (L3)), AGV speed high speed (AGV (L3)), detailed travel route (AGV system (L3)), distance (travel path (L3)), transit time (curve (L3)) ), Transit time (intersection (L3)), unloading station (unloading station (L3))} (g1, g2, g3 = Σ [distance traveled] + Σ [curve transit time × AGV curve transit speed] + Σ [Intersection transit time x AGV curve transit speed])

[15] AGV average speed [HS → SS] (AG
V system (L2) = g4 {AGV speed low speed (AGV
(L3)), AGV speed high speed (AGV (L3)), detailed travel route (AGV system (L3)), distance (travel path (L
3)), AGV average transit time (runway (L3)), distance (curve (L3)), AGV average transit time (curve (L3))
3)), distance (intersection (L3)), AGV average transit time (intersection (L3)), travel time (unloading station (L3))}

[16] AGV average speed [SS → SS] (AG
V system (L2) = g5 {AGV speed low speed (AGV
(L3)), AGV speed high speed (AGV (L3)), detailed travel route (AGV system (L3)), distance (travel path (L
3)), AGV average transit time (runway (L3)), distance (curve (L3)), AGV average transit time (curve (L3))
3)), distance (intersection (L3)), AGV average transit time (intersection (L3)), travel time (unloading station (L3))}

[17] AGV average speed [SS → HS] (AG
V system (L2) = g6 {AGV speed low speed (AGV
(L3)), AGV speed high speed (AGV (L3)), detailed travel route (AGV system (L3)), distance (travel path (L
3)), AGV average transit time (runway (L3)), distance (curve (L3)), AGV average transit time (curve (L3))
3)), distance (intersection (L3)), AGV average transit time (intersection (L3)), travel time (unloading station (L3))} (g4, g5, g6 = P / Q P = Σ [travel Road distance] + Σ [curve transit time × AGV curve transit speed] + Σ [intersection transit time × AGV curve transit speed] Q = Σ [average AGV transit time at each road, curve, and intersection] + travel time of the unloading station )

[18] Lead time [HS → SS] (AGV
System (L2)) = g7 {Detailed travel route (AGV system (L3)), AGV average transit time (travel path (L3)),
AGV average transit time (curve (L3)), AGV average transit time (intersection (L3)), travel time (unloading station (L3))}

[19] Lead time [SS → SS] (AGV
System (L2) = g8 {Detailed travel route (AGV system (L3)), AGV average transit time (travel path (L3)),
AGV average transit time (curve (L3)), AGV average transit time (intersection (L3)), travel time (unloading station (L3))}

[20] Lead time [SS → HS] (AGV
System (L2) = g9 {Detailed travel route (AGV system (L3)), AGV average transit time (travel path (L3)),
AGV average transit time (curve (L3)), AGV average transit time (intersection (L3)), travel time (unloading station (L3))} (g7, g8, g9 = Σ [runway, curve, intersection Average transit time for each AGV] + transit time for loading and unloading stations)

[21] AGV system cost (home station (L2)) = g10 {AGV speed low speed (AGV (L
3)), AGV speed high speed (AGV (L3)), AGV unit price (AGV (L3)), detailed travel route (AGV system (L3)), distance (travel route (L3)), route unit price (travel route (L3)) )), Transit time (curve (L3)), curve unit price (curve (L3)), transit time (intersection (L3)), intersection unit price (intersection (L3), number of AGVs (home station (L
3))} g10 = Σ [unit price of AGV x number of AGVs] + Σ [unit price of driving road x unit price of route] + Σ [curve passage time x AGV curve passage speed x curve unit price] + Σ [intersection passage time x AGV intersection passage speed x intersection unit price] ]

[22] Unloading station total cost (home station (L2)) = station cost (unloading station (L3))

Data conversion rule within [E] (design level 2) [a] Total route length (AGV system) = Σ {route length [H.
S. → SS] [12] + route length [SS → SS] [13] + route length [SS → HS] [14]}

[B] AGV average speed (AGV system) =
h1 {total route length (AGV system) [a], route length [HS → SS] [12], average AGV speed [HS → SS] [1]
5], Route length [SS → SS] [13], AGV average speed [S.
S. → SS] [16], route length [SS → HS] [14], AGV
Average speed [SS → HS] [17]} (h1 = total route length [a] / KK = Σ [each route length / AG
V average speed])

[C] Lead time (AGV system) = Σ
{Lead time [HS → SS] [18] + Lead time [S.
S. → SS] [19] + lead time [SS → HS] [20]}

[D] AGV average stock amount (AGV system)
= (Lead time [SS → SS] [19]) / (AGV average speed [SS → SS] [16]) [e] AgV system total cost (home station) =
H. S. Installation cost + AGV system cost [21] + total loading and unloading station cost [22]

(D) Description of Operation Next, the operation of this embodiment will be described. The main program is executed with substantially the same contents as described in the second embodiment, and a description of the program will be omitted, but an explanation of the display state during execution of the main program will be omitted. Will be described separately.

Schematic Description of Simulation Program The flowcharts of FIGS. 16 to 18 show a part related to the handling of data created so as to be commonly executed in the simulation programs showing the simulation contents to be executed corresponding to each design level. The program is shown in FIG. 4, and the actual simulation part is executed with the contents described later. Prior to the description of the contents of the simulation process, the part related to the data reading and conversion process will be described below.

The simulation calculation section 23 of the simulation apparatus 21 can store the fact that the design level simulation processing executed in the past has been executed. As will be described later, when the simulation is started, When it is necessary to read out the data required in the simulation processing of that design level from the program of the data model used in the simulation processing of another design level, the data is used by using the information at that time. There is.

When the simulation program is started, the simulation device 21 first displays the data input screen on the display device 26 (step R1), and the items of input data necessary for executing this simulation program are displayed. It will be displayed to the user. Subsequently, it is determined whether or not a program of another level has already been executed (step R2), and when the simulation is performed for the first time, that is, when the simulation process of another design level is not executed, When it is determined to be "NO", the process proceeds to step R3.

In the above case, the design level 1
In many cases, the first time simulation is usually performed, and when performing the simulation processing of the design level 2 or 3, the previous simulation has already been performed. Is generally.

Subsequently, the simulation apparatus 21 simultaneously displays the system model used in this design-level simulation processing on the input screen. As a result, the user operates the mouse while observing the screen to arrange each element of the required data model at a desired position and creates a system model on the input screen. 21 performs an input process with the arrangement information of each element of the set system model as data inside (step R4). Then, when the model input is completed (step R5), the simulation apparatus 21 moves to step R11 described later.

Further, when it is judged "NO" in step R2, the simulation device 21 shifts to step R6. In this case, the fact that the simulation process of another design level has already been performed means that there is data newly obtained when the simulation process is executed, and each element of the model used for the simulation at that time is determined. Therefore, when the simulation process is executed using that data, the user gives an input instruction to use the updated data, so the simulation device 21 returns “YES” in step R6. The determination is made, and the process proceeds to step R7.

Even if the simulation processing of another design level has already been carried out, if the user does not use the data obtained at that time, the user inputs an instruction to that effect. Is determined to be “NO” in step R6, the process proceeds to step R3, and steps R3 to R5 are performed in the same manner as described above, and then the process proceeds to step R11 in the same manner.

Next, in step R7, the simulation apparatus 21 accesses the program of the simulated data model, reads the model and data, and performs data conversion processing on the read data. (Step R8). In this case, in the data conversion process, the simulation device 21 performs an operation of converting the data read from another program into a value necessary as the data used in its own program according to the data conversion rule described in the program. The processing is performed, and the above-mentioned data conversion rule is applied. Then, the converted data is displayed on the data input screen so as to be used as the input data (step R9). Similarly, the model read from the program of the other data model is also displayed in a state where each element is arranged on the display screen of the system model (step R10).

When the simulation device 21 proceeds to step R11, it waits for the user to input necessary data using the data input display screen. At this time, in the execution of the simulation program, in the display part where the necessary data is not entered,
For example, preset data can be displayed in a state of being input and set as default data. The user can input data by rewriting the data of the portion that needs to be changed to desired data and inputting the data.

Then, when the user inputs data, the input process is executed corresponding to each (step R
11) Finally, when the user inputs an instruction indicating that all the data has been input, the simulation apparatus 21 determines “YES” in step R12 and proceeds to step R13. Then, the simulation device 21 captures the data input accordingly (step R13) and becomes ready to execute the simulation process.

Subsequently, in the simulation apparatus 21, the simulation calculation unit 23 executes the simulation processing based on the various input data to calculate the initial values of the design parameters (step R14), and then there. The obtained design target model and parameters are stored in the storage device 31 (step R15).

Next, if there is a change setting input for the preset default value condition as the simulation condition (step R16), the simulation condition is changed and set (step R17). The process waits until a processing start command is input (step R18). Then, when the user inputs the simulation start command, the simulation device 21 causes the simulation operation unit 23 to execute the simulation process according to the program (step R19).

In the above case, the simulation conditions include setting conditions such as the time interval of the simulation steps and the display condition of the number of simulation steps per unit time in the animation display.
The user can set desired conditions.

Regarding the contents of the simulation process in step R19, the calculation is executed according to the simulation program set corresponding to the simulation of each design level. , Which will be described later. It should be noted that the results obtained along with this simulation processing are subjected to calculation processing by the display processing calculation section 24 such that they are displayed as animation, for example, and are sequentially displayed at a predetermined timing on the display device 26.
To be displayed.

When the user confirms the animation on the display screen after the series of simulation processes is completed and the confirmation input is made (step R20), the simulation device 21 determines that the confirmation input is "OK". (Step R21) stores the simulation result in the storage device 31 (step R22), calculates other design parameter data obtained by this simulation processing (step R23), and further obtains the result. If necessary, the data is displayed on the display device 26 such as a graph in a visually easy-to-understand manner (step R24).

In this case, a program for creating a visually easy-to-understand display screen such as a graph or a table for the simulation result is stored and set in the storage device 31 as a program of the same format as the data model. In response to a data display request, the processing calculation unit 24 reads out such a display program, performs display processing that meets predetermined conditions, creates a graph or table, and displays the display device 2.
6 is displayed.

Next, the evaluation of the result of the simulation performed as described above is accepted by the user (steps R25, R26),
When the evaluation result is "OK" (step R27), the obtained result is stored in the storage device when the update process is performed according to the designation of whether or not to perform the data update process (step R28). It is stored in 31 (step R29), the program is terminated, and the process returns to the main program.

On the other hand, if the data conversion process is not to be performed, it is determined to be "NO" in step R28, the program is terminated, and the process returns to the main program. If the evaluation input is not "OK" in step R27, a satisfactory result is not obtained in the simulation process, and therefore the process proceeds to step R30.

In this case, since the desired result is not obtained in the simulation at the design level just performed, the setting of the input data is changed and the simulation process at the design level is repeatedly executed, or By returning to the design level of the previous stage and executing the corresponding simulation process to obtain improved data, it is assumed that the simulation process of this design level is executed again.

Therefore, the simulation device 21
Waits for the user to input an instruction as to whether or not to perform another simulation, and when the user inputs an instruction, the following process is performed.

In this case, the simulation device 21
When there is an instruction input to execute this simulation again, in order to change the setting of the input data, the process jumps to step R9 and the above-mentioned processing is repeatedly executed. Further, when returning to the simulation of the design level of the former stage, it is determined as “NO” in step R30 and the process proceeds to step R31, where the simulation conditions of the design level of the former stage are displayed to prompt the user to confirm. After that, the program will end and return to the main program.

Description of Main Display Screen Next, the details of designing an actual production line by executing the simulation processing at each design level as described above will be described below together with the display screen. FIG. 19 shows a main display screen 51 of the simulation apparatus 21. When the main program is started, such a main display screen 51 is first set. In this case, in the display device 26, such a display screen can be arranged at an arbitrary position on the screen. For example, by arranging the display screen at a position closer to the left end, another display operation can be performed. You will be able to let the rest do it. Below are the general contents of this main display screen 51 for design level 3
The case where is set will be described as an example.

In FIG. 19, first, a "Control Panel" display section 52 showing that it is the main display screen 51 for controlling the entire simulation apparatus 21 is displayed on the uppermost stage, and on the lower right side thereof. "Run" for setting the run mode to start the dynamic simulation
A display unit 53 and an "Edit" display unit 54 for mode setting for editing the model are displayed. On the lower side, a "Level" display section 55 showing, for example, level 3 is displayed as the design level of the simulation for setting or changing the setting.

Further, as a display screen corresponding to the above-mentioned design level 3, the "Start" display section 56 for starting and stopping the simulation process is located on the left side in order from the top, and the simulation is executed step by step. A “Step” display unit 57 as a switch for switching, a “Display” display unit 58 as a switch for changing and setting the on / off mode of the simulation screen display, and a “Parameter calculation switch as a parameter calculation switch for changing the design parameter value from the simulation result. The “Calc” display portion 59 is displayed.

A "Timer" display unit 60 for inputting a timer value is displayed at the lower part of these display units. The "Time Interval" display unit 60a displays the time interval in the simulation, and The number of steps is displayed on the "Steps 1 sec" display section 60b. Below that, "Grid" of the grid value input of the simulation screen
A display unit 61 is displayed, in which the scale of the simulation screen is displayed on the "Ratio" display unit 61a and the grid interval is displayed on the "Interval" display unit 61b.

A "Production System" display section 62 as an editor function is displayed at the lower part of these. This includes "Crea" to create a new model.
"te" display unit 62a, "Move" display unit 62b for moving the position of the model, "Resize" display unit 62c for changing and setting the size of the model, "Delete" display for setting the deletion of the model A section 62d, a "Relate" display section 62e for making a relation between the models, and a "Route" display section 62f for setting the route of the AGV are displayed.

Further, a model selection display portion 63 is displayed on the right side of them. Here, in order from the top, as the type of model to be placed, "AAG" display section 63a for setting simple route, "CPR" for setting production instruction
Setting the parameters of the display section 63b, AGV "Set AG
"V" display 63c, BOX for setting BOX parameters
"BOX" display 63d, home station setting "HS" display 63e, stop station "S"
"S" display section 63f, "Node" display section 63 for setting contacts
g, a "Road" display portion 63h for setting a traveling path is displayed.

When performing an operation input using the main display screen 51, for example, an operation input device called a mouse is used to move an index indicated by an arrow or the like on the screen to a desired position. By operating a switch provided on the mouse in this state, setting input is possible.

Description of Design Level 1 Simulation Content Next, the content of the design level 1 simulation processing will be described based on the display state of the main display screen 51 described above. First, when the design level change display unit 55 is turned on and the design level is set to "1", a display screen corresponding to the corresponding setting situation is set. Now, when the "Display" display section 58 is turned on so as to set the simulation screen, the display area 71 is set in the margin of the main display screen 51 of the display device 25 (see FIG. 20).

Then, the system model is set by arranging the elements of the production system to be designed in this display area 71 with reference to the screen. In this case, the user arranges the settings according to the desired conditions according to the design of the concept level. In this case, first, "Create"
The mode setting is performed by operating the display unit 62a, and the model selection display unit 63 is used to select the corresponding model from the display units 63a to 63h and set the layout in the display area 71.

In this case, since this is the case where the simulation of the design level 1 is performed, this is the first time that the system model is set. Therefore, the elements are arranged in the display area 71 and set. When changing the arrangement of each element, the "Resize" display section 62b,
"Move" display section 62c or "Delete" display section 62d
By selecting and setting, the size changing, moving, or deleting setting processing is performed. Also, the relationship between each element is
This is performed by selectively setting the "Relate" display portion 62e, and the route of the transport system is determined by selectively setting the "Route" display portion 62f.

Then, in the example shown in FIG. 20, for example,
As a model of the production system, the processing lines 72 and 73 are set as two "Lines" set at the beginning of the process, and the processing line 74 is set as a "Line" set at the final stage. There is. And between these processing lines 72, 73 and 74, "Store"
Automated warehouse 75 that is placed as
Transfer systems 76 and 77, which are connected as "sfer", are arranged.

Subsequently, the data input screen as shown in FIGS. 23 to 26 is set, and the user inputs necessary data. In this case, since the planned item is new, in the input screen shown in FIG. 23, the "new" display section 81a and the "rationalized" display section 81 are displayed.
From "b", the "new" display 81
Select and set a.

Further, FIG. 24 for inputting each item of the product configuration
On the input screen shown in, the setting items are sequentially input for each displayed item using the mouse. That is, the "number of products" display section 82a and the "average lot size" display section 82
b. Input desired data respectively corresponding to the "production amount per day" display portion 82c and the "product unit price" display portion 82d. The "stock amount (rationalization)" display section 82e
For, it is not necessary to enter because it is the data required in the rationalization mode.

Subsequently, in the input screen shown in FIG. 25 for inputting various data of system specifications / conventional conditions, similarly, setting and input of each item is sequentially performed using the mouse. That is, the "area saving" display portion 83a and the "saving stock" display portion 8
3b, corresponding to the "other expected effect" display portion 83c, the "total effect" display portion 83d, the "production form" display portion 83e, the "maximum allowable inventory amount" display portion 83f, and the "maximum investment amount" display portion 83g. Input the desired data respectively.

Next, in the input screen shown in FIG. 26 for inputting data relating to each model of the system configuration, "*" in the figure is displayed.
Enter and set the necessary data for each part except for the items marked with. That is, each model element “Line” 7 described above
2, 73, 74, "Store" 75 and "Transfer" 7
Since the Nos. 6 and 77 are arranged in the table in the numbered state, the “previous process”,
Input each data of "Post-process" and "Operating time", and also input the data of "Automation rate", "Number of workers", "Investment amount" in "Minimum configuration" and "Number of processes" The data of is also set to be input. As for the three items of "maximum allowable investment amount", "lead time" and "stock amount", the data obtained as a result of the simulation is displayed.
There is no need to input as data.

When the necessary data is input and the instruction to start the simulation processing is input as described above, the simulation apparatus 21 starts the simulation processing and first performs the static calculation as shown below. Execute it and calculate the data of "maximum allowable investment amount", "lead time" or "stock amount" for each individual system,
Furthermore, "Total" data, which is the total value of the data obtained as a result of those calculations, is calculated and displayed in the relevant part of the table in the figure.

The arithmetic expressions used in the static calculation in the above case are set in the following relationship, for example. Further, the values set as the variables a to g in these equations are actually constant values stored in advance in the storage means 31, and are set as reference data for designing the production system. Basic unit data ".

Maximum allowable investment amount = (number of workers × a) + investment amount Stock amount = (number of processes × b) + c Lead time = (stock amount × operating time × operating rate d) /
(Daily production)

As the value of the system as a whole,
It is calculated as follows. Overall system effect = Other expected effect + (area saving xe)
+ (Inventory amount x Product unit price x f) Maximum allowable investment amount = Σ (Each maximum allowable investment amount) + (Overall system effect x g) Inventory amount = Σ (Each inventory amount) Lead time = Σ (Each lead time)

In the above case, in the case shown in FIG.
When the designer converts the minimum investment amount as a set value with a low automation rate centered on workers into a minimum configuration and inputs it, the simulation device 21 causes the automation rate to be 10%.
The allowable investment amount is calculated so that the number of workers becomes 0%, that is, the number of workers becomes zero. In addition, lead time and inventory quantity values will also be calculated using the static approximation formula described above based on data such as production volume and operating time. The expected effect amount due to the increase in area will also be calculated.

When the simulator 21 calculates static data in this way, it then displays the resulting data. This is shown in the table shown in FIG. 26 and based on the calculation results shown in FIG.
It can also be displayed in the form of a graph based on linear programming as shown in FIG. That is, in this graph, the investment level is examined, the horizontal axis shows the automation rate (%), and the vertical axis shows the investment amount (million yen) and the inventory amount (pieces). Indicates the investment amount with a solid line and the inventory amount with a broken line. Further, the horizontal line indicates the lower limit value of the target of each item, and a predetermined width than this is set as the target area.

In this graph, for example, a solution that satisfies both the investment amount and inventory amount targets cannot be obtained. Therefore, it is concluded that the result is that the system configuration must be reviewed and further cost reduction efforts must be made. In this way, based on the data obtained as a result of the simulation, the work of obtaining the target value of the investment amount and the stock amount used in the design level 2 and thereafter is repeated.

As a measure against the above result, for example, the automation rate is set to 90% or more (the automation rate at the point where the broken lines shown by the arrows in the figure intersect 90%), and the capital investment amount is set to 50%. It is possible to obtain the data that satisfies the desired condition by investigating in the direction of setting the value to be reduced by more than 10 million yen (shifting the graph of the calculation result shown by the thick solid line in the figure to the graph shown by the alternate long and short dash line). become able to. Therefore, in subsequent simulations, it is sufficient to proceed with detailed design based on this data. Further, in the system design of the design level 2 or later, the design work is carried out under the condition that the cost reduction is aimed at with the goal of fully automation (automation rate of 90% or more).

When the simulation processing is completed in this way and desired data is obtained, data is stored in the data storage area in the program so that the obtained data can be used in the subsequent simulation at the design level. Remember and exit the program.

Description of Database Used in Design Levels 2 and 3 (a) Schematic Description of Database Now, data is obtained in the design level 1 as described above, and data is obtained as a result of the simulation process. So, design level 2 and 3 after that
In, the following database is constructed based on the data obtained here. Although this database will be described in detail later, its outline will be described here.

That is, in the design level 1, the whole production system is handled as one database, but the construction of the production system after the design level 2 depends on various combinations of individual systems (line, transfer system, etc.). Since it is established, it is necessary to build a database in units of individual systems and also in units of components of individual systems.

Therefore, a database having a format as shown in FIGS. 28 to 40 is set corresponding to such a database. That is, the data tables shown in FIGS. 28 to 40 include input / output data directly handled by the user, as well as intermediate data and items used in internal processing. The calculation is performed based on the conversion formula stored internally.

Further, the feature of such a database is that it includes two types of data, that is, data obtained by static calculation and data obtained as a more accurate value by simulation. With such a database configuration, for example, in design level 2, static calculation is first performed, simulation is performed based on the static data, and as a result, static calculation is performed. The data can be obtained as data with higher accuracy than the data obtained by calculation, and the design accuracy can be improved.

Also, by collecting the data of the results obtained by the simulation of the lower design level 3 and re-obtaining the data, it is adopted as highly accurate data when the simulation is performed again at the design level 2. Now, the accuracy of the data handled each time a simulation is executed at each design level is improved.

In the present embodiment, two types of data, static data and data obtained from simulation results, are displayed together, and based on this,
By changing the setting flag inside the database, the user can easily perform the process for improving the accuracy of the data.

(B) Description of Detailed Contents of Database The details of the above-described database shown in FIGS. 28 to 40 will be described. FIG. 28 shows a table of the production management database (FsCPR00003) in the design level 1, and here shows that the data of the indication time of the transport system is displayed on the screen. Further, FIG. 29 is a database (FsSetBox) of a box (Box) for storing the work in the design level 2.
[00002] table, in which “Length” indicating length data and “Cap” indicating capacity data are shown.
a. Is displayed.

The ones shown in FIGS. 30 and 31 are
3 is a table of a processing line database (FsLMC00004) and an assembly line database (FsLAS00017) in the design level 2, respectively.
2 is the contents of the tables in these databases (GUI; graphi
cal user interface) and internal processing data that is intermediate data that is not displayed on the display device 26 but is necessary for internal processing.

For example, in FIG. 30, as the data of the machining line, the cycle time is displayed in the "Cycle Time" display section 91a and the lead time is displayed in the "Lead Time" display section 91b. The time and lead time are displayed. In addition, "WorkRa" that displays data indicating the line utilization rate
"te" display section 91c, display sections 91d, 91e, 91f showing the inventory quantity of the line with maximum, average, and minimum data, a display section 91g showing the tact time of the line, a display section 91h showing the production capacity of the line, and equipment. Display unit 91 showing cost
i, a display unit 91j showing the running cost, a display unit 91k showing the number of workers, and a display unit 91 showing the number of workpieces being processed.
m and the like are sequentially provided.

Of the data shown in each of the display sections 91a to 91m, the data shown on the left is static data, and is static based on the input data or the input data or the basic unit data. The data obtained by various calculations are shown. For example, in this, the line average inventory data is the lead time divided by the cycle time, and the line production capacity data is calculated as the unit time divided by the cycle time multiplied by the line operating rate. The input data is set as it is for other data.

Further, the data shown on the right side show the data obtained as a result of executing the simulation processing, and for example, these are obtained by using the internal processing data shown in the lower column of FIG. That is, as the internal processing data, data such as transaction average processing time, transaction average staying time, transaction total passing amount, transaction maximum staying amount, transaction average staying amount, transaction minimum staying amount, operating time, and number of in-process transactions are set. Has been done. And, for example, as the line utilization rate data,
It is the value obtained by multiplying the total transaction amount by the tact time and dividing this by the operating time.

Similarly, static data and simulation result data are also displayed in the assembly line database, and a display screen as shown in FIG. 31 is displayed on the display device 26. ing.

FIG. 33 and FIG. 34 are databases (FsSST00012) related to the design level 2 automated warehouse.
Table and the contents including those data and internal processing data. In this case, for example, in FIG.
Various data relating to the automated warehouse including the display section of the automated warehouse inventory content showing detailed information of the inventory quantity in a table are displayed separately as static data and simulation result data. A breakdown of the static data settings and a breakdown of the simulation result settings are shown,
The internal processing data required to generate the simulation result data is also shown.

Further, in FIGS. 35 and 36,
Design level 2 database of AGV system (FsA
AG00020) table and the contents including those data and internal processing data are shown. In FIG. 35, AGV
Various data in the system are displayed separately as static data and simulation result data. In FIG. 36, the contents of these data and the contents of intermediate internal processing data for obtaining the display data are shown. And are shown. Note that “AGV”, “AGV”, etc. in FIG. 36 indicate data obtained by the simulation of “AGV” at the design level 3, and details are shown in FIGS. 39 and 40. ing.

Next, in FIGS. 37 and 38, the database (FsACN) of the loading / unloading conveyor of the design level 2 is used.
00013) and the contents including those data and internal processing data. In FIG. 37, various data on the loading / unloading conveyor are displayed separately as static data and simulation result data. In FIG. 38, the contents of these data and the intermediate for obtaining the display data are shown. The contents of typical internal processing data are shown.

39 and 40, the AGV database (FsSetAGV0 of design level 3) is used.
0001) and the contents including their data and internal processing data. In FIG. 39, various data in AGV are displayed separately as static data and simulation result data. In FIG. 40, the contents of those data and an intermediate internal for obtaining the display data are shown. The contents of the processed data are shown.

Description of Simulation Contents of Design Level 2 In the design level 2, as described above, the simulation is carried out based on the data obtained as a result of the simulation processing performed in the design level 1. Here, the design of the outline specifications is performed for each individual system such as the processing line and the transfer system. Then, in order to achieve the investment scale and automation level obtained in the simulation of the design level 1, the specifications of each system are obtained by simulation processing. In this case, the design level 2 is to determine the specifications of the individual system for satisfying the requirements of the entire system.

However, since it is necessary to determine the highly feasible specifications as an individual system, whether the AGV system using an AGV (unmanned guided vehicle) is adopted in the transport system, Alternatively, it will be examined based on the concrete contents such as whether to adopt a conveyor system that conveys by laying a belt conveyor or the like. In addition, at this time, the data used for the simulation processing and the data obtained with experience are used with relatively high accuracy. Further, in the transport system, data having a relatively high degree of abstraction is used, such as using the transport distance as data, so that the design using the detailed data is performed after proceeding to the design level 3.

From the context of the flow of goods defined in the design level 1, the design level 2 supports the creation of the physical distribution system configuration. So, for example,
When “AGV system” is selected, as shown in FIG. 21, the “AGV system” including the “AGV system (AAG)” and the “home station (HS)” is displayed on the model display screen 71 on the display device 26. Will be displayed in. In this case, the AGV system is provided between the processing line or the automated warehouse and the loading / unloading conveyor that serves as a contact point between the AGV system.

At this time, the transportation of the goods in the AGV system takes a route from the home station (HS) → processing line → loading / unloading station → automatic warehouse loading / unloading station → home station (HS), which is the main control. "Relate" in editor mode on screen 51
The relationship between these elements is set by the function executed by selecting the display unit 62e. Also,
In this AGV system, the number of boxes (boxes) to be processed that are transported by the AGV is also input and set.

As the data of the model of this AGV system, the transport amount is calculated based on the daily production amount and the operating time in the design level 1, and the data of the AGV number as a static calculated value is obtained by this. The calculation result is the home station (H
It is used as an initial value of the number of AGVs in S). On the other hand, on the contrary, the lead time and inventory data obtained at the design level 2 are also used as the data at the design level 1.

At the design level 2, the simulation is carried out based on the initial value of the AGV, whereby whether or not the statically obtained data on the number of AGVs is an appropriate value according to the design intention. It becomes possible to examine the determination based on the result of the simulation. As a result of this simulation, statistical data such as the operating rate status of each element, the occupation rate of the buffer or the AGV path, etc. is displayed in a table or a graph, and based on these data, the user can It is being evaluated.

In FIG. 21, for example, design level 1
Compared with the display of the line model (see FIG. 20) performed in step 2, in the design level 2, on the model display screen 71,
Processing line (Line) 72 to LMC (processing line) 7
2a and ACN (conveyor) 72b, processing line (L
ine) 73 to LMC (processing line) 73a and ACN
Expressed as (conveyor) 73b, automatic warehouse (Store)
e) 75 is expressed as an SST (automatic warehouse) 75a and an ACN (conveyor) 75b, and a transfer system (Tr
Transfer) 76 to AAG (AGV route simple) 76
a. It is designed to be displayed as S (home station) 76b on the display device 26. Also, L
The MCs 72a, 73a, and SST 75a are displayed with CPRs 72c, 73c, and 75c serving as production instructing units, respectively.

Then, on the model display screen 71, for example, the relationships between the elements related to the transportation of the AAG 76a are connected by lines as shown in the drawing, and further, as the data relating to those relationships, as shown in FIG. 35 described above. It is designed to input various data and make settings. In the figure, two lines are set for one ACN.
This is to distinguish the loading position and the unloading position. Further, since the other parts are designed in the same manner as described above, detailed description thereof will be omitted.
In the design level 2, the assembly line (Line) 7 is displayed on the model display screen 71 with respect to the display of the model performed in.
4 LSC (assembly line) 74a and ACN (conveyor)
It is expressed as 74b.

Description of Design Level 3 Simulation Content Next, the content of the design level 3 simulation will be described with reference to FIG. The detail of the design level 3 simulation is to carry out a detailed design of the transport system or the AGV system based on the simulation result of the design level 2. Here, a design is performed for obtaining the specifications of the details of the detailed modeling of the part of the design level 2 AGV system.

Specifically, an AGV transport path is set,
The AGV operates in accordance with the condition of the transport path (acceleration after stop, speed of curve, etc.), and performs simulation so that the AGV operates in a manner similar to the actual condition such as waiting if there is a preceding AGV at the intersection. When the work of the AGV is completed, for example, a detailed design (design level 3) of the machining line can be simulated. In this case, the model of the AGV system is returned to the design level 2 stage by reflecting the result of the design level 3, and the design of the machining line model is refined to proceed to the design level 3 in order to design in detail. This enables efficient design.

When the AGV system of the design level 3 shown in FIG. 22 is designed, if the initial target condition cannot be met, it is said that the AGV system is not properly adopted. In this case, it is necessary to return to the design level 2 and study the application of many systems such as conveyors. In such a case, since the conditions are consistent between the design levels, efficient design can be performed.

FIG. 22 shows a case where a specific route layout is designed as a detailed design of the AGV. In this case, if the design level 3 is set on the main control screen 51. On the model display screen 71, the layout state shown in FIG. 22 is displayed from the layout state performed at the design level 2. Then, in this state, the rearrangement of each element according to the layout is reconstructed on the model display screen 71 using the editor function based on the simulation result at the design level 2.

Then, in accordance with the detailed design of the design level 3, the traveling layout of the AGV is created next. First,
Unloading station (SS), curve C (Nod)
e) and the intersection X (Node) are defined in the layout in the screen. Then, each traveling route is set again on this traveling route. Change the travel route to "H. S. → S. S. ],
"S. S. → S. S. ], “S. S. → H. S. In this order, the loop A and the loop B as shown in the drawing are determined as a specific traveling layout by defining along the traveling route. After that, on the data input screen, the detailed data of the AGV used here is input using the screen of the detailed database shown in FIG.

When the data is input, the simulation device 21 executes the simulation process and displays it on the display device 26 by an animation display, and as a result of the simulation process, the operating condition of each element and each AGV layout element are displayed. The statistical data such as the occupancy rate is displayed on the display device 26 in the form of a table or a graph. The user is supposed to evaluate the data of the simulation result based on this.

Regarding the result data obtained by the simulation of the design level 3 as described above, after the simulation of the design level 3 is executed, the data of each element of the design level 2 or 1 in the preceding stage is Can also be rewritten. In this case, the data conversion rule as described above is used and the data is converted to a value suitable for the data format of the element used in the simulation process. Then, since the data is automatically converted by converting it to data of another design level in this way, it becomes possible to perform evaluation using highly accurate data obtained as a result of the simulation.

Regarding such data conversion processing, by selecting and setting the "Calc" display portion 59 of the main control screen 51 described above, the related simulation program is read out and the data conversion rule of the corresponding data is used. Therefore, only the conversion process is performed, and it is not necessary to execute the simulation process each time.

(E) Effects of the Third Embodiment According to the third embodiment as described above, in the design of the production line using the AGV transfer system, the simulation design levels are set in three stages. Since the data to be used is stored in the storage means 31 as a program of the data model in a state of integrally having the model, the data and the data conversion rule, the data used in the previous design level and the result of the simulation can be obtained. By performing the conversion process on the obtained data based on the data conversion rule, the data can be automatically used as the data of the next design level, and the data input work in the repetition of the simulation between the design levels becomes very simple.

As a result, in designing a large production system, even in today's situation where rapid design development is required, it is possible to sufficiently meet the demand, so that the design level from the abstract level to the concrete level can be satisfied. It will be possible to exchange data in a quick and reliable manner, and it will be possible to reduce the occurrence of human error in data input work as much as possible, so that the efficiency of design work can be greatly improved. become.

Also, when adding or changing a data model, the relationship with other data models or the relationship in the system is described as a program and is integrally described with the data conversion rule in the storage device 31. By storing the data, it becomes possible to easily incorporate it into the simulation processing, and it becomes possible to easily perform expansion work even for system development and design change.

Furthermore, by writing a program for creating and displaying a table, a graph, etc. as a data model and storing it in the storage device 31, the simulation can be performed by using the data model in the simulation process. It becomes possible to easily execute the processing without separately providing a table or graph creating program in the program.

(F) Modifications or Extensions of the Invention The present invention is not limited to the above embodiments,
It can be transformed or expanded as follows. The data conversion rule may be stored and set in any form. Further, the data conversion process may be performed at any stage, and therefore, the data conversion process can be performed after the simulation process is executed.

Not only the simulation of the design levels 1 to 3 but also the production management and maintenance system can be expanded and applied. And this gives
Automatically setting the operating conditions of the production line by directly passing each data of the designed production system to each equipment of the production line or by setting the data model to suit each equipment. Furthermore, even if there is a change in specifications, a change in equipment, or a change in setting conditions, it will be possible to automatically cope with this.

Besides the production line, it can be applied to general production systems designed through a plurality of design levels.

[Brief description of drawings]

FIG. 1 is an overall block configuration diagram showing a first embodiment of the present invention.

FIG. 2 is a flowchart of a main program.

FIG. 3 is a flowchart of a data update program

FIG. 4 is an explanatory diagram showing the relationship between programs and data between design levels.

FIG. 5 is an explanatory diagram showing the relationship between adjacent design level data.

FIG. 6 is an explanatory diagram of a data conversion rule.

FIG. 7 is a view corresponding to FIG. 1, showing a second embodiment of the present invention;

FIG. 8 is a diagram corresponding to FIG. 2;

FIG. 9 is a flowchart of a simulation program.

FIG. 10 is an explanatory diagram showing a relationship between a design level and a flow in designing a production system.

FIG. 11 is an explanatory diagram showing the flow of design levels 1 to 3 in detail.

FIG. 12 is an explanatory diagram conceptually showing the structure of a production system.

FIG. 13 is an explanatory diagram showing a correspondence relationship between data of a production system and execution of a simulation device.

FIG. 14 is an explanatory diagram showing a relationship between a model corresponding to a design level and data handling.

FIG. 15 is an explanatory diagram showing a data relationship between design levels.

FIG. 16 is a flowchart of a simulation program (No. 1)

FIG. 17 is a flowchart of a simulation program (No. 2)

FIG. 18 is a flowchart of a simulation program (No. 3)

FIG. 19 is an explanatory diagram of a main display screen

FIG. 20 is an explanatory diagram of a model display screen of design level 1.

FIG. 21 is an explanatory diagram of a design level 2 model display screen.

FIG. 22 is an explanatory diagram of a model display screen of design level 3

FIG. 23 is an explanatory diagram of a data input screen of design level 1 (No. 1)

FIG. 24 is an explanatory diagram of a data input screen of design level 1 (No. 2)

FIG. 25 is an explanatory diagram of a data input screen of design level 1 (No. 3)

FIG. 26 is an explanatory diagram of the data input screen of design level 1 (No. 4)

FIG. 27 is an explanatory diagram of a display screen of simulation results of design level 1.

FIG. 28 is an explanatory diagram of a display screen showing a table of a production management database of design level 1.

FIG. 29 is an explanatory diagram of a display screen showing a table of a database of boxes that store works of design level 2;

FIG. 30 is an explanatory diagram of a display screen showing a database table of design level 2 processing lines.

FIG. 31 is an explanatory diagram of a display screen showing a table of the database of the assembly line of the design level 2.

FIG. 32 is an explanatory diagram showing the contents of a database of processing lines and assembly lines.

FIG. 33 is an explanatory diagram of a display screen showing a table of a database of a design level 2 automated warehouse.

FIG. 34 is an explanatory diagram showing the contents of the automatic warehouse database.

FIG. 35 is an explanatory diagram of a display screen showing a database table of the design level 2 AGV system.

FIG. 36 is an explanatory diagram showing the contents of the AGV system database.

FIG. 37 is an explanatory diagram of a display screen showing a table of the database of the loading / unloading conveyor of the design level 2.

FIG. 38 is an explanatory diagram showing the contents of the database of the loading / unloading conveyor.

FIG. 39 is an explanatory diagram of a display screen showing a table of a design level 3 AGV database.

FIG. 40 is an explanatory diagram showing the contents of the AGV database.

FIG. 41 is an explanatory view of a basic concept in designing a production system showing a conventional example.

FIG. 42 is a schematic explanatory diagram of design contents of design level 1.

FIG. 43 is a schematic explanatory diagram of design contents of design level 2;

FIG. 44 is a schematic explanatory diagram of design contents of design level 3;

FIG. 45 is a flowchart explaining how to proceed with simulation processing at each design level.

FIG. 46 is a conceptual diagram illustrating the overall flow of designing a production system.

[Explanation of symbols]

21 is a simulation device, 22 is an input / output unit, 23 is a simulation calculation unit, 24 is a display processing calculation unit, 25
Is a data conversion processing unit, 26 is a display device, 27 is an input device, 28 is an external input device, 29 is an external output device, 30
Is a storage device, 30a is a program storage unit, 30b is a data storage unit, 30c is a data conversion rule storage unit, 31 is a storage device, 51 is a main display screen, and 52 is a "Control Pane".
“L” display section, 53 is a “Run” display section, 54 is an “Edit” display section, 55 is a “Level” display section, 56 is a “Start” display section, 57 is a “Step” display section, and 58 is a “Display”. Display section, 59 is "Calc" display section, 60 is "Timer" display section,
61 is a "Grid" display, 62 is a "Production System"
A display unit, 63 is a model selection display unit, 71 is a display area,
72 to 74 are processing lines, 75 is an automatic warehouse, 76, 77
Is a transfer system, 72a and 73a are LMCs (processing lines), 72b and 73b are ACNs (conveyors), 72c,
73c is an unloading station (SS), 74a is L
SC (assembly line), 74b is ACN (conveyor), 7
4c is the unloading station (SS), 75a is SS
T (automatic warehouse), 75b is ACN (conveyor), 75c
Is an unloading station (SS), 76a is AAG
(Simple AGV route), Hb. It is S (home station).

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Fumio Kojima 1-1-1, Showa-cho, Kariya city, Aichi Prefecture Nihon Denso Co., Ltd. (72) Inventor Yoshiro Fukuda 1-1-12, Hachiman-cho, Higashi-Kurume, Tokyo No. 72, Inventor Koichi Suzuki 1-25-1 Nishishinjuku, Shinjuku-ku, Tokyo Within Taisei Construction Co., Ltd. (72) Yoshinori Ikeda 1-2-3 Shibaura, Minato-ku, Tokyo No. Shimizu Construction Co., Ltd.

Claims (5)

[Claims] 1. A production system design support apparatus for performing a simulation and its evaluation in accordance with a plurality of design levels from an abstract design level to a concrete design level to design a production system, A simulation operation unit that executes a simulation program based on data input corresponding to each design level; a data storage unit that stores data used at each design level and data obtained by simulation; Data conversion rule storage means for storing data conversion rules for converting data used at each design level into data used at different design levels; and data conversion rule storage means for storing data used at each design level Other designs based on data conversion rules stored in Data converting processing means and the production system design support apparatus characterized by comprising a converting to the bell of the data. 2. A production system design support apparatus for performing a simulation and its evaluation in accordance with a plurality of stages of design levels from an abstract design level to a concrete design level for designing a production system, A simulation program for executing a simulation corresponding to the design level selected corresponding to each of the plurality of design levels, and data used by executing the simulation program are stored as a data model of the constituent elements of the production system. A data storage unit, the data model is a program unit that defines components corresponding to the simulation content of the set design level of the plurality of design levels, data used in the simulation and the result thereof. Data of And a data conversion rule storage unit that stores a data conversion rule capable of converting the data stored in the data storage unit into data usable at each of the plurality of design levels. A production system design support device characterized in that 3. The production system design support apparatus according to claim 2, wherein a display program for displaying a simulation result of the production system can be stored as a data model of the production system. 4. The production according to claim 2, wherein the conversion program for calculating the data used for the simulation processing of the production system can be stored as a data model of the production system. System design support equipment. 5. The production according to claim 1, wherein the output data obtained by executing the simulation can be selected whether or not to perform the data conversion process. System design support equipment.