Intelligent Computing Systems: How will Enterprise Architecture Evolve?

Intelligent Computing Systems: How will Enterprise Architecture Evolve?

As I have discussed in prior blogs, the focus of enterprise computing for most of the 20th century was on deploying Systems of Record, first on mainframes, then minicomputers, then client-server systems. These were and continue to be the transaction processing backbones that drive global commerce. In the first fifteen years of this century, however, we have seen a profound shift in spending emphasis away from Systems of Record, which are now in maintenance mode, and toward Systems of Engagement, the focus being on connecting with customers, partners, and employees in digitally effective ways leveraging the ubiquity of smart phones. That movement has been inside the tornado for some time now such that, while there will be a lot of money spent here over the next ten years, I think it is time to look ahead to the next wave. That’s the one driven by big data, machine learning, the Internet of things, and artificial intelligence (for additional context, see a prior blog post “Machine Learning is From Mars, Artificial Intelligence is from Venus”).

In talking about this next wave with Qi Lu, formerly head of Office Applications at Microsoft, now Chief Operating Officer at Baidu, one of the key questions that came up is, how will real-world enterprises integrate these next-generation technologies into their established legacy systems? To help address this issue Qi proposed a high-level enterprise architecture that I have sketched out below. Its purpose is to call out the various zones of investment and to show how they can fit into a single coherent system. Here are the key points.

No alt text provided for this image

Systems of Record still are the anchor tenant in any enterprise information system architecture, but now they need to interoperate with Systems of Engagement so that businesses can leverage the digital capabilities consumers have become so accustomed to. This is no small feat as Systems of Engagement are designed to be accessible and Systems of Record need to be unhackable—how can each operate effectively and efficiently without holding the other back? The answer appears to be some version of a micro-services-based architecture running on top of an inter-system bus such that each type of system can connect with the other at arms’ length yet in real time. How one develops, deploys, and secures such an architecture is a work in progress, but the basic idea seems sound enough.

The next step, the one that initiates the next wave, comes from post-processing the log files from Systems of Engagement in combination with the data from Systems of Record in order to discover or detect actionable circumstances relevant to the enterprise’s mission. Today in most enterprises such post-processing work is confined within the IT function itself, focused on improving operations and security. That said, all the great business disrupters of the past decade have taken things far beyond IT’s walls. Amazon, Google, Microsoft, Apple, Tesla, Uber, Airbnb, Netflix—they are all running Systems of Observation against the data flows they are privileged to access or host, and then feeding them into Systems of Intelligence to extract insights from them. 

Today’s Systems of Intelligence are largely focused on machine learning, not artificial intelligence. Deep neural networks, in particular, are extracting complex patterns from highly unstructured data—notably video imagery and speech—which, when combined with transactional records allows disruptive companies to take their business performance to a whole other level. One of the key points in Qi’s diagram is that from a Dev/Ops point of view, it is important to separate Systems of Observation, more in the realm of the Internet of Things, from Systems of Intelligence, more in the realm of analytics, because each stresses the compute fabric in dramatically different ways. 

So now, instead of just two zones to manage, there are a total of four. Moreover, if any of these extracted insights are going to be used to optimize transactions, they have to be fed back into Systems of Engagement and Systems of Record. All this calls for a platform solution, one Qi has labeled a System of Operation. This is the point of insertion where the IT organization asserts its control over the interactions among the prior four systems. In this new order, although there is a natural flow of data and processing following the diagram from left to right, each of the four data processing systems must iterate and interoperate with the other three to learn, improve, and perform, all under a common set of protocols and governance rules.

