Finalising FRS for ERP of S&T deptt in Indian Railways

Finalising FRS for MIS of S&T deptt.
– the SENTI-ZRP
By:-
Lokesh Vishnoi
DyCSTE/C-II/BSP
SEC Railways
LOKESH VISHNOI, DyCSTE/Con/SECR,
earlier SrEDPM and DyCM-IT/SECR
11/25/2014 1

FRS for – the SENTI-ZRP
For S&T., though the department’s
name is still SIGNAL & TELECOM, the work
sphere has changed wastly, to
SNT – SIGNAL, NETWORKs & TELECOM
and is slowly further changing to
SNTI – SIGNAL,NETWORKs,TELECOM & IT deptt.
11/25/2014 2

The present-days’ activities of an
S&T Engineer
00:00- 05:30 05:30 05:30-07:00
09:00- 19:00 19:30-2 2:00 23:00-23:30
11/25/2014 3

SAME USED TO BE SITUATION OF
ENGG OFFICERS
UNTILL……………..
THEIR MIS WAS STARTED
11/25/2014 4

Now they are like ……
11/25/2014 5

Thankfully now, for S&T also, development of
MIS has been sanctioned….
i.e., for us, time has come to be from
to
LETS JOIN HANDS TOGATHER TO DEVELOP THE BEST ERP FOR RAILWAYS,
our SNTI-ZRP, the SIGNAL, NETWORK, TELECOM & IT-ZONAL ERP
11/25/2014 6

Before finalising our objectives for SNTI-MIS,
lets remember this:-
“Small aim is crime , Big aim is divine
Never say I shall try, Just do or die”
-His Holiness Sri Sathya Sai Baba
11/25/2014 7

What is ERP, our SNTI-ZRP
An ERP system is a very useful tool for refining
working processes . Properly implemented
ERP system can help S&T improve efficiency &
effectiveness and modernise its working. We
will design various modules in our ERP system,
the SNTI-ZRP, all of which will be designed to
work together, and will have links to OEM
literature/their maintenance tools & practices
& info-exchange with them.
11/25/2014 8

Our objectives shall be
• Develop an ERP which will improve the working
of S&T and reduce tensions in its working by
using effectiveness of information systems
available with us
• Recognize the benefits of ERP systems for S&T’s
working pattern
• Design an ERP, its uses, data-feeding system &
data-uses to make us the BEST.
1-9
11/25/2014

Characteristics of an ERP System
• Shall includes a management SW that shall enable technical,
finance and Staff (HR) in a completely integrated fashion
• Enables high levels of integration across Supervisors’ Units or
Divisional functions and UNITES the whole Zones working
• Provide for widespread sharing of data from a single
person/place/ /equipment and make the working of whole zone
similar
• Drives extensive system transformation and change management
efforts by integrating with OEM/All units together
• Requires high levels of implementation effort and support, if real
benefits are to be earned
11/25/2014 10

Benefits of designing & deploying SNTI-MIS
• It will streamlines or eliminates inefficient
manual processes, which is time-taking, costly
& low-yielding
• Eliminates disparate stand-alone systems, on
which we are dependent presently
• It will provide integrated, enterprise-wide
common tools, processes and systems, hence
avoiding confusion among Zones or even
Divisions
11/25/2014 11

NOW, WE WILL DISCUSS ABOUT DESIGING
DEPARTMENTAL MIS FOR S&T
• THE PROPOSED SUB-MODULES ARE:-
..PTO..
11/25/2014 12

the SNTI-ZRP
S
N
T
I
SIGNALING
NETWORKS
TELECOM
INFOTECH
ZRP - ZONAL RESOURCE PLANNING
11/25/2014 13

SRS for S = SIGNALING
module
1.Shall have full details, including mfg. coy, year-of-mfg & year-of-installation
of every stations’ all Signalling gears, suggesting
upgrade/replacement based on usage/obsolence etc
2.Data-loggers shall be integrated up to Div & Zonal Test-rooms &
information shall be flashed as specified. It shall also have a De-bugging
SW based on Data-loggers information
3.Shall have system to send SMS to concerned staff, as specified by
1-14
Division time-to-time
4. Power-failure analysis & proposed backup/rectification tools.
4.Shall prepare Sig-failure analysis, comparing it with last month’s or
averaged DN time for station & suggest measures to improve reliability
5.Shall have staff Bio-data and previous records/history to propose by
itself the Staff deployment to minimise failures
6.Shall have specified KNOWLEDGE-OUTPUT for Zone, Division & Sub-
Division for everybody to take action, as per there level
11/25/2014

SRS for = module
S SIGNALING
7. Shall have links to OEM’s site for info-exchange on the
products’ working, efficiency & maintenance needs
8.Auto-Analysis & reporting by SW Application to be developed
for DLA-(DataLogger-Application)
THESE 2 POINTSWILL BE SAME FOR , &
MODULES ALSO
…continued…
N T I
11/25/2014 15

SRS for N = Networking
module
1. Shall have full details for all NWs, like CNL-NW, VOICE-NW, IT-NW, there
functions and inter-patching, interchangeability of Equpt etc. including
mfg. coy, year-of-mfg & year-of-installation of every stations’ all Signalling
gears, suggesting upgrade/replacement based on usage/obsolence etc.
2. Information on failures of concerned NW shall be stored & flashed after
Auto-Pinging or as specified. It shall also have a De-bugging SW,
prompting appropriate replacements.
3.Shall have system to send SMS to concerned staff, as specified by Division
1-16
time-to-time
4.Shall prepare Tele-failure analysis, comparing it with last month’s/averaged
DN time for NW & suggest measures to improve reliability
5.Shall have staff Bio-data and previous records/history to propose by itself
the Staff deployment to minimise failures
11/25/2014

