JP6802500B2 - Information processing equipment, information processing system, its control method and program - Google Patents

Description

The present invention relates to an information processing device, an information processing system, a control method and a program thereof.

In the manufacturing industry, a three-dimensional CAD file that is product information designed by a designer is generally stored in a dedicated data server or a PDM system (Product Data Management system = data management system). In particular, PDMs often have not only the storage of electronic data, but also various additional information and their revision information, as well as functions such as an authorization system and an approval system, which ensure the confidentiality, integrity, and availability of design information. In recent years, it has been operated at design sites of various companies as a system for realizing securing without burden.

Further, in order to ensure the integrity, for example, in order to create design information to be stored in PDM, a technique for consistently creating a tree configuration using assembly and component data as constituent elements before creating a 3D CAD file. Has been published (for example, Patent Document 1)

JP-A-2007-115164

By the way, from the viewpoint of the confidentiality of the data in the PDM, there is a business operation that allows only a specific worker, not the designer, to save the three-dimensional CAD file in the PDM.

In this case, the designer does not create the 3D CAD file on the server designated by the PDM as the storage / registration location of the 3D CAD file, but instead creates the 3D CAD file on his / her own personal PC. And register the 3D CAD file in the PDM, the 3D CAD file is passed to a worker who has the authority to access the PDM, and the registration work is requested.

The number of files for saving a three-dimensional CAD file for one product varies from time to time, but in many cases, it may reach 1,000 to 10,000 points (data capacity is several KB to several tens of MB per file). When data of this scale is saved in a PDM (for example, an external device that stores actual data managed by the PDM) by an operation on the OS of the worker's PC (for example, cut and paste), for example, the relevant Some 3D CAD files may be affected by factors such as the communication load between the PC / server (PDM) due to the number of files and the total data capacity of the files, and the upper limit of the number of files that can be moved at one time set in the OS. It may not be saved to PDM normally.

However, even if some data is not saved, there is no means to notify the worker who has performed the work, so that the worker recognizes that his / her work has been completed. That is, for example, when trying to browse a 3D CAD file that should have been saved in the PDM at a later date, the above-mentioned data that could not be saved cannot be detected, so that the design information remains insufficient. It can be viewed only in the state of.

In order to avoid this, when the worker finishes saving (transmitting) data to PDM, for example, by viewing the file saved (transmitted) in PDM by a 3D CAD application, the intended data configuration It is sufficient to confirm whether or not can be constructed by the stored data in the PDM, but if the above-mentioned worker is not in charge of the data design work, the 3D CAD application is not necessarily set on the worker's PC. It is not always done. Further, when there is a large amount of data constituting the file, in order to view the file, the worker's PC must have hardware that can withstand the viewing of the file (data call, drawing process for that purpose). Even if the file can be opened, it may take several minutes just to open it, and it takes time to confirm whether the 3D CAD file is correctly configured. It is very troublesome because it requires.

An object of the present invention is to allow the user to easily confirm the comparison result between the structure of the transmitted file and the structure of the file before transmission.

The information processing device of the present invention is an information processing device capable of communicating with a server that stores a file, and is a transmission means for transmitting the file to the server and a file that has been transmitted to the server by the transmission means. A first assembly acquisition means for acquiring an assembly of a file stored in the information processing device, a second assembly acquisition means for acquiring an assembly of a transmitted file transmitted by the transmission means from the server, and the above. A comparison means for comparing the first assembly acquired by the first assembly acquisition means and the second assembly acquired by the second assembly acquisition means, and a comparison result compared by the comparison means are displayed on the display screen. It is characterized in that it includes a comparison result display means.

According to the present invention, the user can easily confirm the comparison result between the structure of the transmitted file and the structure of the file before transmission.

As a result, for example, the comparison of the configuration of the 3D CAD file between the same or different systems can be realized without using the 3D CAD application, so that the environment in which the 3D CAD application can be executed becomes unnecessary, and the 3D CAD application becomes unnecessary. Can save time until the file is opened, and even an operator with relatively little knowledge of 3D CAD applications and design can easily check the difference in configuration and store it in PDM efficiently and easily. It is possible to confirm whether the structure of the created 3D CAD file is reliable.

The figure which shows an example of the system structure of the information processing system in embodiment of this invention. The figure which shows an example of the hardware composition of each apparatus in embodiment of this invention. The figure which shows an example of the functional structure of each apparatus in embodiment of this invention. A flowchart showing an outline of the configuration comparison process in the embodiment of the present invention. A flowchart showing an example of configuration information acquisition processing in the embodiment of the present invention. A flowchart showing an example of configuration comparison processing in the embodiment of the present invention. The figure which shows an example of the structure of the comparison result display screen of the structure information in embodiment of this invention. The figure which shows an example of the structure of the structure information table in embodiment of this invention. The figure which shows an example of the structure of the structure information table 1 in embodiment of this invention. The figure which shows an example of the structure of the structure information table 2 in embodiment of this invention. The figure which shows an example of the transition state of the comparison result display screen of composition information in embodiment of this invention. The figure which shows an example of the transition state of the comparison result display screen of composition information in embodiment of this invention. The figure which shows an example of the state of the configuration information table update by the configuration information acquisition processing in the embodiment of the present invention. The figure which shows an example of the state of the configuration information table update by the configuration comparison processing in the embodiment of the present invention. The figure which shows an example of the state of the configuration information table update by the configuration comparison processing in the embodiment of the present invention. A flowchart showing an example of a file upload process according to the embodiment of the present invention. A flowchart showing an example of details of the reception process of the target file 2 in the embodiment of the present invention. The figure which shows an example of the reference restriction information of the target file in embodiment of this invention. The figure which shows an example of the history table of the file upload in embodiment of this invention.

Hereinafter, an example of the embodiment of the present invention will be described with reference to the drawings.

An example of the system configuration of the information processing system according to the embodiment of the present invention will be described with reference to FIG. FIG. 1 is a diagram showing an example of a system configuration of an information processing system according to an embodiment of the present invention.

The file management server 100 stores and manages a file uploaded (transmitted) from the client PC 200 and configuration information constituting the file.

The configuration information referred to here is an assembly in a 3D CAD file (3D model data), and specifically, for example, a file specified from the assembly (3D CAD file configuration = component data, etc.). Information such as storage location, configuration order, existence / non-existence of reference file, file status (configuration), number of members, etc. shall be used.

LAN 101 is a network that connects the file management server 100 and the client PC 200 in a communicable manner.

