เล่นคาสิโนปอยเปต_เล่น เกมส์ ได้ เงิน จริง ฟรี_sbo356 https://www.google.com//352/phoenix en Système Phénix : l’hypocrisie des libéraux révélée avec le budget 2017 https://www.google.com//352/node/5730 <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p>Dans son budget du 22 mars, le gouvernement fédéral ignore le plus important problème que vit actuellement la fonction publique. Les ratés du <strong><a href="https://syndicatafpc.ca/temporary-page-phenix">système de paye Phénix</a></strong> ont eu des conséquences sur des milliers de fonctionnaires au cours de la dernière année. Certains d’entre eux n’ont pas re?u de paye depuis des mois.</p> <p>??Je ne trouve pas les mots pour exprimer à quel point je suis dé?ue qu’il n’y ait rien pour arranger Phénix, déplore Robyn Benson, présidente de l’Alliance de la Fonction publique du Canada. ?a envoie le message aux fonctionnaires qu’ils ne sont pas importants, que ce n’est pas grave s’ils ne sont pas payés.??</p> <h3><strong>Le gouvernement s’attaque aux autres employeurs </strong><strong>qui ne payent pas leurs employés</strong></h3> <p>Par contre, lorsqu’il est question d’autres employeurs du secteur fédéral, le gouvernement n’hésite pas à souligner l’importance de payer aux employés ce qui leur est d?.</p> <p>Dans son<strong><a href="http://www.budget.gc.ca/2017/docs/plan/toc-tdm-fr.html"> budget</a></strong>, il prévoit même modifier le <em>Code canadien du travail</em> afin de ??<strong>renforcer et moderniser les dispositions relatives à la conformité et à l'application de la loi?? et, plus précisément, ??</strong>pour faire en sorte que les Canadiens qui travaillent fort puissent récupérer plus facilement les salaires qui leur sont dus par leur employeur, et pour veiller à ce que les employeurs récidivistes soient sanctionnés??.</p> <p>??C’est ironique. Le gouvernement s’en prend aux employeurs qui ne payent pas correctement leurs employés, alors qu’il n’assume pas ses propres responsabilités pour le gachis causé par Phénix, soutient la présidente Benson. Pourquoi ne traite-t-il pas ses employés comme il demande aux autres de le faire???</p> <h3><strong>Rien dans le budget pour payer ses propres employés correctement</strong></h3> <p>En prévision du dép?t du budget, l’AFPC et d’autres syndicats de la fonction publique fédérale avaient demandé au gouvernement de prévoir <strong><a href="https://syndicatafpc.ca/1er-anniversaire-phenix-lafpc-reclame-fonds">un fonds de réserve de 75?millions</a></strong> de dollars pour permettre aux ministères et aux agences de régler les problèmes de paye causés par le système Phénix.</p> <p>Sans ce fonds de réserve, les problèmes risquent de se prolonger et d’empirer. Le message est clair : arranger Phénix n’est pas une priorité du gouvernement.</p> <p>??C’est une occasion manquée pour les libéraux. Ils auraient pu régler les problèmes de Phénix et s’assurer que les fonctionnaires sont payés à temps et correctement, affirme Chris Aylward, vice-président exécutif national de l’AFPC. ?a n’envoie certainement pas le bon message aux fonctionnaires dévoués qui se rendent au travail chaque jour pour offrir à la population canadienne les services qu’elle mérite.??</p> <p>?</p> <p>?</p> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/federal-budget">Federal Budget</a></li><li class="field-item odd"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-publisher field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Publisher:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/publisher/communications-and-political-action">Communications and Political Action</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/fixphoenix-facebook-fr_2.png" width="680" height="357" alt="Arrangez le systeme de paye Phénix" title="Arrangez Phénix" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Right Half</div> </div> </div> Mon, 27 Mar 2017 18:19:14 +0000 pilona 5730 at/352 Liberals’ hypocrisy on Phoenix shows in Budget 2017 https://www.google.com//352/liberals-hypocrisy-phoenix-shows-budget-2017 <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p>The federal government’s budget, delivered on March 22, failed to address the biggest problem currently facing the public service. The disastrous <strong><a href="/352/temporary-page-phoenix">Phoenix pay system</a></strong> has affected thousands of public service workers over the past year, leaving some workers with no pay for months.</p> <p>“Words don’t even describe how disappointed I am that they did nothing to address Phoenix,” said Robyn Benson, president of the Public Service Alliance of Canada. “This says to public service employees they are not important. It says to them it doesn’t matter if you get paid.”</p> <h3><strong>Government wants to go after other employers for failure to pay wages</strong></h3> <p>On the other hand, the government chose to highlight the importance of this issue when it comes to other employers in the federal sector.</p> <p>The <strong><a href="http://www.budget.gc.ca/2017/docs/plan/toc-tdm-en.html">Budget 2017 document</a></strong> states that the Canada Labour Code will be amended to “strengthen and modernize compliance and enforcement provisions.” Specifically, it states there will be amendments “to ensure that hard-working Canadians can more easily recover wages owed to them by their employer, and to ensure that employers who repeatedly offend will be punished.”</p> <p>“It seems a bit ironic that they will go after other employers for failing to pay wages owed, yet they will not hold themselves accountable for the Phoenix mess,” said Benson. “Why don’t they treat their employees the way they expect other employers to treat workers?”</p> <h3><strong>Budget fails to ensure their own employees are paid properly</strong></h3> <p>Leading up to the budget, PSAC and other federal public service unions had asked the government to include a <strong><a href="/352/psac-calls-phoenix-contingency-fund-first">$75 million contingency fund </a></strong>to assist departments and agencies in dealing with the Phoenix pay system.</p> <p>By not including the contingency fund, the government is going to prolong and worsen the problems with the pay system. It also sends the message that fixing Phoenix is not a priority for this government.</p> <p>“The Liberals missed a chance with this budget to help ensure that Phoenix gets fixed public service employees get paid on time and correctly,” said Chris Aylward, PSAC National Executive Vice President. “It sure sends the wrong message to the hard working public service workers who come to work every day to deliver the services Canadians rely on.”</p> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/federal-budget">Federal Budget</a></li><li class="field-item odd"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-publisher field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Publisher:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/publisher/communications-and-political-action">Communications and Political Action</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/fixphoenix-facebook-en_2_0.png" width="680" height="357" alt="Fix Phoenix pay system" title="Fix Phoenix" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Right Half</div> </div> </div> Mon, 27 Mar 2017 18:08:43 +0000 pilona 5729 at/352 à l’action! https://www.google.com//352/node/7356 <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p>Les fonctionnaires fédéraux et leurs alliés se rassembleront pour faire davantage pression sur le gouvernement afin qu’il prenne urgemment des mesures pour mettre fin au cauchemar Phénix.?</p> <p>De futurs événements Phoenix auront lieu dans diverses régions du pays. Inscrivez-vous pour recevoir un avis si un événement est organisé dans votre région ou si vous souhaitez participer à son organisation.</p> </div> </div> </div> <form class="webform-client-form webform-client-form-7356" enctype="multipart/form-data" action="/taxonomy/term/663/feed" method="post" id="webform-client-form-7356" accept-charset="UTF-8"><div><div class="form-item webform-component webform-component-textfield webform-component--prenom"> <label for="edit-submitted-prenom">Prénom </label> <input type="text" id="edit-submitted-prenom" name="submitted[prenom]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--nom-de-famille"> <label for="edit-submitted-nom-de-famille">Nom de famille </label> <input type="text" id="edit-submitted-nom-de-famille" name="submitted[nom_de_famille]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--code-postal"> <label for="edit-submitted-code-postal">Code postal <span class="form-required" title="This field is required.">*</span></label> <input required="required" type="text" id="edit-submitted-code-postal" name="submitted[code_postal]" value="" size="60" maxlength="128" class="form-text required" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--ville"> <label for="edit-submitted-ville">Ville </label> <input type="text" id="edit-submitted-ville" name="submitted[ville]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--province"> <label for="edit-submitted-province">Province </label> <input type="text" id="edit-submitted-province" name="submitted[province]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-email webform-component--courriel"> <label for="edit-submitted-courriel">Courriel <span class="form-required" title="This field is required.">*</span></label> <input required="required" class="email form-text form-email required" type="email" id="edit-submitted-courriel" name="submitted[courriel]" size="60" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--telephone-cellulaire"> <label for="edit-submitted-telephone-cellulaire">Téléphone cellulaire </label> <input type="text" id="edit-submitted-telephone-cellulaire" name="submitted[telephone_cellulaire]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-radios webform-component--organiser"> <label for="edit-submitted-organiser">Voulez-vous aider à organiser un événement? </label> <div id="edit-submitted-organiser" class="form-radios"><div class="form-item form-type-radio form-item-submitted-organiser"> <input type="radio" id="edit-submitted-organiser-1" name="submitted[organiser]" value="safe_key " class="form-radio" /> <label class="option" for="edit-submitted-organiser-1"> Oui, j'aimerais organiser un événement dans mon lieu de travail </label> </div> <div class="form-item form-type-radio form-item-submitted-organiser"> <input type="radio" id="edit-submitted-organiser-2" name="submitted[organiser]" value="safe_key2 " class="form-radio" /> <label class="option" for="edit-submitted-organiser-2"> No, merci </label> </div> </div> </div> <input type="hidden" name="details[sid]" /> <input type="hidden" name="details[page_num]" value="1" /> <input type="hidden" name="details[page_count]" value="1" /> <input type="hidden" name="details[finished]" value="0" /> <input type="hidden" name="form_build_id" value="form-_BeCW-UPyVHkiz4F3LNy9c7xusd6YJuYEWrqG9CJHqA" /> <input type="hidden" name="form_id" value="webform_client_form_7356" /> <input type="hidden" name="honeypot_time" value="1549670470|uc5WKWirt1ZxaEGvb4mZuL9lmGe8IiJPccCKD6SpHUw" /> <div class="url-textfield"><div class="form-item form-type-textfield form-item-url"> <label for="edit-url">Leave this field blank </label> <input autocomplete="off" type="text" id="edit-url" name="url" value="" size="20" maxlength="128" class="form-text" /> </div> </div><div class="form-actions"><input class="webform-submit button-primary form-submit" type="submit" name="op" value="Submit" /></div></div></form><section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section> Wed, 06 Feb 2019 16:45:39 +0000 ScriveD 7356 at/352 Take action! https://www.google.com//352/take-action <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p>Federal public workers and their allies will come together to further increase pressure on the government for urgent action to end the Phoenix pay system nightmare.?</p> <p>Future Phoenix?events will be held in various regions across the country. Sign up to get a notification if one is organized in your region or if you would like to take part in organizing one.</p> </div> </div> </div> <form class="webform-client-form webform-client-form-7353" enctype="multipart/form-data" action="/taxonomy/term/663/feed" method="post" id="webform-client-form-7353" accept-charset="UTF-8"><div><div class="form-item webform-component webform-component-textfield webform-component--last-name"> <label for="edit-submitted-last-name">Last name </label> <input type="text" id="edit-submitted-last-name" name="submitted[last_name]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--first-name"> <label for="edit-submitted-first-name">First name </label> <input type="text" id="edit-submitted-first-name" name="submitted[first_name]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--postal-code"> <label for="edit-submitted-postal-code">Postal code <span class="form-required" title="This field is required.">*</span></label> <input required="required" type="text" id="edit-submitted-postal-code" name="submitted[postal_code]" value="" size="60" maxlength="128" class="form-text required" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--city"> <label for="edit-submitted-city">City </label> <input type="text" id="edit-submitted-city" name="submitted[city]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--province"> <label for="edit-submitted-province--2">Province </label> <input type="text" id="edit-submitted-province--2" name="submitted[province]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-email webform-component--e-mail"> <label for="edit-submitted-e-mail">E-mail <span class="form-required" title="This field is required.">*</span></label> <input required="required" class="email form-text form-email required" type="email" id="edit-submitted-e-mail" name="submitted[e_mail]" size="60" /> </div> <div class="form-item webform-component webform-component-textfield webform-component--cell-phone"> <label for="edit-submitted-cell-phone">Cell phone </label> <input type="text" id="edit-submitted-cell-phone" name="submitted[cell_phone]" value="" size="60" maxlength="128" class="form-text" /> </div> <div class="form-item webform-component webform-component-radios webform-component--organise"> <label for="edit-submitted-organise">Do you want to help organize? </label> <div id="edit-submitted-organise" class="form-radios"><div class="form-item form-type-radio form-item-submitted-organise"> <input type="radio" id="edit-submitted-organise-1" name="submitted[organise]" value="safe_key" class="form-radio" /> <label class="option" for="edit-submitted-organise-1">Yes, I would like to organize an event in my workplace </label> </div> <div class="form-item form-type-radio form-item-submitted-organise"> <input type="radio" id="edit-submitted-organise-2" name="submitted[organise]" value="safe_key2" class="form-radio" /> <label class="option" for="edit-submitted-organise-2"> No, thanks </label> </div> </div> </div> <input type="hidden" name="details[sid]" /> <input type="hidden" name="details[page_num]" value="1" /> <input type="hidden" name="details[page_count]" value="1" /> <input type="hidden" name="details[finished]" value="0" /> <input type="hidden" name="form_build_id" value="form-xdAU3-gqBkZe0dvHEML9PZeCCvlu0HdqgZ34GaE74s8" /> <input type="hidden" name="form_id" value="webform_client_form_7353" /> <input type="hidden" name="honeypot_time" value="1549670470|uc5WKWirt1ZxaEGvb4mZuL9lmGe8IiJPccCKD6SpHUw" /> <div class="url-textfield"><div class="form-item form-type-textfield form-item-url"> <label for="edit-url--2">Leave this field blank </label> <input autocomplete="off" type="text" id="edit-url--2" name="url" value="" size="20" maxlength="128" class="form-text" /> </div> </div><div class="form-actions"><input class="webform-submit button-primary form-submit" type="submit" name="op" value="Submit" /></div></div></form><section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section> Tue, 05 Feb 2019 21:06:06 +0000 ScriveD 7353 at/352 Phoenix Day of Action: On 3rd anniversary, PSAC to mobilize for damages and more progress https://www.google.com//352/phoenix-day-action-anniversary-2019 <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p>Three years after the launch of the Phoenix Pay System, thousands of PSAC members continue to be plagued by pay problems: they are underpaid, overpaid or not paid at all.</p> <p>On this third anniversary of Phoenix, PSAC members will come together to further increase pressure on the government for urgent action. On <strong>February 28</strong>, <strong><a href="https://www.facebook.com/events/298352514157107/">PSAC will hold a rally in the National Capital Region?</a></strong>to kick off a series of escalated actions around the country in demand of: more concrete action to reduce Phoenix cases; a real timeline to end these pay nightmares; and damages to compensate the hundreds of thousands of public service workers who have been impacted.</p> <blockquote> <h2 class="rtecenter"><a href="https://www.facebook.com/events/298352514157107/"><strong>RSVP for the Day of Action?in the National Capital Region</strong></a></h2> </blockquote> <h2>Some progress, but not enough</h2> <p>The union’s mobilization since last year’s Day of Action has allowed us to win several Phoenix victories. Together, we forced the government to:</p> <ul><li><strong><u><a href="http://hereforcanada.ca/2018/03/12/phoenix-victory-government-delay-recovery-overpayments-emergency-pay/">halt the recovery of overpayments and emergency pay</a></u></strong> until employees’ pay files have been cleared of all outstanding transactions;</li> <li><u><strong><a href="http://hereforcanada.ca/2018/05/11/new-financial-losses-covered-claims-process-need-know/">expand the Treasury Board’s claims process</a></strong></u> for Phoenix related financial losses;</li> <li>and <strong><u><a href="/352/major-phoenix-victory-no-more-gross-payback">end gross payback for overpayments</a></u></strong>.</li> </ul><p>Despite these wins, at the start of 2019, the <strong><u><a href="https://www.tpsgc-pwgsc.gc.ca/remuneration-compensation/services-paye-pay-services/centre-presse-media-centre/tableau-dashboard/tableau-12-2018-dashboard-eng.html">Public Service Pay Centre</a></u></strong> was still facing a backlog of over 280,000 cases. And after three years of Phoenix, about two-thirds of HR data is still being inputted late, causing pay problems across the board. Phoenix continues to also delay the implementation of our collective agreements and the retroactive pay our members are owed.</p> <h3><strong>In the face of so many Phoenix problems that remain, we demand the government:</strong></h3> <ul><li>Provide damages to all public service workers for the great financial and emotional hardship they have endured because of Phoenix.</li> <li>Provide the additional staffing and training needed to: <ul style="list-style-type:circle;"><li>assist members at the Client Contact Centre and the Public Service Pay Centre;</li> <li>reduce Phoenix cases by ensuring HR data is entered on time;</li> <li>and eliminate the backlog of Phoenix cases, including implementing collective agreements and delivering retroactive pay.</li> </ul></li> <li>Provide a clear and accountable timeline to stabilize Phoenix, eliminate the backlog, and transition to a new pay system.</li> </ul><h2>Bargaining offer adds insult to injury</h2> <p>To add insult to injury, in recent bargaining the government <a href="/352/bargaining-impasse-liberals-wage-freeze"><strong>proposed a two-year wage freeze followed by a meagre 0.75% per year increase</strong></a> for over 90,000 members covered by Treasury Board negotiations.</p> <p>After coming to work day after day – delivering the critical services Canadians rely on - without being paid properly, our members deserve so much more than this continued disrespect.</p> <p>Join us on <strong>February 28</strong> to build on recent Phoenix victories and ensure that the Government comes to the bargaining table with a fair offer.??</p> <h2><strong>Future Phoenix?events will be held in various regions across the country. <a href="/352/take-action">Sign up</a> to get a notification if one is organized in your region or if you would like to take part in organizing one.</strong></h2> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/psac-afpc-ottawa-manif.png" width="960" height="483" alt="" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Banner</div> </div> </div> Tue, 05 Feb 2019 20:39:03 +0000 ScriveD 7351 at/352 Les membres de l’AFPC invités à tester des logiciels qui remplaceraient Phénix https://www.google.com//352/node/7312 <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p><a href="http://www.tbs-sct.gc.ca/next-gen-prochaine/systeme-ressources-humaines-paye-prochaine-generation-pour-fonction-publique.html"><strong>L’équipe des ressources humaines et de paye de la prochaine génération</strong></a> (l’équipe ProGen RH et paye) du gouvernement organise dans tout le pays une série <a href="https://ouvert.canada.ca/fr/blog/mobilisation-et-expo-utilisateurs-dans-le-cadre-de-linitiative-progen"><strong>d’expos pour les utilisateurs</strong></a> qui permettra aux membres de tester des logiciels de paye qui pourraient remplacer Phénix. Les tests auront lieu de <strong>9?h à 16?h</strong> dans les halls des immeubles dont vous trouverez la liste plus bas.</p> <p>Ces expos ont pour but de permettre aux fonctionnaires de participer au processus de sélection du futur logiciel de paye du gouvernement.</p> <p>L’AFPC encourage ses membres à faire ces tests et à formuler au gouvernement les précieux commentaires dont il a besoin pour assurer l’efficacité du futur système de paye.</p> <p>Des représentants de l’AFPC assisteront également aux expos afin d’aider à évaluer et à déterminer la solution qui répond le mieux aux besoins de nos membres, notamment ceux du Centre de paye et les autres fonctionnaires. L’AFPC a insisté auprès du gouvernement pour pouvoir participer au processus de sélection du système de paye, car elle veut s’assurer que ses membres n’auront plus jamais à faire les frais d’un fiasco comme Phénix.</p> <p>L’une des <strong><a href="http://syndicatafpc.ca/negociations-avec-conseil-du-tresor-lafpc-vise?_ga=2.101442886.670349503.1547656217-63261665.1491839781">principales revendications de l’AFPC au Conseil du Trésor</a></strong> est que le gouvernement consulte le syndicat avant d’effectuer des changements technologiques qui auront des répercussions sur nos membres.</p> <h2><a href="https://ouvert.canada.ca/fr/blog/mobilisation-et-expo-utilisateurs-dans-le-cadre-de-linitiative-progen">#ProGenRHPaye Expos utilisateurs</a></h2> <table align="left" border="1" cellpadding="0" cellspacing="0"><tbody><tr><td style="width:208px;"> <h2><strong>VILLE</strong></h2> </td> <td style="width:142px;"> <h2><strong>DATE</strong></h2> </td> <td style="width:274px;"> <h2><strong>LIEU</strong></h2> </td> </tr><tr><td style="width:208px;"> <h2>Gatineau</h2> </td> <td style="width:142px;"> <h2><strong>16?janvier</strong></h2> </td> <td style="width:274px;"> <h2>Place du Portage</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>17?janvier</strong></h2> </td> <td style="width:274px;"> <h2>101, promenade Colonel By</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>18?janvier</strong></h2> </td> <td style="width:274px;"> <h2>875, chemin Heron</h2> </td> </tr><tr><td style="width:208px;"> <h2>Montréal</h2> </td> <td style="width:142px;"> <h2><strong>23?janvier</strong></h2> </td> <td style="width:274px;"> <h2>200, boulevard René-Lévesque</h2> </td> </tr><tr><td style="width:208px;"> <h2>Dartmouth</h2> </td> <td style="width:142px;"> <h2><strong>24?janvier</strong></h2> </td> <td style="width:274px;"> <h2>40-45, promenade Alderney</h2> </td> </tr><tr><td style="width:208px;"> <h2>Victoria</h2> </td> <td style="width:142px;"> <h2><strong>28?janvier</strong></h2> </td> <td style="width:274px;"> <h2>25, chemin Huron?(Ouvert aux employés de MPO seulement)</h2> </td> </tr><tr><td style="width:208px;"> <h2>Edmonton</h2> </td> <td style="width:142px;"> <h2><strong>30?janvier</strong></h2> </td> <td style="width:274px;"> <h2>9700, avenue Jasper</h2> </td> </tr><tr><td style="width:208px;"> <h2>Winnipeg</h2> </td> <td style="width:142px;"> <h2><strong>1<sup>er</sup>?février</strong></h2> </td> <td style="width:274px;"> <h2>269, rue Main</h2> </td> </tr><tr><td style="width:208px;"> <h2>Gatineau</h2> </td> <td style="width:142px;"> <h2><strong>4?février </strong></h2> </td> <td style="width:274px;"> <h2>30, rue Victoria</h2> </td> </tr><tr><td style="width:208px;"> <h2>Gatineau</h2> </td> <td style="width:142px;"> <h2><strong>6?février </strong></h2> </td> <td style="width:274px;"> <h2>Terrasses de la Chaudière - 10 Rue Wellington, espace d'événement six (Gatineau, PQ)</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>8?février </strong></h2> </td> <td style="width:274px;"> <h2>1400, chemin Merivale -?Cafétéria (Ouvert aux employés de l’ACIA seulement)</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>11?février</strong></h2> </td> <td style="width:274px;"> <h2>101, promenade Tunney’s Pasture -??immeuble Jean Talon</h2> </td> </tr></tbody></table><p>?</p> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/afpc-web-fr_8.jpg" width="1920" height="1080" alt="" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Right Quarter</div> </div> </div> Wed, 16 Jan 2019 18:11:22 +0000 brownt 7312 at/352 PSAC members invited to test potential Phoenix replacements https://www.google.com//352/psac-members-invited-test-potential-phoenix <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p>The government’s <strong><a href="http://www.tbs-sct.gc.ca/next-gen-prochaine/next-generation-human-resources-pay-system-public-service.html">NextGen HR and Pay Team</a></strong> is hosting a series of <strong><a href="https://open.canada.ca/en/blog/next-gen-user-expo-and-engagement">User Expos</a></strong> across Canada which will allow members to try out potential payroll software that could replace Phoenix. The events will take place from <strong>9:00 am – 4:00 pm</strong> in the lobbies of the buildings listed below.</p> <p>These events will provide an opportunity for many public service workers to contribute to in the selection process for the next generation of government payroll software.</p> <p>PSAC is encouraging members to attend these events to test out the proposed solutions and give the valuable feedback the government needs to ensure the next payroll system is successful.?</p> <p>PSAC representatives will also be attending the expos to help evaluate which pay solution best meets our members’ needs – for both those who process the paycheques and those who receive them. PSAC has insisted that the government must include the union in the pay system selection process so that we can ensure our members never have to endure a Phoenix fiasco again. One of <strong><a href="/352/psac-proposes-important-gains-treasury-board">PSAC’s top Treasury Board bargaining demands</a></strong> is that the government consults the union before any technological changes are put in place affecting our members.</p> <h2><strong><a href="https://open.canada.ca/en/blog/next-gen-user-expo-and-engagement">#NextGenHRPay User Expos</a></strong></h2> <table align="left" border="1" cellpadding="0" cellspacing="0"><tbody><tr><td style="width:208px;"> <h2><strong>CITY</strong></h2> </td> <td style="width:142px;"> <h2><strong>DATE</strong></h2> </td> <td style="width:274px;"> <h2><strong>LOCATION</strong></h2> </td> </tr><tr><td style="width:208px;"> <h2>Gatineau</h2> </td> <td style="width:142px;"> <h2><strong>January 16</strong></h2> </td> <td style="width:274px;"> <h2>Place du Portage</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>January 17</strong></h2> </td> <td style="width:274px;"> <h2>101 Colonel By Drive</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>January 18</strong></h2> </td> <td style="width:274px;"> <h2>875 Heron Road</h2> </td> </tr><tr><td style="width:208px;"> <h2>Montreal</h2> </td> <td style="width:142px;"> <h2><strong>January 23</strong></h2> </td> <td style="width:274px;"> <h2>200 René-Lévesque Boulevard</h2> </td> </tr><tr><td style="width:208px;"> <h2>Dartmouth</h2> </td> <td style="width:142px;"> <h2><strong>January 24</strong></h2> </td> <td style="width:274px;"> <h2>40-45 Alderney Drive</h2> </td> </tr><tr><td style="width:208px;"> <h2>Victoria</h2> </td> <td style="width:142px;"> <h2><strong>January 28</strong></h2> </td> <td style="width:274px;"> <h2>25 Huron Street?(Open to DFO employees only)</h2> </td> </tr><tr><td style="width:208px;"> <h2>Edmonton</h2> </td> <td style="width:142px;"> <h2><strong>January 30</strong></h2> </td> <td style="width:274px;"> <h2>9700 Jasper Avenue</h2> </td> </tr><tr><td style="width:208px;"> <h2>Winnipeg</h2> </td> <td style="width:142px;"> <h2><strong>February 1</strong></h2> </td> <td style="width:274px;"> <h2>269 Main Street</h2> </td> </tr><tr><td style="width:208px;"> <h2>Gatineau</h2> </td> <td style="width:142px;"> <h2><strong>February 4</strong></h2> </td> <td style="width:274px;"> <h2>30 Rue Victoria</h2> </td> </tr><tr><td style="width:208px;"> <h2>Gatineau</h2> </td> <td style="width:142px;"> <h2><strong>February 6</strong></h2> </td> <td style="width:274px;"> <h2>Terrasses de la Chaudière -?10 Rue Wellington, Event Space Six</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>February 8</strong></h2> </td> <td style="width:274px;"> <h2>1400 Merivale Road - Cafeteria (Open to CFIA employees only)</h2> </td> </tr><tr><td style="width:208px;"> <h2>Ottawa</h2> </td> <td style="width:142px;"> <h2><strong>February 11</strong></h2> </td> <td style="width:274px;"> <h2>101 Tunney’s Pasture Driveway -?Jean Talon Building</h2> </td> </tr></tbody></table><p>?</p> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/psac-web-en_11.jpg" width="1920" height="1080" alt="" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Right Quarter</div> </div> </div> Wed, 16 Jan 2019 18:06:10 +0000 brownt 7311 at/352 Victoire dans le dossier Phénix : le recouvrement des montants bruts, c’est fini! https://www.google.com//352/node/7308 <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p><em>Déclaration de Chris Aylward, président de l’AFPC</em></p> <p>??C’est une grande victoire pour les fonctionnaires fédéraux. Après des années de pression exercée par l’AFPC et ses membres, le gouvernement a finalement proposé un <u><a href="https://www.fin.gc.ca/n19/19-004-fra.asp">projet de loi</a></u> qui règlera un des pires problèmes causés par Phénix.</p> <p>Depuis le début du fiasco Phénix, des milliers de fonctionnaires sont trop-payés. Mais au lieu de corriger ces erreurs de calcul et de verser le trop-payé à l’employeur, le gouvernement les a obligés à rembourser le montant brut, qui est plus élevé que ce qui leur a été versé.</p> <p>Le résultat?: des milliers de membres ont hérité d’un lourd fardeau financier et de problèmes fiscaux qui s’étaleront sur des années.</p> <p>Nous aurions préféré que cette loi soit déposée bien plus t?t, mais nous nous réjouissons qu’elle soit rétroactive à 2016, l’année où le cauchemar Phénix a commencé. Le gouvernement doit mettre en ?uvre cette loi le plus rapidement possible.</p> <p>La prochaine étape pour le gouvernement?: dédommager les fonctionnaires qui ont subi les ravages de Phénix. Une telle mesure allégerait le stress financier et personnel que vivent ces personnes depuis bient?t trois ans. ?</p> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-publisher field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Publisher:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/publisher/communications-and-political-action">Communications and Political Action</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/psac-afpc-flag_0.jpg" width="1920" height="1080" alt="Drapeau AFPC" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Right Half</div> </div> </div> Tue, 15 Jan 2019 18:41:51 +0000 calugaj 7308 at/352 Major Phoenix victory: no more gross payback for overpayments https://www.google.com//352/major-phoenix-victory-no-more-gross-payback <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p><em>PSAC President Chris Aylward made the following statement:</em></p> <p>“Public service workers scored a major victory today after years of pressure from PSAC and its membership. The government of Canada has finally proposed <strong><u><a href="https://www.fin.gc.ca/n19/19-004-eng.asp">tax legislation</a></u></strong> to fix a major part of the Phoenix pay system fallout.</p> <p>For 3 years and counting, thousands of workers across the country have received overpayments because of Phoenix. But rather than limiting the burden of these Phoenix errors to calculating the overpayment and repaying it to the employer, the government has forced these workers to reimburse the gross amount of the overpayment (cpp payments, income tax deductions, etc...) – significantly more than the amount they received.</p> <p>Not only has this been a financial burden, but it has resulted in years of tax return problems for thousands of workers.</p> <p>We would have preferred to have this legislation tabled years ago, but we’re pleased that it will be retroactive to 2016, the year the Phoenix crisis began. The government must now move as quickly as possible to implement the legislation.</p> <p>It’s for this kind of financial and personal stress caused by Phoenix – for three years now – that it’s also important that the government move to compensate public service workers with damages.”</p> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-publisher field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Publisher:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/publisher/communications-and-political-action">Communications and Political Action</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/psac-afpc-flag.jpg" width="1920" height="1080" alt="PSAC flag" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Right Half</div> </div> </div> Tue, 15 Jan 2019 18:39:59 +0000 calugaj 7307 at/352 Rajustements salariaux et salaires rétroactifs en retard : l’AFPC dépose une plainte contre le Conseil du Trésor/l'ASFC https://www.google.com//352/node/7295 <div class="field field-name-body field-type-text-with-summary field-label-hidden view-mode-rss"> <div class="field-items"> <div class="field-item even"><p paraeid="{47414ba8-ec40-4fe0-866e-57717a33f153}{21}" paraid="733416048">L'AFPC a décidé d'agir contre le Conseil du Trésor/l'Agence des services frontaliers du Canada (ASFC) pour le non-respect de la date limite pour appliquer la convention collective de ses quelque 8,300 membres qui travaillent pour l’ASFC un peu partout au pays.</p> <p paraeid="{47414ba8-ec40-4fe0-866e-57717a33f153}{21}" paraid="733416048">Le nouveau contrat de travail avec l'ASFC?a été signé en juillet et devait être mis en ?uvre au plus tard le 30?novembre. Aujourd'hui, l'AFPC a déposé une plainte en vertu de?la?<em>Loi sur les relations de travail dans le secteur public fédéral (LRTSPF)?</em>au nom de ses membres visés par ce contrat.</p> <p paraeid="{47414ba8-ec40-4fe0-866e-57717a33f153}{21}" paraid="733416048">Le syndicat est dé?u de l'incapacité du gouvernement de respecter l'échéance raisonnable pour appliquer la convention collective des travailleurs et travailleuses de l’ASFC. Sa frustration est d'autant plus grande qu'il avait généreusement accepté de doubler l'échéance en la faisant passer de 75 à 150 jours. Le problème n'est pas nouveau — le gouvernement a en effet eu de?la difficulté à respecter ses échéances?relatives à plusieurs autres conventions collectives, notamment celles <strong><a href="http://syndicatafpc.ca/date-limite-mise-en-oeuvre-conventions-collectives">des groupes PA, SV, TC et EB</a></strong>, ainsi que Parcs Canada et l'ACIA, en raison du dysfonctionnement de Phénix.</p> <p paraeid="{47414ba8-ec40-4fe0-866e-57717a33f153}{21}" paraid="733416048">Le syndicat demandera à la Commission des relations de travail d'ordonner à l'ASFC de payer des dommages-intérêts à ses membres et de prendre les mesures nécessaires pour se conformer immédiatement à la <em>LRTSPF</em> et mettre en ?uvre les dispositions des conventions collectives.</p> <p paraeid="{47414ba8-ec40-4fe0-866e-57717a33f153}{21}" paraid="733416048">Une date d’audience sera fixée une fois que l’employeur aura répondu à la plainte. L’AFPC continuera d’informer ses membres.</p> </div> </div> </div> <section class="field field-name-field-topics field-type-taxonomy-term-reference field-label-above view-mode-rss"><h2 class="field-label">Topics:&nbsp;</h2><ul class="field-items"><li class="field-item even"><a href="/352/phoenix">Phoenix</a></li></ul></section><section class="field field-name-field-embedded-image field-type-image field-label-above view-mode-rss"><h2 class="field-label">Embedded Image:&nbsp;</h2><div class="field-items"><figure class="clearfix field-item even"><img class="image-style-none" src="/352/sites/psac/files/gettyimages-586718274_0_3.jpg" width="480" height="319" alt="PSAC complaint against CBSA" title="PSAC complaint against CBSA" /></figure></div></section><div class="field field-name-field-image-placement field-type-list-text field-label-above view-mode-rss"> <div class="field-label">Image Placement:&nbsp;</div> <div class="field-items"> <div class="field-item even">Top Right Half</div> </div> </div> Fri, 21 Dec 2018 18:33:16 +0000 fonseca 7295 at/352