SRS for T = T E L E C O M module
1.Shall have full details, including mfg. coy, year-of-mfg & year-of-installation
of every stations’ all Signalling gears, suggesting
upgrade/replacement based on usage/obsolence etc
2.Data-loggers shall be integrated upto Div & Zonal Test-rooms &
information shall be flashed as specified. It shall also have a De-bugging
SW based on Data-loggers information
3.Shall have system to send SMS to concerned staff, as specified by
1-17
Division time-to-time
4.Shall prepare Tele-failure analysis, comparing it with last
month’s/averaged DN time for station & suggest measures to
improve reliability
5.Shall have staff Bio-data and previous records/history to propose by
itself the Staff deployment to minimise failures
11/25/2014

SRS for I = I N F O - T E C H module
1.Shall have full details of Eqpt, including mfg. coy, year-of-mfg & year-of-installation
of gears over the Division, suggesting upgrade or replacement based on
usage/obsolence etc
2.Data-loggers shall be integrated upto Div & Zonal Test-rooms & information shall
be flashed as specified. It shall also have a De-bugging SW based on Data-loggers
information
3.Shall have system to send SMS to concerned staff, as specified by Division time-to-time
4.Shall prepare Eqpt/MIS/SW-failure analysis, comparing it with last
month’s/averaged DN time for station & suggest measures to improve reliability
5.Shall have staff Bio-data and previous records/history to propose by itself the Staff
1-18
deployment to minimise failures
6. Shall have links to OEM’s site for info-exchange on the products’ working,
efficiency & maintenance needs
7.Shall have specified KNOWLEDGE-OUTPUT for Zone, Division & Sub-Division for
everybody to take action, as per there level
11/25/2014

“The journey
of a thousand
miles begins
with one step”
- Lao-Tse
11/25/2014 19

SUB-HEADINGS OF EACH MAIN-TABs(S,N,T & I)
1.Assets D1.eAtaSiSlsE ToSf existing
Gears
Existing gears, their make & vintage, due-date
for replacement, Gears’/systems’
corresponding DESU/DETU/NWU
2.PLANNING for ADDITION or
REPLACEMENT of GEAR
Life-span vs. years lived of each gear &
system, Work-proposal status, AMC/RRC status
3.MANPOWER for
MAINTENANCE
Sanction vs. occupied posts, New-posts creation,
training, leave, Supervising
4.POWER EQPT MAINTENANCE Gear-wise capacity, maintenance/replacement
planning
5.INSPECTION/COMPLIANCE TAB Grade-wise inspections & compliance, with
needed reference tabs
7.Link to OEM websites Interact with OEM automatically for failure
info/Guidance/warranty/ repair status etc.
8. MPR/MCDO for the section Self-printing & sending of MPR to concerned
Officers
11/25/2014 20

Auto-Analysis & reporting by SW
Application to be developed for DLA-
(DataLogger-Application)
• Data-loggers are Networked already. The Data’s
Auto-Analysis & reporting by SW Application to
be developed will be deployed.
• The concerned JE/SM & Test-Room will get SMS
of analyzed failure and action to be taken
• Failure-detection and its logging into system for
future-corrective/replacement strategy shall be
designed
11/25/2014 21

CHOOSING A ZONE & AN AGENCY FOR
SNTI-MIS DEVELOPMENT & TESTING
ERP Solution Components
Implementation
60%
Infrastructure
20%
ERP Software
20%
11/25/2014 22

CHOOSING A ZONE & AN AGENCY FOR
SNTI-MIS DEVELOPMENT & TESTING
1. We need to choose a suitable zone for optimal cost-effective
and user-friendly Application Development
2. I propose SEC Railway, because SECR has Blade Servers
with spare capacity available. This will save 20% of cost.
We can have another Blade added at very less cost, if
needed
3. License-costs of OS & RDBMS, which is another 20% of
the project can be saved immediately
4. Further, SECR already has 08 MIS working in the Zone
(PRIME, AFRES, MMIS, PMIS, OSS, COMIS, HMIS & IPMS)
5. The IT-culture is already prevalent in SECR, with SECR-INET
& SECROADS functioning & employees trained in
multiple IT field at SECR-CT-IT, our in-house IT training
Center
11/25/2014 23

WHY CHOSE SECR FOR DEVELOPING SNTI-ZRP
5. Railway Network in SECR is very strong, having proper
back-up and is maintained properly.
6. Field testing & improvisation will be easier at SECR
because of their strong NW & IT-culture
7. SECR already has the posts of CM/IT and DyCM/IT
created and manned. We can create additional posts
here, if needed for developing SNTI-MIS
8. We have the Engineering MIS deployed here and the
Tabs/Data-cards with P-Way officials already can be
easily & effectively utilised for field-testing
11/25/2014 24

WHY WORK ON OPEN TENDER
• We can choose our terms, conditions,
specialists & references for the work
• SECR has the experience of successfully
floating & finalising Tenders and getting MIS
development & upgrade implemented twice
• Here, CRIS and a selected Central Body of S&T
Officers, can act as Advisors/Consultants to
Railway & the contractor chosen by SECR
11/25/2014 25

THANKS for your attention. I’m sure
we will be moving towards being - - - -
11/25/2014 26

11/25/2014 27

11/25/2014 28

11/25/2014 29

Finalising FRS for ERP of S&T deptt in Indian Railways

Recommended

Recommended

More Related Content

Similar to Finalising FRS for ERP of S&T deptt in Indian Railways

Similar to Finalising FRS for ERP of S&T deptt in Indian Railways (20)

Recently uploaded

Recently uploaded (20)

Finalising FRS for ERP of S&T deptt in Indian Railways