Project management device, project management method, and project management program

Abstract

A technique is provided for reflecting changes in product information in multiple planning masters. [Solution] The management device 100 includes a planning master update unit for creating or updating one or more planning masters 130 each including one or more product information selected from a product master 120 and time series information; an update reflection unit for reflecting an update of certain product information in other planning masters 130C, 130D that are chronologically later than a certain planning master 130B based on an update of certain product information included in a certain planning master 130B among the one or more planning masters 130; and a product master update unit for reflecting an update of certain product information in the product master 120 based on an update of certain product information included in a certain planning master 130B.

Description

[Technical Field]

[0001] The present disclosure relates to project management techniques. [Background technology]

[0002] Retailers and manufacturers, etc., may create POP displays, distribute advertising flyers, and distribute catalogs for delivery services as part of their sales promotion activities. Sales promotion staff may create digital data for these media as part of their plans.

[0003] Regarding technology for creating such plans, for example, Japanese Patent Application Laid-Open No. 2023-133572 (Patent Document 1) discloses a product information management device that "has a theme product data storage unit that stores theme product data in which product data is associated with a theme, and a product master storage unit that stores a product master, and when data is edited for product data associated with the theme, a change confirmation screen is displayed on the terminal to confirm whether or not the edited content should be reflected in the product master corresponding to the edited product data, and the change confirmation screen displays the item to be changed, the value before the change, the value after the change, and an input field for specifying whether or not the data should be reflected, and the item to be changed in the product master that has been specified as being able to be reflected is rewritten with the changed value" (see [Abstract]). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2023-133572 Summary of the Invention [Problem to be solved by the invention]

[0005] Generally, sales promotion staff create plans for each period, such as one week. In doing so, they may create plans for multiple periods simultaneously. Therefore, if information about a certain product changes, the sales promotion staff must revise multiple plans that include that product.

[0006] However, the technology disclosed in Patent Document 1 does not allow changes to product information to be reflected in multiple projects. Therefore, there is a need for a technology that allows changes to product information included in a project to be reflected in the same product information included in one or more projects that chronologically follow the project.

[0007] The present disclosure has been made in consideration of the above-described background, and in one aspect, the purpose is to provide a technology for reflecting changes to certain product information included in a certain project in the same product information included in one or more projects that chronologically follow the certain project. [Means for solving the problem]

[0008] According to one embodiment, there is provided a planning management device including: a planning master update unit for creating or updating one or more planning masters each including one or more pieces of product information selected from a product master and time-series information; an update reflection unit for, based on an update of certain product information included in a certain planning master among the one or more planning masters, reflecting the update of certain product information in another planning master that is chronologically later than the certain planning master; and a product master update unit for, based on an update of certain product information included in the certain planning master, reflecting the update of certain product information in the product master.

[0009] In one aspect, each of the one or more pieces of product information includes a plurality of items. The plan master update unit is configured, when creating the one or more plan masters, to copy the plurality of items of the one or more pieces of product information selected from the product master to each of the one or more plan masters, and, when the product masters are edited, not to reflect the updates of the product masters in the one or more plan masters.

[0010] In one aspect, the management device further includes an input unit for selecting a range of information to be reflected in another planning master when the planning master is updated. The input unit is configured to allow selection of each of a plurality of items.

[0011] In one aspect, each of the one or more plan masters includes, for each of one or more pieces of product information, a plurality of items copied from the product master and information specific to the one or more plan masters.

[0012] In one aspect, the planning master update unit creates a snapshot of a certain planning master based on receiving an instruction to create a snapshot of the certain planning master or based on updating the certain planning master.

[0013] In one aspect, the management device further includes an output unit configured to be able to display differences between two or more snapshots created from the same planning master.

[0014] According to another embodiment, there is provided a method for managing plans, which includes creating or updating one or more plan masters including one or more pieces of product information selected from a product master and time-series information, reflecting the update of the product information in another plan master that is chronologically later than the one plan master based on an update of the product information included in the one or more plan masters, and reflecting the update of the product information in the product master based on an update of the product information included in the one or more plan masters.

[0015] According to another embodiment, there is provided a program executed by a planning management device. The program causes the management device to create or update one or more planning masters including one or more pieces of product information selected from a product master and time-series information, and, based on an update of certain product information included in a certain planning master among the one or more planning masters, reflect the update of the certain product information in another planning master that is chronologically later than the certain planning master, and, based on an update of certain product information included in the certain planning master, reflect the update of the certain product information in the product master. [Effects of the Invention]

[0016] According to one embodiment, changes to certain product information included in a certain project can be reflected in the same product information included in one or more projects that chronologically follow the certain project.

