WO2020154297A1

WO2020154297A1 - Automated time monitoring system and methods of use

Info

Publication number: WO2020154297A1
Application number: PCT/US2020/014421
Authority: WO
Inventors: Peter H. WINSLOW; Daniel B. WINSLOW
Original assignee: Otmail Llc
Priority date: 2019-01-22
Filing date: 2020-01-21
Publication date: 2020-07-30

Abstract

An automated time monitoring system is provided to receive a message for a recipient user interface and compare the time of the message to a pre-defined OT profile of the recipient user such that (i) if the time of the message is not in the OT profile time of the recipient user communicate the message to the recipient user interface, and (ii) if the time of the message is in the OT profile time of the recipient user, log the message as an OT event and communicate the message to the recipient user interface. In some embodiments, if the time of the message is in the OT profile time of the recipient user, the message is stored in a message queue and communicated to the recipient user interface outside the OT profile time of the recipient user.

Description

AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

TITLE OF THE INVENTION:

AUTOMATED TIME MONITORING SYSTEM AND METHODS OF USE

CROSS-REFERENCE TO RELATED APPLICATIONS:

[0001] This application claims benefit of U.S. Pat. App. No. 62/795,374 filed on Jan. 22, 2019 entitled“AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE” and the entire contents of which are herein incorporated by reference.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT:

[0002] Not Applicable.

REFERENCE TO SEQUENCE LISTING, A TABLE, OR A COMPUTER PROGRAM

LISTING COMPACT DISC APPENDIX:

[0003] Not Applicable.

BACKGROUND:

[0004] 1. Field.

[0005] This invention relates to electronic communications systems, in particular, electronic messaging systems configured to automatically monitor and log messaging activities against pre-defined profiles of message recipients.

[0006] 2. Description of the Prior Art.

[0007] Business establishments often use identification badges and timecards to track and manage employee time. Common timekeeping methods use personal computer (PC) terminals, mobile phones and time clocks that are interconnected via wired connections to track employee time. In order to track their time, employees typically gain access to the PC terminal by entering an identification code (and possibly a password) or scanning their identification badge. The PC terminal communicates with the time clocks to obtain timing information and record the employee check in/out time. These clock-based systems typically rely on the user to manually enter their time which is not always done. AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

[0008] Furthermore, these clock-based systems are not always integrated into other systems that the user uses throughout their working day.

BRIEF SUMMARY OF THE INVENTION:

[0009] The following summary is included only to introduce some concepts discussed in the Detailed Description below. This summary is not comprehensive and is not intended to delineate the scope of protectable subject matter, which is set forth by the claims presented at the end.

[0010] In one example embodiment, a method of automated time monitoring is provided, the method comprising: receiving a message for a recipient user; the message identifying a time for the message; an OTM user profile defining an OT profile time of the recipient user; and comparing the time of the message to the OTM user profile of the recipient user to determine whether the time is within the OT profile time of the recipient user. In some embodiment, the method further comprises if the time of the message is not in the OT profile time of the recipient user communicating the message to a recipient user interface of the recipient user; and if the time of the message is in the OT profile time of the recipient user, logging the message as an OT event and communicating the message to the recipient user interface.

[0011] In one example embodiment, a method of automated time monitoring is provided, the method comprising: receiving a message for a recipient user interface of a recipient user; and comparing a time of the message to an OTM user profile of the recipient user whereby: if the time of the message is not in the OT profile time of the recipient user communicating the message to the recipient user interface, and if the time of the message is in the OT profile time of the recipient user, storing the message in a message queue and communicating the message to the recipient user interface outside the OT profile time of the recipient user.

[0012] In some embodiments, the methods may further comprise the message for the recipient user received from a sending user interface; and if the time of the message is in the OT profile time of the recipient user, giving the sending user interface the ability to communicate an override to communicate the message to the recipient user interface whereby: if the sending user interface communicates the override, logging the message as an OT event and communicating the message to a recipient user interface of the recipient user, and if the sending user interface AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE does not communicate the override, storing the message in a message queue and communicating the message to the recipient user interface outside the OT profile time of the recipient user.

[0013] In one example embodiment, a method of automated time monitoring is provided, the method comprising: receiving a request to communicate a message from a first user interface of a first user to a second user interface of a second user; and comparing a time of the message to an OT profile time of an OTM user profile of the second user and determining whether the time of the message is in the OT profile time of the second user: if the time of the message is not in the OT profile time of the second user communicating the message to the second user interface, and if the time of the message is in the OT profile time of the second user, giving the first user interface the ability to communicate an override to communicate the message to the second user device: if the first user interface communicates the override, logging the message as an OT event and communicating the message to the second user interface, and if the first user interface does not communicate the override, storing the message in a message queue and communicating the message to the second user interface outside the OT profile time of the second user.

[0014] In some embodiments, the message is an email message.

[0015] In some embodiments, the message is a text message.

[0016] In some embodiments, the message is a digital communication.

[0017] In some embodiments, the time of the message comprises a delivery time of the message.

[0018] Other objects, features, and advantages of the techniques disclosed in this specification will become more apparent from the following detailed description of embodiments in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS:

[0019] In order that the manner in which the above-recited and other advantages and features of the invention are obtained, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which: AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

