System for managing drawings and information processing device

Abstract

To provide a system capable of reducing the data volume needed for drawings management.SOLUTION: A system according to the present invention registers, in a database 31, a drawing and a lineage of the drawing that are associated one-to-one or many-to-one, a related data related to a drawing and a lineage of the drawing that are associated one-to-one or many-to-one, a drawing and a project identifying manufacturing request for a product manufactured in accordance with the drawing that are associated one-to-one or one-to-many, many-to-one or many-to-many, a lineage of drawing and a project for identifying a manufacturing request for a product manufactured in accordance with the drawing that are associated one-to-one or one-to-many, many-to-one or many-to-many, a related data related to a drawing and a project identifying manufacturing request for a product manufactured in accordance with the drawing that are associated one-to-one or one-to-many, many-to-one or many-to-many, and a drawing and related data related to the drawing that are not associated, respectively, and provides information corresponding to a browsing request to a user terminal on the basis of the browsing request for the information registered to the database 31 that is received from the user terminal.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to a system and an information processing device for managing drawings. [Background technology]

[0002] Patent Document 1 discloses a technique related to a system for managing drawings. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-091769 A Summary of the Invention [Problem to be solved by the invention]

[0004] There has been a demand for a system that can reduce the amount of data required to manage drawings.

[0005] The present invention has been made in consideration of the above-mentioned points, and an object of the present invention is to provide a system and an information processing device that can reduce the data volume required for managing drawings. [Means for solving the problem]

[0006] As a solution to achieve the above objective, The system for managing drawings of the present invention comprises: A control unit and a storage unit are included. The control unit is Registering a drawing and a system of the drawing in the storage unit in a one-to-one or multiple-to-one linked relationship; Registering in the storage unit a related document related to a drawing and a lineage of the drawing in a one-to-one or multiple-to-one linked relationship; registering the drawings and cases specifying manufacturing requests for products to be manufactured according to the drawings in the storage unit in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a series of drawings and a case that specifies a manufacturing request for a product to be manufactured according to the drawings in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a related document associated with a drawing and a case specifying a manufacturing request for a product to be manufactured according to the drawing in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering the drawings and related materials related to the drawings in the storage unit so as not to link them to each other; When a request to view information registered in the storage unit is received from a user terminal, information corresponding to the request is provided to the user terminal. It is characterized by:

[0007] Also, The control unit is a system indicator is generated for each system registered in the storage unit based on a request for browsing the systems registered in the storage unit from the user terminal, and the generated system indicator is provided to the user terminal; The system mark includes one system registered in the storage unit and a reduced drawing obtained by reducing a drawing associated with the one system. This may be done.

[0008] Also, The control unit is a request to view the cases registered in the storage unit is received from the user terminal, the request generating a case indicator for each case registered in the storage unit is provided to the user terminal, The case indicator includes one case registered in the storage unit and a system associated with the one case. This may be done.

[0009] Also, The control unit is Based on receiving a request to view related materials registered in the memory unit from the user terminal, one category linked to the related materials corresponding to the viewing request may be identified, one or more related materials linked to the identified category may be identified, and reduced related materials obtained by reducing the identified one or more related materials and the related materials corresponding to the viewing request may be provided to the user terminal.

[0010] As a solution to achieve the above objective, The system for managing drawings of the present invention comprises: A control unit and a storage unit are included. The control unit is Based on receipt of a registration request for registering a drawing in the storage unit from a user terminal, a case is generated that specifies a manufacturing request for a product to be manufactured in accordance with the drawing corresponding to the registration request, and the generated case and the drawing corresponding to the registration request are registered in the storage unit in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship. It is characterized by:

[0011] As a solution to achieve the above objective, The system for managing drawings of the present invention comprises: A storage unit in which drawings and the systems of the drawings are registered in a one-to-one or multiple-to-one manner; a control unit that, based on receipt of a request from a user terminal to view a drawing registered in the storage unit, provides the user terminal with a drawing corresponding to the request; Including, The control unit is Based on receiving a registration request from the user terminal to register in the storage unit a related document related to the drawing registered in the storage unit, a system linked to the drawing related to the related document corresponding to the registration request is identified from the systems registered in the storage unit, and the identified system is linked one-to-one or one-to-multiple to the related document corresponding to the registration request, while not linking the related document corresponding to the registration request to the drawing related to the related document corresponding to the registration request. It is characterized by:

[0012] As a solution to achieve the above objective, The information processing device for managing drawings of the present invention comprises: An information processing device for managing drawings, A control unit and a storage unit are provided. The control unit is Registering a drawing and a system of the drawing in the storage unit in a one-to-one or multiple-to-one linked relationship; Registering in the storage unit a related document related to a drawing and a lineage of the drawing in a one-to-one or multiple-to-one linked relationship; registering the drawings and cases specifying manufacturing requests for products to be manufactured according to the drawings in the storage unit in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a series of drawings and a case that specifies a manufacturing request for a product to be manufactured according to the drawings in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a related document associated with a drawing and a case specifying a manufacturing request for a product to be manufactured according to the drawing in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; A drawing is registered in the storage unit so as not to be linked to a related document related to the drawing. It is characterized by: Effect of the Invention

[0013] The present invention can provide a system and an information processing device that can reduce the amount of data required to manage drawings. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a schematic diagram showing a system configuration of the present embodiment. [Diagram 2] FIG. 1 is an explanatory diagram for explaining an overview of the present embodiment. [Diagram 3] FIG. 1 is an explanatory diagram for explaining an overview of the present embodiment. [Figure 4]FIG. 1 is an explanatory diagram for explaining an overview of the present embodiment. [Diagram 5] FIG. 2 is a block diagram showing a hardware configuration of a server. [Figure 6] FIG. 2 is a diagram illustrating a database. [Figure 7] FIG. 11 is an explanatory diagram for explaining an example of a request from a customer to a user. [Figure 8] FIG. 13 is a diagram illustrating an example of a table stored in a database. [Figure 9] FIG. 13 is a diagram illustrating an example of a table stored in a database. [Figure 10] FIG. 13 is a schematic diagram showing an example of a system screen. [Figure 11] FIG. 1 is a schematic diagram showing an example of lineage labeling. [Figure 12] FIG. 13 is a schematic diagram showing an example of a drawing detail screen. [Figure 13] FIG. 13 is a schematic diagram showing an example of a quotation screen. [Figure 14] FIG. 13 is a schematic diagram showing an example of a case screen. [Figure 15] FIG. 13 is a schematic diagram showing an example of a case indicator. [Figure 16] FIG. 13 is a schematic diagram showing an example of a case details screen. [Figure 17] FIG. 13 is a schematic diagram showing an example of a case document screen. [Figure 18] FIG. 18 is an enlarged view of a part of FIG. [Figure 19] FIG. 13 is a schematic diagram showing an example of a linking confirmation screen. [Figure 20] FIG. 13 is a schematic diagram showing an example of a linking screen. [Figure 21] FIG. 21 is an enlarged view of a part of FIG. 20. [Figure 22] FIG. 11 is an explanatory diagram for explaining a screen transition. [Figure 23] 13 is a flowchart showing a system screen generation process. [Figure 24] 13 is a flowchart showing a lineage label generation process. [Diagram 25]10 is a flowchart showing a part of the processing in the system. [Figure 26] 13 is a flowchart showing a drawing detail screen generating process. [Figure 27] 13 is a flowchart showing a quotation screen generating process. [Figure 28] 13 is a flowchart showing a case screen generating process. [Figure 29] 13 is a flowchart showing a first case indicator generating process. [Diagram 30] 10 is a flowchart showing a part of the processing in the system. [Diagram 31] 13 is a flowchart showing a case details screen generating process. [Diagram 32] 13 is a flowchart showing a case document screen generating process. [Diagram 33] 13 is a flowchart showing a linking confirmation screen generating process. [Diagram 34] 13 is a flowchart showing a linking screen generating process. [Figure 35-1] FIG. 1 is an explanatory diagram for explaining specific example 1. [Figure 35-2] FIG. 1 is an explanatory diagram for explaining specific example 1. [Diagram 36] FIG. 13 is a schematic diagram showing an example of a first registration screen. [Figure 37] 11 is a flowchart showing a part of the processing in the system. [Figure 38] FIG. 13 is a schematic diagram showing an example of a second registration screen. [Figure 39] 11 is a flowchart showing a part of the processing in the system. [Diagram 40] 13 is a flowchart showing a process of registering drawings, etc. [Diagram 41] 13 is a flowchart showing a drawing etc. linking process. [Diagram 42] FIG. 13 is a schematic diagram showing an example of a third registration screen. [Diagram 43] 11 is a flowchart showing a part of the processing in the system. [Diagram 44]11 is a flowchart showing a part of the processing in the system. [Diagram 45] 13 is a flowchart showing a quotation registration linking process. [Diagram 46] 11 is a flowchart showing a part of the processing in the system. [Figure 47] 13 is a flowchart showing a new case linking process. [Figure 48] 13 is a flowchart showing an existing case linking process. [Figure 49] FIG. 11 is an explanatory diagram for explaining specific example 2. [Figure 50] FIG. 11 is an explanatory diagram for explaining specific example 3. [Figure 51] FIG. 11 is an explanatory diagram for explaining specific example 4. [Figure 52] 13 is a diagram showing a drawing detail screen according to a modified example of the present embodiment. [Diagram 53] 13 is a diagram showing a lineage marker according to a modified example of the present embodiment. [Figure 54] 13 is a case details screen according to a modified example of the present embodiment. [Figure 55] 11 is a case sign according to a modified example of this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of the present invention (the present embodiment) will be described with reference to the drawings.

[0016] FIG. 1 is a schematic diagram showing the configuration of a system according to this embodiment.

[0017] The system 1 includes a user terminal 10 and a server (information processing device) 20.

[0018] The user terminal 10 is a communication terminal used by a user. The user terminal 10 is, for example, a personal computer. The user terminal 10 is connected to a network 2. The user terminal 10 is connected to a server 20 via an ID (account) or the like that identifies the user.

[0019] The user terminal 10 has an input device 10a and an output device 10b. The input device 10a is, for example, a keyboard or a mouse. The output device 10b is, for example, a display. The output device 10b has a display area 10c.

[0020] The server 20 is an information processing device that processes information and the like transmitted from the user terminal 10. The server 20 functions as a platform necessary for operating the system 1. Programs for performing various processes are installed in the server 20. The server 20 is connected to the user terminal 10 via the network 2. The server 20 is built in a cloud. The cloud is a service that allows the user terminal 10 to freely use software, data, and files on the network 2 without having to hold them.

[0021] FIG. 2 is an explanatory diagram for explaining an overview according to this embodiment.

[0022] The customer shown in FIG. 2 is, for example, a manufacturing manufacturer. The user shown in FIG. 2 is, for example, a factory. The customer requests the user to manufacture a product. In response to the request from the customer, the user manufactures the product according to the drawing and delivers it to the customer. The user registers (stores) various documents (drawings, etc.) exchanged between the customer and the user, customer information, information on the product to be delivered, the delivery date of the product, and other information in the server 20 via the user terminal 10. The various documents include drawings and related documents related to the drawings. The related documents are, for example, a request for quotation, a quotation, a purchase order, a CAD, a product sample photo, a purchase order, a subcontracting order, a material order, a process instruction sheet, an inspection sheet, a performance report, a defect management sheet, a delivery note, an invoice, a copy of an e-mail, a subcontracting quotation, a mill sheet, a copy of a program, a work sample, a daily production report, a QC process chart, a packaging specification, a video of a processing method, and the like. In this embodiment, an estimate is used as an example of a related document, and a description of other related documents is omitted.

[0023] FIG. 3 is an explanatory diagram for explaining an overview according to this embodiment.

[0024] In this embodiment, the user classifies the drawings by system before registering the drawings in the server 20, and according to this classification, the drawings are associated with their systems and registered in the server 20. The user terminal 10 displays a screen (system screen G1, described later) in the display area 10c that enables identification of the system of the drawings.

[0025] 3 is an example of classifying drawings A1, B1, and C1 by system. As shown in the figure, the user classifies drawings A1 and C1 into the same system as system 001, classifies drawing B1 into a different system from drawings A1 and C1 as system 002, and registers them in the server 20.

[0026] In this embodiment, the system of the drawing is configured to be determined arbitrarily by the user, and the system of the drawing can be any combination of numbers, kanji, hiragana, katakana, European letters (uppercase and lowercase), symbols, etc. In the following explanation, the system of the drawing is referred to as "system."

[0027] FIG. 4 is an explanatory diagram for explaining an overview according to this embodiment.

[0028] In this embodiment, a request from a customer can be handled as a case. More specifically, when a user registers a drawing in the server 20, the user can request the server 20 to register a case that specifies a manufacturing request for a product to be manufactured according to the drawing (a case registration request shown in the figure). The user terminal 10 displays a screen that enables identification of the case (a case screen G4 described later) in the display area 10c.

[0029] FIG. 4 shows an example of a case in which server 20 is requested to register a case specifying a manufacturing request for a product to be manufactured in accordance with drawing A1, a case specifying a manufacturing request for a product to be manufactured in accordance with drawing B1, and a case specifying a manufacturing request for a product to be manufactured in accordance with drawing C1.

[0030] FIG. 5 is a block diagram showing the hardware configuration of the server 20. As shown in FIG.

[0031] The server 20 includes a storage unit 30 and a control unit 40. The storage unit 30 and the control unit 40 are electrically connected via a communication bus (not shown).

[0032] The storage unit 30 includes a ROM, a RAM, and a hard disk (not shown). The storage unit 30 stores a program executed by the control unit 40. The storage unit 30 has a database 31 (DB31) and an ID storage area 32. The ID storage area 32 is an area for storing a system ID, a case ID, and a drawing ID.

[0033] FIG. 6 is a schematic diagram of the DB31.

