system

Abstract

Provide a system. [Solution] means for receiving production information input by a user; means for storing the received production information in a database; a means for managing the progress status of the production; A means to alert designated members when progress status changes; A means to periodically check the planned revision dates of revised items, A means to generate and notify reminder alerts when revisions are approaching; A system including:

Description

[Technical Field]

[0001] The technology of the present disclosure relates to a system. [Background technology]

[0002] Patent document 1 discloses a persona chatbot control method performed by at least one processor, the method including the steps of receiving a user utterance, adding the user utterance to a prompt including an instruction sentence related to a description of the chatbot character, encoding the prompt, and inputting the encoded prompt into a language model to generate a chatbot utterance in response to the user utterance. [Prior art documents] [Patent documents]

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

[0004] In the production of a product, managing each status, such as the number of comps, submission, final proofreading, and final printing, is complicated, which often leads to miscommunication between members and misunderstandings of tasks. Furthermore, for items that require periodic revisions, it is difficult to properly grasp the timing of revisions and proceed with preparations. These issues make it difficult to efficiently manage the progress of production, increasing the risk of project delays and a decline in quality. [Means for solving the problem]

[0005] To solve the above problems, the present invention provides a means for receiving product information entered by a user and saving it in a database. It also provides a means for managing the product progress status and for sending alerts to designated members when the status changes. It also provides a system that includes a means for periodically checking the planned revision date of revision items and generating and sending reminder alerts when the revision is approaching. This configuration enables centralized management of product progress and schedules, achieving efficient project management.

[0006] "User" means a person or entity that accesses the System and inputs and manages information for Works.

[0007] "Product information" is a series of information related to a product, such as the product name, progress status, and responsible members.

[0008] A "database" is a storage device within the system for storing and managing product information, member information, progress status, and the like.

[0009] "Progress status" is information indicating each stage of the production process of a work (e.g., comp, submission, proofreading, final version).

[0010] An "Alert" is a warning or reminder that notifies a Member when a specified event occurs (e.g., a change in progress status, the arrival of a revision).

[0011] A "reminder alert" is a notification that notifies members that the time for revision is approaching for items that require regular revision.

[0012] A "system" is a collection of devices and programs that receive input from users, store it in a database, manage progress status, and generate and notify alerts as necessary.

[0013] "Member" means a person or entity that participates in a Creation Project and receives notifications of progress status changes and alerts.

[0014] "Revision Item" means a Work or part thereof that requires updating or revision at a specific period of time. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a conceptual diagram showing an example of the configuration of a data processing system according to a first embodiment. [Figure 2] 1 is a conceptual diagram showing an example of main functions of a data processing device and a smart device according to a first embodiment. [Figure 3] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a second embodiment. [Figure 4] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and smart glasses according to a second embodiment. [Figure 5] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a third embodiment. [Figure 6] FIG. 11 is a conceptual diagram showing an example of main functions of a data processing device and a headset-type terminal according to a third embodiment. [Figure 7] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a fourth embodiment. [Figure 8] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and a robot according to a fourth embodiment. [Figure 9] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 10] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 11] FIG. 3 is a sequence diagram showing a processing flow of the data processing system according to the first embodiment. [Figure 12] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 1. [Figure 13]FIG. 10 is a sequence diagram showing the flow of processing in the data processing system according to the second embodiment when an emotion engine is combined. [Figure 14] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 2 when an emotion engine is combined. DETAILED DESCRIPTION OF THE INVENTION

[0016] An example of an embodiment of a system according to the technology of the present disclosure will be described below with reference to the accompanying drawings.

[0017] First, the terms used in the following description will be explained.

[0018] In the following embodiments, a coded processor (hereinafter simply referred to as a "processor") may be a single arithmetic device or a combination of multiple arithmetic devices. Furthermore, a processor may be a single type of arithmetic device or a combination of multiple types of arithmetic devices. Examples of arithmetic devices include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a GPGPU (General-Purpose computing on Graphics Processing Units), and an APU (Accelerated Processing Unit).

[0019] In the following embodiments, a coded RAM (Random Access Memory) is a memory in which information is temporarily stored and is used as a working memory by a processor.

[0020] In the following embodiments, the coded storage is one or more non-volatile storage devices that store various programs, various parameters, etc. Examples of non-volatile storage devices include flash memory (SSD (Solid State Drive)), magnetic disks (e.g., hard disks), and magnetic tapes.

[0021] In the following embodiments, a communication I / F (Interface) with a symbol is an interface including a communication processor, an antenna, etc. The communication I / F controls communication between multiple computers. Examples of communication standards applied to the communication I / F include wireless communication standards including 5G (5th Generation Mobile Communication System), Wi-Fi (registered trademark), Bluetooth (registered trademark), etc.

[0022] In the following embodiments, "A and / or B" is synonymous with "at least one of A and B." In other words, "A and / or B" means that it may be only A, only B, or a combination of A and B. Furthermore, in this specification, the same concept as "A and / or B" is also applied when three or more things are expressed connected by "and / or."

[0023] [First embodiment]

[0024] FIG. 1 shows an example of the configuration of a data processing system 10 according to the first embodiment.

[0025] 1, a data processing system 10 includes a data processing device 12 and a smart device 14. An example of the data processing device 12 is a server.

[0026] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0027] The smart device 14 includes a computer 36, a reception device 38, an output device 40, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The reception device 38, the output device 40, and the camera 42 are also connected to the bus 52.

[0028] The reception device 38 includes a touch panel 38A, a microphone 38B, and the like, and receives user input. The touch panel 38A detects contact with an indicator (for example, a pen or a finger) to receive user input by the touch of the indicator. The microphone 38B detects the user's voice to receive user input by voice. The control unit 46A transmits data indicating the user input received by the touch panel 38A and the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the data indicating the user input.

[0029] The output device 40 includes a display 40A and a speaker 40B, and presents data to the user 20 by outputting the data in a form of expression that the user 20 can perceive (for example, audio and / or text). The display 40A displays visible information such as text and images in accordance with instructions from the processor 46. The speaker 40B outputs audio in accordance with instructions from the processor 46. The camera 42 is a compact digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor.

[0030] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54.

[0031] FIG. 2 shows an example of the main functions of the data processing device 12 and the smart device 14.

[0032] 2, in the data processing device 12, a specific process is performed by the processor 28. A specific processing program 56 is stored in the storage 32. The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific process is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0033] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0034] In the smart device 14, the processor 46 performs the reception output process. The storage 50 stores a reception output program 60. The reception output program 60 is used in conjunction with the specific processing program 56 by the data processing system 10. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0035] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0036] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and will be described in detail below.

[0037] User Registration and Authentication

[0038] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[0039] Registration of productions

[0040] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0041] Status updates and management

[0042] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[0043] Alert generation and notification

[0044] If there is a change in the progress status, the server generates an alert for the relevant member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0045] Examples:

[0046] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0047] Reminders for regularly updated items

[0048] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0049] Examples:

[0050] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0051] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are followed. As a result, projects run smoothly without delays. It is also expected to improve communication between members and reduce discrepancies in information.

[0052] The processing flow will be explained below.

[0053] Step 1:

[0054] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[0055] Step 2:

[0056] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[0057] Step 3:

[0058] The user enters the details of the new creation (name, members, initial status, etc.) from the terminal, and the terminal again generates an HTTP POST request to send this information to the server.

[0059] Step 4:

[0060] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[0061] Step 5:

[0062] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[0063] Step 6:

[0064] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[0065] Step 7:

[0066] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[0067] Step 8:

[0068] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[0069] Step 9:

[0070] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[0071] Step 10:

[0072] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[0073] Example 1

[0074] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0075] With conventional progress management systems, managing project progress and regular revision schedules was cumbersome, resulting in project delays and lack of communication between members. Furthermore, the system's security was also vulnerable due to an insufficient user authentication process. To solve these problems, an integrated and efficient progress management and notification system was needed.

[0076] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0077] In this invention, the server includes a means for verifying user authentication information and generating a session authentication token, a means for generating a project ID and saving it together with the product information, and a means for checking the database at regular intervals to update the progress status. This enhances user security while efficiently managing the progress status and periodic revision schedule of the product. Furthermore, it can notify members in real time of changes in the progress status, preventing project delays and lack of communication.

[0078] "User" means any individual or entity that accesses and operates the System.

[0079] "Authentication information" is data for identifying and authenticating a user, and mainly includes a combination of an email address and a password.

[0080] A "session authentication token" is a unique identifier used to maintain a session after a user logs in.

[0081] "Product information" is detailed data about a product registered by a user, including the name, project members, status, and so on.

[0082] A "database" is a digital storage device that structures and stores information about a system.

[0083] A "project ID" is an identifier that uniquely identifies a registered production.

[0084] "Progress status" is an indicator of the progress of a production, and includes states such as "comp complete."

[0085] An "alert" is a message that notifies the user when a specific condition occurs.

[0086] A "reminder alert" is a message that notifies you when a deadline for a recurring task or event is approaching.

[0087] A "terminal" is a device, such as a computer or smartphone, that a user uses to access the system.

[0088] The present invention relates to a system for automatically managing the progress of a product and issuing reminders for periodic revisions. Specific embodiments of the system are described below.

[0089] User Registration and Authentication

[0090] To log in to the system, a user enters their email address and password from their device. The device sends the information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device, allowing the user to access the system.

[0091] Hardware and software used

[0092] Server: AWS (registered trademark) EC2 (cloud server)

[0093] Database: AWS RDS (relational database)

[0094] Device: The PC or smartphone used by the user

[0095] Communication protocol: HTTPS

[0096] Registration of productions

[0097] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0098] Specific examples

[0099] When a user registers "Product A", they enter the name "Product A", members "Member 1, Member 2", and status "Started". The server saves this information and assigns a unique project ID to "Product A".

[0100] Status updates and management

[0101] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0102] Specific examples

[0103] When the number of comps for Product A reaches the specified number, the server updates the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0104] Alert generation and notification

[0105] If there is a change in the progress status, the server generates an alert for the relevant member, and this alert is notified to the user via their device via SMS or push notification.

[0106] Specific examples

[0107] When Product A reaches "comp complete," the server generates an alert stating "Product A comp complete" and notifies the member's device.

[0108] Reminders for regularly updated items

[0109] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0110] Specific examples

[0111] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0112] Examples of prompt statements

[0113] "Please add a setting to notify you when the progress status of Product A changes."

[0114] "Please include a function to generate a reminder three months before the scheduled revision date."

[0115] This system allows users to efficiently manage the progress of projects and schedule regular revisions, and also facilitates smooth communication between project members, reducing discrepancies in information.

[0116] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0117] Step 1: The user enters their email address and password to log in to the system from their terminal. Based on the input (email address and password), the terminal encrypts the information and sends it to the server using HTTPS. Specifically, the terminal encrypts the email address and password and sends them to the server.

[0118] Step 2: The server checks the received information (email address and password) against the authentication information in its database. If the authentication is successful, the server generates an authentication token for the session. This is the process of running a database query to verify that the corresponding user information exists.

[0119] Step 3: The server returns the generated session authentication token to the device. The device receives this authentication token and stores it in a cookie or local storage. This allows the user to access the system. Specifically, the server generates the token and sends it to the device in an HTTP response.

[0120] Step 4: To register a new project, the user enters details (project name, project members, initial status, etc.) into the device. The device sends this information in JSON format to the server. Specifically, the user enters the details into a form on the device and presses the submit button.

[0121] Step 5: The server stores the received product information in its database. Based on the input data, it creates a new product record and generates a unique project ID. Specifically, the server adds a new entry to the database and generates a unique ID, such as a UUID.

[0122] Step 6: The server returns a response including the generated project ID to the terminal, which displays it. As a specific example, the user registers "Product A" and its detailed information is displayed.

[0123] Step 7: The server uses a regular scheduler, such as a cron job, to check the database at regular intervals to monitor changes in the progress status of the work. It updates the status of work that meets certain criteria, such as the number of comps completed. Specifically, the server runs a scheduled job in the background, running database queries.

[0124] Step 8: The server saves the updated status to the database and generates an alert to the relevant member. This alert information is generated in JSON format and sent via AWS SNS or similar. For example, it generates a message saying "The comp for Product A has been completed" and sends it to the member.

[0125] Step 9: The server periodically checks the database and generates a reminder alert three months before the scheduled revision date. It retrieves the scheduled revision date from the database and generates an alert if the condition is met. Specifically, it filters the entries in the database and sends an email or push notification if there is a match.

[0126] Step 10: The server generates a reminder alert and uses AWS SNS to notify registered members. The device receives this notification and displays the alert to the user. For example, this is the operation of notifying project members of the reminder "Start preparation for revising Product B."

[0127] This series of steps allows users to efficiently manage the progress of the project and the schedule for periodic revisions, and also facilitates smooth communication among project members, reducing discrepancies in information.

[0128] (Application example 1)

[0129] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0130] In modern production projects, progress management and regular revision schedule management are extremely important, but the manual work and confirmation work involved requires a great deal of effort and time. In addition, inadequate information updates and reminders can lead to project delays and errors. Factories, in particular, need an efficient way to grasp progress in real time.

[0131] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0132] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of the revised item, means for generating and notifying a reminder alert when the revision is approaching, means for providing information in real time using a display device that can be worn as a terminal, and means for notifying the user when the progress status or reminder alert is displayed on the display device. This makes it possible to efficiently manage the progress status of products in a factory and the periodic revision schedule, and to provide information to workers in real time.

[0133] A "user" is a person or device that accesses the system and provides input or operations.

[0134] "Product information" is data such as detailed product information and status necessary for project progress management.

[0135] A "database" is a storage device within the system that stores and manages production information and progress status.

[0136] "Progress status" is information that indicates the current work status and progress of the product.

[0137] An "alert" is a warning message that notifies designated members when a progress status change or an important event occurs.

[0138] A "reminder alert" is a notification message that is generated as a reminder when the scheduled revision date approaches.

[0139] A "terminal" is a device, such as smart glasses or other wearable display device, that a user uses to access the system.

[0140] A "display device" is a wearable device for displaying information or notifications to a user in real time.

[0141] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and a specific method for implementing this will be described below.

[0142] System configuration

[0143] The system consists of the following main elements:

[0144] 1. User terminal: This refers to a wearable display device such as smart glasses, which allows users to view information in real time.

[0145] 2. Server: Plays a central role in managing the database, updating progress status, and generating alerts.

[0146] 3. Database: A storage device for storing production information and progress status.

[0147] Authentication Process

[0148] Users log in through their smart glasses and enter their credentials, such as email address and password. The server receives this and checks it against a database. If successful, an authentication token is generated for the session, allowing the user to access the system.

[0149] Registration of productions

[0150] The user inputs details such as the name of the project, project members, and initial status from the device. The device sends this information to the server, which stores it in a database. This allows the project to be managed with a specific project ID.

