भारत सरकार

अंतररक्ष विभाग

अतंररक्ष उपयोग कें द्र(इसरो) आंबािाडी विस्तार पी.ओ.

अहमदाबाद – 380 015 (भारत) दरूभाषः +91-79-2691 3051/98

फैक्स नं. : +91-79-2691 5835/02/48

Government of India

Department of Space

SPACE APPLICATIONS CENTRE (ISRO)

Ambawadi Vistar P.O.

Ahmedabad – 380 015 (INDIA)

Telephone: +91-79 – 2691 3051/98

Fax No.: +91-79 – 2691 5835 / 02 /48

Email: publictender@sac.isro.gov.in

Date: 08/08/2017

Tender Notice No.: SAC/EOI-5/2017-18

For and on behalf of the President of India, Sr. Head, Purchase & Stores, Space Applications Centre, Ahmedabad invites Expression of Interest(EOI) for the following:

क्र. स.ं

Sr.No

निविदा ि.ं

EOI No.

सकं्षिप्त वििरण

Brief Description

नियत नतथि

(अपराह्ि 3 बजे तक)

Due on (Up to 3 pm)

1 SAC/EOI-5/H3/2017-18

Development and Operation of HUB base-band software system for SATCOM Network for Rail Monitoring (SNRM) under MSS Ground Application Project.

06/09/2017

Expression of Interest (Eol) for

Development and operation of HUB base-band software system

for SATCOM Network for Rail Monitoring (SNRM)

under MSS Ground Application Project

DCTD/SSTG/SNAA Space Applications Centre (SAC)

Indian Space Research Organization (ISRO) Ahmedabad- 380015

INDIA

Co nte nts

I. Introduction .................................................................. .. ............................................. 3 2. Condition for Intellectual Property .................................. ... ......................................... 4 3. Scope of\vol'k .................................................................... .......................................... 4 4. HUB-BB configuration block diagram ........................................................................ 5 5. System requirement at HUB-BB .......................... .. ...... .. ............................................. 6 6. Bandwidth estimation .................................................... .. .... ... ..................................... 7 7. Events to be generated during train journey .................. ........ .. .. .................................. 8 8. Deliverable ................................................................................................................. 12 9. Project review and Acceptance test plan ........................ .... ....................................... 12 10. Instructions to vendors .......................................................... .. .................................. 13

2

1. Introduction

SAC has taken the initiative to develop a satellite based networking system for monitoring of train movement and blow warning siren at unmanned railway crossing (UMLC) as well as inside locomotive through remote command when a train approaches to a UMLC. The network consists of a centralized HUB station and number of satellite terminals installed at UMLCs and locomotives. The system also monitors health status of all satellite terminals installed in the network. There are five beams covering total Indian region and each beam will be supported by one outbound TOM channel @ 64 kbps and multiple inbound carriers @ 2.4 Kbps. The access scheme for return link is TOMA. The network should support total 30,000 nos. satellite terminal (12000 locomotives and 18000 UMLCs). The software should able to support 50,000 terminals for future requirement.

~ .. r ll Dluntd roulilll

Figure 1: SATCOM network for Indian railway

The objective of this document is to locate suitable and experienced vendors, who would be interested and capable of carryout the system design, software development, deployment and operation of the system as described. Based on the information provided in this document, Vendors should come forward and

3

have technical discussions with SAC-ISRO to completely understand the requirements.

This document provides the preliminary information of the system requirements for SATCOM based railway service. The system as well as functional requirements identified in this document may undergo some changes due to the on-going refinement of the requirements and based on discussions with the vendors in order to make it most suitable for intended applications. The final Request for Proposal (RFP) will be prepared after thorough discussions with vendors, their responses and will be included in the final specifications. The vendors should provide budgetary estimates with different possible design options/configurations. Vendors should also include the option of continued operation and maintenance of these Hub baseband software system.

2. Condition for Intellectual Property

