Program, management method, and management device

Abstract

To improve the convenience of a user.SOLUTION: A program makes a computer execute processes of: storing common item information related to a plurality of items that are common between data of a plurality of BOM structures, the data of the plurality of BOM structures storing project information and item information in a hierarchical structure; storing individual item information related to the item constituting the BOM structure in each of the data of the plurality of BOM structures; and managing the individual item information and the common item information corresponding to the item of the individual item information in association with each other.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a program, a management method, and a management device. [Background technology]

[0002] A product information management system has been disclosed that manages product information having product configuration information that represents the components of a product, and part information that has configuration information that represents the configuration of each of the components and attribute information that represents the attributes of each of the components (see, for example, Patent Document 1). This product information management system is characterized by having a key information assignment means that calls up a template corresponding to the product information to be registered and assigns key information that identifies the product to the template, an information input means that inputs information into the template, and a product information storage means that stores the template into which the information has been input as new product information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6102567 Summary of the Invention [Problem to be solved by the invention]

[0004] The above-mentioned technologies have sometimes been inconvenient for users, for example, information management has not been properly performed.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide a program, a management method, and a management device that can improve user convenience, for example, by appropriately managing information. [Means for solving the problem]

[0006] An embodiment of the present invention is a program for causing a computer to execute the following processes: storing common item information regarding multiple items common to multiple BOM structure data in multiple BOM structure data in which project information and item information are stored in a hierarchical structure; storing individual item information regarding items that make up the BOM structure in each of the multiple BOM structure data; and managing the individual item information in association with the common item information corresponding to items in the individual item information. [Effects of the Invention]

[0007] The program, management method, and management device of the present embodiment can improve user convenience. [Brief explanation of the drawings]

[0008] [Figure 1] 3 is a diagram illustrating management information managed by a management device according to an embodiment of the present invention. FIG. [Figure 2] 1 is a diagram illustrating an example of a configuration of a management system 1 including a program. [Figure 3] FIG. 10 is a conceptual diagram of management information 184. [Figure 4] FIG. 2 is a diagram showing an example of an interface screen IF1 provided by the management device 100. [Figure 5] 10A and 10B are diagrams illustrating examples of interface screens IF11 and IF12 provided by the management device 100. [Figure 6] 2A and 2B are diagrams illustrating examples of interface screens IF21 and IF22 provided by the management device 100. [Figure 7] 10A and 10B are diagrams illustrating examples of interface screens IF31 and IF32 provided by the management device 100. [Figure 8] 10A and 10B are diagrams illustrating examples of interface screens IF41 and IF42 provided by the management device 100. [Figure 9] FIG. 10 is a conceptual diagram of management information 184. [Figure 10]10A and 10B are diagrams illustrating examples of interface screens IF51 and IF52 provided by the management device 100. [Figure 11] 10A to 10C are diagrams illustrating examples of interface screens IF61, IF62, and IF63 provided by the management device 100. [Figure 12] 10A and 10B are diagrams illustrating examples of interface screens IF71 and IF72 provided by the management device 100. [Figure 13] 1A to 1C are diagrams illustrating examples of interface screens IF81, IF82, and IF83 provided by the management device 100. [Figure 14] 10 is a flowchart showing an example of a processing flow. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of a program, a management method, and a management device of the present invention will be described with reference to the drawings.

[0010] [overview] The management device of this embodiment executes the following processes: in data of multiple BOM structures in which project information and item information are stored in a hierarchical structure, storing common item information (UID) related to multiple items common to the data of multiple BOM structures; in data of the multiple BOM structures, storing individual item information related to the items that make up the BOM structure; and managing the individual item information in association with the common item information corresponding to the items in the individual item information. The multiple BOM structures are, for example, different types of BOMs.

[0011] Common item information may be referred to as UID below. UID is identification information assigned to BOM elements such as items, regardless of the BOM type. UID may be information for linking individual items that are common across BOMs. Common individual items are the same parts or processes, such as parts with the same model number, parts with the same design, or the same manufacturing process, but are assigned different identification information for each BOM structure. The above identification information that differs for each BOM structure is individual item information. As described above, individual item information is identification information unique to each BOM that is assigned to each part, manufacturing process, etc. in each BOM structure. Even if the same parts or manufacturing processes are assigned different individual item information depending on the BOM.

[0012] The data of the multiple BOM structures includes data of a design BOM structure that handles information related to the design of the object, data of a manufacturing BOM structure that handles information related to the manufacturing of the object, and data of an accumulation BOM structure that handles information related to procurement for manufacturing the object.

