FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION (See section 10, rule 13)
1. Title of the Invention:
“A SYSTEM AND METHOD FOR SCHEDULING TASK ON THE BASIS OF CIRCADIAN RHYTHM”
2. APPLICANT (S) -
(a) Name : Zensar Technologies Limited
(b) Nationality : India
(c) Address : Zensar Knowledge Park, Plot #4, MIDC, Kharadi,
Off Nagar Road, Pune, Maharashtra - 411014, India

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
The present application claims priority from Indian Provisional Patent Application No. 201821050043 filed on 31st December 2018, the entirety of which is incorporate herein by a reference.
TECHNICAL FIELD
The present invention relates to a data processing system, and more particularly, to a system and method for assigning tasks to an entity based on entity focus level.
BACKGROUND
The physical, mental, and behavioral changes in a person during a given day is related to Circadian rhythm which is a 24-hour daily biological cycle of living beings. In any given day, there are different time slots or periods during which a person is highly focused and productive as compared to rest of the time slots in the day. The time slot during the person is highly focused and productive can be utilized to finish tasks that are either mentally challenging or require greater physical work to be done.
Similar scenario is observed at a workplace, where the focus of an entity is not constant throughout the working day. The entity could be an employee, a consultant, a vendor, or a freelancer or even a robot. There might be time slots when the entity is highly focused which would lead to high productivity, while there might be time slots where the entity is least focused and would therefore impact the productivity. However, the technical challenge is to how to determine the focus level of the entity during their respective office hours. Since the entity use to spend their time either roaming within the organization campus or working on their workstations. Hence, the technical challenge is to continuously not only the entity activities but also their interaction with their workstations.
There is, therefore, a need for a system that can assign a task to an entity depending upon the focus level of the entity to achieve maximum productivity and also to ensure that highly important tasks are assigned only during the time slot that guarantee maximum focus of the entity to avoid any errors and ensure timely completion.

The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.
SUMMARY
In one non-limiting embodiment of the present disclosure, a method of assigning tasks to an entity is disclosed. The method comprises monitoring entity behavioral parameters during an office timing associated with the entity. The entity behavioral parameters comprise entity availability at entity workstation, entity facial expressions, and entity gestures. The method further comprises determining, based on the monitoring, a plurality of focus levels of the entity at a plurality of time slots during the office timing. The method further comprises extracting a plurality of tasks associated with the entity. Each of the plurality of tasks has an importance level associated therewith. The method further comprises assigning the plurality of tasks to the entity based on the importance level associated with each of the plurality of task and the plurality of focus level determined for the entity.
In one non-limiting embodiment of the present disclosure, a system for assigning tasks to an entity is disclosed. The system comprises one or more sensors to monitor entity behavioral parameters during an office timing associated with the entity. The entity behavioral parameters comprise entity availability at entity workstation, entity facial expressions, and entity gestures. The system further comprises a determining unit to determine, based on the monitoring, a plurality of focus levels of the entity at a plurality of time slots during the office timing. The system further comprises an extracting unit to extract a plurality of tasks associated with the entity, wherein each of the plurality of task has an importance level associated therewith. The system further comprises an assigning unit to assign the plurality of tasks to the entity based on the importance level associated with each of the plurality of task and the plurality of focus level determined for the entity.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:
Figure 1 shows an exemplary environment 100 for assigning a task to an entity, in accordance with some embodiments of the present disclosure;
Figure 2 shows a block diagram 200 illustrating a system for assigning a task to an entity, in accordance with some embodiments of the present disclosure;
Figure 3 depicts a flowchart 300 of a method for assigning a task to an entity, in accordance with some embodiments of the present disclosure; and
Figure 4 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.
DETAILED DESCRIPTION
In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the spirit and the scope of the disclosure.
The terms “comprises”, “comprising”, “includes”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
Disclosed herein is a system and a method for assigning a task to an entity in a workplace. According to embodiments of present disclosure, the entity may be an employee, a consultant, a vendor, a freelancer or a robot or any other entity to whom the task may be assigned. The productivity of an entity is not same throughout the working day as it directly depends upon the focus level of the entity which varies during any given working day. There may be time slots during which the entity is highly focused and therefore is highly productive. However, there might be time slots during which the entity is least focused and therefore, least productive. Now, if a highly important task, in terms of complexity or deadline is assigned to the entity for a time slot during which the entity is generally least focused, proper completion of the assigned task will be difficult.
The present disclosure overcomes this issue by providing a system that determines the focus level of an entity by monitoring entity behavioral parameters such as entity availability at entity workstation, entity facial expressions, and entity gestures during the office timings. However, it may be understood to person skilled in art that the abovementioned parameters are just an example and present disclosure is not limited by these parameters. Based on the focus levels of the entity in various time slots during an entire working day, tasks are assigned to him/her. The tasks to be assigned are also distinguished based on their importance level as highly important, medium important and least important. The importance level assigned to a task is based on certain factors comprising, but not limited to, task complexity, task deadline

