Product order placement / reception system

Abstract

To provide a product order placement / reception system configured to manage multiple drawing files input from an orderer, as one order-placement record for each product, and accept questions or requests (request for additional drawing or confirmation of material) regarding drawings for each product from both order-placement and order-reception parties.SOLUTION: An order placement / reception system for receiving an order for a product from a user includes: a processor comprising a file receiving unit which receives a drawing file including drawings of a product, a record preparation unit which prepares a record for order placement based on the drawing file, and a talk-room generation unit which generates a talk room regarding the record; and a storage unit which stores the drawing file. The record preparation unit stores, in the storage unit, a database for storing the talk room and the drawing file stored in the storage unit in association with the record.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a technology for supporting product ordering. [Background technology]

[0002] Many businesses still place product orders using paper media. These businesses usually place orders by sending product drawings by fax or by email with the drawing data attached, and confirming by phone as needed. When ordering products by fax or email, if there are any defects or unclear points in the drawings, the recipient must contact the purchaser by email or phone inquiring.

[0003] In recent years, systems have been developed that use drawing files to estimate and order products in order to improve the efficiency of product ordering processes.

[0004] As a system for carrying out such order processing, a technology for placing and receiving orders by inputting a drawing file as order information and checking the manufacturing process after the order processing is described in Patent Document 1. Patent Document 1 describes a technology for displaying multiple manufacturing processes in which a product is manufactured, allowing a user to select one of the multiple manufacturing processes and ask a question or make a request. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] International Publication No. 2018 / 230693 (Patent No. 7216421) Summary of the Invention [Problem to be solved by the invention]

[0006] Patent Document 1 discloses a technology that receives order data indicating the specifications, quantity, and delivery date of a product to be manufactured, and displays image data of the manufacturing process in association with the manufacturing process. It also discloses a technology that displays a request from an orderer regarding a corresponding process from among multiple manufacturing processes, or reply data to the request, for the corresponding process.

[0007] In Patent Document 1, the purchaser can communicate requests and questions to the contractor for each manufacturing process, but cannot view multiple manufacturing processes as a whole and confirm requests and questions about the product. Also, only the purchaser can make requests and questions about the manufacturing process, and it is not anticipated that the contractor will make inquiries about drawings (Patent Publication No. 7216421, paragraphs 0048-0054).

[0008] Furthermore, Patent Document 1 does not mention cases where there are multiple drawing files. This means that when a drawing file alone is not sufficient to produce a product and a CAD file is added to supplement the missing information, or when an input drawing file is updated to a new version of the drawing file, the added drawing file or the updated drawing file cannot be treated as a single order record.

[0009] Furthermore, although Patent Document 1 states that drawing files are to be input, it does not mention the format of the drawing files, i.e., whether the drawing files are in PDF format, JPEG format, GIF format, or BMP format, or whether the drawing files are in CAD data STEP format, IGES format, SAT format, etc.

[0010] In reality, during the process of inputting a drawing file and obtaining a quote, additional drawing files with different formats or updated drawing files with updated drawings or processes may be provided to the drawing file. These should be managed as a single order record for one product, but the technology in Patent Document 1 cannot handle this.

[0011] Therefore, the object of this invention is to provide a product ordering system that allows the creation of an order record for each product, and allows the purchaser and the seller to ask questions and make requests regarding drawings (requests for additional drawings, confirmation of materials, etc.). [Means for solving the problem]

[0012] In order to achieve the above-mentioned object, one aspect of the present invention is an order-taking system that accepts product orders from users, and includes a file receiving unit that receives a drawing file containing a drawing of the product, a record creation unit that creates a record for the order based on the drawing file, a memory unit that stores the drawing file, and a talk room creation unit that creates a talk room related to the record, and the record creation unit stores a database in the memory unit that associates and saves the talk room and the drawing file stored in the memory unit with the record. [Effects of the Invention]

[0013] According to the present invention, one order record is created for each product, and questions and requests regarding drawings (requests for additional drawings, confirmation of materials) can be made by the purchaser or the order recipient. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram showing an example of the overall system of this embodiment. [Figure 2] FIG. 2 is a diagram showing an example of the hardware configuration of the order placement and receipt system of this embodiment. [Figure 3] FIG. 3 is a diagram showing an example of a functional block diagram of the ordering system of this embodiment. [Figure 4] FIG. 4 is a diagram showing the overall processing flow of this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of a drawing file input screen according to this embodiment. [Figure 6A] FIG. 6A is a diagram showing an example of a user table for managing users according to this embodiment. [Figure 6B] FIG. 6B is a diagram showing an example of a folder table for managing the correspondence between folders and users in this embodiment. [Figure 6C] FIG. 6C is a diagram showing an example of a record table according to this embodiment. [Figure 6D] FIG. 6D is a diagram showing an example of the intermediate table 1 that manages the correspondence between records and drawing files in this embodiment. [Figure 6E] FIG. 6E is a diagram showing an example of the intermediate table 2 that manages the correspondence between records and talk rooms in this embodiment. [Figure 6F] FIG. 6F is a diagram showing an example of the intermediate table 3 that manages the correspondence between talk rooms and messages in this embodiment. [Figure 6G] FIG. 6G is a diagram showing an example of a drawing table for managing the correspondence between drawing files and file paths in this embodiment. [Figure 6H] FIG. 6H is a diagram showing an example of a message table for managing correspondence between messages, users, and message contents in this embodiment. [Figure 7A] FIG. 7A is a diagram showing an example of a record screen for user U2 in this embodiment. [Figure 7B] FIG. 7B is a diagram showing an example of a record screen for user U1 in this embodiment. [Figure 8A] FIG. 8A is a diagram showing an example of the state of the inquiry screen of user U1 when inviting other users in this embodiment. [Figure 8B] FIG. 8B shows an inquiry screen for user U2 in this embodiment, showing an example of the state before switching to the invitation screen. [Figure 8C] FIG. 8C shows an example of the inquiry screen for user U2 in this embodiment, after switching to the invitation screen. [Figure 9] FIG. 9 is a diagram showing a detailed flow of the folder creation process in the overall processing flow of this embodiment shown in FIG. [Figure 10] FIG. 10 is a diagram showing a detailed flow of the file reception process in the overall processing flow of this embodiment shown in FIG. [Figure 11] FIG. 11 is a diagram showing a detailed flow of image processing in the overall processing flow of this embodiment shown in FIG. [Figure 12] FIG. 12 is a diagram showing a detailed flow of the individual record editing process of the image processing flow of this embodiment shown in FIG. [Figure 13A] FIG. 13A is a diagram showing an example of an individual record editing screen according to this embodiment. [Figure 13B] FIG. 13B is a diagram showing an individual record edit screen according to this embodiment in which an area from which characters are extracted is highlighted. [Figure 13C] FIG. 13C is a diagram showing a state in which a highlighted area is selected on the individual record editing screen of this embodiment. [Figure 13D] FIG. 13D is a diagram showing a state in which a part of the highlighted area is masked on the individual record editing screen of this embodiment. [Figure 14] FIG. 14 is a diagram showing a detailed flow of the quotation and order request process in the overall processing flow of this embodiment shown in FIG. [Figure 15] FIG. 15 is a diagram showing a detailed flow of the inquiry screen creation process in the overall processing flow of this embodiment shown in FIG. [Figure 16] FIG. 16 is a diagram showing another form of the talk room of this embodiment. [Figure 17] FIG. 17 is a diagram showing a detailed flow of an invitation on an inquiry screen in the overall processing flow of this embodiment shown in FIG. [Figure 18] FIG. 18 is a diagram showing a detailed flow of the overall processing flow of this embodiment shown in FIG. 4 when an invitation is received on the inquiry screen. [Figure 19] FIG. 19 is a diagram showing a modification of the overall processing flow shown in FIG. [Figure 20] FIG. 20 is a diagram showing an image of creating a record for each product from one image file in the modified example of FIG. [Figure 21] FIG. 21 is a diagram showing a detailed flow of image processing in the embodiment shown in FIG. [Figure 22] FIG. 22 is a diagram showing a detailed flow of the identification information determination process shown in FIG. [Figure 23] FIG. 23 is a diagram showing a detailed flow of the record creation process of the overall processing flow shown in FIG. [Figure 24] FIG. 24 is a diagram showing a processing flow for inputting an additional drawing in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0015] The following description of the embodiments will be given with reference to the drawings. Note that the embodiments described below do not limit the scope of the invention as claimed, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0016] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0017] In the following explanation, various information may be described using expressions such as "tables," but the various information may be expressed using data structures other than these. When describing identification information, expressions such as "identification information," "identifier," "name," and "ID" are used, but these are interchangeable.

[0018] When there are multiple components having the same or similar functions, they will generally be described using the same reference numerals, but even if the functions are the same, the means for realizing the functions may be different.

[0019] In the following description, processing may be performed by executing a program. The program is executed by a processor (e.g., a CPU) which is a central processing unit, and performs the specified processing while appropriately using storage resources (e.g., memory) and / or interface devices (e.g., communication ports), etc. Therefore, the processor may be the subject of the processing.

[0020] A program may be installed on a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0021] <Terminology> Product: The delivery form specified by the purchaser to the contractor.

[0022] When a purchaser orders a processed product, one processed product is the delivery form of the product, and a standard product that does not require processing is In the case of quasi-products, the standard product is the delivery form. If the purchaser specifies parts as the delivery form to the contractor, the parts become the product, and if the delivery form is a combination of parts, the combined product becomes the product. Therefore, products include processed products, standard products, and products that have been processed or combined from parts of standard products.

[0023] Record: Data that manages the order placement and receipt of a product, which is the delivery form of the purchaser. For example, a database record.

[0024] Ordering: The act of ordering a product by an orderer specifying at least one record. When placing an order, multiple records may be specified in one order.

[0025] Image files: Electronic files in PDF, JPG, PNG, GIF, TIFF, and BMP formats.

[0026] CAD File: A digital file format for objects generated and used by CAD software, including the various formats created by CAD software, including standard formats such as DXF, DWG, STL, and STEP.

[0027] Drawing files: Electronic files that depict the function, structure, and layout of a product, including image files and CAD files.

[0028] Identification information: Information that identifies the product contained in the drawing file. For example, it includes the drawing number (drawing number) and product name written on the drawing in the image file, or a combination of these. If the image file contains multiple pages, the page numbers are also included in the identification information.

