ECT, would mean that Britain would remain an hour ahead of GMT in the winter and two hours ahead in the summer, providing lighter evenings but darker mornings, especially for those north of the border.

However, any proposed plans have stiff opposition from the Scottish Government who suggest that by altering the clocks, many areas in Scotland wouldn’t see daylight during winter until about 10am, meaning many children would have to go to school in the dark.

Other opponents, include traditionalists, argue that GMT has been the basis for British time for over a century, and that any change would be simply … unBritish.
However, a change to ECT would make things easier for businesses that trade with Europe, keeping British workers on a similar timescale to their European neighbours.

Whatever the outcome of the proposed changes to GMT, little will change when it comes to technology and computer networks as they already keep the same timescale all over the globe: UTC (Coordinated Universal Time).

UTC is a global timescale kept true by an array of atomic clocks and is used by all sorts of technologies such as computer networks, CCTV cameras, bank telling machines, air traffic control systems and stock exchanges.

Based on GMT, UTC remains the same the world over, enabling global communication and the transfer of data across time zones without error. The reason for UTC is obvious when you consider the amount of trade that goes on across borders. With industries such as the stock exchange, where stocks and shares fluctuate in price continuously, split second accuracy is essential for global traders. The same is true for computer networks, as computers use time as the only reference as to when an event has taken place. Without adequate synchronisation, a computer network may lose data and international transactions would become impossible.

Most technologies keep synchronised to UTC by using NTP time servers (Network Time Protocol), which continually check system clocks across whole networks to ensure that they all are synced to UTC.

NTP time servers receive atomic clock signals, either by GPS (Global Positioning Systems) or by radio signal broadcast by national physics laboratories such as NIST in the United States or NPL in the UK. These signals provide millisecond accuracy for technologies, so no matter what time zone a computer network is, and no matter where it is in the world, it can have the same time as every other computer network across the globe that it has to communicate with.

Summertime Debate Re-emerges as Clocks go Forward is a post from: Galleon Systems

Greenwich Mean Time may come to an end

UTC (Coordinated Universal Time) has been around since the 1970’s, and already effectively governs the world’s technologies by keeping computer networks synchronised by way of NTP time servers (Network Time Protocol), but it does have one flaw: UTC is too accurate, that is to say, UTC is governed by atomic clocks, not by the rotation of the Earth. While atomic clocks relay an accurate, unchanging form of chronology, the Earth’s rotation varies slightly from day-to-day, and in essence is slowing down by a second or two a year.

To prevent noon, when the sun is highest in the sky, from slowly getting later and later, Leap Seconds are added to UTC as a chronological fudge, ensuring that UTC matches GMT (governed by when the sun is directly above by the Greenwich Meridian Line, making it 12 noon).

The use of leap seconds is a subject of continuous debate. The ITU argue that with the development of satellite navigation systems, the internet, mobile phones and computer networks all reliant on a single, accurate form of time, a system of timekeeping needs to be precise as possible, and that leap seconds causes problems for modern technologies.

This against changing the Leap Second and in effect retaining GMT, suggest that without it, day would slowly creep into night, albeit in many thousands of years; however, the ITU suggest that large-scale changes could be made, perhaps every century or so.

If leap seconds are abandoned, it will effectively end Greenwich Meantime’s guardianship of the world’s time that has lasted over a century. Its function of signalling noon when the sun is above the meridian line started 127 years ago, when railways and telegraphs made a requirement for a standardised timescale.

If leap seconds are abolished, few of us will notice much difference, but it may make life easier for computer networks that synchronised by NTP time servers as Leap Second delivery can cause minor errors in very complicated systems. Google, for instance, recently revealed it had written a program to specifically deal with leap seconds in its data centres, effectively smearing the leap second throughout a day.

Vote Called to End the Use of GMT and Scrapping the Leap Second is a post from: Galleon Systems

Since UTC began in the 1970’s when UTC was introduced, 24 Leap Seconds have been added. Leap seconds are a point of controversy, but without them, the day would slowly drift into night (albeit after many centuries); however, they do cause problems for some technologies.

NTP servers (Network Time Protocol) implement Leap Seconds by repeating the final second of the day when a Leap Second is introduced. While Leap Second introduction is a rare event, occurring only once or twice a year, for some complex systems that process thousands of events a second this repetition causes problems.

