Woots and the Enterprise Digital Genome

The Physical World Was Becoming Part of the Enterprise System

For much of the enterprise software era, business systems were designed around internal records. ERP systems managed resources. CRM systems tracked customers. Supply chain systems managed movement. BPM systems modeled workflows (Davenport, 1993; Hammer & Champy, 1993). These systems were powerful, but they were largely separated from the live conditions of the physical world.

By the mid-2010s, that separation was beginning to collapse.

Everyday objects were becoming identifiable, addressable, readable, and controllable through networks. Sensors, smart labels, smartphones, connected machines, and embedded devices were turning the physical environment into a source of continuous digital signals (Atzori et al., 2010; Mulligan, 2010). The BPM Everywhere chapter framed this shift as the immersion of the physical world into the virtual world, where people, things, and processes would leave behind rich digital traces of their activities and interactions (Reddy, 2015).

The important realization was that these signals were not just data. They were evidence of how the enterprise actually lived, moved, served, failed, recovered, and adapted.

A shipment was no longer just a record in a logistics system. It could become a living object with location, temperature, motion, condition, custody, and history. A product was no longer just an SKU. It could carry a digital memory of how it was manufactured, transported, stored, used, serviced, and recycled (Wahlster, 2013). A customer was no longer just a profile in CRM. The customer’s journey could be understood through interactions across channels, devices, environments, and moments of intent (Peppers & Rogers, 2011). A process was no longer just a workflow diagram. It could become a context-aware system responding to real-world conditions.

This was the core architectural shift: the enterprise was becoming a cyber-physical system (Lee, 2008).

Why BPM Had to Evolve

The article appeared in a BPM context because business processes are the bridge between strategy and execution. But traditional BPM was designed for a more stable world (vom Brocke & Rosemann, 2015; Davenport, 1993).

In a connected environment, processes cannot remain static. They must respond to events, exceptions, signals, and context (Ackoff, 1971; Senge, 1990).

If a temperature-sensitive product begins to degrade during transport, the process should not wait for a human to discover the issue after delivery. If a patient misses a medication measurement, the care process should not remain silent. If a customer’s behavior changes across channels, the engagement process should adapt. If a supply chain disruption begins to propagate, the enterprise should sense it early.

That was the reasoning behind integrating IoT, analytics, cloud, and machine learning into business process intelligence. The BPM Everywhere chapter argued that enterprises had invested heavily in ERP, CRM, and other technology-enabled systems, but those systems had not fully engaged stakeholders and ecosystem partners for real-time sensing and anticipatory decision support (Reddy, 2015).

Enterprise systems had become efficient, but not yet sufficiently aware.

The future of BPM, therefore, was not simply better workflow automation. It was intelligent process adaptation.

Woots: Smart Things as Process Participants

The concept of Woots emerged from this need.

Woots were not imagined as gadgets. They were imagined as intelligent participants in enterprise processes. A Woot was an everyday thing with identity, addressability, presence, sensing capability, communication capability, and enough intelligence to participate in a broader system (Reddy, 2015; Arsénio et al., 2014).

The original architecture described Woots as smart things with the ability to self-organize and communicate with other things, with or without human intervention. It also introduced the idea that Woots would be supported by a cloud-based Semantic Digital Memory that could provide context awareness, autonomy, business process intelligence, and reactivity (Reddy, 2015; Wahlster, 2013).

The design principle was important: intelligence did not have to be fully embedded in every device. The architecture separated concerns cleanly.

Each layer had one job.

This allowed smart things to remain simple while participating in sophisticated business behavior. That architectural choice still matters. The more we connect the physical world, the more important it becomes to avoid overloading every device with unnecessary complexity. Intelligence should be distributed intelligently: some at the device, some at the edge, some in the cloud, some in the enterprise workflow, and some in human judgment (Weiser, 1991; Reddy, 2015).

The Enterprise Digital Genome

The larger idea behind Woots was EDGE: the Enterprise Digital Genome.

EDGE was an attempt to name the living pattern of the enterprise.

Every enterprise generates traces: customer interactions, product movements, process events, sensor readings, transactions, machine signals, employee actions, social data, partner activity, environmental conditions, and operational exceptions. These traces are usually fragmented across systems. But if they are connected, enriched, interpreted, and made actionable, they become something more than data. They become a genome.

The metaphor mattered. A genome is not merely a collection of parts. It is an encoded pattern that shapes behavior, adaptation, and identity (Watson et al., 2004). Similarly, an enterprise digital genome encodes the relationships among customers, products, processes, assets, people, environments, and outcomes.

The BPM Everywhere chapter positioned EDGE as a cloud-based smart-things operating system designed to improve interoperability, reduce architectural complexity, and integrate processes, people, and things (Reddy, 2015). It also linked EDGE to the Big Data Foundry work and the broader open innovation effort around connected enterprises, smart cities, and smart environments.

