3.

4 Сатни систем
The Master Clock system shall be designed as a modular time distribution system
where the individual devices (modules) are connected to a LAN and synchronized
by NTP. Therefore the devices (e.g. Time-Servers / Master Clocks) can be located
where needed, respectively the Master Clock system can be ‘distributed’ at will.

3.4.1 General

1.1. The Master Clock System shall be modern and modular system.
1.2. The Master Clock System shall consist OCC redundant master clock
system:
1.2.1. At the OCC a redundant master clock system, consisting of two master
clocks. Both master clocks are synchronized by means of GPS.

1.2.2. The redundant master clocks shall provide PTP, NTP-time code and
SNMP services (configuration and alarm reporting) as well as other
suitable signals. The highest degree of system security and reliability
shall be achieved by the master-slave operation of the two master clocks
connected via fiber optics (redundant operation).

1.2.3. The Master Clock shall be controllable by SNMP. That means it shall
be possible to configure the Master Clock by SNMP (PUT command)
and it shall be possible to read all parameters by SNMP (GET
command). Alarms shall be signalized by SNMP alarm traps, SNMP
alive-messages and e-mail.

1.3. The Master Clock System shall consist SUB-master clocks at stations:
1.3.1. At each station shall be a sub-master clock in client/server mode with
reference to NTP Ethernet based protocol: i.e. client from redundant
master clock system (OCC) and server for local station IT equipment
synchronization (NTP). In addition, the sub-master clock shall provides
network services as SNMP (for configuration and alarm reporting) as
well as direct secured remote access for supervision and configuration.
 1.4. The Master Clock System shall consist Slave clocks:
1.4.1. Analog outdoor clocks, illuminated, usually double sided, diameter 60
cm (typically). These clocks are mainly installed on platforms or
concourses.
1.4.2. Digital outdoor clocks, character size 180 mm, LED display, hour and
minute display, 7 segment characters.
1.4.3. Analog indoor clocks, diameter 30 to 40 cm.
1.4.4. Digital indoor clocks with hour- and minute- display. Typical
character size: 57 mm.
1.4.5. Facade Clocks with up to 3.5 meter diameter

3.4.2 System Functions

1.5. The Master Clock System shall includes the following functions:
1.5.1. Master Clock shall consist of two Master Clocks operating in
redundant mode. The two Master Clocks automatically negotiate the
master <-> slave status and synchronize each other precisely through an
optical link.
1.5.2. Sub-master Clock shall synchronized from the Master Clock by NTP,
operating as local NTP time server. Internal autonomous clock to
provide correct time information in case the link to the Master Clock is
interrupted.
1.5.3. NTP time distribution over the Ethernet for all devices of the Master
Clock System: Master Clock, Sub-master Clock, digital and analog
Slave Clocks and others sub-systems as CCTV, access control,
ticketing… .
1.5.4. Time Zone Management: since the time transmission on NTP shall be
defined as UTC, the Master Clock System must calculate specific local
times for clocks, time display and additional interfaces for time
distribution. The time zones for clocks and other time interfaces must be
selectable separately. At least 15 different time zones shall be available.
1.5.5. All devices of the Master Clock System, Master Clock, Sub-master
Clock, digital and analog Slave Clocks, shall be fully administrated and
supervised by SNMP (traps, Set- and Get- command).
1.5.6. The Slave Clocks shall be able to retrieve the time information either
from the redundant Master Clock directly or from the local Sub-master
 Clock. Therefore it shall be possible to store at least three time server
addresses in each Slave Clock.
1.5.7. Alternatively, the slave clocks shall retrieve the time information
directly from a master or sub-master clock not being located physically
at the same station/place as the slave clocks.
1.5.8. Integrated software solution for management and supervision
consisting of:
1.5.9. Network Management System (Software for Windows PCs) for the
centralized configuration and administration of all components of the
Master Clock System -Master Clocks, Sub-master Clocks, NTP digital
and analog clocks including the Supervision Service.
1.5.9.1. Device Supervision Service to monitor the entire Master Clock
System automatically.

