CN111557004B - CAD data inspection system and device - Google Patents

Abstract

Provided are a CAD data inspection system and device capable of improving usability. The CAD data inspection system includes: a design terminal (2) that performs design using a CAD system (21); a management server (1) which is connected to the design terminal (2) in a bi-directional communication manner and manages inspection rules for inspecting CAD data generated by a CAD system, wherein the design terminal (2) comprises: a CAD data acquisition unit (22) that acquires CAD data from the CAD system (21); an inspection rule acquisition unit (23) that acquires a predetermined inspection rule corresponding to the CAD data from the management server (1); and an inspection unit (24) for inspecting the acquired CAD data according to the acquired predetermined inspection rule, wherein the management server (1) can edit the stored inspection rule.

Description

CAD data inspection system and device

Technical Field

The present invention relates to CAD data inspection systems and apparatus.

Background

When a CAD (computer aided design) system is used, a technique is known in which cause and effect relationships are extracted from a defective case generated in the past, and a fault tree is generated based on the extracted cause and effect relationships, thereby assisting in finding a cause of a fault (patent document 1).

Prior art literature

Patent literature

Patent document 1: japanese patent laid-open No. 2017-111657

Disclosure of Invention

Problems to be solved by the invention

In the conventional CAD system, since it is impossible to compare a previously prepared inspection rule with CAD data and edit the inspection rule based on the result, it is difficult to reflect the knowledge of the CAD system alone in the inspection rule, and the usability is low.

The present invention has been made in view of the above-described problems, and an object thereof is to provide a CAD data inspection system and apparatus capable of improving usability.

Means for solving the problems

In order to solve the above problems, a system for inspecting CAD data according to the present invention includes: a design terminal that performs design using a CAD system; a management server which is connected to the design terminal in a bi-directional communication manner and manages a check rule for checking CAD data generated by a CAD system, the design terminal comprising: a CAD data acquisition unit that acquires CAD data from a CAD system; an inspection rule acquisition unit that acquires a predetermined inspection rule corresponding to the CAD data from the management server; and an inspection unit for inspecting the acquired CAD data based on the acquired predetermined inspection rule, wherein the management server can edit the stored inspection rule.

Effects of the invention

According to the present invention, CAD data can be checked according to the check rule, and the stored check rule can be edited, thus improving usability.

Drawings

Fig. 1 is a functional block diagram of a CAD data inspection system.

Fig. 2 is a hardware configuration diagram of the CAD data inspection system.

Fig. 3 is a flowchart showing the rule editing process.

Fig. 4 is a flowchart showing an inspection process of CAD data and a process of using the result of the inspection process.

Fig. 5 is an example of a table showing a list of inspection rules.

Fig. 6 is an example of a table for managing the inspection results.

Fig. 7 is a flowchart showing a process of extracting candidates to be added as rules according to the reaction of the designer to the inspection result in the second embodiment.

Fig. 8 is an example of a table showing a list of inspection rules according to the third embodiment.

Fig. 9 is a flowchart of the fourth embodiment, which shows a case of checking whether or not the rule is satisfied every time the component data is generated.

Fig. 10 is an overall configuration diagram of a system for checking CAD data by a management server providing CAD services of the fifth embodiment.

Detailed Description

Hereinafter, embodiments of the present invention will be described with reference to the drawings. As described later, the CAD data inspection system of the present embodiment determines whether CAD data matches inspection rules and parameters corresponding to a design object of the CAD data, and outputs a determination result (inspection result) thereof. Further, according to the present embodiment, the manager of the inspection rule and parameter can edit at least a part of the managed inspection rule and parameter based on the inspection result. For example, the manager edits at least a part of the inspection rules and parameters according to the designer's reaction to the inspection result.

In the present specification, the edit means registration of a new rule, deletion of an existing rule, modification of an existing rule, addition, deletion, or modification of a parameter.

The inspection rule refers to a guideline for inspecting CAD data. Parameters refer to values that meet the rules. For example, when the rule that "the center position of the hole forming process is separated from the position of the bending process by a predetermined size or more" is provided, the value set to the "predetermined size" is different depending on the material, thickness, purpose of use, machine used for the hole forming, and the like of the processing object.

Hereinafter, CAD data may be expressed as a CAD file, and inspection of CAD data may be expressed as inspection of the CAD file.