[0013] The management device assigns first identification information (UID) which is common item information to a first element (project, item, etc.) included in the data of the design BOM structure, and assigns second identification information which is individual item information to the first element (project, item, etc.) included in the data of the design BOM structure. The management device assigns first identification information (UID) which is common item information to a first element included in the data of the manufacturing BOM structure, and assigns third identification information which is individual item information to the first element included in the data of the manufacturing BOM structure. The management device assigns first identification information (UID) which is common item information to a first element included in the data of the integration BOM structure, and assigns fourth identification information which is individual item information to the first element included in the data of the integration BOM structure.

[0014] FIG. 1 is a diagram illustrating management information managed by a management device of this embodiment. Hierarchically structured information is stored in a storage unit of the management device. In the hierarchically structured information, information is organized into layers, and each piece of information is further associated with another. For example, a first lower layer is associated with a higher layer, and a second lower layer is associated with the first lower layer. For example, the higher layer is a project, and the lower layers are items related to the project. For example, a project is a finished product, an item in the first lower layer is an assembly, and an item in the second lower layer is a part. In addition to the first lower layer and the second lower layer, further lower layers may be provided.

[0015] A set of hierarchical structures is what is known as a "Bill of Materials (BOM) structure." The example in Figure 1 shows an Engineering BOM (EBOM), a Manufacturing BOM (MBOM), and a Service Bill of Materials (SBOM), but other types of BOMs may also be included.

[0016] Each element contained in each BOM is assigned identification information for that BOM. For example, if we look at AssyA, it is assigned identification information p1 in the EBOM, identification information p2 in the MBOM, and identification information p3 in the SBOM. In other words, even for the same part, each BOM assigns its own identification information, and the elements are managed within the BOM. Identification information p1 is an example of "second identification information," identification information p2 is an example of "third identification information," and identification information p3 is an example of "fourth identification information."

[0017] Furthermore, in this embodiment, the same identification information is assigned to the same element regardless of the BOM. For example, when focusing on AssyA, the identification information UID "001" is assigned regardless of the BOM type.

[0018] In this way, since the management device of this embodiment assigns the same identification information to the same element, it can easily obtain information managed by different BOMs for the target element and provide it to the user.

[0019] For example, while a user is viewing a specific part in an EBOM, the user may want to check the MBOM that contains the part related to the EBOM. In response to the user's operation corresponding to the above items, the management device can search for information about the part having the UID in the EBOM using the UID as a key and provide the searched information to the user. Also, while a user is viewing a specific part in an EBOM, the user may want to check information about projects or BOMs that use the specific part. In this case, too, the management device can extract information that uses the UID of the specific part and provide it to the user.

[0020] For example, suppose an EBOM and an MBOM have been created, and the version of the EBOM assembly "p1" has been changed. In this case, the management device, automatically or in response to a user operation, determines that the content of "p1" has been changed among "p1," "p2," and "p3," which all had the same UID. In other words, the management device determines the difference in information that has occurred in response to the change. The management device may provide this difference information to the user. For example, the management device may inquire of the user that "p1" or "p1 with a changed version" exists in the MBOM related to the EBOM, and whether to also change the version of "p2" in the MBOM.

[0021] Furthermore, the management device may use UIDs to collectively edit data. For example, the management device may collectively edit information associated with elements having a common UID. Information that can be collectively edited includes basic information (such as name, model number, and phase) and properties (attributes that can be freely set by the user) of an item, the configuration and basic information, quantity, and properties of child items linked to an item, files associated with an item, and a flag indicating that the associated information is CAD drawing data. For example, the information that can be collectively edited may be any predetermined information. For example, information linked to file properties may be excluded from the scope of bulk editing. Furthermore, the information that can be collectively edited can be selected arbitrarily by the user. For example, the user can set properties, basic information, and the like as information to be collectively edited. The management device 100 performs bulk editing based on the user's settings.

[0022] In this way, the management device of this embodiment can improve user convenience by performing various information processes using UIDs and by performing various information processes described below.

[0023] [Overall configuration] 2 is a diagram showing an example of the configuration of the management system 1 including a program. The management system 1 includes, for example, a user terminal device 10 and a management device 100. The management device 100 communicates with the user terminal device 10.

[0024] [User terminal device] The user terminal device 10 is a computer device such as a personal computer, a smartphone, a tablet terminal, etc. The user operates the user terminal device 10 to obtain desired information from the management device 100 and display the obtained information on a display unit, thereby providing the desired information to the user.