[0034] DB31 stores various tables (TB). The various TBs mainly include a system TB, a drawing TB, an estimate TB, and a project TB. The estimate TB shown in Fig. 6 is a TB (table) that stores estimates. Note that in the figure, only representative tables (TB) necessary for explaining this embodiment are shown, and other TBs are omitted.

[0035] Returning to the explanation of Fig. 5, the control unit 40 includes a CPU, a ROM, and a RAM (not shown). The control unit 40 reads out a program stored in the storage unit 30 and loads it on the RAM to execute various processes.

[0036] 5, the control unit 40 includes a reception unit 41, a registration unit 42, a linking unit 43, a generation unit 44, and a provision unit 45. Upon receiving various requests and various information from the user terminal 10, the control unit 40 generates a predetermined screen by referring to the TB stored in the DB 31 and the ID stored in the ID storage area 32, and provides the generated predetermined screen to the user terminal 10.

[0037] FIG. 7 is an explanatory diagram for explaining an example of a request from a customer (see FIG. 2) to a user.

[0038] Request A is a request to manufacture product A according to drawing A1 and deliver it to a customer. Drawing A1 is classified by the user as system 001. Request A is handled as case A, and case A identifies request A. Quotation A2 is a related document related to drawing A1.

[0039] Request B is a request to manufacture product B according to drawing B1 and deliver it to a customer. Drawing B1 is classified by the user into category 002, which is different from drawing A1. Request B is handled as case B, and case B identifies request B. Quotation B2 is a related document related to drawing B1.

[0040] Request C is a request to manufacture product C according to drawing C1 and deliver it to a customer. Drawing C1 is classified by the user into the same category 001 as drawing A1. Request C is handled as case C, and case C identifies request C. Quotation C2 is a related document related to drawing C1.

[0041] Request D is a request to manufacture product A according to drawing A1 and deliver it to a customer. Request D is handled as case D, and case D identifies request D. Quotation D2 is a related document related to drawing A1.

[0042] Request E is a request to manufacture product A according to drawing A1 and product B according to drawing B1 and deliver them to a customer. Request E is handled as project E, and project E identifies request E. Quotation E2 is a related document related to drawings A1 and B1.

[0043] 8 and 9 are examples of each TB.

[0044] Each TB shown in Figures 8 and 9 registers information corresponding to requests A to E shown in Figure 7. Each TB will be described below.

[0045] Fig. 8(a) is an example of a system TB. The system TB is composed of a system ID and a system. In the example of Fig. 8(a), system 001 and system 002 are registered in the system TB. System 001 is associated with system id1. System 002 is associated with system id2.

[0046] FIG. 8(b) is an example of drawing TB.

[0047] Drawing TB is composed of drawing id, system id, and drawing. In the example of Fig. 8(b), drawings A1 to C1 are registered in drawing TB. Drawing A1 is associated with drawing id1 and system id1. Drawing B1 is associated with drawing id2 and system id2. Drawing C1 is associated with drawing id3 and system id1.

[0048] As shown in Fig. 8(b), drawing A1 is linked to system 001, drawing B1 is linked to system 002, and drawing C1 is linked to system 001. In other words, the systems and drawings are linked in a 1-to-N relationship (N is a natural number; the same applies below).

[0049] FIG. 8(c) is an example of a case TB.

[0050] The case TB is composed of a case ID and a case. In the example of Fig. 8(c), cases A to E are registered in the case TB. For example, case A is associated with case id1.

[0051] FIG. 8(d) is an example of a quotation TB.

[0052] The estimate TB is composed of an estimate ID, a system ID, and an estimate. In the example of Fig. 8(d), estimates A2 to E2 are registered in the estimate TB. For example, estimate E2 is associated with estimate ID5, system ID1, and system ID2.

[0053] As shown in Figure 8(d), quotation A2 is linked to system 001, quotation B2 is linked to system 002, quotation C2 is linked to system 001, quotation D2 is linked to system 001, and quotation E2 is linked to systems 001 and 002. In other words, the systems and quotations are linked in a 1-to-N relationship.

[0054] FIG. 9(a) is an example of a first intermediate TB.

[0055] The first intermediate TB is a table for linking systems and cases in an N-to-N relationship. The first intermediate TB is composed of a first intermediate id, a system id, and a case id. For example, the first intermediate id5 is associated with the system id1 and case id5. For example, the first intermediate id6 is associated with the system id2 and case id5.

[0056] As shown in Fig. 9(a), system 001 is linked to case A, system 002 is linked to case B, system 001 is linked to case C, system 001 is linked to case D, system 001 is linked to case E, and system 001 is linked to case E. In other words, the systems and cases are linked in an N-to-N relationship by the first intermediate ID.

[0057] FIG. 9(b) is an example of a second intermediate TB.

[0058] The second intermediate TB is a table for linking drawings and cases in an N-to-N relationship. The second intermediate TB is composed of a second intermediate ID, a drawing ID, and a case ID. For example, the second intermediate ID1 is associated with the drawing ID1 and the case ID1.

[0059] In Figure 9(b), drawing A1 is linked to case A, drawing B1 is linked to case B, drawing C1 is linked to case C, drawing A1 is linked to case D, drawing A1 is linked to case E, and drawing B1 is linked to case E, and the drawings and cases are linked in an N-to-N relationship by the second intermediate ID.

[0060] FIG. 9(c) is an example of a third intermediate TB.

[0061] The third interim TB is a table for linking quotations and cases in an N-to-N relationship. The third interim TB is composed of the third interim ID, quotation ID, and case ID. For example, the third interim ID1 is associated with the quotation ID1 and case ID1.

[0062] In Figure 9 (c), quotations and cases are linked in a one-to-one relationship, but using the third intermediate ID, quotations and cases can be linked in a one-to-many, many-to-one, or many-to-many relationship.

[0063] Next, an overview of the screen generated by the control unit 40 will be described.

[0064] FIG. 10 is an example of the system screen G1.

[0065] The system screen G1 is a screen for displaying the systems registered in the system TB. The system screen G1 includes a system button P1, a case button P2, a first drawing registration button P3a, and a system indicator H.

[0066] The system button P1 is a button for displaying the system screen G1 in the display area 10c. The case button P2 is a button for displaying the case screen G4 in the display area 10c. The first drawing registration button P3a is a button for registering a drawing in the drawing TB. The system indicator H is an indicator for visually representing a drawing associated with one system registered in the system TB.

[0067] In this embodiment, when the first drawing registration button P3a is selected, the first registration screen G10 (Figure 36) is displayed in the display area 10c, and the drawing can be registered in the drawing TB via this first registration screen G10.

[0068] FIG. 11 is an example of lineage label H.

[0069] The system marker H includes one system registered in the system TB and a reduced drawing obtained by reducing one drawing associated with the one system. In the example shown in Fig. 11(a), the system marker H1 includes system 001 and reduced drawing A1. In the example shown in Fig. 11(b), the system marker H2 includes system 002 and reduced drawing B1.

[0070] In this embodiment, when one system marker H is selected on the system screen G1, the system id corresponding to the selected system marker H is stored in the id memory area 32, and a drawing detail screen G2 for displaying in detail the drawing linked to this system id is displayed in the display area 10c.

[0071] FIG. 12 is an example of the drawing details screen G2.

[0072] The plan detail screen G2 is a screen for displaying in detail one plan registered in the plan TB. More specifically, the plan detail screen G2 is a screen corresponding to the system indicator H (system ID stored in the ID storage area 32) selected on the system screen G1.

[0073] The drawing details screen G2 includes a system button P1, a case button P2, a first drawing registration button P3a, an area G2a, an area G2b, an area G2c, a drawing tab T1, an estimate tab T2, and a case confirmation button P5a.

[0074] Area G2a is an area for displaying in detail one drawing registered in drawing TB. More specifically, area G2a is an area for displaying one drawing out of one or more drawings associated with one system ID (system) stored in id storage area 32. In other words, area G2a is an area for displaying in detail a drawing corresponding to a reduced drawing included in system indicator H selected on system screen G1. In the example shown in FIG. 12, drawing C1 is displayed in area G2a.

[0075] The area G2b is an area for displaying one system associated with the drawing displayed in the area G2a. In other words, the area G2b is an area for displaying a system corresponding to the system indicator H selected on the system screen G1. In the example shown in FIG. 12, system 001 is displayed in the area G2b.

[0076] Area G2c is an area for displaying reduced drawings obtained by reducing one or more drawings registered in drawing TB. More specifically, area G2c is an area for displaying reduced drawings obtained by reducing one or more drawings associated with a system ID (system) stored in ID storage area 32. In the example shown in FIG. 12, area G2c displays reduced drawing C1 obtained by reducing drawing C1 and reduced drawing A1 obtained by reducing drawing A1.

[0077] The drawing tab T1 is a tab for displaying the drawing details screen G2 in the display area 10c. The quotation tab T2 is a tab for displaying the quotation screen G3 in the display area 10c. The case confirmation button P5a is a button for displaying the linking confirmation screen G7 in the display area 10c.

[0078] In this embodiment, when the quotation tab T2 is selected on the drawing details screen G2, an quotation screen G3 is displayed in the display area 10c for displaying in detail an estimate linked to one system (system ID stored in the ID memory area 32) displayed in the area G2b of the drawing details screen G2.

[0079] FIG. 13 is an example of the quotation screen G3.

[0080] The estimate screen G3 is a screen for displaying in detail one estimate registered in the estimate TB. More specifically, the estimate screen G3 is a screen for displaying in detail an estimate linked to a system ID stored in the ID storage area 32.

[0081] The quotation screen G3 includes a system button P1, a case button P2, a first drawing registration button P3a, an area G3a, an area G3b, an area G3c, a drawing tab T1, a quotation tab T2, and a first quotation registration button P4a.

[0082] Area G3a is an area for displaying one quotation in detail. More specifically, area G3a is an area for displaying one quotation in detail out of one or more quotations linked to a system ID (system) stored in id storage area 32. In the example shown in FIG. 13, quotation E2 is displayed in area G3a.

[0083] The area G3b is an area for displaying a reduced estimate obtained by reducing one or more estimates registered in the estimate TB. More specifically, the area G3b is an area for displaying a reduced estimate obtained by reducing one or more estimates linked to a system ID (system) stored in the ID storage area 32. In the example shown in FIG. 13, the area G3b displays a reduced estimate E2 obtained by reducing the estimate E2, a reduced estimate D2 obtained by reducing the estimate D2, a reduced estimate C2 obtained by reducing the estimate C2, and a reduced estimate A2 obtained by reducing the estimate A2.

[0084] The area G3c is an area for displaying one system to which the estimate corresponding to the estimate displayed in the area G3a or the reduced estimate displayed in the area G3b is linked. In the example shown in Fig. 13, system 001 is displayed in the area G3c.

[0085] In this embodiment, when the drawing tab T1 is selected on the quotation screen G3, a drawing detail screen G2 is displayed in the display area 10c to display in detail a drawing linked to one system (system ID stored in the ID memory area 32) displayed in the area G3c of the quotation screen G3.

[0086] The first estimate registration button P4a is for registering the estimate in the estimate TB.

[0087] In this embodiment, when the first quotation registration button P4a is selected, the third registration screen G12 (Figure 42) is displayed in the display area 10c, and the quotation is registered in the quotation TB via this third registration screen G12.

[0088] FIG. 14 is an example of the case screen G4.

[0089] The case screen G4 is a screen for displaying cases registered in the case TB. The case screen G4 includes a system button P1, a case button P2, a first drawing registration button P3a, and a case indicator J.

[0090] FIG. 15 is an example of a case indicator J.

[0091] The case marker J is a marker for indicating a drawing and a system associated with one case registered in the system TB. In the example shown in Fig. 15, the case screen G4 includes five case markers J1 to J5.

[0092] Case marker J1 includes case A, reduced drawing A1, and system 001. Case marker J2 includes case B, reduced drawing B1, and system 002. Case marker J3 includes case C, reduced drawing C1, and system 001. Case marker J4 includes case D, reduced drawing A1, and system 001. Case marker J5 includes case E, reduced drawing A1, reduced drawing B1, system 001, and system 002.

[0093] In this embodiment, when one case marker J is selected on the case screen G4, the case ID corresponding to the selected case marker J is stored in the ID memory area 32, and the case details screen G5 corresponding to this case ID is displayed in the display area 10c.

[0094] FIG. 16 is an example of the case details screen G5.

[0095] The case details screen G5 is a screen for displaying in detail one case registered in the case TB. More specifically, the case details screen G5 is a screen corresponding to one case indicator J (case ID stored in the ID storage area 32) selected on the case screen G4.

[0096] The case details screen G5 includes a system button P1, a case button P2, a first drawing registration button P3a, an area G5a, a case tab T3, and a case document tab T4.

[0097] The area G5a is an area for displaying a case, a system, and a reduced drawing. More specifically, the area G5a is an area for displaying a case corresponding to a case ID stored in the ID storage area 32 (a case corresponding to one case indicator J selected on the case screen G4), one or more systems associated with the case, and reduced drawings obtained by reducing one or more drawings associated with the case.

[0098] The case tab T3 is a tab for displaying a case details screen G5 in the display area 10c. The case materials tab T4 is a tab for displaying a case materials screen G6 in the display area 10c.

[0099] In this embodiment, when the case materials tab T4 is selected on the case details screen G5, a case materials screen G6 for displaying materials (e.g., drawings and quotations; hereinafter referred to as "case materials") linked to a single case that were displayed in area G5a of the case details screen G5 is displayed in display area 10c.

[0100] FIG. 17 is an example of the case materials screen G6.

[0101] The case document screen G6 is a screen for displaying case documents associated with one case registered in the case TB. More specifically, the case document screen G6 is a screen for displaying case documents associated with a case ID stored in the ID storage area 32.

[0102] The project document screen G6 includes a system button P1, a project button P2, a first drawing registration button P3a, a project tab T3, a project document tab T4, an area G6a, an area G6b, an area G6c, a second drawing registration button P3b (see FIG. 18), and a second quotation registration button P4b (see FIG. 18).