The client PC 200 stores the file and the configuration information (assembly) of the file. Further, the configuration information of the file stored in the client PC 200 and the configuration information of the file uploaded from the client PC 200 to the file management server 100 are acquired, compared, and the comparison result is displayed. The file referred to here is, for example, a three-dimensional CAD file.

Further, the file management server 100 stores PDM software (Product Data Management software / Product data management software / hereinafter referred to as PDM) in an external memory.

The client PC 200 stores the PDM and a comparison tool (a tool as an add-on function of the PDM) that performs the above-mentioned comparison processing of the configuration information in a predetermined area. As described above, the PDM is installed on both the client PC 200 and the file management server 100, and the PDM installed on the client PC 200 is a case where the client PC 200 (comparison tool) requests data from the PDM of the file management server. It functions as an API (Appliation Programming Client / hereinafter, API).

The file uploaded from the client PC 200 is stored and held by the file management server 100 in the external memory of the file management server 100, and the PDM of the file management server 100 manages the storage location and state of the file, analyzes the data, and so on. The analysis results shall be sent and received.

When the CPU of the client PC 200 starts the PDM of the client PC 200, the comparison tool as the add-on is read from a specific folder on the storage area of the client PC, and the comparison tool is started on the menu screen of the PDM. Display the button.

Then, when the instruction to press the activation button is received, the comparison tool is activated, and the processes shown in FIGS. 4 to 6 are executed in response to the operation instruction from the user. The above is the description of an example of the system configuration of the information processing system according to the embodiment of the present invention shown in FIG.

Next, an example of the hardware configuration of each device in the embodiment of the present invention will be described with reference to FIG. FIG. 2 is a diagram showing an example of a hardware configuration of each device according to the embodiment of the present invention.

In FIG. 2, 201 is a CPU that comprehensively controls each device and controller connected to the system bus 204. Further, the ROM 202 or the external memory 211 is necessary to realize a function executed by a BIOS (Basic Input / Output System) or an operating system program (hereinafter, OS) which is a control program of the CPU 201, and each server or each PC. Various programs described later are stored.

Reference numeral 203 denotes a RAM, which functions as a main memory, a work area, and the like of the CPU 201. The CPU 201 realizes various operations by loading a program or the like necessary for executing a process from the ROM 202 or the external memory 211 into the RAM 203 and executing the loaded program.

Reference numeral 205 denotes an input controller, which controls input from a keyboard (KB) 209, a pointing device such as a mouse (not shown), or the like. Reference numeral 206 denotes a video controller, which controls the display on a display such as a CRT display (CRT) 210. Although it is described as CRT210 in FIG. 2, the display may be not only the CRT but also another display such as a liquid crystal display. These are used by the administrator as needed.

Reference numeral 207 is a memory controller, which is connected to a hard disk (HD) for storing boot programs, various applications, font data, user files, edit files, various data, etc., a flexible disk (FD), or a PCMCIA card slot via an adapter. It controls access to an external memory 211 such as a compact flash (registered trademark) memory.

Reference numeral 208 denotes a communication I / F controller, which connects and communicates with an external device via a network (for example, LAN 101 shown in FIG. 1), and executes communication control processing on the network. For example, communication using TCP / IP is possible.

The CPU 201 can display the outline font on the CRT 210 by executing the outline font expansion (rasterization) process in the display information area in the RAM 203, for example. Further, the CPU 201 enables a user instruction with a mouse cursor or the like (not shown) on the CRT 210.

Various programs described later for realizing 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 needed. Further, a definition file and various information tables used when executing the above program are also stored in the external memory 211, and detailed description of these will be described later. The above is the description of an example of the hardware configuration of each device in the embodiment of the present invention shown in FIG.

Next, an example of the functional configuration of each device in the embodiment of the present invention will be described with reference to FIG. FIG. 3 is a diagram showing an example of the functional configuration of each device according to the embodiment of the present invention.

The file configuration storage unit 321 is a storage unit that stores the configuration information (assembly / assembly file) of the file stored in the external memory of the client PC 200.

The file upload processing unit 322 is a processing unit that transmits (uploads) a file to the file management server 100. For example, a three-dimensional CAD file and its configuration information (assembly file) are transmitted. The local file configuration information acquisition unit 323 is an acquisition unit that acquires the configuration information of the file stored in the external memory of the client PC 200, which has received the designation to be uploaded to the file management server 100.

The upload file configuration information receiving unit 324 is a receiving unit that requests the file management server 100 for the configuration information of the file that has been sent to the file management server 100 (corresponding to the assembly requesting means), and receives the configuration information. .. The configuration comparison processing unit 325 is a processing unit that compares the configuration information acquired by the local file configuration information acquisition unit 323 with the configuration information received by the upload file configuration information reception unit 324.

The comparison result display unit 326 is a display processing unit that displays the results of comparison by the configuration comparison processing unit 325 on the display screen in an identifiable manner.

The upload file reception unit 311 is a reception unit that receives a file transmitted from the client PC 200 and accepts uploads. The upload file configuration information storage unit 312 is a storage unit that stores the configuration information (assembly file) of the file (upload file / 3D CAD file) that has been uploaded by the upload file reception unit 311 (corresponding to the assembly storage means). ..

The upload file configuration information acquisition unit 313 is an acquisition unit that acquires the configuration information of the upload file (sent file / transmitted file) in response to an instruction from the client PC 200. The upload file configuration information transmission unit 314 is a transmission unit that transmits the configuration information acquired by the upload file configuration information acquisition unit 313 to the client PC 200 (corresponding to the assembly transmission means). The above is the description of an example of the functional configuration of each device in the embodiment of the present invention shown in FIG.

Next, an example of a file upload process in the embodiment of the present invention will be described with reference to FIG. FIG. 16 is a flowchart showing an example of a file upload process according to the embodiment of the present invention.

The CPU 201 of the client PC 200 uses the function of the OS set in the client PC 200 to select a file (data) to be copied and transmitted (uploaded) to the file management server 100 in response to a file selection operation from the user. (Step S1601), the user receives an instruction to transmit the data.

For example, the CPU 201 of the client PC 200 activates the PDM in response to an operation instruction from the user, accepts the designation of the path (URI) to be expanded in the window of the PDM, and stores the PDM in the external memory of the file management server 100. Open the area.

The CPU 201 of the client PC 200 moves (sends / uploads) a file stored in the external memory of the client PC 200 onto the window of the PDM by, for example, a drag-and-drop operation on the OS set in the client PC 200. When it is detected that the operation has been accepted (via the running PDM), the selected file is transmitted to the folder path of the file management server 100 being expanded in the window of the PDM (step S1602).