For search engine giants, Google, Leap Seconds can lead to their systems from working during this second, such as in 2005 when some of its clustered systems stopped accepting work. While this didn’t lead to their site from going down, Google wanted to address the problem to prevent any future problems caused by this chronological fudge.

Its solution was to write a program that essentially lied to their computer servers during the day of a Leap Second, making the systems believe the time was slightly ahead of what the NTP servers were telling it.

This gradual speeding up time meant that at the end of a day, when a Leap Second is added, Google’s timeservers do not have to repeat the extra second as the time on its servers would already be a second behind by that point.

Galleon GPS NTP server

Whilst Google’s solution to the Leap Second is ingenious, for most computer systems Leap Seconds cause no problems at all. With a computer network synchronised with an NTP server, Leap Seconds are adjusted automatically at the end of a day and occur only rarely, so most computer systems never notice this small hiccup in time.

Google Finds Innovative Way to Avoid Leap Seconds is a post from: Galleon Systems

Time is an abstract concept, while we may think it is the same for everybody, time is affected by its interaction with the universe. Gravity, for instance, as Einstein observed, has the ability to warp space-time altering the speed in which time passes, and while we all live on the same planet, under the same gravitational forces, there are subtle differences in the speed in which time passes.

Using atomic clocks, scientists are able to establish the effect Earth’s gravity has on time. The high above sea level an atomic clock is placed, the quicker time travels. While these differences are minute, these experiments clearly demonstrate that Einstein’s postulations were correct.

Atomic clocks have been used to demonstrate some of Einstein’s other theories regarding time too. In his theories of relativity, Einstein argued that speed is another factor that affects the speed at which time passes. By placing atomic clocks on orbiting spacecraft or aeroplanes travelling at speed, the time measured by these clocks differs to clocks left static on Earth, another indication that Einstein was right.

Before atomic clocks, measuring time to such degrees of accuracy was impossible, but since their invention in the 1950’s, not only have Einstein’s postulations proved right, but also we have discovered some other unusual aspects to how we regard time.

While most of us think of a day as 24-hours, with every day being the same length, atomic clocks have shown that each day varies. Furthermore, atomic clocks have also shown that the Earth’s rotation is gradually slowing down, meaning that days are getting slowly longer.

Because of these changes to time, the world’s global timescale, UTC (Coordinated Universal Time) needs occasional adjustments. Every six months or so, leap seconds are added to ensure UTC runs at the same rate as an Earth day, accounting for the gradual slowing down of the planet’s spin.

For technologies that require high levels of accuracy, these regular adjustments of time are accounted for by the time protocol NTP (Network Time Protocol) so a computer network using an NTP time server is always kept true to UTC.

Oddities of Time and the Importance of Accuracy is a post from: Galleon Systems

NPL's atomic clock

Researchers have discovered that the British atomic clock controlled by the UK’s National Physical Laboratory (NPL) is the most accurate in the world.

NPL’s CsF2 caesium fountain atomic clock is so accurate that it wouldn’t drift by a second in 138 million years, nearly twice as accurate as first thought.

Researchers have now discovered the clock is accurate to one part in 4,300,000,000,000,000 making it the most accurate atomic clock in the world.

The CsF2 clock uses the energy state of caesium atoms to keep time. With a frequency of 9,192,631,770 peaks and troughs every second, this resonance now governs the international standard for an official second.

The international standard of time—UTC—is governed by six atomic clocks, including the CsF2, two clocks in France, one in Germany and one in the USA, so this unexpected increase in accuracy means the global timescale is even more reliable than first thought.

UTC is essential for modern technologies, especially with so much global communication and trade being conducted across the internet, across borders, and across timezones.

UTC enables separate computer networks in different parts of the world to keep exactly the same time, and because of its importance accuracy and precision is essential, especially when you consider the types of transactions now conducted online, such as the buying of stocks and shares and global banking.

Receiving UTC requires the use of a time server and the protocol NTP (Network Time Protocol). Time servers receive a source of UTC direct from atomic clocks sources such as NPL, who broadcast a time signal over long wave radio, and the GPS network (GPS satellites all transmit atomic clock time signals, which is how satellite navigation systems calculate position by working out the difference in time between multiple GPS signals.)

