Presentation template for ea & bpm 2015 06-14-001
•Download as PPTX, PDF•
1 like•980 views
![presentation template
for EA & BPM
tyuan@gate.sinica.edu.tw
[version: 2015-06-14-001][Last updated: 2015-06-14]](https://image.slidesharecdn.com/presentationtemplateforeabpm2015-06-14-001-150614171926-lva1-app6891/85/Presentation-template-for-ea-bpm-2015-06-14-001-1-320.jpg)
Recommended
More Related Content
Similar to Presentation template for ea & bpm 2015 06-14-001
Similar to Presentation template for ea & bpm 2015 06-14-001 (20)
More from Tein Horng Yuan
More from Tein Horng Yuan (20)
Recently uploaded
Recently uploaded (14)
Presentation template for ea & bpm 2015 06-14-001
- 1. presentation template for EA & BPM tyuan@gate.sinica.edu.tw [version: 2015-06-14-001][Last updated: 2015-06-14]
- 2. High level business model for ASITS ASITS Function blackbox deliverablerequirement Business motivation Service listService list Service list End-to-end trigger event value
- 3. 組織基本活動三層關係圖Foundation for goals, 7 issues-1 Business layer Business driver Business value Management layer Operation layer deliverable accountabilityrequirement transformation
- 4. 組織基本活動三層關係圖Foundation for goals, 7 issues-1 Business layer Business driver Business value Management layer Operation layer requirement report to process deliverable requirement transformation business alignment process accountability accountability requirement transformation solution realization process
- 5. 部分 ASITS 營運趨動力 國際公約、契約 政府目標、政策、法規、 契約 AS 目標、行政規則、 政策、契約 ASITS 主辦業務 政策 行政規則 三層需求 契約 管理、治 理報告 業務評估 調整服務 AS campus- wide 執行 IT系統變更
- 6. 好的治理增加營運系統的透明度及營運價值 Under Control, Jacob Lamm, ISBN: 978-1-4302-1592-9
- 7. Business context viewBusiness in Context, David Needle, ISBN: 978-1-84480-613-3
- 8. 以 The Open Group 的 The Cloud Ecosystem Reference Model 做類比，預視可能的服務關連 http://www.opengroup.org/cloud/cloud/cloud_ecosystem_rm/index.htm
- 9. 我們可能可以如何處理
- 10. EA與BPM合作Combining Business Process Management and Enterprise Architecture for Better Business Outcomes Claus T. Jensen, Owen Cline, Martin Owen , ISBN: 978-0738435619
- 12. ISO/IEC 42010:2007 “Systems and software engineering -- Recommended practice for architectural description of software-intensive systems” 前身 IEEE 1471:2000 --- http://www.iso.org/iso/catalogue_detail.htm ?csnumber=45991
- 13. OMG Business Motivation Model v1.1 Overview引自 OMG BMM manual http://www.omg.org/spec/BMM/
- 14. APQC – Process Classification Framework The American Productivity and Quality Center https://www.apqc.org/
- 16. Oregon State Gov – DAS management map http://www.oregon.gov/DAS/pages/strategic_business.aspx
- 18. Scenario: New business capability Holistic view, system thinking 一個組織所有的活動 (activity) 都是有動機、有目的，是追求價值 (value) 的，活動 裡有非常多的決策。決策影響組織的規劃 (planning)、設計 (design)、執行 (execution)、… 呈現在管理 (management)及治理 (governance) 工作上。 遠觀組織的活動，可見到繁複 (complicated) 的人事物的操作，只要組織持續產出 產品，就可稱為一個系統。 如此系統存在可明確描述 (describable, measurable) 的個體 (entity) 及個體間的關係 (relationship)。當組織的利害關係人了解 (understanding) 這一切，利害關係人可以 掌握組織活動的動機到目的間所有活動的全貌 (holistic view) 及來龍去脈 (business context) 獲得對整個組織的相關營運系統 (operation system) 的透視 (insight)。 當組織外在影響因素變多，內部因應機制隨之變多，整個營運系統的複雜度 (complexity) 變高 ，許多議題及事務變得繁複及複雜 (complicated and complex)。 如何採取有效手段透徹了解組織內外系統性質，使得組織營運得以面對變遷 (change) 的挑戰，使得組織呈現營運機敏性質 (business agility) 仍然能持續產出， 成為當代經營管理的重點工作。
- 19. 基本運作準則 • 都從企業營運整體 (holistic) 系統 (system) 觀察 • 出發點一定是弄清楚現況: as-is • 注意 end-to-end 的議題 • 遇到任何人事物議題，都用組織基本活動三層關係檢視
- 20. EA & BPM Enterprise Architecture “Enterprise Architecture is a well-‐defined practice for conducting enterprise analysis, design, planning, and implementation, using a holistic approach at all times, for the successful development and execution of strategy. Enterprise Architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes.” “A Common Perspective on Enterprise Architecture” http://feapo.org/wp- content/uploads/2013/11/AG_Issue9_4-FEAPOcut.pdf Business Process Management BPM is an enterprise-wide, structured approach to providing the products and services that your customer's value most. It is grounded in the premise that you must take a process view of your company in order to understand what products and services your customer values most. By understanding the key business processes your company uses to meet these customer needs, the gap between customer expectations and your ability to perform begins to emerge. http://www.bpminstitute.org/resources/articles/what-bpm-anyway- business-process-management-explained
Editor's Notes
- 原則上的治理還更多，corporate governance, operation governance, information governance, IT governance, security governance。任何對於目標的管理上都要經由治理去檢視 GRC 議題以確定組織一直如實地面對變遷往目標前進。 Under Control ISBN-13 (pbk): 978-1-4302-1592-9 ISBN-13 (electronic): 978-1-4302-1593-6 pg#3, #4 Governance, risk, and compliance (GRC) focuses on the activities related to the governance of regulatory requirements, enterprise risk areas such as financial and IT risk, compliance controls, and information across the enterprise. GRC is not a specific function in an organization, but rather an integrated approach across multiple business functions related to the management of risk, controls, and compliance. Historically, this management has often been handled by disparate groups with minimal interaction. More recently, there’s been a trend toward a more unified view of these areas to help controls costs, eliminate redundancy, and improve the quality of the information that is used to make decisions related to risk and compliance. GRC includes several different but related areas: • Enterprise risk management focuses on predicting and managing events that might impact the achievement of business goals. • Financial GRC relates to the quality, timeliness, and transparency of financial statements and transactions of the company. • IT GRC relates to managing IT risk and ensuring that the IT infrastructure supports corporate compliance needs. • Finally, information governance focuses on ensuring that the company’s information assets are known, categorized, and available when needed.
- An Exclusive Interview with John A. Zachman in Perspectives of the IASA --- ArtRogerSessionsInterview4.pdf overview of the Zachman Framework The Zachman Framework is a two dimensional classification scheme ... a normalized schema. It is the intersection of two classifications, the universal linguistic communication classification of primitive interrogatives: What, How, Where, Who, When and Why the classification of audience perspectives: Owner, Designer, Builder, bounded by the Scoping Perspective and the Implementation Perspective (Owner, Designer, Builder is more commonly known in the IT community as Concepts - Computation Independent; Logic - Platform Independent; and Technology – Platform Specific and the Scoping Perspective as the Boundary Definition; the Implementation perspective as Vendor Specific.) Top 21 Zachman Framework Myths – Busted question#14 http://live.icmgworld.com/index.php/blogs/entry/top-21-zachman-framework-myths-busted.html John uses the 2000 year old concept of reification i.e. how to transform an abstract idea to reality. Reification consist of 6 phases of transformation i.e. Identification (mapped to Row 1) Definition (mapped to Row 2) Representation (mapped to Row 3) Specification (mapped to Row 4) Configuration (mapped to Row 5) Instantiation (mapped to Row 6) The models in each row get transformed to the next Row below, and the Row 6 wraps up the 6th phase of reification
- Business motivation 是非常重要的，
- Strategy + Strategy execution = management
- Press Release: EA Perspectives White Paper http://feapo.org/press-release-ea-perspectives-white-paper/