[0029] <System Configuration> First, an order placement and receipt system according to one embodiment of the present invention will be described.

[0030] Figure 1 is a system configuration diagram of an order placement and receipt system according to one embodiment. The system 100 includes an order placement terminal 2 used by an orderer who places an order for a product, an order receiving terminal 3 used by a supplier who processes and manufactures the product, and an order placement and receipt system 1 connected to the order placement terminal 2 and the order receiving terminal 3 via a network 4.

[0031] The ordering terminal 2 and the order receiving terminal 3 are configured as general personal computers or tablet terminals, and the ordering system 1 is configured as general personal computers, servers, and virtual machines configured on the cloud. In the following embodiment, the ordering system 1 is configured as a server, but the ordering system 1 is not limited to a server. The network 4 can take any form as long as it allows data to be exchanged between the ordering terminal 2, the order receiving terminal 3, and the ordering system 1.

[0032] The order receiving system 1 receives order data from the order receiving terminal 2 and sends it to the order receiving terminal 3. The order receiving terminal 3 is used by the order receiving party to input information such as the estimated cost of processing the product and delivery date to the order receiving party, and to input information regarding the manufacture of the product to the order receiving party via the order receiving system 1. The order receiving party side may be divided into an intermediary that acts as the contact point for inquiries with the order receiving party, and a supplier that receives orders for product processing and manufacture from the intermediary, or the order receiving party itself may act as both the contact point for inquiries and the supplier.

[0033] Although FIG. 1 shows an example in which the ordering terminal 2 and the order receiving terminal 3 are configured as one unit, the number of units is not limited to this, and for example, there may be a plurality of ordering terminals 2 and a plurality of order receiving terminals 3, respectively.

[0034] 2 is a hardware block diagram of an order placement and receipt system 1 according to one embodiment. The order placement and receipt system 1 has a network I / F 15 for sending and receiving data to and from an order placement terminal 2 and an order receipt terminal 3 via a network 4, a central processing unit (CPU) 11, memory 12, I / O devices 14 such as display devices and input devices such as a keyboard and mouse, a storage device 13 such as an HDD or SSD, and a bus 16 connecting these. The memory 12 is a volatile memory such as SRAM or DRAM.

[0035] The memory 12 stores various programs for realizing the functions of the folder creation unit 31, file reception unit 32, image processing unit 33, record creation unit 34, inquiry processing unit 35, and login processing unit 36 ​​shown in Fig. 3. The CPU 11 executes the programs stored in the memory 12 to realize the various functions.

[0036] The ordering terminal 2 and the order receiving terminal 3 also have the hardware block diagram shown in Figure 2. The ordering terminal 2 has an interface that displays information received from the ordering system 1 on the display device of the ordering terminal 2, and transmits information entered into the interface to the ordering system 1. The order receiving terminal 3 has an interface that displays information received from the ordering system 1 on the display device of the ordering terminal 2, and transmits information entered into the interface to the ordering system 1.

[0037] FIG. 3 shows a functional block diagram of the order placement and receipt system 1.

[0038] The folder creation unit 31 creates folders, which are storage areas, and assigns them to each user. The storage areas assigned to each user store information input by each user, such as drawing files and data of messages posted to a chat room.

[0039] The file receiving unit 32 receives drawing files as part of the order data from the ordering terminal 2 via the network 4. The received drawing files are electronic files that depict the product's functions, structure, and layout, and include image files and CAD files. The received drawing files also include paper-based information that has been digitized using the scanner function of the ordering terminal 2. The drawing files received by the file receiving unit 32 may be a single drawing file, multiple drawing files in a single file format, or multiple drawing files in different file formats.

[0040] One of the features of the order receiving and placing system 1 of this embodiment is its ability to handle drawing files in various formats. These file formats include image files such as PDF, JPEG, GIF, and BMP, as well as CAD data formats such as DXF, DWG, STEP, IGES, and SAT. The file receiving unit 32 is implemented by the network IF 15 and the CPU 11, which executes programs stored in the memory 12. The file receiving unit 32 includes a file type determination unit 321 that determines the type of drawing file and an image generation unit 322. The file type determination unit 321 determines whether the received drawing file is an image file or a CAD file. This determination is made using, for example, the file identifier. If the received drawing file is a CAD file, the image generation unit 322 generates image data from the CAD data. The conversion from a CAD file to an image file can be performed using known techniques. In other words, the file receiving unit 32 obtains an image file from the received drawing file regardless of the format of the drawing file.

[0041] The image processing unit 33 receives an image file from the file receiving unit 32 and extracts words from the received image file. The image processing unit 33 has a page break determination unit 331 that determines page breaks in the image file, a character detection unit 332 that detects characters written on each page of the image file, a word recognition unit 333 that recognizes words from the characters detected by the character detection unit 332, and an identification information determination unit 334 that reads identification information that identifies a product from the words recognized by the word recognition unit 333. The functions of the character detection unit 332 and the word recognition unit 333 to recognize characters and words from each page of the image file can be realized by using a general OCR function or a feature extraction function used for object detection.

[0042] The record creation unit 34 creates a record for each page of the image file determined by the page break determination unit 331 of the image processing unit 33. The record creation unit 34 is realized by the CPU 11 executing a program stored in the memory 12.

[0043] The record created by the record creating unit 34 for each page of the image file may be managed by associating the information read from the image file by the image processing unit 33 and the drawing file with each product.

[0044] The inquiry processing unit 35 processes inquiries, quotation requests, and order requests related to records. The inquiry processing unit 35 includes a talk room creation unit 351, a display processing unit 352, a quotation receiving unit 353, and an order receiving unit 354.

[0045] The talk room creation unit 351 creates a talk room for receiving and displaying requests from purchasers and questions from suppliers regarding each record. After creating a talk room for a record, the talk room creation unit 351 stores the record ID and the talk room ID in intermediate table 2 (see FIG. 6E), and stores the talk room ID in intermediate table 3. When a message is posted to the created talk room, the talk room creation unit 351 stores the message ID in intermediate table 3 (see FIG. 6F), and stores the message ID, the user ID of the user who posted the message, and the content of the message in message table 680 (see FIG. 6H).

[0046] When an intermediary and a supplier exist on the order-receiving side as described above, the chat room creation unit 351 may separately create a buyer chat room between the buyer and the intermediary, where the buyer posts requests, comments about drawing files, etc., and a supplier chat room between the intermediary and the supplier, where the supplier posts questions about product manufacturing, such as product dimensions and processing methods, and quotations, etc. Then, the chat room creation unit 351 or the display processing unit 352 of the processing unit 11 controls the display of the buyer chat room so that the buyer can view it, but prevents the supplier from viewing it. The chat room creation unit 351 or the display processing unit 352 also controls the display of the supplier chat room so that the supplier can view it, but prevents the buyer from viewing it. Thus, the buyer chat room is shared between the buyer and the operator of the order-receiving system 1, and the supplier chat room is shared between the supplier and the operator of the order-receiving system 1.

[0047] When one order includes multiple records, the chat room creation unit 351 may create one orderer chat room where requests from the orderer regarding the multiple records included in one order are posted, and one supplier chat room where questions, etc. from suppliers regarding one order are accepted.

[0048] The display processing unit 352 performs data processing for displaying one or more records created by the record creation unit 34 on the IO device 14, which is a display device. The display processing unit 352 also generates data for displaying the record of each orderer on the display device of the order terminal 2. If a purchaser talk room related to the record exists, the display processing unit 352 also generates data for displaying the purchaser talk room together with the record. The generated display data (inquiry screen) is transmitted from the order receiving system 1 to the order terminal 2 via the network IF 15. The order receiving terminal 2 displays the display data received from the order receiving system 1 on the display device. The display processing unit 352 also generates data for displaying an image file associated with the record on the display device of the order receiving terminal. If a supplier talk room related to the record exists, data for displaying the supplier talk room is also generated. The generated display data is transmitted from the order receiving system 1 to the order receiving terminal 3 via the network IF 15. The order receiving terminal 3 displays the display data received from the order receiving system 1 on the display device.

[0049] The estimate receiving unit 353 receives a request for estimate from the ordering terminal 2 via the network 4. When the purchaser selects at least one of the records created by the record creating unit 34 and inputs the request for estimate into the ordering terminal 2, the ordering system 1 receives the request for estimate via the network 4. The estimate receiving unit 353 also transmits the request for estimate to the order receiving terminal 3 of the supplier. The order receiving terminal 3 that has received the request for estimate transmits estimate information including the estimated amount, delivery date, etc. for the request for estimate of the selected record to the ordering system 1. The estimate information received from the order receiving terminal 3 is sent to the estimate receiving unit 3 of the ordering system 1. 53 and processed.

[0050] The order receiving unit 354 selects a record created by the record creating unit 34 and accepts an order for the selected record. The drawing files received by the file receiving unit 32 have various description formats and formats, but the record creating unit 34 creates a record for each page.

[0051] The login processing unit 36 ​​executes login processing for an orderer using the ordering terminal 2 and a supplier using the order receiving terminal 3 .

[0052] <Overall Processing Flow> Figure 4 is a diagram showing the overall processing flow of the order receiving and placing system 1 of this embodiment. The overall processing flow shows the process of using the order receiving and placing system 1 to allow an orderer to input a drawing file, create a record for ordering, and place an order based on the created record.

[0053] (S41) The order receiving and placing system 1 uses the login processing unit 36 ​​of the processing unit 11 to execute login processing for the orderer using the order receiving terminal 2 and the supplier using the order receiving terminal 3. The storage device 13 of the order receiving and placing system 1 stores various management tables shown in Figure 6. Using the user table 610 (Figure 6A), login processing is performed using the user ID and password entered by the orderer into the order receiving terminal 2 and the user ID and password entered by the supplier into the order receiving terminal 3.

[0054] (S42) If the login fails, a login request is made again. If the login fails a certain number of times, the account of the entered user ID may be suspended.

[0055] (S43) If the login is successful, the login processing unit 36 ​​acquires a user ID as login user information.

[0056] (S44) The folder creation unit 31 of the processing unit 11 acquires the user ID from the login processing unit 36 ​​and creates a folder to be assigned to the logged-in user in order to store drawing files and chat room contents. The folder creation unit 31 stores the user ID of the logged-in user in the folder table of FIG. 6B in association with a folder ID that identifies the folder assigned to the user ID. For a user who already has a folder assigned, the assigned folder is selected based on the folder table. The process of assigning a folder to a user will be described later with reference to FIG. 9.

