Systemic approach towards enterprise functional decomposition


Published on

Kudryavtsev, D., & Grigoriev, L. (2011). Systemic approach towards enterprise functional decomposition. The proceedings of the Workshop “Convergence of Business Architecture, Business Process Architecture, Enterprise Architecture and Service Oriented Architecture” within the 13-th IEEE Conference on Commerce and Enterprise Computing (CEC), September 5-7, 2011, Luxemborg. P. 310-317.

Published in: Business, Education
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Systemic approach towards enterprise functional decomposition

  1. 1. Systemic Approach Towards Enterprise Functional Decomposition Dmitry Kudryavtsev, Lev Grigoriev 20 11 Workshop “Convergence of Business Architecture, Business Process Architecture, Enterprise Architecture and Service Oriented Architecture”
  2. 2. About the company <ul><li>BUSINESS ENGINEERING GROUP SPb </li></ul><ul><li>Consulting </li></ul><ul><li>Organizational design, strategic management, business process improvement and re-engineering, enterprise architecture management, quality management </li></ul><ul><li>Products </li></ul><ul><li>ORG-MASTER® line of software products for organizational design and analysis </li></ul><ul><li>GOV-MASTER ® software for public organizations design and analysis </li></ul><ul><li>Seminars and Trainings </li></ul><ul><li>Business engineering School, School of business analysts, Business ideology school </li></ul><ul><li>Research </li></ul><ul><li>Models and methods of organizational design, enterprise engineering and modeling </li></ul><ul><li>History: management consulting, enterprise modeling software and trainings since 1997 </li></ul><ul><li>Customers: large and medium-sized CIS business and public organizations </li></ul>
  3. 3. Outline <ul><li>What is “enterprise functional decomposition”? </li></ul><ul><li>Requirements for the decomposition </li></ul><ul><li>Currently available models and methods </li></ul><ul><li>The suggested framework </li></ul><ul><ul><li>terminology, </li></ul></ul><ul><ul><li>main principles, </li></ul></ul><ul><ul><li>process / method. </li></ul></ul><ul><li>IT support </li></ul><ul><li>Implementation </li></ul><ul><li>Framework benefits </li></ul>
  4. 4. What is “enterprise functional decomposition”?
  5. 5. What is “enterprise functional decomposition”? <ul><li>“ Functional decomposition identifies the high-level functions of an organization or proposed solution and then breaks down those processes into sub-processes and activities. This can be done as part of a systems development or business process analysis project. The goal is to break functions down into smaller pieces to allow for analysis of the detail processes and to ensure coverage of all significant processes” - A Guide to Business Analysis Body of Knowledge, 2006 </li></ul><ul><li>“ Functional decomposition – a technique for mastering the complexity of the function of a system. The effect of applying the technique is that a functional model of a (sub)system is replaced by a set of functional models? Also called functional subsystems, and vice versa. Where functional model is a black-box model of a concrete system and function is the set of services the concrete system is able to provide” - Jan Dietz, “Enteprise Ontology Theory and Methodology,” 2006. </li></ul>
  6. 6. Functional decomposition role in enterprise engineering Purpose Structure Principles and rules IT-architecture, Technical architecture, People, Organizational structure Mission, Vision, Goals, Strategies, CSF, KPI Value chain, functions, business processes, activities Functional decomposition Function
  7. 7. Requirements for the decomposition System engineering driven Business practice driven Completeness and Necessity (“Do right things”), Correct understanding of semantics (e.g. what does “maintenance management” mean?) Consistency (e.g. avoid overlapping activities…) <ul><li>Support for management best practice: </li></ul><ul><li>Widely-used reference models, </li></ul><ul><li>Methodologies (TQM, VBM…). </li></ul><ul><li>Regulatory compliance (ISO, SOX…) </li></ul>
  8. 8. Requirements for the decomposition <ul><li>In more technological form: </li></ul><ul><li>Activities follow its’ purposes - alignment with the enterprise intentional model (for completeness check, prioritizing), </li></ul><ul><li>Reuse of the proven and shared normative models or knowledge (reference models, patterns, etc), </li></ul><ul><li>Consistency of principles within functional decomposition, </li></ul><ul><li>Value-based management harmonization, </li></ul><ul><li>ISO 9004:2009 harmonization. </li></ul>
  9. 9. ISO 9004:2009 harmonization
  10. 10. Value-based management harmonization
  11. 11. Currently available models and methods <ul><li>Reusable elements for enterprise functional decomposition </li></ul><ul><li>APQC Process Classification Framework, SCOR, ITIL, CBM… </li></ul><ul><li>Lifecycle models </li></ul><ul><li>= starter kit and building blocks, </li></ul><ul><li>require supplementary method </li></ul><ul><li>B. Methods for enterprise functional decomposition </li></ul><ul><li>Goal-oriented ( Kavakli and Loucopoulos) </li></ul><ul><li>Beer’s Viable System Model (VSM) based </li></ul><ul><li>Normative model driven (e.g. Barros) </li></ul><ul><li>Need to be integrated and extended. </li></ul>
  12. 12. The framework: terminology <ul><li>Functional system – purposeful system, which consists of activity elements and has the following features: </li></ul><ul><li>purpose as the main system-forming factor, </li></ul><ul><li>self-regulating – it includes a management component/activity elements, </li></ul><ul><li>hierarchy – it consists of other functional systems, </li></ul><ul><li>isomorphism – all the functional systems have a similar structure. </li></ul><ul><li>where: </li></ul><ul><li>Activity element – any element of enterprise activities description, e. g. process, action, functional area. </li></ul><ul><li>Purpore - high level, overall goal of a system. The role of an object within superior system. </li></ul>
  13. 13. The framework: main principles Strategy & Policy Design & Improvement Operational planning Measure-ment, Analysis, Control Management Enabling systems Value creation Functional system’s pattern Natural resources Finance People in the organization Infrastructure Environment Knowledge Information technologies
  14. 14. The framework: main principles
  15. 15. Alignment of functional system pattern with purposes and goals Stakeholder’s concerns Goals of the functional system Goals of value creation elements Goals of managerial and enabling behavior help achieve help achieve provide Purposes Functional system
  16. 16. All the pattern components are harmonized with ISO 9004:2009
  17. 17. Value-based management (VBM) harmonization Functional system Corporate level Business level Functional area level Features Corporate system Business system (Functional area-level) Functional system Beneficiary Shareholders, Investors Customer Superior system, Internal client Purpose area (value type) Corporate value Customer value + Profit Value for superior system, Value for internal clients Key performance indicators Economic Value Added (EVA), Value Creation Index (VCI) EBITDA, Return-on-Assets (ROA), Free Cash Flow (FCF) Depend on the functional area. Value creation elements Business system, Corporate governance, Environmental health, safety and social responsibility management. Inbound Logistics, Operations, Outbound Logistics, Marketing & Sales, Service. Depend on functional area.
  18. 18. Corporate system pattern Legend:
  19. 19. Business system Legend:
  20. 20. (Functional area-level) Functional system Legend:
  21. 21. Pattern-based enterprise functional decomposition Corporate system Business system Functional systems Functional subsystem Business- lines Corporate strategy / goals Business strategies / goals Functional strategies / goals
  22. 22. The framework: process <ul><li>Identify functional systems and subsystems within business system </li></ul><ul><li>Identify functional systems and subsystems within corporate system </li></ul><ul><li>Identify subsystems and processes </li></ul>
  23. 23. The framework: process <ul><li>Identify functional systems and subsystems within business system </li></ul><ul><ul><li>1.1. Describe customer-oriented value chain/stream in terms of interacting functional systems, </li></ul></ul><ul><ul><ul><li>Usage of existing reference models (VRM, SCOR, APQC), lifecycle models and patterns. </li></ul></ul></ul><ul><ul><li>1.2. Identify groups of managerial processes, </li></ul></ul><ul><ul><li>1.3. Identify enabling functional systems. </li></ul></ul><ul><li>Identify functional systems and subsystems within corporate system </li></ul><ul><ul><li>2.1. Describe corporate-level value chain/stream </li></ul></ul><ul><li>Specify and/or fine-tune corporate system pattern </li></ul><ul><ul><li>2.2. Identify groups of managerial processes </li></ul></ul><ul><ul><li>2.3. Identify enabling functional systems </li></ul></ul><ul><li>Identify subsystems and processes </li></ul><ul><ul><li>3.1. Describe value creating subsystems or processes within functional systems </li></ul></ul><ul><li>Usage of generic (e.g. APQC) and domain-specific reference models (e.g. ITIL), lifecycle models. </li></ul><ul><ul><li>3.2. Generate operational planning processes for value-creating components of functional systems </li></ul></ul><ul><ul><li>3.3. Choose and customize the required processes from Design & improvement, Strategy & Policy and Paradigm groups of processes for functional systems. </li></ul></ul><ul><ul><li>3.4. Identify managerial processes for business system, </li></ul></ul><ul><ul><li>3.5. Identify managerial processes for corporate system. </li></ul></ul>
  24. 24. IT support - The ORG-Master business architecture engineering tool Ontology-based enterprise model editor Ontology-based enterprise model Reporting and query module Documents Diagrams ORG-MASTER ® Modeling process wizard Integration wizard Diagram editor Query results Semi - structured data OWL
  25. 25. Knowledge Process Creation and Acquisition Formalization Distribution Use Knowledge acquisition forms Analytical reports Structured Administrative documents Y Query answering Internal Representation Structured Administrative documents Х Local knowledge acquisition organizational models The ORG-Master business architecture engineering tool Ontology-based organizational model
  26. 26. Knowledge Process Creation and Acquisition Formalization Distribution Use Text X Tables Y Text Y Graphics Y Internal Representation Tables X Graphics X Pseudo-Graphics The ORG-Master business architecture engineering tool Ontology-based organizational model
  27. 27. Implementation <ul><li>Ilim Group, Koryazhma Branch, </li></ul><ul><li>Omskiy Repair plant ( RMZ Gazprom Neft-Omsk Refinery LLC ), </li></ul><ul><li>CottonClub </li></ul><ul><li>+ current clients </li></ul>
  28. 28. Implementation example <ul><li>Ilim Group, Koryazhma Branch </li></ul>Problem: Equipment reliability drop Breakdowns happened often   unplanned equipment downtime increased
  29. 29. Implementation example <ul><li>Solution - maintenance system reengineering project: </li></ul><ul><li>Develop maintenance system concept, strategy and measures; </li></ul><ul><li>Redesign organizational structure, </li></ul><ul><li>Identify maintenance processes and raise their maturity, </li></ul><ul><li>Optimize the key maintenance processes; </li></ul><ul><li>Information system improvement; </li></ul><ul><li>Formalize and enhance key maintenance operations; </li></ul><ul><li>Develop organizational documentation. </li></ul>Maintenance system functional decomposition
  30. 30. Implementation example <ul><li>Maintenance system functional decomposition helped </li></ul><ul><li>to clarify responsibilities during organizational structure redesign, </li></ul><ul><li>to identify maintenance processes and check their list for completeness, </li></ul><ul><li>to deploy functional strategy. </li></ul><ul><li>Functional system pattern </li></ul><ul><li>provided consistent description of different systems, </li></ul><ul><li>helped to embed planning and improvement activities in every functional system and to make mid-level managers responsible for these activities. </li></ul>
  31. 31. Implementation example <ul><li>Overall effects of the maintenance system reengineering project: </li></ul><ul><li>40 percent decrease in the unplanned equipment downtime; </li></ul><ul><li>Increased manageability and performance; </li></ul><ul><li>Repair times reduced; </li></ul><ul><li>Increased equipment reliability. </li></ul>
  32. 32. Framework benefits (1/3) Recursive decomposition using single activities pattern Similar structure of activities at different level of detail and in different functional areas Causal links between activity elements (in addition to hierarchy) Rapid management maturity growth Ease communications between managers Reuse of company’s internal knowledge Corporate standards Better organizational design
  33. 33. Framework benefits (2/3) Purposeful decomposition “ Do right things” Realize strategy quicker with less resources Clear priorities in decision-making Set causal links between activity elements
  34. 34. Framework benefits (3/3) ISO 9004:2009 Harmonization Reuse managerial best-practice Guarantee for sustainable growth Ease the certification process VBM Harmonization Better satisfy key stakeholders Corporate value growth
  35. 35. The END Questions? 20 11 [email_address] , [email_address]