1. GCTC Transportation Super Cluster Smart City SDK
February 2, 2017
Presented by: Dr. Martin J. Burns
National Institute of Standards and Technology
Engineering Laboratory
Smart Grid and Cyber-Physical Systems Program Office

2. Overview
Pivotal Points of Interoperability (PPI) enable agreeing on somethings not everything
NIST CPS Framework – the “algebra” of the Internet of Things
How IES-City Framework is working to “reveal” PPI
What this means for Open Source

3. IoT-Enabled Smart City Framework
Smart City technologies are being developed and deployed at a rapid pace and most smart city deployments are custom solutions.
A number of architectural design efforts are underway worldwide but have not yet converged.
NIST and its partners are convening a public working group to distill a common set of architectural features from these architectural efforts and city stakeholders.
Goal: Facilitate the development of incremental and composable Smart Cities

4. Pivotal Points of Interoperability - PPI
If you standardize everything, you freeze out innovation.
If you standardize nothing, you get non-interoperable clusters that can’t be easily integrated.
The principle of Pivotal Points of Interoperability is to find consensus standardized interfaces that deal with composition of CPS without constraining innovation.

5. Pivotal Points of Interoperability (PPI)
Independent technology deployments
With Pivotal Points of Interoperability
PPI
Minimize distance to interoperability
e.g. REST APIs
PPI
e.g. Convert XML to JSON
e.g. TLS 1.2
Application Diversity
PPI
Potentially large distance to interoperability
e.g. IPv6 address

6. NIST CPS Framework cyber physical system-of-systems system device
human
Action
Physical State
Decision
cyber
physical
Info
Interactions

7. Facets Aspects Activities Artifacts Domains CPS Framework
Conceptualization
Realization
Assurance
Functional
Business
Human
Trustworthiness
Timing
Data
Boundaries
Composition
Lifecycle
Activities
Artifacts
Use Case, Requirements, …
Model of a CPS
Design / Produce / Test / Operate
CPS
Argumentation, Claims, Evidence
CPS Assurance
Manufacturing
Transportation
Energy
Healthcare
. . . Domain
Domains
CPS Framework

8. How to Discover Consensus
OneM2M
FIWARE
Architecture/Framework A
Architecture/Framework B
Possible Gaps
Possible Extension Points
Common Pivotal Points of Interoperability
Process:
Transform architectures to CPS Framework normal form
Transform deployments to CPS Framework normal form
Compare results of 1) and 2)
Broaden consensus of intersections
Document Smart Cities Framework
Union of Applications
CVRIA
Architecture/Framework C

9. Aspects CPS Property Tree Cyber Concern 1 Confidentiality Security
CPS Properties / Solution Model
CPS Aspects and Concerns
CPS Property Tree
Cyber
Security
Physical
Confidentiality
Integrity
Availability
Concern 1
Concern 3
Concern 2
Encryption
Safety
Reliability
Security
Resilience
Privacy
Aspects
Functional
Business
Human
Trustworthiness
Timing
Data
Boundaries
Composition
Lifecycle
A secure, privacy protected message exchange might consist of the simultaneous (set of) properties: {Trustworthiness.Security.Cybersecurity.Confidentiality.Encryption.AES, Trustworthiness.Privacy.Predictability.Controls.Authorization.OAuth}
AES
OAuth
Concern n+1
Concern n+2
Authorization
Controls
Transparency
Innovation
Predictability
Manageability
Dissociability

10. Specs to Pivotal Points of Interoperability
Requirements

11. Zones of Concern: From Requirements To Services
Zone of Concerns = bundles of services that address a “vector” of concerns
E.g. CyberSecurity Zone of Concerns: Authorization service + Confidentiality Service

12. OpenSource and City SDK
Open Source allows for the ready availability of reusable building blocks
Zones of concern can be assembled for offering using these components
The availability of well understood building blocks encourages an ecosystem of deployers, operators, and maintainers for smart city apps
These together minimize the barriers to penetration of smart city technologies to benefit citizens

13. Thanks!