For example, if the file selected as the transmission target is a folder, the files and data in the folder are transmitted to the destination. In the folder, for example, a three-dimensional CAD file, a file necessary for constructing the three-dimensional CAD file (for example, component data constituting the model data in the three-dimensional CAD file), and a reference relationship of the configuration are shown. Includes assembly information (assembly files) and the like.

As described above, the file to be transmitted here is a three-dimensional CAD file, a file necessary for constructing the three-dimensional CAD file (for example, component data constituting model data in the three-dimensional CAD file), and It is an assembly file (configuration information / assembly information) showing the reference relationship of the configuration, and includes at least the assembly file.

The information transmitted to the file management server here is an example of data necessary for specifying the configuration information of the file to be compared, and if the information can specify the configuration information, it is sufficient. It is not limited to the above-mentioned format.

In response to the transmission instruction, the CPU 201 of the client PC 200 determines whether all the files selected according to the selection operation received from the user have been transmitted to the transmission destination (a predetermined storage area of the file management server 100) (step S1603). ), If it has been transmitted, the process is terminated, and if it has not been transmitted, the process proceeds to step S1604.

The CPU 201 of the client PC 200 determines whether the number of transmitted files exceeds a predetermined number (step S1604). It is assumed that the predetermined number of values are set in the OS of the client PC 200 and are stored and managed in advance in the external storage area.

If it is determined that the predetermined number has been exceeded, the process is terminated, and if it is determined that the predetermined number has not been exceeded, one selected file is acquired and the transmission process is started (step S1605).

Here, in addition to the transmission file described above, the CPU 201 of the client PC 200 transmits the file path in which the file to be uploaded is stored and the IP address (identification information) of the client PC 200, and the file is any of them. A request to store the information as a history shall be transmitted together with the information on the location of the device.

The CPU 201 of the file management server 100 receives the data of the file (step S1606) and executes a process of storing the data in a predetermined storage area (a storage location designated by the user) on the external memory (step S1607).

In addition, a history table for storing the upload history (transmission history) is generated, and the file name of the file, the folder path on the client PC 200 of the transmission source, the folder path on the file management server 100 storing the file, and the like are obtained. Stores information and stores it in an external memory. The history table will be described later in the description of FIG.

Here, an example of a file upload history table according to the embodiment of the present invention will be described with reference to FIG. FIG. 19 is a diagram showing an example of a file upload history table according to the embodiment of the present invention.

The history table 1900 is generated by the file management server 100 in response to a request from the client PD 200, and is stored in the external memory of the file management server 100.

No. 1901 is identification information of history information. The file name 1902 is the file name of the uploaded file.

The move source IP1903 is the identification information of the device (here, the client PC200) from which the file is uploaded. The move source path 1904 is the folder path of the upload source of the file (here, the folder path of the storage location immediately before upload in the client PC 200).

The move destination IP1905 is the identification information of the device (here, the file management server 100) to which the file is uploaded. The move destination path 1906 is a folder path of the upload destination of the file (here, the folder path of the file management server 100 where the file is saved). The above is the description of an example of the file upload history table in the embodiment of the present invention shown in FIG.

Returning to the description of FIG. The CPU 201 of the client PC 200 determines whether a predetermined time has elapsed since the start of the file (data) transmission process in response to the transmission instruction (step S1608). For example, when a plurality of files to be transmitted are specified and the plurality of files are transmitted to the destination, a process of acquiring one file to be transmitted and transmitting the file to the destination is sequentially performed. Here, it is determined whether or not a predetermined time has elapsed since the transmission processing of the acquired one file was started.

It is assumed that the information at the predetermined time is set in the OS of the client PC 200 and is stored and managed in advance in the external storage area.

If it is determined that a predetermined time has elapsed from the start of file transmission, the file transmission process is interrupted and the process ends. That is, the CPU 201 of the client PC 200 determines that it is difficult to transmit the subsequent files based on the file capacity and the communication status with the file management server 100, and performs the transmission processing of the file being transmitted and the untransmitted file selected as the transmission target. It interrupts and ends the process. If it is determined that the predetermined time has not elapsed from the start of file transmission, the transmission process is continued and the process proceeds to step S1609.

The CPU 201 of the client PC 200 determines whether the transmission process of the file being transmitted is completed in step S1605 (step S1609). If it is determined that the transmission is completed, the process is returned to step S1603, and if it is determined that the transmission is not completed, the transmission process is continued. The above is the description of an example of the file upload process according to the embodiment of the present invention shown in FIG.

Next, with reference to FIG. 4, the outline of the configuration comparison process in the first embodiment of the present invention will be described. FIG. 4 is a flowchart showing an outline of the configuration comparison process according to the first embodiment of the present invention. Each step from S401 to S412 is processed under the control of the CPU 201 in the client PC 200.

When performing the process shown in FIG. 4, the CPU 201 of the client PC 200 is in a state of being able to communicate with the file management server 100 (PDM).

In step S401, the CPU 201 of the client PC 200 displays the command dialog 700 shown in FIG. 7 by accepting a command activation operation (an operation for activating the configuration information comparison tool) by the operator on the menu screen of the PDM (not shown). indicate. The command dialog 700 is an example of a screen for displaying the comparison result of the configuration information in the embodiment of the present invention.

Here, an example of the configuration of the configuration information comparison result display screen in the embodiment of the present invention will be described with reference to FIG. 7. FIG. 7 is a diagram showing an example of the configuration of the configuration information comparison result display screen according to the embodiment of the present invention.

The comparison result display screen (command dialog 700) is composed of a text box 701, a reference button 702, a list box 703, a text box 704, a reference button 705, a list box 706, an execute button 707, an end button 708, and the like.

The text box 701 is a box that displays the file path of the file (comparison target file / assembly file) selected on the file selection screen (not shown) when the reference button 702 is pressed.

In the file selection screen (not shown) displayed by pressing the reference button 702, only the file stored in the external memory of the client PC 200 can be referenced and specified.

Specifically, reference restriction information such as the reference restriction information 1800 in FIG. 18 is stored in the external memory of the client PC 200, and when the CPU 201 of the client PC 200 accepts the press of the reference button 702, the reference restriction information Specify the file path that can be referenced on the file selection screen, and if the specification of the file path that cannot be referenced is accepted, an error is displayed and the file path that cannot be referenced is not displayed (reference). Control so as not to let).

Here, an example of reference restriction information of the target file in the embodiment of the present invention will be described with reference to FIG. FIG. 18 is a diagram showing an example of reference restriction information of the target file in the embodiment of the present invention.

The reference restriction information 1800 is set according to the operation instruction of the user on the restriction information setting screen (not shown) when the comparison tool is set on the client PC 200, and the CPU 201 of the client PC 200 generates the restriction information of the comparison tool. It is assumed that it is generated by using the function and stored in the external memory of the client PC 200.

