Applies to versions: 2.0
1.11 to 2.0 Migration Guide
TimeIPS version 2.0.x offers many upgrades and improvements over version 1.11.x. To make the most of the new version, please review the following changes: Note: Some of the items listed require optional modules, which may or may not be listed in the description of the change.
- IMPORTANT: TimeIPS 2.0.x upgrades all core system components. Some older TimeIPS hardware servers will need a hardware upgrade to run this new version. If you are still running TimeIPS on a hardware server please check compatibility with your model and SN here.
- Managers may need to be aware of the following:
- When using benefits for employees, it is now possible to set the default time-of-day for the benefit to begin, even when the employee has no schedule.
- Improvements have been made to the tags in the system for visually impaired users.
- The Sign Off report includes new modes for showing the "days" on the report. One of the new options bases days on consecutive work which allows employees who work varied shifts and hours to always see their time grouped as expected, even when their work spans multiple actual andl/or work days.
- When using telephone clocking, Spanish language sounds are now available. When and how these are used can be configured under the telephone clocking administration area.
- Walk-up clocks can be set to show text in English or Spanish. This is configured on the General tab for each clock.
- Employee schedules can be configured to prevent them from clocking in late. In this case, when an employee arrives late, they'll need to go see a manager in person to explain their late arrival and get clocked in.
- New "Segments" have been added to Work Orders to track time worked vs. budgeted time. These can be configured for a single work order job, to track time vs. the budget for that job. They can also be configured for groups of jobs, including all jobs on a work order. Alerts can be configured for each segment, to allow managers to know the progress of work vs. budgeted time.
- If all time employees work should be tracked against a job and/or work order, a new retroactive job change mode is available. When enabled, the first change job done by an employee clocked in without a job is special. Instead of processing a job change, the original clock in is updated to the job specified.
- In addition, Administrators need to be aware of the following:
- Complex accrual rules can now be handled automatically using expression logic in the accrual rules configuration.
- Accruals can be configured to run modifications before or after accruals, and a number of special cases, such as when accruals and modifications run at the same time, are handled better. This could cause changes in accrual calculation results, when compared to 1.x system. After upgrade, be sure to review accrual calculations for expected results.
- When employees work part of a shift, it may be desirable to still apply the shift differential to the employee. To accommodate this, there are new options to configure the amount of time that qualifies, and the evaluation of multiple segments of time that are used to figure the qualification.
- In some situations (employees with identical names, badges, SSN, etc.) it can be helpful to have an internally generated unique identifier for each employee on import and export. This is now provided.
- Custom reports and payroll can export files in several formats, including a new XML mode, useful for integration with external systems.
- A new payroll API module (IPSPAPI) allows external systems to run custom reports with up-to-date payroll calculations, including shift differentials, overtime, etc.
- It is now possible to configure holidays that are not paid, but still reduce the weekly 40 hours-for-overtime requirement.
- Work orders have been upgraded with several additional fields to hold details that maybe helpful to employees working on them. A new job routing report is available for work orders that can display large amounts of detail associated with each work order job.
- Overtime policies can now set a different number of hours for weekly overtime/doubletime based on the day of the week. For example, overtime can start after a standard 40 hours on Saturday, but could start after only 32 hours on Sunday.
- Shifts can be configured with Scheduled Shift Hours. These are the expected number of hours per shift. If employees exceed this time per day, and their overtime policy is configured to use shift hours for overtime per day, then employees will go into overtime when these hours are exceeded. This greatly simplifies overtime configuration when the daily hours before overtime varies by shift and employees frequently changes shifts.
- Shifts have new fields for pay code, shift code, status, note and description. These are not required, but can be used to enhance the description and export detail related to shifts.
Was this article relevant to your question? Yes No