Source: http://www.google.com/patents/US20040098295?dq=5,579,517
Timestamp: 2015-05-26 04:21:03
Document Index: 603906922

Matched Legal Cases: ['art 600', 'art 600', 'art 600', 'art 600', 'art 700', 'art 700', 'art 700', 'art 700', 'art 800', 'art 800', 'art 800', 'art 800', 'art 800']

Patent US20040098295 - Method and system for scheduling workload - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsThe present invention provides for rescheduling workload. A period is selected. A contacts forecasted to be received (CRF) value for the selected period is selected. A contacts forecasted to be handled (CHF) value for the selected period is selected. A volume of contacts that can be handled based on...http://www.google.com/patents/US20040098295?utm_source=gb-gplus-sharePatent US20040098295 - Method and system for scheduling workloadAdvanced Patent SearchPublication numberUS20040098295 A1Publication typeApplicationApplication numberUS 10/714,017Publication dateMay 20, 2004Filing dateNov 14, 2003Priority dateNov 15, 2002Publication number10714017, 714017, US 2004/0098295 A1, US 2004/098295 A1, US 20040098295 A1, US 20040098295A1, US 2004098295 A1, US 2004098295A1, US-A1-20040098295, US-A1-2004098295, US2004/0098295A1, US2004/098295A1, US20040098295 A1, US20040098295A1, US2004098295 A1, US2004098295A1InventorsJohn Sarlay, Paul Leamon, Meghan BarniOriginal AssigneeIex CorporationExport CitationBiBTeX, EndNote, RefManReferenced by (23), Classifications (9), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetMethod and system for scheduling workload
DETAILED DESCRIPTION [0024] In the following discussion, numerous specific details are set forth to provide a thorough understanding of the present invention. However, it will be obvious to those skilled in the art that the present invention may be practiced without such specific details. In other instances, well-known elements have been illustrated in schematic or block diagram form in order not to obscure the present invention in unnecessary detail. Additionally, for the most part, details concerning automatic call distributors, multimedia servers, and the like have been omitted inasmuch as such details are not considered necessary to obtain a complete understanding of the present invention, and are considered to be within the skills of persons of ordinary skill in the relevant art. [0025] It is further noted that, unless indicated otherwise, all functions described herein are performed by a processor such as a computer or electronic data processor in accordance with code such as computer program code, software, or integrated circuits that are coded to perform such functions. [0026] It is still further noted that, while the description of the invention is made in reference to a single contact center, the methods and systems described herein may also be incorporated for and/or across multiple contact centers. The principles of the present invention and their advantages are best understood by referring to the FIGS. 1-11B. [0027] Referring to FIG. 1 of the drawings, the reference numeral 100 generally designates one environment that embodies features of the present invention. The environment 100 is exemplified herein as a contact center environment, though it is understood that other types of environments may constitute the environment 100 as well, and that the environment 100 is not limited to being a contact center environment and may, for example, include environments such as sales force environments, field service environments, manufacturing environments and other types of environments in which tasks must be finished within a certain amount of time. [0028] The environment 100 generally comprises an automatic call distributor (ACD) 110 and a multimedia server 112 coupled to a central processing computer 120 via a network 114, such as a wireline and/or wireless local area network (LAN), a wireline and/or wireless wide area network (WAN), the Internet, an Intranet, or the like. The ACD 110 and multimedia server 112 generally provide routing capabilities for incoming voice calls (via the ACD) and other contacts (via the multimedia server), such as faxes, e-mails, voice mails, web requests, web callback requests, web chats, web voice calls, web video calls, and the like. The function and operation of the ACD 110 and multimedia server 112 are considered to be well known to a person having ordinary skill in the art and, therefore, will not be discussed in further detail herein, except to the extent necessary to disclose the present invention. [0029] The central processing computer 120 receives from the ACD 110 and the multimedia server 112 periodic contact information, such as the number of contacts received and handled for each contact type (“CT”) (i.e., a CT is the type of contact, such as voice call, e-mail, fax, voice mail, web requests, web call-back requests, web chats, web voice calls, web video calls, and the like), the average handling time (“AHT”) of each CT, and the like, and is preferably stored in database 122. Furthermore, there can be multiple CTs for a multimedia server 112. For instance, there can be a CT for Sales E-mail and another for Service E-mail. Furthermore, the system 100 can sort e-mails or other contact types by importance. For instance, an e-mail CT from one customer can be required to be responded to in 3 hours, but an e-mail CT from a second customer can be required to be responded to in 30 minutes. [0030] While the database 122 is shown external to the computer, one skilled in the art will appreciate that the database 122 may be included within the central processing computer 120, or that the data may be retrieved from the ACD 110 and/or the MM server 112, or some other source, when needed instead of storing the data in the database 122. These variations, and others, are considered to be well known to one skilled in the art upon a reading of the present disclosure. [0031] The central processing computer 120 is also coupled via the network 114 to one or more agent workstations 130 and to one or more supervisor workstations 140, which provide an interface between the network 114 and one or more agents 132 and supervisors 142, respectively. The agent workstations 130 and the supervisor workstations 140 are preferably configured to access the central processing computer 120 via the network 114. [0032] Agents 132 access, via telephones (not shown) and agent workstations 130, the ACD 110, multimedia server 112, or other contact servers (not shown) to aid in contact resolution. As the agents 132 service the contacts, the ACD 110 and the multimedia server 112 collect data pertaining to the contacts received and contacts handled and periodically transmit the data to the central processing computer 120, which preferably stores the information in the database 122. [0033] In one embodiment of the present invention, the central processing computer 120 comprises a workforce management system (WMS) 126, such as the TotalView� Workforce Management system available from IEX Corporation. The WMS 126 integrates many management functions, such as workforce forecasting and scheduling, skill planning and scheduling, multimedia contact management, real-time schedule adherence, and the like, and provides an interface to the database 122. Additionally, the WMS 126 generates forecasts of call volumes and call handling times based on historical data, and determines how much staff will be needed at different times of the day and week. Furthermore, these systems have the capability of creating schedules that match the staffing to the anticipated needs. A representative system is described in U.S. Pat. No. 5,325,292, which patent is assigned to the assignee of this application and is incorporated herein by reference for all purposes. The WMS 126 can provide multimedia contact forecasting, planning, and scheduling capabilities. Alternatively, however, a method and/or an apparatus implementing features of the present invention may be designed as a stand-alone component or feature. [0034] In the system 100, the WMS 126 generates initial predictions of the contacts that should be handled by agents (CHF). Generally, CHF represents an initial estimation of the number of contacts that should be handled by agents in the ACD 110. From the CHF value, and other values, such as the number of contacts actually handled (CHA) for a previous time period or periods, the WMS 126 generates a contacts handled intraday value (CHI). Generally, the CHI value can be defined as an updated forecast of the number of contacts that should be handled by agents during a given time period. [0035]FIG. 2 illustrates a flow diagram 200. A current period can be generally defined as a period in which the system 100 makes an original prediction of the number of contacts that can be handled by agents, also known as the contacts handled forecasted, or CHF, and can have also have an associated CHI value for that time period. [0036] After start step 201, in step 202, the system 100 initializes. Initialization occurs when the system 100 starts analyzing data going back a certain amount of time from a time period in question, such as seven days, and retrieving relevant data for the selected time period. Alternatively, it can be for the earliest possible period whose service time affects any period in the range being retrieved, or alternatively, as far back as possible if the relevant data does not exist or is otherwise unavailable. Step 202 defines a time range from a first time, which can be in the past, to a second time, which typically is in the future. In one embodiment, this end of the time range is at the end of the current day. [0037] The relevant data can be as follows. The actual contacts received (CRA) for a given time period or periods, the contacts initially forecasted to be received for a given time period (CRF), the modified forecasted prediction of the number of contacts received (contacts received intraday, or CRI), the contacts that initially were predicted to be handled for a given time period (CHF), and the contacts that were actually handled during a given time period (CHA), if these numbers are available. Received generally refers to contacts that have been delivered to the ACD or multimedia server, and handled refers to contacts that have been completely processed by agents; for example, an e-mail may be received at 3:00 a.m. even though a contact center is not open and this e-mail is considered to be handled once an agent has responded to this e-mail, which may be later that day or even on another day. [0038] In step 203, the number of contacts received intraday (CRI, a modified forecast of the number of contacts to be received) is set equal to the CRF for the same time period, the initial forecast, for the first time period selected by step 202. CRI is set to equal CRF for subsequent time periods. Also, a modified forecast of the number of contacts to be handled during a time period (CHI) is set equal to the number of contacts forecasted to be handled (CHF) for any time period and any or all subsequent time periods. [0039] In step 210, the system 100 determines if the CRA value is available from a previous period from the current period. If the CRA for the previous period is not available, then the CRI, the modified prediction of how many contacts will be received by the contact center 120, is a function of at least the CRF, the original prediction or forecast of how many contacts will be received in step 240. [0040] If the CRA for the previous period is available, then in step 230 the CRI, the modified prediction of how many contacts will be received by the contact center 120, is a function of the CRF, the original prediction or forecast of how many contacts will be received, as well as the CRA, the actual number of contacts that were received in at least one previous period, and the original CRI value for this time period can be overwritten. [0041] In step 250, the method 200 determines whether the forecasting of intraday values CRI is complete when the last time period defined in the time range of step 202 is finished. If not, then step 260 executes, and the period to have the calculated CRI value increments. Then, step 210 is re-executed, and the CRI value for the next period is calculated in either step 230 or step 240, and so on. If the intraday forecasting is complete, stop step 265 executes, and the CRI generation is finished. One general goal of this processing is to recalculate how many contacts are expected to be received and to calculate a new plan for handling contacts for the current and future periods. [0042] Turning now to FIG. 3, a high-level flow diagram 300 illustrates rescheduling a contacts handled intraday value to a current period. Specifically, the contacts handled intraday (CHI) value for a current period can be generally defined as the number of contacts that are planned to be handled during the current period, after a modification of that estimation is allowed to occur. [0043] In step 302, a preliminary contacts handled intraday value (pre-CHI) for the current period is determined by propagating at least part of a contacts received value to the current period. If the CRA contact information for a time period is available, then the CRA value is propagated. If the CRA contact information is not available, then the CRI value is propagated. For instance, for a time period, say 8:00 am, the contacts handled forecast (CHF) is the result of handling contacts received from earlier periods that are scheduled to be handled during this time period. The contacts received from each of these earlier periods is then summed and yields pre-CHI, and the CHI is set equal to the pre-CHI. In other words, the pre-CHI represents the base point from which CHI recalculations use as the initial variable. A more detailed propagation scheme is described in a patent application Ser. No. 09/919,302, titled “METHOD FOR FORECASTING AND MANAGING MULTIMEDIA CONTACTS,” which patent application is assigned to the assignee of this application and is incorporated herein by reference for all purposes. [0044] Propagation of contacts can be governed by service time or quality of service. Generally, service time is the length of time allotted to respond to a given contact. For instance, e-mails may have a 4 hour response from the time they are received, although telephone calls are generally answered within seconds or minutes of being received. These values would both affect propagation, as the telephone calls would be distributed over a narrower response time than the e-mails. Furthermore, the quality of service can differ within a contact type. For instance, e-mails from different customers or contacts could have different priorities for allotted response time. E-mails from customer “A” are to be responded to in three hours, but e-mails from “B” are to be responded to in one hour. [0045] In step 304, it is determined whether the number of contacts actually handled (CHA) in the previous period is available. For various reasons, the number of contacts actually handled in the previous period may or may not be available. For instance, this time period could be in the future, in which case, actual data does not yet exist. [0046] If it is determined in step 304 that the number of contacts actually handled in the previous period is available, then in step 308, the CHI value for this time period is updated by adjusting the pre-CHI value based on the difference, or carryover, between the updated number of contacts planned to be handled in a previous period (CHI) and the number of contacts actually handled in the previous period (CHA). [0047] If it is determined in step 304 that the number of contacts actually handled in the previous period is not available, in step 312, a CHI value is updated by adjusting the pre-CHI value based on the difference between the modified number of contacts planned to be handled in a previous period (CHI) and the number of contacts scheduled to be handled in the previous period (CHS). [0048] The number of contacts scheduled to be handled in a given period (Contacts_Handled_Scheduled or CHS) is calculated using the following equation: Contacts_Handled  _Scheduled = ( ScheduledOpen � SecondsInStatisticsPeriod AHTInSeconds  ) [0049] where: [0050] “ScheduledOpen” is the number of agents who are scheduled to be available in the given period; [0051] “SecondsInStatisticsPeriod” is the length in seconds of the given period; and [0052] “AHTInSeconds” is an average handling time in seconds for the given period. [0053] Generally, a distinction between CHS, CHF and CHI can be stated as follows. The CHF and CHI values refer to the number of contacts that should be handled by the agents. CHF generally refers to the original forecasted number of contacts that should be handled. CHI is the updated forecast of the number of the contacts that should be handled. CHS, however, refers to the contacts which can be handled based upon the agent schedules, and considers variations in agent schedules, lunch breaks, and so on. [0054] Generally, in either step 308 or step 312, CHI is calculated, overwriting the original CHI value derived in step 203 of method 200. Then, typically, the contact center 120 attempts to have the CHS correspond to the CHI value as closely as possible. [0055] In either case, either of the steps 308 and 312 leads to step 314 in which the method 300 determines whether there is an overflow or underflow of backlogged contacts to be processed in the ACD 110, as illustrated and described in relation to method 900 of FIG. 9. If there is an overflow or underflow, then the method 300 can increase or decrease the CHI values for the current time period and future time periods, as illustrated in method 900 of FIG. 9. After the backlog processing is ended, the method 300 stops in step 320. There are various ways of defining and measuring and responding to backlog. This can either measure and respond to predicted backlog or an actual backlog. The backlog can also be measured and responded to as a function of a service time level, wherein a percentage or absolute value of the backlog has exceeded or is close to exceeding its allotted service time. [0056] One general idea is that the revised plan for when to handle contacts will take into account periods where fewer or more contacts were actually handled than originally planned, as well as consider the number of contacts that can be handled by the staffing level. [0057]FIG. 4 is a low-level flow diagram 400 illustrating the step 308 of method 300. Step 308 relates to obtaining the contacts handled intraday (CHI) value when the number of contacts actually handled (CHA) in the previous period is available. [0058] After a start step 401, in step 402, it is determined whether the modified forecast of the number of contacts to be handled (CHI) for the previous period is greater than the number of contacts actually handled (CHA) in the previous period. If it is determined in step 402 that the CHI of the previous period is greater than the CHA in the previous period, the adjusted CHI value for the present period in step 404 is obtained by increasing the preliminary CHI value by the difference between the number of CHI in the previous period and the CHA in the previous period. This is the output of CHI value for step 308. [0059] However, if it is determined in step 402 that the CHI of the previous period is not greater than the CHA in the previous period, the CHI value is set to the preliminary contacts handled intraday value in step 406. This then is the output CHI value for step 308. In either event, the method ends in step 410. Generally, the contacts handled intraday (CHI) for a period is basically being adjusted to account for the difference between the contacts that were planned to be handled in a prior period and the contacts that were actually handled in that prior period. [0060]FIG. 5 is a low-level flow diagram 500 illustrating the step 312, the step of obtaining the CHI value for the present period when the CHA of the previous period is not available. [0061] After start step 501, in step 502, it is determined whether CHI in the previous period is greater than the number of contacts scheduled to be handled in the previous period. If it is determined in step 502 that the CHI in the previous period is greater than the number of CHS in the previous period, the CHI value in step 504 of the present period is derived by increasing the preliminary CHI value by the difference between the number of CHI value a previous period and the CHS to be handled in the previous period. This is the output CHI value from step 508. [0062] If it is determined in step 502 that the CHI in the previous period is not greater than the CHS to be handled in the previous period, the CHI value of the present period is set to the preliminary CHI value in step 506. This is the output CHI value from step 312. In either event, the method ends in step 508. [0063] In a further embodiment, the system that manages non-immediate need contacts (for example, the WMS 126 of FIG. 1) can report actual backlog information using two values that are summed to get the actual total backlog. The first value is called an actual expired backlog and represents contacts that still need to be handled that were not handled within a service level goal time. For example, if the goal is to handle 100% of e-mails within 4 hours, and 10 e-mails have been in queue for more than 4 hours, then the actual expired backlog will be equal to 10. The other value is called an actual unexpired backlog and represents the number of contacts that still need to be handled that were in queue less than the service level goal time. For example, suppose 90 contacts are in the actual unexpired backlog. In this example, with 10 contacts in the actual expired backlog and 90 contacts in the intraday unexpired backlog, the actual total backlog is the sum or 100. Accordingly, if the e-mail (or other contact handling) system reports any 2 of these 3 values, the third value can be determined. So, if there are 100 contacts in actual total backlog and 10 are expired, then we know that 90 are unexpired. [0064] Actual backlog values can also be used to predict backlog in the future. The backlog in the future is called intraday backlog and has three components just as the actual backlog. That is, the intraday total backlog includes two components, intraday unexpired backlog and intraday expired backlog. The intraday total backlog can be determined by calculating the intraday total backlog, the intraday unexpired backlog and then taking the difference to calculate the intraday expired backlog. If any two of the three are known the other can be calculated. [0065] The intraday total backlog is calculated by taking the actual total backlog when calculating the intraday value for the current time period. For future time periods, the intraday total backlog is calculated by taking the intraday total backlog from the previous period and adding to that the CRF in this period and subtracting the contacts handled scheduled for this period. If the resulting number is negative, then the value used for this period's intraday total backlog is then set to zero, since for the resulting number to be negative, there is more work time to handle contacts than the work time it takes to handle contacts that are in the backlog in this period. If the intraday total backlog is zero then the intraday expired backlog and intraday unexpired backlog values are also zero. [0066] The intraday unexpired backlog is calculated by taking the actual unexpired backlog when calculating the intraday value for the current time period. For future time periods, the intraday unexpired backlog is calculated by taking the intraday unexpired backlog from the previous period and adding the CRF value for this time period and subtracting the number of contacts that will expire this period. [0067] Since the intraday total backlog and intraday unexpired backlog have been calculated, then the intraday expired backlog is calculated by taking intraday total backlog and subtracting the intraday unexpired backlog. Alternatively, one skilled in the art could calculate any two of the three intraday backlogs and derive the other. [0068] In the WMS 126, it is helpful to provide management visibility into the changing conditions in the contact center throughout the day. For actual and intraday backlog values, there are a number of ways to display the data in static screens and reports as well as screens that are updated in real time as more data or data changes are made. For example, a representative system such as the WMS 126 shows backlog data on a screen in table and graphical chart formats in addition to reports. The screens are updated in real time. [0069] Preferably, both the actual and intraday backlog data could be drilled down to show the number of contacts in the expired and unexpired backlog based on the last statistic period update from the e-mail system. In addition, a real-time feed could provide real-time statistics as to how many contacts are in the actual expired backlog and the actual unexpired backlog. [0070] In the management of these contacts, it is helpful for the management team to have a view into the future so that problems can be anticipated or predicted and therefore avoided. The reports and/or charts of intraday backlog data can give management the information they need to prevent contacts from being handled too late. In the example of e-mails, backlogged e-mails may cause customers to call in and be handled by a phone call, thereby increasing the actual workload of the company. This most likely increases customer dissatisfaction. If the backlog gets too large, then it can be difficult to catch up; however, if the backlog gets too small, then the agents handling the contacts may not have any work to do during the slow periods of the day. [0071] Now referring to FIG. 6, a line chart 600 illustrates actual backlog data. The line chart 600 shows actual backlog data during past periods. Specifically, the line chart 600 shows actual expired backlog data 602, actual unexpired backlog 604, and actual total backlog 606 over three periods 8:00-8:30 a.m., 8:30-9:00 a.m., and 9:00-9:30 a.m. Note that the time marks (e.g., 8:00, 8:30, and 9:00) on the x-axis indicate periods starting from the time marks and ending half an hour later. [0072] It is important for a management team to notice that after the 8:30-9:00 period, the expired backlog 602 is greater than 0, since there are 10 contacts in the expired backlog 602, and action might be needed to catch up. For example, meetings or training time might be cancelled or overtime might be scheduled. It is clear from the line chart 600 that the contact center is getting further behind, since after the 9:00-9:30 period, the expired backlog 602 has increased to 20 from 10. [0073] Now referring to FIG. 7, a line chart 700 illustrates an expired backlog prediction using actual and intraday expired and unexpired backlog data. The line chart 700 shows an intraday backlog expired at the beginning of each period 702, backlog contacts that expire in each period 704, contacts handled scheduled 706, and intraday expired backlog at the end of each period 708. [0074] The line chart 700 is useful for management, because it provides an understanding of when the contacts that are in the unexpired backlog will expire. Preferably, this data could be shown to predict when contacts would move from the unexpired backlog to the expired backlog. This provides an intraday view of the expired backlog. [0075] At 9:00 a.m., the actual unexpired backlog is 110 contacts. Preferably, another drill-down view of this unexpired backlog can be given along with contacts handled scheduled and intraday expired backlog for future periods. In the line chart 700, 110 contacts are unexpired. These are distributed as indicated by the backlog contacts that expire in each period 704-that is, 30 backlog contacts expire in each of the 9:30-10:00, 10:00-10:30, and 10:30-11:00 periods with the remaining 20 expiring in the 11:00-11:30 period. There are enough agents to handle 20 contacts in each of the 9:30-10:00, 10:00-10:30, and 10:30-11:00 periods with the ability to handle 10 contacts in the 11:00 period as shown with the contacts handled scheduled data 706. The intraday expired backlog 708 is shown and gives management time to prevent too many contacts from being handled too late by showing at 9 am that the system predicts that by 11:30 am there will be 60 contacts in the expired backlog. With this information, management may decide to cancel some meetings or schedule overtime to handle these contacts on time. [0076]FIG. 8 is a line chart 800 illustrating a future trend of an intraday total backlog. The line chart 800 shows an intraday total backlog 802 over various time periods. The line chart provides a high threshold 804, a low threshold 806, and a target threshold 808 for backlog management. These thresholds could be static, could vary throughout the day or could be a function of contact volume, staff, intraday expired projections, any combination of these or other measures as deemed appropriate by the management team. In the line chart 800, static thresholds are assumed. These thresholds can be applied to the actual total backlog, actual expired backlog, actual expired backlog plus backlog that will expired in that period, actual unexpired backlog intraday total backlog, intraday expired backlog, intraday expired backlog plus backlog that will expired in that period, and/or intraday unexpired backlog. However, those of skill in the art will understand that other approaches for measuring and responding to backlog are within the scope of the present Application. In the line chart 800, however, only the total backlog 800 is shown. [0077] The high threshold 804 is set to 200, the target threshold 808 is set to 150, and the low threshold 806 is set to 100. It is important for management to know when the total backlog 802 exceeds the high threshold 804 or goes lower than the low threshold 806. In the line chart 800, the total backlog 802 exceeds the high threshold 804 at a first point 810. Similarly, the total backlog 802 goes lower than the low threshold 806 at a second point 812. These are important data points to draw attention to since the time between the current time and those events gives management time to react (e.g., time durations 814 and 816) and avoid having backlog get too high or too low. [0078] Turning now to FIG. 9, illustrated is a method 900 for altering the CHI value of the present period as a function of backlog. After start step 910, the method 900 determines the backlog of the workload as a function of the backlog in step 920. The backlog can be a function of the carryover (that is, the difference between the number of contacts that were planned to be handled and the number of contacts that were actually handled) or some other relevant variable. [0079] In step 930, it is determined whether the backlog is greater than a threshold value. The threshold value can be a function of contact volume, staffing levels, or some other measure, or could be determined empirically by the management team. The method then stops in step 950. If it is determined that the backlog is below a set threshold, the method ends in step 950. [0080] However, if it is determined that the backlog is greater than a threshold value, in step 940, the CHI value for the present period and, perhaps, future periods, is increased to handle the backlog. This can occur by distributing the CHI increase among a plurality of periods, or can occur to handle the backlog within a single period, is within the scope of the present application. [0081] Turning now to FIGS. 10A and 10B, illustrated is a propagation of contacts from a CRF value to be distributed through different time periods before actual data has been received. An example of the use of methods 200-500 shall be illustrated with the aid of FIGS. 10A and 10B. [0082] In FIG. 10A, the earliest time that the method concerns itself with determining CHF or CRF is 8:00 am. In FIG. 2, in step 202, the example assumes a service time of 2 hours, so the time back for the present time is 6:30 am. In other words, in 10A and 10B, 6:30 am represents the earliest period that has a CRI that has been distributed to the present time period, because contacts received during the 6:30 am time period are to be handled by 8:30 am (that is, during the 8:00 am to 8:30 am time period). In FIGS. 10A and 10B, a portion of contacts from 6:30 am, 7:00 am, 7:30 am and 8:00 am are propagated into the 8:00 am time period as the basis for determining how many contacts are planned to be handled during the 8:00 am time period. [0083] In the system 100, typically there are always CHI values for a period, even though values in the example of FIGS. 10A and 10B are shown at 8:00 am. The initial CHI value is set to the CHF value for that first period. There will always be a CHF value for the first period. [0084]FIGS. 10A and B are discussed in relation to 8:30. For ease of illustration, the time period of 8:30 is processed. In step 202, the CRF values, the CRI values and the CHF values are all initially calculated or obtained in step 202 of step 203. In step 203, the CRI value for 8:00 am is the same as the CRF value forecasted for 8:00 am. Furthermore, the CHI value for forecasted for 8:00 am is the same as the CHF value forecasted for 8:00 am. Thus, the CHI is set equal to the CHF as a default value for this time period. [0085] In step 210, is a CRA value for 8:30 am available? No, there have been no actual contacts recorded. Therefore, in step 240, CRI is a determined as a function of CRF. In this case, CRI is set equal to CRF, and the CRI value is not overwritten. The setting of CRI continues until CRI values for the rest of the time periods in question, such as 8:30 a.m. through 3:00 p.m., are calculated. [0086] After all the CRI values are calculated, then method 300 begins. In method 300, the CHI values for the time periods are calculated; the setting up of CHI to equal CHF can be overwritten for any time period other than the first time period of 8:00 am. [0087] In step 302, the pre-CHI value is determined as illustrated in FIG. 10. In step 302, the pre-CHI of a selected period is equal to the sum of the vertical propagated CRI values for that time period. Because CRI is equal to CRF, the pre-CHI values will also be equal to the CHF values. For instance, in FIG. 10A, for 8:00 am, the propagated values are 25, 23, 20 and 24. This equals 92, the pre-CHI value. [0088] In the method 300, CRI will be equal to CRF if there are no actual values of contacts received (CRA) for any time period being processed—for instance going back in time 7 days to get data to the selected period. Typically, there will be actual values at some period prior to the selected point, so there can be variation between the CRF and the CRA. However, even if there is not a difference between CRF and CRA, the CHS values can affect the CHI values. Therefore, method 300 is still employed, and pre-CHI is defined. In other words, in step 302, pre-CHI is still equal to the propagated CHF values for the selected period. [0089] In step 304, is the number of contacts actually handled (CHA) available? In FIGS. 10A and B, the answer is “no”. Therefore, CHI is determined by adjusting the pre-CHI value based on the difference between the CHI for the previous period and the CHS value for the previous period. Because this is step 312, this invokes method 500, that illustrates how to calculate the difference. In method 300, if the CHS value for the previous period is greater than the CHI value for the previous period, the difference, (the “carryover”), is zero, as illustrated in FIGS. 10A and 10B. Treatment of any backlog is then determined as per method 900. [0090] Turning now to FIGS. 11A and 11B, illustrated is a propagation of contacts after the actual contact information has been received. For instance, in FIGS. 10A and 10B, for the time period of 8:30 am, the (vertically) propagated CRI contact values are 23, 20, 24 and 19, to pre-CHI total 86. However, in FIGS. 11A and 11B for the time period of 8:30 am, the vertically propagated CRA and CRI contacts are 23, 20, 26, and 23, to yield a total of 92, a different pre-CHI value than derived in for a pre-CHI value for FIGS. 10A and 10B because CRA contacts have also been taken into account when determining the pre-CHI values. The CRF values were generated in method 200 as illustrated in FIGS. 10A and B, and are the same. However, CRA values exist up until 11:00 am in the morning in FIGS. 11A and 11B, which will affect how the CHI values are calculated for periods of 11:00 am and before. [0091] For example, at 11:00 am, in step 210 of FIG. 2, the CRA is available for the previous period. Therefore, the CRI is determined as a function of the CRF and the CRA in step 230. However, for later time periods, there is no CRA, so the CRI is left as a function of CRF in step 240. [0092] Then, in FIGS. 11A and 11B, the pre-CHI values are calculated, using CRA values as well as CRI values in the pre-CHI determination. In step 302, the pre-CHI values are determined by summing the vertical CRA or CRI values which terminate in the same period. For instance, at 11:30 am, the pre-CHI is 25+27+22+19=93. [0093] In step 304, it is determined whether the number of contacts handled (CHA) in the previous period is known. For instance, for 11:00 am, the CHA value is known for 10:30, the previous period, CHI is a function of adjusting the Pre-CHI value for 11:00 am (102) by the difference between the CHI for the previous time period (165) and the CHA (80). Because step 308 was invoked and the number of contacts planned to be handled in previous period (CHI) is greater than the number of contacts actually handled, the CHI is increased by the difference. Therefore, CHI for 11:00 am is 187. [0094] For 11:30, however, the CRA value for the previous period is not available. Therefore, CRI is the same as CRF for this period. Once Pre-CHI is calculated for this period (93), it is determined that the number of contacts in the previous period is not available in step 304. Therefore, step 312 is invoked. The CHI value for 11:30 is based on the difference between the CHI for the previous period (189) and the CHS for the previous period (120). Because this is step 312, step 500 is invoked. Because the CHI of the period is greater than the CHS of the previous period, in step 504, the CHI value uses the pre-CHI value and increases by the difference between the CHS value and the CHI value of the previous period. For 11:30 this difference between CHI (187) and CHS (120) of the previous period is 67. In FIG. 11B, 67 is added to the pre-CHI value of 93, to get a CHI value of 160. [0095] The various acronyms used above are merely for purposes of illustration. This particular nomenclature is not intended to limit the scope of the invention. [0096] It is understood that the present invention can take many forms and embodiments. Accordingly, several variations may be made in the foregoing without departing from the spirit or the scope of the invention. [0097] Having thus described the present invention by reference to certain of its preferred embodiments, it is noted that the embodiments disclosed are illustrative rather than limiting in nature and that a wide range of variations, modifications, changes, and substitutions are contemplated in the foregoing disclosure and, in some instances, some features of the present invention may be employed without a corresponding use of the other features. Many such variations and modifications may be considered obvious and desirable by those skilled in the art based upon a review of the foregoing description of preferred embodiments. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the scope of the invention. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7386105May 27, 2005Jun 10, 2008Nice Systems LtdMethod and apparatus for fraud detectionUS7436887Feb 6, 2003Oct 14, 2008Playtex Products, Inc.Method and apparatus for video frame sequence-based object trackingUS7546173Aug 18, 2003Jun 9, 2009Nice Systems, Ltd.Apparatus and method for audio content analysis, marking and summingUS7573421Sep 24, 2002Aug 11, 2009Nice Systems, Ltd.System and method for the automatic control of video frame rateUS7577246Dec 20, 2006Aug 18, 2009Nice Systems Ltd.Method and system for automatic quality evaluationUS7631046Oct 26, 2006Dec 8, 2009Nice Systems, Ltd.Method and apparatus for lawful interception of web based messaging communicationUS7683929Dec 26, 2002Mar 23, 2010Nice Systems, Ltd.System and method for video content analysis-based detection, surveillance and alarm managementUS7714878Aug 9, 2004May 11, 2010Nice Systems, Ltd.Apparatus and method for multimedia content based manipulationUS7716048Jan 25, 2006May 11, 2010Nice Systems, Ltd.Method and apparatus for segmentation of audio interactionsUS7728870Apr 26, 2004Jun 1, 2010Nice Systems LtdAdvanced quality management and recording solutions for walk-in environmentsUS7761544Mar 6, 2003Jul 20, 2010Nice Systems, Ltd.Method and apparatus for internal and external monitoring of a transportation vehicleUS7770221May 18, 2006Aug 3, 2010Nice Systems, Ltd.Method and apparatus for combining traffic analysis and monitoring center in lawful interceptionUS7801288Feb 29, 2008Sep 21, 2010Nice Systems Ltd.Method and apparatus for fraud detectionUS7822605Oct 19, 2006Oct 26, 2010Nice Systems Ltd.Method and apparatus for large population speaker identification in telephone interactionsUS7953219Jul 18, 2002May 31, 2011Nice Systems, Ltd.Method apparatus and system for capturing and analyzing interaction based contentUS8005675Mar 17, 2005Aug 23, 2011Nice Systems, Ltd.Apparatus and method for audio analysisUS8060364Nov 13, 2003Nov 15, 2011Nice Systems, Ltd.Apparatus and method for event-driven content analysisUS8571853Feb 11, 2007Oct 29, 2013Nice Systems Ltd.Method and system for laughter detectionUS8724891Aug 31, 2004May 13, 2014Ramot At Tel-Aviv University Ltd.Apparatus and methods for the detection of abnormal motion in a video streamUS8725518Apr 25, 2006May 13, 2014Nice Systems Ltd.Automatic speech analysisUS20110206198 *May 2, 2011Aug 25, 2011Nice Systems Ltd.Method, apparatus and system for capturing and analyzing interaction based contentUS20120296696 *Feb 17, 2012Nov 22, 2012International Business Machines CorporationSustaining engineering and maintenance using sem patterns and the seminal dashboardWO2006082591A2 *Feb 7, 2006Aug 10, 2006Yoel GoldenbergUpgrading performance using aggregated information shared between management systems* Cited by examinerClassifications U.S. Classification705/80International ClassificationG06Q99/00, H04M3/523Cooperative ClassificationH04M3/5232, G06Q50/188, G06Q99/00, H04M2203/402European ClassificationG06Q50/188, G06Q99/00Legal EventsDateCodeEventDescriptionNov 14, 2003ASAssignmentOwner name: IEX CORPORATION, TEXASFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SARLAY, JOHN DAVID;LEAMON, PAUL HAROLD;BARNI, MEGHAN;REEL/FRAME:014768/0183Effective date: 20031114RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services