"The Intellectual property rights relating to the System network, design, development, processes, technical information, documents and other fabrication details shared/ published by SAC/ISRO shall remain the exclusive property of SAC/ISRO. Service Provider or Personnel deputed/deployed/ assigned job by the Service Provider/ manufacturer shall make no attempt to unlawfully reveal, misuse or encroach upon the intellectual or private datal information/ Computer systems at SAC/ISRO or provided by SAC/ ISRO to which they may have access to, as part of the work to be carried out ".

3. Scope of work

The Space Applications Centre invites interested vendors to submit response to Expression of Interest (EOI) for the Development and operation of HUB base­band software system for SATCOM Network for Rail Monitoring (SNRM) with budgetary information. The vendor is requested to submit following:

• Expression of interest for the execution of the work • Vendor details as per Section 10 • Compliance of understanding the Eol document • Detailed technical proposal including execution plan & manpower

deployment • Bill of material • Operation and maintenance cost - 1, 3, 5 years • Budgetary proposal with and without source code • Development Schedule

The development and operation of network service will involve (not limited to) the minimum activities as under:

4

• Understanding the requirements • System requirement analysis and finalization of requirement • Conduct design reviews • Development/procurement of HUB base-band software and required

components • System transportation to site • Installation and Commissioning • Documentation , User manual and Training • Continued operation and maintenance • Warranty services

• Resolution of software bugs during warranty period • Addition of new features/requirement arising during operation in warranty

period.

4. HUB·BB configuration block diagram

The following picture depicts central HUB configuration .

( - / / / \ ", , \ / Burst demodulator IY Modulator V '- - \

-- '-" . \

111111- - -- II II II II II II • / , \

I \ Switch/Router

I I 0

-- --= -GS M 3G/4G -It It a D Interface to -modem - terrestrial It It It D

networks

Rail Navigation Controller

Figure 2: HUB·BB system configuration

Burst demodulators will be used for receiving TDMA messages from Satellite terminals which contains current position of locomotives. The received position

5

information is then fed to Rail Navigation Controller (RNC) for online monitoring. The current position will be updated on GIS map and displayed on monitor. TOM modulator is used in forward data link. The RNC will generate commands to send to remote satellite terminals for blowing warning siren. It also monitors the health of all terminals at regular intervals and generates alarm in case of faulty terminal. The RNC also have external terrestrial network interface for data forwarding to Railway control Centre. There is an alternative receiving path for receiving positioning information through 3G/4G network. The RNC has to filter out the duplicate copy of messages (received from both the links - satellite & GSM 3G/4G) for further processing .

5. System requirement at HUB-BB

• The network should support multi-beam operation (up to 16 beam) and each beam will be served by one outbound TOM channel @ 64 Kbps and multiple return carriers @ 2.4 Kbps each

• There will be separate return carrier for signaling (used for slot allocation request by terminal) and set of reporting carriers

• Each reporting return link carries operate in TOMA mode. The TOMA slot length is 1 sec (the slot length may get reduced to 250 msec) and slot interval is programmable, depending on train speed

• Each satellite terminal is identified by a unique 10 (preferably 4 bytes) • TOMA slot will be assigned dynamically by RNC, when a train starts its

journey and is released after the train reaches to destination. The slot interval will also be controlled by RNC depending on request (from terminal) under various conditions like - loco hauling a train , only loco moving, loco is not moving etc.

• Location information, received from all locomotive satellite terminals, are fed to the Rail Navigation Controller (RNC) for display on GIS map, Archival and also forward to Railway control Centre and to different divisional control centres)

• RNC should take care of seamless operation when a train moves across beams

• The RNC should filter out the duplicate copy of messages (received from both the links - satellite & GSM 3G/4G) for further processing .

• Generate different events based on GPS/NAVIC location received from terminal. Event will be transmitted to railway control Centre . Event types are discussed in section 7

• RNC will generate commands to blow siren at un-manned railway crossing as well as at locomotive when a train approaches to an unmanned crossing .

• RNC will estimate the time to reach an UMLC and issues siren blow command - 2 min before (command issue timing should be programmable).

