Asterisk Time Clock

Commercial and business-oriented Asterisk discussion.

Moderator: Moderator

Asterisk Time Clock

Postby SPMCAsterisk » Tue Mar 23, 2010 4:15 pm

Looking for someone who can build out a Time Clock system in Asterisk using the software PHP Time Clock. We have something in place, but a looking for a more sophisticated solution. A detailed scope is below. Please submit bids to asterisktimeclock@gmail.com.

________________________________________________________________________________________________________

Employee Time Tracking – An interface between a fresh install of the most recent stable release of PHP Time Clock (“PHPTC”) and our in place Asterisk installation shall be created so that employees can dial an extension and interact with PHPTC via telephone handsets located at multiple locations. Basic error checking shall be integrated (e.g. “You are already logged in – if you forgot to clock out last night, please press 1 to enter the date and time of your last clock out.”) Employees will be required to enter an employee ID # and password, which will be defined when first creating the user, in order to clock in and out of the system. This general system and its constituent parts shall be known as the Time Clock System (“TCS”.) * The TCS code should be well-commented for purposes of system maintenance. All efforts should be made to limit the resource consumption of the TCS, since it runs on the same server as Asterisk and must not degrade telecommunications performance.

Scheduling Interface – Web Site interface, integrated into PHPTC, to allow site administrators to enter/edit employee schedules. The Scheduling Interface should be seamlessly integrated with the PHPTC interface, and should also be integrated into the new user creation workflow within PHPTC. The schedule should include start and end times, as well as a lunch break, and a week shall be defined as Tuesday – Monday. A default schedule of 8:00 am – 5:00pm, Monday – Friday, with a 12:00pm – 1:00 pm lunch break, shall be pre-populated upon creation of a new user. The administrator will be allowed to edit the schedule before finalizing creation of the user. The User Schedule shall be editable via the standard PHPTC user modification interface. A report should be added to PHPTC that will allow all Report Users to print the User Working Schedules – standard PHPTC options and formatting should apply, such as being able to choose All users, or certain subsets of users based on Location, Group, or Individual Employee.

Early Clock In – Employees cannot clock in more than X minutes [defined in config file] before their scheduled start time, as defined via the PHPTC Scheduling Interface. If an attempt is made, a message will be played notifying them that they cannot clock in more than 5 minutes before their start time. There should then be a prompt asking whether this is an emergency and giving the option to override and clock in (see item titled “Emergency Handling”.)

Late Clock Out – Employees who clock out more than X minutes [defined in config file] after their scheduled end time will receive a voice notification/warning that they are clocking out after their scheduled working hours.

Lunch Hours – At the time a user clocks out, the TCS should reference the day’s time records, and if it is determined that a lunch was not taken, the employee should be prompted to confirm whether or not a lunch break was actually taken. If no break was taken, the employee should be clocked out, and an audio message should play indicating that lunch breaks, as scheduled, are required. If the employee indicates that they did take a lunch, they should be prompted as to whether or not they clocked out for the break. If they indicate that they did not clock out, they should then be prompted to enter the time that they clocked in and out (“Please enter the time you started your lunch break - Hour? [1 – 12] Minutes? [0 – 59]Press 1 for AM, 2 for PM.[1 or 2] – You entered XX:XX AM/PM, press 1 to confirm, 2 to reenter [they press 1, the lunch clock out is recorded] Please enter the time you returned from your lunch break – Hour? Etc.)

Emergency Handling – Clocking in and out outside of scheduled hours shall be allowed. When this occurs: the employee should be prompted from a list of reasons – emergency call, schedule adjustment by supervisor, other. They will then be allowed to clock in. A note should be entered on the PHPTC time record indicating the reason selected. An email listing the employee name, off-schedule clock-in reason, and date/time should also be sent to the default system email address, property supervisor’s email address, and employee’s email address (all as defined in PHPTC – hereafter referred to as “all email recipients”).

Emergency Call Tracking – Poll CDR records (mysql) daily and identify outgoing calls to our “emergency maintenance lines” that originated from within our Asterisk dial plan (i.e. a resident calls in to a property’s main line and hits 3 for an emergency, which then connects to a cell phone). These call records should be copied to another database, so that stats can be compiled and emailed – See “Automated Reports” below.)

Creation of New Locations – Administrators should be able to use the PHPTC web GUI to seamlessly create new locations. New locations will include a definition of the set of authorized extensions. Clock in/out attempts from an unauthorized extension will go to a pre-recorded message prompting the user to clock in from an authorized device. The local time zone should also be defined, as well as logic for automatically applying an offset for daylight savings time if applicable, and time records for a new location added via this interface should always be recorded as the time zone defined during the creation of the location. The property supervisor’s email address will also be defined in this section.