[0057] (S45) The order receiving system 1 receives the drawing file from the order receiving terminal 2 via the network 4. This process is executed by the file receiving unit 32 of the processing unit 11. If the received drawing file is an image file, the image file is used as is, and if the received drawing file is CAD data, an image file is generated. Therefore, regardless of the format of the received drawing file, a corresponding image file will exist. This allows the order receiving system 1 to create a record whether the drawing file is an image file or a CAD file. Details of the file receiving unit 32 will be described later using FIG. 10.

[0058] (S46) Next, the image processing unit 33 of the processing unit 11 processes the image of the image file obtained from the drawing file received by the file receiving unit, and extracts words from the image file for each page. It also identifies and acquires the identification information of the drawing and the product described in the drawing. Details of the processing of this image processing unit 33 will be described later with reference to FIG. 11.

[0059] (S47) One image file acquired by the file receiving unit 32 may contain multiple pages, and the record creating unit 34 creates a record for each page of the image file. The record creating unit 34 also generates individual image files by dividing the image file on a page-by-page basis.

[0060] As shown in Figure 6C, records (record table) for ordering are created for each page, with information such as a folder ID, drawing number (one of the identification information), product name, and status corresponding to a record ID that identifies each record, and these records are stored as a database in the storage device 13. In step S47, a record ID is assigned to each page in the record table to create an entry. At this stage, the drawing number, product name, status, etc. corresponding to the record ID are left blank. Since the folder ID has already been assigned, the value of the folder ID can be stored when the record ID is entered.

[0061] (S48) The record creation unit 34 edits the record created for each page in S47 by inputting information such as the drawing number, product name, and status. Details of this process will be described later with reference to Figure 12. This process is one of the features of this embodiment.

[0062] (S49) When the purchaser selects at least one of the records created by the record creation unit 34 and inputs a request for quotation into the ordering terminal 2, the quotation receiving unit 353 of the processing unit 11 receives the request for quotation via the network 4. In addition, the quotation receiving unit 353 receives quotation information including the estimated amount, delivery date, etc. for the request for quotation from the order receiving terminal 3. Details of the processing of the quotation receiving unit 353 of the processing unit 11 will be described later using FIG. 14.

[0063] (S50) The inquiry processing unit 35 processes inquiries for the records created for each product. Inquiries for the records include requests for additional product drawings from the purchaser, inquiries from the purchaser and supplier regarding changes to delivery dates, product materials, and processing methods, and questions and estimates from suppliers regarding the drawings. Here, questions regarding the drawings include confirmation of product dimensions, materials, and processing methods. In order to obtain agreement on the quotation conditions, the inquiry processing unit 35 transmits and receives data to confirm the contents of any inquiries regarding the drawings between the purchaser and supplier. Details of the processing of the inquiry processing unit 35 of the processing unit 11 will be described later using FIG. 15.

[0064] (S51) The order receiving unit 354 receives an order request from the purchaser for a record of the quotation conditions agreed upon by the quotation receiving unit 353, among the records created by the record creating unit 34. When the purchaser selects a record for which they wish to place an order from the record table, the order request is transmitted via the network 4 to the order receiving system 1 and is received by the order receiving unit 354 of the order receiving system. Details of the processing by the order receiving unit 354 of the processing unit 11 will be described later using FIG. 14.

[0065] The above processing has explained the outline of the basic processing of the order placement and receipt system 1, and different processing may be executed in each step. Also, additional processing other than the steps shown in Figure 4 may be executed.

[0066] <Drawing File Input Image> Fig. 5 is a diagram showing an example of a drawing file input screen of the ordering terminal 2 of this embodiment. This input screen 50 has an interface 51 for inputting drawing files. Drawing files can be input by dragging and dropping them. This screen displays that various file formats can be input. A user considering placing an order or making a quote can create an order record without worrying about the file format.

[0067] <Various Management Tables> Next, the management tables that the order receiving and placing system 1 manages and refers to in order to realize each function will be described with reference to Fig. 6. Each management table in Fig. 6 is stored in the storage device 13 of the order receiving and placing system 1.

[0068] FIG. 6A shows an example of a user table 610. Users who use the order placement and receipt system 1 are registered in advance in the user table 610, and the user table 610 is referenced by the login processing unit 36 ​​of the processing unit 11 to perform the login process (S41). The user table 610 manages a user ID 611 of a user who uses the order placement and receipt system 1, in association with a company ID 612 that identifies the user's company, and the user's password (PW). For example, column 614 manages a user ID U1, a company ID C1 for the company to which U1 belongs, and a password P1 for user U1, in association with each other. FIG. 6A shows a state in which users U1 and U2 belong to the same company.

[0069] FIG. 6B shows an example of a folder table. The folder table 620 manages folders for storing data for each user, in association with host information 623 indicating the creator of the data in the folder. When a user registered in the user table 610 logs in, the folder creation unit 31 acquires the user ID, assigns a folder ID 621 to the acquired user ID, flags the host information 623, and stores the information in the folder table. For example, row 624 of the folder table 620 indicates that a folder with folder ID F1 is assigned to user U1 as the host. Row 625 indicates that user U2 has been invited to folder F1 assigned to user U1. Although user U2 is not the user who stored the data in folder F1, he or she can view and partially edit the data stored in folder F1. By adding information identifying the user as either a purchaser or a contractor to the user ID, the same folder can be shared between the purchaser and the contractor.

[0070] 6C shows an example of a record table 630. In the record table 630, a record ID 631 identifying each record created by the record creation unit 34 is associated with a folder ID 632, product identification information (e.g., drawing number) 633 included in the image file, a product name 634, a status 635, and the like, and each row is managed as a record. The record IDs R1, R2, R3, and R8 indicate that the same folder F1 is used, and that drawing files and chat room data related to the record IDs R1, R2, R3, and R8 are stored in the folder F1. When the record creation unit 34 creates a record from each page of the input image file, it adds the record ID identifying the created record to the record table and stores it together with other information constituting the record, such as the folder ID and drawing number corresponding to the record ID, to form a single record.

[0071] The record table 630 is controlled by the processing unit 11 (display processing unit 352) and is displayed on the display unit of the IO device 14.

[0072] FIG. 6D shows an example of intermediate table 1. Intermediate table 1 manages the correspondence between records and drawing files. A record ID 641 that identifies a record is associated with a drawing ID 642 that identifies the drawing file. Rows 643 and 644 of intermediate table 1 indicate that two drawing files with drawing IDs Z1 and Z2 are associated with record ID R1. Z2 is a drawing file whose contents have been updated from Z1. Row 645 indicates that the drawing ID of Z3 is associated with record R2, and row 646 indicates that a mirror copy of the same drawing file as record R3 is managed as a separate record. When the record creation unit 34 creates a record from a drawing file, it associates the created record ID with a drawing ID that identifies the drawing file that is the basis of the record, and stores the intermediate table 1 in the storage unit 13.

[0073] FIG. 6E shows an example of intermediate table 2. Intermediate table 2 manages the correspondence between records and chat rooms. A chat room ID 652, which specifies a chat room, corresponds to a record ID 651, which identifies a record. Row 653 of intermediate table 2 shows that one chat room ID (T1) corresponds to record ID R1. The same chat room T2 corresponds to each record in rows 654 and 655. Record R3 is a mirror of record R2, and since the original drawing file is the same, this allows the purchaser of each record to refer to a common chat room, which also avoids duplicate questions and answers.

[0074] Records R1, R2, R3, and R8 are created by the same user U1 and stored in the same folder F1 (see Figure 6C). Therefore, drawings Z1, Z2, Z3, and Z8 (see Figure 6D) and chat rooms T1, T2, T3, and T7 are also stored in the same folder F1. This makes it easy to implement access restrictions that prevent other users from accessing drawings and chat rooms related to records created by user U1.

[0075] FIG. 6F shows an example of intermediate table 3. Intermediate table 3 manages the correspondence between talk rooms and messages. A talk room ID 661 that identifies a talk room is associated with a message ID 662 that specifies the content of a message posted in that talk room. Row 663 of intermediate table 3 indicates that a message ID of M1 is associated with a talk room ID of T1. When a message is posted to a talk room, the talk room creation unit 351 associates the talk room ID with the message ID and stores them in intermediate table 3.

[0076] 6G shows an example of a drawing table 670. The drawing table 670 manages a drawing ID 671 that identifies a drawing file and a file path 672 that indicates the storage location of the drawing file, in association with each other. The file receiving unit 32 stores the drawing ID that identifies the drawing file and the file path that is the storage location of the drawing file in association with each other in the intermediate table 3.

[0077] FIG. 6H shows an example of a message table 680. The message table 680 manages a message ID 681, a user ID 682, and a message content 683 in association with each other. A user ID 682 that identifies a user and a message content 683 are associated with a message ID 681 that identifies a message. In row 684 of the message table 680, a message "U2, what kind of surface treatment would you like?" by a user U1 is associated with a message ID of M1. User U1 has posted messages M1 and M3. The talk room creation unit 351 receives the user ID 682 of the logged-in user from the folder creation unit 31, and stores the message ID 681 and message content 683 of the message posted by the user in association with each other in the message table 680.

[0078] 7A shows an example of a record screen for user U2. User U2 is one of the orderers, and the display processing unit 352 displays data related to records R4-R7, which were created in the record creation unit 34 according to the drawing file entered by user U2, received from the order placement and receipt system 1.

[0079] The Record screen has check boxes for selecting records, and by checking the check box, the record is selected, and by pressing the Delete button, the selected record can be deleted. In addition, by checking the check boxes for multiple record IDs, the user can select which record IDs to prioritize, i.e., which record IDs to keep and which record IDs to delete, and then by pressing the Merge button, they can be merged.

[0080] When duplicating a record displayed on the record screen of user U2, the query processing unit 35 also duplicates the chat rooms and drawing files associated with the duplicated record. The chat rooms IDs T3-T6 (see FIG. 6E) and drawings Z4-Z7 (see FIG. 6D) associated with records R4-R7 are duplicated. That is, the data structure is such that, based on the record ID in record table 630, the drawing ID is associated with intermediate table 1, the record ID is associated with intermediate table 2, the message is associated with intermediate table 3, the file path indicating the storage location of the drawing is associated with drawing table 670, and the chat room message content is associated with message table 680. Therefore, even if the original record is duplicated or moved, the duplication and movement operations can be performed while maintaining the other data structures, and data related to the record can be easily shared and modified among related parties.