3.4.3 Technical specification

3.4.3.1 Master Clock

1.6.The Master Clock shall support Time synchronization from GPS receiver or
from NTP server.
1.7.The Master Clock shall support Internal oscillator OCXO or Rubidium in
order to maintain time accuracy in case of GPS unavailability
1.8.The Master Clock shall support Visual information on display as: current
time and date, synchronization status, IP-address, power and alarm status,
1.9.The Master Clock shall support Login protected by password
1.10. The Master Clock shall support IP configuration: DHCP, static IP,
IPv4, IPv6
1.11. The Master Clock shall support Network services:
1.11.1. PTP master IEEE1588-2008 (V2) 1 or 2-step
1.11.2. SyncE master (over 1 front side port)
1.11.3. NTP v4 (compatible with v3), (UDP), as per RFC 1305 (Port
123)
1.11.4. NTP Authentication with MD5 Key / Auto key
1.11.5. SNTP (UDP), RFC2030 (Port 123)
1.11.6. TIME (TCP/UDP), RFC 868 (Port 37)
1.11.7. DAYTIME (TCP/UDP), RFC 867 (Port 13)
 1.11.8. Telnet, SSH, FTP, SCP, SFTP - dis engageable
1.12. The Master Clock shall support Time zone server
1.13. The Master Clock shall support NTP modes: Server, Peer, Broadcast,
Multicast. Server and client modes are possible simultaneously,
1.14. The Master Clock shall support Network remote access for device
management by SSH or Telnet,
1.15. The Master Clock shall support Potential-free alarm-relay-contact in
order to propagate alarms (with individual alarm masking capability),
1.16. The Master Clock shall support Insures permanent non volatile
configuration storage,
1.17. The Master Clock shall support USB connector for software updates
and complete configuration backup and restore.
1.18. The Master Clock shall support Operating temperature range:
1.19. The Master Clock shall support -5 to 50ºC, 10-90% relative humidity
(non condensing)
1.20. The Master Clock fit in 19“ rack 1U housing.
1.21. The Master Clock shall support Interfaces:
1.21.1. 3x 10/100/1000 MBit, RJ45
1.21.2. 1x SFP
1.21.3. 1x RS 232 interface for operation control, D-Sub 9 connector
1.21.4. 1x USB interface for firmware update
1.21.5. 2x Serial outputs with configurable time telegrams
1.21.6. 1x IRIG, AFNOR DCF/FSK
1.21.7. 1x 10 MHz (BNC connector)
1.21.8. 1x E1 / 2.048MHz, G811, G.812, G813 according oscillator
1.21.9. 1x DCF 77 CL
1.21.10. 1x Precision pulse/frequency/DCF output on RS422 and C

3.4.3.2 Sub-Master Clock

1.22. The Sub-master Clock shall provides reliable and accurate time for
slave clocks and subsystems. The Sub-master Clock is synchronized to the
time if the Master Clock through LAN/Ethernet by NTP. When
synchronized to the Master Clock, the time accuracy of the output of the
Master Clock, measured at the DCF77 output, is better than +/- 10ms
compared to the time of the Master Clock. When the synchronization to the
 Master Clock is lost, the deviation of the Sub-master Clock is not more than
