JP2016177843A - Information processing apparatus, information processing system, control method thereof and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make a user easily confirm a result of comparison between the constitution of an already transmitted file and the constitution of a file not yet transmitted.SOLUTION: An information processing apparatus that can communicate with a server for storing files is provided. The information processing apparatus transmits a file to the server, obtains an assembly of files which has been transmitted to the server and are stored in the information processing apparatus itself, obtains an assembly of transmitted files from the server, compares a first assembly obtained from the information processing apparatus itself with a second assembly obtained from the server, and displays the comparison result of the comparison on a display screen.SELECTED DRAWING: Figure 4

Description

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

  In a manufacturing industry or the like, 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, PDM not only stores electronic data, but also has various additional information and their revision information, as well as functions such as an authority system and an approval system. In recent years, operation as a system for realizing securing without burden has been promoted at design sites of various companies.

  In order to ensure the completeness, for example, a technique for creating a tree structure consistently using assembly and part data as components before creating a three-dimensional CAD file for creating design information stored in a PDM. (For example, Patent Document 1)

JP 2007-115164 A

  By the way, from the viewpoint of the confidentiality of the data in the PDM, there is a business operation in which a work for saving the three-dimensional CAD file in the PDM is permitted only to a specific worker, not a designer.

  In this case, for example, the designer does not create the 3D CAD file on the server designated as the storage / registration location of the 3D CAD file by the PDM, but the 3D CAD file on his / her personal PC. In order to register the 3D CAD file in the PDM, the 3D CAD file is handed over to a worker having authority to access the PDM and the registration work is requested.

  The number of files when saving a three-dimensional CAD file for one product varies from time to time, but in the case of a large number, it may reach 1000 to 10000 points (data capacity is several KB to several tens of MB per file). When storing data of this scale in a PDM (for example, an external device that stores actual data managed by the PDM) by an operation on the OS of the operator's PC (for example, cut and paste), for example, Depending on factors such as the number of files and the communication load between the PC and server (PDM) due to 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, some 3D CAD files It may not be saved to the PDM normally.

  However, even if some data is not saved, there is no means for notifying the worker who has performed the work, so the worker recognizes that his work has been completed. In other words, for example, when a 3D CAD file that should have been saved in the PDM at a later date is to be browsed, the data that could not be saved cannot be detected, and the design information remains insufficient. You can only browse in the state.

  In order to avoid this, when the operator finishes storing (transmitting) data to the PDM, for example, by viewing a file that has been stored (transmitted) in the PDM by a three-dimensional CAD application, the intended data configuration However, if the above-mentioned worker is not in charge of data design work, a 3D CAD application is not necessarily set on the worker's PC. It is not always done. In addition, when there is a lot of data constituting the file, in order to view the file, the worker's PC must be hardware capable of withstanding the file viewing (data calling and drawing processing for that purpose). Even if the file can be opened, it may take several minutes to open the file. Also, it takes time to check whether the three-dimensional CAD file is configured correctly. Therefore, it is very troublesome.

  An object of the present invention is to allow a user to easily confirm a comparison result between a configuration of a file that has already been transmitted and a configuration of a file before transmission.

  The information processing apparatus of the present invention is an information processing apparatus capable of communicating with a server that stores a file, a transmission unit that transmits the file to the server, and a file that has been transmitted to the server by the transmission unit, First assembly acquisition means for acquiring an assembly of a file stored in the information processing apparatus; second assembly acquisition means for acquiring an assembly of a transmitted file transmitted by the transmission means from the server; Comparison means for comparing the first assembly acquired by the first assembly acquisition means with the second assembly acquired by the second assembly acquisition means, and the comparison result compared by the comparison means are displayed on the display screen. And a comparison result display means.

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

  As a result, for example, the configuration of 3D CAD files can be compared between the same or different systems without using a 3D CAD application, so that an environment in which the 3D CAD application can be executed becomes unnecessary. Can save time to open a file, and even a worker with relatively little knowledge about 3D CAD applications and design can easily check the difference in configuration and efficiently and easily store it in the PDM. It is possible to confirm whether or not the configuration of the three-dimensional CAD file thus obtained is certain.

