Disaster prevention equipment production management system

Abstract

To provide a disaster prevention equipment production management system capable of providing assistance in efficient production management for disaster prevention equipment.SOLUTION: A disaster prevention equipment production management system is provided, comprising an acquisition unit for acquiring a delivery date of disaster prevention equipment and a completion date of a specific step for producing the disaster prevention equipment, and a schedule generation unit configured to generate a production schedule including multiple steps for producing the disaster prevention equipment in such a way that the specific step is completed on the completion date before the delivery date.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a manufacturing management system for disaster prevention equipment that is equipped with a communication means for communicating in accordance with a communication contract with a telecommunications carrier. [Background technology]

[0002] The Fire Service Act requires the installation of automatic fire alarm systems depending on the conditions of buildings and other structures that are fire prevention targets. Disaster prevention equipment such as fire receivers for automatic fire alarm systems, emergency alarm systems, and emergency broadcast systems are generally manufactured in factories, inspected, and then delivered to the building to which they are being delivered. A database appropriate for the building to which the equipment is being delivered is incorporated into the manufactured disaster prevention equipment, and the disaster prevention equipment after delivery is configured to operate in accordance with the building. In recent years, disaster prevention equipment such as fire receivers that can communicate with mobile terminals and the like via communication networks such as the Internet have been proposed (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] From the start of manufacturing fire prevention equipment to delivery, multiple processes are required by multiple departments, including the procurement of parts, assembly, and creation of a database for each building. This process also includes undergoing inspection by the Japan Fire Equipment Inspection Association or a registered inspection organization, which must be completed before the delivery date. Inspection dates are determined in advance by the Japan Fire Equipment Inspection Association or other organizations, and inspection opportunities are limited, for example, twice a month. In addition, fire prevention equipment equipped with communication means that communicates with a telecommunications carrier must conclude a communications contract before the delivery date. However, since costs generally begin to arise from the conclusion of a communications contract, there is a desire to conclude the communications contract as close to the delivery date as possible.

[0005] As such, the manufacturing of disaster prevention equipment involves multiple processes involving multiple departments, and is made more complex by the addition of processes such as communication contracts and testing, which creates a heavy burden on users who need to schedule the entire manufacturing process.

[0006] The present invention provides a manufacturing management system for disaster prevention equipment that can support efficient manufacturing management of disaster prevention equipment. [Means for solving the problem]

[0007] The manufacturing management system for disaster prevention equipment of the present invention includes an acquisition unit that acquires the delivery date of the disaster prevention equipment and the completion date of a specific process for manufacturing the disaster prevention equipment, and a schedule generation unit that generates a manufacturing schedule including multiple processes for manufacturing the disaster prevention equipment so that the specific process is completed on the completion date before the delivery date. The manufacturing management system for disaster prevention equipment of the present invention is a manufacturing management system for disaster prevention equipment equipped with a communication means for communicating in accordance with a communication contract with a telecommunications carrier, and is equipped with an acquisition unit that acquires the delivery date of the disaster prevention equipment, the inspection date of the disaster prevention equipment, and the scheduled arrangement date of the communication contract, and a schedule generation unit that generates a manufacturing schedule including multiple processes for manufacturing the disaster prevention equipment so as to satisfy the first condition that the communication means for which the communication contract has been completed is incorporated into the disaster prevention equipment before the delivery date, and the second condition that the equipment can be inspected on the inspection date. [Effects of the Invention]