• Health monitoring of all SATCOM terminals installed at UMLC and locomotives. RNC will generate alarm in case a faulty terminal or a communication link is down. Alarm should be logged and generate SMS alert to predefined mobile

6

• Emergency/SoS message service to/from terminal • Interface to public terrestrial network for communication (SMS) • Remote terminal OS/ Firmware / Software upgradation • Data communication protocol should be designed as 100% reliable one • System shall operate in 24*7 operational mode. It should handle all

exception during field operation and adequate measure should be taken care in the RNC system for uninterrupted operation

• RCN shall provide facility to generate reports corresponding to reporting data, alarms, events etc. in PDFlWord/Excel/HTML format

6. Bandwidth estimation

Country is divided into five zones and each zone has equal number of locomotives, 2400 each. Assuming 50 percent of the trains (1200) need tracking (running concurrently) . Out of 1200 running train, 20 percent of the trains have designated speed more than 90 Kmph , 40 percent of them have speed between 60 Kmph to 90 Kmph and remaining 40 percent have speed less than 60 Kmph .

Case-A: Transmission slot = 1 sec and tracking everyone Km distance.

Catergory-1 (Super-Fast Trains @ 90 -120 Kmph): Reporting interval = - 30 sec. Catergory-2 (Fast Trains @ 60 - 90 Kmph): Repotting interval = - 40 sec. Catergory-3 ( Slow Trains @ 0 - 60 Kmph): Reporting interval = - 60 sec.

Each zone will need one forward link carrier @ 64 Kbps and 28 return link carrier @2.4 kbps to support the system operations .

Bandwidth Requirement per Zone : Fwd Link BW: 1 carrier of 64 Kbps i.e. 90 KHz BW Return Link BW: 28 carriers of 10 KHz each., i.e. 280 KHz

Case-B: Transmission slot = 1 sec. and tracking every 2 Km distance.

Keeping same activity factor, each zone will need one forward link carrier @ 64 Kbps and 14 return link carrier @2.4 to support the system operations.

Bandwidth Requirement per Zone: Fwd Link BW: 1 carrier of 64 Kbps i.e. 90 KHz BW Return Link BW: 14 carriers of 10 KHz each ., i.e. 140 KHz

Case-C: Transmission slot = 1 sec. and tracking every 4 Km distance.

Keeping same activity factor, each zone will need one forward link carrier @ 64 Kbps and 7 return link carrier @2.4 to support the system operations .

Bandwidth Requirement per Zone:

7

Fwd Link BW: 1 carrier of 64 Kbps i.e. 90 KHz BW Return Link BW: 7 carriers of 10 KHz each., i.e. 70 KHz

7. Events to be generated during train journey

RNC shall identify and transfer the timing details for the following events to divisional COA (Control Office Application) system and COA system shall further transfer these timings to other applications. The details of events to be captured are given below:

Approach Event at Station

• Identify the station approach reference points from all directions. Based on these points, a Station approach zone/circle will be demarcated. The approach zone/circle will be considered to capture station approach time.

• The approach time of a train at a station is the time when the locomotive fitted with GPS/NAVIC device is within the predefined approach zone/circle of the station and speed of the train is not zero.

• The station approach zone may be the area between the following reference points.

o Home Signals of the Station. o Last Stop Signals (LSS) of the station . o The last fouling marks of the station to an approaching train

irrespective of the line to which it belongs. o The starting points of the platforms. In case of multiple platform

line, the starting point of any line which is encountered first to an incoming train.

Arrival Event at station

• Identify the station arrival points from all the direction. The starter signals opposite to the direction of train movement may be taken as arrival points. Based on these points, station arrival zone/circle may be demarcated. The arrival zone/ circle will be referred to capture the arrival time of a train at a station.

• The arrival time of a train at particular station is the time when the locomotive fitted with GPS/NAVIC device is within the arrival circle/zone of the station and speed of the train is zero.