When a predetermined parameter is set for the inspection rule, and whether or not the CAD data conforms to the inspection rule (hereinafter, may be simply referred to as a rule), for example, an inspection result such as "conforming" or "non-conforming" is obtained. When a result of "no match" of a predetermined amount or more is generated, it can be determined that one or both of the rule and the parameter should be improved. For example, an evaluation that the rule or the parameter is inappropriate can be performed, and one or both of the rule and the parameter can be reconsidered based on the evaluation.

At least one or both of the inspection rule and the parameter can be improved according to the response of the designer to the inspection result. For example, the response results such as "handled" and "not handled" can be obtained from the designer.

For example, if the occurrence frequency of "no response" is equal to or higher than a predetermined value for a negative check result, there is a possibility that the rule does not need to be applied at all and the value of the parameter is too strict. If there is no problem in the production process or in the quality of the product even if the designer does not cope with the negative inspection result, the rule for generating the negative inspection result may be omitted, which is related to the design recipe or the production recipe.

As described above, according to the CAD data inspection system of the present embodiment, by applying the rule and the parameter to the CAD data and performing inspection, it is possible to obtain an inspection result (evaluation) as to whether the design is not difficult to manufacture, whether the design satisfies the quality standard, and whether the manufacturing cost does not increase, for example.

Further, according to the present embodiment, one or both of the rule and the parameter can be edited according to the inspection result or the response of the designer to the inspection result. As a result, the rules and parameters can be improved according to individual specific conditions, manufacturing recipes, and the like, and the more convenient the use.

Example 1

A first embodiment will be described with reference to fig. 1 to 6. Fig. 1 is a functional block diagram of a CAD data inspection system. The CAD data inspection system includes, for example, a management server 1, one or more design terminals 2, and a management terminal 3. The management terminal 3 may be provided on the same computer terminal as the design terminal 2. Alternatively, the management terminal 3 may be an operation terminal connected to the management server 1. The hardware configuration of the management server 1, the design terminal 2, and the management terminal 3 will be described later in fig. 2.

The management server 1 includes, for example: the inspection parameter setting screen providing unit 11 (referred to as an inspection parameter setting screen 11 in the figure), the inspection parameter generating unit 12, the registering unit 13, the rule managing unit 14, the inspection result confirming unit 15, the database 16, the user managing unit 17, and the suggesting unit 18.

The inspection parameter setting screen providing unit 11 is a function of providing a screen for setting parameters applied to the inspection rule to the setting unit 31 of the management terminal 3. Hereinafter, the inspection parameter may be simply referred to as a parameter.

The inspection parameter generation unit 12 is a function of generating parameters based on values input from the setting unit 31 of the management terminal 3 to the parameter setting screen.

The registration unit 13 is a function of registering the parameters generated by the parameter generation unit 12 in the management server 1.

The rule management unit 14 is a function for collectively managing rules provided to each design terminal 2 to be managed. The rule management unit 14 registers the parameters delivered from the registration unit 13 in the database 16. The rule management unit 14 recalls rules and/or parameters corresponding to the design object from the database 16 and transmits the recalled rules and/or parameters to the design terminal 2. The rule management unit 14 selects rules and/or parameters to be applied to the design object, for example, based on the identification information of the design object product received from the design terminal 2 or based on the identification information of the designer using the design terminal 2.

Here, there are 3 methods as the transmission methods of the rule of the "check rule". The first method is a method in which rules are stored in the design terminal 2 in advance, and a rule number for specifying the rule used and parameters set to the specified rule are transmitted from the management server 1 to the design terminal 2 when CAD data is checked. The second method is a method of transmitting rules and parameters from the management server 1 to the design terminal 2 at the time of verifying CAD data. The third method is a method of storing rules and parameters in advance to the design terminal 2, and transmitting a rule number for determining the rule used and information for determining the parameters from the management server 1 to the design terminal 2 when the CAD data is verified. In the present embodiment, the case according to the first method is described as an example, but the present invention is not limited to this, and the second method or the third method may be used.

As described above, the case of transmitting the rule and the parameter to the design terminal 2 at the time of checking the CAD data, the case of transmitting only the parameter, and the case of transmitting the information for specifying the rule and the information for specifying the parameter to the design terminal 2 are all examples of acquiring the check rule by the check rule acquiring section.

