JP2000222443A - Drawing management system and computer-readable medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a drawing management system capable of managing the mapping of respective component drawings and respective assembling drawings necessary for executing a module construction method. SOLUTION: When an object to be manufactured is divided into blocks by plural levels from a minimum unit up to a maximum unit in order to manufacture the object in accordance with the module construction method, a block code allocated to a certain block, a block code allocated to a higher block constituted so as to include the block concerned and information for recording the mapping state of a drawing expressing the block concerned are related and registered in an MD constitution tablet for every block.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a drawing management system for realizing a modular construction method for manufacturing a final product by repeating a process of creating a higher order block by combining lower order blocks, and more particularly to an individual order receiving system. The present invention relates to a drawing management system suitable for manufacturing a design product by a module method. The present invention also relates to a computer-readable medium storing a table used in such a drawing management system.

[0002]

2. Description of the Related Art An individual design-to-order product is based on a basic structure that has been determined to some extent. Is a product designed to meet the specifications of

When designing such individually designed products, the size and number of each part are determined after recognizing the product as a set of parts having a specific function. Adjustments were made according to customer requirements. Therefore, the design drawing obtained at the stage of completing the design of the product is a component diagram showing the shape and the like of each of these components and a combination diagram showing a combination relationship between these components. For this reason, such an individual custom-designed product is usually manufactured by manufacturing each component according to each component drawing and then combining each component according to each assembly drawing.

[0004] However, in the case of manufacturing by such a traditional method, even if parts are manufactured in accordance with the part drawing in order from the completed part drawing, the order of completion of the creation of each part drawing is not necessarily the work procedure. Therefore, as a result, it is impossible to assemble the whole unless all parts are manufactured. In this case, the parts manufactured until the completion of the manufacture of all the parts are accumulated as a work waiting for work, so that the cash flow is deteriorated, and the management of the accumulated parts is unnecessary. It caused a problem that it took a lot of trouble. That is, in order to store such parts,
While having to secure a vast temporary storage place,
If it is placed outdoors, rust prevention work and rust removal work will be required. Further, for each individual assembly operation, a parts search operation of searching for a necessary part from a large amount of stored parts is also required, and a considerable loss of operation time was unavoidable.

Further, according to the above-mentioned traditional construction method, the accessory parts to be attached are attached after the main parts and structures constituting the basic skeleton are assembled at an early stage. On the other hand, it was necessary to treat burn marks when welding and to repaint. In addition, work for working at a high place or working in a difficult posture increases in order to attach such accessory small articles, and thus a safety problem arises.

In order to solve the various problems described above, it is desirable to employ a module construction method. This module method gradually increases the size of assembly units toward finished products, such as assembling parts that are the minimum units of manufacturing as units, and then assembling modules as larger units from multiple units. This is the method of construction.

[0007]

By the way, when a large mechanical device is manufactured, individual components become large, and it is difficult to manufacture them all at once in the size as shown in the parts drawings.
Due to the limitations of carrying out from the building and lifting capacity of the hoist,
Actually it was difficult. Therefore, when the module construction method is adopted, it is more convenient to divide a large part into parts of a size suitable for manufacturing and to classify them as components of separate blocks (units or modules). . Therefore, in order to manufacture individual custom-designed products with large overall dimensions by the module method, it is necessary to use a unit other than the part classification based on the functions specified in the design drawings.
That is, it is necessary to reconfigure a product to be manufactured into a unit which is a set of parts of a minimum unit divided for ease of manufacture and a unit of a module as a parent of this unit. Therefore, the drawings necessary for actually performing the work by the module method are drawings at the order receiving stage (that is, component drawings in which parts are divided according to their functions, similar to those used in the above-mentioned traditional method, In addition, the component drawings of each part defined by dividing a single part that fulfills one function into a plurality of parts, and the parts arranged adjacent to each other among these parts Should be an assembly drawing showing the state of each stage (stage of each block) in which.

[0008] However, if these drawings are separately prepared and the parts are manufactured in accordance with the drawings each time they are completed, in-process parts or blocks will eventually accumulate, and as a whole, Work time (work time required from the start of production of the first part to the completion of the whole) may be extended.

Therefore, a first object of the present invention is to manage the release of each part drawing and each assembly drawing necessary for carrying out the module construction method, whereby the generation of in-process parts can be reduced. An object of the present invention is to provide a drawing management system capable of suppressing the entire working time while suppressing the entire operation time, and a computer-readable medium storing a table used in such a drawing management system.

A second object of the present invention is to provide a method for associating work schedules represented by respective drawings (that is, a production process of parts indicated by a part drawing and an assembly operation indicated by an assembly drawing) with a work schedule. It is an object of the present invention to provide a drawing management system which can clarify a work procedure by making it possible to further reduce the occurrence of in-process components and further reduce the work time as a whole. .

[0011]

The present invention has the following features to attain the object mentioned above.

That is, the invention according to claim 1 has been made to solve the first problem, and a final product is manufactured by repeating a process of combining lower blocks and creating a higher block. A drawing management system for managing drawings used in a modular construction method, comprising, for each block in each stage of a manufacturing process according to the module construction method, an identification code assigned to the block, and the block. A medium storing a table in which the drawing status information indicating the drawing status of the drawing representing the block is associated with the identification code given to the upper-level block, and reading the table by accessing the medium and reading the table. Unit, a display unit for displaying the contents of the table read by the reading unit, and a To have an update unit that updates a table, it characterized. With this configuration, since the drawing status of the drawing (part drawing or assembly drawing) representing the block of each stage of the manufacturing process according to the module structure is described in the table stored in the medium. If this is read by the reading unit and displayed by the display unit,
The user can grasp the release status of each drawing.
When a change occurs in the drawing status of each drawing (for example, when a drawing that has not been drawn is displayed), the updating unit appropriately updates the table in the medium. Therefore, since the user can know the latest drawing status, the actual manufacturing process can be performed after confirming that all the drawings have been prepared. Therefore, the stoppage of the process due to the drawing wait is prevented, so that it is possible to suppress the occurrence of unnecessary work due to the stagnation of in-process components.

The invention according to claim 2 is made to solve the second problem, and the table according to claim 1 stores, for each of the blocks, a schedule of a step of creating the block. It is specified by associating the schedule information shown. In this way, the work schedule of the process itself for each block can also be directly managed, so that the work order and schedule can be maintained,
In-process parts can be minimized.

According to the third aspect of the present invention, the release status information of the first aspect is specified by indicating a scheduled release date of the corresponding drawing.

The invention described in claim 4 specifies the release status information of claim 1 by indicating whether or not the corresponding drawing has been released.

According to the invention described in claim 5, the schedule information of claim 2 is specified by indicating the scheduled start date of the corresponding step.

The invention according to claim 6 specifies the schedule information according to claim 2 by indicating the scheduled completion date of the corresponding process.

According to a seventh aspect of the present invention, the display unit according to the first aspect uses the identification code associated with each block and the identification code associated with a higher-order block as clues. The relative relationship is specified by displaying it in a tree format.

According to an eighth aspect of the present invention, the display unit according to the first aspect sorts the identification codes associated with the individual blocks, and the information associated with each block in the sorted order. Is displayed to indicate the item.

According to a ninth aspect of the present invention, the display unit according to the fourth aspect calculates and displays a drawing compliance rate based on the drawing status information associated with each of the blocks, thereby specifying the block. It was done.

According to a tenth aspect of the present invention, the display unit according to the ninth aspect classifies the release status information for each block at an arbitrary stage, and for each classified release status information, the display compliance rate Is calculated and displayed, and thus is specified.

According to an eleventh aspect of the present invention, in the medium of the first aspect, the table is stored for products having a past production record, and the updating unit is configured to execute the update for the products having a past production record. The table is newly identified by appropriately modifying the table, and the table is specified by storing the table in the medium.

According to a twelfth aspect of the present invention, each block in each stage of a manufacturing process according to a module construction method for manufacturing a final product by repeating a process of creating a higher order block by combining lower order blocks, A table in which the identification code assigned to a block and the identification code assigned to a higher-order block including the block are associated with release status information indicating the release status of a drawing representing the block. Is a computer-readable medium characterized by storing

[0024]

Embodiments of the present invention will be described below with reference to the drawings. (Specific examples of individually designed products) First, in order to make the description of the present embodiment easier to understand, the structure of a portal crane which is a specific example of individually designed products whose drawings are managed by the present embodiment will be described. A part drawing group created at the time of receiving an order for this portal crane (that is, a part drawing group of parts classified by respective functions), and a part drawing group and an assembly drawing group created for manufacturing (that is, A description will be given together with a group of parts drawings of each part suitable for assembly and a group of assembly drawings of each block.

The portal crane 100 has the structure shown in FIG. 1, and is a moving tower 101 that moves on a rail (not shown) laid on the ground of a factory, for example, along the X direction in the figure.
And a crane body 106 movably supported on the tower 101 along the Y direction in the figure. The moving tower 101 further includes a rectangular frame-shaped Y-direction rail member 102 for holding both short sides of the crane body 106 slidably in the Y direction, and a vertical direction for supporting four corners of the Y-direction rail member 102. 4 pillars 1
03, four trolleys 104 each having four wheels rolling on rails (not shown) and supporting one of the columns 103 on its upper surface, and two trolleys 104 arranged in the X direction
And a sidewalk 105 installed between the outer wall surfaces so that a worker can move between them.
The portal crane 100 configured as described above moves in the X direction along a rail (not shown) to lift an object placed between the rails (not shown) on the ground of the factory, and It is registered on the object. next,
The crane body 106 moves in the Y direction on the Y-direction rail member 102 of the moving tower 101, and the hook 106a is positioned on the object to be conveyed. In this state, the wire rope is paid out from the crane body 106 and the hook 10
6a is hooked on the numbering object, the wire rope is rewound as it is, and the object to be transported is lifted. Then, the moving tower 101 is appropriately moved along the X direction and the crane body 106 is appropriately moved along the Y direction, so that the object to be carried is carried in a predetermined space.

As described above, at the stage of receiving an order, a part drawing group of parts classified according to their respective functions (design factors of structures, devices, electric components, accessories, etc.) is created. Therefore, in the case of the portal crane 100, the component diagram of each component described above, that is, the component diagram of the crane main body 106 having a function of extending and winding up the hook 106a (the component diagram of the drawing number ES0213 shown in FIG. 2), the crane Body 10
6 (a drawing number ZX07 shown in FIG. 3) of a Y-direction rail member 102 having a function of slidably holding X6 in the X direction.
32, a component diagram of a column 103 having a function of supporting four corners of a Y-direction rail member 102 (a component diagram of drawing number OP1932 shown in FIG. 4), and a cart 4 supporting each column 104 and moving in the X direction. (Part diagram of drawing number PP0131 shown in FIG. 5), and a part diagram of sidewalk 105 (part shown in FIG. 6) that enables an operator to move between two carriages 4 arranged in the X direction. The part number with the number QR1921) is created. Then, in order to organize these parts drawings by approaching them from a functional aspect, a design parts list (EBM [E
ngeineering Bill of Material]) is created. Since only one piece of a part drawing arranged by the EBM is created for parts having the same shape, the number of parts created by each part drawing is described in the EBM.

However, actually, the portal crane 100
Is created, a group of parts drawings of each part and a group of drawings of each block suitable for assembling are created instead of the part drawings arranged by the EBM for the above-described reason.

FIG. 8 shows the portal crane 100 divided into units or modules. As shown in FIG. 8, the Y-direction slide member 102
The beam is divided into each beam arranged in the direction and each beam arranged in the Y direction. Across each dividing line (indicated by a broken line in FIG. 8) of the Y-direction slide member 102, the entire portal crane 100 is divided into three blocks, namely, a traveling module MD01, a traveling module MD02, and a center module MD03. Are classified. Then, these blocks MD01, MD0
2, MD03 is further divided into smaller blocks.
For example, the traveling module MD01 includes a traveling unit U101 composed of each carriage 104 and a sidewalk 105 and a tower structure unit composed of each pillar 103 and a part of the Y-direction slide member 102 at a boundary between each carriage 104 and each pillar 103. U
102. Then, each of these blocks U
101 and U102 are further divided into smaller blocks. For example, the traveling unit U101 is a truck unit B composed of one truck 104 and half of the sidewalk 105.
L01 and BL02 are classified. Each of these blocks BL01 and BL02 is an even smaller block, that is, a block TR made up of wheels and their attached parts.
01, TR11, blocks TR02 and TR12 each including an axle and its accessories, blocks TR03 and TR13 each including a bogie frame and its accessories, and a sidewalk 10.
Block TR04, consisting of 5 fragments and their accessories
It is classified into TR14.

Therefore, the parts drawing group of each part includes the minimum unit blocks TR01... Divided as described above.
Is created for each of the components that make up. In addition, as a group of assembly drawings of each block, an assembly diagram showing a state where lower blocks are combined with higher blocks is created. For example, FIG. 9 is a part diagram (drawing number AF0113) of the wheels and accessories constituting the block TR11.
FIG. 10 is a parts diagram (drawing number AG0331) of the axle and accessories constituting the block TR12, and FIG.
FIG. 12 is a parts diagram (drawing number AD0312) of a bogie frame and accessories constituting the block TR13, and FIG. 12 is a parts diagram (drawing number AE0313) of a sidewalk fragment and accessories constituting the block TR14. These parts drawings are actually three-sided views of each part, but are simplified here and shown as perspective views of main parts in each block. Also, the lower right column in each part drawing
This is a column in which the number of identical parts created according to the part is described.

The combination of these parts manufactured according to the parts drawings of FIGS. 9 to 12 is shown in the assembly drawing of the traveling unit BL02 shown in FIG. 13 (drawing number AA0314).
Is shown in FIG. The combination of this traveling unit BL02 and the other traveling unit BL01 is shown in FIG.
Of the traveling unit U101 shown in FIG.
A3478). The combination of the traveling unit U101 and the tower structure unit U102 is illustrated in the assembly drawing (drawing number CA8231) of the traveling module MD01 shown in FIG.

