JP2012238285A - Pdm system, data registration method and data registration program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a PDM system capable of improving efficiency in managing registered data and capable of speeding up retrieval of the registered data.SOLUTION: As databases for storing template information regarding data files consisting of various documents and drawings including specifications, circuit diagrams and the like, a PDM system comprises: a template storage section 31 for managing version numbers of templates; an assignment number storage section 32 for managing assignment numbers of the templates; an attribute storage section 33 for managing attributes for defining keywords for retrieval of data files applied with the templates. In response to a number assignment request by a terminal device 1, the assignment number of the template is automatically updated and registered in the assignment number storage section 32. When there is a data registration request from the terminal device 1, whether the template to be applied to the registering data is the latest version or not is automatically checked, and an attribute name inputted from the terminal device 1 for each attribute regarding the registering data is registered in the attribute storage section 33 as a keyword for retrieval.

Description

  The present invention relates to a PDM system, a data registration method, and a data registration program used for facilitating obtaining accurate parts information and the like.

  A PDM (Product Data Management) system is a system that centrally manages data related to design and manufacturing. And BOM for centrally managing each part constituting a product as described in Japanese Patent Application Laid-Open No. 2005-004627, “Parts Table Editing Method and Editing System”, and the like. We are trying to realize a mechanism that makes it easy to obtain accurate parts information by devising various configurations of (Bills Of Materials).

JP2009-238086 (page 7-9) Japanese Patent Laying-Open No. 2005-004627 (page 3-5)

  A PDM system that manages design information and product information is generally configured to include various documents and drawings such as specifications and circuit diagrams in addition to the BOM (Bills Of Materials) described above. One of the important requirements is that information on these various documents and drawings can be managed and utilized accurately and easily.

  However, in the current PDM system, when a document / drawing is registered, the numbering number is manually transferred to the document data, so that a transfer error occurs. In other words, the document number is numbered in the PDM system, and when the data is created in the terminal, the numbered document number is transcribed, and then the created data is registered in the PDM system, resulting in a transcription mistake. Resulting in.

  Even when the latest document / drawing format is provided, the old format is still registered in the PDM system. That is, in the case of the current PDM system, a template for data registration to be used when registering data is determined, and even if the latest template is prepared, if the existing data is used, Since it is possible to register an old format using a template, management data is deficient and it becomes difficult to thoroughly manage data.

  Furthermore, when searching for registration data of the PDM system, the search time is required enormously as the number of registered data and the capacity increase in order to search the data file itself using full text search and image search. There is also a problem that it ends up. In other words, when searching for data, the search time increases in proportion to the number of data in order to search the registered data file by full text search or image match search. Furthermore, when there are a plurality of target data to be searched, a search in the data file is required for each target data, and therefore, the search time is further increased depending on the number of data.

(Object of the present invention)
The present invention has been made in view of such circumstances, and by devising a template for data to be registered, it is possible to prevent the occurrence of data management deficiencies and to speed up the search for registered data. An object of the present invention is to provide a PDM system, a data registration method, and a data registration program that can be used.

  In order to solve the above-described problems, the PDM system, data registration method, and data registration program according to the present invention mainly adopt the following characteristic configuration.

  (1) A PDM system according to the present invention is a PDM (Product Data Management) system for managing design information and product information. A template for a data file consisting of various documents / drawings including at least a specification and a circuit diagram is used as the data. It is registered as a database together with attributes for defining a file search keyword, information indicating the version number and numbering of the template.

  (2) A data registration method according to the present invention is a data registration method in a PDM (Product Data Management) system for managing design information and product information, and includes data consisting of various documents and drawings including at least specifications and circuit diagrams. A template relating to a file is registered as a database together with attributes for defining a keyword for searching the data file, information indicating the version number and numbering of the template.

  (3) A data registration program according to the present invention is characterized in that at least the data registration method described in (2) is implemented as a program executable by a computer.

  According to the PDM system, data registration method, and data registration program of the present invention, the following effects can be obtained.

  First, by defining a template including attributes and matching attributes (items) defined as templates with attributes for managing registered data files, attributes for each attribute from the registered data file Since the name (item name) can be managed separately, the attribute (item) content that is also a keyword for specifying the registration data file can be separated and registered as a database on the template side, Registration data files can be managed more reliably.

  Secondly, since the attribute (item) content that is a keyword for searching the registered data file is separated from the registered data file and registered as a database on the template side, the entire text in the actual registered data file is stored. There is no need to perform search and image search, the search range can be narrowed down, and the search time for the registered data file can be greatly shortened.

  Third, since the version number of the template applied to the data file to be registered is set and managed in the database, the version number of the latest version is always checked by checking the version number of the template at the time of data registration. The data using the template can be registered, there is no fear of management failure, and management can be efficiently performed with high reliability.

  Fourth, the number assigned automatically in response to the numbering request for the template is registered in the database, and the numbering result can be output to the terminal device at the time of data creation. There is no need to manually transcribe, and it is possible to reliably prevent the occurrence of numbering mistakes.