[0025] [Management device] The management device 100 includes, for example, an acquisition unit 110, an information processing unit 120, and a storage unit 180. The acquisition unit 110 and the information processing unit 120 are realized by, for example, a hardware processor such as a CPU (Central Processing Unit) executing a program (software) 182 stored in the storage unit 180. Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed by inserting the storage medium into a drive device. The storage unit 180 is realized by a storage device such as a HDD, a flash memory, a RAM (Random Access Memory), etc. The storage unit 180 stores, for example, the above-mentioned program 182, management information 184, and the like.

[0026] The acquisition unit 110 acquires a request sent to the user terminal device 10. The information processing unit 120 executes information processing in response to the request and causes an interface screen including content indicating the results of the information processing to be displayed on the display unit of the user terminal device 10. The information processing unit 120 executes various types of information processing using, for example, management information 184 stored in the storage unit 180 (described later) and generates content indicating the results of the information processing.

[0027] FIG. 3 is a conceptual diagram of the management information 184 (a diagram illustrating the management information in a different representation from FIG. 1). In the management information 184, information is organized hierarchically as described in FIG. 1, and each piece of information is associated and stored. Information other than projects and items is associated with a set of layers and each layer. The associated information is files and properties related to a set of layers and each layer. A file or property may be associated with one product or part, or with multiple products or parts. Files include drawings, cost calculations, test data, CAD data, specifications, requirements definition documents, and quality standards documents. Files are managed by version. Properties are associated with projects, assemblies, and parts. Properties are set by the user, for example.

[0028] In addition to the above, the management information 184 may include various information such as change history information, data tables, specifications, product information on the target component, defect information, defect countermeasure information or guidelines, standards (design requirements, standards, in-house standards), and information on related products or components. The management information 184 further includes master information, which is information on products, components, etc. The master information is information in which various specifications of products, components, etc. are associated.

[0029] [Interface screen provided by the management device] (BOM screen) Here, the information provided by the management device 100 to the user terminal device 10 will be described. FIG. 4 is a diagram showing an example of an interface screen IF1 provided by the management device 100. The interface screen IF1 is a screen that is displayed after a specific project is designated on a screen that displays a list of multiple items (assemblies, parts, etc.). The interface screen IF1 is a BOM screen that hierarchically displays the parts that make up a specific item (for example, a product) that is a specific project. When the master information described above is updated, it is reflected in the information on the BOM screen.

[0030] Interface screen IF1 includes information such as the model number of a specified item, category, phase related to the concept or manufacturing process (drawing release, prototype, mass production, etc.), cost, creation date of the BOM screen, update date (e.g., last update date), creator, and person in charge (project owner). It also includes information about the parts that make up the specified item. Part information is displayed with each part as a single recorder. For example, information such as the part's item name, model number, ID, phase, category, link to CAD data / drawing, and standard unit price is displayed as a record. This interface screen IF1 may also include a UID.

[0031] In this way, the management device 100 can improve user convenience by providing the user with a list of information related to projects.

[0032] (BOM addition screen) FIG. 5 is a diagram showing examples of interface screens IF11 and IF12 provided by the management device 100. A user can add, edit, or archive a BOM by performing operations on the interface screen IF11. For example, when a user operates the add button on the interface screen IF11, the management device 100 displays the interface screen IF12 on the display unit of the user terminal device 10. The user can select a BOM type and register notes on the interface screen IF12. When the user operates the add button on the interface screen IF12, a BOM is added to the management information 184. On the interface screen IF11 or a specified interface screen, the user can edit the BOM or save it in an archive. There is no limit to the number or types of BOMs that can be added.

[0033] In this way, the user can easily add, edit, and archive the BOM, improving user convenience.

[0034] (Category setting edit screen) The management device 100 manages each of the first elements (projects, items, files, etc.) included in each of the data of a plurality of BOM structures by associating the same category information with each of them. In other words, the same category can be assigned to elements between different BOMs.

[0035] FIG. 6 is a diagram showing examples of interface screens IF21 and IF22 provided by the management device 100. A user can set a category as an object to be assigned by performing an operation on the interface screen IF21. The object to be assigned can be any item, such as a project, an item, a file, or a BOM. For example, when a user selects an object to which a category is to be assigned and operates a category button on the interface screen IF21, the management device 100 displays the interface screen IF22 on the display unit of the user terminal device 10. A user can select and register a category on the interface screen IF22.

[0036] For example, the management device 100 can assign different categories to each of the items p1, p2, and p3 in FIG. 1 described above. It is also possible to assign different categories to the same component. For example, when an operation is performed to create an MBOM by duplicating an EBOM, the management device 100 can create an MBOM by inheriting the categories assigned to the components in the EBOM.

