The Enterprise Genome

Woots: When Things Became Participants in Business Processes

The first formal expression of this thesis was a chapter I wrote for the book BPM Everywhere: Business Process Management in the Connected Enterprise (Reddy, 2015), published by Future Strategies. The chapter was titled “Smart Things That Can Think, Act, Learn, and Talk” and introduced both the Woots concept and the EDGE architecture to a practitioner audience working at the intersection of IoT, business process management, and enterprise intelligence.

The argument began with a straightforward observation: the Internet was acting as a ubiquitous communication fabric enabling the fast-paced immersion of the physical world into the virtual world (Reddy, 2015; Mulligan, 2010). Internet-enabled devices of all kinds were paving the way for everyday objects, including sidewalks, traffic lights, products, and medical devices, to become identifiable, readable, addressable, and even controllable through networks (Reddy, 2015; Weiser et al., 1999). People, things, and processes running in this connected world were leaving behind vast digital footprints. The Internet had become the common fabric of interconnection among everything.

I called these intelligent connected objects Woots: Web of Open Things. These were everyday things with significant intelligence, a specific identity, address, and presence on the Internet, with the capability to self-organize and communicate with other things with or without human intervention (Reddy, 2015).

The architectural idea was practical rather than speculative. Rather than embedding complex application logic into devices, the approach recommended moving that logic to the cloud. On the device side, thin servers with RESTful APIs provided simple interfaces to sensor and actuator functions. The richer intelligence, covering context, memory, cooperative machine learning, analytics, and process coordination, lived in the surrounding platform (Reddy, 2015; Arsénio et al., 2014).

A key innovation was the Semantic Digital Memory (SDM): a cloud-based persistent digital diary associated with each physical object, capturing its history, interactions, and contextual data across its entire lifecycle. By embedding sensors, communication, and computing capabilities into physical products, those products could seamlessly gather and use information throughout their lives and communicate meaningfully with other objects and human users (Reddy, 2015; Wahlster, 2013).

The Pulse component sat at the network edge, aggregating data feeds from physical and logical sensors and overlaying them with enterprise intelligence to help leaders better engage customers, deliver innovations, and create context-aware experiences. Pulse nodes were designed for self-organization, discovery, and dynamic routing. Rather than traditional hub-and-spoke architectures, they used a publish/subscribe model capable of handling the scale and heterogeneity of IoT data streams (Reddy, 2015).

This work was part of the experimental open innovation platform called the Big Data Foundry, which I co-founded with PARC, Cisco, and Hitachi. It was designed to be part of the Global Real-time Analytics Centers of Excellence being set up across the U.S., Singapore, and Australia (Reddy, 2015).

That led to the idea of EDGE: the Enterprise Digital Genome operating system. It was a cloud-based architecture designed to improve interoperability, reduce architectural complexity, and facilitate the integration of processes, people, and things (Reddy, 2015). In 2015 terms, this was a connected-enterprise architecture: IoT, business process intelligence, semantic memory, cloud computing, and machine learning working together (Armbrust et al., 2010; Atzori et al., 2010).

Systems thinking was the explicit intellectual frame for this work. Following Senge (1990) and Ackoff (1971), the chapter argued that systems thinking was essential for understanding the interconnections among business processes, people, things, and the variables affecting them, and for challenging existing system boundaries to integrate emerging technology trends coherently (Reddy, 2015).

But the deeper idea was larger than the architecture:

If every thing, process, person, and interaction leaves a digital trace, the enterprise itself begins to develop a living digital memory.

The Enterprise Genome: From Digital Traces to Organizational Meaning

The Enterprise Genome patent took that idea further and gave it formal structure.

The patent application, published as US20160371591A1 in December 2016, was titled “System and method for creating biologically based enterprise data genome to predict and recommend enterprise performance” (Reddy & Koduru, 2016). It listed Surendra Reddy and Vamsi Koduru as inventors, claimed priority to a provisional application filed on June 20, 2015, and was later granted as US10311376B2 on June 4, 2019 (Reddy & Koduru, 2019).

The patent framed the Enterprise Genome as a KPI-driven digital genome system. Its purpose was to go beyond conventional KPI dashboards by continuously measuring, correlating, and discovering hidden relationships among metrics, attributes, causal relationships, and networks (Reddy & Koduru, 2016). That was the central departure from traditional business intelligence:

• A KPI tells you what changed.

• A dashboard shows you where performance is above or below target.

• A report summarizes the state of the business.