[0017] The above and other objects, features, aspects and advantages of the present disclosure will become apparent from the following detailed description of the disclosure taken in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0018] [Figure 1] FIG. 2 is a diagram illustrating an example of basic functions provided by a management device 100 according to the present embodiment. [Figure 2] 10 is a diagram illustrating an example of a process for creating a plan master 130 by the management device 100. FIG. [Figure 3] 10 is a diagram illustrating an example of a process in which the management device 100 reflects updates to product information in a certain plan master 130 in other plan masters 130 and the product master 120. FIG. [Figure 4] FIG. 10 is a diagram showing an example of how data included in each plan master 130 and product master 120 changes when product information is updated. [Figure 5] FIG. 2 is a diagram illustrating an example of functional blocks included in a management device 100. [Figure 6] FIG. 2 illustrates an example of hardware included in a management device 100. [Figure 7] It is a diagram showing an example of a screen 700 provided by the management device 100. [Figure 8] It is a diagram showing an example of an execution procedure of piercing maintenance by the management device 100.

Embodiments for Carrying Out the Invention

[0019] Hereinafter, embodiments of the technical idea according to the present disclosure will be described with reference to the drawings. In the following description, the same parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated. Also, each embodiment, each modification example, each software or program configuration, each hardware configuration, each function, and each process, etc. may be selectively combined as appropriate.

[0020] <A. Operation of the Management Device> FIG. 1 is a diagram showing an example of basic functions provided by the management device 100 according to the present embodiment. The management device 100 provides a function for a user to create a plan. Here, the "plan" includes plans related to advertising flyers, campaigns, pop-ups, delivery services, and other arbitrary promotional activities by retailers and manufacturers, etc. Also, the said plan can be used not only for store sales but also for non-store businesses, etc. In the following description, data representing the "plan" is called a "plan master". The "plan master" is information necessary to realize a certain plan. As an example, the plan master of an advertising flyer may include product information to be published in the advertising flyer and information such as the layout of the advertising flyer. As another example, the plan master of a delivery service may include information such as product information that can be delivered, delivery period, and delivery fee. In any case, the plan master includes at least product information related to the plan and time-series information (that is, information on the implementation period of the plan). The "product information" may include an identifier for identifying a product, product name, manufacturer, raw material, and any item related to the product.

[0021] Product information is centrally managed in a database called a product master 120. In one aspect, the product master 120 may be realized as a relational database or a database in any other format. In another aspect, the management device 100 may include the product master 120. In yet another aspect, the product master 120 may exist outside the management device 100. In this case, the management device 100 communicates with the external product master 120 as necessary.

[0022] Management device 100 has a function of creating one or more plan masters 130 based on multiple pieces of product information stored in product master 120. In one aspect, management device 100 may be realized as a standalone device. In another aspect, management device 100 may be configured to provide the functionality of a web application or a server-client system. In this case, management device 100 may be realized as a server device or as a virtual machine in a cloud environment. In yet another aspect, management device 100 may be realized as an application running on a server device or a cloud environment.

[0023] 1, the functions of the management device 100 will be described using an example of a procedure for creating a planning master 130 for a catalog of a delivery service in which the products to be delivered change every week. Hereinafter, the management device 100 will be described as providing the functions of a web application, as an example.

[0024] A user accesses the management device 100 via the user's terminal 110. The management device 100 transmits to the terminal 110 a UI (User Interface) 502 (see FIG. 5) for providing various functions of the management device 100. The terminal 110 uses a browser function to display the UI 502 on a display.

[0025] The user creates a plan master 130 via the UI 502 and selects one or more products to be included in the plan master 130 from the product master 120. By repeating these operations, the user can create a desired number of plan masters 130, such as the plan master 130 for the first (first week) of January 2024, the plan master 130 for the second (second week) of January 2024, and the plan master 130 for the third (third week) of January 2024, as shown in FIG. 1. These created plan masters 130 can be used for any purpose, such as creating advertising flyers, campaign posters, or delivery service catalogs.

[0026] Generally, a user (such as a person in charge of creating a catalog for a delivery service) does not create such a planning master 130 one by one, but creates planning masters 130 for multiple periods simultaneously. Therefore, when certain product information is updated, the user needs to reflect the update of the certain product information in multiple planning masters 130. However, there may be planning masters 130 in which the update of certain product information should not be reflected. For example, suppose that product X is to be renewed in two weeks. In this case, the product X before the renewal will be sold this week and next week. Therefore, the update of the product information for product X should not be reflected in this week's planning master 130 or next week's planning master 130.

[0027] In this way, when a user learns of a change in certain product information, the user is required to perform an operation to reflect the update of the certain product information in the planning master 130 after a certain point in time, rather than reflecting the update in the planning master 130 before that point in time. This operation places a heavy burden on the user. Therefore, the management device 100 provides a function to, when certain product information is updated, reflect the update of the certain product information in the planning master 130 after a certain point in time all at once, rather than reflecting the update in the planning master 130 before that point in time. Details of this function will be described later with reference to FIG. 3.

