DESC:FIELD
The present disclosure relates to the field for allocating and prioritizing action items.
BACKGROUND
The background information herein below relates to the present disclosure but is not necessarily prior art.
Primarily monitoring pre and post meeting along with the entire meetings details and documents are driven through email and human delegations. Capturing notes and action items through human intervention may increase risk of loss and error of meeting data and action items. Moreover, generation and allotment of action items takes a lot of time. Further, there is no surety that the allotment is done to a right person or not. Also, there are times when the allotted person initiates the work on a least important action item, thus wasting time, energy and resources.
There is, therefore, felt a need for a system for allocating and prioritizing action items which solves the problems as described herein above.
OBJECTS
Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:
An object of the present disclosure is to provide a system for allocating and prioritizing action items.
Another object of the present disclosure is to provide a system for accessing Meeting/Member information for upcoming meetings of leadership.
Still another object of the present disclosure is to provide a system for capturing post meeting notes and action items and driving it through a priority matrix to define criticality.
Still another object of the present disclosure is to provide a system for taking input from pre and post meeting emails and anonymised profile and client surveys.
Yet another object of the present disclosure is to provide a system for auto creating follow up meetings/action items tracker and auto notification mechanism to respective owners.
Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
SUMMARY
The present disclosure envisages a system for allocating and prioritizing action items. The system comprises a server communicatively coupled to at least one user interface. The server is configured to receive at least one input associated with a client meeting from a first user via the user interface.
The server comprises an action item generator, an allocation engine and a prioritization module.
The action item generator is configured to receive the input, and is further configured to identify action items of the client meeting from the received input to generate a list of the identified action items.
In an embodiment, an audio to text converter configured to receive the input in the form of an audio recording, and is further configured to convert the received audio recording to text.
The action item generator includes an identifier and a list generator.
The identifier is configured to receive the input either directly in the form of text or from the audio to text converter, and is further configured to identify action items from the received text.
The list generator is configured to cooperate with the identifier to generate the list the identified action items.
The allocation engine is configured to cooperate with the action item generator to receive the action items, and is further configured to determine at least one owner for executing each of the action items based on the received input.
The allocation engine includes a first repository, a determination module, an assignment module and a self-learning module.
The first repository is configured to store a first look up table having a list of owner IDs and an owner name corresponding to each of the owner IDs, and an archive data of action items associated with each of the owner IDs.
The determination module is configured to cooperate with the action item generator to receive the text, and is further configured to cooperate with the first repository to determine the owner for executing each of the identified action items based on the first look up table.
The assignment module is configured to cooperate with the determination module to:
• assign each of the identified action items to corresponding owner, if the owner is determined by the determination module;
• cooperate with an organizational database to determine the owner of each of the identified action items based on hierarchy and designation data corresponding to the owners pre-stored in the database, if the owner is not determined by the determination module; and
• assign each of the identified action items to corresponding owners determined using the organizational database.
The self-learning module is configured to cooperate with the assignment module to update the archive data of the first repository based on the assignment.
The prioritization module is configured to cooperate with the action item generator to receive the action items, and is further configured to evaluate priority of execution of each of the action items based on the received input. The prioritization module is configured to transmit the evaluated priorities to a user device for facilitating the first user associated with the user device to execute the action items based on the evaluated priority.
The prioritization module includes a second repository, an extractor unit, a scoring engine and an evaluator.
The second repository is configured to store a second look up table having a list of pre-determined parameters, and functions for calculating prioritization scores for each of the parameters, wherein the functions include a plurality of variables.
The extractor unit is configured to receive the text input, and further configured to extract values associated with each of the variables from at least one of the received text input and a customer relationship management engine.
The scoring engine is configured to cooperate with the extractor unit to receive the extracted values, and is further configured to cooperate with the second repository to calculate prioritization score for each of the parameters based on the received values.
The evaluator is configured to cooperate with the scoring engine to perform summation of the prioritization scores to evaluate priority of execution of each of the action items.
The action item generator, the allocation engine and the prioritization module are implemented using one or more processor(s).
The present disclosure envisages a method for allocating and prioritizing action items.