The inspection result confirmation unit 15 is a function for confirming the inspection result (inspection result) of the CAD data by the inspection unit 24 of the design terminal 2. The manager can check the result of the CAD data by making a query from the management terminal 3 to the check result checking unit 15. The inspection result has contents for indicating compliance of the rule and the parameter with the CAD data ("compliance" or "non-compliance"), and a response result ("response" or "non-response") when the inspection result is negative ("non-compliance").

The database 16 manages rules and parameters. The database 16 also stores, for example, a test rule list T1 (see fig. 5) and a test result management table T2 (see fig. 6) which will be described later.

The user management unit 17 is a function of managing information of a designer as a user. The user management unit 17 manages, for example, a user ID, a user name, a department to which the user belongs, the number of years of experience of the user, information indicating the skill level of the user, and the like for specifying the user.

The advice unit 18 is a function of advice the management terminal 3 of editing (adding, deleting, changing) of the rule and/or parameter based on the inspection result of the design terminal 2.

A structural example of the design terminal 2 is explained. The design terminal 2 is a computer terminal used by a designer. The design terminal 2 includes, for example, a CAD system 21, a CAD data acquisition unit 22, a server cooperation unit 23, and a checking unit 24. The CAD data inspection device 20 includes, for example, a CAD data acquisition unit 22, a server cooperation unit 23, and an inspection unit 24. In fig. 1, a case is shown in which the CAD data inspection device 20 is provided in the design terminal 2, but the structure of the CAD data inspection device may be distributed to clients and servers instead.

The CAD system 21 is a function for assisting the design of a product (including a component) to be designed by a computer. In the figure, the CAD system 21 is simply referred to as CAD21.

The CAD data acquisition unit 22 is a function for acquiring CAD data to be inspected from the CAD system 21.

The server cooperation section 23 is a function of exchanging information in cooperation with the management server 1. The server cooperation unit 23 acquires a parameter as "check rule" from the rule management unit 14 that manages the server 1. That is, the server cooperation section 23 is an example of the "inspection rule acquisition section".

The checking unit 24 is a function for determining whether or not CAD data generated by the CAD system 21 satisfies a rule based on a rule stored in advance and a parameter acquired from the management server 1. The inspection result of the inspection unit 24 is transmitted to the inspection result confirmation unit 15 of the management server 1 via the server cooperation unit 23. Therefore, the server cooperation section 23 may also be referred to as "inspection result transmitting section", for example.

A plurality of design terminals 2 can use the management server 1. Fig. 1 illustrates an example in which a plurality of design terminals 2 (1) to 2 (n) belonging to the same design group DG share and use one management server 1. The design terminals 2 (1) to 2 (n) are referred to as design terminals 2 without specific distinction. The design terminals 2 belonging to the design group DG which designs the same product are required to check CAD data using substantially the same rules and parameters. This is to keep the quality of the product constant. However, the design terminals 2 may use different rules and parameters according to, for example, the proficiency of the designer in the design business, the destination of the product, the purpose of use of the product, the cost of the product, and the like.

A structural example of the management terminal 3 is explained. The management terminal 3 is, for example, a computer terminal operated by a manager. The management terminal 3 includes, for example, a setting unit 31 and an analysis unit 32. The setting unit 31 is a function of editing inspection parameters and rules or displaying inspection results on a terminal screen. The analysis unit 32 is a function of analyzing the inspection result and outputting the analysis result. The analysis unit 32 may be provided separately from the management terminal 3 or may be provided in the management server 1.

Fig. 2 is a hardware configuration diagram of the CAD data inspection system. The data management server 1 is connected to the design terminal 2 via a communication path CN1 so as to be capable of bidirectional communication. The data management server 1 is connected to the management terminal 3 via a communication path CN2 so as to be capable of bidirectional communication. The communication path CN1 and the communication path CN2 may be different from each other or may be the same communication path.

The data management server 1 includes, for example, a microprocessor (CPU) 101, a main storage device (main storage in the figure) 102, an auxiliary storage device (auxiliary storage in the figure) 103, and a communication interface (communication IF in the figure) device 104. The auxiliary storage device 103 stores a management program group P1 and a database 16. The database 16 may be stored in a file sharing device or the like separate from the data management server 1.

The functions 11 to 15, 17, and 18 described in fig. 1 are realized by the microprocessor 101 reading and executing the hypervisor group P1 into the main storage device 102. The communication interface device 104 communicates with each design terminal 2 via a communication path CN 1. The communication interface device 104 communicates with the management terminal 3 via the communication path CN 2.