0.1 seconds per day (measured at 20°C +/- 5°C).
1.23. The Sub-master Clock shall be controllable by SNMP. That means
that it shall be possible to configure the Sub-master Clock by SNMP (PUT
command) and read all parameters by SNMP (GET command). Alarms
shall be signalized by SNMP alarm traps, SNMP alive messages and e-mail.
1.24. The Sub-master Clock shall Time synchronization from GPS receiver
or from NTP server.
1.25. The Sub-master Clock shall have internal oscillator in order to
maintain time accuracy in case of unavailability of the time references.
1.26. The Sub-master Clock shall support Visual information on display as:
current time and date, synchronization status, IP-address, power and alarm
status,
1.27. The Sub-master Clock shall support Login protected by password,
1.28. The Sub-master Clock shall support IP configuration: DHCP, static
IP, IPv4, IPv6.
1.29. The Sub-master Clock shall support Time server protocols:
1.29.1. NTP v4 (compatible with v3), (UDP), as per RFC 1305 (Port
123)
1.29.2. NTP Authentication with MD5 Key / Auto key
1.29.3. SNTP (UDP), RFC2030 (Port 123)
1.29.4. TIME (TCP/UDP), RFC 868 (Port 37)
1.29.5. DAYTIME (TCP/UDP), RFC 867 (Port 13)
1.30. The Sub-master Clock shall support NTP modes: Server, Peer,
Broadcast, Multicast. Server and client modes are possible simultaneously,
1.31. The Sub-master Clock shall support Network remote access for
device management by SSH or Telnet,
1.32. The Sub-master Clock shall support Serial output RS232,configurable
telegram strings, 300-38400 Bauds, 7 or 8 Data bits, Parity: no, even, odd,
Stop bit: 1 or 2, no flow control
1.33. The Sub-master Clock shall support Current loop (passive) output for
DCF77 time code or pulse output (selectable), pulse mode: pps, ppm, pph,
user defined 1-3600s,
1.34. The Sub-master Clock shall support Line output to synchronize self-
setting slave clocks, digital or analog type and diverse other interface as
switching relays with the ability to power and power analog clocks and
switching relays: 700 mA output current.
 1.35. The Sub-master Clock shall support impulse line output to control
conventional impulse driven clocks:
1.36. The Sub-master Clock shall support polarized impulses selectable
repetition 1 sec, 1 min, 1 A output current
1.37. The Sub-master Clock shall support Potential-free alarm-relay-
contact,
1.38. The Sub-master Clock shall insure permanent non volatile
configuration storage, dual Power supply, 1 x 90 .. 240 VAC, 1 x 24..28
VDC
1.39. The Sub-master Clock shall support USB connector for software
updates and complete configuration backup and restore.
1.40. The Sub-master Clock shall support Mean time between failure
(MTBF) > 250’000 hours
1.41. The Sub-master Clock shall support Operating temperature range:
1.41.1. -5 to 50ºC, 10-90% relative humidity (non condensing)
1.42. The Sub-master Clocks fit in a 19” rack 1U housing

3.4.3.3 Clocks

1.43. The clocks shall be synchronized by NTP according to the standards

RFC 1305 (V3) and RFC 4330 (SNTP V4).
1.44. Since NTP transmit the time as UTC, an additional telegram shall be
transmitted from the NTP Server to the clocks. This telegram contains the
time offset local time to UTC for at least 15 selectable time zones.
1.45. It shall be possible to operate the NTP clocks in unicast and in
multicast mode, whatever is more convenient for the specific installation.
1.46. Double sided clocks are connected by one LAN-cable only. It shall not
be necessary to install a separate connection cable to the next switch for
each movement or for each side of a double sided digital clock.
1.47. The clocks shall be able to take over the network configuration
automatically from the DHCP server: IP-address, gateway-address, subnet-
mask, up to 4 NTP-server and time-zone server addresses, SNMP-manager
address.
1.48. To integrate the clocks into a supervision / management system, the
clocks shall support SNMP V2c notifications (traps). The clocks shall send
alarm- and alive- traps to the assigned SNMP manager. The traps structures
shall be defined in a MIB-file.
3.4.3.3.1 Analog indoor and outdoor clocks, 60 cm diameter

1.49. Round clocks with hour, minute and second hands. Available in single
and double sided version.
1.50. The clock is illuminated by energy-efficient LEDs. The brightness will
be within 100 to 250 cd/m2.
1.51. The illumination must be evenly distributed. The darkest spot is > 0.5
times the average brightness.
1.52. The housing is made of high quality aluminum, weather-proof powder
coated.
1.53. Dial, hands and case color could be in line with the specifications and
approval of the customer.
1.54. The clocks are protected by an Ingress Protection level of IP 54.
1.55. The single-sided clocks are ready for wall-mounting. The double-sided
clocks are available for sideways fixation on a wall and suspending from a
ceiling.
1.56. The power supply for the different versions are:
1.57. PoE for the movements and 230VAC for the LED illumination

