Transcript The Internet of Things - Weather Monitoring too Bruce Hartley Lead Systems Engineer Meteorological Service of New Zealand Ltd. October 2012

The Internet of Things -
Weather Monitoring too
Bruce Hartley
Lead Systems Engineer
Meteorological Service of New Zealand Ltd.
October 2012
1
The purpose of my presentation is two-fold…
1.To demonstrate what is possible and to stimulate ideas in the weather
monitoring community
2.To stimulate manufacturers into providing all weather sensors and systems
so that they can connect via TCP/IP in a “standardised” way
I will cover three topics in my presentation…
•Some background on the Internet
•MetService New Zealand implementation
•The technology challenge – What we need are smart devices with…
My main background is in Weather Stations and my examples reflect this.
However such is the flexibility of TCP/IP communications that…
The ideas presented here can be applied to any equipment
The ideas are scalable: from a single sensor & display
… to a global network
2
the Internet - the World Wide Web - the Web - the Cloud
Is a global network of networks consisting of millions of private, public, academic,
business, and government networks, that are linked by a broad array of
communications and network technologies, all using the standard Internet
protocol suite ( TCP/IP ).
The Internet – It’s all about Information. Initially for access to stored information,
moving it from place to place and making it available for all to see,
but increasingly it’s about device control and data delivery in real time
from everywhere to anywhere.
the Internet of Things
An extensive range of everyday objects
(data sources and/or sinks) connected and
communicating cheaply with each other
across a global network.
3
How has it developed?
…20 years young!
1960s Researched in the US
1990s Commercial 2-way communications:
Where is it available?
1993 = 1%
2000 = 51%
2007 = 97%
…Everywhere!
With the appropriate modem there is almost nowhere that you cannot connect.
The question is no longer “Can I connect?”, it is now “How do I connect?”
Who is using it?
…Everybody!
2011 estimate - two billion people ( 1/3 of Earth’s population ) using the Internet.
Facebook:
2008 - 100 mil
2009 - 150 mil
2011 - 750 mil
2012 > 1 billion
What can it do?
2010 - 350 mil
…For us!
More information ( accurate, timely, uptime, efficient, management, cheaper )
= Better forecasts = Better decisions = Lower cost and lower loss
4
How Reliable is it?
…Good enough?
The open Internet has built in redundancy - a star type network.
The more providers on different infrastructure - the better the reliability.
ISP reliability:
Dial up 99.9% (9hr/yr) Cable 99.8% (17hr/yr) Wireless 99.4% (52hr/yr)
Not really good enough!
With a bit of ingenuity this can be good
enough for Weather Monitoring:
 Diversity
 Transfer protocols - retries
 Multiple message redundancy
 Backlogging
Resilience: Business, finance, government and military reliance suggests that the
Internet MUST always be viable. The rest of us will piggy back on the system forever.
5
MetService Stations to Central Server Communications
MetService TCP/IP implementation has been driven by the communications providers
implementing new technologies and closing old services.
MetService employs Unified Communications (UC) to make implementation and
movement between communications media and suppliers seamless.
The Office Anywhere (OA) Virtual Private
Network (VPN) is used whenever
possible for security of:
 Data communication
 Remote station access
 Central server access
For increased reliability – some dual
communications has been implemented
from stations to the OA VPN.
6
TCP/IP modes implemented by MetService
184 Weather Stations ( 36 high priority stations have diverse communications )
TCP
1 second
point to point
(local: wind displays)
1 minute
point to point
(local: displays; AWIB; entry)
UDP
1 minute
with a two try handshake protocol
1 minute
with messages repeated every 15 seconds
Email
30 minute METAR SYNOP BUOY SHIP - 28 day backlog
FTP
Third party Delivery at various times and/or event driven
8 Weather Radars ( 6 have diverse communications )
TCP
7.5 minute image push
10 Lightning detection Sensors
TCP
Real time (on event)
7 Webcams
FTP
4 minute image push
We have 8 remaining stations to be migrated from old technologies
( AFTN =1, MTSAT = 7 )
7
Weather Station Connectivity - Now
* Serial sensors on Ethernet!
have a Device Server
Service
Ethernet (TCP/IP)
Serial (USB, RS-232/422/423/485)
Modulated serial
Analogue (voltage, current...)
*Sensor
*Sensor
*Sensor
Weather
Station/
Processor
USBto
toRSxxx
RSxxx
USB
USB
to RSxxx
Modem (and
Router/Switch)
Modem
Internet via Diverse Providers
Current NZ MetService "Traditional" Weather Station Topology
Server
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Analogue
Analogue
Analogue
Analogue
Serial
to
Analogue
Serial
to
Serial
to
to
Serial
toSerial
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Sensor
Sensor
Sensor
Sensor
Sensor
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Display
Display
Display
Display
Display
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Sensor
Modem links optional and as required
Display
Display
Display
Service
Routeror
or
Router
Switch
Switch
Modem(and
(and
Modem
Router/
Router/
Switch)
Switch)
8
oviders
 Some station devices are connected to the TCP/IP network:
sensor; router; watchdog; power supply; service computer.
 Retaining traditional technologies imposes additional overheads:
Future IP Network Weather Station Topology
design;
documentation; training; support services.
Processor
Extend
Processor
Extend
Extend
Processor
Extend
Extend
 Traditional serial ports Extend
(RS232/422/485)
are disappearingEthernet
from (TCP/IP)
Modulated TCP/IP
* Serial sensors and AWS!
computers and modems.
*Sensor
Extend
Extend
*Sensor
Extend
Extend
have a Device Server
Extend
Extend
*Sensor
Extend
Extend
Extend
Extend
Extend
Extend
Display
Display
Display
Weather Station Connectivity - Future
Extend
Extend
Extend
Extend
Extend
Extend
Processor
Processor
Processor
Extend
Extend
Extend
Extend
Extend
Extend
*Sensor
*Sensor
*Sensor
Extend
Extend
Extend
Extend
Extend
Extend
Display
Display
Display
Extend
Extend
Extend
Extend
Server
Server
Service
Processor
Processor
Routeror
or
Router
Switch
Switch
Routeror
or
Router
Switch
Switch
Modem(and
(and
Modem
Router/
Router/
Switch)
Switch)
Internet via Diverse Providers
Future IP Network Weather Station Topology
Ethernet (TCP/IP)
Modulated TCP/IP
* Serial sensors and AWS!
have a Device Server
Extend
Extend
Extend
Extend
Extend
Extend
Processor
Processor
Processor
Extend
Extend
Extend
Extend
Extend
Extend
*Sensor
*Sensor
*Sensor
Extend
Extend
Extend
Extend
Extend
Extend
Display
Display
Display
Extend
Extend
Extend
Extend
*Sensor
*Sensor
Display
Display
Extenders are optional
and as required
Service
Service
 In a simpler world - TCP/IP from the ingest server to every device
 Interconnection between the different link modules is the same…
Ethernet with PoE where practicable and/or Wi-Fi
 Where Ethernet and Wi-Fi won’t reach – Ethernet/WiFi Extenders
 The network is seamlessly expandable using the routers/switches
9
Is it worth the effort to change?
Benefits
TCP/IP Unified Communications - efficiency & adaptability without re-design
Web browser control of ALL devices
Network management possible from anywhere
Communications diversity of the main trunks is inherent in the network
Software management can be centralised - no physical network roll-outs
Data collection and management can be outsourced - Cloud Computing
Weather station processor can be anywhere
Backup processor(s) can be anywhere
Standardised PoE saves cabling, connections and time
Standardised cabling - Cat5E or better
Wi-Fi up to 250 devices can connect to a single module
Built in transient protection/isolation – one scheme, less boxes
Technicians can access and save documentation from anywhere
10
Is it worth the effort to change?
Cons
xMay need diversity from the remote site to the core Internet
xSecurity outside the company firewall - VPN preferred, firewall minimum
xSecure login processes and username/password management
xPower consumption of current modems/routers - solar powering is difficult
xPower supply scheme – 48 vdc
xMore data to manage ( database, monitoring, access tools, archive )
xNetwork management skills and tools required
xNew contracts with telecommunications operators
xNew contracts with others handling and managing equipment and/or data
xWiFi still requires a conventional power supply connection
11
The technology challenge - We need smart devices with…
Standard Ethernet with PoE (PoE 48vdc 15W, PoE+ 48vdc 30W)
Standard Wi-Fi
Standard power supply 48 vdc?
(optional 12 vdc? 24 vdc?)
Standardised messages
(xml? Flexibility for custom messages)
Standardised data pull TCP server
(multiple connections)
Standardised data push FTP / UDP / Email (multiple destinations):
Data push
scheduled
Data push
alert / warning / alarm
Status push
warning / alarm / fault
Standard NTP time synchronisation where appropriate
Built in setup and diagnostics web server, with setup file save & load
New firmware roll outs from anywhere on the VPN (automatic)
All hard wire interfaces include transient protection (including antenna)
Little or no increase in power consumption
Little or no increase in price
12
The consumer market is already there!
13
And to finish - The skies the limit, or is it?
 Today
 Tomorrow
 The Future
www.met.co.nz.aws1
www.met.co.nz.site1.sensor1
mars.met.co.nz.site1.sensor1
All we need is…
Curiosity
14
Thank You
Questions…
15