[0008] According to the present invention, it is possible to support efficient manufacturing management of disaster prevention equipment. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 10 is a diagram illustrating an application example of a manufacturing management system for disaster prevention equipment according to an embodiment. [Figure 2] 1 is a diagram showing a schematic manufacturing process from the start of manufacturing to delivery of a fire control panel according to an embodiment. FIG. [Figure 3] FIG. 2 is a block diagram showing a schematic configuration of a server according to an embodiment. [Figure 4] 1 is a block diagram showing a schematic configuration of a terminal device according to an embodiment; [Figure 5] 1 is a flowchart illustrating an example of the operation of a manufacturing management system according to an embodiment. [Figure 6] 10 is a diagram illustrating an example of a chart display of a manufacturing schedule according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The present invention is not limited to the following embodiments, and various modifications are possible without departing from the spirit of the present invention. Furthermore, the present invention includes all possible combinations of the configurations shown in the following embodiments. Furthermore, the device shown in the drawings is an example of the device of the present invention, and the device of the present invention is not limited to the device shown in the drawings. Furthermore, in each drawing, parts with the same reference numerals are the same or equivalent, and this is common throughout the entire specification.

[0011] Embodiment (System Configuration) FIG. 1 is a diagram showing an application example of a manufacturing management system 100 for disaster prevention equipment according to an embodiment. In this embodiment, an example is shown in which the manufacturing management system 100 for manufacturing a fire alarm receiver, which is an example of disaster prevention equipment, is realized by a server 10 and a terminal device 20. As shown in FIG. 1, the manufacturing management system 100 includes a server 10 and one or more terminal devices 20, and the server 10 and the terminal devices 20 are communicatively connected via a network N. The server 10 generates a manufacturing schedule and provides information about the generated manufacturing schedule to the terminal device 20. The terminal device 20 is used by users in each department involved in manufacturing to input conditions for the manufacturing schedule, display the manufacturing schedule, and the like. The network N is a dedicated or general-purpose, wireless or wired communication network.

[0012] (Fire alarm receiver manufacturing process) First, an outline of the manufacturing process will be described using an example in which the disaster prevention equipment is a fire receiver. Fig. 2 is a diagram showing an outline of the manufacturing process from the start of manufacturing to delivery of the fire receiver according to the embodiment.

[0013] When a project related to a fire alarm receiver begins, the delivery date is first determined (Step S1). The delivery date is determined by the disaster prevention equipment manufacturing manager or the like based on the request from the disaster prevention equipment delivery destination. Next, the overall manufacturing schedule is determined so as to meet the delivery date (Step S2).

[0014] When the manufacturing management system 100 of this embodiment is not used, the manufacturing schedule can be created by a manufacturing manager using general Gantt chart software, schedule management software, etc. In this case, the start and end dates of multiple processes to be carried out by multiple departments are determined so as to meet the delivery date.

[0015] The determined production schedule is then distributed to each department (step S3). Once the production schedule is distributed, each department begins work. Figure 2 shows an example in which the departments are divided into department A, which is responsible for steps S4 to S6, department B, which is responsible for steps S7 to S9, department C, which is responsible for steps S10 to S12, and department D, which is responsible for steps S13 to S15.

[0016] Department A creates a property DB to be incorporated into the fire receiver (step S4), performs a comprehensive system test (step S5), and stores the property DB on an operation server or a storage medium such as a memory card (step S6). Here, the property DB is a database of information on a map of the building where the fire receiver will be delivered and on devices connected to the fire receiver, such as detectors, to be installed in the building. Department B manufactures the fire receiver (step S7), inspects the fire receiver at the factory (step S8), and has the fire receiver certified (step S9). Department C arranges for communication means for the fire receiver (step S10), manufactures a communication unit such as an IoT gateway incorporating the communication means (step S11), and inspects the communication unit (step S12). Department D incorporates the communication unit into the fire receiver (step S13), arranges for a shipping date to the delivery site (step S14), and delivers the product to the site (step S15). The property DB is also incorporated at the delivery site.

