Presentation from the Open Group Conference in San Diego

1. The Value of Architecture and The Internet of Things
Microsoft Services – Enterprise Strategy
alan.hakimi@microsoft.com
http://blogs.msdn.com/zen
@alanhakimi

2. The content presented in this session may or may not represent the
views of my employer, Microsoft Corporation.
The content is designed to be a “value-add” to “things” that most
Enterprise Architects are already doing… but it also addresses the
shortcomings of current thinking in relation to the Internet of Things
My world view comes from complexity theory, organizational design
systems thinking, and socio-technological computing, and enterprise
architecture.

3. Provide a introductory perspective on the value of
architecture around the Internet of Things.
Share some working concept and methods that may help
drive hi level architecture transformation around the
Internet of Things
Set the stage for future discussions on what we must do to
make this a reality.

5. System Value
DesignExecution

6. IoT Ecosystem
System Value
DesignExecution

7. A ginormous opportunity for Enterprise Architecture
Professionals.
Connectivity Data AnalyticsThings

8. 1970 1980 1990 2000 2010
10,000,000,000
1,000,000,000
100,000,000
10,000,000
1,000,000
100,000
10,000
1,000
Transistors
Moore’s Law continues Metcalf‘s Law
what can 25 billion connected things do?
1980 1990 2000 2010
1,000

9. The IoT will significantly transform our digital interactions
with the physical world, therefore people’s experiences are
at center of the conversation.
The information journey from data to wisdom and
providing insights to individuals or teams will help drive
efficiency in both work and life processes.
The foundations of and IoT Ecosystem are ubiquitous
computing and ambient intelligence.

10.  Have data (structure)




 Have code (behavior)



 and context
Simple Thing
Thing of Things
Sense
Thing
Code
Data
Actuator
Sensor
Respond
Streams
Algorithms / Configurations
Thing
Code
Data
Actuator
Sensor
Thing
Code
Data
Actuator
Sensor
Sense
Respond
Thing
Code
Data
Actuator
SensorSense
Respond
Sense
Respond
Streams
Algorithms / Configurations
Data
Code
< >
Hub / Gateway
Pulled
Pushed
Code
Data
Pulled
Pushed
Code
DataSensor
Actuator

11.  What is information?



 Why is this important?




Data

12.  What is Code?


 Why is it Important




Code

13. Can accomplish some pretty amazing things…..
But…. we need to build better architectures within our
own and other enterprises in order to reduce friction
and help serve our clients….

14. Operational
Things
Information
Things
Convergence

15. 2Rules
1 Every new product and service [SYSTEM]
must provide great experience and excellent
value—it works and flows.
2 But each [SYSTEM] must also reduce the
complexity and increase the value of all of
the others. Things work together.

16. ubiquitous
computing
cognitive
organizations business and life
infrastructure
architecture
business and
information
architecture

17. Strategy and
Direction
Command
and Control
Team
Interactions
Individual
Activity
World
Impact

18. Environment Agent “The Brain”
sense
respond
streams
pattern
collecting
reasoningmanipulate
change
percepts
action insight
telemetry
reflective
activities
reflexive
activities
Uniqueness
Dynamic
Variability
Specialized
High Rate of Change
Analysis and Speed
Real Time Decisions
Sameness
Static
Common
Generalized
Low Rate of Change
Synthesis of Insights
Design Time Designs

19. ubiquitous
computing
cognitive
organizations business and
life
environment individuals teams management leadership
market
(opportunity)
products and
services
(value)
business and life
(capability)
information
(certainty)
applications
(functionality)
technology
(modality)

20. ubiquitous
computing
cognitive
organizations business and
life
leadershipmanagementteamsindividualsenvironmentenvironment individuals teams management leadership
market
(opportunity)
demand scenario relationships throughput industry /
competition
products and
services
(value)
components assemble / service supply chain product / service
offering
marketing /
portfolio
business and life
(capability)
impact tasks processes /
interactions
command / control strategy
information
(certainty)
signals / data information knowledge understanding wisdom
applications
(functionality)
collection productivity collaboration reporting insights
technology
(modality)
sensors
actuators
devices networks storage processing