and task completion time. The system, on the basis of the determining of the entity focus level and task complexity, assigns a task to the entity. For example, a task that falls in the highly important category is assigned for a time slot in which the entity is monitored to be highly focused, thus guaranteeing efficient completion of the task and high productivity.
In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.
Figure 1 shows an exemplary environment 100 for assigning a task to an entity in accordance with some embodiments of the present disclosure. As seen in the figure 1, an entity 104 working on his/her workstation 110 at a workplace. The workplace may be a university, a corporate office, a manufacturing plant and like. Further, a system 102 is provided that monitors the focus level of the entity 104 during the working hours and based on the focus level of the entity, assigns a task to be performed. It may be noted that the system 102 may be implemented in various environments other than as shown in Figure 1. For example, the system 102 may be implemented around the entity workstation as shown in figure 1. However, according to other embodiments, the system 102 may be implemented around the campus of the entity workplace.
The environment 100 also shows various time slots 106 (a-e) during which the focus level of the entity 104 varies. It may be understood to the person skilled in art that the time slots (a-e) 106 shown in figure 1 is merely for example and purpose, and therefore there may be different time slots based on the working hours of the entity. For example, if the entity 104 is working in night shifts, then the office hours may start from 9 pm instead of 9 am as shown in figure 1. Depending upon the focus level of the entity 104 during a given time slot, a task is assigned to him/her from a task list 108 that comprise of a plurality of tasks.
Now figure 1 is explained in conjunction with figure 2 which shows a block diagram 200 illustrating the system 102 for assigning task to an entity 104 in accordance with some embodiments of the present disclosure.

The system 102 comprises a memory 202, sensors 204, a determining unit 206, and an assigning unit 208. According to an embodiment, the assigning unit 208 may be communicatively coupled to the entity workstation 110. The memory 202 may comprise of a plurality of tasks each with an assigned importance level. The importance level of a task is assigned based on certain factors such as task complexity, task deadline and task completion time which is explained in later paragraphs of specification. The memory 202 may also comprise of data associated with the focus level of the entity 104 during different time slots in a working day. The memory 202 may be communicatively coupled to the sensors 204 and units 206-210. In one embodiment, the aforementioned data may be stored within the memory 202 in the form of various data structures. Additionally, the said data can also be organized using data models, such as relational or hierarchical data models. Further, the units 206-210 may be dedicated hardware units capable of performing various operations of the system 102. However, according to other embodiments, the units 206-210 may be a processor or an application-specific integrated circuit (ASIC) or any circuitry capable of executing instructions stored in the memory 202 of the system 102.
The sensors 204 monitor the behavioral parameters of the entity 104 during office timings. The behavioral parameters may comprise of a plurality of parameters such as the availability of the entity 104 at the entity workstation 110, facial expressions such as eye blinking frequency and lip biting frequency, and gestures of the entity 104 that may indicate whether the entity 104 is facing towards the workstation 110 or not. It may be understood to the skilled person that the sensor 201 may be part of the system 102 as shown in figure 1 also or an independent entity. The behavioral parameters of the entity 104 are monitored extensively over a couple of days or weeks or months to produce a pattern that helps the determining unit 204 in determining the focus levels of the entity 104 during different time slots in a working day.
In context with figure 1, it may be considered that the determining unit 204 determines based on the availability of the entity 104 at the workstation 110, facial expressions and gestures of the entity 104, that during a normal working day that starts at 9 A.M. and ends at 5 P.M, the entity 104 has high focus level between the time slots 9 A.M. – 11 A.M. and 3:30 P.M – 5 P.M.. It further determines that between 11 A.M – 1 P.M and 2 P.M – 3 P.M., the entity has medium focus level. It also determines that between 1 P.M. – 2 P.M. and 3 P.M. – 3:30 P.M., the entity 104 has least focus level as he/she is either away from the workstation 110 for