[0017] Here, the inspection of the fire control device performed in step S9 is a process carried out by the Japan Fire Equipment Inspection Association or a registered inspection organization. The inspection date is predetermined by the Japan Fire Equipment Inspection Association or the like, and inspection opportunities are generally limited, for example, about twice a month. Furthermore, the communication means related to steps S10 to S12 is for communication with a mobile terminal or server, etc., and communication is performed in accordance with a communication contract with a telecommunications carrier. The communication means is, for example, a SIM (Subscriber Identity Module). Communication means such as a SIM require a communication contract to be concluded before delivery, but since costs generally arise from the conclusion of the communication contract, there is a demand to conclude the communication contract as close to the delivery date as possible. On the other hand, due to external reasons such as a semiconductor shortage in the market, it may take several weeks to arrange for a general-purpose communication means such as a SIM, making it difficult to predict the lead time.

[0018] As described above, the manufacturing process of a fire alarm receiver is made up of multiple steps, including the above-mentioned inspection and communication contract, and in reality, there are more steps and departments involved than those shown in the outline of Figure 2. From the start of manufacturing the fire alarm receiver to delivery, multiple steps handled by multiple departments proceed simultaneously, and in a given process, the products of multiple departments are combined. In this embodiment, a system is provided that supports the creation and management of a manufacturing schedule that includes such manufacturing steps.

[0019] (Server 10) 3 is a block diagram showing a schematic configuration of a server 10 according to an embodiment. The server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11, the storage unit 12, and the communication unit 13 are connected to each other via a bus so as to be able to communicate with each other.

[0020] The control unit 11 includes a CPU (Central Processing Unit), and the CPU reads and executes programs to realize the functions of the control unit 11. Note that some of the functions of the control unit 11 may be realized by dedicated hardware, and some may be realized by the CPU executing programs.

[0021] The storage unit 12 stores various data and programs executed by the control unit 11. The storage unit 12 is, for example, a non-volatile or volatile semiconductor memory such as a RAM, a ROM, a flash memory, an EPROM, or an EEPROM.

[0022] The communication unit 13 includes a communication interface circuit for communicating with the terminal device 20 via the network N.

[0023] The control unit 11 includes, as functional units, an acquisition unit 14, a schedule generation unit 15, a plan input unit 16, a progress input unit 17, a notification information generation unit 18, and a chart generation unit 19. These functional units operate as part of a manufacturing management system 100 for disaster prevention equipment.

[0024] The acquisition unit 14 acquires the delivery date of the disaster prevention equipment and the completion date of a specific process. In this embodiment, the specific process is a process related to the production of a fire alarm receiver, and the completion date of the process is the inspection date. Other specific processes may be provided besides this example. The acquisition unit 14 also acquires the planned arrangement date of a communication contract related to the communication means. The delivery date, inspection date, and planned arrangement date are input by the user into an input screen executed by an application installed on the terminal device 20, for example, and the acquisition unit 14 acquires the delivery date, inspection date, and planned arrangement date sent from the terminal device 20. The acquisition unit 14 may read out the delivery date, inspection date, and planned arrangement date stored in the memory unit 12 or the terminal device 20.

[0025] The schedule generation unit 15 generates a manufacturing schedule for the disaster prevention equipment. The schedule generation unit 15 generates or updates the manufacturing schedule based on the manufacturing process previously stored in the storage unit 12, the delivery date and inspection date acquired by the acquisition unit 14, and information input from the schedule input unit 16 and the progress input unit 17. The storage unit 12 stores data such as a calendar, the working days and working hours of each department, and the like, and this data is used to generate the manufacturing schedule.

[0026] 2, the manufacturing process of the disaster prevention equipment is made up of multiple processes including the above-mentioned inspection. The schedule generation unit 15 generates a manufacturing schedule based on the stored manufacturing process, delivery date, inspection date, etc., so as to satisfy a first condition that a communication means such as a SIM card with a completed communication contract is incorporated into the disaster prevention equipment, and a second condition that the inspection can be conducted on the inspection date. The manufacturing schedule includes, for example, all processes included in the manufacturing process, the scheduled start date and scheduled end date of each process, and the department in charge of each process.

