SAFN Presentation
SAFN Presentation
SAFN
SDH Add-Drop and Access
Multiplexer
Overview
SAFN
OVERVIEW (1)
VoIP
IP users Gateway Nx64 Kb/s, 2 Mb/s G.703.
Router IP/
Ethernet 10/100BT.
Bridge
IP-PBX
SAFN
PERFORMANCES (1)
TM-1 and ADM-1 (Terminal Multiplexer and Add-Drop Multiplexer in STM-1 SDH Networks)
Multiplexing, Submultiplexing, Drop/Insert and Cross-Connecting in Transport/Access functions
IP Routing function, with co-existence of TDM and IP traffic on the same carrier
VoIP Gateway function
IP-PBX for a Service Telephone System
Link protection (1+1, MSP)
Channel protection (redundancy path, SNCP)
Priority list for the synchronization sources and automatic mechanism for ring networks
Point-to-Point, Point-Multipoint and Omnibus connections
SAFN
PERFORMANCES (2)
To increase the equipment reliability, the following parts can be duplicated in the
SAFN-S mechanics:
Power supply
CPU
Configuration (non volatile memory)
Equipment clock
This redundancy, obtained duplicating the UA and UC units of the basic part
constitutes, for all purposes, a ‘hot stand-by’.
Then, the SAFNs can continue to work on the stand-by unit.
A proper signalling is returned to the management system to individuate the operating
condition of the stand-by part.
SAFN
SAFN
SDH Add-Drop and Access
Multiplexer
Functions
SAFN
FUNCTIONS
IP-PBX function
SAFN
FUNCTIONS
Drop / Insert About voice channels, also the associated signalling is cross-
connected in “TS16” time-slot, together with the respective voice.
PBX
SAFN
SDH link
xDSL link
Radio link
Data
PBX E1-G703
SAFN xDSL
STM-1
Data V28
= FXS-FXS connection
SAFN
V11
= FXO-FXS connection
Data
= 2/4 wires - 2/4 wires connection
SAFN SAFN
STM-1
g.shdsl
SAFN
STM-1
g.shdsl
SAFN SAFN
TDM
SAFN
Users
SDH link
xDSL link
IP Radio link
TDM 10/100BT
TDM
Users SAFN E1-G703
xDSL
STM-1
TDM
SAFN
Users
10/100BT
A2
+
A1
+ Point to Multipoint connection
+
A3
PP1
PC
+ PP2 Ominibus connection
PP3
All the connections can be implemented both on voice and data channels and can be relative both to tributaries and
aggregates streams. Both transit channels (on cross-connections) and local channels can be indifferently involved
in the connections.
Proper solutions are taken in the equipment to ensure that the failure or the absence of a channel unit, related to a
Point-Multipoint or Omnibus connection, causes such a state on the aggregate stream not to damage the correct
connection among the other channels involved in the Point-Multipoint or Omnibus structure.
SAFN
LINK PROTECTION 1+1 (Multilex Section Protection)
First Carrier
SDH link
xDSL link It is possible to assign two different interfaces to each
Radio link aggregate streams. SAFN will provide to automatically
implement the branching in transmission and the
switching in reception.
SAFN
SAFN
SAFN
SAFN
OUTj
SAFN
INj
SDH link
xDSL link
Radio link
E1-G703
SAFN xDSL
STM-1
OUTj
SAFN
INj
Network
Management
System
SAFN SAFN
To correctly manage also the ring
and meshed network topologies
(without the generation of
1 1
‘timing-loop’), some information
on the synchronism state must be 0 1
transmitted among the SAFNs,
constituting the network nodes.
1/0
= synchronism status bit
SAFN
(1=OK, 0=KO)
0
SAFN
1
SAFN
SYNCHRONISM MANAGEMENT: Ring network
SAFN SAFN
To correctly manage also the ring
and meshed network topologies
(without the generation of
‘timing-loop’), some information 1
0 1
on the synchronism state must be
transmitted among the SAFNs,
constituting the network nodes.
1/0 1
= synchronism status bit
SAFN
(1=OK, 0=KO)
1
SAFN
0
SAFN
SYNCHRONISM MANAGEMENT: SDH and fiber/copper branch
SDH Network
SAFN SAFN
(ADM) (ADM)
ext
ext
1 1
1 1
1 1 1 SAFN
SAFN SAFN SAFN
(MUX) (MUX) (MUX) (MUX)
0 0 1
SDH Network
SAFN SAFN
(ADM) (ADM)
ext
ext
1 1
1 1
1 0 0 SAFN
SAFN SAFN SAFN
(MUX) (MUX) (MUX) (MUX)
1 1 1
SAFN
SDH link
SAFN xDSL link LAN
SAFN
Radio link
LAN
LAN
This feature connects different LAN segment with SAFN carriers (or SAFN carriers
partition), so that remote users can hold themselves linked in the same LAN.
The equipment works as a “Layer 2 bridge” (based on MAC address).
The MAC addresses needed to update the MAC tables (formerly known as “forwarding
tables”) are transferred over the links between SAFNs.
= Bridge function With this architecture the efficiency is very high because rerouting on link failure is not
based on the spanning-tree algorithm, but on protection mechanism of SAFN solution
(fast and reliable).
SAFN
IP ROUTER
SAFN
SDH link
xDSL link
Radio link
LAN
SAFN
SAFN
SAFN
LAN
LAN
This feature realize IP routing between Ethernet 10/100BT and SAFN carriers (or
SAFN carriers partition).
The equipment works as a “Layer 3 router” (based on IP address).
With this architecture the efficiency is very high because rerouting on link failure
= IP Router function
is not based on the dynamic routing algorithm typical of IP world (RIP, OSPF), but
on protection mechanism of SAFN solution (fast and reliable).
SAFN
SAFN
SDH Add-Drop and Access
Multiplexer
Technical
Specifications
SAFN
VERSIONS
• Each equipment can manage a traffic capacity of 63 VC12 for each Add-Drop
direction (in the cross-connect function), of 8 VC12 (in the plesyochronous transport
function) and of 8 VC12 (in the synchronous access function).
SAFN
Multiplexing, Add-Drop and Cross Connect capability (Access)
• UA
This is the set of circuits which converts the main power supply in the internal voltages
necessary for the equipment operation.
• UC
It contains the circuits for the realisation of the following functionalities: Equipment
control by means of microprocessor, Generation of equipment synchronism,
Management of connections and cross-connections.
• US
It contains the circuits for the realisation of the following functionalities: Interface for
the external synchronisation source (SI interface), Alarm interfaces, Management
Interfaces.
SAFN
ARCHITECTURE: Repetitive units (1)
Board Description
Board Description
Board Description
Board Description
To increase the flexibility in the use of the equipment, the cards are the same both for the use as
tributaries and as aggregates.
As Line Terminals (to cover a given distance on copper or fibre optics) are available:
fibre optics 155 Mb/s (STM-1).
g.shdsl interface to cover, with a ≤ 2 Mb/s stream, the links on one or two copper pair (SHDSL).
As Exchange Terminals (to connect the equipment to higher order multiplexer) are available:
2 Mb/s G.703 interface (L2M-G703).
A mixed equipping of Line Terminals (SDH / DSL) is possible inside the same SAFN.
The Line Terminals integrated in the equipment directly access to the cross-connection matrices.
So to transmit voice and data on links in copper of fibre optics doesn’t require the use of Exchange
Terminals.
SAFN
INTERFACES (1)
TM-1 / ADM-1 (155 Mb/s Optical Fiber) 1/2
The board TM-1 / ADM-1 manages one / two STM-1 streams on a monomode or multimode fibre.
To correctly work both on monomode and multimode fibre, and to work with different power-
budget, the optical interfaces are provided with pluggable optical tranceivers (SFP transceivers).
The optical streams provides the transport of the 63 VC12 of the STM-1 frames (with a full cross
connection of all these VC12).
8 E1 streams are managed as plesiochronous transport, with 2 Mb/s G.703 physical interfaces
directly on the TM-1 / ADM-1 board.
8 E1 streams are managed as synchronous PCM, used by the internal switching-circuit in the
Access functions.
SAFN
INTERFACES (2)
TM-1 / ADM-1 (155 Mb/s Optical Fiber) 2/2
S-1.1 SM ≥- 5 - 34 ≥ 29 1550 80
L-1.1 SM ≥- 5 - 34 ≥ 29 1310 40
L-1.2 SM ≥ -15 - 31 ≥ 16 1310 20
I MM ≥ -20 - 31 ≥ 11 1310 2
SAFN
INTERFACES (3)
SHDSL
It manages a 2 Mb/s stream in compliance with ITU-T G.703, both with line impedance of 75 Ω and
line impedance of 120 Ω.
It is an exchange terminal: the receiver can support line attenuations ≥ 6 dB at 1024 kHz.
The signal handling is in compliance with what specified in ITU-T G.704, G.706 and G.732.
The interface is transparent to the signals multiplexed in it at 64 Kb/s level, except the “TS0” time
slot.
It manages an high rate data channel in compliance with ITU-T X.21 or X.21 bis.
By means of software programming, a scrambler can be inserted on the data in transmission (circuit
103) in compliance with ITU-T V.38; at the same way, the correspondent descrambler circuit can be
inserted on the data in reception (circuit 104).
The data stream at Nx64 Kb/s interface, with N between 1 and 32 and selectable via software, is
divided in N octets; these will be located in the N programmed timeslots of the 2 Mb/s G.704
aggregate stream, maintaining the correct sequence.
By means of Hw presetting, it is possible to work, as electric interface, in three different modalities:
- X.21bis / V.35 access
- X.21bis / V.36 (RS-449 / RS-530) access
- X.21 / V.11 access
SAFN
INTERFACES (5)
DCE-V28 (low rate data channel X.20bis/V.28 ed X.21bis/V.28)
It manages a data channel with bit rate from 1.2 Kb/s to 19.2 Kb/s in compliance with ITU-T
X.20bis/V.28 and X.21bis/V.28, with sub-rate frame in compliance with ITU-T X.50 div. 3.
Channel bit rate (both synchronous and asynchronous): 1.2, 2.4, 4.8, 9.6, 14.4 and 19.2 Kb/s
For the management of the asynchronous channels, the ITU-T V.14 is used (to reduce the
throughput the management of “break signal” is not implemented).
It manages a 64 kb/s stream, in compliance with ITU-T G.703 co-directional, with two E/M
signallings.
The E/M signalling is inserted in “TS16” timeslot, as associated signalling with two ways for direction
(“a” and “b” bits).
It manages a voice channel, on the lines with two or four wires, with two E/M signallings.
The voice signal is converted from analogue to digital, and vice-versa, according to the “A” law of
ITU-T G.711.
The E/M signalling is inserted in “TS16” timeslot as associated signalling with two ways for each
direction (“a” and “b” bits).
It manages, on 2 wires line, BCA phones with decadic and multi-frequency selection, replying the
functions executed by the user connection of the private or public exchange.
The voice signal is converted from analog to digital, and vice-versa, according to the “A” law of
ITU-T G.711.
The signalling is transported in “TS16” timeslot, as associated signalling with two ways for each
direction (bit “a” and “b”).
The signalling coming from phone side (engagement) is inserted in bit “a” towards the cross-
connection matrix. The signalling coming from the cross-connection matrix on bit “a” and “b” are
returned towards the phone as “ring” and “teletaxe pulses” (12 KHz / 16 KHz).
The phone side interface generates the ringing voltage.
In FXS-FXS (PLAT-PLAT) modality (direct call), this interface provides also to the “ring” timing (1
second / 4 seconds), towards the phone, in presence of the active “a” signalling bit, coming from
the cross-connection matrix cross-connection matrix.
It manages, on 2 wires lines, the user connection of the private or public exchange, replying the
functions executed by BCA phone.
The voice signal is converted from analog to digital, and vice-versa, according to the “A” law of
ITU-T G.711.
The signalling is transported in “TS16” timeslot, as associated signalling with two ways for each
direction (“a” and “b” bits).
The signalling coming from exchange side (ring and teletaxe) are inserted in bit “a” and “b” towards
the cross-connection matrix. The signalling coming from the cross-connection matrix on bit “a” is
returned towards the exchange as “engagement”.
If equipped with US unit, SAFN is provided with one synchronisation interface, in compliance with
ITU-T G.703, by means of which the synchronisation of the equipment with a 2048 KHz signal is
possible.
Management interfaces
SAFN is provided with 10BaseT management interface. If equipped with US unit, SAFN is provided
also with two management interfaces, generally one dedicated to a local operator (LT interface)
and one dedicated to a management centre (DCN interface).
Alarms interface
If equipped with US unit, SAFN is provided with an alarms parallel interface. The alarm interface
has contacts which reports the network and the equipment summary alarms, to external
supervision systems (ground = alarm). SAFN, furthermore, makes available a ground contact,
galvanically insulated, to report the alarm of power supply missing (implement by a drop relay).
SAFN
SERVICE INTERFACES (2)
I/O interface
If equipped with US unit, provided with 8I/O subassembly, SAFN can accept signalling/alarms
(coming from external devices in the form of opening or closing of contacts) and can send
commands (to external devices in form of opening or closing of contacts). 8I/O subassembly can
manage up to 8 senders and 8 returners. The state of the contacts to the external devices
(commands) is commanded by the management system. The state of the contacts coming from the
external devices (signallings) is detected by the management system. Each single signalling can
also be configured as “alarm” (identifying then a “work condition” and a “stand-by condition”) and
then managed in the alarms table.
SAFN
Power supply (1)
US 100 15 30 - - -
TM-1/ADM-1 1800 - - - - -
2LSHDSL4w 1100 - - - - -
4L2M-G703 500 - - - - -
2L2M-G703 380 - - - - -
4DF64-G703 250 - - - - -
8CLG 250 25 25 - -
10PLAC 250 30 30 - -
3DCE/2PLAT 250 20/45 (**) 60/30 (**) 60/6 (***) 48/5 (***)
/2CLG
LAN-ETH 1000 - - - -
SAFN
SDH Add-Drop and Access
Multiplexer
Fault monitoring
Provisioning
Performances monitoring
Software updating
Links management
To allow the management of SAFN using a non-proprietary management system (able to manage
different equipment from different providers) :
- The ‘Management Information Base’ (MIB) is available in a syntax compliance with IETF SMI.
- An SNMP agent is implemented on SAFN, to use a standard application protocol.
SAFN
SNMS: EOC
SAFN can manage a service channel (EOC = Embedded Operation Channel) on the streams that
connect the different equipments in a network.
SNMS uses this EOC to work on all the SAFNs of a complex and meshed network (all the
operations on the local SAFN are so also possible on every SAFNs).
To centre this target it is necessary to configure a service network providing an EOC path between
every node interested by the operations and the node connected to the SNMS.
SAFN can route IP packet from the EOC channel and the LT and DCN ports; to do this the only
board required is the UC .
It’s possible however to enhance routing performance and capability adding the LAN-ETH board to
the equipment.
SAFN
SNMS: Point-to-Multipoint EOC
This network topology has the advantage of a fast answer (every network node is directly polled by
the management centre using a Point to Multipoint connection, so the access rate to a network
node does not depend from the location of the node itself in the network).
Usually in Point-to-Multipoint solution (that requires a tree topology) there are, however, some
constrains:
- The management centre must be in a fixed location, chosen during the network configuration
(to move this centre the Point-to-Multipoint connections must be reconfigured).
- The polling from more management centres is not allowed.
- The automatic re-routing on link failure is not allowed.
- Spontaneous signallings (TRAPs) from the network nodes to the centre are not allowed
(the TRAPs must be excluded and the centre must manage a polling to detect the alarms).
Selta’s solution for the Point-to-Multipoint EOC protection (based on a pilota criterion) has the
advantage of the fast answer and no constraints related to the Point-to-Multipoint topology.
SAFN
SNMS: Point-to-Multipoint EOC
Standard solution
P
Advantages : SAFN
- Fast answer in EOC C SAFN
Detriments :
- Only one NMS
- Failure restore unmanaged
- Traps unmanaged
P
SAFN
C
SAFN
SAFN SAFN
P C P
P
Network
Management
System
= EOC
C = Central in Point to Multipoint
P = Peripheral in Point to Multipoint
SAFN
SAFN
SNMS: Point-to-Multipoint EOC
SAFN solution
0
Advantages : P
SAFN
- Fast answer in EOC C SAFN
P 1
- NMS mobile (More NMS)
- Channel protection (Failure restore)
0
Detriments : 0
1
- Traps unmanaged 0
P P
SAFN 0
C
1 SAFN 0 C P 0
SAFN SAFN
P 1 1
P P
Network 0
Management
System 0 = EOC (Active)
1 0
= EOC (backup)
C = Central in Point to Multipoint
P = Peripheral in Point to Multipoint
SAFN
C P 0/1 = Pilota Criterion
SAFN
SNMS: Point-to-Multipoint EOC
SAFN solution 0
P
Advantages : SAFN
- Fast answer in EOC P SAFN
1
- NMS mobile (More NMS) C
- Channel protection (Failure restore)
1
Detriments : 0
0
- Traps unmanaged 0
P P
SAFN 1
P
0 SAFN 0 P P 0
SAFN SAFN
P 0 1
C C
1 = EOC (Active)
0 0
= EOC (backup)
C = Central in Point to Multipoint
P = Peripheral in Point to Multipoint
Network SAFN
Management 0/1 = Pilota Criterion
System
SAFN
SNMS: Point-to-Multipoint EOC
SAFN solution
0
Advantages : P
SAFN
- Fast answer in EOC C SAFN
P 1
- NMS mobile (More NMS)
- Channel protection (Failure restore)
0
Detriments : 0
1
- Traps unmanaged 0
P P
SAFN 0
C
1 SAFN 0 C P 0
SAFN SAFN
P 1 1
P P
Network 0
Management
System 0 = EOC (Active)
1 0
= EOC (backup)
C = Central in Point to Multipoint
P = Peripheral in Point to Multipoint
SAFN
C P 0/1 = Pilota Criterion
SAFN
SNMS: Point-to-Multipoint EOC
SAFN solution
1
Advantages : P
SAFN
- Fast answer in EOC C SAFN
P 1
- NMS mobile (More NMS)
- Channel protection (Failure restore) 1
1
Detriments :
1
- Traps unmanaged 1
P P
SAFN 0
C
1 SAFN 1 C P 1
SAFN SAFN
P 1 1
P P
Network 0
Management
System 1 = EOC (Active)
1 0
= EOC (backup)
C = Central in Point to Multipoint
P = Peripheral in Point to Multipoint
SAFN
C P 0/1 = Pilota Criterion
SAFN
SNMS: Point-to-Multipoint EOC
SAFN solution
0
Advantages : P
SAFN
- Fast answer in EOC P SAFN
C 1
- NMS mobile (More NMS)
- Channel protection (Failure restore) 1
1
Detriments :
1
- Traps unmanaged 0
P P
SAFN 0
C
1 SAFN 1 P P 0
SAFN SAFN
P 1 1
P C
Network 0
Management
System 1 = EOC (Active)
1 0
= EOC (backup)
C = Central in Point to Multipoint
P = Peripheral in Point to Multipoint
SAFN
C P 0/1 = Pilota Criterion
SAFN
SNMS: Point-to-Point EOC
This network topology has the advantage to allow spontaneous signallings (TRAPs) from network
nodes to the centre, but it is slower in the answer because of the packet retransmission in every
node (routing function).
More centres and alternative paths are managed using the standard solutions in a packet network
(routing tables, dynamic routing, etc.).
With SAFN (both Point-to-Multipoint and routing capability) it is possible to use mixed solutions for
EOC (Point-to-Multipoint connections, using polling from SNMS, and Point-to Point connections,
using routing).
It is possible to report to the management centre also other equipments, geographically located in
the same place of a SAFN, but without any carrier towards the network (service networks with
extensions).
SAFN
SNMS: Point-to-Point EOC
SAFN routing capability
Advantages : SAFN
- Traps managed SAFN
- More NMS
- Failure restore managed
Detriments :
- Slow answer in EOC
SAFN
SAFN
SAFN SAFN
Network
Management
System
= EOC between UC
Other equipment
With TCP/IP
Network
DCN Management
System
SAFN
SAFN
SAFN SAFN
SAFN
SAFN SNMS
Access point
SNMS
SAFN SAFN
Access point SAFN
SAFN
SAFN
IP Network
Network
Management
System
SAFN
SNMS: Other features
More simultaneous SNMS Access points
A solution to reduce the polling time
SAFN SAFN
SAFN
SAFN SNMS
Access point
SNMS
SAFN SAFN
Access point SAFN
IP Network
Red and Green
simultaneous pollings
Network
Management
System
SAFN
SNMS: Alarms classification
Alarm type
Alarm severity
- URG (it includes the CRITICAL and MAJOR categories, as defined in M.3100):
This alarm causes a service loss; therefore, an immediate action is required.
- NURG (it includes the MINOR and WARNING categories):
This alarm does not involve the service; however, a corrective intervention is required to avoid
alarms of higher severity.
Note: Some COMMUNICATION alarms are classified as IND, instead of URG or NURG, when
they report the indication of an alarm detected on the remote equipment.
SAFN
SNMS: Loopbacks
External loopback
It consists in closing the circuits in input from the (user or network) interface on the circuits in
output towards (user or network) interface.
Internal loopback
It consists in closing the streams from the cross-connection matrix (from inside the equipment) on
the streams towards the cross-connection matrix (towards the inside of the equipment).
The state of the loopbacks can be read both from the local terminal and from the management
centre.
SAFN
SAFN
SDH Add-Drop and Access
Multiplexer
Applications
SAFN
Applications: Transport & Access
SDH ring
(MSP and SNCP protections managed by SAFNs)
SAFN SAFN
ADM ADM
(Transport) (Transport)
Plesyochronous E1 Plesyochronous E1
MUX MUX
(Access) (Access)
SDH network
SAFN SAFN
(ADM) (ADM)
May be
the same
equipment PDH network
Both TDM
and IP
LAN LAN
RTU RTU RTU
H.261
mpeg Remote video
Audio broadcast monitoring (TDM)
Remote video
monitoring (IP)
SAFN
Applications: PBX/RTU in Railways and Pipeline
Primary link on pipeline (STM-1)
Branch (XDSL)
PBX
g.shdsl
SAFN
RTU
LAN
SAFN
Applications: Service Telephone System / RTU
Primary link (STM-1)
Branch (XDSL)
Telephone System
CO
g.shdsl
Operator 1
g.shdsl
Operator 2 SAFN
SAFN
Operator 3 RTU
LAN
SIP Phone
SAFN
Applications: Protected Point-Multipoint
SAFN SAFN
SAFN
SAFN
SAFN SAFN
SAFN
Point-Multipoint
Root SAFN
SAFN
SCADA
SAFN
Applications: Protected Point-Multipoint
SAFN SAFN
SAFN
SAFN
SAFN SAFN
SAFN
Point-Multipoint
Root SAFN
SAFN
SCADA
SAFN
Applications: Protected Point-Multipoint (disaster recovery)
SAFN SAFN
SAFN
SAFN
SAFN SAFN
SAFN
Normal Point-
Multipoint Root SAFN
SAFN
Emergency
SCADA
SCADA (Disaster
(Normal recovery)
Central CE)
SAFN
Applications: Protected Point-Multipoint (disaster recovery)
SAFN SAFN
SAFN
SAFN Emergency
Point-Multipoint
Root
SAFN SAFN
SAFN
SAFN
SAFN
Emergency
SCADA
SCADA (Disaster
(Normal recovery)
Central CE)
SAFN
Applications: Protected Point-Multipoint (example with MSP)
Multiplex
Dynamic Central CE
Section
Protection
Cable 1
Emergency Cable 2
SCADA RTU RTU RTU RTU RTU
Peripheral CE
SAFN
Applications: Protected Point-Multipoint (example with MSP)
Multiplex
Dynamic Central CE
Section
Protection
Cable 1
Bandwith / 2
SAFN SAFN SAFN SAFN SAFN
SCADA
Emergency
SCADA Cable 2
RTU RTU RTU RTU RTU
Peripheral CE
SAFN
Applications: Protected Point-Multipoint (example MSP and SNCP)
Multiplex
Dynamic Central CE
Section
Protection
Cable 1
Bandwith / 2
SAFN SAFN SAFN SAFN SAFN
SCADA
Emergency Cable 2
SCADA RTU RTU RTU RTU RTU
Peripheral CE
SAFN
Applications: Protected Point-Multipoint (example MSP and SNCP)
Emergency
SCADA RTU RTU RTU RTU RTU
SAFN
Applications: Protected Point-Multipoint (recovery)
Emergency
SCADA RTU RTU RTU RTU RTU
Connection recovery
with SNCP in the ring
SAFN
Applications: Digital Teleprotection
SDH
Power Line
SAFN SAFN
Distance Distance
Protection Protection
Analog Switch in Rx
Analog PTMP in Tx
SAFN
Customers (1)
CLEMESSY (Senegal)
SFERIACOM (Italy)
RFI METROPOLIS (Italy)
SAFE COMMUNICATION LTD (Northern Ireland Railways)
SELEDISON (Italy)
SIELTE (Italy)
SILIANI ELETTRONICA IMPIANTI (Italy)
TRENITALIA (Italy)
VENTURE (Italy)
HAMDAM Trading EST (Middle East)
IRTE (Italy)
CIET (Italy)
GRAPHTEL (Italy)
ACEA Distribuzione (Italy)