Block Efficiency

itachi

There is need to revise the MCDO Format for Engineering Blocks

The existing format in GM’s MCDO to CRB captures the position regarding Engineering blocks in the following format:

It is obvious in the above format is that an inflated demand of blocks (more than required) would have the effect of suppressing this ratio.

It has been seen that on Northern Railway despite heavy blocks and mega blocks granted in the last two months, the above percentage as obtained from TMS has hovered only around 60%.

It is therefore felt, that the above mode of analyzing blocks, tends to shift management focus from an efficient utilization of blocks granted towards a perpetual requirement for more and more blocks.

We may looks at this, through an example:-

A TRT machine is expected to deliver output measurable in terms of kilometers of tracks renewal done. 7 Km per month would be a decent output to expect from TRT.
Given the rated progress of TRT of 400 metres per effective hours of block, 7 km output implies a requirement of 7000m/400m = 17.5 hours effective blocks to be given.
We may remind ourselves that effective hours implies that 75 minute ineffective time would be deducted in each block (for setting up, winding down and travelling upto/back from worksite).
This means that given the target of 7 km TRT work- 17.5 hours of effective blocks is needed in a month.
Let’s say during the month in question the actual effective hours of block granted (in various spells) are 15 hours.
Then the efficacy of Blocks Granting (EBG) would be 15 Hours/ 17.5 Hours = 85.7%.
The efficiency of block granting in a given month could be less or more depending on the issues like urgency of freight and passenger flows, other failures affecting these flows like S&T failures, Loco failures and extra engineering restrictions as these would end up affecting total flow and the time taken by the flows in the sections. (For example, with high extra ER trains would require to take more time in clearing the section and reduce the available block margins.
Focus however, is also needed on how well the granted blocks one utilized (utilization of granted blocks or UGB).

In our example against a requirement of 17.5 Hours of effective blocks for doing 7 Km of track renewal by TRT, only 15 hours was actually granted in the month.
At the stipulated TRT progress of 400 meters per effective hours, the expected track renewal would be 400 m X 15 hours = 6 Kms.
However, various issues like labour availability/efficiency at site, sleeper availability, management of sleeper depot issues, quality of prior preparation works, machine working efficiency and breakdowns etc.will be determine the actual output obtained from the available 15 hours of block.
Suppose the actual output of track renewal is 3 km.
Then the Utilization of Granted Blocks for that month would be 3 km/6km = 50%. instead of 85.7% as shown earlier, which should have been the ideal case.
In the current system, if we look only at the demanded block hours, and do not place any emphasis upon the required block hours for the carrying out the same work, the picture that granted/demanded ratio gives, can be grossly misleading.
**- Let us say that for 7 km of TRT, the actual demanded block instead of 17.5 hrs required,is 35 hours and the block granted remains 15 hours- we would be reading a granted/demanded ratio of 15/35 = 42.8%.
This would make us conclude that more blocks are needed to undertake safety critical track renewal works whereas the real devil may lie in the detail of how the granted blocks are being utilized.**

The following format can help in getting the real picture:-

The above format with Nine columns is able to bring out the complete picture as well as the real issues needed to be tackled. Col 6 indicates how much block were granted against the requirement and col 9 brings out how well theyare utilized.
Only the principal track machines such as TRT, PQRS, BCM and unimat need be for monitored at Board’s level. The subsidiary machines like TTM/DGS etc can be monitored at Zonal/Divisional level.
It is also submitted that a mechanism for capturing the data at block granting level i.e. Section controller in division controller in division control through COA, also needs to be put in place.

Credits for above post: @vikaschaube95 Sir, CFTM NR

itachi

I would like to add few more points which I have discussed while in Solapur, and many times in Watsapp group and with seniors

Many Divisions have made Block Management System, eg. Jaipur(Abhay Sir), Kota(Param), Delhi(Rajneesh Sir) and Firozpur division, etc

I feel we are making a mistake by doing Decentralisation where Centralisation is needed and vice versa. In Blocks, Rest House and Loading/Unloading figures, Rail Fractures, etc a centralised system is needed.

I am explaining in words here (dummy app will show some other time):

An app/website/webapp, you open
Select the Zone say NR.
Select the Division say Delhi.
Now say you want to look at Blocks (different type, efficiency, hours, demanded etc)
say we take the above post as example:
Today a machine has worked for say 3 hours, now in the system already benchmark is feed, based on local constraints (standard benchmark for each machine in all divisions will not work, say the above mentioned TRT machine benchmark output is 400m/hr.
Now whenever we give block and output is less than 400m/hr, there will be RED FLAG and the row of that day will be shown in RED COLOR, there will be a remarks column to give explanation and if explanation is justified then the color will be changed to say MAGENTA (after both Sr. DOM and DRM accept in there login that explanation for less work is justified, then only the color will change to MAGENTA from RED, but NOT Green)
Whenever they exceed the benchmark it will be shown in GREEN color and in remarks staff including Sr. DOM and Sr. DEN name will be there including contractor who has done good work and their suggestions will be there. This will help us make a database of good staff.(will help in APAR too 😂 )
Now whenever we want to check the efficiency of any machine or any particular type of block then we can simply arrange in this app/website.
This will help us identify which blocks are most effective in which month which season which time of the day, which machine works best in which conditions etc.
As all this can be graphically plotted on Bubble chart as well as comparative Line chart.

Now these comparisons later can be made percentage-wise wrt to different divisions and zones, and those who “consistently” perform wrt to particular machines or in particular parameter, they can share best practices which can be adopted by other Zones/Divisions.

This will help immensely in making decisions and increasing the efficiency.

P.S. My experience is very limited in Railways, but based on my experience in other fields I believe this system will drastically improve our efficiency.

itachi

Another benefit (unintended) of the above app/website.

Currently, Engineering and operating separately feed data for machine output.

There are often mismatch in figures.

Also we don’t have password or access to their records.

So we are dependent on them and analysis is difficult and same work is repeated many times(biggest problem in railways) when someone ask report on say machine progress for say GM meeting.

If we implement above app/web system many things like login/access to engineering, and correct data etc can be solved. Offcourse it’s an unintended benefit.