[0027] The schedule input unit 16 accepts input of desired changes to the generated manufacturing schedule. For example, the schedule input unit 16 accepts input of desired changes to the scheduled arrangement date and inspection date for arranging communication means such as a SIM card with a telecommunications carrier.

[0028] The progress input unit 17 accepts input of progress information of actual work in the generated manufacturing schedule. The progress information may include the degree of progress of each process (e.g., 10% complete), as well as information such as the name of the person in charge, the number of work steps, the start date of the work, the completion date of the work, and matters to be shared among the workers.

[0029] Information for the schedule input unit 16 and the progress input unit 17 is entered by the user, for example, on an input screen executed by an application installed on the terminal device 20, and the schedule input unit 16 and the progress input unit 17 acquire the information sent from the terminal device 20.

[0030] The notification information generation unit 18 generates information to be notified to the user operating the terminal device 20. For example, when a manufacturing schedule that satisfies the first condition related to the communication contract and the second condition related to the inspection date cannot be generated before the delivery date, the notification information generation unit 18 generates notification information to prompt the user to set a new delivery date. Furthermore, when progress information has not been input into the progress input unit 17 even after the scheduled end date of a process has passed, or when the progress of a process is slower than expected, the notification information generation unit 18 may generate notification information to prompt the user to input or confirm progress information. Furthermore, when each process is completed, the notification information generation unit 18 may generate notification information to notify the user that a process has been completed. Furthermore, when the delivery date of a part or the like required for a process is extended or a discontinued product is produced, the notification information generation unit 18 may generate notification information to notify other departments of the information when the information is input via the input unit 25 of the terminal device 20. The notification information generated by the notification information generation unit 18 is transmitted to the terminal device 20 by e-mail, a dedicated application, or the like, and is notified to the user on a display unit 24 (see FIG. 4) of the terminal device 20. The destination address of the notification information is stored in advance in the storage unit 12. The destination address may be varied depending on the content of the notification information, so that the notification information is sent only to the relevant parties.

[0031] The chart generation unit 19 generates data for expressing the manufacturing schedule generated by the schedule generation unit 15 in a diagram format such as a flowchart or a Gantt chart. The progress information input to the progress input unit 17 may be reflected in the flowchart or the like generated by the chart generation unit 19.

[0032] (Terminal device 20) 4 is a block diagram showing a schematic configuration of a terminal device 20 according to an embodiment. The terminal device 20 is a dedicated or general-purpose computer device, a tablet terminal, a smartphone, or the like, and is used by a user involved in the manufacture or management of disaster prevention equipment. The terminal device 20 includes a control unit 21, a storage unit 22, a communication unit 23, a display unit 24, and an input unit 25. The control unit 21, the storage unit 22, the communication unit 23, the display unit 24, and the input unit 25 are connected to each other via a bus so as to be able to communicate with each other.

[0033] The control unit 21 includes a CPU, and the CPU reads and executes programs to realize the functions of the control unit 11. Note that some of the functions of the control unit 21 may be realized by dedicated hardware, and some may be realized by the CPU executing programs.

[0034] The storage unit 22 stores various data and programs executed by the control unit 21. The storage unit 22 is, for example, a non-volatile or volatile semiconductor memory such as a RAM, a ROM, a flash memory, an EPROM, or an EEPROM.

[0035] The communication unit 23 includes a communication interface circuit for communicating with the server 10 via the network N.

[0036] The display unit 24 is a device that displays information, and is, for example, a liquid crystal display, an organic EL display, or electronic paper.

[0037] The input unit 25 is a device that accepts information input from a user, and is, for example, a keyboard, a mouse, a touch panel, or the like.

[0038] In this embodiment, a dedicated application for viewing the production schedule of disaster prevention equipment and inputting changes to the production schedule is installed on the terminal device 20, and the user inputs and outputs information to and from the server 10 via the application. Note that instead of a dedicated application program, information may be input and output to and from the server 10 using a general-purpose browser or the like.