[0028] 2 is a diagram showing an example of a process for creating the plan master 130 by the management device 100. The data structures of the product master 120 and the plan master 130 and how the plan master 130 is created from the product master 120 will be described with reference to FIG.

[0029] The product master 120 stores one or more pieces of product information. In the example of FIG. 2, a plurality of pieces of product information A to Z are registered in the product master 120. In reality, the product master 120 may store more product information. Each record of product information in the product master 120 includes any item related to the product. The any item related to the product may include any item such as a product identifier, product name, manufacturer, ingredients, temperature range, etc. The temperature range is an item related to the storage location of the product, and may include categories such as room temperature, refrigerated, and frozen.

[0030] The user can include one or more pieces of product information registered in the product master 120 in the newly created plan master 130. In the example of FIG. 2, the user registers product information A to E in the plan master 130. In this case, the management device 100 copies all of the items included in the product information A to E from the product master 120 to the plan master 130. In some aspects, some of the items included in the product information A to E may be copied to the plan master 130.

[0031] In some aspects, the plan master 130 may include plan information (K01, K02, etc. in FIG. 2) that is information specific to the plan master 130, in addition to any item related to the product copied from the product master 120. As an example, the plan information may include any information such as the layout of an advertising flyer, a campaign catchphrase, or discount information. Furthermore, the plan master 130 may include a combination of these pieces of information as plan information.

[0032] After the planning master 130 is created, the product information in the planning master 130 is not directly synchronized with the product information in the product master 120. For example, suppose that product information E in the product master 120 is updated after the planning master 130 is created. In this case, the product information E in the planning master 130 is not updated. This is because, as mentioned above, when certain product information is updated, there exists a planning master 130 in which the update of the product information should not be reflected.

[0033] 3 is a diagram showing an example of a process in which the management device 100 reflects updates to product information in a certain plan master 130 in other plan masters 130 and the product master 120. The management device 100 provides a function for editing product information included in the plan master 130. Furthermore, the management device 100 provides a function for, based on updates to product information included in a certain plan master 130, reflecting the updates in other plan masters 130 and the product master 120.

[0034] These functions will be described with reference to Figure 3. Assume that a user (such as a sales promotion staff member) is creating a plan for next year in December 2023. In the example of Figure 3, the user has created four plan masters 130A, 130B, 130C, and 130D. Plan masters 130A, 130B, 130C, and 130D relate to the first plan for January 2024, the second plan for January 2024, the third plan for January 2024, and the fourth plan for January 2024, respectively. Furthermore, plan masters 130A, 130B, 130C, and 130D all include product information A to E.

[0035] Assume that the user receives information from a supplier or the like that a certain product will be renewed at the beginning of the second week of January 2024. In this case, the user edits the plan master 130B related to the second plan (second week) of January 2024 via the UI 502. More specifically, the user edits the item of product information E related to a certain product in the plan master 130B. The management device 100 updates the product information E in the plan master 130B based on the input received from the user. Hereinafter, for the sake of distinction, the updated product information E will be referred to as product information E2.

[0036] Next, the management device 100 searches the plan DB (Database) 514 (see FIG. 5) for a plan master 130 that is later in time series than the edited plan master 130B. The time series order of each plan master 130 is determined by the time or period in which the plan is implemented. As an example, the plan of plan master 130A is implemented before the plan of plan master 130B. Therefore, from the perspective of plan master 130B, plan master 130A is the "previous plan master" in time series. As another example, the plan of plan master 130C is implemented after the plan of plan master 130B. Therefore, from the perspective of plan master 130B, plan master 130C is the "later plan master" in time series. If a plan master 130 later than plan master 130B exists in the plan DB 514, the management device 100 acquires one or more later plan masters from the plan DB 514. In the example of FIG. 3, the management device 100 acquires the planning masters 130C and 130D as subsequent planning masters.

[0037] Next, the management device 100 determines whether product information E is included in each of one or more subsequent planning masters. If product information E is included in the subsequent planning master, the management device 100 updates the product information E in the subsequent planning master to product information E2. In the example of FIG. 3, both planning masters 130C and 130D include product information E. Therefore, the management device 100 updates the product information E in the planning masters 130C and 130D to product information E2. In some cases, the management device 100 may search the planning DB 514 for a subsequent planning master that includes product information E. Furthermore, the management device 100 updates the product information E in the product master 120 to product information E2. However, the management device 100 does not reflect the update of the product information E in the planning master 130A, which chronologically precedes the planning master 130B.