[0037] In this way, the user can easily assign a category to the object to be assigned, improving user convenience.

[0038] In addition to categories, the management device 100 can associate phases, member information, model numbers, revision information, and the like with each of the first elements (projects, items, files, etc.) included in each of the multiple BOM structure data. Phases are classifications for managing the project status (mass production, first stage of prototyping, second stage, etc.), and can be set arbitrarily by the user. Member information is information about members related to projects, items, etc. Model numbers are model numbers of parts, etc. Revision information is information about past revision history and version information. These pieces of information may also be capable of processing in the same way as categories. For example, settings may be edited, and properties, which will be described later, may be assigned, etc.

[0039] The management device 100 can assign properties to categories (see FIG. 7, which will be described later, for a setting method). For example, assume that the management device 100 assigns category A to a specific item in response to a user operation. The management device 100 can assign properties to categories for each BOM in response to a user operation (see AR1 of IF21 in FIG. 6). For example, the management device 100 can assign the property "Delivery Date" as a property of category A to item A in the EBOM, and assign the property "Procurement Time" as a property of item A in the MBOM. In this way, the management device 100 can assign the same category to each BOM and assign different properties to each of the same categories. In other words, the management device 100 can manage the same category assigned to each first element included in each of multiple BOM structure data by associating different property information with each of the same categories (even if the same category is assigned to the same component between BOMs, different properties can be assigned to the category between BOMs).

[0040] This allows the management device 100 to provide the user with information that matches the keyword specified by the user. For example, if the user specifies as keywords that the category is Category A and the property is "Delivery date," the management device 100 can extract information that matches the keyword and provide the extracted information to the user.

[0041] (Properties screen) The management device 100 manages the data of a plurality of BOM structures by associating different property information with each of the first elements (projects, items, files, etc.) included in each of the data. Properties may also be associated with BOMs. Property information may also be associated with the above-mentioned categories. When a user performs an operation to perform a search using a word to be searched, the management device 100 may extract property information including the search word and the elements associated with the property, and provide the extracted information to the user terminal device 10.

[0042] FIG. 7 shows examples of interface screens IF31 and IF32 provided by the management device 100. A user can add, set, or edit a property to an object by performing operations on the interface screen IF31. A user can also delete a property that has been assigned to an object. For example, when a user selects an object to which a property is to be assigned and operates the Add Property button on the interface screen IF21, the management device 100 displays the interface screen IF32 on the display unit of the user terminal device 10. A user can add a new property by entering details of the property on the interface screen IF32.

[0043] Properties are information that indicate the attributes of an item. Attribute items include design, procurement, manufacturing, and cost estimation. Design attribute items include various design-related information, such as the person who inspected the drawing, the person who approved it, the material of the item, the production method, and weight. Procurement attribute items include various procurement-related information, such as quotation-related matters, supplier, price, estimated delivery date, budget, manufacturer product number (MPN), and minimum order quantity (MOQ). Manufacturing attribute items include various manufacturing-related information, such as production performance and inventory management classification. Cost estimation items are, for example, MBOMs with monetary data added and parts below a certain level excluded. Users can assign tags, which are keywords used during searches, to each attribute item. Users can have the management device 100 search and narrow down information using property information and tags. Users can assign property names, data types, units, descriptions, and other information to the attribute items.

[0044] Furthermore, when a user changes information, the management device 100 stores the changes as a change history, allowing the user to perform cost analysis, search for past drawings, and the like by referring to the information before and after the change.

[0045] As described above, the user can set properties. Generally, customizing properties requires development costs, but the management device 100 provides an environment in which settings can be made without coding, thereby reducing the burden on the user. Furthermore, various information related to product development management, such as cost price and inventory quantity, as well as physical attributes of parts (weight and material), can be added, improving user convenience. In this way, the user can easily assign properties to the object to which they are to be assigned, improving user convenience.

[0046] (Property bulk import screen) 8 is a diagram showing an example of interface screens IF41 and IF42 provided by management device 100. A user can select a BOM to be overwritten on interface screen IF41 and drop a file in a predetermined format into the target area on interface screen IF41, thereby overwriting the information of the target BOM managed by management device 100 with the information of the file. The predetermined format is, for example, any format such as CSV.

[0047] When the file is dropped, the management device 100 displays an interface screen IF42 on the display unit of the user terminal device 10. The interface screen IF42 includes, for example, the model number to be overwritten, information on the properties to be overwritten (e.g., material, approval status, delivery date, supplier, standard price, manufacturer, etc.), model numbers that cannot be overwritten (model numbers not included in the target BOM), etc.

