VACATION AND HOLIDAY SCHEDULING SYSTEM

Abstract: The present invention provides a vacation and holiday scheduling system (10, 12, 14). The system includes a variety of objects (24, 26, 28, 30, 32) to assist a business in controlling and managing the scheduling of vacations by their employees and for assisting the employees in bidding on vacation days and holidays based upon employee seniority.

Description: VACATION AND HOLIDAY SCHEDULING SYSTEM TECHNICAL FIELD This invention relates generally to computerized systems and methods of planning, scheduling and managing vacations and holidays in a business environment. BACKGROUND OF THE INVENTION Scheduling management systems for use in planning, scheduling and managing personnel are known in the prior art. Such systems typically include a basic scheduling capability to enable a business to forecast future needs and then allocates agent work hours according to the staffing requirements that have been forecast. Prior art vacation and holiday scheduling systems used with such scheduling management systems suffer from many disadvantages. Such systems rely on conventional time series forecasting techniques to generate forecasts for a large block or unit of time, e.g., a month. These techniques use fixed factors to decompose the monthly forecast into weekly, daily, and then hourly or small increments. This approach is computationally efficient but lends itself to accuracy only on a macro scale, e.g., month-to-month, as opposed to reflecting real changes in the business needs as they actually occur. Prior art systems thus do not have the flexibility to be responsive to changing conditions to forecast work loads and provide realistic scheduling of personnel to meet the dynamic requirements of the business. Moreover, prior art systems are typically structured around a single business location, thus ignoring the needs of multi-cite facilities. Another disadvantage associated with prior art approaches us with the inability of such systems to efficiently generate optimal work shifts for available agents and forecasting is complete. Further, these systems do not have the capability to efficiently generate schedules to satisfy agent preferences, availability and seniority. Thus, a need has arisen for a vacation scheduling system enabling the scheduling of agent vacations over a number of site locations and allowing all needs of a business to be efficiently met. BRIEF SUMMARY OF THE INVENTION The present invention overcomes the foregoing and other problems with a vacation and holiday scheduling system. The vacation and holiday scheduling system of the present invention includes a variety of objects enabling a business to control and manage the scheduling of vacations and holidays by their employees. An administration object enables a user to set up the conditions and rules by which the vacation and holiday scheduling system will function. A plan object enables the determination of business unit and management unit staffing requirements for a particular business. These requirements are able to be downloaded from a remote force management system or may be generated locally. A calculate vacation days object enables the system to determine the number of vacation days which have been earned by each agent within a business unit. The agent information and vacation days calculated are displayed via a vacation profile object which gives complete information concerning the vacation requirements and selections of each employee. Finally, a bidding object allows employees of a business to access the vacation and holiday planning system and select available holiday and vacation periods on a seniority basis. An employee selects their name from an agent listing and are allowed access if each individual senior to them has already selected their vacation and holiday requirements. Upon entry and approval of a user associated password, the employee may access selection utilities to assist them in selecting their vacations and holidays. The foregoing has outlined some of the more pertinent aspects of the present invention. These aspects should be construed to be merely illustrative of some of the more prominent features and applications of the invention. Many other beneficial results can be attained by applying the disclosed invention in a different manner or modifying the invention as will be described. Accordingly, other aspects and a full understanding of the invention may be had by referring to the following detailed description of the preferred embodiment. BRIEF DESCRIPTION OF THE DRAWINGS For a more complete understanding of the present invention and the advantages thereof, reference should be made to the following Detailed Description taken in connection with the accompanying drawings in which: FIGURE 1 is a functional block diagram illustrating how the vacation schedule of the present invention is implemented with a PC workstation and a force management system; FIGURE 2 is a functional flow diagram of the vacation scheduling system of the present invention; FIGURE 3 is a flow chart illustrating the method for generation of management unit allocations; FIGURE 4 is a flow chart illustrating the method for calculating the number of vacation days available to an agent; FIGURE 5 is a representation of the Agent Vacation Profile screen; FIGURE 6 is a diagram of the Vacation Holiday Bidding screen; and FIGURE 7 is a representation of the Vacation Days Selection screen. DETAILED DESCRIPTION Referring now to the drawings and more particularly the FIGURE 1 there is illustrated a functional block diagram of the operating environment of the vacation and holiday scheduling system (vacation scheduler) 10 of the present invention. The vacation scheduler 10 is designed to be accessed by a single user to enable selection of vacation days and holidays while enabling an employer to maintain control of employee staffing requirements such that all positions for any particular day or during any particular time period are covered. The vacation scheduler 10 is locally stored within a PC workstation 1 2 or may be accessed via a network 1 6. Data required by the vacation scheduler 10 is locally stored at the PC work station 12. The vacation scheduler 10 is designed as a stand-alone mechanism not requiring the use of a force management system 14 in order to carry out its functionalities. However, the vacation scheduler 10 may be utilized in conjunction with a force management system such as described in applicant's U.S. Patent Number 5,289,368. The force management system 14 may be accessed by the local PC workstation 1 2 via a modem or other type of network 1 6. For purposes of this discussion the Applicant incorporates herein by reference the disclosure contained with U.S. Patent Number 5,289,368. Data required for generating the vacation schedules of various agents (employees of a business) are transmitted from the force management system 14 in response to user requests. Generated vacation schedule data may also be uploaded to the force management system 14 over a network 1 6 after generation by the vacation scheduler 10. Referring now to FIGURE 2, there is illustrated a functional flow diagram of the vacation scheduler 10. The functionality of the vacation scheduler 10 is accessed via a graphical user interface 20. The graphical user interface 20 is preferably a windows-type interface enabling user access to the various system functionalities via point and click techniques. However, it should be realized that the present invention is not limited to the use of a windows type graphical user interface and may also function equally well using a DOS or other type of user interface. The main menu 22 presents a user with a number of vacation scheduler objects including the administration object 24, plan object 26, calculate vacation days object 28, vacation profile object 30 and bidding object 32. The administration object 24 enables the user to set up how the vacation schedule 10 will control processing of vacation scheduling requests and data. With the administration object 24, the user is able to determine which management units (MUs) will be included in the vacation scheduler database, to initialize vacation and holiday data, and to set rules and parameters governing the behavior of the vacation scheduler. A management unit is a grouping or department of employees of a business such as sales, marketing, etc. The administration object 24 provides a number of functional tools to the user. The rules set function 38 provides for generation of sets of parameters and rules that are assigned to one or more management units. These parameters and rules determine how the vacation scheduler handles scheduling of vacation days and holidays for the management units. Each management unit has its own individual rule and parameter set. Examples of rule sets or parameters associated with a management unit would include MU010 has ten paid holidays, and MU01 1 has eleven paid holidays. The rules sets generally comprise anything to do with the defining or controlling of how a particular agent may take or use a holiday or vacation day. The shift allocations function 40 and vacation shifts function 42 are used in conjunction to determine the number of vacation hours allowed from data supplied by the calculate vacation days object 28. Each agent of a management unit is assigned to a vacation shift using the vacation shifts function 42. The vacation shifts function 42 defines the various working shifts occurring throughout the work day from which a vacation may be taken. A vacation shift is defined by a shift name, shift start time and shift end time. For example, the morning shift may be defined as beginning at 6:00 a.m. and ending at 2:00 p.m., whereas the day shift may be defined as beginning at 8:00 a.m. and ending at 5:00 p.m. and the afternoon shift may be defined as beginning at 1 1 :00 a.m. and ending at 7:00 p.m. The shift name and starting and ending times are defined using selection blocks or pop-up windows that appear in response to selection of the vacation shifts function. The shift allocation function 40 enables the establishment of peak requirements and percentage of total workload for the day for each half-hour time period during the workday. This information is useful in determining the number of vacation hours which are allowed during the vacation/holiday bidding process. As with the vacation shift function 42, the required data is entered via user selected blocks or pop-up windows. The holidays function 44 allows the user to define the holidays which are or are not recognized by the business utilizing the system. The user is able to select holidays and associate them with particular management units on a selective basis. Thus, each management unit need not have the same assigned holidays. The holidays function 44 enables a user to set the holiday date; the day of the week on which the holiday occurs; a description of the holiday, such as Christmas Day, Halloween, etc.; and an indication of whether or not the office is open on the particular holiday. Finally, the add business units function 46 enables a user to enter business unit data, business unit teams, business unit management units, and business unit agents into the vacation scheduler database. The plan object 26 allows for the generated staffing plan requirements downloaded from the force management system 14 to be altered by the user for purposes of determining vacation planning schedules. The staffing plan may be altered using the MU allocations function 48, the build BU requirements function 50, the adjust requirements function 52, or the load data function 54. The load data function 54 downloads employee requirements from a force management system 14. The user is provided with the option of downloading data of several different types. These data types include long-term forecast data providing daily staffing requirements for periods six months or further in the future, active forecast data for current through six months daily staffing requirements, and actual staffing requirements data for filling up staffing requirements for past time periods when a vacation plan is prepared for the current year. The adjust requirements function 52 enables a user to adjust the daily staffing requirements which have been downloaded by the vacation scheduler. These staffing requirements may be changed for either the long-term forecast data, active forecast data or actual data. The build BU requirements function 50 provides the user with the capability for generating long-term, active, or actual and average forecast data for specific dates to determine the BU's forecasted staffing requirements. The MU allocations function 48 enables the user to allocate the BU requirements established by the build BU requirements function 50 to each MU within the BU. During allocation to the management units, the business unit requirements, MU hours of operation, number of agents available each day and available holidays are all considered factors. From the MU allocation function 48, the user may generate management unit allocations, indicate the open and closed status of management units during particular holidays and adjust management unit allocations that have been generated. Referring now to FIGURE 3, there is illustrated a flow chart describing the method for generating management unit allocations. Initially, a variety of data necessary for calculating the number of available vacation days and allocating agent resources is retrieved at step 56. This data includes the business unit staffing requirements for each calendar day of a vacation year, the staffing requirements for each management unit within the business unit for each day of the calendar year, the hours of operation for each management unit, and the total number of available agents for each day of the vacation year. The percentage of available agents which must be allocated to each management unit to meet the requirements for each management unit throughout the vacation year is calculated at step 58. The available business unit requirements are allocated at step 60 to the management units according to the calculated percentages. The number of vacation days allowed is calculated by subtracting at step 62 the number of agents available from the total management unit requirements for the year. The remainder comprises the number of available vacation days. Should the remainder be negative, a zero number of vacation days is assigned at step 64. Using the adjust requirements function 52, a user may alter the number of vacation days allowed for a particular day or group of days as desired. Referring back to FIGURE 2, the calculate vacation days object 28 provides means for generating the number of vacation days earned by each agent for the business in the manner shown in FIGURE 4. Initially, the number of vacation days earned for each agent is calculated at step 70. The total number of earned vacation days are determined using cutoff date, seniority date and vacation table information. Next, personal days are added at step 71 to the total number of vacation days allowed. The total number of floating holidays is further added at step 72 to the number of vacation days. Inquiry step 73 compares the total number of earned vacation days to the number of allowed vacation days determined by the MU allocation functions 48 of the plan object 26. If the number of allowed vacation days is greater than the number of earned vacation days, then the procedure ends at step 74 since all employees will be able to take their vacation days and the MU will be fully staffed. Otherwise, a second pass of the data is performed to reallocate the total number of vacation days allowed since vacation days earned have priority over the number of vacation days allowed. The number of vacation days allowed is calculated at step 78 by subtracting requirements from the agent count. One day of vacation is added at step 80 to the total number of vacation days allowed. One is subtracted from the total agent count at step 82 and from the number of days needed at step 84. Control passes back to inquiry step 73 to determine if additional vacation days are still needed to meet the number vacation days earned. If so, control proceeds back to step 78 for an additional reallocation pass. Otherwise, the procedure ends at step 74. T O Referring again to FIGURE 2, the agent vacation profile object 30 generates vacation profiles for each agent within a management unit for a selected vacation year. The agent vacation profiles consist of identifying data and detailed vacation and holiday data for each agent. FIGURE 5 illustrates an agent vacation profile screen. The agent vacation profile screen comprises several different columns containing information describing each agent within a selected management unit. The agent number column 92, agent name column 94, seniority date column 96 and seniority date extension column 98 comprise the agent identification information. This data may not be changed. The agent password column indicates the password used for enabling an agent access to the bidding object 32. Passwords may be preassigned by entering the password into the appropriate cell for each agent or by allowing the agent to enter their own password during the vacation/holiday bidding process. Each agent's password must be unique for the selected management unit. The work shift week 102 indicates the working shift to which the agent is assigned, and the work week days 104 indicate the number of days included within the work shift. The vacation/holiday bidding object 32 provides the functionality for carrying out vacation and holiday bidding. Upon selection of the bidding object 32, the user is provided with the option of selecting at 1 10 from an agent list. The agent list may be sorted by seniority date or agent name. The agents must bid in seniority date order. That is, the agent with rank order number 1 must bid first, followed by the agent with the rank order number 2, and so on. Should an agent attempt to bid for vacation days out of seniority order, an error message is provided. Upon selection of an agent name, the bidding user is required to enter a password associated with the agent name at 1 1 2. Upon successful validation of the password, entry into the vacation/bidding utilities 1 14 is provided. The summary function 1 1 6 provides a display as shown in FIGURE 6 summarizing the relevant vacation data for a particular agent. The ID summary block 1 18 provides the name of the agent, vacation year being bid upon, the shift and times worked by the selected agent. The vacation/holiday summary block 1 20 provides a complete summary of the total number of vacation days, holidays and alternate vacation days; and the number of vacation and holidays earned selected, taken and remaining with respect to the selected agent. The holiday requirements summary block 1 22 provides a description of the various holidays, the agent requirements for those holidays and the number of requests to work or not work on holidays which have been requested to this point. The calendar function 1 24 provides a user with a complete view of the vacation calendar year as shown in FIGURE 7. From this calendar, the user is able to select vacation days from those indicated as being available. By pointing and clicking on entity selection box 1 26, a user is able to select between vacation days, holidays, or alternate vacation days. Selection from the entity selection box 126 alters the update boxes 128 illustrating the total number of days, the number of days selected and the number of days remaining. The first day of the week selection box 1 30 allows the user to view the vacation calendars with different first days of the week. The example shown in FIGURE 7 illustrates a week running Sunday through Saturday. Alternatively, weeks might be indicated to run Monday through Sunday, or Saturday through Friday. Selection period icons 132 allow the user to select vacation periods of a week 132a, day 132b or partial day 132c. When the week icon 132a is selected, the calendar display 136 is altered to indicate weeks which may be selected or deselected by the user as vacation days. The operation occurs in a similar manner when either the full day or partial day period options are chosen. The vacation calendars are displayed having a variety of different colors to indicate status of particular days on calendar. The colors will be several conditions including, (1 ) a day is not available to be selected, (2) the day is available to be selected, (3) partial day vacation selected, (4) all day vacation selected, (5) holiday, (6) office closed, and (7) alternate vacation day. It should be appreciated by those skilled in the art that the specific embodiments disclosed above may be readily utilized as a basis for modifying or designing other structures for carrying out the purposes of the present invention. It should also be realized by those skilled in the art that such equivalent constructions do not depart from the spirit and scope of the invention as set forth in the appended claims.

Claims: IN THE CLAIMS What is claimed is: 1 . A vacation and holiday scheduling system comprising: a graphical user interface; and a plurality of objects for assisting a business in managing the vacation and holiday scheduling of employees and enabling employees to select vacations and holidays.

Inventors: GREEN EDWIN ELLIOT, GREEN, EDWIN, ELLIOT
Applicants: IEX CORP, IEX CORPORATION
Application year: 1996
Main classification: G06F17
IPC codes: G06Q10