[0081] FIG. 7B shows an example of a record screen for user U1. User U1 is also one of the purchasers, and the display processing unit 352 receives and displays data from the order-entering system 1 about records R1-R3, and R8 created in accordance with the drawing file entered by user U1 among the records created by the record creation unit 34. As shown in FIGS. 7A and 7B, each user can, in principle, view and edit only their own records. In other words, the display processing unit 352 controls the transmission of data about records created from the entered drawing file to the purchaser who entered the drawing file that served as the basis for record creation among the records created by the record creation unit 34.

[0082] Since drawings and chat rooms related to records created by the same user U1 are basically stored in the same folder by the record creation unit 34, if the order placement and purchase system 1 does not provide information about the folder to other users, access restrictions can be easily implemented to prevent other users from accessing drawings and chat rooms related to records created by user U1.

[0083] FIG. 8A shows an example of a query screen for user U1. On U1's query screen, a drawing with a drawing ID of Z2 is selected and displayed large. Drawings Z3 and Z8 are thumbnail images of other drawings stored in the folder that stores the drawing Z2, and T1 is a chat room. Drawings and chat rooms related to records created by user U1 are generally stored in the same folder. In FIG. 8A, the tabs Rev1 (Z1) and Rev2 are displayed next to drawing Z2, indicating that drawing Z2 is an updated version of drawing Z1. In this way, if the additional drawing file (Z2) updates an already stored drawing file (Z1), a query screen is generated indicating that the original drawing (Z1) has been updated. By clicking the "Add" button on the query screen, user U1 can instruct the record creation unit 34 to associate the additional drawing file (Z2) with his or her own record R1 and store it in the storage unit 13.

[0084] When user U1 wants to share the drawing file or chat room contents corresponding to the record with user U2, he / she designates user U2 and presses the invitation button displayed on this inquiry screen, and an invitation email is sent to user U2 by the inquiry processing unit 35. Note that user U1 and user U2 are both orderers (e.g., belonging to the company that places the order) who use the ordering terminal 2. Details of the process for sending the invitation email will be described later.

[0085] Figure 8B shows an example of an inquiry screen for user U2. On U2's inquiry screen, a drawing with drawing ID Z4 is selected and displayed large. Drawings Z5-7 are thumbnail images of other drawings stored in the same folder as drawing Z4, and T3 is a chat room. Drawings and chat rooms related to records created by user U1 may be stored in a single folder, or may be stored in folders created individually for each project, etc. User U2 receives an invitation to the inquiry screen from user U1 in this state.

[0086] FIG. 8C shows an example of an invitation-based inquiry screen for user U2. U2's invitation-based inquiry screen displays the same content as the inquiry screen of the inviter, U1. This allows U2 to view and edit the drawing files and chat rooms related to the records displayed on U1's inquiry screen. When U1 invites U2 via the inquiry screen, the estimate receiving unit 353 creates a new entry in the folder table 620 and stores the shared folder and the invited user in association with each other. Row 625 in FIG. 6B is stored as a state in which folder F1 has been shared with U2 by U1. Note that the flag in host information 623 is not set in this newly created entry (row 625), and U2 is managed as the inviter, not the host, of folder F1.

[0087] 8A and 8B, the query processing unit 35 generates a query screen for the record created by each user. Then, invitations to the talk room via the query screen are limited to the user who created the record. Upon receiving an invitation request from the ordering terminal 2, the query processing unit 35 references the folder table 620 and confirms whether the user who made the invitation request is the host of the folder that stores information about the record for which the invitation request is made.

[0088] From the invitation inquiry screen of user U2, user U2 can view the drawings and chat room contents stored in the folder assigned to user U1. In addition, by pressing the "Add" button on the invitation inquiry screen, user U2 can cause the record creation unit 34 to associate an additional drawing file (Z2) with record R1 of other user U1 and store it in the storage unit 13. However, by referring to the folder table 620, the inquiry processing unit 35 imposes a restriction that prohibits placing an order for the record.

[0089] When an item managed as a record, such as the product name or material, posted in a chat room is entered, the inquiry processing unit 35 can automatically reflect the information in the record table by sending it to the record creation unit. For example, when a message is entered in a chat room in a predetermined format pre-stored in the storage unit 13, such as "Material: ●●," the inquiry processing unit 35 can detect the predetermined format and send the extracted information to the record creation unit.

[0090] When users U1 and U2 jointly place an order using the invitation inquiry screen, they can share a chat room displaying the drawing contents, questions, and answers, thereby improving work efficiency. Also, since user U2 is not allowed to access the record table, it is possible to prevent erroneous orders from being placed by someone without ordering authority. <Detailed Processing Flow> Next, the details of each process in the overall processing flow shown in Figure 4 will be explained.

[0091] <Folder Creation> FIG. 9 is a process flow showing details of the folder creation process S44 in FIG.

[0092] (S441) When a user logs in and acquires a user ID from the logged-in user (S43), folder creation unit 31 of processing unit 11 refers to folder table 620 and determines whether a folder corresponding to the user ID of the logged-in user has been assigned (S441). At this time, even if a folder exists, if there is no host flag in host information 623 of folder table 620, it is determined that the folder does not exist. If the folder exists, proceed to step S443; if not, proceed to step S442.

[0093] (S442) If the result of the determination in step S441 is that the folder does not exist, the folder creation unit creates a new folder to be assigned to the logged-in user, and stores the folder ID and user ID in association with each other in the folder table 620. At this time, a host flag is stored in the host information 623 of the folder table 620.

[0094] (S443) If the result of the determination in step S441 is that a folder already exists and a host flag exists in the host information, the folder creation unit selects a folder associated with the user ID of the logged-in user.

[0095] (S444) Furthermore, if the user ID of the logged-in user exists in the folder table 620 but there is no host information, the logged-in user is a guest, so a new folder is created to be assigned to the logged-in user, and the folder ID and user ID are stored in association with each other in the folder table 620.

[0096] (S445) The folder creation unit 31 finalizes the allocation of the folder to the logged-in user.

[0097] Through the folder creation process, the user ID, folder ID, and host information are stored in association with each other in folder table 620 of FIG. 6B.

[0098] <File Reception> FIG. 10 is a process flow showing details of the file reception process S45 in FIG.

[0099] (S451) The file receiving unit 32 of the processing unit 11 receives the order When a drawing file input by a user to the ordering terminal 2 is received via the network, the file extension of the drawing file is extracted to determine the file type of the drawing file. This process is executed by the file type determination unit 321 of the file receiving unit 32.

[0100] (S452) File type determination unit 321 determines whether the drawing file is an image file. This process can be performed based on the extension of the extracted drawing file. For example, if the drawing file has an extension of PDF, JPEG, GIF, or BMP, it is determined to be an image data file, and if it has an extension of any other format, such as DXF, DWG, STEP, IGES, or SAT, it is determined to be a CAD data file. If it is not an image file, the process proceeds to step S453; if it is an image file, the process proceeds to step S455.

[0101] (S453) If it is determined in step S452 that the drawing file is not an image file, the image generation unit 322 of the file receiving unit 32 generates an image file from the CAD data. The CAD data can be visualized using existing means. For example, if the CAD data is 3D data, an image projected from a certain direction can be used as image data.

[0102] (S454) After the CAD data is visualized, the visualized data and the CAD data are stored in the folder created in step 44 and assigned to the user.

[0103] (S455) If it is determined in step S452 that the drawing file is an image file, the file receiving unit 32 stores the image file in the folder created in step S44 and assigned to the user.

[0104] When the file receiving unit 32 acquires an image file corresponding to the input drawing file, it stores the image file in a folder assigned to the user and sends the image file data to the image processing unit 33 .

[0105] (S457) The file receiving unit 32 determines whether there are any unprocessed drawing files, and if there are, returns to step S451 and performs the same processes as steps S451 to S456. If there are no unprocessed drawing files, the process ends.

[0106] In this way, even if the drawing file is a CAD file other than an image file, the order receiving and placing system 1 of this embodiment can process it.

[0107] <Image Processing> FIG. 11 is a processing flow showing details of the image processing S46 in FIG.

[0108] (S461) The page break determination unit 331 of the image processing unit 33 determines the page breaks of the image file sent from the file receiving unit 32. This allows the image file to be processed as an image for each page.

[0109] (S462) Character detection unit 332 of image processing unit 33 extracts characters from the image and detects their coordinates. This process may be performed using, for example, an existing OCR function.

[0110] (S463) Word recognition unit 333 of image processing unit 33 recognizes words from the characters detected by character detection unit 332. This process may be performed using, for example, an existing OCR function or a word recognition function used together with OCR.

[0111] (S464) The identification information determination unit 334 of the image processing unit 33 stores the words recognized for each page in the record creation unit .

[0112] <Record Creation> The record creation unit 34 creates a record for each piece of image data (individual image file) separated by page by the image processing unit 33, and stores the record ID of the record table 630 and the folder ID assigned to the user. The record creation unit 34 stores the words read for each page sent from the image processing unit 33 in association with the record in the folder assigned to the record.

[0113] <Editing Individual Records> FIG. 12 is a process flow showing details of editing individual records S48 in FIG.

[0114] (S481) The user selects a record using check button 638 in record table 630, and record creation unit 34 receives a request for an individual record edit screen. The individual record edit screen is the screen shown in FIG. 13A, and includes a drawing area slightly to the left of the center that displays the drawing of the selected record, and an input area in the upper right that displays basic information such as the item name and drawing number, which are items of the selected record, and an input area in the lower right that displays quotation information such as quantity, request comments, and quotation amount, among other quotation conditions. Note that FIG. 13A shows the individual record edit screen in normal mode.

[0115] (S482) The record creation unit 34 retrieves the drawing, basic information, and estimate information from the storage unit based on the selected record. The drawing ID can be identified by referencing intermediate table 1 from the selected record ID, and the drawing contents can be read by referencing drawing table 670 from the identified drawing ID. The basic information and estimate information are read if there is information stored in association with the record ID; otherwise, they become null information. Note that while record table 630 lists only the status as estimate information, the status is assumed to include the quantity, request comments, estimated amount, etc. However, columns for managing the quantity, request comments, estimated amount, etc. as information other than the status may be created in record table 630.

