| Location: | Ohio |
|---|---|
| Posted: | Oct 16, 2026 |
| Due: | Nov 6, 2026 |
| Agency: | City of North Olmsted |
| Type of Government: | State & Local |
| Category: |
|
| Publication URL: | To access bid details, please log in. |
| Description | Opening Date | Closing Date |
|
Time, Attendance and Scheduling Software RFP Questions & Answers |
October 14, 2026 : |
November 06, 2026 2:00 PM |
| Current Systems & Integration | |||
|---|---|---|---|
| 1. Could you provide the names of the timekeeping and scheduling systems currently used across the | |||
| City, including which departments use each solution? | |||
| * Administrative (Council/Mayor/HR/IT/Finance/Law/Rec Dir/Service Dir/Econ Dir), Senior | |||
| Center, Pantry, Court, Engineering and Building - manual scheduling, tracking and recording | |||
| * Service, Fleet and WasteWater Treatment Plant - Aladtec for scheduling and timekeeping | |||
| * Police - Manual scheduling and timekeeping | |||
| * Fire - Aladtec for scheduling and timekeeping | |||
| * Parks and Recreation - Aladtec for scheduling and timekeeping | |||
| * Springvale - Aladtec for scheduling and timekeeping | |||
| 2. Does the City currently utilize an automated interface with Tyler Munis for any of these systems, or | |||
| is all time data manually entered into payroll? | |||
| * Manual payroll entry | |||
| 3. Which version of Tyler Munis is currently in use, and does the City have an established integration | |||
| method or preferred interface for exchanging payroll and employee data? | |||
| * Munis Version 2024.4 moving to 2026.2 on November 5th | |||
| * Currently printing payroll vouchers each pay with various pay types and rates using Crystal | |||
| Reports. Hours are manually added to the sheet, returned to Finance for entry. | |||
| Employee Groups & Payroll Rules | |||
| 1. Are there collective bargaining agreements or union-specific requirements that will need to be | |||
| accommodated? If so, how many bargaining units are involved? | |||
| * Yes, there are six (6) union contracts that need to be accommodated - AFSCME Clerical | |||
| Tech, AFSCME Service, FOP, IAFF, Dispatch and Corrections | |||
| 2. Are there specific overtime rules, shift differentials, holiday premiums, or other unique pay policies | |||
| that vary by department? | |||
| * Yes, each union has their own special pays and overtime rules. | |||
| 3. Approximately how many supervisors, managers, and payroll administrators will require access to | |||
| review, approve, or manage employee time? | |||
| * Approximately 7 payroll administrators, 10-12 managers, 7 Directors, and 1 Finance overall | |||
| approver (this workflow could change through automation, however) | |||
| 4. Does the City require employees to allocate time across multiple departments, projects, grants, or | |||
| cost centers within the same pay period? | |||
| * Time is not usually allocated based on projects. Some employees have separate jobs at Rec | |||
| Center and Springvale. Police sometimes allocate time between Police, Court and Council. | |||
| Service can use cost centers from the Street Fund and the General Fund. | |||
| Scheduling & Leave Management | |||
| 1. Are Police, Fire, and Wastewater currently using dedicated scheduling applications? If so, which | |||
| systems? | |||
| * See question 1. | |||
| 2. Beyond standard scheduling, does the City require capabilities such as rotating shifts, shift trades, | |||
| open-shift bidding, minimum staffing requirements, certification-based assignments, or automated | |||
| overtime management? |
Current Systems & Integration
1. Could you provide the names of the timekeeping and scheduling systems currently used across the
City, including which departments use each solution?
* Administrative (Council/Mayor/HR/IT/Finance/Law/Rec Dir/Service Dir/Econ Dir), Senior
Center, Pantry, Court, Engineering and Building - manual scheduling, tracking and recording
* Service, Fleet and WasteWater Treatment Plant - Aladtec for scheduling and timekeeping
* Police - Manual scheduling and timekeeping
* Fire - Aladtec for scheduling and timekeeping
* Parks and Recreation - Aladtec for scheduling and timekeeping
* Springvale - Aladtec for scheduling and timekeeping
2. Does the City currently utilize an automated interface with Tyler Munis for any of these systems, or
is all time data manually entered into payroll?
* Manual payroll entry
3. Which version of Tyler Munis is currently in use, and does the City have an established integration
method or preferred interface for exchanging payroll and employee data?
* Munis Version 2024.4 moving to 2026.2 on November 5th
* Currently printing payroll vouchers each pay with various pay types and rates using Crystal
Reports. Hours are manually added to the sheet, returned to Finance for entry.
Employee Groups & Payroll Rules
1. Are there collective bargaining agreements or union-specific requirements that will need to be
accommodated? If so, how many bargaining units are involved?
* Yes, there are six (6) union contracts that need to be accommodated - AFSCME Clerical
Tech, AFSCME Service, FOP, IAFF, Dispatch and Corrections
2. Are there specific overtime rules, shift differentials, holiday premiums, or other unique pay policies
that vary by department?
* Yes, each union has their own special pays and overtime rules.
3. Approximately how many supervisors, managers, and payroll administrators will require access to
review, approve, or manage employee time?
* Approximately 7 payroll administrators, 10-12 managers, 7 Directors, and 1 Finance overall
approver (this workflow could change through automation, however)
4. Does the City require employees to allocate time across multiple departments, projects, grants, or
cost centers within the same pay period?
* Time is not usually allocated based on projects. Some employees have separate jobs at Rec
Center and Springvale. Police sometimes allocate time between Police, Court and Council.
Service can use cost centers from the Street Fund and the General Fund.
Scheduling & Leave Management
1. Are Police, Fire, and Wastewater currently using dedicated scheduling applications? If so, which
systems?
* See question 1.
2. Beyond standard scheduling, does the City require capabilities such as rotating shifts, shift trades,
open-shift bidding, minimum staffing requirements, certification-based assignments, or automated
overtime management?
| * There are currently shift trades in a number of departments. There is likely to be a | |||
|---|---|---|---|
| preference for some departments | |||
| 3. Does the City intend to replace all existing scheduling solutions, or would certain departmental | |||
| systems remain in place and require integration? | |||
| * The City intends to move all current timekeeping systems to a new system or implement | |||
| new systems. Timekeeping and scheduling systems would change for some and not be | |||
| needed for others. | |||
| 4. Are leave accruals and balances currently maintained within Munis, and should Munis remain the | |||
| system of record for this information? | |||
| * Accruals and balances are maintained within Munis and best-case scenario would keep it | |||
| this way or have the new system have a matching/reconciled balance with Munis. | |||
| Time Collection & Hardware | |||
| 1. Approximately how many physical time clocks does the City anticipate needing, and at which | |||
| locations? | |||
| * This depends, physical time clocks are variable if clocking in is also an option on a web | |||
| browser or app. | |||
| 2. Does the City have a preferred employee authentication method, such as proximity badges, PINs, | |||
| or biometric verification? | |||
| * The City is open to all options. | |||
| 3. Would the City prefer a combination of physical clocks, mobile applications, and web-based time | |||
| entry depending on departmental needs? | |||
| * The City is open to all options based on departmental needs. | |||
| 4. Are there existing employee identification badges or time clocks the City would like to continue | |||
| using? | |||
| * There is not preference for current ID badges or time clocks but there could be fiscal | |||
| constraints to adopting all new. | |||
| Implementation & Project Scope | |||
| 1. Does the City anticipate implementing all departments simultaneously, or would a phased rollout | |||
| be preferred following the June 1, 2027 pilot? | |||
| * Implementation either all at once or a phased rollout is fine. | |||
| 2. Which departments or employee groups are expected to participate in the initial pilot? | |||
| * At a minimum the departments currently using our current system (Aladtec) to avoid | |||
| overlapping costs of having two software payments while implementing.. | |||
| 3. Is historical timekeeping and scheduling data migration required? If so, how much historical | |||
| information should be included? | |||
| * If Munis cannot be the system of record, we would expect the new system to migrate over | |||
| at least 10 years. If Munis remains the system of record ideally a back to January 1 of the | |||
| implementation year | |||
| 4. Has the City established a project budget or anticipated investment range for software, hardware, | |||
| implementation, and ongoing support? |
* There are currently shift trades in a number of departments. There is likely to be a
preference for some departments
3. Does the City intend to replace all existing scheduling solutions, or would certain departmental
systems remain in place and require integration?
* The City intends to move all current timekeeping systems to a new system or implement
new systems. Timekeeping and scheduling systems would change for some and not be
needed for others.
4. Are leave accruals and balances currently maintained within Munis, and should Munis remain the
system of record for this information?
* Accruals and balances are maintained within Munis and best-case scenario would keep it
this way or have the new system have a matching/reconciled balance with Munis.
Time Collection & Hardware
1. Approximately how many physical time clocks does the City anticipate needing, and at which
locations?
* This depends, physical time clocks are variable if clocking in is also an option on a web
browser or app.
2. Does the City have a preferred employee authentication method, such as proximity badges, PINs,
or biometric verification?
* The City is open to all options.
3. Would the City prefer a combination of physical clocks, mobile applications, and web-based time
entry depending on departmental needs?
* The City is open to all options based on departmental needs.
4. Are there existing employee identification badges or time clocks the City would like to continue
using?
* There is not preference for current ID badges or time clocks but there could be fiscal
constraints to adopting all new.
Implementation & Project Scope
1. Does the City anticipate implementing all departments simultaneously, or would a phased rollout
be preferred following the June 1, 2027 pilot?
* Implementation either all at once or a phased rollout is fine.
2. Which departments or employee groups are expected to participate in the initial pilot?
* At a minimum the departments currently using our current system (Aladtec) to avoid
overlapping costs of having two software payments while implementing..
3. Is historical timekeeping and scheduling data migration required? If so, how much historical
information should be included?
* If Munis cannot be the system of record, we would expect the new system to migrate over
at least 10 years. If Munis remains the system of record ideally a back to January 1 of the
implementation year
4. Has the City established a project budget or anticipated investment range for software, hardware,
implementation, and ongoing support?
* The City does not have a formal implementation budget necessarily as it is variable depending
on the solution/proposal offered. For ongoing costs the City expects to remain at or below the
current ongoing support costs of approximately 44,000.

With GovernmentContracts, you can:
...Solicitation ID: SRC0000042792 Solicitation Name: Brittco Software Original Begin Date: 10/30/2026.../13/2026 4:00:00 PM ...
State Government of Ohio
Bid Due: 11/17/2026
...Solicitation ID: SRC0000042670 Solicitation Name: Kiteworks Software Platform Renewal Original... submit a response ...
State Government of Ohio
Bid Due: 11/20/2026
...Solicitation ID: SRC0000042986 Solicitation Name: Vocera - Software Renewal Original Begin Date... ID ...
State Government of Ohio
Bid Due: 11/25/2026
...Solicitation ID: SRC0000042683 Solicitation Name: LexisNexis AVCC Software Original Begin Date: 10... Date: ...
State Government of Ohio
Bid Due: 11/16/2026