lunch or tea break or is distracted because of any other reason. The general pattern of the focus levels of the entity 104 is stored in the memory 202.
However, it may so happen that on any given day, the focus levels of the entity 104 may deviate from the predetermined pattern. In this case, it is determined by the determining unit 204 whether the deviation in the behavioral parameters produce a change in the predetermined pattern of the focus levels or not. If a change in the predetermined focus levels is noticed for a shorter period or no deviation is detected, then the system reinforces the association of the plurality of focus levels of the entity at the plurality of time slots during the office timing. However, if a change in the predetermined focus levels is noticed for a longer period of time or on regular basis, then the memory 204 is updated with the new focus levels.
According to the embodiments of the present disclosure, how the focus level of the entity is determined has been shown in below table 1.

Entity Behavioral Parameters High focus level Medium focus level Low focus level
Entity Availability Yes Yes Yes
Entity Facial Expression Attentive Anxious Distress
Entity Gesture Facing towards workstation Facing towards workstation Intermittently
facing towards
workstation
Table 1 – Different focus level of the entity
From the above table 1, it can be observed that the high focus level of the entity is determined when the entity is available at the entity workstation 110, entity facial expression indicates entity is attentive based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is facing towards the entity workstation 110. Consider the lip biting frequency range of 5-10/minute and eye blinking frequency range of 10-15/minute. If

the lip biting of the entity is observed to be 3/minute and eye blinking frequency is observed to be 7/minute, then it determined that the entity is attentive and have a high focus level.
Similarly, the medium focus level of the entity is determined when the entity is available at the entity workstation, entity facial expression indicates entity is anxious based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is facing towards the entity workstation 110. In this case, the lip biting of the entity may be observed to be 7/minute and eye blinking frequency is observed to be 12/minute, then it determined that the entity is anxious and have a medium focus level.
Similarly, the low focus level of the entity is determined when the entity is available at the entity workstation, however the entity facial expression indicates entity is in distress based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is intermittently facing towards the entity workstation 110. In this case, if the lip biting of the entity is observed to be 15/minute and eye blinking frequency is observed to be 25/minute, then it determined that the entity attentive is worried or distress and have a low focus level. It may be understood to the person skilled in art that the above taken ranges for lip biting and eye blinking and scenarios is just an example for determining the focus level of the entity, and therefore the above examples shall not limit the scope of the present disclosure.
Now, once the focus levels are determined for the entities, in next step, the extraction unit 208 extracts plurality of tasks 108 associated with the entity 104 from the task list 108 as seen in figure 1. Each task is associated with an assigned importance level. The importance level associated with a task is based on certain task related parameters such as task criticality, task deadline and task turnaround time. The example of assigning the importance level for the tasks (task 1-task 5) is shown in below table 2.

Task Parameters High Importance Medium Importance Low Importance
Task Deadline 2 days 5 days 7 days
Task Criticality High importance tag No tag/flag Low importance
Task Turnaround Time 6 hours 4 hours 2 hours
Table 2 – Different importance levels of the task