The person in charge of manufacturing the portal crane 100 is:
The parts clerk (EBM)
When the component drawings arranged in the same manner are created, the module configuration (parent-child relationship of each block) most suitable for the actual situation of the manufacturing is determined in consideration of the past manufacturing results of the same type of portal crane 100 in the past. Then, set the type and number of assembly drawings of each block indicating the determined module configuration,
In order to manage each drawing, an MD configuration table (manufacturing parts list: MBM [Manufacturing Bill of Material
l: manufacturing information].

As shown in FIG. 16, the MD configuration table includes, for each block, a block code (own block code) as an identification code assigned to the block, and a higher-order block including the block. The block code (parent block code) assigned to the block, the EBM number (child number) indicating the function of the block, the item name of the block, the planned number of blocks to be created, and the drawing representing the block was actually created Drawing number (release status information) given at the time, scheduled release date of the drawing (release status information), actual release date of the drawing (release status information), and planned weight of the target block indicated by the bare surface , A process name indicating a process of manufacturing the target block, and a column for listing a scheduled start date and a scheduled completion date (schedule information) of the process.

The own block code and the parent block code in the MD configuration table specify a module configuration formed by each block by being correlated with each other. The own block code and the parent block code are codes automatically given according to the upper and lower levels in the module configuration, and are also referred to as “MBM codes”. The item name, the drawing number, the scheduled release date, the actual release date, and the planned weight are items for managing the release of each drawing, and are collectively referred to as “item information”. Also, the process name,
The scheduled start date and the scheduled completion date are items for managing a part manufacturing or block assembling process according to the drawing, and are collectively referred to as “production information”. As described above, in the MD configuration table, since “production information” is associated with each part drawing, individual drawings are required for blocks having the same shape, unlike the EBM. However, it is also possible to manage that each of them travels between each process on its own schedule as completed products.

When the person in charge of manufacturing the portal crane 100 prepares this MD composition table, the date is appropriately written in the column of scheduled release date in this MD composition table, and the designer is instructed to prepare a drawing. Each time there is a drawing from the designer, the actual drawing number is written in the drawing actual date column and the actual drawing number in the drawing number column.

When all the drawings are obtained in this way, the production manager is required to increase the size from the lower block to the upper block in an order so that the in-process parts do not stay apart as much as possible. Set the scheduled start date and scheduled completion date. Specifically, according to the module configuration shown in FIG. 8, first, each of the blocks TR01 to TR4 belonging to the lower order of the bogie unit BL01 is manufactured, and then the bogie unit BL01 is assembled.
The truck unit BL02 is assembled after the blocks TR11 to TR4 belonging to the lower rank of the second unit 2 are manufactured. Subsequently, the traveling unit U101 is assembled from the both bogie units BL01 and BL02. Subsequently, after assembling the tower structure unit U102 from a predetermined lower block, the traveling module MD01 is assembled from the traveling unit U101 and the tower structure unit 102. Similarly,
Travel module MD02 and center module MD0
3 in order, and finally three modules MD0
The portal crane 100 is completed by combining 1 to 03. By setting the work schedule based on each drawing in such an order, the generation of in-process parts can be minimized, so extra work such as rust prevention work, rust removal work, repainting work, and parts search work is required. Labor can be reduced, and the storage space for parts can be minimized.

When the actual production operation starts, the production supervisor monitors the progress of the actual operation based on the production information in the MD composition table, and appropriately produces the production in accordance with the progress of the actual operation. Update the information and manage the process so that all work can be completed as quickly as possible.

The MD configuration table used as described above is actually constructed as data stored in a computer-readable medium. Therefore, the creation, update, content display, and the like of the MD configuration table are performed as data processing using a computer. Hereinafter, hardware and software of a computer system (drawing management system) according to the present embodiment for executing data processing on such an MD configuration table will be described. (Hardware Configuration of Drawing Management System) FIG. 17 is a block diagram showing a hardware configuration of the drawing management system. As shown in FIG. 17, the drawing management system includes a server 1 and a large number of clients 2 communicably connected to each other via a LAN (Local Area Network) 3 such as Ethernet (registered trademark).
It is configured. The server 1 is a computer that builds various databases (see FIG. 18) in the hard disk 4 and accesses (reads and updates) these various databases. Also, each client 2 has L
A computer that communicates with the server 1 via the AN 3 and requests the server 1 to access various databases.

The server 1 includes a LAN interface 10, a CPU 11, and an RA
M12, disk control unit 13, input interface 14, bus controller 15, and image output interface 16, hard disk 4 connected to disk control unit 13, keyboard 5 and mouse 6 connected to input interface 14, and image output Display 7 connected to interface 16
And from.

Of these, the bus controller 16
The device manages the state of the bus B.

The LAN interface 10 communicates with each client 2 via the LAN 3 so that the CPU 1
1 is sent to the destination client 2 after the data sent to any one of the clients 2 is edited and divided into a packet format suitable for distribution in the LAN 3, and transmitted from the client 2 via the LAN 3. This is a device that edits and combines the received packet format data into a format that can be processed by the CPU 11 and then notifies the CPU 11 of the edited data.

The disk controller 13 has a CPU 11
The device accesses the hard disk 14 in response to an instruction from the CPU 11 and drives the hard disk 14 to read necessary data or write data notified by the CPU 11. The hard disk 14 as a computer-readable medium includes various databases (a serial number master database 31, a standard MD configuration database 32, and a serial number MD) shown in FIG.
Configuration database 33, standard medium schedule database 34,
Production date schedule database 35, result collection database 3
6, and a middle schedule activity pattern database 37 are stored. The contents of each of these databases will be described later in detail.

The input interface 14 is a keyboard 5
Alternatively, it is an interface for coding the input content input by the operator via the mouse 6 and inputting the content to the CPU 11. In the following description, the expression "input by the operator" means "information input by the operator using the keyboard 5 or the mouse 6 is passed to the CPU 11 via the input interface 14".

The image output interface 16 includes the CPU 1
Reference numeral 1 denotes an interface for appropriately converting image data created based on data in the hard disk 4 into a format in which the display 7 can display an image, and outputting the format to the display 7.

The RAM 12 is a main storage device in which the work area of the CPU 11 is expanded, and the drawing management program 20 read from the hard disk 4 is paged in preparation for processing by the CPU 11. Thereby, RAM1
2, each processing unit as shown in FIG. 18 (that is, a model-specific standard MD configuration search unit 21, a serial number MD configuration generation / registration unit 22, a production drawing registration update unit 23, a drawing progress status inquiry unit) 24, a serial number MBM / EBM browsing unit 25, a model-specific standard mid-schedule search unit 26, a serial number mid-schedule development unit 27, a serial number mid-schedule result registration / update unit 28, and a serial number mid-schedule browsing unit 29) Be expanded.