[0151] Progress Updates

[0152] The server periodically checks the database to monitor the progress of the work. For example, if a certain number of comps have been completed, the status is updated to "Comp Completed." This change is then reflected in the database.

[0153] Alert generation and notification

[0154] If there is a change in the progress status, the server generates an alert and notifies the relevant member. The notification is displayed in real time through the smart glasses. For example, a message such as "Product A's comp is complete" is displayed.

[0155] Regular revision reminder

[0156] The server retrieves the planned revision date from the database and periodically checks it. Three months before the planned revision date, a reminder alert is generated to notify project members. The message "Start preparation for revision of Product B" is displayed on the smart glasses.

[0157] Hardware and software used

[0158] Hardware: Smart glasses (e.g., Google® Glass®)

[0159] Software: Django (Python framework), SQLite (database), Celery (task queue)

[0160] Specific examples

[0161] Consider a process where a factory worker wears smart glasses to check the status of their production. By voice-inputting the project ID into the smart glasses, the latest status is displayed. If there is a change in the status, real-time notifications are provided.

[0162] Prompt Sentence Examples

[0163] We will build a system to automate project progress management. It will have functions for user authentication, progress status updates, automatic notifications, and periodic reminders. We are considering an application to be installed on smart glasses used in factories. Please explain, with concrete examples and code, how to use Python and Django to manage project progress and notify workers in real time.

[0164] In this way, the present invention realizes a system for efficiently managing the progress of a product and providing reminders for periodic revisions.

[0165] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0166] Step 1:

[0167] A user logs in to the system through smart glasses. The user enters their email address and password, and the device sends this authentication information to the server. The server compares the authentication information with that in the database, and if successful, generates an authentication token for the session and sends it back to the device. The input is the user's login information, and the output is the authentication token.

[0168] Step 2:

[0169] The user inputs detailed information about the project. The user inputs the project name, project members, initial status, etc. into the terminal through the smart glasses. The terminal sends this information to the server, which stores it in a database. The input is the project details, and the output is the project information stored in the database.

[0170] Step 3:

[0171] The server checks the database at regular intervals to monitor the progress status of the production. For example, when the number of comps reaches a certain number, the server updates the status to "Comp complete." This updated information is also reflected in the database. The input is the progress information in the database, and the output is the updated status.

[0172] Step 4:

[0173] If the server detects a change in the progress status, it generates an alert. The generated alert is sent to the user's device and notified in real time to the user's smart glasses. The input is the changed status, and the output is the generated alert.

[0174] Step 5:

[0175] The server periodically checks the planned revision date of the revised item. When it is three months before the planned revision date, it generates a reminder alert to notify the specified members. The input is the planned revision date information in the database, and the output is the generated reminder alert.

[0176] Step 6:

[0177] The user checks the progress status and reminder alerts through the smart glasses, allowing the user to grasp the progress and revision schedule in real time. The input is alerts and status information, and the output is the user's recognition.

[0178] Step 7:

[0179] The server records the information and progress updates it receives in a database for future checks and notifications. The input is the newly generated information or updates, and the output is the information stored in the database.

[0180] Through the above processing steps, the system can efficiently automate the progress management and revision schedule of productions.

[0181] Furthermore, an emotion engine that estimates the user's emotion may be combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59 and perform identification processing using the user's emotion.

[0182] The present invention relates to a system that automatically manages the progress of a project and issues reminders for periodic revisions, as well as a system that recognizes the user's emotions and adjusts notification content and priority based on those emotions.

[0183] User Registration and Authentication

[0184] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[0185] Registration of productions

[0186] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0187] Status updates and management

[0188] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[0189] Alert generation and notification

[0190] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0191] Examples:

[0192] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0193] Reminders for regularly updated items

[0194] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0195] Examples:

[0196] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0197] Introducing the Emotion Engine

[0198] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0199] Tailoring notification content based on emotions

[0200] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0201] Examples:

[0202] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0203] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are not forgotten. It also recognizes users' emotions in real time and enables flexible responses according to the situation, which is expected to improve work efficiency and strengthen teamwork.

[0204] The processing flow will be explained below.

[0205] Step 1:

[0206] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[0207] Step 2:

[0208] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[0209] Step 3:

[0210] The user enters details of a new creation (such as name, members, and initial status) from the device, which then generates an HTTP POST request to send this information to the server.

[0211] Step 4:

[0212] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[0213] Step 5:

[0214] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[0215] Step 6:

[0216] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[0217] Step 7:

[0218] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[0219] Step 8:

[0220] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[0221] Step 9:

[0222] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[0223] Step 10:

[0224] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[0225] Step 11:

[0226] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0227] Step 12:

[0228] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0229] Step 13:

[0230] Example: If the emotion engine recognizes that a user is under stress, the server will set notifications for that user to "low priority" and send follow-up notifications to other members to reduce the user's burden.

[0231] Example 2

[0232] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0233] While existing production management systems have functions for managing the progress of production and for reminders for periodic revisions, they lack the ability to respond to the user's emotional state. As a result, users can feel stressed or anxious, which can have a negative impact on work efficiency and teamwork. Furthermore, the lack of a mechanism for flexibly adjusting the content and priority of notifications increases the burden on users, which is a problem.

[0234] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[0235] In this invention, the server includes means for receiving production information input by a user, means for saving the received production information in a database, means for monitoring the progress of the production, means for notifying designated members by sending an alert when there is a change in the progress, means for periodically checking the planned revision date of an item to be revised, means for generating and sending a reminder alert when the revision is approaching, means for recognizing the user's emotions, and means for adjusting the notification content and priority based on the recognized emotions. This enables flexible adjustment of the notification content and priority to match the user's emotional state, reducing stress and anxiety and ultimately improving work efficiency and teamwork.

[0236] "Production information" refers to detailed information about a production that a user inputs into the system, such as the name of the production, project members, and initial status.

[0237] A "database" is a storage device and its components for storing and managing information such as production information, progress status, and planned revision dates.

[0238] "Progress status" refers to information or status that indicates the progress of a production, such as "comp complete" or "in progress."

[0239] An "alert" is a notification generated by the system based on changes in progress status or planned revision dates, and notifies users and members of important information.

[0240] "Regular revision" refers to inspections and evaluations that are carried out periodically to ensure the quality and maintain the products.

[0241] A "reminder alert" is a notification generated by the system when the scheduled date for a regular revision approaches, encouraging users and members to prepare for and implement the revision.

[0242] "Emotion" refers to the user's psychological state, and includes, for example, stress, anxiety, satisfaction, and the like.

[0243] An "emotion engine" is a software or hardware configuration that analyzes a user's facial image, voice, and text input in real time to recognize the user's emotions.

[0244] "Notification content" refers to information contained in an alert or reminder alert, and refers to the message or information to be conveyed to the user.

[0245] "Priority" indicates the importance of the notification content or alert, and is an index that sets the urgency or importance of the notification to users or members.

[0246] This invention is a system that not only automatically manages the progress of production and sends reminders for periodic revisions, but also has the function of recognizing the user's emotions and adjusting the content and priority of notifications based on those emotions.

[0247] User Registration and Authentication

[0248] To log in to the system, a user first enters their email address and password from their device. The device sends the entered information to the server, which checks it against the authentication information in the database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system. The hardware required is the user's device (PC, smartphone, etc.), a server, and a database.

[0249] Registration of productions

[0250] To register a new project, a user enters details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID. The required software is a database management system (DBMS) and a web server application.

[0251] Status updates and management

[0252] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0253] Alert generation and notification

[0254] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0255] Specific examples

[0256] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0257] Reminders for regularly updated items

[0258] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0259] Specific examples

[0260] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0261] Introducing the Emotion Engine

[0262] The device captures a picture of the user's face with a camera and analyzes the voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.). Hardware such as a camera and microphone are required, while software such as an emotion analysis engine is required.

[0263] Tailoring notification content based on emotions

[0264] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0265] Specific examples

[0266] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0267] Prompt Sentence Examples

[0268] "The system allows users to manage the progress of their creations and automatically reminds them of regular revision schedules. It also uses an emotion engine to recognize users' emotions and adjust the priority of notifications based on those emotions."

[0269] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0270] Step 1:

[0271] To log in to the system, a user enters their email address and password from their device. The entered information is sent from the device to the server. The server compares the received authentication information with the information in the database, generates an authentication token, and sends it back to the device. This allows the user to access the system.

[0272] Input: Email address, Password

[0273] Output: Authentication token

[0274] Step 2:

[0275] To register a new project, a user inputs its details (project name, project members, initial status, etc.) into the terminal. The input information is sent from the terminal to the server, which stores the received project information in a database and assigns a specific project ID.

[0276] Input: Name of project, project members, initial status

[0277] Output: Project ID

[0278] Step 3:

[0279] The server checks the database at regular intervals to monitor the progress of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp complete." The updated progress is also reflected in the database.

[0280] Input: Product progress information

[0281] Output: Updated progress

[0282] Step 4:

[0283] If there is a change in the progress status, the server generates an alert for the corresponding member. The alert notification is sent to the user via SMS or push notification on the device, allowing members to know the progress status in real time.

[0284] Input: Updated progress

[0285] Output: Alert notification

[0286] Specific behavior:

[0287] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp is complete" is sent to all members participating in the project.

[0288] Step 5:

[0289] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0290] Input: Planned revision date

[0291] Output: Reminder alert

[0292] Specific behavior:

[0293] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for the revision of product B" and notifies the project members.

[0294] Step 6:

[0295] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0296] Input: User's facial image, voice, and text input

[0297] Output: Recognized emotion data

[0298] Step 7:

[0299] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0300] Input: Recognized emotion data

[0301] Output: Adjusted notification content and priority

[0302] Specific behavior:

[0303] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0304] (Application example 2)

[0305] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0306] In manufacturing environments such as factories, tasks such as managing the progress of production and reminders for periodic revisions are diverse and highly complex. It is also important to note that the emotions and mental state of workers on the front lines have a significant impact on work efficiency and quality. However, current systems lack the ability to recognize workers' emotions and adjust notification content and priorities accordingly. A new system is needed to address this shortcoming.

[0307] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0308] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of an item to be revised, means for generating and notifying a reminder alert when the revision is approaching, and means for recognizing the user's emotions and adjusting the content and priority of notifications based on the emotions. This allows for efficient management of the progress status of the product and flexible responses according to the emotional state of the worker.

[0309] "Product information" refers to detailed data about each project or item in the manufacturing process, including the name, members, progress, etc.

[0310] "Progress status" is information that indicates the current stage of a production or project, and serves as a criterion for managing the progress of work.

[0311] A "database" is a system for organizing and storing product information, progress status, user information, and the like.

[0312] An "alert" is a notice or notification sent to a user or member when a specific condition is met.

[0313] A "reminder" is an alert that notifies the user based on a specific date and time or conditions, and prompts the user to take a specific action.

[0314] "User emotion" refers to the emotional state of a person using a system, including psychological states such as stress, anxiety, and satisfaction.

[0315] "Emotion recognition" is a technology that analyzes data such as a user's face, voice, and text to determine the user's emotions.

[0316] The system of the present invention manages the progress of products, provides reminders for periodic revisions, recognizes the emotions of workers, and adjusts notifications based on the emotions in a manufacturing environment such as a factory. A specific embodiment of this system will be described below.

[0317] User Registration and Authentication

[0318] First, a user enters their email address and password on their device to log in to the system. The device sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system.

[0319] Registration of productions

[0320] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0321] Status updates and management

[0322] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0323] Alert generation and notification

[0324] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0325] Reminders for regularly updated items

[0326] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0327] Introducing the Emotion Engine

[0328] The device captures a user's face with a camera and analyzes voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0329] Tailoring notification content based on emotions

[0330] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0331] Examples and software used

[0332] This system uses a programming language based on Python (registered trademark) to realize various functions. It also uses common machine learning models and natural AI tools for emotion recognition. It uses RDBMS such as MySQL (registered trademark) and PostgreSQL for the database, and Firebase Cloud Messaging (FCM) for notification functions.

[0333] For example, if the emotion engine recognizes that a user is under stress, the server will set notifications to that user as "low priority" and send follow-up notifications to other members to reduce the user's burden.

[0334] Examples of prompt statements

[0335] Examples of prompts that can be given to a generative AI model include:

[0336] "I want to create an application that recognizes user emotions and manages project progress. Please add a feature that adjusts notification content and priority based on emotion data. Please output Python code that registers new projects, updates progress status, and generates alerts based on emotions."

[0337] This makes it possible to realize a flexible progress management system that takes into account the user's emotions.

[0338] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0339] Step 1:

[0340] A user enters their email address and password on a terminal and sends a login request to the server. The server checks the input information against the authentication information in the database, and if authentication is successful, generates an authentication token for the session and returns it to the terminal. This authentication token allows the user to access the system.

[0341] Input: User's email address, password

[0342] Data processing: The server checks the authentication information against the database

[0343] Output: Authentication token for the session

[0344] Step 2:

[0345] To register a new project, a user inputs details such as the project name, project members, and initial status into a terminal and sends them to the server, which stores the received information in a database and manages the project with a specific project ID.

[0346] Input: Name of the project, project members, initial status

[0347] Data processing: The server stores the information in a database

[0348] Output: Specific project ID

[0349] Step 3:

[0350] The server checks the database at regular intervals to monitor changes in the progress status of the work. When the progress status is updated, the new status information is updated in the database. At this time, if a specified number of comps have been completed, for example, the status is updated to "Comp complete."

[0351] Input: Contents of the production database

[0352] Data processing: The server periodically checks the database and updates the status information

[0353] Output: Updated status information

[0354] Step 4:

[0355] When there is a change in the progress status, the server generates an alert for the corresponding project member, and this alert is sent to the device via SMS or push notification to notify the user.

[0356] Input: Updated status information

[0357] Data processing: Server generates alerts and sends notifications

[0358] Output: Notification to users and members

[0359] Step 5:

[0360] For items that require periodic revision, the server retrieves the planned revision date from the database and checks whether the date is approaching. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0361] Input: Database contents of revised items

[0362] Data processing: The server checks the scheduled revision date and generates a reminder

[0363] Output: Reminder alert and notification to user

[0364] Step 6:

[0365] The device captures the user's face with a camera and captures voice and text input, which is then analyzed by an emotion engine to recognize the user's emotional state (stress, anxiety, satisfaction, etc.).

[0366] Input: User's face image, voice, text input

[0367] Data processing: Emotion engine analyzes emotional data

[0368] Output: Recognized emotion data

[0369] Step 7:

[0370] The server receives the emotion data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user's emotion is recognized as stress, the server lowers the urgency of the notification and reduces the notification frequency.

[0371] Input: Emotion data provided by the emotion engine

[0372] Data processing: The server adjusts the notification content and priority