[0020] FIG. 1A shows a process diagram illustrating the general concepts of one embodiment of methods of automated time monitoring;

[0021] FIG. IB shows a process diagram illustrating the general concepts of one embodiment of methods of automated time monitoring;

[0022] FIG. 2 shows a functional software diagram illustrating one example embodiment of an automated time monitoring system;

[0023] FIG. 3 shows a functional software diagram illustrating one example embodiment of an automated time monitoring system;

[0024] FIGS. 4A-4B show example embodiments of administrative interfaces of an automated time monitoring system with FIG. 4A showing an example company administration page and FIG. 4B showing an example individual user’s administration page;

[0025] FIGS. 5A-5G show example embodiments of screen shots of the user interfaces as users use an automated time monitoring system;

[0026] FIG. 6 shows an example embodiment of a monthly metrics report; and

[0027] FIG. 7 illustrates one example embodiment of a computer system suitable for an automated time monitoring system.

DETAILED DESCRIPTION OF THE INVENTION:

[0028] COPYRIGHT NOTICE: A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to any software and data as described below and in the drawings hereto: Copyright © 2018, OTMail LLC, All Rights Reserved.

[0029] Automated time monitoring systems and methods will now be described in detail with reference to the accompanying drawings. It will be appreciated that, while the following description focuses on a system that automatically monitors email and text messaging systems, the systems and methods disclosed herein have wide applicability. For example, the systems and methods disclosed may be used with any type of digital communications including, but not limited to, emails, texts, digital messages and messages from applications such as Snapchat, social media Direct Messages, and other future technologies that utilize digital messaging AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE application that transmits communications to users. Notwithstanding the specific example embodiments set forth below, all such variations and modifications that would be envisioned by one of ordinary skill in the art are intended to fall within the scope of this disclosure.

[0030] As used herein, the term "module" refers to hardware and/or software

implementing entities and does not include a human being. The operations performed by the "module" are operations performed by the respective hardware and/or software implementations, e.g. operations that transform data representative of real things from one state to another state, and these operations do not include mental operations performed by a human being.

Technical Problem.

[0031] One of the technical problems associated with the current state of the art is how to automatically recognize and block, queue or log message events that occur outside of a time window such as normal working hours of a user. Current solutions may have shared calendars, or the user may have to manually check the hours an individual is working to keep from messaging someone on their time off. However, these solutions do not integrate a solution that recognizes a pre-defined profile time of a user, and then monitors and processes messages to that user according to pre-defined rules that include the ability to forward or block and queue the message. And no known solution uses these pre-defined rules to automatically credit, such as a payment credit, a recipient for receiving and/or acting on the message during a certain pre defined profile time. And no known solution uses these pre-defined rules to automatically create attributes for the user analysis of the user or organization’s communication characteristics.

Technical Solution.

[0032] While existing email systems and software allow recipients to limit the hours in which incoming emails are received or allow senders to time when outgoing messages are delivered, the disclosed time monitoring systems can block the receipt of messages that fall outside of a pre-defined time window (e.g., a normal working hours window) or when messages are sent outside of that pre-defined time window (e.g., in an overtime (or“OT”) window outside of normal working hours), the system allows for the tracking for additional compensation or reward to employees for each such messages received and/or replied to. Furthermore, the disclosed time monitoring system may provide alerts when messages are due to be sent to a AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE recipient during an OT profile window and it may further allow the sender to override the normal email receiving restrictions of the intended recipient.

[0033] The technical solution includes a time monitoring system configured to monitor and recognize messages that are sent to and from users of the system and process these messages according to a set of pre-defined system rules. The pre-defined rules include rules that recognize whether the time the message is originally sent (message time) is within the pre-defined time window of the recipient and then processes the message accordingly. The pre-defined rules are applied to each user according to a pre-defined user profile that defines such attributes as the pre defined OT profile time window of the recipient. The pre-defined rules may also apply rules based on pre-defined profile attributes of the sender. The pre-defined rules may also recognize when messages are sent or acted upon by users during pre-defined time windows and may log and later provide a credit to the user for receiving or action upon those messages.

Practical Application.

[0034] The disclosed automated time monitoring systems, also called an OTMail system (the“system” or“OTM system”) and its methods of use have several practical applications. For example and not for limitation, the OTM system provides an automated way to keep a worker’s messaging attention limited to a certain time profile such as a set of working hours. The system also provides a way to automatically track and/or reward workers for acting on messages outside of that certain time profile. Also, by defining and automatically capturing metrics related to a worker’s messaging versus their OT time profile, the OTM system can provide consolidated reports on this type of activity for each worker, other message senders and recipients as well as reports on statistics and trends across a larger population of OTM system users.

[0035] Some embodiments of the OTM system create a business method that can automatically (a) improve the recruiting, retention and recharging of human capital talent by creating market incentives for companies to adhere to a defined work day for improved work-life balance and for adequate time away from work for employees; and (b) apply the time-value of work for salaried employees that already exist for wage-earner employees who are required to work more than 40 hours weekly, on weekends or holidays by defining the employer-employee bargain by reference to both salary and time required for work rather than solely salary; and (c) create a new employee benefit for work required to be performed outside defined work days or defined working hours. AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