NTP keeps all computers accurate to UTC by continuously checking each system clock and adjusting for any drift compared to the UTC time signal. By using an NTP time server, a network of computers is able to remain within a few milliseconds of UTC preventing any errors, ensuring security and providing an attestable source of accurate time.

British Atomic Clock Leads Race for Accuracy is a post from: Galleon Systems

Early clocks had a very visible form of clock precision, the pendulum. Galileo Galilei was the first to discover the effects of weight suspended from a pivot. On observing a swinging chandelier, Galileo realised that a pendulum oscillated continuously above its equilibrium and didn’t falter in the time between swings (although the effect weakens, with the pendulum swinging less far, and eventually stops) and that a pendulum could provide a method of keeping time.

Early mechanical clocks that had pendulums fitted proved highly accurate compared to other methods tried, with a second able to be calibrated by the length of a pendulum.

Of course, minute inaccuracies in measurement and effects of temperature and humidity meant that pendulums were not wholly precise and pendulum clocks would drift by as much as half an hour a day.

The next big step in keeping track of time was the electronic clock. These devices used a crystal, commonly quartz, which when introduced to electricity, will resonate. This resonance is highly precise which made electric clocks far more accurate than their mechanical predecessors were.

True accuracy, however, wasn’t reached until the development of the atomic clock. Rather than using a mechanical form, as with a pendulum, or an electrical resonance as with quartz, atomic clocks use the resonance of atoms themselves, a resonance that doesn’t change, alter, slow or become affected by the environment.

In fact, the International System of Units that define world measurements, now define a second as the 9,192,631,770 oscillations of a caesium atom.

Because of the accuracy and precision of atomic clocks, they provide the source of time for many technologies, including computer networks. While atomic clocks only exist in laboratories and satellites, using devices like Galleon’s NTS 6001 NTP time server.

A time server such as the NTS 6001 receives a source of atomic clock time from either GPS satellites (which use them to provide our sat navs with a way to calculate position) or from radio signals broadcast by physics laboratories such as NIST (National Institute of Standards and Time) or NPL (National Physical Laboratory).

What Governs our Clocks is a post from: Galleon Systems

GPS time signals are secure

And time doesn’t just need to be accurate for these organizations, but secure too. A malicious user who interferes with a timestamp could cause all sorts of trouble, so ensuring time sources are both secure and accurate is vital.

Security is increasingly important for all sorts of organisations. With so much trade and communication conducted over the internet, using a source of accurate and secure time is as important a part of network security as anti-virus and firewall protection.

Despite the need for accuracy and security, many computer networks still rely on online time servers. Internet sources of time are not only unreliable, with inaccuracies commonplace, and distance and latency affecting the precision, but an Internet time server is also unsecure and able to be hijacked by malicious users.

But an accurate, reliable and completely secure source of time is available everywhere, 365 days a year—GPS.

While commonly thought of as a means of navigation, GPS actually provides an atomic clock time code, direct from the satellite signals. It is this time code that navigation systems use for calculating position but it is just as effective to provide a secure time stamp for a computer network.

Organizations that rely on accurate time for safety and security all use GPS, as it is a continuous signal, that never goes down, is always accurate and can’t be interfered with by third parties.

To utilise GPS as a source of time, all that is required is a GPS time server. Using an antenna, the time server receives the GPS signal, while NTP (Network Time Protocol) distributes it around the network.

GPS time server

With a GPS time server, a computer network is able to maintain accuracy to within a few milliseconds of the atomic clock time signal, which is translated into UTC time (Coordinated Universal Time) thanks to NTP, ensuring the network is running the same accurate time as other networks also synchronised to a UTC time source.

Receiving Time Signals with GPS is a post from: Galleon Systems

NTS 6001 from Galleon Systems

The international stock exchanges such as the NASDAQ and London Stock Exchange all require accurate and precise time. With traders buying and selling shares for customers across the globe, a few seconds of inaccuracy could cost millions as share prices fluctuate.

NTP servers linked to atomic clock timing signals ensure that the stock exchange keeps an accurate and precise time. As computers across the globe all receive the stock prices, as and when they change, these two use NTP server systems to maintain time.

The global timescale UTC (Coordinated Universal Time) is used as the basis for atomic clock timing, so no matter where a trader is on the globe, the same timescale prevents confusion and errors when dealing with stocks and shares.