BRIEF DESCRIPTION OF ACCOMPANYING DRAWING
A system and method for allocating and prioritizing action items, of the present disclosure will now be described with the help of the accompanying drawing, in which:
Figure 1 illustrates a block diagram of a system for allocating and prioritizing action items; and
Figure 2 illustrates a flow chart of a method for allocating and prioritizing action items.
LIST OF REFERENCE NUMERALS USED IN DETAILED DESCRIPTION AND DRAWING
100 System
102 server
104 action item generator
106 allocation engine
108 prioritization module
110 user device
112 user interface
114 audio to text converter
116 identifier
118 list generator
120 first repository
122 determination module
124 assignment module
126 self-learning module
128 second repository
130 extractor unit
132 scoring engine
134 evaluator
136 organizational database
138 customer relationship management engine

DETAILED DESCRIPTION
Embodiments, of the present disclosure, will now be described with reference to the accompanying drawing.
Embodiments are provided so as to thoroughly and fully convey the scope of the present disclosure to the person skilled in the art. Numerous details, are set forth, relating to specific components, and methods, to provide a complete understanding of embodiments of the present disclosure. It will be apparent to the person skilled in the art that the details provided in the embodiments should not be construed to limit the scope of the present disclosure. In some embodiments, well-known processes, well-known apparatus structures, and well-known techniques are not described in detail.
The terminology used, in the present disclosure, is only for the purpose of explaining a particular embodiment and such terminology shall not be considered to limit the scope of the present disclosure. As used in the present disclosure, the forms "a,” "an," and "the" may be intended to include the plural forms as well, unless the context clearly suggests otherwise. The terms "comprises," "comprising," “including,” and “having,” are open ended transitional phrases and therefore specify the presence of stated features, integers, steps, operations, elements, modules, units and/or components, but do not forbid the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The particular order of steps disclosed in the method and process of the present disclosure is not to be construed as necessarily requiring their performance as described or illustrated. It is also to be understood that additional or alternative steps is be employed.
A system and method for allocating and prioritizing action items (hereinafter referred as “system”) (100) of the present disclosure is now being described with reference to Figure 1 through Figure 2.
Referring to Figure 1, the system (100) for allocating and prioritizing action items comprises a server (102) communicatively coupled to at least one user interface (20). The server (102) is configured to receive at least one input associated with a client meeting from a first user via the user interface (112).
The server (102) comprises an action item generator (104), an allocation engine (106) and a prioritization module (108).
The action item generator (104) is configured to receive the input, and is further configured to identify action items of the client meeting from the received input to generate a list of the identified action items.
In an embodiment, an audio to text converter (114) configured to receive the input in the form of an audio recording, and is further configured to convert the received audio recording to text.
The action item generator (104) includes an identifier (116) and a list generator (118).
The identifier (116) is configured to receive the input either directly in the form of text or from the audio to text converter, and is further configured to identify action items from the received text.
The list generator (118) is configured to cooperate with the identifier (116) to generate the list the identified action items.
The allocation engine (106) is configured to cooperate with the action item generator (104) to receive the action items, and is further configured to determine at least one owner for executing each of the action items based on the received input.
The allocation engine (106) includes a first repository (120), a determination module (122), an assignment module (124) and a self-learning module (126).
The first repository (120) is configured to store a first look up table having a list of owner IDs and an owner name corresponding to each of the owner IDs, and an archive data of action items associated with each of the owner IDs.
The determination module (122) is configured to cooperate with the action item generator (104) to receive the text, and is further configured to cooperate with the first repository (120) to determine the owner for executing each of the identified action items based on the first look up table.
The assignment module (124) is configured to cooperate with the determination module (122) to:
• assign each of the identified action items to corresponding owner, if the owner is determined by the determination module;
• cooperate with an organizational database (136) to determine the owner of each of the identified action items based on hierarchy and designation data corresponding to the owners pre-stored in the organizational database (136), if the owner is not determined by the determination module; and
• assign each of the identified action items to corresponding owners determined using the organizational database (136).
The self-learning module (126) is configured to cooperate with the assignment module (124) to update the archive data of the first repository based on the assignment.
The prioritization module (108) is configured to cooperate with the action item generator (104) to receive the action items, and is further configured to evaluate priority of execution of each of the action items based on the received input. The prioritization module (108) is configured to transmit the evaluated priorities to a user device (110) for facilitating the first user associated with the user device (110) to execute the action items based on the evaluated priority.
The prioritization module (108) includes a second repository (128), an extractor unit (130), a scoring engine (132) and an evaluator (134).
The second repository (128) is configured to store a second look up table having a list of pre-determined parameters, and functions for calculating prioritization scores for each of the parameters, wherein the functions include a plurality of variables.
In an embodiment, the pre-determined parameters on the basis of which prioritization scores are calculated are as follows:

• Deal Pipeline of account

• Target Impact of Deal/ Deal Importance

• Revenue Impact

• Date of closure

• Strategic Importance factor
The extractor unit (130) is configured to receive the text input, and further configured to extract values associated with each of the variables from at least one of the received text input and a customer relationship management engine (138).
In an embodiment, the extractor unit (130) interacts with the customer relationship management engine (138) to extract the Deal Pipeline of account, Target Impact of Deal/ Deal Importance and Revenue Impact.
In another embodiment, the extractor unit (130) extracts the score from the customer relationship management engine (138) corresponding to the date of closure received from at least one of the received text input.
Table 1 illustrates the score corresponding to the days of closure.

Table 1
In an embodiment, the user manually enters the score for the parameter strategic importance parameter. The scores of the strategic parameter are extracted from the customer relationship management engine (138).
Table 2 illustrates the scores corresponding to the strategic importance.
Table 2
The scoring engine (132) is configured to cooperate with the extractor unit (130) to receive the extracted values, and is further configured to cooperate with the second repository (128) to calculate prioritization score for each of the parameters based on the received values.
In an embodiment, the Prioritization Score is calculated as
Deal Pipeline of account score+ 2*(Target Impact of Deal/ Deal Importance score) + 1.5*(Revenue Impact) + 2*(days of closure score) + strategic importance score
The evaluator (134) is configured to cooperate with the scoring engine (132) to perform summation of the prioritization scores to evaluate priority of execution of each of the action items.
In an embodiment, the first user is provided alerts to remind about the allotments of the action items and the priority of each of the action items, along with the deadline approaching.
In another embodiment, the alerts can be send through messages, emails and pop-up alerts.
In an operative embodiment, there is a meeting of a Head with a Client on an agenda on 30th Oct, 2019 and the Head implements the system (100) to put in the following notes for this meeting:

Post the meeting is completed, the head again records the following action item –