CPU as reading section, display section and updating section
Reference numeral 11 denotes a central processing unit that controls the entire server 1 and executes the drawing management program 20 read from the hard disk 4 to expand the above-described processing units in the RAM 12 and appropriately execute the processing units. To achieve that function. The function of each of these processing units realized by the CPU 11 will be described later in detail. (Software Configuration of Drawing Processing System) Next, FIG.
, The various processing units 21 to 2 developed in the RAM 12 based on the various databases 31 to 37 and the drawing management program stored in the hard disk 4 described above.
The specific contents of No. 9 will be described.

The serial number master database 31 stores the serial numbers and model names (all of which are portal crane) of all individually designed products that have been manufactured in the past at the manufacturing site where the drawing management system was introduced. ) Are listed in association with each other.

The standard MD configuration database 32 stores, for all the serial numbers stored in the serial number master database 31, the MD configuration table used when the individual custom-designed product corresponding to the serial number is manufactured. Database. It should be noted that the MD configuration table stored in the standard MD configuration database 32 is referred to when a new individual order-designed product is manufactured, and its contents are appropriately updated to generate a new MD configuration table. Since it is used as a starting point, it is particularly called a “standard MD configuration table”. Each standard MD configuration table is associated with a unique product name given to an individual design-to-order product created in the past.

The serial number MD configuration database 33 is a database for storing an MD configuration table created for an individual design-to-order product currently being manufactured. Since the MD configuration table stored in the serial number MD configuration database 33 is associated with the serial number given to the individual made-to-order product currently being manufactured, in particular, the “number serial MD”
It is referred to as a “configuration table”.

The standard middle schedule database 34 shows a standard schedule indicating the manufacturing schedule of each block at the time of manufacturing an individually designed product for each serial number stored in the serial number master database 31. Stores the middle schedule pattern table. As shown in FIG. 19, this standard middle schedule pattern table is, for each block constituting the individual custom-designed product, the item name of the block, the scheduled start date, the scheduled completion date, and the start after completion of the block. 5 is a table listing “chains” indicating codes of blocks to be formed and “activity patterns” indicating detailed work patterns (for example, cutting, welding, and painting) for manufacturing the blocks. Each standard mid-schedule pattern table is associated with a unique product name given to an individual design-to-order product created in the past.

The mid-serial production schedule database 35 is a database for storing a mid-schedule pattern table (middle-schedule activity table) created for an individual design-to-order product currently being manufactured. This medium schedule activity table has the same kind of contents as the standard medium schedule pattern table in the standard medium schedule database 34, except that a specific date considering the designated delivery date is written in the scheduled start date and the scheduled completion date. .

The result collection database 36 is a database that records the completion date and work time (actual time) for each block that constitutes the individual custom-designed product currently being manufactured.

The mid-schedule activity pattern database 37 lists various types of activity patterns, and calculates an operation formula (lead time) for calculating the time (lead time) required to perform the work according to each activity pattern. This is a database that stores arithmetic expressions) in association with each activity pattern. Note that the lead time calculation formula is defined as a function of the estimated weight of each block.

The model-specific standard MD configuration search unit 21 reads out all the serial numbers corresponding to the model name input by the operator from the serial number master database 31,
The standard MD configuration table in the standard MD configuration database 32 is searched based on the read serial number, and a list of product names assigned to the standard MD configuration table corresponding to each serial number is displayed. Further, if any of the product names is selected and input by the operator as the one closest to the module configuration of the individual custom-designed product to be manufactured from now on, the model-specific standard MD configuration search unit 21 sets the selected one. The standard MD configuration table corresponding to the product name is downloaded from the standard MD configuration database 32 and passed to the serial number MD configuration generation / registration unit 22.