[0039] (Generating a production schedule) FIG. 5 is a flowchart showing an example of the operation of the manufacturing management system 100 according to the embodiment. The manufacturing management system 100 acquires the delivery date, the inspection date, and the scheduled delivery date (step S101). In this embodiment, the acquisition unit 14 of the server 10 acquires the delivery date, the inspection date, and the scheduled delivery date input to the terminal device 20. In step S101, the completion date of another specific process may also be acquired. Subsequently, the schedule generation unit 15 generates a manufacturing schedule (step S102) and determines whether the generated manufacturing schedule satisfies the first and second conditions (step S103). The first condition is that a communication means, such as a SIM card, for which a communication contract has been completed before the delivery date is incorporated into the disaster prevention equipment. The second condition is that the certification can be completed on the certification date. An example of a case in which the first condition is not satisfied is when the scheduled delivery date is too close to the delivery date and the work for the process after the communication contract cannot be completed within the time until the delivery date. An example of a case in which the second condition is not satisfied is when the manufacturing process for the fire alarm receiver is not completed before the certification date. The first condition may include a condition that the period from the completion of the communication contract to the delivery date is less than a threshold value. This allows the completion of the communication contract and the delivery date to be closer together, thereby reducing costs incurred before the delivery date due to the communication contract.

[0040] If the first condition and the second condition are not satisfied, i.e., if one or both of the first condition and the second condition are not satisfied (step S103: NO), the user is prompted to set a new delivery date (step S104). Specifically, the notification information generation unit 18 generates notification information for prompting the user to set a new delivery date, and the notification information is transmitted to the terminal device 20. When the user, who has viewed the notification information on the terminal device 20, inputs a new delivery date into the terminal device 20, the process returns to step S101, and the new delivery date is acquired by the acquisition unit 14.

[0041] If the first condition and the second condition are satisfied (step S103: YES), the generated production schedule is output (step S105). Specifically, the server 10 transmits the production schedule to the terminal device 20, and the display unit 24 of the terminal device 20 displays the production schedule in a table format or the like. Alternatively, the chart generation unit 19 may generate a flowchart or a Gantt chart and transmit it to the terminal device 20, and the display unit 24 of the terminal device 20 may display the production schedule in the form of a flowchart or a Gantt chart.

[0042] The user, upon viewing the production schedule output in step S105, checks the planned arrangement date for the communication means to determine whether or not the planned arrangement date needs to be changed, and checks the examination date to determine whether or not the examination can be taken on that examination date. The planned arrangement date and examination date reflected in the production schedule are those obtained in step S101, but the user can change them if adjustments are necessary when viewing the entire generated production schedule. If the user wishes to change the planned arrangement date for the communication means, the user inputs the desired change date into the input unit 25 of the terminal device 20. The user also inputs whether or not the examination can be taken on the examination date.

[0043] In step S106, it is determined whether a desired change date for the scheduled order date has been input. If an input has been made (step S106: YES), the process returns to step S102, and a new production schedule is generated based on the desired change date for the scheduled order date. If a desired change date for the scheduled order date has not been input (step S106: NO), the process proceeds to step S107.

[0044] In step S107, it is determined whether the user has input that they will not take the test on the test date. If the user has input that they will not take the test on the test date (step S107: YES), the system prompts the user to input a new test date (step S108). Specifically, the notification information generation unit 18 generates notification information to prompt the user to input a new test date, and the notification information is sent to the terminal device 20. When the user sees the notification information on the terminal device 20 and inputs a new test date into the terminal device 20, the system returns to step S101, and the new test date is acquired by the acquisition unit 14. Alternatively, the display unit 24 of the terminal device 20 may display multiple test date candidates, and the user may input a new test date by selecting one from the multiple candidates.

[0045] If there is no input indicating that the test will not be taken on the test date (step S107: NO), the generated production schedule is confirmed (step S109). Based on the confirmed production schedule, the chart generation unit 19 can generate a flowchart, a Gantt chart, or the like.