No. 1801 is identification information for identifying reference restriction information. The target file 1802 shows the target file 1 and the target file 2 shown in the command dialog 700 of FIG. 7. When the reference button 702 is accepted, the restriction information in which the "target file 1" is inserted in the target file 1802 is applied. When the reference button 705 is accepted, the restriction information in which the "target file 2" is inserted in the target file 1802 is applied.

The reference destination IP1803 is identification information of a device that is permitted to refer to a file path on a file selection screen (not shown). Although the IP address is inserted here, any information that can identify the device is sufficient.

The reference destination path 1804 indicates a file path for which reference is permitted on a file selection screen (not shown). On the file selection screen (not shown), only the file path below the file path set in the reference path 1804 can be specified and referenced.

The reference IP 1803 of the target file 1802 = "target file 1" is inserted by the CPU 201 of the client PC 200 acquiring the IP address of its own device when the comparison tool is set and stored in the client PC 200. Is set by.

The target file 1802 = the reference destination IP 1803 of the "target file 2" is, for example, a file management according to a user's operation instruction on a restriction information setting screen (not shown) when the comparison tool is set and stored in the client PC 200. It is set by inputting the IP address of the server 100.

That is, according to the reference restriction information 1800, the files that can be compared by the comparison tool are the target file 1 = the local file stored in the external memory of the client PC 200 (the file that received the upload instruction) and the target file 2 = the file. This is an uploaded (sent) file stored in the management server 100 (PDM).
The above is the description of an example of the reference restriction information of the target file in the embodiment of the present invention shown in FIG.

Returning to the description of FIG. The list box 703 is a box for displaying the configuration information of the comparison target file (here, the target file 1) acquired and generated by the configuration information acquisition process of FIG. 5 described later.

The text box 704 displays the file path of the file (comparison target file / assembly file) selected on the file selection screen (not shown) when the browse button 705 is pressed, or accepts the designation of the target file 1. In this case, the file path of the file corresponding to the target file 1 (target file 1 = file after upload when the file before upload) is acquired from the file management server 100 and displayed.

The list box 706 is a box for displaying the configuration information of the comparison target file (here, the target file 2) acquired and generated by the configuration information acquisition process of FIG. 5 described later.

By accepting the presses of the reference button 702 and the reference button 705, the execution button 707 executes a comparison process of the configuration information (configuration information displayed in each list box) of the file selected on the file selection screen (not shown). It is a button for.

The end button 708 is a button for terminating the command dialog 700. The above is the description of an example of the configuration of the configuration information comparison result display screen according to the embodiment of the present invention shown in FIG. 7.

Returning to the description of FIG. In step S402, the operator accepts the target file 1 (comparison target file / file for comparing configuration information with other files). Specifically, by accepting a pressing instruction by the operator of the reference button 702 in the command dialog 700 of FIG. 7, a file selection screen (not shown) is displayed, and the file selected by the operator on the file selection screen is targeted. Accepted as file 1 (corresponding to the selection receiving means), the file path of the target file 1 is displayed in the text box 701 of FIG. 7, and the process proceeds to step S403.

In step S403, configuration information acquisition processing is performed on the file received in step S402. Details will be described later with reference to FIG. The configuration information table 1 shown in 900 of FIG. 9 is created by the process of step S403, and the process shifts to step S404 (corresponding to the first assembly acquisition means). The configuration information table 1 is stored in the external memory of the client PC 200.

Here, the configuration information acquisition process performed in step S403 of FIG. 4 (and step S406 of FIG. 4 described later) will be described with reference to the configuration information table 800 of FIGS. 5 and 8.

First, an example of the configuration of the configuration information table in the embodiment of the present invention will be described with reference to FIG. FIG. 8 is a diagram showing an example of the configuration of the configuration information table according to the embodiment of the present invention.

The configuration information table 800 is composed of record No. 801 and level 802, folder path 803, file name 804, configuration path 805, type 806, configuration name 807, number of members 808, determination 809, and the like.

Record No. 801 stores the order of records in the processing file (file to which processing is being applied). Level 802 stores the configuration hierarchy of the processing file. The folder path 803 stores the folder path of the processing file.

The file name 804 stores the file name of the processing file. The configuration path 805 stores the configuration order of the processing files.

Here, the configuration order will be described with reference to 900 (configuration information table 1) of FIG. The configuration order indicates the path of the reference relationship in general 3D CAD. For example, since the file received in step S502 of FIG. 5 (assumed to be TopAssy) is located at the top of the file structure (configuration), the configuration path is Null. Next, the configuration path of the file having a primary reference relationship with TopAssy is TopAssy. Specifically, the record No. 2 shown in 900 (configuration information table 1) of FIG. 9 corresponds to this. Further, the configuration path of the file having a secondary reference relationship with TopAssy is TopAssy / Assy1. Specifically, records Nos. 3 to 5 shown in 900 (configuration information table 1) in FIG. 9 correspond to this.

The type 806 stores the type of the processing file (difference depending on the extension of the CAD file). The configuration name 807 is used when the identification name information of the data in the file of the processing file (for example, a plurality of internal states having different shapes, for example, a right-handed version and a left-handed version of the same part, etc. are stored in one file). , Information for identifying one of them) is stored.

The number of members 808 stores the total number of files in which the processing file, the file name 804, the configuration path 805, and the type 806 all match (hereinafter, the first condition). The determination 809 stores the existence information of the processing file and the comparison determination result.

Further, the configuration information table 800 created when processing step S403 is the configuration information table 1, and the configuration information table 800 created in step S406 described later is the configuration information table 2. However, in the process described below, 1 to 1 to If 2 is not specified, common processing will be applied. The above is the description of an example of the configuration of the configuration information table in the embodiment of the present invention shown in FIG.

Next, an example of the configuration information acquisition process in the embodiment of the invention will be described with reference to FIG. FIG. 5 is a flowchart showing an example of the configuration information acquisition process according to the embodiment of the present invention. It is assumed that each step of steps S501 to S516 is processed by using the function of the configuration information comparison tool under the control of the CPU 201 in the client PC 200.

In step S501, for example, in response to the target file selection operation received in step S402 of FIG. 4, the file to be processed is accepted, and the configuration information table 800 of FIG. 8 is created, which is the same as the configuration information table. Create a temporary record of only one record with a structure.

Further, when the restart processing of this processing is performed in step S516 described later, the file received from step S515 is the processing target. In the case of restart processing, a new configuration information table is not created. That is, the reference file of the target file that has been selected by the user is also processed in FIG. 5 and registered in the same configuration information table as the target file.

