The  Business Operations domain describes how business units operate to deliver products (goods and services) that fit their customers needs (value).

This includes:

1) the management structure that organizes responsibility and accountability : People & Accountability.

2) the processes that describe the end to end delivery of goods and services: Organization & Processes.

The  Business Operations domain has dependencies with domains providing Business Systems used to support and automate operations: Software System ArcOps and Hardware System ArcOps.

The  SOF - Business Resource Operating Pattern (B-SOF) domain defines concepts and relationships used to model how physical resources (Business Operating Assets) operates/functions in Business Resource Ecosystems to deliver Business Outcome Events.

Business Operating Asset is an abstraction for Org-Unit, Business Software System, Concrete Hardware System and Networking System and their behaviors (Business Resource Process, Business Resource Interaction Process).

The  SOF - Business Resource Operating Pattern (B-SOF) is used as a template for all concrete operating domains such as People & Accountability or Application Functional Architecture.

The  SOF - Business System Operating Pattern domain defines concepts and relationships used to model how a Business System operates/functions in its Operating Eco-System..

It includes Business Systems, System Processes, Business System Interaction Processs,  System Rules,  Functionality(ies), Information Outcome Events.

The  SOF - Resource System Operating Pattern (R-SOF) domain is a conceptualization level that comprises abstract entities that belong to the physical space and comprise Human resources,  Software resources, Hardware resources and natural resources.

Unlike Conceptual entities (which are independent of physical implementation), Resource entities represent tangible or operational abstractions.

 Resource entities constrast with  Conceptual entities, which abstract from any physical implementation.

This level is sometimes referred to as the "Organic Level" because it deals with functional, real-world elements. For example:

. "Vision" is a Conceptual entity, abstract in nature.

. "Eye" is a Resource entity, representing its physical realization (e.g., human eyes, batrachian eyes, etc.). However, "Eye" remains an abstract resource since it encompasses multiple concrete implementations.

The Resource conceptualization level models how a Resource Agent operates/functions within its Resource Operating Ecosystem to produce Resource Outcome Events.

It includes Resource Agents, Resource Action Processes, Resource Service Interfaces,  Resource Rules, Resource Capabilitys, Resource Outcome Events.