In an exemplary embodiment of the present disclosure, a task deadline range of the task may be 4-6 days. For example, if task deadline range is “below” 4 days, then the task may be considered to be of high importance. If the task deadline range is “within” 4-6 days, then the task may be considered to be of medium importance. Whereas, if task deadline range is “more than” 6 days, then the task may be considered to be of low importance. From the above, it may be understood that if the task deadline is shorter based on the provided range, then the task is assigned under the high importance category, whereas if the task deadline is longer then the task is assigned under the low importance category. However, the above given deadline range is just an example and shall not be considered to limit the scope of the present disclosure.
Apart from the task deadline range, another deciding factor is turnaround time range which may be for example, 3-5 hours. For example, if task turnaround time range is “greater” 5 hours, then the task may be considered to be of high importance. If the task deadline range is “within” 3-5 hours, then the task may be considered to be of medium importance. Whereas, if task deadline range is “lower” than 3 hours, then the task may be considered to be of low importance. It may be noticed that, if task completion requires longer time, then the task is given the high importance than the task which requires less time. It may be understood to the skilled person that the above give range and condition for determining the criticality is merely an example and shall not limit the scope of the present disclosure.
Yet another deciding factor may be the task criticality which indicates how much the task which is to be assigned is critical. The task criticality may be determined based on an indicator associated with it. For example, while requesting the task, if the requester raises a flag indicating that the task is very much important. In another example, while sending task thorough an email, the requester may select a “high importance tag” or “low importance tag” indicating the task criticality. Further, it may also happen that there may be no tag or flag associated with the task which is to be assigned. In such case, the system 102 may consider the criticality as neutral and focuses on other two task parameters (deadline and turnaround time) for deciding the importance level of the task.
Now referring to the above table, it can be observed that the having 2 days deadline, 6 hours of turnaround time and also marked with “high importance tag” is considered to be of high importance category. Whereas, the task with “no tag/flag” but deadline of 5 days and turnaround time of 4 hours is considered under the medium importance category. In this case, though there is no criticality indicator is marked, however the task has been considered to be

of medium importance and not low importance. Similarly, if the task having 7 days deadline (i.e., having enough time), 2 hours of turnaround time and also marked with “low importance tag” is considered under the low importance category. It may be understood to the person skilled in art that the abovementioned criteria/scenario for defining task under the different importance categories is merely an example, and hence there may be other task parameters or scenarios which may be used for determining the importance level of the task.
Based on the predetermined focus levels (table 1) and the importance levels (table 2) as discussed in the above paragraphs, a task is assigned to the entity 104 by the assigning unit 210. It may be noted that the task assignment may be conveyed to the entity 104 by means of a pop-up notification on the desktop/laptop screen on the entity workstation 110 or via email or in hard copy. An exemplary assignment of the extracted tasks based on the focus levels of the entity 104 in context with figure 1 are presented in table 3.

Time Slot Focus Level Task Assigned
9 A.M. – 11 A.M. (106a) High Task 1 (High importance level)
11 A.M – 1 P.M (106b) Medium Task 3 (Medium importance level)
1 P.M. – 2 P.M. (106c) Low Task 5 (Low importance level)
2 P.M – 3 P.M. (106d) Medium Task 4 (Medium importance level)
3:30 P.M – 5 P.M. (106e) High Task 2 (High importance level)
Table 3 – Assigning of the task based on focus level and task complexity

As seen from the above table 3, the task assigned to the entity 104 for a given time slot depends upon his/her focus level during that time slot. A highly important task like Task 1 or Task 2 which is either complex or has a strict deadline is assigned during the time slots 106a and 106e when the entity 104 has high focus level which ensures that the assigned task will be completed efficiently and provides high productivity. Similarly, a low importance task that is neither complex nor has a strict deadline to it is assigned during the time slot 106c. Similarly, the task with medium importance level is assigned at the time slot when the entity focus level is a medium level. It may be understood to the person skilled in the art that the above considered scenario for assigning the task is just an example, and therefore should not be considered for limiting the scope of the present disclosure.
Figure 3 depicts a flowchart illustrating a method assigning a task to an entity in accordance with some embodiments of the present disclosure.
As illustrated in figure 3, the method 300 includes one or more blocks illustrating a method to assign the task to the entity. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.
The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
At block 302, one or more sensors 204 monitor entity behavioural parameters during an office timing associated with the entity. The entity behavioural parameters comprise entity availability at entity workstation 110, entity facial expressions, and entity gestures.
At block 304, the determining unit 206 determines, based on the monitoring, a plurality of focus levels of the entity at a plurality of time slots during the office timing. The plurality of focus levels comprises a high focus level, a medium focus level and a low focus level. The high