In step S502, the file path of the file received in step S501 is acquired, and the folder path from which the file name is removed is stored in the folder path 803 of the temporary record.

In step S503, the file name of the file received in step S501 is acquired and stored in the file name 504 of the temporary record.

Hereinafter, in the acquisition processing of various information in steps S504 to S507 (acquisition processing of each information in the configuration information table 800), the file received in step S501 is the target file 1 (file stored in the external memory of Klein and PC200). In some cases, the running comparison tool requests acquisition of various information from the API of the 3D CAD application set in Klein and PC200, and the information of the result corresponding to the acquisition request is obtained from the API of the 3D CAD application. Performed by receiving.

If the file received in step S501 is the target file 2 (file stored in the external memory of the file management server 100 / file registered in the PDM), the comparison tool being started is in the API of the PDM, and various information is displayed. It is executed by making an acquisition request of the above and receiving the information of the result corresponding to the acquisition request from the API of the PDM.

In step S504, for the file received in step S501, the configuration name specified by the API of the three-dimensional CAD or PDM is acquired from the API, stored in the configuration name 807 of the temporary record, and processed in step S505. Transition.

In step S505, the file type information specified by the API of the three-dimensional CAD or PDM is acquired from the API for the file received in step S501, and is stored in the temporary record type 806.

In step S506, for the file received in step S501, the configuration order specified by the API of the three-dimensional CAD or PDM is acquired from the API and stored in the configuration path 805 of the temporary record.

In step S507, the order of the configuration level (corresponding to the above-mentioned degree reference relationship) obtained in the process of executing step S506 is acquired from the API of the three-dimensional CAD or PDM and stored in the level 802 of the temporary record. Then, the process shifts to step S508.

In step S508, the temporary record and the record whose values 802 to 807 in FIG. 8 match are searched for in the configuration information table being processed. If no matching record is detected, the process proceeds to step S509, and if a matching record is detected, the process proceeds to step S510. That is, it is determined whether the information of each item of the acquired file has been registered in the configuration information table.

In step S509, the value of the temporary record is added to the configuration information table as a new record, 1 is stored in the number of members 808, and the process shifts to step S511.

In step S510, 1 is added to the value of the number of matching records 808 detected in the configuration information table, and the process shifts to step S511.

In step S511, the existence confirmation process of the processing file is performed, and if the processing file does not exist, the process proceeds to step S512, and if the processing file exists, the process proceeds to step S513. That is, it is determined whether or not the file is actually stored in the location on the client PC 200 or the file management server 100 (PDM) indicated by the folder path.

In step S512, the value of -1 is stored in the determination 809 of the record of the configuration information table updated in step S509 or S510, and the configuration information acquisition process ends.

In step S513, the migration destination of the processing is determined according to the processing file type 806. Here, the type premised on having a reference file is Assy, the type premised on not having a reference file is Part, and if the processing file type is Assy, the process is shifted to step S514 and the processing file is processed. If the type is Part, the configuration information acquisition process is terminated.

In step S514, a list of reference files is acquired by using API for the processing file, and the processing is transferred to step S515. If there are multiple reference files, get multiple reference files.

In step S515, the presence / absence of an unprocessed file is determined for the file acquired in step S514, and if there is an unprocessed file, the process is shifted to step S516 to restart the configuration information acquisition process. That is, one of the acquired reference files is acquired, the acquired file is accepted in step S501, and thereafter, the processes of steps S502 to S516 are applied.

If there is no unprocessed file, the configuration information acquisition process ends. That is, when the processing of steps S501 to S516 for all the reference files of all the files is completed, the acquisition processing of the configuration information is terminated. The above is the description of an example of the configuration information acquisition process in the embodiment of the present invention shown in FIG.

The state of updating the configuration information table by the configuration information acquisition process of FIG. 5 is as shown in FIG.

Returning to the description of FIG. In step S404, the records of the configuration information table (hereinafter, shown in configuration information table 1/900 of FIG. 9) created in step S403 showing the configuration information of the target file 1 are all recorded in the order of record numbers, and all the records are in the command dialog 700 of FIG. Is displayed in the list box 703 of the above, and the process proceeds to step S405.

The items to be displayed are the seven items of the folder path, file name, configuration path, type, configuration name, and number of members in the columns of the configuration information table 1. In addition, the list box background color is changed in order to effectively suggest the result of the configuration information acquisition process to the operator. Specifically, among the records in the configuration information table 1 of 900 in FIG. 9, the background color of the record row displayed in the list box 703 is changed to red for the record whose determination column value is -1. As a result, the comparison result of the configuration information of the file is shown (here, since the file to be compared with the file (the file for which the configuration information is acquired in step S406 described later) has not been acquired, the unacquired file and the configuration information The comparison result is shown). The specific processing result (comparison result) of step S404 is shown, for example, in the command dialog of 1100 in FIG.

In step S405, the target file 2 whose configuration is compared with the target file 1 is accepted (corresponding to the second assembly acquisition means). The details of the reception process of the target file 2 will be described later in the description of FIG.

Here, an example of details of the reception process of the target file 2 in the embodiment of the present invention will be described with reference to FIG. FIG. 17 is a flowchart showing an example of details of the reception process of the target file 2 in the embodiment of the present invention.

The CPU 201 (comparison tool) of the client PC 200 transmits the file name of the target file 1, the folder path, and the IP address of the client PC 200 to the file management server 100 (PDM) (step S1701).

Upon receiving this (step S1702), the file management server 100 (PDM) displays the file and the file name (file name 1902) in the history table 1900 stored in the external memory, and the device of the transmission source (movement source IP1903). , It is determined whether there is a history in which the folder path (movement source path 1904) matches (step S1703).

If there is a matching history, that is, if there is a file (target file 2) corresponding to the target file 1, the folder path of the target file 2 is specified and transmitted to the client PC 200 (step S1704). If there is no matching history, information (error information) indicating that the matching history (corresponding file) does not exist is transmitted to the client PC 200 (step S1705).

The CPU 201 (comparison tool) of the client PC 200 receives the folder path or error information of the target file 2 (step S1706), and determines whether the received information is the folder path of the target file 2 (step S1707).

When it is determined that the received information is the folder path of the target file 2, the information of the folder path is inserted into the text box 704 of FIG. 7 as the folder path of the target file 2 (step S1708), and the process is terminated. ..

If it is determined that the received information is not the folder path of the target file 2 (error information), a file selection screen (not shown) for allowing the user to select the target file 2 is displayed (step S1709), and the file is selected. Accept (step S1710). Then, the folder path of the file that has received the selection is inserted into the text box 704 of FIG. 7 as the folder path of the target file 2 (step S1708), and the process ends.

