s01- installation requirement specifications its standerd-del...auto tests should be launched...

S01- Installation Requirement

Specifications Release S01-2015V1.0

This document defines the detailed specifications of ITxPT installation requirements.

S01-2015V1 Installation Requirements specifications 2/27

Content

1 Architecture requirements ................................................................................................................ 3 2 Minimum set of regulative requirements .......................................................................................... 4 3 Operational requirements to fulfil for compliancy............................................................................. 5

3.1 Delivery rules ............................................................................................................................ 5 3.2 Installation rules ........................................................................................................................ 5 3.3 End of line ................................................................................................................................. 5 3.4 Maintenance .............................................................................................................................. 5 3.5 Tools and validation .................................................................................................................. 6

4 Vehicle interface requirements ........................................................................................................ 7 4.1 Power Supply Interface ............................................................................................................. 7

4.1.1 Principle ............................................................................................................................... 7 4.1.2 ITS consumption modes ...................................................................................................... 7

4.1.2.1 ECO0 mode ................................................................................................................. 7 4.1.2.2 Low consumption mode with peripherals in low consumption mode (ECO1) ............. 7 4.1.2.3 Low consumption mode with switched off peripherals (ECO2) ................................... 7 4.1.2.4 SLEEP Mode ............................................................................................................... 7 4.1.2.5 Synthesis of consumption for each mode and each module ....................................... 7

4.1.3 ITS consumption modes compare to vehicle use phases ................................................... 8 4.1.4 ITxPT requirements on vehicle interface for Power Supply .............................................. 10 4.1.5 Power over Ethernet .......................................................................................................... 12

4.2 BUS FMS ................................................................................................................................ 12 4.3 Other Interfaces ...................................................................................................................... 12

4.3.1 Audio management............................................................................................................ 12 4.3.2 Wireless communication interface ..................................................................................... 13 4.3.3 Auxiliary interface .............................................................................................................. 14

5 Space for the installation of ITxPT ITS modules in the vehicle ..................................................... 15 5.1 ITxPT ITS enclosure definition ................................................................................................ 15 5.2 Requirements for module fixation inside enclosures .............................................................. 15 5.3 Requirements for connectors at enclosure interface .............................................................. 16

5.3.1 Main enclosure interface ................................................................................................... 16 5.3.2 Optional enclosure interface .............................................................................................. 17 5.3.3 Other interfaces ................................................................................................................. 17

6 Ethernet network ............................................................................................................................ 18 6.1 Ethernet Backbone .................................................................................................................. 18 6.2 Ethernet Cables ...................................................................................................................... 20 6.3 Ethernet Connectors ............................................................................................................... 21

7 Harness installation rules ............................................................................................................... 23 7.1 Definitions ............................................................................................................................... 23 7.2 Basic requirements ................................................................................................................. 23 7.3 Added requirements ................................................................................................................ 23

8 Retrofit of the vehicles ................................................................................................................... 24 9 Back-Office installation requirements ............................................................................................ 25

9.1 Description .............................................................................................................................. 25 9.2 Wireless communication compatible with IP ........................................................................... 25 9.3 Hierarchical structure .............................................................................................................. 25

10 Requirements & recommendations ............................................................................................... 27


1 Architecture requirements

Each ITxPT compliant vehicle MUST be equipped with onboard ITS, including sensors, actuators,

Electronic Control Unit (ECU) and wirings.

A major part of these ITS will be ITxPT compliant as described in S02- Onboard Architecture

Specifications.

The minimum set of support functions in order to be ITxPT compliant are:

FMStoIP bridge

IP backbone

Vehicle Gateway

Multi-Application Driver Terminal (MADT)

Maintenance Ethernet plug

Power management

Geographical localization

We then have other functions defined as services, such as:

Dynamic Passenger Information

Advanced Vehicle Monitoring System

Remote Diagnostic

Voice over IP

Passenger counting

Ticketing system

Traffic light control

Video surveillance

...

http://wiki.itxpt.org/index.php?title=S02-_Onboard_Architecture_Specifications



2 Minimum set of regulative requirements

ITS systems are installed inside vehicles and, as any other electronic units, shall thus respect rules.

Because many of these rules deal with passenger’s safety, they comply with standard regulations

(automotive regulations) issued from ISO, EC or UNECE working groups.

You will find in the next table an informative list, not exhaustive (in particular, no local regulation is

given), of common topics managed by regulations, the corresponding regulations and ITxPT position