The production number MD configuration generation / registration unit 22 displays the standard MD configuration table passed from the model-specific standard MD configuration search unit 21 on the display 7 and, based on the instruction input by the operator, Unnecessary rows are deleted from the standard MD configuration table (that is, rows in which blocks that are not scheduled to be added to the custom-designed product to be manufactured from now on) or a new row is added to the standard MD configuration table (that is, , A line in which blocks such as options to be added to the individually designed product to be manufactured are written. For example, as shown in FIG. 20, when a buffer (shock absorbing mechanism) TR15 is optionally added to the bogie unit BL02 of the standard portal crane 100, the buffer TR15 is classified as a lower block of the bogie unit BL02. This buffer TR1
5 must be added (FIG. 21). Therefore, the row of the own block code = TR14 and the own block code = BL0 in the standard MD configuration table having the structure shown in FIG.
As shown in FIG. 22, a line of own block code = TR15 (item name = buffer) is added between the second line and the second line. Further, the serial number MD configuration generation / registration unit 22 serves as an update unit in accordance with the specific data input by the operator in the scheduled release date column, the actual release column, and the scheduled weight column in each row of the standard MD configuration table. Write a specific value corresponding to the individual custom-designed product to be manufactured (note that the drawing of each block is not shown at this time, so the drawing number column is left blank. It is identified only by the block code [temporary figure number], and the scheduled start date column and the scheduled completion date column are also left blank at this time.) Thereby, the production number MD configuration generation /
The registration unit 22 creates a serial number MD configuration table for an individual custom-designed product to be manufactured. Then, the serial number MD configuration generation / registration unit 22 uploads the created serial number MD configuration table to the serial number MD configuration database 33 in association with the serial number of the individually designed product to be created.

The production drawing registration / updating unit 23 stores the drawing number input by the operator when the drawing scheduled to be released according to the production number MD configuration table is actually released.
Write into the drawing number column in the line of the own block code (temporary drawing number) corresponding to the drawing. If a drawing that is not scheduled in the production number MD configuration table is issued due to design reasons, the production drawing registration / update unit 23 inserts a new line into this production number MD configuration table, and And the information about the block indicated by the drawing is written.

The drawing progress inquiring section 24 as a reading section and a display section, when the drawing state inquiry instruction is input by the operator, generates a serial number MD configuration table corresponding to the serial number specified by the operator. The readout rate is read from the serial number MD configuration database 33, and the compliance rate for each block (the number of issued drawings / the number of planned drawings × 100 [%]) is calculated.
3 is displayed on the display 7 as a block-by-block compliance rate graph. In FIG. 23, the compliance rate of the block at the MD level is graphed, but the compliance rate of the block at the BL level or the compliance rate of the block at the U level can be graphed. It is.
When the operator further inputs a drawing progress graph display instruction, the drawing progress inquiry section 24 is scheduled for a block selected from the block-by-block compliance rate graph (FIG. 23) by the operator. For each drawing, whether it has been released (released), whether it has not been released after the scheduled release date (delay delay), or only 10 days until the planned release date Is checked (10 days before the release) or whether the unreleased drawing is still more than 11 days before the scheduled release date (normal unreleased). Then, the drawings are classified according to the check results, and the number of the classified cases is displayed in a bar graph format in which each is classified by color. FIG. 24 is a block-by-block progress color graph used for this display. In the graph shown by FIG. 24, out of the ten drawings scheduled to be released for MD01, one has been released, four have been delayed, and two have not been released normally. In this case, it is shown that three sheets are 10 days before the release.

Serial number MBM · E as readout unit and display unit
The BM browsing unit 25 reads the serial number MD configuration table corresponding to the serial number specified by the operator from the serial number MD configuration database 33, and displays it on the display in the format specified by the operator. Specifically, if the operator specifies the EBM format, the serial number MD
Each row of the composition table is sorted by its EBM number (child number), and the detailed information of each row is arranged in the order of the EBM number, the number, the item number, the planned weight, the standard number, the parent block code, and the own block code ( Display is performed in the format of FIG. 25). In addition, the MBM
When the format of the D configuration table (A) is designated, as shown in FIG. 26, the parent-child relationship of each block is determined based on the combination of the parent block code and the own block code in each row of the serial number MD configuration table. Derived and expressed in a tree format. And beside each block included in this tree,
Item name, process name, estimated weight,
The scheduled start date and scheduled completion date are arranged in a table format. When the format of the MD configuration table (B) of the MBM is designated by the operator, it is displayed in the format as it is in the serial number MD configuration table shown in FIG.

The model-specific standard schedule search unit 26 reads out all the serial numbers corresponding to the model names input by the operator from the serial number master database 31, and based on the read serial numbers, the standard intermediate schedule database. 34
The standard medium schedule pattern table is searched for, and a list of the product names assigned to the standard medium schedule pattern table corresponding to each serial number is displayed. Further, when any of the product names is selected and input by the operator as the closest one to the individual custom-designed product to be manufactured from now on, the model-specific standard middle schedule search unit 26 sets the selected product name to The corresponding standard middle schedule pattern table is downloaded from the standard middle schedule database 34. Then, based on the downloaded standard middle schedule pattern table, an MD creation flow diagram (FIG. 27) in which the middle schedule is developed is created.
It is displayed on the display 7. Specifically, the model-specific standard schedule search unit 26 arranges the block codes and the item names of the blocks described in the standard middle schedule pattern table in the column direction using the chain of the blocks as a clue. Then, based on the scheduled start date and the scheduled completion date of each block, a bar (schedule bar) indicating a period from the scheduled start value to the scheduled completion date is drawn in the row direction corresponding to the time (year / month / day) axis. In FIG. 27, only the middle schedule of the blocks at the BL level or higher is shown, but actually, the middle schedule of the blocks at the TR level is also displayed. In addition, the schedule bar of each block further displays the details of the work specified by the “activity pattern” (how many percent for material cutting, how many percent for welding,
The pattern is divided into a plurality of periods and displayed according to the percentage of the paint, etc.). When the operator inputs a registration instruction after displaying such an MD creation flowchart, the model-specific standard schedule search unit 26 attempts to create a standard middle schedule pattern table from which the MD creation flowchart is based. Upload to the mid-serial production schedule database as a mid-schedule activity table corresponding to the serial number of the custom-designed product to be manufactured.

The serial number developing section 27 operates as a reading section.
The medium schedule activity table corresponding to the serial number input by the operator is read from the serial number schedule database 35 and the serial number MD configuration table corresponding to the serial number is read from the serial number MD database 33. Then, the two are compared, and if the constituent blocks do not match, the row of the middle schedule activity table is added or subtracted to match the constituent blocks of the serial number MD constituent database 33. In addition, when the configuration blocks of the middle schedule activity table and the serial number MD configuration table match each other, the serial number middle schedule developing unit 27 serves as a display unit in the same manner as the model-specific standard schedule search unit 26 does. Next, an MD creation flowchart (FIG. 27) is created based on the medium schedule activity pattern table read from the serial numbering schedule database 35 (however, the schedule bar is not entered). And the production number MD
The expected weight of each block described in the configuration table is substituted into the lead time calculation formula stored in the middle schedule activity database 37 to calculate the lead time required for the process of each block. Then, the process order of each block is specified based on the chain of each block described in the middle schedule activity table. Then, a lead time is assigned to each process so that the end date of the work of the last block (that is, the work of assembling the entire apparatus) is immediately before the delivery date specified by the operator.
Arrange the schedule bar of each block in the MD creation flow diagram with the left-justification. The serial number development schedule development section 27 finely adjusts the length of the schedule bar arranged as described above, when an instruction from the operator is input. Then, as an update unit, the start point and the end point of the schedule bar of each block are determined as the scheduled start date and the scheduled completion date of the block, respectively,
The mid-schedule activity table in which the scheduled start date and the scheduled completion date of each block are written is uploaded (overwritten) to the mid-schedule activity table, and the scheduled start date and the scheduled completion date of each block are numbered MD.
It is written in the production number MD configuration table in the configuration database 33.

The serial number recording schedule update unit 28 reads out the medium date activity table corresponding to the serial number input by the operator from the serial numbering database 35 as a reading unit, and displays the medium numbering schedule as a display unit. Similarly to the developing unit 27, an MD creation flowchart (FIG. 27) is created based on the middle schedule activity table. Then, as an update unit, for the blocks for which work has been completed, the work results (actual work completion date and work time) for each block collected in the result collection database 36
, The schedule bar is rewritten to a performance bar (a color bar different from the schedule bar indicating the actual work period). The end point of the result bar rewritten in this manner may be shifted from the start point of the schedule bar of the next block. The serial number production schedule registration / update unit 28 appropriately adjusts the schedule bar of the subsequent blocks according to the instruction of the operator. Then, based on the adjusted schedule bar and actual result bar, the scheduled start date and the scheduled completion date of each block in the middle schedule activity table are rewritten, and the middle schedule activity table is uploaded to the serial numbering schedule database 35,
The scheduled start and completion dates for each of these blocks are
The data is written in the serial number MD configuration table in the D configuration database 33. .

The serial number schedule viewing section 29 reads the intermediate schedule activity table corresponding to the serial number input by the operator from the serial number schedule database 35 and displays it on the display 7 in the format specified by the operator. (Processing by Drawing Management Program 20) Next, the flow of actual processing by the CPU 11 that has read the drawing management program 20 will be described with reference to the flowcharts of FIGS.

In the first step S001 after this process starts,
The CPU 11 displays a menu screen on the display 7. From this menu, "Create New MD Composition Table",
“Registration of drawings to MD composition table”, “Introduction of drawing progress”, “M
It is possible to select the items of “D configuration browsing”, “new registration of middle schedule activity table”, “middle schedule development”, “result registration”, and “medium schedule browsing”.

In the next step S002, the CPU 11 waits for any one of the items displayed on the menu screen to be selected by the operator. Then, when any item is selected, the CPU 11 switches the subsequent processing according to the selected item. That is, the CPU 11 advances the process to S101 when “Create New MD Configuration Table” is selected, advances the process to S201 when “Register Drawing in MD Configuration Table” is selected, If "Introduction of progress" is selected, the process proceeds to S301. If "View MD configuration" is selected, the process proceeds to S401. If "New registration of middle schedule activity table" is selected, the process is performed. To “S501”, and if “medium schedule development” is selected, the process proceeds to S601; if “result registration” is selected, the process proceeds to S701; and “medium schedule browsing” is selected. The process proceeds to S801.

In S101, the CPU 11 (standard M for each model)
The D configuration search unit 21) waits for the operator to specify and input any model name.

In S102, which is executed when any model name is designated, the CPU 11 (model-specific standard MD configuration search unit 21) stores all the model numbers corresponding to the designated model name in the model master database. Read from 31.

In the next S103, the CPU 11 (model-specific standard MD configuration search unit 21) searches the standard MD configuration database 32 based on all the serial numbers read out in S102, and is associated with each serial number. Read out all the product names.

In the next step S104, the CPU 11 (model-specific standard MD search unit 21) displays a list of all the product names read in step S13 on the display. The product names displayed in this manner can be selected by the operator.

In the next step S105, the CPU 11 (model-specific standard MD search unit 21) waits until any of the displayed product names is selected by the operator.

In S106 executed when any product name is selected, the CPU 11 (model-specific standard MD configuration search unit 21) instructs the operator to download a standard MD configuration table corresponding to the selected product name. Wait for it to come.

At S107 executed when the operator instructs the download, the CPU 11 (standard MD for each model)
The configuration searching unit 21) downloads the standard MD configuration table associated with the product name selected in S105 from the standard MD configuration database 32.

In the next S108, the CPU 11 (serial number MD)
The configuration generation / registration unit 22) displays the standard MD configuration table downloaded in S107 on the display 7.

In the next S109, the CPU 11 (serial number MD)
The configuration generation / registration unit 22) determines, based on information from the operator, that the module configuration of the standard MD configuration table displayed on the display 7 matches the module configuration of the individually designed product to be manufactured. Is determined. If the former does not match the latter, the CPU 11 (serial number MD configuration generation / registration unit 2)
2) In S110, after receiving an input from the operator and appropriately adding or deleting a row in the standard MD configuration table or modifying the information described in each row, the process proceeds to S110.
Return to 109. As a result of repeating the loop processing of S109 and S110, if the module configuration of the standard MD configuration table displayed on the display 7 matches the module configuration of the individually designed product to be manufactured from now on, The CPU 11 (serial number MD configuration generation / registration unit 22) advances the processing from S109 to S111.

At S111, the CPU 11 (manufactured by
The configuration generation / registration unit 22) operates the display 7 at that time.
Wait for the operator to input an instruction to register the standard MD configuration table displayed in (1) as a serial number MD configuration table.

At S112, which is executed when an instruction to register is input, the CPU 11 (serial numbering MD configuration generation / registration unit 22) associates the serial number with the serial number of the individually designed product to be created. The standard MD configuration table displayed on the display 7 is used as the serial number MD configuration table.
Upload to configuration database 33. When S112 is completed, the CPU 11 (serial number MD configuration generation / registration unit 2)
In 2), the process returns to S001.

On the other hand, in S201, the CPU 11 (manufacturing drawing registration / update section 23) waits for an operator to input a drawing registration instruction. In order to register this drawing,
Serial number, drawing number, MBM code of the block corresponding to the drawing in the serial number MD composition table, and item of the block manufactured in accordance with the drawing Manufacturing drawing information such as a name, the number of blocks manufactured according to the drawing, the planned weight of the blocks manufactured according to the drawing, and the like are included as supplementary information.

At S202, which is executed when an instruction to register drawing is input, the CPU 11 (manufacturing drawing registration updating unit 2)
3) Acquires production drawing information from the input drawing registration instruction.

