Latest Posts

Loading...

Monday, August 1, 2016

Com. B Samal, Divnl. Secy, AIPEU, Gr.-C, Bhubaneswar & Vice-President, Odisha Circle writes to NFPE / Confederation on difficulty in fixing the pay under CCS (Revised Pay) Rules, 2016 in case of bunching

To
1.     Com. M Krishnan
Secretary General
Confederation of Central Govt. Employees and Workers, CHQ
New Delhi

2.     Com. R N Parashar
Secretary General NFPE & General Secretary, AIPEU, Group-C, CHQ
Dada Ghosh Bhawan, New Delhi-110 008

Sub:   Difficulty in fixing the pay under CCS (Revised Pay) Rules, 2016 in case of bunching.  

Ref.-   1.       Para 5.1.36 & 5.1.37 of the Report of 7th CPC
          2.       Rule 7 of CCS (Revised Pay) Rules, 2016

This has a reference to the recommendations of 7th CPC under Para 5.1.36 and Para 5.1.37 which state as follows.

Para : 5.1.36 :  Although the rationalisation has been done with utmost care to ensure minimum bunching at most levels, however if situation does arise whenever more than two stages are bunched together, one additional increment equal to 3 percent may be given for every two stages bunched, and pay fixed in the subsequent cell in the pay matrix.

Para : 5.1.37 :  For instance, if two persons drawing pay of ₹53,000 and ₹54,590 in the GP 10000 are to be fitted in the new pay matrix, the person drawing pay of ₹53,000 on multiplication by a factor of 2.57 will expect a pay corresponding to ₹1,36,210 and the person drawing pay of ₹54,590 on multiplication by a factor of 2.57 will expect a pay corresponding to ₹1,40,296. Revised pay of both should ideally be fixed in the first cell of level 15 in the pay of ₹1,44,200 but to avoid bunching the person drawing pay of ₹54,590 will get fixed in second cell of level 15 in the pay of ₹1,48,500.

But while instructing fixation of pay in the revised pay structure under Rule 7 of CCS (Revised Pay) Rules, 2016, no guideline has been issued in this regard which may cause difficulty if situation does arise whenever more than two stages are bunched together.

Thus, in the absence of clear instructions, the process of  fixation of pay and calculation of arrears in the revised pay structure will be delayed.

Therefore, it is requested to bring this shortcoming in the CCS (Revised Pay) Rules, 2016 to the notice of the competent authority to issue suitable guidelines immediately on bunching so that revised pay can be fixed correctly and disbursed to the employees in time along with arrears.

        With greetings.
Comradely yours,

Bhubaneswar
The 30th  July, 2016
( B  SAMAL)
Vice-President
AIPEU, Group- C, Odisha Circle &
Divl. Secy. Bhubaneswar

Copy to all Circle Secretaries, AIPEU, Group-C

Reply Received

from:
Krishnan M <mkrishnan6854@gmail.com>
to:
"All India Postal Employess Union, Group-C Bhubaneswar Division" <aipeup3bbsr@gmail.com>

date:
Sat, Jul 30, 2016 at 10:36 PM
subject:
Re: Difficulty in fixing the pay under CCS (Revised Pay) Rules, 2016 in case of bunching.
This point is brought to our notice from Bangalore.  On this account fixation need not be delayed. Drawl of Bunching increment and fixation can be done later when Govt order comes. Now fixation should be done as per the present order. As I have already informed you this case also will be taken up for early orders.


 = M Krishnan =

1 comment:

  1. Union leader could have put pressure on the Govt for issue of notification regarding implementation of Pay commission report that ;- Revised Pay and allowances may be drawn as per recommendation of Justice Mathur committee (Pay and allowances ) . The committee established will examined further. But now the pay will be fixed less then Justice Mathur Committee i.e factor 2.57 ,2.62, 2.72 and 2.82 . also allowance like HRA ,Transporting allowance ,SDA and other will be drawn at old rate i.e as if pay has not been revised. This sentence will caused loss to each employee. For exampla . One who will draw 70000/- basic will draw HRA at old rate ( Old basic 25000/- @ 10% i.e Rs.2500/-) though he is entitled for HRA @ 8% in new scale Rs.5600/-- thus there is loss of Rs.3100/- .

    ReplyDelete