[0373] Output: Adjusted alert notification

[0374] The specific processing unit 290 transmits the result of the specific processing to the smart device 14. In the smart device 14, the control unit 46A causes the output device 40 to output the result of the specific processing. The microphone 38B acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0375] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (registered trademark) (Internet search engine).<URL: https: / / openai.com / blog / chatgpt> ), Gemini (registered trademark) (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0376] In the above embodiment, an example in which the specific process is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific process may be performed by the smart device 14.

[0377] [Second embodiment]

[0378] FIG. 3 shows an example of the configuration of a data processing system 210 according to the second embodiment.

[0379] 3, the data processing system 210 includes the data processing device 12 and smart glasses 214. An example of the data processing device 12 is a server.

[0380] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0381] The smart glasses 214 include a computer 36, a microphone 238, a speaker 240, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, and the camera 42 are also connected to the bus 52.

[0382] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0383] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0384] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0385] Fig. 4 shows an example of the main functions of the data processing device 12 and the smart glasses 214. As shown in Fig. 4, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0386] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0387] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0388] In the smart glasses 214, the reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0389] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the smart glasses 214 will be referred to as the "terminal."

[0390] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and will be described in detail below.

[0391] User Registration and Authentication

[0392] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[0393] Registration of productions

[0394] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0395] Status updates and management

[0396] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[0397] Alert generation and notification

[0398] If there is a change in the progress status, the server generates an alert for the relevant member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0399] Examples:

[0400] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0401] Reminders for regularly updated items

[0402] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0403] Examples:

[0404] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0405] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are followed. As a result, projects run smoothly without delays. It is also expected to improve communication between members and reduce discrepancies in information.

[0406] The processing flow will be explained below.

[0407] Step 1:

[0408] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[0409] Step 2:

[0410] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[0411] Step 3:

[0412] The user enters the details of the new creation (name, members, initial status, etc.) from the terminal, and the terminal again generates an HTTP POST request to send this information to the server.

[0413] Step 4:

[0414] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[0415] Step 5:

[0416] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[0417] Step 6:

[0418] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[0419] Step 7:

[0420] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[0421] Step 8:

[0422] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[0423] Step 9:

[0424] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[0425] Step 10:

[0426] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[0427] Example 1

[0428] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0429] With conventional progress management systems, managing project progress and regular revision schedules was cumbersome, resulting in project delays and lack of communication between members. Furthermore, the system's security was also vulnerable due to an insufficient user authentication process. To solve these problems, an integrated and efficient progress management and notification system was needed.

[0430] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0431] In this invention, the server includes a means for verifying user authentication information and generating a session authentication token, a means for generating a project ID and saving it together with the product information, and a means for checking the database at regular intervals to update the progress status. This enhances user security while efficiently managing the progress status and periodic revision schedule of the product. Furthermore, it can notify members in real time of changes in the progress status, preventing project delays and lack of communication.

[0432] "User" means any individual or entity that accesses and operates the System.

[0433] "Authentication information" is data for identifying and authenticating a user, and mainly includes a combination of an email address and a password.

[0434] A "session authentication token" is a unique identifier used to maintain a session after a user logs in.

[0435] "Product information" is detailed data about a product registered by a user, including the name, project members, status, and so on.

[0436] A "database" is a digital storage device that structures and stores information about a system.

[0437] A "project ID" is an identifier that uniquely identifies a registered production.

[0438] "Progress status" is an indicator of the progress of a production, and includes states such as "comp complete."

[0439] An "alert" is a message that notifies the user when a specific condition occurs.

[0440] A "reminder alert" is a message that notifies you when a deadline for a recurring task or event is approaching.

[0441] A "terminal" is a device, such as a computer or smartphone, that a user uses to access the system.

[0442] The present invention relates to a system for automatically managing the progress of a product and issuing reminders for periodic revisions. Specific embodiments of the system are described below.

[0443] User Registration and Authentication

[0444] To log in to the system, a user enters their email address and password from their device. The device sends the information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device, allowing the user to access the system.

[0445] Hardware and software used

[0446] Server: AWS EC2 (cloud server)

[0447] Database: AWS RDS (relational database)

[0448] Device: The PC or smartphone used by the user

[0449] Communication protocol: HTTPS

[0450] Registration of productions

[0451] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0452] Specific examples

[0453] When a user registers "Product A", they enter the name "Product A", members "Member 1, Member 2", and status "Started". The server saves this information and assigns a unique project ID to "Product A".

[0454] Status updates and management

[0455] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0456] Specific examples

[0457] When the number of comps for Product A reaches the specified number, the server updates the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0458] Alert generation and notification

[0459] If there is a change in the progress status, the server generates an alert for the relevant member, and this alert is notified to the user via their device via SMS or push notification.

[0460] Specific examples

[0461] When Product A reaches "comp complete," the server generates an alert stating "Product A comp complete" and notifies the member's device.

[0462] Reminders for regularly updated items

[0463] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0464] Specific examples

[0465] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0466] Examples of prompt statements

[0467] "Please add a setting to notify you when the progress status of Product A changes."

[0468] "Please include a function to generate a reminder three months before the scheduled revision date."

[0469] This system allows users to efficiently manage the progress of projects and schedule regular revisions, and also facilitates smooth communication between project members, reducing discrepancies in information.

[0470] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0471] Step 1: The user enters their email address and password to log in to the system from their terminal. Based on the input (email address and password), the terminal encrypts the information and sends it to the server using HTTPS. Specifically, the terminal encrypts the email address and password and sends them to the server.

[0472] Step 2: The server checks the received information (email address and password) against the authentication information in its database. If the authentication is successful, the server generates an authentication token for the session. This is the process of running a database query to verify that the corresponding user information exists.

[0473] Step 3: The server returns the generated session authentication token to the device. The device receives this authentication token and stores it in a cookie or local storage. This allows the user to access the system. Specifically, the server generates the token and sends it to the device in an HTTP response.

[0474] Step 4: To register a new project, the user enters details (project name, project members, initial status, etc.) into the device. The device sends this information in JSON format to the server. Specifically, the user enters the details into a form on the device and presses the submit button.

[0475] Step 5: The server stores the received product information in its database. Based on the input data, it creates a new product record and generates a unique project ID. Specifically, the server adds a new entry to the database and generates a unique ID, such as a UUID.

[0476] Step 6: The server returns a response including the generated project ID to the terminal, which displays it. As a specific example, the user registers "Product A" and its detailed information is displayed.

[0477] Step 7: The server uses a regular scheduler, such as a cron job, to check the database at regular intervals to monitor changes in the progress status of the work. It updates the status of work that meets certain criteria, such as the number of comps completed. Specifically, the server runs a scheduled job in the background, running database queries.

[0478] Step 8: The server saves the updated status to the database and generates an alert to the relevant member. This alert information is generated in JSON format and sent via AWS SNS or similar. For example, it generates a message saying "The comp for Product A has been completed" and sends it to the member.

[0479] Step 9: The server periodically checks the database and generates a reminder alert three months before the scheduled revision date. It retrieves the scheduled revision date from the database and generates an alert if the condition is met. Specifically, it filters the entries in the database and sends an email or push notification if there is a match.

[0480] Step 10: The server generates a reminder alert and uses AWS SNS to notify registered members. The device receives this notification and displays the alert to the user. For example, this is the operation of notifying project members of the reminder "Start preparation for revising Product B."

[0481] This series of steps allows users to efficiently manage the progress of the project and the schedule for periodic revisions, and also facilitates smooth communication among project members, reducing discrepancies in information.

[0482] (Application example 1)

[0483] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0484] In modern production projects, progress management and regular revision schedule management are extremely important, but the manual work and confirmation work involved requires a great deal of effort and time. In addition, inadequate information updates and reminders can lead to project delays and errors. Factories, in particular, need an efficient way to grasp progress in real time.

[0485] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0486] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of the revised item, means for generating and notifying a reminder alert when the revision is approaching, means for providing information in real time using a display device that can be worn as a terminal, and means for notifying the user when the progress status or reminder alert is displayed on the display device. This makes it possible to efficiently manage the progress status of products in a factory and the periodic revision schedule, and to provide information to workers in real time.

[0487] A "user" is a person or device that accesses the system and provides input or operations.

[0488] "Product information" is data such as detailed product information and status necessary for project progress management.

[0489] A "database" is a storage device within the system that stores and manages production information and progress status.

[0490] "Progress status" is information that indicates the current work status and progress of the product.

[0491] An "alert" is a warning message that notifies designated members when a progress status change or an important event occurs.

[0492] A "reminder alert" is a notification message that is generated as a reminder when the scheduled revision date approaches.

[0493] A "terminal" is a device, such as smart glasses or other wearable display device, that a user uses to access the system.

[0494] A "display device" is a wearable device for displaying information or notifications to a user in real time.

[0495] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and a specific method for implementing this will be described below.

[0496] System configuration

[0497] The system consists of the following main elements:

[0498] 1. User terminal: This refers to a wearable display device such as smart glasses, which allows users to view information in real time.

[0499] 2. Server: Plays a central role in managing the database, updating progress status, and generating alerts.

[0500] 3. Database: A storage device for storing production information and progress status.

[0501] Authentication Process

[0502] Users log in through their smart glasses and enter their credentials, such as email address and password. The server receives this and checks it against a database. If successful, an authentication token is generated for the session, allowing the user to access the system.

[0503] Registration of productions

[0504] The user inputs details such as the name of the project, project members, and initial status from the device. The device sends this information to the server, which stores it in a database. This allows the project to be managed with a specific project ID.

[0505] Progress Updates

[0506] The server periodically checks the database to monitor the progress of the work. For example, if a certain number of comps have been completed, the status is updated to "Comp Completed." This change is then reflected in the database.

[0507] Alert generation and notification

[0508] If there is a change in the progress status, the server generates an alert and notifies the relevant member. The notification is displayed in real time through the smart glasses. For example, a message such as "Product A's comp is complete" is displayed.

[0509] Regular revision reminder

[0510] The server retrieves the planned revision date from the database and periodically checks it. Three months before the planned revision date, a reminder alert is generated to notify project members. The message "Start preparation for revision of Product B" is displayed on the smart glasses.

[0511] Hardware and software used

[0512] Hardware: Smart glasses (e.g., Google Glass)

[0513] Software: Django (Python framework), SQLite (database), Celery (task queue)

[0514] Specific examples

[0515] Consider a process where a factory worker wears smart glasses to check the status of their production. By voice-inputting the project ID into the smart glasses, the latest status is displayed. If there is a change in the status, real-time notifications are provided.

[0516] Prompt Sentence Examples

[0517] We will build a system to automate project progress management. It will have functions for user authentication, progress status updates, automatic notifications, and periodic reminders. We are considering an application to be installed on smart glasses used in factories. Please explain, with concrete examples and code, how to use Python and Django to manage project progress and notify workers in real time.

[0518] In this way, the present invention realizes a system for efficiently managing the progress of a product and providing reminders for periodic revisions.

[0519] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0520] Step 1:

[0521] A user logs in to the system through smart glasses. The user enters their email address and password, and the device sends this authentication information to the server. The server compares the authentication information with that in the database, and if successful, generates an authentication token for the session and sends it back to the device. The input is the user's login information, and the output is the authentication token.

[0522] Step 2:

[0523] The user inputs detailed information about the project. The user inputs the project name, project members, initial status, etc. into the terminal through the smart glasses. The terminal sends this information to the server, which stores it in a database. The input is the project details, and the output is the project information stored in the database.

[0524] Step 3:

[0525] The server checks the database at regular intervals to monitor the progress status of the production. For example, when the number of comps reaches a certain number, the server updates the status to "Comp complete." This updated information is also reflected in the database. The input is the progress information in the database, and the output is the updated status.

[0526] Step 4:

[0527] If the server detects a change in the progress status, it generates an alert. The generated alert is sent to the user's device and notified in real time to the user's smart glasses. The input is the changed status, and the output is the generated alert.

[0528] Step 5:

[0529] The server periodically checks the planned revision date of the revised item. When it is three months before the planned revision date, it generates a reminder alert to notify the specified members. The input is the planned revision date information in the database, and the output is the generated reminder alert.

[0530] Step 6:

[0531] The user checks the progress status and reminder alerts through the smart glasses, allowing the user to grasp the progress and revision schedule in real time. The input is alerts and status information, and the output is the user's recognition.

[0532] Step 7:

[0533] The server records the information and progress updates it receives in a database for future checks and notifications. The input is the newly generated information or updates, and the output is the information stored in the database.

[0534] Through the above processing steps, the system can efficiently automate the progress management and revision schedule of productions.

[0535] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[0536] The present invention relates to a system that automatically manages the progress of a project and issues reminders for periodic revisions, as well as a system that recognizes the user's emotions and adjusts notification content and priority based on those emotions.

[0537] User Registration and Authentication

[0538] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[0539] Registration of productions

[0540] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0541] Status updates and management

[0542] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[0543] Alert generation and notification

[0544] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0545] Examples:

[0546] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0547] Reminders for regularly updated items

[0548] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0549] Examples:

[0550] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0551] Introducing the Emotion Engine

[0552] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0553] Tailoring notification content based on emotions

[0554] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0555] Examples:

[0556] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0557] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are not forgotten. It also recognizes users' emotions in real time and enables flexible responses according to the situation, which is expected to improve work efficiency and strengthen teamwork.

[0558] The processing flow will be explained below.

[0559] Step 1:

[0560] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[0561] Step 2:

[0562] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[0563] Step 3:

[0564] The user enters details of a new creation (such as name, members, and initial status) from the device, which then generates an HTTP POST request to send this information to the server.

[0565] Step 4:

[0566] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[0567] Step 5:

[0568] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[0569] Step 6:

[0570] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[0571] Step 7:

[0572] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[0573] Step 8:

[0574] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[0575] Step 9:

[0576] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[0577] Step 10:

[0578] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[0579] Step 11:

[0580] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0581] Step 12:

[0582] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0583] Step 13:

[0584] Example: If the emotion engine recognizes that a user is under stress, the server will set notifications for that user to "low priority" and send follow-up notifications to other members to reduce the user's burden.

[0585] Example 2

[0586] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0587] While existing production management systems have functions for managing the progress of production and for reminders for periodic revisions, they lack the ability to respond to the user's emotional state. As a result, users can feel stressed or anxious, which can have a negative impact on work efficiency and teamwork. Furthermore, the lack of a mechanism for flexibly adjusting the content and priority of notifications increases the burden on users, which is a problem.

[0588] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[0589] In this invention, the server includes means for receiving production information input by a user, means for saving the received production information in a database, means for monitoring the progress of the production, means for notifying designated members by sending an alert when there is a change in the progress, means for periodically checking the planned revision date of an item to be revised, means for generating and sending a reminder alert when the revision is approaching, means for recognizing the user's emotions, and means for adjusting the notification content and priority based on the recognized emotions. This enables flexible adjustment of the notification content and priority to match the user's emotional state, reducing stress and anxiety and ultimately improving work efficiency and teamwork.