It is a system configuration figure showing an example of a system configuration of a PDM system by the present invention. It is a flowchart which shows an example of numbering request | requirement operation | movement when request | requiring numbering to a template in the PDM system shown in FIG. 3 is a flowchart showing an example of a data registration request operation when requesting data registration in the PDM system shown in FIG. 1. 3 is a flowchart showing an example of a search request operation when a data search is requested in the PDM system shown in FIG. FIG. 3 is a schematic diagram illustrating an example of a numbering / registration request screen displayed when the terminal device illustrated in FIG. 1 requests a numbering of a template from the information processing apparatus. It is a schematic diagram which shows another example of the numbering / registration request screen displayed when the terminal device shown in FIG. 1 requests numbering of a template from the information processing apparatus. FIG. 3 is a schematic diagram illustrating an example of a search request screen displayed when the terminal device illustrated in FIG. 1 requests the information processing device to search for registered data. It is a schematic diagram which shows an example of the data registration template used when the terminal device shown in FIG. 1 registers data with an information processing apparatus. FIG. 9 is a schematic diagram illustrating an example of input data (attributes) when a terminal device registers a data file in an information processing device using the data registration template illustrated in FIG. 8. It is a table which shows an example of the template information registered into the template memory | storage part of the memory | storage device shown in FIG. It is a table which shows an example of the numbering information registered into the numbering memory | storage part of the memory | storage device shown in FIG. It is a table which shows an example of the attribute information registered into the attribute memory | storage part of the memory | storage device shown in FIG.

  Preferred embodiments of a PDM system, a data registration method, and a data registration program according to the present invention will be described below with reference to the accompanying drawings. In the following description, the PDM system and the data registration method according to the present invention will be described. However, the data registration method may be implemented as a data registration program executable by a computer, or the data registration program. It goes without saying that may be recorded on a computer-readable recording medium.

(Features of the present invention)
Prior to the description of the embodiments of the present invention, an outline of the features of the present invention will be described first. In the PDM (Product Data Management) system that centrally manages design information and product information, the present invention is highly capable of registering and retrieving data such as various documents and drawings including at least specifications and circuit diagrams. The main feature is to provide a mechanism that is reliable and efficient.

  That is, in the PDM system of the present invention, a mechanism for automatically assigning a numbering number and version number to a template for registered data, and a keyword for searching registered data along with the numbering number and version number in the template. Data registration and data search can be performed with high reliability and efficiency by adopting a mechanism for registering as a database for templates separated from data files in a format that provides attributes (items) for defining data. It is possible to do. That is, with respect to attributes (items) for defining a data file template to be registered in the PDM system together with automatically assigned number / version number and creating a database, and defining keywords in the registered data file Also, a mechanism is adopted in which attributes (items) in the template applied to the data file are registered separately from the data file in the database on the template side.

  When such a mechanism is adopted, it is possible to narrow down the search range at the time of data search by separating and managing the registration data file and the data related to the attribute name (item name) in the registration data file Therefore, the search can be performed at a higher speed than the case of using a search method that performs full text search and image search of a file.

  In addition, the present invention enables the check of the version number of the template applied to the data file at the time of data file registration using the automatically assigned number / version number. Since it is possible to register data using the template, it is possible to prevent deficiencies in data management.