The design terminal 2 includes, for example, a microprocessor 201, a main storage device 202, an auxiliary storage device 203, a communication interface device 204, and a User Interface (UI) device 205. The auxiliary storage device 203 stores CAD software P21 and design checking software P22.

The CAD system 21 described in fig. 1 is implemented by the microprocessor 201 reading CAD software P21 into the main memory device 202 and executing it. Similarly, the CAD data inspection device 20 described in fig. 1 is implemented by the microprocessor 201 reading the design inspection software P22 into the main storage device 202 and executing it.

The communication interface device 204 communicates with the data management server 1 via the communication path CN 1.

The user interface device 205 is a device that the designer exchanges information with the design terminal 2. The user interface device 205 may be divided into an information input device and an information output device (both not shown). Examples of the information input device include a pointing device such as a keyboard and a mouse, a touch panel, and a voice recognition device. Examples of the information output device include a display, a printer (including a three-dimensional printer), a speech synthesis device, and the like.

The management terminal 3 includes, for example, a microprocessor 301, a main storage device 302, an auxiliary storage device 303, a communication interface device 304, and a user interface device 305, similarly to the design terminal 2. The auxiliary storage device 303 stores, for example, a web browser P3.

The setting unit 31 described in fig. 1 is realized by the microprocessor 301 reading and executing the web browser P3 into the main storage device 302.

The communication interface device 304 communicates with the data management server 1 via a communication path CN 2. The user interface device 305 is a device that the manager exchanges information with the management server 1 via the management terminal 3.

Any one or more of the plurality of design terminals 2 may function as the design terminal 2 and the management terminal 3. Alternatively, the management terminal 3 may be integrated with the data management server 1. The management terminal 3 may be configured as a personal computer such as a portable information terminal (including a so-called smart phone), a notebook type, or a tablet type.

Fig. 3 is a flowchart showing a process of editing a rule (including parameters) registered in the management server 1.

The manager instructs the management screen (not shown) displayed on the management terminal 3 to edit the rule (S1). Authentication information input by a manager is transmitted to a data management server (sometimes simply referred to as "management server" in the figure) 1, and user authentication is performed (S2).

If the user authentication is successful, the management server 1 reads out the inspection rule list T1 as an example of "list information of inspection rules" from the database 16 (S3), and transmits it to the management terminal 3 (S4).

The manager edits the inspection rule list T1 by the web browser P3 of the management terminal 3 (S5). When the editing is completed, the editing result of the rule is transmitted from the management terminal 3 to the management server 1 (S6).

The rule management unit 14 of the management server 1 reflects the rule edit result received from the management terminal 3 to the database 16 (S7). That is, the rule management unit 14 adds new rules and/or parameters (hereinafter referred to as "rules and the like") to the database 16, deletes existing rules and the like, and changes existing rules and the like.

The rule management section 14 is also capable of notifying that the rule or the like registered in the database 16 has been updated on the CAD screen operated by the designer associated with the updating section (S8). Notification to the relevant person may also be omitted.

Fig. 4 is a flowchart showing the process of inspecting CAD data (S11 to S21) and the process of using the result of the inspection process (S31 to S35).

When the design or the design paragraph is ended, the designer instructs the inspection of the generated CAD data (S11). For example, check boxes are displayed in a screen provided by the CAD system 21, and by operating the check boxes by a designer, inspection of CAD data (inspection of CAD data) can be instructed.

When execution of the inspection is instructed (S11), a file name (CAD file name) to be inspected is transmitted from the design terminal 2 to the management server 1.

The management server 1 identifies a product to be inspected based on the received file name (S13), and transmits an inspection rule list T10 applicable to the identified product to the design terminal 2 (S14). The inspection rule list T10 transmitted here corresponds to an example of "list information of selectable inspection rules".

The inspection rule list T10 received from the management server 1 is displayed on the screen of the design terminal 2, and one or a plurality of rule sets are selected by the designer (S15). Identification information (set ID or rule set ID) for specifying the rule set selected by the designer is transmitted from the design terminal 2 to the management server 1 (S16).

The management server 1 reads out a parameter set corresponding to the set ID from the database 16 based on the set ID received from the design terminal 2 (S17), and transmits the read parameter set to the design terminal 2 (S18).

