A production process intelligent reminding method and system
Patent Information
- Application Number
- CN202611138725.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-29
- Publication Date
- 2026-10-30
AI Technical Summary
[0005]本发明提供一种生产过程智能提醒方法及系统，以至少解决现有技术中多渠道分散且缺乏全生命周期管理的问题
本申请提供的生产过程智能提醒方法中，本申请通过接收通知请求，并根据模板编号从模板库中查询对应的通知模板，通过模板编号统一索引和查询机制，实现了通知模板的集中管理和复用，降低了重复配置成本。
Smart Images
Figure CN123014295A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of production management technology, and in particular relates to an intelligent reminder method and system for the production process. Background Technology
[0002] In the field of industrial manufacturing and production management, various abnormal alarms, equipment maintenance reminders, and quality warnings during the production process are crucial for ensuring the continuous and stable operation of production lines. With the increasing informatization of the manufacturing industry, enterprises are placing higher demands on the timeliness, accuracy, and traceability of these notifications.
[0003] To address these needs, existing technologies primarily use single channels such as independent system notifications, emails, or voice broadcasts to send production reminders. Some enterprises embed notification functions into their business systems through custom-developed hard-coded methods, with each business system managing its own reminder content and sending logic.
[0004] However, in existing notification methods, the same notification content needs to be configured repeatedly, and important information is easily missed due to the single channel; the notification content is stored in the business system in a fixed text format, and it is impossible to dynamically generate personalized information according to the recipient or scenario; after the notification is sent, the operation and maintenance personnel cannot confirm whether the notification has been received and processed. Summary of the Invention
[0005] This invention provides a method and system for intelligent reminders during the production process, which at least solves the problems of multiple channels being scattered and lacking full lifecycle management in the prior art.
[0006] In a first aspect, embodiments of this application provide a method for intelligent reminders during the production process, the method comprising: Step S1: Configure a notification template, which includes a template number, template name, notification title, notification content, notification type, notification level, notification method, and variable placeholders, and store the configured notification template in the template library; Step S2: Receive a notification request, which includes a template number, recipient information, notification level code, and variable parameters. Query the corresponding notification template from the template library based on the template number. Step S3: Replace the variable placeholders with the variable parameters to generate the final notification content; Step S4: According to the notification method in the notification template, the final notification content is concurrently distributed to the corresponding channels through the multi-channel unified distribution engine; Step S5: Create notification records and manage the full lifecycle status of notifications.
[0007] Furthermore, in step S1, the notification method includes at least one of the following: System notifications, emails, voice broadcasts, and Andon systems.
[0008] Furthermore, in step S4, the multi-channel unified distribution engine operates concurrently, specifically including: Parse the target channel set based on the notification method field, and create an independent distribution task for each channel; Each dispatch task is submitted to a thread pool, which uses a configurable core thread count and maximum thread count. If the initial transmission fails, the system will retry according to the exponential backoff strategy. If the retry still fails, the system will select an alternative channel to send a downgrade notification according to the downgrade routing table and record the failure log. The notification method field in the notification template is defined in the form of an ordered list, with channels appearing earlier in the list having higher priority. When a high-priority channel sends successfully and a low-priority channel is configured in serial mode, the low-priority channel skips sending. When a high-priority channel fails to send, the low-priority channel sends normally. Generate a distribution report, which includes the success or failure status of each channel, the sending time, and the number of retries, and write the distribution report to the notification record.
[0009] Furthermore, in step S2, the recipient information includes a list of recipient IDs and their configuration dimensions; the configuration dimensions include user dimension, role dimension, and department dimension. The user dimension specifies a user ID, and the single user corresponding to that user ID is the recipient. The role dimension specifies the role ID, and all users under that role ID are the recipients. The department dimension specifies the department ID, and all users under that department ID are the recipients.
[0010] Furthermore, the notification template also includes an access Andon flag, broadcast timeout time, and callback address.
[0011] Furthermore, the method also includes Andon processing, specifically including: after the final notification content is distributed to the Andon system, automatically creating an Andon call record and starting timeout monitoring, covering the status flow of triggering, arrival, processing, transfer and escalation; If the handler fails to respond within the configured timeout period, a timeout escalation will be automatically triggered. The handler will be replaced or added according to the escalation policy, and an escalation notification will be sent to the replaced or added handler.
[0012] Furthermore, the method also includes voice broadcasting processing, specifically including: A standalone audio broadcast server is deployed, and a configuration file is loaded upon startup. The configuration file contains parameters such as playback interval, volume, and speech rate. The audio broadcast server periodically polls and calls the main system application programming interface according to the playback interval to obtain the list of active broadcasts; The audio broadcasting server opens a Hypertext Transfer Protocol interface to receive priority push requests and set a priority playback flag. The audio broadcasting server calls the operating system's speech synthesis engine to convert the notification text into a speech signal and play it; wherein, the English words in the notification text are split letter by letter and played in sequence, the playback is controlled according to the volume and speech rate parameters in the configuration file, and the number of playbacks and the last playback time are recorded. Automatically filter out expired broadcasts and update the broadcast status to complete.
[0013] Furthermore, the English words in the notification text are broken down letter by letter and then broadcast sequentially, specifically including: Iterate through each character in the notification text. When a continuous sequence of English letters is detected, the sequence is split into characters one by one, and a pause marker of a preset duration is inserted after each split letter. Non-English letter characters remain unchanged and are directly concatenated into the broadcast text. The speech synthesis engine uses the Speech API built into the Windows operating system and is configured in character reading mode, with the speech rate parameter set to 0 and the volume parameter set to 80.
[0014] Furthermore, in step S5, the processing result feedback from the external system is received through the status callback interface, and notification archiving and cleanup are implemented.
[0015] Secondly, embodiments of this application also provide a system applied to the intelligent reminder method for the production process as described in the above aspects, the system comprising: The notification template configuration module is used to configure and manage notification templates, storing template number, template name, notification title, notification content, notification type, notification level, notification method, and variable placeholders, and storing the configured notification templates to the template library; The notification request receiving module is used to receive notification requests, which include template number, recipient information, notification level code and variable parameters, and to query the corresponding notification template from the template library according to the template number. The content generation module is used to replace the variable placeholders with the variable parameters to generate the final notification content; A multi-channel unified distribution engine is used to concurrently distribute the final notification content to the corresponding channels according to the notification method in the notification template; The notification status management module is used to create notification records and manage the status of notifications throughout their entire lifecycle.
[0016] As can be seen from the above technical solutions, the present invention has the following advantages: In the intelligent reminder method for the production process provided in this application, the application receives notification requests and queries the corresponding notification template from the template library according to the template number. Through the unified indexing and query mechanism of template number, the centralized management and reuse of notification templates are realized, reducing the cost of repetitive configuration.
[0017] This application generates the final notification content by replacing variable placeholders with variable parameters, so that the same template can be adapted to different recipients and different workstations.
[0018] According to the notification method in the notification template, this application distributes the final notification content concurrently to the corresponding channels through a multi-channel unified distribution engine. The multi-channel unified distribution engine enables concurrent distribution of system notifications, emails, voice broadcasts, and Andon systems, ensuring that important information reaches the recipients simultaneously through multiple channels and avoiding information omissions caused by a single channel.
[0019] This application achieves traceable management of the entire lifecycle of a notification by creating notification records and managing the full lifecycle status of the notification. By creating notification records and tracking key statuses such as creation time, sending time, receiving time, and processing time, it enables full lifecycle management of notifications from creation to completion. Attached Figure Description
[0020] To more clearly illustrate the technical solution of this application, the accompanying drawings used in the description will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 This is a flowchart of the intelligent reminder method for the production process described in this invention. Detailed Implementation
[0022] To make the purpose, features, and advantages of this application more apparent and understandable, specific embodiments and accompanying drawings will be used to clearly and completely describe the technical solution protected by this application. Obviously, the embodiments described below are only some embodiments of this application, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.
[0023] This application provides a method and system for intelligent reminders during the production process, addressing the urgent technical problem of achieving unified distribution across multiple channels and full lifecycle management.
[0024] The technical solutions proposed in the embodiments of this application will be described in detail below with reference to the accompanying drawings.
[0025] Figure 1 A flowchart illustrating a production process intelligent reminder method provided in an embodiment of this application. Figure 1 As shown in the embodiment of this application, a production process intelligent reminder method is provided, the method comprising: Step S1: Configure the notification template. The notification template includes a template number, template name, notification title, notification content, notification type, notification level, notification method, and variable placeholders. Store the configured notification template in the template library. The notification method uses multi-channel distribution. The template content supports dynamic replacement of variable placeholders. For example, if the template content is "Please {receiver} go to {address}-{workstation} to handle equipment malfunction," it will be replaced by "Please Mr. Zhang go to Workshop A-Plug-in Workstation to handle equipment malfunction" at runtime using the template engine. The notification level includes multiple levels, which are differentiated according to urgency to ensure that higher-level notifications are delivered first.
[0026] Step S2: Receive a notification request. The notification request includes a template number, recipient information, notification level code, and variable parameters. Query the corresponding notification template from the template library based on the template number. After receiving the notification request, the service queries the corresponding notification template based on the template number, replaces the variable placeholders in the notification template with the variable parameters to generate the final notification content, creates a notification record to generate a notification ID, creates a notification user association record, triggers multi-channel distribution based on the notification method, and returns the notification ID for subsequent tracking.
[0027] Step S3: Replace the variable placeholders with the variable parameters to generate the final notification content; Step S4: According to the notification method in the notification template, the final notification content is concurrently distributed to the corresponding channels through the multi-channel unified distribution engine; Step S5: Create notification records and manage the full lifecycle status of notifications.
[0028] It should be noted that, in step S1, the notification method includes at least one of the following: System notifications, emails, voice broadcasts, and Andon systems.
[0029] In an exemplary embodiment, step S4, where the multi-channel unified distribution engine operates concurrently, specifically includes: Parse the target channel set based on the notification method field, and create an independent distribution task for each channel; Each task is submitted to the thread pool, which has a configurable number of core threads and a maximum number of threads. The default number of core threads is twice the number of CPU cores. After the initial transmission fails, the system will retry according to the exponential backoff strategy, with a backoff base of 2 seconds and a maximum of 3 retries. If the system still fails after retrying, a downgrade notification will be sent through an alternative channel selected according to the downgrade routing table, and a failure log will be recorded. The notification method field in the notification template is defined in the form of an ordered list, with channels appearing earlier in the list having higher priority. When a high-priority channel sends successfully and a low-priority channel is configured in serial mode, the low-priority channel skips sending. When a high-priority channel fails to send, the low-priority channel sends normally. Generate a distribution report, which includes the success or failure status of each channel, the sending time, and the number of retries, and write the distribution report to the notification record.
[0030] In step S4, according to the notification method in the notification template, the final notification content is concurrently distributed to the corresponding channels through a multi-channel unified distribution engine, specifically including: Automatically select the distribution channel based on the notification method: If the notification method includes system notifications, a system notification record will be created and pushed to the front end; If the notification method includes email, the email service will be invoked to send the message and log it. If the notification method includes voice broadcast, a broadcast record is created and pushed to the broadcast server; If the notification method includes the Andon system, create an Andon call record and start timeout monitoring.
[0031] Specifically, it supports multiple channel selection configurations based on the notification method and automatically selects distribution channels based on the notification method field, executes the distribution process concurrently, and provides combinations of notification methods: When the notification method only includes system notifications, the system notification is initiated by creating a system notification record and pushing it to the front end; the user perceives it as receiving the notification message on the front end interface.
[0032] When the notification method only includes email, the system initiates an email service call to send an email to the recipient's mailbox and records the sending log; the user perceives it as receiving a notification email in their inbox.
[0033] When the notification method only includes voice broadcast, the system initiates the creation of a broadcast record and pushes it to the broadcast server. The broadcast server then broadcasts the notification content via TTS; the user perceives this as hearing the voice broadcast.
[0034] When the notification method only includes the Andon system, the initiation is to create an Andon call record and start timeout monitoring. The Andon system enters the triggered state and waits for the handler's response. When the user perceives the Andon system as triggered, the handler needs to be present to handle it.
[0035] When notification methods include system notifications and emails, they are initiated concurrently—a system notification record is created and pushed to the front end, while the email service is called to send the email; the user perceives that the front end and the email address receive the notification simultaneously.
[0036] When notification methods include system notifications and voice broadcasts, they are initiated concurrently—a system notification record is created and pushed to the front end, while a broadcast record is created and pushed to the broadcast server; the user perceives that the front end sees the notification and hears the voice broadcast at the same time.
[0037] When the notification method includes system notifications and Andon system notifications, the process is initiated concurrently—a system notification record is created and pushed to the front end, while an Andon call record is created and timeout monitoring is started; the user perceives the notification as the front end seeing it, and the Andon system starts timing.
[0038] When notification methods include email and voice broadcast, they are initiated concurrently—the email service is called to send the email, and a broadcast record is created and pushed to the broadcast server at the same time; the user perceives that the email has been received in the mailbox and the voice broadcast has been heard at the same time.
[0039] When notification methods include email and the Andon system, the process is initiated concurrently—the email service is called to send the email, while an Andon call record is created and timeout monitoring is started; the user perceives that the email has been received in their mailbox, and the Andon system starts timing.
[0040] When the notification method includes voice broadcast and Andon system, the process is initiated concurrently—a broadcast record is created and pushed to the broadcast server, while an Andon call record is created and timeout monitoring is started; the user perceives this as hearing the voice broadcast, and the Andon system starts timing.
[0041] When notification methods include system notifications, emails, and voice broadcasts, the process is initiated concurrently: creating a system notification record and pushing it to the front end, calling the email service to send the email, and creating a broadcast record and pushing it to the broadcast server; the user perceives receiving notifications from the front end, email, and voice channels simultaneously.
[0042] Notification methods include system notifications, emails, and Andon system notifications. When initiated, these actions are performed concurrently: creating a system notification record to push to the front end, calling the email service to send the email, creating an Andon call record, and starting timeout monitoring; the user perceives that the front end and email have received notifications, and the Andon system is timing the notification.
[0043] The notification methods include system notifications, voice broadcasts, and Andon system notifications. When these are initiated, they are executed concurrently: a system notification record is created and pushed to the front end; a broadcast record is created and pushed to the broadcast server; and an Andon call record is created and timeout monitoring is started. The user perceives that the front end and voice receive the notification, and the Andon system times out.
[0044] When notification methods include email, voice broadcast, and Andon system, the process is initiated concurrently—calling the email service to send emails, creating a broadcast record to push to the broadcast server, creating an Andon call record, and starting timeout monitoring; the user perceives receiving notifications via email and voice, while the Andon system times out.
[0045] Notification methods include system notifications, email, voice broadcasts, and Andon system notifications. When the system is activated, all four channels are concurrently executed for distribution: creating a system notification record and pushing it to the front end, calling the email service to send the email, creating a broadcast record and pushing it to the broadcast server, creating an Andon call record, and starting timeout monitoring. The user perceives that they receive notifications simultaneously from the front end, email, and voice channels, while the Andon system starts timeout monitoring.
[0046] Under each combination, the multi-channel unified distribution engine iterates through the selected channels in the notification method field and executes the corresponding distribution logic for each channel. The channels do not block each other and execute concurrently.
[0047] According to another embodiment of the present invention, in step S2, the recipient information includes a list of recipient IDs and their configuration dimensions; the configuration dimensions include user dimension, role dimension and department dimension; The user dimension specifies a user ID, and the single user corresponding to that user ID is the recipient. The role dimension specifies the role ID, and all users under that role ID are the recipients. The department dimension specifies the department ID, and all users under that department ID are the recipients.
[0048] Enables dynamic querying and verification of recipient information to ensure the accuracy of notification delivery.
[0049] According to an embodiment of this application, the notification template further includes an access Andon flag, a broadcast timeout time, and a callback address.
[0050] In one embodiment, the method further includes Andon processing, specifically including: automatically creating an Andon call record and starting timeout monitoring after the final notification content is distributed to the Andon system, covering the status flow of triggering, arrival, processing, transfer and escalation; If the handler fails to respond within the configured timeout period, a timeout escalation will be automatically triggered. The handler will be replaced or added according to the escalation policy, and an escalation notification will be sent to the replaced or added handler.
[0051] The system automatically assigns handlers based on the preset handler rules in the notification template. These rules include assignment by role-based round-robin, assignment based on the lowest current load, or assignment by a specified user. After assignment, the status is set to "triggered," and the assignment time and handler information are recorded. The operator confirms arrival by scanning the QR code at the workstation with a barcode scanner, touching the near-field communication tag, or clicking the arrival button in the mobile terminal application. The system records the arrival time and updates the status to "arrived". If the operator fails to confirm arrival within the preset first timeout period, an escalation will be automatically triggered. The person handling the issue fills in the processing results on the terminal and submits them. The system records the processing completion time and updates the status to "processed". The processing results include the cause of the problem, the repair measures, and the spare parts replacement record. The handler initiates a transfer request through the terminal. The system verifies whether the transfer target has the processing permission for that workstation. If the permission verification is successful, the handler is updated as the transfer target, and the transfer trajectory is recorded. If the permission verification fails, the transfer is rejected and an error message is returned. If the handler fails to confirm their arrival within the first timeout period or fails to complete the processing within the second timeout period, an escalation will be automatically triggered. The escalation strategy includes: advancing step by step according to the preset escalation path, or automatically recommending a replacement handler based on skill matching. After the escalation, an escalation notification will be sent to the new handler, and the escalation history will be recorded. The transition conditions and triggering actions between each state are as follows: The transition from "triggered" to "present": triggered after the handler completes the presence confirmation action; The status changes from "triggered" to "processed": triggered after the processor submits the processing result; The transition from "present" to "processed" is triggered after the processor submits the processing result; The status changes from "triggered" to "upgraded": This will automatically trigger after the first timeout period has elapsed. The transition from "present" to "upgraded" will be automatically triggered after the second timeout period has elapsed. The transition from "triggered" to "transferred" occurs after the handler initiates the transfer and the permission verification is successful. The transition from "present" to "transferred" is triggered after the handler initiates the transfer and the authorization verification is successful. The transition from "Upgraded" to "Attended" is triggered after the new handler completes the attendance confirmation. The transition from "upgraded" to "processed" is triggered after a new processor submits the processing result.
[0052] Upon receiving a notification, the Andon system automatically creates an Andon call record and initiates timeout monitoring. During the trigger phase, an Andon call record is created, its status is set to triggered, it is assigned to a preset handler, and the trigger time is recorded. Upon arrival confirmation, the handler confirms arrival at the site via a terminal, the status is updated to "Arrived," and the response time is recorded. Upon completion, the issue is marked as completed, and the closing time is recorded. Timeout escalation is automatically triggered if the handler fails to respond within the configured timeout period, creating an escalation record, changing or adding handlers according to the escalation strategy, and sending an escalation notification to the new handler. The task transfer function allows handlers to transfer tasks to other personnel, creating a transfer record.
[0053] As an example, the method also includes voice broadcasting processing, specifically including: A standalone audio broadcast server is deployed, and a configuration file is loaded upon startup. The configuration file contains parameters such as playback interval, volume, and speech rate. The audio broadcast server periodically polls and calls the main system application programming interface according to the playback interval to obtain the list of active broadcasts; The audio broadcasting server opens a Hypertext Transfer Protocol interface to receive priority push requests and set a priority playback flag. The audio broadcasting server calls the operating system's speech synthesis engine to convert the notification text into a speech signal and play it; wherein, the English words in the notification text are split letter by letter and played in sequence, the playback is controlled according to the volume and speech rate parameters in the configuration file, and the number of playbacks and the last playback time are recorded. Automatically filter out expired broadcasts and update the broadcast status to complete.
[0054] The audio broadcast server is deployed independently using a Spring Boot architecture. During startup, a configuration file is loaded to set parameters such as playback interval, volume, and speech rate. It periodically polls the main system API to retrieve the list of active broadcasts based on the playback interval. It receives push notifications via an open HTTP interface, accepting priority push requests and setting a priority playback flag. Voice broadcasting utilizes a Windows speech synthesis engine to break down English words letter by letter before broadcasting them, playing them according to the configured volume and speech rate parameters, and recording the number of playbacks and the last broadcast time. Expiration management automatically filters expired broadcasts and updates their status to "completed."
[0055] The English words in the notification text are broken down letter by letter and then read out sequentially, specifically including: Iterate through each character in the notification text. When a continuous sequence of English letters is detected, the sequence is split into characters one by one, and a pause marker of a preset duration is inserted after each split letter. Non-English letter characters remain unchanged and are directly concatenated into the broadcast text. The speech synthesis engine uses the Speech API built into the Windows operating system and is configured in character reading mode, with the speech rate parameter set to 0 (normal speech rate) and the volume parameter set to 80 (80% of the maximum volume percentage).
[0056] Furthermore, as a refinement and extension of the specific implementation of the above embodiments, in order to fully illustrate the specific implementation process in this embodiment, another method is provided. In step S5, the full lifecycle status of the notification includes creation time, sending time, receiving time, and processing time.
[0057] The events that trigger each state transition are: The transition from the created state to the sent state is triggered after the multi-channel unified distribution engine has completed distribution to all channels; The transition from the sent state to the received state is triggered after any channel returns a receipt confirmation. The receipt confirmation includes a system notification front-end read receipt, an email opened receipt, a voice broadcast completed receipt, or an Andon system arrival confirmation receipt. The transition from the received state to the processed state is triggered after the external system returns a processing completion status via the status callback interface. The process can be automatically triggered after a preset archiving time has elapsed, or the archiving operation can be manually triggered by the administrator. The state persistence storage scheme is as follows: notification records are stored in a relational database, the main table stores basic notification information, and the state change history is stored in a separate change log table. Each change record includes the state before the change, the state after the change, the change time, and the operator. The cross-system state synchronization mechanism is as follows: This system acts as the state center and pushes state change events to subscribed external systems through Hypertext Transfer Protocol Webhook or message queue; external systems can also obtain the current state of a specified notification through an active query interface; the state callback interface adopts Hypertext Transfer Protocol POST request, and the request body is in JavaScript object notation format, containing notification identifier, processing status, processing time and processor information; The status statistics and visualization display methods are as follows: a real-time dashboard is provided to display the distribution of notification quantity, average processing time, timeout rate and channel success rate indicators for each status, and supports filtering and chart display by time period, department or notification type.
[0058] In step S5, the system also receives feedback on the processing results from external systems through the status callback interface, and implements notification archiving and cleanup.
[0059] The interaction between external systems and the notification system is achieved through a status callback interface, and the specific process is as follows: The multi-channel unified distribution engine distributes notifications to external systems (such as the Andon system) and simultaneously creates a notification record in this notification system with a status of "sent".
[0060] External system processing tasks: After receiving the notification, the external system executes the corresponding business processing (such as on-site confirmation and problem handling in the Andon system).
[0061] External system call callback interface: When an external system reaches a critical point in the task (such as completion), it calls the callback interface URL provided in advance by this notification system via an HTTP POST request. The request body carries the following parameters: notificationId: Notification ID (a unique identifier passed to external systems when sending a notification); status: Processing status (e.g., "processed"); processedTime: Processing time; processor: processes human information; After receiving the callback request, the notification system finds the corresponding notification record based on the notificationId, updates the notification status to the status reported by the external system (such as "processed"), and records the processing time and the person who processed it.
[0062] Take equipment malfunction notification as an example: This notification system sends a notification to the Andon system with the notification ID NOTIF_20260422_0001 and the content "Please have Engineer Zhang go to Workshop A - Plug-in Workstation to handle equipment malfunction". When sending the notification, this system also passes the notification ID NOTIF_20260422_0001 and the callback interface URL to the Andon system.
[0063] After receiving the notification, the Andon system creates an Andon call record, and the person in charge, Mr. Zhang, arrives on-site to handle the problem.
[0064] After Zhang finished processing the request, he clicked the "Processing Completed" button in the Andon system. The Andon system then sent an HTTP POST request to the callback interface of this notification system, with the following request body: { "notificationId": "NOTIF_20260422_0001", "status": "processed", "processedTime": "2026-04-22 14:30:00", "processor": "Zhang Gong", "remark": "The faulty sensor has been replaced" } After receiving the callback request, the notification system finds the notification record based on the notificationId, updates the status from "sent" to "processed", and records the processing time as 2026-04-22 14:30:00, the processor as "Engineer Zhang", and the processing remarks as "faulty sensor replaced".
[0065] The present invention also provides an intelligent reminder system for the production process. The following are embodiments of the intelligent reminder system for the production process provided in this disclosure. This intelligent reminder system for the production process belongs to the same inventive concept as the intelligent reminder methods for the production process in the above embodiments. For details not described in detail in the embodiments of the intelligent reminder system for the production process, please refer to the embodiments of the intelligent reminder methods for the production process described above.
[0066] The system includes: a notification template configuration module, used to configure and manage notification templates, store template number, template name, notification title, notification content, notification type, notification level, notification method and variable placeholders, and store the configured notification templates to the template library; The notification request receiving module is used to receive notification requests, which include template number, recipient information, notification level code and variable parameters, and to query the corresponding notification template from the template library according to the template number. The content generation module is used to replace the variable placeholders with the variable parameters to generate the final notification content; A multi-channel unified distribution engine is used to concurrently distribute the final notification content to the corresponding channels according to the notification method in the notification template; The notification status management module is used to create notification records and manage the status of notifications throughout their entire lifecycle.
[0067] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
[0068] Any changes, modifications, substitutions, and variations made to the embodiments without departing from the principles and spirit of the present invention still fall within the protection scope of the present invention.
Claims
1. A method for intelligent reminders during the production process, characterized in that, The method includes: Step S1: Configure a notification template, which includes a template number, template name, notification title, notification content, notification type, notification level, notification method, and variable placeholders, and store the configured notification template in the template library; Step S2: Receive a notification request, which includes a template number, recipient information, notification level code, and variable parameters. Query the corresponding notification template from the template library based on the template number. Step S3: Replace the variable placeholders with the variable parameters to generate the final notification content; Step S4: According to the notification method in the notification template, the final notification content is concurrently distributed to the corresponding channels through the multi-channel unified distribution engine; Step S5: Create notification records and manage the full lifecycle status of notifications.
2. The method according to claim 1, characterized in that, In step S1, the notification method includes at least one of the following: System notifications, emails, voice broadcasts, and Andon systems.
3. The method according to claim 2, characterized in that, In step S4, the multi-channel unified distribution engine performs concurrent distribution, specifically including: Parse the target channel set based on the notification method field, and create an independent distribution task for each channel; Each dispatch task is submitted to a thread pool, which uses a configurable core thread count and maximum thread count. If the initial transmission fails, the system will retry according to the exponential backoff strategy. If the retry still fails, the system will select an alternative channel to send a downgrade notification according to the downgrade routing table and record the failure log. The notification method field in the notification template is defined in the form of an ordered list, with channels appearing earlier in the list having higher priority. When a high-priority channel sends successfully and a low-priority channel is configured in serial mode, the low-priority channel skips sending. When a high-priority channel fails to send, the low-priority channel sends normally. Generate a distribution report, which includes the success or failure status of each channel, the sending time, and the number of retries, and write the distribution report to the notification record.
4. The method according to claim 1, characterized in that, In step S2, the recipient information includes a list of recipient IDs and their configuration dimensions; the configuration dimensions include user dimension, role dimension, and department dimension. The user dimension specifies a user ID, and the single user corresponding to that user ID is the recipient. The role dimension specifies the role ID, and all users under that role ID are the recipients. The department dimension specifies the department ID, and all users under that department ID are the recipients.
5. The method according to claim 1, characterized in that, The notification template also includes an access Andon flag, broadcast timeout time, and callback address.
6. The method according to claim 2, characterized in that, The method also includes Andon processing, specifically including: automatically creating an Andon call record and starting timeout monitoring after the final notification content is distributed to the Andon system, covering the status flow of triggering, arrival, processing, transfer and escalation; If the handler fails to respond within the configured timeout period, a timeout escalation will be automatically triggered. The handler will be replaced or added according to the escalation policy, and an escalation notification will be sent to the replaced or added handler.
7. The method according to claim 2, characterized in that, The method also includes voice broadcasting processing, specifically including: A standalone audio broadcast server is deployed, and a configuration file is loaded upon startup. The configuration file contains parameters such as playback interval, volume, and speech rate. The audio broadcast server periodically polls and calls the main system application programming interface according to the playback interval to obtain the list of active broadcasts; The audio broadcasting server opens a Hypertext Transfer Protocol interface to receive priority push requests and set a priority playback flag. The audio broadcasting server calls the operating system's speech synthesis engine to convert the notification text into a speech signal and play it; wherein, the English words in the notification text are split letter by letter and played in sequence, the playback is controlled according to the volume and speech rate parameters in the configuration file, and the number of playbacks and the last playback time are recorded. Automatically filter out expired broadcasts and update the broadcast status to complete.
8. The method according to claim 7, characterized in that, The English words in the notification text are broken down letter by letter and then read out sequentially, specifically including: Iterate through each character in the notification text. When a continuous sequence of English letters is detected, the sequence is split into characters one by one, and a pause marker of a preset duration is inserted after each split letter. Non-English letter characters remain unchanged and are directly concatenated into the broadcast text. The speech synthesis engine uses the Speech API built into the Windows operating system and is configured in character reading mode, with the speech rate parameter set to 0 and the volume parameter set to 80.
9. The method according to claim 1, characterized in that, In step S5, the system also receives feedback on the processing results from external systems through the status callback interface, and implements notification archiving and cleanup.
10. A system applied to the intelligent reminder method for the production process as described in any one of claims 1-9, characterized in that, The system includes: The notification template configuration module is used to configure and manage notification templates, storing template number, template name, notification title, notification content, notification type, notification level, notification method, and variable placeholders, and storing the configured notification templates to the template library; The notification request receiving module is used to receive notification requests, which include template number, recipient information, notification level code and variable parameters, and to query the corresponding notification template from the template library according to the template number. The content generation module is used to replace the variable placeholders with the variable parameters to generate the final notification content; A multi-channel unified distribution engine is used to concurrently distribute the final notification content to the corresponding channels according to the notification method in the notification template; The notification status management module is used to create notification records and manage the status of notifications throughout their entire lifecycle.