[0116] (S483) The processing unit 11 (display processing unit 352) receives the drawing, basic information, and estimate information read by the record creation unit 34 in step S482, generates an individual record editing screen (see FIG. 13A), and transmits it to the user's terminal. If the user is an orderer, it is transmitted to the ordering terminal 2. The inquiry processing unit 35 displays the individual image file corresponding to the specified record in the drawing area of ​​the individual record editing screen (see FIG. 13A).

[0117] (S484) The processing unit 11 (image processing unit 33) determines whether the mode is a character extraction mode for detecting characters, and if it is a character extraction mode, the process proceeds to S485.

[0118] (S485) The query processing unit 35 generates an individual record editing screen in which the image processing unit 33 highlights the area where the characters have been extracted, and sends this to the ordering terminal 2 used by the user. The individual record editing screen in which the area where the characters have been extracted is the screen shown in FIG. 13B. In FIG. 13B, the areas where the characters have been extracted, such as the dimensions 131 of the drawing, the approver 132 in the title box, and the drawing number 133, are surrounded by a rectangle and displayed in a highlighted manner. FIG. 13B shows the input completion mode of the individual record editing screen.

[0119] (S486) The processing unit 11 (display processing unit 352) selects the highlighted area and generates a screen for the user to input and edit the items in the selected area. Figure 13C shows the screen for editing. In Figure 13C, the character string "ABC-123" 134 adjacent to the drawing number 133 is selected. "ABC-123" is information indicating the drawing number of the drawing on this page. Figure 13C shows the input completion mode of the individual record editing screen.

[0120] When the query processor 35 receives a designation to mask a word in the drawing area, it executes masking on that word, as shown in Figure 13D. Figure 13D shows the mask mode on the individual record editing screen. This can assist in masking words that you do not want to reveal when placing an order, such as personal information. Instead of overwriting the data of the original image, a separate image after masking is created, and the mask is deleted later.

[0121] The query processing unit 35 generates a masked image file of the individual record editing screen including the drawing area of ​​the masked word. This masked image file is stored in the storage unit (a folder assigned to the user who input the drawing file) in association with the corresponding record by the record creation unit 34. Since the masked image file is associated with the record in this way, when placing an order, the query processing unit 35 can use the masked image file to make an order request to the contractor terminal 3. Because an order can be placed using a masked image file, the contractor does not need to prepare an image file in which information that the contractor does not want to see is masked when placing an order.

[0122] In addition, you can make inquiries (talk) using drawing files that have been masked on the individual record editing screen, so you can confirm the validity of the parts that should be masked by interacting with staff from other departments or operators on the inquiry screen.

[0123] Because it is inconvenient to switch modes to check the masked areas, the masked image continues to be displayed even when switching to normal mode in FIG. 13A or input completion mode in FIG. 13B after masking. When displaying the individual record editing screen in normal mode or input completion mode, the presence or absence of mask information can be determined, and if present, the masked image can be displayed. Also, on the user's screen, the masked areas can be made semi-transparent so that the words are not completely hidden. This allows the user to see which words were masked even when looking back at the screen later, eliminating the need to remove the mask to check what the hidden words were.

[0124] (S487) The record creation unit 34 stores the characters of the selected area in the field of the record table corresponding to the selected area. FIG. 13C shows that the character string "ABC-123" of the selected area 134 is reflected as the drawing number "ABC-123" of the basic information. By assuming that the information "ABC-123" 134 adjacent to the drawing number 133, which is a character string extracted from the image file, is drawing number information, when the area 134 is selected, "ABC-123" can be reflected in the drawing number of the basic information. The information reflected on the individual record editing screen is entered into the corresponding information in the record table 630.

[0125] The memory unit 13 stores a plurality of reference words associated with any of the input areas. For example, "drawing number," "planning number," and "Drawing No." are stored as reference words in the memory unit 13. When the query processing unit 35 receives the designation of an input area on the individual record editing screen, it selects a word associated with the input area from the plurality of reference words and controls the display unit to highlight the character string adjacent to the selected word.

[0126] (S489) The record creation unit 34 determines whether the user has selected other input fields, such as the product name of the basic information. If so, the process returns to step S486 and repeats the same process. If not, the process ends.

[0127] In this way, the records created for each page of the image file can be automatically entered into the record table while checking the information in the input fields that make up the record. The words extracted for each page sent from the image processing unit 33 to the record creation unit 34 in step S464 can be automatically entered into the corresponding fields of basic information and quotation information, and the correct input can be confirmed and edited using an individual record edit screen request (see FIG. 13). <Receiving a request for quotation and receiving an order request> Next, the process of receiving a request for quotation S49 and the process of receiving an order request S51 will be explained. As both processes have much in common, they will be explained together in FIG. 14.

[0128] First, the request for quotation will be described.

[0129] (S481) The quotation receiving unit 353 (processing unit 11 of the order receiving system 1) receives the quotation request. The quotation requester selects a record stored in the record table sent from the order receiving system 1 to the order terminal 2 and sends the quotation request to the order receiving system 1. At this time, the order receiving system 1 sends to the order terminal 2 the record from the record table that corresponds to the folder assigned to the quotation requester (the record created by the quotation requester inputting the drawing file). The quotation requester displays the records sent to the order terminal 2 and prompts the requester to select the record for which a quotation is to be made. Step S481 can be understood to correspond to the act of adding shopping items to a card at a typical online shop and confirming the total payment amount.

[0130] (S482) The estimate receiving unit 353 updates the status of each item for which an estimate has been requested in the record table to "Estimate in progress."

[0131] Next, an order request will be described.

[0132] (S481) The order receiving unit 354 (order receiving system 1 The processing unit 11) receives the order request. The orderer selects a record stored in the record table sent from the order system 1 to the order terminal 2, and the order request is received by the order system 1. At this time, the order system 1 sends to the order terminal 2 the record in the record table that corresponds to the folder assigned to the orderer. The orderer displays the records sent to the order terminal 2, and prompts the orderer to select the record for which to place the order. Step S481 can be understood to correspond to the act of putting shopping items on a card at a typical online shop and purchasing them all at once.

[0133] (S482) The order receiving unit 354 updates the status of each order request in the record table to "Ordered." If the authority to process estimates and orders is set for each user in the user table 610, estimate requests and order requests from users who do not have the authority to estimate or order can be rejected, preventing erroneous estimate requests and erroneous orders.

[0134] For example, if columns for quotation authority and ordering authority are provided in the user table 610 and set for each user, quotation authority and ordering authority will not be granted to users who belong to the company that issues quotation or orders but are users in the development department and not in the procurement department, and quotation requests and ordering requests from users who do not have quotation authority or ordering authority can be rejected.

[0135] <Inquiry Transmission and Reception> The process executed by the inquiry processing unit 35 to inquire about a record to be inquired about among a plurality of records created by inputting a drawing file will be described below.

[0136] Fig. 15 shows details of the inquiry process, and is a processing flow showing details of the inquiry reception process S50 in Fig. 4 which is executed by the inquiry processing unit 35. Fig. 16 shows an example of an inquiry screen created by the inquiry processing unit 35 and displayed on the display device of the order receiving and supplying system 1 (S501). A user making an inquiry about a record selects the record they wish to inquire about from the user's record table and sends a screen request to the order receiving and supplying system 1. If the inquirer is on the order placing side, the request is sent from the order placing terminal 2 to the order receiving and supplying system 1, and if the inquirer is on the order receiving party (supplier) side, the request is sent from the order receiving terminal 3 to the order receiving and supplying system 1.

[0137] By identifying the folder ID assigned to a user using the folder table 620 and extracting the record corresponding to that folder ID from the all record table, it is possible to identify the record for each user. The inquiry processing unit 35 of the order placement and receipt system 1 sends information on the records related to each user to the order terminal. If information that can identify whether the user is an orderer or a contractor is added to the user ID in the folder table 620, inquiries from the contractor side as well as inquiries from the orderer side will be possible. Below, an example will be explained in which an orderer makes an inquiry. For example, when the orderer selects a record to inquire about from the records related to the orderer displayed on the order terminal 2, the inquiry processing unit 35 generates an inquiry screen request and sends it to the order terminal 2.

[0138] (S502) When the query processing unit 35 receives a screen request, it references intermediate table 1 and intermediate table 2 to obtain the drawing ID and talk room ID corresponding to the selected record. It references drawing table 670 from the obtained drawing ID to obtain the drawing, and references intermediate table 3 and message table 680 from the talk room ID to obtain the content of the message written in the talk room.

[0139] (S503) The inquiry processing unit 35 creates a drawing as shown in FIG. 16 from the acquired drawing and chat room messages. FIG. 16 shows that drawing Z2 corresponding to the selected record, other drawings Z3 and Z8 in the folder in which drawing Z2 is saved, and the orderer chat room T1-1 and contractor chat room T1-2 related to the folder are displayed. These chat rooms T1-1 and contractor chat room T1-2 are managed as chat room IDs T1-1 and T1-2, respectively. The order placement and receipt system 1 conceals the contents of the contractor chat room from the contents of FIG. 16 and generates a drawing as shown in FIG. 8A with only the orderer chat room for the ordering terminal 2, and sends it to the ordering terminal 2. The orderer posts requests to the contractor, such as changes to delivery dates and drawings, in the chat room associated with the record.

[0140] (S504) The contractor who has received the request from the purchaser on the inquiry screen of the order receiving terminal 3 posts a reply message in the contractor's chat room. The reply message from the contractor is sent from the order receiving terminal 3 to the order receiving and placing system 1. If the time of receipt of the reply message is stored, the latest reply message can be displayed in an easy-to-understand manner.

[0141] (S505) The talk room creation unit 351 transmits a reply message notification from the contractor.

[0142] The above has been described regarding inquiries from purchasers, but inquiries from contractors can also be handled in the same way.

[0143] <Processing of sending invitation email> The processing executed by the inquiry processing unit to invite other users to the inquiry screen, which is another form of the inquiry processing in Fig. 4, will be described with reference to Fig. 17. The outline of the operation of inviting other users to the inquiry screen is as described in Figs. 8A-C.

