CN111557004A - 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 is provided with: a design terminal (2) that performs design using a CAD system (21); a management server (1) connected to a design terminal (2) so as to be capable of two-way communication, and managing an inspection rule 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 a 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) that inspects the acquired CAD data based on the acquired predetermined inspection rule, and the management server (1) can edit the stored inspection rule.

Description

CAD data inspection system and device

Technical Field

The present invention relates to a CAD data inspection system and device.

Background

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

Documents of the prior art

Patent document

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

Disclosure of Invention

Problems to be solved by the invention

In the conventional CAD system, it is not possible to compare a previously prepared inspection rule with CAD data and edit the inspection rule based on the result, and therefore it is difficult to reflect the knowledge unique to the user of the CAD system in the inspection rule, and usability is low.

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

Means for solving the problems

In order to solve the above problem, a system for inspecting CAD data according to the present invention includes: a design terminal which performs design using a CAD system; a management server connected to the design terminal in a two-way communication manner and managing an inspection rule for inspecting the CAD data generated by the CAD system, the design terminal including: 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 that inspects the acquired CAD data based on the acquired predetermined inspection rule, and 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 ease of use.

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 a rule editing process.

Fig. 4 is a flowchart showing the inspection process of CAD data and the process 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 of the second embodiment, which shows a process of extracting candidates to be added as rules based on a reaction of a designer to an inspection result.

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 where whether or not a rule is satisfied is checked each time component data is generated.

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

Detailed Description

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

In this specification, editing means registration of a new rule, deletion of an existing rule, change of an existing rule, addition, deletion, or change of a parameter.

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

Hereinafter, CAD data is sometimes expressed as a CAD file, and inspection of the CAD data is sometimes expressed as verification of the CAD file.

When a predetermined parameter is set for a rule for inspection and whether or not CAD data conforms to the rule for inspection (hereinafter, may be simply referred to as a rule), inspection results such as "fit" and "not fit" are obtained. When a result of "not meeting" by 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, it is possible to perform evaluation that the rule and the parameter are inappropriate, and to reconsider one or both of the rule and the parameter based on the evaluation.

At least one or both of the rules and parameters for inspection can be improved according to the response of the designer to the inspection result. For example, the designer can obtain the results of "dealt with" and "not dealt with".

For example, when the frequency of occurrence of "no treatment" is equal to or higher than a predetermined value with respect to a negative check result, it is possible to consider the possibility that the rule need not be applied at all and the parameter value is too strict. If no problem occurs in the manufacturing process or product quality even if the designer does not deal with a negative check result, the rule that the negative check result is generated can be ignored, which is related to a trick in design or a trick in manufacturing.

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

Further, according to the present embodiment, one or both of the rule and the parameter can be edited in accordance with 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 situations, manufacturing recipes, and the like, and the use is more convenient.

Example 1

The 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: an inspection parameter setting screen image providing unit 11 (marked as an inspection parameter setting screen image 11 in the figure), an inspection parameter generating unit 12, a registering unit 13, a rule managing unit 14, an inspection result confirming unit 15, a database 16, a user managing unit 17, and an advising unit 18.

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

The inspection parameter generating unit 12 is a function of generating a parameter based on a value 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 parameter generated by the parameter generation unit 12 in the management server 1.

The rule management unit 14 is a function of collectively managing rules provided to each design terminal 2 as a management target. The rule management unit 14 registers the parameters delivered from the registration unit 13 in the database 16. The rule management unit 14 calls out a rule and/or a parameter corresponding to the design object from the database 16 and transmits the rule and/or the parameter to the design terminal 2. The rule management unit 14 selects a rule and/or a parameter 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, as a rule of "check rule", there are 3 methods as a sender method. The first method is a method in which a rule is stored in advance in the design terminal 2, and a rule number for specifying the rule to be used and a parameter 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 when checking CAD data. The third method is a method of storing rules and parameters in the design terminal 2 in advance, and transmitting a rule number for specifying the used rule and information for specifying the parameters from the management server 1 to the design terminal 2 when checking the CAD data. In this embodiment, the case according to the first method is described as an example, but the present invention is not limited thereto, 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, 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 at the time of checking the CAD data are all examples of the case where the check rule acquisition unit acquires the check rule.