In the file selection screen (not shown) displayed in step S1709, the folder path of the reference destination specified on the file selection screen for selecting a file is the target file 1802 = "target file" of the reference restriction information in FIG. 2 ”, the file management server 100 (reference IP = 182.16.YYY.ZZZ) is limited to the folders under“ \\ Saver \ PDM \ data ”.

That is, when the designation of a reference destination other than the above-mentioned reference destination is accepted on the file selection screen (not shown), the CPU 201 (comparison tool) of the client PC 200 cannot display the reference destination other than the above-mentioned reference destination. An error screen indicating is displayed, and control is performed so that a file is not selected from other than the file management server 100. The above is a description of an example of details of the reception process of the target file 2 in the embodiment of the present invention shown in FIG.

Returning to the description of FIG. In step S406, the configuration information acquisition process is performed on the file received in step S405 (that is, the file received in step S501 in FIG. 5 = the file received in step S405 in FIG. 4). Since the details of the configuration information acquisition process have been described above in the description of FIG. 5, the description is omitted here (corresponding to the second assembly acquisition means).

Since the file received in step S405 is stored in the external memory of the file management server 100 and its storage location is managed by the PDM, the CPU 201 (comparison tool) of the client PC 200 corresponds to the API of the PDM. Request information on the configuration name, file type, configuration path, and level of the target file 2 (corresponding to the assembly request means), and receive and acquire the same information specified by the PDM as a result of the request (corresponding to the assembly request means). See steps S504 to 507 in FIG. 5).

By the process of step S406, the configuration information table 2 showing the configuration information of the target file 2 shown in 1000 of FIG. 10 is created, stored in the external memory of the client PC 200, and the process is transferred to step S407.

In step S407, all the records of the configuration information table 2 shown in FIG. 11 created in step S406 are displayed in the list box 706 of FIG. 7 in the same manner as in step S404 (that is, the command dialog is displayed from the state of 1100 in FIG. 11 to 1150. Update to the state of), and shift the process to step S408.

In step S408, the operator performs the execution button 707 acceptance process of the command dialog 700 of FIG. When the button press by the operator is accepted, the process proceeds to step S409.

In step S409, a configuration comparison process is performed. Details will be described later with reference to FIG. By the process of step S409, the configuration information table 1 shown in 900 of FIG. 9 is updated to the state shown in 950 of FIG. 9, the configuration information table 2 shown in 1000 of FIG. 10 is updated to the state shown in 1050 of FIG. The process will be transferred to S410.

Here, the configuration comparison process performed in step S409 will be described with reference to FIG. FIG. 6 is a flowchart showing an example of the configuration comparison process according to the embodiment of the present invention. Each step of S601 to S617 is processed by using the function of the configuration information comparison tool under the control of the CPU 201 in the client PC 200.

In step S601, an unprocessed file is determined for the record in the configuration information table 1, and if there is an unprocessed file, one record is acquired and the process proceeds to step S602. If there is no unprocessed file, the process proceeds to step S610. Migrate processing. That is, it is determined whether or not there is a file in the configuration information table 1 to which the processing of steps S601 to S609 has not been applied.

In step S602, the unprocessed file for the record in the configuration information table 2 is determined for the record (hereinafter, record 1) passed from step S601. That is, it is determined whether or not there is a record (file) in the configuration information table 2 for which the content matching determination with the record 1 has not yet been performed. If there is an unprocessed file, one unprocessed file (record) is acquired from the configuration information table 2 and the process is transferred to step S603. If there is no unprocessed file, the process is transferred to step S607.

In step S603, a match determination of the first condition is performed on the record 1 described above and the record (hereinafter, record 2) delivered from step S602 (that is, the processing file and the file name 804, the configuration path 805, and the type 806). It is determined whether or not all three match), and if they match, the process proceeds to step S604, and if they do not match, the process proceeds to step S602. When the processing is transferred to step S602, the record 2 to which the processing up to step S603 is applied is treated as a processed record. The information on whether or not the processing has been completed shall be temporarily stored in the temporary storage area of the client PC 200 in association with the identification information of the record until the processing of FIG. 6 is completed.

In step S604, the order of the records 2 in the configuration information table 2 is moved to the same record No. as the order of the record 1 (record No. 801 in the configuration information table 800), and the process proceeds to step S605. That is, when the user is made to compare and confirm the configuration information shown in the configuration information table 1 and the configuration information table 2 in the command dialog 700, the record 1, the record 1, the processing file, the file name 804, and the configuration path are confirmed. The order in the record is updated so that the positions in the list box 703 (706) of the record 2 in which all three of 805 and the type 806 match match.

As a result, the record 2 is displayed right next to the record 1 in the list box 703. That is, when the user visually compares and confirms the status of the records, the user only sees the record 2 located right next to the record 1 to be confirmed, and the presence or absence of the difference between the statuses of the record 1 and the record 2 and the difference. You can check the contents.

In step S605, the determination process of matching both the configuration name 807 and the number of members 808 of the record 1 and the record 2 (hereinafter referred to as the second condition) is performed, and the process shifts to step S606 regardless of the match or the mismatch. However, if there is a discrepancy, a record that matches record 1 with any of the first and second conditions is detected from the processed records in table 2, and if detected, the detected record is recorded in table 2 in record 1. Move to the same No as the order of.

In step S606, the determination process of step S605 updates the determination 809 of the record 1, and the process shifts to step S602. In the update process, based on the comparison result of record 1 and record 2, the determination 809 of record 1 and record 2 is set to 0 when the first condition and the second condition match, and 1 when only the first condition matches. Store each. Here, storing 0 indicates that there is a configuration file in which the configuration information matches with respect to record 1, and storing 1 indicates that the same configuration file exists although some of the configuration information is different. Indicates that it exists.

In step S607 (NO in step S602), it is determined whether or not there is one or more records in the configuration information table 2 that match the first condition for the record 1, and if there is one or more records, the process proceeds to step S601. If there is no case, the process is shifted to step S608. When the process is transferred to step S601, the record 1 up to step S607 is treated as a processed record.

In step S608, a new blank record is newly added to the same No. in the order of the record 1 in the table 2, and the process shifts to step S609.

In step S609, the value of 2 is stored in the determination 809 of the record 1 and the record added in step S608, and the process shifts to step S601. Storing 2 here means comparing Table 1 and Table 2 even if there is no configuration file with matching configuration information in Table 2 with respect to record 1, or even if there is a configuration file with matching configuration information. Indicates that there is no paired record at the time of this (a state in which a pair has already been confirmed with another record even if the configuration information matches).