[0036] The disclosed OTM system provides the practical application of allowing companies to improve their recruiting, retention and recharging of their human capital talent pool by shaping company culture and working hours to conform to improved work-life balance and ensuring that employees have adequate time off from work. Similar to medical co-pays, which shape behavior in utilization of medical care, the compensation/reward cost to send employees after hours messages creates an incentive for people managers not to engage in such practice unless necessary for the company’s interests. There are numerous studies and reports supporting the premise that employee productivity and happiness are improved by time away from work during the course of their day.

[0037] Significantly, the disclosed time monitoring system also provides the practical application of enabling companies to better understand and control their people managers’ abilities to manage and utilize teams to best effect by real-time analytics that are an improvement over current employee attrition data. Rather than understanding which teams are losing talent after employees have already left the company, the time monitoring system analytics enable company knowledge of which employees are at risk of overwork, which people managers best utilize their team talent during regular working hours, and which people managers’ requests for more FTE headcount are supported by the system data and analytics to prevent loss of talent.

[0038] The disclosed OTMail system is a processor based system configured to integrate with and provide the described enhancements to messaging systems, such as but not limited to Gmail, Thunderbird, Outlook, Exchange and Microsoft Office 365, to deliver email to employees’ email inboxes only during defined working hours on defined work days, except when the sender is authorized by the company to override the limitation on sending messages in which case the messages can be delivered at any time and the receiving employee is entitled to receive additional defined compensation or reward for each message overridden to their message inbox/client outside the pre-defined working hours or work days.

[0039] The disclosed time monitoring system unconventionally integrates novel features with elements of messaging systems and concepts of time tracking systems to provide a solution that improves both messaging systems and time tracking systems. This solution is particularly useful for the management of employees working remotely and are engaged to coordinate work tasks through messaging systems. This solution is also particularly useful for employee AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE management systems when employees are working with others around the globe and it is not easy to determine whether work times overlap.

One Example Embodiment of the Automated Time Monitoring System:

[0040] Referring to FIG. 2, embodiments of the automated time monitoring system 200 generally comprise a first client device 220 to send messages, a message server 240 to monitor and process the messages 288, a second client device 290 intended to be the recipient of messages from the sender and a communication network 295 (e.g., the Internet) to allow the system components to communicate with each other.

[0041] It is understood that messages may include any type of digital communications including, but not limited to, emails, texts, and message from applications such as Snapchat, social media Direct Messages, and other future technologies that utilize digital messaging application that transmits communications to users.

[0042] It is also understood that the sending of messages, in addition to the normal definition of the term in the art, may include any type of communication of a message to an interface of a user. For example only and not for limitation, the sending of the message may be the communication of the message to a message client interface of a user or it may be allowing the message to be viewed by a client, such as web browser interface, from a messaging server.

[0043] As shown in FIG. 2, the client device 220 generally comprises a message client 222 having an OTM client plugin 244. The message client 222 provides the normal messaging functionality of sending and receiving messages over a network 295 such as the Internet as well as storing, viewing and retrieving messages. The OTM client plugin 224 includes the features that communicate with the message server 240. For example, the OTM client plugin 224 may include a user interface 226 with interfaces features such as an OTM flagger 227 that present the user with alerts that the message time is in the OT profile time of the recipient and may further include interface features such as an OTM override flagger 228 that presents the user with the ability to communicate and override the queuing of the message during the OT profile time and send the message. The OTM client plugin 224 may also provide unique interface features that allow the user to provide user profile information from the client device.

[0044] The message server 240 generally comprises the normal messaging server functionality of receiving, forwarding and otherwise communicating messages 288 from client devices such as client device 20 over a network 295 such as the Internet. The message server AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

240 also stores message server data in the message database 260 and may communicate with its message applications and other applications through APIs 280.

[0045] In the embodiment shown, the message server 240 further comprises an OTM server application 250 that comprises the elements to monitor and process messages 288 according to the pre-defined OTM rules 266. The OTM server application 250 utilizes the message server APIs 280 to monitor messages 288 being sent to recognize those messages flagged as belonging to a user or organization having an OTM user profile 262. The OTM server application 250 may include an OT checker module 252 to check the message time with the OT profile time of the recipient, here client device 292. The OTM server application may include an alert sender module 251 to notify the sender that the message time is in the recipient’s OT profile time window. The OTM server application may include an OTM forwarder module 254 to recognize if a sender has properly provided an override to send the message even if in the recipient’s OT profile time window. The OTM server application 250 may also include an OTM log module 265 to log OTM server application actions such as logging when a recipient is sent messages during their OT profile time. The OTM server application 250 may include a reporter module 253 to provide reports on OTM server application actions and OTM log data.

[0046] Within the message server 240, the message database 260 generally stores message server information such as but not limited to user/company profiles 262, message queues 264, messages 288 and message logs 285.

[0047] Within the message server 240, the message transport module 242 generally comprises those elements that receive, forward or otherwise communicate messages 288 from the data network 295. The message application module and APIs 280 generally comprise those elements that allow the message server 240 to monitor, process and act on messages 288. The message log module 285 generally comprises those elements that log message server activities. The periodic checker module 283 generally comprises those functional element of the message application that recognizes messages 288 being in a message queue 264 due to scheduling rules and periodically checks those messages 288 against a schedule such as in a user profile 262 and sends the messages 288 when the scheduling rule is satisfied.