[0590] "Production information" refers to detailed information about a production that a user inputs into the system, such as the name of the production, project members, and initial status.

[0591] A "database" is a storage device and its components for storing and managing information such as production information, progress status, and planned revision dates.

[0592] "Progress status" refers to information or status that indicates the progress of a production, such as "comp complete" or "in progress."

[0593] An "alert" is a notification generated by the system based on changes in progress status or planned revision dates, and notifies users and members of important information.

[0594] "Regular revision" refers to inspections and evaluations that are carried out periodically to ensure the quality and maintain the products.

[0595] A "reminder alert" is a notification generated by the system when the scheduled date for a regular revision approaches, encouraging users and members to prepare for and implement the revision.

[0596] "Emotion" refers to the user's psychological state, and includes, for example, stress, anxiety, satisfaction, and the like.

[0597] An "emotion engine" is a software or hardware configuration that analyzes a user's facial image, voice, and text input in real time to recognize the user's emotions.

[0598] "Notification content" refers to information contained in an alert or reminder alert, and refers to the message or information to be conveyed to the user.

[0599] "Priority" indicates the importance of the notification content or alert, and is an index that sets the urgency or importance of the notification to users or members.

[0600] This invention is a system that not only automatically manages the progress of production and sends reminders for periodic revisions, but also has the function of recognizing the user's emotions and adjusting the content and priority of notifications based on those emotions.

[0601] User Registration and Authentication

[0602] To log in to the system, a user first enters their email address and password from their device. The device sends the entered information to the server, which checks it against the authentication information in the database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system. The hardware required is the user's device (PC, smartphone, etc.), a server, and a database.

[0603] Registration of productions

[0604] To register a new project, a user enters details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID. The required software is a database management system (DBMS) and a web server application.

[0605] Status updates and management

[0606] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0607] Alert generation and notification

[0608] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0609] Specific examples

[0610] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0611] Reminders for regularly updated items

[0612] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0613] Specific examples

[0614] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0615] Introducing the Emotion Engine

[0616] The device captures a picture of the user's face with a camera and analyzes the voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.). Hardware such as a camera and microphone are required, while software such as an emotion analysis engine is required.

[0617] Tailoring notification content based on emotions

[0618] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0619] Specific examples

[0620] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0621] Prompt Sentence Examples

[0622] "The system allows users to manage the progress of their creations and automatically reminds them of regular revision schedules. It also uses an emotion engine to recognize users' emotions and adjust the priority of notifications based on those emotions."

[0623] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0624] Step 1:

[0625] To log in to the system, a user enters their email address and password from their device. The entered information is sent from the device to the server. The server compares the received authentication information with the information in the database, generates an authentication token, and sends it back to the device. This allows the user to access the system.

[0626] Input: Email address, Password

[0627] Output: Authentication token

[0628] Step 2:

[0629] To register a new project, a user inputs its details (project name, project members, initial status, etc.) into the terminal. The input information is sent from the terminal to the server, which stores the received project information in a database and assigns a specific project ID.

[0630] Input: Name of project, project members, initial status

[0631] Output: Project ID

[0632] Step 3:

[0633] The server checks the database at regular intervals to monitor the progress of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp complete." The updated progress is also reflected in the database.

[0634] Input: Product progress information

[0635] Output: Updated progress

[0636] Step 4:

[0637] If there is a change in the progress status, the server generates an alert for the corresponding member. The alert notification is sent to the user via SMS or push notification on the device, allowing members to know the progress status in real time.

[0638] Input: Updated progress

[0639] Output: Alert notification

[0640] Specific behavior:

[0641] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp is complete" is sent to all members participating in the project.

[0642] Step 5:

[0643] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0644] Input: Planned revision date

[0645] Output: Reminder alert

[0646] Specific behavior:

[0647] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for the revision of product B" and notifies the project members.

[0648] Step 6:

[0649] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0650] Input: User's facial image, voice, and text input

[0651] Output: Recognized emotion data

[0652] Step 7:

[0653] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0654] Input: Recognized emotion data

[0655] Output: Adjusted notification content and priority

[0656] Specific behavior:

[0657] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0658] (Application example 2)

[0659] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0660] In manufacturing environments such as factories, tasks such as managing the progress of production and reminders for periodic revisions are diverse and highly complex. It is also important to note that the emotions and mental state of workers on the front lines have a significant impact on work efficiency and quality. However, current systems lack the ability to recognize workers' emotions and adjust notification content and priorities accordingly. A new system is needed to address this shortcoming.

[0661] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0662] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of an item to be revised, means for generating and notifying a reminder alert when the revision is approaching, and means for recognizing the user's emotions and adjusting the content and priority of notifications based on the emotions. This allows for efficient management of the progress status of the product and flexible responses according to the emotional state of the worker.

[0663] "Product information" refers to detailed data about each project or item in the manufacturing process, including the name, members, progress, etc.

[0664] "Progress status" is information that indicates the current stage of a production or project, and serves as a criterion for managing the progress of work.

[0665] A "database" is a system for organizing and storing product information, progress status, user information, and the like.

[0666] An "alert" is a notice or notification sent to a user or member when a specific condition is met.

[0667] A "reminder" is an alert that notifies the user based on a specific date and time or conditions, and prompts the user to take a specific action.

[0668] "User emotion" refers to the emotional state of a person using a system, including psychological states such as stress, anxiety, and satisfaction.

[0669] "Emotion recognition" is a technology that analyzes data such as a user's face, voice, and text to determine the user's emotions.

[0670] The system of the present invention manages the progress of products, provides reminders for periodic revisions, recognizes the emotions of workers, and adjusts notifications based on the emotions in a manufacturing environment such as a factory. A specific embodiment of this system will be described below.

[0671] User Registration and Authentication

[0672] First, a user enters their email address and password on their device to log in to the system. The device sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system.

[0673] Registration of productions

[0674] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0675] Status updates and management

[0676] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0677] Alert generation and notification

[0678] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0679] Reminders for regularly updated items

[0680] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0681] Introducing the Emotion Engine

[0682] The device captures a user's face with a camera and analyzes voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0683] Tailoring notification content based on emotions

[0684] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0685] Examples and software used

[0686] This system uses a Python-based programming language to realize various functions. It also uses common machine learning models and natural AI tools for emotion recognition. It uses RDBMS such as MySQL or PostgreSQL for the database, and Firebase Cloud Messaging (FCM) for notification functions.

[0687] For example, if the emotion engine recognizes that a user is under stress, the server will set notifications to that user as "low priority" and send follow-up notifications to other members to reduce the user's burden.

[0688] Examples of prompt statements

[0689] Examples of prompts that can be given to a generative AI model include:

[0690] "I want to create an application that recognizes user emotions and manages project progress. Please add a feature that adjusts notification content and priority based on emotion data. Please output Python code that registers new projects, updates progress status, and generates alerts based on emotions."

[0691] This makes it possible to realize a flexible progress management system that takes into account the user's emotions.

[0692] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0693] Step 1:

[0694] A user enters their email address and password on a terminal and sends a login request to the server. The server checks the input information against the authentication information in the database, and if authentication is successful, generates an authentication token for the session and returns it to the terminal. This authentication token allows the user to access the system.

[0695] Input: User's email address, password

[0696] Data processing: The server checks the authentication information against the database

[0697] Output: Authentication token for the session

[0698] Step 2:

[0699] To register a new project, a user inputs details such as the project name, project members, and initial status into a terminal and sends them to the server, which stores the received information in a database and manages the project with a specific project ID.

[0700] Input: Name of the project, project members, initial status

[0701] Data processing: The server stores the information in a database

[0702] Output: Specific project ID

[0703] Step 3:

[0704] The server checks the database at regular intervals to monitor changes in the progress status of the work. When the progress status is updated, the new status information is updated in the database. At this time, if a specified number of comps have been completed, for example, the status is updated to "Comp complete."

[0705] Input: Contents of the production database

[0706] Data processing: The server periodically checks the database and updates the status information

[0707] Output: Updated status information

[0708] Step 4:

[0709] When there is a change in the progress status, the server generates an alert for the corresponding project member, and this alert is sent to the device via SMS or push notification to notify the user.

[0710] Input: Updated status information

[0711] Data processing: Server generates alerts and sends notifications

[0712] Output: Notification to users and members

[0713] Step 5:

[0714] For items that require periodic revision, the server retrieves the planned revision date from the database and checks whether the date is approaching. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0715] Input: Database contents of revised items

[0716] Data processing: The server checks the scheduled revision date and generates a reminder

[0717] Output: Reminder alert and notification to user

[0718] Step 6:

[0719] The device captures the user's face with a camera and captures voice and text input, which is then analyzed by an emotion engine to recognize the user's emotional state (stress, anxiety, satisfaction, etc.).

[0720] Input: User's face image, voice, text input

[0721] Data processing: Emotion engine analyzes emotional data

[0722] Output: Recognized emotion data

[0723] Step 7:

[0724] The server receives the emotion data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user's emotion is recognized as stress, the server lowers the urgency of the notification and reduces the notification frequency.

[0725] Input: Emotion data provided by the emotion engine

[0726] Data processing: The server adjusts the notification content and priority

[0727] Output: Adjusted alert notification

[0728] The specific processing unit 290 transmits the result of the specific processing to the smart glasses 214. In the smart glasses 214, the control unit 46A causes the speaker 240 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0729] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0730] In the above embodiment, an example in which the specific processing is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the smart glasses 214.

[0731] [Third embodiment]

[0732] FIG. 5 shows an example of the configuration of a data processing system 310 according to the third embodiment.

[0733] 5, the data processing system 310 includes the data processing device 12 and a headset type terminal 314. An example of the data processing device 12 is a server.

[0734] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0735] The headset type terminal 314 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a display 343. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the display 343 are also connected to the bus 52.

[0736] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0737] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0738] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0739] Fig. 6 shows an example of the main functions of the data processing device 12 and the headset type terminal 314. As shown in Fig. 6, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0740] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0741] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0742] In the headset type terminal 314, a reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0743] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the headset type terminal 314 will be referred to as the "terminal."

[0744] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and will be described in detail below.

[0745] User Registration and Authentication

[0746] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[0747] Registration of productions

[0748] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0749] Status updates and management

[0750] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[0751] Alert generation and notification

[0752] If there is a change in the progress status, the server generates an alert for the relevant member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0753] Examples:

[0754] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0755] Reminders for regularly updated items

[0756] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0757] Examples:

[0758] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0759] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are followed. As a result, projects run smoothly without delays. It is also expected to improve communication between members and reduce discrepancies in information.

[0760] The processing flow will be explained below.

[0761] Step 1:

[0762] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[0763] Step 2:

[0764] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[0765] Step 3:

[0766] The user enters the details of the new creation (name, members, initial status, etc.) from the terminal, and the terminal again generates an HTTP POST request to send this information to the server.

[0767] Step 4:

[0768] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[0769] Step 5:

[0770] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[0771] Step 6:

[0772] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[0773] Step 7:

[0774] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[0775] Step 8:

[0776] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[0777] Step 9:

[0778] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[0779] Step 10:

[0780] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[0781] Example 1

[0782] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[0783] With conventional progress management systems, managing project progress and regular revision schedules was cumbersome, resulting in project delays and lack of communication between members. Furthermore, the system's security was also vulnerable due to an insufficient user authentication process. To solve these problems, an integrated and efficient progress management and notification system was needed.

[0784] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0785] In this invention, the server includes a means for verifying user authentication information and generating a session authentication token, a means for generating a project ID and saving it together with the product information, and a means for checking the database at regular intervals to update the progress status. This enhances user security while efficiently managing the progress status and periodic revision schedule of the product. Furthermore, it can notify members in real time of changes in the progress status, preventing project delays and lack of communication.

[0786] "User" means any individual or entity that accesses and operates the System.

[0787] "Authentication information" is data for identifying and authenticating a user, and mainly includes a combination of an email address and a password.

[0788] A "session authentication token" is a unique identifier used to maintain a session after a user logs in.

[0789] "Product information" is detailed data about a product registered by a user, including the name, project members, status, and so on.

[0790] A "database" is a digital storage device that structures and stores information about a system.

[0791] A "project ID" is an identifier that uniquely identifies a registered production.

[0792] "Progress status" is an indicator of the progress of a production, and includes states such as "comp complete."

[0793] An "alert" is a message that notifies the user when a specific condition occurs.

[0794] A "reminder alert" is a message that notifies you when a deadline for a recurring task or event is approaching.

[0795] A "terminal" is a device, such as a computer or smartphone, that a user uses to access the system.

[0796] The present invention relates to a system for automatically managing the progress of a product and issuing reminders for periodic revisions. Specific embodiments of the system are described below.

[0797] User Registration and Authentication

[0798] To log in to the system, a user enters their email address and password from their device. The device sends the information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device, allowing the user to access the system.

[0799] Hardware and software used

[0800] Server: AWS EC2 (cloud server)

[0801] Database: AWS RDS (relational database)

[0802] Device: The PC or smartphone used by the user

[0803] Communication protocol: HTTPS

[0804] Registration of productions

[0805] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0806] Specific examples

[0807] When a user registers "Product A", they enter the name "Product A", members "Member 1, Member 2", and status "Started". The server saves this information and assigns a unique project ID to "Product A".

[0808] Status updates and management

[0809] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0810] Specific examples

[0811] When the number of comps for Product A reaches the specified number, the server updates the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0812] Alert generation and notification

[0813] If there is a change in the progress status, the server generates an alert for the relevant member, and this alert is notified to the user via their device via SMS or push notification.

[0814] Specific examples

[0815] When Product A reaches "comp complete," the server generates an alert stating "Product A comp complete" and notifies the member's device.

[0816] Reminders for regularly updated items

[0817] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0818] Specific examples

[0819] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0820] Examples of prompt statements

[0821] "Please add a setting to notify you when the progress status of Product A changes."

[0822] "Please include a function to generate a reminder three months before the scheduled revision date."

[0823] This system allows users to efficiently manage the progress of projects and schedule regular revisions, and also facilitates smooth communication between project members, reducing discrepancies in information.

[0824] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0825] Step 1: The user enters their email address and password to log in to the system from their terminal. Based on the input (email address and password), the terminal encrypts the information and sends it to the server using HTTPS. Specifically, the terminal encrypts the email address and password and sends them to the server.

[0826] Step 2: The server checks the received information (email address and password) against the authentication information in its database. If the authentication is successful, the server generates an authentication token for the session. This is the process of running a database query to verify that the corresponding user information exists.

[0827] Step 3: The server returns the generated session authentication token to the device. The device receives this authentication token and stores it in a cookie or local storage. This allows the user to access the system. Specifically, the server generates the token and sends it to the device in an HTTP response.