The inspection result confirmation unit 15 is a function of confirming a result of inspection (inspection result) of the CAD data by the inspection unit 24 of the design terminal 2. The administrator can check the inspection result of the CAD data by making an inquiry from the management terminal 3 to the inspection result checking unit 15. The inspection result has a content ("conformity" or "nonconformity") indicating the conformity of the rule and the parameter to the CAD data, and a corresponding result ("coping" or "non-coping") in the case of a negative inspection result ("nonconformity").

The database 16 manages rules and parameters. The database 16 also stores, for example, an inspection rule list T1 (see fig. 5) and an inspection result management table T2 (see fig. 6) 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 for specifying a user, 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.

The recommendation unit 18 is a function for recommending (adding, deleting, changing) the rules and/or parameters to the management terminal 3 based on the inspection result of the design terminal 2.

An example of the structure 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 an inspection 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. Although fig. 1 shows the case where the CAD data inspection device 20 is provided in the design terminal 2, the configuration of the CAD data inspection device may be distributed between the client and the server.

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 CAD 21.

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

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

The checking unit 24 is a function of determining whether or not the CAD data generated by the CAD system 21 satisfies the rule based on the rule stored in advance and the 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 unit 23 may be referred to as an "inspection result transmission unit", for example.

The management server 1 can be used by a plurality of design terminals 2. In the example of fig. 1, a case is shown 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. When the design terminals 2(1) to 2(n) are not distinguished, they are referred to as design terminals 2. The design terminals 2 belonging to the design group DG designing the same product are required to check the CAD data using substantially the same rules and parameters. This is to keep the quality of the product constant. However, each design terminal 2 may use different rules and parameters depending on, for example, the skill of the designer for the design business, the delivery destination of the product, the purpose of use of the product, the product cost, and the like.

An example of the configuration of the management terminal 3 will be described. 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 parameters and rules for inspection, 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 bidirectionally communicably connected to the design terminal 2 via a communication path CN 1. The data management server 1 is connected with the management terminal 3 bidirectionally communicably via a communication path CN 2. The communication path CN1 and the communication path CN2 may be different communication paths or the same communication path.

The data management server 1 includes, for example, a microprocessor (in the figure, "CPU") 101, a main storage device (in the figure, "main storage") 102, an auxiliary storage device (in the figure, "auxiliary storage") 103, and a communication interface (in the figure, "communication IF") device 104. The secondary storage device 103 stores a hypervisor group P1 and a database 16. The database 16 may be stored in a file sharing apparatus 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 in 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 a 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 in the figure) device 205. The auxiliary storage device 203 stores CAD software P21 and design check software P22.

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

The communication interface device 204 communicates with the data management server 1 via a 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 or 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), and a speech synthesis device.

The management terminal 3 also 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, as in the case of the design terminal 2. The secondary storage device 303 stores, for example, a web browser P3.

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

The communication interface means 304 communicates with the data management server 1 via a communication path CN 2. The user interface device 305 is a device in which an administrator exchanges information with the management server 1 via the management terminal 3.

All or 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) or a notebook type or tablet type.

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

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

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

The administrator edits the check rule list T1 by using the web browser P3 of the management terminal 3 (S5). When the editing is finished, the rule editing result 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 edit result of the rule 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, changes existing rules and the like.

The rule management part 14 can also notify that the rules and the like registered in the database 16 have been updated on the CAD screen operated by the designer associated with the update part (S8). Notification to the relevant person may also be omitted.

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

When the design or the design bulletin section is finished, the designer instructs the inspection of the generated CAD data (S11). For example, a check box is displayed on a screen provided by the CAD system 21, and the check box is operated by the designer to instruct checking of the CAD data (checking of the CAD data).

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 checked from the received file name (S13), and transmits a check 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 more 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 the 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-out parameter set to the design terminal 2 (S18).

