This is initial data I am going to use to calculate working days and hours.
Working Time table
|Day Of Week||Start Time||End Time|
|Monday||10:00 am||6:00 pm|
|Tuesday||10:00 am||6:00 pm|
|Wednesday||10:00 am||6:00 pm|
|Thursday||10:00 am||6:00 pm|
|Friday||10:00 am||6:00 pm|
|Saturday||0:00 am||0:00 am|
|Sunday||0:00 am||0:00 am|
If Start Time = End Time this day is considered as a weekend.
|1/19/2009||Birthday of Martin Luther King, Jr.|
|1/1/2009||New Year’s Day|
Test 1: End date calculation.
|Start Date||The beginning of any process. The date is set by user.|
|Working Duration (Hours)||The duration of the process in hours. Set by user.|
|End Date||The system calculates the End date taking into account holydays and working time.|
On practice it can be used to manage projects or in planning. For example, you need to calculate the end date of anything (working days and hours included).
Test 2: Working time calculation.
|Start Date/Time||The beginning of any process. The date is set by user.|
|End Date/Time||The ending of the process. Set by user.|
|Working Duration (Hours)||The system calculates the duration taking into account holydays and work time.|
For example, one can control SLA in CRM. Let’s take the case you commit yourself to handle the client request within N business hours.
Well, I understand it’s not such an easy task, that’s why I am asking vendors to tune it in their systems if possible. After that I’ll sum up the results so you could compare the implementation (if any at all) in different systems, how easy it is and what skills are required.