[0103] The area G6a is an area for displaying one drawing in detail. More specifically, the area G6a is an area for displaying one drawing in detail among one or more drawings linked to a case ID (case) stored in the id storage area 32. In the example shown in FIG. 17, the area G6a displays a drawing A1 linked to a case A.

[0104] FIG. 18 is an enlarged view of areas G6b and G6c in FIG.

[0105] Area G6b is an area for displaying reduced drawings obtained by reducing one or more drawings linked to one case registered in case TB. More specifically, area G6b is an area for displaying reduced drawings obtained by reducing one or more drawings linked to a case ID (case) stored in id storage area 32. In the example shown in FIG. 18, reduced drawing A1 obtained by reducing drawing A1 linked to case A is displayed in area G6b.

[0106] In the region G6b, a second drawing registration button P3b is arranged. The second drawing registration button P3b is a button for registering a drawing in the drawing TB.

[0107] In this embodiment, when the second drawing registration button P3b is selected, a second registration screen G11 (Figure 38) is displayed in the display area 10c, and the drawing is registered in the drawing TB via the second registration screen G11.

[0108] In this embodiment, a first drawing registration button P3a and a second drawing registration button P3b are provided as buttons for registering a drawing in the drawing TB. The first drawing registration button P3a is configured to link a drawing to be registered in the drawing TB via the first registration screen G10 with one case registered in the case TB in response to a user's selection. On the other hand, the second drawing registration button P3b is configured to always link a drawing to be registered in the drawing TB via the second registration screen G11 with one case registered in the case TB.

[0109] The area G6c is an area for displaying a reduced estimate obtained by reducing one or more quotations linked to one project registered in the project TB. More specifically, the area G6c is an area for displaying a reduced estimate obtained by reducing one or more quotations linked to a project ID (project) stored in the ID storage area 32. In the example shown in FIG. 18, a reduced estimate A2 is displayed in the area G6c.

[0110] In the region G6c, a second estimate registration button P4b is disposed. The second estimate registration button P4b is a button for registering the estimate in the estimate TB.

[0111] In this embodiment, when the second quotation registration button P4b is selected, a fourth registration screen (not shown) is displayed in the display area 10c, and the quotation is registered in the quotation TB via this fourth registration screen.

[0112] In this embodiment, a first quotation registration button P4a and a second quotation registration button P4b are provided as buttons for registering an estimate in the estimate TB. The first quotation registration button P4a is configured to link an estimate to be registered in the estimate TB via the third registration screen G12 with one system registered in the system TB (a system corresponding to the system ID stored in the ID storage area 32). On the other hand, the second quotation registration button P4b is configured to link an estimate to be registered in the estimate TB via the fourth registration screen with one case registered in the case TB (a case corresponding to the case ID stored in the ID storage area 32).

[0113] FIG. 19 is an example of the association confirmation screen G7.

[0114] The link confirmation screen G7 is a screen for confirming a case linked to one drawing registered in the drawing TB. More specifically, the link confirmation screen G7 is a screen for confirming a case linked to a drawing ID stored in the ID storage area 32.

[0115] The linking confirmation screen G7 includes a case indicator J, a case linking button P5b, and a close button P6a.

[0116] The case linking button P5b is a button for displaying the linking screen G8 in the display area 10c. The close button P6a is a button for hiding the linking confirmation screen G7 and displaying the drawing details screen G2.

[0117] 19, the linking confirmation screen G7 includes a case indicator J1 including case A, reduced drawing A1, and system 001, a case indicator J4 including case D and reduced drawing A1, and a case indicator J5 including case E, reduced drawing A1, reduced drawing B1, system 001, and system 002. The linking confirmation screen G7 shown in FIG. 19 indicates that the cases linked to drawing A1 are case A, case D, and case E.

[0118] FIG. 20 is an example of the association screen G8.

[0119] The linking screen G8 is a screen for linking a drawing with a case. The linking screen G8 includes a case indicator J, a new case linking button P5c, an existing case linking button P5d, and a close button P6b.

[0120] The new case linking button P5c is a button for generating a new case that is not registered in the case TB, and linking this newly generated case with one drawing registered in the drawing TB (a drawing corresponding to the drawing ID stored in the ID memory area 32).

[0121] In this embodiment, by selecting the new case linking button P5c without selecting any of the case indicators J displayed on the linking screen G8, a new case is generated and the generated case is linked to one drawing registered in the drawing TB (the drawing corresponding to the drawing ID stored in the ID memory area 32).

[0122] The existing case linking button P5d is a button for linking one case (one existing case) registered in the case TB with one drawing registered in the drawing TB (a drawing corresponding to the drawing ID stored in the ID memory area 32).

[0123] In this embodiment, by selecting one of the case indicators J displayed on the linking screen G8 and then selecting the existing case linking button P5d, the case corresponding to the selected case indicator J is linked to one drawing registered in the drawing TB (the drawing corresponding to the drawing ID stored in the ID memory area 32).

[0124] FIG. 21 is an enlarged view of a portion (item sign J) of FIG.

[0125] In the example shown in Figure 21, case marker J includes case markers J1 to J5. Case marker J1 includes case A, reduced drawing A1, and system 001. Case marker J2 includes case B, reduced drawing B1, and system 002. Case marker J3 includes case C, reduced drawing C1, and system 001. Case marker J4 includes case D, reduced drawing A1, and system 001. Case marker J5 includes case E, reduced drawing A1, reduced drawing B1, system 001, and system 002.

[0126] Fig. 22 is an explanatory diagram for explaining screen transitions. The screen transitions will be explained below with reference to Fig. 22 and other figures.

[0127] Regarding the transition from the system screen G1 to other screens (see FIG. 10), selecting the case button P2 transitions to the case screen G4 (a), and selecting the system indicator H transitions to the drawing details screen G2 (b).

[0128] Regarding the transition from the drawing details screen G2 to other screens (see Figure 12), selecting the case button P2 transitions to the case screen G4 (a), selecting the system button P1 transitions to the system screen G1 (c), selecting the quotation tab T2 transitions to the quotation screen G3 (e), and selecting the case confirmation button P5a transitions to the linking confirmation screen G7 (f).

[0129] Regarding the transition from the quotation screen G3 to other screens (see Figure 13), selecting the case button P2 transitions to the case screen G4 (a), selecting the system button P1 transitions to the system screen G1 (c), and selecting the drawing tab T1 transitions to the drawing details screen G2 (e).

[0130] Regarding the transition from the case screen G4 to other screens (see FIG. 14), selecting the system button P1 transitions to the system screen G1 (C), and selecting the case indicator J transitions to the case details screen G5 (D).

[0131] Regarding the transition from the case details screen G5 to other screens (see Figure 16), selecting the case button P2 transitions to the case screen G4 (a), selecting the system button P1 transitions to the system screen G1 (c), and selecting the case document tab T4 transitions to the case document screen G6 (g).

[0132] Regarding the transition from the case document screen G6 to other screens (see Figure 17), selecting the case button P2 transitions to the case screen G4 (a), selecting the system button P1 transitions to the system screen G1 (c), and selecting the case tab T3 transitions to the case details screen G5 (g).

[0133] Regarding the transition from the linking confirmation screen G7 to other screens (see FIG. 19), selecting the case linking button P5b transitions to the linking screen G8 (K), and selecting the close button P6a transitions to the drawing details screen G2 (IX).

[0134] Regarding the transition from the association screen G8 to another screen (see FIG. 20), the selection operation of the close button P6b transitions to the drawing details screen G2 (K).

[0135] Next, a process for generating the system screen G1 will be described.

[0136] The control unit 40 executes a process of generating a system screen G1 based on receiving a request to view the systems registered in the DB 31 (systems TB) from the user terminal 10 (for example, information corresponding to a selection operation of the system button P1), and provides the generated system screen G1 to the user terminal 10. The user terminal 10 displays the system screen G1 provided from the server 20 in the display area 10c.

[0137] In this embodiment, a request to view the systems registered in DB31 (system TB) is a request to the server 20 to display the system screen G1 in the display area 10c. Note that in this embodiment, when the user terminal 10 logs in to the server 20, the system screen G1 is displayed in the display area 10c immediately thereafter. Therefore, a request to view the systems registered in DB31 (system TB) includes a request to log in to the server 20.

[0138] FIG. 23 is a flowchart showing the system screen generation process.

[0139] As shown in FIG. 23, the generation unit 44 first refers to the system TB to identify the systems registered in the system TB (S11), then executes a system label generation process to generate one system label H for each system identified in S11 (S20), and then generates a system screen G1 including the system labels H generated in S20 (S12), and terminates the system screen generation process.

[0140] FIG. 24 is a flowchart showing the lineage label generation process (S20).

[0141] (S21 to S23) The generation unit 44 first extracts one of the systems identified in S11 for which a system indicator H has not been generated (S21), then refers to the drawing TB to identify a drawing linked to the one system extracted in S21 (S22), and then determines whether or not there is one drawing identified in S22 (S23).

[0142] (S24) If the answer is YES in S23, the generation unit 44 transfers the process to S24, generates one system indicator H including one system extracted in S21 and a reduced drawing obtained by reducing one drawing identified in S22, and transfers the process to S27.

[0143] (S25, S26) If NO in S23, the generation unit 44 shifts the process to S25, identifies one latest drawing from the multiple drawings identified in S22 (S25), then generates one system indicator H including one system extracted in S21 and a reduced drawing obtained by reducing the one latest drawing identified in S25 (S26), and shifts the process to S27. The latest drawing refers to the drawing with the latest date and time registered in the drawing TB among the multiple drawings linked to one system.

[0144] (S27) The generation unit 44 determines whether or not the generation of the lineage indicators H for the lines identified in S11 has been completed, and if NO in S27, proceeds to before S21, and if YES in S27, ends the lineage indicator generation process.

[0145] For example, the system screen G1 shown in FIG. 10 and FIG. 11 is a screen when system 001 and system 002 are specified in S21, and this screen includes a system indicator H1 corresponding to system 001 and a system indicator H2 corresponding to system 002.

[0146] Next, a process for generating the drawing detail screen G2 will be described.

[0147] The control unit 40 executes a process of generating a drawing detail screen G2 based on a request to view a drawing registered in the DB 31 (drawing TB) (information corresponding to the selection operation of the system indicator H or information corresponding to the selection operation of the drawing tab T1) from the user terminal 10. In explaining this process, first, a process performed in the system 1 in response to the selection operation of the system indicator H will be explained.

[0148] In this embodiment, a request to view a drawing registered in the DB 31 (system TB) is a request to the server 20 to display the drawing details screen G2 in the display area 10c.

[0149] FIG. 25 is a flowchart showing a part of the processing in the system 1.

[0150] 25, the user terminal 10 transmits information on the system ID corresponding to the selected system ID H to the server 20 by selecting the system ID H (S30), and the server 20 receives the system ID information (S31), first, referring to the system TB, identifies the system corresponding to the system ID information received in S31 (S32), then stores the system ID identified in S32 in the ID storage area 32 (S33), then executes a plan detail screen generation process to generate a plan detail screen G2 based on the system ID stored in the ID storage area 32 (S40), and provides the plan detail screen G2 generated in S40 to the user terminal 10 (S34). The user terminal 10 displays the plan detail screen G2 provided from the server 20 in the display area 10c (S35).

[0151] FIG. 26 is a flowchart showing the drawing detail screen generating process (S40).

[0152] (S41 to S45) The generation unit 44 first refers to the system TB to identify a system corresponding to the system id stored in the id memory area 32 (S41), then refers to the drawing TB to identify a drawing linked to the system identified in S41 (S42), then identifies the latest drawing among the drawings identified in S42 (S43), then stores the drawing id corresponding to the latest drawing identified in S43 in the id memory area 32 (S44), then generates a drawing detail screen G2 including the system identified in S41, a reduced drawing obtained by reducing the drawing identified in S42, and the latest drawing identified in S43 (S45), and terminates the process of generating the drawing detail screen G2.

[0153] For example, as shown in the drawing details screen G2 of FIG. 12, area G2b displays the system identified in S41, area G2c displays a reduced drawing of the drawing identified in S42, and area G2a displays the latest drawing identified in S43.

[0154] Next, the process for generating the quotation screen G3 will be described.

[0155] The control unit 40 executes a process to generate a quotation screen G3 based on receiving a request to view a quotation registered in DB31 (quotation TB) (information corresponding to the operation of selecting the quotation tab T2) from the user terminal 10, and provides the generated quotation screen G3 to the user terminal 10.

[0156] In this embodiment, a request to view a quotation registered in the DB 31 (quote TB) is a request to the server 20 to display the quotation screen G3 in the display area 10c.

[0157] FIG. 27 is a flowchart showing the estimate screen generation process.

[0158] (S51 to S54) The generation unit 44 first refers to the system TB to identify the system linked to the estimate corresponding to the estimate viewing request registered in DB31, i.e., the system ID (system) stored in the ID memory area 32 (S51), then refers to the estimate TB to identify an estimate linked to the system identified in S51 (S52), then extracts the latest estimate from the estimates identified in S52 (S53), then generates an estimate screen G3 including a reduced estimate obtained by reducing the estimate identified in S52 and the latest estimate identified in S53 (S54), and terminates the process of generating the estimate screen G3.

[0159] For example, as shown on the quotation screen G3 in FIG. 13, a reduced quotation that is a reduced version of the quotation identified in S52 is displayed in area G3b, the latest quotation identified in S53 is displayed in area G3a, and the system corresponding to the system ID stored in the ID storage area 32 is displayed in area G3c.

[0160] Next, the process for generating the case screen G4 will be described.

[0161] The control unit 40 executes a process to generate a case screen G4 based on receiving a request to view a case registered in DB 31 (case TB) (information corresponding to an operation of selecting the case button P2) from the user terminal 10, and provides the generated case screen G4 to the user terminal 10. The user terminal 10 displays the case screen G4 provided from the server 20 in the display area 10c.