[0048] In yet another embodiment of the automated time monitoring system, as shown in FIG. 3, the system 300 may have components distributed in a manner that supports business models such as a Software as a Service (SaaS) model. As shown in this FIG. 3, the message AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE server 380 components may be separated from the OTM server 340 components over a communication network 395. In this embodiment, the OTM server 340 functions may be provided at one location by one service provider and the message server 380 functions may be provided at another location by another service provider. This example embodiment may allow a message service provider system (e.g., Gmail, Exchange or Office365) to provide the normal messaging functionality while a specialized OTM server service provider may provide the special functionality of the OTM system by communicating with the message server.

[0049] Referring to FIG. 3, the function of the client device 320 is generally similar to that described above with respect to FIG. 2. The client device may comprise a message client 322 having an OTM client plugin 344. The message client 320 provides the normal messaging functionality of sending, receiving and otherwise communicating messages over a network 395 as well as storing, viewing and retrieving messages. The OTM client plugin 324 includes the features that communicate with the message server 340 and may include a user interface 326 with interfaces features such as an OTM flagger 327, an OTM override flagger 328 and unique interface features that allow the user to provide user profile information from the client device similar to those described for FIG. 2.

[0050] In the embodiment shown in FIG. 3, the message server 380 generally comprises the normal messaging server functionality of receiving, forwarding and communicating messages 388 from the client device 320 through the OTM server 340 over a network 395 such as the Internet to a receiving client device 390. The message server 380 may also store message server data in a message server database 389 and may communicate with its message

applications and other applications through APIs 391. Within the message server 380, a message database 389 generally stores message server information such as but not limited to

user/company profiles 382, message queues 384, messages 388 and message logs 385. Within the message server 380, the message transport module 386 generally comprises those elements that receive and forward messages 388 from the data network 395. The message application module and API 391 generally comprise those elements that allow the message server 380 to monitor, process and act on messages 388. The message logger module 387 generally comprises those elements that log message server activities and stores them in the message log 385. The periodic checker module 383 generally comprises those functional element of the message application that recognizes messages 388 being in a message queue 384 due to scheduling rules AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE and periodically checks those messages 388 against a schedule such as in a user profile 382 and sends the messages 388 when the scheduling rule is satisfied. The message queuer module 381 may recognize those messages 388 that should be queued in the message server database 389 for communication later. The user profile 382 may contain profile information specific to the OTM application or the message server 380 may look to the user profile 362 of the OTM database for user profile information.

[0051] In the embodiment shown in FIG. 3, the automated time monitoring system 300 further comprises an OTM server 340 having an OTM server application and APIs 350 and an OTM database 360. The OTM server application 350 generally comprises the elements to monitor, process and communicate messages 388 according to the pre-defined OTM rules. The OTM server database generally stores the information for use by the message server 380 and the OTM server application 350.

[0052] As shown, the OTM server 340 utilizes an OTM server application and APIs 350 to monitor messages 388 being sent to recognize those messages flagged as belonging to a user or organization having an OTM user profile 362. The OTM server application 350 may include an OT checker module 352 to check the message time with the OT profile time of the recipient. The OTM server application 350 may include an alert sender module 351 to notify the sender that the message time is in the recipient’s OT profile time window. The OTM server application 350 may include an OTM forwarder module 356 to recognize if a sender has properly provided an override to communicate the message even if in the recipient’s OT profile time window. The OTM server application 350 may also include an OTM logger module 359 to log OTM server application actions such as logging when a recipient is communicated messages during their OT profile time. The periodic checker module 358 generally comprises those functional element of the message application that recognizes messages 388 being in a message queue 364 due to scheduling rules and periodically checks those messages 388 against a schedule such as in a user profile 362 and sends the messages 388 when the scheduling rule is satisfied.

[0053] As shown, the OTM database 360 may comprise a data store for information such as user profiles 362, message queues 364 and OTM logs 365. The OTM rules 366 comprise the OTM rules that dictate features of the OTM service. For example and not for limitation, the OTM rules 366 may define whether OT overrides are possible, what the normal work hours for users are and what type of rewards or credits users will get for receiving OT AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE messages. The user profiles 362 include profile information for each user to allow the system to recognize, log and credit that user according to the OTM rules. For example, the user profile 362 and may include information such as the individual’s work hours. The message queue 364 may include those messages that are being held in a queue until the OTM rules 366 allow the message to be communicated or sent to the user. Messages 388 being held in a queue may also be held in the queue 384 of the message server database 389 until being communicated or sent.

[0054] The OTM server application may also include a reporter module 353 to provide reports on OTM server application actions and OTM log data.

[0055] One example embodiment of the automated time monitoring system generally comprises the functional elements of FIGS. 2 and 3 in a software program product to be executed by a computer implemented system.

[0056] As will be readily apparent to those skilled in the art, automated time monitoring systems and methods can be embodied in hardware, software, or a combination of hardware and software. For example, a computer system or server system, or other computer implemented apparatus combining hardware and software adapted for carrying out the methods described herein, may be suitable. One embodiment of a combination of hardware and software could be a computer system with a computer program that, when loaded and executed, carries out the respective methods described herein. In some embodiments, a specific use computer, containing specialized hardware or computer programming for carrying out one or more of the instructions of the computer program, may be utilized. In some embodiments, the computer system may comprise a device such as, but not limited to a digital phone, cellular phone, laptop computer, desktop computer, digital assistant, server or server/client system.