focus level indicates the highest productivity time and the low focus level indicate lowest productivity time of the entity during the office timing.
At block 306, the extracting unit 208 extracts a plurality of tasks associated with the entity, wherein each of the plurality of task has an importance level associated therewith. Further, the importance level comprises at least one of a highest importance level, a medium importance level, and a lowest importance level.
At block 308, assigning unit 210 assigns the plurality of tasks to the entity based on the importance level associated with each of the plurality of task and the plurality of focus level determined for the entity.
Computer System
Fig.4 illustrates a block diagram of an exemplary computer system 400 for implementing embodiments consistent with the present invention. In an embodiment, the computer system 400 can be the system 102 which is used for assigning a task to the entity. According to an embodiment, the computer system 400 may receive task list 410 along with a request for completing the task. The computer system 400 may comprise a central processing unit (“CPU” or “processor”) 402. The processor 402 may comprise at least one data processor for executing program components for executing user- or system-generated business processes. The processor 402 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.
The processor 402 may be disposed in communication with one or more input/output (I/O) devices (411 and 412) via I/O interface 401. The I/O interface 401 may employ communication protocols/methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS/2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System For Mobile Communications (GSM), Long-Term Evolution (LTE) or the like), etc.

Using the I/O interface 401, the computer system 400 may communicate with one or more I/O devices (411 and 412).
In some embodiments, the processor 402 may be disposed in communication with a communication network 409 via a network interface 403. The network interface 403 may communicate with the communication network 409. The network interface 403 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), Transmission Control Protocol/Internet Protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. The communication network 409 can be implemented as one of the different types of networks, such as intranet or Local Area Network (LAN) and such within the organization. The communication network 409 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the communication network 409 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc.
In some embodiments, the processor 402 may be disposed in communication with a memory 405 (e.g., RAM 413, ROM 414, etc. as shown in FIG. 4) via a storage interface 404. The storage interface 404 may connect to memory 405 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fiber channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.
The memory 405 may store a collection of program or database components, including, without limitation, user/application data 406, an operating system 407, web browser 408 etc. In some embodiments, the computer system 400 may store user/application data 406, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.
The operating system 407 may facilitate resource management and operation of the computer system 400. Examples of operating systems include, without limitation, Apple

Macintosh OS X, UNIX, Unix-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD, Net BSD, Open BSD, etc.), Linux distributions (e.g., Red Hat, Ubuntu, K-Ubuntu, etc.), International Business Machines (IBM) OS/2, Microsoft Windows (XP, Vista/7/8, etc.), Apple iOS, Google Android, Blackberry Operating System (OS), or the like. I/O interface 401 may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, I/O interface may provide computer interaction interface elements on a display system operatively connected to the computer system 400, such as cursors, icons, check boxes, menus, windows, widgets, etc. Graphical User Interfaces (GUIs) may be employed, including, without limitation, Apple Macintosh operating systems’ Aqua, IBM OS/2, Microsoft Windows (e.g., Aero, Metro, etc.), Unix X-Windows, web interface libraries (e.g., ActiveX, Java, JavaScript, AJAX, HTML, Adobe Flash, etc.), or the like.
In some embodiments, the computer system 400 may implement a web browser 408 stored program component. The web browser 408 may be a hypertext viewing application, such as Microsoft™ Internet Explorer, Google™ Chrome, Mozilla™ Firefox, Apple™ Safari™, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS) secure sockets layer (SSL), Transport Layer Security (TLS), etc. Web browsers may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, Application Programming Interfaces (APIs), etc. In some embodiments, the computer system 400 may implement a mail server stored program component. The mail server 416 may be an Internet mail server such as Microsoft Exchange, or the like. The mail server 416 may utilize facilities such as Active Server Pages (ASP), ActiveX, American National Standards Institute (ANSI) C++/C#, Microsoft .NET, CGI scripts, Java, JavaScript, PERL, PHP, Python, WebObjects, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), Microsoft Exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system 400 may implement a mail client 415 stored program component. The mail client 415 may be a mail viewing application, such as Apple™ Mail, Microsoft™ Entourage, Microsoft™ Outlook, Mozilla™ Thunderbird, etc.
Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store

instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, nonvolatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.
Advantages of the embodiment of the present disclosure are illustrated herein.
In an embodiment, the present disclosure provides a method of optimizing the entity utility by assigning the task based on entity productivity level.
In an embodiment, the present disclosure provides a method of ensuring efficient delivery of the task.
The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.
The terms "including", "comprising", “having” and variations thereof mean "including but not limited to", unless expressly specified otherwise.
The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.
The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.
A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.
When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single

device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the invention need not include the device itself.
Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present invention are intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims

Referral Numerals:

Reference Number Description
100 ENVIRONMENT
102 SYSTEM
104 ENTITY
106 TIME SLOTS
108 TASK LIST
110 ENTITY WORKSTATION
202 MEMORY
204 SENSORS
206 DETERMINING UNIT
208 EXTRACTING UNIT
210 ASSIGNING UNIT
400 EXEMPLARY COMPUTER SYSTEM
401 I/O INTERFACE OF THE EXEMPLARY COMPUTER SYSTEM
402 PROCESSOR OF THE EXEMPLARY COMPUTER SYSTEM
403 NETWORK INTERFACE
404 STORAGE INTERFACE
405 MEMORY OF THE EXEMPLARY COMPUTER SYSTEM
406 USER/APPLICATION
407 OPERATING SYSTEM
408 WEB BROWSER
409 COMMUNICATION NETWORK
410 TASK LIST
411 INPUT DEVICES
412 OUTPUT DEVICES
413 RAM
414 ROM
415 MAIL CLIENT
416 MAIL SERVER
417 WEB SERVER

We Claim:
1. A method of assigning tasks to an entity, wherein the method comprises:
monitoring, by one or more sensors (204), entity behavioural parameters during an
office timing associated with the entity, wherein the entity behavioural parameters comprise entity availability at entity workstation (110), entity facial expressions, and entity gestures;
determining, by a determining unit (206), based on the monitoring, a plurality of focus levels of the entity at a plurality of time-slots during the office timing;
extracting, by an extracting unit (208), a plurality of tasks associated with the entity, wherein each of the plurality of task has an importance level associated therewith; and
assigning, by as assigning unit (210), the plurality of tasks to the entity based on the importance level associated with each of the plurality of task and the plurality of focus level determined for the entity.
2. The method as claimed in claim 1, wherein the plurality of focus levels, determined for the entity, comprises a high focus level, medium focus level, and a low focus level, and wherein the importance level associated with the task comprises a high importance level, a medium importance level and a low importance level.
3. The method as claimed in claim 1, further comprising determining, by the determining unit (206),
the high focus level of the entity when the entity is available at the entity workstation (110), entity facial expression indicates entity is attentive based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is facing towards the entity workstation (110);
the medium focus level of the entity when the entity is available at the entity workstation, entity facial expression indicates entity is anxious based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is facing towards the entity workstation (110); and
the low focus level of the entity when the entity is available at the entity workstation, entity facial expression indicates entity is in distress based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is intermittently facing towards the entity workstation (110).

