Chapter 11: Dataloggers And Predictive Maintenance Systems PDF

Chapter 11: Dataloggers and Predictive Maintenance Systems Section 1: Dataloggers 11.1.1 Purpose of Dataloggers (a) To monitor of signalling equipment and to provide real-time alerts/offline reports for taking necessary action by concerned staff....

Chapter 11: Dataloggers and Predictive Maintenance Systems Section 1: Dataloggers 11.1.1 Purpose of Dataloggers (a) To monitor of signalling equipment and to provide real-time alerts/offline reports for taking necessary action by concerned staff. (b) Assist in collaborative working of various agencies/persons responsible for upkeep of signalling system by sharing of data. (c) To provide Data evidence for investigation of unusual incidences. (d) To provide Data to Train operation Applications (as required). 11.1.2 Assets for Status Monitoring The following equipments shall be monitored (not limited to) (a) Relays – potential free contacts. (b) Power supplies – voltages, Currents. (c) Electronic Interlocking – Signalling elements data, Diagnostic data of EI. (d) Earth leakage detectors for Signal & Power Cables. (e) Wherever Potential free contacts are available for any signalling equipment like SPD, fire detection system, IPS etc, the same shall be monitored through Datalogger. (f) Diagnostic Data from MSDAC, IPS, Trackside ATP, Fire Alarm etc. (g) Door Opening/Closing of Relay Rooms. 11.1.3 General Requirements: The Datalogger system shall; (a) Perform the following functions; (i) Sensing the parameters of signalling equipments and acquiring diagnostic data from other processor based equipments. (ii) Communicating the data to a central location, analyzing the data and providing actionable decisions as alarm. (iii) Dissemination of alarms to the concerned staff for taking necessary action. (iv) To send short messages to concerned staff for taking appropriate actions. (b) Chronologically monitor and record the status of various field functions like track circuits, points & signals through their indoor repeater relays, operator’s push buttons/switches (digital Inputs) and level of various analog signals like DC and AC supply voltages. (c) Be capable of receiving both Digital Inputs & Analog Inputs at regular intervals by scanning them for change of state/Values. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 220 of 530  (d) Be suitable for working on non-electrified, AC electrified areas. (e) Be capable of working in any type of signalling installations on Indian Railways. (f) Dataloggers shall be suitable for deployment in the outdoor locations such as LC gates, goomties of Distributed Electronic interlocking, Automatic Block signalling goomties and IB Signal Huts using Remote Terminal Unit (RTU) which shall be connected to Datalogger system through suitable communication media. (g) Datalogger system shall provide data driven decisions to various agencies involved with asset management/usage. (h) Be re-configurable to any changes required by user, whenever modifications are carried out in the yard. (i) Validation of Datalogger for accurate correspondence of Inputs, Outputs, Alerts & yard layout display both at the time of Initial Installation & after every yard/signalling alterations shall be done. (j) The following outputs shall be available from Datalogger system at Test rooms and remote locations (i) Online alarms (ii) Online simulation (iii) Reports of alarms, events in textual and graphical form. (iv) Historic simulation display (k) Datalogger shall provide real time inputs (with appropriate interfaces) on train arrival/Departures for improving Train operations. 11.1.4 Technical Requirements (a) For monitoring digital inputs, potential free contacts shall be used. Analog signals shall be connected directly to Datalogger which in turn will convert to digital data for further processing. (b) The Datalogger shall have built in Real Time Clock for time stamping the receipt of particular information. (c) It shall be feasible to store the data in an external device. (d) Synchronisation with Indian Regional Navigational Satellite System (IRNSS) Clock or any Satellite Based approved clock is required for clock synchronisation with the network. (e) Existing telecom services shall be used to send alerts to required staff. (f) Interoperability among various makes shall be ensured. (g) RDSO’s Latest Specifications shall be followed. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 221 of 530 11.1.5 Network Requirements (a) Datalogger shall be capable of working with different transmission media like underground telecom cable, microwave (Digital or Analog) & OFC. The modem can be either in-built or external. The external modem will be housed within the Datalogger cabinet. (b) It shall be possible for networking and remote monitoring of several Dataloggers from the central location. All features like on-line Simulation, Off- line simulation, failure management, exception logics and Synchronization should be feasible from the central location. (c) It shall be feasible to provide IP based networking. (d) Data storage and management infrastructure: To support the requirements of local and remote access of online and offline data and alarms and reports – an approved robust IT infrastructure shall be provided. (e) Approved system of Data security and safety shall be provided to protect from viruses and unauthorised access. (f) Path Redundancy for the networks shall be provided. Section 2: Applications of Datalogger 11.2.1 Fault & Asset Management (a) Datalogger system provides data driven decisions to various agencies involved with asset management and usage. An approved process for using full potential of Datalogger system by integrating its results with the existing process shall be provided with appropriate software. (b) Generation of Exceptional Reports: These reports shall be generated by a computer connected to Datalogger at the station (and at a central location also in case of networked Dataloggers). Special software loaded in the computer, shall implement defined logics and generate exceptional reports as alarms. As per their category, they shall be sent as messages to required Officials for prompt action. Please see Annexure: 11-A1 for guidance. 11.2.2 The following users may be provided with exception Reports/Alarms (a) Maintenance staff of signalling equipments (b) Electrical maintenance Staff (c) P - way maintenance Staff (d) Traffic staff/controllers (e) Operating staff at station/cabins Section 3: Remote Diagnostic and Predictive Maintenance System (RDPMS) 11.3.1 The objective of providing Remote Diagnostic and Preventive Maintenance system is to assist maintenance team in taking appropriate maintenance action in advance to prevent the failure of signalling gears. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 222 of 530  At functional level the system is broadly divided into two categories: (a) Remote Diagnostic of Equipment: To reduce MTTR and providing aid to maintenance staff in rectifying the signal failures. This is achieved by automated analysis of parameters of Signal gears collected remotely using IoT (Internet of Things) devices. The system shall be able to give probable cause of failure to aid the maintenance staff for early restoration reducing MTTR. (b) Predictive Maintenance: To facilitate predictive maintenance by advance computing of Big data using Machine Learning and Artificial Intelligence. The data of all the stations shall be continuously analysed by system for developing the supervised and unsupervised machine learning. The system shall be able to send automatic alerts for Signalling gears which are likely to fail based on the system learning. This will assist the maintenance staff to take necessary action to eliminate failure before it occurs. (c) Data Acquisition from Field & Indoor Equipments: The data from each signalling gear at the station shall be collected on real time basis using the inbuilt diagnostic ports of the signalling gears and/or the external sensors. Sensors of proper rating to be used as per monitoring range of various parameters of signalling gears to be monitored. 11.3.2 IoT System The IoT device shall be software embedded system preferably COTS (commercially off the shelf) and will do the basic function of capturing the parameters from the signalling gears using the sensors and diagnostic ports and transmit the data to Local Server through Gateway at the station. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 223 of 530 11.3.3 Network Requirements Communication from IoT device (in station yard near point, signals and other equipments) to Gateway at station may be on Wireless/Optical fiber/Copper cable/Wi-Fi communication. Indoor signalling gears will also be suitably interfaced for monitoring. For communication from Station to Cloud, optical fibre network with redundancy may be used. 11.3.4 Cloud Based Predictive Maintenance Algorithms (a) The exchange of information from IoT device to Local server and to Centralized Cloud shall be on standard format for interoperability between different systems. (b) The time synchronization between various IoT devices is an important requirement for data interpretation in machine learning. For master clock, the IRNSS (Indian Regional Navigation Satellite System) clock may be taken for reference at each station. (c) Transfer of raw data from site using IoT devices to local server at station. The data from local servers at every station will be sent to centralized cloud. This data complemented by historical data and trends will be processed using advance computing through data analytics (Artificial Intelligence/Machine Learning) to anticipate any issues or failures before they occur. (d) It is proposed that there may be integrated single cloud for all stations of Indian Railways. However, if it is not feasible due to any reason, the cloud can be as per Zonal Railway or a group of Zonal Railways. A mirror cloud may also be setup for data backup. (e) An automated alert mechanism will send information to Signal Control of concerned Division and the concerned maintenance staff over SMS/mobile app. The monitoring terminals shall display real-time alerts on the screen. 11.3.5 Power Supply Requirement for RDPMS at Station (a) The power supply for IoT devices near the outdoor equipments shall be taken from signalling equipment supply with suitable rating fuse, wherever feasible. Where power is not existing, 24 V DC may be extended from nearby location. (b) The power supply for IoT devices in Indoor i.e. relay room shall be provided from 24 V DC of IPS (preferably dedicated module in N+1 configuration). (c) The power supply for all other equipments i.e. Gateway, Local server, etc. may be provided from 230 V UPS. The input to UPS shall be from same source of IPS i.e. selective AT after auto-changeover of IPS. The backup time of UPS to be decided based on the power-cut duration at particular station. Note: This Chapter has under mentioned Annexures S.No Annexure No Description 1 11-A1 Datalogger Fault Logics – An Example Note: This Chapter has under mentioned Maintenance schedule in Appendix-I S.No Annexure No Description 2 11-MS1 Maintenance Schedule of Datalogger Chapter 11: Dataloggers and Predictive Maintenance Systems Page 224 of 530 Para No. 11.2.1(b) Annexure: 11-A1 Datalogger Fault Logics – An Example Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message The time difference between ECR (UP to DN to UP) is S1 HECR Signal in between 500 msec. to 2 Sec which should be taken M 1 Signal Bobbing RDSO Bobbing as 1 count and for satisfying the fault logic 2 to 3 counts should happen within 10 Sec. The time difference between TPR (UP to DN to UP) is in between 50 msec to 1 Sec which should be taken as1 61 TPR Track 2 Track Bobbing RDSO M count and for satisfying the fault logic 2 to 3 counts Bobbing should happen within 10 seconds. The time difference of (NWKR/RWKR) (UP to DN to UP) is in between 500 msec. to 2 Sec which should be taken as 1 59 NWKR Point 3 Point Bobbing RDSO M count and for satisfying the fault logic 2 to 3 counts should Bobbing happen within 10 Sec. At that time TPR is UP. 1. If NWKR, RWKR both are down for more than time interval then it is point failure. 4 Point Failure RDSO M C (120 Sec) 59 Point Failure 2. In case of Siemens − WKR1 is Down for more than the given time interval. 1. In case of siemens − The time difference between WKR1 Down to Up is in between the set time interval. 51 NWKR Point 5 Sluggish Operation of Point RDSO 2. Other than siemens − time interval of NWKR down to M Sluggish Operation RWKR up OR RWKR down to NWKR up is more than set time. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 225 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message T1,T2,T3 are sequential tracks, a) When T2 is DN. b) T1 and T3 UP. 51 TPR Track 6 Track Circuit Failure RDSO c) The time difference between T1 UP and T2 DN is M C (120 Sec) more than 5 Sec. Circuit Failure d) The time difference between T3 UP and T2 DN is more than 5 Sec. e) T2 is not bobbing and is DN for more than 10 Sec. When 110 V supply to signals has not failed (i.e. analog voltage value is used in fault logic) a) Yellow (three aspect): After HR picks UP and DR is DOWN, if HECR is not picked UP within 10 seconds. HR is triggering signal b) Green (three aspect): After HR and DR pickup if DECR S1 HHG Fusing of 7 Fusing of Signal Lamp RDSO has not picked UP within 10 seconds. HR and DR is M C (120 Sec) Signal lamp triggering signal. c) Red: After HR/DR is DN, if RECR has not picked UP within 10 seconds. HR/DR is triggering signal. d) Yellow/green (two aspect): After HR/DR picks UP, if HECR/DECR has not picked UP within 10 seconds. HR/DR is triggering signal. When 110 V supply to signals has not failed and all ECRs 8 Signal Blanking RDSO M C (120 Sec) S1 Signal Blanking are down (i.e. analog voltage value is used in fault logic). Chapter 11: Dataloggers and Predictive Maintenance Systems Page 226 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message When RECR is up continuously for more than 2 seconds - in that condition if UCR/LR/U(R)S is up and HR/GR2 is S1 Signal Flying 9 Signal Flying Back to Danger RDSO M C (120 Sec) down and signal replacement track(TPR) is up and back to Danger EGGNR down, then it is Signal Flying back to danger. The TIME difference between JSLR UP and NJPR UP is S1 Timer setting 10 Timer Setting More RDSO greater by more than 10% (more than 132 seconds for M More 120 seconds timer) of the prescribed time. 101 WNR Button 11 Button Stuck Up Button relay is up for more than specified time 20 Sec C Relay Stuck Up In between two sequential TPRs Down to Up (To ensure it is train movement) if the status of NWKR or 59 Point Loose 12 Point Loose Packing RDSO RWKR Changes more than 2 times and status of EWNR C Packing not changed (Point emergency operation not done) then it is Loose Packing. 13 Signal Bobbing without If HR/DR is up and HECR/DECR changes its status from Design Problem (i.e Signal Up to Dn to Up is in between 500 msec to 2 Sec and S1 HECR Signal Control Relay not Dropped) HECR/DECR is not operated along with HR/DR then it is M Bobbing without Sig Not Applicable Bobbing without design problem. Design Problem ECR is triggering sig Not Applicable. 14 Signal Bobbing with Design If HR/DR is up, HECR/DECR changes its status from Up Problem (i.e Signal Control to Dn to Up is in between 500 msec to 2 Sec and S1 HECR Signal Relay Dropped) HECR/DECR is operated along with HR/DR then it is Sig M Bobbing with Not Applicable Bobbing with design problem.ECR is Design Problem triggering sig Not Applicable. 15 Signal not Lowered even Same as Logic no.19 C Operation is Valid Chapter 11: Dataloggers and Predictive Maintenance Systems Page 227 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message Power Supply Use analog voltage monitoring where LVR is not 16 Power Supply Failure Alarm RDSO M C (120 Sec) Failure & Power provided. Supply Restored 17 Fuse Blown Off (Additional Hardware to be used to RDSO Additional hardware to be used to detect Fuse Failure. C Detect Fuse Failure) 18 ELD Detected Low Earth Leakage Insulation of Supply appeared in 110V (Potential Free Contact of C AC Supply, Earth RDSO Potential free contact of ELD. ELD to be Wired as Input to Leakage Datalogger) disappeared in 110V AC Supply 19 Route not set when Operation is Valid giving the Sequence of Relay Operations. (1. Possible in case of panels where button/switch relays pick up with operation of button/switch even-though RDSO GNR, UNR are Up, EGGNR is Dn then after given time C Route Failure the operating conditions are interval if HR is in down then check the Route. not favourable 2. Sequence of relays shall be provided by railways 3. Not possible for switch type non route setting type panels) Chapter 11: Dataloggers and Predictive Maintenance Systems Page 228 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message If the train arrives on the track2 proving the sequence of track1 DN and ahead track to point zone track is M 20 Point Burst RDSO C (120 Sec) 101 Point Burst down, the point setting in the unfavourable position and then the NWKR/RWKR both are DN for 2min. At the time of HR/DR/ HECR/DECR up, signal lock relays S1 Signal Cleared 21 Clearing of Signal without RDSO i.e all G(R)LR's/G(R)R/ASR/ALSR in the possible Routes C without Route Route Locking from signal are in down state then it is Failure. Locking The TIME difference between JSLR UP and NJPR UP is S1 Timer setting 22 Timer setting Less RDSO less by more than 10% (less than 108 seconds for 120 C Less seconds timer) of the prescribed time. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 229 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message 23 Check for Passing of Danger a) When track 2 is DN after track 1 is DN and RECR is UP. Signal b) The time difference between T2 DN and T3 UP is more than 5 Sec. c) The time difference between T2 DN and RECR UP is more than 5 Sec. d) T2 is not bobbing and is DN for more than 1.2 Sec. SPAD CASES 1. Multiple signals (stop, shunt and calling on) on the same post (When RECR is Up, SH/HECR, COECR are Down, Corresponding Point indication and TPR1, TPR2 are Down, TPR3 is Up and time difference between TPR2 Down (triggering) and TPR3 Up is more than time T1,and the time difference between TPR2 Down and RECR Up is more than the given S1 Check for RDSO time interval T1, TPR2 is continuously Down for T2. C Passing of Danger T2 is triggering. Signal 2. Two signals on different lines ex. starters) with first controlling track common and point selection. Point selection to be used for each signal apart from the above logic. 3. Two signals on the same line reading to the same line on different posts (home and shunt) home signal ASR/ALSR/G(R)LR to be used in shunt signal SPAD logic. 4. Two opposite signals (ex. starter and opposite shunt from siding) with one track circuit in between and no approach track circuit for shunt signal -- in starter signal SPAD logic use shunt GNR/UNR not operated condition or Conflicting HR Down. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 230 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message 24 Route Released without a) ASR UP / G(N)LR Up and S1 Route released Sequential Route Relays in b) Concerned route TSSLR DN or TPZR DN or TLSR DN or without sequential Route Picking up RDSO C TRSR DN or UYRs Down or U(R)Ss Up. route relays in c) Emergency route cancellation, NJPR DN, AJTR3 /JR Dn. route picking up 25 Signal assuming Green with S1 Signal assuming At the time of DR/DECR is picked up, RWKR in the Points in the Route Reverse RDSO C Green with 31 corresponding Route are picked up then it is Fault. Point Reverse 26 Home/Main Line Starter S1 Home Signal Signal assuming Green with When DR/DECR Of Home/Main Line starter Signal is up assuming Green RDSO C Adv Starter Danger and if the Advance Starter RECR is up then it is Fault. with S2 Adv Starter Danger 27 Advance Starter Off without S2 Advance starter Line Clear HR/DR UP and concerned Line clear relay DN. C Off without Line Clear T1, T2 and T3 are track circuits in sequence. Length of T2 is fed in the logic option a) Counter starts when T2 goes DN with T1 already DN. Over Speeding at M 28 Over Speeding RDSO b) Counter stops when T3 goes DN with T2 already DN. 1TPR On Main c) Time interval between (a) and (b) is less than length line/Loop line of T2 divided by maximum permissible speed by more than 10%. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 231 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message 29 Failure to set Point Against After complete arrival of the train, if the point is not set Occupied Line against the line on which the train is received within a pre determined time. On Double line rear end points Rear end Point not and on single line both front and rear end points are to set against 01T RDSO be considered. C Occupied line Note: 1. Implementation of this logic on big yards is not from S1-S4 possible as the options are too many. 2. There can be a case where it is not possible to set the point as all lines are occupied. Relay Room Opening If Relay Room Door Relay is Down then it is Relay room Relay Room Door 30 RDSO C (75,76) opened. Opened, Closed 31 Emergency Route S1-S2 Emergency RDSO Operation of required buttons/switches. C Cancellation Route Cancellation 32 Point Emergency Operation 101 Emergency When Point Controlling RDSO Operation of required buttons/switches. C Point Operation Track(S) Fails Axle Counter 33 Axle Counter Resetting RDSO Operation of required buttons/switches. C Reset Approach track drop,1st controlling track drop,2nd Train Passed at S1 34 Train Passing Blank Signal RDSO controlling track pick up & RECR,HECR,DECR,CO ECR,SH C Blank Signal ECR drop for specific time. a) Berthing track DN and b) HECR/DECR UP and Late start of Train 35 Late Start of Train RDSO c) Signal replacement track DN and M at S1 Signal d) Time difference between time of occurrence of b and c is more than time defined by user. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 232 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message The time difference between signal approach track circuit Late Lowering of Home down and signal HECR/DECR/HHECR/COECR Up time is Late Operation of 36 RDSO M signal more than set time. Time difference to be displayed in case S1 Home Signal signal is cleared late compared to set time. Premature 37 Premature Operation of C RDSO If LCPR Dn before DR/DECR Dn and SR is Up. Operation of Block Double Line Block to TOL Instrument Possible in case the design of circuit is such that route Late Closing of LC- gets locked after operation of the signal before gate M 38 Late Closure of LC Gate RDSO 131 Gate in the closing and the signal clears as soon as the gate is Route S1-S3 closed. At the time of COECR (input1) (triggering) Up, if COJSLR S1A Calling on 39 Calling On Operation MM (input2) is in up state then it is Calling On Operation. operation In between ASR (input1) Down to Up if JSLR (input2) Operated then it is Emergency Route Release. ASR Up is triggering (or) GNR (input1) Up, UNR (input2) Up S1-S2 Emergency 40 Emergency Route Released OM EUUYNR (input3) Up after given time interval if ASR Route Released (input4) Up then it is Emergency Route Released.GNR, UNR, EUUYNR are triggerings. S1-S2 Emergency 41 Emergency Sub Route If EUYNR (input1) Up and WNR (input2) Up then it is OM Sub Route Released Emergency Sub Route Released. Both are triggering. Released If UNR (input1) is Up and if OVYNR (input2) Up then it is S1-S2 Emergency 42 Emergency Overlap Emergency overlap cancellation. Both are triggering OM Overlap Cancellation signals. Cancellation Chapter 11: Dataloggers and Predictive Maintenance Systems Page 233 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message 43 Emergency Signal If GNR (Input1) is Up & EGGNR (input2) is Up then it is S1 Emergency OM Cancellation Emergency Signal Cancellation. GNR, EGGNR are triggering. Signal Cancellation In Between WNR (input1) Up to Up, if NWKR (input2), RWKR (input3) are not Up then it is Point Repeated 13 NWKR Point 44 Point Repeated Operation Operation. WNR is triggering (or) In between NCR/RCR OM Repeated up to Down if Point (NWKR/RWKR) is not set then it is Operation Point repeated operation, NCR/RCR (Down) triggering. 45 Panel Failure due to AC Panel Failure Due All RECR's (Conflicting signals) are down then it is Panel MM to AC Power Power Failure failure due to AC Power Failure. All are triggering inputs. Failure 46 Panel Failure due to DC All ASR's (Conflicting signals) are down then it is Panel Panel Failure Due failure due to DC Power Failure. All are triggering MM to DC Power Power Failure inputs. Failure When RECR (input1) is Up and TPR1 (input2), TPR2 (input3) are Down, TPR3 (input4) is Up and time difference between TPR2 Down (triggering) and TPR3 S1 Shunting with 47 Shunting with Permission Up is more than time T1, and the time difference MM Permission between TPR2 Down and RECR Up is more than the given time interval T1, TPR2 is continuously Down for T2., SHKR Down status considered in extra variable. Chapter 11: Dataloggers and Predictive Maintenance Systems Page 234 of 530  Example of Fault Fault Name Ref: Fault Information Momentary Confirmed Message When RECR (input1) is Up and TPR1 (input2), TPR2 (input3) are Down, TPR3 (input4) is Up and time 48 SPAD at Adv Str without difference between TPR2 Down (triggering) and TPR3 S1 SPAD at adv str Up is more than time T1, and the time difference SC without shunt Shunt Permission between TPR2 Down and RECR Up is more than the permission given time interval T1, TPR2 is continuously Down for T2., SHKR Up status considered in extra variable. DC-DC Converter, Inverter-1,2,3...., SMPS, CALL S&T, 49 IPS Failure RDSO MC (120 sec) IPS Failure 50% DOD, MAINS FAIL, FRFC FAIL. DC-DC Converter, Inverter-1,2,3...., SMPS, CALL S&T, 50 IPS Restored RDSO MM (120 sec) IPS Restored 50% DOD, MAINS FAIL, FRFC FAIL. 51 TFR Relay Stuckup IF TFR IS PICKED UP THEN IT IS TFR RELAY STUCKUP. MM If Buttons (GNR, UNR) are pressed in wrong S1-S2 Wrong 52 Wrong Operation combination Then it is WRONG OPERATION. Both are MM Operation triggering signals. At the time of Point zone track (input1) Up, if Platform track (input2) Down, Before Point zone track (input3) Up and after time interval if G(R)LR (input4) is Up then S1-S2 Route not 53 Route not Released RDSO MM Check the following. Backlock tracks are in Up state and Released G(R)LR is Up. If any of above relays are not in required state then it is Fault. Point zone track is triggering. Note: (i) RDSO Latest guidelines to be followed (ii) User may define & configure some more Logics as per Specific need Chapter 11: Dataloggers and Predictive Maintenance Systems Page 235 of 530