[0057] Computer program, software program, program, software or program code in the present context mean any expression, in any language, code or notation, of a set of instructions readable by a processor or computer system, intended to cause a system having an information processing capability to perform a particular function or bring about a certain result either directly or after either or both of the following: (a) conversion to another language, code or notation; and (b) reproduction in a different material form. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

[0058] FIG. 7 is a schematic diagram of one embodiment of a computer system 700 by which the environmental system reaction methods may be carried out. The computer system 700 can be used for the operations described in association with any of the computer implemented methods described herein. The computer system 700 includes at least one processor 710, a memory 720 and an input/output device 740. Each of the components 710, 720, and 740 are operably coupled or interconnected using a system bus 750. The computer system 700 may further comprise a storage device 730 operably coupled or interconnected with the system bus 750.

[0059] The processor 710 is capable of receiving the instructions and/or data and processing the instructions of a computer program for execution within the computer system 700. In some embodiments, the processor 710 is a single-threaded processor. In some embodiments, the processor 710 is a multi-threaded processor. The processor 710 is capable of processing instructions of a computer stored in the memory 720 or on the storage device 730 to

communicate information to the input/output device 740. Suitable processors for the execution of the computer program instruction include, by way of example, both general and special purpose microprocessors, and a sole processor or one of multiple processors of any kind of computer.

[0060] The memory 720 stores information within the computer system 700. Memory 720 may comprise a magnetic disk such as an internal hard disk or removable disk; a magneto optical disk; an optical disk; or a semiconductor memory device such as PROM, EPROM, EEPROM or a flash memory device. In some embodiments, the memory 720 comprises a transitory or non-transitory computer readable medium. In some embodiments, the memory 720 is a volatile memory unit. In another embodiments, the memory 720 is a non-volatile memory unit.

[0061] The processor 710 and the memory 720 can be supplemented by, or incorporated in, ASICs (application- specific integrated circuits).

[0062] The storage device 730 may be capable of providing mass storage for the system 700. In various embodiments, the storage device 730 may be, for example only and not for limitation, a computer readable medium such as a floppy disk, a hard disk, an optical disk, a tape device, CD-ROM and DVD-ROM disks, alone or with a device to read the computer readable medium, or any other means known to the skilled artisan for providing the computer program to AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE the computer system for execution thereby. In some embodiments, the storage device 730 comprises a transitory or non-transitory computer readable medium.

[0063] In some embodiments, the memory 720 and/or the storage device 730 may be located on a remote system such as a server system, coupled to the processor 710 via a network interface, such as an Ethernet interface.

[0064] The input/output device 740 provides input/output operations for the system 700 and may be in communication with a user interface 740A as shown. In one embodiment, the input/output device 740 includes a keyboard and/or pointing device. In some embodiments, the input/output device 740 includes a display unit for displaying graphical user interfaces or the input/output device 740 may comprise a touchscreen. In some embodiments, the user interface 740A comprises devices such as, but not limited to a keyboard, pointing device, display device or a touchscreen that provides a user with the ability to communicate with the input/output device 740.

[0065] The computer system 700 can be implemented in a computer system that includes a back-end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of them. The components of the system can be connected by any form or medium of digital data communication such as a communication network. Examples of communication networks include, e.g., a LAN, a WAN, wireless phone networks and the computers and networks forming the Internet.

[0066] One example embodiment of the automated time monitoring systems and methods may be embodied in a computer program product, the computer program product comprising a computer readable medium having a computer readable program code tangibly embodied therewith, the computer program code configured to implement the methods described herein, and which, when loaded in a computer system comprising a processor, is able to carry out these methods.

One Embodiment of Methods to Automate Time Monitoring:

[0067] The method to use an automated time monitoring system generally comprises receiving a request to communicate a message from a first user interface to a second user interface, comparing a time of the message to an OTM system user profile of the second user in AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE the profile of the second user and determining whether the time of the message is in an OT profile time from the OTM system user profile of the second user. If the time of the message is not in the OT profile time of the second user, communicating or sending the message to the second user; and if the time of the message is in the OT profile time of the second user, logging the message as an OT event and treating it according to pre-defined rules for OT events. The pre-defined rules for OT events may allow the message to be communicated to the second user as an OT event or the pre-defined rules for OT events may put the message in a message queue to be communicated to the second user interface outside the OT profile time of the second user. Optionally, the methods may give the first user interface the ability to select or otherwise communicate an override to communicate the message to the second user interface. In this case, if the first user interface communicates the override, logging the message as an OT event and communicating the message to the second user interface, and if the first interface user does not communicate the override, storing the message in a message queue and communicating the message to the second user interface outside the OT profile time of the second user.

[0068] In some embodiments, the OT event may be logged and may generate a credit or other action to one of the recipient or sender of the message. For example, the recipient of the message may receive a financial reward for receiving and/or acting on messages received during their OT profile time. As another example, the sender may receive a penalty for sending messages during the recipient’s OT profile time. The credits and other actions to be associated with an OT event may be any time of credit or action such as but not limited to financial credits such as additional pay, recognition awards or additional time off. Credits and other actions to be associated with an OT event may be generated automatically or they may be generated by system components such as the reporter module.