In the next S203, the CPU 11 (manufacturing drawing registration / updating unit 23) generates a manufacturing number MD corresponding to the manufacturing number included in the manufacturing drawing information acquired in S202.
It is read from the configuration database 33 and it is checked whether or not the item name included in the production drawing information matches any of the item names included in the serial number MD configuration table. If the item names do not match, an error display or a mistake list is displayed on the display 7 in S205.

In the next S206, the CPU 11 (manufacturing drawing registration / updating section 23) determines whether the item name mismatch determined in S204 is due to a drawing error (an error in description of the manufacturing drawing information), or It is determined whether this is due to a shortage of rows in the table. When it is determined that the drawing error is caused, the CPU 11 (the production drawing registration / update unit 23) executes S2
At 07, after receiving the correction of the production drawing information by the operator, the process returns to S201. On the contrary,
If it is determined in S206 that the line is insufficient, the CPU
11 (manufacturing drawing registration / update unit 23) returns the process to S201 after accepting the addition or correction of a row to the serial number MD configuration table by the operator in S208.

On the other hand, if it is determined in S204 that the item name included in the production drawing information matches any of the item names included in the serial number MD configuration table, the CP
U11 (manufacturing drawing registration updating unit 23) displays "OK" on the display 7 in S209.

In the next step S210, the CPU 11 (production drawing registration / update section 23) writes the contents of the production drawing information acquired in S202 into a production number MD configuration table corresponding to the production number. After completion of S210, the CPU 11 (manufactured drawing registration / update section 23) returns the process to S001.

On the other hand, in S301, the CPU 11 (drawing progress status inquiry section 24) waits for the operator to specify and input any model name.

In S302, which is executed when the operator designates any model name, the CPU 11 (drawing progress status inquiry section 24) acquires information on the current date at that time.

In the next step S303, the CPU 11 (drawing progress inquiry section 24) determines whether or not the operator wants to display the drawing compliance graph based on the designation input from the operator, or the drawing progress color. It is determined whether the user wants to display a graph. If the CPU 11 (drawing progress status inquiry unit 24) determines that it wants to display the drawing compliance rate graph, it advances the process to S304, and determines that it wants to display the drawing progress color graph. If it is determined, the process proceeds to S307.

In step S304, the CPU 11 (drawing progress status inquiry unit 24) reads the serial number MD configuration table corresponding to the serial number specified in step S301 from the serial number MD configuration database 33, and sets the number of planned drawings for each block. And the number of drawings issued.

In the next step S305, the CPU 11 (drawing progress inquiry section 24) calculates the drawing compliance rate for each block based on the planned drawing number and the drawing drawing number counted in S304. .

In the next step S306, the CPU 11 (drawing progress status inquiry section 24) displays the drawing compliance rate graph for each block (FIG. 23) based on the drawing compliance rate for each block calculated in S305. 7 is displayed. S306
Is completed, the CPU 11 (drawing progress status inquiry unit 24)
Returns the process to S001.

On the other hand, in S307, the CPU 11 (drawing progress status inquiry section 24) waits until any block is selected by the operator.

In S308, which is executed when any block is selected by the operator, the CPU 11 (drawing progress status inquiry unit 24) creates a serial number MD configuration table corresponding to the serial number specified in S301. No. 3 is read from the No. MD configuration database 33 and S3
At 07, the drawing output status of the selected block and all the blocks related thereto are extracted.

Next, the CPU 11 (drawing progress inquiry section 2)
In step 4), a loop process from S309 to S317 is executed in order to check the drawing status of each drawing extracted in S308 one by one. First S3 after entering this loop processing
In 09, the CPU 11 (drawing progress inquiry section 24)
One of the unchecked drawings is specified as a check target, and it is checked whether the scheduled release date of the specified drawing is earlier than the current date acquired in S302.
If the scheduled release date is the same as or before the current date, the CPU 11 (drawing progress status inquiry unit 24) advances the process to S310, and the scheduled release date is earlier than the current date. If so, the process proceeds to S311.

In S310, the CPU 11 (drawing progress status inquiry unit 24) checks whether the drawing to be checked has been released or has not been released yet. And if the drawing to be checked has already been released (if there is a drawing number)
In step S3, the CPU 11 (drawing progress status inquiry unit 24)
In step 13, the register "number of issued items" is incremented. On the other hand, if the drawing to be checked is not shown (when there is no drawing number), the CPU 11
(Drawing progress status inquiry unit 24) increments the register “drawing delay count” in S314.

In step S311, the CPU 11 (drawing progress inquiry section 24) checks whether the drawing to be checked has been released or has not been released yet. If the drawing to be checked has been issued, the CPU 11
The (drawing progress inquiry unit 24) increments the register “number of drawings already released” in S313. On the other hand, if the drawing to be checked has not been published, C
The PU 11 (drawing progress status inquiry unit 24) performs the processing in S31.
Proceed to 2.

In S312, the CPU 11 (drawing progress inquiry section 24) determines the number of days from the current date to the planned release date (if the planned release date is earlier than the current date, a negative value is given). Check if it takes more than 10 days. And the number of days from the current date to the scheduled release date is +
If it has been more than 10 days, the CPU 11 (drawing progress status inquiry unit 24) increments the register “normally unprinted number” in S315. On the other hand, if the number of days from the current date to the scheduled release date is within +10 days, the CPU 11 (drawing progress inquiry section 24).
Is the register “number of cases 10 days before release” in S316.
Is incremented.

S313, S314, S315, S316
Is completed, the CPU 11 (drawing progress status inquiry unit 24) checks in S317 whether or not unchecked drawings from the drawing status extracted in S308 remain. If any unchecked drawings remain, the process returns to S309 so that the next unchecked drawing is to be checked. On the other hand, if there are no unchecked items, the CPU 11
In step S318, the (drawing progress status inquiry unit 24) registers the “drawing completed number”, the register “drawing delayed number”,
The register “No. of unshown figures” and the register “No.
A progress color-coded graph for each block (FIG. 24) is displayed based on each value of “number of cases before 0 days.” After completion of S318, CP
U11 (drawing progress status inquiry unit 24) performs the processing in S001.
Return to

On the other hand, in S401, the CPU 11 (serial number M
The BM / EBM browsing unit 25) waits for the operator to specify a serial number.

In S402 executed when the serial number is designated by the operator, the CPU 11 (serial number MBM-E)
The BM browsing unit 25) selects the serial number M corresponding to the specified serial number.
The D configuration table is read from the serial number MD configuration database 33.

In the next S403, the CPU 11 (serial number MB
The M / EBM browsing unit 25) displays an MD configuration output selection menu on the display 7. From this menu,
Each item of “EBM”, “MD configuration (A)” and “MD configuration (B)” can be selected.

In the next S404, the CPU 11 (serial number MB
The M / EBM browsing unit 25) waits for any one of the items to be selected by the operator. Then, if “EBM” is selected, the process proceeds to S405, and if “MD configuration (A)” or “MD configuration (B)” is selected, the process proceeds to S407.

In S405, the CPU 11 (serial number MBM
The EBM browsing unit 25) reads the serial number M read in S402.
Sort each row of the D composition table according to its EBM number (child number). In the next step S406, the columns of each line sorted in step S405 are rearranged in the order of the EBM number, the number, the item number, the planned weight, the standard number, the parent block code, and the own block code.
5) is created and displayed on the display 7.

On the other hand, in S407, the CPU 11
(Production number MBM / EBM browsing unit 25) checks whether “MD configuration (A)” or “MD configuration (B)” is selected by the operator. And
When “MD configuration (A)” is selected, the CPU 11
In step S408, the (manufacturing number MBM / EBM browsing unit 25) derives the parent-child relationship of each block based on the combination of the parent block code and the own block code in each row of the manufacturing number MD configuration table read out in S402, and forms a tree. Format (however, each block constituting this tree is arranged on a different line). In the next step S409, the item name of the block, the item name of the block,
By arranging the process name, the planned weight, the planned start date, and the planned completion date in a table format, an MD configuration table (A) (FIG. 26) is created and displayed on the display 7.

On the other hand, in S410, the CPU 11
(Production number MBM / EBM browsing unit 25) sorts each row of the production number MD configuration table read in S402 by its own block code. In the next S411, the serial number MD configuration table sorted in S410 is displayed on the display 7 as the MD configuration table (B).

When any one of S406, S409 and S411 is completed, the CPU 11 (manufacturer of the serial number MBM / EBM browsing unit 2)
5) returns the processing to S001.

On the other hand, in S501, the CPU 11 (model-specific standard schedule search unit 26) waits for the operator to specify and input any model name.

In S502, which is executed when any model name is given, the CPU 11 (model-specific standard mid-schedule search unit 26) determines all the serial numbers corresponding to the specified model name.
Read from the serial number master database 31.

In the next step S503, the CPU 11 (model-specific standard schedule search section 26) searches the standard medium schedule database 34 based on all the serial numbers read out in S502, and associates them with each serial number. Read out all the product names.

In the next step S504, the CPU 11 (the model-specific standard middle schedule search unit 26) displays a list of all the product names read in S503 on the display. The product names displayed in this manner can be selected by the operator.

In the next step S505, the CPU 11 (model-specific standard schedule search unit 26) waits until any of the displayed product names is selected by the operator.

In S506 executed when any of the product names is selected, the CPU 11 (model-specific standard middle schedule search unit 26) stores the standard middle schedule pattern table corresponding to the selected product name in the standard middle schedule database. Download from 34. Then, based on the downloaded standard middle schedule pattern table, an MD creation flowchart (FIG. 27) in which the middle schedule is developed is created.

In the next step S507, the MD creation flow chart (FIG. 27) created in S506 is displayed on the display 7.

In the next step S508, the CPU 11 (model-specific standard schedule search unit 26) registers the standard medium schedule pattern table based on the creation flow diagram (FIG. 27) displayed on the display as a numbering activity table. Waits for the operator to instruct.