The figure which shows an example of the system configuration | structure of an information processing system in embodiment of this invention The figure which shows an example of the hardware constitutions of each apparatus in embodiment of this invention The figure which shows an example of a function structure of each apparatus in embodiment of this invention The flowchart which shows the outline | summary of a structure comparison process in embodiment of this invention. The flowchart which shows an example of the structure information acquisition process in embodiment of this invention The flowchart which shows an example of a structure comparison process in embodiment of this invention The figure which shows an example of a structure of the comparison result display screen of structure information in embodiment of this invention. The figure which shows an example of a structure of the structure information table in embodiment of this invention. The figure which shows an example of a structure of the structure information table 1 in embodiment of this invention. The figure which shows an example of a structure of the structure information table 2 in embodiment of this invention. The figure which shows an example of the mode of the transition of the comparison result display screen of structure information in embodiment of this invention The figure which shows an example of the mode of the transition of the comparison result display screen of structure information in embodiment of this invention The figure which shows an example of the mode of the structure information table update by the structure information acquisition process in embodiment of this invention. The figure which shows an example of the mode of the structure information table update by the structure comparison process in embodiment of this invention The figure which shows an example of the mode of the structure information table update by the structure comparison process in embodiment of this invention The flowchart which shows an example of the file upload process in embodiment of this invention The flowchart which shows an example of the detail of the reception process of the object file 2 in embodiment of this invention. The figure which shows an example of the reference restriction information of the object file in the embodiment of the present invention The figure which shows an example of the log | history table of the file upload in embodiment of this invention

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

  With reference to FIG. 1, an example of the system configuration of the information processing system in the embodiment of the present invention will be described. FIG. 1 is a diagram illustrating an example of a system configuration of an information processing system in 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 here is an assembly in a three-dimensional CAD file (three-dimensional model data), and specifically, for example, a file specified from the assembly (a component of the three-dimensional CAD file = part data, etc.) It is assumed that the information includes storage location, configuration order, presence / absence of a reference file, file status (configuration), number, and the like.

  The 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 files and file configuration information (assembly). In addition, 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 here is, for example, a three-dimensional CAD file.

  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 a PDM and a comparison tool (a tool as an add-on function of the PDM) that performs the above-described configuration information comparison process in a predetermined area. As described above, the PDM is installed in both the client PC 200 and the file management server 100, and the PDM installed in the client PC 200 is a case where the client PC 200 (comparison tool) requests data from the PDM of the file management server. API (Application Programming Interface / hereinafter referred to as API).

  The file uploaded from the client PC 200 is stored and held in the external memory of the file management server 100 by the file management server 100, and the PDM of the file management server 100 manages the storage location, state of the file, data analysis, It is assumed that analysis results are sent and received.

  When the PDM of the client PC 200 is activated, the CPU of the client PC 200 reads out the comparison tool as the add-on from a specific folder on the storage area of the client PC, and activates the comparison tool on the menu screen of the PDM. Show button.

  Then, when an instruction to press the activation button is received, the comparison tool is activated, and the processes of FIGS. 4 to 6 are executed in accordance with an operation instruction from the user. The above is the description of an example of the system configuration of the information processing system in 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 illustrating an example of a hardware configuration of each device in the embodiment of the present invention.

  In FIG. 2, reference numeral 201 denotes 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 BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS), which is a control program of the CPU 201, or a function executed by each server or each PC. Various programs to be described later are stored.

  A RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program or the like necessary for execution of processing from the ROM 202 or the external memory 211 into the RAM 203 and executing the loaded program.

  An input controller 205 controls input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown). A video controller 206 controls display on a display device such as a CRT display (CRT) 210. In FIG. 2, although described as CRT 210, the display device is not limited to the CRT, but may be another display device such as a liquid crystal display. These are used by the administrator as needed.

  A memory controller 207 is connected to the hard disk (HD), flexible disk (FD), or PCMCIA card slot for storing a boot program, various applications, font data, user files, editing files, various data, etc. via an adapter. The access to the external memory 211 such as a compact flash (registered trademark) memory is controlled.

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

  Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  Various programs to be described later for realizing the present invention are recorded in the external memory 211 and executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information tables used when executing the program are also stored in the external memory 211, and a detailed description thereof will be described later. The above is an explanation of an example of the hardware configuration of each device in the embodiment of the present invention shown in FIG.

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

  The file configuration storage unit 321 is a storage unit that stores file configuration information (assembly / assembly 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 configuration information of a file stored in the external memory of the client PC 200 that has received a designation for uploading 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 configuration information of a file that has already been transmitted to the file management server 100 (corresponding to an assembly request unit), 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 and 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 result 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 receives an upload. The upload file configuration information storage unit 312 is a storage unit that stores configuration information (assembly file) of a file (upload file / 3-dimensional CAD file) received by the upload file reception unit 311 (corresponding to an assembly storage unit). .

  The upload file configuration information acquisition unit 313 is an acquisition unit that acquires configuration information of an upload file (transmitted file / sent 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 an assembly transmission unit). The above is 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 file upload processing according to the embodiment of the present invention.

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

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

  For example, 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 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 active PDM), the selected file is transmitted to the folder path of the file management server 100 being expanded in the PDM window (step S1602).

  For example, when the file selected as the transmission target is a folder, the file and data in the folder are transmitted to the transmission destination. In the folder, for example, a 3D CAD file, a file necessary for configuring the 3CAD file (for example, part data configuring model data in the 3D CAD file), and a reference relationship of the configuration are shown. Assembly information (assembly file) and the like are included.

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

  Note that 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 not limited to the above-described 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 (predetermined storage area of the file management server 100) (step S1603). ) If the transmission has been completed, the process ends. If the transmission has not been completed, 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). The predetermined number of values 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 the predetermined number has been exceeded, the process is terminated. If it is determined that the predetermined number has not been exceeded, one selected file is acquired and transmission processing 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 and the IP address (identification information) of the client PC 200 are stored, It is assumed that a request for storing the information as a history is transmitted together with information on where the device is stored.

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

  Further, 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, etc. Store information and store in external memory. The history table will be described later with reference to FIG.

  Here, an example of a file upload history table in 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 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 source IP 1903 is identification information of the upload source device (here, the client PC 200) of the file. The migration source path 1904 is the folder path of the upload source of the file (here, the folder path of the storage location immediately before the upload in the client PC 200).

  The destination IP 1905 is identification information of the upload destination device (here, the file management server 100) of the file. The destination path 1906 is a folder path to which the file is uploaded (here, the folder path where the file is stored in the file management server 100). The above is an explanation of an example of a 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 according to the transmission instruction (step S1608). For example, when a plurality of transmission target files are designated and the plurality of files are transmitted to the transmission destination, a process of acquiring one transmission target file and transmitting it to the transmission 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.

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

  When it is determined that a predetermined time has elapsed since 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 subsequent file transmission is difficult from the file capacity and the communication status with the file management server 100, and performs transmission processing of the file being transmitted and the untransmitted file selected as the transmission target. The process is interrupted and the process is terminated. If it is determined that the predetermined time has not elapsed since 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 in step S1605 is completed (step S1609). If it is determined that the transmission has been completed, the process returns to step S1603. If it is determined that the transmission has not been completed, the transmission process is continued. The above is an explanation of an example of the file upload process in the embodiment of the present invention shown in FIG.

  Next, with reference to FIG. 4, an outline of the configuration comparison processing in the first embodiment of the present invention will be described. FIG. 4 is a flowchart showing an outline of the configuration comparison process in the first embodiment of the present invention. Note that steps S401 to S412 are performed under the control of the CPU 201 in the client PC 200.

  When the processing shown in FIG. 4 is performed, the CPU 201 of the client PC 200 is in a state where it can communicate with the file management server 100 (PDM).

  In step S401, the CPU 201 of the client PC 200 accepts a command activation operation (operation for activating the configuration information comparison tool) by the operator on the menu screen of the PDM (not shown), thereby displaying the command dialog 700 shown in FIG. indicate. The command dialog 700 is an example of a configuration information comparison result display screen 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. FIG. 7 is a diagram illustrating 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) includes 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 execution button 707, an end button 708, and the like.

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

  In the file selection screen (not shown) displayed when the reference button 702 is pressed, only files stored in the external memory of the client PC 200 can be referred to and designated.

  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. When the CPU 201 of the client PC 200 accepts pressing of the reference button 702, the reference restriction information is displayed. The file path that can be referred to is specified on the file selection screen, and if an unreferenceable file path is accepted, an error is displayed and the unreferenceable file path is not displayed (see Control).

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

  The reference restriction information 1800 is set according to a user operation instruction on a restriction information setting screen (not shown) when the comparison tool is set in the client PC 200, and the CPU 201 of the client PC 200 generates restriction information of the comparison tool. Assume that it is generated 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 indicates the target file 1 and the target file 2 shown in the command dialog 700 of FIG. When the pressing of the reference button 702 is accepted, the restriction information in which “target file 1” is inserted into the target file 1802 is applied. When the pressing of the reference button 705 is accepted, the restriction information in which “target file 2” is inserted into the target file 1802 is applied.

  The reference destination IP 1803 is identification information of a device that is allowed to refer to a file path on a file selection screen (not shown). Although an IP address is inserted here, any information can be used as long as it can identify the device.

  A reference destination path 1804 indicates a file path that is allowed to be referenced on a file selection screen (not shown). In a file selection screen (not shown), only a file path below the file path set in the reference destination path 1804 can be specified and referred to.

  Note that the reference destination IP 1803 of the target file 1802 = “target file 1” is obtained when the CPU 201 of the client PC 200 acquires and inserts the IP address of the own device when the comparison tool is set and stored in the client PC 200. Is set by

  When the comparison tool is set and stored in the client PC 200, the reference IP 1803 of the target file 1802 = “target file 2” is, for example, a file management in response to a user operation instruction on a restriction information setting screen (not shown). 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 accepted the upload instruction), and the target file 2 = file. It is an uploaded (sent) file stored in the management server 100 (PDM).