3.4.3.3.2 Analog Indoor Clocks, 30-40 cm

1.58. Round clocks with hour and minute hands.

1.59. The clocks are optionally available with second hands.
1.60. The clock sets itself automatically to the correct time, after connecting
it to correspondent LAN network.
1.61. The clock doesn't require any further cable installation than the LAN
cable.
1.62. The clocks are available in two sizes, 30 and 40 cm diameter
providing viewing distances (daylight) of 40 and 50 m.
1.63. With an optional mounting kit, two clocks can be combined to a
double sided clock with a bracket for ceiling and wall mounting.
 1.64. Dial, hands and case color are in line with the specifications and
approval of the railway company.
1.65. The clocks are protected by an Ingress Protection level of IP 30

3.4.3.3.3 Facade Clock

1.66. Facade Clock up to 1 to 3.5 meter diameter with self-setting motor-

movement
1.67. Hour- and minute- hand
1.68. Outdoor mounting without cover glass.
1.69. The dials are available in various executions. With and without
illuminated markers.
1.70. The dials are made of black thermo-lacquered light metal and are
mounted directly onto the facade. The solid clock movement is mounted
behind the wall, which means inside the building and the length of the hand
shaft is made according to the wall thickness.
1.71. The clock could be self-setting, controlled and synchronized by
MOBALine. This Timecode is provided by the Sub-master Clocks.
1.72. wide-range power supply: 90-265 VAC, 50/60 Hz.
3.4.4 Network Management System

Software to administrate Master Clock system devices as well as NTP Slave Clocks
shall be available. This software, named Network Management System NMS, shall
be platform independent. (e.g. written in Java). The NMS shall be designed to
handle more than 1000 devices per network and it supports the Master Clock
system devices as well as analog and digital Slave Clocks. The NMS shall has an
intuitive GUI (Graphical User Interface) and it shall includes well known features
such as Drag and Drop.

1.73. The NMS shall have following features:

1.73.1. Device auto detection for multicast and unicast (IP range scan)
communication
1.73.2. Read and change device configuration with a comfortable user
interface
1.73.3. Display device status, time, error and alarm information of each
device. Error and alarm information are additionally shown at group
level
1.73.4. Create and remove logical groups and move / sort devices per
drag and drop for easier management and supervision
1.73.5. Save and load created configurations of the DTS devices with
all members of a logical group
1.73.6. Based on the device type, the NMS can display and change all
configuration values like IP address, NTP server, SNMP settings etc.
1.73.7. For each device a short overview with the current status and
configuration information is available
1.73.8. The NMS can send device commands (like the 12:00 position
command for analog clocks) to one or more devices / logical groups for
installation and maintenance purposes
1.73.9. With the integrated TFTP server a device firmware upgrade for
the Slave Clocks is done with only a few clicks
1.73.10. Monitor for the NTP telegrams
1.73.11. Monitor for the time zone telegrams
1.73.12. Each monitor can listen to multiple multicast groups and display
all received network packets
1.73.13. Operation control – administration, configuration and
supervision - of the Master Clock devices.
1.73.14. Editor for time zone definitions
1.73.15. Configuration and administration of the Centralized Supervision
Service
1.73.16. Centralized Device Supervision Service to monitor the entire
Master Clock System automatically, including the following features:
1.73.16.1. Centralized service for supervision of Slave Clocks and
Master Clock system devices
1.73.16.2. Active supervision: Status / Alarm information update,
Network pings, NTP requests, SNMP requests.
1.73.16.3. Passive supervision: Receive SNMP traps / notifications
and alive messages.
1.73.16.4. Alarm forwarding by E-Mail or SNMP traps /
notifications.(acts as alarm collector).
1.73.16.5. Web interface for status display.
1.73.16.6. Support for NMS configuration files.
1.73.16.7. Configuration of the SNMP supervision service over the
NMS