Phoenix pay: The knock-on effects accumulate, this time with the RCMP

  • 主题发起人 主题发起人 guest
  • 开始时间 开始时间

guest

Moderator
管理成员
注册
2002-10-07
消息
402,610
荣誉分数
76
声望点数
228
There seems to be no end to the knock-on effects of the Phoenix pay debacle.

Acting RCMP commissioner Daniel Dubeau confirmed in an email to staff Monday that the RCMP would indefinitely delay a proposed shift of 4,000 plus civilian employees into the Phoenix pay system.

“We will not move forward … until we resolve ongoing challenges and make sure that the pay centre and pay system are ready,” Dubeau wrote.

The transfer to Phoenix had been scheduled for April 26, 2018, coinciding with the shift of the RCMP’s civilian employees into the core public service under the Public Service Employment Act.

Although the proposed move was initiated by the former Conservative government, the Liberals apparently still intend to follow through at some point. Meantime, RCMP civilians will continue to rely on their current antiquated system to process pay, transfers and other essentials related to conditions of work.

It’s just the latest in a series of delays and workarounds triggered by the botched rollout of the Phoenix pay system, which went live February 2016.

In late October, for instance, the Senate issued a request for bids on an “autonomous” system to do payroll processing and related pension benefits for some 940 current and retired senators and staff. As the Senate employs its own compensation advisors, it has been coping with the fallout from Phoenix adequately, but its desire to become more independent of Phoenix is revealing.

Earlier this year, the Department of National Defence put a stop to a key phase of a pay project dubbed Guardian, which has been under development for at least five years.

The idea was to replace outdated pay technology with systems that are flexible and automated. Parts of the pay systems at both Phoenix and Guardian are to standardize human resources software built by PeopleSoft.

In order to make this work, however, the two systems must be linked. The Phoenix project had planned to give DND access to its system last October, but that will now have to wait.

While 290,000 government employees outside of the military are now part of Phoenix in some form, the lion’s share of difficulties with pay transactions has been borne by the 200,000 or so workers at 46 departments that rely on compensation advisors based in Miramichi, N.B. The pay technology used by these departments has traditionally been based on PeopleSoft software.

The other group of government employees work for departments or agencies such as Canada Revenue Agency, Canada Border Services Agency and Statistics Canada. These rely on non-PeopleSoft software and consequently still employ internal compensation advisors. This is not expected to change until the technical issues associated with Phoenix are resolved.

The idea was that eventually all government departments would standardize on a future version of PeopleSoft (version 9.1) and reap substantial economies of scale and effort.

To judge just how far the Phoenix project has veered from its initial goals, consider Treasury Board president Scott Brison’s reply to a query at a House of Commons committee earlier this month about the soundness of delaying the RCMP move into the new pay system:

“We don’t want to add to the burden of Phoenix right now at a time when we’re still working through the problems,” he said.

Throughout government, bureaucrats no longer have to be convinced to lighten the weight on Phoenix.

b.gif


查看原文...
 
后退
顶部
首页 论坛
消息
我的