[0046] FIG. 6 is an example of a chart display of a production schedule according to an embodiment. FIG. 6 illustrates an example of a production schedule displayed as a flowchart showing the processes performed by departments A through Z in chronological order from top to bottom. In FIG. 6, each open or shaded rectangle represents a process. Open rectangles represent processes that have not yet been performed, and shaded rectangles represent processes that have been completed. By displaying each of the multiple processes in a manner that corresponds to its progress, the production manager and the managers of each process can easily grasp the progress status. The display of each process may differ depending on the progress level of each process. For example, a number indicating the progress level (e.g., 0%, 20%, 100%) may be added to the symbol representing the process, or the color of the symbol representing the process may be changed depending on the progress level. Processes that are behind schedule may be displayed with a specific symbol or in a specific color.

[0047] As described above, the manufacturing management system 100 for disaster prevention equipment of this embodiment includes an acquisition unit 14 that acquires the delivery date of the disaster prevention equipment and the completion date of a specific process for manufacturing the disaster prevention equipment, and a schedule generation unit 15 that generates a manufacturing schedule including multiple processes for manufacturing the disaster prevention equipment so that the specific process is completed on the completion date before the delivery date. According to this embodiment, it is possible to support efficient manufacturing management of disaster prevention equipment.

[0048] Furthermore, in this embodiment, the acquisition unit 14 acquires the delivery date of the disaster prevention equipment, the inspection date of the disaster prevention equipment, and the planned date for arranging the communication contract. The schedule generation unit 15 generates a production schedule to satisfy a first condition that a communication means for which a communication contract has been completed is incorporated into the disaster prevention equipment before the delivery date, and a second condition that the inspection can be conducted on the inspection date. Therefore, the production management system 100 can support efficient production management of disaster prevention equipment, including communication contracts involving external businesses.

[0049] The manufacturing schedule generated by the schedule generating unit 15 also includes the planned arrangement date for arranging for the communication means with the telecommunications carrier. Therefore, the user can easily understand the planned arrangement date for the telecommunications carrier by viewing the generated manufacturing schedule.

[0050] The manufacturing management system 100 also includes a schedule input unit 16 that accepts input of a desired change date for the scheduled delivery date. When a desired change date for the scheduled delivery date is input, the schedule generation unit 15 updates the manufacturing schedule so that the desired change date is met. Although costs related to communication means can vary depending on the date on which communication means are arranged with a telecommunications carrier, a manufacturing schedule that reflects the desired change date for the scheduled delivery date can be generated, allowing for a manufacturing schedule that suits the situation.

[0051] The manufacturing management system 100 also includes a schedule input unit 16 that accepts input regarding whether or not the test will be taken on the test date. When input indicating that the test will not be taken on the test date is accepted, the schedule generation unit 15 generates a manufacturing schedule based on another test date. Since there are only a limited number of test dates, if the initial test date is inconvenient, a manufacturing schedule can be generated for another test date, improving user convenience.

[0052] Furthermore, the manufacturing management system 100 includes a notification unit that prompts the user to set a new delivery date if a manufacturing schedule that satisfies the first condition related to the planned arrangement date for the communication means and the second condition related to the inspection date cannot be generated. In this embodiment, the notification information generation unit 18 of the server 10 and the display unit 24 of the terminal device 20 function as the notification unit. In this manner, by prompting the user to set a new delivery date if a manufacturing schedule that satisfies the first and second conditions and is in time for the delivery date cannot be generated, the manufacturing manager can easily adjust the delivery date with the delivery destination, etc., and resetting the delivery date can create a reasonable manufacturing schedule.

[0053] The manufacturing management system 100 also includes a display unit 24 on the terminal device 20 that displays the manufacturing schedule as a flowchart or Gantt chart. The display unit 24 displays each of the multiple processes included in the manufacturing schedule in a format that corresponds to the progress status. This makes it easy for the user to understand the manufacturing schedule and its progress status, even if the manufacturing process is complex and involves multiple departments.

