Study on feasibility of SATCOM for railway communication
SRAIL-FNR-010-IND%20-%20FinalReport_v1.1_20170216
SRAIL-FNR-010-IND%20-%20FinalReport_v1.1_20170216
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Final Report<br />
<br />
<br />
Survey <strong>on</strong> operati<strong>on</strong>al communicati<strong>on</strong>s (study <strong>for</strong> the evoluti<strong>on</strong> <strong>of</strong> the <strong>railway</strong> communicati<strong>on</strong>s<br />
system), Ref: 37760-496v04 [RD-17]<br />
CCS TSI (Technical specificati<strong>on</strong>s <strong>for</strong> interoperability) – EU Decisi<strong>on</strong> 2012/88/EU<br />
CRT-NONT-3 The proposed <strong>SATCOM</strong> system <strong>for</strong> the future <strong>railway</strong> communicati<strong>on</strong>s architecture<br />
shall provide at least an acceptable level <strong>of</strong> cost efficiency, taking into account full lifecycle costs<br />
covering the full lifespan <strong>of</strong> the selected soluti<strong>on</strong>, and as l<strong>on</strong>g as technical and functi<strong>on</strong>al<br />
requirements allow <strong>for</strong> this opti<strong>on</strong>.<br />
RATIONALE<br />
Costs are a key decisi<strong>on</strong> driver <strong>for</strong> the selecti<strong>on</strong> <strong>of</strong> a new communicati<strong>on</strong> system. The future<br />
system shall have at least an ―Acceptable‖ cost efficiency. This is due to the fact that, despite<br />
costs not being the key driver <strong>for</strong> such a system, it should not have a worse costs per<strong>for</strong>mance<br />
than the existing GSM-R system.<br />
The cost-efficiency <strong>of</strong> the system has been defined according to several key influencing factors<br />
which have an impact <strong>on</strong> the CapEx and OpEx values.<br />
<br />
<br />
<br />
Use <strong>of</strong> Commercial Off the Shelf equipment: The use <strong>of</strong> commercial equipment allows <strong>for</strong> a<br />
reducti<strong>on</strong> <strong>of</strong> the costs <strong>of</strong> both procuring and operating equipment.<br />
Dedicated infrastructure/Potential <strong>for</strong> added value services. The potential <strong>for</strong> sharing<br />
infrastructure with other systems and/or providing additi<strong>on</strong>al services which could be<br />
m<strong>on</strong>etized.<br />
Durati<strong>on</strong> <strong>of</strong> deployment: The l<strong>on</strong>ger the deployment time the less time infrastructure is made<br />
use <strong>of</strong> and l<strong>on</strong>ger that legacy systems have to be kept in place.<br />
Cost-Efficiency<br />
High<br />
Acceptable<br />
Descripti<strong>on</strong><br />
A fully COTS based system allows <strong>for</strong> a reducti<strong>on</strong> in both CapEx<br />
and OpEx due to larger volumes, higher industrial competiti<strong>on</strong><br />
and resulting lower costs both <strong>for</strong> infrastructure and systems<br />
investments as well as <strong>for</strong> direct running costs.<br />
The use <strong>of</strong> infrastructure (spectrum, terminals) which is shared<br />
with other services and allows <strong>for</strong> direct revenue from the system.<br />
This includes commercial services such as passenger<br />
communicati<strong>on</strong>s.<br />
Deployment time <strong>of</strong> 5 years or less <strong>for</strong> average Member State.<br />
A modified <strong>of</strong>f the shelf system allows <strong>for</strong> leveraging from existing<br />
standards, but due to the COTS soluti<strong>on</strong> not fulfilling all necessary<br />
requirements, requires certain specific modificati<strong>on</strong>s.<br />
Some infrastructure can be leveraged to provide additi<strong>on</strong>al<br />
services outside <strong>of</strong> the <strong>on</strong>es required.<br />
Deployment time <strong>of</strong> approximately 10 years <strong>for</strong> average Member<br />
State.<br />
Doc.Nº: SRAIL-FNR-010-IND<br />
Edit./Rev.: 1/1<br />
Date: 16/02/2017<br />
Page 201 <strong>of</strong> 285