Freight Operations Information System (FOIS) PDF

FREIGHT OPERATIONS INFORMATION SYSTEM (FOIS) (Back to Index) I. INTRODUCTION In keeping with global trend, there has been a long outstanding demand of the industry & trade for transparency in sharing of information to give the customers an up-to date business like en...

FREIGHT OPERATIONS INFORMATION SYSTEM (FOIS) (Back to Index) I. INTRODUCTION In keeping with global trend, there has been a long outstanding demand of the industry & trade for transparency in sharing of information to give the customers an up-to date business like environment. Railways in this millennium have decided not only to perform the traditional tasks of carrying passengers and goods efficiently, but also to change the mindset of working as a closed system. The great concern to improve on its market share has prompted Railways to have a multi pronged approach to its freight policy. Continuous Cargo Visibility has always been a critical component of the Supply Chain Distribution Management System. To achieve this, out of the stated multi pronged new freight policy, a lot of emphasis has been laid on establishing a computerized FREIGHT OPERATIONS INFORMATIONS SYSTEMS (FOIS). The system indigenously developed is fully functional in the B.G. system of Indian Railways being the first of its kind in South East Asia. 1. Freight Operations Information Systems Mission – FOIS To give a total transparent system with continuous Cargo visibility and an up-to date business environment to the Customers with instant access to information regarding their consignments in transit for just in time inventory’. FOIS is an On-line Real-Time system based on absolute current State of Art Technology and efficient Communication system. A management tool to optimize utilization of costly assets and resources by improving the distribution of Rakes/Wagons & Locos, and also scheduling and Routing Traffic in an optimized cost effective manner. Provides Continuous Cargo Visibility and enables the Freight customers to have instant access to information regarding the current status of their consignments in transit for just in time inventory. 2. Strategic Advantages Derived From The FOIS System Extension of the current business practice from bulk movement of freight traffic in train load formations to piecemeal traffic by clubbing and moving together similar type of stock in ‘Hub & Spoke’ arrangement to increase its market share by re diverting high profit yielding piecemeal cargo from road to rail. Global tracking of consignments in real time Rakes or individual wagons. The insight and pipeline of consignments thus captured on the entire BG network is made available for timely planning and just in time inventory management on a time span cargo movement which may extend to 2 to 5 days from origin to destination... Facilitate acceptance (customer’s Orders), billing and cash accountal of freight traffic from identified nodal customer centers which may not necessarily be the handling terminals. Extension of such facilities to customer’s premises and introduction of e-commerce, benefitting both IR and the trade & industry, by eliminating manual transactions which necessarily add to the burden of logistics management. Providing requisite Foundation for a total logistics system furnishing real time information of the chain of physical distribution, an essential element in reducing inventory costs. 3. Scope Of FOIS Systems Presently two subsystems of FOIS are already in use after extensive field trials and validation. RMS TMS. a) Rake Management Systems –RMS - Rake based consignment tracking and pipeline  - Train/Rake operation - Stock Holding in terms of summary of wagon types - Train and stock Interchange - Terminal Handling performance - Loco holding, outage and power on-line - Reporting to take care of Train/Load on summary basis - Invoice based consignment tracking - Wagon wise Stock Holding - Reporting of consist Wagon wise - Invoice based loading originating tonnage and revenues. - Wagon wise Interchange - Statement of missing Wagons/wrongly delivered b) Terminal Management Systems –TMS - Computerized booking and delivery of consignment - Station Accounting - RR generation/Transmission - Improved Customer Interface 4. Crew Management has been developed & is under implementation. Control charting of trains currently being done manually will also be integrated with FOIS. The above two sub systems have been fully developed and tested and are ready for implementation. 5. FOIS Design Architecture FOIS is designed and developed in conformity with the state of art technology which is scaleable, maintainable, with open systems architecture and is based on the Indian Railways organizational hierarchy, its present and future requirements. Based on the business processes that are being adopted, the business model developed in the FOIS - IT architecture is based on the assumptions: - The current business practice of bulk movement in rake formation is the accepted norm for future also. Around 80 to 85% of traffic already moves in Rake, majority of which comprises similar type of rolling stock. Global perception is more important, with respect to tracking of consignment and Rakes rather than of individual wagon, locomotive and train. The insight and pipeline of consignment and rakes should be seamlessly available. Railways would like to share information on booking and movement of consignments with individual customers also. The operations and data capturing, will remain control centric for train, rake locomotive and stock management and terminal centric for booking, loading, unloading, and delivery. Taking into account the spatial distribution of activities, which need to be captured. Integrity of Operation and Commercial data is an absolute necessity. RMS and TMS application are conceptualized, to provide the integration with the other subsystems as and when these are developed. FOIS ultimately expects an event driven integrated reporting in real time, beginning with the tendering of Forwarding note to loading and generation of invoice, followed by load consists, train ordering and departure/arrival of load destination, unloading and delivery. The data thus captured is used for generating associated managerial reports on-line information (MIS). The data will also be used for expanding the scope to cover other functional areas of the remaining modules and can easily integrate with RMS/TMS using appropriate middle ware Technology for sharing information locally. Therefore, a strategic approach has been adopted to computerize IR operations by implementing RMS/TMS systems in a phased manner using modular approach. 6. FOIS System Architecture Key components of the System Architecture Intelligent terminals will be placed at the field locations to capture the data from the place of activity namely control offices, yards, goods sheds, C & W depot, Loco sheds etc., and connected to the identified Application Server through reliable communication links for transaction processing. Application servers are centrally placed at CRIS office. These servers are connected to the Zonal Hd. Qrs., Divisional Control Offices, yards, interchange points, and good sheds etc., with a reliable and integrated network. The servers are networked amongst themselves and to the central server for global level transactions. The central Server provides management Reports at board level and acts as repository of all the global data and also provides global services to maintain referential integrity of the databases including master files.] 7. Network Topology In view of the Centralized application architecture, a star based network topology has been designed. However, in order to provide alternate paths ( to meet the up time requirement of 99.9%) from reporting locations, a mesh has been created with in each zone so that every location has at least two paths to reach CRIS. Each zonal HQ has been connected to central location (CRIS) on high bandwidth pipes. In addition to this, another zonal location has been connected to CRIS using high capacity link. Hence these two high bandwidth links shall cater to the entire transaction load generated by a zone. Railway telecommunication network, leased lines, DOT, VSAT Technology as communication media has been provided for reliable and fast means of data transfer. 8. Phased Implementation – Approach h) In case implementation is attempted for events of all the functions to be reported in real time, concurrently from day one, then the reporting sites to be readied, the associated communication requirements and the number of staff to be trained assume enormous proportions. To ensure that the implementation effort is within manageable limits, one way is to take up, one by one, only limited portions of geographical territory for computerization at any given time. On the other hand, if the territory is small, instances of repetitive data entry increase; resulting in redundant expenditure on reporting infrastructure that will have no use as the territory expands. At the same time, if the MIS requirements are to be met in totality, the territorial expansion must ensure that a function is implemented on end to end basis as quickly as possible, otherwise only a truncated picture will be available to various levels of users and the benefits of computerization remain postponed till the entire Indian Railways have been covered. ii) The FOIS comprises several subsets of functions each meeting a distinct set of objectives. Certain FOIS subsets presuppose others to be operational before they can be implemented. Loco and wagon based functions presuppose load/train/rake functions to be operational. Goods shed functions expect wagon-based functions to be in place before they can be implemented. With these assumptions the FOIS / RMS systems have been designed in a modular structure which could be taken up for implementation in a phased manner. For example:- Phase I (PI module) Provides facility for reporting load summary with only wagon type and number of units. Phase II (PII module) Provides facility for reporting the consists with details of wagon numbers. Phase III (PIII module) TMS provides facility for good shed functions and generation of RR. 9. Implementation Strategy Realizing that functional phasing is the only way to keep the implementation effort within manageable limit and yet remain meaningful at every stage, FOIS software has been developed as above in three modules such that functions of global utility are implemented faster from fewer sites. It also takes into account that the beginning is made from the control offices where computer awareness is of a high order. The implementation can grow on need basis driven by the Railways themselves. For timely completion of field implementation, the total involvement and commitment of Railways is very essential from day one. Therefore, COM’s of Railways have been given the total responsibility and charge of implementation of FOIS, to provide for the following:- - Railways to get staff identified and train them to work on PCs - Railways to prepare the sites for installation of hardware including provision of electrical and civil facilities. - Maintenance of channels & data com equipment has been given to CSR of the zones. - CRIS would provide specifications for the same. For facilitating this process the organization of CAO/FOIS has been strengthened and made responsible for coordination, implementation on All - India-basis. The software implementation and maintenance shall remain the responsibility of CRIS. Pre implementation training of the required number of staff (consisting of Core Implementers and Telecom Inspectors from each of the divisions), in RMS - phase 1 has been completed by CRIS for all the zonal railways and their divisions. However, Railways will be required to make arrangements through the Zonal Training Schools to train the remaining staff of the concerned categories. 10. Benefits i) Continuous Cargo Visibility ƒ Rake based consignment tracking and pipeline ƒ Invoice based loading –Originating Tonnage & Revenue ƒ Information on trains on the run, the ETA at next point and the work to be performed. ƒ Vehicle guidance of all trains on run. ƒ Daily report describing the performance of all through trains operated in a controlled territory for the day. ƒ Actual/Estimated arrival and departure particulars for a particular train at any or all the reporting points ƒ Yard or on the run delay information. ƒ Train & stock Interchange ƒ Wagon wise Interchange ii) Optimised Asset Utilisation Improved Locomotive Utilization by reduction in Light Engine running and reduced in effectives Statement of missing or wrongly delivered wagons and finally its elimination. Elimination of unconnected wagons Increased Availability of Repair Capacity Stock Holding Loco Holding iii) Increased Revenue Savings in wagon fleet would result in corresponding saving in the recurring cost of maintenance of wagons ƒ Reduced Locomotive power and Rolling Stock Maintenance Cost ƒ Savings in Time & Cost of handling in yards, cost of empty haulage ƒ Ensures optimal crew management and monitors statutory limits for running duty and overtime payments ƒ Reduction in staff cost per unit of transportation due to improved productivity of the available manpower iv) Improved Productivity per/man Year  Accuracy of reporting –In the Head &Hand system collecting data on telephones results in sizeable error levels, which need to be reconciled &corrected periodically.FOIS data with built in validation systems has Zero errors. ƒ Drudgery of manual processes like maintenance of registers etc. is eliminated. ƒ Particulars of crew on train with hours spent on duty. ƒ Re-deployment of major portion of staff involved in wagon tracing and accounts checking activities. ƒ Improved Customer service and satisfaction ƒ Facilitation of acceptance (customer’s Orders), billing and cash accountals from identified nodal customer services centers and not necessarily at the handling terminals ƒ E-Commerce will facilitate the customers to operate from their premises for the above requirements of billing and cash accountal and thus reduce the burden of logistics management, and in addition drastically bring down the inventory costs. in the entire chain of physical distribution system. ƒ Quick settlement of Claims ƒ Just in Time Inventory v) Goods shed Operations Arrival particulars of Wagons Placement and Release Particulars Information on demands registered and pending Indents Preparation of Railway Receipts Information on Demurrage and Wharfage Loading Particulars Goods Shed Earning Information on delayed wagons and Wagons awaiting Placement/Release II. Application/Software RMS module has been developed with GUI interface which is highly interactive, very user friendly. The software is totally menu driven and navigation is through logically linked tasks. The application and front end forms for reporting events has been developed in Visual Basic and resides in the client machine located at the reporting location. Data is stored in the central server locate at CRIS. 1. General Concepts A Rake is a very generalized term, which refers to any set of wagons moving together and has been identified in the system as rake. Wagons can be attached/detached to a Rake. A Rake is identified by a uniquely defined ID number, which remains unchanged through various Load/Empty cycles & movements. A Rake, when given a destination, is known as a Load. A Load, when given a loco, is known as a Train. Thus, there can be no Train without a Load & no Load without a Rake (except where a load is mixed and is not identified in the system as a rake). With a clear understanding of these terms, you enter data through clearly defined “tasks”. The RMS software has two identifiable cycles- Train cycle: It starts the moment a load is identified as a train and the following tasks are used for online reporting: - Train Ordering: TO/Call between two crew-changing points. Train Departure: reports departure. Train Arrival: reports arrival. Train Run-through: reports through runs Train rerouting Yard Cycle: It starts as soon as a terminating load a terminating load arrives at its destination or a train is cancelled. (i.e. the load is sent to load planning)and the following tasks are used for various online reporting:- Load Related Tasks Inward Number Taking: destination validates consist. Load Planning: initial activity, following rake assignment. Load Stabling: run/ordering termination is reported through this. Load Diversion/Termination/Extension: reports changes in planned load destinations Load Yarding: takes a load-to-load planning screen, but will not reflect in stabled position. Vehicle Guidance Related Tasks Consist Reporting: originating station reports summary details. (Guidance is also called as Consist). Rake Related Tasks Rake Formation Details: form/modify rake consist. Movement order: facility to give advance assignments to rake Rake Placement/Release: reporting Load/Empty cycle. Rake Dissipation: for generating piecemeal out of rake or for doing away with a rake which has no wagons left. After a load is made ready, loco attached and train ordered Again the train cycle begins. Loco Related Tasks Attachment/Detachment of Locos. Loco Reporting: reporting shed activities of loco. Light Engine: reports light engine movements Given above is the list of tasks that are to be performed on real-time basis i.e. as soon as the event takes place. Demand:- This function is to be reported at station where the party/consignor registers his Demand for supply of Rake/Piecemeal wagon for loading of goods. The following tasks are used for reporting this activity:- New demand Modify demand Add/delete demand Fulfilling demand Forefeiture/Withdrawl of demand Interchange forecast:- In the system as the trains are planned, a pipeline is generated from Originating Station to destination and the position can be viewed at any point in its route. Forecast can be reported by selecting trains from the pipeline shown at the interchange point. The task used is interchange forecast reporting task. Given below is a summarized list of entity related tasks :- Rake Related Tasks Rake Formation Details: form/modify rake consist. Movement order : facility to give advance assignments to rake Rake Placement/Release: reporting Load/Empty cycle. Rake Merging: moving wagons from one to another rake. Rake Dissipation: for generating piecemeal out of rake or for doing away with a rake which has no wagons left. Load Related Tasks Load Planning: initial activity, following rake assignment. Load Stabling: run/ordering termination is reported through this. Inward Number Taking: destination validates consist. Load Diversion/Termination/Extension: reports changes in planned load destinations Load Yarding: similar to stabling, but will not reflect in stabled position. Cut-in by Arrival/Departure: was useful when there were non-computerized territories also. Train Related Tasks Train Ordering: TO/Call between two crew-changing points. Train Departure: reports departure. Train Arrival: reports arrival. Train Run-through: reports through runs. Loco Related Tasks Attachment/Detachment of Loco: reporting loco failure on run. Loco Reporting: reporting shed activities of loco. Light Engine: reports light engine movements. Roadside/Piecemeal Wagons Related Tasks Attachment/Detachment of Wagons en route: load & consist are automatically modified in this task. Piecemeal Placement/Release: reports piecemeal activities. Piecemeal Sick/Fit Reporting: reports sick/fit. Clearance of Detached Wagons: clears detached wagons. Demand: reports indents for a good shed type of loading. Vehicle Guidance Related Tasks Consist Reporting: originating station reports summary details. (Guidance is also called as Consist) Detentions Related Tasks Train Detention en route: reports unscheduled stoppages. Pre departure Detentions: reports detentions suffered by loads/trains at yards/stations. Other Tasks Interchange Forecast: reports daily targets, which should be frozen by noon. BPC & Crew Details: reports these details. Modify ETA: changes ETA for a train. Re-routing: changes path of a train while on run. As you realize, these are all routine tasks. Besides this the divisions have to carry out some systemic tasks which help in generating MIS reports (name for reports which are not generated on online data) and some time specific reports.  TSS (Terminal Sub-Systems) (Back to Index) TSS (Terminal Sub-Systems) is a generic word used in FOIS to refer to PCs, Printers & UPS. This PC is used for entering (and retrieving) data. Following are the important guidelines for users. Power Connection: Please make sure that a data entry PC or a “Reporting Terminal” is always kept in the “ON” condition. The power feed required is met through a 5A dedicated socket. Please make sure that all the different PCs & Printers have a separate 5A socket. Don’t use multi-plug adapters. Also check up with the Electrical personnel as to whether your sockets have Earthing arrangement. In absence of the same, your PC may get damaged. The earthing to neutral voltage not be more than 2- 3V. It is also better to have a MCB attached to main power supply point/board. Your AC connection & PC supply must be on different phases. This saves from fluctuations. Your PC is not connected to the mains directly. Instead, the Power supply is routed through a UPS (Uninterrupted Power Supply). Please ensure that this is always done. This saves your PC from power fluctuations as well as gives a power from batteries for about 20 minutes, in case of power failure. There should be a power back up, either through AT (OHE) or through Diesel Generator. The change over switch should be close to you.(care to be taken that earthing is proper) It is a healthy practice to ensure that various power chords feeding your PC, Printer etc are neatly tied together, rather than strewn all over. If you locate your UPS very close to your monitor, the display will wobble. Please ensure that UPS & Monitor are separated by at least 24 inches. When the PC is ON, don’t try to change any connection. This applies equally to not only power connectors, but also to various chords connecting different equipments, LAN Cables etc. When turning the PC ON, (if need arises) follow this sequence Mains → UPS → Monitor → Printer → CPU. The reverse is followed when switching off. Environment: If an AC is provided, make sure that it is working properly. AC should be on a phase different from the one feeding your PC. The room should be kept as clean as possible. Dust, smoke particles & moisture cause maximum damage to your PC. So, don’t allow any smoking, eating or drinking at the workstation. Never clean your PC using an organic solvent (such as Colin). Always use a soft, damp, dirt-free cloth. When the PC is not in use, keep it covered with “Dust Covers”. Make sure that the Keyboard has been supplied with a “Skin” – a tight-fitting plastic covering for Keyboard, which does not stop usage. Your PC should not face direct sunlight. Nor should it be placed so close to window where rains can affect it. CPU (Central Processing Unit) & Monitor should not be placed in such a way that the fans/outlets at the rear of these equipment get blocked by walls/other objects. Virus Protection: Viruses come to you PC through pirated softwares of games & utilities that you load. Yet another source is downloading of files from Internet. Once a virus is on a single PC of a network, it spreads on its own to the entire network. Therefore, you must not load pirated software or download wallpapers etc from Internet. Make sure that Virus protection files are loaded on your PC. Please enable virus scans on data transfers, floppy drive files & CD files. Please schedule your Virus software to run every day at a fixed time. To do this, open “My Computer”. Double Click on “Scheduled Tasks” Folder. Double Click on “Add Scheduled Task”. This will activate “Schedule Task Wizard”. Click next & select the name of the Anti-Virus program given to you. Keep following the simple steps to schedule your Anti-Virus to run daily. Once scheduling is done, your PC will automatically run the program everyday at a given time, as specified by you. There is an arrangement whereby we get updated Anti-Virus files every 3 months. These CDs are available at your Divisional HQ through OCC. You must update your anti-virus programs to enable it to take care of new viruses. There are tell tale signs of virus on your PC. Please be on lookout for these signs, which are listed below: Unexplained disk drive activity light or floppy drive light Reduction in RAM Availability “File Copied” message appears without copying anything Failure of a memory resident program to operate properly System behaves slowly or in a chaotic manner  Bad clusters on the disk Increased number of files on disk Increase in size of executable programs Change in file’s date and time stamp, without modification Program running slower; taking more time Program/Data file corruption/disappearance Internet Connections: There should be no Internet connection on your PC. This restriction is applicable to everything related with Internet – email, chat, surfing etc. Further, your PC should not have access to another network – such as Railnet. This makes the network prone to hackers & Viruses. Since the information available on FOIS is confidential, therefore hackers have to be prevented from entering our network. This is the reason for having separate LAN and Routers for FOIS. Important Files (Software): You work with Windows 98 (Second Edition). A quick restore CD is also available with you, along with Anti-Virus software & RMS. Also windows back up files are normally available in the cab folder. Please ensure that none of the following files are tampered. COMMAND.COM IO.SYS MSDOS.SYS Similarly, ensure that RMS file – which resides in Program Folder of your Hard Disk - is never tampered. Datacom Equipment & Connectivity In this chapter, we shall deal with some pertinent issues regarding Connectivity. Your PC is connected not only to adjacent PC but also to each & every PC on FOIS. (Each PC on the network, therefore, has a unique identification or Address – known as IP address). This has been achieved by using leased lines, ISDN connections & VSATs for data transfer. This data transfer rate is higher than PRS system. Also, unlike PRS terminal, your terminal is a full-fledged independent machine. The interface is Windows, unlike text type processing in PRS. Your PC is connected to FOIS through a Router, which is a junction between LAN (Local Area Network – connecting all PCs in your premises) & WAN (Wide Area Network – a bigger network which connects all PCs on the system). A Router does this mostly through Channels – which are connected to it using Modems. (A channel has two ends. One end is connected to Router through a Modem in your premises. The other end is again connected through a Modem to the equipment of Channel Provider, at his premises. This can be S&T or BSNL or any other telephone company). Finally, a Router will have connections with your LAN (through Hub/Switch), Modems (one for each channel), ISDN Connections (directly to Router) & VSAT (directly to Router). All this equipment is collectively referred to as Datacom Equipment. Routers: A Router routes the data that you want to send/receive. It is an intelligent device, unlike Hubs & Modems. The data is sent & received in data packets. A LAN works below a Router. Data sharing between various PCs connected on a LAN is automatic & Router has no role. It is only when the data requires being sent/accessed from a remote PC/Server – i.e. accessing WAN terminals - that Router’s role assumes significance. Its IP Number specifies each Router – like all intelligent devices on a network –. This IP Number actually identifies its Ethernet port. A Router may have WAN, LAN, & VOICE port. A port is actually a point where a channel (through Modem) or LAN or ISDN or VSAT connection can connect to Router. On Railways, we have two makes of Routers supplied – Cisco & Motorola. Router has to remain “ON” at all times. Also ensure that the power feed is having a proper earthing arrangement. The earthing norm of 2-3V to be maintained. Power supply to Router should be routed through a UPS. Never operate a Router without a UPS. Also, wide fluctuations in input voltage can damage the Router. There should be a power back up, in addition to Normal Power Supply. This could be through Auxiliary Transformers (AT) in OHE area or through a Diesel Generator Set (DG Set). The change over switch should be accessible easily. The Router should be kept in a dust, smoke & moisture free environment. Please use Racks provided to house the Router. Since Router is expensive & sensitive equipment – which does not require daily maintenance – therefore, it is better to leave the equipment undisturbed. Essentially provide Air-conditioning for routers. A Router, along with Modems should be placed at a location where it is always accessible to the user. You actually don’t have to do anything with Router, but just by looking at various displays & reporting the same, you will be participating in troubleshooting. For this reason, you must have Router under your control and not locate it in Test Room. Some of the Routers have a specialized Port for ISDN. (Not all Routers have it). Unlike all other terminating leads on a Router, ISDN connection gives a higher voltage (≈ 100 V). Therefore, if ISDN lead is connected to any other port, that port will burn down. Be careful. Firm connections of all chords to Router are to be ensured. Nothing should be placed on Router. Router should not be dragged. Modems: Modem (Modulator/Demodulator) is the device through which a channel connects to your Router (& through it, to your PCs on LAN). It is a very sturdy & maintenance free device. It also requires a dust & smoke free environment. It is normally housed in a Rack along with Router. A lot of information is available on its front display. We have two types of Modems on Railway – G703 (at service provider’s premises) & V35 (at our premises, with Router). When the channel connected to a Modem is working properly, you will find both “RD” & “TD” glowing & blinking. If it is not so, then there is some problem with channel. As always, you have to ensure that Modem is always kept “ON”. Also ensure that the power feed is having a proper earthing arrangement. Never use a metallic brush to clean the surface. Organic solvents are also not permitted. Since one end of a channel always resides at the channel provider’s premises, therefore you must also know some simple checks to analyse the channel position. Some of these steps you take in tandem with the operator at other end, who is observing his Modem. These steps, which are invoked when the channel is down (i.e. “line protocol” is down), are Make “LL” (Local Loop) switch “ON”. This gives the status of the Modem & Router. If “TD”, “RD” blinks, then local equipment is OK. If it doesn’t, then the problem is with Modem/Router. In the next step, we make “RL” (Remote Loop) switch “ON”. This checks the local lead condition between Modems. However, to get the response of this action, there should be an observer at the other end. If everything is OK, then at the remote end, “RD” & “TD” will blink. Similarly, remote end can also give a “RL”, in which you will get blinking “RD” & “TD” on your Modem, if everything is OK between two Modems. If both “RL” & “LL” give OK results, then the problem is beyond the Modem at service provider’s end. You have to take a docket number after registering the fault with service provider (i.e. S&T or BSNL). If Modem at the other end is not able to execute “LL” successfully then Modem at that end is defective/improperly connected. If all loops show positive result & line protocol is still down, try initialising Modem by switching it off & then on. If everything gives OK & data is still not able to pass through then there may be problem with Router. Inform Divisional Control. Always ensure that all leads are firmly connected. However, no lead should be checked with power at “ON” position. Channels: A Channel refers to a leased line dedicated channel for data transmission. You have two types of channels – Railway & BSNL. However, as a user you don’t see a difference. Though technically a Channel refers to a leased line channel, in this section we will also cover ISDN & VSAT in it. A channel connects your system through Modems & Routers. In addition to leased channels, you also have ISDN connections & VSAT (Very Small Aperture Terminal) connections to enhance your Connectivity. Connectivity refers to the immediate links that your PCs on LAN (at a Node) has with neighbouring nodes. It has been planned that ideally each node has a minimum of two links, each giving a different route to your data – so that data transmission can continue even if one link is down. This is technically known as Route Diversity. Unless a Channel is available, data will not transmit. If your node is connected through two channels & one of them is down, you will not know the difference. However, with one channel down, you are in a very precarious position as data entry will stop as soon as the second channel even flickers. It is therefore important for you to take active interest in knowing the state of a channel. This can be done through “pinging”. Pinging is the name given to sending & receiving a test data packet from one computer to another remote PC/Router or to any intelligent device. However, you can ping only if you know the (IP) address of remote PC or Router. These are listed in Annexure I. You can ping by following command Start → Run → Ping [IP Address of Remote Router] → OK Only an entry like “Request Timed Out” or “ttl expired in transit” indicates failure. VSAT connections can also be pinged. Some other important points for VSATs are as follows The data is transferred directly to CRIS SERVER. This is a sturdy system, which once stabilized, works trouble-freely. The earthing resistance should be less than 1 ohm. Neutral to earth leakage should be 2V. It should never work without UPS&CVT Air-conditioning is a must. The antennae base structure should be firmly fixed and clamped. At the time of installation it should be ensured that ODU is having its protective laminated cover(to protect it from water and dust) OR at least the rubber cap of Radio Frequency (RF) unit is in place. There should be one ladder for antennae access. There should be a routine of checking the equipments. It should be ensured that rubber cap of RF unit is in place and the cord going to indoor unit is firmly in place. Similarly, ISDN connections can directly pass the data, bypassing Router (or more accurately, bypassing Router at that node but connecting to a remote Router). Only in such ISDN connections where Routers are not provided, you will not know the status of channel through pinging. Please ensure that ISDN connections are always with power “ON”. Also ensure that ISDN connections are not STD barred. Though it is not possible for you to know as through which particular channel your PC is transferring data, the same is always very accurately known to Router. Depending on the channel availability, it keeps on defining the route dynamically. Thus, if ISDN is available & all other channels are down, Router shall use ISDN to transmit data. (ISDN connection can also be assigned a higher priority by configuring the Router). As soon as any of the other channels becomes stable for a predefined time interval, it again resumes data transfer through that channel, shutting off ISDN. This is what is known as programming of Router. ISDN is a secondary channel and since its usage is very expensive so it should be used very judiciously. LAN: LAN connects all your PCs available at a location. However, it need not be confined to a building. It can be extended to a few kilometers (up to 6 km) also. Such extension is normally through a LAN Extender. Even if PCs are connected through LAN Extender, there is no role of Router in sharing of data among these PCs. LAN is achieved by using the network card available on your PC. An identical work group is to be defined on each PC on the LAN so that they are “visible” to all other PCs. While defining Network Properties on your PC, make sure that only one Gateway (i.e. IP address of your Router) is defined. Disable DNS. A PC may be visible on a LAN. However, other PCs can use only those files, folders, drives etc of that PC which the owner of that PC has decided to “Share”. To share a file, single click on the file name, followed by right click. Select “Properties”, followed by “Sharing” tab. Share to the extent you desire. You can decide to allow other users to even write on your Hard disk. However, you cannot differentiate between your co-users on LAN & other users on WAN! You can also share some scarce resources – such as Printers – through this scheme. LAN wiring consists of two parts – first, a CAT5 structured cabling from Router/Hub to I/O box (a 3” x 3” x 2” white box) & second a flexible cable from I/O box to your PC. Please ensure that all PCs at a location are connected on LAN. Ensure that CAT5 cable is mounted on wall properly & is not hanging loosely. Ensure that flexible chord is not stretched. Also ensure that I/O box is located close to your PC. Hubs/Switches are devices for connecting additional PCs to Router’s LAN port. Please ensure that these are properly mounted on wall. Uptime: It refers to the time when a node or a channel remains available for data entry. As explained earlier, it is of utmost importance to know the status of availability of equipment for user. You should keep records both of Channel Uptime & Node Uptime. It is easier to maintain record of Node uptime. Simply record in a register the daily position of availability of a node. (Along with the reasons of failure for doing analysis.) It is very essential to keep check on the health of secondary channel when primary channel is up. Give summary position of the entire day to your Zonal OCC at odd hours. For finding the channel uptime, you have to schedule task of pinging, even if your Node is up. Ideally, every 4 hours, you should ping to adjacent Routers & note the result. This, compiled over entire day, will give channel availability of each channel at your Node. Record this also in a register, giving message to Zonal OCC through Messaging Feature of RMS. There should a fixed regime of reporting of failure to be in place so that in case of a failure trouble shooting is fast. A list of phone numbers of service provider should be readily available both at div headquarters and zonal headquarters. You also have to keep tab on the time taken by various service providers to attend to your reports of breakdowns of Routers, Modems, UPS, Printers, PCs etc. This should be in a separate register, which is not to be reported daily to your headquarters Other Applications: Do not use your FOIS network for any other regular data transfer programs. This can cause virus threats, slowing down of application, vitiate OCC tasks & mis-programming of Routers. Within LAN, you can share information occasionally. However, running regular & heavy program may reduce the availability of system for data entry to FOIS. Please don’t run any heavy or regular programs on your LAN. Unless you procure genuine copies of software that you intend to use on a single PC, please don’t load it. In any case, this should never be done on a “Reporting Terminal”. Other Networks: Your PC should not have access to another network – such as Rail net. This makes the network prone to hackers & Viruses. Since the information available on FOIS is confidential, therefore hackers have to be prevented from entering our network. This is the reason for having separate LAN and Routers for FOIS. Do not allow any Internet connectivity.  SYSTEM ADMINISTRATION (Back to Index) Operational Control Center (OCC) For successful implementation of FOIS over Indian Railways each zone shall have to undertake following responsibilities towards FOIS. Real time updating of system data Management of Network Maintenance of equipment – PCs, Printers, UPS, RAS, LAN extender, Routers, Switches, Hubs and associated accessories Replacement of manual information system In service training To achieve this each zone should deploy personnel to set up an Operational Control Centre (sufficient work charged posts have been provided and adequate staff has been trained by CRIS). OCC will be the empowered body for prescribing and enforcing working procedures. It will also monitor performance and take appropriate (pre-emptive and remedial) measures to ensure cent percent availability of system. OCC shall be manned round the clock to operate NMS and to provide proactive support to field reporting units (help desk) in every respect. It will have additional functionaries during day shift for management support for maintenance, analysis of system efficacy, up gradation of procedures, and escalation as may be required. Real time updating of system data Procedures, roles and responsibilities should be prescribed to ensure that data is entered into the system as soon as the physical event has occurred but definitely before the next event takes place these delays can be monitored with help of Transaction log (Query Operation Control Exception task Transaction log) Procedures should be location specific and further device specific i.e.functionary specific. Specific office orders to be issued covering every possible eventuality on a given territory with the sole objective of not allowing any data element to escape. Participation of train staff to deliver data though train documents for both normal and abnormal working will be prescribed as local procedures. In case, when abnormal working has been introduced on account of failures, OCC to co-ordinate for proxy reporting and restoration of normal working. Each division should nominate a Sr. supervisor who shall be responsible for timely update over his division and accountable to OCC. Reporting terminals have been provided at divisional and sub control offices, in yard locations, (terminals are provided at the place where all the information required to be input is available). Control Office will report for non-device locations. The entire gamut of reporting to the system is to be engineered around these terminals, which must be manned round the clock. Procedures should also be prescribed for reporting in case any failure affects data entry from the nominated device beyond two hours. Each division shall have a predetermined reporting regime in case of failure. In such cases data should be entered from a pre-defined alternative device at that location/site or from the reporting devices at another location by following the mechanism of proxy reporting. Proxy reporting will be possible through the permission of zonal OCC who will enable the nominated device to report for the failed location/site. Proxy reporting regime can be devised on the following lines: a) If at a location, terminal/s have failed, reporting will be donethrough remaining terminals at that location/site. b) At a location there may be several sites. If a particular site has failed, proxy reporting will be done through a nominated site. c) In case of failure at yard - Divisional Control or sub control office will report d) In case of failure at Division - Zonal OCC will report e) In case of failure of complete Zone – Disaster management will come in use. Management of Network: - Having route/media diversity and adequate spare equipment has provided sufficient redundancy. It should always be ensured that redundancies are always in working order. Monitoring the functioning of Network with the help of NMS software installed is also the function of zonal OCC that has to be manned round the clock on a continuous basis. It will include – Ensuring that primary and secondary data and voice channels are in working condition. If your node is connected through two channels & one of them is down, you will not know the difference. However, with one channel down, you are in a very precarious position, as data entry will stop as soon as the second channel even flickers. It is therefore important for you to take active interest in knowing the state of a channel. This can be done through “pinging”. Pinging is the name given to sending & receiving a test data packet from one computer to another remote PC/Router or to any intelligent device. However, you can ping only if you know the (IP) address of remote PC or Router. List of IP addresses of your zone should be available with OCC. You can ping by following command Start → Run → Ping [IP Address of Device] → OK For finding the channel uptime, you have to schedule task of pinging, even if your Node is up. Ideally, every 4 hours, you should ping to adjacent Routers & note the result. This, compiled over entire day, will give channel availability of each channel at your Node. Registering complaints for channels that are not working and following up for rectification. Liaison with both BSNL and railways for the above. Routers have been configured to route data on a predetermined priority. Rerouting and load balancing will have to be done through OSPF (Open Shortest Pathfinder) on the NMS and need basis. Analysis of network failures for identifying problematic links for up gradation. Monitoring payment processes of rentals of communication channels. Trouble shooting for other equipment failures in association with central OCC and ordering its replacement from the spares. Maintenance of equipment: Regarding maintenance of equipments, OCC shall keep a record of hardware components provided at each locations/sites and their failures at zonal headquarters and its division. Repairs will be through maintenance contracts. A PC breakdown (either Monitor or CPU or UPS) is crucial as it affects data entry. However, you must first make sure that there is no such problem, which cannot be fixed locally. Please check for power chord, operating system & RMS program. (A step-by-step procedure is given in Annexure – III. If all of these are there & still your PC does not respond, bring it to the knowledge of Divisional HQ. At each site you have one extra PC, complete in all respects, to take care of such eventuality. Replace the defective PC with this stand-by. Finally, report the failure to concerned vendor or as prescribed by the maintenance practice of that div/zone. Addresses of vendors should be readily available. OCC should prescribe spare maintenance practices on their respective zones. The following points should be kept in mind before prescribing any spare maintenance practice: - - Uptime requirement of location - Accessibility of vendor from a location - Sourcing of spares may be done from a central point ideally a big city were vendor services are available readily.  In house skills would be confined to troubleshooting and to replacement of equipment out of spares. NMS software also helps in troubleshooting. Vendors with whom AMC has been drawn and entered can then repair defective pieces. Replacement of manual Information System: Suspension of parallel manual system will be the biggest challenge. It has to be gradual. First of all it will have to be explained to operations managers that value lies in using application in an interactive mode. Dependence on fixed time reports should be minimized. Fixed time reports should be more in the nature of exception reports to reflect failures. It would be prudent to prioritize this effort in the following order. Interchange Stock and Demand c) Loco inventory OCC will in consultation with COM prescribe a schedule for identified manual reports and bring systems stability in terms of data capturing in those areas first. OCC will also evolve a mechanism to analyze systems usage at every step and match it with expected returns. Returns can be in terms of savings in efforts, accuracy of information, avoidance of disputes, less correspondences and cross references, more time for planning operations, resultant customers satisfaction, enhancement in business achievements and productivity (redeployment achieved, overtime curtailed), reduction in work pressure amongst staff, less diversions etc. From the analysis of application by OCC, it is expected that items for up gradation of application further will get identified. However before undertaking development OCC will weigh every new requirement for its return justifies it and then only forwards it to agencies responsible for application development. In service training: It is very essential that concurrently a programme be made by each railway to disseminate the learning to rest of the cadre. The training should be institutionalized taking the help of zonal training schools. The components of training will comprise exposure to revised ground procedures for data collection and maintenance, reporting tasks of the application and OCC functions. The participation of all those in the field who are associated with operations taken together will only ensure sustained upkeep and usage of the system. The FOIS training should be made a part of the induction and refreshers courses of TNC, GC, SM, TXR, Trains, Power, C&W and Commercial Controllers, Guards, and Loco pilots. There will also be an element. This training is essentially for understanding of procedures and application tasks. In case of those who have to man OCC and perform its functions an extended module will be prescribed in addition to training in procedures and application tasks. OCC of each railway will nominate trainers from their existing cadre strength who in turn will be trained by CRIS to establish training processes on their railways and train others. OCC will thereafter monitor progress of training on their railways and ensure that regularity is maintained. Miscellaneous Issues Printing Reports: All reports, which are available on display, can also be printed. You should decide as to which reports are most useful & which require printing. You can print either the view shown (through F7) or you can choose which columns & rows you want (by clicking them) & then print your selection by pressing F11. For printing, you should have a Dot Matrix Printer attached either to Network or attached to a PC & “Shared”. You must plan in advance for your requirement of paper & ribbons. Messaging Feature: This is a very powerful communication tool that should be used for meaningful works only. Don’t allow it to become a general-purpose e-mail feature. Since the addressee is not a filter, the entire list of messages for a station increases exponentially. However, use it freely & liberally for communicating messages related to freight operations, FOIS messages & emergent non-personal messages. Passwords: The RMS package has a concept of passwords. For each user, who enters data, such passwords can be defined. Once a password is given by CRIS, you can change your password on your own by going to Access > Password. As a supervisor, you must also ensure that anyone who is going away from FOIS work (on transfer etc) should be struck off from user list & his password is disabled by CRIS. Assigning passwords gives responsibility to user. This password helps in keeping the security trail i.e. the reporting done carry the id of the user. Password management task is being passed on the zones so that they can manage password on their own without getting CRIS involved. Besides RMS password there is Windows password, which you use at the time of logging in your PC, if you are using this password then all the users of that device should know it. Reports available in RMS module : CONFERENCE SET Interchange forecast summary: gives desktop summarized view of forecast & interchange of current date. It is updated by I/C forecast and arr. /dep reporting task. Running interchange: gives detailed view of forecast & interchange and also gives running position of trains forecasted. It is updated by I/C forecast and arr. /dep.reporting task. Current interchange: gives summary information of interchange with break-up of empties and loaded stock, stock (4w) interchanged. It also provides summary of jumbo and box rakes interchange It is updated by I/C forecast and arr. /dep. reporting task. Likely shortfall : gives summarized view of interchange along with trains likely to shortfall along with the reasons of their shortfall. It is updated by I/C forecast and arr. /dep. reporting and I/C shortfall reporting task. Train interchange shortfall: gives shortfall /excess of yesterday interchange along with reason of shortfall in despatch. It is updated by I/C forecast and arr. /dep. report task. Stream wise pipe line : provides pipeline between two nominated stations and also pipeline for a via. It is updated by Load planning, Train ordering, arrival / departure reporting tasks. Loads on run : this is an unstructured query for all loads on run in the system. There are different filters available for viewing loads according to users requirements. It is updated by Load planning, Train ordering, arrival / departure reporting tasks. Traffic flow :gives information regarding likely traffic flow terchange points upto 3 days in advance. It is updated by Load planning, Train ordering, arrival / departure reporting tasks. Outward train railway wise: gives division wise destination railway wise view of all outward trains on a zone. Filters for rake types, commodity are also available. It is updated by Load planning, arrival / departure reporting tasks. Terminal position: displays total rakes at the terminals as well as the insight for those terminals. On selecting a cell relevant details rake wise are displayed. It is updated by arrival/departure reporting, I/w no. taking, Rake placement/rel tasks. Terminal performance : gives terminal performance for a selected period It is updated by arrival / departure reporting, I/W no. taking, Rake placement /rel tasks. Terminal history: gives details of individual rakes handled at the terminal for a selected period.It is updated by arrival / departure reporting, I/W no. taking, Rake placement /rel tasks. Terminal performance and running position: gives status of load at terminal along with its insight. It is updated by arrival /departure reporting, I/W no. asking, rake placement/rel tasks. ODR wise rake outstanding (details):gives ODR wise outstanding demand details It is updated by demand reporting task. Rake performance: gives performance of rakes for the period they were in the division /zone along with total kms ran in the division. It is updated by arrival / departure reporting, rake Formation/dissipation, I/W no taking, Rake placement /rel tasks Rake position: gives break up of rakes over a division/zone Under following heads:U/R,U/L,O/W,I/W and Empty. It is updated by arrival / departure reporting, I/W no. taking, Rake placement /rel tasks Rakeintegrity: gives details of all attachment/detachment/sick reporting on a individual rake on the selected zone. The examination & dissipation if done) is also shown. Further details can be seen after selecting a cell and pressing enter. It is updated by all rake reporting, consist reporting, and TXR examination Current traffic flow: holding of each railway is shown in terms of I/W,O/W and empties. the flows between the railways are shown by arrows for both loaded & empty rakes. Details of individual rakes can be seen on selecting the desired cell and pressing enter. It is updated by all rake & load reporting Terminal management planning: for a selected group rake type, division wise, outstanding rake demands, rakes on hand and pipeline of terminating loads are displayed. On selection of cell & pressing enter, details relevant to that cell are displayed. It is updated by Demand, rake placement/rel and arrival/departure task. All stock: current rake holding of zone is shown division wise, specifying loaded empties, at terminal, cross traffic (through), originating for foreign railway, local and terminating received from other Railways. Facility to see details of individual rakes on selecting any cell is also available. other stock icon in the conference set run on the same query BCN,BCX, CRT,BOXN,BOX,SHERPA SHERPA- N,CONTAINER,TANKS) It is updated by load planning, consist reporting, Placement /release tasks. Loco position: this query displays all the locos for the selected Division, location wise. A type wise summary is also displayed. It is updated by loco reporting, arrival/departure, loco attachment/detachment task.  MANAGERIAL REPORT (Back to Index) Interchange Yesterday Yesterday Interchange: This query displays the information of the trains actually interchanged in terms of the Loads and Light Engines at the divisional interchange point., The shortfall and excess columns display direction wise summary of loads that were short or excess vis a vis the forecast for the previous day. Receipts and dispatches are shown separately for each of the I/C point. It is updated by the Interchange forecast and Arrival/Departure Reporting tasks. Current Interchange monitoring this query gives view of current I/C, giving the Status of forecasted trains and also the trains, which are not forecasted, but are likely to go in the I/C. It is updated by train forecast, arrival/dep tasks. Rake & Terminal Position Yesterday 24:00 Hrs Terminal Position: gives status of load at terminal alongith its insight at 24 hrs. It is updated by arrival/dep reporting. I/W no.taking, Rake placement /rel tasks Current Optimised movement of rakes This query displays movement of rakes originating from the logged in zone and available in the database till the queried date. It shows empty and loaded runs of the rakes and the kms clocked by them and time taken for a run. It has the facility for displaying the detention details of the rake.Filters are provided to view details of specific commodities and stock types. This information is updated by the arrival/departure, rake formation /dissipation, placements/release- reporting tasks. CC rakes BPC Position: this query gives running details of close circuit rakes which are running in the system on the logged in date for the logged in Zone/div.or selected BPC station of that zone. Option is available for selecting a rake type also if the rakes of a specific rake type are to be seen It is updated by BPC details, train arr/drake formation/dissipation tasks. Movement of a rake It shows empty and loaded runs of the rake on entering the ID of the rake the kms clocked by them and time taken for a run. It has the facility for displaying the detention details of the rake.Filters are provided to view details of specific commodities and stock types. This information is updated by the arrival/departure, rake formation/dissipation, placements/release- reporting tasks Demand & Loading Yesterday Commodity wise loading and outstanding This query displays loading information for a Division/zone against particular station in terms of the no. of rakes 4w, piece meal, 4w, and the total tonnage and freight. The user can use options for (a specific consignee or all consignees or excluding a consignee) and for a (specific commodity, or all commodities, or excluding a commodity).These options are mutually exclusive and can be used in any combination. Load Planning, Consist Reporting, Loading tasks, updates this query. Yesterday Loading Terminal wise loading of rake demand This query gives the terminal wise rake loading performance of a zone/div. along with demand details and handling activity details. views of commodity wise and destination rly wise summary are also available Option is also available for viewing terminal wise unloading details in term of balances. Arrival/departure, rake formation /dissipation, placements/release-reporting tasks updates this query. Loading performance This query displays loading information for a Division/zone against particular station in terms of the no. of rakes 4w, piece meal, 4w, and the total tonnage and freight. The user can use options for (a specific consignee or all consignees or excluding a consignee) and for a (specific commodity, or all commodities, or excluding a commodity).These options are mutually exclusive and can be used in any combination. In this query there is submenu for O/S loading division wise and commodity wise loading and o/s. Demand reporting and placement/rel. tasks, update this query. Current Type wise stock position this query gives break up of all rake types or selected rake type over the zone (in terms of rake/pm).on selecting a row and pressing enter Details of the highlighted wagon type are shown. This query is updated by arrival/departure, rake formation, dissipation, and consist reporting tasks. Piecemeal outstanding summary: gives destination wise details of piecemeal o/s over a zone with ODR Demand reporting and Piecemeal placement /release tasks update this query. Loco Power interchange gives summary of Zonal loco I/C and also a summary of holding of locos type wise over a zone. Arrival/departure and loco reporting tasks update this query.  OPERATIONS CONTROL (Back to Index) Interchange Yesterday Train wise interchange This query displays I/C load wise of a division I/C point wise for specified date. View is available for specified I/C point and direction. The details of loads, like load name, L/E, type, loco, unit, I/C date/time for handed over and taken over is listed separately. This information is updated by load planning, arrival/ departure tasks. Load interchange analysis This query displays I/C load wise of a division I/C point wise for specified period. View is available for specified I/C point and direction. The details of loads, like load name, L/E, type, loco, unit, I/C date/time for handed over and taken over is listed separately. There are filters provided for originating zone/div/station and terminating zone/div/ station so that various analysis can be done on I./C data. This information is updated by the arrival/departure and I/C reporting tasks. Stock interchange load wise This query displays summarized information of receipts and dispatches of stock at divisional level for a specific type of stock. Loaded stock classified in terms of through and terminating. Empty stock is shown separately. This query displays and distribute output fields like No./units for each classification with total(No./Unit), for both receipts and for every I/C point. This information is updated by the arrival/departure and I/C reporting tasks. Current Stock forecast The query displays summarized information of receipts and dispatches of stock at Divisional level for a specific type of stock. Loaded stock classified in terms of through And terminating. Empty stock is shown separately. This query displays output fields like No./Unit, for both receipts and dispatches for every I/C point. The train I/C forecast reporting task updates this information. Stock interchange (summary) An online query which gives forecast and actual trains ran till the time of viewing the report, along with stock interchanged in terms of L/E in 4- w units I/C point wise. Summary of I/C is also given rly wise. I/C forecast and arrival /dep update this query. LOAD & PIPELINE Yesterday Change in load destination The query gives information on the loads for loaded/empty/mixed/All within Zone/Division with revised change of destination and the station where the change was effected with the message No. and the functionary who authorized the change of destination. The reports can be obtained selectively for a specific commodity, for consignee or for a specific destination. This information is updated by the change in Load destination tasks. Stabled loads at 24.00 hrs. This query gives information on the loads for both loaded/empty stabled with date and time, reason as at odd hrs. This information is updated by load planning arr/dep and train stabling tasks. Current Type wise Terminating load in sight The query gives information of terminating loads for a station/division. The loads details along with the current location and status with the expected arr/dep time and date at the I/C station and destination. Are displayed. This query is updated from Load Planning, train ordering, Train Arrival/Departure tasks. Outgoing loads gives details of loads which have originated from the logged zone/div /station. It also gives the I/C time of that load and also its expected time at its destination. Load planning, placement /release, arrival /dep, tasks update this query. Running position optimized destination wise This query displays rakes loaded from a zone and are running on that date. It gives loading details and I/C date and time, its current status. filters are provided for stock type commodity and unloading zone. Load planning, placement /release, arrival /dep, tasks update this query. STOCK Yesterday Rake performance: gives performance of rakes for the period they were in the division /zone along with total kms ran in the division.(query picks rake from their date of exit from zone/div) It is updated by arrival / dep reporting, rake Formation/dissipation,I/W no. taking, Rake placement /rel tasks Stock holding:The query displays yesterday position of the total holding for the zonefor all Wagon types, loaded and empty, separately for piecemeal, Rakes and DVS Stock. Details of a stock can be seen by selecting that stock type by clicking and pressing enter. This query is updated by Inward No. taking, departure, consist reporting, rake formation/dissipation,and attachment/ detachment of wagons enroute reporting tasks. Rakes at 24 hours: The query displays information of rakes at 24 hrs on yesterday. Rakes group type wise or rake type wise for a specific commodity included, or commodity excluded, or all types and for a specific consignee included, or a specific consignee excluded or all consignees for a zone. This query is updated by Inward No. taking, Arrival/departure, consist reporting, rake formation/dissipation and placement/release tasks Current Rake Position The query displays information of rakes on real-time basis. Rakes group type wise or rake type wise for a specific commodity included, or commodity excluded, or all types and for a specific consignee included, or a specific consignee excluded or all consignees for a zone. Inward No. taking, Arrival/departure, consist reporting, rake formation/dissipation and placement/release tasks Destination Rly Wise Outstanding displays demand details of a zone, division wise, clubbed on destination railway basis. Gives details of commodity and no. of units indented.filters are provided for viewing rake/piecemeal wise demands, commodity and consignor can be selected. This query is updated by demand and placement /release tasks. I/W traffic shows handling details of inward loads of a specified terminal on current date basis. Arrival/departure and placement/release tasks update this query. O/W traffic shows handling details of outward loads of a specified terminal on current date basis. Arrival/departure and placement/release tasks update this query. MISCELLANEOUS Load Wise Route This query gives the complete route details for the selected load (selection is made by entering the load name ) like load from-to, load direction, load type, units, stn, Arrl/Dep. Date/Time, Inward Dren, Outward Direction of the selected load. This information is updated by the load planning Train ordering, arrival/departure tasks. Load Wise Train Details This query gives the details of all the trains ordered for a particular load’s journey(selection is made by entering the load name ). The load is recalled by giving departure time from the originating station details of each train leg are also available including the Loco details. The train details show all the stations en route and the reporting, if any, made during that run. This information is updated by the Train ordering and arrival/departure tasks. Train Schedule This query shows all train schedules in the system between any pair of stations. The details show all the stations in the train schedule, including indicators for zonal, divisional and sectional interchange. This information is updated by static database in the system. Route display This query shows the default load route between any pair of stations. The inward and outward details are shown against each interchange station on the route. This information is updated by static database in the system. Invoice details gives details of invoices made generated in a division/station for a period. This query gives RR details and freight and weight of loading done. This information is updated by demand registration, placement/release and RR reporting tasks. Station Help This Query provides help regarding station code or name/. In case only part of either station name or station code are known, the system shows all stations in the database having the input name as a part.This information is updated by static database in the system. Booking profile this query gives the booking profile of the selected station as given in the Alphabetical List of IRCA This information is updated by static database in the system. EXCEPTION TASKS Transaction log this task is provided to monitor the delay in reporting Taking place. This can be viewed for a date and for a division/station. There are filters to view train and rake reporting tasks separately Train and rake reporting tasks update this. Statistical Report (Reports) INTERCHANGE I/C Summary gives I/C summary in terms of no. of loads Interchanged vis a vis forecast and shortfall Forecast and arrival /dep tasks update this query LOAD & PIPELINE Reason wise stabling gives details of load stabled during a specified period along with load details, reasons of stabling and the time when that load was lifted Stabling, load planning and arrival/dep tasks updates this query. Diversion register gives diversion details for a specified period Filters available for originating station commodity, i/e Diversion task updates this query Maintenance procedures for FOIS: CHECK LIST FOR DAILY MAINTENANCE OF HVNET VSAT PREREQUISITES 1 Minimum 1KVA On line UPS – dedicated to VSAT 2 Dedicated Electronic earth less than 1ohm 3 Earth to neutral Voltage should be less than 2 volts 4 Air –conditioned dust free environment with clearance of at least 8” in front and rear of indoor unit. This provides airflow and prevents overheating. 5 AC input requirements-230v+10%v VAC 47-63 Hz for PES 6 Grounding of VSATs antenna and unit is a must resistance should be less than10ohm 7 AC input voltage to PES must be derived from UPS output only (Live to neutral 230 VAC Live to Earth 230 V Neutral to Earth OV) 8 Do not allow moisture to enter in the RF unit. Plastic tape should be put on all the Connectors at the ODU. A properly designed rain protection over can also be used to prevent the same. ON-OFF PROCEDURE 9 1. Do not put off the power supply. Keep it continuously “on” because Hub is always polling each location for status and control signals must be received at any time from the Hub. 2. If PES is switched off and subscriber switches it on, in this case PES will take nearly 40 minutes to get ready for normal working provided it is ON continuously for that period. 3. Observation of the LEDs should be recorded during this period and it may be conveyed to HUB if PES does not come to normal position i.e. dots do not flash on all cards of PES. 10 Single phase 230 ohms 50Hz with input circuit breaker of 3amps for protection PRECAUTIONS 11 Do not disconnect the IFL cable from DIU without switching power supply off. This may damage equipment. 12 Protect your antenna/FL cable/ODU from tampering by unauthorized person. 13 To prevent damage to the DIU turn power off before connecting/disconnecting any telephone failure to remove power may damage the VDPC card. 14 Do not use rotary telephones with VSATs. Use only Touch tone (DTMF) telephones. 15 Do not place equipment, which produce dust near the DIU (Certain copier of computer primers produce carbon dust, which can cause malfunction. 16 Prevent moisture from getting inside DIU 17 Limit the distance between VSATs DIU to telephone instrument 15 meter for proper operation. 18 For normal operation the VSATs should be displaying, flashing dots in all the cards i.e. IFM, VDPC and MPC. Any other display is an abnormal condition In case of difficulty contact HUB numbers: (To be taken from CRIS) Specify the display of all the three PES cards PES= Power Earth Station ODU= Out door unit DIU= Digital Indoor Unit IFM=Intermediate Frequency Module VDPC=Voice Data Port Card MPC=Multiport Port Control  INTEGRATED COACHING MANAGEMENT SYSTEMS - AN OVERVIEW (Back to Index) 1. MODULES IN ICMS i) Punctuality Module (PAM):For Post facto analysis of punctuality loss and its causes (not an on-line system), Captures train running at Originating/ Terminating and interchange points and the causes of detention. Data input predominantly at Divisional HQ level. Status: Implemented. ii) Coaching Operations Information System (COIS): Captures events on Coaches/Rakes, Generates Reports for Management of Coaching Stock. Data input predominantly at Station/Coaching Yard level. Status: Implemented. iii) COIS Data Entry Module: Support module of ICMS, to maintain database pertaining to the information of Rake Links, Yard Infrastructure, Coach Master, Train Schedules etc. Data input at Zonal HQ level. Status: Implemented. iv) Coaching Maintenance Module: To capture depot activities related to coaching maintenance operations, Utility tool for managers looking after mechanical and electrical maintenance, Includes module for Material Management and Manpower data (gang strength per shifts etc), Data input at CDO level. Status : Under system study. i) Time-tabling Module: For simulating the suitable timings for running of all kinds of trains, simulating the best available path for planning a train keeping in view all variables, simulating optimum utilization of rake link, generating all time-tabling documents. Data input at Zonal HQ level. Status : Under system study. 2) ICMS-SYSTEM ARCHITECTURE User connects through browser interface (like Internet Explorer) Separate URL for PAMS ,COIS and DATA modules ( for ex: http/…/cois , http…./pam , http/…/data and so on) Users have Thin clients at location Back-end: RDBMS (Oracle based) 3) ICMS-DATA FEEDING i) Master Data: Common Master database for PAMs and COIS, includes Infrastructure data: (of more permanent nature like List of Stations, Platforms, washing lines) and Other Master Data: (of less permanent nature like Rake Link Data, Time Table data, Coach Master etc) ii) Running Data: Separate and independent running database for PAMS and COIS a) PAM: Feeding mostly at divisional level, Interchange owning division controls the data feeding for handing over or taking over, Zonal client does the responsibility fixing( deciding the trains “lost in punctuality”) Activities include: Originating terminating, interchange timings Detention Reports, Cause wise logging, Fixing Responsibility  b) COIS: Unlike PAM - no concept of data “feeding” in COIS. Instead working on the system at station/yard level leads to generation of required data (and memos for the operator).This works as input for MIS. All station/yard activities from arrival to departure of rake are captured: Yard stock entry Dispute Resolve Yard Position Sick Marking Rake formation Sickline PlacementSickline Operation Modify consist Shop Marking Movement Shop Placement Movement (Yard to yard) Remove fit available coaches Rake Examination Search Feedbacks Departure Reporting Send Feedbacks En route Attachments/Detachments Generate memo Arrival Reporting (iii) ICMS-MIS-REPORTS a) PAM : Reports for Management at Divisional Level, HQ level, Board level like: Railway Punctuality Performance for a date for a Division Movement of Trains (Division wise) in a Zone Punctuality percentage of Mail/Express Cause wise/Gauge Wise breakup of Lost Trains between dates Division wise analysis of Cause of Lost Trains on Date in a Zone Railway Punctuality performance for a date in a Zone Cause wise breakup of Trains lost in a period Summary of Monitored trains daily Run and Lost Section wise/Cause wise analysis for all trains on a date Zone wise/Cause wise analysis for all trains on a date, etc b) COIS: Reports for Management at Station Level, Divisional Level, HQ, RB level like : Yard Stock Position (Line position) Vehicle Guidance Zonal Stock Balance sheet (type wise details of Bare Requirement, allotment, running in service, ineffective etc) Coaches on way from/to shop Foreign Railway Coaches Ineffective Coaches Coach History Rake Link Information Zonal/Divisional Coaching Stock allotment/availability, etc.