4. The method as claimed in claim 1, further comprising assigning, by the assigning unit
(210), the importance level associated to each of the plurality of task by:
analyzing task deadline, task criticality, and task turnaround time associated with the plurality of tasks,
wherein the task deadline comprises a time of a day by which the task is to be completed;
wherein the task criticality is determined based on an indicator associated with the task, wherein the indicator comprises at least one of a flag assigned with the task and a tag assigned to the task; and
wherein the task turnaround time comprises an estimated time to be required by the entity for completing the task; and
categorizing each of the plurality of task in at least one of a highest importance level, a medium importance level, and a lowest importance level based on the analyzing.
5. The method as claimed in claim 2, wherein the method further comprising assigning,
by the assigning unit (210), the plurality of tasks to the entity in such a manner that:
a task having a highest importance level is assigned at a time slot when the entity is having the high focus level;
a task having a medium importance level is assigned at a time slot when the entity is having the medium focus level; and
a task having a lowest importance level is assigned at a time slot when the entity is having the low focus level.
6. The method as claimed in claim 1, further comprising performing, based on the
monitoring of the entity behavioural parameters, at least one of:
reinforcing the association of the plurality of focus levels of the entity at the plurality of time-slots during the office timing, when no deviation is detected in the entity behavioural parameters; and
updating the association of the plurality of focus levels of the entity at the plurality of time-slots during the office timing, when deviation is detected in the entity behavioural parameters.
7. A system (102) for assigning tasks to an entity, the system comprises:

one or more sensors (204) to monitor entity behavioural parameters during an office timing associated with the entity, wherein the entity behavioural parameters comprise entity availability at entity workstation (110), entity facial expressions, and entity gestures;
determining unit (206) to determine, based on the monitoring, a plurality of focus levels of the entity at a plurality of time-slots during the office timing;
extracting unit (208) to extract a plurality of tasks associated with the entity, wherein each of the plurality of task has an importance level associated therewith; and
assigning unit (210) to assign the plurality of tasks to the entity based on the importance level associated with each of the plurality of task and the plurality of focus level determined for the entity.
8. The system (102) as claimed in claim 7, wherein the plurality of focus levels, determined for the entity, comprises a high focus level, medium focus level, and a low focus level, and wherein the importance level associated with the task comprises a high importance level, a medium importance level and a low importance level.
9. The system (102) as claimed in claim 7, is further configured to determine:
the high focus level of the entity when the entity is available at the entity workstation (110), entity facial expression indicates entity is attentive based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is facing towards the entity workstation (110);
the medium focus level of the entity when the entity is available at the entity workstation, entity facial expression indicates entity is anxious based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is facing towards the entity workstation (110); and
the low focus level of the entity when the entity is available at the entity workstation, entity facial expression indicates entity is in distress based on entity lip biting frequency and eye blinking frequency, and entity gesture indicate entity is intermittently facing towards the entity workstation (110).
10. The system (102) as claimed in claim 7, for assigning the importance level associated
to each of the plurality of task is configured to:
analyse task deadline, task criticality, and task turnaround time associated with the plurality of tasks,

wherein the task deadline comprises a time of a day by which the task is to be completed,
wherein the task criticality is determined based on an indicator associated with the task, wherein the indicator comprises at least one of a flag assigned with the task and a tag assigned to the task, and
wherein the task turnaround time comprises an estimated time required by the entity for completing the task; and
categorize each of the plurality of task in at least one of a highest importance level, a medium importance level, and a lowest importance level based on the analyzing.
11. The system (102) as claimed in claim 8, wherein the assigning unit (210) assigns the
plurality of tasks to the entity in such a manner that:
a task having a highest importance level is assigned at a time slot when the entity is having the high focus level;
a task having a medium importance level is assigned at a time slot when the entity is having the medium focus level; and
a task having a lowest importance level is assigned at a time slot when the entity is having the low focus level.
12. The system (102) as claimed in claim 7, is further configured to, based on the
monitoring of the entity behavioural parameters, at least one of:
reinforce the association of the plurality of focus levels of the entity at the plurality of time-slots during the office timing when no deviation is detected in the entity behavioural parameters; and
update the association of the plurality of focus levels of the entity at the plurality of time-slots during the office timing when a deviation is detected in the entity behavioural parameters.