(Configuration example of embodiment)
Next, an example of the system configuration of the PDM system according to the present invention will be described with reference to FIG. FIG. 1 is a system configuration diagram showing an example of a system configuration of a PDM system according to the present invention. A PDM system 100 shown in FIG. 1 includes a terminal device 1 and a configuration / document registration device 2. The terminal device 1 includes a user interface for a user to operate and output a screen display to the user, and the device is used by the user to operate the configuration / document registration device 2.

  The configuration / document registration apparatus 2 includes at least a storage device 3 that stores data and an information processing device 4 that executes a processing request from the terminal device 1. The storage device 3 includes at least a template storage unit 31, a numbering storage unit 32, and an attribute storage unit 33 as a database for registering information related to the template in addition to the area for registering the data file. Includes at least input / output means 41, template selection means 42, format check means 43, and information registration means 44.

  The template storage unit 31 in the storage device 3 stores a template for data registered in the information processing device 4 by the terminal device 1 in a state in which the version number is managed. Here, the registration data template provided to the terminal device 1 has a format as shown in FIG. 8, for example, and a template ID 51 for uniquely identifying the template and a version number A52 indicating the version number of the template. Is presented to the terminal device 1 in a state of being attached. FIG. 8 is a schematic diagram showing an example of a data registration template used when the terminal device 1 shown in FIG. 1 registers data in the information processing device 4. FIG. 8 (A) shows a “XX specification”. FIG. 8B shows an example of a template related to “ΔΔ circuit diagram information”.

  In the template relating to “XX specification” shown in FIG. 8A, the template ID 51 for uniquely specifying the template is “1”, and the version number A52 indicating the version number of the template is “1. The case of 01 ′ is shown. Such a template related to “XX specification” is prepared across multiple pages according to the number of attributes (items) for defining keywords for data search from page 1 to page 5. An example is shown. On the other hand, in the template related to “ΔΔ circuit diagram information” shown in FIG. 8B, the template ID 51 for uniquely specifying the template is “2”, and the version number A52 indicating the version number of the template is The case of “1.00” is shown. Unlike the case of FIG. 8 (A), such a template relating to “ΔΔ circuit diagram information” is prepared only for page 1 according to the number of attributes (items) for defining keywords for data search. An example is shown.

  Also, as shown in FIGS. 8A and 8B, the numbering number 56 for presenting the result of automatic numbering by the numbering request from the terminal device 1 to the user of the terminal device 1 at the time of data registration. As an input frame for inputting the version number B57 and the attribute name (item name) for defining the attribute relating to the registered data as a search keyword by the user of the terminal device 1, the attribute A53, the attribute B54, the attribute C55, ..., attribute Z etc. are also arranged.

  An example of the template information registered in the template storage unit 31 is shown in FIG. FIG. 10 is a table showing an example of template information registered in the template storage unit 31 of the storage device 3 shown in FIG. 1. No. 61 indicating the item number, management ID 62 for managing the template information, and each template uniquely Each item includes a template ID 63 for specifying, a version number A64 indicating the version number of each template, a file name 65 indicating the file name of each template file, and the like.

  For example, the template related to “XX specification” shown in FIG. 8A has a template ID 51 of “1”, but the template storage unit 31 has a plurality of templates with a template ID 63 of “1”. Yes.

  However, the version number A52 of the template related to “XX specification” shown in FIG. 8A presented to the user is “1.01” indicating the latest version, and the template of FIG. This corresponds to the template information in which the No. 61 of the template storage unit 31 is “3”, the version number A64 is “1.01”, and the management ID 62 is “003”. 'A specification. The fact that it is a template for registering doc 'is registered. In addition, 'A specification. As the template of doc, it is registered that the template has a version number A64 of “1.00” and a management ID 62 of a newer version number (that is, the latest version number) than the template of “001”.

  When the template shown in FIG. 8 is registered in the template storage unit 31 as template information, as described above, the attribute name (item name) for each attribute (item) in the registered data file used as a keyword at the time of data search is extracted. And register it as a database on the template side in a format separate from the registration data file. That is, as shown in attribute A53, attribute B54,... In FIG. 8, the attribute name 97 (eg, attribute A, attribute B) managed in the attribute storage unit 33 shown in FIG. ,...) And input from the terminal device 1 in association with the attribute names (item names) entered in the input fields of attribute A53, attribute B54,... Described in the template shown in FIG. It is registered and managed in the storage unit 33, and matches the content of each attribute set as an attribute name (item name) related to registered data in the attribute name 97 (attribute A, attribute B,...) Of the attribute storage unit 33.

  Next, the numbering storage unit 32 in the storage device 3 registers the numbering result obtained by automatically numbering the “XX specification” template as shown in FIG. Yes, a numbering / registration request screen as shown in FIGS. 5 and 6 is displayed on the terminal device 1 side, and a numbering request is made from the terminal device 1 side. Processing is performed, and the numbering number / version number B of the template automatically updated to the latest value as the numbering result is stored.

  FIG. 5 is a schematic diagram illustrating an example of a numbering / registration request screen displayed when the terminal device 1 illustrated in FIG. 1 requests the information processing device 4 to number a template. Shows a case where a template of “XX specification” is selected and numbered. 6 is a schematic diagram showing another example of the numbering / registration request screen displayed when the terminal device 1 shown in FIG. 1 requests the information processing device 4 to number the template. This shows a case where a data file to which a template of “XX specification” selected and numbered in FIG. 8 is applied is instructed to be registered with a file name “A.xls”.

  In the numbering / registration request screens of FIGS. 5 and 6, a selection button column 71, a template name column 72, a registered file name column 73, a numbering button 74, and a registration button 75 are arranged. In the numbering / registration request screen shown in FIG. 5, the selection button 71a in the selection button column 71 corresponding to “XX specification” in the template name column 72 is selected, and the numbering button 74 is pressed (clicked). By doing so, it shows a state in which the numbering of the template information of the “XX specification” is instructed.

  On the other hand, in the numbering / registration request screen shown in FIG. 6, “A.” is displayed in the input frame 73a of the registered file name field 73 corresponding to the “XX specification” numbered in FIG. By inputting the file name “xls” (“.xls” indicates an extension) and pressing (clicking) the registration button 75, the file name “A. A state in which the data file is registered with xls ′ is shown.

  An example of the numbering information registered in the numbering storage unit 32 is shown in FIG. FIG. 11 is a table showing an example of numbering information registered in the numbering storage unit 32 of the storage device 3 shown in FIG. 1. No81 indicating the item number, template ID 82, numbering number 83, numbering ID 84, version Each item consists of a number B85,...

  For example, the numbering information related to the template “XX specification” is numbered with the numbering number 83 being “1”, but the numbering storage unit 32 has the numbering number 83 is “1”. There are multiple pieces of information. Here, the version number A of the “XX specification” template shown in FIG. 8A numbered by pressing (clicking) the numbering button 74 is “1.01” as described above. The corresponding numbering information in the numbering storage unit 32 is numbering information No 81 is “4”, and is automatically updated as the latest version, the numbering ID 84 is “4”, the numbering number. "001" and the version number B85 is registered as information of "1.01".

  Next, when the terminal device 1 requests the information processing device 4 to register data using the numbering / registration request screen of FIG. 6, the attribute storage unit 33 in the storage device 3 registers as shown in FIG. By inputting an attribute name (item name) for each attribute of the data file to be stored, it is stored in association with the management attributes (eg, attribute A53, attribute B54,... In FIG. 9) of the template.

  FIG. 9 is a schematic diagram illustrating an example of input data (attribute) when the terminal device 1 registers a data file in the information processing device 4 using the data registration template illustrated in FIG. ) Shows an example of data (attribute) input using the “XX specification” template, and FIG. 9B shows data (attribute) input using the “△△ circuit diagram information” template. An example is shown.

  In the template related to “XX specification” shown in FIG. 9A, as described above, the template ID 51 is “1”, the version number A52 is “1.01”, and the numbering / registration screen is displayed. Based on the numbering request, the automatically assigned numbering number 56 is displayed as “001” and the version number B57 is displayed as “1.01”. In the example of setting data regarding the attribute name for each attribute of the data file, The attribute A53 is input as “A” and the attribute B54 is input as “Yes”.

  On the other hand, in the template related to “ΔΔ circuit diagram information” shown in FIG. 9B, the template ID 51 is “2” and the version number A52 is “1.00” as described above. Based on the numbering request of the registration screen, the automatically assigned number 56 is displayed as “001” and the version number B57 is “1.00”, but the data setting example for the attribute name for each attribute of the data file , The attribute A53 is input as “11”, the attribute B54 is “22”, and the attribute C55 is input as “33”.

  Next, an example of attribute information that separates an attribute (item) for defining a keyword for searching the registration data file from the registration data file and registers it in the attribute storage unit 33 as a database on the template side is shown in FIG. 12 shows. FIG. 12 is a table showing an example of attribute information registered in the attribute storage unit 33 of the storage device 3 shown in FIG. 1. No91 indicating the item number, template ID 92, version number A93, numbering ID 94, numbering number 95 , Version number B96, attribute name 97, file name 98, and so on.

  For example, in the attribute storage unit 33, as shown in FIG. 9A, the attribute information related to the data file registered using the “XX specification” template has the template ID 92 of “1”, the version number A93 and the version number B96. Are both “1.01” and the numbering number 83 is “001”, that is, the numbering ID 94 is “4”. As illustrated in the attribute name 97, the attribute A is “A”. ', Attribute B is' Yes', attribute C is' Yes', ..., attribute Z is registered as' Yes'.

  Similarly, in the attribute storage unit 33, as shown in FIG. 9B, the attribute information related to the data file registered using the “ΔΔ circuit diagram information” template has the template ID 92 of “2”, the version number A93 and the version number. The numbers B96 are all “1.00”, and the numbering number 83 is “001”, that is, the numbering ID 94 is “2”. As illustrated in the attribute name 97, the attribute A is “11”, attribute B is “22”, attribute C is “33”,..., Attribute Z is registered as “−”.

  The information processing device 4 receives various processing requests from the terminal device 1 via the input / output means 41, performs processing according to the requests, and registers and registers the settings in each storage unit in the storage device 3. Search each storage unit. Further, the template selection means 42 of the information processing device 4 provides a processing menu to the terminal device 1, and the numbering / registration request screen of FIGS. 5 and 6 requested by the terminal device 1 and the search request screen of FIG. Etc. are displayed on the screen, and processing corresponding to the input from the terminal device 1 is executed.

  The format check means 43 of the information processing apparatus 4 checks the contents requested by the terminal device 1 (template ID, version number A, numbering number, version number B) and uses the latest version of the template. A process of determining whether or not is executed. The information registration unit 44 of the information processing apparatus 4 registers a data file, registers the file name of the data file in the attribute storage unit 33, and uses attributes (items) used as keywords for searching the data file. ) The information is separated from the data file and stored in the attribute storage unit 33 of the database on the template side.

  Here, FIG. 7 is a schematic diagram showing an example of a search request screen displayed when the terminal device 1 shown in FIG. 1 requests the information processing device 4 to search for registered data. , The case where data including “Ah” is designated in the attribute A of “XX specification” is shown. The search request screen in FIG. 7 includes a search target document column 101, a selection button column 102, a search target attribute name column 103, a search content column 104, and a search button 105. In the search request screen shown in FIG. 7, “XX specification” is selected in the search target document column 101, and the selection button 102a in the selection button column 102 corresponding to the attribute A in the search target attribute name column 103 is selected. Furthermore, “ah” is input as a character string of the attribute name related to the attribute A to be searched for in the search content column 104, and the search button 105 is pressed (clicked), whereby the attribute A of “XX specification” is displayed. This indicates a state instructing to search for a data file including the character string “Ah” as an attribute name.