In S509, which is executed when the operator instructs to register, the CPU 11 (model-specific standard middle schedule search unit 26) stores the standard middle schedule pattern table downloaded from the standard middle schedule database 34 in S506. In association with the serial number of the individually designed product to be manufactured, it is uploaded to the serial numbering schedule database 35 as a serial number activity table. S50
When Step 9 is completed, the CPU 11 (model-specific standard schedule search unit 26) returns the process to S001.

On the other hand, in S601, the CPU 11 (the mid-serial numbering schedule developing unit 27) waits for any one of the serial numbers to be designated by the operator.

At S602, which is executed when any of the serial numbers is designated, the CPU 11 (the serial number developing section 27)
Indicates the MD configuration table corresponding to the specified serial number
It is read from the configuration database 33.

In the next step S603, the CPU 11 (the mid-serial number schedule developing unit 27) reads out the mid-schedule activity table corresponding to the serial number designated in S601 from the mid-serial number schedule database 35.

In the next step S604, the CPU 11 (the mid-serial number schedule developing section 27) compares the MD configuration table read in S602 with the MBM code (own block code) in the middle schedule activity table read in S603. And the MBM code of the middle schedule activity table is M
A check is made to see if the block code in the D configuration table matches the block code without excess or deficiency. If there is an excess or deficiency, the process proceeds to S607.

In this S607, the CPU 11 (the mid-serial production schedule development section 27) executes the M
It is checked whether the BM code is insufficient for the own block code in the MD composition table or whether the MBM code not in the MD composition table is included in the middle schedule activity table. If an MBM code not included in the MD configuration table is included in the middle schedule activity table, the CPU 11 (the mid-serial production schedule developing unit 27) proceeds to S60.
In step 8, the line to which the MBM code not included in the MD configuration table belongs is deleted from the middle schedule activity table. After the completion of S608, the CPU 11 (during-serialization schedule developing unit 2)
7) returns the processing to S603.

On the other hand, if the MBM code in the middle schedule activity table is insufficient for the own block code in the MD configuration table, the CPU 11 (the mid-serial numbering schedule developing unit 27) proceeds to step S608. The schedule activity pattern database 37 is searched, and the next S609
In, all activity patterns stored in the middle schedule activity pattern database 37 are displayed on the display.

In the next step S610, the CPU 11 (the mid-serial production schedule developing section 27) executes the
From the displayed activity patterns, it is determined whether or not there is an activity pattern that matches the process of the missing block. If there is a matching activity pattern, the process proceeds to S612 after accepting the operator's selection of the activity pattern in S611. On the contrary,
When there is no activity pattern that matches the process of the missing block, the CPU 11 (the mid-serial numbering schedule developing unit 27) in S613, after receiving an input of an original activity pattern by the operator, proceeds to S612. Proceed. In S612, the CPU 11 (the mid-serial production schedule developing unit 27) adds one line to the mid-schedule activity table, and supplies the missing MBM code and production serial number M.
The planned weight read from the corresponding row in the D composition table,
Then, the activity pattern selected in S611 or the unique activity pattern input in S613 is written. When S612 ends, the CPU 11
(Serial numbering schedule developing unit 27) returns the process to S603.

When the loop processing of S603 to S613 described above is repeated and it is determined in S606 that the MBM code in the middle schedule activity table matches the own block code in the MD configuration table without excess or deficiency. The CPU 11 (the mid-serial production schedule developing unit 27) advances the process from S606 to S614. In this S614, C
The PU 11 (the mid-serial number schedule developing unit 27) waits until the designated delivery date of the individually designed product to be manufactured is set by the operator.

S executed when specified delivery date is set
At 615, the CPU 11 (the mid-serial production schedule developing unit 27)
The planned weight of each block described in the serial number MD configuration table read in S602 is extracted.

In the next step S616, the CPU 11 (the mid-serial number schedule developing section 27) reads, for each block, the activity pattern corresponding to the block from the middle schedule activity table read in S603. Then, a lead time calculation formula corresponding to the read activity pattern is read from the middle schedule activity pattern database 37. Then, the expected weight extracted in S615 is substituted into the lead time calculation formula to calculate the lead time.

In the next step S617, the CPU 11 (the mid-serial production schedule developing section 27) displays the MD creation flow chart on the display 7 based on the middle schedule activity table, and also describes the flow chart in the middle schedule activity table. The process order of each block is specified based on the “chain” of each block. Then, the lead time calculated in S616 is assigned to each flocking process, and the schedule of each block is displayed in the MD creation flow diagram so that the end date of the work of the last block is immediately before the delivery date specified by the operator. Draw the bar with the left justified.

In the next step S618, the CPU 11 (the mid-serial production schedule developing section 27) executes the M
Check whether fine adjustment of the schedule bar drawn on the D creation flow diagram is necessary. If fine adjustment is not required, the process proceeds directly to S620. If fine adjustment is required, the process proceeds to S620 after accepting fine adjustment of the schedule bar by the operator in S619.

In S620, CPU 11 (during-serialization schedule developing section 27) waits for an instruction to register a during-serialization schedule by the operator.

In S621, which is executed when the operator instructs the registration of the mid-serial production schedule, the CPU 11 (the mid-serial production schedule development unit 27) executes the processing of the schedule bar of each block drawn on the MD creation flowchart. Start point and end point, respectively
The scheduled start date and the scheduled completion date of the block are determined, and the middle schedule activity table in which the scheduled start date and the scheduled completion date of each block are written is uploaded to the serial numbering schedule database 35 (overwriting).
The scheduled start and completion dates for each of these blocks are
The data is written in the serial number MD configuration table in the D configuration database 33. After the completion of S621, the CPU 11 (the mid-serial number schedule developing unit 27) returns the processing to S001.

On the other hand, in S701, the CPU 11 (the mid-serial numbering schedule result registration / update unit 28) waits for any one of the serial numbers to be designated by the operator.

In S702 executed when any of the serial numbers is designated, the CPU 11 (the mid-serial numbering schedule result registration / updating unit 28) stores the mid-schedule activity table corresponding to the serial number designated in S701. It is read out from the database 35 during serial numbering.

In the next step S703, the CPU 11 (the mid-serial production schedule result registration / updating unit 28) creates an MD creation flow chart based on the middle schedule activity table read in the step S702, and displays this on the display 7. indicate.

In the next step S704, the CPU 11 (the mid-serial numbering schedule result registration / updating unit 28) executes the result collection database 36.
To check whether there is a block for which work has been completed. If there is no block for which the work has been completed, the CPU 11 (the mid-serial numbering schedule developing unit 27) advances the process to S706. On the other hand, if there is a block for which work has been completed, the CPU 11 (the mid-serial numbering schedule result registration / updating unit 28), in S705, executes the work result (actual number) for each block collected in the result collection database 36. Work completion date and work time)
After rewriting the schedule bar for the completed block to the result bar, the process proceeds to S706.

In S706, the CPU 11 (the mid-serial numbering schedule result registration / updating unit 28) determines whether it is necessary to change the schedule bar for the block that is being worked on or has not been started based on an instruction from the operator. I do. Then, when the schedule bar does not need to be changed, the CPU 11 (the mid-serial numbering schedule result registration updating unit 28) advances the processing to S708 as it is. On the other hand, if the schedule bar needs to be changed, the CPU 11 (serial numbering schedule result registration update unit 28)
In S707, after appropriately adjusting the schedule bar on the MD creation flow chart in accordance with the instruction of the operator, the process proceeds to S7.
Proceed to 08.

In S708, the CPU 11 (the mid-serial numbering schedule result registration / updating unit 28) determines the starting point and the ending point of the result bar and the schedule bar drawn on the MD creation flow chart at that time in the corresponding block, respectively. It is determined as the scheduled start date (start date) and the scheduled completion date (completed date). And the scheduled start date (start date) of each block determined in this way
In addition to uploading (overwriting) the mid-schedule activity table overwriting the scheduled completion date (completion date) to the serial numbering schedule database 35, the scheduled start date (start date) and scheduled completion date (completion date) of each of these blocks ) Is written in the serial number MD configuration table in the serial number MD configuration database 33. S
After completion of step 708, the CPU 11 (the mid-serial production schedule result registration update unit 28) returns the processing to S001.

On the other hand, in S801, the CPU 11 (the mid-serial numbering schedule browsing unit 29) waits until one or a plurality of serial numbers are designated by the operator.

In S802 executed when the serial number is designated by the operator, the CPU 11 (the serial number browsing section 29) displays a browse menu on the display 7. From this menu, each item of "designation of serial number" and "designation of multiple serial numbers" can be selected.

In the next step S803, the CPU 11 (the mid-serial numbering schedule browsing unit 29) waits for any one of the items to be selected by the operator. If “designation of serial number” is selected, the process proceeds to S804, and “designation of multiple serial numbers” is performed.
If is selected, the process proceeds to S806.

In S804, the CPU 11 (medium production number schedule browsing unit 29) reads the medium production activity table corresponding to the production number specified in S801 from the production medium production schedule database 35. Then, in the next S805, the CPU 11 (the serial number browsing unit 29) performs the MD based on the medium schedule activity table extracted in S804.
A creation flow diagram is created and displayed on the display 7.

On the other hand, if it is determined in S803 that “designation of a plurality of serial numbers” has been selected, the CPU 11 (the mid-serial numbering schedule result registration / updating unit 28) proceeds to S806.
In S801, all the middle schedule activity tables corresponding to the plurality of serial numbers specified are read from the serial number schedule database 35.