[0162] In this embodiment, a request to view a case registered in the DB 31 (case TB) is a request to the server 20 to display the case screen G4 in the display area 10c.

[0163] FIG. 28 is a flowchart showing the case screen generating process.

[0164] (S60, S71, S72) The generation unit 44 executes a process for generating a case indicator J (first case indicator generation process) (S60), then generates a case screen G4 including the case indicator J generated in S60 (S71), clears the ID stored in the ID memory area 31 (S72), and terminates the process for generating the case screen G4.

[0165] FIG. 29 is a flowchart showing the first case indicator generating process (S60).

[0166] (S61 to S65) The generation unit 44 first refers to the case TB to identify cases registered in the case TB (S61), then extracts one of the cases identified in S61 for which a case indicator J has not been generated (S62), then refers to the second intermediate TB and the drawing TB to identify a drawing linked to the one case extracted in S62 (S63), then refers to the first intermediate TB and the system TB to identify a system linked to the one case extracted in S62 (S64), then generates one case indicator J including the case extracted in S62, a reduced drawing obtained by reducing the drawing identified in S63, and the system identified in S64, and moves to the next step S66.

[0167] (S66) The generation unit 44 determines whether the generation of the case indicator J for each of the cases identified in S61 has been completed, and if NO in S66, proceeds to before S62, and if YES in S66, ends the first case indicator generation process.

[0168] For example, the case screen G4 shown in Figures 14 and 15 is the screen displayed when case A, case B, case C, case D, and case E are identified in S61, and this screen includes a case indicator J1 corresponding to case A, a case indicator J2 corresponding to case B, a case indicator J3 corresponding to case C, a case indicator J4 corresponding to case D, and a case indicator J5 corresponding to case E.

[0169] Next, the process for generating the case details screen G5 will be described.

[0170] The control unit 40 executes a process of generating a case details screen G5 based on receiving a request to view one case registered in the DB 31 (case TB) (information corresponding to an operation of selecting the case indicator J on the case screen G4) from the user terminal 10. In explaining this process, first, a process performed in the system 1 in response to the operation of selecting the case indicator J will be explained.

[0171] FIG. 30 is a flowchart showing a part of the processing in the system 1.

[0172] 30, when a case indicator J on a case screen G4 is selected, the user terminal 10 transmits information on the case ID corresponding to the selected case indicator J to the server 20 (S81), and when the server 20 receives the case ID information transmitted in S81 (S82), it first stores the case ID received in S82 in the ID storage area 32 (S83), then refers to the case TB to identify the case corresponding to the case ID stored in S83 (S84), and then executes a process of generating a case details screen G5 based on the case identified in S84 (S90). The user terminal 10 displays the case details screen G5 provided by the server 20 in the display area 10c (S85).

[0173] FIG. 31 is a flowchart showing the case detail screen generation process (S90).

[0174] (S91 to S93) The generation unit 44 first refers to the second intermediate TB and the drawing TB to identify a drawing linked to the case identified in S84 (S91), then refers to the first intermediate TB and the system TB to identify a system linked to the case identified in S84 (S92), and then generates a case details screen G5 including one case identified in S84, a reduced drawing obtained by reducing the drawing identified in S91, and the system identified in S92, and terminates the case details screen generation process.

[0175] For example, as shown in the case details screen G5 of Figure 16, area G5a displays case A identified in S84, reduced drawing A1 which is a reduced version of drawing A identified in S91, and system 001 identified in S92.

[0176] Next, the process of generating the case document screen G6 will be described.

[0177] The control unit 40 executes a process to generate a project document screen G6 based on receiving from the user terminal 10 a viewing request (information corresponding to a selection operation of the project document tab T4) to view project documents (drawings and estimates) related to one project registered in the DB 31 (project TB), and provides the generated project document screen G6 to the user terminal 10. The user terminal 10 displays the project document screen G6 provided from the server 20 in the display area 10c.

[0178] FIG. 32 is a flowchart showing the case document screen generation process.

[0179] (S101 to S104) The generation unit 44 refers to the case TB to identify one case corresponding to the viewing request to view the case materials, i.e., the case corresponding to the case ID stored in the ID memory area 32 (S101), then refers to the second interim TB and the drawing TB to identify a drawing linked to the case identified in S101 (S102), then refers to the third interim TB and the quotation TB to identify the quotation linked to the case identified in S101 (S103), then generates a case materials screen G6 including the drawing identified in S102, a reduced drawing obtained by reducing the drawing identified in S102, and a reduced estimate obtained by reducing the estimate identified in S103, and terminates the case materials screen generation process.

[0180] For example, as shown in the project document screen G6 in Figures 17 and 18, reduced drawing A1 obtained by reducing drawing A1 identified in S102 is displayed in area G6b, reduced estimate A2 obtained by reducing estimate A2 identified in S103 is displayed in area G6c, and drawing A1 identified in S102 is displayed in area G6a.

[0181] Next, a process for generating the association confirmation screen G7 will be described.

[0182] The control unit 40 executes a process of generating an association confirmation screen G7 based on receipt from the user terminal 10 of a request (information corresponding to the selection operation of the case confirmation button P5a) ​​to confirm a case linked to the drawing displayed in the area G2a of the drawing details screen G2 (the drawing corresponding to the drawing ID stored in the ID storage area 32), and provides the generated association confirmation screen G7 to the user terminal 10. The user terminal 10 displays the association confirmation screen G7 provided from the server 20 in the display area 10c.

[0183] FIG. 33 is a flowchart showing the association confirmation screen generating process.

[0184] (S111 to S113, S120) The generation unit 44 first refers to the drawing TB to identify the drawing displayed in area G2a of the drawing details screen G2 (the drawing corresponding to the drawing ID stored in the ID memory area 32) (S111), then refers to the case TB to identify the case linked to the drawing identified in S111 (S112), then executes a process to generate a case indicator J corresponding to the case identified in S112 (second case indicator generation process) (S120), then generates a linking confirmation screen G7 including the case indicator J generated in S120 (S113), and terminates the process of generating the linking confirmation screen G7.

[0185] Although the second case indicator generation process (S120) is not illustrated, the generation unit 44 generates a case indicator J corresponding to each case identified in S112. Specifically, the generation unit 44 first extracts one case for which a case indicator J has not been generated from among the cases identified in S112 (S121), then refers to the second intermediate TB and the drawing TB to identify a drawing linked to the one case extracted in S121 (S122), then refers to the first intermediate TB and the system TB to identify a system linked to the one case extracted in S121 (S123), and then generates one case indicator J including the case extracted in S121, a reduced drawing obtained by reducing the drawing identified in S122, and the system identified in S123 (S124). Next, the generation unit 44 determines whether the generation of case indicators J for each of the cases identified in S111 has been completed (S125), and if NO at S125, the processing proceeds to before S121, and if YES at S125, the second case indicator generation processing is terminated.

[0186] For example, the linking confirmation screen G7 in Figure 19 is a screen generated when case A, case D, and case E are identified in S112, and this screen includes a case indicator J1 corresponding to case A, a case indicator J4 corresponding to case D, and a case indicator J5 corresponding to case E.

[0187] Next, the process of generating the association screen G8 will be described.

[0188] Based on receiving a request (information corresponding to the selection operation of the case linking button P5b) from the user terminal 10 to link a case to the drawing displayed in area G2a of the drawing details screen G2 (the drawing corresponding to the drawing ID stored in the ID memory area 32), the control unit 40 executes a process to generate a linking screen G8 and provides the generated linking screen G8 to the user terminal 10.

[0189] FIG. 34 is a flowchart showing the associated screen generating process.

[0190] (S60, S131) The generation unit 44 first executes a process for generating a case indicator J (first case indicator generation process) (S60), then generates a linking screen G8 including the case indicator J generated in S60 (S131), and terminates the process for generating the linking screen.

[0191] Next, a specific example 1 will be described.

[0192] 35 is an explanatory diagram for explaining specific example 1. Specific example 1 is an example showing a transition of a screen displayed in the display area 10c of the user terminal 10 in accordance with an update of each ID (system ID, drawing ID, case ID) stored in the ID storage area 32. In specific example 1, it is assumed that each TB shown in FIG. 8 and FIG. 9 is stored in DB31.

[0193] (Example 1: Generating a system screen) As shown in FIG. 35-1(a), the server 20 has received a login request from the user terminal 10. As a result, the server 20 has permitted the login of the user terminal 10. Upon permitting the login of the user terminal 10, the server 20 generates a system screen G1. At this time, in S11, the system TB in FIG. 8(a) is referenced to identify system 001 and system 002, and in S20, a system indicator H1 corresponding to system 001 and a system indicator H2 corresponding to system 002 are generated.

[0194] In generating the system indicator H1, in S22, the drawing TB in Fig. 8(b) is referenced to identify drawings A1 and C1 linked to system 001. In S25, of the drawings A1 and C1 identified in S22, drawing C1 is identified as the drawing with the most recent date and time of registration in the drawing TB. In S26, a system indicator H1 (Fig. 11(a)) is generated that includes system 001 and reduced drawing C1 obtained by reducing drawing C1.

[0195] In generating the system marker H2, in S22, the drawing TB in Figure 8(b) is referenced to identify the drawing B1 linked to the system 002, and in S24, the system marker H2 (Figure 11(b)) is generated which includes the system 001 and the reduced drawing B1 obtained by reducing the drawing B1.

[0196] As a result, the system screen G1 shown in Fig. 10 is displayed in the display area 10c (Fig. 35-1(b)). Note that, as shown in Fig. 35(b1), the system ID, drawing ID, and case ID are not stored in the ID storage area 32 by generating the system screen G1.

[0197] A system indicator H is generated for each system registered in the system TB, and the system screen G1 is configured to include the generated system indicator H. Therefore, the user can easily understand the systems of the drawings registered in the DB31 via the system screen G1.

[0198] The system indicator H includes a system (e.g., system 001) and a reduced drawing of a drawing (e.g., drawing C1) associated with the system. Therefore, the user can visually recognize the systems registered in the system TB.

[0199] The reduced drawing included in the system indicator H corresponds to the drawing registered in the system TB with the most recent date and time. This makes it easier for the user to understand the systems registered in the system TB.

[0200] In this embodiment, when the login of the user terminal 10 is permitted, the system screen G1 is displayed in the display area 10c immediately thereafter. Therefore, no troublesome operation is required to display the system screen G1.

[0201] (Example 1: Creating a drawing details screen) As shown in FIG. 35-1(b2), the system indicator H1 (FIG. 11(a)) is selected on the system screen G1 shown in FIG. 10. The server 20 generates a plan detail screen G2 corresponding to the system indicator H1 in response to the selection of the system indicator H1. At this time, in S33, the system id1 (system 001) corresponding to the system indicator H1 selected in S30 is stored. In S41, the system TB in FIG. 8(a) is referenced to identify the system 001 corresponding to the system id1 stored in the id storage area 32. In S42, the plan TB in FIG. 8(b) is referenced to identify the plans A1 and C1 linked to the system 001 identified in S41. In S43, the latest plan C1 is identified from among the plans A1 and C1 identified in S42. In S44, the plan id3 corresponding to the latest plan C1 identified in S43 is stored in the id storage area 32. In S45, a drawing detail screen G2 is generated, which includes the system 001 identified in S41, a reduced drawing A1 obtained by reducing the drawing A1 identified in S42, a reduced drawing C1 obtained by reducing the drawing C1 identified in S42, and the latest drawing C1 identified in S43.

[0202] As a result, the drawing details screen G2 shown in FIG. 12 was displayed (FIG. 35-1(c)). As shown in FIG. 12, reduced drawing C1 and reduced drawing A1 are arranged in area G2c. System 0001 is arranged in area G2b. The latest drawing C1 is arranged in area G2a. Note that, as shown in FIG. 35(c1), by generating the drawing details screen G2, system id1 corresponding to system 001 and drawing id3 corresponding to drawing C1 are stored in the id storage area 32.

[0203] The drawing detail screen G2 includes an area G2c, which displays reduced drawings of drawings associated with one system registered in the system TB. In other words, the area G2c is an area that displays a list of drawings associated with one system. This makes it easy to search for drawings.

[0204] The drawing detail screen G2 includes an area G2a, and the area G2a displays the latest drawing among drawings associated with one system registered in the system TB. Therefore, the drawing detail screen G2 of the present embodiment can display drawings that are likely to be desired by the user.

[0205] (Example 1: Creating a quote screen) As shown in FIG. 35-1(c2), the quotation tab T2 is selected on the drawing details screen G2 of FIG. 12. The server 20 generates a quotation screen G3 corresponding to the system 001 displayed in the area G2c of the drawing details screen G2, triggered by the selection of the quotation tab T2. At this time, in S51, the system TB in FIG. 8(a) is referenced to identify the system id1 (system 001) stored in the id storage area 32. In S52, the quotation TB in FIG. 8(d) is referenced to identify the quotations A2, C2, D2, and E2 linked to the system 001 identified in S51. In S53, the latest quotation E2 is identified from the quotations A2, C2, D2, and E2 identified in S52. In S54, an estimate screen G3 is generated, which includes a reduced estimate A2 obtained by reducing the estimate A2, a reduced estimate C2 obtained by reducing the estimate C2, a reduced estimate D2 obtained by reducing the estimate D2, a reduced estimate E2 obtained by reducing the estimate E2, and the latest estimate E1.

[0206] As a result, the quotation screen G3 shown in FIG. 13 is displayed in the display area 10c (FIG. 35-1(d)). As shown in FIG. 13, the reduced estimate E2, reduced estimate D2, reduced estimate C2, and reduced estimate A2 are arranged in the area G3b. The latest estimate E2 is arranged in the area G3a. Note that, as shown in FIG. 35-1(d1), the generation of the quotation screen G3 does not cause a new ID to be stored in the ID storage area 32, and the storage of the system ID1 and drawing ID3 is maintained (the ID storage area 32 is not updated).