[0048] The management device 100 compares the model number of the dropped file with model numbers managed by the management device 100, and for matching model numbers, overwrites the property information associated with the model number in the dropped file (for example, information written on a specific line or information associated with a property label) as a property in the management information 184 managed by the management device 100. At this time, the management device 100 may provide the user with an interface screen showing the results of the overwrite. This interface screen may include an overwrite approval button, an overwrite disapproval button, an indication that no options exist, and the like. The management device 100 completes or cancels the overwrite depending on the operation of the above buttons.

[0049] In this way, the user can easily overwrite property information, improving user convenience.

[0050] [Summary so far] FIG. 9 is a conceptual diagram of management information 184. As described above, the management device 100 can assign a category or property to an object to be assigned. As shown in FIG. 9, for example, different properties can be assigned to the same element in the same category for each BOM. Furthermore, the management device 100 can collectively overwrite properties for selected, predetermined BOM objects.

[0051] (Project list screen) The management device 100 associates data of one or more specified BOM structures among data of multiple BOM structures with labels indicating projects and manages them. FIG. 10 is a diagram showing an example of interface screens IF51 and IF52 provided by the management device 100. For example, information on one or more BOMs created by a user for a certain project is associated. The management device 100 displays a list of data of one or more BOM structures associated with labels on the display unit in response to a predetermined operation, and displays information indicating details of the data of a specified BOM structure among the displayed data of one or more BOM structures on the display unit. For example, as shown in FIG. 10 (described later), a list screen of projects having EBOMs is displayed. When a user selects a specific project on the list screen, the management device 100 displays information indicating details of the EBOM data of the specified project on the display unit. In this way, the management device 100 provides an interface screen that allows a user to easily select information related to a specific BOM and can provide the user with details of the data of the specific BOM in response to a user operation.

[0052] When a user operates a new creation button on interface screen IF51, which is a project list screen, the management device 100 displays interface screen IF52 on the display unit. Interface screen IF52 is a screen for creating a new project. For example, when a user enters a project name, BOM type, model number, category, etc. on interface screen IF52 and operates the new creation button, the management device 100 creates a new project.

[0053] In this way, when creating a new project, the management device 100 can easily add information such as a BOM and a category to the project, thereby improving user convenience.

[0054] (Item list screen) The management device 100 manages data of a specified BOM structure among a plurality of BOM structure data or items included in the plurality of BOM structure data by associating them with a label indicating a project. The management device 100 manages data of a BOM structure (for example, data configured as a spreadsheet) including a predetermined column specified in response to a predetermined operation (for example, an upload operation) by associating it with the label of a predetermined project being displayed.

[0055] 11 is a diagram showing an example of interface screens IF61, IF62, and IF63 provided by the management device 100. When a user operates a predetermined button (CSV creation button) on interface screen IF61, which is an item list screen for a predetermined project, the management device 100 displays interface screen IF62 on the display unit.

[0056] The user can add information about items included in the target BOM managed by the management device 100 to the management information 184 by selecting the import destination BOM on the interface screen IF62 and dropping a file in a predetermined format into the target area of ​​the interface screen IF62. The predetermined format is, for example, any format such as CSV.

[0057] For example, when a file of a predetermined format is dropped, the management device 100 displays an interface screen IF63 on the display unit. The interface screen IF63 includes information indicating the correspondence between the type of information in the first line of the uploaded file and the display mode of the item information in the management device 100. For example, on the interface screen IF63, the first line of the uploaded file indicates "quantity," indicating that the display mode of the item information in the management device 100 is also "quantity." For example, item identification information is arranged in each column of the uploaded file, and information about each type of item is arranged in each row. In this case, the management device 100 can identify the item identification information and item information based on the above rules, extract combinations of these, and store the extracted information in the management information 184.

[0058] By providing the user with the information in the first row and the display mode as described above, the user can confirm that the management device 100 will correctly store the file information in the management information 184. When the user confirms that the file information will be correctly stored in the management information 184 and operates the Next button, the item information of the uploaded file is stored in the management information 184. While the example of adding an item has been described above, it is also possible to overwrite item information or create new item information using a similar principle.

[0059] As described above, the user can easily store information about items in the management information 184, which improves user convenience.