The action item generator (104), the allocation engine (106) and the prioritization module (108) are implemented using one or more processor(s).
The processor may be a general-purpose processor, a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), and/or the like. The processor may be configured to retrieve data from and/or write data to the memory. The memory can be for example, a random access memory (RAM), a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a read only memory (ROM), a flash memory, a hard disk, a floppy disk, cloud storage, and/or so forth.
Figure 2 illustrate a flow diagram of a method for allocating and prioritizing action items. The steps include:
• Step 202: coupling (202), by a server (102), to at least one user interface (112) to receive at least one input associated with a client meeting from a user;
• Step 204: identifying (204), by an action item generator (104), the action items of the client meeting from the received input to generate a list of the identified action items;
• Step 206: determining (206), by an allocation engine (106), at least one owner for executing each of the action items based on the received input;
• Step 208: evaluating (208), by a prioritization module (108), priority of execution of each of the action items based on the received input; and
• Step 210: transmitting (210), by the prioritization module (108), the evaluated priorities to a user device for facilitating the user of the user device to execute the action items based on the evaluated priority.
The sub-step of identifying (204), by an action item generator (104), the action items of the client meeting from the received input to generate a list of the identified action items includes:
• receiving, by an identifier (116), the input either directly in the form of text or from the audio to text converter;
• identifying, by the identifier (116), action items from the received text; and
• generating, by a list generator (118), the list the identified action items.
The sub-step of determining (206), by an allocation engine, at least one owner for executing each of the action items based on the received input includes:
• storing, by a first repository (120), a first look up table having a list of owner IDs and an owner name corresponding to each of the owner IDs, and an archive data of action items associated with each of the owner IDs;
• determining, by a determination module (122), the owner for executing each of the identified action items based on the first look up table;
• assigning, by an assignment module (124), each of the identified action items to corresponding owner, if the owner is determined by the determination module (122);
• cooperating, by the assignment module (124), with an organizational database (136) to determine the owner of each of the identified action items based on hierarchy and designation data corresponding to the owners pre-stored in the organizational database (136), if the owner is not determined by the determination module; and
• assigning, by the assignment module (124), each of the identified action items to corresponding owners determined using the organizational database (136); and
• updating, by a self-learning module (126), the archive data of the first repository based on the assignment.
The foregoing description of the embodiments has been provided for purposes of illustration and not intended to limit the scope of the present disclosure. Individual components of a particular embodiment are generally not limited to that particular embodiment, but, are interchangeable. Such variations are not to be regarded as a departure from the present disclosure, and all such modifications are considered to be within the scope of the present disclosure.
TECHNICAL ADVANCES AND ECONOMICAL SIGNIFICANCE
The present disclosure described herein above has several technical advantages including, but not limited to, the realization of a system and method for allocating and prioritizing action items that:
• provides a system for automated monitoring of meetings and action items;
• provides a system for accessing Meeting/Member information for upcoming meetings of leadership;
• provides a system of capturing post meeting notes and action items and driving it through a priority matrix to define criticality;
• provide a system of taking input from pre and post meeting emails and anonymized profile and client surveys; and
• provide a system of auto creating follow up meetings/action items tracker and auto notification mechanism to respective owners.
The foregoing description of the specific embodiments so fully reveals the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
Throughout this specification the word “comprise”, or variations such as “comprises” or “comprising”, will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.
Any discussion of documents, acts, materials, devices, articles or the like that has been included in this specification is solely for the purpose of providing a context for the disclosure. It is not to be taken as an admission that any or all of these matters form a part of the prior art base or were common general knowledge in the field relevant to the disclosure as it existed anywhere before the priority date of this application.
While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
,CLAIMS:WE CLAIM:
1. A system (100) for allocating and prioritizing action items, said system (100) comprising:
• a server (102) communicatively coupled to at least one user interface (112), said server (102) configured to receive at least one input associated with a client meeting from a first user via said user interface (112), said server (102) comprising:
i. an action item generator (104) configured to receive said input, and further configured to identify action items of said client meeting from said received input to generate a list of said identified action items;
ii. an allocation engine (106) configured to cooperate with said action item generator (104) to receive said action items, and further configured to determine at least one owner for executing each of said action items based on said received input; and
iii. a prioritization module (108) configured to cooperate with said action item generator to receive said action items, and further configured to evaluate priority of execution of each of said action items based on said received input, said prioritization module (108) configured to transmit said evaluated priorities to a user device (110) for facilitating the first user associated with said user device (110) to execute said action items based on said evaluated priority,
wherein said action item generator (104), said allocation engine (106) and said prioritization module (108) are implemented using one or more processor(s).

2. The system (100) as claimed in claim 1 includes an audio to text converter (114) configured to receive said input in the form of an audio recording, and further configured to convert said received audio recording to text.