[0069] For illustration purposes and not for limitation, one example embodiment of the present invention is shown in FIGS. 1A and IB. As shown in FIG. 1A, this example method of using an automated time monitoring system generally comprises determining whether a message to be sent to a recipient is being sent within the receiver’ s OT profile time window and (i) if it is not, sending the message and (ii) if it is, log the messages as an OT event and send the message. Optionally, as shown, the methods may allow or require an override decision to be made, for example by the sender, and (i) if the override is selected, the message is logged as an OT event and the message is sent and (ii) if the override is not selected, the message is put into a message AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE queue to be sent later. If the message is put into the queue, the system may periodically check the time against the receiver’ s OT profile time window and when the time it outside of that window, the message will be sent.

[0070] Walking through the process 100 shown in FIG. 1A, OTM user profiles are defined or otherwise associated with users at 110. These profiles are used as the rules associated with messages sent and received through the OTM system and may include an OT profile time for each user.

[0071] At 120, a user requests to send a message to a recipient. The message is sent over the communication network utilizing the normal functionality of the messaging server.

[0072] At 140, the OTM system features check the message time (the time the message is being sent or will be delivered) against the pre-defined OT profile time of the recipient. As shown, if the message time is not in the OT profile time (e.g., is in normal work hours), the message is sent at 185.

[0073] As shown, if the message time is within the OT profile time, additional steps may be taken. The message may be logged at 160 as an OT event and the message may be forwarded at 185. The OTM system may also default to blocking or queue messages (see 180) sent during the recipient’s OT profile time to be forwarded when they are not in the OT profile time.

[0074] Optionally, the OTM system may provide the ability for the sender to override the blocking or queuing of messages so that they can be forwarded to the recipient. As shown, if the user overrides the blocking/queuing, the OTM system will log the message as an OT event at 160 and forward the message at 185. If the user does not, or cannot override, the message will be blocked or queued at 180 to be sent later when the time is outside of the OT profile time of the recipient. The OTM system may log certain OT events, such as overrides at 165 as an OT override to be processed according the OTM rules.

[0075] The OTM system may also provide the functionality to provide analysis and reports on OTM system activities. In particular, the OTM system may recognize OT events similar to“over-time” work and give credits, such as extra pay, for recipients of messages identified as OT events. The OTM system may also provide credits for messages, such as replies to messages, as OT events.

[0076] As illustrated in FIG. IB, another embodiment of the method of using an automated time monitoring system com comprises activities illustrated through client-side and AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE server-side activities. As shown, the client 120 generally communicates with the message server 140. The message server 140 may comprise a service application and database 150 as well as messaging servers such as the SMTP mail servers 180 shown. The methods may comprise the user performing a login at 102. With the login, the service application 150 checks the user credentials against the user profiles 162 and shares permissions with the client 120. When the client composes and attempts to communicate a message at 104, the attempt is communicated to the service application 150 that checks at the status of the user at 152 to see whether the delivery is being attempted in or out of the OT profile time. If the delivery is outside of the OT profile time, during normal hours, the message s forwarded to the mail server 180 to be sent. If the delivery is within the OT profile time, the delivery is flagged and logged as an OT event at 160and the message is not sent but normally put into a message queue to be sent later according to OTM rules. As an OT event, the sending client may be notified at 105 and the sending client 120 may be able to select options on what to do. One option, event response 1, may be to override the OT event and communicate the message now at 106. With this option, the override may be logged so that credit may be provided to the user later. Another option, event response 2, may be to allow the service application 150 to store the message in a message queue to be sent later at 108. With this option event response 2, the service application may periodically check the time against the user profile and OTM rules at 158 until a time that is OK to send. At that time, the message is then communicated by the mail server 180.

[0077] In some embodiments, the OTM system may be configured to control the delivery of a selected amount, or all, of the digital communications to users to include personal communications, work communications or both. For example only and not for limitation, a user could configure their profile so that all emails to them during their OT profile time could be blocked or queued unless an override is made. In some embodiments, the override may provide a credit or payment for the user to receive the communication. For example and not for limitation, a user who has defined all email to be blocked during the OT profile time, unless a payment is made for an override.

[0078] In some of these embodiments, a payment service such as PayPal may be used to provide the credit to the user for receiving the message. In some of these embodiments, the user may be able to define and modify the attributes (e.g., payment) needed to allow the override. In AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE some of these embodiments, a third-party provider may define and modify the attributes needed to allow the override.

One Embodiment of the Automated Time Monitoring System in Operation:

[0079] For purposes of illustrating the operation of one embodiment of an automated time monitoring system, and not for limitation, the operation of an automated time monitoring assembly for email messages is described.

[0080] Referring to FIGS. IB and 5A-5G, the process of operation generally starts with the user logging into the system. With the user credentials being shared with the message server, profiles and permissions for the user are associated with the client for that user.

[0081] From the sender’s client, the first user (sender) composes and attempts to send an email. The message server receives the request to send a message from the sender to a second user (recipient) and checks the OTM database and the recipient’s OTM user profile to compare, with an OT checker module, the time of the message to an OTM user profile of the recipient. From this comparison, the system determines whether the time of the message is in the OT profile time of the recipient and treats the message according to the pre-defined OT event rules. If the time of the message is not in the OT profile time of the recipient (e.g., it is normal work hours), the message server sends the email with a message transport module. If the time of the message is in the OT profile time of the recipient (e.g., not normal work hours), the OT event rules may allow the message to be sent to the recipient as an OT event or the OT event rules may store the message in a message queue and send the message to the recipient outside of the OT profile time of the recipient.