[0207] The drawing details screen G2 not only includes a drawing linked to one system registered in the system TB, but also includes an estimate tab T2 for viewing an estimate linked to this system, and by selecting the estimate tab T2, an estimate screen G3 showing the estimate in detail is displayed. Therefore, while the user is viewing a drawing desired by the user on the drawing details screen G2, the user can check the details of the estimate related to the drawing being viewed by a single operation of selecting the estimate tab T2.

[0208] (Example 1: Creating a case screen) As shown in FIG. 35-1 (d2), the Item button P2 is selected on the quotation screen G3. In response to the selection of the Item button P2, the server 20 generates a Item screen G4. At this time, in S61, the Item TB in FIG. 8 (c) is referenced to identify Item A, Item B, Item C, Item D, and Item E registered in the Item TB. In S62, a Item indicator J1 corresponding to Item A, a Item indicator J2 corresponding to Item B, a Item indicator J3 corresponding to Item C, a Item indicator J4 corresponding to Item D, and a Item indicator J5 corresponding to Item E are generated.

[0209] In generating the case indicator J1, in S63, the second intermediate TB in Fig. 9(b) and the drawing TB in Fig. 8(b) are referenced to identify the drawing A1 linked to the case A, and in S64, the first intermediate TB in Fig. 9(a) and the line TB in Fig. 8(a) are referenced to identify the line 001 linked to the case A. In S65, the case indicator J1 is generated, which includes the case A identified in S62, the reduced drawing A1 obtained by reducing the drawing A1 identified in S63, and the line 001 identified in S64. Note that the generation of the case indicators J2 to J5 corresponding to the cases B to E is similar to that of the case indicator J1, and therefore the description thereof will be omitted.

[0210] As a result, the case screen G4 shown in Fig. 14 is displayed in the display area 10c (Fig. 35(e)). The case screen G4 shown in Fig. 14 has case indicators J1 to J5 shown in Fig. 15 arranged thereon. Note that, as shown in Fig. 35-1(e1), the generation of the case screen G4 (by the selection operation of the case button P2) clears each ID stored in the ID storage area 32.

[0211] A case indicator J is generated for each case registered in the case TB, and the case screen G4 includes the generated case indicator J. Therefore, the user can easily understand the cases registered in the case TB via the case screen G4.

[0212] The case indicator J includes a case (e.g., case A) and a reduced drawing of a drawing (e.g., drawing A1) associated with the case. This allows the user to visually recognize the contents of the case.

[0213] (Example 1: Creating a case details screen) As shown in FIG. 35-1(e2), the case indicator J1 (FIG. 15) corresponding to case A is selected on the case screen G4. The server 20 generates a case details screen G5 corresponding to the case indicator J1 in response to the selection of the case indicator J1. At this time, in S83, the case id1 (case A) corresponding to the case indicator J1 selected in S81 is stored in the id storage area 32. In S91, the second intermediate TB and the drawing TB are referenced to identify the drawing A1 linked to the case A identified in S84. In S92, the first intermediate TB and the system TB are referenced to identify the system 001 linked to the case A identified in S84. In S93, the case details screen G5 is generated, including the case A, the reduced drawing A1 obtained by reducing the drawing A1 identified in S91, and the system 001 identified in S92.

[0214] As a result, the case details screen G5 shown in Fig. 16 was displayed in the display area 10c (Fig. 35-1(f)). As shown in Fig. 16, the case A identified in S84, the system 001 identified in S92, and the reduced drawing A1 which is a reduced version of the drawing A1 identified in S91 are arranged in the area G5a of the case details screen G5. Note that, as shown in Fig. 35-1(f1), the case id1 corresponding to case A (case indicator J1) was stored in the id storage area 32 by generating the case details screen G5 (by the selection operation of the case indicator J1).

[0215] The case details screen G5 includes a lineage linked to one case registered in the case TB, so that the lineage of the drawings used in the request corresponding to the case can be confirmed.

[0216] The case details screen G5 includes reduced drawings that are linked to a case registered in the case TB, so that the user can check the drawings to be used in requests corresponding to the case.

[0217] In the present embodiment, the case indicator may not include a reduced drawing. That is, the generating unit may be configured to identify a case corresponding to the selected case indicator from among the cases registered in the case TB based on a user's operation of selecting the case indicator, identify a system linked to the identified case from the system TB by referring to the first intermediate TB and the system TB, and generate a case details screen including the identified case and a reduced drawing obtained by reducing the identified system.

[0218] (Example 1: Creating a case document screen) As shown in FIG. 35-1(f2), the project document tab T4 is selected on the project details screen G5. The server 20 generates a project document screen G6 corresponding to the project A displayed in the area G5a of the project details screen G5 in response to the selection of the project document tab T4. At this time, in S101, the project TB is referenced to identify the project A corresponding to the project id1 stored in the id storage area 32. In S102, the second interim TB in FIG. 9(b) and the drawing TB in FIG. 8(b) are referenced to identify the drawing A linked to the project A identified in S101. In S103, the third interim TB in FIG. 9(c) and the quotation TB in FIG. 8(d) are referenced to identify the quotation A2 linked to the project A identified in S101. In S104, a case materials screen G6 is generated, which includes the drawing A1 identified in S102, a reduced drawing A1 obtained by reducing this drawing A1, and a reduced estimate A2 obtained by reducing the estimate A2 identified in S103.

[0219] As a result, the project document screen G6 shown in FIG. 17 was displayed in the display area 10c (FIG. 35-1(g)). As shown in FIG. 17, the drawing A1 is arranged in the area G6a. As shown in FIG. 18, the reduced drawing A1 obtained by reducing the drawing A1 is arranged in the area G6b, and the reduced quotation A2 obtained by reducing the quotation A2 identified in S103 is arranged in the area G6c. Note that, as shown in FIG. 35-1(g1), the generation of the project document screen G6 does not result in a new ID being stored in the ID storage area 32, and the storage of the project ID1 is maintained.

[0220] The project document screen G6 includes areas G6b and G6c, where the area G6b displays a reduced drawing that is a drawing linked to one project registered in the project TB, and the area G6c displays a reduced quotation that is a quotation linked to the one project. Therefore, the user can grasp all the documents (drawings, quotation) linked to one project via the project document screen G6.

[0221] (Example 1: Creating a linking confirmation screen) As shown in FIG. 35-2(h2), the case confirmation button P5a is selected on the drawing details screen G2. At this time, as shown in FIG. 35-2(h1), the system id1 and the drawing id1 are stored in the id storage area 32. That is, when the case confirmation button P5a is selected, the drawing A1 corresponding to the drawing id1 is displayed in the area G2a of the drawing details screen G2. The server 20 generates the linking confirmation screen G7 corresponding to the drawing A1 displayed in the area G2a of the drawing details screen G2, triggered by the selection of the case confirmation button P5a. At this time, in S111, the drawing A1 corresponding to the drawing id1 stored in the id storage area 32 is identified by referring to the drawing TB. In S112, the second intermediate TB in FIG. 9(b) and the case TB in FIG. 8(c) are referred to, and the case A (case id1), case D (case id4), and case E (case id5) linked to the drawing A1 (drawing id1) identified in S111 are identified. In S120, a case document screen G6 is generated that includes a case indicator J1 corresponding to case A identified in S111, a case indicator J4 corresponding to case D identified in S111, and a case indicator J5 corresponding to case E identified in S111.

[0222] As a result, the association confirmation screen G7 shown in Fig. 19 is displayed in the display area 10c (Fig. 35-2(j)). As shown in Fig. 19, the association confirmation screen G7 includes a case indicator J1 corresponding to case A, a case indicator J4 corresponding to case D, and a case indicator J5 corresponding to case E.

[0223] By selecting the case confirmation button P5a on the drawing details screen G2, a case indicator J (linking confirmation screen G7) corresponding to the case linked to the drawing (drawing id1 stored in the id storage area 32) displayed in the area G2a of the drawing details screen G2 is displayed in the display area 10c. Therefore, the user can grasp all the cases linked to one drawing (the drawing displayed in the area G2a of the drawing details screen G2) via the linking confirmation screen G7.

[0224] (Example 1: Creating a pegging screen) As shown in FIG. 35-2(j2), the case indicator J1 corresponding to case A is selected on the linking confirmation screen G7. In response to the selection of the case indicator J1, the server 20 generates a linking screen G8. At this time, in S60, the case TB in FIG. 8(c) is referenced to identify case A, case B, case C, case D, and case E (S61), and case indicators J1 to J5 corresponding to these cases A to E are generated (S66). In S131, the linking screen G8 is generated including the case indicators J1 to J5 generated in S60.

[0225] As a result, the linking screen G8 shown in Fig. 20 was displayed in the display area 10c (Fig. 35-2(k)). As shown in Fig. 20, the linking screen G8 includes a case indicator J1 corresponding to case A, a case indicator J2 corresponding to case B, a case indicator J3 corresponding to case C, a case indicator J4 corresponding to case D, and a case indicator J5 corresponding to case E.

[0226] Although not shown, when a case indicator J is selected on the linking screen G8, the control unit 40 stores the case id corresponding to the selected case indicator J in the id storage area 32. For example, when a case indicator J1 is selected on the linking screen G8, the control unit 40 stores the case id1 corresponding to the case indicator J1 in the id storage area 32. Although details will be described later, when the case indicator J is selected on the linking screen G8 and then the link existing case button P5b is selected, the case id and drawing id stored in the id storage area 32 are linked.

[0227] Next, a process for registering various pieces of information (drawings, systems, cases, estimates) in the DB 31 and a process for linking the various pieces of information registered in the DB 31 will be described.

[0228] FIG. 36 is a schematic diagram showing the first registration screen G10.

[0229] The first registration screen G10 is a screen for registering a drawing in the drawing TB. The first registration screen G10 is displayed in the display area 10c by selecting the first drawing registration button P3a. The first drawing registration button P3a is arranged on the drawing details screen G2 and other screens.

[0230] As shown in FIG. 36, the first registration screen G10 includes a first area G10a, a first input field G10b, a request field G10c, and a first send button G10d.

[0231] The first area G10a is an area for specifying a drawing to be registered in the drawing TB. The user specifies a drawing to be registered in the drawing TB by dragging and dropping the drawing to be registered in the drawing TB into the first area G10a. The first input field G10b is a field for inputting the lineage of the drawing specified in the first area G10a. The request field G10c is a field for selecting whether or not to request the server 20 to treat the manufacturing request of the product to be manufactured according to the drawing specified in the first area G10a as an item (hereinafter referred to as "itemization"). The first send button G10d is a button for transmitting to the server 20 the drawing specified in the first area G10a, the lineage input in the first input field G10b, and information on whether or not to request itemization selected in the request field G10c (hereinafter referred to as "itemization information").

[0232] FIG. 37 is a flowchart showing the process executed in the system 1 in response to the selection operation of the first send button G10d.

[0233] As shown in FIG. 37, when the server 20 receives from the user terminal 10 the drawing specified in the first area G10a, the system entered in the first input field G10b, and the case information (S201), that is, when it receives a drawing registration request via the first registration screen G10, it first executes a first drawing etc. registration process (S210), then executes a first drawing etc. linking process (S220), then stores the drawing ID corresponding to the drawing received in S201 in the ID memory area 32 (S202), then executes a process to generate a drawing details screen G2 based on the various information registered in DB31 and the drawing ID stored in the ID memory area 32 (S40), and provides the drawing details screen G2 generated in S40 to the user terminal 10 (S203).

[0234] FIG. 38 is a schematic diagram showing the second registration screen G11.

[0235] The second registration screen G11 is a screen for registering drawings in the drawing TB. The second registration screen G11 is displayed in the display area 10c by selecting the second drawing registration button P3b. The second drawing registration button P3b is only arranged on the project document screen G6.

[0236] As shown in FIG. 38, the second registration screen G11 includes a second area G11a and a second send button G11b.

[0237] The second area G11a is an area for specifying a drawing to be registered in the drawing TB. The user specifies the drawing to be registered in the drawing TB by dragging and dropping the drawing to be registered in the drawing TB into the second area G11a. The second send button G11b is for sending the drawing specified in the second area G11a to the server 20.

[0238] FIG. 39 is a flowchart showing the process executed in the system 1 in response to the selection operation of the second send button G11b.

[0239] As shown in FIG. 39, when the server 20 receives a drawing specified in the second area G11a from the user terminal 10 (S231), that is, when it receives a drawing registration request via the second registration screen G11, it first executes a second drawing etc. registration process (S240), then executes a second drawing etc. linking process (S250), then generates a case document screen G6 based on the various information registered in DB31 and the case ID stored in the ID memory area 32 (S100), and then provides the case document screen G6 generated in S100 to the user terminal 10 (S232).

[0240] FIG. 40(a) is a flow chart showing the first drawing etc. registration process (S210) of FIG.

[0241] (S211 to S213) The registration unit 42 refers to the system TB and determines whether or not the same system as the system accepted in S201 of Fig. 37 is registered in the system TB (S211), and if the same system as this system is registered in the system TB (YES in S211), the process proceeds to S213, where the system accepted in S201 is identified from the system TB in S213, and the system id corresponding to this identified system is stored in the id storage area 32 (S213), and the process proceeds to S214. On the other hand, if NO in S211, the registration unit 42 proceeds to S212, where the system accepted in S201 is registered in the system TB, and a system id is assigned to this registered system, and this assigned system id is stored in the id storage area 32 (S212), and the process proceeds to S214.

[0242] (S214) The registration unit 42 registers the drawing received in S201 of FIG. 37 in the drawing TB, assigns a drawing ID to this drawing, and moves the process to S215.