3. The system (100) as claimed in claim 2, wherein said action item generator (104) includes:
• an identifier (116) configured to receive said input either directly in the form of text or from said audio to text converter, and further configured to identify action items from said received text; and
• a list generator (118) configured to cooperate with said identifier (116) to generate said list said identified action items.

4. The system (100) as claimed in claim 1, wherein said allocation engine (106) includes:
• a first repository (120) configured to store a first look up table having a list of owner IDs and an owner name corresponding to each of said owner IDs, and an archive data of action items associated with each of said owner IDs;
• a determination module (122) configured to cooperate with said action item generator (104) to receive said text, and further configured to cooperate with said first repository to determine the owner for executing each of said identified action items based on said first look up table;
• an assignment module (124) configured to cooperate with said determination module (122) to:
o assign each of said identified action items to corresponding owner, if said owner is determined by said determination module (122);
o cooperate with an organizational database (136) to determine said owner of each of said identified action items based on hierarchy and designation data corresponding to said owners pre-stored in said organizational database (136), if said owner is not determined by said determination module (122); and
o assign each of said identified action items to corresponding owners determined using said organizational database (136),
• a self-learning module (126) configured to cooperate with said assignment module (124) to update said archive data of said first repository based on said assignment.

5. The system (100) as claimed in claim 1, wherein said prioritization module (108) includes:
• a second repository (128) configured to store a second look up table having a list of pre-determined parameters, and functions for calculating prioritization scores for each of said parameters, wherein said functions include a plurality of variables;
• an extractor unit (130) configured to receive said text input, and further configured to extract values associated with each of said variables from at least one of said received text input and a customer relationship management engine (138);
• a scoring engine (132) configured to cooperate with said extractor unit (130) to receive said extracted values, and further configured to cooperate with said second repository to calculate prioritization score for each of said parameters based on said received values; and
• an evaluator (134) configured to cooperate with said scoring engine (132) to perform summation of said prioritization scores to evaluate priority of execution of each of said action items.
6. A method for allocating and prioritizing action items, said method comprises the steps of:
• coupling (202), by a server (102), to at least one user interface (112) to receive at least one input associated with a client meeting from a user (10);
• identifying (204), by an action item generator (104), said action items of said client meeting from said received input to generate a list of said identified action items;
• determining (206), by an allocation engine (106), at least one owner for executing each of said action items based on said received input;
• evaluating (208), by a prioritization module (108), priority of execution of each of said action items based on said received input; and
• transmitting (210), by said prioritization module (108), said evaluated priorities to a user device for facilitating the user of said user device to execute said action items based on said evaluated priority.

7. The method as claimed in claim 6, wherein the sub-step of identifying (204), by an action item generator, said action items of said client meeting from said received input to generate a list of said identified action items includes:
• receiving, by an identifier (116), said input either directly in the form of text or from said audio to text converter;
• identifying, by said identifier (116), action items from said received text; and
• generating, by a list generator (118), said list said identified action items.

8. The method as claimed in claim 6, wherein the sub-step of determining (206), by an allocation engine, at least one owner for executing each of said action items based on said received input includes:
• storing, by a first repository (120), a first look up table having a list of owner IDs and an owner name corresponding to each of said owner IDs, and an archive data of action items associated with each of said owner IDs;
• determining, by a determination module (122), the owner for executing each of said identified action items based on said first look up table;
• assigning, by an assignment module (124), each of said identified action items to corresponding owner, if said owner is determined by said determination module;
• cooperating, by said assignment module (124), with an organizational database to determine the owner of each of said identified action items based on hierarchy and designation data corresponding to said owners pre-stored in said database, if said owner is not determined by said determination module; and
• assigning, by said assignment module (124), each of said identified action items to corresponding owners determined using said organizational database; and
• updating, by a self-learning module (126), said archive data of said first repository based on said assignment.