In the next step S807, the CPU 11 (the mid-serial numbering schedule result registration / updating unit 28) checks whether or not a plurality of middle dates are displayed for each workplace in accordance with an instruction from the operator. And when displaying by workplace, CPU1
1 (serial numbering schedule result registration updating unit 28) extracts information on the workplace designated by the operator from each of the medium-schedule activity tables in S809.
In 810, the middle schedule (MD creation flowchart) is displayed on the display 7 based on the information extracted in S809. On the other hand, if you do not want to display by workplace,
The PU 11 (the mid-serial production schedule result registration update unit 28) executes S80
At 8, a summary of each middle schedule activity table extracted at S806 is displayed on the display 7.

When S805, S808, and S810 are completed, the CPU 11 (the mid-serial numbering schedule result registration update unit 28)
The process returns to S001.

[0138]

According to the drawing management system of the present invention configured as described above, it is possible to manage the release of each part drawing and each assembly drawing required for implementing the module construction method. As a result, the generation of in-process components is suppressed, and the overall work time can be reduced as compared with the conventional method, even when manufacturing the same product. further,
According to the drawing management system of the second aspect, since the information relating the work schedule and the work schedule represented by each figure can be associated with each figure, the work procedure can be clarified. Therefore, the occurrence of useless work is suppressed as much as possible, and the work time as a whole is further reduced.

[0139]

[Brief description of the drawings]

FIG. 1 is a perspective view of a portal crane showing an example of an individually designed product.

FIG. 2 is a component diagram of a crane body constituting the portal crane of FIG.

FIG. 3 is a component diagram of a Y-direction rail member constituting the portal crane of FIG. 1;

FIG. 4 is a component diagram of a column constituting the portal crane of FIG. 1;

FIG. 5 is a component diagram of a truck constituting the portal crane of FIG. 1;

FIG. 6 is a component diagram of a sidewalk constituting the portal crane of FIG. 1;

FIG. 7 is a design parts list (EBM) for managing the parts drawings of FIGS. 2 to 6;

FIG. 8 is an explanatory diagram showing a module configuration of the portal crane of FIG. 1;

FIG. 9 is a diagram showing parts of wheels constituting the portal crane of FIG. 8;

FIG. 10 is a component diagram of an axle constituting the portal crane of FIG. 8;

FIG. 11 is a part view of a bogie frame constituting the portal crane of FIG. 8;

FIG. 12 is a component diagram of a sidewalk fragment constituting the portal crane of FIG. 8;

FIG. 13 is an assembly drawing of a bogie unit.

FIG. 14 is an assembly drawing of a traveling unit.

FIG. 15 is an assembly drawing of a traveling module.

FIG. 16: Standard MD configuration table (MBM)

FIG. 17 is a block diagram of a drawing management system as one embodiment of the present invention;

18 is a software configuration diagram showing a relationship between various databases stored in the hard disk in FIG. 17 and processing units developed in the RAM when the CPU executes a drawing management program.

FIG. 19: Standard Medium Schedule Pattern Table

FIG. 20 is a perspective view of a portal crane with an optional buffer added.

FIG. 21 is a component diagram of the buffer of FIG. 20;

FIG. 22 shows M in which the line in which the buffer is written is inserted
D composition table

FIG. 23 is a compliance rate graph for each block.

FIG. 24 is a graph of the progress color for each block.

FIG. 25: Drawing schedule

FIG. 26: MD calibration business (A)

FIG. 27 is an MD creation flowchart.

FIG. 28 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 29 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 30 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 31 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 32 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 33 is a flowchart showing processing executed by a CPU that has read a drawing program;

FIG. 34 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 35 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 36 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 37 is a flowchart showing processing executed by a CPU that has read a drawing program.

[Description of Signs] 1 server 4 hard disk 7 display 11 CPU 12 RAM 20 drawing management program 22 serial number MD configuration generation / registration unit 23 production drawing registration / update unit 24 drawing progress status inquiry unit 25 serial number MBM / EBM browsing unit 27 Serial numbering schedule development section 28 Serial numbering schedule result registration / update section 29 Serial numbering schedule reading section 33 Serial number MD configuration database 35 Serial numbering schedule database

────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] February 19, 1999 (Feb.
9)

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] 0026

[Correction method] Change

[Correction contents]

As described above, at the stage of receiving an order, a part drawing group of parts classified according to their respective functions (design factors of structures, devices, electric components, accessories, etc.) is created. Therefore, in the case of the portal crane 100, the component diagram of each component described above, that is, the component diagram of the crane main body 106 having a function of extending and winding up the hook 106a (the component diagram of the drawing number ES0213 shown in FIG. 2), the crane Body 10
6 is a component diagram of a Y-direction rail member 102 having a function of holding the slide member 6 slidably in the Y direction (drawing number ZX07 shown in FIG.
32, a component diagram of a column 103 having a function of supporting four corners of a Y-direction rail member 102 (a component diagram of drawing number OP1932 shown in FIG. 4), and a cart 4 supporting each column 104 and moving in the X direction. (Part diagram of drawing number PP0131 shown in FIG. 5), and a part diagram of sidewalk 105 (part shown in FIG. 6) that enables an operator to move between two carriages 4 arranged in the X direction. The part number with the number QR1921) is created. Then, in order to organize these parts drawings by approaching them from a functional aspect, a design parts list (EBM [E
ngeineering Bill of Material]) is created. Since only one piece of a part drawing arranged by the EBM is created for parts having the same shape, the number of parts created by each part drawing is described in the EBM.

[Procedure amendment 2]

[Document name to be amended] Statement

[Correction target item name] 0054

[Correction method] Change

[Correction contents]

The production number MD configuration generation / registration unit 22 displays the standard MD configuration table passed from the model-specific standard MD configuration search unit 21 on the display 7 and, based on the instruction input by the operator, Unnecessary rows are deleted from the standard MD configuration table (that is, rows in which blocks that are not scheduled to be added to the custom-designed product to be manufactured from now on) or a new row is added to the standard MD configuration table (that is, , A line in which blocks such as options to be added to the individually designed product to be manufactured are written. For example, as shown in FIG. 20, when a buffer (shock absorbing mechanism) TR15 is optionally added to the bogie unit BL02 of the standard portal crane 100, the buffer TR15 is classified as a lower block of the bogie unit BL02. This buffer TR1
5 must be added (FIG. 21). Therefore, the row of the own block code = TR14 and the own block code = BL0 in the standard MD configuration table having the structure shown in FIG.
As shown in FIG. 22, a line of own block code = TR15 (item name = buffer) is added between the second line and the second line. Further, the serial number MD configuration generation / registration unit 22 serves as an update unit in accordance with the specific data input by the operator in the scheduled release date column, the actual release column, and the scheduled weight column in each row of the standard MD configuration table. Write a specific value corresponding to the individual custom-designed product to be manufactured (note that the drawing of each block is not shown at this time, so the drawing number column is left blank. It is identified only by the block code [temporary figure number], and the scheduled start date column and the scheduled completion date column are also left blank at this time.) Thereby, the production number MD configuration generation /
The registration unit 22 creates a serial number MD configuration table for an individually designed product to be manufactured. Then, the serial number MD configuration generation / registration unit 22 uploads the created serial number MD configuration table to the serial number MD configuration database 33 in association with the serial number of the individually designed product to be created.

[Procedure amendment 3]

[Document name to be amended] Statement

[Correction target item name] 0060

[Correction method] Change

[Correction contents]

The serial number recording schedule update unit 28 reads out the medium date activity table corresponding to the serial number input by the operator from the serial numbering database 35 as a reading unit, and displays the medium numbering schedule as a display unit. Similarly to the developing unit 27, an MD creation flowchart (FIG. 27) is created based on the middle schedule activity table. Then, as an update unit, for the blocks for which work has been completed, the work results (actual work completion date and work time) for each block collected in the result collection database 36
, The schedule bar is rewritten to a performance bar (a color bar different from the schedule bar indicating the actual work period). The end point of the result bar rewritten in this manner may be shifted from the start point of the schedule bar of the next block. The serial number production schedule registration / update unit 28 appropriately adjusts the schedule bar of the subsequent blocks according to the instruction of the operator. Then, based on the adjusted schedule bar and actual result bar, the scheduled start date and the scheduled completion date of each block in the middle schedule activity table are rewritten, and the middle schedule activity table is uploaded to the serial numbering schedule database 35,
The scheduled start and completion dates for each of these blocks are
The data is written in the serial number MD configuration table in the D configuration database 33.

[Procedure amendment 4]

[Document name to be amended] Statement

[Correction target item name] 0062

[Correction method] Change

[Correction contents]

In the first step S001 after this process starts,
The CPU 11 displays a menu screen on the display 7. From this menu, "Create New MD Composition Table",
"Drawing registration to MD composition table", "Drawing progress inquiry", "M
It is possible to select the items of “D configuration browsing”, “new registration of middle schedule activity table”, “middle schedule development”, “result registration”, and “medium schedule browsing”.

[Procedure amendment 5]

[Document name to be amended] Statement

[Correction target item name] 0063

[Correction method] Change

[Correction contents]

In the next step S002, the CPU 11 waits for any one of the items displayed on the menu screen to be selected by the operator. Then, when any item is selected, the CPU 11 switches the subsequent processing according to the selected item. That is, the CPU 11 advances the process to S101 when “Create New MD Configuration Table” is selected, advances the process to S201 when “Register Drawing in MD Configuration Table” is selected, If “inquiry of progress” is selected, the process proceeds to S301. If “view MD configuration” is selected, the process proceeds to S401. If “new registration of middle schedule activity table” is selected, the process proceeds. To “S501”, and if “medium schedule development” is selected, the process proceeds to S601; if “result registration” is selected, the process proceeds to S701, and “medium schedule browsing” is selected. The process proceeds to S801.

[Procedure amendment 6]

[Document name to be amended] Statement

[Correction target item name] 0067

[Correction method] Change

[Correction contents]

In the next S104, the CPU 11 (model-specific standard MD search unit 21) displays a list of all the product names read in S103 on the display. The product names displayed in this manner can be selected by the operator.

[Procedure amendment 7]

[Document name to be amended] Statement

[Correction target item name] 0072

[Correction method] Change

[Correction contents]

In the next S109, the CPU 11 (serial number MD)
The configuration generation / registration unit 22) determines, based on information from the operator, that the module configuration of the standard MD configuration table displayed on the display 7 matches the module configuration of the individually designed product to be manufactured. Is determined. If the former does not match the latter, the CPU 11 (serial number MD configuration generation / registration unit 2)
2) In S110, after receiving an input from the operator and appropriately adding or deleting a row in the standard MD configuration table or modifying the information described in each row, the processing is performed in S10.
Return to 9. As a result of repeating the loop processing of S109 and S110, if the module configuration of the standard MD configuration table displayed on the display 7 matches the module configuration of the individually designed product to be manufactured from now on, The CPU 11 (serial number MD configuration generation / registration unit 22) advances the processing from S109 to S111.