[0243] (S215, S216) The registration unit 42 determines whether or not information requesting case creation has been received in S201 of Fig. 37, and if information requesting case creation has not been received (NO in S215), ends the first process of registering drawings, etc. On the other hand, if information requesting case creation has been received in S201 of Fig. 37 (YES in S215), the registration unit 42 creates a new case, registers this created case in the case TB, assigns a case ID to this case (S216), and ends the first process of registering drawings, etc.

[0244] FIG. 40(b) is a flow chart showing the second registration process (S240) of drawings, etc. in FIG.

[0245] (S241, S242) The registration unit 42 first registers the drawing accepted in S231 of Figure 39 in the drawing TB and assigns a drawing ID to this drawing (S241), then identifies the case corresponding to the case ID stored in the ID memory area 32 (S242), and terminates the second drawing etc. registration process.

[0246] FIG. 41(a) is a flowchart showing the first drawing etc. linking process (S220) of FIG.

[0247] (S221) The linking unit 43 executes a linking process between the system and the drawing. Specifically, if the system received in S201 is registered in the system TB (YES in S221), the system identified in S213 is linked to the drawing registered in the drawing TB in S214. On the other hand, if the system received in S201 is not registered in the system TB (NO in S211), the system registered in the system TB in S212 is linked to the drawing registered in the drawing TB in S214.

[0248] (S222) The linking unit 43 determines in S216 whether the registration unit 42 has registered the case in the case TB, and if the case has been registered (YES in S222), proceeds to S223, and if the case has not been registered (NO in S222), terminates the first drawing etc. linking process.

[0249] (S223) The linking unit 43 executes a linking process between a system and a case. Specifically, when a system is specified in S213 (YES in S211), first, a first intermediate ID is generated, and then, by associating the generated first intermediate ID, the system specified in S213, and the case registered in the case TB in S216, the system specified in S213 is linked to the case registered in the case TB in S216. On the other hand, when a system is registered in S212 (NO in S211), first, a first intermediate ID is generated, and then, by associating the generated first intermediate ID, the system registered in the system TB in S212, and the case registered in the case TB in S216, the system registered in the system TB in S212 is linked to the case registered in the case TB in S216.

[0250] (S224) The linking unit 43 executes a linking process between the drawing and the case. Specifically, first, a second intermediate ID is generated, and then, by associating the generated second intermediate ID with the drawing registered in the drawing TB in S214 and the case registered in the case TB in S216, the drawing registered in the drawing TB in S214 and the case registered in the case TB in S216 are linked, and the first linking process of the drawing, etc. is terminated.

[0251] FIG. 41(b) is a flowchart showing the second drawing etc. linking process (S250) of FIG.

[0252] (S251) The linking unit 43 executes a linking process between the drawing and the case. Specifically, first, a second intermediate ID is generated, and then, by associating the generated second intermediate ID with the drawing registered in the drawing TB in S241 and the case identified in S242, the drawing registered in the drawing TB in S241 and the case identified in S242 are linked, and the second drawing etc. linking process is terminated.

[0253] FIG. 42 is a schematic diagram showing the third registration screen G12.

[0254] The third registration screen G12 is a screen for registering a quotation in the quotation TB. The third registration screen G12 is displayed in the display area 10c by selecting the first quotation registration button P4a. The first quotation registration button P4a is only arranged on the quotation screen G3.

[0255] As shown in Fig. 42, the third registration screen G12 includes a third area G12a and a third send button G12b. The third area G12a is an area for specifying a quote to be registered in the quote TB. The user specifies a quote to be registered in the quote TB by dragging and dropping the quote to be registered in the quote TB into the third area G12a. The third send button G12b is a button for sending the quote specified in the third area G12a to the server 20.

[0256] FIG. 43 is a flowchart showing the process executed in the system 1 in response to the selection operation of the third send button G12b.

[0257] As shown in FIG. 43, the user terminal 10 transmits the quotation specified in the third area G12a to the server 20 by selecting the third send button G12b (S261), i.e., makes a quotation registration request via the third registration screen G12. When the server 20 accepts the quotation sent in S261 (S262), it executes a first quotation registration linking process to register the quotation accepted in S262 in the quotation TB (S270), and then executes a process to generate a quotation screen G3 based on the various information registered in DB31 and the system ID stored in the ID memory area 32 (S50 in FIG. 27), and then provides the quotation screen G3 generated in S50 to the user terminal 10 (S263).

[0258] The fourth registration screen is a screen for registering a quotation in the quotation TB. The fourth registration screen is displayed in the display area 10c by selecting the second quotation registration button P4b. The second quotation registration button P4b is only located on the project document screen G6. The design of the fourth registration screen is the same as that of the third registration screen, and therefore is not shown in the drawings.

[0259] The fourth registration screen includes a fourth area and a fourth send button. The fourth area is an area for specifying the estimate to be registered in the estimate TB. The user specifies the estimate to be registered in the estimate TB by dragging and dropping the estimate to be registered in the estimate TB into the fourth area. The fourth send button is for sending the estimate specified in the fourth area to the server 20.

[0260] FIG. 44 is a flowchart showing the process executed in the system 1 in response to the selection operation of the fourth send button.

[0261] As shown in FIG. 44, the user terminal 10 sends the quotation specified in the fourth area to the server 20 by selecting the fourth send button (S281), i.e., makes a quotation registration request via the fourth registration screen. When the server 20 accepts the quotation sent in S281 (S282), it first executes a second quotation registration linking process (S290) to register the quotation accepted in S282 in the quotation TB, etc., and then generates a case document screen G6 based on the various information registered in DB31 and the case ID stored in the ID memory area 32 (S100 in FIG. 32), and then provides the case document screen G6 generated in S100 to the user terminal 10 (S283).

[0262] FIG. 45(a) is a flowchart showing the first quotation registration linking process (S270).

[0263] (S271) The registration unit 42 first registers the quotation received in S262 of FIG. 43 in the quotation TB, and assigns a quotation ID to the registered quotation, and then proceeds to S272.

[0264] (S272, S273) The linking unit 43 identifies the system corresponding to the system ID stored in the ID memory area 32 (S272), links the estimate registered in the estimate TB in S271 with the system identified in S272 (S273), and terminates the first estimate registration linking process.

[0265] Although a specific example of the process of FIG. 45(a) is omitted, when the server 20 (control unit 40) receives a registration request from the user terminal 10 to register the quotation A2 (related materials) related to the drawing A1 registered in the DB31 (storage unit 30) in the DB31 (S262 in FIG. 43), the server 20 (control unit 40) refers to the system TB stored in the DB31, identifies the system 001 linked to the drawing A1 related to the quotation A2 corresponding to the registration request (i.e., identifies the system 001 corresponding to the system id1 stored in the id storage area 32) (S272), and links the identified system 001 to the quotation A2 corresponding to the registration request received in S262 on a one-to-one or one-to-multiple basis (S273). At this time, the linking unit 43 does not link the quotation A2 corresponding to the registration request received in S262 to the drawing A1 related to the quotation A2.

[0266] FIG. 45(b) is a flowchart showing the second quotation registration linking process (S290).

[0267] (S291) The registration unit 42 first registers the quotation received in S262 of FIG. 43 in the quotation TB, and assigns a quotation ID to the registered quotation, and then proceeds to S292.

[0268] (S292, S293) The linking unit 43 identifies a case corresponding to the case ID stored in the ID storage area 32 (S292), executes a process of linking the quotation registered in the quotation TB in S291 with the case identified in S292 (S293), and terminates the second quotation registration linking process.

[0269] A specific example of the process of FIG. 45(b) is not shown, but for example, when the user wants to link the quotation E2 to the case E and register it in the DB31 (storage unit 30), the user first displays the case screen G4 (FIG. 14) in the display area 10c, selects the case indicator J5 corresponding to the case E displayed on the case screen G4, and displays the case details screen G5 (FIG. 16) in the display area 10c. At this time, the case id5 corresponding to the case E is stored in the id storage area 32. The user selects the case document tab T4 arranged on the case details screen G5, displays the case document screen G6 (FIG. 17) in the display area 10c, and selects the second quotation registration button P4b arranged in the area G6c of the case document screen G6. Then, the fourth registration screen is displayed in the area 10c. Then, the user specifies the quotation E2 in the fourth area of ​​the fourth registration screen, and thereafter selects the fourth send button, whereby the server 20 (control unit 40) first accepts from the user terminal 10 a registration request to register in DB31 the quotation E2 (related materials) related to the case E registered in DB31 (S282 in FIG. 44), then refers to the case TB in FIG. 8(c), identifies the case E corresponding to the case id5 stored in the id memory area 32, links this identified case E with the quotation E2 corresponding to the registration request accepted in S282 in a one-to-one, one-to-many, many-to-one, or many-to-many relationship, and registers the quotation E2 in the quotation TB (FIG. 9(c)).

[0270] FIG. 46(a) is a flowchart showing the process executed in the system 1 when the new case linking button P5c is selected.

[0271] As described above, the new case linking button P5c is a button for generating a new case and linking the generated new case with a drawing corresponding to the drawing ID stored in the ID storage area 32. The new case linking button P5c is arranged only on the linking screen G8.

[0272] As shown in FIG. 46(a), the user terminal 10 makes a new case linking request to the server 20 by selecting the new case linking button P5c (S301), and when the server 20 accepts the new case registration request (S302), it executes the new case linking process (S310).

[0273] FIG. 46(b) is a fifteenth flowchart showing a part of the processing in the system 1 in response to the selection operation of the link to existing case button P5d.

[0274] As described above, the existing case linking button P5d is a button for linking one case registered in the case TB with a drawing corresponding to the drawing ID stored in the ID storage area 32. The existing case linking button P5d is arranged only on the linking screen G8.

[0275] As shown in FIG. 46(b), the user terminal 10 selects (S321) the case indicator J arranged on the linking screen G8, and then selects (S322) the existing case linking button P5d to send the case corresponding to the case indicator J selected in S321 to the server 20, i.e., makes a request to the server 20 to link the case corresponding to the case indicator J selected in S321 with the drawing corresponding to the drawing id stored in the id memory area 32 (hereinafter referred to as an "existing case linking request").When the server 20 accepts the existing case linking request (S322), it executes the existing case linking process (S330).

[0276] FIG. 47 is a flowchart showing the new case linking process (S310).

[0277] (S312 to S315) The registration unit 42 first refers to the drawing TB to identify the drawing corresponding to the drawing ID stored in the ID memory area 32 (S311), then generates a case (S312), then registers the case generated in S312 in the case TB (S313), then assigns a case ID to the case registered in the case TB in S313 (S314), then executes a process of linking the drawing identified in S311 with the case registered in S313 (S315), and terminates the new case linking process.

[0278] FIG. 48 is a flowchart showing the existing case linking process (S330).

[0279] (S331 to S333) The linking unit 43 first refers to the case TB to identify the case corresponding to the case indicator J selected by the user in S321, i.e., the case accepted by the server 20 in S323 (S331), then refers to the drawing TB to identify the drawing corresponding to the drawing id stored in the id storage area 32 (S332), then executes a process of linking the case identified in S331 with the drawing identified in S332 (S333), and terminates the existing case linking process. Note that the control unit 40 stores the case id corresponding to the case identified in S331 in the id storage area 32.

[0280] Next, a specific example 2 will be described.

[0281] FIG. 49 is an explanatory diagram for explaining the specific example 2. The specific example 2 is an example in which a new request F is made from a customer to a user. As shown in FIG. 49(a), the request F is a request to manufacture a product B manufactured according to a drawing B1 and a product C manufactured according to a drawing C1, and to deliver both products B and C to the customer. Here, as shown in FIG. 8(b), both the drawing B1 and the drawing C1 are registered in the drawing TB. Therefore, the user does not need to register the drawings B1 and C1 in the drawing TB via the first registration screen G10 (FIG. 36) or the second registration screen G11 (FIG. 38). Therefore, as shown in FIG. 49(b), in specific example 2, the user first generates a new case F to which drawing B1 is linked via the linking screen G8 (step 1), and then links the existing case F generated in step 1 to drawing C1 via the linking screen G8 (step 2), thereby turning request F into a case (deciding to link case F to drawing B1, and case F to drawing C1, respectively).

[0282] Fig. 49(c) shows step 1 of concrete example 2. As shown in the figure, in order to generate a new case F to which the drawing B1 is linked, the user first displays the drawing details screen G2 showing the details of the drawing B1 in the display area 10c, selects the case confirmation button P5a on this screen G2, displays the linking confirmation screen G7 in the display area 10c, then selects the case linking button P5b on this screen G7, displays the linking screen G8 in the display area 10c, and then selects the new case linking button P5c on this screen G8. In response to this selection operation, the control unit 40 executes the new case linking process (S310) of Fig. 46(a), and generates a new case F to which the drawing B1 is linked by this process.

[0283] 49(c) in detail, since the drawing details screen G2 is a screen that displays in detail the drawing corresponding to the drawing id stored in the id storage area 32, when the case confirmation button P5a is selected on the drawing details screen G2 showing the details of drawing B1, the drawing id2 corresponding to drawing B1 is stored in the id storage area 32. Therefore, in S311 of the new case linking process, the drawing TB in FIG. 8(b) is referenced to identify drawing B1 corresponding to drawing id2 stored in the id storage area 32, and in S315, the drawing B1 identified in S311 is linked to the case F newly generated in S312. As a result, a new case F linked to drawing B1 is generated.

[0284] In this way, in this embodiment, the creation of a new case and linking the newly created case to an existing drawing (hereinafter referred to as an "existing drawing") registered in the drawing TB can be performed with a single operation of selecting the New Case Linking button P5c.

