addressing iot challenges - cisco › assets › sol › dc › day_two_close.pdf7 thursday am:...
TRANSCRIPT
1 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1
Addressing IoT Challenges Breakout Readout
Doug Merritt, SVP Product, Solutions and Industry Marketing, Cisco
2
Engagement Matrix
• Need to build trust in context
• Need to define domains for engagement (countries/ cities/ industries/ horizontal vs. vertical)
• Need to differentiate levels of urgency
• Innovation agendas
Use Cases (successes, constraints)
• Privacy and Security - Perception vs. reality - Appropriate levels
• Current vs. Future Environment
• Best practices
Group 1: Policy: Innovation Enabler or Inhibitor 10:15 – 11:45pm, February 21 Facilitator: Robert Pepper, Vice President of Government Affairs, Cisco
Framework for Fall Discussion: What is the role of IoT Policy?
3
Key Challenges
• What is balance between levels, and cost of security, that prohibit or drive companies to make the investment to move IoT forward?
• What level of security is required, and will it scale? How does it cross all industries for IoT? Smart grid/meters versus oil rigs and manufacturing
• Security spans beyond the network. How do you provide security where there is no network connectivity?
Action Steps/Opportunities
• Unify around common standards, because security is not a profit center. Only govt’s will pay. We must build it together.
• Engrave security into IoT DNA so that it is truly pervasive. Build security modules together to cross industries.
• Leverage what we already know from the Internet. Identify common practices and put them in play.
• Create Evangelism that security has to be part of IoT DNA
Group 2: Securing the Internet of Things 10:15 – 11:45pm, February 21 Facilitator: Nancy Cam-Winget, Distinguished Engineer, Cisco
4
Key Themes/Ground Truths
• Fragmented networks require collaboration to resolve – 10-20 year duty cycles; competition; different use case scenarios; vested interests.
• Many dimensions of performance need context or event based modelling
• Intelligent endpoints and clouds will not be the answer. Systems will require more distributed computing, storage and services.
Action Steps/Opportunities
• Architecture as an exploration enabling technologies – building blocks – instead of standards solutions or systems.
• Distribute capabilities throughout the network. More hierarchical systems that enable use-case/ context driven requests for service.
• Let working implementations drive and shape standards.
Group 3: Technical Challenges: Architecting IoT 10:15 – 11:45pm, February 21 Facilitator: JP Vassuer and Flavio Bonomi, Cisco Fellows
We need to pursue a new reality in networking. It is likely multiple networks for the near-term future. We should continue to look to the opportunities for consolidation over time on common platforms.
5 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 5
Internet of Things World Forum Steering Committee Meeting February 20-21, 2013
6
Wednesday PM: Defining IoT Opportunities • Urban: IoT will be both infrastructure driven and services driven
• Agility and rapid development is imperative
• Government can enable—provide a platform and engagement for private innovation
• Ecosystem will drive business value
• Create platforms as aggregators of data at local level, and move up the stack
• Top-down driven transformation is required
• Bottom-up use-case scenarios will drive understanding, innovation, ecosystem
• To accelerate the market, standards, security and policy must be addressed
7
Thursday AM: Addressing IoT Challenges • Security, security, security: Appropriate levels of security and privacy
• Build security modules together –into IoT DNA—to cross industries.
• Differentiate policy priorities (and everything else) based on use cases
• Architect around a building block metaphor – instead of standards solutions or systems
• Let working implementations drive and shape standards
• Distributed Intelligence—computing, storage and services
8
Thursday PM: Accelerating IoT Impact Group 1: Creating a Platform for IoT
• Takeaway: Taxonomy is critical; interoperability testing is critical; need common operating system
Group 2: Roadmap for Technology Standards
• Takeaway: Standards should be horizontal based. For example: transport, security, management, interoperability
Group 3: Navigating Disruption
• Takeaway: IoT is not a technology disruption; it is a business model disruption.
9
Pace of Adoption
10
Define Technology Architectures
Orient around Buying Centers
Educate the Ecosystem
Standards, Policy, and Regulation
Awaken to the Possible
Enable Business Innovation
Six Things We Need to Do as an Industry
11
Objectives
• Build momentum and sense of urgency for Internet of Things
• Create a platform for IoT industry acceleration and innovation – place to meet and exchange ideas
• Foster cross-industry, cross-discipline innovation and best practices
• Address horizontal issues across verticals • Accelerate standardization • Articulate “the” IoT Platform
INTERNET THINGS
12
Themes So Far . . . Horizontal • Security/policy/privacy
• Platform requirements
• Standards
• Policy acceleration • IT/OT partnership
• Ecosystem management
Industry • Use cases and best practices
• New user experiences
• Vertical platform requirements
• Public-Private Sector cooperation
• Legacy integration
13
Steps to the World Forum • IoT World Forum Steering Committee community
• Industry awareness by announcing the World Forum location/dates
• Follow on meetings to establish agenda, work groups and tracks
Your Role
• Participate in the community and working groups
• Shape agenda topics and tracks
• Develop the ecosystems
• Educate your constituents
INTERNET THINGS
14
Location Short List
• London (Oct 7) • Amsterdam (Oct 21)
• Barcelona (Oct 28)
• Copenhagen (Oct 7)
INTERNET THINGS
15
Call to Action
• Actionable Industry Roadmaps • Partnerships to propel the industry • IoT Education • Active participation in the World Forum • Think and dream big
INTERNET THINGS