[0060] (export) On the screens displaying the above-described projects and items, the target screen or the information contained therein can be edited, exported (output), and finalized. For example, when the edit button is operated, the management device 100 can duplicate the target screen or the information contained therein, or duplicate and replace it. The management device 100 can also replace an item, add a child item to an item, and create or delete a child item. Duplication is a process that only duplicates data, while duplication and replacement also serves to delete the original data of the duplicate. When the export button is operated, the management device 100 displays options for selecting a BOM, properties, change history, and file on the display unit, and exports the selected information.

[0061] (BOM Import) When a user performs a predetermined operation on a predetermined interface screen to instruct management device 100 to perform BOM import processing, management device 100 displays an interface screen (such as the screen shown on interface screen IF62) on the display unit that includes an area for uploading a file. For example, if a file contains information that associates information for identifying an object (such as an item name), information indicating a hierarchy (hierarchical level), and information to be included in the hierarchy, management device 100 defines the hierarchical level of the file in management information 184, associates the information included in the hierarchical level of the file with the hierarchical level of management information 184, and generates BOM structure data in management information 184. In BOM import, if the file contains the above-mentioned item information or property information, this information can also be imported. For example, when a file is imported in which target product numbers and other information are defined in columns and hierarchical levels and information types (item information and property information) are defined in rows, the management device 100 associates the corresponding information in the file with the corresponding hierarchical levels and information types based on the hierarchical levels and information types in the management information 184, thereby updating or generating the management information 184. In this way, a user can easily import BOM information using a file. In BOM import, only information associated with a specified item may be uploaded. Furthermore, in BOM import and the various imports of items or properties described above, the user can specify the BOM type on an interface screen provided to the user. For example, if a user provides a column for BOM type in a CSV file and enters the BOM type, the management device 100 can recognize the BOM type specified by the user and import information based on the recognized BOM type. For example, item information and property information in the CSV file are imported into a BOM of the specified type.

[0062] (Project duplication) The management device 100 manages a specified BOM structure data among multiple BOM structure data by associating it with a label indicating a project. When duplicating information associated with a label indicating a specified project in response to a predetermined operation, the management device 100 duplicates the specified BOM structure data among the BOM structure data associated with the label. When BOM structure data is duplicated in this way (when a user performs an operation to duplicate data of a BOM structure selected by the user and create new BOM structure data), the management device 100 assigns, to the first element (e.g., project or item) included in the new BOM structure data, the first identification information (UID) that was assigned to the first element included in the original BOM structure data (the same applies when duplicating an expanded BOM). When the above project is duplicated, the user can select the type of BOM to duplicate, and the management device 100 may duplicate the selected BOM.

[0063] 12 is a diagram showing examples of interface screens IF71 and IF72 provided by the management device 100. The interface screen IF71 is a screen that displays project information. For example, when a user operates a button for duplicating a project on the interface screen IF71, the management device 100 displays the interface screen IF72 on the display unit.

[0064] The interface screen IF72 is a screen for selecting a BOM to be duplicated from among the BOMs that exist under a project. For example, if an EBOM, SBOM, and MBOM exist, when the user selects the BOM to be duplicated and operates the project duplicate button, the management device 100 duplicates the BOM of the project according to the operation.

[0065] In this way, the management device 100 can copy the desired BOM information when copying a project, which improves user convenience. Furthermore, the management device 100 can easily manage elements using UIDs by issuing UIDs.

[0066] (BOM Explosion Replication) When an operation to duplicate data of a specified BOM structure among data of an existing BOM structure is performed, the management device 100 duplicates the data of the BOM structure to be duplicated and manages it as data of a new BOM structure. The type of the existing BOM structure and the type of the new BOM structure may be different or the same. The management device 100 issues common item information (UID) for items included in the data of the new BOM structure to be duplicated, and associates the common item information with the items. In the above process, the user can select the type and category (project, item, file) of the BOM to be newly created, and the management device 100 duplicates the selected BOM type and category.

[0067] When replicating BOM-structured data, the management device 100 replicates the BOM-structured data excluding specified data from the source BOM-structured data. For example, when replicating BOM-structured data, the management device 100 replicates the BOM-structured data without replicating information specified by the user from among the source BOM-structured data, including file information related to design drawings (e.g., CAD drawing data), information about set members (e.g., members with viewing permissions or related members), and information about the BOM structure or properties included in the BOM structure and associated with the information. Alternatively, the management device 100 may target only information specified by the user for replication of the BOM-structured data. In the above example, the replication of projects and BOMs has been described. In addition, items may also be replicated in the same manner as described above. For example, the management device 100 may replicate information about items specified by the user and information associated with the items.