[0285] FIG. 49(d) shows step 2 of the specific example 2. As shown in the figure, in order to link the drawing C1 with the case F generated in step 1, the user first displays the drawing details screen G2 showing the details of the drawing C1 in the display area 10c. At this time, the drawing id3 corresponding to the drawing C1 is stored in the id storage area 32. The user selects the case confirmation button P5a on the drawing details screen G2 showing the details of the drawing C1 to display the linking confirmation screen G7 in the display area 10c, and selects the case linking button P5b on this screen G7 to display the linking screen G8 in the display area 10c. At this time, the case indicator J corresponding to the case F generated in step 1 is displayed on the linking screen G8. The user selects the case indicator J corresponding to the case F on the linking screen G8, and subsequently selects the existing case linking button P5d. As a result, the control unit 40 executes an existing case linking process (S310 in Figure 46 (b)), and through this process, the case F corresponding to the case mark J selected by the user is linked to the drawing C1 corresponding to the drawing id3 stored in the id memory area 32.

[0286] In this manner, in this embodiment, the linking screen G8 includes an existing case linking button P5d for linking an existing drawing with an existing case registered in the case TB (hereinafter referred to as an "existing case"), and an existing drawing can be linked with an existing case by simply operating this button P5d once. Therefore, linking an existing drawing with an existing case is easy.

[0287] In this embodiment, by displaying the drawing details screen G2 in the display area 10c before linking an existing drawing with an existing case, it is possible to specify the existing drawing to be linked with the existing case (hereinafter referred to as the "existing drawing to be linked"), making it easy to specify the existing drawing.

[0288] In particular, in this embodiment, the drawing details screen G2 includes an area G2a, which is an area that displays the drawing in detail, and the drawing displayed in this area G2a (i.e., the drawing corresponding to the drawing ID stored in the ID storage area 32) can be specified as the existing drawing to be linked, so that the existing drawing and the existing case can be linked after confirming the details of the existing drawing to be linked. This makes it possible to prevent mistakes in linking the existing drawing and the existing case.

[0289] Next, a specific example 3 will be described.

[0290] FIG. 50 is an explanatory diagram for explaining the concrete example 3. The concrete example 3 is an example in which a new request F (different from the request F in FIG. 49) is made from a customer to a user. As shown in FIG. 50(a), the request F is a request to manufacture a product B manufactured according to a drawing B1 and a product F manufactured according to a drawing F1, and to deliver both products B and F to a customer. Here, as shown in FIG. 8(b), since the drawing B1 is registered in the drawing TB, there is no need to register the drawing B1 via the first registration screen G10 (FIG. 36) or the second registration screen G11 (FIG. 38), but since the drawing F1 is not registered in the drawing TB, there is a need to register the drawing F1 via the registration screens G10 and G11. Therefore, as shown in Fig. 50(b), the user first generates a new case F to which drawing B1 is linked via the linking screen G8 (step 1), similar to step 1 in specific example 2, then registers drawing F1 in drawing TB via the first registration screen G10 (step 2), and finally links drawing F1 to the case F generated in step 1 via the linking screen G8 (step 3), thereby turning request F into a case. It goes without saying that steps 1 and 2 shown in Fig. 50(b) may be reversed.

[0291] 50(c) shows step 1 of specific example 3. Step 1 of specific example 3 is the same as step 1 of specific example 2, so a description thereof will be omitted.

[0292] Fig. 50(d) shows step 2 of concrete example 3. As shown in Fig. 50(a), the user sorts out the system of drawing F1 into system 001. In order to register drawing F1 in drawing TB, the user first displays the first registration screen G10 (Fig. 36) in the display area 10c as shown in Fig. 50(d), then specifies drawing F1 in the first area G10a of this screen G10, inputs system 001 in the first input field G10b, and selects the first send button G10d without requesting that the request F related to drawing F1 be made into a case (without selecting the request field G10c). As a result, the control unit 40 executes the first drawing etc. registration process (S210) and the first drawing etc. linking process (S220) in Figure 37, and through these processes, registers drawing F1 in drawing TB (S214) and links this drawing F1 to system 001 registered in the system TB (S221).

[0293] To explain in detail the linking process between the case F and the system 001 in Fig. 50(d), since the system 001 is registered in the system TB as shown in Fig. 8(a) (YES in S211), the registration unit 42 identifies the system 001 in S213, and registers the drawing F1 in the drawing TB in S214, and assigns a drawing ID (not shown) to the drawing F1. As described above, since the user has not requested that the request F related to the drawing F1 be made a case in step 1 in Fig. 50(c) (NO in S222), the linking unit 43 links the drawing F1 to the system 001 without generating a case that identifies the request F (S221).

[0294] FIG. 50(e) shows step 3 of concrete example 3. As shown in the figure, in order to link the existing case F generated in step 1 with the existing drawing F1 registered in the drawing TB in step 2, the user first displays the drawing details screen G2 including the details of the drawing F1 in the display area 10c, then selects the case confirmation button P5a on this screen G2 to display the linking confirmation screen G7 in the display area 10c, selects the case linking button P5b on this screen G7 to display the linking screen G8 in the display area 10c. Then, the user selects the case indicator J corresponding to the case F on the linking screen G8, and then selects the existing case linking button P5d. As a result, the control unit 40 executes the existing case linking process (S330) of FIG. 46(b), and this process links the existing case F registered in the case TB with the existing drawing F1 registered in the drawing TB.

[0295] In this manner, in this embodiment, if one wishes to link a drawing (hereinafter referred to as a "new drawing"; for example, drawing F1 in specific example 3) that one wishes to register in the drawing TB to an existing case (a case registered in the case TB; for example, case F in specific example 3), one first registers the drawing in the drawing TB without intentionally requesting case creation (without selecting the request field G10c) on the first registration screen G10, and then one can link the drawing registered in the drawing TB to the existing case via the linking screen G8.

[0296] For example, when registering a drawing in the drawing TB, even if you do not want to or cannot make it a case, for example, because the request for this drawing has not been officially confirmed, if a customer officially requests the manufacture of a product to be manufactured according to the existing drawing later (after the drawing has been registered in the drawing TB), it is possible to register a case that identifies this request and link this case to the existing drawing.

[0297] Next, a fourth specific example will be described.

[0298] FIG. 51 is an explanatory diagram for explaining the specific example 4. The specific example 4 is an example in which a new request F is made from a customer to a user. As shown in FIG. 51(a), the request F is a request to manufacture a product B manufactured according to a drawing B1 and a product F manufactured according to a drawing F1, and to deliver both products B and F to the customer. Here, as shown in FIG. 8(b), the drawing B1 is registered in the drawing TB, but the drawing F1 is not registered in the drawing TB. Therefore, as in the specific example 2, the user must register the drawing F1 via the registration screens G10 and G11. Therefore, as shown in FIG. 51(b), the user first generates a new case F to which the drawing B1 is linked via the linking screen G8 (step 1), as in the step 1 of the specific example 2, and then, unlike the step 2 of the specific example 3, registers the drawing F1 in the drawing TB via the second registration screen G11, and links the drawing F1 to the case F generated in the step 1 (step 2), thereby making the request F a case.

[0299] 51(c) shows step 1 of specific example 4. Step 1 of specific example 4 is the same as step 1 of specific example 2, so a description thereof will be omitted.

[0300] FIG. 51(d) shows step 2 of specific example 4. As shown in the figure, the user first displays the case details screen G5 showing the details of the case F in the display area 10c in order to register the drawing F1 in the drawing TB and to link the case F generated in step 1 with the drawing F1. At this time, the case ID (not shown) corresponding to the case F is stored in the id storage area 32 (S83 in FIG. 30). The user selects the case document tab T4 on the case details screen G5 showing the details of the case F to display the case document screen G6 in the display area 10c, and selects the second drawing registration button P3b on this screen G6 to display the second registration screen G11 (FIG. 38) in the display area 10c. At this time, the case ID (not shown) corresponding to the case F is stored in the id storage area 32 (see FIG. 35(r)(v)). Then, the user specified the drawing F1 in the second area G11a of the second registration screen G11, and then selected the second send button G11b. As a result, the control unit 40 executes the second drawing etc. registration process (S240) and the second drawing etc. linking process (S250) as shown in Fig. 39 and Fig. 40, and through these processes, the drawing F1 is registered in the drawing TB (S241), the case F corresponding to the case id stored in the id storage area 32 is identified (S242), and the drawing F1 registered in the drawing TB in S241 and the case F identified in S242 are linked (S251).

[0301] In this way, in this embodiment, not only can a new drawing be registered via the second registration screen G11, but the new drawing can also be linked to an existing case, eliminating the need for cumbersome operations and reducing the user's effort in managing drawings.

[0302] In this embodiment, by displaying the case details screen G5 in the display area 10c before linking a new drawing with an existing case, it is possible to specify the existing case to be linked with the new drawing (hereinafter referred to as the "existing case to be linked"), making it easy to specify the existing case.

[0303] In particular, in this embodiment, the project document screen G6, which is transitioned to by operating the project document tab T4 from the project details screen G5, includes areas G6a, G6b, and G6c, and these areas are configured to display each document (drawing and estimate) related to the existing project to be linked, so that the new drawing and the existing project can be linked after confirming the details of the existing project to be linked. Therefore, it is possible to prevent mistakes in linking the new drawing and the existing project.

[0304] In this embodiment, systems and drawings are registered in DB31 (storage unit 30) in a 1-to-N relationship, systems and quotations (related documents) are registered in a 1-to-N relationship, drawings and cases are registered in a N-to-N relationship, systems and cases are registered in a N-to-N relationship, and quotations (related documents) and cases are registered in a N-to-N relationship, and a specific screen is generated in response to a viewing request from user terminal 10, and the generated specific drawing is provided to user terminal 10, but the configuration is not limited to this.

[0305] As a variation of the above, more specifically, in addition to various information on systems, drawings, quotations, and projects, DB31 may register information on the requesting customer, information on the product requested by the customer to be manufactured, the date on which the customer requested the product to be manufactured (request date), the date on which the request from the customer was officially received (order date), progress on the request (for example, "not yet accepted" indicating that the request has not yet been officially received, "being accepted" indicating that the request has been officially received, "completed" indicating that the officially received request has been completed), the number of orders received (number of orders), and other information, and this information may be linked, for example, to projects registered in the project TB or systems registered in the system TB.

[0306] When configured as described above, for example, as shown in FIG. 52, information on products, customers, and progress can be displayed in area G2a on the drawing details screen G2; for example, as shown in FIG. 53, information such as progress (for example, completion as shown in the same figure) and products (flanges as shown in the same figure) can be displayed in system marker H; for example, as shown in FIG. 54, information such as progress, order date, delivery date, and number of orders can be displayed in area G5a on the project details screen G5; and for example, as shown in FIG. 55, information on each progress, delivery date, etc. can be displayed in project markers J1 to J5.

[0307] As described above, the relationship between the systems registered in the system TB and the drawings registered in the drawing TB is such that one system (e.g. system 001) is linked to multiple drawings (e.g. drawings A1, C1), and one drawing (e.g. drawing A1) is linked to one system (e.g. system 001), and the systems and drawings are linked in a one-to-one or one-to-many relationship. Therefore, the amount of data registered in DB31 can be compressed, compared to a configuration in which the systems and drawings are linked in a one-to-one relationship.

[0308] In addition, the relationship between the systems registered in the system TB and the quotations registered in the quotation TB is a one-to-one or one-to-many relationship between the systems and quotations, similar to the relationship between the systems and drawings. Therefore, the amount of data registered in the DB31 can be compressed, compared to a configuration in which the systems and drawings are linked in a one-to-one relationship.

[0309] Furthermore, the relationship between the systems registered in the system TB and the cases registered in the case TB is such that one system (for example, system 001) is linked to multiple cases (for example, cases A, C, D, E) and one case (for example, case E) is linked to multiple systems (for example, systems 001, 002) by the first intermediate TB, and the systems and cases are linked in a one-to-one or one-to-many or many-to-one or one-to-many or many-to-many relationship. Therefore, the amount of data registered in DB31 can be compressed compared to a configuration in which the systems and cases are linked in a one-to-one, one-to-many or many-to-one relationship.

[0310] Furthermore, the relationship between the drawings registered in the drawing TB and the projects registered in the project TB is linked by the second intermediate TB in a one-to-one, one-to-many, many-to-one, one-to-many, or many-to-many relationship, similar to the relationship between systems and projects. Therefore, the amount of data registered in DB31 can be compressed, compared to a configuration in which the drawings and projects are linked in a one-to-one, one-to-many, or many-to-one relationship.

[0311] Also, the relationship between the estimates registered in the estimate TB and the projects registered in the project TB is linked by the third intermediate TB in a one-to-one, one-to-many, many-to-one, one-to-many, or many-to-many relationship, similar to the relationship between systems and projects. Therefore, the amount of data registered in DB31 can be compressed, compared to a configuration in which estimates and projects are linked in a one-to-one, one-to-many, or many-to-one relationship.

[0312] In this embodiment, the drawings registered in the drawing TB are not linked to the quotations registered in the quotation TB, so the amount of data registered in the DB 31 can be reduced compared to a configuration in which the drawings and quotations are linked.

[0313] The system, program, etc. in the present embodiment can be modified in various ways without departing from the spirit of the present invention. In addition, the order of control can also be modified as appropriate as long as a desired effect is obtained.