[0144] (S5011) The inquiry processing unit 35 receives information that the invitation email button has been pressed. For example, when inviting user U2 to the inquiry screen of user U1, the user presses the invitation button displayed on the inquiry screen of U1 (see FIG. 8A), and receives the information.

[0145] (S5012) The inquiry processing unit 35 accepts input of the destination email address. In the example of FIG. 8A, the email address of U2 is input.

[0146] (S5013) The inquiry processing unit 35 receives an instruction to send an invitation email.

[0147] (S5014) When the inquiry processing unit 35 receives an instruction to send an invitation email, it generates a link (URL link) in the body of the invitation email, embedding the record ID corresponding to the drawing displayed in the drawing area of ​​the inquiry screen. For example, in Fig. 8A, a drawing with drawing ID Z2 is displayed in the drawing area, and a link is generated to reference a folder storing information on record R1 (see Fig. 6D) corresponding to Z2, and an invitation email is generated.

[0148] (S5015) The inquiry processing unit 35 sends the invitation email generated in step S5014 to the address entered in step S5012, for example, the email address of user U2.

[0149] <Processing for Receiving Invitation Email> Processing executed by the inquiry processing unit when an invitation to an inquiry screen is received from another user, which is another form of the inquiry processing in FIG. 4, will be described with reference to FIG.

[0150] (S5021) The inquiry processing unit 35 receives an access request for the link in the invitation email from the user who has received the invitation email.

[0151] (S5022) The query processing unit 35 determines whether the user who made the access request is currently logged in. If the user is not currently logged in, a login request is made (S5023), and if the user is currently logged in, the process proceeds to step S5024. This process is performed by the login processing unit 36, but may also be performed by the query processing unit 35.

[0152] (S5024) If the user who has made the access request is currently logged in, the processing unit 11 acquires the user ID. This process is performed by the login processing unit 36, but may also be performed by the inquiry processing unit 35.

[0153] (S5025) The query processing unit 35 determines whether the user who made the access request has access rights to the folder associated with the invited query screen. If the user does not have access rights, the process proceeds to step S5027. If the user has access rights, the process proceeds to step S5026. For example, in the example of Figures 8A-C, U2 is the user who received the invitation email and made an access request to the link in the invitation email body. The process determines whether U2 has the authority to access the folder associated with U1's query screen, i.e., the folder that stores U1's data. For example, this can be achieved by adding an additional column to the folder table 620 to store the user IDs that are permitted to access the folder IDs assigned to each user, and storing the user IDs. In Figure 6B, row 624 assigns folder ID (F1) to user U1. However, as shown in row 625, a folder ID (F1) may also be assigned to user U2.

[0154] (S5026) If the access right is not set for the user who made the access request, the inquiry processing unit 35 generates an access denial screen and sends it to the terminal of the user who made the access request. At the time when user U2 was invited by user U1, user U2 has the access right to folder F1, as shown in row 625 of Figure 6B. However, if it is later discovered that the invitation was a mistake or the invitation is no longer necessary, and user U1 deletes user U2's access right to folder F1, the process proceeds to step S5026.

[0155] (S5027) The query processing unit 35 acquires information about the drawing and the chat room of the record contained in the folder to which the record ID embedded in the link of the invitation email belongs. The folder to which the record ID belongs is identified by the record table 620. Other records stored in the same folder are also identified by the record table 620, and from the record ID embedded in the link and the other identified record IDs, the drawing ID can be identified by intermediate table 1, and the chat room ID can be acquired by intermediate table 2.

[0156] (S5028) The inquiry processing unit 35 generates an inquiry screen from the drawing and the talk room information acquired in step S5026, and transmits it to the terminal of the user who made the access request.

[0157] <Record Creation According to a Modified Example> FIG. 19 is a diagram showing another example of the overall processing flow of the present embodiment shown in FIG.

[0158] Steps S41 to S45, excluding steps S191 and S192, are the same as in Fig. 4, and steps S48 to S50 are the same as steps S49 to S51 in Fig. 4. Explanation of the same processes as in Fig. 4 will be omitted. The process in Fig. 19 realizes record creation for each drawing, such as for each product, as shown in Fig. 20.

[0159] FIG. 20 is a diagram showing an image of creating a record from one image file in this embodiment.

[0160] The left side of Figure 20 shows a case where one drawing file entered on the screen of Figure 5 contains six pages. Also, drawings for product AA, product AA, product BB, product CC, product DD, and product DD are drawn on each page in that order.

[0161] In this case, the order placement and purchase system 1 of this embodiment performs image processing S46 and record creation S47 for each page of the input drawing file, and creates record R1 for product AA, record R2 for product BB, record R3 for product CC, and record R4 for product DD.

[0162] On the other hand, the right side of Figure 20 shows a case where one drawing file entered on the screen of Figure 5 contains six pages. Also, drawings relating to product AA, product AA, product BB, product CC, product DD, and product AA are drawn on each page in that order.

[0163] In this case, the order placement and receipt system 1 of this embodiment performs image processing S46 and record creation S47 for each page of the input drawing file, and creates a record R1 for product AA, a record R2 for product BB, a record R3 for product CC, and a record R4 for product DD. In this case, even if there is a page on which product AA is drawn after the page for product DD, the records are all created together as one record R1 for product AA.

[0164] The contents of the functional blocks in FIG. 3 required to perform the processing in FIG. 19 will be explained again.

[0165] Image processing unit 33 receives the image file generated by the file receiving unit 32 and extracts words from the received image file for each page. Furthermore, the identification information determination unit 34 of the image processing unit 33 identifies the product's identification information. The image processing unit 33 includes a page break determination unit 331 that determines page breaks in the image file, a character detection unit 332 that detects characters written on each page of the image file, a word recognition unit 333 that recognizes words from the characters detected by the character detection unit 332, and an identification information determination unit 334 that reads identification information that identifies the drawing from the words recognized by the word recognition unit 333. The function of the image processing unit 33 to recognize characters and words from each page of the image file can be realized by using a general OCR function or a feature extraction function used for object detection.

[0166] In this embodiment, the identification information determination unit 334 of the image processing unit 33 executed by the processing unit 11 uses the drawing number (draft number - drawing number) identified by character recognition of each page of the image file. This is because the drawing number is information that identifies the drawing depicted in the drawing file. Furthermore, since the drawing number is also information that identifies the product depicted in the drawing file, the identification information may be treated as information that identifies both the drawing number and the product. Hereinafter, the drawing will be referred to as the product in the sense of identifying the drawing.

[0167] The record creation unit 34 creates one order record (hereinafter, sometimes simply referred to as a record) by collecting the same drawing, i.e., drawing files related to a product, from one or more drawing files received by the file receiving unit 32. The record creation unit 34 is realized by the CPU 11 executing a program stored in the memory 12.

[0168] The description format of one drawing file targeted by this embodiment is basically one in which one product is described per page, but one drawing file may contain multiple pages. Also, drawings of the same product may be described across multiple pages, or drawings of the same product may be described on some pages and drawings of other products on other pages. Also, while one product is generally described on one page of a drawing file, there are cases in which multiple products are described on one page.

[0169] In addition, one product may be described using multiple drawing files.

[0170] Furthermore, the formats of multiple drawing files may differ from image files such as PDF, JPEG, GIF, and BMP, or from CAD data in DXF, DWG, STEP, IGES, and SAT formats.

[0171] In this way, in the ordering system 1, the record creation unit 34 creates one record for the same product from various drawing description formats and drawing files with different formats. When placing an order, you can select the created record to place an order for each product.

[0172] The record created for each product by the record creating unit 34 may manage information read from the image file by the image processing unit 33 and drawing files in association with each product.

[0173] Returning to FIG. 19, the process of the modified example will be described.

[0174] A folder for storing data is assigned to the logged-in user, drawing files are received, and image files are created, and then the process of step S191 is executed.

[0175] (S191) The image processing unit 33 of the processing unit 11 performs image processing on the image file obtained from the drawing file received by the file receiving unit, and identifies and acquires the drawing and the identification information of the product described on the drawing from the drawing file. Details of the processing of this image processing unit 33 will be described later using FIG. 21.

[0176] (S192) Next, the record creation unit 34 creates records for ordering based on the identification information specified by the image processing unit 33. As shown in Fig. 6C, the order records (record table) are created based on the identification information, with records that identify each record corresponding to information such as a folder ID, drawing number (one piece of identification information), product name, and status, and are stored as a database in the storage device 13. Details of the processing by the record creation unit 34 of the processing unit 11 will be described later using Fig. 23.

[0177] The above processing has explained the outline of the basic processing of the order placement and receipt system 1, and different processing may be executed in each step. Also, additional processing other than the steps shown in FIG. 19 may be executed.

[0178] <Detailed Processing Flow> Next, details of the processing in the overall processing flow shown in FIG. 19 that differs from that shown in FIG. 4 will be described.

[0179] <Image Processing> FIG. 21 is a processing flow showing details of the image processing S191 in FIG.

[0180] (S1911) The page break determination unit 331 of the image processing unit 33 determines the page breaks of the image file sent from the file receiving unit 32. This allows the image file to be processed as an image for each page.

[0181] (S1912) Character detection unit 332 of image processing unit 33 extracts characters from the image and detects their coordinates. This process may be performed using, for example, an existing OCR function.

[0182] (S1913) Word recognition unit 333 of image processing unit 33 recognizes words from the characters detected by character detection unit 332. This process may be performed using, for example, an existing OCR function or a word recognition function used together with OCR.

[0183] (S1914) The identification information determination unit 334 of the image processing unit 33 determines the identification information of the product from the words recognized by the word recognition unit 333. Details of the identification information determination process will be described with reference to FIG.

[0184] (S1915) The image processing unit 33 determines whether there are any unprocessed pages, and if there are, performs the same processing as steps S1911 to S1914 for each page. When all pages have been processed, the process proceeds to step S1916.

[0185] (S1916) The image processing unit 33 sends the determined identification information to the record creation unit 34. If the identification information cannot be determined from each page, the image processing unit 33 assigns temporary identification information to each page for which identification information could not be determined and sends the pages to the record creation unit 34.

[0186] Basically, there is one piece of identification information per page, but the processing unit 11 of this embodiment can handle various description formats, such as a case where one product is described on one page, a case where one product is described across multiple pages, or a case where multiple products are described on one page.