[0828] Step 4: To register a new project, the user enters details (project name, project members, initial status, etc.) into the device. The device sends this information in JSON format to the server. Specifically, the user enters the details into a form on the device and presses the submit button.

[0829] Step 5: The server stores the received product information in its database. Based on the input data, it creates a new product record and generates a unique project ID. Specifically, the server adds a new entry to the database and generates a unique ID, such as a UUID.

[0830] Step 6: The server returns a response including the generated project ID to the terminal, which displays it. As a specific example, the user registers "Product A" and its detailed information is displayed.

[0831] Step 7: The server uses a regular scheduler, such as a cron job, to check the database at regular intervals to monitor changes in the progress status of the work. It updates the status of work that meets certain criteria, such as the number of comps completed. Specifically, the server runs a scheduled job in the background, running database queries.

[0832] Step 8: The server saves the updated status to the database and generates an alert to the relevant member. This alert information is generated in JSON format and sent via AWS SNS or similar. For example, it generates a message saying "The comp for Product A has been completed" and sends it to the member.

[0833] Step 9: The server periodically checks the database and generates a reminder alert three months before the scheduled revision date. It retrieves the scheduled revision date from the database and generates an alert if the condition is met. Specifically, it filters the entries in the database and sends an email or push notification if there is a match.

[0834] Step 10: The server generates a reminder alert and uses AWS SNS to notify registered members. The device receives this notification and displays the alert to the user. For example, this is the operation of notifying project members of the reminder "Start preparation for revising Product B."

[0835] This series of steps allows users to efficiently manage the progress of the project and the schedule for periodic revisions, and also facilitates smooth communication among project members, reducing discrepancies in information.

[0836] (Application example 1)

[0837] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[0838] In modern production projects, progress management and regular revision schedule management are extremely important, but the manual work and confirmation work involved requires a great deal of effort and time. In addition, inadequate information updates and reminders can lead to project delays and errors. Factories, in particular, need an efficient way to grasp progress in real time.

[0839] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0840] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of the revised item, means for generating and notifying a reminder alert when the revision is approaching, means for providing information in real time using a display device that can be worn as a terminal, and means for notifying the user when the progress status or reminder alert is displayed on the display device. This makes it possible to efficiently manage the progress status of products in a factory and the periodic revision schedule, and to provide information to workers in real time.

[0841] A "user" is a person or device that accesses the system and provides input or operations.

[0842] "Product information" is data such as detailed product information and status necessary for project progress management.

[0843] A "database" is a storage device within the system that stores and manages production information and progress status.

[0844] "Progress status" is information that indicates the current work status and progress of the product.

[0845] An "alert" is a warning message that notifies designated members when a progress status change or an important event occurs.

[0846] A "reminder alert" is a notification message that is generated as a reminder when the scheduled revision date approaches.

[0847] A "terminal" is a device, such as smart glasses or other wearable display device, that a user uses to access the system.

[0848] A "display device" is a wearable device for displaying information or notifications to a user in real time.

[0849] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and a specific method for implementing this will be described below.

[0850] System configuration

[0851] The system consists of the following main elements:

[0852] 1. User terminal: This refers to a wearable display device such as smart glasses, which allows users to view information in real time.

[0853] 2. Server: Plays a central role in managing the database, updating progress status, and generating alerts.

[0854] 3. Database: A storage device for storing production information and progress status.

[0855] Authentication Process

[0856] Users log in through their smart glasses and enter their credentials, such as email address and password. The server receives this and checks it against a database. If successful, an authentication token is generated for the session, allowing the user to access the system.

[0857] Registration of productions

[0858] The user inputs details such as the name of the project, project members, and initial status from the device. The device sends this information to the server, which stores it in a database. This allows the project to be managed with a specific project ID.

[0859] Progress Updates

[0860] The server periodically checks the database to monitor the progress of the work. For example, if a certain number of comps have been completed, the status is updated to "Comp Completed." This change is then reflected in the database.

[0861] Alert generation and notification

[0862] If there is a change in the progress status, the server generates an alert and notifies the relevant member. The notification is displayed in real time through the smart glasses. For example, a message such as "Product A's comp is complete" is displayed.

[0863] Regular revision reminder

[0864] The server retrieves the planned revision date from the database and periodically checks it. Three months before the planned revision date, a reminder alert is generated to notify project members. The message "Start preparation for revision of Product B" is displayed on the smart glasses.

[0865] Hardware and software used

[0866] Hardware: Smart glasses (e.g., Google Glass)

[0867] Software: Django (Python framework), SQLite (database), Celery (task queue)

[0868] Specific examples

[0869] Consider a process where a factory worker wears smart glasses to check the status of their production. By voice-inputting the project ID into the smart glasses, the latest status is displayed. If there is a change in the status, real-time notifications are provided.

[0870] Prompt Sentence Examples

[0871] We will build a system to automate project progress management. It will have functions for user authentication, progress status updates, automatic notifications, and periodic reminders. We are considering an application to be installed on smart glasses used in factories. Please explain, with concrete examples and code, how to use Python and Django to manage project progress and notify workers in real time.

[0872] In this way, the present invention realizes a system for efficiently managing the progress of a product and providing reminders for periodic revisions.

[0873] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0874] Step 1:

[0875] A user logs in to the system through smart glasses. The user enters their email address and password, and the device sends this authentication information to the server. The server compares the authentication information with that in the database, and if successful, generates an authentication token for the session and sends it back to the device. The input is the user's login information, and the output is the authentication token.

[0876] Step 2:

[0877] The user inputs detailed information about the project. The user inputs the project name, project members, initial status, etc. into the terminal through the smart glasses. The terminal sends this information to the server, which stores it in a database. The input is the project details, and the output is the project information stored in the database.

[0878] Step 3:

[0879] The server checks the database at regular intervals to monitor the progress status of the production. For example, when the number of comps reaches a certain number, the server updates the status to "Comp complete." This updated information is also reflected in the database. The input is the progress information in the database, and the output is the updated status.

[0880] Step 4:

[0881] If the server detects a change in the progress status, it generates an alert. The generated alert is sent to the user's device and notified in real time to the user's smart glasses. The input is the changed status, and the output is the generated alert.

[0882] Step 5:

[0883] The server periodically checks the planned revision date of the revised item. When it is three months before the planned revision date, it generates a reminder alert to notify the specified members. The input is the planned revision date information in the database, and the output is the generated reminder alert.

[0884] Step 6:

[0885] The user checks the progress status and reminder alerts through the smart glasses, allowing the user to grasp the progress and revision schedule in real time. The input is alerts and status information, and the output is the user's recognition.

[0886] Step 7:

[0887] The server records the information and progress updates it receives in a database for future checks and notifications. The input is the newly generated information or updates, and the output is the information stored in the database.

[0888] Through the above processing steps, the system can efficiently automate the progress management and revision schedule of productions.

[0889] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[0890] The present invention relates to a system that automatically manages the progress of a project and issues reminders for periodic revisions, as well as a system that recognizes the user's emotions and adjusts notification content and priority based on those emotions.

[0891] User Registration and Authentication

[0892] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[0893] Registration of productions

[0894] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[0895] Status updates and management

[0896] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[0897] Alert generation and notification

[0898] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0899] Examples:

[0900] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0901] Reminders for regularly updated items

[0902] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0903] Examples:

[0904] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0905] Introducing the Emotion Engine

[0906] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0907] Tailoring notification content based on emotions

[0908] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0909] Examples:

[0910] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0911] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are not forgotten. It also recognizes users' emotions in real time and enables flexible responses according to the situation, which is expected to improve work efficiency and strengthen teamwork.

[0912] The processing flow will be explained below.

[0913] Step 1:

[0914] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[0915] Step 2:

[0916] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[0917] Step 3:

[0918] The user enters details of a new creation (such as name, members, and initial status) from the device, which then generates an HTTP POST request to send this information to the server.

[0919] Step 4:

[0920] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[0921] Step 5:

[0922] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[0923] Step 6:

[0924] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[0925] Step 7:

[0926] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[0927] Step 8:

[0928] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[0929] Step 9:

[0930] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[0931] Step 10:

[0932] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[0933] Step 11:

[0934] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[0935] Step 12:

[0936] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0937] Step 13:

[0938] Example: If the emotion engine recognizes that a user is under stress, the server will set notifications for that user to "low priority" and send follow-up notifications to other members to reduce the user's burden.

[0939] Example 2

[0940] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[0941] While existing production management systems have functions for managing the progress of production and for reminders for periodic revisions, they lack the ability to respond to the user's emotional state. As a result, users can feel stressed or anxious, which can have a negative impact on work efficiency and teamwork. Furthermore, the lack of a mechanism for flexibly adjusting the content and priority of notifications increases the burden on users, which is a problem.

[0942] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[0943] In this invention, the server includes means for receiving production information input by a user, means for saving the received production information in a database, means for monitoring the progress of the production, means for notifying designated members by sending an alert when there is a change in the progress, means for periodically checking the planned revision date of an item to be revised, means for generating and sending a reminder alert when the revision is approaching, means for recognizing the user's emotions, and means for adjusting the notification content and priority based on the recognized emotions. This enables flexible adjustment of the notification content and priority to match the user's emotional state, reducing stress and anxiety and ultimately improving work efficiency and teamwork.

[0944] "Production information" refers to detailed information about a production that a user inputs into the system, such as the name of the production, project members, and initial status.

[0945] A "database" is a storage device and its components for storing and managing information such as production information, progress status, and planned revision dates.

[0946] "Progress status" refers to information or status that indicates the progress of a production, such as "comp complete" or "in progress."

[0947] An "alert" is a notification generated by the system based on changes in progress status or planned revision dates, and notifies users and members of important information.

[0948] "Regular revision" refers to inspections and evaluations that are carried out periodically to ensure the quality and maintain the products.

[0949] A "reminder alert" is a notification generated by the system when the scheduled date for a regular revision approaches, encouraging users and members to prepare for and implement the revision.

[0950] "Emotion" refers to the user's psychological state, and includes, for example, stress, anxiety, satisfaction, and the like.

[0951] An "emotion engine" is a software or hardware configuration that analyzes a user's facial image, voice, and text input in real time to recognize the user's emotions.

[0952] "Notification content" refers to information contained in an alert or reminder alert, and refers to the message or information to be conveyed to the user.

[0953] "Priority" indicates the importance of the notification content or alert, and is an index that sets the urgency or importance of the notification to users or members.

[0954] This invention is a system that not only automatically manages the progress of production and sends reminders for periodic revisions, but also has the function of recognizing the user's emotions and adjusting the content and priority of notifications based on those emotions.

[0955] User Registration and Authentication

[0956] To log in to the system, a user first enters their email address and password from their device. The device sends the entered information to the server, which checks it against the authentication information in the database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system. The hardware required is the user's device (PC, smartphone, etc.), a server, and a database.

[0957] Registration of productions

[0958] To register a new project, a user enters details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID. The required software is a database management system (DBMS) and a web server application.

[0959] Status updates and management

[0960] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[0961] Alert generation and notification

[0962] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[0963] Specific examples

[0964] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[0965] Reminders for regularly updated items

[0966] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0967] Specific examples

[0968] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[0969] Introducing the Emotion Engine

[0970] The device captures a picture of the user's face with a camera and analyzes the voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.). Hardware such as a camera and microphone are required, while software such as an emotion analysis engine is required.

[0971] Tailoring notification content based on emotions

[0972] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[0973] Specific examples

[0974] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[0975] Prompt Sentence Examples

[0976] "The system allows users to manage the progress of their creations and automatically reminds them of regular revision schedules. It also uses an emotion engine to recognize users' emotions and adjust the priority of notifications based on those emotions."

[0977] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0978] Step 1:

[0979] To log in to the system, a user enters their email address and password from their device. The entered information is sent from the device to the server. The server compares the received authentication information with the information in the database, generates an authentication token, and sends it back to the device. This allows the user to access the system.

[0980] Input: Email address, Password

[0981] Output: Authentication token

[0982] Step 2:

[0983] To register a new project, a user inputs its details (project name, project members, initial status, etc.) into the terminal. The input information is sent from the terminal to the server, which stores the received project information in a database and assigns a specific project ID.

[0984] Input: Name of project, project members, initial status

[0985] Output: Project ID

[0986] Step 3:

[0987] The server checks the database at regular intervals to monitor the progress of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp complete." The updated progress is also reflected in the database.

[0988] Input: Product progress information

[0989] Output: Updated progress

[0990] Step 4:

[0991] If there is a change in the progress status, the server generates an alert for the corresponding member. The alert notification is sent to the user via SMS or push notification on the device, allowing members to know the progress status in real time.

[0992] Input: Updated progress

[0993] Output: Alert notification

[0994] Specific behavior:

[0995] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp is complete" is sent to all members participating in the project.

[0996] Step 5:

[0997] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[0998] Input: Planned revision date

[0999] Output: Reminder alert

[1000] Specific behavior:

[1001] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for the revision of product B" and notifies the project members.

[1002] Step 6:

[1003] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[1004] Input: User's facial image, voice, and text input

[1005] Output: Recognized emotion data

[1006] Step 7:

[1007] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[1008] Input: Recognized emotion data

[1009] Output: Adjusted notification content and priority

[1010] Specific behavior:

[1011] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[1012] (Application example 2)

[1013] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1014] In manufacturing environments such as factories, tasks such as managing the progress of production and reminders for periodic revisions are diverse and highly complex. It is also important to note that the emotions and mental state of workers on the front lines have a significant impact on work efficiency and quality. However, current systems lack the ability to recognize workers' emotions and adjust notification content and priorities accordingly. A new system is needed to address this shortcoming.

[1015] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[1016] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of an item to be revised, means for generating and notifying a reminder alert when the revision is approaching, and means for recognizing the user's emotions and adjusting the content and priority of notifications based on the emotions. This allows for efficient management of the progress status of the product and flexible responses according to the emotional state of the worker.

[1017] "Product information" refers to detailed data about each project or item in the manufacturing process, including the name, members, progress, etc.

[1018] "Progress status" is information that indicates the current stage of a production or project, and serves as a criterion for managing the progress of work.

[1019] A "database" is a system for organizing and storing product information, progress status, user information, and the like.

[1020] An "alert" is a notice or notification sent to a user or member when a specific condition is met.

[1021] A "reminder" is an alert that notifies the user based on a specific date and time or conditions, and prompts the user to take a specific action.

[1022] "User emotion" refers to the emotional state of a person using a system, including psychological states such as stress, anxiety, and satisfaction.

[1023] "Emotion recognition" is a technology that analyzes data such as a user's face, voice, and text to determine the user's emotions.

[1024] The system of the present invention manages the progress of products, provides reminders for periodic revisions, recognizes the emotions of workers, and adjusts notifications based on the emotions in a manufacturing environment such as a factory. A specific embodiment of this system will be described below.