None of these automatically explain the underlying relationships that caused the change. The Enterprise Genome was designed to map those relationships. It treated enterprise entities as nodes, relationships as edges, and contextual relevance as something that could be scored, labeled, and interpreted. The patent described methods for identifying attributes, measures, and thresholds that influence financial, operational, and innovation outcomes; extracting and contextualizing those measures from enterprise data; mapping entities and relationships; and creating ontologies and semantic maps of enterprise entities (Reddy & Koduru, 2016).

This was the move from performance monitoring to enterprise sensemaking (Weick, 1995).

Why the Genome Metaphor Mattered

The word genome was deliberate.

A genome is not simply a collection of parts. It is a relational code that influences how a living system develops, behaves, responds, and adapts (Watson et al., 2014). The enterprise has a similar hidden structure. Customers, products, processes, employees, partners, transactions, assets, policies, risks, and markets are not isolated objects. They influence one another. A customer experience problem may be connected to inventory, pricing, staffing, logistics, supplier reliability, or process design. A compliance failure may be connected to data quality, workflow fragmentation, policy interpretation, analyst workload, or system latency.

Traditional dashboards flatten this complexity (Davenport & Harris, 2007). The Enterprise Genome was an attempt to preserve it.

The patent described the digital genome map as analogous to a biological genome, where nodes and edges carry signals of varying strength and together provide a map of organizational behavior (Reddy & Koduru, 2016). That was the heart of the insight:

The enterprise is not just a set of systems. It is a living network of relationships. To manage it intelligently, leaders need more than visibility. They need a map of meaning.

The Problem With Static Dashboards

By 2015 and 2016, many enterprises had invested heavily in ERP, CRM, data warehouses, BPM tools, analytics platforms, and dashboards. These systems created value, but they also created fragmentation (Davenport, 2006). Enterprise information was spread across ERP systems, data warehouses, web clickstreams, CRM systems, spreadsheets, and other files, creating a growing gap between the speed at which data became available and the ability of business users to make sense of it (Reddy & Koduru, 2016).

That was the operating reality of the big data era. The issue was not lack of data. The issue was the widening gap between data availability and human comprehension (McAfee & Brynjolfsson, 2012).

Business professionals were spending enormous time consolidating, reconciling, and interpreting data. Meanwhile, organizations needed faster decisions, better customer engagement, stronger operational efficiency, and more adaptive execution (Manyika et al., 2011). The Enterprise Genome proposed a different model: instead of asking users to manually assemble meaning from fragmented data, the system would create a contextual map of measures, indicators, attributes, relationships, and outcomes.

It was not another dashboard. It was an attempt to build the enterprise’s underlying intelligence model.

From KPIs to Key Indicators in Context

The patent did not reject KPIs. It argued that KPIs had been weakened by fragmented implementation and superficial use (Eckerson, 2010). Performance indicators are powerful when they connect organizational objectives to measurable outcomes. But when they become isolated numbers on a screen, their intelligence value declines (Parmenter, 2015). The patent argued that performance indicators should help users understand what action to take, what may be contributing to subpar performance, and where opportunities for improvement exist (Reddy & Koduru, 2016).

That required context. A metric becomes useful when it can be connected to the processes, people, customers, products, and risks that influence it. The Enterprise Genome sought to make indicators role-aware, process-aware, and relationship-aware, applying context at department, team, and individual levels (Reddy & Koduru, 2016).

Metrics needed to stop being abstract numbers. They needed to become navigational instruments that guided people toward root causes, dependencies, opportunities, and action.

From Woots to Enterprise Genome

The Woots chapter and the Enterprise Genome patent were not separate ideas. They were two layers of the same architecture.

• Woots focused on the edge of the enterprise: smart things, sensors, smart labels, mobile devices, and connected environments.

• EDGE focused on the operating layer connecting smart things, people, processes, and data.

• Enterprise Genome focused on the semantic and causal structure of the enterprise itself.

Woots made the physical world readable. The Enterprise Genome made the organization interpretable. Together, they pointed toward an enterprise that could sense and learn, which is what Senge (1990) called a learning organization, now made structurally possible through connected data and machine intelligence.

The Role of Machine Learning

In the 2015–2020 period, machine learning was becoming increasingly relevant to enterprise systems, but the practical challenge was embedding it usefully inside decision workflows (Domingos, 2015).

The Enterprise Genome patent described machine learning and AI methods for learning, reasoning, inference, prediction, probabilistic determination, and statistical determination. It described inference as the process of reasoning about the state of a system, environment, or user from events and data (Reddy & Koduru, 2016; Russell & Norvig, 2021). The system was designed to:

• Identify hidden relationships

• Generate hypotheses

• Connect events from multiple sources

• Score relevance

• Support prediction

• Recommend next-best actions

The goal was not to replace business judgment. It was to give business users better context, faster discovery, and stronger decision support (Davenport & Ronanki, 2018). Augmented intelligence, not automated intelligence.

Sensemaker: Applying the Thesis to Financial Crime Intelligence

By 2017, the same architecture began appearing in a more specific and high-consequence domain: financial crime intelligence.

The Sensemaker platform was designed to augment human investigators by ingesting large volumes of structured and unstructured data, surfacing anomalies, tracing relationships, and uncovering hidden narratives using NLP, machine learning, semantic modeling, graph analysis, time-series intelligence, and natural language generation (Reddy, 2017). Financial institutions had enormous amounts of data, but investigators still struggled with fragmented systems, alert fatigue, false positives, and hidden relationships, a problem well documented in the AML and financial crime literature (FATF, 2019; Palermo, 2014).

Sensemaker was not a simple automation tool. It was a human-machine collaboration system (Kahneman, 2011; Sheridan, 2016). That distinction mattered. The goal was to make investigators more effective, not to remove them from the loop.

The throughline became clear:

• Woots explored how the physical world could generate meaningful signals.

• The Enterprise Genome explored how an organization could map the relationships among those signals.

• Sensemaker explored how a platform could help humans interpret those signals in a complex, high-stakes decision environment.

The 2015–2020 Architecture

Looking across the period, the architecture can be understood as four connected layers:

This was not yet the language of later AI platform categories. It belonged to the cloud, IoT, big data, BPM, analytics, machine learning, and regulatory intelligence era. But the core belief was clear:

Why This Mattered

The Enterprise Genome mattered because it challenged the dominant assumption that more data and better dashboards would automatically create better decisions. They would not (Davenport & Harris, 2007; McAfee & Brynjolfsson, 2012).

Enterprises needed a way to connect data to context, context to relationships, relationships to meaning, and meaning to action. The four-layer architecture, covering sensing, memory, genome mapping, and sensemaking, formed a practical thesis for the 2015–2020 enterprise:

The enterprise is becoming a connected, sensing, learning system. Its products, customers, processes, devices, employees, partners, and risks all generate signals. Those signals need to be mapped into context. That context needs to reveal relationships. Those relationships need to support better decisions. And those decisions need to continuously improve the system.

The Enduring View

By 2020, the arc from Woots to Enterprise Genome to Sensemaker had become clear.

Woots gave the enterprise new senses. The Enterprise Genome gave it a structure of memory and meaning. Sensemaker gave it a method for human-machine interpretation. The larger thesis was never about technology alone. It was about a new kind of enterprise capability: the ability to understand the business as a living system and to act with greater awareness, speed, and precision (Meadows, 2008; Senge, 1990).

That was the promise of the Enterprise Genome. Not another report. Not another dashboard. Not another isolated analytics application. A way for the enterprise to read its own signals, understand its own patterns, and improve its own performance.

References

Ackoff, R. L. (1971). Towards a system of systems concepts. Management Science, 17(11), 661–671. https://doi.org/10.1287/mnsc.17.11.661

Armbrust, M., Fox, A., Griffith, R., Joseph, A. D., Katz, R., Konwinski, A., Lee, G., Patterson, D., Rabkin, A., Stoica, I., & Zaharia, M. (2010). A view of cloud computing. Communications of the ACM, 53(4), 50–58. https://doi.org/10.1145/1721654.1721672

Arsénio, A., Serra, H., Francisco, R., Nabais, F., Andrade, J., & Serrano, E. (2014). Internet of intelligent things: Bringing artificial intelligence into things and communication networks. In I. Besimi & S. Loshkovska (Eds.), Advanced research in data privacy (pp. 1–37). Springer. https://doi.org/10.1007/978-3-642-35016-0_1

Ashton, K. (2009). That “Internet of Things” thing. RFID Journal, 22(7), 97–114.

Atzori, L., Iera, A., & Morabito, G. (2010). The Internet of Things: A survey. Computer Networks, 54(15), 2787–2805. https://doi.org/10.1016/j.comnet.2010.05.010

Berners-Lee, T., Hendler, J., & Lassila, O. (2001). The semantic web. Scientific American, 284(5), 34–43. https://doi.org/10.1038/scientificamerican0501-34

Davenport, T. H. (2006). Competing on analytics. Harvard Business Review, 84(1), 98–107.