The above is 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 that displays the configuration information of the comparison target file (here, the target file 1) that is 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 specification of the target file 1 In this case, the file path of the file corresponding to the target file 1 (the file after upload when the target file 1 = the file before upload) is acquired from the file management server 100 and displayed.

  The list box 706 is a box that displays the configuration information of the comparison target file (here, the target file 2) acquired and generated by the configuration information acquisition process of FIG.

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

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

  Returning to the description of FIG. In step S402, the reception process of the target file 1 (comparison target file / file for comparing configuration information with other files) by the operator is performed. Specifically, by receiving an instruction to press the reference button 702 in the command dialog 700 of FIG. 7 by the operator, 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 selection accepting 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 proceeds to step S404 (corresponding to the first assembly acquisition unit). The configuration information table 1 is stored in the external memory of the client PC 200.

  Here, the configuration information acquisition processing performed in step S403 in FIG. 4 (and step S406 in FIG. 4 described later) will be described using the configuration information table 800 in FIGS.

  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 a configuration information table according to the embodiment of the present invention.

  The configuration information table 800 includes record No. 801, level 802, folder path 803, file name 804, configuration path 805, type 806, configuration name 807, number 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 processing file structure hierarchy. 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 processing file configuration order.

  Here, the configuration order will be described using 900 (configuration information table 1) in FIG. The configuration order indicates a reference relationship path in a general three-dimensional CAD. For example, the file received in step S502 in FIG. 5 (assuming TopAssy) is positioned at the apex of the file structure (configuration), so 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) in FIG. 9 corresponds to this. Furthermore, the configuration path of a file that has a secondary reference relationship with TopAssy is TopAssy / Assy1. Specifically, record Nos. 3 to 5 shown in 900 (configuration information table 1) in FIG. 9 correspond to this.

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

  The number 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 referred to as the first condition). The determination 809 stores processing file existence information and a 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. If 2 is not specified, the common processing is performed. The above is an example of the configuration of the configuration information table in the embodiment of the present invention shown in FIG.

  Next, an example of configuration information acquisition processing 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 in the embodiment of the present invention. Note that each of steps S501 to S516 is performed 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 selection operation of the target file received in step S402 in FIG. 4, reception processing of the file to be processed is performed, and the creation of the configuration information table 800 in FIG. 8 is the same as the configuration information table. A temporary record having only one record having a configuration is created.

  In addition, when the restart process of this process is performed in step S516 described later, the file received from step S515 is the processing target. In the restart process, a new configuration information table is not created. That is, the reference file of the target file that has been selected from 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 accepted in step S501 is acquired, and the folder path from which the file name has been removed is stored in the folder path 803 of the temporary record.

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

  In the following, the various information acquisition process (information acquisition process of the configuration information table 800) in steps S504 to S507 is the target file 1 (file stored in Klein and the external memory of the PC 200) in step S501. If there is, the active comparison tool makes an acquisition request for various information to the API of the 3D CAD application set in the Klein and the PC 200, and information on the result corresponding to the acquisition request is sent from the API of the 3D CAD application. Executed by receiving.

  When 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 activated comparison tool includes various information in the PDM API. This is executed by making an acquisition request and receiving information on the result corresponding to the acquisition request from the API of the PDM.

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

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

  In step S506, the configuration order specified by the three-dimensional CAD or PDM API for the file received in step S501 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 obtained in the process of performing step S506 (corresponding to the above-described hierarchical reference relationship) is acquired from the 3D CAD or PDM API and stored in the level 802 of the temporary record. Then, the process proceeds to step S508.

  In step S508, for the configuration information table being processed, search processing is performed for a record in which the temporary record matches the values 802 to 807 in FIG. If no matching record is detected, the process proceeds to step S509. 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 as a new record to the configuration information table, 1 is stored in the number 808, and the process proceeds to step S511.

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

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

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

  In step S513, the processing migration destination is determined based on the processing file type 806. Here, Assy is a type that is assumed to have a reference file, and Part is a type that is assumed to have no reference file. If the type of processing file is Assy, the process proceeds to step S514, and the processing file If the type is Part, the configuration information acquisition process ends.

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

  In step S515, it is determined whether or not there is an unprocessed file for the file acquired in step S514. If there is an unprocessed file, the configuration information acquisition process is restarted by shifting the process to step S516. That is, one of the acquired reference files is acquired, the acquired file is received in step S501, and the processing of steps S502 to S516 is applied thereafter.

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

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

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

  Items to be displayed are seven items of folder path, file name, configuration path, type, configuration name, and number in the columns of the configuration information table 1. In addition, a list box background color change process is performed to effectively suggest the result of the configuration information acquisition process to the operator. Specifically, 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 in the records of the configuration information table 1 900 in FIG. As a result, the comparison result of the configuration information of the file is shown (here, the file to be compared with the file (the file from which configuration information is acquired in step S406 described later) is not acquired. Comparison results are shown). The specific processing result (comparison result) of step S404 is shown in, for example, a command dialog 1100 in FIG.

  In step S405, the target file 2 whose configuration is compared with the target file 1 is received (corresponding to the second assembly acquisition unit). Details of the reception process of the target file 2 will be described later with reference to FIG.

  Here, with reference to FIG. 17, an example of the details of the reception process of the target file 2 in the embodiment of the present invention will be described. 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, folder path, and IP address of the client PC 200 to the file management server 100 (PDM) (step S1701).

  The file management server 100 (PDM) receives this (step S1702), and in the history table 1900 stored in the external memory, the file and file name (file name 1902), source device (source IP 1903). Then, it is determined whether there is a history that matches the folder path (source path 1904) (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).

  If it is determined that the received information is the folder path of the target file 2, the information on 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 ends. .

  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 for which the selection has been accepted 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 reference destination folder path specified on the file selection screen for selecting a file is the target restriction file 1802 = “target file” in FIG. 2 ”, the file management server 100 (reference destination IP = 182.16.YYY.ZZZ) is limited to folders under“ ¥¥ Server ¥ PDM ¥ data ”.

  That is, when designation of a reference destination other than the above-described reference destination is received on the file selection screen (not shown), the CPU 201 (comparison tool) of the client PC 200 cannot display a reference destination other than the above-described reference destination. Is displayed, and control is performed not to select a file from other than the file management server 100. The above is an explanation of an example of the 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, configuration information acquisition processing 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). The details of the configuration information acquisition process have been described above with reference to FIG.

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

  The configuration information table 2 indicating the configuration information of the target file 2 shown in 1000 of FIG. 10 is created by the processing of step S406, stored in the external memory of the client PC 200, and the processing proceeds to step S407.

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

  In step S408, an execution button 707 reception process of the command dialog 700 in FIG. If a 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. The configuration information table 1 shown at 900 in FIG. 9 is updated to the state shown at 950 in FIG. 9 by the processing of step S409, the configuration information table 2 shown at 1000 in FIG. 10 is updated to the state shown at 1050 in FIG. The processing is shifted to S410.

  Here, the configuration comparison processing performed in step S409 will be described with reference to FIG. FIG. 6 is a flowchart showing an example of the configuration comparison process in the embodiment of the present invention. The steps S601 to S617 are performed 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. 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 there is a file in the configuration information table 1 to which the processing in steps S601 to S609 has not been applied.

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

  In step S603, the first condition is determined to match the record 1 described above and the record delivered from step S602 (hereinafter, record 2) (that is, the processing file and file name 804, the configuration path 805, and the type 806). It is determined whether or not all three match). If they match, the process proceeds to step S604, and if they do not match, the process proceeds to step S602. When the process proceeds to step S602, the record 2 to which the process up to step S603 is applied is handled as a processed record. Information regarding whether or not the processing is completed is 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.

  In step S604, the order of record 2 in the configuration information table 2 is moved to the same record No as the order of record 1 (record No. 801 in the configuration information table 800), and the process proceeds to step S605. That is, in the command dialog 700, when the user compares and confirms the configuration information shown in the configuration information table 1 and the configuration information table 2, the record 1, the record 1, the processing file, the file name 804, and the configuration path are displayed. 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 type 806 match are matched.

  As a result, the record 2 is displayed right next to the record 1 in the list box 703. In other words, when the user visually compares and checks the records, the user simply looks at the record 2 positioned directly beside the record 1 to be checked, and whether or not there is a difference in the status between the record 1 and the record 2. You can check the contents.

  In step S605, a determination process of matching (hereinafter, second condition) of both the configuration name 807 and the number 808 of the record 1 and the record 2 is performed, and the process proceeds to step S606 regardless of the match or mismatch. However, if they do not match, a record in which the record 1 matches both the first condition and the second condition is detected from the processed records in the table 2, and if it is detected, the detected record is recorded in the table 2 as the record 1 Move to the same No as the order.

  In step S606, the update process of the determination 809 of the record 1 is performed by the determination process of step S605, and the process proceeds to step S602. In the update process, based on the comparison result between the record 1 and the record 2, the decision 1 809 of the record 1 and the record 2 is set to 0 when the first condition matches the second condition, and 1 when only the first condition matches. Store each one. Here, storing 0 indicates that there is a configuration file having the same configuration information in table 2 with respect to record 1, and storing 1 indicates that the same configuration file is stored 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 that match the first condition in the configuration information table 2 for the record 1, and if there are one or more records, the process proceeds to step S601. If there is no item, the process proceeds to step S608. When the processing is shifted to step S601, record 1 up to step S607 is handled as a processed record.

  In step S608, a blank record is newly added to the same No as the order of record 1 in Table 2, and the process proceeds to step S609.

  In step S609, the value 2 is stored in record 1 and the record determination 809 added in step S608, and the process proceeds to step S601. Storing 2 here means that table 1 and table 2 are compared even if there is no configuration file with matching configuration information in table 2 for record 1 or even if there is a configuration file with matching configuration information. In this case, there is no paired record (a state in which a pair with another record has already been confirmed even if the configuration information matches).

  FIG. 14 shows a state of the processing (configuration comparison processing) in 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, a determination is made as to whether an unapplied file exists in steps S611 to S617). One unprocessed file is acquired from the table 2, and the process proceeds to step S611. If there is no unprocessed file, the configuration comparison process is terminated.

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

  In step S612, the first condition is determined to match for record 2 and record 1 delivered from step S611 (that is, whether or not all of the processing file and file name 804, configuration path 805, and type 806 match). If they match, the process proceeds to step S613. Otherwise, the process proceeds to step S611. When the process proceeds to step S611, record 1 to which the process up to step S612 is applied is handled as a processed record.

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

  In step S614, the update process of the record 809 and the record 1 determination 809 is performed by the determination process of step S613, and the process proceeds to step S611. In the update process, based on the comparison result between the record 2 and the record 1, the determination 809 of the record 2 and the record 1 is performed. If the first condition and the second condition are matched, 0 is set. Store each one. When a blank record is added in step S614, 1 is stored in the determination 809 of the table 2 and the table 1, respectively.

  In step S615, it is determined whether or not there is one or more records that match the first condition in the table 1 with respect to the record 2. If there are one or more records, the process proceeds to step S610. The process proceeds to S616. When the process proceeds to step S610, record 2 up to step S615 is handled as a processed record.

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

  In step S617, 3 is stored in record 2 and the record determination 809 added in step S616, and the process proceeds to step S601. Storing 3 here means that table 1 and table 2 are compared even if there is no configuration file with the same configuration information in table 1 for record 2 or there is a configuration file with the same configuration information. In this case, there is no paired record (a state in which a pair with another record has already been confirmed even if the configuration information matches).

  FIG. 15 shows a state of the processing (configuration comparison processing) in 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 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 in FIG. 7 are updated using the configuration information table 1 shown in 950 in FIG. 9 updated in step S409 by the same procedure as in step S404, and the process proceeds to step S411. At this time, the list box background color changing process is performed in order to effectively suggest the result of the structure comparison process (comparison result) to the operator.

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

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

  In step S412, a command end acceptance process (configuration information comparison tool end instruction acceptance process) is performed. Specifically, when the operator presses the end button 708 in FIG. 7, the command dialog 700 in FIG. 7 is hidden, and the process ends. The above is the description of the outline of the configuration comparison process in FIG. 4 according to the first embodiment of the present invention.

  As described above, according to the present invention, the user can easily check 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 being uploaded to the external device matches the configuration of the file after being uploaded to the external device, and the user can be confirmed whether the file has been 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. In particular, in the case of large-scale configuration information, it is not necessary to read a file by a 3D CAD application, so that the time until the 3D CAD application opens the file can be omitted.

  In addition, for example, the user can easily check the difference in the configuration information without expanding the file with a 3D CAD application and comparing / matching the results, and it 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 above-described first embodiment of the present invention, 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, if the history table is not refined when the file is transmitted to the file management server 100 in step S1605 of FIG. 16, a new history table is generated and the history information of the file to be transmitted to the file management server 100 is stored. In addition to the history table, it is stored in the external memory of the client PC 200. The destination IP 1905 is acquired from the file management server 100 and stored in the history table after the file transmission.

  In this case, it is assumed that the CPU 201 of the client PC 200 executes all the processes in 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. In the second embodiment, the respective files are acquired. Let the user choose freely.

  In this way, when a file is moved or transmitted, the file structure before moving and the file structure after moving regardless of whether the device that stores the file before and after moving is different. The user can easily check the comparison result.

  Hereinafter, in the second embodiment, description of parts that are the same as those in the first embodiment described above will be omitted, and parts that are different from those 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 in FIG. In step S402, the information on the folder path designated by the user is displayed in a selectable manner 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 process of accepting the target file 2 shown in FIG. 17 is not executed, and the process waits until the press of the reference button 705 is accepted with the command dialog 700 of FIG. 7 displayed on the display screen.

  When the CPU 201 of the client PC 200 accepts pressing of the reference button 705, the CPU 201 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 on the folder path designated by the user is displayed in a selectable manner 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.

  Thereafter, the process proceeds to step S406, and the processes of steps S406 to S412 are executed by the same method 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 file configuration before the movement and the file configuration after the movement are not affected, regardless of whether the device for storing the file before and after the movement is different. The comparison result can be easily confirmed by the user.

  The present invention can be implemented as a system, apparatus, method, program, storage medium, or the like, and can be applied to a system including a plurality of devices. You may apply to the apparatus which consists of one apparatus.

  Note that the present invention includes a software program that implements the functions of the above-described embodiments directly or remotely from a system or apparatus. The present invention also includes a case where the system or the computer of the apparatus is achieved by reading and executing the supplied program code.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

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

  Examples of the recording medium for supplying the program include a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, and CD-RW. In addition, there are magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD-R), and the like.

  As another program supply method, a browser on a client computer is used to connect to an Internet home page. The computer program itself of the present invention or a compressed file including an automatic installation function can be downloaded 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 a different homepage. That is, 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 is also included in the present invention.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. Let It is also possible to execute the encrypted program by using the downloaded key information and install the program on a computer.

  Further, the functions of the above-described embodiments are realized by the computer executing the read program. In addition, based on the instructions of the program, an OS or the like running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

  Further, the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiments are realized by the processing.

  Note that the above-described embodiments are merely examples of implementation in carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner. That is, the present invention can be implemented in various forms without departing from the technical idea or the main features thereof.

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

