Subtitle: Fusing Enterprise IoT and Traditional Enterprise Architecture
External IoT – External world of devices, events, connections, storage, and analysis; the “traditional” Internet of Things; the world of devices outside the enterprise.
Internal IoT – Internal world within the enterprise consisting of business processes, business objects, actors and roles; application components, application services, application functionality, and data objects; and lastly, infrastructure consisting of servers, networks, data stores, foundation services, and foundational functionality. The “hum” within an Enterprise.
Enterprise IoT – The confluence or integration of External IoT and Internal IoT landscapes centered around a particular enterprise organization. Often represented and accessed as an enterprise graph.
Ecosystem IoT – The confluence or integration of 2 or more separate Enterprise IoT landscapes (complete or partial) centered around a specific ecosystem or community. Supporting Federated Enterprise Architecture.
Do some of these latter terms sound familiar? If so, you likely have some exposure, background, and experience with the practice of Enterprise Architecture Management (EAM). Having lived on both sides of the IoT divide for more than a decade, it’s interesting to watch how the current rage around IoT is almost exclusively focused on External IoT and it’s coupling to Business Intelligence and Analysis.
What about what’s happening inside the business, information, application and infrastructure architecture of our own enterprises? …regardless of whether the “things” are internal to your organization, external to your organization, or, possibly, part of someone else’s organization (e.g. owned by a client, customer, partner, …), it’s all part of the Enterprise IoT landscape.
A good name for the combination of External IoT and Internal IoT is the “Enterprise of Things” …but another organization is already using this term.
Ultimately, this is all about the Internet of Things merged and being combined with Enterprise Architecture Management: Enterprise IoT.
“More news at 11…”
Michael Herman (Toronto)
4 responses to “External IoT vs. Internal IoT: Beware of the Hype Cycle”
Here’s a copy of a humorous postscript I added to a recent email:
p.s. I’m downtown tomorrow afternoon. Do you work from an office or are you an “Internet thing”? 🙂
Pingback: FYHumor: A list of humorous IoT sightings | hyperonomy.com
Pingback: Crossing the EA Chasm: “Where does IoT fit in?” | hyperonomy.com
Are you limiting your scope or definition of a Device to hardware devices? Why can’t Device also include a Business Processing emitting state change, performance, usage or any other type of telemetry information? …or the same for a SharePoint, SAP, or Salesforce application?