Time Off Tracking – When a new user is created, there shall be an option to designate that individual as an “Attendance Tracker.” The Attendance Tracker is a property-level login that is a user ID used to mark the opening and closing of the property. The TCS, immediately after an employee has entered their employee ID and password, should check the Attendance Tracker status of the Employee ID. If the Employee ID is marked as an Attendance Tracker, the clock in process will be identical to other employees. However, the clock out process will require the employee, after entering their ID and password but before clocking out, to identify any individuals who were absent from work that day. “Were any employees scheduled for work today absent? Press 1 if yes, 2 if no.” If they select 1 for no, “Thank you for clocking out.” If they select 2 for yes, “Please enter the absent employee’s ID #. [12345] You entered 12345 – Press 1 if this is correct, 2 if you need to reenter the employee ID #. [1] What was the nature of this absence? Please press 1 for Vacation, 2 for Sick, 3 for Personal Day, 4 for Holiday, or 5 for Unpaid Absence. [1,2,3,4,5] Thank you. Were any other employees absent? Etc.” The employee ID entered as being absent should have entries made according to their working schedule for that day, and a note should be recorded for each entry indicating the absence type.

Employee Attendance Tracking – If someone attempts to clock in more than 7 minutes after their scheduled start time, a notification/warning will be sent to all email recipients, and a voice message will notify the user of the number of times they have clocked in late in the past X # of days [definable via config file]. A report should be added to the PHPTC reports section that details the # of late clock-ins for a given time period.

Employee Absence Management – The TCS will help manage internal and external customer expectations by sending a notification if there are any voicemails across our system that have not been listened to in a reasonable amount of time [length of time configurable via config file]. The voicemail on the Asterisk server should be polled every day at 3:00 pm Central, and an email should be sent to phones@companyname.com (perhaps this email address can be included as a definable variable in the system configuration file) summarizing all un-played voicemail messages older than 20 hours (this email will list extension, time message was left, message length, and any other pertinent information).

Employee Trending – Upon clocking out, employees should be notified of their hourly trending for the current workweek, again defined as Tuesday – Monday. The TCS should calculate the total scheduled hours up to that point in the week (e.g. on a Tuesday, for a regular full-time (40 hrs/week) employee, the TCS will return 8 scheduled hours, Wednesday will return 16, Thursday 24, so on to Monday, which will return 40 scheduled hours). The number of hours actually worked should then be calculated. The employee should be notified of the difference between scheduled hours and hours worked, which will be reported as the time trend – (e.g. On Wednesday, there were 16 scheduled hours for the week. The employee recorded 17.4 hours of actual time worked through that day. The TCS should report – “You are trending,” [2], “hours over schedule this week.”[2 = 1.4 rounded up to nearest whole #]) On the last day of the week (Monday), the TCS should calculate the total # of hours, and give the employee a time that they should clock out for the day equal to the time required to avoid going over their scheduled hours. For example, someone has 35 hours recorded going into Monday. They are scheduled to work 5 more hours that week. The TCS should notify them after clocking in that “You should clock out by 1pm today [8:00 am start time + 5 hours remaining scheduled hours] in order to avoid working over your scheduled hours.”

Automated Reporting – Every evening at midnight, a batch of reports will be emailed. The following data should be contained in the emails, with the individual employee receiving the report for just themselves, the property manager receiving an email containing information pertaining to all active employees at their location, and the default system address receiving an email summarizing all active employees:
- Supervisor/System Only - # and details of Emergency Calls
- Employee Display Name
- All time transactions for the day (In, Lunch Out, Lunch In, Out, etc.)
- Number of late clock-ins over the past 90 days
- Trending times (as defined above in “Employee Trending”)
SPMCAsterisk
Newsterisk
 
Posts: 1
Joined: Tue Mar 23, 2010 4:05 pm

Re: Asterisk Time Clock

Postby sub_zero255 » Thu Mar 25, 2010 11:36 am

DId you received the e-mail I sent you from plugworld@micnes.com ??
sub_zero255
Oldsterisk
 
Posts: 102
Joined: Thu May 10, 2007 1:59 pm

Re: Asterisk Time Clock

Postby sub_zero255 » Fri Mar 26, 2010 6:45 am

JamesHarrisburg wrote:How much do these usually cost and how difficult is it to install them?

Send me an email at plugworld@micnes.com and I will send you details.
sub_zero255
Oldsterisk
 
Posts: 102
Joined: Thu May 10, 2007 1:59 pm

Re: Asterisk Time Clock

Postby sub_zero255 » Thu Apr 08, 2010 7:35 pm

Do you mean when changing from summer time zone to winter ?
Yes it will change
sub_zero255
Oldsterisk
 
Posts: 102
Joined: Thu May 10, 2007 1:59 pm


Return to Asterisk Biz & Jobs

Who is online

Users browsing this forum: No registered users and 1 guest