In the case station is covered then the approach time may be used to deduce the approximate arrival time for scheduled train with scheduled hall. The added time value may be calculated on basis of permitted speed and distance . between station approach point and center point of station arrival zone/circle.

8

Departure Event at station

• The departure time of a train from a station is the time when the locomotive fitted with GPS/NAVIC, after halting in arrival zone/circle, moves out of the predefined arrival zone/circle of a station and speed of train is greater than zero.

• However, the departure time of a train will be updated only after the train has crossed the station exit zone/circle. The area between following landmarks may be considered as station exit zone/circle .

o The Advance starter signals of a station or o The top points of the station. The top point as reference point may

be required in case of a station where the vehicles are backed to trip shed or coaching yard etc.

Based on the station exit points, a station exit zone/circle will be demarcated. As soon as the locomotives fitted with GPS/NAVIC moves out of station exit zone, the departure time captured earlier will be updated.

• In case the locomotive stops after moving out of station arrival zone stops before moving out of station exit zone, then the last reported departure time immediately before the time locomotive moves out of station exit zone/circle will be taken as departure time. This condition is required to handle multiple departure time.

Through Event at Station

The train which passes through a station without halting is termed as through train. A train is run through if a locomotive fitted with GPS/NAVIC moves out of station arrival zone/circle without speed touching zero. The time when locomotive fitted with GPS/NAVIC moves out of the station arrival zone/circle will be taken as run through time of the train. However, the run through time of a train will be posted only when the locomotive fitted with GPS/NAVIC moves out of station exit zone/circle.

Halt in mid-Block Section

The time of halt of a train in the mid of block section instead of station is called as halt in mid-block section. The halt time in mid-block section of a train is the time when locomotive moves out of a station's exit zone/circle and does not reach the next station arrival zone/circle and speed becomes zero.

9

Functional Representation

, , , , , , ,

, , , ,

, ,

, , , ,

, , , ,

, ,

, , , , , , , , , , r-~E~~A~~P ________ ~~ __________ ~Q~B~~: __ -1N , , , , , , , , , , , , , , , , , ,

, , , ,

Direction ofTrairj" __ ~

PQ C CN EC AC

= Platform line ----

= Center Point of Platform line = Departure circle radius = Approach circle radius = Arrival circle radius

---

10

,

, , ,

,

, , , ,

, , , , , , ,

, , , , , ,

, , ,

, , , ,

-------------------

" "

, , , , , . , , . .

• . • • • •

• • • • •

N~ __ r-~B~Qr-______ ~~ __________ ~P~A~~E~~:

• • • • . , , , ",

" ,

PQ = Platform line

---

C Center Point of Platform line CN = Departure circle radius EC = Approach circle radius AC = Arrival circle radius

II

, , , ,

, , , ,

, , ,

• , , , , , , , , , , , ,

Direction of Train ---

8. Deliverable

1. Rail Navigation Controller on Server machine in HA configuration. 2. 52" LED display monitor for GUI and GIS map display 3. L2/L3 Ethernet switch 4. GSM 3G/4G modem 5. SMS gateway 6. External Storage solutions 7. Data archival solution 8. Documents prepared in all steps of development process

a. System (both software and hardware) requirement specification . b. Component list, all cable details c. Detailed software design d. Test plan and procedure

9. Source code of application software used in system development. 10. Performance evaluation reports of complete integrated system. 11. Network Security Solution in HA mode 12. User manual, cables, power adaptor and other required accessories. 13.0nsite installation and training at SAC. Vendor should provide full

technical support during field trial 14. Operation and maintenance of network for 1 + 5 years. 1st year will be

under warranty period and additional 5 years on payment basis)

9. Project review and Acceptance test plan

The project management will periodically review the progress of the activity. The typical reviews will be as under:

• Preliminary Design Review • Detailed/Critical Design Review • Test and acceptance plan review • Final acceptance review