[0038] In this way, when a user acquires change information about a certain product, the user simply edits or updates the earliest planning master 130 in which the change is to be reflected. This automatically reflects the updated product information for the certain product in planning masters 130 that are chronologically later than the planning master 130 in which the user updated the product information. Furthermore, the updated product information for the certain product is automatically reflected in the product master 120. However, the updated product information for the certain product is not reflected in planning masters 130 that are chronologically earlier than the planning master 130 in which the user updated the product information. As a result, the user can ensure the consistency of multiple planning masters 130 with only minor editing tasks. In the process described in FIG. 3, multiple planning masters 130 containing updated product information are updated or maintained in a cross-sectional manner. Therefore, this series of processes shown in FIG. 3 is sometimes referred to as "cross-sectional maintenance."

[0039] In addition to the cross-maintenance function, the management device 100 also has a function for creating snapshots of the planning master 130. A snapshot is a copy of data at a certain point in time. Snapshots are not affected by updates to the original planning master 130 and are managed as read-only. The management device 100 can create snapshots of the planning master 130 at any time. In one aspect, the management device 100 can create and save a snapshot based on receiving an operation to create a snapshot from a user via the input unit 504 (see FIG. 5). This allows a user to create a snapshot of a desired planning master 130 at any time. In another aspect, the management device 100 can create and save a snapshot of a certain planning master 130 when the certain planning master 130 is created or updated. The management device 100 may save the snapshot in the planning DB 514. A snapshot of a planning master 130 edited by a user may be created by the planning master update unit 510 (see FIG. 5). Furthermore, a snapshot of the planning master 130 that reflects updates made by cross-site maintenance may be created by the update reflecting unit 512 (see FIG. 5).

[0040] Furthermore, the management device 100 has a function for outputting snapshots. The management device 100 can present snapshots to a user via the output unit 506 (see FIG. 5). The output unit 506 can also display comparisons, differences, and combinations of two or more snapshots. A user can input a request to output a snapshot of a desired planning master 130 to the management device 100 via the input unit 504. By checking the differences between two or more snapshots, a user can check whether cross-site maintenance has been properly reflected.

[0041] Furthermore, the management device 100 may have a function of displaying a copy of a snapshot as a template on the output unit 506 when creating a new planning master 130. In this case, the user can easily create a new planning master 130 by using the template. The user may select a snapshot of a desired planning master 130 as a template via the input unit 504.

[0042] The management device 100 can ensure data integrity by providing users with a snapshot creation function. As an example, suppose two people, a media production specialist and a sales promotion data manager, edit the plan master 130. In this case, a technology is needed to prevent inconsistencies in usage data between the media production specialist and the sales promotion data manager. The media production specialist and the sales promotion data manager can determine whether the plan master 130 being edited has been appropriately updated by checking the snapshot differences, history, or both of the plan master 130 being edited. In this way, by having the function to create and present snapshots, the management device 100 can prevent inconsistencies in usage data between users, even if multiple users edit the plan master 130 at the same time.

[0043] 4 is a diagram showing an example of how data included in each plan master 130 and product master 120 changes when product information is updated. With reference to FIG. 4, the procedure for updating the plan master 130 and product master 120 when the product name of a certain product is changed will be described.

[0044] Table 400 conceptually shows a portion of the product information stored in the product master 120 and the planning masters 130A to 130E at each point in time. Column 410 shows a portion of the product information stored in the product master 120 and the planning masters 130A to 130E before the product information is updated. Column 420 shows a portion of the product information stored in the product master 120 and the planning masters 130A to 130E after cross-sectional maintenance. Column 430 shows a portion of the product information stored in the product master 120 and the planning masters 130A to 130E after the planning master 130E is created after cross-sectional maintenance.

[0045] Referring to column 410, the product master 120 and the plan masters 130A to 130D all contain the product name "Nigari-Filled Tofu 300g x 2," which is part of the product information. At this point, the plan master 130E has not been created. After this, suppose the user is informed by a supplier or the like that the product name "Nigari-Filled Tofu 300g x 2" will change to "Nigari-Filled Tofu 300g x 2" from the third week of February. In this case, the user edits the plan master 130C related to the plan for the third time in February (third week).

[0046] Referring to column 420, the user has updated the product name "Nigari-filled Tofu 300g x 2" included in the planning master 130C to "Nigari-filled Tofu 300g x 2." Based on this update, the management device 100 updates the product name "Nigari-filled Tofu 300g x 2" included in the planning master 130D, which chronologically comes after the planning master 130C, to "Nigari-filled Tofu 300g x 2." Furthermore, the management device 100 updates the product name "Nigari-filled Tofu 300g x 2" included in the product master 120 to "Nigari-filled Tofu 300g x 2."

