Business support device, business support method, and business support program
Patent Information
- Application Number
- JP2025023600
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-17
- Publication Date
- 2026-08-27
AI Technical Summary
【0009】 本発明によれば、より漏れが少なく注意喚起を行うことができるという効果を奏する。
Smart Images

Figure 2026137470000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a business support device, a business support method, and a business support program.
Background Art
[0002] In manufacturing and the like, for products that are manufactured for the first time, products whose design has been changed, and products that have been manufactured for a long time (manufactured again after a long time), mistakes are particularly likely to occur, and more attention is required in the work. Incidentally, the work related to the manufacture of these products may be collectively referred to as "3H" work based on the initial letters of "first time", "change", and "long time".
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] Regarding the alert for 3H work, since alerts are given even for work that does not require much attention, there is a higher possibility that alerts for work that requires attention will be missed, leading to mistakes.
[0005] The present invention has been made in view of the above, and an object thereof is to provide a business support device, a business support method, and a business support program that can give alerts with fewer omissions.
Means for Solving the Problems
[0006] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention comprises an acquisition unit and a determination unit. The acquisition unit acquires information related to an order, including information indicating the scheduled completion time of the work and information regarding changes to the work. The determination unit outputs information indicating that the work is a modified work if the period from the initial completion time of the work to the scheduled completion time of the work, corresponding to the change information of the work, is within a predetermined period.
[0007] Furthermore, the business support method according to the present invention includes the steps of: a computer acquiring information related to an order, including information indicating the scheduled completion time of the work and information regarding changes to the work; and outputting information indicating that the work is a modified work, corresponding to the information regarding changes to the work, if the period from the initial completion time of the work to the scheduled completion time of the work is within a predetermined period.
[0008] Furthermore, the business support program according to the present invention causes a computer to perform the steps of: acquiring information related to an order, including information indicating the scheduled completion time of the work and information regarding changes to the work; and outputting information indicating that the work is a modified work, corresponding to the information regarding changes to the work, if the period from the initial completion time of the work to the scheduled completion time of the work is within a predetermined period. [Effects of the Invention]
[0009] According to the present invention, the effect is to reduce leakage and provide better warnings. [Brief explanation of the drawing]
[0010] [Figure 1] Figure 1 shows an example of the configuration of a business support system according to the embodiment. [Figure 2] Figure 2 shows an example of the information stored in the master storage unit of the business support device according to this embodiment. [Figure 3] Figure 3 shows an example of a part number master stored in the master storage unit according to the embodiment. [Figure 4]Figure 4 shows an example of a change management master stored in the master storage unit according to the embodiment. [Figure 5] Figure 5 shows an example of a shipment history master stored in the master storage unit according to the embodiment. [Figure 6] Figure 6 shows an example of the information stored in the data storage unit of the business support device according to the embodiment. [Figure 7] Figure 7 shows an example of preliminary order data stored in the data storage unit according to this embodiment. [Figure 8] Figure 8 shows an example of the process for determining a "first-time" operation and updating the part number master according to the embodiment. [Figure 9] Figure 9 shows an example of the determination process for a "change" operation according to the embodiment, as well as the update process for the change management master and the shipping history master. [Figure 10] Figure 10 shows another example of the "change" operation determination process and the shipping history master update process according to the embodiment. [Figure 11] Figure 11 shows an example of the process for determining a "long time no see" operation and updating the shipping history master according to the embodiment. [Figure 12] Figure 12 shows an example of notification data stored by the data storage unit according to the embodiment. [Figure 13] Figure 13 shows an example of a notification email according to an embodiment. [Figure 14] Figure 14 shows another example of the determination process for a "change" operation and a "long time no see" operation according to the embodiment. [Figure 15] Figure 15 shows another example of notification data stored by the data storage unit according to the embodiment. [Figure 16] Figure 16 shows another example of a notification email according to the embodiment. [Modes for carrying out the invention]
[0011] Embodiments of the present invention will be described in detail based on the drawings. Note that the present invention is not limited to these embodiments.
[0012] [1. Overview] So-called "3H work" is likely to result in mistakes, for example, in the case of "first-time" products (initial products), due to new operations, equipment, materials, etc.; in the case of "changed" products, due to changes in operations, equipment, materials, etc.; and in the case of "long-unused" products, due to forgetting work procedures or dulled senses. To prevent mistakes, it is important for production management personnel to recognize the timing when 3H work occurs and take pre-emptive measures such as reviewing the creation of in-house drawings, creating and reviewing in-house procedure manuals (requirement documents).
[0013] According to this embodiment, by determining and notifying the operations corresponding to "first-time" products, "changed" products, and "long-unused" products for 3H work, it is possible to call the attention of production management personnel in advance. Note that although the operations related to the manufacture of products will be described below, this embodiment is also applicable to other operations that require calling attention to 3H work, such as construction work. Also, hereinafter, operations related to "first-time" products, "changed" products, and "long-unused" products may be represented as "first-time" operations, "changed" operations, and "long-unused" operations.
[0014] [2. Configuration] FIG. 1 is a diagram showing an example of the configuration of a business support system 1 according to an embodiment. The business support system 1 is configured, for example, as a server-client system, and includes a business support device 100 that functions as a server, a plurality of terminal devices 200, and an EDI site 400, which are communicably configured via a network 300. The EDI site 400 is arranged, for example, at the business office of a customer who places an order for manufacturing, and transmits data related to order reception to the business support device 100 via the network 300.
[0015] When the business support device 100 acquires data related to an order, it determines whether or not the data related to the order includes 3H work and outputs the determination result to the terminal device 200, etc. In response to a request from the terminal device 200, it provides the terminal device 200 with various input screens, accepts information input from the terminal device 200 on the various input screens, and centrally manages the accepted information in the various data of the storage unit. In addition, the business support device 100 provides information on various data in response to a request from the terminal device 200, and the terminal device 200 can view the information on various data. In this embodiment, the data related to an order is, for example, preliminary order data transmitted via the EDI site 400 at a stage prior to the actual order. Details of the preliminary order data will be explained in detail later.
[0016] The business support device 100 can be composed of, for example, a workstation or a personal computer.
[0017] The terminal device 200 is located, for example, in the manufacturing department. Alternatively, the terminal device 200 may be located at the business premises of a customer that places an order. The terminal device 200 is equipped with a monitor, keyboard, printer, etc. The terminal device 200 displays various input screens provided by the business support device 100 on its monitor, allowing the person in charge (operator) to perform various inputs. The terminal device 200 also displays information about various data stored in the business support device 100 on its monitor, allowing users to view it.
[0018] The terminal device 200 may be, for example, a commercially available desktop personal computer, and is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.
[0019] As shown in Figure 1, the business support device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each component of the business support device 100 is connected to communicate via any communication path.
[0020] The communication interface unit 104 connects the business support device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines, enabling communication between them. The communication interface unit 104 has the function of communicating data with other devices via communication lines. Here, the network 300 has the function of connecting the business support device 100 and the terminal device 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).
[0021] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or mouse 112.
[0022] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.
[0023] As shown in Figure 1, the storage unit 106 includes a master storage unit 106a and a data storage unit 106b.
[0024] As shown in Figure 2, the master storage unit 106a stores the part number master 106aa, the change management master 106ab, and the shipment history master 106ac. Figure 2 is a diagram showing an example of the information stored in the master storage unit 106a of the business support device 100 according to this embodiment. The information stored in the master storage unit 106a is registered or updated by the update unit 102c, which will be described later. The master storage unit 106a may also include customer masters and the like, which are not shown.
[0025] As shown in Figure 3, the part number master 106aa stores information about the manufactured product, associating part number names with part number codes. Figure 3 is a diagram showing an example of the part number master 106aa stored by the master storage unit 106a according to this embodiment. The part number code is information that uniquely identifies the product with the part number name. Note that the part number code is an example of information that identifies a product.
[0026] As shown in Figure 3, the part number master 106aa contains two records: record aa11 with part number code "31008" and record aa12 with part number code "352057". Note that the part number master 106aa may also store other information not shown, such as the sales price of the product.
[0027] The change management master 106ab stores information regarding design changes to the manufactured product. Figure 4 shows an example of the change management master 106ab stored by the master storage unit 106a according to the embodiment. As shown in Figure 4, the change management master 106ab stores the design change information, the initial shipment date, and the change confirmation period in association with the part number code. Records in the change management master 106ab are registered, for example, when a new record is registered in the part number master 106aa, in association with the part number code of that new record.
[0028] The "Design Change Information" in Change Management Master 106ab indicates, for example, the version related to a product's design change. When a new record is registered, the initial value in the Design Change Information is, for example, "A," and it is updated sequentially to "B," "C," and so on, each time a design change occurs.
[0029] In the Change Management Master 106ab, the "Initial Shipment Date" field registers the date on which the product corresponding to the design change information was first shipped, and the "Change Confirmation Period" field registers the period during which a warning is required, even after the initial shipment date. The Initial Shipment Date field is blank when a record is added, for example, and is reset when the design change information is updated. The Change Confirmation Period may also be updated simultaneously when the design change information is updated, for example. The judgment process related to "change" work will be explained in detail later. Note that the design change information registered in Change Management Master 106ab is an example of work change information, the Initial Shipment Date is an example of information indicating the time of initial work completion, and the Change Confirmation Period is an example of a predetermined period.
[0030] As shown in Figure 5, the shipment history master 106ac stores the shipment history of the products to be manufactured. Figure 5 is a diagram showing an example of the shipment history master 106ac stored by the master storage unit 106a. As shown in Figure 5, the shipment history master 106ac stores the design change information, the last shipment date, and the long-term judgment period associated with the product code. Note that in Figure 5, records ac01 and ac02 are shown in the state before the design change information for product code "352057" shown in Figure 4 was updated.
[0031] Records in the shipping history master 106ac are registered or updated, for example, when design change information corresponding to a product code is updated, and also when a product corresponding to that design change information is shipped. The "last shipping date" indicates the date on which the product corresponding to the product code and design change information was last shipped. The "long-awaited shipment period" is registered as the period after the last shipping date during which a warning should be issued if the period exceeds this. The long-awaited shipment period is set in association with each combination of product code and design change information. Note that the shipping history master 106ac may be configured in such a way that, for example, design change information is not registered. In this case, the "last shipping date" will be updated even if a product with different design change information is shipped. The last shipping date is an example of information indicating the time when the above work was last completed, and the long-awaited shipment period is another example of a predetermined period.
[0032] Returning to Figure 1, the data storage unit 106b stores preliminary order data 106ba and notification data 106bb, as shown in Figure 6. Figure 6 is a diagram showing an example of the information stored by the data storage unit 106b of the business support device 100 according to this embodiment. The preliminary order data 106ba stores information related to orders, which is acquired by the acquisition unit 102a, which will be described later. The notification data 106bb stores information based on the determination result for the preliminary order data 106ba by the determination unit 102b, which will be described later. Details of the notification data 106bb will be described in detail later.
[0033] As shown in Figure 7, the preliminary order data 106ba stores information regarding orders for products to be manufactured. Figure 7 is a diagram showing an example of preliminary order data 106ba according to an embodiment. The preliminary order data 106ba stores the preliminary order date, scheduled shipping date, customer code, customer name, part number code and product name, design change information, quantity, sales unit price and sales amount, and customer order number in association with each other.
[0034] The preliminary order date indicates the date on which the preliminary order was received, which is a preliminary stage before the order is officially placed. The scheduled shipping date indicates the scheduled shipping date for the goods corresponding to that order. Note that the scheduled shipping date is an example of information indicating the expected completion date of the work, which is included in the order information, and the design change information is an example of information indicating changes in the work.
[0035] The control unit 102 is a CPU or the like that comprehensively controls the business support device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. Functionally, the control unit 102 comprises an acquisition unit 102a, a determination unit 102b, an update unit 102c, and an output unit 102d. Note that the configuration of the control unit 102 is just an example, and it may be configured to lack some functional units or to have other functional units. Furthermore, some or all of the functions of the update unit 102c and the output unit 102d may be executed by the determination unit 102b, or some of the functions of the determination unit 102b may be executed by other functional units.
[0036] The acquisition unit 102a acquires information related to orders. The acquisition unit 102a acquires information related to product orders via email or other means through the network 300, for example, from the EDI site 400 or terminal device 200 shown in Figure 1, and stores it in the provisional order data 106ba of the data storage unit 106b. The information related to product orders includes, for example, the provisional order date, scheduled shipping date, customer code and customer name, part number code and product name, design change information, quantity, sales unit price and sales amount, and customer order number, as shown in Figure 7, but the information may not include some of these. For example, the acquisition unit 102a may register the date on which it acquired information related to product orders as the provisional order date in the provisional order data 106ba, or the acquisition unit 102a, upon receiving information containing only the part number code, may refer to the part number master 106aa in the master storage unit 106a to acquire the product name and register it in the provisional order data 106ba.
[0037] The determination unit 102b determines whether the record registered in the provisional order data 106ba corresponds to a so-called "3H" operation. The update unit 102c registers or updates the contents of each master stored in the master storage unit 106a based on the information acquired by the acquisition unit 102a or the determination result by the determination unit 102b. The output unit 102d outputs the information based on the determination result by the determination unit 102b to the output device 114, etc., or transmits it to the terminal device 200, etc. via the network 300.
[0038] The determination unit 102b performs the determination process at a predetermined time each day, for example. Note that the timing at which the determination unit 102b performs the determination process is just an example; it may be at any time, such as each time a record is registered in the provisional order data 106ba by the acquisition unit 102a, or when instructed by a user (not shown).
[0039] [3-1. Determination process for "first-time" tasks] In the determination process, first, the determination unit 102b determines whether each record in the provisional order data 106ba corresponds to a "first-time" process. The update unit 102c may also update the part number master 106aa based on the determination result by the determination unit 102b. Figure 8 shows an example of the determination process for "first-time" operations and the update process for the part number master 106aa according to the embodiment. As shown in Figure 8, the determination unit 102b compares each record in the provisional order data 106ba shown in Figure 7 with the part number master 106aa shown in Figure 3. Specifically, the determination unit 102b determines whether the part number code of each record in the provisional order data 106ba is registered in the part number master 106aa based on the first determination condition shown below. <First Judgment Criteria> Preliminary order data. Part number code not in Part number master. Part number code
[0040] As shown in Figure 8, the part code "31008" for record ba11 and the part code "352057" for record ba12 of the preliminary order data 106ba are registered in records aa11 and aa12 of the part code master 106aa, respectively. On the other hand, the part code "352196" for record ba13 of the preliminary order data 106ba is not registered in the part code master 106aa. In this case, the determination unit 102b determines that record ba13 corresponds to a "first" operation.
[0041] In this case, the update unit 102c may register the "product code" and "product name" of the record determined to be a "first-time" operation in the product code master 106aa. As shown in Figure 8, the update unit 102c registers the product code "352196" and product name "disc spring 1" of record ba13, which was determined to be a "first-time" operation, in record aa23 of the product code master 106aa. The update unit 102c may also add a record of design change information "A" corresponding to product code "352196" to the change management master 106ab. Furthermore, when the initial shipment of the product corresponding to record ba13 is completed, the update unit 102c may add a record (not shown) corresponding to product code "352196" to the shipment history master 106ac.
[0042] [3-2. Determination process for "change" operations] Next, the determination unit 102b determines whether the records in the preliminary order data 106ba that are determined not to be "first-time" operations relate to "change" operations. First, the determination unit 102b determines whether the design change information for each record in the preliminary order data 106ba that is determined not to meet the first determination condition matches the design change information in the change management master 106ab, as shown in Figure 9, based on the second determination condition shown below. Figure 9 is a diagram showing an example of the determination process for "change" operations according to the embodiment, as well as the update process for the change management master 106ab and the shipping history master 106ac. Note that Figure 9 explains the determination for record ba02, which was acquired at a time (2024 / 10 / 1) before acquiring the information on orders corresponding to records ba11 to ba13 shown in Figure 8. <Second Judgment Criterion> Preliminary Order Data. Design Change Information ≠ Change Management Master. Design Change Information
[0043] The design change information "C" in record ba02 of the preliminary order data 106ba shown in Figure 9 does not match the design change information "B" registered in record ab01 of the change management master 106ab. In this case, the determination unit 102b determines that record ba02 corresponds to a "change" operation.
[0044] In this case, as shown in Figure 9, the update unit 102c updates the design change information corresponding to the part number code "352057" in the change management master 106ab to "C" as shown in record ab11. Alternatively, when the initial shipment of the product corresponding to record ba02 is completed, the update unit 102c may register the initial shipment date "2024 / 11 / 5" in the change management master 106ab as shown in record ab21.
[0045] Furthermore, based on the determination result, when the shipment of the product corresponding to record ba02 is completed, the update unit 102c also updates the final shipment date in the shipment history master 106ac to "2024 / 11 / 5" as shown in Figure 9. In this case, in record ac12 of the shipment history master 106ac, the design change information corresponding to product code "352057" is updated from "B" to "C", and the long-awaited judgment period is changed from "180" days to "30" days. Alternatively, the update unit 102c may update the design change information in the shipment history master 106ac when the design change information in the change management master 106ab is updated, and then update the final shipment date in the shipment history master 106ac again when the initial shipment of the product corresponding to that design change information is completed.
[0046] Furthermore, the determination unit 102b determines whether each record of the provisional order data 106ba, which has been determined to not meet the second determination condition, matches the third determination condition shown below, as determined to be the same as the design change information registered in the record of the change management master 106ab. Figure 10 is a diagram showing another example of the "change" determination process and the update process of the shipping history master 106ac according to the embodiment. The third determination condition is to determine whether the "scheduled shipping date" of each record of the provisional order data 106ba shown in Figure 10 is before the date on which the "change confirmation period" has elapsed from the "initial shipping date" in the record corresponding to the change management master 106ab (hereinafter sometimes referred to as the "change determination date"). In Figure 10, the determination of records ba11 to ba13 of the provisional order data 106ba is performed at the timing after record ba21 of the change management master 106ab and record ac12 of the shipping history master 106ac have been updated, as shown in Figure 9. <Third Judgment Condition> Preliminary Order Data: Scheduled Shipping Date ≤ Change Management Master: Initial Shipping Date + Change Management Master: Change Confirmation Period
[0047] The design change information "C" in record ba12 of the preliminary order data 106ba shown in Figure 10 is the same as the design change information "C" registered in record ab21 of the change management master 106ab. In other words, record ba12 does not meet the second determination condition. In this case, the determination unit 102b determines whether the scheduled shipping date "2024 / 11 / 25" of the preliminary order data 106ba shown in record ba12 is after the date (change determination date) when the change confirmation period of "60" days has elapsed from the initial shipping date "2024 / 11 / 5" of record ab21 for part number code "352057" in the change management master 106ab.
[0048] As shown in Figure 10, the date corresponding to record ab21 in the change management master 106ab, which is the date after the change confirmation period (60 days) has elapsed from the initial shipment date (2024 / 11 / 5), i.e., the change determination date is "2025 / 1 / 5". On the other hand, the scheduled shipment date for record ba12 in the preliminary order data 106ba shown in Figure 10 is "2024 / 11 / 25", which is a date before the change determination date. In this case, the determination unit 102b determines that record ba12, which does not meet the second determination condition but does meet the third determination condition, also corresponds to a "change" operation.
[0049] Furthermore, based on the determination result, when the shipment of the product corresponding to record ba12 is completed, the update unit 102c also updates the final shipment date of record ac12 in the shipment history master 106ac to "2024 / 11 / 25" as shown in record ac22, as shown in Figure 10.
[0050] On the other hand, as shown in Figure 10, if "Initial Shipment Date" is registered in the change management master 106ab, the shipment corresponding to the design change information does not qualify as the initial shipment. In this case, the update unit 102c does not update the change management master 106ab.
[0051] In this embodiment, even if the "initial shipment date" in the change management master 106ab is registered, meaning the product was manufactured in the past, if the scheduled shipment date falls within the change confirmation period, it may be determined to be a "change" operation. This allows for a decision process that provides warnings even when there is a history of performing the work, as long as the user becomes proficient in the process, thus reducing the likelihood of missed warnings. Furthermore, according to this embodiment, even for products determined to be "first-time" operations, if an order is received before the change confirmation period expires, they can be treated as "change" operations and subject to warnings. Alternatively, instead of a change confirmation period, for example, a number of change confirmations could be registered, and if a product has been shipped more than a predetermined number of times based on the same design change information, it may be determined that it is not a "change" operation.
[0052] In this embodiment, the determination unit 102b will determine that the record of the provisional order data 106ba satisfies the third determination condition even if the "initial shipment date" is not registered in the change management master 106ab, as shown in record ab11 in Figure 9. In this case, the update unit 102c may register the "initial shipment date" in the corresponding record of the change management master 106ab.
[0053] [3-3. Determination process for "long time no see" tasks] Next, the determination unit 102b determines whether each record in the preliminary order data 106ba relates to a "long time no see" operation. First, the determination unit 102b compares the scheduled shipping date of each record in the preliminary order data 106ba with the shipping history master 106ac, as shown in Figure 11, based on the fourth determination condition shown below. Figure 11 is a diagram showing an example of the "long time no see" operation determination process and the shipping history master 106ac update process according to the embodiment. Note that the "long time no see" operation determination process shown in Figure 11 is performed at the same timing as, for example, the "change" operation determination process for records ba11 to ba13 shown in Figure 10. <Fourth Judgment Condition> Informal Order Data: Scheduled Shipping Date ≥ Shipping History Master: Last Shipping Date + Shipping History Master: Delayed Shipping Period
[0054] As shown in Figure 11, the scheduled shipping date "2024 / 12 / 2" for record ba11 with product code "31008" is after the "long-awaited" judgment date "2024 / 8 / 4", which is the day after the last shipping date (2024 / 2 / 5) of record ac11 in the shipping history master 106ac, which is the day after the "long-awaited" judgment date (2024 / 8 / 4), which is the day after the "long-awaited" judgment date (2024 / 12 / 6), which is the day after the last shipping date (2025 / 11 / 5) of record ac12 in the shipping history master 106ac, which is the day after the "long-awaited" judgment date (2024 / 12 / 6), which is the day after the "long-awaited" judgment date (30 days). In this case, the determination unit 102b determines that record ba11 is a "long-awaited" operation, and record ba12 is not a "long-awaited" operation.
[0055] Furthermore, when the shipment of the product with product code "31008" in record ba11 is completed, the update unit 102c updates the final shipment date for product code "31008" in the shipment history master 106ac to "2024 / 12 / 2". Also, for product code "352057" in record ba12, which is determined not to be a "long time no see" operation, when the shipment of the corresponding product is completed, the update unit 102c updates the final shipment date for product code "352057" in the shipment history master 106ac to "2024 / 11 / 25", as shown in Figure 11.
[0056] As a result of this determination process, for example, the determination unit 102b registers records bb11 to bb13, as shown in Figure 12, in the notification data 106bb of the data storage unit 106b. Figure 12 is a diagram showing an example of the notification data 106bb stored by the data storage unit 106b according to this embodiment. As shown in Figure 12, the notification data 106bb further includes a "notification content" column in addition to the columns of the preliminary order data 106ba shown in Figure 7.
[0057] The "Notification Details" column in Figure 12 registers whether the operation corresponding to the product code and design change information of the record falls under one of the following categories: "Long Time No See" operation (product after a long time), "Change" operation, or "First Time" operation (product after a first time). For example, the notification details "Product after a long time no see" in record bb11 are an example of information indicating that it is a long time no see operation, the notification details "Change" in record bb12 are an example of information indicating that it is a change operation, and the notification details "First Time" in record bb13 are an example of information indicating that it is a first time operation.
[0058] Furthermore, while the example shown in Figure 12 describes an example where notification content is registered for all records ba11 to ba13 of the preliminary order data 106ba shown in Figure 7, if any of the records are not subject to notification, the notification data 106bb may not include that record, or the notification data 106bb may include that record but no "notification content" is registered.
[0059] Furthermore, the output unit 102d may send an email, as shown in Figure 13, to production management personnel, work personnel, etc., with the table of notification data 106bb shown in Figure 12 attached. Figure 13 is a diagram showing an example of a notification email according to the embodiment. As shown in Figure 13, the notification email states that the information on the order subject to judgment includes "first-time items", "changed items" and "items that have been changed for a long time".
[0060] As described above, the business support device 100 according to the embodiment has an acquisition unit 102a and a determination unit 102b. The acquisition unit 102a acquires information related to orders, including information indicating the scheduled completion time of the work and information on changes to the work. The determination unit 102b outputs information indicating that the work is a changed work if the period from the time of initial completion of the work to the scheduled completion time of the work, corresponding to the change information of the work, is within a predetermined period. With this configuration, warnings for work requiring attention, such as 3H work, can be issued with fewer omissions.
[0061] Furthermore, in this embodiment, the determination process for "long time no see" work based on the fourth determination condition is also performed for records that have been determined to be "change" work based on the second or third determination condition. Figure 14 is a diagram showing another example of the determination process for "change" work and the determination process for "long time no see" work according to the embodiment. Record ba22 of the preliminary order data 106ba shown in Figure 14 is based on information about an order with customer order number "C00022" that was acquired by the acquisition unit 102a on "2024 / 12 / 3", after the date on which the determination process for each record ba11 to ba13 shown in Figure 7 was performed, and after any of the scheduled shipping dates shown in records ba11 to ba13. In the record ba22 of the preliminary order data 106ba corresponding to customer order number "C00022", data regarding the order with part number code "352057" is registered.
[0062] In this case, the final shipping date in record ac21 of the shipping history master 106ac is "2024 / 12 / 2" as a result of the update process shown in Figure 11, as shown in Figure 14, and the final shipping date in record ac22 is "2024 / 11 / 25". On the other hand, as mentioned above, the initial shipping date in record ab21 of the change management master 106ab shown in Figure 14 remains unchanged at "2024 / 11 / 5" as shown in Figure 10.
[0063] In this situation, the "long time since last use" determination date based on record ac22 is changed to "2024 / 12 / 26," which is the last shipment date (2024 / 11 / 25) with the "long time since last use" determination period (30 days) added, while the "change determination date" based on record ab21 remains unchanged at "2025 / 1 / 5."
[0064] In this case, the determination unit 102b determines that the scheduled shipping date "2014 / 12 / 28" of record ba22 in the preliminary order data 106ba is on or before the change determination date "2025 / 1 / 5". The determination unit 102b also determines that the scheduled shipping date of record ba22 is after the long-awaited work determination date "2024 / 12 / 25". In other words, the determination unit 102b determines that record ba22 falls under both the "change" operation and the "long-awaited work" operation.
[0065] In this state, the notification data 106bb contains data as shown in Figure 15. Figure 15 shows another example of the notification data 106bb stored by the data storage unit 106b according to the embodiment. As shown in Figure 15, after the determination process shown in Figure 14, two records with customer order number "C00022" are registered. Of these, record bb221 indicates that the order is a "change" operation, and record bb222 indicates that the order is a "long-awaited item".
[0066] In other words, in this embodiment, two records, bb221 and bb222, may be registered in the notification data 106bb, corresponding to one record ba22 in the preliminary order data 106ba.
[0067] In this case, the output unit 102d sends an email as shown in Figure 16, with the table shown in Figure 15 attached. Figure 16 is a diagram showing another example of notification data 106bb stored in the data storage unit 106b according to this embodiment.
[0068] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.
[0069] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.
[0070] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.
[0071] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.
[0072] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.
[0073] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.
[0074] Furthermore, with respect to the business support device 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.
[0075] For example, the processing functions of the business support device 100, particularly those performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the business support device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) stores a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to form the control unit.
[0076] Furthermore, this computer program may be stored on an application program server connected to the business support device 100 via any network, and it is possible to download all or part of it as needed.
[0077] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.
[0078] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.
[0079] The various databases stored in the memory unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.
[0080] Furthermore, the business support device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the business support device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment on the device.
[0081] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]
[0082] This invention is useful in manufacturing and other industries where 3H (hour, half, and half) work is common. [Explanation of Symbols]
[0083] 1. Business support system 100 Business support equipment 102 Control Unit 102a Acquisition Department 102b Judgment section 102c update section 102d Output Section 104 Communication Interface Section 106 Storage section 106a Master Storage Unit 106aa Part Number Master 106ab Change Management Master 106ac Shipping History Master 106b Data storage unit 106ba Preliminary Order Data 106bb notification data 108 Input / Output Interface Section 112 Input device 114 Output device 200 terminal devices 300 Networks 400 EDI sites
Claims
1. An acquisition unit that acquires information related to the order, including information indicating the expected completion date of the work and information on changes to the work, A determination unit that outputs information indicating that the work is a modified work if the period from the time of initial completion of the work to the scheduled time of completion of the work, corresponding to the change information of the said work, is within a predetermined period. A business support device having the following features.
2. It includes a storage unit that stores information about changes to the work and information about the time of the first completion of the work corresponding to the changes in the work, The determination unit, The system determines whether the work change information stored in the memory unit matches the work change information included in the order information. If it is determined that they do not match, the system outputs information indicating that the information regarding the order corresponds to the modification work. The business support device according to claim 1.
3. The determination unit, The memory unit determines whether or not information corresponding to the change information of the work at the time of the initial completion of the work is stored there. If it is determined that the information is not stored, the system outputs information indicating that the information regarding the order corresponds to the modification work. The business support device according to claim 2.
4. The memory unit stores information indicating the time when the operation was last completed. The determination unit, Determine whether the scheduled completion time of the aforementioned work is after a predetermined period from the time the last work was completed. If it is determined that the period is longer than the predetermined period, the system outputs information indicating that the order information corresponds to work that has not been performed for a long time. The business support device according to claim 2.
5. The information relating to the order includes information identifying the goods to be manufactured by the said work, The determination unit, Determine whether the information identifying the product included in the order information is stored in the storage unit. If it is determined that information identifying the previous product is not stored, the system outputs information indicating that the operation to manufacture the said product is the first time the operation has been performed. The business support device according to claim 2.
6. A business support method performed by a business support device equipped with a control unit, The control unit, Steps include obtaining information related to the order, including information indicating the expected completion date of the work and information regarding changes to the work, A step of outputting information indicating that the work in question is a change work if the period from the time of initial completion of the work to the scheduled time of completion of the work corresponding to the change information of the said work is within a predetermined period, A business support method characterized by performing the following actions.
7. A business support program to be executed by a business support device equipped with a control unit, The control unit, Steps include obtaining information related to the order, including information indicating the expected completion date of the work and information regarding changes to the work, A step of outputting information indicating that the work in question is a change work if the period from the time of initial completion of the work to the scheduled time of completion of the work corresponding to the change information of the said work is within a predetermined period, A business support program characterized by its ability to execute certain actions.
Citation Information
Patent Citations
Work instruction support system and work instruction support method
JP2020154589A