The checking section 24 of the design terminal 2 checks whether or not the CAD file (CAD data) meets the rule by using the parameter set received from the management server 1 for the rule set selected in step S15 (S19). Then, the design terminal 2 transmits the inspection result to the management server 1 (S20). The inspection result confirmation unit 15 of the management server 1 confirms the inspection result of the inspection unit 24 of the design terminal 2, and gives the inspection result to the rule management unit 14. The user management unit 17 and the advice unit 18 can refer to the inspection result.

Next, a process using the inspection result will be described. The manager can query the management server 1 for the inspection result by using the management screen displayed on the management terminal 3 (S31). The manager can query the management server 1 for the inspection result from one or more viewpoints such as a product category, a product ID, a CAD file name, a designer name, an ID of the design terminal 2, a design group name, a date time or a period during which the inspection result is recorded, for example.

The management server 1 reads the inspection result from the database 16 according to the inquiry received from the management terminal 3 (S32), and transmits the inspection result to the management terminal 3 (S33).

When receiving the inspection result from the management server 1, the management terminal 3 analyzes the received inspection result (S34), and outputs the analysis result (S35).

Analysis refers to, for example, the generation of objective evidence, the analysis of the tendency of design errors, the evaluation of the skill of the designer, and the like. Objective evidence refers to, for example, evidence for proving a regulatory benchmark that satisfies ISO (international organization for standardization). And sending the analysis result to an off-graph system. The management server 1 may be provided with a function of utilizing the analysis result.

Fig. 5 shows an example of the inspection rule list T1. The check rule list T1 includes, for example, a set ID C11, a rule number C12, an applicable flag C13, and at least one parameter C14.

The set ID C11 is identification information for determining a rule set including one or more rules. The rule number (in the figure, "rule#") C12 is the number of the rule contained in the rule set determined by the set ID.

The applicability flag C13 is flag information indicating whether the rule set specified by the set ID can be applied to the CAD file to be inspected. The applicable flag C13 can be set to a value of "applicable" or "inapplicable" and also can be set to conditions such as "desired applicable" and "preferably applicable to a portion requiring high quality". Even if the "inapplicable" set ID is set to the flag C13, the designer may select the set ID.

The designer refers to the inspection rule list T10 and selects a set ID to be applied to the CAD file to be inspected. Alternatively, the management server 1 may transmit the inspection rule list T10 including only the set ID set to "applicable" for the applicable flag C13 to the design terminal 2.

Fig. 6 shows an example of the inspection result management table T2. When the inspection of the CAD file in the design terminal 2 is completed, the inspection result management table T2 is transmitted from the design terminal 2 to the management server 1.

The inspection result management table T2 includes, for example, a user ID C21, a time C22, an object file C23, and an inspection result C24.

The user ID C21 is information for identifying the designer. Time C22 is the time at which the CAD file is checked. The object file C23 is information (e.g., file name) for determining the checked CAD file.

The inspection result C24 includes, for example, a set ID C241, a rule number C242, and a handling result C243. The set ID C241 is an ID of a rule set used in the inspection. The rule number C242 is information for determining the rule contained in the rule set. The coping C243 is the coping of the designer with the inspection result.

For example, values such as "handled", "not handled", "partially handled" and "partially not handled" can be set to the handled result 243. It may be indicated only whether or not it has been dealt with.

According to the present embodiment thus configured, it is possible to check whether CAD data is generated according to a rule, and therefore, it is possible to pay attention to improvement points in design and the like, and to efficiently perform design using the CAD system 21. In the present embodiment, the management server 1 can edit rules and the like, and therefore, for example, rules and the like corresponding to usage results and the like can be accumulated, and the more convenient the user. For example, a manager who manages the rules and the like can appropriately edit the rules and the like with reference to the reaction of the designer, the reaction on the manufacturing line, and the like.

Example 2

A second embodiment will be described with reference to fig. 7. The following embodiments including the present embodiment correspond to modifications of the first embodiment, and therefore differences from the first embodiment will be mainly described. In this embodiment, candidates to be added as rules or the like are extracted and suggested to the manager based on the designer's reaction to the inspection result.

Fig. 7 shows a process of extracting an editing target candidate from the inspection result of the design terminal 2 and providing the editing target candidate to the management terminal 3.

The management server 1 reads the inspection result management table T2 from the database 16 (S41), and calculates the number N1 of rules for which "no-coping" is set for the coping-up result C243 of the inspection result C24 (S42). That is, the management server 1 calculates the number N1 of rules that the designer does not deal with, regardless of whether the check result is negative.