[0047] Referring to column 430, the user has created a new plan master 130E. Because the plan master 130E was created by referencing the latest product master 120, the plan master 130E includes the updated product name "Nigari-Made Tofu 300g x 2." Meanwhile, the product names included in the plan masters 130A and 130B, which are chronologically earlier than the plan master 130C updated by the user, have not been updated. In this way, the user only needs to update the product information included in one plan master 130C. Accordingly, the management device 100 automatically reflects the same updates in the plan master 130D and product master 120 that follow the plan master 130C updated by the user.

[0048] As described with reference to FIGS. 1 to 4, the management device 100 has a function for creating each plan master 130 by copying product information included in the product master 120. The management device 100 does not directly synchronize the created plan master 130 with the product master 120. Furthermore, the management device 100 has a function for performing cross-maintenance on subsequent plan masters 130, starting from the plan master 130 edited by the user. Providing these functions in the management device 100 provides various benefits to the user.

[0049] First, the user can store the past plan master 130 with the same content as when the plan was implemented. From the perspective of customer support, it is desirable for the user to accurately maintain the past plan master 130. Suppose the plan master 130 does not copy the product information from the product master 120, but refers only to the product identifier. In this case, when the product information in the product master 120 is updated, the product information included in the past plan master 130 is also updated. In this case, the product information included in the updated past plan master 130 will differ from the information on the products that were actually sold when the plan was implemented.

[0050] Second, the user can easily edit products whose items change according to the season or the timing of a specific plan. As an example, for products such as chocolate, the temperature zone classification (refrigeration in summer and freezing in winter) differs depending on the season. As another example, information such as product descriptions and catchphrases for promotions can be regularly changed according to the delivery time of the target product and the time of the event, etc. When such products are included in each plan, the user can individually change the items of each product for each of the plurality of plan masters 130.

[0051] Third, the user can change the product at the timing when they learn of the change in product information. As an example, the form of delivery of a certain product and the handling of the product in the logistics warehouse after delivery may be changed from a specific timing. In this case, the user only needs to edit one plan master 130 for the plan implemented after the specific timing. When the edit operation is received, the management device 100 reflects the same change in all the remaining plan masters 130 after the specific timing. As another example, for information whose rules are defined by laws, such as allergen information, the rules for information management for each product must be changed at the timing defined by the laws. Even in this case, the user only needs to edit one plan master 130 for the plan implemented after the timing defined by the laws. When the edit operation is received, the management device 100 reflects the same change in all the remaining plan masters 130 after the timing defined by the laws.

[0052] <B. Configuration of the Management Device> FIG. 5 is a diagram illustrating an example of functional blocks included in management device 100. Each functional block illustrated in FIG. 5 is a configuration for realizing the functions of management device 100 described in this embodiment, and may be realized by a program, hardware, or a combination of these. In one aspect, each functional block illustrated in FIG. 5 may be realized by executing a program on hardware illustrated in FIG. 6. In another aspect, some of the functional blocks illustrated in FIG. 5 may be realized as hardware. In this case, management device 100 includes hardware corresponding to one or more functional blocks illustrated in FIG. 5, in addition to the hardware illustrated in FIG. 6.

[0053] The management device 100 includes a UI 502, a product master update unit 508, a plan master update unit 510, an update reflection unit 512, and a plan DB 514. The UI 502 includes an input unit 504 and an output unit 506. The product master update unit 508 is configured to be able to communicate with the product master 120.

[0054] UI 502 is an interface for using various functions of management device 100. A user can input various operations to management device 100 via UI 502. Similarly, a user can view information output by management device 100 via UI 502. That is, UI 502 includes an input unit 504 that receives various information from terminal 110 and an output unit 506 that outputs various information to terminal 110. UI 502 can include multiple UIs as necessary. Furthermore, each of the multiple UIs may have the function of input unit 504, the function of output unit 506, or both of these functions.

[0055] As one example, the user may add product information to the product master 120, and update and delete product information registered in the product master 120, via the UI 502. As another example, the user may add the plan master 130 to the plan DB 514, and update and delete the plan master 130 registered in the plan DB 514, via the UI 502.

[0056] In one aspect, UI 502 may be provided as a web application screen. In this case, user terminal 110 receives UI 502 from management device 100 and displays UI 502 on a browser. In another aspect, UI 502 may be provided as a screen of a server-client system. In this case, UI 502 is included in a client application installed on user terminal 110.

[0057] The product master update unit 508 updates the product master 120 based on a command received from the terminal 110. The product master update unit 508 can add product information to the product master 120, and update and delete product information registered in the product master 120. Furthermore, the product master update unit 508 can update product information registered in the product master 120 based on an update command received from the update reflection unit 512. This update processing corresponds to the update processing of the product master 120 in the cross-site maintenance described with reference to FIG. 3.