[0068] 13 is a diagram showing an example of interface screens IF81, IF82, and IF83 provided by the management device 100. The interface screen IF81 is a screen that is displayed when, for example, a predetermined operation for switching the BOM is performed on the above-mentioned interface screen IF71. For example, when the user operates a button for creating another BOM on the interface screen IF81, the management device 100 displays the interface screen IF82 on the display unit.

[0069] The interface screen IF82 includes, for example, a first button for selecting to create a new BOM by expanding the BOM displayed immediately before on the interface screen IF81, and a second button for selecting to create a new BOM. For example, when the first button is selected and the Next button is operated, the management device 100 displays the interface screen IF83 on the display unit. The interface screen IF83 includes, for example, selection fields for selecting the project name, BOM type, model number, and category for expanding the BOM, and selection fields for selecting items to duplicate from the source BOM information. The items include, for example, property contents, files (CAD drawing data), members, etc. For example, CAD drawing data is assigned a flag indicating that it is CAD drawing data, and the management device 100 can determine whether a file is CAD drawing data by referencing this flag. The user can expand the BOM by selecting any item. For example, when creating information for a new project related to the project of the source BOM, the information for the new project can be created using information from the source BOM.

[0070] In this way, the management device 100 can generate information by using the information in the BOM, thereby improving user convenience.

[0071] As described above, in this embodiment, the management device 100 provides various interface screens to the user and executes processing according to the user's operations on the interface screens, thereby improving user convenience. Furthermore, in this embodiment, by using a common UID regardless of the type of BOM, the management device 100 can provide information that is suitable for the user. The following is a flowchart focusing on the UID.

[0072] [Flowchart (1)] Flowchart 1 in FIG. 14 is a flowchart showing an example of the flow of processing executed by the management device 100. The processing in Flowchart 1 is processing when target information to which a UID has been assigned is duplicated. Below, processing when expanding a BOM will be described as an example. When the management device 100 duplicates information that is associated with a label indicating a project and indicates an item, it issues common item information (UID) to the item to be duplicated and associates the common item information with the item.

[0073] First, management device 100 determines whether an operation to expand a BOM has been performed (step S100). If an operation to expand a BOM has been performed, management device 100 identifies the UIDs of the items to be included in the expanded BOM (step S102). Next, management device 100 assigns UDIs to the items in the expanded BOM (step S104) and provides the BOM (step S106). This completes the processing of one routine of this flowchart.

[0074] In this way, the management device 100 can manage items across different projects or different BOMs by assigning UIDs to the items.

[0075] The process of flowchart 2 in Fig. 14 is a process when information on a target to which a UID is assigned is searched. Below, as an example, the process when information on a specific item is searched will be described.

[0076] First, the management device 100 determines whether information related to a specific item has been searched for (step S200). If information related to the specific item has been searched for, the management device 100 identifies the UID of the specific item and identifies items that have the same UID (step S202). Next, the management device 100 provides the user with information related to the identified item (step S204). This completes one routine of the process of this flowchart.

[0077] In this way, the management device 100 can provide useful information to the user by comprehensively identifying information related to items to which IUDs are attached and providing the information to the user.

[0078] For example, the management device 100 of this embodiment manages information within a BOM (e.g., item information) individually, and also manages, for example, the version of an item individually. The management device 100 uses individual item information to manage each individual part (item) for each BOM, so it can recognize which BOM information the target part belongs to. For example, even if the versions of parts are different, by using this individual item information, it is possible to manage part information that reflects the version. Furthermore, because individual item information exists for each BOM, it is possible to assign properties and categories to each BOM. It is also possible to manage the history of information changes.

[0079] On the other hand, a model number (or product number) can be included in the management information 184, but is not required, and model numbers can be assigned to parts of the same type. A management device in a comparative example, which differs from the management device of this embodiment, is designed to require different model numbers if the BOMs are different. In this case, the same part may be assigned different model numbers depending on the BOM, which can be inconvenient for the user. For example, when viewing a part in a specific BOM, it may be difficult to move to a different BOM and identify the same part. In contrast, in this embodiment, the model number can be made the same and a UID is assigned, making it possible to identify the same part between BOMs and provide information about the identified part to the user.

[0080] According to the embodiment described above, the management device 100 can improve user convenience by performing the following processes: storing common item information about multiple items that are common among multiple BOM structure data in multiple BOM structure data in which project information and item information are stored in a hierarchical structure; storing individual item information about items that make up the BOM structure in each of the multiple BOM structure data; and managing the individual item information in association with the common item information corresponding to the items in the individual item information.