[Procedure amendment 8]

[Document name to be amended] Statement

[Correction target item name] 0075

[Correction method] Change

[Correction contents]

On the other hand, in S201, the CPU 11 (manufacturing drawing registration / update section 23) waits for an operator to input a drawing registration instruction. In order to register this drawing,
Serial number, drawing number, MBM code of the block corresponding to the drawing in the serial number MD structure table, and item name of the block manufactured in accordance with the drawing, , The number of blocks manufactured according to the drawing, the planned weight of the blocks manufactured according to the drawing, and the like, are included as supplementary information.

[Procedure amendment 9]

[Document name to be amended] Statement

[Correction target item name] Brief description of drawings

[Correction method] Change

[Correction contents]

[Brief description of the drawings]

FIG. 1 is a perspective view of a portal crane showing an example of an individually designed product.

FIG. 2 is a component diagram of a crane body constituting the portal crane of FIG.

FIG. 3 is a component diagram of a Y-direction rail member constituting the portal crane of FIG. 1;

FIG. 4 is a component diagram of a column constituting the portal crane of FIG. 1;

FIG. 5 is a component diagram of a truck constituting the portal crane of FIG. 1;

FIG. 6 is a component diagram of a sidewalk constituting the portal crane of FIG. 1;

FIG. 7 is a design parts list (EBM) for managing the parts drawings of FIGS. 2 to 6;

FIG. 8 is an explanatory diagram showing a module configuration of the portal crane of FIG. 1;

FIG. 9 is a diagram showing parts of wheels constituting the portal crane of FIG. 8;

FIG. 10 is a component diagram of an axle constituting the portal crane of FIG. 8;

FIG. 11 is a part view of a bogie frame constituting the portal crane of FIG. 8;

FIG. 12 is a component diagram of a sidewalk fragment constituting the portal crane of FIG. 8;

FIG. 13 is an assembly drawing of a bogie unit.

FIG. 14 is an assembly drawing of a traveling unit.

FIG. 15 is an assembly drawing of a traveling module.

FIG. 16: Standard MD configuration table (MBM)

FIG. 17 is a block diagram of a drawing management system as one embodiment of the present invention;

18 is a software configuration diagram showing a relationship between various databases stored in the hard disk in FIG. 17 and processing units developed in the RAM when the CPU executes a drawing management program.

FIG. 19: Standard Medium Schedule Pattern Table

FIG. 20 is a perspective view of a portal crane with an optional buffer added.

FIG. 21 is a component diagram of the buffer of FIG. 20;

FIG. 22 shows M in which the line in which the buffer is written is inserted
D composition table

FIG. 23 is a compliance rate graph for each block.

FIG. 24 is a graph of the progress color for each block.

FIG. 25: Drawing schedule

FIG. 26: MD configuration table (A)

FIG. 27 is an MD creation flowchart.

FIG. 28 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 29 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 30 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 31 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 32 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 33 is a flowchart showing processing executed by a CPU that has read a drawing program;

FIG. 34 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 35 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 36 is a flowchart showing processing executed by a CPU that has read a drawing program.

FIG. 37 is a flowchart showing processing executed by a CPU that has read a drawing program.

[Procedure amendment 10]

[Document name to be amended] Statement

[Correction target item name] Explanation of sign

[Correction method] Change

[Correction contents]

[Description of Signs] 1 server 4 hard disk 7 display 11 CPU 12 RAM 20 drawing management program 22 serial number MD configuration generation / registration unit 23 production drawing registration / update unit 24 drawing progress status inquiry unit 25 serial number MBM / EBM browsing unit 27 Serial numbering schedule development section 28 Serial numbering schedule result registration / update section 29 Serial numbering schedule reading section 33 Serial number MD configuration database 35 Serial numbering schedule database

[Procedure amendment 11]

[Document name to be amended] Drawing

[Correction target item name] Fig. 1

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 12]

[Document name to be amended] Drawing

[Correction target item name] Figure 2

[Correction method] Change

[Correction contents]

FIG. 2

[Procedure amendment 13]

[Document name to be amended] Drawing

[Correction target item name] Figure 3

[Correction method] Change

[Correction contents]

FIG. 3

[Procedure amendment 14]

[Document name to be amended] Drawing

[Correction target item name] Fig. 4

[Correction method] Change

[Correction contents]

FIG. 4

[Procedure amendment 15]

[Document name to be amended] Drawing

[Correction target item name] Fig. 5

[Correction method] Change

[Correction contents]

FIG. 5

[Procedure amendment 16]

[Document name to be amended] Drawing

[Correction target item name] Fig. 6

[Correction method] Change

[Correction contents]

FIG. 6

[Procedure amendment 17]

[Document name to be amended] Drawing

[Correction target item name] Fig. 8

[Correction method] Change

[Correction contents]

FIG. 8

[Procedure amendment 18]

[Document name to be amended] Drawing

[Correction target item name] Fig. 9

[Correction method] Change

[Correction contents]

FIG. 9

[Procedure amendment 19]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 10

[Procedure amendment 20]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 11

[Procedure amendment 21]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 22]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 13

[Procedure amendment 23]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 14

[Procedure amendment 24]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 25]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 26]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 27]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 28]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 21

[Procedure amendment 29]

[Document name to be amended] Drawing

[Correction target item name] FIG. 28

[Correction method] Change

[Correction contents]

FIG. 28

[Procedure amendment 30]

[Document name to be amended] Drawing

[Correction target item name] FIG. 29

[Correction method] Change

[Correction contents]

FIG. 29

[Procedure amendment 31]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 32]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 31

[Procedure amendment 33]

[Document name to be amended] Drawing

[Correction target item name] FIG. 32

[Correction method] Change

[Correction contents]

FIG. 32

[Procedure amendment 34]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 33

[Procedure amendment 35]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 34

[Procedure amendment 36]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 35

[Procedure amendment 37]

[Document name to be amended] Drawing

[Correction target item name] Fig. 36

[Correction method] Change

[Correction contents]

FIG. 36

[Procedure amendment 38]

[Document name to be amended] Drawing

[Correction target item name] Fig. 37

[Correction method] Change

[Correction contents]

FIG. 37

Claims (12)

[Claims] 1. A drawing management system for managing drawings used in a module construction method for producing a final product by repeating a process of creating a higher order block by combining lower blocks, comprising: For each block in each stage of the process, the identification code given to the block and the identification code given to the upper-level block including the block are shown together with the release status of the drawing representing the block. A medium storing a table in which drawing status information is associated with each other, a reading unit that accesses the medium and reads the table, a display unit that displays the contents of the table read by the reading unit, An update unit that accesses a medium and updates the table. 2. The drawing management system according to claim 1, wherein the table further associates, for each of the blocks, schedule information indicating a schedule of a step of creating the block. 3. The drawing management system according to claim 1, wherein the release status information indicates a scheduled release date of the corresponding drawing. 4. The drawing management system according to claim 1, wherein the drawing status information indicates whether a corresponding drawing has been released. 5. The drawing management system according to claim 2, wherein said schedule information represents a scheduled start date of a corresponding process. 6. The drawing management system according to claim 2, wherein said schedule information represents a scheduled completion date of a corresponding process. 7. The display unit displays a relative relationship of each block in a tree format based on an identification code associated with each block and an identification code associated with a higher-order block. The drawing management system according to claim 1, wherein: 8. The apparatus according to claim 1, wherein the display unit sorts the identification codes associated with the individual blocks, and displays information associated with each block in the sorted order. Item 2. The drawing management system according to Item 1. 9. The drawing management system according to claim 4, wherein said display unit calculates and displays a drawing compliance rate based on the drawing status information associated with each of said blocks. . 10. The display unit classifies the release status information for each block at an arbitrary stage, and calculates and displays the release compliance rate for each classified release status information. The drawing management system according to claim 9, wherein: 11. The medium stores the table for products having a past production record, and the update unit corrects the table for the products having a past production record as appropriate. Create the table for newly manufactured products,
2. The drawing management system according to claim 1, wherein the drawing is stored in the medium. 12. An identification given to each block in each stage of a manufacturing process according to a module method for manufacturing a final product by repeating a process of creating a higher order block by combining lower order blocks. A table is stored in which a code and an identification code assigned to a higher-level block including the block and release status information indicating a release status of a drawing representing the block are stored. Computer-readable medium.