Needless to say, there are boatloads of technology involved across this entire landscape that are far beyond my ability even to describe, much less prescribe. However, I expect that may also hold true for many enterprise CIOs who come to their position through a line-of-business as opposed to a technical route. The value of the Intelligent Computing Systems framework is that it helps a business-oriented generalist understand where investments need to be made and in what order. That is, without Systems of Engagement log files, there is little need for a System of Observation or a System of Intelligence—you can just use a data warehouse and traditional Business Intelligence analytics. With the advent of log files, on the other hand, you are now well and truly in the world of big data, which creates demand for the twin engines of a System of Observation and a System of Intelligence. Here you want to be careful to keep these two separate to optimize for performance, or you may end up getting surprised with a whopping bill from your favorite cloud computing provider. And finally, we all need to remember that machine learning itself has to be given time and space to learn so that ensuring it can iterate back and forth among the various systems critical to getting the training outcomes needed to make a material contribution to enterprise success.

All in all this is a lot to digest. For the time being, I hope that this framework can at least help you organize your meals.

That’s what I think. What do you think?

Geoffrey Moore Mailing List

______________________________________________________________________

Geoffrey Moore | Zone to Win | Geoffrey Moore Twitter | Geoffrey Moore YouTube

Great article......

Kingsley Uyi Idehen

Founder & CEO at OpenLink Software | Advancing Data Connectivity, Multi-Model Data Management, and AI Smart Agents | Unifying Disparate Data Silos via Open Standards (SQL, SPARQL, RDF, ODBC, JDBC, HTTP, GraphQL)

6y

Great post, that provides a nice segue into the following realms to executive level managers: [1] Basic Data Virtualization -- providing a common interface to disparate data originating from Systems of Record and Systems of Engagement [2] Conceptual Data Virtualization -- providing a Semantic Web of Linked Data that serves the needs of both Systems of Observation and Systems of Intelligence. Links to a few posts that hopefully but my points into perspective: [1] https://kidehen.blogspot.com/2015/07/conceptual-data-virtualization-across.html -- Conceptual Data Virtualization [2] https://medium.com/openlink-software-blog/swagger-the-api-economy-rest-linked-data-and-a-semantic-web-9d6839dae65a -- REST, APIs, and a Semantic Web of Linked Data [3] https://medium.com/openlink-software-blog/semantic-web-layer-cake-tweak-explained-6ba5c6ac3fab -- Revised Semantic Web Layer Cake (important role of language and logic in data integration) [4] https://www.quora.com/What-is-the-purpose-of-data-virtualization/answer/Kingsley-Uyi-Idehen -- Why is Data Virtualization Important answer on Quora #DataVirtualization #SemanticWeb #LinkedData #DataIntegration #SmartData

Like
Reply
Stephen Olatunji

Software Engineering Manager | ASP.NET Core | C# | NodeJs | Angular

6y

Great article.

Like
Reply
Kumud Kalia

CIO | CTO | COO | Advisor | Board Member

6y

This will certainly take time to digest :) Some dimensions that should be considered here: Many SoRs were conceived, implemented, operated as on-premise systems, well controlled for regulations such as SOX, with high levels of data reliability, much of which has to be reproduced intact after several years. Not so with SoEs which are often cloud-based, not as stringently controlled, and with data that is often superseded and quickly obsoleted. These are very different data types, static vs transient, if you will, and the Observation/Intelligence concepts obscure the fact that just combining these data types is itself a challenge - before producing meaningful results! Add in system-to-system interactions happening without human engagement; delivery of customized insights to end-users in real-time (preferably on their mobile device of choice); correlation or combination with various other asynchronous data which will not be in structured systems (social, IoT) while respecting privacy and geo concerns; self-tuning algos; learning systems that spawn new code or even new apps spontaneously...this is bewildering for anyone! Lots still to learn...

Munish Gupta

PwC Partner/Principal | Driving Business Model Transformation & Revenue Growth Through Cloud & Digital Innovations

6y

I agree with your thoughts and in fact I published an article on a similar topic last week. https://www.linkedin.com/pulse/future-path-enterprise-apps-goes-through-cognitive-automation-gupta-1 The key is the orchestration across SoR, SoE and SoI to realize true value from digital business.

Like
Reply

To view or add a comment, sign in

Insights from the community

Others also viewed

Explore topics