in front of each one.

ITxPT requires the compliancy with up-to-date Bus-FMS standard (http://bus-fms-

standard.com/Bus/index.htm), which specifies data interface between the vehicle and the ITS network.

In a more applicative point of view, ITxPT recommends that ITS services defined in ITxPT scope also

comply with up-to-date 2010/40/EU directive on the framework for the deployment of Intelligent

Transport Systems in the field of road transport and for interfaces with other modes of transport.

(*)in case of a component with external part

Category Procedure Mandatory

(minimum

acceptable for

ITxPT)

ITxPT Recommendation

Electrical ISO7637-2

ISO16750-2

Level III

Level E (10V/32V

for supply voltage)

Climatic ISO16750-4

IEC60068-2

Industrial Range Levels F-C or H-G* Parts 1 Ae

& 2 Be (T°C), 14 (T°C cycles),

78 (Damp Heat)

Mechanical ISO16750-3

IEC60068-2

Level D Level S

Parts 27 (shocks), 64

(vibration), 32 (fall)

Protection degree

against foreign objects,

water and access

ISO20653 IP40 IP5K2 or IP5K4K*

Chemical ISO16750-5 None Level B

Electrostatic Discharge ISO10605 None Level III

Electro Magnetic

Compatibility

2009/19/EC(72/245/E/C)

ECE R10 revision 3

e-marking or

E-marking

Bulk current injection up to 200

mA and field strength up to 200

V/m

Fire ECE R118

UL94

E-marking or

Level V0

Radio electrical

interferences

CISPR25

2010/368/EC

None

None

6.4, Level 4

x

Table 1 - Regulations synthesis

ITxPT recommends the compliance of each ITS installed to automotive rules but, in any case, ITxPT

recommendations do not replace any regulations or any Bus manufacturers, Operators or PTA

requirements.

http://bus-fms-standard.com/Bus/index.htm



3 Operational requirements to fulfil for compliancy

Most of IT system and peripherals inside vehicle are commonly mounted in vehicle production plant.

They follow then a standard manufacturing process, including End Of Line control.

ITxPT recommendations are based on manufacturer’s generic manufacturing rules and today’s know-

how about ITS installation:

3.1 Delivery rules

Modules should be delivered with dedicated certification, as requested in regulation’s chapter.

Modules must be delivered with the minimum dataset which permits installation testing in End

of Line.

3.2 Installation rules

Modules must be quickly assembled / disassembled, in conformity with the §5.3 ITS

Enclosures definition below.

Cables / Wires have to be installed in conformity with the §7 Harness installation rules below

(in particular, avoid proximity between Ethernet cables and power cables)

Mechanical coding (especially for connectors) is preferable, at least with colour.

3.3 End of line

Avoid End of Line (EOL) configuration for Private (internal configuration under supplier

responsibility) and Customer datasets (configuration under customer responsibility). Only

configuration requested by manufacturer and under its own responsibility should be carried

out in plant. The component should be ideally finally configured by the customer, through

wireless connection when SIM card will be inserted.

SIM card SHOULD not be not supplied in plant and not installed by the manufacturer

At the End of the Line, a so-called EOL check will be carried out. The aim for the manufacturer

is to check with a minimum of additional components that the installation, which he is

responsible for, is operational. For instance, in the plant the bus manufacturer must have the

ability to check the operational status of the modules through a dedicated tool which is

connected on a specific port on the IP backbone (available also for maintenance purposes).

This connection permits to check the full installation. Apart from this, an embedded diagnosis

is also possible.

3.4 Maintenance

Even if there are not safety components, ITS system and peripherals inside vehicle must have

great availability. Auto tests should be launched regularly (at least at each vehicle start) or on

request (in this case, more complete test can be carried out) in order to be able to maintain

quickly a module which does not work properly. Results must be published on the MADT

requested by remote maintenance service, or sent to back office.

Then, components (connectors and mounting’s screw) should be quickly reachable by either

technicians or drivers if necessary. Standard tools and connectors should be used, in

conformity with dedicated chapter inside this document.

A standard protocol on IP is used in order to help to diagnose the problems which ITS network

and components encounter. By remote communication or with a physical connection to IP


network, an operator can access to ITS defaults and associated contexts. It can also check

each system’s availability through specific commands. ITxPT shall define minimum

maintenance functionalities to be fulfil ed. Today, ITxPT only recommends getting specific