[0058] The plan master update unit 510 updates the plan DB 514 based on a command received from the terminal 110. The plan master update unit 510 can add plan masters 130 to the plan DB 514, and update and delete plan masters 130 registered in the plan DB 514. Furthermore, the plan master update unit 510 notifies the update reflecting unit 512 of update information. The update information includes at least an identifier of the updated plan master 130 and information indicating the updated product information items. As an example, assume that the item "Product Name" of product X included in the plan master 130A is updated. In this case, the update information includes an identifier of the plan master 130A and information indicating the product name "Product Name" of product X. The information indicating the item may be an item name, an item identifier, etc. The update information may also include any other information.

[0059] Based on the acquired update information of a certain plan master 130, the update reflecting unit 512 reflects the update of the certain plan master 130 in one or more plan masters 130 that are chronologically subsequent to the certain plan master 130. More specifically, suppose that the item "Product Name" of product X included in a certain plan master 130 is updated. In this case, the update reflecting unit 512 updates the item "Product Name" of product X included in the plan master 130 that is chronologically subsequent to the certain plan master 130 in the same manner as the certain plan master 130. This update processing corresponds to the update processing of the plan masters 130C and 130D in the cross-sectional maintenance described with reference to FIG. 3. Furthermore, the update reflecting unit 512 outputs an update command including the update information to the product master updating unit 508. The product master updating unit 508 updates the product master 120 based on the update command, thereby keeping the product master 120 up to date.

[0060] One or more plan masters 130 are registered in the plan DB 514. Each plan master 130 includes one or more pieces of product information and time series information (information on the implementation period of the plan). The update reflecting unit 512 can determine the order or chronological relationship of each plan master 130 in the time series by referencing the implementation period information. In one aspect, the plan DB 514 can be realized as a relational database or a database in any other format. In yet another aspect, the plan DB 514 may exist outside the management device 100. In this case, the management device 100 communicates with an external product master 120 as necessary.

[0061] 5, the management device 100 according to the present embodiment includes a plan master update unit 510 for creating or updating one or more plan masters 130 each including one or more pieces of product information selected from the product master 120 and time-series information. The management device 100 also includes an update reflecting unit 512 for, based on an update of certain product information included in a certain plan master 130 among the one or more plan masters 130, reflecting the update of certain product information in another plan master 130 that is chronologically later than the certain plan master 130. The management device 100 also includes a product master update unit 508 for, based on an update of certain product information included in a certain plan master 130, reflecting the update of certain product information in the product master 120.

[0062] By using the management device 100 having the above configuration, a user can easily edit product information whose items change according to the season or the timing of a specific project. Furthermore, by using the management device 100, a user can change products when they become aware of changes in the product information.

[0063] In one aspect, each of the one or more pieces of product information includes multiple items. When creating one or more plan masters 130, the plan master update unit 510 copies multiple items of one or more pieces of product information selected from the product master 120 to each of the one or more plan masters 130, and is configured to prevent updates to the product master 120 from being reflected in the one or more plan masters 130 when the product master 120 is edited. By having this configuration, the management device 100 can store past plan masters 130 with the content as it was at the time the plan was implemented.

[0064] In one aspect, each of the one or more plan masters 130 includes, for each of one or more pieces of product information, a plurality of items copied from the product master 120 and information specific to the one or more plan masters 130. This allows the user to manage, for each plan master 130, one or more pieces of product information and information specific to the plan (such as a campaign description or discount information).

[0065] In one aspect, the planning master update unit 510 is configured to be able to create a snapshot of a certain planning master 130 based on receiving an instruction to create a snapshot of a certain planning master 130 or based on updating the certain planning master 130. Furthermore, the update reflecting unit 512 can be configured to be able to create snapshots of one or more planning masters 130 in which updates are reflected by cross-maintenance.

[0066] In one aspect, output unit 506 is configured to be able to display the differences between two or more snapshots created from the same planning master 130.

[0067] Fig. 6 is a diagram showing an example of hardware included in management device 100. Management device 100 may not include some of the components shown in Fig. 6. Management device 100 may also include components not shown in Fig. 6. Furthermore, management device 100 may include multiple components shown in Fig. 6. The various functions included in management device 100 described with reference to Fig. 5 can be realized by executing a program on the hardware shown in Fig. 6.

[0068] Management device 100 includes a processor 601, a memory 602, a storage 603, an external device IF 604, an input IF 605, an output IF 606, and a communication IF 607. In some aspects, management device 100 may include two or more of each component, or may not include some of the components.

[0069] The processor 601 can execute programs for implementing various functions of the management device 100. The processor 601 is configured, for example, with at least one integrated circuit. According to an embodiment, the integrated circuit may include at least one central processing unit (CPU), at least one graphics processing unit (GPU), at least one field programmable gate array (FPGA), at least one application specific integrated circuit (ASIC), at least one artificial intelligence (AI) chip, or a combination thereof.