The management server 1 determines whether or not the number N1 of "not to deal with" is equal to or greater than a predetermined threshold Th1 for the same number of rules (S43). For example, the threshold value Th1 may be determined for each product to be designed, the threshold value Th1 may be determined for each component constituting the product, or the threshold value Th1 may be determined according to the destination of the product and the required quality.

When the number N1 of "unmatched" rules is equal to or greater than the threshold Th1 (yes in S43), the management server 1 stores the rule as an editing target candidate (S44). Then, the management server 1 determines whether or not editing of a rule or the like has been instructed from the management terminal 3 (S45), and when editing has been instructed (yes in S45), transmits the editing target candidate stored in step S44 to the management terminal 3 (S46). The management server 1 transmits the editing target candidates to the management terminal 3 in step S3 described in fig. 3, for example.

The manager confirms the editing target candidate received from the management server 1, and determines whether or not registration as a formal rule is necessary. When the rule or the like needs to be registered as a formal rule, the manager instructs the management server 1 to register the editing target candidate as a formal rule or the like as described in steps S5 and S6 of fig. 3.

The present embodiment thus constructed also has the same operational effects as the first embodiment. Further, according to the present embodiment, editing target candidate rules and the like can be extracted and suggested to the manager in response to the result of the designer's inspection of the CAD file. Thus, for example, by changing the value of the parameter initially set for the editing target candidate rule, it is possible to generate an individual rule or the like and register the rule in the management server 1.

That is, if the designer does not deal with the inspection result at all regardless of whether or not the inspection result is negative, the designer knows that there is no problem even if the inspection result is disregarded. That is, the recipe on site is superior to the rule or the like managed in the management server 1. In this case, the manager edits the rule of "not to deal with" and registers it in the management server 1, thereby reflecting the know-how and the like on site as a rule or the like, and improving usability.

Example 3

A third embodiment will be described with reference to fig. 8. In the present embodiment, a priority can be set to the rule set. Fig. 8 shows an example of the inspection rule list T1 a.

The inspection rule list T1a of the present embodiment has a priority C15 as compared with the inspection rule list T1 described in fig. 5. The priority C15 indicates a priority suitable for use in the inspection of CAD files. The higher the priority, the higher the necessity of application.

The present embodiment thus constructed also has the same operational effects as the first embodiment. Further, according to the present embodiment, since the priority can be set for the rule set, the designer can judge whether to use the rule set in the inspection of the CAD file with reference to the priority, and the usability can be improved. Further, if the rule set with high priority is automatically selected by the inspection unit 24, omission of design errors can be further suppressed, and ease of use and reliability can be improved.

Example 4

A fourth embodiment will be described with reference to fig. 9. In the present embodiment, the inspection can be performed every time a CAD file (CAD data) of the component is generated.

When the CAD file of the component constituting the product is generated (S51), the CAD system 21 of the design terminal 2 instructs the management server 1 to check the CAD file of the component (S52). The management server 1 transmits the inspection rule list T1 to the design terminal 2 in response to the instruction from the design terminal 2, and transmits the parameter set corresponding to the selected rule set to the design terminal 2 (S53).

Hereinafter, the designer can perform the inspection (S54 to S56, S57 to S59) each time the CAD file of the component is generated.

The present embodiment thus constituted can check whether or not the rule is satisfied for each part or each part of the parts constituting the product. In contrast, as in the first embodiment, CAD files of the entire product can be checked uniformly.

Example 5

A fifth embodiment will be described with reference to fig. 10. In the present embodiment, the CAD system and the inspection system are provided as cloud services.

Fig. 10 is an overall configuration diagram of the CAD service of the present embodiment. The design terminal 2 and the management terminal 3 belonging to the plurality of organizations Oa, ob are bidirectionally communicably connected with the CAD service management server 4 via the communication network CN 3.

The organizations Oa, ob are, for example, different organizations that require confidentiality, such as different enterprises, or different departments within the same enterprise. One or more design groups DGa (1), DGa (2) can be set for the tissue Oa. Likewise, one or more design groups DGb (1) and DGb (2) may be provided for the organization Ob.

The design terminals 2a (1) and 2a (2) can be provided for the design group DGa (1), and the design terminals 2a (3) and 2a (4) can be provided for the design group DGa (2). Similarly, the design terminals 2b (1) and 2b (2) may be provided for the design group DGb (1), and the design terminals 2b (3) and 2b (4) may be provided for the design group DGb (2).