software tool for free and on a standard PC from supplier so that diagnosis can be carried out

(display of self-tests results).

3.5 Tools and validation

To validate the ITxPT network compliancy of the ITS, equipment MUST be able to use the §4.1-

Module Inventory Service described in the S01- Onboard Architecture Specifications.

The response message of the module inventory service MUST contain:

Type of module

Model

Manufacturer

Serial number

Software version

Hardware version

Current status (ok/nok/errorcode…)

IPv4/IPv6/MAC/ <other> address

DHCP enabled

IP subnet/gateway if static configure

Connected sub-module(s), (Yes/No, details in xml file)

Module specific attributes ‘screen on right side of driver with 5 buttons and 480x800

resolution, 16 colors, no touch screen’.

64 digit for OEM part number

http://wiki.itxpt.org/index.php?title=S01-_Onboard_Architecture_Specifications#Module_Inventory_Service



4 Vehicle interface requirements

4.1 Power Supply Interface

4.1.1 Principle

ITS are power-supplied by vehicle, through the battery which supplies in particular all the electronic

architecture inside vehicle. No additional dedicated battery is required by ITxPT. But special care must

be taken in order to spare battery life.

When the vehicle is in operation (monitoring engine speed for instance for thermal engine vehicle), the

battery is in charge and ITS can consume normal power needs.

But, when the vehicle is not in operation and the battery remains the only power source inside vehicle,

the consumption has to be limited to the strict necessary.

Thus, this chapter is dedicated to the specification of an optimal management of ITS power

consumption, respectively to the vehicle use phases.

ITxPT defined 4 ITS power consumption modes (ECO0, ECO1, ECO2 and SLEEP). Each

consumption mode is related to one vehicle phase.

4.1.2 ITS consumption modes

With reference to ITS power consumption modes are identified:

4.1.2.1 ECO0 mode

Full telematics functions are available in ITS network, without restriction.

4.1.2.2 Low consumption mode with peripherals in low consumption mode (ECO1)

Full telematics functions are available on ITS network but with peripherals in low consumption modes

such as economical displays and destination signs.

4.1.2.3 Low consumption mode with switched off peripherals (ECO2)

Some functions are available on ITS network but with no display. These functions deal with data

backup before switching off, data and software exchanges with back-office if required.

4.1.2.4 SLEEP Mode

No function is available on Telematics system. If it is connected to permanent power supply inside

vehicle, maximum consumption shall be below 2mA. If this mode cannot be managed by ITS, it has to

be connected to 24V after Main Switch only!

4.1.2.5 Synthesis of consumption for each mode and each module

Maximum power allowed for each know ITS system in each mode is:


Module Maximum allowed consumed power (W@24V)

ECO0 ECO1 ECO2 SLEEP

Vehicle Gateway 8W 8W 8W 0.048W

Ethernet Switch 5W 5W 5W 0.048W

FMStoIP Gateway 5W 5W 0W 0W

MADT 30W 30W 15W 0.048W

Localization 5W 5W 0W 0W

Onboard AVMS (display not included) 30W 30W 15W 0.048W

Onboard DPI (display not included) 30W 30W 15W 0.048W

Remote Maintenance 30W 30W 15W 0.048W

Passenger counting 30W 30W 0W 0W

Ticketing system 30W(70W peak) 30W(70W peak) 0.048W 0.048W

Private voice radio 30W 30W 0W 0W

RFID reader 5W 5W 0W 0W

External displays 300W 150W 0W 0W

Internal display (TFT, LCD screens, Sign) 30W 15W 0W 0W

Other module 30W 15W 15W 0.048W

Table 2 - Modules consumption vs ITS mode

Each ITS must fulfil requirement as described in this table and following one.

4.1.3 ITS consumption modes compare to vehicle use phases

ITS modes are defined in the following:

n° Vehicle use phases

Power supply ITS

Recommendation BAT

Main

Switch

ON

Engine On

(full power

available)

mode

1 Vehicle stopped before service 24V 0 0 SLEEP

2 Vehicle switched on by the driver 24V 24V 0 ECO1 Maximum 2 hours a

day

3 Vehicle switched on by the driver

AFTER 30 mn 24V 24V 0 ECO2

This abnormal mode

has to be avoided by

the driver.

4 Vehicle running (Speed >0) with

engine on 24V 24V 1 ECO0 Not limited

5

Vehicle stopped (Speed = 0) with

engine on

EX: The vehicle is stopped at a

