Committee members received an update on the city’s Workday implementation, the LAPD voluntary overtime bank (VOB) rollout, and broader time‑tracking integration work intended to reduce payroll errors.

Ed Magos of the Information Technology Agency (ITA) summarized the VOB status: "It officially launched on November 16," he said, and staff are testing an update to let the deployment accept dates retroactive to Aug. 24. The VOB work required changes to Workday, to an overtime‑tracking system used by LAPD (OLOTS), and vendor updates; ITA said validations to prevent calculation errors are being added and are expected to be completed by the end of the month.

Committee members asked whether the system now handles the 171‑hour/28‑day rule correctly. ITA said fixes to 171‑hour calculations were implemented and cleared the path for VOB. LAPD fiscal staff and the city’s chief executive office noted the VOB agreement runs through June 2035 but that the planned evaluation window is January 2026; city staff have offered to extend that evaluation to April to gather more deployment data.

The committee also discussed time‑tracking and scheduling for sworn departments. ITA described a strategy to replace legacy systems that previously sent pay amounts into Workday with systems that exchange raw time data and work tags so Workday’s pay engine can produce accurate calculations. Sam Ynajosa, CIO at LAFD, said Fire is evaluating a third‑party scheduling vendor and working with ITA, the controller, personnel, and CAO to define responsibilities between Workday and any third party.

Law‑enforcement and fire payroll teams reported a backlog of tickets related to legacy integrations. ITA said the backlog has declined incrementally (from over 100 toward the 70s) but will require continued post‑go‑live support; Ted Ross, General Manager at ITA, said ITA lost staff during the project and is requesting additional staffing and contractor support to reduce the backlog.

Sam Ynajosa said the city expects to decide in January whether to proceed with a recommended third‑party vendor for scheduling and integration; if integration tests fail, the city would need to run a full RFP, which could take several months.

The committee held the item for further work and requested follow‑up information on testing, evaluation timelines, and staffing needs.