The checking section 24 of the design terminal 2 checks whether the CAD file (CAD data) conforms to 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 check 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 passes the inspection result to the rule management unit 14. The user management unit 17 and the recommendation unit 18 can also refer to the examination result.

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

The management server 1 reads out the check result from the database 16 in response to the query received from the management terminal 3 (S32), and transmits the check 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).

The analysis means, for example, generation of objective proof, analysis of a tendency of design error, evaluation of skill of a designer, and the like. The objective evidence means, for example, evidence for proving that the supervision standard of ISO (international organization for standardization) is satisfied. And sending the analysis result to a system outside the graph. A function of using the analysis result may be provided in the management server 1.

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 specifying a rule set including one or more rules. The rule number (in the figure, "rule #") C12 is the number of a rule included in the rule set determined by the set ID.

The applicability flag C13 is flag information indicating whether or not the rule set specified by the set ID can be applied to the CAD file to be checked. The applicable/not-applicable flag C13 can be set to a value of "applicable" or "not applicable", and can also be set to conditions of "desired application" and "preferably applied to a portion where high quality is required". Even if the flag C13 is set to "inapplicable" set ID, the designer may be able to 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 check rule list T10 including only the set ID set as "applicable" to the applicability 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 finished, 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. The time C22 is the time when the CAD file is checked. The object file C23 is information (e.g., a file name) for specifying the CAD file to be checked.

The inspection result C24 includes, for example, a set ID C241, a rule number C242, and a response result C243. Set ID C241 is the ID of the rule set used in the check. The rule number C242 is information for specifying a rule included in the rule set. The correspondence result C243 is a correspondence of the designer to the inspection result.

For example, values such as "supported", "not supported", "partially supported", and "partially not supported" can be set in correspondence with the support result 243. Or may simply indicate whether or not it has dealt with.

According to the present embodiment configured as described above, since whether or not CAD data is generated according to a rule can be checked, it is possible to pay attention to an improvement point in design and the like, and it is possible to efficiently perform design using the CAD system 21. Further, in the present embodiment, since the management server 1 can edit the rule and the like, for example, the rule and the like corresponding to the use record and the like can be accumulated, and the convenience can be increased. For example, a manager who manages the rules and the like can edit the rules and the like appropriately by referring to the reaction of the designer, the reaction on the manufacturing line, and the like.

Example 2

The 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 based on the reaction of the designer to the inspection result, and are suggested to the administrator.

Fig. 7 shows a process of extracting candidates to be edited based on the inspection result of the design terminal 2 and providing the candidates to be edited to the management terminal 3.

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

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

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

The administrator confirms the candidate for editing received from the management server 1 and determines whether or not registration as a regular rule or the like is necessary. When the registration of the candidate editing rule or the like is required, the administrator instructs the management server 1 to register the candidate editing rule or the like as the official rule as described in steps S5 and S6 of fig. 3.

The present embodiment thus configured also achieves the same operational effects as the first embodiment. Further, according to the present embodiment, it is possible to extract an editing target candidate rule and the like to suggest to the administrator according to the response of the designer to the inspection result of the CAD file. Thus, for example, by changing the value of a parameter initially set for the candidate rule to be edited, an individual rule or the like can be generated and registered in the management server 1.

That is, when the designer fails to cope with the inspection result at all regardless of whether the inspection result is negative or not, the designer knows that there is no problem in practice regardless of the inspection result. That is, the technical know-how of the scene is superior to the rule and the like managed in the management server 1. In this case, the manager can reflect a recipe or the like in the field as a rule or the like by editing the rule of "not to deal" and formally registering the rule in the management server 1, and usability can be improved.

Example 3

The third embodiment will be described with reference to fig. 8. In the present embodiment, 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 over the inspection rule list T1 shown in fig. 5. The priority C15 indicates a priority applied to the inspection of the CAD file. Higher priority means higher necessity of application.

