Understanding Enterprise Architecture and the Role of APQC’s Process Classification Framework
The article explains enterprise architecture as a practice of modeling and managing organizational, process, system, data, and product/service models, discusses how these models converge, emphasizes the importance of governance, and shows how APQC’s PCF and the cloud‑based MosaiQ tool can accelerate EA work while also providing community links for further discussion.
What Is Enterprise Architecture?
Enterprise architecture (EA) is described as the practice of modeling an enterprise and managing the related models, encompassing organization, process, system, data, and product/service models.
Models Within Enterprise Architecture
The article lists common EA models: organization structure, process model, system architecture, data model, and product/service portfolio, noting that these are interrelated aspects of the enterprise.
Convergence of Models
It explains that isolated models eventually converge—organization models define processes, data models inform system architecture, and process models include data and system aspects. Proper governance of this convergence yields consistency and cost reduction, while lack of governance can cause problems.
Being Part of the Process
The author argues that understanding the organization’s processes is essential for grasping the relationships among all other models, emphasizing that processes should often be prioritized.
Simple Integration with MosaiQ
APQC’s cloud‑based MosaiQ tool, launched in 2016, is presented as a solution to create and manage custom process frameworks, preventing redundant work and enabling seamless linking of organization models to process elements.
The article concludes with links to various community platforms (WeChat groups, QQ groups, video channels, etc.) for deeper discussion on enterprise architecture and related emerging technologies.
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.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.