bus stop or at a traffic light

24V 24V 1 ECO0 Not limited

6

Vehicle stopped with Engine OFF

with Main Switch ON DURING 30

mn after Engine OFF (ITS

network)

EX: The vehicle is stopped

24V 24V 0 ECO1 Maximum 2 hours a

day


n° Vehicle use phases

Power supply ITS

Recommendation BAT

Main

Switch

ON

Engine On

(full power

available)

mode

waiting passengers at the

terminus of the line

7

Vehicle stopped with Engine OFF

with Main Switch ON AFTER 30

mn

EX: The vehicle is stopped

waiting passengers at the

terminus of the line.|24V

24V 24V 0 ECO2

This abnormal mode

has to be avoided by

the driver.

8 Vehicle

stopped with

Engine OFF

with Main

Switch OFF

EX: Stop for

the night or

between two

trips in the

depot

The vehicle is in

the sleeping

phase EX: <

10mn after Main

Switch OFF

24V 0 0 ECO2 minimum*

9

The vehicle is

waked-up by the

ITS EX: During

the night in order

to upload data


10

The vehicle is out

of the sleeping

and wake- up

phases


11 Vehicle stopped with manual

battery switch OFF 0 0 0

No

consumption Not limited

*minimum: this time

MUST be agreed by

the operator or PTA

and bus manufacturer

Table 3 - ITS mode vs Vehicle Use Phase


Besides, in case of vehicle warning about very low battery (low battery pin, see fig2), following

degraded mode has to be managed by ITS, especially through IP gateway:

If vehicle is not in operation, only SLEEP mode is allowed

If vehicle is in operation, ITS transient to SLEEP mode is required as soon as possible

For future evolution, each ITS may indicate at registration its expected consumption for each mode.

4.1.4 ITxPT requirements on vehicle interface for Power Supply

On the basis of consumption table, vehicle power interface in compliant S01- Onboard Architecture

Specifications is designed as followed:

One common GROUND linked to vehicle chassis

One permanent power line (24V) linked to the battery after Manual Switch

One non-permanent power line (24V) linked to the battery after Main Switch (also called Key

or Ignition)

One logical signal which indicates if full power is available on vehicle or not (engine ON for

instance for thermal engine vehicle)

One unique additional logical line is also required, which permits vehicle to warn ITS system (via IP

gateway) that the battery energy is considered to be low and that ITS systems must fall into SLEEP

mode in 2 minutes.

First three lines are supplied through an electrical interface inside each enclosure for each component.

MCP type connector with 6 pins, TYCO reference: 1-965641-1 Blue Code A, is recommended with the

following pinning:




1-965641-1 Blue Code A

PIN Signal

1 24V after Manual Switch

2 GROUND

3 24V after Main Switch

4 NC

5 NC

6 NC

Table 4 - Power Supply connector's pinning

Figure 1 - Power supply layout example


4.1.5 Power over Ethernet

Regarding the Power over Ethernet, pointing the fact that this technologies is growing, ITxPT

considers to let the possibility to install modules that uses Power over Ethernet. The supplier must