The SNRM HUB-BB system will be tested in satellite loop at SAC. All other subsystems like - burst demodulator, TOM modulator, RF components and satellite terminal will be arranged by SAC during acceptance testing . Vendor may be required to develop simulator for testing of base-band software in their lab during development phase. Performance of system will be evaluated in full loaded conditions in term of data reliability, proper alarm generation, handling abnormal condition etc. A detailed ATP will be worked out jointly in consultation with SAC team after placement of firm PO.

12

10. Instructions to vendors

The prospective vendors will be judged based on the following preferred criteria:

• Demonstrable proof of competence in undertaking this kind of communication network design & development, Integration, testing and commissioning , and service maintenance.

• Execution of work of similar nature for organization like ISRO, DRDO, DAE etc. or other Gov!. of India/PSU, R&D Organizations.

• In-house Facilities and Infra-structure, tie ups with relevant / specialized companies, overall manpower strength and expertise and prior experience of executing orders of similar nature using High-Reliability processes, components etc.

• Undertaking regarding Non-Disclosure Agreement (NDA), Confidentiality Agreement, Intellectual Property Rights (IPR) and Arbitration.

To meet the above-mentioned requirements and mode of working envisaged, the Vendor shall meet the following minimum requirements in order to technically qualify:

• Vendor must be a reputed software development company registered with government agencies and in existence for a minimum of 3 years on the date of issue of this tender, with necessary technical facilities and experience. It should not be a consortium of firms / companies or a placement agency.

• Vendor should also fulfil the following minimum requirements and attach relevant documents if ordered , P.O. copies, service satisfaction certificates , etc. with the tender document to support these requirements:

1. A Minimum annual turnover of Rs. 2 Crores per Year (Income-Tax returns , Audited Financial statements of last three years with PAN and such other relevant documents required as proof, to be enclosed along with Final Proposal.)

2. Experience in the field of "Tech. Services/Products" for last Two (02) years.

3. Vendor's Company/firm should not have been banned or black-listed by any Government Department / Central Government Unit / Public Sector UniU Financial Institutions / Court and submit a declaration in this regard.

4. SAC reserves the right to accept or reject any offer, fully or partly without assigning any reasons, if the rates quoted are NOT RATIONAL and UNVIABLE.

13

5. SAC also reserves the right to spilt and enter into parallel Contracts with

more than one Parties for different items.

6. SAC/ISRO designers will be continuously interacting with the vendor's

teams during the total development period and will provide all the

necessary inputs and assistance required for the satisfactory completion

of the assigned developmental contract.

The prospective vendors should submit full details of their technical competence for undertaking project of this nature, in the technical part of their proposal document. A preferable format (not limited to) is provided in the following table.

51# Description Details 1. Year Of Establishment 2. Vendor's Area Of Core Competence I

Activities 3. Infrastructure Details (Area, Facilities Etc.) 4. Annual Turnover in the last three financial

years 5. Value of major orders currently being

executed with client's name, Address, etc. 6. Number of Technical Manpower with breakup

of Engineers 7. List of in house facilities (Software license

details) 8. Quality certification (ISO-9000, CMMI Etc.)

and Internal QC procedures followed 9. Details Of Customer Base In India 10. Detail of similar system development in past 11 . Development & delivery schedule 12. Willingness to provide Non-Disclosure

Agreement (NDA) , Confidentiality Agreement , Intellectual Property Rights (IPR) and Arbitration

14

\

NOTICE OF INTENT TO PRE-BID

Eol Title: Development HUB base-band software system for SATCOM Network for Rail Monitoring (SNRM)

Vendors must compete and return this form to SAC/ISRO. The undersigned person should read all Eol instructions and requirements and will submit a proposal in compliance with those instructions.

Company Name:

Company Name: Name: Title : Address : Telephone: Fax :

Email : Website:

Signature: Date:

Contact person for any technical clarification

Mr Sudhir Agarwal, Head DCTD: Bldg.#24, Room #92, Space Applications Centre (SAC) , ISRO, Ahmedabad-380015 Telephone: 26912492/50 Email: sUdhir@sac.isro.gov.in

15