• Thanks for stopping by. Logging in to a registered account will remove all generic ads. Please reach out with any questions or concerns.

Phoenix Pay System - Shit's Horrible

SupersonicMax said:
I hope those responsible (at all levels) are held accountable for the botched implementation and fired.  The incentive not to do sub-par should be that you get to keep your job.  Bonuses should be kept for the ourstanding and above/beyond kind of work.

I imagine their bonus' for getting the number of subordinates contributing to the Unite Way is greatly affected, as well.
 
In the reserve world, if someone didn't get paid because they didn't fill out a pay sheet, that's not the problem of the pay office, the pay mangers, or the pay system (RPSR); the problem is with the member not filling out their damn pay sheet!

In the Reserve world it was not unheard of to not be paid for six months when you first joined up. Lots of excuses but little action. It was also not un common to go on a Class B contract and be paid incorrectly or not for a few pay periods. The same for a Class C Reservist. The system always fell back on to the "it is up to the individual Soldier to ensure their pay s correct".  fair enough. I remember argueing with the Orderly room, I had a Soldier not paid for 2 months, they blamed him for the lack of pay. Turns out a Clerk messed up the paper work. Yet it was the Soldiers fault.

This is how they have always done things. If a Clerk messes up very little to nothing is done to discipline the person. Yet it is the individual who suffers the mess up.

To be honest if you have Soldiers not signing a pay sheet who are in attendance it tells me that your not doing doing Roll call at the start of training. I always made sure my Troops signed the pay sheet. I also made sure I dealt with pay issues quickly and always went to the IC and demanded immediate results.

I have to think the new pay system for the public service is having issues with more then the individual is not doing it correctly. The truth will be some where between blame the individual for the problem and blame the Supervisor. With little to no blame on the program itself.







 
"To do it over again, I would have made training absolutely mandatory," she said.

So they took surplus employees from another government software boondoggle, The Firearms Program, AND put them to work in the new pay system AND didn't think they needed mandatory training in one of the most illiterate areas of Atlantic Canada. 
 
Looks like government is winning the image game with this.

http://www.cbc.ca/news/politics/trudeau-meeting-constituency-office-1.3766790

At least, this time they did.
 
CTD said:
I have to think the new pay system for the public service is having issues with more then the individual is not doing it correctly. The truth will be some where between blame the individual for the problem and blame the Supervisor. With little to no blame on the program itself.

The website is not user-friendly. It is user-belligerent. It must have cost a lot more money to design something that hideous.
 