Davenport, T. H., & Harris, J. G. (2007). Competing on analytics: The new science of winning. Harvard Business School Press.

Davenport, T. H., & Ronanki, R. (2018). Artificial intelligence for the real world. Harvard Business Review, 96(1), 108–116.

Domingos, P. (2015). The master algorithm: How the quest for the ultimate learning machine will remake our world. Basic Books.

Eckerson, W. W. (2010). Performance dashboards: Measuring, monitoring, and managing your business (2nd ed.). Wiley.

Financial Action Task Force. (2019). Guidance for a risk-based approach to virtual assets and virtual asset service providers. FATF/OECD.

ITU. (2005). The Internet of Things: Executive summary. International Telecommunication Union.

Jordan, M. I., & Mitchell, T. M. (2015). Machine learning: Trends, perspectives, and prospects. Science, 349(6245), 255–260. https://doi.org/10.1126/science.aaa8415

Kahneman, D. (2011). Thinking, fast and slow. Farrar, Straus and Giroux.

Klein, G., Moon, B., & Hoffman, R. R. (2006). Making sense of sensemaking 1: Alternative perspectives. IEEE Intelligent Systems, 21(4), 70–73. https://doi.org/10.1109/MIS.2006.75

Manyika, J., Chui, M., Brown, B., Bughin, J., Dobbs, R., Roxburgh, C., & Byers, A. H. (2011). Big data: The next frontier for innovation, competition, and productivity. McKinsey Global Institute.

McAfee, A., & Brynjolfsson, E. (2012). Big data: The management revolution. Harvard Business Review, 90(10), 60–68.

Meadows, D. H. (2008). Thinking in systems: A primer. Chelsea Green Publishing.

Mulligan, G. (2010). The Internet of Things: Here now and coming soon. IEEE Internet Computing, 14(1), 35–36. https://doi.org/10.1109/MIC.2010.19

Palermo, G. (2014). Financial crime investigation and control. Journal of Financial Crime, 21(1), 1–11.

Parmenter, D. (2015). Key performance indicators: Developing, implementing, and using winning KPIs (3rd ed.). Wiley.

Pérez, I. C., & Barbolla, A. M. B. (2014). Exploring major architectural aspects of the Web of Things. In A. Bahga & V. Madisetti (Eds.), Internet of Things, smart sensors, measurement and instrumentation (Vol. 9, pp. 23–54). Springer. https://doi.org/10.1007/978-3-319-04223-7_2

Reddy, S. (2015). Smart things that can think, act, learn, and talk. In L. Fischer (Ed.), BPM everywhere: Business process management in the connected enterprise (pp. 1–28). Future Strategies. http://www.futstrat.com/books/BPMEverywhere.php

Reddy, S. (2017). Sensemaker: Augmented intelligence for financial crime. Quantiply Corporation.

Reddy, S., & Koduru, V. (2016). System and method for creating biologically based enterprise data genome to predict and recommend enterprise performance (U.S. Patent Application No. US20160371591A1). U.S. Patent and Trademark Office.

Reddy, S., & Koduru, V. (2019). System and method for creating biologically based enterprise data genome to predict and recommend enterprise performance (U.S. Patent No. US10311376B2). U.S. Patent and Trademark Office.

Russell, S., & Norvig, P. (2021). Artificial intelligence: A modern approach (4th ed.). Pearson.

Senge, P. M. (1990). The fifth discipline: The art and practice of the learning organization. Doubleday.

Sheridan, T. B. (2016). Human–robot interaction: Status and challenges. Human Factors, 58(4), 525–532. https://doi.org/10.1177/0018720816644364

Wahlster, W. (2013). The semantic product memory: An interactive black box for smart objects. In W. Wahlster (Ed.), Semantic product memories (pp. 1–24). Springer. https://doi.org/10.1007/978-3-642-37377-0_1

Watson, J. D., Baker, T. A., Bell, S. P., Gann, A., Levine, M., & Losick, R. (2014). Molecular biology of the gene (7th ed.). Pearson.

Weick, K. E. (1995). Sensemaking in organizations. Sage Publications.

Weiser, M. (1991). The computer for the twenty-first century. Scientific American, 265(3), 94–104. https://doi.org/10.1038/scientificamerican0991-94

Weiser, M., Gold, R., & Brown, J. S. (1999). The origins of ubiquitous computing research at PARC in the late 1980s. IBM Systems Journal, 38(4), 693–696. https://doi.org/10.1147/sj.384.0693