[0082] Optionally, the system may give the sender the options for the message if the message time is in the receiver’s OT profile time. For example, an alert sender module may recognize the message time being sent during the receiver’s OT profile time and alert the sender that the message time is in the OT profile time of the recipient and the system may allow the sender to select an override to send the message to the recipient. In this embodiment, if the override is selected, the system logs the message as an OT event in an OTM log and sends the message to the recipient. If the sender does not select the override, the system stores the message in a message queue and sends the message to the recipient outside of the OT profile time of the recipient. Whether the sender has the ability to select an override may be a profile element of the user whereby some users have that ability and some users do not. AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

[0083] FIG. 4A shows an example embodiment of a company administration page as may be shown to the company administrator on a user interface. As an example, this page shows scope of service options including but not limited to: turning the system features on or off, the scope of messages monitored and processed by the system, the scope of employees having messages monitored and processed by the system, the ability to provide OT profile times and days for employees (e.g., time outside of identified work hours), the ability for user to request override authority and the ability to pre-define rewards for the employee for OT events.

[0084] FIG. 4B shows an example embodiment of an employee administration page as may be shown to an employee user on their device user interface. As an example, this page shows scope of service options including but not limited to: turning the system features on or off, the scope of messages monitored and processed by the system, the ability of the employee user to define their OT profile times and days (e.g., time outside of identified work hours) and the ability to request override authority.

[0085] FIGS. 5A-5G show example user interface screens as administrators and users may see while using the system. FIG. 5A shows an example user interface message for a sender whose message time was during the recipient’s OT profile time. As shown, the sender is given the ability to select an override for the message by clicking on the“OTMail Override” icon.

[0086] FIG. 5B shows an example user interface message for a sender whose message time was during the recipient’s OT profile time. In this message, the sender is not given the ability to select an override for the message.

[0087] FIG. 5C shows an example user interface message for a sender whose message time was during the recipient’s OT profile time and the sender is given the ability to request authority to override by clicking on the“Request Override” icon.

[0088] FIG. 5D shows an example interface for an administrator that allows the administrator to provide different levels of override authority. For example, as shown, the administrator may deny the requestor override authority, they may approve override authority, or the administrator may give the requester override authority for a limited time/date.

[0089] FIG. 5E shows an example interface reply message for a sender that requested override authority. In the example shown, the user has been approved for override authority.

[0090] FIG. 5F shows an example interface reply message for a sender that requested override authority. In the example shown, the user has not been approved for override authority. AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

[0091] FIG. 5G shows an example interface reply message for a sender that requested override authority. For the example shown, the user may be approved for a time-limited override authority and the user may request an extension of this authority by clicking on the‘Request Override” icon.

[0092] FIG. 6 shows an example interface screen of a system administrator showing the types of reports that may be selected to be run with some examples of the type of information that may be included. For illustration purposes only and not for limitation, the reports shown are unpopulated. For example, the reports may include details of: the total overrides during a time period, the override trend history over a time period, analysis of shifts of employees, statistics of messages sent outside of normal work hours and analysis of employee time off history.

Example Embodiments of the Automated Time Monitoring System and Methods:

[0093] In one example embodiment, a method of automated time monitoring is provided, the method comprising: receiving a request to communicate a message from a first user interface of a first user to a second user interface of a second user; and comparing a time of the message to an OT profile time of an OTM user profile of the second user and determining whether the time of the message is in the OT profile time of the second user: if the time of the message is not in the OT profile time of the second user communicating the message to the second user interface, and if the time of the message is in the OT profile time of the second user, giving the first user interface the ability to communicate an override to communicate the message to the second user interface: if the first user interface communicates the override, logging the message as an OT event and communicating the message to the second user interface, and if the first user interface does not communicate the override, storing the message in a message queue and communicating the message to the second user interface outside the OT profile time of the second user.

[0094] In one example embodiment, a computer-implemented method of automated time monitoring is provided, the method comprising: receiving, at a server, a request to communicate a message to a second user interface of a second user; and comparing, with an OT checker module, a time of the message to an OTM user profile of the second user and determining whether the time of the message is in the OT profile time of the second user: if the time of the message is not in the OT profile time of the second user, communicating, with a message transport module, the message to the second user interface, and if the time of the message is in the OT profile time of the second user, giving a first user interface the ability, with an alert AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE sender module, to communicate an override to communicate the message to the second user interface: if the first user interface communicates the override, logging the message as an OT event, in an OTM log, and communicating the message to the second user interface, and if the first user interface does not communicate the override, storing the message in a message queue and communicating the message to the second user interface outside of the OT profile time of the second user.

[0095] In one example embodiment, an automated time monitoring system is provided comprising one or more processors; and one or more memory elements including instructions that, when executed, cause the one or more processors to perform operations comprising:

receiving a request to communicate a message from a first user interface of a first user to a second user interface of a second user; and comparing a time of the message to an OT profile time of an OTM user profile of the second user and determining whether the time of the message is in the OT profile time of the second user: if the time of the message is not in the OT profile time of the second user communicating the message to the second user interface, and if the time of the message is in the OT profile time of the second user, giving the first user interface the ability to communicate an override to communicate the message to the second user interface: if the first user interface communicates the override, logging the message as an OT event and communicating the message to the second user interface, and if the first user interface does not communicate the override, storing the message in a message queue and communicating the message to the second user interface outside the OT profile time of the second user.

[0096] In one example embodiment, a non-transitory computer-readable medium storing instructions is provided, that when executed, cause one or more processors to perform operations including: receiving a request to communicate a message from a first user interface of a first user to a second user interface of a second user; and comparing a time of the message to an OT profile time of an OTM user profile of the second user and determining whether the time of the message is in the OT profile time of the second user: if the time of the message is not in the OT profile time of the second user communicating the message to the second user interface, and if the time of the message is in the OT profile time of the second user, giving the first user interface the ability to communicate an override to communicate the message to the second user device: if the first user interface communicates the override, logging the message as an OT event and communicating the message to the second user interface, and if the first user interface does not AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE communicate the override, storing the message in a message queue and communicating the message to the second user interface outside the OT profile time of the second user.

[0097] Although this invention has been described in the above forms with a certain degree of particularity, it is understood that the foregoing is considered as illustrative only of the principles of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation shown and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope of the invention which is defined in the claims and their equivalents.

Claims

AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USECLAIMS: We claim:

1. A method of automated time monitoring, the method comprising:

receiving a message for a recipient user;

the message identifying a time of the message;

an OTM user profile defining an OT profile time of the recipient user; and

comparing the time of the message to the OTM user profile of the recipient user to determine whether the time is within the OT profile time of the recipient user.

2. The method of claim 1 further comprising:

if the time of the message is not in the OT profile time of the recipient user

communicating the message to a recipient user interface of the recipient user; and if the time of the message is in the OT profile time of the recipient user, logging the message as an OT event and communicating the message to the recipient user interface.

3. The method of claim 2 further comprising:

the message for the recipient user received from a sending user interface; and

if the time of the message is in the OT profile time of the recipient user, giving the sending user interface an ability to communicate an override to communicate the message to the recipient user interface whereby:

if the sending user interface communicates the override, logging the message as an OT event and communicating the message to a recipient user interface of the recipient user, and

if the sending user interface does not communicate the override, storing the message in a message queue and communicating the message to the recipient user interface outside the OT profile time of the recipient user.

4. The method of claim 1 wherein the message is a digital message. AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE

5. The method of claim 1 wherein the message is an email message.

6. The method of claim 1 wherein the message is a text message.

7. The method of claim 1 wherein the time of the message is a delivery time of the message.

8. A computer-implemented method of automated time monitoring, the method comprising: receiving, at a server, a request to communicate a message to a second user interface of a second user; and

comparing, with an OT checker module, a time of the message to an OTM user profile of the second user and determining whether the time of the message is in an OT profile time of the second user:

if the time of the message is not in the OT profile time of the second user, communicating, with a message transport module, the message to the second user interface, and

if the time of the message is in the OT profile time of the second user, giving a first user interface an ability, with an alert sender module, to communicate an override to communicate the message to the second user interface:

if the first user interface communicates the override, logging the message as an OT event, in an OTM log, and communicating the message to the second user interface, and

if the first user interface does not communicate the override, storing the message in a message queue and communicating the message to the second user interface outside of the OT profile time of the second user.

9. A method of automated time monitoring, the method comprising:

receiving a request to communicate a message from a first user interface of a first user to a second user interface of a second user; and

comparing a time of the message to an OT profile time of an OTM user profile of the second user and determining whether the time of the message is in the OT profile time of the second user: AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE if the time of the message is not in the OT profile time of the second user communicating the message to the second user interface, and

if the time of the message is in the OT profile time of the second user, giving the first user interface an ability to communicate an override to communicate the message to the second user interface:

if the first user interface communicates the override, logging the message as an OT event and communicating the message to the second user interface, and

if the first user interface does not communicate the override, storing the message in a message queue and communicating the message to the second user interface outside the OT profile time of the second user.

10. An automated time monitoring system comprising:

one or more processors; and

one or more memory elements including instructions that, when executed, cause the one or more processors to perform operations comprising:

comparing a time of the message to an OT profile time of an OTM user profile of the second user and determining whether the time of the message is in the OT profile time of the second user:

if the time of the message is not in the OT profile time of the second user communicating the message to the second user interface, and

if the first user interface does not communicate the override, storing the message in a message queue and communicating the AUTOMATED TIME MONITORING SYSTEMS AND METHODS OF USE message to the second user interface outside the OT profile time of the second user.

11. A non-transitory computer-readable medium storing instructions, that when executed, cause one or more processors to perform operations including:

12. A method of automated time monitoring, the method comprising:

receiving a message for a recipient user interface of a recipient user; and

comparing a time of the message to an OTM user profile of the recipient user whereby: if the time of the message is not in an OT profile time of the recipient user communicating the message to the recipient user interface, and

if the time of the message is in the OT profile time of the recipient user, storing the message in a message queue and communicating the message to the recipient user interface outside the OT profile time of the recipient user.