Its detroit2018 ndot
•Download as PPTX, PDF•
1 like•51 views
"Building an ITS Network for the Future" as presented by Seth Daniels, Chief Traffic Operations Engineer at NDOT at ITS Americas 2018 in Detroit.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Its detroit2018 ndot
Similar to Its detroit2018 ndot (20)
Recently uploaded
Recently uploaded (20)
Its detroit2018 ndot
- 1. Building an ITS network for the future Seth Daniels, Assistant Chief Traffic Operations Engineer Nevada Department of Transport
- 2. Vehicles have come a long way …have our networks kept pace? 6/6/2018 2 Pilot Car, 1920 1920’s Striper 1920’s Snow Removal Equipment
- 3. ITS Investments Support NDOT’s Mission 6/6/2018 3 Excerpt from Statewide Transportation Improvements Program (STIP) Our Mission Provide the traveling public the information and technology they need to reach their destinations quickly and safely NDOT Information Technology Mission Statement 1985: DARPA vehicle drives thru CO hills without human driver (avg speed: 5mph) 1995: “No Hands Across America” demo: 98.2% of 2,849 mi trip driven autonomously 2005: FCC establishes frequencies for DSRC 2016: All electronic toll systems must be interoperable per MAP-21 ITS progress
- 4. Barriers to advanced ITS Solutions 6/6/2018 4 Devices Network Users • Managing explosion of new devices • Providing power (PoE) without increasing complexity • Lack of visibility of network state • Disconnect between “smart” core and “dumb” edge • Multiple departments using the same physical infrastructure with different and competing needs Staffing • Flat or shrinking headcount budgets means higher degree of automation required
- 5. Connected devices are everywhere & growing more numerous • In place: Cameras, DMS, RWIS • Coming soon: V2I devices • Many require PoE, PoE+, PoE++: injectors increase complexity 6/6/2018 5
- 6. Roadside Networks need to evolve and become “enterprise-class” 6/6/2018 6 Better management tools to facilitate troubleshooting, decrease MTTR Analytics to better understand usage trends Open, standards-based protocols like shortest-path bridging… … allows for the elimination of spanning tree, increasing reliability
- 7. NDOT “Enterprise Class” Network Architecture 6/6/2018 7 Network Operations Center OmniVista 2500 Network Management Distribution/Fiber Hut Fiber ringOS6900 OS6860E OS6865 OS6865 OS6865 OS6865 NEMA-TS2 Enclosures SPB to the edge Fully Managed from NOC Temperature Controlled • Aggregation of rings • Redundant ring connections • Support for PoE Managed switches provide high degree of visibility Spanning tree eliminated in favor of SPB High flexibility: stacking switches, ample PoE budgets OS6900 OS6900OS6900 OS6900 Temperature Controlled • Server Connections • Fiber Hut Aggregation • Core Mesh Topology Core/Data Center Edge/Hardened Switches OS6900
- 8. Conclusion • Advanced ITS Applications need ‘smart’ IP networks • ‘Smart’ networks: managed, automated, ample PoE, resilient! • We invite you to visit us in Carson City! 6/6/2018 8
Editor's Notes
- The vehicles we use on the roadways today are very different than they were 100 years ago. A lot has changed in that time. ITS is a younger technology but it has also evolved; the networks needed to run modern ITS applications are a lot different than the networks we deployed initially. I wouldn’t want to run that Pilot car on the Interstate, and I wouldn’t want to run NDOT’s ITS applications on a 10M network either!
- ITS has progressed incredibly quickly as you can see from this very brief history. DARPA’s 1985 project had an autonomous vehicle that drove through the Colorado Hills…at an average speed of 5mph. In 10 years, that technology improved to long-haul driving with the “No Hands Across America” demonstration. 10 years after that we moved out of “demo” mode and into “standards” mode with the ratification by the FCC of DSRC for autonomous vehicle operation. NDOT has been at the forefront of these ITS progressions and our latest STIP shows lots of investments in ITS projects. All of these support our mission to provide the traveling the public the info and tech they need to reach their destinations quickly and safely.
- But delivering on that mission is not without its challenges. Building an advanced ITS network like we have at NDOT is challenging for a number of reasons, some of which are outlined here. Every month brings new devices to connect to the network. And we’re really just getting started with the next wave of devices that will support V2I communications to support autonomous and assisted driving applications. These devices will need to be connected to the network, and many of them will need power. Power over Ethernet is an important consideration. With these devices, having a highly available “enterprise-class” network is crucial. Knowing what’s going on at every point in your network, core, edge, and cabinet level is mandatory. It’s no longer acceptable to have blind spots because the edge of your network is “dumb” and invisible to your operation center. Different departments will want access to your infrastructure and meeting those departmental needs without impacting the overall mission can be very challenging as they often have conflicting needs. And of course, you’re expected to cope with all this novelty with a flat or shrinking headcount. Clearly the networks need to become smarter, need to provide greater degrees of automation to allow us to cope. Old school switch by switch configuration needs to fall by the wayside.
- So let’s think about that first challenge, devices – lest you think you have lots of time, bear in mind that Toyota announced that DSRC will be implemented in all their US cars starting in the 2021 model year. Other auto manufacturers are not far behind. This will drive a tremendous uptick in the number of devices that you will need to have connected at roadside, competing with already existing cameras, DMS, RWIS. The infrastructure needed to support V2I communications is perhaps not fully defined but it’s a given that it will need network connectivity and is likely to be PoE-powered. PoE can be a headache because if your network doesn’t have ample power budget, or isn’t able to drive high-powered devices (e.g. cameras, microwave radios) then you’ll have to resort to injectors, which increase wiring complexity, introduce another point of failure and aren’t managed and hence invisible to your operations center. Not a good thing.
- NDOT has chosen to deploy what we call an “enterprise-class” roadside network to meet these challenges. This “enterprise-class” network inherits many of the standard features found in an IT network. First of all, it’s fully managed centrally from our operations center. We can see every switch, every port and perform diagnostic tests with a few clicks rather than a truck roll. In the event of an issue we can quickly figure out what’s gone wrong and perform the appropriate action and get the service back on line ASAP. We have adopted the idea of reducing service outage time, and reducing Mean Time to Recovery. This enterprise-class network also includes tools built into the management platform that allow us to see usage trends throughout the network so we can make adjustments or plan for enhancements well before they become an issue. What’s especially useful is the ability to leverage predictive analytics so we can project network usage 6 months or a year from now. It goes without saying that any network you deploy must be based on open standards so that you have the flexibility of choosing different vendors to meet your needs. One standard NDOT is particularly happy about is Shortest Path Bridging, which we use all the way to our cabinets. SPB allows us to get rid of the convergence issues that are typical of legacy networks that are based on spanning tree. We’ve completely eliminated spanning tree from our network as a result, and the reliability of the network has improved significantly as a result.
- Here you can see our end-to-end “enterprise class” network architecture from operations center to the roadside. All the switches you see here, whether they are roadside, in the fiber huts or in the data center, are all managed by the same piece of software that sits in our Network Operations Center. This visibility makes our jobs easier since it eliminates blind spots and allows us to plan much better. The vendor we’re using, Alcatel-Lucent Enterprise, supports IEEE-standard shortest path bridging throughout their networking portfolio, including in their hardened switches. This has allowed NDOT to design the network in such a way to eliminate spanning tree completely. This allows us to reduce or prevent entirely downtime in the network, be it planned or unplanned. What’s also nice about the OmniSwitch family is that there’s lots of support for PoE, including high-power PoE. This allows us to get rid of power injectors and once again improve the maintainability of the network. Added benefit of PoE connected devices is that they can be reset remotely from the Network Operations Center – so if a camera’s software freezes, we can reboot it with a click of a mouse by resetting its Ethernet port. Prevent those truck rolls!
- So to sum up, what we’ve learned at NDOT is that getting ready for the next wave of ITS applications is going to require much smarter, “enterprise-class” IP networks, from the core all the way to the cabinet. Some of the features to look for in an enterprise class network is remote management, automation of configuration activities, lots of support for PoE (and high-power PoE) all in packages that work to the roadside If you’d like to learn more, I encourage you to make a visit to our HQ in Carson City, a short drive away from Lake Tahoe and Reno, NV. We’d love to show you what we’ve done!