[0070] The memory 602 functions as a workspace for the processor 601. The memory 602 stores programs executed by the processor 601 and data referenced by the processor 601. In one aspect, the memory 602 can be realized by a dynamic random access memory (DRAM), a static random access memory (SRAM), or the like.

[0071] Storage 603 is a non-volatile memory that stores programs executed by processor 601 and data referenced by processor 601. Processor 601 executes programs read from storage 603 to memory 602 and references data read from storage 603 to memory 602. In one aspect, storage 603 can be realized by a hard disk drive (HDD), a solid state drive (SSD), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a flash memory, or the like.

[0072] The external device IF 604 can be connected to any external device such as a printer, a scanner, an external HDD, etc. In one aspect, the external device IF 604 can be realized by a USB (Universal Serial Bus) terminal or the like.

[0073] The input IF 605 can be connected to any input device such as a keyboard, a mouse, a touchpad, a gamepad, etc. In one aspect, the input IF 605 can be realized by a USB terminal, a PS / 2 terminal, a Bluetooth (registered trademark) module, etc.

[0074] The output IF 606 can be connected to any output device such as a cathode ray tube display, a liquid crystal display, an organic electroluminescence (EL) display, etc. In one aspect, the output IF 606 can be realized by a USB terminal, a D-sub terminal, a DVI (Digital Visual Interface) terminal, an HDMI (High-Definition Multimedia Interface) terminal, a DisplayPort terminal, etc.

[0075] The communication IF 607 is connected to other devices via a wired network or a wireless network. In one aspect, the communication IF 607 may be implemented by a wired local area network (LAN) port, a Wi-Fi (registered trademark) (Wireless Fidelity) module, or the like. In another aspect, the communication IF 607 may transmit and receive data using a communication protocol such as TCP / IP (Transmission Control Protocol / Internet Protocol) or UDP (User Datagram Protocol).

[0076] 7 is a diagram showing an example of a screen 700 provided by the management device 100. The screen 700 is provided as part of the UI 502 or the input unit 504. The screen 700 is configured to allow selection of product information items that reflect the cross-sectional maintenance. As an example, the UI 502 may be configured to allow transition to the screen 700 from a product information editing screen for editing the items of each product included in the planning master 130.

[0077] Screen 700 includes a list of changed items 710, a list of pre-change information 720, a list of post-change information 730, and a list of update settings 740. The list of changed items 710 displays a list of items changed on the product information editing screen. The list of pre-change information 720 shows information before the change for each item changed on the product information editing screen. The list of post-change information 730 shows information after the change for each item changed on the product information editing screen. The list of update settings 740 indicates whether cross-maintenance should be applied to each item changed on the product information editing screen. The list of update settings 740 includes any form, such as a check box, and is configured to be able to accept input from the user.

[0078] In the example of FIG. 7, the list of change items 710 displays "Ingredient Origin Indication," "Printed Product Name," "Order Product Name," and "Planned Quantity." Furthermore, according to the list of update settings 740, the check boxes for "Ingredient Origin Indication," "Printed Product Name," and "Order Product Name" are checked. In other words, these items are included in the cross-sectional maintenance. On the other hand, the check box for "Planned Quantity" is not checked. In other words, "Planned Quantity" is not included in the cross-sectional maintenance. In this way, by using screen 700, the user can individually set for each item whether or not it is to be included in the cross-sectional maintenance (i.e., updated).

[0079] In a certain situation, the screen 700 may further include a list (not shown) of period information (or time-series information) for specifying the range of the planning master 130 to which the skewering maintenance is applied. In this case, the user can reflect the change in an item of product information only in the planning master 130 related to the plan to be implemented during a specific period by editing the list of period information. As an example, the user can reflect the change of making the item "temperature zone classification" of the chocolate product refrigerated only in the planning master 130 related to the plan to be implemented from July to September by editing the list of period information.

[0080] As described with reference to FIG. 7 (Claim: 3 support), the management device 100 further includes an input unit 504 for selecting the range of information to be reflected in other planning masters 130 when the planning master 130 is updated. The input unit 504 is configured to be able to select each of a plurality of items. The user can select the range of information to be reflected in other planning masters 130 by using the function of the input unit 504.

[0081] <C. Processing Procedure of Management Device> FIG. 8 is a diagram showing an example of the execution procedure of the skewering maintenance by the management device 100. In a certain situation, the processor 601 may read a program for performing the processing of FIG. 8 from the storage 603 into the memory 602 and execute the program. In other situations, part or all of the processing may also be realized as a combination of circuit elements configured to execute the processing. Further, in other situations, the following steps may be executed in a different order.

[0082] In step S810, the management device 100 accepts, via the UI 502, an update input for an item of product information included in a certain plan master 130. In one aspect, the management device 100 may accept update input for multiple items related to a certain product information. In another aspect, the management device 100 may receive, via the screen 700, an update setting indicating whether each item is to be subject to cross-sectional maintenance. Hereinafter, a plan corresponding to a certain plan master 130 will be referred to as a "plan to be updated." Furthermore, an item changed via the UI 502 will be referred to as an "item to be updated."

