Operations 5 min read

Salesforce Operating, Governance, and Architecture Framework (SOGAF): Applying the MIT‑CISR Enterprise Architecture Model

The article introduces the Salesforce Operating, Governance, and Architecture Framework (SOGAF), explains its two‑dimensional operating model—process standardization and integration—describes four model types (Diversify, Replicate, Coordinate, Unify), provides guidance on selecting the appropriate model, and highlights contributor Martin Griffiths' expertise in enterprise architecture.

Architects Research Society
Architects Research Society
Architects Research Society
Salesforce Operating, Governance, and Architecture Framework (SOGAF): Applying the MIT‑CISR Enterprise Architecture Model

Introduction

SOGAF (Salesforce Operating, Governance and Architecture Framework) applies the MIT‑CISR Enterprise Architecture framework to Salesforce implementations and programs.

The operating model has two dimensions: business process standardization and business process integration . Standardizing processes and related systems means precisely defining how a process should be executed, which improves overall company efficiency and predictability.

Integration of business processes through shared data connects the work of organizational units. This data sharing can enable end‑to‑end transaction processing or provide a unified customer experience, delivering benefits such as higher efficiency, better coordination, increased transparency, and greater agility.

Operating Model Types

SOGAF defines four operating models:

Diversify – different processes and different data

Replicate – same processes, different data

Coordinate – different processes, shared data

Unify – same processes, shared data

The appropriate operating model depends on the level of process standardization and the required degree of data integration. The chosen model drives the technical capabilities needed across the enterprise.

How to Choose an Operating Model

Selection depends on whether business processes are identical and whether data is shared among the business units shown in the decision tree. In practice, companies often sit on a continuum between two of the four models.

About the Contributor

Martin Griffiths is the Director of Business Architecture at Salesforce. With a bilingual French‑English background, he has 30 years of experience in CRM, ERP, and digital transformation, covering business consulting, enterprise architecture, and project delivery. His focus is on guiding complex Salesforce‑based transformations, operating models, and governance using academic frameworks.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Salesforceoperating modelSOGAF
Architects Research Society
Written by

Architects Research Society

A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.