[0314] <Configuration 1> The system 1 for managing drawings includes a control unit 40 and a storage unit 30. The control unit 40 registers drawings (e.g., drawings A1 and C1 shown in FIG. 8(b)) and the system of the drawings (e.g., system 001 shown in FIG. 8(a)) in a one-to-one or many-to-one linked relationship in the memory unit 30 (DB31), and registers related documents related to the drawings (e.g., quotations A2, C2, D2, and E2 shown in FIG. 8(d)) and the system of the drawings (e.g., system 001 shown in FIG. 8(a)) in a one-to-one or many-to-one linked relationship in the memory unit 30 (DB31), A drawing (e.g., drawings A1 and B1 shown in FIG. 8(b)) and a case specifying a manufacturing request for a product to be manufactured according to the drawing (e.g., case E shown in FIG. 8(c)) are registered in the storage unit 30 (DB31) in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship (e.g., see the second intermediate TB shown in FIG. 9(b)). A system of drawings (e.g., systems 001 and 002 shown in FIG. 8(a)) and a case specifying a manufacturing request for a product to be manufactured according to the drawing (e.g., case E shown in FIG. 8(c)) are registered in the storage unit 30 (DB31) in a one-to-one, one-to-many, many-to-many, or many-to-many linked relationship (e.g., see the second intermediate TB shown in FIG. 9(b)). For example, a document related to the drawing (e.g., quotation A2 shown in FIG. 8(d)) and a document specifying a manufacturing request for a product to be manufactured in accordance with the drawing (e.g., document A shown in FIG. 8(c)) are registered in the memory unit 30 (DB31) in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship (for example, see the first intermediate TB shown in FIG. 9(a)). Related materials related to the drawing (e.g., quotation A2 shown in FIG. 8(d)) and a document specifying a manufacturing request for a product to be manufactured in accordance with the drawing (e.g., document A shown in FIG. 8(c)) are registered in the memory unit 30 (DB31) in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship (for example, see the third intermediate TB shown in FIG. 9(c)). The drawing and related materials related to the drawing are registered in the memory unit 30 (DB31) in an unlinked relationship. Based on a request to view information registered in the memory unit 30 (DB31) (e.g., a request to view the drawing shown in FIG. 25) from the user terminal 10, information corresponding to the viewing request (e.g., the drawing details screen shown in FIG. 25) is provided to the user terminal 10.

[0315] <Configuration 2> the control unit 40 is configured to generate a system indicator H for each system registered in the storage unit 30 based on a request to view the systems registered in the storage unit 30 (DB31) (e.g., a login request shown in FIG. 35(a)) from the user terminal 10, and provide the generated system indicator H to the user terminal 10; One system label H (for example, system label H1 in Figure 11(a)) includes one system (for example, system 001) registered in the memory unit 30 and a reduced drawing obtained by reducing any one of one or more drawings linked to this one system (for example, reduced drawing C1 obtained by reducing drawing C1 out of drawings A1 and C1 linked to system 001).

[0316] <Configuration 3> The control unit 40 is configured to generate a case indicator J for each case registered in the storage unit 30 based on a request to view the cases registered in the storage unit 30 (DB31) (selection of the case button P2 shown in FIG. 35(k)) from the user terminal 10, and provide the generated case indicator J to the user terminal 10. One case indicator J (for example, case indicator J1 in Figure 15) includes one case (for example, case A) registered in the memory unit 30 and a system linked to this one case (for example, system 001 linked to case A).

[0317] <Configuration 4> Based on receiving a request to view related materials registered in the memory unit 30 (DB31) from the user terminal 10 (an operation of selecting the quotation tab T2 on the drawing details screen G2 that displays drawing C1 in detail (Figure 35 (g))), the control unit 40 identifies one system (e.g., system 001 linked to drawing C1) linked to the related materials corresponding to the viewing request, identifies one or more related materials linked to the identified system (e.g., quotations A2, C2, D2, E2 linked to system 001), and provides reduced related materials that are reduced versions of the identified one or more related materials (e.g., reduced estimate A2, reduced estimate C2, reduced estimate D2, reduced estimate E2 displayed in area G3b of the quotation screen G3 in Figure 13) and the related materials corresponding to the viewing request (e.g., estimate E2 displayed in area G3a of the quotation screen G3 in Figure 13) to the user terminal 10.

[0318] <Component 5> The system 1 for managing drawings includes a control unit 40 and a memory unit 30, and based on receiving a registration request from a user terminal 10 to register a drawing in the memory unit 30 (selection of the first send button G10d on the first registration screen G10 (Figure 36)), the control unit 40 generates a case that identifies a manufacturing request for a product to be manufactured in accordance with the drawing corresponding to the registration request (S216 in Figure 40(a)), and registers the generated case and the drawing corresponding to the registration request in the memory unit 30 in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship (see Figures 8, 9, etc.).

[0319] <Component 6> The system 1 for managing drawings includes a memory unit 30 (see Figure 8, etc.) that registers drawings and their series in a one-to-one or many-to-one association, and a control unit 40 that, based on receiving a request from a user terminal 10 to view a drawing registered in the memory unit 30, provides the user terminal 10 with a drawing corresponding to the viewing request. Based on receiving a registration request from the user terminal 10 to register related materials related to the drawings registered in the memory unit 30 in the memory unit 30 (selection operation of the third send button G12b in Figure 42 (see S261 in Figure 43)), the control unit 40 identifies, from the series registered in the memory unit 30, a series linked to the drawings related to the related materials corresponding to the registration request (S272 in Figure 45(a)), and links the identified series to the related materials corresponding to the registration request in a one-to-one or one-to-many association, while not linking the related materials corresponding to the registration request to the drawings related to the related materials.

[0320] <Component 7> A server (information processing device) 20 that manages drawings is equipped with a control unit 40 and a memory unit 30, and the control unit 40 registers in the memory unit 30 a drawing and a system of the drawing in a one-to-one or multiple-to-one linked relationship, registers in the memory unit 30 related materials related to the drawing and the system of the drawing in a one-to-one or multiple-to-one linked relationship, registers in the memory unit 30 a drawing and a case specifying a manufacturing request for a product to be manufactured in accordance with the drawing in a one-to-one, one-to-multiple, multiple-to-one, or multiple-to-multiple linked relationship, registers in the memory unit 30 a system of the drawing and a case specifying a manufacturing request for a product to be manufactured in accordance with the drawing in a one-to-one, one-to-multiple, multiple-to-one, or multiple-to-multiple linked relationship, registers in the memory unit 30 related materials related to the drawing and a case specifying a manufacturing request for a product to be manufactured in accordance with the drawing in a one-to-one, one-to-multiple, multiple-to-one, or multiple-to-multiple linked relationship, registers in the memory unit 30 a related material related to the drawing and a case specifying a manufacturing request for a product to be manufactured in accordance with the drawing in a one-to-one, one-to-multiple, multiple-to-one, or multiple-to-multiple linked relationship, and registers in the memory unit 30 a drawing and related materials related to the drawing so as not to be linked.

[0321] <Component 8> Based on receiving a request to view one system registered in the memory unit 30 (DB31) from the user terminal 10 (for example, an operation to select system indicator J1 shown in Figure 35 (d)), the control unit 40 identifies one system corresponding to the viewing request (for example, system 001 corresponding to system indicator J1), identifies one or more drawings linked to the identified one system (for example, drawings A1, C1 linked to system 001), and provides the user terminal 10 with reduced drawings that are reduced in size from the identified one or more drawings (for example, reduced drawing A1 and reduced drawing C1 shown in area G2C in Figure 12).

[0322] In this embodiment, the selection operation of the system indicator J is configured to display the drawing detail screen G2 in the display area 10c. Since the drawing detail screen G2 is a screen that shows one drawing in detail, the selection operation of the system indicator J is also a request to the server 20 to view one drawing. Therefore, it is also possible to read the "viewing request for one system registered in the storage unit 30 (DB31)" in the above configuration 8 as a "viewing request for one drawing registered in the storage unit 30 (DB31)". When read in this way, the control unit 40, based on receiving a view request for one drawing registered in the storage unit 30 (DB31) from the user terminal 10, identifies a system linked to one drawing corresponding to the view request, identifies one or more drawings linked to the identified system, and provides the user terminal 10 with reduced drawings obtained by reducing the identified one or more drawings.

[0323] <Component 9> The system 1 for managing drawings includes a control unit 40 and a memory unit 30. Based on receiving a registration request to register a drawing in the memory unit 30 from the user terminal 10 (e.g., selection of the second send button G11b on the second registration screen G11 (Figure 38)), the control unit 40 identifies one case registered in the memory unit 30 (S242 in Figure 40(b)), and registers the identified case and the drawing corresponding to the registration request in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship in the memory unit 30 (see Figures 8, 9, etc.).

[0324] <Component 10> Based on receiving a viewing request from the user terminal 10 to view details of one of the cases registered in the memory unit 30 (for example, a selection operation of the case indicator J1 corresponding to case A shown in FIG. 35(p)), the control unit 40 identifies one or more systems linked to the one of the cases corresponding to the viewing request (for example, system 001 linked to case A (FIG. 9(a))) and one or more drawings linked to the one of the cases corresponding to the viewing request (for example, drawing A1 linked to case A (FIG. 9(b))), and provides the one of the cases corresponding to the viewing request (for example, case A), the identified one or more systems (for example, system 001), and reduced drawings (for example, reduced drawing A1) obtained by reducing the identified one or more drawings to the user terminal 10 (see FIG. 16).

[0325] <Component 11> Based on receiving a viewing request from the user terminal 10 to view details of one case registered in the memory unit 30 (DB31) (a selection operation of the case indicator J1 corresponding to case A shown in FIG. 35(p)), the control unit 40 identifies a system linked to the one case corresponding to the viewing request (for example, system 001 linked to case A (FIG. 9(a))) and provides the one case corresponding to the viewing request (for example, case A) and the identified system (for example, system 001) to the user terminal 10 (see FIG. 16).

[0326] <Component 12> Based on receiving a viewing request (selection operation of the case materials tab T4 shown in FIG. 35(t)) from the user terminal 10 to view materials related to one case registered in the memory unit 30 (for example, drawings and estimates shown in FIG. 8), the control unit 40 identifies one or more drawings (for example, drawing A1 linked to case A) linked to the one case corresponding to the viewing request and one or more related materials (for example, estimate A2 linked to case A) linked to the one case corresponding to the viewing request, and provides a reduced-size drawing of the identified drawing (for example, reduced drawing A1) and a reduced-size related material (for example, reduced estimate A2) reduced from the identified related material to the user terminal 10 (see FIG. 17 and FIG. 18).

[0327] <Component 13> The linking screen G8 includes a new case linking button P5c and an existing case linking button P5d. Selecting the new case linking button P5c generates a new case that is not registered in the case TB and links this new case to one drawing registered in the drawing TB (a drawing corresponding to the drawing ID stored in the ID memory area 32). Selecting the existing case linking button P5d links one case registered in the case TB to one drawing registered in the drawing TB (a drawing corresponding to the drawing ID stored in the ID memory area 32). [Explanation of symbols]

[0328] 1 System 10 User terminal 20 Server (information processing device) 30 Storage section 31 Database 40 Control section G1 system screen G2 Drawing details screen G3 Quote Screen G4 project screen G5 Item details screen G6 project document screen H strain indicator J project indicator

Claims

1. A system for managing drawings, comprising: A control unit and a storage unit are included. The control unit is A drawing and a system of the drawing are registered in the storage unit in a one-to-one or multiple-to-one linked relationship; Registering in the storage unit a related document related to a drawing and a lineage of the drawing in a one-to-one or multiple-to-one linked relationship; registering the drawings and cases specifying manufacturing requests for products to be manufactured according to the drawings in the storage unit in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a series of drawings and a case that specifies a manufacturing request for a product to be manufactured according to the drawings in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a related document relating to a drawing and a case specifying a manufacturing request for a product to be manufactured according to the drawing in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering the drawings and related materials related to the drawings in the storage unit so as not to link them to each other; When a request to view information registered in the storage unit is received from a user terminal, information corresponding to the request is provided to the user terminal. A system characterized by:

2. The control unit is a system indicator is generated for each system registered in the storage unit based on a request for browsing the systems registered in the storage unit from the user terminal, and the generated system indicator is provided to the user terminal; The system indicator includes one system registered in the storage unit and a reduced drawing obtained by reducing a drawing associated with the one system.

2. The system of claim 1 .

3. The control unit is a request to view the cases registered in the storage unit is received from the user terminal, the request generating a case indicator for each case registered in the storage unit is provided to the user terminal, The case indicator includes one case registered in the storage unit and a system associated with the one case.

3. The system according to claim 1 or 2.

4. The control unit is Based on receiving a request to view related materials registered in the storage unit from the user terminal, the method identifies one category linked to the related materials corresponding to the viewing request, identifies one or more related materials linked to the identified category, and provides the user terminal with reduced related materials obtained by reducing the identified one or more related materials and the related materials corresponding to the viewing request.

2. The system of claim 1 .

5. A system for managing drawings, comprising: A control unit and a storage unit are included. The control unit is Based on receipt of a registration request for registering a drawing in the storage unit from a user terminal, a case is generated that specifies a manufacturing request for a product to be manufactured in accordance with the drawing corresponding to the registration request, and the generated case and the drawing corresponding to the registration request are registered in the storage unit in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship. A system characterized by:

6. A system for managing drawings, comprising: A storage unit in which drawings and the systems of the drawings are registered in a one-to-one or multiple-to-one manner; a control unit that, based on receipt of a request from a user terminal to view a drawing registered in the storage unit, provides the user terminal with a drawing corresponding to the request; Including, The control unit is Based on receiving a registration request from the user terminal for registering in the storage unit a related document related to the drawing registered in the storage unit, a system linked to the drawing related to the related document corresponding to the registration request is specified from among the systems registered in the storage unit, and the specified system is linked one-to-one or one-to-multiple to the related document corresponding to the registration request, while not linking the related document corresponding to the registration request to the drawing related to the related document corresponding to the registration request. A system characterized by:

7. An information processing device for managing drawings, A control unit and a storage unit are provided. The control unit is A drawing and a system of the drawing are registered in the storage unit in a one-to-one or multiple-to-one linked relationship; Registering in the storage unit a related document related to a drawing and a lineage of the drawing in a one-to-one or multiple-to-one linked relationship; registering the drawings and cases specifying manufacturing requests for products to be manufactured according to the drawings in the storage unit in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a series of drawings and a case that specifies a manufacturing request for a product to be manufactured according to the drawings in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; registering in the storage unit a related document relating to a drawing and a case specifying a manufacturing request for a product to be manufactured according to the drawing in a one-to-one, one-to-many, many-to-one, or many-to-many linked relationship; A drawing is registered in the storage unit so as not to be linked to a related document related to the drawing.

23. An information processing apparatus comprising:

Images