[1025] User Registration and Authentication

[1026] First, a user enters their email address and password on their device to log in to the system. The device sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system.

[1027] Registration of productions

[1028] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[1029] Status updates and management

[1030] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[1031] Alert generation and notification

[1032] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[1033] Reminders for regularly updated items

[1034] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1035] Introducing the Emotion Engine

[1036] The device captures a user's face with a camera and analyzes voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[1037] Tailoring notification content based on emotions

[1038] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[1039] Examples and software used

[1040] This system uses a Python-based programming language to realize various functions. It also uses common machine learning models and natural AI tools for emotion recognition. It uses RDBMS such as MySQL or PostgreSQL for the database, and Firebase Cloud Messaging (FCM) for notification functions.

[1041] For example, if the emotion engine recognizes that a user is under stress, the server will set notifications to that user as "low priority" and send follow-up notifications to other members to reduce the user's burden.

[1042] Examples of prompt statements

[1043] Examples of prompts that can be given to a generative AI model include:

[1044] "I want to create an application that recognizes user emotions and manages project progress. Please add a feature that adjusts notification content and priority based on emotion data. Please output Python code that registers new projects, updates progress status, and generates alerts based on emotions."

[1045] This makes it possible to realize a flexible progress management system that takes into account the user's emotions.

[1046] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[1047] Step 1:

[1048] A user enters their email address and password on a terminal and sends a login request to the server. The server checks the input information against the authentication information in the database, and if authentication is successful, generates an authentication token for the session and returns it to the terminal. This authentication token allows the user to access the system.

[1049] Input: User's email address, password

[1050] Data processing: The server checks the authentication information against the database

[1051] Output: Authentication token for the session

[1052] Step 2:

[1053] To register a new project, a user inputs details such as the project name, project members, and initial status into a terminal and sends them to the server, which stores the received information in a database and manages the project with a specific project ID.

[1054] Input: Name of the project, project members, initial status

[1055] Data processing: The server stores the information in a database

[1056] Output: Specific project ID

[1057] Step 3:

[1058] The server checks the database at regular intervals to monitor changes in the progress status of the work. When the progress status is updated, the new status information is updated in the database. At this time, if a specified number of comps have been completed, for example, the status is updated to "Comp complete."

[1059] Input: Contents of the production database

[1060] Data processing: The server periodically checks the database and updates the status information

[1061] Output: Updated status information

[1062] Step 4:

[1063] When there is a change in the progress status, the server generates an alert for the corresponding project member, and this alert is sent to the device via SMS or push notification to notify the user.

[1064] Input: Updated status information

[1065] Data processing: Server generates alerts and sends notifications

[1066] Output: Notification to users and members

[1067] Step 5:

[1068] For items that require periodic revision, the server retrieves the planned revision date from the database and checks whether the date is approaching. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1069] Input: Database contents of revised items

[1070] Data processing: The server checks the scheduled revision date and generates a reminder

[1071] Output: Reminder alert and notification to user

[1072] Step 6:

[1073] The device captures the user's face with a camera and captures voice and text input, which is then analyzed by an emotion engine to recognize the user's emotional state (stress, anxiety, satisfaction, etc.).

[1074] Input: User's face image, voice, text input

[1075] Data processing: Emotion engine analyzes emotional data

[1076] Output: Recognized emotion data

[1077] Step 7:

[1078] The server receives the emotion data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user's emotion is recognized as stress, the server lowers the urgency of the notification and reduces the notification frequency.

[1079] Input: Emotion data provided by the emotion engine

[1080] Data processing: The server adjusts the notification content and priority

[1081] Output: Adjusted alert notification

[1082] The specific processing unit 290 transmits the result of the specific processing to the headset type terminal 314. In the headset type terminal 314, the control unit 46A causes the speaker 240 and the display 343 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[1083] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[1084] In the above embodiment, an example was given in which the specific processing is performed by the data processing device 12, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the headset type terminal 314.

[1085] [Fourth embodiment]

[1086] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.

[1087] 7, a data processing system 410 includes a data processing device 12 and a robot 414. An example of the data processing device 12 is a server.

[1088] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[1089] The robot 414 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a control target 443. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the control target 443 are also connected to the bus 52.

[1090] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[1091] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[1092] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[1093] The control object 443 includes a display device, LEDs in the eyes, and motors for driving the arms, hands, and feet. The posture and gestures of the robot 414 are controlled by controlling the motors of the arms, hands, and feet. Some of the emotions of the robot 414 can be expressed by controlling these motors. In addition, the facial expressions of the robot 414 can also be expressed by controlling the light emission state of the LEDs in the eyes of the robot 414.

[1094] Fig. 8 shows an example of the main functions of the data processing device 12 and the robot 414. As shown in Fig. 8, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[1095] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[1096] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[1097] In the robot 414, the processor 46 performs the reception output process. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[1098] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1099] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and will be described in detail below.

[1100] User Registration and Authentication

[1101] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[1102] Registration of productions

[1103] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[1104] Status updates and management

[1105] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[1106] Alert generation and notification

[1107] If there is a change in the progress status, the server generates an alert for the relevant member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[1108] Examples:

[1109] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[1110] Reminders for regularly updated items

[1111] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1112] Examples:

[1113] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[1114] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are followed. As a result, projects run smoothly without delays. It is also expected to improve communication between members and reduce discrepancies in information.

[1115] The processing flow will be explained below.

[1116] Step 1:

[1117] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[1118] Step 2:

[1119] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[1120] Step 3:

[1121] The user enters the details of the new creation (name, members, initial status, etc.) from the terminal, and the terminal again generates an HTTP POST request to send this information to the server.

[1122] Step 4:

[1123] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[1124] Step 5:

[1125] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[1126] Step 6:

[1127] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[1128] Step 7:

[1129] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[1130] Step 8:

[1131] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[1132] Step 9:

[1133] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[1134] Step 10:

[1135] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[1136] Example 1

[1137] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1138] With conventional progress management systems, managing project progress and regular revision schedules was cumbersome, resulting in project delays and lack of communication between members. Furthermore, the system's security was also vulnerable due to an insufficient user authentication process. To solve these problems, an integrated and efficient progress management and notification system was needed.

[1139] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[1140] In this invention, the server includes a means for verifying user authentication information and generating a session authentication token, a means for generating a project ID and saving it together with the product information, and a means for checking the database at regular intervals to update the progress status. This enhances user security while efficiently managing the progress status and periodic revision schedule of the product. Furthermore, it can notify members in real time of changes in the progress status, preventing project delays and lack of communication.

[1141] "User" means any individual or entity that accesses and operates the System.

[1142] "Authentication information" is data for identifying and authenticating a user, and mainly includes a combination of an email address and a password.

[1143] A "session authentication token" is a unique identifier used to maintain a session after a user logs in.

[1144] "Product information" is detailed data about a product registered by a user, including the name, project members, status, and so on.

[1145] A "database" is a digital storage device that structures and stores information about a system.

[1146] A "project ID" is an identifier that uniquely identifies a registered production.

[1147] "Progress status" is an indicator of the progress of a production, and includes states such as "comp complete."

[1148] An "alert" is a message that notifies the user when a specific condition occurs.

[1149] A "reminder alert" is a message that notifies you when a deadline for a recurring task or event is approaching.

[1150] A "terminal" is a device, such as a computer or smartphone, that a user uses to access the system.

[1151] The present invention relates to a system for automatically managing the progress of a product and issuing reminders for periodic revisions. Specific embodiments of the system are described below.

[1152] User Registration and Authentication

[1153] To log in to the system, a user enters their email address and password from their device. The device sends the information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device, allowing the user to access the system.

[1154] Hardware and software used

[1155] Server: AWS EC2 (cloud server)

[1156] Database: AWS RDS (relational database)

[1157] Device: The PC or smartphone used by the user

[1158] Communication protocol: HTTPS

[1159] Registration of productions

[1160] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[1161] Specific examples

[1162] When a user registers "Product A", they enter the name "Product A", members "Member 1, Member 2", and status "Started". The server saves this information and assigns a unique project ID to "Product A".

[1163] Status updates and management

[1164] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[1165] Specific examples

[1166] When the number of comps for Product A reaches the specified number, the server updates the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[1167] Alert generation and notification

[1168] If there is a change in the progress status, the server generates an alert for the relevant member, and this alert is notified to the user via their device via SMS or push notification.

[1169] Specific examples

[1170] When Product A reaches "comp complete," the server generates an alert stating "Product A comp complete" and notifies the member's device.

[1171] Reminders for regularly updated items

[1172] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1173] Specific examples

[1174] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[1175] Examples of prompt statements

[1176] "Please add a setting to notify you when the progress status of Product A changes."

[1177] "Please include a function to generate a reminder three months before the scheduled revision date."

[1178] This system allows users to efficiently manage the progress of projects and schedule regular revisions, and also facilitates smooth communication between project members, reducing discrepancies in information.

[1179] The flow of the identification process in the first embodiment will be described with reference to FIG.

[1180] Step 1: The user enters their email address and password to log in to the system from their terminal. Based on the input (email address and password), the terminal encrypts the information and sends it to the server using HTTPS. Specifically, the terminal encrypts the email address and password and sends them to the server.

[1181] Step 2: The server checks the received information (email address and password) against the authentication information in its database. If the authentication is successful, the server generates an authentication token for the session. This is the process of running a database query to verify that the corresponding user information exists.

[1182] Step 3: The server returns the generated session authentication token to the device. The device receives this authentication token and stores it in a cookie or local storage. This allows the user to access the system. Specifically, the server generates the token and sends it to the device in an HTTP response.

[1183] Step 4: To register a new project, the user enters details (project name, project members, initial status, etc.) into the device. The device sends this information in JSON format to the server. Specifically, the user enters the details into a form on the device and presses the submit button.

[1184] Step 5: The server stores the received product information in its database. Based on the input data, it creates a new product record and generates a unique project ID. Specifically, the server adds a new entry to the database and generates a unique ID, such as a UUID.

[1185] Step 6: The server returns a response including the generated project ID to the terminal, which displays it. As a specific example, the user registers "Product A" and its detailed information is displayed.

[1186] Step 7: The server uses a regular scheduler, such as a cron job, to check the database at regular intervals to monitor changes in the progress status of the work. It updates the status of work that meets certain criteria, such as the number of comps completed. Specifically, the server runs a scheduled job in the background, running database queries.

[1187] Step 8: The server saves the updated status to the database and generates an alert to the relevant member. This alert information is generated in JSON format and sent via AWS SNS or similar. For example, it generates a message saying "The comp for Product A has been completed" and sends it to the member.

[1188] Step 9: The server periodically checks the database and generates a reminder alert three months before the scheduled revision date. It retrieves the scheduled revision date from the database and generates an alert if the condition is met. Specifically, it filters the entries in the database and sends an email or push notification if there is a match.

[1189] Step 10: The server generates a reminder alert and uses AWS SNS to notify registered members. The device receives this notification and displays the alert to the user. For example, this is the operation of notifying project members of the reminder "Start preparation for revising Product B."

[1190] This series of steps allows users to efficiently manage the progress of the project and the schedule for periodic revisions, and also facilitates smooth communication among project members, reducing discrepancies in information.

[1191] (Application example 1)

[1192] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1193] In modern production projects, progress management and regular revision schedule management are extremely important, but the manual work and confirmation work involved requires a great deal of effort and time. In addition, inadequate information updates and reminders can lead to project delays and errors. Factories, in particular, need an efficient way to grasp progress in real time.

[1194] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1195] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of the revised item, means for generating and notifying a reminder alert when the revision is approaching, means for providing information in real time using a display device that can be worn as a terminal, and means for notifying the user when the progress status or reminder alert is displayed on the display device. This makes it possible to efficiently manage the progress status of products in a factory and the periodic revision schedule, and to provide information to workers in real time.

[1196] A "user" is a person or device that accesses the system and provides input or operations.

[1197] "Product information" is data such as detailed product information and status necessary for project progress management.

[1198] A "database" is a storage device within the system that stores and manages production information and progress status.

[1199] "Progress status" is information that indicates the current work status and progress of the product.

[1200] An "alert" is a warning message that notifies designated members when a progress status change or an important event occurs.

[1201] A "reminder alert" is a notification message that is generated as a reminder when the scheduled revision date approaches.

[1202] A "terminal" is a device, such as smart glasses or other wearable display device, that a user uses to access the system.

[1203] A "display device" is a wearable device for displaying information or notifications to a user in real time.

[1204] The present invention relates to a system that automatically manages the progress of a product and issues reminders for periodic revisions, and a specific method for implementing this will be described below.

[1205] System configuration

[1206] The system consists of the following main elements:

[1207] 1. User terminal: This refers to a wearable display device such as smart glasses, which allows users to view information in real time.

[1208] 2. Server: Plays a central role in managing the database, updating progress status, and generating alerts.

[1209] 3. Database: A storage device for storing production information and progress status.

[1210] Authentication Process

[1211] Users log in through their smart glasses and enter their credentials, such as email address and password. The server receives this and checks it against a database. If successful, an authentication token is generated for the session, allowing the user to access the system.

[1212] Registration of productions

[1213] The user inputs details such as the name of the project, project members, and initial status from the device. The device sends this information to the server, which stores it in a database. This allows the project to be managed with a specific project ID.

[1214] Progress Updates

[1215] The server periodically checks the database to monitor the progress of the work. For example, if a certain number of comps have been completed, the status is updated to "Comp Completed." This change is then reflected in the database.

[1216] Alert generation and notification

[1217] If there is a change in the progress status, the server generates an alert and notifies the relevant member. The notification is displayed in real time through the smart glasses. For example, a message such as "Product A's comp is complete" is displayed.

[1218] Regular revision reminder

[1219] The server retrieves the planned revision date from the database and periodically checks it. Three months before the planned revision date, a reminder alert is generated to notify project members. The message "Start preparation for revision of Product B" is displayed on the smart glasses.

[1220] Hardware and software used

[1221] Hardware: Smart glasses (e.g., Google Glass)

[1222] Software: Django (Python framework), SQLite (database), Celery (task queue)

[1223] Specific examples

[1224] Consider a process where a factory worker wears smart glasses to check the status of their production. By voice-inputting the project ID into the smart glasses, the latest status is displayed. If there is a change in the status, real-time notifications are provided.

[1225] Prompt Sentence Examples

[1226] We will build a system to automate project progress management. It will have functions for user authentication, progress status updates, automatic notifications, and periodic reminders. We are considering an application to be installed on smart glasses used in factories. Please explain, with concrete examples and code, how to use Python and Django to manage project progress and notify workers in real time.

[1227] In this way, the present invention realizes a system for efficiently managing the progress of a product and providing reminders for periodic revisions.

[1228] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1229] Step 1:

[1230] A user logs in to the system through smart glasses. The user enters their email address and password, and the device sends this authentication information to the server. The server compares the authentication information with that in the database, and if successful, generates an authentication token for the session and sends it back to the device. The input is the user's login information, and the output is the authentication token.

[1231] Step 2:

[1232] The user inputs detailed information about the project. The user inputs the project name, project members, initial status, etc. into the terminal through the smart glasses. The terminal sends this information to the server, which stores it in a database. The input is the project details, and the output is the project information stored in the database.

[1233] Step 3:

[1234] The server checks the database at regular intervals to monitor the progress status of the production. For example, when the number of comps reaches a certain number, the server updates the status to "Comp complete." This updated information is also reflected in the database. The input is the progress information in the database, and the output is the updated status.

[1235] Step 4:

[1236] If the server detects a change in the progress status, it generates an alert. The generated alert is sent to the user's device and notified in real time to the user's smart glasses. The input is the changed status, and the output is the generated alert.

[1237] Step 5:

[1238] The server periodically checks the planned revision date of the revised item. When it is three months before the planned revision date, it generates a reminder alert to notify the specified members. The input is the planned revision date information in the database, and the output is the generated reminder alert.

[1239] Step 6:

[1240] The user checks the progress status and reminder alerts through the smart glasses, allowing the user to grasp the progress and revision schedule in real time. The input is alerts and status information, and the output is the user's recognition.

[1241] Step 7:

[1242] The server records the information and progress updates it receives in a database for future checks and notifications. The input is the newly generated information or updates, and the output is the information stored in the database.

[1243] Through the above processing steps, the system can efficiently automate the progress management and revision schedule of productions.

[1244] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1245] The present invention relates to a system that automatically manages the progress of a project and issues reminders for periodic revisions, as well as a system that recognizes the user's emotions and adjusts notification content and priority based on those emotions.

[1246] User Registration and Authentication

[1247] To log in to the system, a user first enters their email address and password from their device. The device then sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and returns it to the device, allowing the user to access the system.

[1248] Registration of productions

[1249] To register a new project, a user enters its details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[1250] Status updates and management

[1251] The server periodically checks the database to monitor changes in the progress status of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp Completed." This update information is also reflected in the database.

[1252] Alert generation and notification

[1253] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[1254] Examples:

[1255] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[1256] Reminders for regularly updated items

[1257] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1258] Examples:

[1259] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[1260] Introducing the Emotion Engine

[1261] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[1262] Tailoring notification content based on emotions

[1263] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[1264] Examples:

[1265] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[1266] This system allows users to efficiently manage the progress of their work and ensure regular revision schedules are not forgotten. It also recognizes users' emotions in real time and enables flexible responses according to the situation, which is expected to improve work efficiency and strengthen teamwork.

[1267] The processing flow will be explained below.

[1268] Step 1:

[1269] The user enters their email address and password into the device, which then generates an HTTP POST request to send this authentication information to the server.

[1270] Step 2:

[1271] The server receives the request, connects to a database, and matches the entered email address with the hashed password. If the match is successful, the server generates an authentication token and sends it back to the device.

[1272] Step 3:

[1273] The user enters details of a new creation (such as name, members, and initial status) from the device, which then generates an HTTP POST request to send this information to the server.

[1274] Step 4:

[1275] The server receives the information about the new project and stores it in the database. Once the information is saved, the server generates a new project ID and returns it to the device.

[1276] Step 5:

[1277] The server periodically checks the database to monitor the progress of the production and updates the status according to certain rules (e.g., when a certain number of comps are reached).

[1278] Step 6:

[1279] When the server detects a change in the progress status, it generates an alert for the corresponding member. The alert content is generated as a plain text message and sent to the device via a notification method (e.g., SMS, Push notification).

[1280] Step 7:

[1281] The device notifies the user of the alerts received from the server by displaying them on the screen, making sounds, vibrating, etc. The user can be aware of changes in progress status in real time.

[1282] Step 8:

[1283] The server periodically scans the database for items due for revision and checks their planned revision dates, generating a reminder alert three months before the planned revision date.

[1284] Step 9:

[1285] The server notifies the relevant members of the reminder alert and sends a message to the members to prepare for the revision.

[1286] Step 10:

[1287] The terminal notifies the member of the reminder alert received from the server, and the user starts preparing for the revision.

[1288] Step 11:

[1289] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[1290] Step 12:

[1291] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[1292] Step 13:

[1293] Example: If the emotion engine recognizes that a user is under stress, the server will set notifications for that user to "low priority" and send follow-up notifications to other members to reduce the user's burden.

[1294] Example 2

[1295] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1296] While existing production management systems have functions for managing the progress of production and for reminders for periodic revisions, they lack the ability to respond to the user's emotional state. As a result, users can feel stressed or anxious, which can have a negative impact on work efficiency and teamwork. Furthermore, the lack of a mechanism for flexibly adjusting the content and priority of notifications increases the burden on users, which is a problem.

[1297] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[1298] In this invention, the server includes means for receiving production information input by a user, means for saving the received production information in a database, means for monitoring the progress of the production, means for notifying designated members by sending an alert when there is a change in the progress, means for periodically checking the planned revision date of an item to be revised, means for generating and sending a reminder alert when the revision is approaching, means for recognizing the user's emotions, and means for adjusting the notification content and priority based on the recognized emotions. This enables flexible adjustment of the notification content and priority to match the user's emotional state, reducing stress and anxiety and ultimately improving work efficiency and teamwork.

[1299] "Production information" refers to detailed information about a production that a user inputs into the system, such as the name of the production, project members, and initial status.

[1300] A "database" is a storage device and its components for storing and managing information such as production information, progress status, and planned revision dates.

[1301] "Progress status" refers to information or status that indicates the progress of a production, such as "comp complete" or "in progress."

[1302] An "alert" is a notification generated by the system based on changes in progress status or planned revision dates, and notifies users and members of important information.

[1303] "Regular revision" refers to inspections and evaluations that are carried out periodically to ensure the quality and maintain the products.

[1304] A "reminder alert" is a notification generated by the system when the scheduled date for a regular revision approaches, encouraging users and members to prepare for and implement the revision.

[1305] "Emotion" refers to the user's psychological state, and includes, for example, stress, anxiety, satisfaction, and the like.

[1306] An "emotion engine" is a software or hardware configuration that analyzes a user's facial image, voice, and text input in real time to recognize the user's emotions.

[1307] "Notification content" refers to information contained in an alert or reminder alert, and refers to the message or information to be conveyed to the user.

[1308] "Priority" indicates the importance of the notification content or alert, and is an index that sets the urgency or importance of the notification to users or members.

[1309] This invention is a system that not only automatically manages the progress of production and sends reminders for periodic revisions, but also has the function of recognizing the user's emotions and adjusting the content and priority of notifications based on those emotions.

[1310] User Registration and Authentication

[1311] To log in to the system, a user first enters their email address and password from their device. The device sends the entered information to the server, which checks it against the authentication information in the database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system. The hardware required is the user's device (PC, smartphone, etc.), a server, and a database.

[1312] Registration of productions

[1313] To register a new project, a user enters details into the terminal, including the project name, project members, and initial status. The terminal sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID. The required software is a database management system (DBMS) and a web server application.

[1314] Status updates and management

[1315] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[1316] Alert generation and notification

[1317] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[1318] Specific examples

[1319] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp has been completed" is sent to members participating in the project.

[1320] Reminders for regularly updated items

[1321] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1322] Specific examples

[1323] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for revising product B" and notifies the project members.

[1324] Introducing the Emotion Engine

[1325] The device captures a picture of the user's face with a camera and analyzes the voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.). Hardware such as a camera and microphone are required, while software such as an emotion analysis engine is required.

[1326] Tailoring notification content based on emotions

[1327] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[1328] Specific examples

[1329] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[1330] Prompt Sentence Examples

[1331] "The system allows users to manage the progress of their creations and automatically reminds them of regular revision schedules. It also uses an emotion engine to recognize users' emotions and adjust the priority of notifications based on those emotions."

[1332] The flow of the identification process in the second embodiment will be described with reference to FIG.

[1333] Step 1:

[1334] To log in to the system, a user enters their email address and password from their device. The entered information is sent from the device to the server. The server compares the received authentication information with the information in the database, generates an authentication token, and sends it back to the device. This allows the user to access the system.

[1335] Input: Email address, Password

[1336] Output: Authentication token

[1337] Step 2:

[1338] To register a new project, a user inputs its details (project name, project members, initial status, etc.) into the terminal. The input information is sent from the terminal to the server, which stores the received project information in a database and assigns a specific project ID.

[1339] Input: Name of project, project members, initial status

[1340] Output: Project ID

[1341] Step 3:

[1342] The server checks the database at regular intervals to monitor the progress of the work. For example, when the number of comps reaches a specified number, it updates the status to "Comp complete." The updated progress is also reflected in the database.

[1343] Input: Product progress information

[1344] Output: Updated progress

[1345] Step 4:

[1346] If there is a change in the progress status, the server generates an alert for the corresponding member. The alert notification is sent to the user via SMS or push notification on the device, allowing members to know the progress status in real time.

[1347] Input: Updated progress

[1348] Output: Alert notification

[1349] Specific behavior:

[1350] When the number of comps for Product A reaches the specified number, the server changes the status to "Comp Completed." At the same time, an alert stating "Product A's comp is complete" is sent to all members participating in the project.

[1351] Step 5:

[1352] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1353] Input: Planned revision date

[1354] Output: Reminder alert

[1355] Specific behavior:

[1356] When the planned revision date of a certain product B approaches in three months, the server generates a reminder alert saying "Start preparations for the revision of product B" and notifies the project members.

[1357] Step 6:

[1358] The device captures the user's face with a camera and analyzes voice and text input in real time, which is then analyzed by an emotion engine to recognize the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[1359] Input: User's facial image, voice, and text input

[1360] Output: Recognized emotion data

[1361] Step 7:

[1362] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[1363] Input: Recognized emotion data

[1364] Output: Adjusted notification content and priority

[1365] Specific behavior:

[1366] If the emotion engine recognizes that a user is under stress, the server sets the notification to that user as "low priority" and sends follow-up notifications to other members, taking measures to reduce the user's burden.

[1367] (Application example 2)

[1368] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1369] In manufacturing environments such as factories, tasks such as managing the progress of production and reminders for periodic revisions are diverse and highly complex. It is also important to note that the emotions and mental state of workers on the front lines have a significant impact on work efficiency and quality. However, current systems lack the ability to recognize workers' emotions and adjust notification content and priorities accordingly. A new system is needed to address this shortcoming.

[1370] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[1371] In this invention, the server includes means for receiving product information input by a user, means for saving the received product information in a database, means for managing the progress status of the product, means for notifying designated members of an alert when there is a change in the progress status, means for periodically checking the planned revision date of an item to be revised, means for generating and notifying a reminder alert when the revision is approaching, and means for recognizing the user's emotions and adjusting the content and priority of notifications based on the emotions. This allows for efficient management of the progress status of the product and flexible responses according to the emotional state of the worker.

[1372] "Product information" refers to detailed data about each project or item in the manufacturing process, including the name, members, progress, etc.

[1373] "Progress status" is information that indicates the current stage of a production or project, and serves as a criterion for managing the progress of work.

[1374] A "database" is a system for organizing and storing product information, progress status, user information, and the like.

[1375] An "alert" is a notice or notification sent to a user or member when a specific condition is met.

[1376] A "reminder" is an alert that notifies the user based on a specific date and time or conditions, and prompts the user to take a specific action.

[1377] "User emotion" refers to the emotional state of a person using a system, including psychological states such as stress, anxiety, and satisfaction.

[1378] "Emotion recognition" is a technology that analyzes data such as a user's face, voice, and text to determine the user's emotions.

[1379] The system of the present invention manages the progress of products, provides reminders for periodic revisions, recognizes the emotions of workers, and adjusts notifications based on the emotions in a manufacturing environment such as a factory. A specific embodiment of this system will be described below.

[1380] User Registration and Authentication

[1381] First, a user enters their email address and password on their device to log in to the system. The device sends the entered information to the server, which checks it against the authentication information in its database. If the check is successful, the server generates an authentication token for the session and sends it back to the device. This allows the user to access the system.

[1382] Registration of productions

[1383] To register a new project, a user enters details into the device, including the project name, project members, and initial status. The device sends this information to the server, which stores it in a database. Once registered, the project is managed with a specific project ID.

[1384] Status updates and management

[1385] The server periodically checks the database to monitor changes in the progress status of the work. For example, if the number of comps reaches a specified number, the status is updated to "Comp Completed." This updated information is also reflected in the database.

[1386] Alert generation and notification

[1387] If there is a change in the progress status, the server generates an alert for the corresponding member. This alert is notified to the user via their device via SMS or push notification, allowing members to grasp the progress status in real time.

[1388] Reminders for regularly updated items

[1389] The server retrieves the planned revision date for items that require periodic revision from the database and periodically checks it. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1390] Introducing the Emotion Engine

[1391] The device captures a user's face with a camera and analyzes voice and text input in real time. An emotion engine analyzes this and recognizes the user's emotions (e.g., stress, anxiety, satisfaction, etc.).

[1392] Tailoring notification content based on emotions

[1393] The server receives the emotional data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user is feeling stressed, the server may lower the urgency of the alert or reduce the frequency of notifications.

[1394] Examples and software used

[1395] This system uses a Python-based programming language to realize various functions. It also uses common machine learning models and natural AI tools for emotion recognition. It uses RDBMS such as MySQL or PostgreSQL for the database, and Firebase Cloud Messaging (FCM) for notification functions.

[1396] For example, if the emotion engine recognizes that a user is under stress, the server will set notifications to that user as "low priority" and send follow-up notifications to other members to reduce the user's burden.

[1397] Examples of prompt statements

[1398] Examples of prompts that can be given to a generative AI model include:

[1399] "I want to create an application that recognizes user emotions and manages project progress. Please add a feature that adjusts notification content and priority based on emotion data. Please output Python code that registers new projects, updates progress status, and generates alerts based on emotions."

[1400] This makes it possible to realize a flexible progress management system that takes into account the user's emotions.

[1401] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[1402] Step 1:

[1403] A user enters their email address and password on a terminal and sends a login request to the server. The server checks the input information against the authentication information in the database, and if authentication is successful, generates an authentication token for the session and returns it to the terminal. This authentication token allows the user to access the system.

[1404] Input: User's email address, password

[1405] Data processing: The server checks the authentication information against the database

[1406] Output: Authentication token for the session

[1407] Step 2:

[1408] To register a new project, a user inputs details such as the project name, project members, and initial status into a terminal and sends them to the server, which stores the received information in a database and manages the project with a specific project ID.

[1409] Input: Name of the project, project members, initial status

[1410] Data processing: The server stores the information in a database