[0054] (Variation 1) In the embodiment, an example has been shown in which the manufacturing management system 100 is realized by the server 10 and the terminal device 20, but these functions may be realized by a single device. Also, the functions of the server 10 may be realized by multiple devices.

[0055] (Variation 2) While Fig. 5 shows an example in which the user can change the planned arrangement date and inspection date of the communication means in the generated manufacturing schedule, the user may also be able to edit other milestone dates. In this case, the user inputs a change to the due date of one of the multiple processes included in the manufacturing schedule output in step S105 of Fig. 5 into the terminal device 20, and the schedule generation unit 15 updates the manufacturing schedule based on the changed due date. Furthermore, if an additional process is required, the user may input the change into the terminal device 20 to generate a manufacturing schedule that adds that process. In this way, a manufacturing schedule that flexibly responds to the parts procurement situation, etc. can be generated.

[0056] (Variation 3) In the present embodiment, an example of generating a manufacturing schedule for a fire alarm receiver, which is disaster prevention equipment, has been shown, but the manufacturing management system 100 may also generate a schedule for a replacement process for disaster prevention equipment or a replacement process due to a malfunction or the like. The replacement process and replacement process for disaster prevention equipment include multiple processes carried out by multiple departments, so that the same effect as in the embodiment can be provided to the user. Furthermore, the disaster prevention equipment may be an emergency alarm system, an emergency broadcast system, or other equipment. [Explanation of symbols]

[0057] 10 Server, 11 Control unit, 12 Memory unit, 13 Communication unit, 14 Acquisition unit, 15 Schedule generation unit, 16 Plan input unit, 17 Progress input unit, 18 Notification information generation unit, 19 Chart generation unit, 20 Terminal device, 21 Control unit, 22 Memory unit, 23 Communication unit, 24 Display unit, 25 Input unit, 26 Input unit, 100 Manufacturing management system, N network.

Claims

1. A manufacturing management system for disaster prevention equipment, An acquisition unit that acquires the delivery date of the disaster prevention equipment and the completion date of a specific process for manufacturing the disaster prevention equipment; a schedule generating unit that generates a manufacturing schedule including a plurality of processes for manufacturing the disaster prevention equipment so that a specific process is completed on the completion date before the delivery date. Disaster prevention equipment manufacturing management system.

2. A manufacturing management system for disaster prevention equipment equipped with a communication means for communicating with a telecommunications carrier under a communication contract, an acquisition unit that acquires the delivery date of the disaster prevention equipment, the inspection date of the disaster prevention equipment, and the planned arrangement date of the communication contract; and a schedule generating unit that generates a manufacturing schedule including a plurality of processes for manufacturing the disaster prevention equipment so as to satisfy a first condition that the communication means for which the communication contract has been completed is incorporated into the disaster prevention equipment before the delivery date and a second condition that the inspection can be performed on the inspection date. Disaster prevention equipment manufacturing management system.

3. a schedule input unit that receives input of a desired date for changing the scheduled arrangement date or whether or not the test can be taken on the test date; When it is input that the scheduled delivery date cannot be inspected on the desired change date or the inspection date, the schedule generation unit updates the production schedule so that the desired change date is met or based on another inspection date. The manufacturing management system for disaster prevention equipment according to claim 2.

4. a notification unit that prompts the user to set a new delivery date when the production schedule that satisfies the first condition and the second condition cannot be generated; The manufacturing management system for disaster prevention equipment according to claim 2 or 3.

5. a display unit that displays the manufacturing schedule as a flowchart or a Gantt chart, The display unit displays each of the plurality of processes included in the manufacturing schedule in a manner according to a progress status. The manufacturing management system for disaster prevention equipment according to claim 1 or 2.

Images