The organization Oa includes a management terminal 3a for managing each of the design groups DGa (1) and DGa (2). Similarly, the organization Ob also includes a management terminal 3b for managing each of the design groups DGb (1) and DGb (2). However, the present invention is not limited thereto, and a management terminal may be provided for each design group.

The CAD service management server 4 includes CAD systems 21a and 21b and design checking units 24a and 24b. The CAD service management server 4 is provided with partitions 41a and 41b corresponding to the organizations Oa and Ob, and stores the secrets of the respective partitions. In the partition 41a corresponding to the organization Oa, the CAD system 21a and the design checking section 24a are provided. In the partition 41b corresponding to the organization Ob, the CAD system 21b and the design checking section 24b are provided.

The present embodiment thus constructed also has the same operational effects as the first embodiment. In the present embodiment, the CAD service management server 4 can provide the CAD system 21 and the checking function 24 of the CAD file as a so-called cloud service to the design terminals 2 belonging to different design groups of different organizations.

The present invention is not limited to the above embodiment. Various additions, modifications and the like can be made by those skilled in the art within the scope of the present invention. The above-described embodiments are not limited to the structural examples illustrated in the drawings. The configuration and processing method of the embodiment can be appropriately changed within the scope of the present invention.

The present invention is also intended to include an invention having a structure in which each constituent element of the present invention can be arbitrarily selected and selected. In addition, the structures described in the claims can be combined in addition to the combinations explicitly described in the claims.

The structure of the above embodiment can also be expressed as an invention of a method as follows, for example.

"a CAD data inspection method which is a method for inspecting CAD data using a computer, wherein the computer 1 transmits a predetermined inspection rule from among inspection rules stored in a database 16 in response to a request from a design terminal 2, receives a result that the design terminal inspected CAD data in accordance with the predetermined inspection rule from the design terminal, and can edit the inspection rule stored in the database 16.

Description of the reference numerals

1: a management server; 2. 2a, 2b: designing a terminal; 3. 3a, 3b: a management terminal; 4: a CAD service management server; 11: a parameter setting screen for inspection; 12: an inspection parameter generation unit; 13: a registration unit; 14: a rule management unit; 15: a checking result confirming part; 16: a database; 17: a user management unit; 18: a suggestion section; 21. 21a, 21b: a CAD system; 22: a CAD data acquisition unit; 23: a server cooperation unit; 24. 24a, 24b: an inspection unit; 31: a setting unit; 32: an analysis unit.

Claims (4)

1. A CAD data inspection system for inspecting CAD data is characterized by comprising:

a design terminal that performs design using a CAD system;

a management server which is connected with the design terminal in a bi-directional communication manner and manages a checking rule for checking the CAD data generated by the CAD system,

the design terminal comprises:

a CAD data acquisition unit that acquires the CAD data from the CAD system;

an inspection rule acquisition unit that acquires a predetermined inspection rule corresponding to the CAD data from the management server; and

an inspection unit configured to inspect the acquired CAD data based on the acquired predetermined inspection rule,

the management server can edit the stored inspection rules,

the management server transmits list information of selectable inspection rules to the design terminal according to a request from the design terminal,

the inspection rule acquiring unit of the design terminal that receives the list information acquires, as the predetermined inspection rule, an inspection rule selected by a designer among the inspection rules included in the list information,

the inspection result of the inspection unit includes response result information indicating the response of the designer to the inspection result,

the management server extracts a check rule to be an editing target candidate based on the corresponding result information acquired from the design terminal.

2. The CAD data inspection system of claim 1, wherein,

the management server may edit at least a part of the inspection rule stored in the management server based on an inspection result of the inspection unit of the design terminal.

3. The CAD data inspection system of claim 2, wherein,

the predetermined inspection rule is an inspection rule selected in correspondence with a design object designed using the CAD system,

the inspection rule obtaining unit of the design terminal obtains the same predetermined inspection rule from the management server.

4. The CAD data inspection system of claim 1, wherein,

a value indicating that there is no action of the designer on the inspection result can be set for the coping-result information,

the management server extracts, as the editing target candidate, an inspection rule corresponding to the inspection result for which there is no action of the designer, edits at least a part of the extracted inspection rule, and stores the edited inspection rule in the management server.