Because of the billions of pounds worth of stocks and shares that are bought and sold on trading floors every day, security is essential. NTP servers work externally to networks, getting their time from sources such as GPS (Global Positioning System) or radio signals put out by organisations like the National Physical Laboratory (NPL) or the National Institute for Standards and Time (NIST).

The stock exchanges can’t use a source of internet because of the risk this could pose. Hackers and malicious users could tamper with the time source, leading to mayhem and cost millions and perhaps billions if the wrong time was spread around the exchanges.

The precision of internet time is limited too. Latency over distance can create delays, which could lead to errors, and if the time source ever went down, the stock markets could hit trouble.

It is not only stock markets that need precise and accurate time, computer networks across the globe concerned about security use dedicated NTP servers like Galleon Systems’ NTS 6001. Providing accurate time from both GPS and radio signals from NPL and NIST, the NTS 6001 ensure accurate, precise and secure time every day of the year.

Precise Time on the Markets is a post from: Galleon Systems

Various forms of security exist to defend against unauthorised access to computer networks such as antivirus software and firewalls.

One area often overlooked, however, is where a computer network gets it source of time from, which can often be a vulnerable aspect to a network and a way in for hackers.

NTP servers helps secure computer networks

Most computer networks use NTP (Network Time Protocol) as a method of keeping synchronised. NTP is excellent at keeping computers at the same time, often to within a few milliseconds, but is dependent on a single source of time.

Because computer networks from different organisations need to communicate together, having the same source of time makes sense, which is the reason most computer networks synchronise to a source of UTC (Coordinated Universal Time).

UTC, the world’s global timescale, is kept true by atomic clocks and various methods of utilising UTC are available.

Quite often, computer networks use an internet time source to obtain UTC but this is often when they run into security issues.

Using internet time sources leave a computer network open to several vulnerabilities. Firstly, to allow access to the internet time source, a port needs keeping open in the system firewall (UDP 123). As with any open port, unauthorised users could take advantage of this, using the open port as a way into the network.

Secondly, if the internet time source itself if tampered with, such as by BGP injection (Border Gateway Protocol) this could lead to all sorts of problems. By telling internet time servers it was a different time or date, major havoc could ensue with data getting lost, system crashes—a type of Y2K effect!

Finally, internet time servers can’t be authenticated by NTP and can also be inaccurate. Vulnerable to latency and affected to distance, errors can also occur; earlier this year some reputable time servers lost several minutes, leading to thousands of computer networks receiving the wrong time.

To ensure complete protection, dedicated and external time servers, such as Galleon’s NTS 6001 are the only secure method of receiving UTC. Using GPS (or a radio transmission) an external NTP time server can’t be manipulated by malicious users, is accurate to a few milliseconds, can’t drift and is not susceptible to timing errors.

Hackers and Time Servers is a post from: Galleon Systems

75 Years of the speaking clock

The service, available by dialling 123 on any BT landline (British Telecom), began in 1936 when the General Post Office (GPO) controlled the telephone network. Back then, most people used mechanical clocks, which were prone to drift. Today, despite the prevalence of digital clocks, mobile phones, computers and a myriad number of other devices, the BT speaking clock still provides the time to 30 million callers a year, and other networks implement their own speaking clock systems.

Much of the speaking clock’s continuing success is perhaps down to the accuracy that it keeps. The modern speaking clock is accurate to five milliseconds (5/1000ths of a second), and kept precise by the atomic clock signals provided by NPL (National Physical Laboratory) and the GPS network.

But the announcer declaring the time ‘after the third stroke’ provides people with a human voice, something other time-telling methods don’t provide, and may have something to do with why so many people still use it.

Four people have had the honour of providing the voice for the speaking clock; the current voice of the BT clock is Sara Mendes da Costa, who has provided the voice since 2007.

Of course, many modern technologies require an accurate source of time. Computer networks that need to keep synchronised, for security reasons and to prevent of errors, require a source of atomic clock time.

Network time servers, commonly called NTP servers after Network Time Protocol that distributes the time across the computers on a network, use either GPS signals, which contain atomic clock time signals, or by radio signals broadcast by places like NPL and NIST (National Institute for Standards and Time) in the US.

75 Years of the Speaking Clock is a post from: Galleon Systems