21.  Standardization Around Connectivity and Data
 Federated Frameworks, Models, and Methodologies
The We Can Evaluate and Simulate
 Evolve The Notion of Architecture Beyond Standards
and Governance

22. Architecture Value
System Value
DesignExecution

23. Can we use architecture to
deliver better products?
Can we use architecture to
drive business efficiency?
Can we use architecture to
guide the right solutions?
Can we use architecture to
provide a seamless and quiet
integration with technology?
The Right Advantage
The Right Product
The Right Cost
The Right Speed
The Right Risk

24. Process
Efficiency
Cost
Reduction
IoT is all about
providing INSIGHTS
Develop
New Business
Models

25. Predicting future performance from historical data
Recommenda-
tion engines
Advertising
analysis
Weather
forecasting for
business planning
Social network
analysis
IT infrastructure
and web app
optimization
Legal
discovery and
document
archiving
Pricing analysis
Fraud
detection
Churn
analysis
Equipment
monitoring
Location-based
tracking and
services
Personalized
Insurance
Predictive analytics should
address the likelihood of
something happening in
the future, even if it is just
an instant later…

26. SynthesisAnalysis

27. Insights
Reporting
Evaluating
Measuring
Collaboration
and Process
Interactions and
Types
Symbols and
Reading

28.  Human Experience
throughout the “product”
lifecycle.
 The design is based upon an
explicit understanding of users,
tasks, and environments.
 Users are involved through
design and development
 The design is driven and refined
by user-center evaluation
 The process is iterative
 The design addresses the whole
user experience.
 The design team includes
multidisciplinary skills and
perspectives.
Above is from ISO 9241-210 (201) Human Center
Design for Interactive Systems
Purpose Autonomy Mastery
Success Community Collaboration
Social
Individual
Experience

29. Business
Case

30. Purpose Means Results Value Drivers
Provide New (Capability,
Functionality, Modality)
Produce Something New New Product or
Service
Value Expectation
Improve Something Existing Enhanced Product of
Service
Understand Constraints,
Barriers and Obstacles to
Achieve Desired Outcome
Address Limiting Factors Smart Governance
and Compliance and
Enablement
Opposing Forces
Identify and Manage Risk Reduce Risk of
Operation
Manage and Cope with
Anticipated and
Unanticipated Change
Exploit New Opportunities Marketplace
Competitiveness
Change Catalyst
Adapt Quickly To New
Conditions
Organizational
Change Management

31. Robust functionality requires
essential complexity.
Can we provide it without
unnecessary
complicatedness?
Value expectations and
limitations are like Yin and
Yang, if there are no
obstacles, the value is less
because the outcome is easy.

33. Architecture Design
Considerations System Value
DesignExecution

34. Descriptive Quality
Prescriptive Quality
Predictive Quality

35. Telemetry is fundamental in operating a healthy and
learning system.
Solving the architectural problem is not enough,
feedback is required to determine to determine both
short term and long term viability.
Application of
telemetry to
a solution
Surfacing of
telemetry from
a solution
Transporting
telemetry
Creation of a
telemetry data
marketplace
and routing
Standarised
consumption
including real-time
Insight creation
Design Emit Transport Ingest Consume Insights

36. The Analog Physical
World
The Digital Virtual
World

37. temporal relation temporal relation
x before y x starts y
y contains x y started by x
x overlaps y x finishes y
x meets y y finished by x
x equals y
Environmental Based Trigger
Time Based Trigger
Location Based Trigger
Object Based Trigger

38. What Events are on The Edge?
What Events are the Core?

39. antifragile
f(x)
harmful beneficial



40. Architecting
Transformation System Value
DesignExecution

41. Results
Realization
Viewpoints
Transformation
Viewpoints

42.  Evangelize the Importance of Holistic Systemic Architecture and It Processes
to Modernize Business
 Leverage Human Experience and Business Architecture Together
 Understand The Consumption Metrics of What You Are Building
 Modern Architecture Frameworks Must Address All Things.
 We Must Develop Better Cadence on How Architecture Delivers Outcomes.
 There Is No End State Just a Series of Potential Next States

43. Thank You