[0187] <Determination of Identification Information> FIG. 22 is a process flow showing details of the determination of identification information S1914 in FIG.

[0188] (S19141) The identification information determination unit 334 of the image processing unit 33 reads out a determination dictionary stored in advance in the storage device 13. The determination dictionary stores characters that are typically written on drawings and indicate items that can identify the product depicted on the drawings. For example, these include the drawing number (drawing number), product name, creator, creation date, mirror, and page number.

[0189] (S19142) Next, the identification information determination unit 334 compares the word recognized by the word recognition unit 333 in step S1913 with the dictionary read out in step S19141. The recognized word is compared with items (drawing number (drawing number), product name, etc.) that can identify the product stored in the determination dictionary, and the reading confidence level is calculated. The reading confidence level is the degree of match between the recognized word being compared and a word in the read dictionary. The higher the degree of match, the higher the reading confidence level is processed. The recognized word is compared, for example, with all the words in the dictionary, and the degree of match with the word in the dictionary that has the highest degree of match is added as color information.

[0190] (S19143) Next, the identification information determination unit 334 extracts words whose confidence level is equal to or greater than a predetermined threshold value in order to identify the product depicted in the drawing of the image file.

[0191] In this embodiment, drawing numbers and product names that are always included in drawings are registered in a dictionary for determination, and drawing numbers and product names are extracted from recognized words.

[0192] (S19144) If there is no identification information with a reading confidence level equal to or greater than the predetermined threshold, it is determined that the identification information cannot be read, and the process ends. In this case, the individual record editing process S48 shown in Figure 4 may be executed. If it is determined that the identification information cannot be read, the user can input the recognized word while checking it.

[0193] (S19145) The identification information determination unit 334 determines whether the words extracted in step S19143 are identification information itself. That is, the drawing number and product name themselves are not identification information, but identification information is written in their vicinity. The "page number" of the drawing, "mirror," "multiple component information," and "presence or absence of specified features" in the drawing are themselves identification information. The drawing number, product name, and drawing number (draft number or product name) written in the title column of the drawing are relevant, and "mirror" refers to a description indicating that the product is a mirror product of the product depicted in the drawing. "Multiple product information" refers to information indicating that different products are drawn on the same page, such as when multiple product name columns are provided. "Presence or absence of specified features" refers to a description indicating that both products with specified features (structure, shape), such as screw holes, and products without such features exist.

[0194] In determining the identification information, the drawing number is first used.

[0195] Even if the drawing number is the same, if the product name is different, it is a drawing depicting a different product, so the product name will be used as identification information. However, even if the drawing number is the same but the product name column is different, if the page numbers are 1 / 2 and 2 / 2, for example, even if the product names are different, such as the "seat" and "legs" of a chair, they will be determined to be the same product with the same page number notation, because they represent one product, a chair.

[0196] (S19146) The identification information determination unit 334 identifies the extracted words as identification information. This includes descriptions such as "number of pages," "mirror," "multiple product information," and "presence or absence of specified features." In this case, color-coding information may be added to the extracted words depending on the reading confidence (matching degree) calculated in step S19142. The difference in color can alert the user to check words with a low degree of match.

[0197] (S19147) The identification information determination unit 334 identifies a character string near the extracted word as identification information. For example, if the extracted word is "drawing number," the character string indicating the drawing number, such as "SD12," written nearby is identified as identification information. In this case, color-coding information may be added to the extracted word depending on the reading confidence (matching degree) calculated in step S19142. This can alert the user to the need for confirmation. The inventors have found that drawing numbers are often assigned to individual products. Therefore, this is based on the finding that using information related to drawing numbers as identification information is efficient for creating records for each product.

[0198] (S19148) Identification information determination unit 334 determines whether any other words have been extracted, and if any words have been extracted, returns to step S19145 and performs the same process. If no words have been extracted, the process ends.

[0199] <Record Creation> Figure 23 is a processing flow showing details of the record creation process S192 in Figure 19 executed by the record creation unit 34. The record creation unit 34 receives an image file from the file receiving unit 32 or the image processing unit 33. The record creation unit 34 also receives from the image processing unit 33 each page of the image file, as well as characters and identification information read from each page.

[0200] (S1921) When a drawing file is received by file receiving unit 32 and the image file that has been subjected to image processing by image processing unit 33 is received by record creating unit 34 from image processing unit 33, record creating unit 34 determines whether the image file is made up of multiple pages. If the image file is made up of multiple pages, the process proceeds to step S1925; if it is made up of one page, the process proceeds to step S1922.

[0201] (S1922) If the image file is one page, the record creation unit 34 creates multiple records based on the identification information of the page. It is determined whether a product is included and the number of products can be identified. If multiple products are included and the number of products can be identified, the process proceeds to step S1923; if not, the process proceeds to step S1924. For example, if the page contains multiple pieces of identification information, multiple products are drawn in the image, and even if the drawing numbers are the same, if the identification information "mirror" is extracted from the drawing, they are treated as separate products. In this way, it is determined whether multiple products are drawn in the drawing and the number of products can be identified.

[0202] (S1923) If multiple products are included on one page and the number of products can be identified in step S1922, the record creation unit 34 creates records for the number of products. Specifically, it creates entries (rows) in the record table 630 for the number of products.

[0203] The record creating unit 34 then associates the image files to be processed with the created records. The drawing files associated with the records may be only image files, or may be both image files and CAD files.

[0204] To associate a record with an image file, the record creation unit 34 inputs the value of the folder ID in the record table 630. As a result, the record table 630 stores the relationship between the record ID and the folder ID.

[0205] The folder ID is information that identifies the folder that is the data storage location of the user to whom the folder is assigned. The record creation unit 34 registers the drawing ID in the record ID created in the intermediate table 1 for the record to be processed, and registers a file path including the folder ID for the drawing ID in the drawing table 670, thereby associating and registering the record and the drawing file.

[0206] (S1924) If the image file does not contain multiple products on one page based on the identification information, or if the number of products cannot be determined from the identification information, the record creation unit 34 creates one record corresponding to the page. Specifically, it creates one entry (row) in the record table 630. The record creation unit 34 then associates the image file to be processed with the created record. This association can be performed in the same manner as in step S1923.

[0207] (S1925) If the image file has multiple pages, the record creation unit 34 determines whether identification information has been identified from each of the multiple pages.

[0208] If the identification information can be identified from the target page, the process proceeds to step S1926; if not, the process proceeds to step S1927.

[0209] (S1926) The record creation unit 34 determines whether the identification information identified from each page has common identification information.

[0210] For example, the record creation unit 34, having acquired identification information including the drawing numbers of all pages (10 pages), makes a determination in order starting from page 1. First, if the drawing number of page 1 matches the drawing numbers of other pages (for example, pages 2 and 6), the process proceeds to S1931 (= creating an individual file that integrates pages 1, 2, and 6). If there are pages remaining that have not been determined or integrated (returned from S1935), the record creation unit 34 makes a determination based on the drawing number of page 3. In other words, the record creation unit 34 determines whether a page with the same drawing number as page 3 exists among the remaining pages (i.e., pages 4 to 5, and pages 7 to 10).

[0211] As another example, even if the drawing numbers are different on each page, if part of the character string in the drawing number is common (for example, the "1234" part is common in "1234-100" and "1234-101") and a word indicating the page number is read on each page (for example, "1 / 2" or "2 / 2" indicating the first or second page of a total of two pages), it may also be determined to be the same identification information.

[0212] (S1927) The record creation unit 34 creates individual files, each of which is a single file for each of the multiple pages. In this case, an entry for one file path 672 is added to the drawing table 670 for one drawing ID.

[0213] (S1928) The record creation unit 34 determines whether multiple products are included and the number of products can be identified based on the multiple pieces of identification information in the image of the created individual file. If multiple products are included and the number of products can be identified, the process proceeds to step S1929; if not, the process proceeds to step S1930. This process is similar to step S1922, although the processing target is different.

[0214] (S1929) If multiple products are included and the number of products can be identified in step S1928, record creation unit 34 creates records for the number of products. Specifically, record table 630 creates an entry (row) for each product name.

[0215] The record creating unit 34 then associates the image files to be processed with the created records. This process is similar to step S1923, although the processing target is different.

[0216] (S1930) If the identification information of the image information of the individual file does not include multiple products or the number of products cannot be identified, the record creation unit 34 creates one record and associates the individual file created in step S1927 with the created record. To save the new record created, a new entry is created in the record table 630 and intermediate table 1. The intermediate table 1 stores a drawing ID that identifies the individual file.

[0217] (S1931) If it is determined in step S1926 that multiple pages share a common identification number, the record creation unit 34 creates a single file (individual file) that brings together multiple pages with the same identification information. In this case, multiple file path 672 entries are added to the drawing table 670 for one drawing ID.

[0218] (S1932) When the record creation unit 34 creates individual files from each page having a common drawing number, it determines whether multiple products are included and the number of products can be identified based on the multiple pieces of identification information in the image of the individual file. If multiple products are included and the number of products can be identified, the process proceeds to step S1933; if not, the process proceeds to step S1934. This process is similar to step S1922, although the processing target is different.

[0219] (S1933) The record creation unit 34 creates as many records as there are products, and associates individual files having the same drawing number with the multiple records.

[0220] This association can be achieved by creating entries (record IDs) in the record table 630 for the number of product names, and inputting the same drawing ID into the multiple record IDs created in the intermediate table 1.

[0221] (S1934) If the identification information of the image information of the individual file does not include multiple products or the number of products cannot be identified, the record creation unit 34 creates a new record for the individual file and associates it with the individual file created in step S1931. To associate the record with the individual file, a new entry (record ID) is created in the record table 630 and the drawing ID is stored in the record ID created in the intermediate table 1.

[0222] (S1935) The record creation unit 34 checks whether there are other pages, and if there are, returns to step S1925 and executes the same process, steps S1925-S1933, for the unprocessed pages.

[0223] (S1936) Record creating unit 34 determines whether the received drawing file is CAD data or not. If it is CAD data, the process proceeds to step S1937, and if it is not CAD data, the process proceeds to step S1938.

[0224] (S1937) The record creation unit 34 also associates the CAD data with the created record (the new entry added to the record table). This association can be achieved by adding a column to the drawing table 670 that stores the file path where the CAD file is stored, in addition to the file path 672 that is the storage destination of the image file.