FIG. 14 shows the state of the processing (configuration comparison processing) of steps S601 to S609 described above. That is, an example of the state of the content update process of the configuration table 2 based on the content of the configuration table 1 is shown.

In step S610, an unprocessed file is determined for the record in table 2 (that is, it is determined whether there is a file to which the processing of steps S611 to S617 has not been applied), and if there is an unprocessed file, configuration information. One unprocessed file is acquired from Table 2, the process is shifted to step S611, and if there is no unprocessed file, the configuration comparison process is terminated.

In step S611, the unprocessed file for the record in the configuration information table 1 is determined for the record 2 handed over from step S610 (that is, the configuration information for which the content matching with the record 2 has not yet been determined). It is determined whether there is a record (file) in the table 1), and if there is an unprocessed file, the process is shifted to step S612, and if there is no unprocessed file, the process is shifted to step S615.

In step S612, a match determination of the first condition is performed on the record 2 and the record 1 handed over from step S611 (that is, whether or not the processing file and the file name 804, the configuration path 805, and the type 806 all match. If they match, the process proceeds to step S613, and if they do not match, the process proceeds to step S611. When the processing is transferred to step S611, the record 1 to which the processing up to step S612 is applied is treated as a processed record.

In step S613, the determination process of the second condition is performed on the record 2 and the record 1 (that is, it is determined whether both the configuration name 807 and the number of members 808 of the record 2 and the record 1 match), and the match and the mismatch are determined. Regardless, the process shifts to step S614. However, if they do not match, a new blank record is newly added to the record No. in the same order as the record 2 in the configuration information table 1.

In step S614, the determination process of step S613 updates the determination 809 of record 2 and record 1, and the process shifts to step S611. In the update process, based on the comparison result of record 2 and record 1, the determination 809 of record 2 and record 1 is set to 0 when the first condition and the second condition match, and 1 when only the first condition matches. Store each. When a blank record is added in step S614, 1 is stored in each of the determination 809 of the table 2 and the table 1.

In step S615, a process of determining whether or not there is one or more records in the table 1 that match the first condition is performed for the record 2, and if there is one or more records, the process proceeds to step S610. The processing is transferred to S616. When the process is transferred to step S610, the record 2 up to step S615 is treated as a processed record.

In step S616, a new blank record is newly added to the same No. in the order of the record 2 in the table 1, and the process shifts to step S617.

In step S617, 3 is stored in the record 2 and the determination 809 of the record added in step S616, and the process shifts to step S601. Storing 3 here means comparing Table 1 and Table 2 even if there is no configuration file in Table 1 with matching configuration information for record 2, or even if there is a configuration file with matching configuration information. Indicates that there is no paired record at the time of this (a state in which a pair has already been confirmed with another record even if the configuration information matches).

FIG. 15 shows the state of the process (configuration comparison process) of steps S610 to S617 described above. That is, an example of the state of the content update process of the configuration table 1 based on the content of the configuration table 2 is shown. The above is the description of an example of the configuration comparison process in the embodiment of the present invention shown in FIG.

Returning to the description of FIG. In step S410, the display contents of the list box 703 of FIG. 7 are updated by using the configuration information table 1 shown in 950 of FIG. 9 updated in step S409 by the same procedure as in step S404, and the process shifts to step S411. At this time, the list box background color is changed in order to effectively suggest the result (comparison result) of the configuration comparison process to the operator.

Specifically, when the value of the judgment column of the configuration information table 1 shown in FIG. 9 950 is 1, the background color of the record row on the corresponding list box is blue, and when the value of the judgment column is 2, it is yellow. , If the value of the judgment column is 3, change it to green to display the file comparison result. The display of the comparison result is, for example, the display of the command dialog of 1200 in FIG.

In step S411, the display contents of the list box 706 of FIG. 7 are updated by using the configuration information table 2 shown in 1050 of FIG. 10 updated in step S409 by the same procedure as in step S410. For example, the display of the command dialog of 1250 in FIG.

In step S412, command end acceptance processing (end instruction acceptance processing of the configuration information comparison tool) is performed. Specifically, the command dialog 700 of FIG. 7 is hidden by pressing the end button 708 of FIG. 7 by the operator, and the process is terminated. The above is the description of the outline of the configuration comparison process in the first embodiment of the present invention in FIG.

As described above, according to the present invention, the user can easily confirm the comparison result between the configuration of the transmitted file and the configuration of the file before transmission.

That is, the configuration of the file before uploading to the external device and the configuration of the file after uploading to the external device match, and the user can confirm whether the file is uploaded correctly.

For example, it is possible to efficiently compare the configuration information of CAD files between different systems without using a three-dimensional CAD application. Especially in the case of large-scale configuration information, it is not necessary to read the file by the 3D CAD application, so that the time until the 3D CAD application opens the file can be omitted.

Further, for example, the file can be expanded by a 3D CAD application, and the user can easily confirm the difference in the configuration information without comparing and evaluating the results, and the file is efficiently and easily stored in the PDM. It is possible to confirm whether the configuration information of the three-dimensional CAD file is reliable.

In the first embodiment of the present invention described above, the history table 1900 of FIG. 19 is generated by the file management server 100 (PDM) and stored in the external memory of the file management server 100. For example, it may be generated by the client PC 200 (comparison tool) and stored in the external memory of the client PC 200.

That is, when the file is transmitted to the file management server 100 in step S1605 of FIG. 16, if the history table is unrefined, a new history table is generated and the history information of the file to be transmitted to the file management server 100 is input. It is added to the history table and stored in the external memory of the client PC 200. Further, the move destination IP1905 is acquired from the file management server 100 and stored in the history table after the file is transmitted.

In this case, it is assumed that the CPU 201 of the client PC 200 executes all the processes of steps S1701 to S1710 in the reception process of the target file 2 shown in FIG.

<Second embodiment>
Hereinafter, a second embodiment of the present invention will be described.

In the first embodiment described above, the comparison target files (target file 1 and target file 2) are acquired from the client PC and the file management server, respectively, but in the second embodiment, the respective files are acquired. Let the user freely select.

By doing so, when a file is moved or transmitted, the configuration of the file before the move and the configuration of the file after the move are performed regardless of whether the device that stores the file is different before and after the move. The user can easily confirm the comparison result with.

Hereinafter, with respect to the second embodiment, the portion in which the processing is the same as that in the first embodiment described above will be omitted, and the portion in which the processing is different from that in the first embodiment will be described. In the second embodiment, the information shown in FIGS. 17 to 19 is not used.

The CPU 201 of the client PC 200 executes the processes of steps S401 to S404 of FIG. In step S402, the information of the folder path specified by the user is selectively displayed on the file selection screen (not shown) without referring to the reference restriction information 1800 as described above in the first embodiment. .. That is, not only the file stored in the external memory of the client PC 200 but also the file stored in the external memory of the file management server 100 can be selected as the target file 1.

In step S405, the command dialog 700 of FIG. 7 is displayed on the display screen without executing the reception process of the target file 2 shown in FIG. 17, and the user waits until the reference button 705 is pressed.

When the CPU 201 of the client PC 200 accepts the press of the reference button 705, it displays a file selection screen (not shown), accepts a file (assembly file) selection operation from the user on the file selection screen, and performs the selection operation. The file selected by is accepted as the target file 2.

In step S405, the information of the folder path specified by the user is selectively displayed on the file selection screen (not shown) without referring to the reference restriction information 1800 as described above in the first embodiment. .. That is, not only the file stored in the external memory of the file management server 100 but also the file stored in the external memory of the client PC 200 can be selected as the target file 1.

After that, the process proceeds to step S406, and the processes of steps S406 to S412 are executed in the same manner as in the first embodiment described above.

The above is the description of the second embodiment of the present invention.

As a result, when a file is moved or transmitted, the structure of the file before the move and the structure of the file after the move are different regardless of whether the device that stores the file is different before and after the move. The comparison result can be easily confirmed by the user.

The present invention can be, for example, an embodiment as a system, an apparatus, a method, a program, a storage medium, or the like, and specifically, may be applied to a system composed of a plurality of devices, or 1 It may be applied to a device consisting of two devices.

The present invention includes a software program that realizes the functions of the above-described embodiments, which is directly or remotely supplied to the system or device. The present invention also includes cases where the computer of the system or device can also read and execute the supplied program code.

Therefore, in order to realize the functional processing of the present invention on a computer, the program code itself installed on the computer also realizes the present invention. That is, the present invention also includes a computer program itself for realizing the functional processing of the present invention.

In that case, as long as it has a program function, it may be in the form of an object code, a program executed by an interpreter, script data supplied to the OS, or the like.

Recording media for supplying programs include, for example, flexible disks, hard disks, optical disks, magneto-optical disks, MOs, CD-ROMs, CD-Rs, CD-RWs, and the like. There are also magnetic tapes, non-volatile memory cards, ROMs, DVDs (DVD-ROM, DVD-R) and the like.

In addition, as a program supply method, a browser of a client computer is used to connect to an Internet homepage. Then, the computer program itself of the present invention or a compressed file including the automatic installation function can be supplied from the homepage by downloading it to a recording medium such as a hard disk.

It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from different homepages. That is, the present invention also includes a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer.

In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and the key information for decrypting the encryption is downloaded from the homepage to the user who clears the predetermined conditions. Let me. Then, by using the downloaded key information, it is also possible to execute an encrypted program and install it on a computer.

Further, the function of the above-described embodiment is realized by the computer executing the read program. In addition, based on the instruction of the program, the OS or the like running on the computer performs a part or all of the actual processing, and the function of the above-described embodiment can be realized by the processing.

Further, the program read from the recording medium is written to the memory provided in the function expansion board inserted in the computer or the function expansion unit connected to the computer. After that, based on the instruction of the program, the function expansion board, the CPU provided in the function expansion unit, or the like performs a part or all of the actual processing, and the function of the above-described embodiment is also realized by the processing.

It should be noted that the above-described embodiments merely show examples of embodiment in carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner by these. That is, the present invention can be implemented in various forms without departing from the technical idea or its main features.

100 File management server 101 LAN
200 client PC
201 CPU
202 RAM
203 ROM
204 System Bus 205 Input Controller 206 Video Controller 207 Memory Controller 208 Communication I / F (Interface) Controller 209 Input Device 210 Display Device 211 External Memory

Claims (15)

Information processing device,
A designated receiving means for accepting the designation of the first assembly and the second assembly,
To function as an output means for outputting a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match . program. The program according to claim 1 , wherein the output means functions as a means for outputting a comparison result relating to the hierarchy of the parts . It said output means, before Symbol comparisons results, the program according to any one of claims 1 or 2 to function as means for displaying on the display screen for each of the components. Said output means, the information first included in the assembly part is not included in part of the second assembly, the second does not include the part of the first assembly The program according to any one of claims 1 to 3 , for functioning as a means for identifiablely displaying at least one of the information contained in the parts of the assembly. A designated receiving means for accepting the designation of the first assembly and the second assembly,
An output means for outputting a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match .
An information processing device characterized by being equipped with. It is a control method for information processing equipment.
The designated reception means receives the designation of the first assembly and the second assembly, and the designated reception process.
Output means, and an output step of outputting a comparison result based on whether the first hierarchical information and the file name of the part in the assembly and hierarchy information and the file name of the component in the second assembly, is consistent ,
Control methods including . A designated receiving means for accepting the designation of the first assembly and the second assembly,
An output means for outputting a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match .
An information processing system characterized by being equipped with. It is a control method for information processing systems.
The designated reception means receives the designation of the first assembly and the second assembly, and the designated reception process.
Output means, and an output step of outputting a comparison result based on whether the first hierarchical information and the file name of the part in the assembly and hierarchy information and the file name of the component in the second assembly, is consistent ,
Control methods including . A program for controlling an information processing system
The information processing system
A designated receiving means for accepting the designation of the first assembly and the second assembly,
To function as an output means for outputting a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match . program. Information processing device,
A designated receiving means for accepting the designation of the first assembly and the second assembly,
To function as a comparison display means for displaying a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match. Program. A designated receiving means for accepting the designation of the first assembly and the second assembly,
A comparative display means for displaying a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match .
An information processing device characterized by being equipped with. It is a control method for information processing equipment .
The designated reception means receives the designation of the first assembly and the second assembly, and the designated reception process.
The comparison display means displays a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match. Process and
Control methods including . A designated receiving means for accepting the designation of the first assembly and the second assembly,
A comparative display means for displaying a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match .
An information processing system characterized by being equipped with. It is a control method for information processing systems .
The designated reception means receives the designation of the first assembly and the second assembly, and the designated reception process.
The comparison display means displays a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match. Process and
Control methods including . A program for controlling an information processing system
The information processing system
A designated receiving means for accepting the designation of the first assembly and the second assembly,
To function as a comparison display means for displaying a comparison result based on whether or not the hierarchical information and file name of the parts in the first assembly and the hierarchical information and file name of the parts in the second assembly match. Program.

Images