An object of the present invention is to provide a mechanism that allows a user to easily confirm the comparison result of the configuration of the first assembly and the second assembly .

The program according to the present invention includes: an information processing apparatus that includes a first subassembly or a first subassembly constituting a first assembly; a first subassembly comprising a hierarchical information and a file name of a part; Receiving means for accepting designation of the second assembly having part hierarchy information and file name, and hierarchical information and file name of the first subassembly or part constituting the first assembly that has accepted designation by the accepting means. Determining means for determining whether or not the hierarchical information and the file name of the second subassembly or part constituting the second assembly match, and the result of determination by the determining means is displayed on the display screen It is made to function as a display control means to control to do.

According to the present invention, it is possible to provide a mechanism that allows the user to easily confirm the comparison result of the configuration of the first assembly and the second assembly .

Claims (9)

An information processing apparatus capable of communicating with a server storing a file,
Transmitting means for transmitting a file to the server;
First assembly acquisition means for acquiring an assembly of a file which has been transmitted to the server by the transmission means and is stored in the information processing apparatus;
Second assembly acquisition means for acquiring the assembly of the transmitted file transmitted by the transmission means from the server;
Comparing means for comparing the first assembly obtained by the first assembly obtaining means with the second assembly obtained by the second assembly obtaining means;
Comparison result display means for displaying a comparison result compared by the comparison means on a display screen;
An information processing apparatus comprising:   The assembly is information indicating the configuration of the three-dimensional model data, and the configuration information of the three-dimensional model data including identification information, storage location, configuration order, type, state, and number of the components of the three-dimensional model data The information processing apparatus according to claim 1, wherein:   3. The comparison unit according to claim 1, wherein the comparison unit compares whether the configuration order of the components indicated by the first assembly matches the configuration order of the components indicated by the second assembly. 4. Information processing device.   The said comparison result display means displays the said 1st assembly and the said 2nd assembly on a display screen so that the result of the said comparison means can be identified, The any one of Claim 1 thru | or 3 characterized by the above-mentioned. The information processing apparatus described.   The second assembly acquisition unit acquires the second assembly corresponding to the first assembly acquired by the first assembly acquisition unit, using a file transmission history by the transmission unit. The information processing apparatus according to any one of claims 1 to 4. Selection accepting means for accepting selection of an assembly of a file that has been sent to the server by the sending means and is stored in the information processing apparatus;
6. The information processing apparatus according to claim 1, wherein the first assembly acquisition unit acquires an assembly whose selection is received by the selection reception unit as the first assembly. 7. A method for controlling an information processing apparatus capable of communicating with a server storing a file,
A sending step for sending the file to the server;
A first assembly acquisition step of acquiring an assembly of files that have been transmitted to the server in the transmission step and stored in the information processing apparatus;
A second assembly acquisition step of acquiring the assembly of the transmitted file transmitted in the transmission step from the server;
A comparison step of comparing the first assembly acquired in the first assembly acquisition step with the second assembly acquired in the second assembly acquisition step;
A comparison result display step of displaying the comparison result compared in the comparison step on a display screen;
A method for controlling an information processing apparatus, comprising: A program that can be executed by an information processing apparatus that can communicate with a server that stores a file,
The information processing apparatus;
Transmitting means for transmitting a file to the server;
First assembly acquisition means for acquiring an assembly of a file which has been transmitted to the server by the transmission means and is stored in the information processing apparatus;
Second assembly acquisition means for acquiring the assembly of the transmitted file transmitted by the transmission means from the server;
Comparing means for comparing the first assembly obtained by the first assembly obtaining means with the second assembly obtained by the second assembly obtaining means;
A program for an information processing apparatus that functions as comparison result display means for displaying a comparison result compared by the comparison means on a display screen. An information processing system including an information processing apparatus that stores an assembly of a file before transmission and a server that stores an assembly of the file after transmission,
The server
Assembly storage means for storing an assembly of files received from the information processing apparatus;
Assembly transmission means for transmitting the assembly to be acquired by the information processing apparatus in response to a request from the information processing apparatus;
With
The information processing apparatus includes:
Transmitting means for transmitting a file to the server;
First assembly acquisition means for acquiring an assembly of a file which has been transmitted to the server by the transmission means and is stored in the information processing apparatus;
Assembly request means for requesting the server to obtain the assembly of the transmitted file transmitted by the transmission means;
Second assembly acquisition means for acquiring an assembly received from the server in response to a request by the request means;
Comparing means for comparing the first assembly obtained by the first assembly obtaining means with the second assembly obtained by the second assembly obtaining means;
Comparison result display means for displaying a comparison result compared by the comparison means on a display screen;
An information processing system comprising:

Images