Good2Golf said:
I don't know who didn't get the training, but I can tell you that the training (PS' own online training) that I took as a military manager of server public servants and that the PS employees themselves undertook, appeared more than sufficient for them to be capable of keeping an eye on their pay...if they actually were payed.
CTD said:
I have to think the new pay system for the public service is having issues with more then the individual is not doing it correctly. The truth will be some where between blame the individual for the problem and blame the Supervisor. With little to no blame on the program itself.

Right so, as a military manager, and keep in mind I am accountable for over a hundred civilians, I was in NO way adequately trained.

If you had 9-5 Civilian employees with no special things on their file you might be lucky. I had people returning from sick leave who just never got added to phoenix, and so were never paid. I had people who were on variable shifts whose entire schedule kept getting reverted to 1 hour a week no matter how many times we changed it back. I had no ability to enter into Phoenix and had to do everything through pay compensation enquiry system whose online documented processes are far from complete which leads to multiple submissions for the same file. I, and my staff, spent literal days as in periods collected equalling greater then 48 hours on the phone with their people, the pay office, the enquiry people, phoenix and eventually the treasury board.

Please do not deflect this on management, or on the civilians. Yes, some people could probably have done better, but this was an extremely poorly executed move. When the pay centre begged the government to stop transferring files 4 months after launch, the department ignored it and transferred 80 000 more. My team has been furious because they have being told there is nothing they can do and its a waiting game as we have members who are simply not being paid. It also doesn't help that when we issue the Emergency pays, we are being told they will all be deducted off the first normal pay rather then being spread out. So if 3 months of emergency pay comes off your first pay all at once you get paid an amazing 0$ again as the back pay will apparently be coming separately.

Don't get me starting on leave with income averaging folks being screwed over with clawbacks...

Right...getting worked up /end rant
 
Not to mention the hash that Phoenix has done on MATA/PATA benefits. Not only is messing with new parents wholly loathsome, but screwing with people's pay and benefits based on their family status is probably in violation of the Canadian Human Rights Act.

 
NSDreamer said:
Right so, as a military manager, and keep in mind I am accountable for over a hundred civilians, I was in NO way adequately trained.

If you had 9-5 Civilian employees with no special things on their file you might be lucky. I had people returning from sick leave who just never got added to phoenix, and so were never paid. I had people who were on variable shifts whose entire schedule kept getting reverted to 1 hour a week no matter how many times we changed it back. I had no ability to enter into Phoenix and had to do everything through pay compensation enquiry system whose online documented processes are far from complete which leads to multiple submissions for the same file. I, and my staff, spent literal days as in periods collected equalling greater then 48 hours on the phone with their people, the pay office, the enquiry people, phoenix and eventually the treasury board.

Please do not deflect this on management, or on the civilians. Yes, some people could probably have done better, but this was an extremely poorly executed move. When the pay centre begged the government to stop transferring files 4 months after launch, the department ignored it and transferred 80 000 more. My team has been furious because they have being told there is nothing they can do and its a waiting game as we have members who are simply not being paid. It also doesn't help that when we issue the Emergency pays, we are being told they will all be deducted off the first normal pay rather then being spread out. So if 3 months of emergency pay comes off your first pay all at once you get paid an amazing 0$ again as the back pay will apparently be coming separately.

Don't get me starting on leave with income averaging folks being screwed over with clawbacks...

Right...getting worked up /end rant

NSDreamer, I had a small number of PS civilians with established career streams and no exceptional elements to their pay situation, so I think that my training (yes, it was not anywhere near the most comprehensive on-line training I've ever taken) was sufficient to understand the transition overall and more importantly to have a rapport with my civilian team members.  That said, the fact that I and every other military manager had no direct visibility to our civilian subordinates' specifics because we did not have a PRI, and thus not electronically 'engagable' in the case of any Phoenix system is but one of the overall issues with the roll-out.

I find it deplorable that executives are trying to portray mis-management on the part of users, managers and HR operators, while the executives, "upon reflection" might have considered (more involved) training as mandatory...  ::)  Jeez, ya think???  :not-again:

I also find it strange that the executives say it's only a training challenge, yet in the next breath, note how the Phoenix will need $50M at least, to fix the system.  Those two positions are pretty much diametrically opposed, IMO.

I hope that the Public Service Labour Relations Board tribunal was not as far as the senior PSPC leadership is going to be "held to account"...

:2c:

Regards,

G2G
 
NSDreamer said:
I wonder if anyone has said "Yes this was a good idea" ... ???

I worked on AITIS Project from 1995 to 2000, 1993 to 1999 was building a working prototype in stages adding the first users in 1997.  1999 to 2008 was building the system as a functional model that reflected the organization of army training and could be multi platform.  Even now it is not perfect BUT it just moved to ACIMS (SharePoint) from Documentum as I retired so it did fit as a multi function platform.  Talking with the AITIS folks, the move was very smooth and the Army National Calendar is finally part of AITIS (which was planned in 1994).  But that gives you an idea how long it should take to make a successful custom application on an enterprise scale integrate smoothly.  One thing we did do was reams of user training, much of it in user location and face to face for the initial training. Training should always be a lot of hand holding.  Now if they would only build the infrastructure to serve every training video from a central location, we could say mission accomplished. 
 
Lightguns said:
I worked on AITIS Project from 1995 to 2000, 1993 to 1999 was building a working prototype in stages adding the first users in 1997.  1999 to 2008 was building the system as a functional model that reflected the organization of army training and could be multi platform.  Even now it is not perfect BUT it just moved to ACIMS (SharePoint) from Documentum as I retired so it did fit as a multi function platform.  Talking with the AITIS folks, the move was very smooth and the Army National Calendar is finally part of AITIS (which was planned in 1994).  But that gives you an idea how long it should take to make a successful custom application on an enterprise scale integrate smoothly.  One thing we did do was reams of user training, much of it in user location and face to face for the initial training. Training should always be a lot of hand holding.  Now if they would only build the infrastructure to serve every training video from a central location, we could say mission accomplished.

ACIMS.... I shudder every time a link takes me to that..."thing". It's even less user friendly that the new standardized web pages for the rest of the military (such as the new Defence Team and RCN home pages).I could write a whole page of complaints about ACIMS, but I don't want to hijack this thread.
 
Uh-oh...  "Houston?  We have a problem!"

"Phoenix Down..."
Reproduced under the Fair Dealings Act

Phoenix pay system down across federal public service
Public Service and Procurement Canada investigating cause of outage, spokesperson says
CBC News Posted: Sep 20, 2016 9:36 AM ET Last Updated: Sep 20, 2016 10:00 AM ET

The troubled Phoenix pay system is down in all federal government departments, CBC News has learned.

Public Service and Procurement Canada spokesperson Nicolas Boucher said the department is investigating why the pay system is down. It's unclear if this was a planned outage or a technical problem.


In late July, the department said it had ended the practice of turning off the ability of employees to view their pay stubs in Phoenix a week before pay day.


The centralized payroll system was launched across the public service in April.

Public service unions warned the federal government not to go ahead with the full launch of the system and that it wouldn't be reliable.

In June, the government admitted 80,000 people had experienced some pay problems, including being underpaid, overpaid or not paid at all.

On Monday, Public Services and Procurement Minister Judy Foote was before a meeting of the government operations and estimates committee investigating problems with Phoenix.

She said the backlog had been reduced to 67,500 and it would be eliminated by Oct. 31.
 
Good2Golf said:
Public Service and Procurement Canada investigating cause of outage, spokesperson says
Perhaps someone brought in an outside contractor...... www.dyingwithdignity.ca  ;)
 