The present embodiment thus configured also achieves the same operational effects as the first embodiment. Further, according to the present embodiment, since the rule set can be set with a priority, the designer can refer to the priority and determine whether or not to use the rule set for checking the CAD file, thereby improving usability. Further, if the inspection unit 24 is configured to automatically select a rule set with a high priority, omission of design errors can be further suppressed, and usability and reliability can be improved.

Example 4

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

When the CAD system 21 of the design terminal 2 generates a CAD file of a part constituting a product (S51), it instructs the management server 1 to check the CAD file of the part (S52). The management server 1 transmits the check rule list T1 to the design terminal 2 and transmits the parameter set corresponding to the selected rule set to the design terminal 2 in accordance with the instruction from the design terminal 2 (S53).

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

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

Example 5

The 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 requiring privacy, like different enterprises, or different departments within the same enterprise. One or more design groups DGa (1), DGa (2) can be set for the organization Oa. Similarly, one or more design groups DGb (1), DGb (2) may be set for the organization Ob.

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

The organization Oa includes a management terminal 3a for managing the design groups DGa (1) and DGa (2). Similarly, the organization Ob also includes a management terminal 3b for managing the design groups DGb (1) and DGb (2). However, the present invention is not limited to this, 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 24 b. 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 partitions. In the partition 41a corresponding to the tissue Oa, the CAD system 21a and the design check unit 24a are provided. In the partition 41b corresponding to the tissue Ob, a CAD system 21b and a design check unit 24b are provided.

The present embodiment thus configured also achieves 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 CAD file checking function 24 to the design terminals 2 belonging to different design groups of different organizations as a so-called cloud service.

The present invention is not limited to the above-described embodiments. Those skilled in the art can make various additions, modifications, and the like within the scope of the present invention. The above embodiments are not limited to the configuration examples illustrated in the drawings. The configuration and the processing method of the embodiment can be appropriately modified within the range reaching the object of the present invention.

In addition, each component of the present invention can be arbitrarily selected, and an invention having a configuration selected by selection is also included in the present invention. In addition, the configurations described in the claims can be combined with each other in addition to the combinations explicitly described in the claims.

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

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

Description of the reference numerals

1: a management server; 2. 2a, 2 b: designing a terminal; 3. 3a, 3 b: 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: an inspection result confirmation unit; 16: a database; 17: a user management unit; 18: a recommendation section; 21. 21a, 21 b: a CAD system; 22: a CAD data acquisition unit; 23: a server cooperation unit; 24. 24a, 24 b: an inspection unit; 31: a setting unit; 32: an analysis unit.

Claims (7)

1. A CAD data inspection system for inspecting CAD data, comprising:

a design terminal which performs design using a CAD system;

a management server connected to the design terminal in a two-way communication manner and managing an inspection rule for inspecting the CAD data generated by the CAD system,

the design terminal includes:

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 that inspects the acquired CAD data based on the acquired predetermined inspection rule,

the management server can edit the stored check rule.

2. The CAD data inspection system of claim 1,

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 included in the design terminal.

3. The CAD data inspection system of claim 2,

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

the inspection rule acquisition unit of the design terminal acquires the same predetermined inspection rule from the management server.

4. A CAD data inspection system according to any one of claims 1 to 3,

the management server transmits list information of selectable check rules to the design terminal in response to a request from the design terminal,

the inspection rule acquisition unit of the design terminal that has received the list information acquires, as the predetermined inspection rule, an inspection rule selected by the designer from among the inspection rules included in the list information.

5. The CAD data inspection system of claim 4,

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

the management server extracts an inspection rule to be a candidate for editing based on the response result information acquired from the design terminal.

6. The CAD data inspection system of claim 5,

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

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

7. A CAD data inspection device for inspecting CAD data, comprising:

a CAD data acquisition unit that acquires CAD data;

an inspection rule acquisition unit that acquires, from an inspection rule management unit that manages an inspection rule of CAD data, an inspection rule corresponding to the CAD data acquired by the CAD data acquisition unit; and

and an inspection unit that inspects the CAD data based on the inspection rule.

Images