refer in that case to the IEEE802.3af (https://standards.ieee.org/findstds/standard/802.3af-2003.html)

or IEEE802.3at (https://standards.ieee.org/findstds/standard/802.3at-2009.html) standards.

4.2 BUS FMS

This interface brings to ITS vehicle data under BUS FMS standard (http://bus-fms-

standard.com/Bus/index.htm). Concerning installation, connector is imposed by the Bus-FMS standard

(http://bus-fms-standard.com/Bus/index.htm).

Vehicle side Bus-FMS CAN network contains one 120 Ohms termination resistor. ITS part (FMSoIP)

shall put the other 120 Ohms termination resistor.

Most of ITxPT requirements are based on BUS FMS 2 interface (http://bus-fms-standard.com/). This

standard is evolving; ITxPT will contribute to the next Bus-FMS standard revisions.

4.3 Other Interfaces

4.3.1 Audio management

ITxPT recommends to let manufacturer supply and install inside vehicle (in plant) audio amplification /

dispatching system, loudspeaker, radio and driver microphone (including ambient noise management

if requested).

Amplifier inside vehicle requires the following input lines, which have to be given accordingly by audio

consumers, such as DPI:

Stereo low level interface.

o One stereo input (3 wires) :

Input sensitivity: 100mV - 1V

Input impedance (1kHz): > 10kΩ

Frequency range: 20Hz – 20kHz (-2dB to +1dB)

Type: Single ended, unbalanced

Three HW logical control wires.

o 1’st (prio 1) ==> Passengers area

o 2’nd (prio 2) ==> Drivers area

o 3’rd (prio 3) ==> External area (external speakers at doors)

Inputs are filtered, behind load resistors, with an RC time constant (Tconst).

o Tconst 2-5 ms

o Vin Low < 2,5V == activate the specific speakers area

o Vin High > 5,3V == deactivate ( if a wire is disconnected the load resistor at the

amplifier will make the input to Vin High)

ITxPT recommends specific connector dedicated to this interface. Multiple connector such as MCP

type from Tyco with 9 pins, TYCO reference: 1-967626-1 Yellow Code A, pins is recommended with

the following pinning :

https://standards.ieee.org/findstds/standard/802.3af-2003.html

https://standards.ieee.org/findstds/standard/802.3at-2009.html



http://bus-fms-standard.com/



1-967626-1 Yellow Code A

PIN Signal

1 LEFT CHANNEL

2 COMMON GROUND

3 RIGHT CHANNEL

4 Not Connected

5 Not Connected

6 Not Connected

7 1'dt (prio 1)

8 2'nd (prio 2)

9 3'rd (prio 3)

Table 5 - Audio connector's pinning

Male connector is predisposed inside vehicle, at the input of the §5.3- Main enclosure below.

4.3.2 Wireless communication interface

All antennas (if more than one) shall be installed on the roof of the vehicle, above driver’s seat and min

80cm away from each other.

Apart from RF communication means (such as Tetra) which are considered as out of ITxPT scope,

there should be ideally one unique antenna which manages Long Range communication

(GSM/GPRS/UMTS nowadays), Short Range Communication (Wi-Fi nowadays), and Satellite

localization (GPS, Galileo).

Cables from antenna are connected directly to dedicated component if available with Fakra

connectors. If components are not available, Fakra connectors are predisposed at cable end with a

reasonable cable length reserve (50cm) from the input of the enclosure, in order to ensure connectivity

with IP Gateway.

Fakra Code I /

Female / Beige

Fakra Code D /

Female / Bordeaux

Fakra Code C /

Female / Blue


Following codes are required :

WLAN Antenna Fakra Code I / Female / Beige

Main GSM Antenna Fakra Code D / Female / Bordeaux

GPS Antenna Fakra Code C / Female / Blue

Table 6 - Wireless communications and GPS Fakra connectors' color code

4.3.3 Auxiliary interface

This connector has been chosen to allow interface with not yet ITxPT compliant modules.

This connector has a large scale use with the possibility to insert up to 18 PINs. It is cheap, easy to

plug, reliable and compliant with bus manufacturer rules. The logical signal dealing with full power

available (Monitoring Engine speed) is available on IP network.

The logical signal dealing with low battery is supplied by wiring in a dedicated MCP type connector 18

pins (PIN 1) , TYCO reference: 1-967629-1 Grey Code A, which will accept further interface evolution

between vehicle end ITS.

1-967629-1 Grey Code A

PIN Signal

1 Low battery

2 Odometer (analogue pulse)

3 Doors 1 open (analogue signal)




7 NC

8 NC

9 NC

10 NC

11 NC

12 NC

13 NC

14 NC

15 NC

16 NC

17 NC

18 NC

Table 7 - Auxiliary signals possible implementation example


5 Space for the installation of ITxPT ITS modules in the

vehicle

5.1 ITxPT ITS enclosure definition

Figure 2 - Main enclosure and Optional enclosure

ITxPT requires that Bus manufacturers dedicate free space inside vehicle in order to be able to mount

ITS modules by optimization of the space. This free space is split into the following units:

A main enclosure inside vehicle, easily reachable by operator for maintenance, but not by

passenger, with at least 50 dm3 volume, will contain main and/or big modules (AVMS and/or

IP gateway, IP switch, FMSoIP gateway for instance).

Several optional enclosures will contain the other ITxPT ITS modules. Their number depends

on customer order. Their volume, location will depend on vehicle type (it can be close to the

doors, in the middle or rear of the vehicle for instance). A minimum volume (mono-module

enclosure) for each optional enclosure is 6 dm3 (i.e. 130x180x250mm for instance). The

modules can get power inside enclosure and connect to IP network inside enclosure or close

to. As main enclosure, these optional enclosures must be inside vehicle and reachable.

Free space is predisposed inside the driver cab area for the minimum ITxPT MADT

requirement (7”/7.5”).

o Minimum allowed volume inside (fitted): Length 170mm/ height 110mm /depth

110mm.

o with minimum outside front face free: height 150mm length 200mm,

o with 1,2 Kg min charge for load fixation points

For the maximum outside front face, the suppliers must contact the bus manufacturer to have its

requirements.

Other modules, especially displays, are not inside the enclosures. There is no specific ITxPT

restriction on them.

5.2 Requirements for module fixation inside enclosures

Fixation holes are predisposed by manufacturer in vehicle body.

Additional mechanical interface will have to be customized for each component inside enclosures to

fasten ITS (This can be plates, grids, 19” racks).

ITxPT requires the accessibility of fastening points, and the need of a tool to lock fixation screws.


Each support shall support at least 0.5Kg per liter.

A free grid can be predisposed to fill in the box in order to accept other components for future retrofit, if

requested by customer.

5.3 Requirements for connectors at enclosure interface

Connection requirements are defined in EN13149 Part 8 (for Ethernet) – see §3.1.1.1 in Wiki ITxPT

related Standards. These requirements lead to the following requirements at enclosures’ interface:

5.3.1 Main enclosure interface

Figure 3- Main Enclosure's electrical interface

The number of 6 pin connectors for Power-Supply depends on global enclosure volume. ITxPT

requests 1 connector for each 10L inside enclosure.

Each connector inside enclosure is predisposed by vehicle manufacturer. One or several free “holes”

are also planned, in order to be able to add new 6 pins connector for future customization.

Connectors predisposed inside vehicle are Male type. Maximum section used is 2,5 mm² for each

wire.

http://wiki.itxpt.org/index.php?title=ITxPT_Related_Standards#EN13149


5.3.2 Optional enclosure interface

Figure 4 - Optional enclosures’ electrical interface

The number of 6 pin connectors for Power-Supply depends on global enclosure volume. ITxPT

requests 1 connector for each 10L inside enclosure, with a minimum of 1.

Each connector inside enclosure is predisposed by vehicle manufacturer. One or several free “holes”

are also planned, in order to be able to add new 6 pins connector for future customization.

Connectors predisposed inside vehicle are Male type. Maximum section used is 2,5 mm².

5.3.3 Other interfaces

Modules which are not mounted inside the enclosures, (MADT, Displays, Signs, Ticketing

Machines…) are linked to power-supply and to Ethernet network with preferentially the same kind of

connectors as for enclosures (6 Pins MCP type for Power-Supply and M12 type for Ethernet network).

Maximum section used should be 2,5 mm².


6 Ethernet network

Each enclosure, as defined in §5- Space for the installation of ITxPT ITS modules in the vehicle

above, has to be linked to an IP network. Ideally, a switch is then predisposed in each enclosure (as

power-supply repartition) and all switches are connected to each other with Ethernet cable

predisposed on vehicle.

6.1 Ethernet Backbone

The Backbone installed in the buses is dedicated to embedded purpose and has to respect the ITxPT

regulations defined in §2- Minimum set of regulative requirements.

The backbone installed in the ITxPT enclosure of the vehicle described in §5- Space for the installation

of ITxPT ITS modules in the vehicle could be able to manage PoE+ (Power over Ethernet Plus,

respecting the IEEE 802.3af standard -https://standards.ieee.org/findstds/standard/802.3af-2003.html-

as a minimum).

This backbone MUST support a 24V supply in order to fulfil the requirements for IT power supply

described in §4.1 Power Supply Interface.

The backbone MUST be able to receive M12 4 pins connectors D-coded at minimum for 10/100Base-

TX. There is also a possibility to use M12 8 pins connectors X-coded in order to use 1000Base-TX

communications.

The backbone MUST forecast a minimum of 2 free M12 plugs available. One of these plugs will be

dedicated to maintenance purposes and will have to be identified as so.

The on-board network IT architecture links all the enclosures (main and optional) together. To do so,

the switches could be placed IN or OUT of the enclosures. But in either cases, the switches must be

accessible for maintenance purposes.

Examples of network architectures:

Figure 5 - Network topology in line

http://wiki.itxpt.org/index.php?title=ITxPT_Installation_Requirements#Space_for_the_installation

http://wiki.itxpt.org/index.php?title=ITxPT_Installation_Requirements#Space_for_the_installation

https://standards.ieee.org/findstds/standard/802.3af-2003.html


Figure 6 - Network topology in line with external switches

Figure 7 - Network topology in star


Figure 8 - Network topology in star with external switches

6.2 Ethernet Cables

The Ethernet cable that will be installed in the buses should be minimum Cat 5e and over in order to

manage 10/100/1000Base-TX connections at 100MHz. This type of cable also allows PoE

applications.

Category 5e cable - Cat 5e

Cat5a Ethernet cables

Pins T568A Color T568B Color

1 white/green stripe white/orange stripe

2 green solid orange solid

3 white/orange stripe white/green stripe

4 blue solid blue solid

5 white/blue stripe white/blue stripe

6 orange solid green solid

7 white/brown stripe white/brown stripe

8 brown solid brown solid


Table 8 - Cat5e Ethernet cables design

6.3 Ethernet Connectors

EN13149 Part 8 allows RJ45 connectors in order to support the migration to the full ITxPT

architecture.

EN13149 Part 8 recommends M12 Ethernet connectors with 4 pins D-coded for 10/100Base-TX, and

M12 Ethernet connectors with 8 pins X-coded for 1000Base-TX.

M12 Ethernet connector with 4 pins D-coded

For 10/100Base-TX: TIA/EIA-568-A

Pins Cable T568A Color Cable T568B Color Data PoE(mode A)

1 white/green stripe white/orange stripe Rx + DC+

2 green solid orange solid Rx - DC+

3 white/orange stripe white/green stripe Tx + DC-

4 blue solid blue solid unused unused

5 white/blue stripe white/blue stripe unused unused

6 orange solid green solid Tx - DC-

7 white/brown stripe white/brown stripe unused unused

8 brown solid brown solid unused unused

Table 9 - 10/100Base-TX M12 connector's pinning

M12 Ethernet connector with 8 pins X-coded

For 1000Base-TX: TIA/EIA-568-B

Pins T568A Color T568B Color Data PoE

1 white/green stripe white/orange stripe TxRx A + DC+

2 green solid orange solid TxRx A - DC+

3 white/orange stripe white/green stripe TxRx B + DC-

4 blue solid blue solid TxRX C + optional

5 white/blue stripe white/blue stripe TxRx C - optional

6 orange solid green solid TxRx B - DC-

7 white/brown stripe white/brown stripe TxRx D + optional

8 brown solid brown solid TxRx D - optional




Table 10 - 1000Base-TX M12 connector's pinning

This connector choice is based on detailed IP connectors’ comparison based on the following criteria:

Mechanical resistivity

Locking system

Coding system

Shielding

Availability

No soldering for electrical contacts

Environmental resistivity (T°C, H2O)

Indicative Cost

Volume

Common use on existing switches

Power Over Ethernet

PCB Counterparts availability

The M12 connector type is compliant with quality rules according to the §2- Minimum set of regulative

requirements above.


7 Harness installation rules

This chapter synthesizes the state of the art of harness installation inside vehicle and ITxPT

recommendations.

7.1 Definitions

Low signal: data signals like Ethernet, RS232, and communication link in general. Low power: vehicle

power supply distributed to low consumption module, in general, IT type module.

7.2 Basic requirements

To insure compliancy with state of the art EMC signal protection rules for IT harness ways inside

vehicle body, the following items should be respected:

IT low signal wires should be separated from high voltage, power or current harnesses by

metallic chassis blade

Harnesses should be lied down to chassis metallic grounded parts all along the way

Power supply lines for IT system dedicated/ independent from chassis/body vehicle

manufacturer module should be used

Wiring signal, power or ground loops should be forbidden

Ethernet wire must be installed with curves radius > 2cm

7.3 Added requirements

This takes into account the specificity of new technologies added or replacing thermal energy for

power trains.

For electric, full or hybrid vehicle specifically, trolley or trams also concerned, rules above are

maintained and completed by:

Low signals and power supply should be mandatory to be located with same rules than above,

but also on different ways than power converters lines, meaning neither with superposition nor

along their paths.

The power supply of IT system should be strongly filtered at the departure point of distribution

Ad-hoc head power filtering should be used

Minimum distances or shielding for power converters components should be used to reduce

EMC pollution

Pay attention if converters are located on composite roof, they could give perturbation in their

under area, links in this area should be avoided.


8 Retrofit of the vehicles

The goal of this chapter is to describe, in the case of a need to retrofit of a vehicle to be able to have a

harmonized fleet, the minimum required in order to be upgraded with the compliant S01- S01-

Onboard Architecture Specifications deployment of a standard ITS architecture on-board and back-

office has to take into account existing vehicles, in order to be ready, in case of a demand of an

operator of PTA to retrofit the old ITS architecture into the S01- S01- Onboard Architecture

Specifications

Minimum requirements for retrofitted vehicles with ITS compliant S01- S01- Onboard Architecture

Specifications

Being able to install a Bus-FMS interface

IP network (Ethernet switch)

MADT

IP Gateway

FMStoIP

The installation recommendations such as the main enclosure and optional enclosure, or the power

supply modes, are not applicable in this context.

The connectors for the IP network, M12 connectors, must be respected.

The retrofit of the vehicles concerns multiplexed vehicles (Euro3 vehicles minimum), equipped or not

with a Bus-FMS gateway.








9 Back-Office installation requirements

9.1 Description

Since Public Transport has different organization architectures in different countries, it adds some

complexity to the basic Back Office Network architecture. Because of this there will be several different

solutions to get the required connectivity.

WAN links should be used to interconnect Back Office Networks. Encrypted VPN is only required

when using Internet for the WAN link.

Router functionalities that allow this network to transfer messages with other Networks must be

included.

General recommendations concerning termination of VPN tunnels from vehicle are to:

Choose as “high” termination point in the architecture as possible.

Change only termination point when the vehicle change registered owner.

Change of (for example) AVMS system can be done without changing VPN termination point and

instead routing traffic at Back Office level (There has to be be a network connection between the two

Back Offices).

9.2 Wireless communication compatible with IP

It must allow communication between “Onboard IP Network” and Back-office networks with several

compatible IP wireless media.

This functionality will allow modules connected to “Onboard IP Network” to communicate with back-

office components, others “Vehicle Gateways”, identified on Back-office networks.

Examples of current technologies:

Long range

Mobile Phone technologies (GPRS, UMTS)

WCDMA

WiMAX

Short range

Wi-Fi

WiGIG

9.3 Hierarchical structure

Picture below shows the aimed hierarchical structure for “PTA IP network” in accordance with the

“Overall description of the Bus on-board and back- office IP network Architecture”:


Figure 9 - PTA IP network


10 Requirements & recommendations

This final part recalls main requirements and recommendations defined in this document. Detailed

information can be found in the dedicated chapters.

Each ITxPT compliant vehicle must be equipped with the minimum set of On-Board ITS modules.

ITS modules installed inside vehicles must respect the applicable regulations, like for the other vehicle

ECUs.

ITS modules installed inside vehicles must respect the applicable bus manufacturers, operators or

PTA quality rules.

ITS modules should be delivered with dedicated certifications. Cabling and wiring have to be installed

according to the state of the art described in the “Harness installation rules” chapter.

ITS modules, especially ECUs, must be delivered with the minimum dataset which permits the

installation testing by the End of Line process.

About End of Line, only configurations requested by vehicle manufacturer under its own responsibility

should be carried out in the vehicle production plant.

SIM card should be not supplied in vehicle production plant and not installed by the bus manufacturer.

Bus manufacturers must predispose, in the vehicle, dedicated places with minimum volumes for the

ITS module.

Bus manufacturers must equip these places with connectivity defined by ITxPT and with mechanical

supports and fixing points.

An Ethernet backbone ITxPT compliant must be predisposed with switches accessible inside or near

the dedicated places.

The Ethernet backbone must forecast a minimum of 2 free plugs available for extension and

maintenance purpose ITxPT should recommend one unique antenna for long range, short range and

satellite localization.

Modules (connectors and mounting’s screw) should be quickly reachable by either technicians or

drivers if necessary. Standard tools and connectors should be used.

Auto tests should be launched regularly (at least at each vehicle start) or on request (in this case,

more complete test can be carried out) in order to be able to maintain quickly an module which does

not work properly.

Each On-Board ITS module must fulfil ITxPT requirements about the limits of power consumption.

Each On-Board ITS modules must integrate an ECO mode strategy ITxPT compliant to limit its energy

consumption.

ITxPT requires the compliancy with the up-to-date Bus-FMS standard.

To get vehicle data from the electrical/electronic architecture, the On-Board ITS module must use the

channel Bus-FMS interface.

- §§§ -

s01- installation requirement specifications its standerd-del...auto tests should be launched...

Documents