[0081] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0082] 1. Management system, 10. User terminal device, 100. Management device, 110. Acquisition unit, 120. Information processing unit, 180. Storage unit, 184. Management information

Claims

1. On the computer, A process of storing common item information regarding a plurality of items common to a plurality of BOM structured data in which project information and item information are stored in a hierarchical structure; A process of storing individual item information regarding items constituting the BOM structure in each of the plurality of BOM structure data; a process of managing the individual item information and the common item information corresponding to the items of the individual item information in association with each other; A program to execute.

2. The data of the plurality of BOM structures includes data of a design BOM structure that handles information related to the design of an object, data of a manufacturing BOM structure that handles information related to the manufacturing of the object, and data of an accumulation BOM structure that handles information related to procurement for manufacturing the object. The program according to claim 1.

3. On the computer, In the data of the design BOM structure, first identification information which is the common item information is assigned to a first element included in the data of the design BOM structure, and second identification information which is the individual item information is assigned to the first element; In the data of the manufacturing BOM structure, the first identification information which is the common item information is assigned to the first element included in the data of the manufacturing BOM structure, and the third identification information which is the individual item information is assigned to the first element; In the data of the cumulative BOM structure, the first identification information which is the common item information and the fourth identification information which is the individual item information are assigned to the first element included in the data of the cumulative BOM structure. The program according to claim 2.

4. When a user duplicates the data of the selected BOM structure and creates new BOM structure data, On the computer, In the new BOM structure data, assigning the first identification information that was assigned to the first element included in the data of the BOM structure of the original to a first element included in the data of the new BOM structure; The program according to claim 3.

5. On the computer, managing the first elements included in each of the plurality of BOM structure data in association with the same category information; The program according to claim 1 or 2.

6. On the computer, managing the plurality of BOM structure data by associating different property information with each of the same category information assigned to each of the first elements included in the plurality of BOM structure data; The program according to claim 5.

7. On the computer, The data of one or more BOM structures designated from among the data of the plurality of BOM structures is associated with a label indicating the project and managed; displaying a list of data of one or more BOM structures associated with the label on a display unit in response to a predetermined operation; displaying information indicating details of the data of a specified BOM structure among the data of the one or more displayed BOM structures on the display unit; The program according to claim 1 or 2.

8. On the computer, a label indicating a project is associated with a specified BOM structure data among a plurality of BOM structure data or an item included in the plurality of BOM structure data, and the associated data is managed; The data of the BOM structure including a predetermined column designated in accordance with a predetermined operation is managed in association with the label of the predetermined project being displayed. The program according to claim 1 or 2.

9. On the computer, The data of a specified BOM structure among the data of the plurality of BOM structures is associated with a label indicating a project and managed; When duplicating information associated with a label indicating a specified project in response to a predetermined operation, data of the specified BOM structure is duplicated from among data of the BOM structure associated with the label; The program according to claim 1.

10. On the computer, When duplicating information that is associated with the label that indicates the project and that indicates an item, issuing common item information for the item to be duplicated and associating the common item information with the item. The program according to claim 9.

11. On the computer, When an operation to copy data of a specified BOM structure among data of existing BOM structures is performed, the data of the BOM structure to be copied is copied and managed as data of a new BOM structure. The program according to claim 1.

12. The type of the new BOM structure is different from the type of the existing BOM structure. The program according to claim 11.

13. On the computer, When copying the data of the BOM structure, the data of the BOM structure is copied excluding designated data from the data of the BOM structure of the copy source. The program according to claim 11.

14. On the computer, When copying the data of the BOM structure, copying the data of the BOM structure without copying information designated by the user among the data of the BOM structure of the copying source, namely, information on files related to design drawings, information on set members, and information on properties included in the BOM structure or associated with information, The program according to claim 13.

15. On the computer, issuing common item information for the items included in the copied data of the new BOM structure, and associating the common item information with the items; The program according to claim 11.

16. The computer A process of storing common item information regarding a plurality of items common to a plurality of BOM structured data in which project information and item information are stored in a hierarchical structure; A process of storing individual item information regarding items constituting the BOM structure in each of the plurality of BOM structure data; a process of managing the individual item information and the common item information corresponding to the items of the individual item information in association with each other; Management method to carry out.

17. A process of storing common item information regarding a plurality of items common to a plurality of BOM structured data in which project information and item information are stored in a hierarchical structure; A process of storing individual item information regarding items constituting the BOM structure in each of the plurality of BOM structure data; a process of managing the individual item information and the common item information corresponding to the items of the individual item information in association with each other; A management device that executes the above.

Images