[0083] In step S820, the management device 100 updates the items to be updated that are included in a record of a certain plan master 130 stored in the plan DB 514. When the management device 100 receives update input for multiple items, it updates the multiple items included in the plan master record. In one aspect, the record of the plan master 130 may be made up of multiple records, such as a record for the plan master 130 itself and a record for each piece of product information included in the plan master 130. In this case, the management device 100 updates the record that includes the items to be updated.

[0084] In step S830, the management device 100 searches the plan DB 514 for plan masters 130 related to plans that will be implemented chronologically later than the plan to be updated. In step S840, the management device 100 updates the item to be updated of certain product information included in one or more plan masters 130 acquired by the search. In step S850, the management device 100 updates the item to be updated of certain product information included in the product master 120.

[0085] 8, the management device 100 can perform cross-site maintenance by executing a program. That is, the program causes the management device 100 to create or update one or more planning masters 130 including one or more pieces of product information selected from the product master 120 and time-series information, to reflect the update of the product information in another planning master 130 that is chronologically later than the one planning master 130 based on an update of the product information included in the one or more planning masters 130, and to reflect the update of the product information in the product master 120 based on an update of the product information included in the one or more planning masters 130.

[0086] <D.まとめ> As described above, the management device 100 according to this embodiment has a function for, when a certain item of product information is updated in a certain plan master 130, reflecting the updated information of the item in the other plan masters 130 and the product master 120. As a result, even if there is a change in product information included in multiple plan masters 130, the user only needs to update the product information included in one plan master 130. The remaining plan masters 130 and product masters 120 are automatically updated by the management device 100. As a result, the consistency of the plan masters 130 and the product masters 120 is guaranteed, and the workload on the user is reduced.

[0087] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. Furthermore, the disclosures described in the embodiments and each modification are intended to be implemented, as far as possible, either alone or in combination. [Explanation of symbols]

[0088] 100 management device, 110 terminal, 120 product master, 130, 130A, 130B, 130C, 130D, 130E planning master, 400 table, 410, 420, 430 column, 502, 504 input section, 506 output section, 508 product master update section, 510 planning master update section, 512 update reflection section, 514 planning DB, 601 processor, 602 memory, 603 storage, 604 external device IF, 605 input IF, 606 output IF, 607 communication IF, 700 screen, 710 list of changed items, 720 list of information before change, 730 list of information after change, 740 list of update settings.

Claims

1. a planning master updating unit for creating or updating one or more planning masters including one or more pieces of product information selected from the product master and time-series information; an update reflecting unit for reflecting, based on an update of certain product information included in a certain planning master among the one or more planning masters, an update of the certain product information in other planning masters that are chronologically later than the certain planning master; a product master updating unit for, based on an update of the certain product information included in the certain plan master, reflecting an update of the certain product information in the product master.

2. Each of the one or more pieces of product information includes a plurality of items, The planning master update unit When creating the one or more planning masters, the plurality of items of the one or more product information selected from the product master are copied to each of the one or more planning masters; The management device according to claim 1 , wherein when the product master is edited, the management device is configured not to reflect the update of the product master in the one or more plan masters.

3. an input unit for selecting a range of information to be reflected in the other planning master when the one planning master is updated; The management device according to claim 2 , wherein the input unit is configured to allow selection of each of the plurality of items.

4. The management device according to claim 2 , wherein each of the one or more planning masters includes, for each of the one or more pieces of product information, the plurality of items copied from the product master and information specific to the one or more planning masters.

5. A management device described in any one of claims 1 to 4, wherein the planning master update unit creates a snapshot of the certain planning master based on receiving an instruction to create a snapshot of the certain planning master or based on the certain planning master being updated.

6. The management device according to claim 5 , further comprising an output unit configured to be able to display differences between two or more of the snapshots created from the same planning master.

7. 1. A method for project management, comprising: Creating or updating one or more planning masters including one or more pieces of product information selected from the product master and time-series information; Based on an update of certain product information included in a certain planning master among the one or more planning masters, reflecting the update of the certain product information in other planning masters that are chronologically later than the certain planning master; and reflecting the update of the certain product information in the product master based on the update of the certain product information included in the certain plan master.

8. A program executed by a project management device, Creating or updating one or more planning masters including one or more pieces of product information selected from the product master and time-series information; Based on an update of certain product information included in a certain planning master among the one or more planning masters, reflecting the update of the certain product information in other planning masters that are chronologically later than the certain planning master; and, based on an update of the certain product information included in the certain planning master, reflecting the update of the certain product information in the product master.

Images