(Description of operation of embodiment)
Next, the operation of the PDM system 100 of FIG. 1 described above as an example of the PDM system according to the present invention will be described by taking operations corresponding to the numbering request, data registration request, and search request from the terminal device 1 as an example. .

  First, the operation in the case of a numbering request for requesting numbering of a template from the terminal device 1 will be described using the flowchart of FIG. FIG. 2 is a flowchart showing an example of a numbering request operation when requesting numbering of a template in the PDM system 100 shown in FIG.

  In the flowchart of FIG. 2, the terminal device 1 first presents the processing menu prepared in the template selection unit 42 to the configuration / document registration device 2 via the input / output unit 41 of the information processing device 4. The numbering / registration request screen illustrated in FIG. 5 is selected from the presented processing menu, and the numbering / registration request screen is displayed on the screen.

  Next, in the terminal device 1, the user who visually recognizes the numbering / registration request screen shown in FIG. 5 displayed on the screen displays the selection button 71 a in the selection button column 71 corresponding to “XX specification” in the template name column 72. Is selected, and the numbering button 74 is pressed (clicked) while the template of “XX specification” is selected to instruct the numbering of the template information of “XX specification” (step) S21).

  When the configuration / document registration apparatus 2 receives the instruction via the input / output means 41 of the information processing apparatus 4, the template selection means 42 is activated, and the template selection means 42 refers to the template storage unit 31 illustrated in FIG. Then, the template information in which the version number A64 is the latest version number from the template information whose template ID 63 uniquely indicates the template of “XX specification” is “1” (NO61 in the case of the registration example of FIG. 10). Is the latest version of template information with version number A64 of “1.01” in the record with management ID 62 of “003”.

  Thereafter, the template selection unit 42 increments the numbering ID 84 of the numbering storage unit 32 by “1” (for example, the numbering ID 84′3 ”in which No81 is“ 3 ”in the registration example of FIG. 11 is the last ID number). If it is, the numbering ID 84 is incremented by “1” and set to “4”), and the numbering number 83 of the numbering storage unit 32 corresponding to the template information is incremented by “1”. (For example, if the numbering number 83 is “000”, it is updated to “001”), and the version number B84 is updated with the version number A64 related to the extracted template information (for example, the version number A64 is “1.01”). If there is, update to '1.01') (step S22).

  When the numbering process for the numbering storage unit 32 is completed, the template selecting unit 42 assigns the number as the latest version template, as shown in the data registration template numbering number 56 and the version number B57 in FIG. 9A. The template information of “XX specification” with the numbering number “001” and the version number B “1.01” registered in the storage unit 32 is output to the terminal device 1 through the input / output means 41. Then, the user of the terminal device 1 is notified (step S23). Therefore, the user only needs to confirm the numbered number and the version number B, and there is no need to manually transfer the number.

  Next, the operation in the case of a data registration request for requesting data registration from the terminal device 1 will be described using the flowchart of FIG. FIG. 3 is a flowchart showing an example of a data registration request operation when requesting data registration in the PDM system 100 shown in FIG.

  In the flowchart of FIG. 3, the terminal device 1 first sends the configuration / document registration apparatus 2 to the template selection means 42 via the input / output means 41 of the information processing apparatus 4 as in the flowchart of FIG. 2. The presentation of the prepared processing menu is requested, the numbering / registration request screen illustrated in FIG. 5 is selected from the presented processing menus, and the numbering / registration request screen is displayed on the screen.

  Next, in the terminal device 1, the user who visually recognizes the numbering / registration request screen shown in FIG. 5 displayed on the screen displays the selection button 71 a in the selection button column 71 corresponding to “XX specification” in the template name column 72. In the state where the template of “XX specification” is selected, the input frame 73a of the registered file name column 73 corresponding to the template of “XX specification” is displayed as “A” as shown in FIG. . By inputting a file name “xls” (where “.xls” is an extension indicating the file type) and pressing (clicking) the registration button 75, the file name “A. It is instructed to register the data file as xls' (step S31).

  When the configuration / document registration apparatus 2 receives the instruction via the input / output means 41 of the information processing apparatus 4, the format check means 43 is activated, and the format check means 43 refers to the template storage unit 31 illustrated in FIG. 'A. The template ID and the version number A applied to the file “XX specification” having the file name “xls” are checked (step S32). That is, the file name 65 in the template storage unit 31 in FIG. The contents of the template ID 63 and the version number A64 of the record in which the file name of “XX specification” “xls” is set are extracted, and it is checked whether or not the template ID and version number indicate the latest version.

  'A. If the template ID and version number A applied to the file with the file name “XX specification” “xls” are not the latest (NG in step S32), the process proceeds to step S37, and the template An NG result indicating that the ID and the version number A are not the latest version is output to the terminal device 1 (step S37).

  On the other hand, 'A. If the template ID and the version number A applied to the file with the file name “XX specifications” named “xls” are the latest (OK in step S32), then the format check means 43 Referring to the numbering storage unit 32 illustrated in FIG. 11, the numbering number 83 and the version number B85 in which the template ID extracted by the template ID 63 of the template storage unit 31 is set in the template ID 82 of the numbering storage unit 32. Is checked to determine whether the numbering number 83 and the version number B85 have already been set (step S33).

  If the numbering number 83 and the version number B85 are not set (in the case of “NO” in step S33), the registration is instructed by starting the flowchart of FIG. A. Numbering number and version number B are assigned to the template applied to the file with the file name “XX specification” called “xls”, and the numbering number and version number B are registered in the numbering storage unit 32 (step S34) Thereafter, the process proceeds to step S35.

  On the other hand, if the numbering number 83 and the version number B85 are set (in the case of “Yes” in step S33), the process proceeds to step S35, the template selection means 42 is activated, and the template selection means 42 For example, “1” is set in the template ID 51, “1.01” is set in the version number A52 indicating the latest version, “001” is set in the numbering number 56, and “1.01” is set in the version number B57. In order to set a keyword for each attribute used for searching the “XX specification” on the terminal device 1 and displaying a data registration template related to “XX specification” as shown in FIG. A53, attribute B54,... Each attribute name (item name) is requested to be input.

  The user who has visually recognized that the data registration template is displayed on the screen of the terminal device 1 is registered in each of the attribute A53, attribute B54,. The character string indicating the attribute name (item name) for each attribute applied to the data file of the file name “XX specification” named “xls” (for example, in the input example of FIG. “A”, “Yes”,...

  When each of the character strings (attribute names) input to the attribute A53, attribute B54,... Is received by the composition / document registration apparatus 2 via the input / output means 41 of the information processing apparatus 4, the information registration means 44 is activated. Then, the information registration unit 44 refers to the attribute storage unit 33 illustrated in FIG. The template ID 92 attached to the template information of “XX specification” “xls” is “1”, the version number A93 is “1.01”, the numbering number 95 is “001”, and the version number B is “1. Each character string (attribute name) input to the attribute A53, attribute B54,... Is set and registered in each attribute name 97 of the record corresponding to 01 ′ (step S35). That is, in the registration example of the attribute storage unit 33 in FIG. 12, the record No. 91 of “3” has “A” as the attribute A, “Yes” as the attribute B, “U” as the attribute Z. Settings are registered.

  Further, the information registration means 44 uses the file name “A. xls' data file and the file name 'A.X specification' registered as a data file in the file name 98 of the attribute storage unit 33 in FIG. xls' is set and registered (step S36). Thereafter, the process proceeds to step S37, and an OK result to the effect that registration of the data file has been successfully performed is output to the terminal device 1 (step S37).

  As described above, the attribute (item) for specifying the registered data file is defined as the latest version template, and the attribute name (item name) included in the registered data file is defined for each defined attribute (item). The data file can be managed based on the latest version of the template by extracting and setting and registering it in the attribute storage unit 33, which is one of the databases on the template side, in a form separated from the registered data file. Data management can be performed with high reliability and efficiency.

  Next, an operation in the case of a search request for requesting a search for registered data from the terminal device 1 will be described with reference to the flowchart of FIG. FIG. 4 is a flowchart showing an example of a search request operation when a data search is requested in the PDM system 100 shown in FIG.

  In the flowchart of FIG. 4, the terminal apparatus 1 first sends the configuration / document registration apparatus 2 to the template selection means 42 via the input / output means 41 of the information processing apparatus 4 as in the flowchart of FIG. 2. A request for the prepared processing menu is requested, and the search request screen illustrated in FIG. 7 is selected from the presented processing menus, and the search request screen is displayed on the screen.

  Next, in the terminal device 1, the user who has viewed the search request screen shown in FIG. 7 displayed on the screen selects “XX specification” in the search target document column 101, and sets the attribute in the search target attribute name column 103. By selecting the selection button 102a of the selection button column 102 corresponding to A, inputting the character string “ah” of the attribute to be searched in the search content column 104, and pressing (clicking) the search button 105, It is instructed to search for data in which the attribute A of “XX specification” is “Ah” (step S41).

  When the configuration / document registration apparatus 2 receives the instruction via the input / output means 41 of the information processing apparatus 4, the template selection means 42 is activated, and the template selection means 42 receives the “XX specification” input on the search request screen. The data in which the character string “Ah” is set and registered in the attribute A column of the attribute name 97 with reference to the attribute storage unit 33 illustrated in FIG. A file is searched (step 42). That is, since “XX specification” is set as “1” in the template ID 92 of the attribute storage unit 33, the record in which “1” is set as the template ID 92 of the attribute storage unit 33 is targeted. The record having the character string “Ah” in the attribute A column of the attribute name 97 is searched, and the search target file name is acquired from the file name 98 of the record.

  When the search operation ends, the process proceeds to step S43, and the search result is output to the terminal device 1 (step S43).

  As described above, the attribute storage unit that forms the database on the template side by separating the attribute name (item name) for each attribute (item) that defines the keyword for searching the registered data file from the registered data file. By collectively setting and registering in 33, it is possible to perform an overwhelmingly high-speed search as compared to the case of performing full text search or image search in an actual registration data file.

(Explanation of effect of embodiment)
As described in detail above, the following effects are obtained in the present embodiment.

  First, the data registration template shown in FIG. 8 is defined in a form including attributes, and the attributes (items) defined as templates are matched with the attributes managed by the attribute storage unit 33. Since it is possible to manage the attribute name (item name) for each attribute separately from the collected data, the attribute (item) content that is also a keyword for specifying registered data is separated as a database on the template side. Registration is possible, and registration data can be managed more reliably.

  Secondly, since the attribute (item) content that is a keyword for searching the registration data is separated from the registration data and is collectively registered in one attribute storage unit 33 of the database on the template side, the actual registration is performed. There is no need to perform full text search and image search of data, the search range can be narrowed down, and the search time for registered data can be greatly shortened.

  Thirdly, since the template ID and the version number A of the template related to the registered data are managed by registration in the template storage unit 31, the latest version is always checked by checking the template version number at the time of data registration. Data using a number of templates and attribute names (item names) for each attribute can be registered, and there is no risk of management failure, and management can be efficiently performed with high reliability.

  Fourth, a template storage unit 31 and a numbering storage unit 32 are provided, and a numbering number and a version number B automatically assigned in response to a template numbering request are registered. Since the result can be output to the terminal device 1, it is not necessary to manually transfer the numbering number, and it is possible to reliably prevent the numbering mistake.

  The configuration of the preferred embodiment of the present invention has been described above. However, it should be noted that such embodiments are merely examples of the present invention and do not limit the present invention in any way. Those skilled in the art will readily understand that various modifications and changes can be made according to a specific application without departing from the gist of the present invention.

1 Terminal Device 2 Configuration / Document Registration Device 3 Storage Device 4 Information Processing Device 31 Template Storage Unit 32 Numbering Storage Unit 33 Attribute Storage Unit 41 Input / Output Unit 42 Template Selection Unit 43 Format Check Unit 44 Information Registration Unit 51 Template ID
52 Version A
53 Attribute A
54 Attribute B
55 Attribute C
56 Numbering number 57 Version number B
61 No
62 Management ID
63 Template ID
64 edition A
65 File name 71 Selection button field 71a Selection button 72 Template name field 73 Registration file name field 73a Input frame 74 Numbering button 75 Registration button 81 No
82 Template ID
83 Numbering number 84 Numbering ID
85 edition number B
91 No
92 Template ID
93 Edition A
94 Numbering ID
95 Numbering number 96 Version number B
97 attribute name 98 file name 100 PDM system 101 search target document column 102 selection button column 102a selection button 103 search target attribute name column 104 search content column 105 search button

Claims (9)

  To define keywords for data file search in templates related to data files consisting of various documents and drawings including at least specifications and circuit diagrams in PDM (Product Data Management) systems that manage design information and product information A PDM system which is registered as a database together with information indicating the attributes of the template, the version number of the template, and the numbering number.   In response to a numbering request from a terminal device operated by a user, means for automatically generating and assigning the version number and numbering number of the template and registering them in the database, and a data file from the terminal device A format check means for automatically confirming whether or not the template applied to the data file is the latest version template with reference to the database when a registration request is made; The PDM system according to claim 1, wherein   When there is a data registration request from a terminal device operated by a user, an input screen for inputting a keyword for searching for the data file in association with the attribute is displayed on the terminal device, and for each attribute. By inputting a keyword, an information registration unit that separates the keyword for each attribute received from the terminal device from the data file and registers the keyword as an attribute of a template applied to the data file. The PDM system according to claim 1, wherein the PDM system is provided.   When there is a search request for the registered data file from a terminal device operated by the user, data is referred to by referring to a keyword registered in the database as an attribute of the template applied to the data file. The PDM system according to claim 3, wherein a file is searched.   A data registration method in a PDM (Product Data Management) system that manages design information and product information, and a template for a data file consisting of various documents and drawings including at least a specification and a circuit diagram is used for searching the data file. A data registration method characterized in that it is registered as a database together with attributes for defining a keyword, information indicating the version number and numbering of the template.   In response to a numbering request from a terminal device operated by a user, the version number and numbering number of the template are automatically generated and assigned, registered in the database, and a data file registration request from the terminal device 6. The data according to claim 5, wherein when there is, the database is automatically checked to determine whether or not the template applied to the data file is the latest version of the template. Registration method.   When there is a data registration request from a terminal device operated by a user, an input screen for inputting a keyword for searching for the data file in association with the attribute is displayed on the terminal device, and for each attribute. By inputting a keyword, the keyword for each attribute received from the terminal device is separated from the data file and registered in the database as an attribute of a template applied to the data file. The data registration method according to claim 5 or 6.   When there is a search request for the registered data file from a terminal device operated by the user, data is referred to by referring to a keyword registered in the database as an attribute of the template applied to the data file. 8. The data registration method according to claim 7, wherein a file search is performed.   9. A data registration program, wherein the data registration method according to claim 5 is implemented as a program executable by a computer.

Images