[0225] (S1938) The record creation unit 34 creates a list display screen for the created record table. The list display screen for the record table includes, for example, as shown in Fig. 6C, the record ID, folder ID, drawing number, and product name, as well as the status of each record, indicating whether it is in the estimate state or has been ordered.

[0226] <Sending and Receiving Inquiries> As with FIG. 4, it is possible to perform inquiry processing on the records created in FIG. 19 as well, as shown in FIGS.

[0227] <Additional Drawings> Figure 24 shows the processing flow of the processing unit 11 of the order-taking and ordering system 1 when additional drawings are input from the order-taking terminal 2 and sent to the order-taking and ordering system 1 after record creation S47 in Figure 4 or after record creation S47 in Figure 19.

[0228] (S1001) When the processing unit 11 receives a request to add a drawing file from the ordering terminal 2, it determines whether the request contains information specifying an already created record. If no record is specified, the processing unit 11 proceeds to step S1002, and if a record is specified, the processing unit 11 proceeds to step S1007.

[0229] (S1002) If no record is specified, the processing unit 11 performs file reception processing. Note that the details of this processing are the same as step S45 in FIG. 4, so a description thereof will be omitted.

[0230] (S1003) The processing unit 11 performs image processing. Note that the details of this processing are the same as those of step S46 in FIG. 4, and therefore will not be described here.

[0231] (S1004) The processing unit 11 determines whether the identification information of the added drawing file as a result of the image processing in step S1003 is identical to the identification information stored in an existing record in the record table 630. If they are identical, the process proceeds to step S1005, and if they are not identical, the process proceeds to step S1006. The determination of whether they are identical in this step can be made in the same way as in step S19143, by determining whether the degree of match exceeds a predetermined threshold.

[0232] (S1005) The processing unit 11 overwrites the record of the drawing file of the existing record. Specifically, the drawing number 633, product name 634 in the record table 630, and the drawing ID information in the intermediate table 1 are overwritten, and information on the file path 672 of the additional drawing file is added to a blank row in the drawing table 670. If the additional drawing file (Z2) is to update the already stored drawing file (Z1), the query processing unit 35 generates a query screen that displays that the original drawing (Z1) has been updated.

[0233] (S1006) If the same identification information as the identification information of the added drawing file is not found in any existing record, a new record is added for the added drawing file. Note that the details of this process are the same as step S47 in Fig. 4 or step S47 in Fig. 19, so a detailed explanation will be omitted.

[0234] (S1007, S1008) If the request to add a drawing file specifies which existing record the drawing file is to be added to, the processing unit 11 determines the file type of the added drawing file. That is, it determines whether the added drawing is an image file. This determination is the same as the processing shown in S451 and S452 in FIG. 10, so details will be omitted.

[0235] (S1009) If the result of determination in step S1008 is that the added drawing file is an image file, the image file is added to the specified record and saved. This process is achieved by adding a drawing ID to the specified record in intermediate table 1. If the added drawing file (Z2) is to update an already stored drawing file (Z1), the query processing unit 35 generates a query screen that displays that the original drawing (Z1) has been updated.

[0236] (S1010) If the added drawing file is not an image file but a CAD file that stores CAD data, the processing unit 11 determines whether the CAD file is associated with the specified record. This determination is made by checking whether the drawing file for the record ID specified in the intermediate table 1 is associated with the CAD file. This can be done by obtaining the ID and checking whether the file path for the drawing ID obtained in the drawing table is a CAD file. If an existing CAD file exists, proceed to step S1011; if not, proceed to step S1012.

[0237] (S1011) The processing unit 11 overwrites the content of the CAD file associated with the record with the added CAD file. If the added drawing file (Z2) is to update the already stored drawing file (Z1), the query processing unit 35 generates a query screen that displays that the original drawing (Z1) has been updated.

[0238] (S1012) The processing unit 11 associates the added CAD file with the instructed record. This association is achieved by adding a drawing ID to the record specified in the intermediate table 1 and storing a file path corresponding to the drawing ID in the drawing table. If the added drawing file (Z2) is to update an already stored drawing file (Z1), the query processing unit 35 generates a query screen that displays that the original drawing (Z1) has been updated.

[0239] (S1013) The processing unit 11 checks whether there is an unprocessed additional drawing file, and if there is, the process returns to step S1007, and if there is not, the process ends.

[0240] As described above, according to the ordering system described in this embodiment, even if the drawing file has a different format, it is possible to create a record to be used for ordering from the drawing file.

[0241] In addition, even if a drawing file contains multiple products, a record can be created for each product. Even if an image file obtained from a drawing file contains multiple products on one page, a record can be created for each product.

[0242] Furthermore, if the image file acquired from the drawing file has multiple pages, a record can be created for each page or each product.

[0243] Furthermore, the individual record editing screen makes it easy to reflect words extracted from an image file in record items.

[0244] Furthermore, each record is associated with the drawing file that was the basis for its creation, so that when a record is selected at the time of placing an order, the associated drawing file can be sent to the contractor.

[0245] Furthermore, if any changes or additions are made to drawing files between the time the record is created and the time the order is placed, they can be associated with the corresponding record, and it is possible to check whether the added drawing file is an update to an existing drawing file or a newly added one.

[0246] Furthermore, the words read from the image file are displayed in different colors to indicate how closely they match the reference words in the dictionary, allowing the user to easily check the input items.

[0247] Additionally, you can manage chat rooms for posting inquiries and corrections related to records.

[0248] In addition, by storing the drawing files and chat rooms entered by the client who created the record in a folder assigned to the client, it is easy to view and edit drawing files and chat rooms related to other records by the same client.

[0249] In addition, other users can be invited to the inquiry screen that displays the client's drawing files and chat rooms, making it easier to collaborate with other users.

[0250] Furthermore, other users invited to the chat room can view and edit the chat room and drawing files on the inquiry screen, but are not given ordering authority for the records, which can prevent, for example, developers from placing erroneous orders as other invited users.

[0251] In addition to the effects described above, the configuration of the ordering system described in this embodiment has various other effects. [Explanation of symbols]

[0252] 1: Ordering system, 2: Orderer terminal, 3: Supplier terminal, 4: Network, 11: CPU (processing unit), 12: Memory, 13: Storage device, 14: I / O device, 15: NW I / F, 16: Bus, 21: Record creation unit, 22: Order acceptance unit, 23: Storage unit, 24: Reading unit, 25: File receiving unit.

Claims

1. An order placement and receipt system that accepts product orders from users, a file receiving unit that receives a drawing file containing a drawing of the product; a record creating unit that creates an order record based on the drawing file received by the file receiving unit; a storage unit for storing the drawing file received by the file receiving unit; a talk room generation unit that generates a talk room related to the record created by the record creation unit, The record creation unit stores in the storage unit a database that associates and stores the chat rooms and the drawing files stored in the storage unit with the records. Ordering system.

2. 2. The ordering system according to claim 1, an inquiry processing unit that generates an inquiry screen corresponding to a chat room and a drawing file associated with a record stored in the storage unit; a display unit that displays the inquiry screen; An order receiving and placing system further comprising:

3. 3. The ordering system according to claim 2, The file receiving unit Get the image file from the received drawing file, The record creation unit If the drawing numbers read from different pages of the image file are different, the image file is divided based on the drawing numbers, and individual files are created for each drawing number. Ordering system.

4. 3. The ordering system according to claim 2, The record creation unit When the file receiving unit receives an additional drawing file for the record, the additional drawing file is associated with the record and stored in a database. Ordering system.

5. 5. The ordering system according to claim 4, The inquiry processing unit If the additional drawing file is an update to an already stored drawing file, a query screen is generated to display that the original drawing has been updated. Ordering system.

6. In the ordering system according to claim 3, an image processing unit that recognizes characters from the drawing file received by the file receiving unit; The record creation unit When the image processing unit recognizes any of "mirror," "multiple product information," and "presence or absence of predetermined features" from one page of the image file, it creates multiple records for that page, The inquiry processing unit The same chat room and drawing file are associated with the plurality of records created from one page of the image file. Ordering system.

7. 7. The ordering system according to claim 6, The inquiry processing unit When duplicating the record created by the record creation unit, the associated chat room and drawing file are also duplicated. Ordering system.

8. 3. The ordering system according to claim 2, The inquiry processing unit The system has an invitation function for inviting a second user different from the first user to a chat room related to a record created based on a drawing file input by a first user. Ordering system.

9. 9. The ordering system according to claim 8, The inquiry processing unit Identify the logged-in user and limit the invitation function for the chat room to the user who created the record. Ordering system.

10. 10. The ordering system according to claim 9, The inquiry processing unit When receiving a post from the second user to the chat room to which the second user has been invited, the post is reflected in the content of the chat room; Rejecting an order request for multiple records from the second user. Ordering system.

11. The ordering system according to claim 10, When the inquiry processing unit receives an additional drawing file via the inquiry screen including the talk room invited by the second user, the record creation unit associates the additional drawing file with the record associated with the first user and saves the additional drawing file. Ordering system.

12. 7. The ordering system according to claim 6, The record creation unit The inquiry processing unit stores the chat rooms and drawing files associated with the plurality of records created from one image file in the same folder. Ordering system.

13. 7. The ordering system according to claim 6, The inquiry processing unit A chat room for the orderer and a chat room for the order recipient are created separately. The contents of the client's chat room will not be provided to the contractor, but will be provided to the client. Ordering system.

14. The ordering system according to claim 13, The inquiry processing unit The contents of the Contractor's chat room will not be provided to the Ordering Party, but will be provided to the Contractor. Ordering system.

15. An order placement and receipt system that accepts product orders from users, a file receiving unit that receives a drawing file containing a drawing of the product; a record creating unit that creates an order record based on the drawing file; a chat room generation unit that generates a chat room related to the product; a storage unit for storing, for each record, a corresponding chat room and drawing file, and a database for saving a plurality of records; an inquiry processing unit that displays, for each record, an inquiry screen including at least one of a chat room and a drawing file associated with the record on a display unit; The database further stores information about users registered in the ordering system; The inquiry processing unit generating a first inquiry screen for a first user, the first inquiry screen including at least one of a first chat room and a first image file associated with a first record of the first user; generating a second inquiry screen including at least one of the first chat room and the first image file included in the first inquiry screen, and transmitting the second inquiry screen to a terminal of a second user different from the first user; Ordering system.

Images