[1411] Output: Specific project ID

[1412] Step 3:

[1413] The server checks the database at regular intervals to monitor changes in the progress status of the work. When the progress status is updated, the new status information is updated in the database. At this time, if a specified number of comps have been completed, for example, the status is updated to "Comp complete."

[1414] Input: Contents of the production database

[1415] Data processing: The server periodically checks the database and updates the status information

[1416] Output: Updated status information

[1417] Step 4:

[1418] When there is a change in the progress status, the server generates an alert for the corresponding project member, and this alert is sent to the device via SMS or push notification to notify the user.

[1419] Input: Updated status information

[1420] Data processing: Server generates alerts and sends notifications

[1421] Output: Notification to users and members

[1422] Step 5:

[1423] For items that require periodic revision, the server retrieves the planned revision date from the database and checks whether the date is approaching. Three months before the planned revision date, it generates a reminder alert and notifies the relevant members.

[1424] Input: Database contents of revised items

[1425] Data processing: The server checks the scheduled revision date and generates a reminder

[1426] Output: Reminder alert and notification to user

[1427] Step 6:

[1428] The device captures the user's face with a camera and captures voice and text input, which is then analyzed by an emotion engine to recognize the user's emotional state (stress, anxiety, satisfaction, etc.).

[1429] Input: User's face image, voice, text input

[1430] Data processing: Emotion engine analyzes emotional data

[1431] Output: Recognized emotion data

[1432] Step 7:

[1433] The server receives the emotion data provided by the emotion engine and adjusts the content and priority of the alert notification based on that data. For example, if the user's emotion is recognized as stress, the server lowers the urgency of the notification and reduces the notification frequency.

[1434] Input: Emotion data provided by the emotion engine

[1435] Data processing: The server adjusts the notification content and priority

[1436] Output: Adjusted alert notification

[1437] The specific processing unit 290 transmits the result of the specific processing to the robot 414. In the robot 414, the control unit 46A causes the speaker 240 and the control target 443 to output the result of the specific processing. The microphone 238 acquires voice indicating a user input regarding the result of the specific processing. The control unit 46A transmits voice data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the voice data.

[1438] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[1439] In the above embodiment, an example was given in which the specific processing is performed by the data processing device 12, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the robot 414.

[1440] The emotion identification model 59 as an emotion engine may determine the user's emotion according to a specific mapping. Specifically, the emotion identification model 59 may determine the user's emotion according to an emotion map (see FIG. 9), which is a specific mapping. Similarly, the emotion identification model 59 may determine the robot's emotion, and the identification processing unit 290 may perform identification processing using the robot's emotion.

[1441] FIG. 9 is a diagram illustrating an emotion map 400 on which multiple emotions are mapped. In the emotion map 400, emotions are arranged in concentric circles radiating from the center. Emotions closer to the center of the concentric circles are more primitive. Emotions representing states and actions arising from a state of mind are arranged on the outer edges of the concentric circles. The concept of emotion includes both affect and mental states. Emotions generally generated from reactions occurring in the brain are arranged on the left side of the concentric circles. Emotions generally induced by situational judgment are arranged on the right side of the concentric circles. Emotions generally generated from reactions occurring in the brain and induced by situational judgment are arranged on the upper and lower sides of the concentric circles. Furthermore, the emotion of "pleasure" is arranged on the upper side of the concentric circles, and the emotion of "discomfort" is arranged on the lower side. In this way, in the emotion map 400, multiple emotions are mapped based on the structure by which emotions are generated, and emotions that tend to occur simultaneously are mapped close to each other.

[1442] These emotions are distributed in the 3 o'clock direction on emotion map 400, and typically fluctuate between relief and anxiety. In the right half of emotion map 400, situational awareness dominates over internal sensations, resulting in a sense of calm.

[1443] The inside of emotion map 400 represents what is going on in the mind, and the outside of emotion map 400 represents behavior, so the further you go outside emotion map 400, the more visible the emotions become (the more they are expressed in behavior).

[1444] Human emotions are based on various balances, such as posture and blood sugar levels. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. Emotions can also be created for robots, automobiles, and motorcycles, based on various balances, such as posture and remaining battery life. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. An emotion map can be generated, for example, based on Dr. Mitsuyoshi's emotion map (Research on Voice Emotion Recognition and Emotional Brain Physiological Signal Analysis Systems, Tokushima University, Doctoral Dissertation: https: / / ci.nii.ac.jp / naid / 500000375379). The left half of the emotion map lists emotions belonging to the "reaction" domain, where sensation is dominant. The right half of the emotion map lists emotions belonging to the "situation" domain, where situational awareness is dominant.

[1445] The emotion map defines two emotions that promote learning. One is a negative emotion on the situation side, around the middle of "repentance" or "reflection." In other words, this occurs when the robot experiences negative emotions such as "I never want to feel this way again" or "I don't want to be scolded again." The other is a positive emotion on the response side, around "desire." In other words, this occurs when the robot experiences positive feelings such as "I want more" or "I want to know more."

[1446] The emotion identification model 59 inputs user input into a pre-trained neural network, obtains emotion values ​​indicating each emotion shown in the emotion map 400, and determines the user's emotion. This neural network is pre-trained based on multiple pieces of training data that are combinations of user input and emotion values ​​indicating each emotion shown in the emotion map 400. Furthermore, this neural network is trained so that emotions that are located close to each other have similar values, as in the emotion map 900 shown in FIG. 10. FIG. 10 shows an example in which multiple emotions, "relieved," "calm," and "reassuring," have similar emotion values.

[1447] The system according to the present disclosure has been described above mainly with respect to the functions of the data processing device 12, but the system according to the present disclosure is not necessarily implemented on a server. The system according to the present disclosure may be implemented as a general information processing system. The present disclosure may be implemented, for example, as a software program running on a personal computer or an application running on a smartphone, etc. The method according to the present disclosure may be provided to users in the form of SaaS (Software as a Service).

[1448] In the above embodiment, an example was given in which the specific processing is performed by one computer 22, but the technology of the present disclosure is not limited to this, and the specific processing may be distributed and performed by a plurality of computers including the computer 22. For example, the data generation model 58 may be provided in an external device of the data processing device 12, and data may be generated in the external device in accordance with input data.

[1449] In the above embodiment, an example in which the specific processing program 56 is stored in the storage 32 has been described, but the technology of the present disclosure is not limited to this. For example, the specific processing program 56 may be stored in a portable, computer-readable, non-transitory storage medium such as a USB (Universal Serial Bus) memory. The specific processing program 56 stored in the non-transitory storage medium is installed in the computer 22 of the data processing device 12. The processor 28 executes the specific processing in accordance with the specific processing program 56.

[1450] Alternatively, the specific processing program 56 may be stored in a storage device such as a server connected to the data processing device 12 via the network 54, and the specific processing program 56 may be downloaded and installed on the computer 22 in response to a request from the data processing device 12.

[1451] It is not necessary to store all of the specific processing program 56 in a storage device such as a server connected to the data processing device 12 via the network 54, or to store all of the specific processing program 56 in the storage 32; only a portion of the specific processing program 56 may be stored.

[1452] The hardware resource for executing a specific process can be any of the following processors: An example of a processor is a CPU, which is a general-purpose processor that functions as a hardware resource for executing a specific process by executing software, i.e., a program. Another example of a processor is a dedicated electrical circuit, such as an FPGA (Field-Programmable Gate Array), a PLD (Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit), which is a processor with a circuit configuration designed specifically for executing a specific process. Each processor has built-in or connected memory, and each processor uses the memory to execute the specific process.

[1453] The hardware resource that executes the specific processing may be configured with one of these various processors, or may be configured with a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA). Also, the hardware resource that executes the specific processing may be a single processor.

[1454] As an example of a system configured with a single processor, first, one processor is configured by combining one or more CPUs and software, and this processor functions as a hardware resource that executes a specific process. Second, there is a system that uses a processor that realizes the functions of an entire system including multiple hardware resources that execute a specific process on a single IC chip, as typified by SoC (System-on-a-chip). In this way, a specific process is realized using one or more of the above-mentioned various processors as hardware resources.

[1455] Furthermore, the hardware structure of these various processors can be, more specifically, an electric circuit that combines circuit elements such as semiconductor devices. The specific processing described above is merely an example. Therefore, it goes without saying that unnecessary steps may be deleted, new steps may be added, or the processing order may be rearranged, without departing from the spirit of the invention.

[1456] The above-described description and illustrations are a detailed explanation of the parts related to the technology of the present disclosure and are merely an example of the technology of the present disclosure. For example, the above description of the configuration, functions, actions, and effects is an explanation of an example of the configuration, functions, actions, and effects of the parts related to the technology of the present disclosure. Therefore, it goes without saying that unnecessary parts may be deleted, new elements may be added, or replacements may be made to the above-described description and illustrations within the scope of the gist of the technology of the present disclosure. Furthermore, to avoid confusion and facilitate understanding of the parts related to the technology of the present disclosure, the above-described description and illustrations omit explanations of common technical knowledge that do not require particular explanation to enable the implementation of the technology of the present disclosure.

[1457] All publications, patent applications, and technical standards mentioned in this specification are herein incorporated by reference to the same extent as if each individual publication, patent application, or technical standard was specifically and individually indicated to be incorporated by reference.

[1458] The following is further disclosed regarding the above embodiment.

[1459] (Claim 1)

[1460] means for receiving production information input by a user;

[1461] means for storing the received production information in a database;

[1462] a means for managing the progress status of the production;

[1463] A means to alert designated members when progress status changes;

[1464] A means to periodically check the planned revision dates of revised items,

[1465] A means to generate and notify reminder alerts when revisions are approaching;

[1466] A system including:

[1467] (Claim 2)

[1468] 2. The system according to claim 1, wherein the means for managing the progress status is means for checking a database at specific intervals to confirm the progress status of each product.

[1469] (Claim 3)

[1470] 2. The system according to claim 1, wherein the means for checking the scheduled revision date is means for generating a reminder alert three months before the scheduled revision date and notifying the designated registered member of the alert.

[1471] "Example 1"

[1472] (Claim 1)

[1473] means for receiving production information input by a user;

[1474] means for storing the received production information in a database;

[1475] a means for managing the progress status of the production;

[1476] A means to alert designated members when progress status changes;

[1477] A means to periodically check the planned revision dates of revised items,

[1478] A means to generate and notify reminder alerts when revisions are approaching;

[1479] means for verifying a user's authentication information and generating a session authentication token;

[1480] A means for generating a project ID and storing it together with the production information;

[1481] A means to check the database at regular intervals to update the progress status,

[1482] A means to notify target members in real time when status is updated,

[1483] A system including:

[1484] (Claim 2)

[1485] 2. The system according to claim 1, wherein the means for managing the progress status is means for checking a database at specific intervals to confirm the progress status of each product.

[1486] (Claim 3)

[1487] 2. The system according to claim 1, wherein the means for checking the scheduled revision date is means for generating a reminder alert three months before the scheduled revision date and notifying the designated registered member of the alert.

[1488] "Application Example 1"

[1489] (Claim 1)

[1490] means for receiving production information input by a user;

[1491] means for storing the received production information in a database;

[1492] a means for managing the progress status of the production;

[1493] A means to alert designated members when progress status changes;

[1494] A means to periodically check the planned revision dates of revised items,

[1495] A means to generate and notify reminder alerts when revisions are approaching;

[1496] a means for providing information in real time using a display device that can be worn as a terminal;

[1497] a means for notifying the user when progress status and reminder alerts are displayed on the display device;

[1498] A system including:

[1499] (Claim 2)

[1500] 2. The system according to claim 1, wherein the means for managing the progress status is means for checking a database at specific intervals to confirm the progress status of each product.

[1501] (Claim 3)

[1502] 2. The system according to claim 1, wherein the means for checking the scheduled revision date is means for generating a reminder alert three months before the scheduled revision date and notifying the designated registered member of the alert.

[1503] "Example 2: Combining Emotion Engines"

[1504] (Claim 1)

[1505] means for receiving production information input by a user;

[1506] a means for storing the received production information in a database;

[1507] a means for monitoring the progress of the production;

[1508] A means to notify designated members of an alert when there is a change in progress status;

[1509] A means to regularly check the planned revision dates for revised items,

[1510] A means to generate and notify reminder alerts when revisions are approaching;

[1511] means for recognizing a user's emotion;

[1512] A means to tailor notification content and priorities based on perceived emotions; and

[1513] A system including:

[1514] (Claim 2)

[1515] 2. The system of claim 1, wherein the means for monitoring the progress of each product checks the database at specific intervals to ascertain the progress of each product.

[1516] (Claim 3)

[1517] 2. The system according to claim 1, wherein the means for checking the scheduled revision date is means for generating a reminder alert three months before the scheduled revision date and notifying the designated registered member of the alert.

[1518] (Claim 4)

[1519] 2. The system according to claim 1, wherein the emotion recognition means is a means for capturing a picture of the user's face with a camera and analyzing voice and text input in real time.

[1520] (Claim 5)

[1521] 2. The system according to claim 1, wherein the means for adjusting the notification content or priority is means for lowering the urgency of the alert or reducing the notification frequency based on the recognized emotion.

[1522] "Application example 2 when combining emotion engines"

[1523] (Claim 1)

[1524] means for receiving production information input by a user;

[1525] means for storing the received production information in a database;

[1526] a means for managing the progress status of the production;

[1527] A means to alert designated members when progress status changes;

[1528] A means to periodically check the planned revision dates of revised items,

[1529] A means to generate and notify reminder alerts when revisions are approaching;

[1530] A means for recognizing a user's emotions and adjusting notification content and priority based on the emotions;

[1531] A system including:

[1532] (Claim 2)

[1533] 2. The system according to claim 1, wherein the means for managing the progress status is means for checking a database at specific intervals to confirm the progress status of each product.

[1534] (Claim 3)

[1535] 2. The system according to claim 1, wherein the means for checking the scheduled revision date is means for generating a reminder alert three months before the scheduled revision date and notifying the designated registered member of the alert. [Explanation of symbols]

[1536] 10, 210, 310, 410 Data Processing Systems 12 Data Processing Device 14 Smart Devices 214 Smart Glasses 314 Headset-type terminal 414 Robot< / url:> < / url:> < / url:> < / url:>

Claims

1. means for receiving production information input by a user; means for storing the received production information in a database; a means for managing the progress status of the production; A means to alert designated members when progress status changes; A means to periodically check the planned revision dates of revised items, A means to generate and notify reminder alerts when revisions are approaching; A system including:

2. 2. The system according to claim 1, wherein said means for managing the progress status is means for checking a database at specific intervals to confirm the progress status of each product.

3. 2. The system according to claim 1, wherein said means for checking the scheduled revision date is means for generating a reminder alert three months before the scheduled revision date and notifying designated registered members of the alert.

Images