Loachman said:
The website is not user-friendly. It is user-belligerent. It must have cost a lot more money to design something that hideous.

If that holds true, then I'm sure I'd be gobsmacked at how much DRMIS must have cost us.
 
Occam said:
If that holds true, then I'm sure I'd be gobsmacked at how much DRMIS must have cost us.

Neither are websites, they are content management systems designed to serve documents not propaganda.  There is simple user paced training for both which should be mandatory but again isn't, so some folks have issues doing their jobs in ACIMS/DRMIS. 
 
Websites became a real pain to deal with. It’s almost impossible to change things in a timely manner and getting everything translated costs huge amounts of time and money. Funny yesterday, looking at a 125 page document with almost no maps, apparently all the title blocks need to be translated, even when the maps are submitted by an outside proponent, so it’s easier not to have maps to get the document posted, except that maps really help the end users who on this coast don’t give a crap about the French. I spend a great deal of time trying to help clients find stuff on our website. Many of our pages are just endless loops. The only good thing they did was to make them google friendly.
 
It is surprising that there has only been one lawsuit launched so far.

http://www.cbc.ca/news/canada/ottawa/phoenix-lawsuit-ottawa-darrel-delisle-1.3766028

 
CBC is reporting that, given two independent reviews of Phoenix prior to go-live, the staff at PSPC decided to give the minister the rosier one. http://www.cbc.ca/news/politics/minister-not-briefed-on-independent-phoenix-analysis-1.3773148

In reading the CBC story, it appears that at go live the system had never been tested end-to-end; there was no detailed test plan; and there was no fallback plan if rollout didn't work.

Anyone with project management experience feel free to chime in, but that does not sound like anything that respected PMBOK.
 
Back
Top