Browse Prior Art Database

System and method of managing enrollment dynamically/intelligently

IP.com Disclosure Number: IPCOM000194429D
Publication Date: 2010-Mar-24
Document File: 2 page(s) / 35K

Publishing Venue

The IP.com Prior Art Database

Abstract

When meeting room seats are limited and there are many invitees for an invitation, current calendar system can not handle this situation properly. Instead of managing enrollment by accepting or not by receivers, in our invention, we have a Rule Engine which can process the acception and provide a final list of enrolled people.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

System and method of managing enrollment dynamically

System and method of managing enrollment dynamicallySystem and method of managing enrollment dynamically /

intelligently

Let us take meeting invitation as an example to explain the problem . In current meeting invitation implementation , sender of the invitation gets to know how many people will join the meeting based on how many people accept the invitation . Current implementation can't resolve below problems :

The situation is:


One department has a weekly technical meeting . A meeting room with 20 seats is booked , it can hold 20 people at most. This meeting is open for all technical people (about 200 technical people in this department ). But due to meeting room limitation , TechnicalLead group(20 people) people have high priority to join the meeting .

Usually we send out the invitation with TechnicalLead group in the "Required Invitee" list and other employees in the "Optional Invitee" list to inform all the people . People receiving the invitation will accept or decline the invitation .

The problems

The problemsThe problems

///intelligentlyintelligentlyintelligently

are:
1. Other employees do NOT know if there 's and how many available seats left , unless they go to the meeting room to check after the meeting is already started . It may turn out the meeting room is full and there is no seat for him . Then he has to return back to work .
2.Other employees may arrive and take seats earlier than TechnicalLead people , and there may be no seats left for TechnicalLead people .
3. Other employees may think there are no seats for them , so all of them don't come. And some of the people in TechnicalLead group don 't have time to join. It may end up with no enough people joining this meeting .

Current invitation do NOT have a smart mechanism to ensure all TechnicalLead attendees will have seats and available seats left can be provided to other employees with "First accept the invitation , first served" principle and avoid the situation when no enough people join the meeting .

Below diagram describes how our invention works .

In the middle, it's rule engine component where some rules can be set . As showed in the

1

[This page contains 18 pictures or other non-text objects]

Page 2 of 2

rule engine component , three rules(or more) can be set:

Rule

RuleRule

1111:::: Max AttendeesMax AttendeesMax Attendees

Max Attendees

By setting this rule, sender can define how many people can join this meeting . For example, if 20 is set, that means only 20 people can be allowed to join this meeting .

Rule

RuleRule

2222:::: Attendees PriorityAttendees...