The deeper thesis was this: enterprises need a common intelligence layer that can connect physical-world signals with business-process execution.

Without such a layer, every application builds its own partial view. Every department defines its own data. Every device speaks its own language. Every workflow reacts only to the signals it already knows. The enterprise becomes connected at the network level but fragmented at the meaning level (Weick, 1995).

EDGE was designed to solve the meaning problem.

Semantic Memory: Giving Things a History

One of the most important ideas in the BPM Everywhere chapter was Semantic Digital Memory.

Smart things should not merely emit events. They should accumulate meaningful histories. A product, asset, device, or physical object should have a persistent digital diary that captures its lifecycle, interactions, conditions, and changes over time (Reddy, 2015; Wahlster, 2013).

The chapter described Semantic Digital Memory as a way to associate product-related information with a physical object in an application-independent manner. This memory could include history, usage, real-world events, sensor readings, machine-to-machine updates, and human interactions, making the object’s information reusable across applications and environments (Wahlster, 2013; Hribernik et al., 2011).

This was a powerful concept because many enterprise decisions require history, not just current state.

A wine shipment exposed to heat is not the same product it was when it left the warehouse. A medical device used in a care pathway is not just equipment; it is part of a patient’s context. A machine that has been vibrating abnormally for three weeks carries a different risk profile than one that has just produced a single alert. A customer who has interacted across mobile, store, service, and social channels has a richer context than a single CRM entry can represent.

Semantic memory turns events into context. And context is what makes intelligent action possible (Klein et al., 2006; Weick, 1995).

From Data Streams to Context-Aware Action

The BPM Everywhere chapter also recognized one of the hardest challenges of IoT-era enterprise architecture: not all data streams are useful in advance.

In traditional enterprise systems, data sources are often predefined. But in connected environments, useful signals may emerge from unexpected combinations of devices, places, times, events, or correlations. The chapter argued that data streams from new devices need to be recognized through affinities of place, time, and correlation so they can form useful information neighborhoods (Reddy, 2015; Atzori et al., 2010).

The enterprise should not merely collect sensor data. It should discover which signals matter together.

Signals become meaningful in combination.

The value is not in the individual signal. The value is in the relationship among signals (Getoor & Taskar, 2007; Robinson et al., 2013).

This is where Big Data, machine learning, semantic modeling, and BPM begin to converge.

Why Systems Thinking Was Essential

The article was deeply influenced by systems thinking (Senge, 1990; Ackoff, 1971).

A connected enterprise is not a linear machine. It is a system of systems. People, machines, processes, devices, partners, customers, and environments interact in ways that produce emergent behavior (Holland, 1995; Stacey, 2007).

Traditional architecture often simplifies these relationships too much. It assumes clean boundaries, stable workflows, predefined data flows, and predictable exceptions. But smart environments do not behave that way.

The BPM Everywhere chapter argued that systems thinking is necessary because enterprises are overwhelmed by complexity and must understand the interconnections among business processes, systems, people, things, variables, actions, and decisions (Reddy, 2015; Meadows, 2008).

That was the real reason for introducing Woots and EDGE. They were not only technology constructs. They were systems constructs.

They asked: how do we design an enterprise that can perceive its environment, understand relationships, adapt to change, and act with greater intelligence?

Augmented Intelligence, Not Blind Automation

Another important principle was that IoT is ultimately about human augmentation.

Adding sensors does not magically make an enterprise smarter. Sensors create visibility, but intelligence emerges only when humans, interfaces, machines, models, and processes work together (Licklider, 1960; Kahneman, 2011). The BPM Everywhere chapter explicitly framed IoT as a context-oriented world enabled by better data and emphasized the complex interplay of humans, interfaces, and machines (Reddy, 2015).

This was an early expression of a belief that has remained central to this work: the goal is not to remove humans from the system. The goal is to give humans better context, better timing, better insight, and better ability to act. In complex environments, full automation can be dangerous if the system does not understand context.

But purely manual processes are too slow when signals arrive continuously (Sheridan, 2002). The answer is augmented intelligence: machines sense, detect, classify, recommend, and coordinate; humans interpret, judge, decide, and govern. Woots and EDGE were designed around that balance.

The EDGE Operating System for the Smart Enterprise

The BPM Everywhere chapter used the phrase “operating system” deliberately. The enterprise needed more than a collection of IoT applications. It needed a common layer for connecting data, processes, devices, and intelligence (Reddy, 2015; Weiser et al., 1999).

EDGE was described as an architecture for seamless interaction among applications and smart spaces. It included the notion of a “global brain” that could provide context awareness, autonomy, business process intelligence, and proactive behavior. In practical terms, EDGE was meant to:

collect signals from people, things, and systems; integrate data from enterprise and external sources; enrich those signals with meaning; use machine learning and reasoning to detect patterns; convert insights into actions; support process execution; and preserve context as enterprise memory (Reddy, 2015; Bollacker et al., 2008).

This made EDGE a bridge between the physical world and enterprise decision-making. It was not just IoT middleware. It was not just analytics. It was not just BPM. It was not just cloud. It was an early attempt to define an enterprise intelligence operating layer.

The Business Value: Anticipatory Enterprise Operations

The larger business promise was anticipatory action. The EDGE approach would allow leaders to see facts, trends, and patterns through a new lens, shifting from forecasting toward anticipatory thinking (Reddy, 2015; Hamel & Prahalad, 1994). That distinction is important. Forecasting often extrapolates from the past. Anticipatory thinking reads weak signals in the present.

A connected enterprise should not only ask: what happened? It should ask: what is beginning to happen? And then: what should we do before the outcome becomes irreversible?

That is the business power of Woots and EDGE.

In manufacturing, this could mean protecting product quality before damage becomes visible. In healthcare, it could mean coordinating care before a risk becomes an emergency. In retail, it could mean adjusting offers based on real-time context. In logistics, it could mean rerouting assets before delays cascade. In cities, it could mean responding to emerging congestion, safety, or infrastructure signals (Atzori et al., 2010; Manyika et al., 2011).

The common thread is the same: context-aware intelligence translated into timely action.

The Enduring Thesis

Looking back, the BPM Everywhere chapter was about much more than smart objects.

It was about the beginning of a new enterprise model.

The enterprise was making six moves at once.

Woots represented the intelligent edge of this future. EDGE represented the enterprise operating layer needed to make that edge meaningful.

The thesis can be summarized this way: as the physical world becomes digitally connected, enterprises need a new architecture that allows people, things, processes, and data to operate as one intelligent system. Smart things must carry identity, context, and memory. Business processes must become adaptive and event-aware. Cloud and Big Data must be connected to real-world signals. And the enterprise must develop a digital genome that allows it to sense, understand, and act with greater speed, precision, and intelligence (Reddy, 2015; Senge, 1990; Weick, 1995).

That was the heart of the Woots article. It was written in the language of IoT, BPM, cloud, Big Data, and smart environments. But its deeper concern was enterprise intelligence: how organizations could become more aware, more adaptive, and more capable of acting in a world where every object, person, process, and environment was beginning to speak.

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

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

Bollacker, K., Evans, C., Paritosh, P., Sturge, T., & Taylor, J. (2008). Freebase: A collaboratively created graph database for structuring human knowledge. In Proceedings of the 2008 ACM SIGMOD international conference on management of data (pp. 1247–1250). ACM. https://doi.org/10.1145/1376616.1376746

Davenport, T. H. (1993). Process innovation: Reengineering work through information technology. Harvard Business School Press.

Getoor, L., & Taskar, B. (Eds.). (2007). Introduction to statistical relational learning. MIT Press.

Hamel, G., & Prahalad, C. K. (1994). Competing for the future. Harvard Business School Press.

Hammer, M., & Champy, J. (1993). Reengineering the corporation: A manifesto for business revolution. HarperBusiness.

Holland, J. H. (1995). Hidden order: How adaptation builds complexity. Addison-Wesley.

Hribernik, K. A., Hans, C., Kramer, C., & Thoben, K.-D. (2011). A service-oriented, semantic approach to data integration for an Internet of Things supporting autonomous cooperating logistics processes. In D. Uckelmann, M. Harrison, & F. Michahelles (Eds.), Architecting the Internet of Things (pp. 131–158). Springer. https://doi.org/10.1007/978-3-642-19157-2_6

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

Lee, E. A. (2008). Cyber physical systems: Design challenges. In Proceedings of the 11th IEEE international symposium on object and component-oriented real-time distributed computing (pp. 363–369). IEEE. https://doi.org/10.1109/ISORC.2008.25

Licklider, J. C. R. (1960). Man-computer symbiosis. IRE Transactions on Human Factors in Electronics, HFE-1(1), 4–11. https://doi.org/10.1109/THFE2.1960.4503259

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.

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

Peppers, D., & Rogers, M. (2011). Managing customer relationships: A strategic framework (2nd ed.). Wiley.

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

Robinson, I., Webber, J., & Eifrem, E. (2013). Graph databases. O’Reilly Media.

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

Sheridan, T. B. (2002). Humans and automation: System design and research issues. Wiley.

Stacey, R. D. (2007). Strategic management and organisational dynamics: The challenge of complexity (5th ed.). Pearson Education.

vom Brocke, J., & Rosemann, M. (Eds.). (2015). Handbook on business process management 1: Introduction, methods, and information systems (2nd ed.). Springer.

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. (2004). Molecular biology of the gene (5th 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