Information processing device, information processing system, control method therefor, and program
The mechanism enables efficient application of design settings across multiple parts in 3D CAD by automating the transfer of design attributes from one model to another, addressing the time-consuming manual input issue in existing CAD systems.
Patent Information
- Application Number
- JP2025120391
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-07-17
- Publication Date
- 2025-09-11
AI Technical Summary
Existing 3D CAD software requires manual input and application of design attributes for each part, which is time-consuming.
A mechanism that allows for the easy application of settings to design data by using a selection receiving means to receive setting information from first design data and a control means to apply it to second design data.
Facilitates efficient and automated application of design settings across multiple parts, reducing manual input time and improving productivity in 3D CAD design processes.
Smart Images

Figure 2025134052000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to an information processing device, an information processing system, a control method thereof, and a program. [Background technology]
[0002] When designing using 3D CAD (Computer-Aided Design) software, there are times when you want to reuse information from existing design data.
[0003] For example, this includes design information such as drawing number, name, production number, customer name, material, and production date, as well as dimensions of parts.
[0004] When creating similar parts, this information must be set for each individual part, which is time-consuming. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-352678 DISCLOSURE OF THE INVENTION [Problem to be solved by the invention]
[0006] Patent Document 1 describes a technology that fixes labels that move as the 3D model rotates so that they are easier to input when manually inputting attribute information onto a 3D model. However, this ultimately requires manually inputting and applying attributes one by one, which is time-consuming.
[0007] An object of the present invention is to provide a mechanism that allows settings to be easily applied to design data. [Means for solving the problem]
[0008] The present invention comprises a selection receiving means for receiving a selection of setting information set in first design data, and a control means for controlling the setting information selected and received by the selection receiving means to be applied to the second design data. [Effects of the Invention]
[0009] According to the present invention, it is possible to provide a mechanism that allows settings to be easily applied to design data. [Brief explanation of the drawings]
[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration according to an embodiment of the present invention. [Figure 2] 1 is a block diagram showing an example of a hardware configuration of an information processing device applicable to a client terminal 100 and a server 200 in an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram illustrating an example of a functional configuration according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram showing an example of assembly configuration information in the embodiment of the present invention. [Figure 5] FIG. 10 is a diagram showing an example of feature information in the embodiment of the present invention. [Figure 6] 10 is a flowchart showing an outline of a definition output process in the embodiment of the present invention. [Figure 7] 10 is a flowchart showing details of a dimension definition output process in the embodiment of the present invention. [Figure 8] 10 is a flowchart showing details of a property definition output process in the embodiment of the present invention. [Figure 9] 10 is a flowchart showing an outline of a definition application process in an embodiment of the present invention. [Figure 10] 10 is a flowchart showing details of a setting process for a dimension change (a shape change due to a dimension change) in the embodiment of the present invention. [Figure 11] 10 is a flowchart showing details of a property change setting process in the embodiment of the present invention. [Figure 12] 10 is a flowchart showing details of a batch execution process in the embodiment of the present invention. [Figure 13] 3A to 3C are diagrams illustrating examples of configurations of various screens according to an embodiment of the present invention. [Figure 14] 3A to 3C are diagrams illustrating examples of various data configurations in the embodiment of the present invention. [Figure 15] 3A to 3C are diagrams illustrating examples of configurations of various screens according to an embodiment of the present invention. [Figure 16] 3A to 3C are diagrams illustrating examples of configurations of various screens according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0011] FIG. 1 is a diagram showing an example of the configuration of an information processing system according to an embodiment of the present invention.
[0012] A client terminal 100 and a server 200 are connected via a network 101. In this embodiment, the network 101 is a LAN (Local Area Network), but a WAN (Wide Area Network) may also be used.
[0013] CAD software (hereinafter referred to as CAD) is installed on the client terminal 100.
[0014] CAD is an application that can generate and edit two-dimensional design data and three-dimensional design data. The design data is generated as a file that can be edited by CAD (CAD file) and stored in a storage area of the client terminal 100 or the server 200.
[0015] Design data includes types such as parts, assemblies, and drawings. Drawings are two-dimensional drawings in which the three-dimensional information of parts / assemblies is projected onto a plane and dimension notes and other information are inserted. Details of parts / assemblies will be explained later.
[0016] The client terminal 100 is a terminal operated by an operator who creates design data using CAD, and the created design data is stored in the client terminal 100 and transmitted to the server 200 by management software (client) for storage.
[0017] The server 200 is a server that stores design data created by a CAD installed in the client terminal 100.
[0018] The server 200 stores management software (server) that is an application for managing the storage location and editing status of the CAD file.
[0019] Furthermore, design assistance software is installed in the client terminal 100. The design assistance software is software that functions as an add-on to CAD. This concludes the explanation of FIG.
[0020] Next, an example of the hardware configuration of various devices in the embodiment of the present invention will be described with reference to FIG.
[0021] FIG. 2 is a block diagram showing a hardware configuration applicable to the client terminal 100 and the server 200 shown in FIG.
[0022] In FIG. 2, a CPU 201 controls all devices and controllers connected to a system bus 204 .
[0023] In addition, the ROM 202 or external memory 211 stores the BIOS (Basic Input / Output System), which is the control program of the CPU 201, an operating system (hereinafter referred to as the OS), and various programs described below that are necessary to realize the functions executed by each server or each PC.
[0024] A RAM 203 functions as the main memory, work area, etc. of the CPU 201. The CPU 201 loads programs and the like required for executing processing from the ROM 202 or the external memory 211 into the RAM 203 and executes the loaded programs to realize various operations.
[0025] An input controller 205 controls inputs from an input device 209 such as a keyboard (KB) and a pointing device such as a mouse (not shown).
[0026] The input device is not limited to this, and may be a touch panel capable of detecting positions touched by multiple fingers, such as a multi-touch screen.
[0027] The user can issue various instructions by pressing (touching with a finger or the like) an icon, cursor, or button displayed on the touch panel.
[0028] A video controller 206 controls the display on a display device 210. The display device 210 is a CRT display, a liquid crystal display, or the like.
[0029] It may also be a display of a notebook computer integrated with the information processing device itself, or a projector. These are to be used by the administrator as needed.
[0030] Furthermore, the display 210 that can receive touch operations has the function of an input device 209 .
[0031] Reference numeral 207 denotes a memory controller, which controls access to an external memory 211 such as a hard disk (HD) that stores boot programs, various applications, font data, user files, edited files, various data, etc., a flexible disk (FD), or a CompactFlash (registered trademark) memory connected to a PCMCIA card slot via an adapter.
[0032] A communication I / F controller 208 connects to and communicates with external devices via a network (for example, the network 101 shown in FIG. 1) and executes communication control processing over the network. For example, communication using TCP / IP is possible.
[0033] The CPU 201 enables display on the display 210 by, for example, executing a process of expanding (rasterizing) an outline font into a display information area in the RAM 203. The CPU 201 also enables user instructions using a mouse cursor (not shown) or the like on the display 210.
[0034] Various programs described below for implementing the present invention are recorded in the external memory 211 and are executed by the CPU 201 by being loaded into the RAM 203 as required.
[0035] Furthermore, definition files and various information tables used when the above programs are executed are also stored in the external memory 211, and these will be described in detail later. This concludes the explanation of FIG.
[0036] Next, an example of the functional configuration of various devices in the embodiment of the present invention will be described with reference to FIG.
[0037] The client terminal 100 includes a file storage unit 301, a file editing unit 311, and the like.
[0038] The file storage unit 301 is a storage unit that stores CAD files.
[0039] The three-dimensional design data (three-dimensional CAD file) created and edited using a CAD file includes parts and assemblies made up of multiple parts.
[0040] In this embodiment, a file for an assembly is called an assembly file. Furthermore, the parts and assemblies that make up a design expressed by a 3D CAD file are collectively called components.
[0041] An assembly file is a file that represents an assembly made up of multiple parts by referencing those multiple parts. Details will be explained later in the explanation of Figure 4.
[0042] The file editing unit 311 is a processing unit that executes editing of a part in a CAD file being developed in CAD in accordance with an editing operation on the part. It is also a processing unit that executes editing of an assembly file in accordance with an editing operation on the assembly file. In other words, it is a functional unit that edits CAD files.
[0043] The selection screen display unit 321 is a functional unit that displays setting items such as dimensions and properties in a selectable manner.
[0044] The dimension selection receiving unit 322 is a functional unit that receives the selection of dimensions, for example, the selection of dimensions to be reused in the source file.
[0045] The property selection receiving unit 323 is a functional unit that receives the selection of a property, for example, a selection of a property to be reused in a source file.
[0046] The definition information output unit 324 is a functional unit that outputs information selected by the dimension selection receiving unit 322 and the property selection receiving unit 323 to the storage unit as a definition information file.
[0047] The definition information acquisition unit 325 is a functional unit that acquires the definition information output by the definition information output unit 324. In other words, it is a functional unit that acquires information that has been stored for reuse.
[0048] The change information display unit 326 is a display unit that displays how the target information will be changed based on the definition information acquired by the definition information acquisition unit 325. For example, it displays a screen that compares the information before and after the change.
[0049] The batch change screen display unit 327 is a functional unit that displays a screen for determining what to change based on the definition information acquired by the definition information acquisition unit 325. For example, it displays a screen that allows the user to select whether to change dimensions or properties, or both. The information to change is selected by selecting a function for changing the target information. For example, it displays a screen that allows the user to select whether to execute the dimension change function or the property change function.
[0050] The control unit 328 is a functional unit for changing the target information based on the definition information in accordance with the content of the instruction given by the batch change screen display unit 327. For example, the control unit 328 transmits the changed information to the CAD software and instructs the CAD software to execute the change.
[0051] The file editing unit 311 of the CAD software edits (changes) the information in the file in accordance with the instruction.
[0052] The server 200 includes a file storage unit 331. The file storage unit 331 is a storage unit that stores CAD files. This concludes the explanation of FIG.
[0053] Next, an example of assembly configuration information in an embodiment of the present invention will be described with reference to FIG.
[0054] The assembly configuration information 400 is information in an assembly file. The assembly configuration information stores which parts the assembly file references. In other words, it is information that indicates which parts make up an assembly.
[0055] The assembly configuration information 400 is composed of a record number 401, a level 402, a folder path 403, a file name 404, a configuration path 405, a type 406, a configuration name 407, and the like.
[0056] The record number 401 is identification information for each record in the assembly configuration information 400. The level 402 indicates the configuration hierarchy of each record. The folder path 403 indicates the folder path where the file of each record is stored.
[0057] The file name 404 indicates the file name of the assembly file or part file indicated by the processing record.
[0058] The configuration path 405 indicates the reference relationship between an assembly file and a part file, and between assembly files. For example, a value of Null is registered as the value of the configuration path 405 located at the apex of the reference relationship.
[0059] The assembly file at the top of the reference relationship is called the top assembly. Specifically, the record with record No. 401=1 shown in the assembly configuration information 400 in FIG. 4 corresponds to this.
[0060] The configuration path of the assembly file (Assy1), which is a file that is directly referenced by the top assembly (TopAssy), is TopAssy.
[0061] This indicates that Assy1 is directly referenced by TopAssy. Specifically, this corresponds to the record No. 401=2 shown in the assembly configuration information 400 in FIG.
[0062] Furthermore, the configuration path of the part file (Part1) that TopAssy indirectly references via Assy1 is TopAssy / Assy1.
[0063] This indicates that Part1 is directly referenced by Assy1 and indirectly referenced by TopAssy. Specifically, this corresponds to records No. 3, 4, and 5 shown in the assembly configuration information 400 in FIG.
[0064] The type 406 stores the type of the processed file. The type indicates whether the file indicated by each record is an assembly file (Assy) or a part file (Part). Whether the file is an assembly file or a part file is determined by the file extension.
[0065] The configuration name 407 is identification information for a variation of the file indicated by the file name 404. Variations are stored and managed within a single file. A variation refers to, for example, a right-handed version or a left-handed version of a part of a file.
[0066] For example, in a file with file name 404 = Part2, there are variations of the right-hand version and the left-hand version of the 3D part represented by Part2, and these names are stored as configuration names. This concludes the explanation of Figure 4.
[0067] The editing history of the design data is stored in the CAD file. For example, if an assembly file is opened and a part file in the assembly file is edited, the editing history information is stored in the assembly file.
[0068] Edit history information, for example, is stored and managed in chronological order as a list of features. A feature is the name of a command that edits a part. Feature information stores what type and parameters of a feature were applied to which part of which part.
[0069] An example of feature information in an embodiment of the present invention will be described with reference to FIG.
[0070] The feature information 500 includes an ID 501, a feature name 502, a feature type 503, an application location 504, a color scheme (color information) 505, a last edit date and time 506, a last editor 507, and the like.
[0071] An ID 501 indicates an ID for uniquely identifying a feature. A feature name 502 indicates the name of each feature. A feature type 503 indicates the type (kind) of the feature.
[0072] The application location (element) 504 indicates the element to which the feature is applied.
[0073] The elements in a CAD file are, for example, points, lines, surfaces, and other elements on a part.
[0074] The color scheme 505 indicates information about the color settings of the feature. The color set in the color scheme 505 is used to color the parts of the part that are deformed or generated by the feature.
[0075] The date and time when the feature was last edited is registered in last edit date and time 506. The username of the user who last edited the feature is registered in last editor 507. This concludes the explanation of FIG.
[0076] Next, an overview of definition output processing in an embodiment of the present invention will be described with reference to Fig. 6. Note that the processing of this flowchart is executed by the CPU 201 of the client terminal 100, which is one of the information processing devices, using the functions of each functional unit.
[0077] In step S601, the client terminal 100 executes a process of outputting dimension definitions, for example, a process of outputting dimension information from existing design data that is to be reused for other design data to a definition file and storing it.
[0078] In step S602, a property definition output process is executed, which is, for example, a process of outputting property information from existing design data that is to be reused for other design data to a definition file and storing it.
[0079] The above is the processing in Fig. 4. Details of the output processing of the dimension definition (step S601) will be described later in the description of Fig. 7. Details of the output processing of the property definition (step S602) will be described later in the description of Fig. 8.
[0080] Next, the output process of the dimension definition will be described in detail with reference to Fig. 7. The process of this flowchart is executed by the CPU 201 of the client terminal 100, which is one of the information processing devices, using the functions of each functional unit.
[0081] In step S701, the client terminal 100 displays a dimension definition creation / editing screen (shown as 1300 in FIG. 13).
[0082] 13, a description will be given of a dimension definition creation / editing screen 1300. This screen is composed of a file name 1301, a dimension definition model ID 1302, a definition file 1303, a display section 1304, a selection receiving section 1305, a "Save" button 1306, etc.
[0083] The file name 1301 is a display section that acquires and displays the file name of the model (active model) that is active on the CAD software. The file name here is, for example, the file name 404 in Fig. 4, which is also called the component name. The file name is assumed to be unique.
[0084] In this embodiment, the file name is registered in the system setting file of the design support tool, and the model identification information (model ID) is registered in the system setting file in association with the file name.
[0085] There are two types of model IDs: "dimension definition model ID" and "property definition model ID." These are identification information used by the dimension change function and property change function of the design support software, respectively.
[0086] The process of associating the file name with the dimension definition model ID and the property definition model ID is executed by the CPU 201 of the client terminal 100 using the ID setting function of the design assistance software, and is stored in the external memory.
[0087] When associating, the ID setting screen 1600 in Fig. 16 is displayed, and each ID is created and stored in response to user operation. Specifically, the file name of each component part in the active file is obtained and displayed in a component part list 1601. Then, input of values for a dimension definition model ID 1602 and a property definition model ID 1603 is accepted. When a "Set" button 1604 is pressed, the model name in 1601 and the values (IDs) entered in 1602 and 1603 are associated with each other and registered and stored in the system setting file.
[0088] An example of a system setting file is shown in 1460 in Fig. 14. In the system setting file of the present invention, a file name 1461, a folder path of the file, a dimension definition model ID 1462, and information (folder path 1463) about the location where dimension information (dimension definition information) registered to be reused from the file to which the dimension definition model ID is set is stored in association with each other. The file name of the file indicated by the path (a definition file storing dimension definition information) is stored at the end of the folder path.
[0089] Also, file name 1461, property definition model ID 1464, and information (folder path 1465) of the location where information on the property (property definition information) registered to be reused from the file to which the property definition model ID is set is stored in association with each other. The file name of the file indicated by the path (definition file storing property definition information) is stored at the end of the folder path. Return to the explanation of FIG. 13.
[0090] The dimension definition model ID 1302 is a display unit that acquires and displays the value of the dimension definition model ID (1462) stored in the system setting file in association with the active model.
[0091] Specifically, the acquired file name specified in 1301 is acquired from the file name 1461 in the system setting file 1460, and the dimension definition model ID 1462 corresponding to the file name is acquired and displayed.
[0092] The definition file 1303 displays the dimension definition folder path (folder path 1463) defined in the system setting file.
[0093] A display section 1304 displays a list of dimensions of the active model in a selectable manner.
[0094] A selection receiving section 1305 is a check box that receives the selection of dimension information to be set (registered) in the dimension definition file whose folder path is displayed in 1303 from among the displayed dimensions.
[0095] An example of dimension information set in the active model is shown as dimension information 1400 in Fig. 14. 1401 is the dimension name, and display dimension name 1402 is the dimension name displayed on the CAD software. There are multiple types of dimension names, such as height, width, and depth. Value 1403 is the value (setting information) of the dimension at the location indicated by the dimension name.
[0096] The "save" button 1306 is a button for saving the dimensions selected and accepted by the selection accepting section 1305 as dimension definitions (information on dimensions to be reused).
[0097] Returning to the description of Fig. 7, in step S702, the client terminal 100 selects a model whose dimensions are to be displayed on the display unit 1304. Specifically, the active model on the CAD software is identified and selected, and the file name is displayed in 1301.
[0098] In step S703, the client terminal 100 displays on the display unit 1304 a list of dimensions of the model selected in step S702.
[0099] Here, the system setting file 1460 is referenced, and the dimension definition corresponding to the file name 1461 of the active model (the dimension definition file corresponding to the dimension definition model ID 1462 corresponding to the active model) is identified from the folder path 1463. The lines of dimension names whose values are already registered in the dimension definition file are displayed with a background color that is different from the background color of unregistered dimensions.
[0100] In this way, by distinguishing and displaying dimensions that have already been registered as information to be reused from unregistered dimensions, it is possible to easily check whether any dimensions have been omitted from registration.
[0101] It will also be possible to easily confirm whether the value of each dimension name to be registered in the dimension definition file will be newly registered as a dimension with no registered value, or whether it will be registered by overwriting an already registered value.
[0102] For example, a user can check this identification display, check the values for only the unregistered dimensions (dimension names), and register them, thereby registering values to the dimension definition without the need to check unnecessary values (values that have already been registered in the dimension definition), which has the effect of making the registration process more efficient.
[0103] Furthermore, dimensions that have already been registered in the dimension definition file are displayed in the selection receiving section 1305 in a selected state.
[0104] This reduces the time and effort required to reselect dimensions that have already been selected for registration in a dimension definition (dimension values of dimension names that the user has decided should be reused).
[0105] In addition, there is an effect of preventing omission of selection, such as updating a dimension definition file without selecting a dimension with a dimension name that the user once decided should be reused.
[0106] In step S704, the client terminal 100 accepts a click operation or the like on the selection accepting section 1305 to accept the selection of dimensions.
[0107] In step S705, the client terminal 100 accepts pressing of the "Save" button 1306. Then, the information on the selected dimensions is output to the dimension definition file stored in the path displayed in 1303, and is stored in the storage unit.
[0108] For example, as shown in 1410 in Fig. 14, only selected dimensions from the dimension information 1400 are stored as dimension definition information. In other words, 1410 is an example of a dimension definition file. The above is a detailed explanation of the output process of the dimension definition in Fig. 7.
[0109] Next, details of the property definition output process in the embodiment of the present invention will be described with reference to Fig. 8. Note that the process of this flowchart is executed by the CPU 201 of the client terminal 100, which is one of the information processing devices, using the functions of each functional unit.
[0110] In step S801, the client terminal 100 displays a property definition creation / editing screen (shown as 1310 in FIG. 13).
[0111] 13, the property definition creation / editing screen 1310 will be described. This screen is composed of a file name 1311, a property definition model ID 1312, a definition file 1313, a display section 1314, a selection receiving section 1315, a "Save" button 1316, etc.
[0112] The file name 1311 is a display section that acquires and displays the file name of the model that is active on the CAD software (active model).
[0113] The property definition model ID 1312 is a display unit that acquires and displays the value of the property definition model ID (1464) stored in the system setting file in association with the active model.
[0114] The definition file 1313 displays a folder path 1465 defined in the system setting file 1460 .
[0115] The display unit 1314 displays a list of properties of the active model in a selectable manner. The selection receiving unit 1315 is a check box that receives the selection of property information (setting information) to be set (registered) in the property definition file from among the displayed properties.
[0116] An example of property information set in an active model in a design data file is shown in property information 1420 in Fig. 14. 1421 is the property name. Type 1422 indicates the type of property that can be set for the property. For example, "text," "date," or "integer." Value 1423 is the value set for the property and indicates the content of the property.
[0117] The "save" button 1316 is a button for saving the property selected by the selection receiving section 1315 as a property definition.
[0118] Returning to the description of Fig. 8, in step S802, the client terminal 100 selects a model whose properties are to be displayed in a list on the display unit 1314. Specifically, the active model on the CAD software is identified and selected, and its file name is displayed in 1311.
[0119] In step S803, the client terminal 100 displays on the display unit 1314 a list of properties of the model selected in step S802.
[0120] Here, the system setting file 1460 is referenced, and the property definition corresponding to the active model (the property definition file corresponding to the property definition model ID 1464 corresponding to the active model) is identified from the folder path 1465.
[0121] In this way, by distinguishing and displaying registered properties as information to be reused from unregistered properties, it is possible to easily check whether any properties have been omitted from registration.
[0122] It is also possible to easily check whether the value of each property name to be registered in the property definition file will be newly registered as a property with no registered value, or will be registered by overwriting an already registered value.
[0123] For example, a user can check this identification display, check the values of only the unregistered properties (property names), and register them, thereby registering values to the property definition without the need to check unnecessary values (values that have already been registered in the property definition), which has the effect of making the registration process more efficient.
[0124] Furthermore, properties that have already been registered in the property definition file are displayed in a selected state in the selection receiving section 1315.
[0125] This reduces the effort required to reselect properties that have already been selected to be registered in the property definition (property values of property names that the user has decided should be reused).
[0126] In addition, there is an effect of preventing omission of selection, such as updating a property definition file without selecting a property name value that the user once decided should be reused.
[0127] In step S804, the client terminal 100 accepts a click operation or the like on the selection accepting section 1315, thereby accepting the selection of a property.
[0128] In step S805, the client terminal 100 accepts pressing of the "Save" button 1316. Then, the information on the selected property is output to a property definition file, and stored in the storage unit.
[0129] For example, as shown in 1430 in Fig. 14, only the information on the selected property from the property information 1420 is stored as property definition information. In other words, 1430 is an example of a property definition file. The above is a detailed explanation of the property definition output process in Fig. 8.
[0130] As explained above, the selection, identification, and output of definition information (information to be reused) for each of dimensions and properties are completed through the processing in FIGS.
[0131] Next, an overview of definition application processing in an embodiment of the present invention will be described with reference to Fig. 9. Note that the processing of this flowchart is executed by the CPU 201 of the client terminal 100, which is one of the information processing devices, using the functions of each functional unit.
[0132] In step S901, the client terminal 100 performs a setting process for changing dimensions. Details of this process (step S901) will be described later in the description of FIG.
[0133] In step S902, the client terminal 100 performs a property change setting process. Details of this process (step S902) will be described later in the description of FIG.
[0134] In step S903, the client terminal 100 changes the dimensions and properties all at once based on the settings made in steps S901 and S902. Details of this process (step S903) will be described later in the description of Fig. 12. This concludes the description of Fig. 9.
[0135] First, details of the setting process for dimension change (shape change due to dimension change) in the embodiment of the present invention will be described with reference to Fig. 10. The process of this flowchart is executed by the CPU 201 of the client terminal 100, which is one of the information processing devices, using the functions of each functional unit.
[0136] In step S1001, the client terminal 100 displays the shape change screen 1500 (FIG. 15).
[0137] The configuration of the shape modification screen 1500 will now be described with reference to Fig. 15. The shape modification screen 1500 is made up of a definition file designation section 1501, a model configuration display section 1502, a dimension comparison display section 1503, a "Settings complete" button 1504, and the like.
[0138] The definition file designation unit 1501 is a functional unit that accepts designation of a desired definition file from among the definition files stored in the paths indicated in the folder paths 1463 in FIG.
[0139] The model configuration display section 1502 is a display section that displays the configuration (list of component parts) of the active file at the time when the shape modification screen 1500 is displayed in a selectable manner.
[0140] The dimension comparison display section 1503 displays, among the dimension names of the dimensions of the model (e.g., part) selected and accepted in the model configuration display section 1502, dimension names that match the dimension names whose dimension values are registered in the definition file selected and accepted in 1501. It is also a display section that correlates (makes the correspondence recognizable) the values of the dimensions indicated by the dimension names currently set in the model selected and accepted in the model configuration display section 1502 with the values registered in the definition file selected and accepted in 1501, allowing them to be checked and compared.
[0141] The "Settings Complete" button 1504 is a button for storing the dimension values (values (after change)) stored in the dimension definition file displayed in the dimension comparison display area 1503 in association with the file name of the part, in order to apply the dimension values (values (after change)) to the model (e.g., part) selected in 1502. This completes the description of the configuration of the shape modification screen 1500.
[0142] Returning to the description of Fig. 10, in step S1002, the client terminal 100 accepts the specification of a definition file. For example, it accepts a selection operation of a definition file stored in the client terminal 100. Then, the specified and selected file is read and expanded on RAM.
[0143] In step S1003, the client terminal 100 accepts the selection of a model. Here, the model selected by a selection operation such as a mouse click among the models displayed in the model configuration display section 1502 is the model whose selection has been accepted.
[0144] In step S1004, the client terminal 100 displays the dimension names that are defined in the definition file whose specification was accepted in step S1002 and that are included in the model whose selection was accepted in step S1003. Specifically, the dimension names are displayed in a list in the "dimension name" item of the dimension comparison display area 1503.
[0145] In step S1005, the client terminal 100 displays the currently set dimension value for each dimension in the model selected in step S1003 in "Value (Current)." Also, the value of each dimension in the definition file specified in step S1002 is displayed in "Value (Changed)" as the changed dimension.
[0146] In step S1006, the client terminal 100 accepts pressing of the "Settings Complete" button 1504. That is, an instruction to change the dimension value of each dimension name displayed in the dimension comparison display area 1503 from "Value (before change)" to "Value (after change)" and to store the changed value is accepted.
[0147] In step S1007, the client terminal 100 temporarily stores the value of "Value (after change)" in the storage area in association with each dimension name of the model and the file name selected in 1502. This concludes the explanation of FIG.
[0148] As described above, according to the process of FIG. 10, it is possible to easily confirm which dimension in which component has which dimension name is an item for which a value should be reused from another component.
[0149] In addition, it is possible to easily check what values are registered as dimension values to be reused for each dimension.
[0150] It is also possible to check the dimension values before and after the reuse, and how the values of each dimension change.
[0151] This makes it easier for the user to determine whether or not to reuse the dimensions.
[0152] That is, it is possible to provide a mechanism that allows settings to be easily applied to design data.
[0153] Next, details of the property change setting process in the embodiment of the present invention will be described with reference to Fig. 11. Note that the process of this flowchart is executed by the CPU 201 of the client terminal 100, which is one of the information processing devices, using the functions of each functional unit.
[0154] In step S1101, the client terminal 100 displays the property change screen 1510 (FIG. 15).
[0155] The configuration of the property change screen 1510 will now be described with reference to Fig. 15. The property change screen 1510 is made up of a definition file specification section 1511, a model configuration display section 1512, a property comparison display section 1513, a "Settings complete" button 1504, and the like.
[0156] The definition file designation unit 1511 is a functional unit that accepts designation of a desired definition file from among the definition files stored in the paths indicated in the folder paths 1465 in FIG.
[0157] The model configuration display section 1512 is a display section that displays the configuration (list of component parts) of the active file at the time when the property change screen 1510 is displayed in a selectable manner.
[0158] The property comparison display section 1513 displays, among the properties of the model (e.g., a part) whose selection has been accepted in the model configuration display section 1512, the property names that match the property names whose values are registered in the definition file whose specification has been accepted in 1511. It is also a display section that displays, in association with each other, the values indicated by the property names that are currently set in the model whose selection has been accepted in the model configuration display section 1512 and the values registered in the definition file whose specification has been accepted in 1511, so that they can be checked and compared.
[0159] The "Settings Complete" button 1514 is a button for storing the property value (value (after change)) stored in the property definition file displayed in the property comparison display area 1513 in association with the file name of the component, in order to apply the property value (value (after change)) to the model (e.g., component) selected in 1512. This completes the description of the configuration of the property change screen 1510.
[0160] Returning to the description of Fig. 11, in step S1102, the client terminal 100 accepts the specification of a definition file, for example, accepts a selection operation of a definition file stored in the client terminal 100. Then, the specified and selected file is read and expanded on RAM.
[0161] In step S1103, the client terminal 100 accepts the selection of a model. Here, the model selected by a selection operation such as clicking a mouse among the models displayed in the model configuration display section 1512 is considered to be the model whose selection has been accepted.
[0162] In step S1104, the client terminal 100 displays the property names that are defined in the definition file whose specification was accepted in step S1102 and that are included in the model whose selection was accepted in step S1103. Specifically, the property names are displayed in a list in the "Property Name" field of the property comparison display area 1513.
[0163] In step S1105, the client terminal 100 displays the value of each property name in the model selected in step S1103 in "Value (Current)." Also, the value of each property name in the definition file specified in step S1102 is displayed in "Value (Changed)" as the changed value.
[0164] In step S1106, the client terminal 100 accepts pressing of the "Settings Complete" button 1504. That is, the client terminal 100 accepts an instruction to change the value of each property name displayed in the property comparison display area 1513 from "Value (before change)" to "Value (after change)" and to store the changed value.
[0165] In step S1107, the client terminal 100 temporarily stores the value of "Value (after change)" in the storage area in association with each property name of the model and the file name of the component part selected in 1512. This concludes the explanation of FIG. 11.
[0166] As described above, according to the process of FIG. 11, it is possible to easily check which property name in which component is an item for which a value should be reused from another component.
[0167] Furthermore, it is possible to easily check what values are registered as property values to be reused for each property.
[0168] You can also check the property values before and after the reuse to see how the values of each property change.
[0169] This makes it easier for the user to determine whether or not to reuse the property.
[0170] That is, it is possible to provide a mechanism that allows settings to be easily applied to design data.
[0171] Next, details of the batch execution process (processing for batch executing changes to dimensions and properties) in the embodiment of the present invention will be described with reference to Fig. 12. Note that the process of this flowchart is executed by the CPU 201 of the client terminal 100, which is one of the information processing devices, using the functions of each functional unit.
[0172] In step S1201, the client terminal 100 displays the batch execution screen 1520 (FIG. 15).
[0173] The configuration of the batch execution screen 1520 will now be described with reference to Fig. 15. The batch execution screen 1520 is made up of a save destination designation section 1521, a function list display section 1522, an "execute" button 1523, and the like.
[0174] The save destination designation section 1521 is a functional section that accepts designation of a save destination for saving a file that is generated or updated by executing a function selected in the function list display section 1522 .
[0175] The function list display section 1522 is a display section that displays a list of functions that the design assistance software has in a selectable manner. For example, a shape change (dimension change) function and a property change function are also displayed in the list in a selectable manner.
[0176] The "Execute" button 1523 is a button for executing a function that has been checked in the "Execute" checkbox in the function list display section 1522, i.e., a function that has been selected to be executed. The above is the description of the configuration of the batch execution screen 1520.
[0177] Returning to the description of Fig. 12, in step S1202, the client terminal 100 accepts a designation of a destination for saving the file, for example, a designation of the URL of a folder on the external memory of the client terminal 100.
[0178] In step S1203, the client terminal 100 accepts the selection of a function to be executed from among the functions in the function list display section 1522. Specifically, by accepting an operation to check the "execute" checkbox corresponding to the "function name" in the function list display section 1522, the client terminal 100 determines that the function has been selected as the function to be executed.
[0179] In step S1204, the client terminal 100 accepts the pressing of the "execute" button, that is, accepts an instruction to execute the selected functions all at once.
[0180] In step S1205, the client terminal 100 accepts the selection in step S1203 and executes the function for which the "execute" checkbox is checked.
[0181] For example, if the shape change (dimension change) function is checked, the selection is accepted in step S1003 of FIG. 10, and the dimension value of the dimension name temporarily saved in step S1007 is changed to the value (after change) stored in step S1007.
[0182] Also, for example, if the property change function is checked, the selection is accepted in step S1103 of Fig. 11, and the value of the property name temporarily saved in step S1107 is changed to the value (after change) stored in step S1107. This concludes the explanation of Fig. 12.
[0183] 12, the functions to be executed can be confirmed from a list, selected, and executed on the batch execution screen 1520. This reduces the time and effort required to execute functions compared to executing each function one by one.
[0184] As shown in FIGS. 9 to 12, in the present invention, first, the screens for each function of the design assistance software (e.g., 1500 and 1510 in FIG. 15) are displayed in order, and after accepting the settings and operations for each function on each screen, the functions are not executed when operating each screen, and finally, it is possible to select the functions to be executed all at once.
[0185] This allows you to see at a glance, for example, what functions will be executed (whether settings will be changed or updated by that function).
[0186] Therefore, it is possible to check at a glance whether any functions have been omitted, that is, whether any settings have been updated or changed, and then change or update the settings.
[0187] This makes it possible to provide a mechanism that allows settings to be easily applied to design data.
[0188] Next, with reference to 1610 in FIG. 16, the rearrangement of component parts and the changes in dimensions and properties after the rearrangement will be described.
[0189] The design support software has a function for changing dimensions and properties as well as rearranging component parts.
[0190] The settings for the component recombination function are determined via a component recombination screen 1610 in FIG.
[0191] Specifically, the CPU 201 of the client terminal 100 displays the component recombination screen 1610 immediately before step S901 in FIG. 9, for example.
[0192] The component recombination screen 1610 is configured from components 1612, configurations 1613, processes 1614, files 1615, configurations 1616, a "settings complete" button 1617, and the like, all of which are displayed in a component configuration display section 1611.
[0193] The component parts 1612 is a display section that displays a list of file names of the component parts of the active file. The configuration 1613 is a display section that displays the configuration of each component part.
[0194] The process 1614 is a specification receiving section that receives a specification of what process to execute for the component part 1612. For example, it is a pull-down type item, and "replace," "reference switch," "add," "delete," etc. can be selected.
[0195] The file 1615 is a specification receiving unit that receives the specification of a file to be used when applying the process selected in the process 1614. For example, a CAD file stored in the client terminal 100 or the server 200 can be specified as the file.
[0196] The file 1615 is only enabled when "replace" or "add" is selected in the process 1614. This is because, for example, when the process 1614 is "delete," the component part 1612 is deleted, and there is no need to specify a new file. To prevent unnecessary selection processing, the file is disabled unless the target item is selected in the process 1614.
[0197] The configuration 1616 is enabled when the process 1614 is "replace," "switch reference," or "add." As the name suggests, this is an operation section for replacing the component 1612 and configuration 1613 with the configuration 1616, switching the reference, or adding. By entering the configuration name, it is possible to specify the configuration to be replaced, the configuration to be switched to, or the configuration to be added. The "Settings Complete" button 1617 is a button for temporarily storing the processing content (1614) and processing settings (1615-1616) of each component part in the external memory of the client terminal 100 or the server 200 in order to execute the processing 1614 according to the settings specified in each item of the component configuration display section 1611.
[0198] When the "Settings Complete" button 1617 is pressed, the CPU 201 of the client terminal 100 shifts the process to step S901 in FIG. 9 and starts the process in FIG.
[0199] In addition, the model configuration display sections (1502, 1512) in each screen of FIG. 15 to be displayed hereafter will display a list of component configurations when process 1614 is applied to component 1612 so that dimensions and properties can be changed for the component after the process specified on component recombination screen 1610 has been applied.
[0200] For example, according to the component recombination screen 1610 in FIG. 16, TopAssy1 to Part2 displayed in the component 1612 <1> Part 1 of <1> are replaced with the files designated in 1615 and 1616 and displayed in the model configuration display areas 1502 and 1512.
[0201] Also, Part 1 <2> The model configuration display areas 1502 and 1512 display the configuration as if it had been reference-switched from ConfC to ConfB, and subsequent setting and execution of property and dimension changes are performed on ConfB.
[0202] Also, Part 2 <1> are treated as having been deleted and are not displayed in the model configuration display areas 1502 and 1512 on each screen to be displayed later.
[0203] On the other hand, Part 2 <1> The file (file specified in 1615) for which an additional item is specified in 1614 and which is displayed in the line immediately below is treated as a newly added file. In other words, when added, the specified part is displayed in the model configuration display areas 1502 and 1512 of each screen to be displayed later.
[0204] The process specified in process 1614 is actually executed after the "Execute" button 1523 is pressed on the batch execution screen 1520 and before the dimension and property change process is performed in step S1205. The dimension and property changes are then applied to and executed on the file after process 1614 has been executed.
[0205] As described above, according to the present invention, for the functions of adding, changing, and deleting the referenced file itself, an operation screen is displayed so that settings such as changes to dimensions and properties can be applied to the component parts list after the function has been executed, even before the function is executed.
[0206] This makes it possible to easily specify settings to be applied to subsequent files even when files themselves are added, changed, or deleted.
[0207] Furthermore, even when a file itself is added, changed, or deleted, a mechanism can be provided that allows the specified settings to be easily applied to subsequent files.
[0208] As described above, according to the present invention, it is possible to provide a mechanism that allows settings to be easily applied to design data.
[0209] In the above-described embodiment, one dimension value (e.g., value 1403) is stored for one dimension name, but multiple dimension values may be stored in association with one dimension name. For example, there may be a set value that is set and stored by the user operating and specifying the CAD, and a measurement value (evaluation value) obtained by measuring the completed shape using the CAD's dimension measurement function. In this way, when multiple dimension values are stored in association with one dimension name, both dimension values may be displayed in 1304 of FIG. 13.
[0210] Then, in 1304, a check box may be placed and displayed next to each cell in which each dimension value is displayed, and the dimension value that receives the operation of checking the check box may be selected and stored in a temporary area so that the dimension value can be output to the dimension definition file.
[0211] In addition, which type of dimension value among multiple dimension values (e.g., set value and measured value) should be output to the dimension definition file may be stored in a setting file in advance, and the dimension value that is set to be prioritized in the setting file may be output to the dimension definition file in S706 of Figure 7.
[0212] Furthermore, in the embodiment of the present invention, the configuration has been described in which the CPU of the client terminal 100 executes the processing of each flowchart in Figures 6 to 12 using various functions (e.g., functions 301, 311, 321 to 328 in Figure 3) provided in the client terminal 100, but the functions may be provided in the server 200, and the CPU of the server 200 may be configured to execute the processing of each flowchart in Figures 6 to 12 using the functions provided in the server 200.
[0213] Also, some of the processes may be executed by the client terminal 100, and some may be executed by the server 200. For example, the processes of steps S701 to S705 in Fig. 7 may be executed by the client terminal 100, and the server 200, having received definition file information from the client terminal 100, may output and store the process of step S706 in its own external memory. In this case, the information required to execute each process and the information on the execution results are stored and held by the client terminal 100 and the server 200 transmitting and receiving information and synchronizing the information.
[0214] Although one embodiment has been described above, the present invention can be embodied as, for example, a system, an apparatus, a method, a program, a recording medium, etc. Specifically, the present invention may be applied to a system made up of multiple devices, or may be applied to an apparatus made up of a single device.
[0215] Furthermore, the program of the present invention is a program that enables a computer to execute the processing methods of the flowcharts shown in Figures 6 to 12, and the storage medium of the present invention stores a program that enables a computer to execute the processing methods of Figures 6 to 12. Note that the program of the present invention may be a program for each processing method of each device.
[0216] As described above, it goes without saying that the object of the present invention can also be achieved by supplying a recording medium on which a program that realizes the functions of the above-mentioned embodiments is recorded to a system or device, and having the computer (or CPU or MPU) of that system or device read and execute the program stored on the recording medium.
[0217] In this case, the program itself read from the recording medium will realize the novel functions of the present invention, and the recording medium on which the program is recorded will constitute the present invention.
[0218] Examples of recording media for supplying the program include flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, DVD-ROMs, magnetic tapes, non-volatile memory cards, ROMs, EEPROMs, and silicon disks.
[0219] Furthermore, it goes without saying that not only are the functions of the above-mentioned embodiments realized by the computer executing a program it has read, but also cases are included in which an OS (operating system) running on the computer performs some or all of the actual processing based on the instructions of the program, and the functions of the above-mentioned embodiments are realized through that processing.
[0220] Furthermore, it goes without saying that this also includes cases where a program read from a recording medium is written into a memory provided on a function expansion board inserted into a computer or a function expansion unit connected to the computer, and then a CPU or the like provided on the function expansion board or function expansion unit performs some or all of the actual processing based on the instructions of the program code, thereby realizing the functions of the above-mentioned embodiments.
[0221] Furthermore, the present invention may be applied to a system consisting of multiple devices, or to a device consisting of a single device. It goes without saying that the present invention can also be applied to a system or device that is achieved by supplying a program to the system or device. In this case, the system or device can enjoy the effects of the present invention by reading a recording medium that stores a program for achieving the present invention into the system or device.
[0222] Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or device can enjoy the effects of the present invention. Note that the present invention also includes configurations that combine the above-mentioned embodiments and their modified examples. [Explanation of symbols]
[0223] 100 client terminals 101 Network 200 servers
Claims
1. an information processing device that stores first design data and second design data; a selection receiving means for receiving a selection of setting information set in the first design data; a control means for controlling the setting information selected by the selection receiving means to be applied to the second design data; A program to make it function as such.
2. causing the selection receiving means to function as a means for receiving a selection of the setting item for which the setting information is set; 2. The program according to claim 1, for causing the control means to function as a means for controlling the application of setting information set in a setting item in the first design data, the selection of which has been accepted by the selection accepting means, to a setting item in the second design data corresponding to the setting item in the first design data.
3. 3. The program according to claim 1, wherein the setting information is dimension information and / or property information set in the first design data.
4. the selection receiving means functions as a means for receiving a selection of a dimension value to be applied to the second design data from among a plurality of dimensions including width, height, and depth dimensions set in the first design data; 4. The program according to claim 3, wherein the control means applies the dimension value of the dimension selected by the selection receiving means as the dimension value of the dimension corresponding to the selected dimension in the second design data.
5. The information processing device A program described in any one of claims 1 to 4, which is intended to function as a display means for recognizably displaying the correspondence between the setting information selected by the selection receiving means and the setting information currently set in the second design data at the location to which the setting information is applied.
6. The information processing device causing the setting information selected by the selection receiving means to function as an operation screen display means for displaying an operation screen for applying the setting information to the second design data; 6. The program according to claim 1, for causing the control means to function as a control means for applying the setting to the second design data by accepting an operation on the operation screen.
7. The program according to claim 6, characterized in that the operation screen is a screen capable of accepting a selection of which type of setting information the selection of which is accepted by the selection accepting means is to be applied to.
8. The information processing device functioning as a receiving means for receiving a selection of another design object in order to replace the component in the second design data with the other design object; A program according to any one of claims 1 to 7, for causing the control means to function as a means for controlling the application of the setting information selected by the selection receiving means to the other design object selected by the receiving means.
9. The information processing device functioning as an output means for outputting the setting information selected by the selection receiving means to a definition file; The control unit reads the definition file and stores the setting information specified by the definition file in the 9. The program according to claim 1, which functions as a control means for applying the second design data to the second design data.
10. An information processing device that stores first design data and second design data, a selection receiving means for receiving a selection of setting information set in the first design data; a control means for controlling the setting information selected by the selection receiving means to be applied to the second design data; An information processing device comprising:
11. A control method for an information processing device that stores first design data and second design data, comprising: a selection receiving step in which a selection receiving means receives a selection of setting information set in the first design data; a control step in which a control unit controls the setting information selected by the selection receiving unit to be applied to the second design data; A control method comprising:
12. An information processing system including a storage device that stores first design data and an information processing device that stores second design data, a selection receiving means for receiving a selection of setting information set in the first design data; a control unit that controls the setting information selected by the selection receiving unit to be applied to the second design data; An information processing system comprising:
Citation Information
Patent Citations
Cad system and design supporting method
JP2000035987A
Products structure management system and program
JP2004110155A
Three-dimensional CAD component data configuration generation device and generation method
JP2007133559A
Information processing device, information processing system, control method and program thereof
JP2019008391A
Information processor, control method therefor, program, and storage medium
JP2005352678A